We have CA-OPS and have put things in place but management isn’t mainframe literate and may be adamant about splitting. Up to me, I would move on to something more pressing.
Thanks for the responses. On Thu, Dec 8, 2022 at 1:24 PM Allan Staller < [email protected]> wrote: > Classification: Confidential > > Rather than split the spool, (no cold start required IIRC, it might be > more prudent to limit the amount of output a job can create. > > Look up $ESTLNCT(?) in the JES2 manual; Set an appropriate Count and > specify option 2. > > When the job exceeds the defined limit (more or less), the job will abend > w/S722. > > HTH, > > -----Original Message----- > From: IBM Mainframe Discussion List <[email protected]> On Behalf > Of Michael Babcock > Sent: Thursday, December 8, 2022 1:16 PM > To: [email protected] > Subject: Split JES2 MAS > > [CAUTION: This Email is from outside the Organization. Unless you trust > the sender, Don’t click links or open attachments as it may be a Phishing > email, which can steal your Information and compromise your Computer.] > > 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 > ::DISCLAIMER:: > ________________________________ > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. E-mail transmission is not > guaranteed to be secure or error-free as information could be intercepted, > corrupted, lost, destroyed, arrive late or incomplete, or may contain > viruses in transmission. The e mail and its contents (with or without > referred errors) shall therefore not attach any liability on the originator > or HCL or its affiliates. Views or opinions, if any, presented in this > email are solely those of the author and may not necessarily reflect the > views or opinions of HCL or its affiliates. Any form of reproduction, > dissemination, copying, disclosure, modification, distribution and / or > publication of this message without the prior written consent of authorized > representative of HCL is strictly prohibited. If you have received this > email in error please delete it and notify the sender immediately. Before > opening any email and/or attachments, please check them for viruses and > other defects. > ________________________________ > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Michael Babcock OneMain Financial z/OS Systems Programmer, Lead ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
