Re: Some Authority Change V4R1-V4R5 Submitted jobs ?

[thomas@xxxxxxxxxxx]

Chuck:

On Tue, 06 November 2001, Chuck Lewis wrote:

> Went from V4R1 to V4R5 this weekend (FINALLY) and we use the Robot Job
> Scheduler to submit jobs to run.
>
> Well certain jobs were bombing.
(snipped)
> So I created an additional jobd description and called it HDJPACK_2 and
> (placed it in one of our libraries) and lncluded the libraries that they
> had in HDJPACK and then I added our program libraries and now everything
> is fine...

Though it seems likely to be a library list problem, tracking it down might be 
complicated. Lots of variables in going from V4R1 to V4R5.

Another post mentioned that the various library list parameters for SBMJOB have 
changed over time, though I can no longer recall when the changes happened. (I 
think those have all been *CURRENT since version 3 at least.) However, even if 
the changes didn't happen between R1 and R5, it's possible that your V4R1 
SBMJOB command had default changes applied and those changes were lost during 
your upgrade and now you're back to the "original" *CURRENT.

I might vote for that possibility but there are others that are less likely. 
Two that come to mind easily are that your previous batch *sbsd had a library 
specified for SYSLIBLE() but now it's reverted to SYSLIBLE(*NONE) and that you 
had a routing program that modified the job's *libl at run-time but the routing 
entry is lost.

I imagine some thought would bring a few others to mind.

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/