TRACING=(PFX=
prefix
       [,APPEND={N|
Y}]
       [,BUFFERS={
number_of_buffers|
100}]
       [,FILENUM={
number_of_files|
5}]
       [,FLUSH={
flush_interval|
99}]
       [,RECLEN={
record_length|
80}]
       [,SIZE={
log_size|
100}]
       [,VIEW={
N|Y}]
)

PFX=

prefix

Required. Specifies the prefix for the alternative log file names.

PowerExchange uses the following system-based rules to create the alternative log file names:

i5/OS

PowerExchange uses the PFX value to create the member names of the log files in the PowerExchange data library. The generated log file names vary based on whether the PowerExchange Listener, PowerExchange Condense, or other PowerExchange jobs create the files.

The PowerExchange Listener uses the following file naming convention:

datalib/P
listener_port(
prefixnnn)

PowerExchange Condense and other PowerExchange jobs use the following file naming convention:

datalib/JOB
job_number(
prefixnnn)

These naming conventions include the following variables:

datalib
is the PowerExchange data library name specified during PowerExchange installation.
listener_port
is the PowerExchange Listener port number.
job_number
is the
i5/OS
job number for the tracing subtask, DTLTRTSK, that runs under PowerExchange Condense or other PowerExchange jobs.
prefixnnn
is the PFX parameter value with an appended sequential number from 001 through 999.

For example, a PowerExchange Listener that has a listener port number of 2480, a PFX value of PWXLOG, and a FILENUM value of 3 creates the following log files:

datalib/P02480(PWXLOG001) 
datalib/P02480(PWXLOG002) 
datalib/P02480(PWXLOG003)

Maximum length for the PFX value is seven characters.

Linux, UNIX, and Windows

PowerExchange uses the PFX value as the subdirectory name in which to place the log files. PowerExchange uses the LOGPATH statement in the dbmover.cfg file to determine the directory in which to place this log subdirectory.

The generated log file names vary based on whether the PowerExchange Listener, PowerExchange Condense, or other PowerExchange tasks create the files.

The PowerExchange Listener uses the following file-naming convention:

Linux and UNIX:

logpath/
prefix/DTLLST1.p
listener_port.n
nnn.log

Windows Listener Service:

logpath\
prefix\DTLLSTNT.p
listener_port.n
nnn.log

Windows Listener:

logpath\
prefix\DTLLST1.p
listener_port.n
nnn.log

The PowerExchange Logger for Linux, UNIX, and Windows uses the following file-naming convention:

Linux and UNIX:

logpath/
prefix/PWXCCL.t
yyyymmddhhmmss.p
pid.n
nnn.log

Windows:

logpath\
prefix\PWXCCL.t
yyyymmddhhmmss.p
pid.n
nnn.log

For other tasks, PowerExchange uses the following file-naming convention:

Linux and UNIX:

logpath/
prefix/
module.t
yyyymmddhhmmss.p
pid.n
nnn.log

Windows:

logpath\
prefix\
module.t
yyyymmddhhmmss.p
pid.n
nnn.log

The variables represent the following values:

logpath
is the value of the LOGPATH statement in the dbmover configuration file.
prefix
is the PFX parameter value.
module
is the name of the PowerExchange module that is running, such as DTLURDMO for that utility or DTLODBCDRVR for PowerCenter operations.
listener_port
is the PowerExchange Listener port number.
yyyymmddhhmmss
is the time stamp when the file was created.
pid
is the process ID of the PowerExchange task.
nnn
is a sequential number from 001 through 999.

For example, a PowerExchange Listener that runs on UNIX with a port number of 2480, a PFX value of PWXLOG, and a FILENUM value of 3 creates the following log files:

logpath/PWXLOG/DTLLST1.p02480.n001.log 
logpath/PWXLOG/DTLLST1.p02480.n002.log 
logpath/PWXLOG/DTLLST1.p02480.n003.log

Maximum length for the PFX value is 210 characters.

z/OS

PowerExchange uses the PFX value as the high-level qualifier or qualifiers (HLQ) for dynamically allocated alternative log data sets. These data sets are sequential data sets. Alternatively, you can specify DTLLOG

nn

DD statements in the JCL for a PowerExchange task to allocate the alternative log data sets. By default, PowerExchange uses dynamically allocated alternative log data sets.

If you use a DTLLOG

nn

DD statement that allocates an extended sequential data set, PowerExchange writes only one message on each track. If the DD statement allocates a normal sequential data set, PowerExchange writes one message to each data block.

Do not use DFSMS compression for alternative log data sets.

For dynamically allocated log data sets, the generated data set names vary based on whether the PowerExchange Listener or other PowerExchange batch jobs or started tasks create the files.

The PowerExchange Listener uses the following file naming convention:

prefix.
sysid.P
listener_port.N
nnn

All other PowerExchange batch jobs and started tasks use the following file naming convention:

prefix.
job_name.
job_number.
sysid.N
nnn

The variables represent the following values:

prefix
is the high-level qualifier or qualifiers that you specify in the PFX parameter. Maximum length of the entire prefix is 16 characters.
sysid
is the system ID of the
z/OS
system on which the batch job or started task runs.
listener_port
is the PowerExchange Listener port number.
job_name
is the job name of the batch job or started task.
job_number
is the JES job number, which begins with JOB for batch jobs and STC for started tasks.
nnn
is a generated sequential number from 001 through 999.

For example, a PowerExchange Listener that runs on the MVS1 system with a port number of 2480, a PFX value of PWXLOG, and a FILENUM value of 3 creates the following log files:

PWXLOG.MVS1.P02480.N001
PWXLOG.MVS1.P02480.N002
PWXLOG.MVS1.P02480.N003

APPEND={N|

Y

}

Optional. Controls how PowerExchange uses the message log files when the PowerExchange component that issues messages is restarted.

Options are:

N
. PowerExchange opens a new log file or overwrites the oldest log file as the log file.
For example, if you set
FILENUM=3
to use three dynamically allocated log files, when the PowerExchange Listener starts, it tries to open log file 1, 2, and 3, in that order. Then, PowerExchange completes one of the following actions:
If one or more of the dynamically allocated log files do not exist, PowerExchange uses the first nonexistent log file as the initial log file. For example, if log files 1 and 2 exist but log file 3 does not exist, PowerExchange uses log file 3 as the initial log file. If no log files exist, PowerExchange uses log file 1 as the initial log file.
If all three log files exist, PowerExchange uses the oldest log file as the initial log file, completely overwriting it.
If you use a GDG on
z/OS
for alternative logging, PowerExchange creates a new generation when the PowerExchange Listener starts.
Y
. PowerExchange opens the most recent log file, if one exists, and appends log messages to the end of it. If no log files exist, PowerExchange opens a new log file.
For example, if you set
FILENUM=3
to use three log files, when the PowerExchange Listener starts, it tries to open log file 1, 2, and 3, in that order. Then, PowerExchange completes one of the following actions:
If one or more log files exist, PowerExchange opens the most recent log file and appends log messages to the end of it.
If you use a GDG for alternative logging on z/OS and specify
GDG(0)
in the DTLLOG
nn
DD statement of the PowerExchange Listener JCL, PowerExchange appends messages to the end of the current generation. If you do not use GDG(0), PowerExchange ignores this parameter.
If no log files exist, PowerExchange opens a new log file 1 and uses it as the log file.

Default is Y.

BUFFERS={

number_of_buffers

|

100

}

Optional. Specifies the number of buffers that PowerExchange allocates to receive message and trace information from PowerExchange subtasks. If the buffer space is full, the PowerExchange subtasks that generate message and trace information wait until buffer space is available. PowerExchange programs use this buffer space internally.

Valid values are 5 through 9999. Default is 100.

Specify this parameter only at the direction of Informatica Global Customer Support.

FILENUM={

number_of_files

|

5

}

Optional. Specifies the number of alternative log files that PowerExchange creates and uses when the log files are dynamically allocated. When a log file becomes full, PowerExchange switches to the oldest alternative log file and overwrites it.

Valid values are from 1 through 99. Default is 5.

On z/OS, the FILENUM parameter is ignored if you use a GDG for alternative logging or if you specify DTLLOG

nn

DD statements in the JCL for a PowerExchange component that issues DTLLOG messages. For a GDG, the parameter is ignored regardless of whether you specify

GDG(0)

or

GDG(+1)

in the DTLLOG

nn

DD statement in the JCL.

FLUSH={

flush_interval

|

99

}

Optional. Specifies the number of log records that PowerExchange collects before it flushes them to the log file on disk. PowerExchange must periodically flush log records to enable PowerExchange to recover from out-of-space conditions. Low flush values result in more

I/O

activity to the log file.

Valid values are 1 through 99. Default is 99.

RECLEN={

record_length

|

80

}

Optional. Specifies the record length that PowerExchange uses to write log records to the log file. PowerExchange writes the log record on multiple lines if the length of the message exceeds the record length.

Valid values are 80 through 255. Default is 80.

If you do not specify the RECLEN parameter and if you enter a value greater than 80 in the LOG_LINE_LIMIT statement, PowerExchange uses the LOG_LINE_LIMIT value as the RECLEN value.

SIZE={

log_size

|

100

}

Optional. Specifies the approximate amount of log data, in megabytes, that PowerExchange writes to an alternative log file. After PowerExchange reaches this value, it closes the current log file and opens the next log file to continue writing log records.

Valid values are 1 through 2048. Default is 100.

On z/OS, if a manually allocated data set is larger than the SIZE value, PowerExchange limits the amount of log data that it writes to the data set to the SIZE value. If the data set is smaller than the SIZE value, the data set size limits the amount of log data that PowerExchange can write to it. When an out-of-space condition occurs, PowerExchange switches to the next manually allocated message data set.

VIEW={

N

|Y}

Optional. Controls whether PowerExchange periodically closes and reopens the current log file when the FLUSH interval expires. You can specify this parameter on all operating systems, but it is most useful on

z/OS

. On

z/OS

, you cannot view the alternative message log records until the log data set is closed. On operating systems other than z/OS, you can view the log records after PowerExchange flushes the log records to disk based on the FLUSH interval. The current log file does not need to be closed for you to view the log records.

Options are:

N
. PowerExchange does not periodically close and reopen the current log file.
Y
. PowerExchange periodically closes and reopens the current log file.
On z/OS, Informatica recommends that you specify VIEW=Y to periodically close and reopen the alternative log data set so that you can view the log records.
If you specify VIEW=Y on z/OS, the following considerations apply:
If you use a GDG for alternative logging on
z/OS
, you must specify
GDG(0)
and DISP=SHR in a single DTLLOG
nn
DD statement in the PowerExchange Listener JCL. Also, allocate and create at least one generation of the GDG data set before starting the PowerExchange Listener.
If you use third-party products that manipulate data set allocations, these products might interfere with
VIEW=Y
processing. For example, the products might change the SYSDSN ENQ to EXCLUSIVE mode, which prevents you from viewing the data set.
The performance of the PowerExchange job that writes data to the alternative log data set might be degraded because of frequent data set open and close requests. Use the default value of 99 for the FLUSH parameter to minimize performance degradation.

Default is N.

Use alternative logging to improve logging performance and to customize the amount of data logged for long-running jobs, such as a PowerExchange Logger for Linux, UNIX, and Windows process that runs in continuous mode.
When dynamic alternative logging is enabled, PowerExchange creates a set of alternative log files for each PowerExchange process in a separate directory.
You can specify the location, the number of log files, and the log file size in megabytes. When a log file reaches the specified size, PowerExchange switches to the next log file and begins overwriting any data in that file.
If you define the TRACING statement, also define the LOGPATH statement to specify a directory for the alternative log files on a Linux, UNIX, or Windows system.
PowerExchange dynamically allocates the alternative log data sets unless you define DTLLOG
nn
DD statements in the JCL for a PowerExchange job or started task.
On z/OS, Informatica recommends that you specify SYSOUT=* in a DTLLOG01 DD statement that you use in the JCL for all PowerExchange jobs and started tasks that issue messages, for example:
//DTLLOG01 DD SYSOUT=*
This strategy simplifies configuration because you define only one DTLLOG01 DD statement with a single SYSOUT option. Also, this strategy makes finding message output for a particular execution of a job or task easier because PowerExchange writes all of the message output to a single SYSOUT data set, which is available with the other job output.
If you use a GDG on
z/OS
for the alternative logging, specify
GDG(0)
in the DTLLOG
nn
DD statement of the PowerExchange Listener JCL. For example:
 DTLLOG01 DD   DSN=USER1.V901.TRCGDG(0),DISP=SHR
By using
GDG(0)
, you can use
APPEND=Y
to resume logging messages to the current generation. Also, you can use
VIEW=Y
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.
If you use
GDG(+1)
instead, PowerExchange ignores the APPEND and VIEW parameters on the TRACING statement and creates a new generation whenever the PowerExchange Listener starts.
Also, when using a GDG, allocate and create at least one generation of the GDG before starting the PowerExchange Listener.
On z/OS, if you use a GDG for alternative logging or specify a DTLLOG01 DD statement in the JCL for a PowerExchange job or started task, the FILENUM parameter is ignored.