Re: Define and start JES2
In fact, the command is xPJES2, where x is what is specified as CONCHAR= on the CONDEF init statement. The default is $ but you may want to select something else for a secondary JES. 2 more comments: That CONCHAR (in case of my alternate JES a .) also precedes HASP-Messages. They look like this: .HASPxxx. So automation may be affected. If IEFUSI fails a job if it does not have a knwon subsystem name you want to include the name of your JES in IEFUSI. My USI checks for subsystem 'JES2', and when I started my alternate JES as JESX (to test new JES exits), all my jobs sent there were getting a JCL error - until I included subsystem 'JESX' in USI. Regards, Barbara Nitz -- Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko! Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner -- 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
Re: Define and start JES2
In [EMAIL PROTECTED], on 01/04/2006 at 11:32 AM, Edward E. Jaffe [EMAIL PROTECTED] said: |Cmd JobName StepName ProcStep |--- / |VTAM VTAM VTAM Perhaps at your shop, but I've got IBM documentation that calls for a proc name of NET. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Define and start JES2
Since this was originally a discussion related to SUBSYSTEMs: VTAM is not a subsystem. It doesn't listen on the SSI for commands but seems to get its commands internally from the MVS command handler. Peter Hunkeler Credit Suisse - Information Technology -- 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
Re: Define and start JES2
Baloney. Here is the start of the IEFSSNxx member from my Test system called MVS4 so JES2 runs as JES4; SUBSYS SUBNAME(JES4) /* JES4 IS THE PRIMARY SUBSYSTEM NAME */ PRIMARY(YES) START(YES) Two questions: 1,here you use 'JES4' and maybe I could use another name such as 'ABCD'.Then, how could the system know that the subsystem you want to initialize is JES2? Put it in another word,how to establish the relationship between the SUBNAME and the corresponding subsystem? 2,START(YES),means that system will automatically issue a START command to invoke JES2 procedure.However,which procedure name system'll use in START command? S JES4? -- Best Regards, Johnny Luo -- 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
Re: Define and start JES2
Also remember that the command to shut it down is $PJES2, not $PJES4. In fact, the command is xPJES2, where x is what is specified as CONCHAR= on the CONDEF init statement. The default is $ but you may want to select something else for a secondary JES. Peter Hunkeler Credit Suisse - Information Technology -- 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
Re: Define and start JES2
2,START(YES),means that system will automatically issue a START command to invoke JES2 procedure. However,which procedure name system'll use in STARTcommand? S JES4? First an answer to your second Q (it's a short one): The SUBNAME. 1,here you use 'JES4' and maybe I could use another name such as 'ABCD'.Then, how could the system know that the subsystem you want to initialize is JES2? Put it in another word,how to establish the relationship between the SUBNAME and the corresponding subsystem? Apart from what I wrote about implying SUB=MSTR on the start command the system does not care about whether the STC's JOBNAME and the subsystem's SUBNAME match or not. It does not keep record of that relationship. The system builds SSCVTs from the IEFSSNxx entries and the STC needs to find its SSCVT in order to point to its SSVT (the function matrix). If you name the subsystem ABCD and the STC WXYZ everything will work provided the program running in WXYZ knows its SSCVT is named ABCD. If the subsystem implements functions (via SSVT), e.g. listening for commands, it needs to place a routine in common storage and point to ist entry point from the SSVT. MVS will simply give control to that entry point when appropriate, e.g. when a command has been entered, without knowing which STC this routine belongs to. In fact, the even doesn't have to be a STC around. If you can build your function entirely within common storage and don't need an own address space, you don't need an STC to stay alive after your code was initialized. It's long since I dealt with this, so I hope I haven't mixed up things too seriously. I'm sure some will correct me should I. Peter Hunkeler Credit Suisse - Information Technology -- 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
Re: Define and start JES2
On Wed, 4 Jan 2006 16:32:27 +0800, Johnny Luo [EMAIL PROTECTED] wrote: Two questions: 1,here you use 'JES4' and maybe I could use another name such as 'ABCD'.Then, how could the system know that the subsystem you want to initialize is JES2? Put it in another word,how to establish the relationship between the SUBNAME and the corresponding subsystem? What runs is the member JES4 of SYS1.PROCLIB, the SUBNAME is the proc name. In my case that is a copy of the JES2 proc but renamed and pointing to a different set of initialisation parms. 2,START(YES),means that system will automatically issue a START command to invoke JES2 procedure.However,which procedure name system'll use in START command? S JES4? Yes, see above. -- 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
Re: Define and start JES2
In ![EMAIL PROTECTED], on 01/03/2006 at 08:14 AM, Lizette Koehler [EMAIL PROTECTED] said: The main reason is that every piece of documentation is for JES2. You might get someone confused at operations or Level2 if you say my JESA system is down. Trust me, you do not want to confuse Level2 at 0200 am with a JES is down call. Why would you say my JESA system is down? The name of the component is JES2, regardless of the name of the cataloged procedure used to start it. Would you describe a VTAM problem as my NET is down? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- 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
Re: Define and start JES2
Shmuel Metz (Seymour J.) wrote: Why would you say my JESA system is down? The name of the component is JES2, regardless of the name of the cataloged procedure used to start it. Would you describe a VTAM problem as my NET is down? |Cmd JobName StepName ProcStep |--- / |VTAM VTAM VTAM -- .-. | Edward E. Jaffe|| | Mgr, Research Development| [EMAIL PROTECTED]| | Phoenix Software International | Tel: (310) 338-0400 x318 | | 5200 W Century Blvd, Suite 800 | Fax: (310) 338-0801| | Los Angeles, CA 90045 | http://www.phoenixsoftware.com | '-' -- 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
Re: Define and start JES2
In a message dated 1/4/2006 1:32:47 P.M. Central Standard Time, [EMAIL PROTECTED] writes: Cmd JobName StepName ProcStep |--- / | VTAM VTAM VTAM Kinda of a special case. ===c vtam or ===z net,quick -- 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
Re: Define and start JES2
Short answer is that the primary subsystem (for JES2) must be named JES2 Someone may have already mentioned this but when JES2 and JES3 initialize, they mark their SSCT entry that the subsystem is either JES2 or JES3 in the SSCTSSID byte. So if you are looking for the JES2 subsystem, you traverse the SSCT entries doing this: CLI SSCTSSID-SSCT(Rx),SSCTJES2 So the subsystem name can be anything you desire. Personally, I'd rather JES2 be a STC/proc named JES2. -- 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
Re: Define and start JES2
On 1/5/06, David Alcock [EMAIL PROTECTED] wrote: Short answer is that the primary subsystem (for JES2) must be named JES2 Someone may have already mentioned this but when JES2 and JES3 initialize, they mark their SSCT entry that the subsystem is either JES2 or JES3 in the SSCTSSID byte. So if you are looking for the JES2 subsystem, you traverse the SSCT entries doing this: CLI SSCTSSID-SSCT(Rx),SSCTJES2 So the subsystem name can be anything you desire. Personally, I'd rather JES2 be a STC/proc named JES2. Really appreciate all your kind reply.I would present my understanding of JES2 definition at this time and maybe someone can point my errors. Say,in IEFSSNXX parmlib memeber,you define a subsystem : SUBSYS SUBNAME(ABCD) PRIMARY(YES) START(NO) From these statements,system just know that you define 'ABCD' as the primary subsystem and you want to start it by yourself-And system doesn't know anything else. And you create a procedure which start the real 'JES2' but you name it ''. Then in COMMNDXX or somewhere else,you issue : S , JOBNAME=ABCD,SUB=MSTR The '' procedure starts the real 'JES2' and because system finds that its jobname equals the primary subsystem name in IEFSSNXX ,JES2 can be successfuly started.The only difference is that in this sytem there is no subsystem named 'JES2'.You can find 'ABCD' only,though in fact it's just the JES2. Despite of the fact that it works,it's not recommended to do so for: 1,It leads to misunderstanding. 2,Other software may assume that the name of JES2 subsytem is always 'JES2'.You need to do some adjustments to make them work properly. Above is how I understand JES2 definition now.Did I omit something? Thank you all. Johnny -- 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
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？ -- Best Regards, Johnny Luo -- 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
Re: Define and start JES2
Short answer is that the primary subsystem (for JES2) must be named JES2 and the procedure must have the same name. Johnny Luo wrote: 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？ -- Best Regards, Johnny Luo -- 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 -- 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
Re: Define and start JES2
I believe that you are incorrect. We had one system in our sysplex have a JES2 running as JESR for several years. No problems at all. Mark Jacobs Time Customer Service Inc. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Steve Arnett Sent: Tuesday, January 03, 2006 10:04 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: Define and start JES2 Short answer is that the primary subsystem (for JES2) must be named JES2 and the procedure must have the same name. Johnny Luo wrote: 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？ -- Best Regards, Johnny Luo -- 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 -- 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 -- 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
Re: Define and start JES2
You will probably get different answers on this question. Here is my answer. My memory says that the MAIN JES2 Subsystem needs to be JES2. If you define addition JES2 subsystems (secondary) then they can be JESA, JESB, etc... The main reason is that every piece of documentation is for JES2. You might get someone confused at operations or Level2 if you say my JESA system is down. Trust me, you do not want to confuse Level2 at 0200 am with a JES is down call. Leaving it JES2 will make everything happy. Besides I am not sure if other vendors might need to see JES2 to make their products happy. I have run JES2 as the main JES2 subsystem name forever and there have not been any fallout. When I set up a JESA system, there were many factors to consider, such as third party products, documentation, NJE/RJE partners, etc... So I only had a JESA up on my test system; never in a production box. Now for the proc, personally I would keep it the same name (again for clarification). Unless you are running a very large environment, there is no need to make it any different. In the shop I was at we had 36 images running. So in our staging library we had a different JES2 proc for each image, but during our roll out procedure, it was renamed to JES2 on the target system. That way we could maintain all of our environments in one staging Proclib. Hope this helps. Lizette Koehler -- 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
Re: Define and start JES2
No matter what you name it, keep the PROC and SUBNAME names in sync. An STC whose name matches a subsystem name is started under the MASTER instead of under the primary JES, which is what you want for JESx. (Otherwise, you would need to explicitly specify SUB=MSTR on the start command.) And, I'd expect JESx to fail if it doesn't find an SSCVT with its name. Peter Hunkeler Credit Suisse - Information Technology -- 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
Re: Define and start JES2
-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
Re: Define and start JES2
I believe that you are incorrect. We had one system in our sysplex have a JES2 running as JESR for several years. No problems at all. We had a three site complex with JES2 at two sites and JES3 at another. We always called the sub-systems 'JES', with no number. It made automation easier. When we converted the JES3 shop to JES2, we never changed the sub-system names. The reason we converted was because we couldn't find any SYSPROGs to support JES3, after we converted to MVS/XA. -teD Me? A skeptic? I trust you have proof! -- 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
Re: Define and start JES2
Short answer is that the primary subsystem (for JES2) must be named JES2
and the procedure must have the same name.
Baloney. Here is the start of the IEFSSNxx member from my Test system
called MVS4 so JES2 runs as JES4;
SUBSYS SUBNAME(SMS) /* SMS SHOULD BE THE FIRST ENTRY*/
INITRTN(IGDSSIIN)
INITPARM('ID=00,PROMPT=DISPLAY')
SUBSYS SUBNAME(JES4) /* JES4 IS THE PRIMARY SUBSYSTEM NAME */
PRIMARY(YES) START(YES)
The only complication is one of the CA products (11) specifies the
subsystem name in its start command, so check the CAUTOCMD member of
PPOPTION. Also remember that the command to shut it down is $PJES2, not
$PJES4.
Good luck
DC
--
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
