CDC Guide for z/OS

10.5
- 10.5.8
- 10.5.6
- 10.5.5
- 10.5.4
- 10.5.3
- 10.5.2
- 10.5.1
- 10.4.1
- 10.4.0 HotFix 1
- 10.4.0

Back Next

EDMSDIR Options Module

Set configuration options for the PowerExchange Agent in the EDMSDIR options module.

When you run the SETUPAGT job during installation, the PowerExchange installer assembles and link-edits the EDMSDIR options module and writes it to the PowerExchange USERLIB data set for CDC. The USERLIB is created when you run the SETUPCC1 job during installation. The installer enters values for some EDMSDIR options based on your entries in the z/OS Installation Assistant.

The EDMSDIR options apply to any PowerExchange CDC component that points to this USERLIB library. You can modify the EDMSDIR options, if necessary.

The following table describes the EDMSDIR options:

Option	Description	Default Value	Valid Values
AGENTID	The name of the default PowerExchange Agent.	EDMA	A valid name has the following characteristics: Consists of four characters, beginning with a letter, #, @, or $. Does not conflict with an existing MVS subsystem. Is not the same as the LOGGER name.
CCERR	The action to take when a Db2 for z/OS, IMS synchronous, batch VSAM, or CICS/VSAM ECCR is unable to capture changes for a data source.	CONT	Valid values: CONT . Stops change data capture but allows the transaction or job to continue. Some changes might not be captured. ABEND . Ends the job. The transaction does not update the source. For IMS synchronous capture, the BMP or MPP ends abnormally but the control region continues to be active. In a batch DL/I environment, the batch jobs abend. Notes: If you specify ABEND and the CICS/VSAM ECCR encounters a serious error or abends during initialization, PowerExchange ends and backs out in-flight CICS transactions on VSAM source files during syncpoint processing. If this action is not possible, PowerExchange shuts down the CICS region to ensure data integrity. If the PowerExchange Logger abends or shuts down, it cannot receive updates from the ECCR. In this case, the CICS/VSAM ECCR causes the CICS update transaction to abend with abend code ASP7 at the transaction syncpoint. Because the transaction does not write updates to the VSAM files that are registered for change capture, PowerExchange does not miss any changes. Similarly, if the registration status of a file cannot be determined when the file is opened, the CICS/VSAM ECCR abends transactions that update the file, typically with abend code ASP7 at the transaction syncpoint. This situation might occur when the PowerExchange Agent is down or repository access through the PowerExchange Agent has been stopped. Because no updates are written to the files with the uncertain registration status, PowerExchange does not miss any changes.
CENTURY	Controls whether to include the century in dates that the PowerExchange CDC components display.	Y	Valid values: Y . Displays the century. N . Displays the date without the century.
DATE	The date format that the PowerExchange CDC components use, for example, in messages.	(MDY,/)	In the date format, the first value is one of the following format values: YMD . For YY/MM/DD. MDY . For MM/DD/YY. DMY . For DD/MM/YY. The second value is the separator to use in the date. You can use any character. Default is the forward slash (/).
ESLLIB	The data sets to be concatenated to existing DFSESL DD statements in the IMS dependent region or IMS control region. This option is required for IMS synchronous ECCR online environments. If a DFSESL DD statement does not already exist in your dependent region or control region, PowerExchange allocates one for you. For more information about the DFSESL DD statement, see the IBM IMS installation procedures.	N/A	When you set this value, follow these guidelines: Specify the appropriate data set or data sets, enclosed within parentheses. If you specify multiple data sets, separate them with commas. You can specify up to five data sets.
IAUPABND	Controls the behavior of IMS online update transactions and online batch jobs in an IMS control region when the CCERR=ABEND option is specified and the PowerExchange Logger for z/OS ends abnormally after the IMS control region is running. This option also controls the behavior of IMS batch DL/I jobs when the PowerExchange Logger is not available when the jobs start. In an online environment, this option does not affect transactions that access the database in read-only mode. In a batch DL/I environment, this option does not affect jobs that use PSBs that do not update any database. In all environments, this option has no effect when CCERR=CONT is specified. If the PowerExchange Logger is down when you try to start the IMS control region, this option is ignored and control region startup fails. If the Logger is down when you try to start the IMS control region, this option is ignored and the control region startup fails.	Y	Valid values: Y. In an online environment, all update transactions and online batch jobs abend. In a batch DL/I environment, the batch jobs abend. N . In an online environment, only the transactions and online batch jobs that update registered source segments abend. In a batch DL/I environment, only the batch DL/I jobs that update registered source segments abend.
LGWAITTO	The maximum number of seconds that an ECCR waits to write change data records to the PowerExchange Logger queue when CCERR=CONT is specified. Define this option only under the following conditions: ECCR requests to write change data to the PowerExchange Logger queue are blocked because the queue has become full. The queue might become full, for example, because the PowerExchange Logger does not have enough resources to offload data from its active log data sets. You prefer for user applications to continue without error, even though some change data loss might occur when the timeout interval is exceeded. You confirm with Informatica Global Customer Support that this option is appropriate for use in your environment. If you use the VSAM/CICS ECCR, this option can be particularly useful. With this ECCR, a blocked queue can cause the CICS region to stop, which potentially affects many users. If you enter a non-zero value, PowerExchange issues message PWXEDM172895I at ECCR initialization to indicate that this timeout is in effect. When the timeout interval elapses, PowerExchange issues PWXEDM172895I again and discards change records as long as the timeout persists. When the PowerExchange Logger resumes reading records from its queue, PowerExchange issues message PWXEDM172834I.	0 This default value disables the LGWAITTO timeout.	A valid value: Is a number in the range of 30 to 21600 seconds. Is rounded to the nearest 10-second multiple, if not a multiple of 10.
LOGGER	Specifies the name of the default PowerExchange Logger. You can specify only one instance of the PowerExchange Logger with this parameter. Consequently, if you use multiple PowerExchange Loggers you must have a separate EDMSDIR for each instance of the PowerExchange Logger. Because you cannot rename EDMSDIR, you must allocate a separate user library, your .USERLIB, for each copy of EDMSDIR.	EDML	A valid name has the following characteristics: Consists of four characters, beginning with a letter, #, @, or $. Does not conflict with an existing MVS subsystem Is not the same as the AGENTID value.
LOGRGRP	Indicates whether the PowerExchange Logger is configured for Post-Log Merge.	N	Valid values: Y . Uses the Post-Log Merge configuration. N . Does not use the Post-Log Merge feature.
SYSOUT	The default SYSOUT class that any dynamically allocated SYSOUT data sets use.		This value can be any valid SYSOUT class.
TIME	The time format that the PowerExchange CDC components display, for example, in messages.	(24,:)	In the time format, the first value indicates the hours format: 24 . A 24-hour format, such as military time. 12 . A 12-hour format. The second value is the separator to use in the time. You can use any character. Default is a colon (:).

Rename Saved Search

Table of Contents

CDC Guide for z/OS

CDC Guide for z/OS

EDMSDIR Options Module

EDMSDIR Options Module