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:[email protected]] On > Behalf Of Carmen Vitullo > Sent: Tuesday, December 06, 2016 8:17 AM > To: [email protected] > 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 [email protected] with the message: INFO IBM-MAIN
