You can run the CICS-supplied job DFHDEFDS to allocate and catalog the dump data sets for an active CICS® region or the CICS-supplied job DFHALTDS to allocate and catalog them for an alternate CICS region. For information about the jobs DFHDEFDS and DFHALTDS, see the CICS Transaction Server for z/OS® Installation Guide.
Alternatively, you can use the sample data definition statements in Figure 17 to allocate and catalog dump data sets on disk.
//DFHDMPA DD DSN=CICSTS31.CICS.applid.DFHDMPA,DISP=(NEW,CATLG),
// UNIT=3380,VOL=SER=volid,SPACE=(CYL,(5,1))
//DFHDMPB DD DSN=CICSTS31.CICS.applid.DFHDMPB,DISP=(NEW,CATLG),
// UNIT=3380,VOL=SER=volid,SPACE=(CYL,(5,1))
If you are running CICS with XRF, you must allocate different data sets for the alternate.
If you use tape for recording dump output, use unlabeled tape. Standard-labeled tape, whether on a single tape drive or on two tape drives, stops you processing the contents of any of the volumes with the DFHDU640 utility until after the CICS step has been completed. If you want to use standard-labeled tape, make sure that all the output produced in the CICS run fits on the one or two volumes mounted.
You cannot catalog dump data sets defined on unlabeled tapes. Your data set definitions must be in the CICS startup job stream each time CICS is run.
If you intend copying dump data sets to tape or disk, you must specify DCB parameters on the DD statements when allocating and cataloging the dump data sets, as follows:
// DCB=(RECFM=VB,BLKSIZE=4096,LRECL=4092)
Otherwise, if you do not intend copying dump data sets to tape or disk, it is not necessary to include DCB parameters when defining dump data sets on disk, as illustrated in the sample job in Figure 17.
For the initial installation of CICS, a dump data set of between 5 and 10MB should be enough. When normal operation begins, you can adjust this to suit your own installation’s requirements.
[[ Contents Previous Page | Next Page Index ]]