Thanks everyone for the responses. Found it - JES2 Exit 9 treats jobclass "N"
as a testing class ("O" isn't) and metes out punishment for exceeding the
estimate; a holdover from a long time ago. Need to update the exit.
_______________________________________________________________________________
Karl S Huf | Senior Vice President | World Wide Technology
50 S LaSalle St, LQ-11, Chicago, IL 60603 | phone (312)630-6287 |
[email protected]
Please visit northerntrust.com
CONFIDENTIALITY NOTICE: This communication is confidential, may be privileged
and is meant only for the intended recipient. If you are not the intended
recipient, please notify the sender ASAP and delete this message from your
system.
IRS CIRCULAR 230 NOTICE: To the extent that this message or any attachment
concerns tax matters, it is not intended to be used and cannot be used by a
taxpayer for the purpose of avoiding penalties that may be imposed by law. For
more information about this notice, see http://www.northerntrust.com/circular230
Please consider the environment before printing this e-mail.
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf
Of Lizette Koehler
Sent: Wednesday, October 16, 2013 11:49 AM
To: [email protected]
Subject: Re: Abend S722 & $HAPS375
And do not neglect to look at how your JOB card is handled by any exits.
The
//JOBNAME JOB (xx,yy,zz,aa,...),'Pgm Name Field', ...
The xx, yy, zz, aa could reflect a Line count. In this sample, aa would be
the line count.
The JCL manual shows
(pano,room,time,lines,cards,forms,copies,log,linect)
You should validate any JOBCARD and/or JOBCARD EXIT that might place something
in the job card that just happens to be in the LINE COUNT parameter.
And any use of OUTLIM could also affect the LINE Numbers.
The OUTLIM parameter of the DD statement controls the number of logical records
in the sysout data set defined by that DD statement. If the sysout limit
defined on the LINES parameter is exceeded before the limit defined on OUTLIM,
the system will take the action defined on LINES. If the sysout limit defined
on the OUTLIM parameter is exceeded before the limit defined on LINES, the
system exits to the sysout limit exit routine.
Lizette
> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]]
> On Behalf Of Lizette Koehler
> Sent: Wednesday, October 16, 2013 9:34 AM
> To: [email protected]
> Subject: Re: Abend S722 & $HAPS375
>
> This is a good point. Your jobcard has
>
>
> 1 //DFPRM043 JOB '7502,PROD,LS33','>> PROD DEFRAG <<',
> // REGION=6M,CLASS=O,MSGCLASS=T,NOTIFY=XXXX,
> // MSGLEVEL=(1,1),
> // USER=MAINTLID
>
> So SYSOUT=* will default to SYSOUT=T
>
> So , could you provide the definition for SYSOUT CLASS T in your JES Deck ?
>
> Lizette
>
>
> > -----Original Message-----
> > From: IBM Mainframe Discussion List
> > [mailto:[email protected]] On Behalf Of Elardus Engelbrecht
> > Sent: Wednesday, October 16, 2013 9:22 AM
> > To: [email protected]
> > Subject: Re: Abend S722 & $HAPS375
> >
> > Karl Huf wrote:
> >
> > >I feel silly for asking this as I’m certain it’s obvious but it’s
> > >been so long since I’ve
> > dealt with it I’m not finding what must be staring me in the face.
> >
> > No, only clever persons ask questions. ;-)
> >
> >
> > >JOBCLASS(O) PROCLIB=03,PERFORM=000,
> > ...
> > IEFUSO=YES,
> >
> > Check your exit for handling of the limit.
> >
> >
> > >5 XXSYSPRINT DD SYSOUT=(*,,)
> > >6 XXSYSMAP DD SYSOUT=(*,,)
> > >7 XXSYSUDUMP DD SYSOUT=(*,,)
> >
> > What are the eventual output classes?
> >
> > Groete / Greetings
> > Elardus Engelbrecht
>
----------------------------------------------------------------------
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
