NOCOMP control statement
A NOCOMP control statement specifies the field that you want to exclude from comparison. A NOCOMP control statement applies to all members that the SYSIN DD statement specifies, regardless of the order of the statements.
Summary of NOCOMP keyword parameters for source-level compare
The following table summarizes the NOCOMP keyword parameters and, for each parameter, the statements and parameters that are not compared. Refer to this table when you compare members at the source level.
NOCOMP keyword parameter | Affected member type | Statements and parameters not compared |
---|---|---|
AREA | DBD |
|
COMPRTN | DBD |
|
DBDNAME | DBD |
|
IMSREL | DBD |
|
PSB |
|
|
KEYLEN | PSB |
|
LANG | PSB |
|
LIST | PSB |
|
METADATA (or CATALOG) | DBD |
|
PSB | EXTERNALNAME=, REMARKS= | |
PCBNAME | PSB |
|
PROCOPT | PSB |
|
PROCSEQ | PSB |
|
PROCSEQD | PSB |
|
PSB_ACCESS | PSB |
|
PSB_PSELOPT | PSB |
|
PSBNAME | PSB |
|
RMNAME | DBD |
|
VERSION | DBD |
Note: NOCOMP=VERSION parameter specifies that the value of the VERSION= parameter of
the DBD statement is not compared. It is not for the DBVER= parameter of the DBD statement, which is
used for database versioning.
|
Summary of NOCOMP keyword parameters for block-level compare
The following table summarizes the NOCOMP keyword parameters and, and for each parameter, the fields that are not compared. Refer to this table when you compare members at the block level.
NOCOMP keyword parameter | Affected member type | Fields that are not compared (Section and field description) |
---|---|---|
AREA | DBD | Fields related to the AREA statement and the following fields:
|
DBD-type ACB | Fields related to the AREA statement and the following fields:
|
|
COMPRTN | DBD | Fields related to the COMPRTN= parameter of the SEGM statement and the following fields:
|
DBD-type ACB | Fields related to the COMPRTN= parameter of the SEGM statement and the following fields:
|
|
DBDNAME | DBD, DBD-type ACB | Fields related to the DBD NAME= statement |
DMBNUM | DBD-type ACB | DMB number field |
IMSREL | DBD |
|
PSB |
|
|
KEYLEN | PSB | Fields related to the KEYLEN= parameter of the PCB statement |
PSB-type ACB | Fields related to the KEYLEN= parameter of the PCB statement and the following fields:
|
|
LANG | PSB, PSB-type ACB | Field related to the LANG= parameter |
LIST | PSB, PSB-type ACB | Field related to the LIST= parameter |
METADATA (or CATALOG) | DBD, DBD-type ACB, PSB, PSB-type ACB | Fields related to the metadata fields in DBD, PSB, or ACB |
PCBNAME | PSB | Fields related to the PCBNAME= parameter, the label parameter of the PCB statement, and the
following fields:
|
PSB-type ACB | Fields related to the PCBNAME= parameter, the label parameter of the PCB
statement, and the following field:
|
|
PROCOPT | PSB | Fields related to the PROCOPT= parameter |
PSB-type ACB | Fields related to the PROCOPT= parameter and the following fields:
|
|
PROCSEQ | PSB | Fields related to the PROCSEQ= parameter |
PSB-type ACB | Fields related to the PROCSEQ= parameter and the following fields:
|
|
PROCSEQD | PSB | Fields related to the PROCSEQD= parameter
|
PSB-type ACB | Fields related to the PROCSEQD= parameter and the following fields:
|
|
PSB_ACCESS | PSB, PSB-type ACB | Fields related to the ACCESS= parameter |
PSB_PSELOPT | PSB, PSB-type ACB | Fields related to the PSELOPT= parameter |
PSBNAME | PSB, PSB-type ACB | Fields related to the PSBNAME= parameter |
RMNAME | DBD | Fields related to the RMNAME= parameter |
DBD-type ACB | Fields related to the RMNAME= parameter and the following fields:
|
|
VERSION | DBD, DBD-type ACB, PSB-type ACB | Fields related to the VERSION= parameter Note: NOCOMP=VERSION parameter specifies that the value of the VERSION= parameter of
the DBD statement is not compared. It is not for the DBVER= parameter of the DBD statement, which is
used for database versioning.
|
Description of NOCOMP keyword parameters
- AREA
- This parameter indicates that for DBD and DBD-type ACB members, the AREA statements of the
DBDGEN utility and the fields that relate to the AREA statements are not compared.
The AREA statement of the DBDGEN utility defines an area within the database, and it also affects fields in the member. If NOCOMP=AREA is specified, the fields that are defined by the AREA statement and any fields affected by the AREA statement are not compared.
- COMPRTN
- This parameter indicates that for DBD and DBD-type ACB members, the fields that relate to the
COMPRTN= parameter of the SEGM statement of the DBDGEN utility are not compared.
The COMPRTN= parameter of the DBDGEN utility defines the segment compression parameters, and it also affects fields in the member. If NOCOMP=COMPRTN is specified, the fields that are defined by the COMPRTN= parameter and the fields affected by the COMPRTN= parameter are not compared.
- DBDNAME
- This parameter indicates that the fields that are related to the DBD NAME= statement, which was used for creating the DBD or DBD-type ACB member, are not compared. DBD names that are specified by other statements, such as external DBD names, are compared even if this parameter is specified. This parameter is useful for comparing members that have different names.
- DMBNUM
- This parameter indicates that the DMB number field in DBD-type ACB is not compared. This field value depends only on the order of ACB generations.
- IMSREL
- Even if two members are generated from the same source, if the version of IMS that generated the two members is different, the compare utility might report some differences between the members. If you specify NOCOMP=IMSREL, the utility does not compare such difference and reports that the two members are the same.NOCOMP=IMSREL works as follows:
- For source-level compare, the utility does not compare the parameters that were added or removed by certain IMS versions.
- For block-level compare, the utility does not compare the fields that are different between certain IMS versions or that were added or removed by certain IMS versions.
Usage note: Whether NOCOMP=IMSREL is specified or not, the utility does not compare the IMS release that generated the DBD or the PSB members. - KEYLEN
- This parameter indicates that for PSB and PSB-type ACB members, the fields that relate to the
KEYLEN= parameter of the PCB statement of the PSBGEN utility are not compared.
The KEYLEN= parameter of the PSBGEN utility defines the length of the longest concatenated key for the PCB, and it also affects fields in the member. If NOCOMP=KEYLEN is specified, the fields that are defined by the KEYLEN= parameter and the fields affected by the KEYLEN= parameter are not compared.
- LANG
- This parameter indicates that for PSB and PSB-type ACB members, the field that relates to the LANG= parameter of the PSBGEN utility is not compared.
- LIST
- This parameter indicates that for PSB and PSB-type ACB members, the field that relates to the LIST= parameter of the PSBGEN utility is not compared.
- METADATA
- This parameter indicates that the metadata fields in DBD, PSB, or ACB are not compared.
Instead of specifying NOCOMP=METADATA, you can specify NOCOMP=CATALOG. CATALOG is an alias for METADATA.
- PCBNAME
- This parameter indicates that for PSB and PSB-type ACB members, the fields that relate to the
PCBNAME= parameter and the label parameter of the PCB statement of the PSBGEN utility are not
compared.
The PCBNAME= parameter and the label parameter of the PSBGEN utility define the name of the PCB, and they also affect fields in the member. If NOCOMP=PCBNAME is specified, the fields that are defined by these parameters and the fields affected by the parameters are not compared.
- PROCOPT
- This parameter indicates that for PSB and PSB-type ACB members, the fields that relate to the
PROCOPT= parameter of the PSBGEN utility are not compared.
The PROCOPT= parameter of the PSBGEN utility defines the processing options, and it also affects fields in the member. If NOCOMP=PROCOPT is specified, the fields that are defined by the PROCOPT= parameter and the fields affected by the PROCOPT= parameter are not compared.
- PROCSEQ
- This parameter indicates that for PSB and PSB-type ACB members, the fields that relate to the
PROCSEQ= parameter of the PSBGEN utility are not compared.
The PROCSEQ= parameter of PSBGEN utility defines the name of a secondary index, and it also affects fields in the member. If NOCOMP=PROCSEQ is specified, the fields that are defined by the PROCSEQ= parameter and the fields affected by the PROCSEQ= parameter are not compared.
- PROCSEQD
- This parameter indicates that for PSB and PSB-type ACB members, the fields that relate to the
PROCSEQD= parameter of the PSBGEN utility are not compared.
The PROCSEQD= parameter of the PSBGEN utility defines the name of a secondary index for the primary DEDB database, and it also affects fields in the member. If NOCOMP=PROCSEQD is specified, the fields that are defined by the PROCSEQD= parameter and the fields affected by the PROCSEQD= parameter are not compared.
- PSB_ACCESS
- This parameter indicates that for PSB and PSB-type ACB members, the field that relates to the ACCESS= parameter of the PSBGEN utility is not compared.
- PSB_PSELOPT
- This parameter indicates that for PSB and PSB-type ACB members, the field that relates to the PSELOPT= parameter of the PSBGEN utility is not compared.
- PSBNAME
- This parameter indicates that the fields that are related to the PSBNAME= parameter, which was used for creating the PSB or PSB-type ACB member, are not compared. This parameter is useful for comparing members that have different names.
- RMNAME
- This parameter indicates that for DBD and DBD-type ACB members, the fields that relate to the
RMNAME= parameter of the DBD statement of the DBDGEN utility are not compared.
The RMNAME= parameter of the DBDGEN utility defines the randomizing parameters, and it also affects fields in the member. If NOCOMP=RMNAME is specified, the fields that are defined by the RMNAME= parameter and the fields affected by the RMNAME= parameter are not compared.
- VERSION
- This parameter indicates that for DBD, DBD-type ACB, and PSB-type ACB members, the fields
related to the VERSION= parameter of the DBDGEN utility is not compared.Note: NOCOMP=VERSION parameter specifies that the value of the VERSION= parameter of the DBD statement is not compared. It is not for the DBVER= parameter of the DBD statement, which is used for database versioning.
Examples
- To specify a single parameter, code the statement as follows:
NOCOMP=VERSION
- To specify multiple parameters, use commas to separate the parameters. For
example:
NOCOMP=VERSION,DBDNAME,AREA
- To specify multiple parameters that cannot fit on one line, code multiple NOCOMP keywords as
follows:
NOCOMP=VERSION,DMBNUM,IMSREL NOCOMP=DBDNAME,PSBNAME NOCOMP=AREA,RMNAME,COMPRTN,PCBNAME,KEYLEN NOCOMP=LANG,LIST,PROCOPT,PROCSEQ NOCOMP=PROCSEQD,PSB_PSELOPT,PSB_ACCESS NOCOMP=METADATA