You should be able to do that, but you'll need to assign a unique XCFGRPNM on the MASDEF statement for the JES2 in the sandbox system.
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, June 15th, 2021 at 10:21 AM, Richards, Robert B. (CTR) <000001c91f408b9e-dmarc-requ...@listserv.ua.edu> wrote: > I am installing z/OS 2.4 on my sandbox system and discovered I have > inadvertently missed some PTFs on both 2.4 and 2.3 to resolve a JES2 > downlevel condition. JES2 (in a MAS) produced errors and will not start until > this issue is resolved. > > I've applied the fixes for both z/OS environments but need to migrate those > fixes to development and production lpars that are still under z/OS 2.3 and > all in the same MAS configuration. > > My question is this: > > Temporary condition: Is it okay to fire up a different JES2 spool and > checkpoints on the sandbox system, removing the MAS definitions,etc. while > still being part of the sysplex and those systems still believing that the > sandbox JES2 is still part of their MAS? That will allow me to continue to > work on the z/OS 2.4 implementation without waiting for our change management > process to propagate the fixes across the other environments. > > Or do I need to IPL as a monoplex? Or do I need to wait until the fixes have > been installed across the board? > > Bob > > > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > 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
