Troubles when SMF summary file is full

Contents:

Bottom

1. SMF summary file full emergency actions

2. SMF saving procedure

3. Wrong dumped SMF records

4. SMF saving processing of  production system

          When SMF summary file is   full and  the job DUMPXY of z/   ended  with cc=0008 (due to 100% full of  SMF summary file)   and a new active work SMF file  is switched with   dump  required  it is necessary to perform some emergency actions to solve the problem  and to avoid this situation in the future.

          1. SMF summary file full emergency actions

When a warning message is received that SMF summary file is 100% full, the normal process of  gathering  SMF records via DUMPXY on the current active work SMF file  (S-BC2A.MAN2) and writing (dump ) it on the SMF summary file  (when 99% filled up)   is interrupted.  The job DUMPXY  is  ended  with cc=0008 requiring a dump of the current active work file (99% filled up)  to be performed because   SMF summary file is full. The next  alternate work  file (P-BC2A.MAN1) is started as active  to continue gathering next  SMF data without loss of SMF records.  The  ISPF/sd.log  command /D SMF display the following status:

IEE974I 10.49.58 SMF DATA SETS 513

NAME                VOLSER SIZE(BLKS) %FULL  STATUS

P-BC2A.MAN1           BC2MCC     27000    22  ACTIVE

S-BC2A.MAN2           BC2MCC     27000    99  DUMP REQUIRED

S-BC2A.MAN3           BC2MCC     27000     0  ALTERNATE

 

The system requires dump to be performed from the work file S-BC2A.MAN2  (99% FULL)    to  the SMF summary file.  Looking at   the  message IEC030I B37-04  ..  (for IPOSAV.SMFDUMPW summary file of the failed job DUMPXY)    it   is found the following  Return Code 04 Explanation:

“all space was used on the current volume and no more volumes were specified” or   “The data set already had 16 extents, but required more space”.

The first thing to do  is to save the present status of the  full   SMF summary file  IPOSAV.SMFDUMPW  (if it is  necessary for further processing) on  saved  file KCI08.SMF.D221112  using job FCOPSMFW:

// FCOPSMFW JOB (,0100),CLASS=R,MSGCLASS=R

//*

//STEP04  EXEC PGM=ADRDSSU,REGION=0M,TIME=1440 PARM=’TYPRUN=NO

//SYSPRINT DD  SYSOUT=*

//SYSIN    DD  *

COPY DATASET(INC(      –

IPOSAV.SMFDUMPW      –

)) –

RENAMEU(IPOSAV.SMFDUMPW      –

KCI08.SMF.D221112)  –

OPT(4)  –

SHARE   –

ALLEXCP –

ALLDATA(*) –

CATALOG

/*

The same may be done on saved  tape VOL=SER=DC1263 with JOB DMPSMF2:

 //DMPSMF2   JOB (,0100),CLASS=R,MSGCLASS=R

//DMPSMF   EXEC PGM=IFASMFDP,REGION=768K,COND=(0,LT)

//SYSPRINT DD  SYSOUT=*

//INDD1    DD  DSN=IPOSAV.SMFDUMPW,

//             DISP=SHR

//OUTDD1   DD  DSN=BACKUP.SMFDUMP,

//             DISP=(,CATLG,DELETE),VOL=SER=DC1263,

//             LABEL=(1,SL),UNIT=(200,,DEFER),

//             DCB=(IPOSAV.SMFDUMPW)

//SYSIN    DD  *               all= dump + clear

INDD(INDD1,OPTIONS(ALL))

OUTDD(OUTDD1,TYPE(000:255))

/*

           2. SMF saving procedure 

 To avoid possible SMF problems (during further SMF processing) ,  a  procedure is started  on a scratch tape as a  GENERATION DATA  SET and the following 3 steps are to be performed:

backup IPOSAV.SMFDUMPW  on  tape, empty IPOSAV.SMFDUMPW  and dump all work  SMF files to IPOSAV.SMFDUMPW as follows:

 First  this   JCL is used to backup on  a save tape:

//DMPSMF2   JOB (,0100),CLASS=R,MSGCLASS=R

//DMPSMF   EXEC PGM=IFASMFDP,REGION=768K,COND=(0,LT)

//INDD1    DD  DSN=IPOSAV.SMFDUMPW,

//             DISP=SHR

//OUTDD1   DD  DSN=BACKUP.SMFDUMP(+1),

//             DISP=(,CATLG,DELETE),

//             LABEL=RETPD=365,UNIT=3490,

//             DCB=(IPOSAV.SMFDUMPW)

//SYSIN    DD  *

INDD(INDD1,OPTIONS(ALL))

OUTDD(OUTDD1,TYPE(000:255))

/*

The second step is to  empty the saved  SMF summary file  IPOSAV.SMFDUMPW with :

//DMPSMF5 EXEC PGM=IEBGENER,REGION=768K,COND=(4,LT)

//SYSPRINT DD  SYSOUT=*

//SYSIN    DD  DUMMY

//SYSUT1   DD  DSN=NULLFILE,DCB=IPOSAV.SMFDUMPW

//SYSUT2   DD  DSN=IPOSAV.SMFDUMPW,

//             DISP=OLD

/*

The third step   is  to dump SMF work data sets (Man1,2,3 including the  active one  which is then empted)  and to write all   them  on IPOSAV.SMFDUMPW with job DMPSMF6 and to  continue gathering next  SMF data on SMF work data sets (Man1,2,3)  without loss of SMF records:

//DMPSMF6  JOB (,0100),CLASS=R,MSGCLASS=R

//DMPSMF   EXEC PGM=SMFDUMP,REGION=768K,COND=(4,LT)

//DUMPOUT  DD  DSN=IPOSAV.SMFDUMPW,

//             DISP=(MOD,PASS)

           3. Wrong dumped SMF records

 If meanwhile  the failed job  DUMPXY is resubmitted,  another trouble can occur – some SMF records  are wrong dumped on the summary SMF file (IPOSAV.SMFDUMPW ) that will reflect on the error processing  of monthly SCRT report  for Sub-capacity charges of Mainframe. This is  because of the bad SMF records written on the summary SMF file (IPOSAV.SMFDUMPW) that  must  be removed.  Look the article “Troubles with  removing bad SMF records”

          4. SMF saving processing of  production system

When the production LPAR  of z/OS system is with less  work load, the system uses less Mainframe resources and produces  less SMF records. Then a  monthly procedure (instead of weekly)  should be  started  and    2 steps   performed: to save  IPOSAV.SMFDUMPW  on  a disk file  (for next prosessing)   and  empty IPOSAV.SMFDUMPW (for next summary)  with care this  to be done before the current work file is 99% full. Care should be taken also  about IPOSAV.SMFDUMPW summary file not to reach  100% full – to have enough space for SMF regular dumps with DUMPXY (for Man1,2,3)  during the month.

The extension of IPOSAV.SMFDUMPW  file size  is possible   on only one  bigger disk  volume (the empty procedure  operation  of SMFDUMPW file is not working properly when it  is performed on multivolume file – the extent on the second volume is not emptied)  and  then  the following steps  should  be executed:

1/. Find a free  bigger  disk volume (9GB) with p.6 – rmf – 2 – 2 -3 – f sp – sp1789 /spare volume/

2/. Initiate  volume   sp1789 as TSOC04 for storage group SGTSO

3/. Add volume   TSOC04 to storage group SGTSO

4/. Copy the current summary file IPOSAV.SMFDUMPW to volume TSOC04 with temporary name IPOSAV.SMFDUMPN using job COPYSMFX on  extended  SPACE=(CYL,(2500,110).

//COPYSMFX JOB   (9999,IPO,10,10),

//         ‘OPERATOR’,

//        ,

//         MSGCLASS=X,

//         MSGLEVEL=(1,1),

//         TIME=1440

//*

//COPYB01  EXEC PGM=IEBGENER

//SYSPRINT DD  SYSOUT=*

//SYSIN    DD  DUMMY

//SYSUT1   DD  DISP=OLD,DSN=IPOSAV.SMFDUMPW

//SYSUT2   DD DSN=IPOSAV.SMFDUMPN,UNIT=SYSDA,

//         VOL=SER=(TSOC04),

//   SPACE=(CYL,(2500,110)),DISP=(NEW,CATLG,DELETE)

//*

5/. Delete the current summary file IPOSAV.SMFDUMPW (verify with /d smf  that the current active work SMF file  /S-BC2A.MAN2/) is  less than    99% full).

6/. Rename the temporary file IPOSAV.SMFDUMPN as IPOSAV.SMFDUMPW to continue collecting SMF dumps of jobs DUMPXY without lost of information.

End

Leave A Reply

Comments

No comments yet, be the first to add one!

Places

 

Clef two-factor authentication

woolrich outlet woolrich outlet online tiffany milano tiffany outlet tiffany outlet tiffany outlet tiffany outlet tiffany milano tiffany outlet peuterey outlet peuterey uomo hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel hogan outlet hogan rebel roshe run pas cher roshe run parajumpers pas cher parajumpers soldes parajumpers pas cher parajumpers soldes parajumpers pas cher parajumpers soldes louboutin pas cher louboutin pas cher louboutin pas cher nike tn pas cher nike tn pas cher