Look at your jes2parm for what the limits are set at. I've seen messages for lines exceeded and later KBYTES in the same job log once that limit was reached. I assume that pages are specifically meant for fully composed AFP data and lines for line mode data.
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 Monday, November 9th, 2020 at 1:55 PM, Jesse 1 Robinson <[email protected]> wrote: > We've had some cases of a job taking over the spool. In researching a > solution, we've noticed that message $HASP375 varies in ways we don't > understand. Doc for the message looks like this: > > > --jobname--ESTIMATE EXCEEDED BY--nnn--+-LINES--+---------------> > > +-CARDS--+ > +-KBYTES-+ > '-PAGES--' > > > > --+-------------+--------------------------------------------->< > > '-xxx--%SPOOL-' > > We don't understand why the overage is sometimes reported as Lines, Cards, > Kbytes, or Pages. Why does JES2 pick one descriptor or another? > > . > > . > > J.O.Skip Robinson > > Southern California Edison Company > > Electric Dragon Team Paddler > > SHARE MVS Program Co-Manager > > 323-715-0595 Mobile > > 626-543-6132 Office <===== NEW > > [email protected]mailto:[email protected] > > -- > > 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
