Yes, a JES2 cold start with newly defined/allocated spool and checkpoint datasets will be needed. Have you looked into setting default estimates in JES2PARM, bytes, lines, pages, with OPT=1 to cancel jobs that exceed your limits?
Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&[email protected] ------- Original Message ------- On Thursday, December 8th, 2022 at 2:16 PM, Michael Babcock <[email protected]> wrote: > We have a 3 system plex, with two of those systems, DEV and PROD, in a > JES2 MAS. We had an incident recently where a development job got into > a loop and used up all spool. This in turn, caused our PROD system to > come to, basically, a screeching halt. > > Management wants to investigate removing PROD from the MAS. > > Beyond the obvious cons below, what else am I missing? Will a cold > start be required? > > CONS: > 1. No longer monitor production jobs from DEV > 2. User's will need to logon to production to check on production jobs > 3. Significant changes to desk procedures > 4. May require changes to production jobs and/or CA7 (convert from > SYSAFF to ROUTE XEQ) > > ---------------------------------------------------------------------- > 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
