Yes, proclib is in there. //MSTJCL00 JOB MSGLEVEL=(1,1),TIME=1440 // EXEC PGM=IEEMB860,DPRTY=(15,15) //STCINRDR DD SYSOUT=(A,INTRDR) //TSOINRDR DD SYSOUT=(A,INTRDR) //IEFPDSI DD DSN=SYS1.PROCLIB,DISP=SHR // DD DSN=SYS1.IBM.PROCLIB,DISP=SHR //SYSUADS DD DSN=SYS1.UADS,DISP=SHR //IEFJOBS DD DSN=SYS1.STCJOBS,DISP=SHR
I was equally surprised when I tested my sample I provided and it worked. I don't know why it worked. Thanks for the clarification _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Pommier, Rex Sent: Thursday, December 18, 2014 2:46 PM To: [email protected] Subject: Re: JCLLIB in started proc? Dave and Charles, I would guess that SYS1.PROCLIB is in your MSTJCL00 member under the IEFPDSI DD card concatenation. I just did a bit of high level testing, as I have a PROCLIB that is in my JES2 concatenation, but not in the IEFPDSI concatenation. I placed a simple job in this PROCLIB and got the "misplaced job statement" and "misplaced JCLLIB statement". I then copied the PROC to SYS1.PROCLIB and ran the same JCO, and it ran successfully. The relevant line out of the init and tuning reference is this: "If the source JCL for a started task is a job, the member containing the JCL must be part of a data set in the IEFPDSI DD or the IEFJOBS DD concatenation of MSTJCLxx. (If the member is not part of a data set in the IEFPDSI or IEFJOBS concatenation of MSTJCLxx, the procedures that act as source JCL for other started tasks will not be found.) IBM suggests that you define a new data set in MSTJCLxx (pointed to by the IEFJOBS DD statement) that will contain the tailored JCL to support started tasks." Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Thursday, December 18, 2014 12:51 PM To: [email protected] Subject: Re: JCLLIB in started proc? Charles, Everything you said it true, except: - You cannot use a JOB statement in a started PROC unless MSTJCL DD IEFJOBS or IEFPDSI points to the PDS; mere inclusion in the PARMLIB concatenation is not enough. I just tested putting a full jobcard, and JCLLIB statement into proclib, and it worked. Not sure I know why, though. DD IEFJOBS was added back in the MVS V5 days which is/was intended to be support for jobcards on STC's. EDIT SYS1.PROCLIB(EKMSERV) - 01.04 Command ===> ****** ********************************* Top of Data ******* 000001 //EKMSERV JOB (DP,3640),'JAVA EKM SERVER', 000002 // MSGLEVEL=(1,1), 000003 // MSGCLASS=C 000004 //* 000005 //OUT1 OUTPUT JESDS=ALL,CLASS=C 000006 //PROCS JCLLIB ORDER=(E008058.PROCLIB) 000007 //*-------------------------------------------------- 000008 //* Execute ISKLM 000009 //*-------------------------------------------------- 000010 //* 000011 //ISKLM EXEC JVMPROC, 000012 // JAVACLS='com.ibm.jzosekm.ISKLMConsoleWrapper' 000013 //* 000014 //STDENV DD DSN=SYSV.JAVAPRMS(CKLENV),DISP=SHR _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Thursday, December 18, 2014 12:25 PM To: [email protected] Subject: Re: JCLLIB in started proc? Okay, to summarize this as I now understand it. Someone please correct me if I am wrong. I will use the shorthand "started PROC" to mean "a procedure stored as a member in a PDS that is intended to be the operand of a successful console Start command." - You cannot use a JCLLIB statement in a started PROC unless the PROC begins with a JOB statement. - You cannot use a JOB statement in a started PROC unless MSTJCL DD IEFJOBS or IEFPDSI points to the PDS; mere inclusion in the PARMLIB concatenation is not enough. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Thursday, December 18, 2014 5:32 AM To: [email protected] Subject: Re: JCLLIB in started proc? Charles, as others have pointed out, you cannot add jobcard JCLLIB statements to the PROCLIB member. You must modify/configure MSTJCL to include a IEFJOBS dd statement pointing at a PDS dataset. In that library, you can code a jobcard and JCLLIB statement that calls the proc you want. _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Charles Mills Sent: Wednesday, December 17, 2014 8:05 PM To: [email protected] Subject: JCLLIB in started proc? I just added a JCLLIB statement to a cataloged procedure that I start with a Start command. I am getting IEFC019I MISPLACED JCLLIB STATEMENT. Should I infer that JCLLIB is not allowed in a started PROC, or should I be looking for a fat-finger coding error? (I want the JCLLIB for INCLUDE, not EXEC PROC=.) I RTFM but don't see anything explicit. It does refer to "in a job" at several points. Is JCLLIB allowed in a started PROC if the PROC has a JOB statement? I know I can do that but I've never done it. Where is that documented? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
