Research helps....

This topic describes: 

Where the master JCL resides
How to change the master JCL
How to set up started tasks with the master JCL
How to write your own master JCL.
IBM® supplies default master JCL in the MSTJCL00 load module in SYS1.LINKLIB.  
Figure 1 shows MSTJCL00 as it exists before it is assembled and link-edited 
into SYS1.LINKLIB:

Figure 1. MSTJCL00 Load Module in SYS1.LINKLIB
MSTJCL00 CSECT DC CL80'
  //MSTJCL00 JOB MSGLEVEL=(1,1),TIME=1440' DC CL80'// EXEC PGM=IEEMB860' DC 
CL80'//STCINRDR DD SYSOUT=(A,INTRDR)' DC CL80'//TSOINRDR DD SYSOUT=(A,INTRDR)' 
DC CL80'//IEFPDSI DD DSN=SYS1.PROCLIB,DISP=SHR' DC CL80'//SYSUADS DD 
DSN=SYS1.UADS,DISP=SHR' DC CL80'/*' END
MSTJCL00 contains:

DD statements needed to define the internal reader data sets for started task 
control and TSO/E logons
SYS1.UADS, a system data set used in TSO/E logons and terminal communications.
MSTJCL00 does not contain the START command that starts the primary job entry 
subsystem during master scheduler initialization. You can define and start the 
primary job entry subsystem using the PRIMARY parameter in the IEFSSNxx parmlib 
member.

Your installation can either use the default master JCL (shown in Figure 1) or 
specify an alternate version of the master JCL, as described in Changing the 
master scheduler JCL.

  

Sorry about the wrap guys and gals on my iPad..


Scott ford
www.identityforge.com
from my IPAD




> On Dec 18, 2014, at 1:50 PM, Jousma, David <david.jou...@53.com> wrote:
> 
> 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
> david.jou...@53.com
> 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:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Charles Mills
> Sent: Thursday, December 18, 2014 12:25 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Jousma, David
> Sent: Thursday, December 18, 2014 5:32 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 david.jou...@53.com
> 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:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Charles Mills
> Sent: Wednesday, December 17, 2014 8:05 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 
> lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to