Reference Manual

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

Back Next

PowerExchange Alternative Log File Configuration Styles on z/OS

To configure PowerExchange to use alternative log files, define the TRACING statement in the DBMOVER configuration file. When alternative logging is enabled, PowerExchange writes runtime messages from PowerExchange components, programs, and commands to a set of alternative log files that are used on a rotating basis.

By default, PowerExchange dynamically allocates five alternative log files. On z/OS only, you can add DTLLOGnn DD statements in the JCL for a PowerExchange component that logs messages to alternative log data sets if you do not want to use the TRACING statement to dynamically allocate the alternative log data sets. Manual allocation by the DD statements overrides dynamic allocation.

To send the message output to a JES2 or JES3 SYSOUT file rather than to a data set that you specify, specify 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. If you use dynamic allocation, PowerExchange dynamically creates a set of log data sets in a separate directory for each PowerExchange process. Alternatively, you can specify a DD statement that points to the current GDG(0). If you set APPEND=Y in the TRACING statement, PowerExchange appends messages to the end of the current GDG.

You can configure alternative logging by using one of the following styles:

Style 1: Dynamic allocation without DTLLOGnn DD statements
. Disk data sets are used on a rotating basis. Specify the TRACING statement but do not specify //DTLLOG01 DD statements in the JCL. Informatica recommends this style because it has the following benefits:

Fast logging

Reduced use of spool resources for long-running jobs

Ability to retrieve messages on Windows by using the PWXUMSGS utility

Dynamic allocation of data sets if they do not already exist

Style 2: Single DTLLOG01 DD statement that specifies a GDG
. GDG data sets are accessed through a JCL //DTLLOG01 DD statement. To use a GDG for alternative logging on

z/OS

, complete the following actions:

Specify

GDG(0)

and DISP=SHR in a single DTLLOG01 DD statement in the PowerExchange Listener JCL.

Allocate and create at least one generation of the GDG before starting the PowerExchange Listener.

If you use

GDG(0)

, you can specify

APPEND=Y

in the TRACING statement to enable PowerExchange to resume logging messages to the current generation. You can also specify

VIEW=Y

in the TRACING statement to view log records in the GDG while the PowerExchange Listener task is active. If you specify

APPEND=N

, PowerExchange creates a new generation when the PowerExchange Listener starts.

PowerExchange does not limit the number of GDG generations. The FILENUM parameter in the TRACING statement is ignored. Instead, the LIMIT value in the GDG definition limits the number of generations. When this limit is reached, the operating system automatically removes the oldest generation from the GDG and deletes it if the SCRATCH parameter is defined for the GDG.

You cannot retrieve messages through the PWXUMSGS utility with this style.

Style 3: DTLLOGnn DD statements with different data set names
.

Disk data sets are used on a rotating basis. PowerExchange ignores the following parameters in the TRACING statement:

The PFX parameter, even though it's a required parameter .

The FILENUM parameter, for all jobs that have DTLLOGnn DD statements in their JCL.

Specify the TRACING statement in the DBMOVER configuration file and the DD statements DTLLOG01 DD, DTLLOG02 DD, and so on in the JCL for PowerExchange jobs or started tasks.

To switch to another alternative log file when the current one becomes full, PowerExchange uses the same rotating algorithm as it uses for dynamically allocated log data sets. Although this style has benefits similar to those of the first dynamic allocation style, Informatica does not recommend it because you must pre-allocate the data sets to avoid JCL errors.

You must specify the PFX parameter on the TRACING statement, but PowerExchange ignores it. PowerExchange also ignores the FILENUM parameter for all jobs that include the DTLLOGnn DD statements.

Style 4: Single DTLLOG01 DD statement with SYSOUT=*
. The JES spool file is accessed through the JCL //DTLLOG01 DD SYSOUT=* statement. To simplify configuration and make finding message output for a specific job execution easier, Informatica recommends that you define a single DTLLOG01 DD statement that points to SYSOUT=* in the JCL for PowerExchange jobs and started tasks that issue messages. When you run one of these jobs or tasks, all of its message output is written to a single SYSOUT data set. In this case, PowerExchange does not use the PFX, APPEND, FILENUM, and VIEW parameters from the TRACING statement. However, if you have other jobs and started tasks that use dynamic allocation, PowerExchange honors the PFX, APPEND, FILENUM, and VIEW parameters for these jobs and tasks.

This style provides improved performance because of reduced open and close activity. However, this style is not recommended because it can result in excessive consumption of spool resources for long-running jobs.

Rename Saved Search

Table of Contents

Reference Manual

Reference Manual

PowerExchange Alternative Log File Configuration Styles on z/OS

PowerExchange Alternative Log File Configuration Styles on z/OS