There are some fields in SDSF (by default way to the right) that attempt to explain why a job is not running. Some of these are
Scheduling-Env Dly Mode Spin PhaseName Phase Type DelayRsn I would expect to see something non-blank in one or more of these columns. We happen to have several jobs in the input queue. All but one show a status of HOLD. The other one shows PhaseName Phase AWAIT CONV 129 I looked into the job and found this--no idea how it happened: /*JOBPARM SYSAFF=(ANY,IND) . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Monday, December 05, 2016 8:42 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: new JES2 MAS jobs will not run on member 2 we're a TSS show but I think if its security related any tracing I can activate would help, so far the only think I question is at the end of the JES2 PARM DECK my predecessor added a $HQ,ALL $S $HQ,ALL I'm wondering if this stopped my test job from hitting the converter also, we don't have any WLM resources defined, but I question why the RES display in SDSF shows, I know we don't use these resources but could the state of the resource (SYSNAME) in RESET cause jobs not to run? RESPONSE=SYSC IWM038I 10.33.50 WLM DISPLAY 027 RESOURCE: SYSA DESCRIPTION: SYSA resource SYSTEM STATE SYSTEM STATE SYSTEM STATE SYSA RESET SYSC RESET SYST RESET thanks for your help Paul Carmen ----- Original Message ----- From: "Paul Feller" <paul.fel...@transamerica.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, December 5, 2016 10:27:57 AM Subject: Re: new JES2 MAS jobs will not run on member 2 Carmen, sometimes it just helps to see others definitions. This is the definitions we use for a three member MAS. All three members are running z/OS 2.2. All three members share the same startup parms. I would put in the SECURITY=YES just in case there might be a RACF (security) related to the job(s). I'm sure everyone has a little different take on how some the parms should look. MASDEF DORMANCY=(80,500), /* MIN/MAX DORMANCY TIME OC*/ HOLD=40, /* MINIMUM HOLD TIME &MINHOLD OC*/ LOCKOUT=1000, /* LOCK-OUT WARNING TIME &WARNTIM OC*/ OWNMEMB=&SYSNAME, /* SMF ID OF THIS SYSTEM &SID WS*/ SHARED=CHECK, /* CHECK FOR SHARED DASD ---(NEW) OC*/ SYNCTOL=120, /* SYNCH.TOLERANCE (SEC.) &SYNCTOL OC*/ XCFGRPNM=TS00 /* XCF comm group name OC*/ MEMBER(3) NAME=TS01 /* TS01 member */ MEMBER(4) NAME=TS02 /* TS02 MEMBER */ MEMBER(5) NAME=TS03 /* TS03 member */ /* */ SPOOLDEF BUFSIZE=3992,TGSIZE=36,TGSPACE=(MAX=1856832,WARN=80), TRKCELL=3,TGBPERVL=5,FENCE=NO,LARGEDS=ALLOWED, DSNAME=SYS1.VALD.HASPACE,SPOOLNUM=64,VOLUME=OSSP /* */ CKPTDEF CKPT1=(STR=TS00_JES2CKPT), NEWCKPT1=(DSN=SYS1.TS00.JESCKPTX,VOLSER=OSS007), CKPT2=(DSN=SYS1.TS00.JESCKPT2,VOLSER=OSSCK2,INUSE=YES), NEWCKPT2=(DSN=SYS1.TS00.JESCKPTY,VOLSER=OSS005), MODE=DUPLEX,DUPLEX=ON,LOGSIZE=1,APPLCOPY=NONE /* */ /*------------------------------------------------------------------*/ /* SECURITY=YES: Provides additional RACF security info related */ /* to the $HASP186 message */ /* SYMREC=YES: Message $HASP805 is written when a LOGREC symptom */ /* record is written */ /*------------------------------------------------------------------*/ DEBUG SECURITY=YES,SYMREC=YES Thanks.. Paul Feller AGT Mainframe Technical Support -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Monday, December 05, 2016 08:13 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: new JES2 MAS jobs will not run on member 2 Thanks Gerhard - Carmen ----- Original Message ----- From: "Gerhard Adam" <gada...@charter.net> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, December 5, 2016 8:00:17 AM Subject: Re: new JES2 MAS jobs will not run on member 2 Correct. Those define NJE APPL's ... -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Carmen Vitullo Sent: Monday, December 5, 2016 5:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: new JES2 MAS jobs will not run on member 2 and along those lines I think my other issue is I don't need APPL(LITJES2A) NODE=1 <-- this is member( 1) APPL(LITJES2C) NODE=1 <--- this is member(2) APPL(LITJES2T) NODE=2 APPL(A6504JEA) NODE=4 ----- Original Message ----- From: "Gerhard Adam" <gada...@charter.net> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Monday, December 5, 2016 7:40:12 AM Subject: Re: new JES2 MAS jobs will not run on member 2 I'm sorry, but it seems that you're trying to set up an NJE node but you're calling it a MAS. A MAS doesn't require anything, except that the SPOOL and CKPT parameters point to the same data set. That's it. There's nothing else required. All these references to MEMBER and OWNMEMB are NJE definitions. If it's the latter you want, then you need a network connection and you need to ensure it is started before the systems will recognize each other. Adam -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Vitullo, Carmen P Sent: Sunday, December 4, 2016 2:25 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: new JES2 MAS jobs will not run on member 2 Easier for this situation to do an IPL, since both systems jes2parms were needing change I used a jobparm to direct the job to the correct system, but now that you mention this, I really didn't need it since member 2 has only one specific class Carmen Vitullo Lead Systems Programmer Arkansas Blue Cross and Blue Shield IT Infrastructure Services 515 West Pershing Blvd. North Little Rock, Arkansas 72114 Office: 501.210.4705 Cell: 501.514.4266 cpvitu...@arkbluecross.com arkansasbluecross.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gerhard Adam Sent: Sunday, December 04, 2016 3:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: new JES2 MAS jobs will not run on member 2 Not sure what you're doing but a MAS certainly doesn't require an IPL, nor does it use the /*JOBPARM statement. If there is an initiator available, it will pick up the job. Sent from my iPhone > On Dec 4, 2016, at 1:13 PM, Vitullo, Carmen P > <cpvitu...@arkbluecross.com> wrote: > > I just brought 2 systems into a JES2MAS everything looked OK, some fat > finger issues, and an IPL and all OK Testing the batch submitting I > submit job from member 1 to member 2 using /*JOBPARM S=memb2 Job sits > on JES2 queue awaiting conversion - I've tried everything with node > and member statements and nothing works If I submit from member 2 the > jobs still sits in the input queue, now showing the correct class, Has anyone seen this type of issue? my first time bringing 2 systems into a MAS, What am I missing ? > Thanks > > > > Carmen Vitullo > Lead Systems Programmer > > Arkansas Blue Cross and Blue Shield > IT Infrastructure Services > 515 West Pershing Blvd. > North Little Rock, Arkansas 72114 > Office: 501.210.4705 > Cell: 501.514.4266 > cpvitu...@arkbluecross.com > arkansasbluecross. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
