Log parameters

About the CFTLOG object

A CFTLOG object defines the Transfer CFT log file declarations. Transfer CFT records the significant events occurring during a transfer, such as:

  • Session start
  • Transfer start
  • Restart points
  • Transfer end
  • Session close
  • Incidents

Transfer CFT uses a primary and an alternate file. Files are switched: when the current file is full, when the number of records exceeds the limit set in the object, or at the time indicated in the switch field.

Transfer CFT then executes the procedure defined in the exec field.

The CFTLOG object can be permanently deleted from the configuration. Once the CFTLOG is deactivated, it as well as all log filters appear grey in the tree structure displayed in the left pane. For more information refer to Deleting the CFTLOG object.

For a given PARM, there is one associated CFTLOG for that PARM.

The LOG parameter value of the CFTPARM command must correspond to the value of the ID parameter for this command.

Logging transfer details

When a transfer occurs, a message is created that describes the transfer event. This message is:

  • Written in a log
  • Sent to an operator via the Transfer CFT screen, an operator console, or to you, depending on the system. The number of message sent to this operator is defined by the OPERMSG parameter of the CFTLOG object

You can also redirect the transfer messages to the console of another user. To do this, declare the following in the CFTSEND object:

  • User name in the NOTIFY parameter
  • Category of the messages to be redirected in the USERMSG parameter

When you activate the CFTLOG object, Transfer CFT records transfer events messages in the LOG file.

Transfer CFT closes this file in the following cases, when:

  • Transfer CFT is shut down via the SHUT command
  • MAXREC the maximum number of records is reached
  • A SWITCH command is sent as defined in the CFTLOG object [ Switching files]

The transfer event messages are written in an alternate ALOG file, if any. At the next scheduled time or action, the ALOG file is closed and Transfer CFT returns to recording in the LOG file. The LOG file must be empty for Transfer CFT to return to recording in this file.

Switching log files

A file can be switched to another by means of one of 5 events:

  • the daily schedule set by the SWITCH parameter
  • SWITCH TYPE=LOG operating command
  • the number of records written in the current log file exceeds the limit set by the MAXREC parameter or, according to the OS possibilities, the file is full
  • Transfer CFT is shut down via the SHUT command
  • Transfer CFT is activated

The Transfer CFT cannot open a log file which is not empty on start up. Transfer CFT automatically attempts to switch to the alternate log file. It is important for the procedure associated with the switch to regenerate an empty file following the processing of the log file.

Switching leads to the execution of the procedure described by the EXEC parameter of this command. This procedure can typically save a file, create a new empty file, with the same name, and print out the saved file as required.

Log files must be created by operations before Transfer CFT is activated (CFTFILE TYPE = LOG command).



Related Links