The Data Set Cross-Reference report lists all data sets and members used by the job, and that exist for more than one step. Included in the report are all permanent data sets and all temporary data sets with a disposition other than NEW, DELETE.
To generate this report, specify the XREF option.
CA REPORT 3 - DATA SET CROSS REFERENCE PAGE 3 CA JCLCHECK SYS: xxxx JOB: BK042005 PGMR: CAUSER02 WEDNESDAY SEPTEMBER 12, yyyy ---------------------------------------------------------------------------------------------------------------------------------- DATA SET NAME MEMBER DSET DCB INFO DEFN DELETE CATLG REFERENCED SPACE VOL(S) TYPE FMT LRECL,BLK STMT STMT STMT IN STATEMENTS ---------------------------------------------------------------------------------------------------------------------------------- KNEBO01.$J6ESTG.LISTING >TSU028 PDSE F 133,3325 3 DATACLAS: DCWRKD STORCLAS: TSO MGMTCLAS: TSO KNEBO01.MYLIB.N ?????? ASMDSECT 8 CONVDATE 9 CONVTIME 6 11 IEBGENER 4 5 KNEBO01.REP.VOLSER2 ?????? 12 KNEBO01.REPORT#3 >TSU014 PDSE F 80,3120 ASM#ONLY 7 DATACLAS: DEFAULT STORCLAS: TSO MGMTCLAS: TSO **********************************************************************************************************************************
This report contains the following fields:
Indicates the data set name of the data set.
Generation data group members are listed with the relative generation numbers in existence before the job executes. Temporary data sets are listed with a data set name beginning with a single ampersand (&). For unnamed data sets included on this report, CA JCLCheck generates a data set name in the following format:
&nnnn
Indicates the statement number of the statement creating the data set.
Indicates the space allocation for the data set.
Indicates the member name of the data set.
Indicates the volume serial numbers of the volumes containing the data set.
Direct-access data sets created by this job with no volume explicitly assigned (including all temporary data sets) are arbitrarily assigned to the first eligible volume associated with their unit type. (When the job is actually executed, the system may choose a different volume assignment.) VOL is shown as *VIO* if the data set is eligible for allocation on a VIO device and as *MSS* for a nonspecific mass storage volume.
Indicates the data set type:
Indicates an alias data set
Indicates a cartridge
Indicates a non-VSAM, non-PDS disk data set
Indicates a base GDG entry
Indicates an ISAM data set
Indicates a partitioned data set
Indicates PDS extended
Indicates PDSE/X
Indicates a DB2 table
Indicates a tape data set
Indicates a VSAM data set
Indicates a data component
Indicates an index component
Indicates the DCB of this data set, including the following:
If the data set has a logical record length of 0, only the block size is displayed. DCB information is taken from the DD statement for data sets created or modified in this job and from the data set label for other (previously existing) data sets.
Indicates the statement number of the DD statement that created this data set.
This field is blank if this job does not create the data set.
Indicates the statement number of the DD statement that deleted this data set.
This field contains the value EOJ if the data set was created in this job and passed from step to step without ever being kept or cataloged. This field is blank if this job does not delete this data set.
Indicates the statement number of the DD statement that cataloged this data set.
This field is blank if this job does not catalog this data set.
Indicates the statement numbers of all DD statements that reference the data set, including the creating, deleting and cataloging statements, if applicable.
Indicates the data class associated with the data set.
Indicates the storage class associated with the data set.
Indicates the management class associated with the data set.
Note: DATACLAS, STORCLAS, and MGMTCLAS are fields that display for output data sets when DFSMS is installed. The values printed in these fields are the derived DFSMS data constructs used for the allocation. For more information, see the IBM documentation for Storage Management Library.
|
Copyright © 2014 CA.
All rights reserved.
|
|