OUTDDX
The OUTDDX keyword is valid with the RELOAD and COPY commands.
This keyword is available in PLUSIN; it is not available as a global option. The following table describes the keyword.
Table 1. Write secondary index records to non-DFSURWF1 file keyword
To do this | Specify this in PLUSIN |
|---|---|
Place secondary index work file records in a data set other than DFSURWF1. | OUTDDX(ddname1(indexdb1),ddname2(indexdb2)...) |
Place secondary index work file records in dynamically allocated data sets other than DFSURWF1. | OUTDDX(AUTO) |
Internal default: None | |
The OUTDDX keyword enables you to place secondary index records in a data set other than DFSURWF1. When the OUTDDX keyword is specified, secondary index records are not written to the DFSURWF1 data set; the records for each secondary index are written to separate data sets.
If you do not include an OUTDDX keyword, all secondary index records are written to the DFSURWF1 data set or HLDURIDX.
The OUTDDX keyword does not support shared secondary indexes.
The Reload function OUTDDX keyword is normally used with the Index Build function INDDX keyword.
OUTDDX(ddname1(...)) | Specify the output ddnames to use and the secondary index WF1 records to be written to them in the following format (maximum of 256 characters): OUTDDX(ddname1(indexdb1),ddname2(indexdb2)... ) You must specify each secondary index, and each secondary index must have a different ddname. The records for any secondary index not specifically selected are written to DFSURWF1. |
|---|---|
OUTDDX(AUTO) | When you specify OUTDDX(AUTO), control records are written to the DFSURWF1 file along with DFSURWF1 records for logical relationships. All secondary index records are written to separate DFSURWF1-format data sets. If you specify INDDX(AUTO) in a subsequent Index Build function job step, the file written to DFSURWF1 in the Reload function step is used to dynamically allocate all the separate OUTDDX DFSURWF1 files. To use OUTDDX(AUTO), you must include the following DD statements to the JCL:
|