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
