On Sun, Dec 4, 2016 at 3:13 PM, Vitullo, Carmen P < [email protected]> 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 ? > Silly question: Is JES2 on the new system "started". I don't mean started in the S JES2,SUB=MSTR sense. I mean, do you have a PARM=NOREQ in the JES2 proc so that it automatically starts processing once it's up? My first thought is to just do a $S command to tell JES2 "wake up, fool!". Do you use scheduling environments. I saw this: http://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.hasa200/sjpc.htm [quote] CNVT_SCHENV=HONOR|IGNORE Specifies whether the availability of a scheduling environment that is associated with a job controls which member a job converts on. If CNVT_SCHENV=HONOR is specified, then a job can only convert on a system where the scheduling environment associated with the job is available. [quote/] Maybe try the command: $TJOBDEF,CNVT_SCHENV=IGNORE > 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 > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
