Re: Objects not restored - Job ends normally

Walden:

On Mon, 10 December 2001, "Walden H. Leverich" wrote:

> On V5R1 I just submitted a restore from SAVF for a library, the job ran fine
> and then ended NORMALLY (ending code 0 according to the history log)
> HOWEVER, the history log also shows "2 objects restored. 56 not restored to
> WEPLEX." Shouldn't that message result in an abnormal end?

Maybe it should have; it's impossible to tell without knowing both what values 
you supplied to the RSTxxx command parms and what the reasons were that the 
objects did not restore. And depending on the reasons, we might also need to 
know a system value or two plus all related authorities.

A particular example could be that you specified ALWOBJDIF(*NONE) but the 
restore found significant differences for some objects. If so, then the objects 
were "correctly not restored"; hence, the job had no failure according to the 
parameters you set. (I'm not defending how it works, just trying to see if 
there's any logic.)

> PS. I assume changing message id CPF3773 to a severity > 20 would result in
> an abnormal end, no?

This would probably do what you expect for this particular case. But I wouldn't 
recommend it as a general technique. Too many other CL programs might be 
checking related diagnostic messages and expecting a SEV(30) to show up. This 
might be most true for install programs, both from IBM and from 3rd-party 
vendors.

Perhaps better would be to create a new *msgf and duplicate CPF3773 into it 
with SEV(30). Then you could use OVRMSGF only in jobs that need it without 
affecting others. Perhaps.

Tom Liotta

--
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788
Fax  253-872-7904
http://www.400Security.com


___________________________________________________
The ALL NEW CS2000 from CompuServe
 Better!  Faster! More Powerful!
 250 FREE hours! Sign-on Now!
 http://www.compuserve.com/trycsrv/cs2000/webmail/