OK, thanks Tom, I understand, I know a cold start is using the big hammer and would add time, and another point of failure to a process that should be straight forward. I'll take your good advice and display current JES2 environment and use the reset ($T) command where needed. my next downtime request will be to TEST JES2MAS configuration - if all works I just leave it in :)
Thanks again Carmen I found in my test LPAR the $T command works well for things I wanted to test From: "Tom Marchant" <[email protected]> To: [email protected] Sent: Monday, December 5, 2016 2:18:05 PM Subject: Re: new JES2 MAS jobs will not run on member 2 On Mon, 5 Dec 2016 13:30:47 -0500, Carmen Vitullo wrote: >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. It isn't that you need a cold start, but you can't do it by changing your JES2PARM and doing a warm start. A cold start can be pretty traumatic, and I wouldn't recommend it. For that matter, your JES2PARM is not a reliable method to determine what you have. The reason is that you can change most of what you have specified with commands, and those changes are kept in checkpoint and used upon a warm start. I would start by issuing JES2 display commands to document where you are, and figure out the $T commands that you need to set it the way you want it. Then you will probably want to update your JES2PARM so that it will be ready in case you ever need a cold start. -- 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
