My money would also NOT be on using the wrong access method, but it is theoretically possible.
Bill Fairchld ----- Original Message ----- From: "Skip Robinson" <jo.skip.robin...@sce.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Saturday, December 14, 2013 1:39:10 PM Subject: Re: EXCP Counts in SMF Exit I have considered that I/O to the DB2 data base might be accounted for by DB2. Maybe even the tape I/O, but that seems a stretch. But the job also does I/O to conventional files like STEPLIB and SYSIN, which is reported by the SMF exit for other steps in the same job. My money is on the structure of the SMF record presented to the exit in this particular step. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: DASDBILL2 <dasdbi...@comcast.net> To: IBM-MAIN@LISTSERV.UA.EDU, Date: 12/14/2013 11:30 AM Subject: Re: EXCP Counts in SMF Exit Sent by: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> The SMF EXCP counting code counts all EXCPs but not necessarily all I/O requests. If your wayward job is using the STARTIO "access method" or the Media Manager to do its output I/O to tape, then its bazillions of I/O requests will never be accounted for in SMF data, but they will show up in RMF data for the device(s) involved. BSAM, QSAM, BPAM, and BDAM all use EXCP under the covers, so all their I/Os are counted by SMF. I don't know about VSAM. DB2 and IMS use Media Manager internally, which uses STARTIO internally, so their I/Os are not automatically counted in SMF. Bill Fairchild ----- Original Message ----- From: "Skip Robinson" <jo.skip.robin...@sce.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Friday, December 13, 2013 5:36:43 PM Subject: EXCP Counts in SMF Exit 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 jo.skip.robin...@sce.com ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
