KDCMSAT - modify SAT logging

The conditions for the SAT audit are defined in the UTM generation. You specify the event classes from which events are to be logged, and you define the processing results (successful or failed execution) for user-specific, TAC-specific, or event-specific logging. The UTM SAT administrator can modify these generated values using KDCMSAT:

• Define the logging values with a separate statement for EVENT, TAC or USER.

• Activate or deactivate logging.

  In the UTM generation, you can preset the SAT logging values without activating SAT logging itself. When required, you can then switch on logging during operation with KDCMSAT SAT=ON. Logging can also be switched on if no values were preset in the UTM generation. In this case, you can specify the logging values with KDCMSAT.

• Query the syntax of this command.

The modifications for event-driven logging (SATSEL ...,EVENT=) and the switching on and off (SAT=ON/OFF) only apply until the end of the application run. Modifications for user and job-driven logging (SATSEL ...,TAC= and SATSEL...,USER=) are retained past the end of the application run, even for UTM-F. These values can be transferred to a new UTM generation with an inverse KDCDEF.

KDCMSAT

{ SATSEL={ BOTH | SUCC | FAIL | NONE | OFF },          { EVENT=(event1, ..., event n ) |            TAC=(tacname1, ..., tacname n ) |            USER=(username1, ..., username n ) } or: SAT={ OFF | ON } or: HELP }

SATSEL =
	Controls the type of SAT logging. The value of SATSEL changes the generated logging type for the element of the application specified in the subsequent operand. Each time you issue the KDCMSAT command, you can change the setting for one of the criteria EVENT, TAC, or USER.
BOTH	Both successful and failed events are logged.
SUCC	Successful events are logged.
FAIL	Failed events are logged.
NONE	No EVENT-specific, TAC-specific, or USER-specific event selection.
OFF	This setting is only possible for the EVENT criterion. In this case, no events are logged for the event classes specified in EVENT, even if SAT logging was activated in the UTM generation in the USER or TAC command.
EVENT=(event1, ..., eventn)
	Specifies the list of event classes for which the SAT logging conditions are to be changed. The following event classes can be specified and combined in any way. A maximum of 8 values can be specified.
SIGN	Sign-on of a user.
CHANGE-PW	Modification of the password by the user or the UTM administator.
START-PU	Start of a program unit run or acceptance of a dialog or asynchronous job.
END-PU	End of a program unit run.
GSSB	Access to a global secondary storage area.
TLS	Access to a terminal-specific long-term storage area (TLS).
ULS	Access to a user-specific long-term storage area (ULS).
ADM-CMD	Execution of an administration call.
TAC=(tacname1, ..., tacnamen)
	Specifies the list of transaction codes for which the conditions of SAT logging are to be changed. A list containing a maximum of 10 transaction codes can be specified.
USER=(username1, ..., usernamen)
	Specifies the list of users (USER) for whom the conditions of SAT logging are to be changed. You can specify a list containing a maximum of 10 user names.
SAT=ON/OFF
	Switch on/off SAT logging.
ON	SAT logging is switched on. When SAT=ON, you can activate SAT logging when required during the application run for values that were preset in the UTM generation or were set with a preceding KDCMSAT command.
OFF	SAT logging is switched off.
HELP
	Shows the syntax of this command.

Output of KDCMSAT

The old and new SAT logging values, which were modified or switched on/off with this command, are output at the SAT administrator terminal.

Example 1

If you enter:

KDCMSAT SATSEL=SUCC,EVENT=(START-PU,END-PU)

the following is output:

SAT	EVENT	SATSEL
		NEW	OLD
ON	START-PU END-PU	SUCC SUCC	FAIL FAIL

A corresponding table is output for the criteria TAC and USER.

Example 2

If you enter:

KDCMSAT SAT=ON

the following is output:

SAT	NEW	OLD
	ON	OFF