|
|
|
In addition to creating CSV members, CA JARS and CA Earl can write index records to the CAIJSIDX data set as each CSV member is created. This index, or directory, is used to keep track of the CSV files. Each record in the CSV directory has a one byte record type field in the first position of the record. Valid record types are:
Version
Job record
Data set name record
Query name
Member name record
Each record in the CSV directory has one or more fields in addition to the record type field. These fields have a fixed format and length. The version record is created when the CAIJSIDX directory data set is initially created, and identifies the level of the CSV directory and the version of the host software that created the directory file. The job record contains the job name of the execution that created the directory entry, along with a description. The data set name record contains the name of the data set that contains the CSV members that are indicated on subsequent member records. The Query name record will always contain the constant JARBAT, followed by the date and time that the batch execution occurred. The member records contain the CSV member name, the number of records, the report title, and the key structure field. On the next page is an example of what a CA JARS or CA Earl CAIJSIDX directory data set may contain.
position
1 2 3 4 5 6 7
1...5....0....5....0....5....0....5....0....5....0....5....0....5....0
V JARSR12 SP0
J CHARLIEB RUN DATE 1998/09/03 RUN TIME 16:05:47
D CHARLIE.JARS.CSVPDS.OUTPUT
I JARBAT 98/09/03 16:05 CA JARS BATCH EXECUTION
M CSVTST22 00000008 PEAK PAGING PERIODS K1D1
M CSVTST20 00000004 RESOURCE CONSUMPTION SUMMARY K1D1
M CSVTST32 00000004 DISK EXCP SUMMARY BY DAY K1D1
M CSVTST16 00000011 UTILIZATION SUMMARY BY JOB K1D1
M CSVTST18 00000013 PROGRAM PAGING PROFILE K1D1
J CHARLIEB RUN DATE 1998/09/03 RUN TIME 16:20:03
D CHARLIE.JARS.CSVPDS.GDG.G0001V00
I JARBAT 98/09/03 16:20 CA JARS BATCH EXECUTION
M CSVTST22 00000008 PEAK PAGING PERIODS K1D1
M CSVTST20 00000004 RESOURCE CONSUMPTION SUMMARY K1D1
M CSVTST32 00000004 DISK EXCP SUMMARY BY DAY K1D1
M CSVTST16 00000011 UTILIZATION SUMMARY BY JOB K1D1
M CSVTST18 00000013 PROGRAM PAGING PROFILE K1D1
J CHARLIEB RUN DATE 1998/09/03 RUN TIME 16:24:04
D CHARLIE.JARS.CSVPDS.GDG.G0002V00
I JARBAT 98/09/03 16:24 CA JARS BATCH EXECUTION
M CSVTST22 00000008 PEAK PAGING PERIODS K1D1
M CSVTST20 00000004 RESOURCE CONSUMPTION SUMMARY K1D1
M CSVTST32 00000004 DISK EXCP SUMMARY BY DAY K1D1
M CSVTST16 00000011 UTILIZATION SUMMARY BY JOB K1D1
M CSVTST18 00000013 PROGRAM PAGING PROFILE K1D1
Note that only one version record exists, followed by "groups" of Job, data set, query, and member name records that correspond to the various batch executions that have occurred. The CAIJSIDX DD is required during any execution of CA JARS or CA Earl that creates output CSV members, but may be specified as DD DUMMY for users who do not want to maintain this file. Notice that the index file can point to many different data sets that contain CSV files. This example points at a NON-GDG type PDS in the first data set record, and a GDG type PDS in the next two data set records. As many index files and PDS CSV repositories can be maintained by the user as desired. You can have one directory file for each CSV PDS file, one directory file for all CSV PDS files, or a combination of the two.
| Copyright © 2012 CA. All rights reserved. |
|