Controlling the LMSCONV run

The following section describes the facilities provided by LMSCONV for controlling the LMSCONV run.

Controlling log output

The LMSCONV log contains everything output by LMSCONV, such as the result of the statements, their execution or abnormal termination, the assigned I/O libraries as well as lists generated, for example, when members are listed or compared.

The log may be written to the system file SYSOUT, SYSLST or to a library member. The output medium is specified by means of the TEXT-OUTPUT= operand of the MODIFY-LOGGING-PARAMETERS statement.

If the log is written to a member, LMSCONV normally creates a P-type member.

Error messages are always output.

The following table shows which operands in which statements control output of the log:

Statement	Operand	Function
MODIFY-LOGGING-PARAMETERS	LOGGING	Specifies whether or not positive acknowledgments are logged
	TEXT-OUTPUT	Specifies the output medium for the log
	OUTPUT-LAYOUT	Specifies the output format for the log
	LINES-PER-PAGE	Specifies the number of lines on a log page
	LINE-SIZE	Specifies the length of a line
	EXTRA-FORM-FEED	Controls the form feed of the log for member change
	HEADER-LINES	Specifies whether headers are output
SHOW-ELEMENT	OUTPUT-FORM	Specifies the record layout when listing member contents.
	TEXT-/ MODULE-/ PHASE-/ LLM- INFORMATION	Specifies the output scope when listing the member contents.
SHOW-ELEMENT-ATTRIBUTES	SORT	Specifies the sort mode for the contents
	LAYOUT	Specifies the log format of the contents
	INFORMATION	Specifies the log scope of the contents.
	TEXT-OUTPUT	Controls the log output

Table 6: Log output control

Positive and negative acknowledgments

If the operand LOGGING=*MAXIMUM is set in the LMSCONV statement MODIFY-LOGGING-PARAMETERS, the execution of each LMSCONV statement affecting a member will be logged. If the statement is executed successfully, LMSCONV will issue a positive acknowledgment.

If the statement cannot be executed, LMSCONV will log a negative acknowledgment and, if applicable, a corresponding LMSCONV error message.

All success and failure messages have the following format:

[NO] statement mem[word mem][cause]

Function

NO	The statement has not been executed
statement	Statement name
mem	Member designation or file name (in ADD-ELEMENT and EXTRACT-ELEMENT)
word	Keyword: AS, INTO, WITH
cause	Result: EXISTING, REPLACED, etc.

Controlling screen overflow

LMSCONV does not itself perform any screen overflow control. BS2000 handles this function. LMSCONV outputs can therefore only be aborted if the program interrupt key (K2) key is pressed and /INFORM-PROGRAM is subsequently entered and sent, see "MODIFY-DEFAULTS - Modify defaults".

Error handling in interactive and procedure modes

LMSCONV differentiates between interactive mode and procedure mode.

• Interactive mode

  In interactive mode, following output of the error message, the prompt // appears, requesting entry of the next statement.

• Procedure mode

  Users can themselves specify what errors are to trigger LMSCONV’s spin-off mechanism. They control this by setting the MAX-ERROR-WEIGHT operand (see the MODIFY-DEFAULTS statement). According to the setting of this operand, serious errors cause LMSCONV to branch to the next STEP or END statement. If a serious error occurs during the processing of substatements, the associated main statement is aborted and the spin-off mechanism is activated. This means that a main statement is always expected to follow STEP. If the spin-off mechanism is activated in LMSCONV without a STEP having been read, LMSCONV then terminates with TERM UNIT=STEP,MODE=ABNORMAL.

Interrupting the LMSCONV run

The user can interrupt the LMSCONV run by pressing one of the program interrupt keys (e.g. K2).

Continuation of the LMSCONV run can be controlled by /INFORM-PROGRAM, which may optionally be supplied with an input text. This input text is subsequently interpreted by LMSCONV during interrupt handling. The current function is informed of the type of termination and terminates in the desired way. The possible inputs are described under the DIALOG-CONTROL operand of the MODIFY-DEFAULTS statement (see "MODIFY-DEFAULTS - Modify defaults").

Termination of LMSCONV due to errors

Error handling is also controlled by means of the STXIT routine.

In the case of program termination, connection failure, or specification of /START-EXECUTABLE-PROGRAM, /LOAD-EXECUTABLE-PROGRAM, /CANCEL-JOB, /LOGOFF, /CANCEL-PROGRAM, /ABEND, /EXIT-JOB, a check is performed to ensure that the libraries remain consistent.

The following applies to all program termination conditions:

• All STXIT routines in LMSCONV are deactivated in order to prevent any incorrect continuation of processing by /INFORM-PROGRAM.

• LMSCONV simulates an END statement. This causes all open libraries to be closed.