Your Browser is not longer supported

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

{{viewport.spaceProperty.prod}}

Job-driven SAT logging

For each individual transaction, you can define whether the CHANGE-PW, START-PU, END-PU, DATA-ACCESS, ADM-CMD events initiated by the associated program unit and any security-related events of a participating database are to be logged. In addition, the creation of jobs of this transaction code (START-PU) is logged. However, an event is not logged for the transaction code if SAT logging is switched off for this event with OFF.

You can specify the following for each transaction code:

SUCC

The events of the program unit run are logged if the result is success.

FAIL

The events of the program unit run are logged if the result is failure.

BOTH

The events of the program unit run are logged regardless of the result.

NONE

No job-driven logging.

The preselection values for job-driven logging can be set in the UTM generation with the following statement:

TAC tacname,...,SATSEL=...

Using UTM SAT administration functions, you can set the preselection values with the command:

KDCMSAT SATSEL=...,TAC=tacname

These settings are retained past the end of the application run, even for UTM-F.