z/OS HCD User's Guide
Previous topic | Next topic | Contents | Index | Contact z/OS | Library | PDF


IODF dump

z/OS HCD User's Guide
SC34-2669-00

IODF dump

Use the ID=IODF parameter of the TRACE command to produce an IODF dump. This command goes through your IODF, checks it for corrupted data, and writes all records and defects into the trace data set. If you have a consistent IODF, you must set the LEVEL parameter to LEVEL=128 or higher to get an output. Otherwise, an output is only shown if the IODF contains defects.

If your IODF has defects, error message CBDA999I 'Defect(s) detected in IODF xxx' is displayed, and message CBDA099I is written into the message log data set. In addition, the trace data set records defects with the string 'Error:' followed by the reason. You can locate the reported defects by searching to that string in the trace data set.

If no defects are detected in the IODF, message CBDA126I 'TRACE command was accepted' is given.

If you cannot invoke HCD, and therefore, cannot use the TRACE command any longer, use a JCL stream for producing a dump. Figure 210 is an example of the JCL stream for producing an IODF dump.

Make changes to the entries according to your installation requirements.

Figure 210. Example: JCL stream for producing an IODF dump
//WAS$IODF JOB '3259,BOX01,S=C','SMITH',MSGLEVEL=(1,1),
//             NOTIFY=WAS,CLASS=A,MSGCLASS=Q,REGION=4096K
//PRTVSAM  EXEC PGM=IDCAMS
//INPUT    DD  DSNAME=WAS.IODF02.WORK,DISP=SHR
//OUTPUT   DD  DSNAME=WAS.IODF02.DUMP,UNIT=SYSALLDA,
//             SPACE=(CYL,(20,10)),
//             DCB=(LRECL=125,BLKSIZE=629,RECFM=VBA),
//             DISP=(NEW,CATLG)
//SYSPRINT DD  SYSOUT=*
//SYSIN    DD  *
     PRINT -
       INFILE(INPUT) -
       DUMP -
       OUTFILE(OUTPUT)
/*
//

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014