Just wanted to thank everyone on the list for their insight to my issues with a new JES2MAS, especaiilly Lizzette, followed the doc to the letter, removed the old member first with a warm start MEMBER(2),NAME= once I responded to the JES2 WTOR are you sure, JES2 Initialized, I shutdown JES2 and updated the member name MEMBER(2)NAME=SYSC started JES2 and viola ! job submission via sysaff works as designed only issue I'm having now is an NJE connection to a test lpar, once SYSC joined SYSA, node names were redefined for some reason, so for now I'm stuck with node name N1 on SYSA as OWNNODE, the connections to the test system fail
IAZ0543I NETSRV1 TCP/IP connection with IP Addr: TCPIPT1.abcbs.net Port: 1041 Successful IAZ0520I NETSRV1 NJETCP Signon error: OHOST value 'LITJES2A' not valid in OPEN from IP addr: TCPIPT1.abcbs.net well that's true the node(LITJES2A) has become N1 looks like a cold start to correct OWNNODE, I'm reviewing the doc, I'm sure I messed up somehow not defining the nodes on SYSC the same as SYSA - but this is an NJE connection to a test LPAR so not so critical. again thanks everyone for their help Carmen ----- Original Message ----- From: "Lizette Koehler" <stars...@mindspring.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tuesday, December 6, 2016 9:44:56 AM Subject: Re: new JES2 MAS jobs will not run on member 2 And just to make sure I remember correctly. The way a warm start works is no work is running in JES2. So nothing up using SYSOUT. Then abend JES2 and restart with WARM,NOREQ If any work is running with SYSOUT, then I think JES2 changes to a HOT START. So, when I have done a warm start, I am at a Master Console (not SDSF) and the only tasks running is what comes up in NIP and JES2. No TSO, no VTAM, etc... Then I can $PJES2,ABEND S JES2,PARM='WARM,NOREQ' Just checking Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Carmen Vitullo > Sent: Tuesday, December 06, 2016 8:17 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: new JES2 MAS jobs will not run on member 2 > > I spent the morning reviewing and re-reading the link Lizz provided, this was > a great help, I was thinking I could just rename the member to what I wanted > and warm start JES2, according to the good doc not so fast > > > > Figure 1. Reassigning Member Identifiers to Different Processors > MEMBER(1) NAME=SYSA /* ORIGINAL CONFIGURATION */ > MEMBER(2) NAME=SYSB > > . > . > . > > > Step 1: > MEMBER(1) NAME=SYSA /* DEFINE TEMPORARY */ > MEMBER(2) NAME=SYSY /* MEMBER IDENTIFIERS */ > /* AND THEN WARM START */ > . > . > . > > > Step 2: > $PJES2 on all members in MAS. > > > Step 3: > Perform an all-member warm start with the above configuration. > > > Step 4: > When JES2 starts redefine with the following statements: > > > MEMBER(1) NAME=SYSA /* NEW CONFIGURATION */ > MEMBER(2) NAME=SYSC > > this will be my plan for my next downtime schedule, again thanks ALL for your > great insight , thanks Lizz for the push to re read the doc Carmen . > . ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
