Table of Contents

Search

  1. Preface
  2. Part 1: PowerExchange Change Data Capture Introduction
  3. Part 2: CDC Components Configuration and Management
  4. Part 3: CDC Sources Configuration and Management
  5. Part 4: Change Data Extraction
  6. Part 5: Monitoring and Tuning
  7. Appendix A: CDC for z/OS Troubleshooting
  8. Appendix B: DTL__CAPXTIMESTAMP Time Stamps

ARCHIVE_OPTIONS Parameters

ARCHIVE_OPTIONS Parameters

In the ARCHIVE_OPTIONS substatement of the DEFINE statement, you can set parameters for allocating and managing archive log data sets.
Syntax:
ARCHIVE_OPTIONS   [PREFIX_COPY1=
prefix
,]   [PREFIX_COPY2=
prefix
,]   [ARCHIVE_BLKSIZE=
number
,]   [ARCHIVE_DACL=
sms_dataclas
,]   [ARCHIVE_DACL2=
sms_dataclas
,]   [ARCHIVE_MGCL=
sms_mgmtclas
,]   [ARCHIVE_MGCL2=
sms_mgmtclas
,]   [ARCHIVE_RTPD=
number_of_days
,]   [ARCHIVE_RTPD2=
number_of_days
,]   [ARCHIVE_STCL=
sms_storclas
,]   [ARCHIVE_STCL2=
sms_storclas
,]   [ARCHIVE_UNIT=
unit_name
,]   [ARCHIVE_UNIT2=
unit_name
,]   [ARC_UNIT_CNT=
number
,]   [PRIM_SPACE=
number
,]   [SEC_SPACE=
number
,]   [SPACE_ALLOC=
type_of_units
]
Parameters:
The following table describes the ARCHIVE_OPTIONS parameters:
Parameter
Description
Valid Values
PREFIX_COPY1
Specifies the prefix for the first archive log data set name.
If you use multiple qualifiers, enclose the prefix in quotation marks.
The value can be up to 17 alphanumeric characters long and must follow MVS data set name rules.
With Post-Log Merge, all member Loggers must have a unique value for this parameter.
PREFIX_COPY2
Specifies the prefix for the second archive log data set name.
If you use multiple qualifiers, enclose the prefix in quotation marks.
The value can be up to 17 alphanumeric characters long and must follow MVS data set name rules.
If you use this keyword, the value cannot be blank, even if you specified ARCHIVE_LOG_MODE=SINGLE.
With Post-Log Merge, all member Loggers must have a unique value for this parameter.
ARCHIVE_BLKSIZE
Specifies the block size of the archive log data set.
The block size must be compatible with the device type you specify in the ARCHIVE_UNIT parameter.
The value must be a multiple of 4096 and must be in the range 4096 through 28672.
Default is 24576.
ARCHIVE_DACL
Specifies the SMS data class name of the archive log data set.
If this value is omitted, no SMS data class is specified when allocating the primary archive log data set. One might be assigned by your SMS ACS routines.
ARCHIVE_DACL2
Specifies the SMS data class name of the second archive log data set.
If this value is omitted, the second archive log takes the data class of the first archive log data set, if specified.
Specify ARCHIVE_DACL2=, to prevent a data class name specified for the first archive log data set being used as a default for the second.
ARCHIVE_MGCL
Specifies the SMS management class name of the archive log data set.
If this value is omitted, no SMS management class is specified when allocating the primary archive log data set. One might be assigned by your SMS ACS routines.
ARCHIVE_MGCL2
Specifies the SMS management class name of the second archive log data set.
If this value is omitted, the second archive log takes the management class of the first archive log data set, if one is specified.
Specify ARCHIVE_MGCL2=, to prevent a management class name specified for the first archive log data set being used as a default for the second.
ARCHIVE_RTPD
Specifies the number of days to retain the archive log data set.
A number from 0 through 9999.
Default is 9999.
ARCHIVE_RTPD2
Specifies the number of days to retain the second archive log data set.
Use this parameter only if you want to set the value differently for the second data set.
A number from 0 through 9999.
Default is 9999.
ARCHIVE_STCL
Specifies the SMS storage class name of the archive log data set.
If this value is omitted, no SMS storage class is specified when allocating the primary archive log data set. One might be assigned by your SMS ACS routines.
ARCHIVE_STCL2
Specifies the SMS storage class name of the second archive log data set.
If this value is omitted, the second archive log takes the storage class of the first archive log data set, if specified.
Specify ARCHIVE_STCL2=, to prevent a storage class name specified for the first archive log data set being used as a default for the second.
ARCHIVE_UNIT
Specifies the device type or unit name of the device used to store the archive log data set.
Specify a device type or unit name up to eight alphanumeric characters long.
Informatica recommends that you write the primary archive log data set to DASD.
ARCHIVE_UNIT2
Specifies the device type or unit name of the device used to store the second archive log data set.
Use this parameter only if you want to set the value differently for the second data set.
If this value is omitted, the second archive log takes the UNIT value of the first archive log data set.
Specify ARCHIVE_UNIT2=, to prevent a unit type specified for the first archive log data set being used as a default for the second
Specify a device type or unit name up to 8 alphanumeric characters long.
ARC_UNIT_CNT
Specifies the number of DASD units to use for archiving.
Use this parameter in the same way you use the count option of the MVS UNIT parameter.
If using SMS, the SMS data class specifies the volume count for SMS-managed data sets.
Default is 2 units.
PRIM_SPACE
Specifies the primary space allocation for DASD data sets in the unit type specified by SPACE_ALLOC.
A number greater than 0.
Default is 4320 blocks.
SEC_SPACE
Specifies the secondary space allocation for DASD data sets in the unit type that you specify in SPACE_ALLOC.
A number greater than 0.
Default is 540 blocks.
SPACE_ALLOC
Specifies the type of units in which primary and secondary space are allocated.
  • BLK. Allocates space in blocks.
  • CYL. Allocates space in cylinders.
  • TRK. Allocates space in tracks.
Default is BLK.
Usage Notes:
You must specify at least one parameter for this statement.
If you specify multiple parameters, use a comma (,) as a separator character. The last parameter must not end in a comma.

0 COMMENTS

We’d like to hear from you!