Wrong library list in job submitted by scheduler
Helen Edith Stephenson
A job submitted by the job scheduler appears to be taking its library
list from the QJOBSCD job and not from the job description specified on
the job schedule entry.
According to the OS/400 Work Management manual, the non-default value
*JOBD will be used for INLLIBL when the job scheduler submits a job.
This doesn't seem to be happening.
This is a long-standing entry in the job scheduler, and was apparently
working correctly until a day or two ago.
Any ideas, anyone?
AFAIK, no PTFs have been installed in the last week or two, and it's
puzzling why this library list should suddenly go wrong.
Helen
--
Helen Edith Stephenson <he...@baronmoss.nomed.co.uk#>
(change "nomed" to "demon" and remove # to reply)
http://www.baronmoss.demon.co.uk
Bruce Bardini
changed? When *CURRENT is specified for the initial library list, this
means that the submitted job will use the library list of the submitting
job. Maybe the INLLIBL should be *JOBD?
--
"Helen Edith Stephenson" <he...@baronmoss.nomed.co.uk#> wrote in message
news:f5UHTIAG...@baronmoss.demon.co.uk...
Helen Edith Stephenson
>news:f5UHTIAG...@baronmoss.demon.co.uk...
>> A customer has SBMJOB set up with INLLIBL(*CURRENT)
>>
>> A job submitted by the job scheduler appears to be taking its library
>> list from the QJOBSCD job and not from the job description specified on
>> the job schedule entry.
>>
>> According to the OS/400 Work Management manual, the non-default value
>> *JOBD will be used for INLLIBL when the job scheduler submits a job.
>>
>> This doesn't seem to be happening.
>>
>> This is a long-standing entry in the job scheduler, and was apparently
>> working correctly until a day or two ago.
>>
>> Any ideas, anyone?
>>
>> AFAIK, no PTFs have been installed in the last week or two, and it's
>> puzzling why this library list should suddenly go wrong.
>>
>> Helen
>
Bardini <bruc...@home.com> writes
>Hi Helen! Are you sure that the job parms in the job scheduler haven't been
>changed? When *CURRENT is specified for the initial library list, this
>means that the submitted job will use the library list of the submitting
>job. Maybe the INLLIBL should be *JOBD?
>
According to the OS/400 Work Management manual, the non-default value
*JOBD will be used for INLLIBL when the job scheduler does a SBMJOB.
This job definition has a valid job description on it.
The SBMJOB command on the system defaults to INLLIBL(*CURRENT) but the
job scheduler should be submitting the job with INLLIBL(*JOBD) according
to the manual.
A work colleague from another team has apparently come up against the
same problem and did a bit of playing around with it some time ago, and
in his opinion, when you add an entry to the job scheduler, that job
will be submitted with INLLIBL(*JOBD) but if you then go back in and
edit the entry, somehow the scheduler stops using INLLIBL(*JOBD) and
goes back to using the default INLLIBL(*CURRENT).
This is not what the manual says the job scheduler will do, and it could
be that IBM need to issue a PTF to sort this out.
Helen Edith Stephenson
Stephenson <he...@baronmoss.nomed.co.uk#> writes
The same colleague who said that he had observed that the job scheduler
was not working according to what the manual said did some playing
around on our new (this year) RISC box and the library lists of the jobs
it submitted were consistently correct. He is of the opinion that IBM
may have fixed whatever ailed the scheduler in earlier releases of
OS/400.
We've got around it on our client site by scheduling a SBMJOB which
submits the job we really want with INLLIBL(*JOBD) explicitly coded.
That's probably the best solution for now, as I don't think they're in a
position to upgrade OS/400 at present.