We don't have a plex so I can't answer your question directly, but do you have 
any kind of automated console monitoring?  We set up a rule so that if test 
jobs go over a certain percent of spool space, we just automatically cancel and 
purge them, no questions asked.  We implemented this after a couple incidents 
where this exact scenario occurred at o-dark-30 a couple times and we couldn't 
get the developers to watch out for themselves.

Rex

-----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: [EXTERNAL] Split JES2 MAS

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

----------------------------------------------------------------------
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to