Mcl
2500 pts. | Aug 12 2009 3:51PM GMT
You should also check the job log from the scheduled job that runs the backup. It might be helpful to turn on all logging for that job for a day or two to get all the details.
Regards
Mike
Pdraebel
865 pts. | Aug 13 2009 8:38AM GMT
Checking the History Log is one thing you can do.
DSPLOG JOB(Backup) MSGID(CPF3701 CPF3741)
Another option is to have your Backup commands create output files and checking those files. This could be handy if you needed to create a procedure to make a copy of unsaved objects anyway.
Peter
Splat
1040 pts. | Aug 13 2009 2:30PM GMT
If possible, enable the SAVACT parameter on your SAVxxx command.
Eduardb
50 pts. | Aug 14 2009 9:49AM GMT
To be complete after a full system save you can check the systemlog for all the appropriate messages which are DSPLOG PERIOD((’savetime’ ‘date of save’)) MSGID(CPC3702 CPC3707 CPC370C CPC9410) then you get the completion messages of the SAVSYS SAVLIB (nonsys) SAVDLO ans SAV commands. If you get 4 answers all the save were OK.
Eduard






