iSeries backup question

Hi.

I'm using OS400 backup procedures.
Each night QEZBKT.... job starts and perform backup.
Then I see in QHST log list of libraries which was saved.
There is an information about library name and how many objects were
or
were not saved.

Problem is that I can't find out how to check which objects were not
saved.
I've configured backup to print detailed report. It creates QPJOBLOG
spool file with lot of inforation but it's difficult to find list of
non-saved objects.

Is there a way to find out which were not saved ?

Regards,
Tomasz

CHGJOBD QEZBACKUP LOG(4 20 *seclvl)



tomasz <t.stefaniak@gmail.com> wrote in news:1188505583.577492.109790
@i38g2000prf.googlegroups.com:
[color=blue]
> Hi.
>
> I'm using OS400 backup procedures.
> Each night QEZBKT.... job starts and perform backup.
> Then I see in QHST log list of libraries which was saved.
> There is an information about library name and how many objects were
> or
> were not saved.
>
> Problem is that I can't find out how to check which objects were not
> saved.
> I've configured backup to print detailed report. It creates QPJOBLOG
> spool file with lot of inforation but it's difficult to find list of
> non-saved objects.
>
> Is there a way to find out which were not saved ?
>
> Regards,
> Tomasz
>
>[/color]



--
Ad,

What's The Use Of Getting Sober
(When You're Gonna Get Drunk Again)

On Aug 30, 1:26 pm, tomasz <t.stefan...@gmail.com> wrote:[color=blue]
> Hi.
>
> I'm using OS400 backup procedures.
> Each night QEZBKT.... job starts and perform backup.
> Then I see in QHST log list of libraries which was saved.
> There is an information about library name and how many objects were
> or
> were not saved.
>
> Problem is that I can't find out how to check which objects were not
> saved.
> I've configured backup to print detailed report. It creates QPJOBLOG
> spool file with lot of inforation but it's difficult to find list of
> non-saved objects.
>
> Is there a way to find out which were not saved ?
>
> Regards,
> Tomasz[/color]

Change the save command to output the save to *OUTFILE using *ERR as
the parameter for INFTYPE. This will create a file containing all
objects that did not save. Or use *OBJ as the INFTYPE. This will
create a file listing all objects procesed (saved or not) that can be
queried to show unsaved objects or whatever else you'd want to query
on. I do a *REPLACE on the outfile so it is fresh after every save.

HTH,

Thad Rizzi

Hi.
Save commands in job scheduler looks like:
RUNBCKUP BCKUPOPT(*DAILY) co I can't change any SAV* parameter.
Any idea?

Regards,
Tomasz


Thad Rizzi pisze:[color=blue]
> On Aug 30, 1:26 pm, tomasz <t.stefan...@gmail.com> wrote:[color=green]
>> Hi.
>>
>> I'm using OS400 backup procedures.
>> Each night QEZBKT.... job starts and perform backup.
>> Then I see in QHST log list of libraries which was saved.
>> There is an information about library name and how many objects were
>> or
>> were not saved.
>>
>> Problem is that I can't find out how to check which objects were not
>> saved.
>> I've configured backup to print detailed report. It creates QPJOBLOG
>> spool file with lot of inforation but it's difficult to find list of
>> non-saved objects.
>>
>> Is there a way to find out which were not saved ?
>>
>> Regards,
>> Tomasz[/color]
>
> Change the save command to output the save to *OUTFILE using *ERR as
> the parameter for INFTYPE. This will create a file containing all
> objects that did not save. Or use *OBJ as the INFTYPE. This will
> create a file listing all objects procesed (saved or not) that can be
> queried to show unsaved objects or whatever else you'd want to query
> on. I do a *REPLACE on the outfile so it is fresh after every save.
>
> HTH,
>
> Thad Rizzi
>[/color]

il 30/08/2007 22.26, Scrive tomasz 40375864:[color=blue]
> Hi.
>
> I'm using OS400 backup procedures.
> Each night QEZBKT.... job starts and perform backup.
> Then I see in QHST log list of libraries which was saved.
> There is an information about library name and how many objects were
> or
> were not saved.
>
> Problem is that I can't find out how to check which objects were not
> saved.
> I've configured backup to print detailed report. It creates QPJOBLOG
> spool file with lot of inforation but it's difficult to find list of
> non-saved objects.
>
> Is there a way to find out which were not saved ?[/color]
Using operational assistant backup you can specify a backup exit-program
on the EXITPGM parameter of CHGBCKUP command for each back-up option
(*DAILY *WEEKLY *MONTHLY), the program may be the same for any option.
The program will be called before and after the backup with a fixed
parameter list, refer to
[url]http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/XEZBCKUP.htm[/url]
for the complete documentation.
When the program is called *after with a return code difeerent from
CPC1E62 it means that something went wrong during backup. At this event
the exit program should DSPOBJD *all/*all *outfile and select from the
outfile the objects that have not the same volume, that appear in input
parameters, and have a save date/time that's not compatible with the
actual date/time, a date/time not included between the time the program
was called *BEFORE and the time the program was called *after.
The selection as above includes all objects, so the objects that were
not included in the back-up otion too. So you should have a method to
omit objects that were not included in the backup either on dspobjd
command or during the selection. The information about library backup
planning, is held in QEZBACKUPL *USRIDX, that lists libraries that have
were omitted from a backup option, eg if a library has to be saved only
*MONTHLY will have options flags set to 001, a library that have never
to be saved will have options flags set to 000. So the first flag is set
to 1 if *daily was specified, the second for *weekly and the third for
*monthly.
The same can be done for folders, but the information is held in
QEZBACKUPF *USRIDX in the same fashion, while for IFS directory there's
no list to check.
To have an idea how those *usridx are made DMPOBJ OBJ(QEZBACKUPL)
OBJTYPE(*USRIDX) and look at the QPSRVDMP spooled file in the current
job. To access usridx objects you can use usridx apis, either to get
usridx attributes (as entry length) and to get each entry value. Refer
to
[url]http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/obj4.htm[/url]




--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherAñejoAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers vão à merda
Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'

Hi.

Thanks for information, it was very helpfull.
Unfortunatelly I don't know how to read *USRIDX file to get list of
libraries which are backed up.

Regards,
Tomasz


Dr.UgoGagliardelli pisze:[color=blue]
> il 30/08/2007 22.26, Scrive tomasz 40375864:[color=green]
>> Hi.
>>
>> I'm using OS400 backup procedures.
>> Each night QEZBKT.... job starts and perform backup.
>> Then I see in QHST log list of libraries which was saved.
>> There is an information about library name and how many objects were
>> or
>> were not saved.
>>
>> Problem is that I can't find out how to check which objects were not
>> saved.
>> I've configured backup to print detailed report. It creates QPJOBLOG
>> spool file with lot of inforation but it's difficult to find list of
>> non-saved objects.
>>
>> Is there a way to find out which were not saved ?[/color]
> Using operational assistant backup you can specify a backup exit-program
> on the EXITPGM parameter of CHGBCKUP command for each back-up option
> (*DAILY *WEEKLY *MONTHLY), the program may be the same for any option.
> The program will be called before and after the backup with a fixed
> parameter list, refer to
> [url]http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/XEZBCKUP.htm[/url]
> for the complete documentation.
> When the program is called *after with a return code difeerent from
> CPC1E62 it means that something went wrong during backup. At this event
> the exit program should DSPOBJD *all/*all *outfile and select from the
> outfile the objects that have not the same volume, that appear in input
> parameters, and have a save date/time that's not compatible with the
> actual date/time, a date/time not included between the time the program
> was called *BEFORE and the time the program was called *after.
> The selection as above includes all objects, so the objects that were
> not included in the back-up otion too. So you should have a method to
> omit objects that were not included in the backup either on dspobjd
> command or during the selection. The information about library backup
> planning, is held in QEZBACKUPL *USRIDX, that lists libraries that have
> were omitted from a backup option, eg if a library has to be saved only
> *MONTHLY will have options flags set to 001, a library that have never
> to be saved will have options flags set to 000. So the first flag is set
> to 1 if *daily was specified, the second for *weekly and the third for
> *monthly.
> The same can be done for folders, but the information is held in
> QEZBACKUPF *USRIDX in the same fashion, while for IFS directory there's
> no list to check.
> To have an idea how those *usridx are made DMPOBJ OBJ(QEZBACKUPL)
> OBJTYPE(*USRIDX) and look at the QPSRVDMP spooled file in the current
> job. To access usridx objects you can use usridx apis, either to get
> usridx attributes (as entry length) and to get each entry value. Refer
> to
> [url]http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/obj4.htm[/url]
>
>
>
>[/color]

il 31/08/2007 13.20, Scrive tomasz 40375864:[color=blue]
> Hi.
>
> Thanks for information, it was very helpfull.
> Unfortunatelly I don't know how to read *USRIDX file to get list of
> libraries which are backed up.[/color]
I told you, using User Index APIs. See the bottom of my previous post.
Its not difficult at all. You can wrap that APIs even in a file SPECIAL
exit program to read index entries fom an RPG program with READ op.code,
if it's more comfortable to you.
But if you prefer, it's not as smart as I like, you can read and parse
the spooled file produced by the DMPOBJ Command as well.[color=blue][color=green]
>> To have an idea how those *usridx are made DMPOBJ OBJ(QEZBACKUPL)
>> OBJTYPE(*USRIDX) and look at the QPSRVDMP spooled file in the current
>> job. To access usridx objects you can use usridx apis, either to get
>> usridx attributes (as entry length) and to get each entry value. Refer
>> to
>> [url]http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/obj4.htm[/url][/color][/color]


--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherAñejoAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers vão à merda
Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'

Sorry,my mistake.

Thank you very much for help.

Tomasz



Dr.UgoGagliardelli pisze:[color=blue]
> il 31/08/2007 13.20, Scrive tomasz 40375864:[color=green]
>> Hi.
>>
>> Thanks for information, it was very helpfull.
>> Unfortunatelly I don't know how to read *USRIDX file to get list of
>> libraries which are backed up.[/color]
> I told you, using User Index APIs. See the bottom of my previous post.
> Its not difficult at all. You can wrap that APIs even in a file SPECIAL
> exit program to read index entries fom an RPG program with READ op.code,
> if it's more comfortable to you.
> But if you prefer, it's not as smart as I like, you can read and parse
> the spooled file produced by the DMPOBJ Command as well.[color=green][color=darkred]
>>> To have an idea how those *usridx are made DMPOBJ OBJ(QEZBACKUPL)
>>> OBJTYPE(*USRIDX) and look at the QPSRVDMP spooled file in the current
>>> job. To access usridx objects you can use usridx apis, either to get
>>> usridx attributes (as entry length) and to get each entry value.
>>> Refer to
>>> [url]http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/obj4.htm[/url][/color][/color]
>
>
>[/color]

If you go the menu SETUPBCKUP, as long as you have authority, you can select
the Daily, Weekly or Monthly option and then with F16, you can change the
libraries to be saved.

Peter

"tomasz" <tom@nospam.com> wrote in message
news:fb8v75$d3v$1@atlantis.news.tpi.pl...[color=blue]
> Sorry,my mistake.
>
> Thank you very much for help.
>
> Tomasz
>
>
>
> Dr.UgoGagliardelli pisze:[color=green]
>> il 31/08/2007 13.20, Scrive tomasz 40375864:[color=darkred]
>>> Hi.
>>>
>>> Thanks for information, it was very helpfull.
>>> Unfortunatelly I don't know how to read *USRIDX file to get list of
>>> libraries which are backed up.[/color]
>> I told you, using User Index APIs. See the bottom of my previous post.
>> Its not difficult at all. You can wrap that APIs even in a file SPECIAL
>> exit program to read index entries fom an RPG program with READ op.code,
>> if it's more comfortable to you.
>> But if you prefer, it's not as smart as I like, you can read and parse
>> the spooled file produced by the DMPOBJ Command as well.[color=darkred]
>>>> To have an idea how those *usridx are made DMPOBJ OBJ(QEZBACKUPL)
>>>> OBJTYPE(*USRIDX) and look at the QPSRVDMP spooled file in the current
>>>> job. To access usridx objects you can use usridx apis, either to get
>>>> usridx attributes (as entry length) and to get each entry value. Refer
>>>> to
>>>> [url]http://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=/apis/obj4.htm[/url][/color]
>>
>>[/color][/color]

il 31/08/2007 17.23, Scrive Peter Kinsman 40375864:[color=blue]
> If you go the menu SETUPBCKUP, as long as you have authority, you can select
> the Daily, Weekly or Monthly option and then with F16, you can change the
> libraries to be saved.
>
> Peter[/color]

Do it in batch.


--
Dr.Ugo Gagliardelli,Modena,ItalyCertifiedUindoscrasherAñejoAlcoolInside
Spaccamaroni andate a cagare/Spammers not welcome/Spammers vão à merda
Spamers iros a la mierda/Spamers allez vous faire foutre/Spammers loop
schijten/Spammers macht Euch vom Acker/Spamerzy wypierdalac'