Replies in-line.

Charles

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On
Behalf Of retired mainframer
Sent: Wednesday, December 11, 2013 8:04 AM
To: [email protected]
Subject: Re: SMF DUMP SB37 - what am I doing wrong?

Since your extent count/total tracks are inconsistent your JCL, maybe you
should dump the DSCB and see what is really going on with your dataset.  The
TSO LISTDS command with the LABEL option is one universally available
method.

Now at 160 tracks.

--FORMAT 1 DSCB--                                                        
 F1 E5D7D4E5E2C3 0001 710157 000000 09 00 00 C9C2D4D6E2E5E2F24040404040   
 71015920000000 4000 58 00 6D5E 7FF8 00 0000 82 80000064 009F02 619E 0000 
 010000A5000A00AB000C 010100AB000D00AD000D 010200AD000E00AF000D 0001000008
 --FORMAT 3 DSCB--                                                        
 03030303 010300AF000E00AF000E 010400B0000000B00000 010500B0000100B00001  
 010600B0000200B00002 F3 010700B0000300B00003 010800B0000400B00004        
 00000000000000000000 00000000000000000000 00000000000000000000           
 00000000000000000000 00000000000000000000 00000000000000000000           
 00000000000000000000 0000000000                                          

What is the return code associated with the B37?  It should be available
from the accompanying IEC030I message.  If it is 4, you may want to move the
dataset to a volume with room for the dataset to grow.

There is room on the volume.

What is specified for the INTVAL parameter in your SMFPRMxx member?  That
will determine how frequently you generate type 89 records.  Since the
maximum value is 60 (minutes), one has to wonder how in 24 hours you
generated only 8 records.

30 minutes. SMF dump runs more frequently than once a day.

How many times have you run the job?  Unless you clean out the MAN1 dataset,
you are repeatedly dumping the same SMF records.  Did you notice the NOT
CATLGD 2 disposition on all executions after the first?

Will not INDD(INDD1,OPTIONS(ALL)),OUTDD(DUMPOUT,TYPE(89)) clear it?

There are tools on the CBT tape that will analyze SMF records and tell you
what other jobs are using your SMFDATA dataset.  I'm partial to Mike
Cleary's DAF tool.

As indicated earlier, no other jobs could be using the dataset. I made the
name up myself.

:>: -----Original Message-----
:>: From: IBM Mainframe Discussion List [mailto:[email protected]] On
:>: Behalf Of Charles Mills
:>: Sent: Tuesday, December 10, 2013 5:10 PM
:>: To: [email protected]
:>: Subject: SMF DUMP SB37 - what am I doing wrong?
:>:
:>: This has to be less than sysprog 101 but I am obviously less than a
:>: sysprog.
:>:
:>: Here is my SMF Dump proc:
:>:
:>: //SMFDUMPS PROC MAN='SYS1.S0W1.MAN1'
:>: //DUMP1   EXEC PGM=IFASMFDP,REGION=1M
:>: //INDD1    DD  DSN=&MAN,DISP=SHR
:>: //DUMPOUT  DD  DSN=xxxxxx.SMFDATA,DISP=(MOD,CATLG),
:>: //     SPACE=(TRK,(10,10),RLSE),
:>: //     LRECL=32760,RECFM=VBS
:>: //SYSPRINT DD  SYSOUT=H           Was D
:>: //SYSIN    DD  DSN=VENDOR.PARMLIB(CLRMAN),DISP=SHR
:>:
:>: VENDOR.PARMLIB(CLRMAN) is
:>:   INDD(INDD1,OPTIONS(ALL)),OUTDD(DUMPOUT,TYPE(89))
:>:

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to