I would open a DEFECT case with IBM L2 JES2. It should terminate any job (not
STC) that exceeds your requirements.
I had an issue with an STC was getting a S722 abend but it was not exceeding
the limits hard coded in JES2. IBM has published a fix for STCs getting S722
abends.
This might be a
TIL. Thanks.
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 Wednesday, April 22, 2020 11:13 AM, Joe Monk wrote:
> JES2 limits do not apply to STCs
JES2 limits do not apply to STCs.
https://groups.google.com/forum/#!msg/bit.listserv.ibm-main/1YPjynrHqBo/EN7BpmG6AQAJ
Joe
On Wed, Apr 22, 2020 at 7:58 AM Mark Jacobs <
0224d287a4b1-dmarc-requ...@listserv.ua.edu> wrote:
> We've been trying to enforce limits on how much spool space a single
We've been trying to enforce limits on how much spool space a single job can
use before it's canceled. We don't have any automation products, nor JES2
exits. The method that we're trying to use is ESYBYTES with OPT=1.
On one system we've set it to this value, $HASP845 ESTBYTE
NUM=478848,INT=99
