DD statements for OPC
DD statements for OPC determine the input and output data sets and specify how to run OPC.
The following table summarizes the DD statements for OPC. The optional output data sets that are used by OPC are determined by the combination of the TYPRUN keyword and the FULLSTEP keyword of the ANALYZE control statement.
DDNAME | Use | Format | Required or optional |
---|---|---|---|
JOBLIB or STEPLIB | Input | PDS | Required |
FPXOPTS | Input | LRECL=80 | Optional |
FPXIN, or SYSIN and DASYSIN | Input | LRECL=80 | Required |
FPXMFILE | Output | LRECL=133 | Optional |
FPXRPTS | Output | LRECL=133 | Optional |
FPXSPRT | Output | LRECL=133 | Optional |
HFPPRINT | Output | LRECL=133 | Optional |
reportdd | Output | LRECL=133 | Optional |
SYSPRINT | Output | LRECL=121 | Required |
DFSUDUMP (ic1outdd or ic2outdd) | Output | IC1 or IC2 | Optional |
SNAPPIT | Output | LRECL=133 | Optional |
FPXAUOWC | Input | LRECL=80 | Required when FPXAHST2 DD is specified |
FPXAHST | Output | DISP=MOD | Optional |
FPXAHST2 | Output | LRECL=133 | Required when FPXAUOWC DD is specified |
FPXARERG | Output | LRECL=80 | Optional |
TARnnnnn | Output | PS | Required when both of the following conditions
are met:
|
DAR12O | Output |
|
Required when FULLSTEP=NO |
DAR13SO | Output |
|
Required when FULLSTEP=NO |
SORT12 | Output | LRECL=80 | Required when FULLSTEP=NO |
SORT3CS | Output | LRECL=80 | Required when FULLSTEP=NO |
DAR3CSO | Output |
|
Required when FULLSTEP=NO |
IMSDALIB | Input | PDS | Optional |
RECONn | Input/Output |
|
Required when all of the following
conditions are met:
|
TOOLSNP1 | Output | LRECL=125 | Optional |
TOOLSNP2 | Output | LRECL=125 | Optional |
HFPABEND | Output | LRECL=125 | Optional |
SYSOUT | Output | LRECL=121 | Optional |
i001WKnn | Input/Output |
|
Optional |
i001SMSG | Output | LRECL=133 | Optional |
ICEIN | Input | LRECL=80 | Optional |
ICEPRINT | Output | LRECL=133 | Optional |
ICERPRT | Output | LRECL=133 | Optional |
dataout1 | Output | PS | Optional |
dataout2 | Output | PS | Optional |
D2Xnnnn | Input/Output | Optional | |
D3Cnnnn | Input/Output | Optional | |
D3SRnnnn | Input/Output | Optional | |
D3SInnnn | Input/Output | Optional | |
D4Pnnnn | Input/Output | Optional | |
D4Snnnn | Input/Output | Optional | |
WPRNnnn | Input/Output | Optional | |
WSNAP | Input/Output | LRECL=133 | Optional |
- STEPLIB DD
- Defines the library that contains the OPC utility.
- The load library of IMS HP Image Copy must be concatenated if you specify the comprtn parameter on the IC keyword or the IC=(YES,ICEIN) keyword.
- The IMS Tools Base library (SHKTLOAD) is required if you specify the ADXCFGRP keyword, the ITKBSRVR keyword, or the SENSOR=YES option.
- The library that contains DFSMDA dynamic allocation members for the RECON data sets.
- FPXOPTS DD
- Defines the input data set that contains the option control statements for the process. FPXOPTS usually resides in the input stream. However, it can also be defined as a sequential data set or as a member of a partitioned data set. It must contain 80-byte fixed-length records. Block size, if coded, must be a multiple of 80. It can be specified as DUMMY, NULLFILE, or an empty file.
- FPXIN DD
- Defines the control statements for OPC. FPXIN describes the area to be processed, and it can contain optional user requests that further define the operating mode. FPXIN DD and SYSIN DD are mutually exclusive. FPXIN usually resides in the input stream. However, it can also be defined as a sequential data set or as a member of a partitioned data set. It must contain 80-byte fixed-length records. Block size, if coded, must be a multiple of 80. It cannot be specified as DUMMY, NULLFILE, or an empty file. When both FPXIN DD and DASYSIN DD are specified, DASYSIN DD is ignored.
- SYSIN DD
- Defines the input control data set that contains the IMS IFP utility control statements. A minimum of four statements is required,
as shown below:
TYPE TOOL AREA areaname EXIT ANALYZE GO
where areaname is the name of an area to be processed. Only one area per job step can be specified.
- DASYSIN DD
- Defines the control statement file that contains the data collection options, image copy specifications and reporting options. This data set can reside on a direct-access device or be routed through the input stream.
- FPXMFILE DD
- Defines the default message output. The output can go to a data set or to a printer, routed through the output stream. If the DD statement is specified explicitly or implicitly by the MFILE keyword of the ANALYZE control statement, and if the DD statement for the specified DD name is not coded in the JCL stream, the DD is allocated dynamically to the system output stream with SYSOUT=*. If the DD name is overridden by the MFILE keyword with a different DD name, the DD statement for the specified DD name must be coded in the JCL stream.
- FPXRPTS DD
- Defines the default report output. The output can go to a data set or to a printer, routed through the output stream. If the DD statement is specified explicitly or implicitly by the RFILE keyword of the ANALYZE control statement and if the DD statement for the specified DD name is not coded in the JCL stream, the DD is allocated dynamically to the system output stream with SYSOUT=*. If the DD statement is overridden by the RFILE keyword with a different DD name, and the DD statement for the specified DD name is not coded in the JCL stream, the DD is allocated dynamically to the system output stream with SYSOUT=*.
- FPXSPRT DD
- Defines the report output data set when SENSOR=YES is specified. This output data set contains
the Sensor Data Statistics report that can be used to verify which sensor data is stored in the
Sensor Data repository of IMS Tools KB. The following DCB
attributes of the file are set by FPO:
- RECFM=FBA
- LRECL=133
- BLKSIZE=1330
- HFPPRINT DD
- Defines the message output data set when FULLSTEP=YES is specified. This output data set
contains the HFP messages, which are the processing messages issued by FPA. The following DCB
attributes of the file are set by FPA:
- RECFM=FBA
- LRECL=133
- BLKSIZE=1330
The HFPPRINT data set contains 133-byte, fixed-length records. It is recommended that you code your DD statement as follows://HFPPRINT DD SYSOUT=A
- reportdd DD
- Defines the output for the following reports:
- DEDB Area Analysis reports
- UOW report
- UOW Exception report
- Largest Database Records report
- Consolidated Largest Database Records report
- Segment Length Distribution report
- DB Record Length Distribution report
- RBA of Used IOVF CI report
This statement is used only when you specify the TYPRUN=RPT and the FULLSTEP=YES keywords, or the TYPRUN=FS and the FULLSTEP=YES keywords.
reportdd DD is similar to the reportdd DD of the Analyze function of FPA.
- SYSPRINT DD
- Defines the system message output. For OPC with SYSIN DD, SYSPRINT is used by OPC as the default
message data set until it is (optionally) overridden by the MFILE= keyword of the ANALYZE control
statement. Warning: You cannot allocate the OPC SYSPRINT DD output stream to a data set because SYSPRINT DD is also used by IMS. If you specify SYSPRINT DD as a data set, some output might become overridden or unpredictable open or close errors might occur. Therefore, you must specify SYSPRINT DD as SYSOUT.
- DFSUDUMP DD
- Defines the default output image copy data set. DFSUDUMP is used by OPC as the default primary
image copy data set until it is (optionally) overridden by the IC1OUTDD keyword of the ANALYZE
control statement. The output can reside on a tape or on a direct-access device. If the DD statement
is overridden by the IC1OUTDD keyword with a different DD name, the DD statement for the specified
DD name must be coded in the JCL stream.
Do not specify DISP=MOD for this DD statement.
- SNAPPIT DD
- Defines the output for the CI SNAP dump produced by OPC.
- FPXAUOWC DD
- Each record in this data set specifies a range of UOW numbers of an area, which defines a UOW group of the area. The information about the UOW group is recorded in the FPXAHST2 data set or in a sensor data record set in the order that is specified in the FPXAUOWC data set, even if the UOW ranges overlap or are in reverse order.
- FPXAHST DD
- Defines an output data set that contains historical records. The analysis report generation process adds one record for each DEDB area that it processes. The record contains the key space utilization and performance information for that area. This statement is used only when you specify the TYPRUN=RPT keyword and the FULLSTEP=YES keyword.
- FPXAHST2 DD
- Defines an output data set that contains historical records. The analysis report generation process adds one record for each UOW group that is specified by FPXAUOWC DD. The record contains the key space utilization and performance information for the area, which is based on the information obtained from the specified UOW range. This statement is used only when you specify the FPXAUOWC DD statement, the TYPRUN=RPT keyword, and the FULLSTEP=YES keyword. If FPXAUOWC DD statement is not specified, this statement is ignored.
- FPXARERG DD
- Defines an output data set that contains the reorganization control statements for the
High-Speed DEDB Direct Reorganization utility (DBFUHDR0).
This statement is used only when you specify the TYPRUN=RPT and the FULLSTEP=YES keywords, or the TYPRUN=FS and the FULLSTEP=YES keywords.
The following DCB attributes of the file are set by the Analyze process:- RECFM=PS
- LRECL=80
- BLKSIZE=800
The FPXARERG DD is similar to the HFPARERG DD of the Analyze function of FPA.
- TARnnnnn DD
- Defines the tuning aid record data set. A TARnnnnn DD statement specifies
the tuning aid record data set for one area.
When TARECGEN=YES is specified, TARnnnnn DD statements define the output data sets for generating tuning aid records. If this statement is not specified for an area, the tuning aid record for that area is not generated.
A TARnnnnn DD statement is for areas in the range of 1 - 9999. The value of nnnnn must be right-aligned, with leading zeros if necessary. When you code multiple TARnnnnn DD statements, do not specify the same data set more than once; each TARnnnnn DD statement must point to a different data set.
This data set can be allocated dynamically by specifying the TARDSNMASK keyword of the ANALYZE statement.
For a description and space requirement of the tuning aid records, see Tuning aid records.
- DAR12O DD
- Defines the output data set containing the free space and area information records. The data set can reside on either a direct-access device or a tape. When FULLSTEP=YES is specified, this DD statement is not used.
- DAR13SO DD
- Defines the output data set containing the segment information records for all segments that reside in the root addressable part of the database. The data set can reside on either a direct-access device or a tape. When FULLSTEP=YES is specified, this DD statement is not used.
- SORT12 DD
- Defines the output data set for the SORT control statements for the SORT12 step. The data set
must reside on a direct-access device. When FULLSTEP=YES is specified, this DD
statement is not used.
Space requirements are very small (1 track suffices). Do not specify DISP=MOD for this DD statement.
DCB information is hard-coded in OPC. Do not code DCB information in your JCL.
- SORT3CS DD
- Defines the output data set for the SORT control statements for the sort before pointer
resolution. The data set must reside on a direct-access device. When FULLSTEP=YES
is specified, this DD statement is not used.
Space requirements are very small (1 track suffices). Do not specify DISP=MOD for this DD statement.
DCB information is hard-coded in OPC. Do not code DCB information in your JCL.
- DAR3CSO DD
- Defines the output data set containing all pointer information records and the segment information records for all segments that reside in IOVF and SDEP. The data set can reside on either a direct-access device or a tape. When FULLSTEP=YES is specified, this DD statement is not used.
- IMSDALIB DD
- An optional DD statement that defines the library that contains DFSMDA dynamic allocation members for the RECON data sets.
- RECON1/RECON2/RECON3 DD
- Defines the DBRC RECON data sets. You must specify these DD statements when you
specify both IC=YES and ICNOTIFY=YES keywords, or both ITKBSRVR=servername and
DBRC=YES keywords. RECONn data sets must be the same data sets that are used in
the IMS control region.
When you specify IC=YES and ICNOTIFY=YES, OPC updates RECONn data sets because OPC registers the image copy data set to DBRC. When you specify ITKBSRVR=servername and DBRC=YES, OPC retrieves the RECON ID from RECON data sets.
If these statements are omitted when the data sets are necessary and if DFSMDA members are available, the utility uses the DFSMDA members and dynamically allocates the data sets.
- TOOLSNP1
- Defines a snap dump output data set used for diagnostic purposes. All you need to provide is the DSN and space allocation. OPC assigns the correct DCB parameters internally. Usually, //TOOLSNP1 DD SYSOUT=* is sufficient.
- TOOLSNP2
- Defines a secondary diagnostic output file subject to the same restrictions as TOOLSNP1.
- HFPABEND DD
- Defines a snap dump output data set used for diagnostic purposes. This data set might be used when FULLSTEP=YES is specified and the FPO job ends abnormally. Do not code the DCB information in your JCL statement. The output data set must be a standard SYSOUT or a sequential data set.
- SYSOUT DD
- Defines the output data set that is used by both OPC and DFSORT for message functions. OPC writes images of its control statements that are specified in DASYSIN DD. When the FULLSTEP=YES keyword is specified, this output data set also contains the message that is produced by DFSORT.
- i001WKnn DD
- An optional DD statement. These are intermediate storage data sets that are used by DFSORT. For
more information about coding the SORTWKnn DD statements, see the DFSORT
Application Programming Guide. The adequate size of storage data sets is 1.5 to 2.5 times the
input file size. This statement is used only when you specify the FULLSTEP=YES keyword.
Allocating twice the space used by the SORTIN data set is usually adequate for each work data set.
Do not specify DISP=MOD for these DD statements.
- i001SMSG DD
- This DD statement is an optional DD statement. However, this DD statement is required when DFSORT is used. This statement defines an output data set for storing DFSORT messages. For the condition for running DFSORT and the naming rules for the DD names, see the description of i001WKnn DD.
- ICEIN DD
- This DD statement is an optional DD statement. This statement specifies the input data set that contains the control statements for IMS HP Image Copy. The data set can reside on a tape, a direct-access volume, or it can be routed through the input stream (DD * or DD DATA). This data set is used only when you specify IC=(YES,ICEIN). If the DD statement is not coded and if IC=(YES,ICEIN) is specified, the default control statements are used. For details about the ICEIN control statements, see the IMS High Performance Image Copy User's Guide.
- ICEPRINT DD
- This DD statement is an optional DD statement. This statement specifies the output data set that contains the reports that are produced by IMS HP Image Copy. The data set can reside on a tape, a direct-access volume, or a printer, or it can be routed through the output stream (SYSOUT). This data set is used only when you specify IC=(YES,ICEIN). If the DD statement is not coded and IC=(YES,ICEIN) is specified, a SYSOUT stream is dynamically allocated for the DD.
- ICERPRT DD
- This DD statement is an optional DD statement. This statement specifies the output data set that contains the Image Copy Dump Process report, which is produced by IMS HP Image Copy. It can reside on a tape, a direct-access volume, or a printer, or it can be routed through the output stream (SYSOUT). This data set is used only when you specify IC=(YES,ICEIN).
- dataout1 DD
- This DD statement is an optional DD statement. This statement defines the primary image copy data set. One DD statement is required for each data set that is to be dumped. The DD name can be any 1- to 8-character string. The data set specified by the DD statement must be on either a direct-access device or a tape device. This data set is used only when you specify IC=(YES,ICEIN).
- dataout2 DD
- This DD statement is an optional DD statement. This statement defines the secondary image copy data set. This statement is required only if the associated ICEIN control statement requests the secondary image copy. The data set specified by the DD statement must be on either a direct-access device or a tape device. This data set is used only when you specify IC=(YES,ICEIN).
- D2Xnnnn DD
- D3Cnnnn DD
- D3SRnnnn DD
- D3SInnnn DD
- D4Pnnnn DD
- D4Snnnn DD
- WPRNnnn DD
- Define the intermediate work data sets. FPO uses up to three sets of intermediate work data
sets, one set for processing one area. For each set, the same nnnn value is used.
nnnn must be right-aligned with leading zeros. These statements
are used only when you specify the FULLSTEP=YES keyword.
- D2Xnnnn data sets contain the free space and area information records.
- D3Cnnnn data sets contain all non-SDEP pointer information records.
- D3SRnnnn data sets contain the segment information records for all segments that reside in the RAP part of the database.
- D3SInnnn data sets contain the segment information records for all segments that reside in the IOVF part of the database.
- D4Pnnnn data sets contain all SDEP pointer information records.
- D4Snnnn data sets contain the segment information records for all segments that reside in the SDEP part of the database.
- WPRNnnn data sets contain analysis reports.
Do not specify DISP=MOD for these DD statements. DCB information is hard-coded in OPC. Do not code DCB information in your JCL.
- Note on dynamic allocation:
- If these statements are not specified in the JCL statements when these data sets are necessary, FPO allocates them dynamically.
- WSNAP DD
- This DD statement is an optional DD statement. It defines the intermediate work data set for
snap dumps. This statement is used only when you specify the FULLSTEP=YES keyword.
Do not specify DISP=MOD for this DD statement. DCB information is hard-coded in OPC. Do not code DCB information in your JCL.
- Note on dynamic allocation:
- If this statement is not specified in the JCL statements when this data set is necessary, FPO allocates it dynamically.