yep got ya ! from member(1)'s jes2parms
MASDEF AUTOEMEM=ON, CKPTLOCK=ACTION, DORMANCY=(200,500), HOLD=50, LOCKOUT=1000, OWNMEMB=&SYSNAME, RESTART=YES, SHARED=CHECK, SYNCTOL=120, XCFGRPNM=LITJES2 MEMBER(1) NAME=SYSA MEMBER(2) NAME=SYSC from member(2)'s jes2parms MASDEF AUTOEMEM=ON, CKPTLOCK=ACTION, DORMANCY=(200,500), HOLD=50, LOCKOUT=1000, OWNMEMB=&SYSNAME, RESTART=YES, SHARED=CHECK, SYNCTOL=120, XCFGRPNM=LITJES2 /* */ /**** MULTI-ACCESS SPOOL ****************/ /* */ MEMBER(1) NAME=SYSA MEMBER(2) NAME=SYSC thanks ----- Original Message ----- From: "Gerhard Adam" <[email protected]> To: [email protected] Sent: Monday, December 5, 2016 7:53:22 AM Subject: Re: new JES2 MAS jobs will not run on member 2 One correction to my previous comment ... you also need a MASDEF parameter. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Vitullo, Carmen P Sent: Sunday, December 4, 2016 2:25 PM To: [email protected] 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 [email protected] arkansasbluecross.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Gerhard Adam Sent: Sunday, December 04, 2016 3:51 PM To: [email protected] 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 <[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 ? > 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 > [email protected] > arkansasbluecross.com > > > > IBM-MAIN > > -- > Privacy Information: http://privacynotice.net (data rate charges may > apply) or 800-524-2621. > > -- > Privacy Information: http://privacynotice.net (data rate charges may > apply) or 800-524-2621. > > ---------------------------------------------------------------------- > 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 -- Privacy Information: http://privacynotice.net (data rate charges may apply) or 800-524-2621. -- Privacy Information: http://privacynotice.net (data rate charges may apply) or 800-524-2621. ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
