the more I review and diagnose the more I tend to think a warm start is not good enough, I agree Tom, a cold start may be needed to do this correctly. one thing I did fail to mention was there WAS another system in a MAS with SYSA, that is now defunked, SYSB, still defined in the old JES2PARMS, and once SYSA's JES2 is up, I get a message about changing the member, I'll have to check the log for the exact message, but it does rename member(2) to SYSC, I should just add the MEMBER(2)= statement to nullify the member name but every time I back out its an afterthought thanks again for your thoughts and assistance. Carmen
----- Original Message ----- From: "Tom Marchant" <[email protected]> To: [email protected] Sent: Monday, December 5, 2016 12:09:57 PM Subject: Re: new JES2 MAS jobs will not run on member 2 On Mon, 5 Dec 2016 08:24:12 -0500, Carmen Vitullo wrote: >mermber definition in both systems jes2parms are; (snipped) You may be focusing unnecessarily on your JES2PARMS. Many parameters, including MASDEF cannot be changed with a warm start. The only way tho change them is with a cold start, or via command, e.g. $TMASDEF. -- Tom Marchant ---------------------------------------------------------------------- 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
