When using the IDCAMS command "LISTCAT <dataset specification> ALL", a report is created with a number of different columns, and 2 or 3 lines of data for each dataset listed.
This document explains how to interpret the report.
Report Part #1
==============
Example:
DSN C C DSOR RecF Lrecl Blksi KyL KyOff GDG
xxxxxxxx - MFSLV.CLUSTER.BASE
Y A VSAM KS 80 8 0
PC File - C:\\ESADMIN\\EDBATCH\\DATA\\MFSLV.CLUSTER.BASE.DAT
GDG BASE - MFISVR.SCR.GDG
Y A GDG ? 0 0 3
NONVSAM - MFISVR.SCR.GDG.G0004V00
Y A PS FB 80 65535
PC File - C:\\ESADMIN\\EDBATCH\\DATA\\MFISVR.SCR.GDG.G0004V00.DAT
The first line of data for each dataset contains the entity type (shown above as xxxxxxxx in the first data line) and the dataset name.
Where xxxxxxxx is one of:
AIX - VSAM Alternate Index
CLUSTER - VSAM Cluster
DATA - VSAM Data component
INDEX - VSAM Index component
PATH - VSAM Path component
MODEL - Dataset Model
GDG BASE - Generation Data Group base component
NONVSAM - Non-VSAM dataset (including GDG bias components)
The column headings after DSN refer to data on the second line, and are as follows:
# Title Description
-- ---------- ---------------------------------------------------------------------
2) C Cataloged flag (Y=cataloged, N=uncatalged, S=Spool)
3) C Character Set (E=Ebcdic, A=Ascii)
4) DSOR Dataset Organisation
For VSAM datasets, KS=KSDS, ES=ESDS, RR=RRDS
For non-VSAM datasets, refer to the JCL DSORG parameter
5) RecF Record format, refer to the JCL RECFM parameter
6) Lrecl Logical record length, refer to the JCL LRECL parameter
7) Blksi Block size, refer to the JCL BLKSIZE parameter
8) Kyl Key length for indexed datasets
9) KeyOff Key offset for indexed datasets
10) GDG For a GDG, the maximum number of biases (i.e. generations) to retain
If the ALL option was specified on the LISTCAT (or LISTC) command, for entities that have a physical existence outside of the catalog, there will be a third line containing the actual physical file name, as stored on the platform's file system, for example:
PC File - C:\\ESADMIN\\EDBATCH\\DATA\\MFISVR.SCR.GDG.G0004V00.DAT - the physical name and location of the GDG bias file #4
Report Part #2
==============
Example:
S E UK RU xt Dataclas Volume RecMn RecMx Changed Job/On/At Created Job/On/At XDXR
PRTAIX DEFBASE
NR C 8 80 20140804 11090790 20131008 10115983
MFISVRGD
S N 20140805 13231399 20140128 16001372
MFISVRGD MFISVRGD
20140217 13572146 20140217 13521993
The column headings after GDG refer to data on the second line (except where indicated below), and are as follows:
# Title Description
-- ---------- ---------------------------------------------------------------------
11) S GDG Roll up disposition - S=SCRATCH, N=NOSCRATCH
12) E GDG Empty specification - E=EMPTY, N=NOEMPTY
13) UK For indexed datasets or VSAM Paths, the key type - UK=Unique,
NU=Non-Unique (i.e. duplicate keys allowed)
14) RU For VSAM datasets, the reuseable attribute - RE=Reuseable,
NR=Non-Reuseable
15) xt For VSAM datasets, the extended type - A=Aix, C=Cluster, P=Path,
M=Model, E=Aix Index, J=Aix Data, I=Index, D=Data, ?=Unknown
16) Dataclass On the first line, the SMS MGMTCLAS attribute
On the second line the SMS DATACLAS attribute
17) Volume Refer to the JCL VOLUME parameter
18) RecMn For VSAM datasets, the minimum record length
19) RecMx For VSAM datasets, the maximum record length
20) Changed On the first line, the name of the job, user, or process (e.g. ESMAC)
that changed the dataset's catalog entry
On the second line the date on which the dataset's catalog entry was changed
21) Job/On/At On the second line the time at which the dataset's catalog entry was changed
22) Created On the first line, the name of the job, user, or process (e.g. ESMAC) that created the dataset's catalog entry
On the second line the date on which the dataset's catalog entry was created
23) Job/On/At On the second line the time at which the dataset's catalog entry was created
24) XD Extended dataset type (P=PDS, L=PDSE, I=PIPE, H=HFS)
25) XR Extended RBA support (Y=yes)
#EnterpriseDeveloper
#IDCAMSMFJAMSLISTCATLISTC
#MFDS
