AW: Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-27 Thread Peter Hunkeler
>Seriously, no one cited security as a "why" for this restriction. Part of a proper system setup anc change management is to limit who can use the START command, possibly what he/she can START and for sure who can apply changes to JCL the JCL (procedure) libraries in discussion. If this JCL cou

Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-25 Thread Shmuel Metz (Seymour J.)
In <20141221173446.fd8ed08264703ad3452c5...@gmx.net>, on 12/21/2014 at 05:34 PM, ibmmain said: >Nice summary, Peter. Do you happen to know who puts in //STARTING JOB >... when MEMBER is only contained in the JES2 proclib concatenation >and not in MSTJCL? Presumably IEEVSTAR for START, but the

Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-24 Thread Charles Mills
:33 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: //STARTING JOB ... was: Re: JCLLIB in started proc? On Wed, 24 Dec 2014 04:55:19 -0800, Charles Mills wrote: >Briefly, I would like to add a JCLLIB/INCLUDE to a proc in the PROCLIB >concatenation. I have to go with my hat in my hand to the

Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-24 Thread Walt Farrell
On Wed, 24 Dec 2014 04:55:19 -0800, Charles Mills wrote: >Briefly, I would like to add a JCLLIB/INCLUDE to a proc in the PROCLIB >concatenation. I have to go with my hat in my hand to the powers that be to >edit the PROCLIB. (No approval needed for the specific changes; just to make >any change.)

Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-24 Thread John McKown
On Wed, Dec 24, 2014 at 6:55 AM, Charles Mills wrote: > Briefly, I would like to add a JCLLIB/INCLUDE to a proc in the PROCLIB > concatenation. I have to go with my hat in my hand to the powers that be to > edit the PROCLIB. (No approval needed for the specific changes; just to > make > any chang

Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-24 Thread Charles Mills
: //STARTING JOB ... was: Re: JCLLIB in started proc? > If we could solve your problem we could also solve mine presumably. Sorry, Charles, I've lost track of what you initial problem was. Would you like to reiterate? --

AW: Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-23 Thread Peter Hunkeler
> If we could solve your problem we could also solve mine presumably. Sorry, Charles, I've lost track of what you initial problem was. Would you like to reiterate? -- Peter Hunkeler -- For IBM-MAIN subscribe / signoff / arch

AW: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-23 Thread Peter Hunkeler
> Nice summary, Peter. Thanks > Do you happen to know who puts in //STARTING JOB ... when MEMBER is only > contained in the JES2 proclib concatenation and not in MSTJCL? You probably mean //STARTING EXEC ... not //STARTING JOB, do you? Well, again, I can only tell from what is my understandi

Re: //STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-21 Thread Charles Mills
mmain Sent: Sunday, December 21, 2014 8:35 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: //STARTING JOB ... was: Re: JCLLIB in started proc? > The START command processor needs to build and "initiate" some JCL to start what was requested. The JCL will be sent to a subsystem that is able t

//STARTING JOB ... was: Re: JCLLIB in started proc?

2014-12-21 Thread ibmmain
> The START command processor needs to build and "initiate" some JCL to start > what was requested. The JCL will be sent to a subsystem that is able to > process that JCL. The Master Subsystem (MSTR) and the Job Entry Subsystems 2 > (JES2) and 3 (JES3) are the ones I know. > The first operand