RECONCOPY processing
The RECON copy (RECONCOPY) support function creates a copy of the RECON data sets that are used by IMS Database Recovery Facility Extended Functions processing, instead of the live RECON data sets.
This process uses the DBRC BACKUP.RECON RECON1 command, so that whichever copy of the RECON data set is COPY1 is used. This process then makes a second and third copy and then allocates these three data sets to the RECON1, RECON2, and RECON3 DD statements.
The RECONCOPY support function is used only in conjunction with other Extended Functions; it does not operate alone.
Not all of the Extended Functions can operate on RECON copies. The following Extended Functions cannot use RECON copies:
- Recovery Point Create (RPCR)
- IMS Commands (IMSCMD)
The following Extended Functions can use RECON copies:
- Recovery point identification (RPID)
- RECON cleanup (RCU)Note: The RECON cleanup (RCU) function requires the use of RECONCOPY. The RCU function will not process without RECONCOPY.
- Recovery health checker (HCHECK)
- Verify recovery assets (VERIFY)
RECONCOPY syntax
RECONCOPY( DSNPREF( dsn-prefix )
REUSE( YES | NO | Y | N )
DELETE( YES | NO | Y | N )
COPY1VOL( volser-list )
COPY2VOL( volser-list )
COPY3VOL( volser-list )
SPACE( space-parameters )
STORCLASS( SMS-storage-class )
MGMTCLASS( SMS-management-class )
DATACLASS( SMS-data-class )
)
RECONCOPY parameter reference
The only required parameter is DSNPREF.
If you do not specify the allocation type parameters (for example, SPACE and VOLSER), their values are obtained from the existing RECON1 data set that is used as a model.
- DSNPREF(dsn-prefix)
- Use this parameter to specify the pattern to use to create the prefix for the RECON copy data
sets.
The prefix length is limited to 38 characters.
The RECON copy data set names will consist of this prefix with .C1 C2, or .C3 as the suffix.
This parameter is required and there is no default.
The prefix allows for several special character strings that cause Extended Functions to substitute values into the prefix. These special character strings are:
- &date
- Substitute a date stamp in the format Dyyyyddd within the name.
- &time
- Substitute a timestamp in the format Thhmmss within the name.
- &jobnm
- Substitute the job name within the name.
- &stepnm
- Substitute the jobstep name within the name.
- REUSE( Y | YES | N | NO )
- Use this parameter to indicate whether to reuse an existing RECON copy data set, if one is
found, with the same name as the one that is being created.
A specification of YES or Y causes the process to delete and redefine the existing data sets.
A specification of NO or N causes the process to terminate when one or more of the data sets already exist.
The default for REUSE is REUSE(NO).
- DELETE( Y | YES | N | NO )
- Use this parameter to indicate whether the RECON copy data sets are deleted at job step
termination.
The default is DELETE(NO).
- COPY1VOL(volser-list ), COPY2VOL( volser-list ), COPY3VOL( volser-list )
- Use these parameters to specify a list of one-to-five volsers on which to allocate the specified
RECON copy data set.
- Use the COPY1VOL parameter to specify the list of volsers for RECON COPY1.
- Use COPY2VOL to specify the list for RECON COPY2.
- Use COPY3VOL to specify the list for RECON COPY3.
- SPACE( space-parameters )
- Use this parameter to specify the space characteristics for the RECON copy data sets.
The values that you specify for this parameter must adhere to the SPACE() parameter that are allowed by IDCAMS as follows:
- SPACE(CYLINDERS(primary, secondary))
- SPACE(TRACKS(primary, secondary))
- SPACE(RECORDS(primary, secondary))
- STORCLASS( SMS-storage-class )
- MGMTCLASS( SMS-management-class )
- DATACLASS( SMS-data-class )
- Use the three SMS parameters to specify the various SMS classes that are used to allocate COPY1, COPY2, and COPY3 of the RECON data sets.