Here are some of the benefits of using a Started Job through the IEFJOBS process: * Started Jobs (from IEFJOBS) run under the same general security as Started Tasks. You can, however, specify a USER=xxx parameter on the JOB card (be sure the proper Surrogate rules are in place) or a USER=xxx,PASSWORD=xxx value (not recommended for obvious reasons). * Since the execution is via a console START, normal job initiators are not used, and the job is started immediately, without consideration of any resources needed. * Also, since initiators are not used, the Started Job will always have a clean address space. * Like a normal job, the JCL you mentioned can be used. Since you have a JOB card, you can also keep the JCLLIB and INCLUDE members. * Unlike a Started Task, Started Jobs can use DD DUMMY and DD * files. * Accounting information can come from the JOB card accounting, rather than having to specify special STEP accounting (in a multi-step execution).
I hope this is somewhat helpful for you. Merry Christmas! Billy On Wed, Dec 17, 2014 at 10:02 PM, Lizette Koehler <stars...@mindspring.com> wrote: > > I did a quick internet search using ibm stc jcl with jobcard > > I found this > > Job Cards for Started Tasks > Sometime around MVS/ESA V5.1, IBM introduced job card support for started > tasks. To use this feature, the started task JCL must reside in a dataset > specified in either the IEFJOBS or IEFPDSI DD statements of the master > scheduler JCL (MSTJCLxx PARMLIB member). Refer to "MVS Initialization and > Tuning Reference" for some suggestions on how to set this up. > For the purpose of the following examples, I will presume that a separate > IEFJOBS dataset has been allocated. > Adding Accounting Information > > A typical member in IEFJOBS could look like this: > > //JES2 JOB (8022,BX00) **** JOB CARD SUPPORT > //IEFPROC EXEC JES2 > The JCL for JES2 will be picked up from the IEFPDSI concatenation. The > resulting started task JCL could look something like: > > //JES2 JOB (8022,BX00), > // MSGLEVEL=1 > //IEFPROC EXEC JES2 > At this point, we have added some accounting information to the started > task. > Additional Features > Now, you are able to add other features to the started task JCL. For > instance, say you wished to change the output characteristics for the > started task. You could do something like this: > > //INIT JOB (8024,BX00) **** JOB CARD SUPPORT > //DFLT OUTPUT JESDS=ALL,CLASS=Z > //IEFPROC EXEC INIT > So this started task can have a different sysout class than others. > Another > new capability is getting the started task JCL from somewhere else: > > //TAPEINI JOB (8100,BX01) **** JOB CARD SUPPORT > //STCJCL JCLLIB ORDER=(TAPELIB.STCJCL) > //TPINIT EXEC TAPEINI > The JCL for TAPEINI will be picked up from TAPELIB.STCJCL. > Notes > If you specify the PARM option on the MVS START command; for example, > > S JES2,PARM='WARM,NOREQ' > the specified PARM value will not be used if you are using job cards. An > alternative method of accomplishing the same result, is to set up a > symbolic > parameter PRM in the PROC for JES2 which will be substituted into the PARM > value of the EXEC statement and use the command > > S JES2,PRM='WARM,NOREQ' > instead. Your JES2 PROC (in IEFPDSI) would look like: > > //JES2 PROC PRM='WARM,NOREQ' > //IEFPROC EXEC PGM=HASJES20,PARM='&PRM', > ..... etc .... > > If a job card member is not present in the IEFJOBS dataset, then the > started > task JCL will be built and work as before. > I have only scratched the surface on this subject. Refer to the chapter on > "Started Tasks" in "MVS JCL Reference" for more information. Go to the > links > page to find OS/390 books on the Web. > > > Check what libraries are in your MSTJCLxx member in SYS1.PARMLIB > > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > > Behalf Of Charles Mills > > Sent: Wednesday, December 17, 2014 6: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? > > > > Thanks, > > > > Charles > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Thank you and best regards, *Billy Ashton* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
