LOG/NLOG Dialog Logging

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.