Thanks. Yes, you answered the right question. Re-phrasing your answer - In all cases (started procs, ordinary jobs, whatever) JCLLIB must come before the first EXEC so as to keep the resolution of proc names simple and unambiguous. - In a started proc with no JOB statement, the command processor builds the JOB and EXEC PROC=, so there is no convenient way to insert a JCLLIB statement in-between.
> why should it? You can create jobs including JCLLIB easily In my particular case, I have to jump through some (modest) hoops to update a start-eligible proclib. (And for whatever reason, the only start-eligible proclib I can update at all is not in the JOB-statement-permitted concatenations.) I thought if I could include JCL from my own PDS via JCLLIB and INCLUDE it would make my life easier. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter Hunkeler Sent: Sunday, December 21, 2014 6:30 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: AW: Re: JCLLIB in started proc? > Thanks. Digressing ... any idea of the WHY for this restriction? What restriction? The restriction that JCLLIB is only allowed in cased 1a) and 2a)? Only guessing here. I suspect that it would have made things too complex if JCLLIB was allowed anywhere in JCL. Imagine a procedure was resolved and within that part, a new JCLLIB was defined before another procedure had to resolved, etc., etc. Nesting is allowed for up to 15 levels. So a design decision was taken to allow JCLLIB only between the JOB statement and the first EXEC statement in a job. If not case 1a) or 2a), the JOB and EXEC statements are built by the START command processor. There is no way to place a JCLLIB, unless the START command itself would support some keyword to specify a library that trigged building a JCLLIB statement between the JOBs and the EXEC statments. It does not, and honestly why should it? You can create jobs including JCLLIB easily. If this is not an answer to your question, please be more specific. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
