Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
WRKJOBSCDE/ADDJOBSCDE question and JOBD parameter
926 views
Skip to first unread message
Mr. K.V.B.L.
Aug 2, 2012, 9:59:48 AM8/2/12
to
When I add a job to the job scheduler, the JOBD parameter implies, at least to me, that it will use the library list of the job description I put in there. That doesn't happen, apparently. I think it's silly to have to do a SBMJOB command, which has a INLLIBL parameter, inside of a job scheduler entry, which is doing a SMBJOB command itself.
It makes me wonder what the purpose of the JOBD parameter is, in the context of WRKJOBSCDE, in the first place.
So, help me out here. Am I missing something? I'd like to just run my command/program cleanly without having to crowd a bunch of SMBJOB command stuff in there.
It makes me wonder what the purpose of the JOBD parameter is, in the context of WRKJOBSCDE, in the first place.
So, help me out here. Am I missing something? I'd like to just run my command/program cleanly without having to crowd a bunch of SMBJOB command stuff in there.
larry_...@hotmail.com
Aug 3, 2012, 7:28:40 AM8/3/12
to
On Thursday, August 2, 2012 9:59:48 AM UTC-4, Mr. K.V.B.L. wrote:
> When I add a job to the job scheduler, the JOBD parameter implies, at least to me, that it will use the library list of the job description I put in there. That doesn't happen, apparently. I think it's silly to have to do a SBMJOB command, which has a INLLIBL parameter, inside of a job scheduler entry, which is doing a SMBJOB command itself. It makes me wonder what the purpose of the JOBD parameter is, in the context of WRKJOBSCDE, in the first place. So, help me out here. Am I missing something? I'd like to just run my command/program cleanly without having to crowd a bunch of SMBJOB command stuff in there.
I am not sure of the conditions, and since nobody has replied: here is my "2 cents".
> When I add a job to the job scheduler, the JOBD parameter implies, at least to me, that it will use the library list of the job description I put in there. That doesn't happen, apparently. I think it's silly to have to do a SBMJOB command, which has a INLLIBL parameter, inside of a job scheduler entry, which is doing a SMBJOB command itself. It makes me wonder what the purpose of the JOBD parameter is, in the context of WRKJOBSCDE, in the first place. So, help me out here. Am I missing something? I'd like to just run my command/program cleanly without having to crowd a bunch of SMBJOB command stuff in there.
If you are doing WRKJOBSCDE, and submitting a job (*IMMED) from the list, then it is probably picking up your library list from your workstation session. If it is submitted by the system (viva time), the system will use the library list from the JOBD.
Christian Bartels
Aug 6, 2012, 4:30:19 AM8/6/12
to
Specifying INLLIBL in the job description affects only the user part of the
library list, not the system part. On my system, I could setup a personal
user library list through a job description, and the job would use it when
starting it through WRKJOBSCDE. If you need a library in the system part of
the library list (such as a secondary language library), you can specify
that in the subsystem description.
If your job description specifies a library in INLLIBL that is already part
of the system part of the library list, submitting the job will fail with
CPI1141 "Job not submitted for job schedule entry...", because duplicate
entries are not allowed in the resulting library list.
Kind regards,
Christian Bartels.
"Mr. K.V.B.L." <kenvery...@gmail.com> wrote in message
news:8660d47a-658c-4e9c...@googlegroups.com...
library list, not the system part. On my system, I could setup a personal
user library list through a job description, and the job would use it when
starting it through WRKJOBSCDE. If you need a library in the system part of
the library list (such as a secondary language library), you can specify
that in the subsystem description.
If your job description specifies a library in INLLIBL that is already part
of the system part of the library list, submitting the job will fail with
CPI1141 "Job not submitted for job schedule entry...", because duplicate
entries are not allowed in the resulting library list.
Kind regards,
Christian Bartels.
"Mr. K.V.B.L." <kenvery...@gmail.com> wrote in message
news:8660d47a-658c-4e9c...@googlegroups.com...
0 new messages