Bob, I got your sample exit. Plan to pursue it. As for what my exit has access to, it's just a standard SMF exit call in a batch job. Here's what a 'normal' job shows:
+------------------------------------------------------------------------------- | --TIMINGS (MINS.)-- | JOBNAME STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK SERV PG | ZWAITEST STEP1 00 3103 12307 .01 .00 .2 68745 0 | | DDNAME UNIT TYPE BLKSIZ EXCP (ONLY NON-ZERO COUNTS LISTED) | | STEPLIB 7C12 3390 32760 2 | SYSPRINT 3408 3490 262080 3053 +------------------------------------------------------------------------------- Here's the problem job. Note the huge number of EXCPs. There is simply no device level detail displayed. +-------------------------------------------------------------------------------| | --TIMINGS (MINS.)-- | | JOBNAME STEPNAME PROCSTEP RC EXCP CONN TCB SRB CLOCK SERV PG| | CSSDCU01 CSSDCU01 STEP160 00 17819K 6166K 3.24 .69 112.0 18641K 0+ +-------------------------------------------------------------------------------I . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] From: Bob Rutledge <[email protected]> To: [email protected], Date: 12/13/2013 04:30 PM Subject: Re: EXCP Counts in SMF Exit Sent by: IBM Mainframe Discussion List <[email protected]> Does your IEFACTRT deal with continuation type 30-4 records? From the Installation Exits book: "When the data for an SMF record exceeds 32,756 bytes in length, the system constructs one or more "continuation" or "additional" records to ensure that no individual record exceeds that length. The system invokes IEFACTRT once for the original record and once for each continuation record." (When the exit is called with a continuation record, SMF30TON is zero.) Bob Skip Robinson wrote: > We use an SMF exit modeled on SAMPLIB(SCEACTMS). For each step, it formats > various stats in the job message log for every device used. It works well > most of the time, but for a particular job in a particular where we really > need to see some values, the crucial lines are totally missing. I've > looked at the code and concluded that the only way we could be missing all > device detail is if the field SMF30EON is zero. The job step in question > does enormous I/O to tape. > > PUTMSG3B DS 0H EXCP COUNTS > SLR R5,R5 GET COUNT OF > ICM R5,B'0011',SMF30EON EXCP SECTIONS <------------- > BZ PUTMS3BX IF NONE, SKIP RTN <------------- > BAL R14,MSGRTN PUT BLANK LINE OUT > MVC MSGAREA,LINE3B SET UP HEADER LINE > BAL R14,MSGRTN PUT LINE OUT > BAL R14,MSGRTN PUT BLANK LINE OUT > LR R4,R9 GET RECORD ADDRESS > A R4,SMF30EOF POINT TO ID SEGMENT > USING SMF30EXP,R4 ENABLE RECORD DSECT > EXCPLOOP DS 0H PRINT NON-ZERO EXCP COUNTS > PUSH USING > USING LINE3BD,R6 ENABLE DETAIL LINE DSECT > ... > > I've searched the web and found some references even in IBM-Main to a > 'triplet' that handles multiple EXCP sections. But I haven't found any > example of how to utilize the additional fields. I suspect that the data I > need is available to the exit, but I need some guidance. > > > Offset > SMF30EOF > Length > SMF30ELN > Number > SMF30EON - Reports the number of EXCP sections on the current record. > This section also has additional control fields in the > ‘header/self-defining’ section: > SMF30EOS reports the number of EXCP sections for the current period on > Subsequent Type 30 records. These are known as the ‘chained’ Type 30 > records. > SMF30EOR also reports this same information but is only a 2 byte field > which can overflow so SMF30EOS is the preferred field for processing this > data. > > > . > . > JO.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 626-302-7535 Office > 323-715-0595 Mobile > [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
