> -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[EMAIL PROTECTED] On Behalf Of Johnny Luo > Sent: Tuesday, January 03, 2006 7:47 AM > To: IBM-MAIN@BAMA.UA.EDU > Subject: Define and start JES2 > > > New to mainframe..so the question maybe look a little silly. > > Here is what IEFSSN00 of our site defines JES2: > > SUBSYS SUBNAME(JES2) /* JES2 AS PRIMARY SUBSYSTEM */ > PRIMARY(YES) START(NO) > > My question is concerning parmameter SUBNAME: > > Is it true that it must be the same name as JES2 procedure? > Take the above IEFSSN00 for example,do I need to name the > JES2 procedure 'JES2' also?Or I can use another name for it,say, > JESA？ >
I strongly agree with all the others. Keep the SUBNAME and the PROC name the same. It simply makes it easier. However, on my "sandbox", I did do the following: copy JES2 to JESX in SYS1.PROCLIB $PJES2,ABEND to terminate JES2 S JESX,JOBNAME=JES2 This did start up the JES2 subsystem. So, in your case, you __COULD__ use JESA, but you must remember to put the parameter JOBNAME=JES2 on it. The only use I see for this is if you are going to change the JES2 proc. You could copy the current JES2 proc to JESx. Update the JES2 proc and restart JES2 (or reIPL). If JES2 failed, you could try the alternate S JESX,JOBNAME=JES2 to go back to the old JES2 proc. -- John McKown Senior Systems Programmer UICI Insurance Center Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
