CA Dynam for VSE User Guide
CA Dynam for VSE User Guide CA Dynam for VSE User Guide
Reporting on Tape Files Important! Run the LIST NEW report only when there are no tape files being created in other partitions. PASSWORD= Generates a list of all data sets which are password-protected, along with the associated password. Eight-character catalog password enclosed in single quotation marks. SCRATCH VOL= Generates a listing of all scratch tapes in the library in volume serial number sequence. Generates a listing of all active tapes or tapes selected by volume serial number. The list is in volume serial number sequence. Valid entries are: 1- to 6-character volume serial number ALL - for all active tapes Example: // JOB PRINT VARIOUS REPORTS // ASSGN SYS001,130 DISK WORK FILE // DLBL WORK1,'WORKAREA',0,SD // EXTENT SYS001,... // EXEC TDYNUTL,SIZE=128K LIST ALL LIST DSN='ALL' or LIST DSN=ALL LIST DSN='FILE NAME' LIST VOL=ALL LIST VOL=234 LIST NEW LIST SCRATCH /* /& This job stream generates the following listings: • All tapes in volume serial number sequence • All data sets in data set name sequence • All tapes associated with the file FILE NAME in ascending sequence by version number (the current version is listed first) • All active tapes in volume serial number sequence • Volume serial number 234 • Two lists of all tapes cataloged in the library since the last time this function was performed. One list is in volume serial number sequence and the other one in Data Set Name sequence • All scratch tapes in the library in volume serial number sequence 3–42 User Guide
Reporting on Tape Files Report Fields and Comments Each of the reports produced by TDYNUTL and DYNCAT uses a similar format. The following lists describe the fields and special comments that can appear on the reports: CPU CUU DATE DAY DSN EXP-DATE FIL JOB-NAME LEN MODE MSG NGEN NOAC OW ID Alphabetic CPU ID of the CPU on which this version was created. It is determined by the System Adapter option record. Tape unit on which this version was created. If the version was created using the DYNCAT ADD function, this field is blank. Creation date of this version. This is taken from the system date in the supervisor—not the temporary COMRG date. You can modify it with the DYNCAT ALTER function. Number of days from creation date that data set versions are to be retained. Name of the data set as it appears in the catalog file. Expiration date of this version. If days retention is specified, this value is calculated when the version is created or taken from the TLBL. You can modify it with the DYNCAT ALTER function. File sequence number. Jobname in which this version of the data set was created. Length specified for the data set, tape volume, or both. Mode at which the version was created. Additional notes about this version; for example, MF for multifile data set and AMF for automatic multifile data set. Number of versions to be retained. Number of days to retain this version since it was last accessed as input. Data set owner identification characters—blank if there is no ownership for the data set. Chapter 3: Supporting Tape File Management 3–43
- Page 109 and 110: Using Other Software with CA Dynam/
- Page 111 and 112: Using Other Software with CA Dynam/
- Page 113 and 114: Controlling Single and Multi-Volume
- Page 115 and 116: Specifying the SET Command SET Comm
- Page 117: Using the Console Alarm Facility IB
- Page 120 and 121: Tape File Management Utilities Usin
- Page 122 and 123: Tape File Management Utilities Note
- Page 124 and 125: Tape File Management Utilities The
- Page 126 and 127: Tape File Management Utilities TDYN
- Page 128 and 129: Tape File Management Utilities UPSI
- Page 130 and 131: Tape File Management Utilities // J
- Page 132 and 133: Tape File Management Utilities TEST
- Page 134 and 135: Tape File Management Utilities The
- Page 136 and 137: Tape File Management Utilities The
- Page 138 and 139: Tape File Management Utilities CATN
- Page 140 and 141: Tape File Management Utilities Exam
- Page 142 and 143: Tape File Management Utilities VER
- Page 144 and 145: Tape File Management Utilities SYST
- Page 146 and 147: Reporting on Tape Files The TDYNUTL
- Page 148 and 149: Reporting on Tape Files The followi
- Page 150 and 151: Reporting on Tape Files In addition
- Page 152 and 153: Reporting on Tape Files TDYNPULL Pr
- Page 154 and 155: Reporting on Tape Files UNCONTROLLE
- Page 156 and 157: Reporting on Tape Files Note: • S
- Page 158 and 159: Reporting on Tape Files This job st
- Page 162 and 163: Reporting on Tape Files PED AS-OF-D
- Page 164 and 165: Vault Location Control Program—TD
- Page 166 and 167: Vault Location Control Program—TD
- Page 168 and 169: Vault Location Control Program—TD
- Page 170 and 171: IBM 3494 Tape Library Interface IBM
- Page 172 and 173: IBM 3494 Tape Library Interface Not
- Page 174 and 175: IBM Virtual Tape Facility (VTAPE) S
- Page 176 and 177: IBM Virtual Tape Facility (VTAPE) S
- Page 178 and 179: IBM Virtual Tape Facility (VTAPE) S
- Page 180 and 181: IBM Virtual Tape Facility (VTAPE) S
- Page 182 and 183: Basic Components The enhanced VTOC
- Page 184 and 185: Basic Components Disk Space Availab
- Page 186 and 187: Basic Components Method Two Submitt
- Page 188 and 189: Basic Components Overriding Catalog
- Page 190 and 191: Managing the VTOC Default Allocatio
- Page 192 and 193: Managing the VTOC Searching the VTO
- Page 194 and 195: Defining File ID Option Codes Defin
- Page 196 and 197: Defining File ID Option Codes F Fra
- Page 198 and 199: Defining File ID Option Codes O Old
- Page 200 and 201: Controlling Generation Data Sets //
- Page 202 and 203: Controlling Generation Data Sets De
- Page 204 and 205: Automatic Volume Assignment and Rec
- Page 206 and 207: Selecting Logical Units LUB Availab
- Page 208 and 209: Modifying Logical Unit Assignments
Reporting on Tape Files<br />
Report Fields and Comments<br />
Each of the reports produced by TDYNUTL and DYN<strong>CA</strong>T uses a similar <strong>for</strong>mat.<br />
The following lists describe the fields and special comments that can appear on<br />
the reports:<br />
CPU<br />
CUU<br />
DATE<br />
DAY<br />
DSN<br />
EXP-DATE<br />
FIL<br />
JOB-NAME<br />
LEN<br />
MODE<br />
MSG<br />
NGEN<br />
NOAC<br />
OW ID<br />
Alphabetic CPU ID of the CPU on which this version was created. It is<br />
determined by the System Adapter option record.<br />
Tape unit on which this version was created. If the version was created using<br />
the DYN<strong>CA</strong>T ADD function, this field is blank.<br />
Creation date of this version. This is taken from the system date in the<br />
supervisor—not the temporary COMRG date. You can modify it with the<br />
DYN<strong>CA</strong>T ALTER function.<br />
Number of days from creation date that data set versions are to be retained.<br />
Name of the data set as it appears in the catalog file.<br />
Expiration date of this version. If days retention is specified, this value is<br />
calculated when the version is created or taken from the TLBL. You can modify<br />
it with the DYN<strong>CA</strong>T ALTER function.<br />
File sequence number.<br />
Jobname in which this version of the data set was created.<br />
Length specified <strong>for</strong> the data set, tape volume, or both.<br />
Mode at which the version was created.<br />
Additional notes about this version; <strong>for</strong> example, MF <strong>for</strong> multifile data set and<br />
AMF <strong>for</strong> automatic multifile data set.<br />
Number of versions to be retained.<br />
Number of days to retain this version since it was last accessed as input.<br />
Data set owner identification characters—blank if there is no ownership <strong>for</strong> the<br />
data set.<br />
Chapter 3: Supporting Tape File Management 3–43