LOG Log message traffic

In a CFS connection, the user can extract all input and output messages to a file. Logging is started by entering the command LOG. BS2000 dialog sessions, as well as UTM and DCAM sessions can be logged.

Starting Dialog Logging

LOG {file | [lib] ([t/] element) | STD | B | BR | C} [, opt]

file Name of the file to which all input/output messages should be written. The LOG file will always be created in the CFS basic task.

lib ( [t/] element)  Name of the PLAM library and element to which the input/output messages should be written. If not otherwise specified, the element type will be taken as S (Source).

([t/] element)  If no library name is used, the CFS-userlib will be substituted. For a full description of the userlib, see Chapter 21.

STD CFS will use a standard name for the LOG file: CFS.LOG.yymmdd. hhmmss.tsn.

B Break. Logging will be suspended until the command LOG C (LOG Continue, see below) is entered.

BR Same as LOG B (see above), except that before suspending the logging a record is created in the LOG file containing a 'STEP BREAK'. If the dialog is later replayed (RES), the STEP BREAK record has the effect of suspending the replay until a RES C (RES Continue) command is entered. This allows the user to insert steps which were not contained in the original LOG file.

C Continue. The suspended process of logging input/output messages is continued. To interrupt the logging, see above. (B/BR parameter).

opt The type and scope of the message logging can be specified using this optional parameter.

I Input. Only the Input messages are captured (Standard).

S Special. Only the input messages are captured. (Difference to I: see Note 3).

O Output. Only the Output messages are captured.

IO Both. Input and Output messages are captured.

M preModify. With formatted screens, the contents of all input fields are saved, including those not modified by the user.

The M-option can be used in conjunction with the I-, S-, or IO-option, separated by a comma.

Notes:

In a connection the LOG command can be used in both Line Mode as well as Mask Mode. With a mask, the LOG command should be entered in the first overwriteable field. An exception to this is in EDT, where the LOG command should be entered in the 24th line (command line). No other field may be modified in the same mask.

With screen masks whose first overwriteable field is too short to hold the full LOG command, the screen can be cleared before entering the LOG command with the LSP key.

When replaying a dialog captured with the S option, the generated input steps cannot be displayed on the screen. When replaying a dialog captured with the I option (Standard option), both input and output steps will be displayed on the screen. The S option has the effect of capturing pure input to the LOG file without any additional information for the internal use of CFS.

The M option (preModify) only has effect when capturing Mask or Formatted input (SAW: "read modified fields"). The M option causes the contents of all overwriteable fields, including those not modified by the user, to be written to the LOG file. The M option has no effect in Line Mode entry.

Example: EDT session in F mode. If a screen is made overwriteable by pressing the F2 key, the contents of all displayed data lines will be captured to the LOG file. The effect is thus the same as if the user had modified all data lines.

The commands LOG and NLOG will still take effect in a DO procedure if the statements /WR-T 'LOG...', or /WR-T 'NLOG' respectively are displayed on the screen as comment.

By setting an option, the system administrator can generate CFS such that all commands destined for the Connection Handler must be preceded by the escape symbol. The activating and deactivating of Logging will in this case be done by ^LOG and ^NLOG respectively. To check if the ^ option is set, display the CRD mask (CRD command).

LOG files may be stored as Type S elements in PLAM libraries. The RES command is likewise applicable to Type S PLAM library elements (RES lib(element) ).