For this option, the output data set is a sequential file. The rows are fixed length with a record length equal to the length of detail records generated by the query to be output.
CA Dataquery writes the data as returned, one row per output record and does not export totals, header, or trailer records. The output columns have the same data types and lengths as the columns in the CA Datacom/DB table from which they were retrieved. Nullable fields are preceded with a 1-byte null indicator:
Indicates that the field is not null.
Indicates that the field has a null value.
Only one set of data is available in the fixed record formatted file. CA Dataquery overwrites any data in the file when it exports data. Therefore, if you are doing several successive batch exports, specify a different data set in the job stream for each export.
Procedure
When you create your JCL member for exporting data, you need to specify the name of the data set to which the export data is to be written. The JCL member can specify any device type supported by IBM QSAM (z/OS). You can specify either a tape or disk file in your JCL member.
CA Dataquery has specific requirements for the DDname in your export JCL member name. In z/OS, the DDname must be DQFIXD. In z/VSE, the DLBL must be DQFIXD. specifies the devices as tape or disk.
When exporting fixed-format records, you can execute only one query per execution of CA Dataquery Batch. CA Dataquery allows only one EXPORT FIXED control statement per execution. The EXPORT FIXED statement should follow the EXECUTE statement.
EXPORT Control Statement (z/OS)
A sample format for z/OS EXPORT FIXED control statement follows:
►►─ EXPORT ─ 'setname' ─ FIXED ───────────────────────────────────────────────►◄
EXPORT Control Statement (z/VSE)
A sample format for z/VSE EXPORT FIXED control statement follows:
►►─ EXPORT ─ 'setname' ─ FIXED ─┬─ DISK ─┬────────────────────────────────────►◄ └─ TAPE ─┘
TAPE and DISK are used only in z/VSE and are ignored for z/OS. In z/VSE, you must specify either TAPE or DISK to indicate the output media.
Note: The job control statements used to execute DQBATCH must contain the necessary data definition statements to define the output data set for the EXPORT command.
The type of device is determined only by the data definition statements in the JCL.
|
Copyright © 2014 CA.
All rights reserved.
|
|