backing away from this for now, I ran out of time and had to back out, some good take away's, displaying the job, I knew there was a jes2 command to see why a job was held up just in the flurry of issue I did not think of this, next time for sure to answer your questions: we had one one WLM init, new to both systems, no resources defined or tied to that INIT. no TPM or MODS, only exits are exit5 and exit1, my mermber definition in both systems jes2parms are;
MEMBER(1) NAME=SYSA MEMBER(2) NAME=SYSC MASDEF AUTOEMEM=ON, CKPTLOCK=ACTION, DORMANCY=(200,500), HOLD=50, LOCKOUT=1000, OWNMEMB=&SYSNAME, RESTART=YES, SHARED=CHECK, SYNCTOL=120, XCFGRPNM=LITJES2 JES2 comes up no issues, jobclasses not held, queues not held, like i said jobs submitted from member 1 sit in the input queue class(*) awaiting conversion, I was thinking I had some INTRDR issues? but that didn't seem to jive. gone back to the operlogs and see if I can see any other issues. thanks Lizz Carmen ----- Original Message ----- From: "Lizette Koehler" <[email protected]> To: [email protected] Sent: Sunday, December 4, 2016 6:37:39 PM Subject: Re: new JES2 MAS jobs will not run on member 2 First thing to do is $DJ#####,LONG It should show you want Resource JES2 is waiting to show up. Next, do you have Thruput Manager by MVS Solutions, or zOSEM by Trident Software Or do you have any JES2 Mods that need resources? If you have SDSF issue the I against the Job in the Command Column Everything depends on what you have JES2 setup to do. Do you use WLM Inits? If so, are they started? Do you have MAS set up for both LPAR names? Try this link http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa300/masmem.htm Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Vitullo, Carmen P > Sent: Sunday, December 04, 2016 2:13 PM > To: [email protected] > Subject: new JES2 MAS jobs will not run on member 2 > > 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 > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
