When alternative logging is enabled, the DTLLOG data set contains only the messages up to the point when the alternative logging subtask initializes. Usually, this information consists of only the DBMOVER statements. If you enabled traces with the TRACE statement in the DBMOVER configuration member, the data set also includes diagnostic trace information.

When alternative logging is

not

enabled, the DTLLOG data set is the primary message log data set for run-time messages from the PowerExchange programs and components, including the PowerExchange Agent, PowerExchange Condense, PowerExchange Listener, ECCRs, and PowerExchange utilities.

If you set the CAPT_STATS parameter to Y for the Adabas, Datacom, IDMS, or IMS log-based ECCR, the data set also contains ECCR capture statistics by capture registration.

All message lines begin with a time stamp.

When alternative logging is enabled, PowerExchange sends run-time messages from PowerExchange components, programs, and commands to a set of DTLLOG

nn

data sets that are used in a rotating manner. If you set the CAPT_STATS parameter to Y for the Adabas, Datacom, IDMS, or IMS log-based ECCR, the DTLLOG

nn

log data sets contain ECCR capture statistics messages by capture registration. The DTLLOG

nn

data sets do not include trace information.

The data set names end with a sequential number

nn

. When a log file reaches its specified size, PowerExchange switches to the next log file and begins overwriting any data in that file. Informatica strongly recommends that you use alternative logging on z/OS to help improve logging performance and be able to customize the amount of data that is logged for long-running jobs.

To allocate the DTLLOG

nn

data sets, you can either add DTLLOG

nn

DD statements in the JCL for a PowerExchange component that logs messages to these data sets or configure the TRACING statement to dynamically allocate the data sets. To send the output to a JES2 or JES3 SYSOUT file rather than a data set that you specify, enter a single DLTLLOG01 DD statement in the JCL that specifies the SYSOUT parameter. By using SYSOUT, you can keep the output from a single PowerExchange Listener execution with the rest of the job output. With dynamic allocation, PowerExchange dynamically creates a set of log data sets in a separate directory for each PowerExchange process. The generated data set names vary by component type.

If you use an extended sequential data set as the DTLLOG

nn

data set format, PowerExchange writes only one message on each track. If you use a normal sequential data set, PowerExchange writes one message to each data block.

DTLOUT is a dynamically allocated data set that usually contains normal output from PowerExchange programs. When alternative logging is disabled, this data set contains most of the same run-time messages as in the DTLLOG data sets but without the time stamps at the beginning of each message line.

If you set the CAPT_STATS parameter to Y for the Adabas, Datacom, IDMS, or IMS log-based ECCR, the DTLOUT data set also contains ECCR capture statistics messages by capture registration.

If alternative logging is enabled and you use PowerExchange Condense, the DTLOUT data set contains messages only if condense file allocation errors occurred.

The EDMMSG data set includes Logger messages that are generated when CDC workflows run. If you use PowerExchange Condense, this data set also includes messages that indicate the PowerExchange Logger and PowerExchange Agent to which a Condense job attaches and the starting point at which to begin, which is passed to the Logger.