Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Restrictions

&pagelevel(4)&pagelevel

In the following cases the user cannot influence logging:

  • Logging has been prohibited in the command definition. Whether and how logging takes place depends on the executing module.

  • The command/statement contains operands defined as SECRET (e.g. passwords). If the entry for a secret operand can be uniquely assigned to that operand, “P” is inserted as the operand value in the log. If no unique assignment is possible, only the command/statement name appears in the log. “No unique assignment” means that the command/statement name is recognized but subsequent operands contain a syntax error.

  • The command/statement name cannot be recognized. In this case, only the errored command/statement name appears in the log because the entry may contain details of secret operands.

  • Procedures cannot be logged unless this has been permitted within the procedure. An additional restriction for S procedures is that they are not logged unless the caller also possesses an authorization for read access to the procedure file.