Initial library list error tolerance
Starting in 7.1, the way certain errors are handled for the initial library list when starting certain types of
jobs has changed to allow the job to start. In prior releases, they would have received an error message
and the job would have been prevented from starting. When starting an interactive job, an autostart job, a
communications job, a prestart job, or starting a batch job that is on a job queue, if a library is not found
it now dropped from the library list. Also for these job types, if a library is specified more than once,
only the first reference is kept in the library list. Other interfaces affecting library lists are not changed.
I just tested a SBMJOB with initial library list jobd, jobd contained a library that does not exist.
At V7R1, I expected this job to run, but it behaved the same as at V6R1, CPF1153, Library .. not found, and CPF1338 Errors occurred on SBMJOB command.
I also tested an interactive job, jobd contains a library that does not exist.
At V6R1, job does NOT start, posts CPF1113 Library in initial library list not found
At V7R1, job does start, posts CPI146B Library in initial library list not found, (No one will ever see this message)
I'm a bit confused to what will run and not run.
The V6R1 logic was equal across the board, a good safety check, now its gone.
If a library was missing or a jobd was wrong, the job would not run.
Does anyone know why this was changed?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
midrange.com
