Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Permissibility of logging

&pagelevel(5)&pagelevel

Whether logging is allowed is controlled in part by the protection mechanisms of the data management system. The procedure can be assigned a read password. (Read protection can be canceled only if the appropriate password is specified.) BASIC-ACL can be used to grant execution and read authorization separately.

Whether logging is allowed is also controlled within the procedure with the SET-PROCEDURE-OPTIONS and MODIFY-PROCEDURE-OPTIONS commands, in each case by means of the LOGGING-ALLOWED operand. A distinction is made between logging commands and logging data.

If logging is to be prohibited for commands and/or data from the beginning of procedure execution, the procedure must begin with the SET-PROCEDURE-OPTIONS command. There, the operand LOGGING-ALLOWED = *PARAMETERS(...) must be specified with CMD = *NO and/or DATA = *NO.

If command and/or data logging is to be prohibited for only part of the procedure, the MODIFY-PROCEDURE-OPTIONS command must be called in the procedure body and the corresponding value specified in the operand LOGGING-ALLOWED = *PARAMETERS(...). The (*YES/*NO) setting is retained until it is changed by another MODIFY-PROCEDURE-OPTIONS command.

If logging is prohibited for parts of the procedure, this setting cannot be changed “externally”, i.e. it cannot be changed using procedure call commands or interactive commands.

Logging should be prohibited, for example, if the caller is not supposed to “see” certain commands or data.