Trace management concepts

About trace management

ATM trace management is comprised of two stages:

  • Information collection, or trace acquisition in Transfer CFT, with records in one or more trace files
  • Examination of this information, outside Transfer CFT, at a later date or time

Only the information collection stage is covered in this section. Examination of information, which Transfer CFT support staff carry out, is performed using trace files.

The following paragraphs describe:

  • How to start trace acquisition, either before starting up Transfer CFT or during operations
  • How to synchronize data collection with application events linked to transfers

Collecting information

The implementation of traces in Transfer CFT involves three types of operations:

  • Configuring the communication medium
  • Defining the trace files
  • Controlling collection: activation/shutdown, closing files, shutdown of the process

Configuring the ATM communication medium

The CONFIG command is required to:

  • Initially define the communication medium with which the utility will function
  • Redefine this medium during operations, if necessary

This communication medium can be the same as that defined for CFTUTIL.

Depending on the systems it can be either a file or a mailbox.

Defining trace files

One or more trace acquisition processes can be activated in Transfer CFT, to supply one or more trace files.

To do this, the description of the trace file must be given to Transfer CFT, either:

  • In the CFTUTIL parameter settings, using a CFTTRACE command which is taken into account when Transfer CFT is started
  • Or dynamically, using a SETTRC command, sent to the Transfer CFT communication medium during its operations. The SETTRC command can be made before Transfer CFT is started, if the communication medium is a file

The word process is not used here as a synonym for task. There is at most one task dedicated to trace acquisition in Transfer CFT.
In general, when a CFTTRACE or SETTRC command is taken into account, this is accompanied by the physical creation and initialization of the corresponding trace file. In some environments, especially on mainframe platforms, this operation must be carried out in advance, using a TRCFILE TYPE=TRACE command.

This command is also used to define a direct file.

For more information, refer to the specific documentation or the examples supplied with the Transfer CFT products.

The CFTTRACE parameter settings command initializes a trace acquisition process and provides it with operating parameters.

Depending on the value of this command’s START parameter, trace acquisition starts:

  • As soon as Transfer CFT is started
  • When a start trace command (STARTTRC) is entered

During Transfer CFT operations, only the CFTTRACE command referenced by the CFTPARM command’s TRACE parameter is taken into account:

CFTPARM     ..., TRACE= identifier, ....
CFTTRACE     ID= identifier, ...

Conversely, during Transfer CFT operations, several SETTRC commands can be taken into account. However, after a SETTRC command, a STARTTRC command must always be entered. This command provides Transfer CFT with the additional parameters to control and actually trigger trace acquisition.

Note The CFTTRACE and SETTRC commands provide Transfer CFT with operating and trace acquisition parameters. The term ‘‘trace vector" will therefore be used to represent these items overall in the rest of the document.

Filtering traces by partner

This function enables you to filter FPDU protocol traces by partner.

Example

CFTTRACE STARTTRC ID=ID,TID=TID,PTRACE=16,FILTER=Part

The command to start a trace FPDU (PTRACE=16) only applies to thePart partner. When you start a Trace, a new message is written in the LOG File with a CFTT57 message:

CFTT92I IDTU=&idtu CTX=&ctx IDT=&idt 

Related Links