Previous Topic: VOLSEQNO — Multivolume data set Volume Sequence NumberNext Topic: Special Considerations While Processing PSEs


VSAMORG — VSAM organization type

The second operand in a VSAMORG comparison can be any of the following:

BROKEN

Broken VSAM data sets (component)

ESDS

Entry-sequenced data set (cluster)

KSDS

Key-sequenced data set (cluster)

LDS

Linear data set (cluster)

RRDS

Relative record data set (cluster)

VRRDS

Variable length relative record data set (cluster)

For example, to select only KSDS clusters; use:

SELECT CRITERIA=(DSORG,EQ,VSAM,AND,VSAMORG,EQ,KSDS)

After CA Disk determines that a VSAM data set is broken, the value of VSAMORG is set to BROKEN. Broken VSAM data sets will only be selected for the REPORT action command. Only the DSINDX, DSUTIL, MAPPER, MVD and SVD reports will report on broken VSAM data sets. The broken VSAM data sets are reported at the component level as opposed to the cluster level.

When using the SCAN REALVOLS command, uncataloged or incorrectly cataloged VSAM components will be detected as broken if the COMPONENTS parameter is not specified. When using the SCAN CAT or FIND commands, cataloged VSAM components that do not physically reside on their cataloged volumes are detected as broken by CA Disk.

Specifying the CA Disk sysparm DSCLMSGS to Y causes CA Disk to issue messages concerning the broken VSAM data sets.

For more information, see DSORG—Data set Organization, PDSORG—Partitioned Data Set Organization, and PSORG—Physical Sequential Extended.

ZFS - zSeries File System (yes/no)

Set the value of this field to YES/TRUE/ON or NO/FALSE/OFF. For example, SELECT CRITERIA=(ZFS,EQ,YES) selects all zFS data sets.