Defining the data fields

This section describes the log data fields that are defined when logging the individual events.

The following tables provide an overview of which log data fields are defined in accordance with the events. The log data fields are listed in the sequence in which they appear in the SAT log record. The field contents are then explained for the individual events.

Meaning of the entries in the following tables:

—	Field not defined
Y	Field defined (mandatory fields in the context of SAT)
O	Field defined in certain cases

Field name	UTM events
	TASK- ON	TASK- OFF	SIGN	CHANGE- PW	START- PU	END- PU	DATA- ACCESS	ADM- CMD	SEL- CMD	CHG- PROG
APPLNAM	-	-	O	-	-	-	-	O	-	-
UTMUSER	-	-	Y	Y	Y	Y	Y	Y	Y	-
UTMAPPL	Y	Y	Y	Y	Y	Y	Y	Y	Y	Y
UTMSUBC	Y	Y	Y	Y	Y	Y	Y	Y	Y	Y
LTERM	-	-	Y	-	O	Y	-	O	-	-
PTERM	-	-	Y	-	-	-	-	O	-	-
MUXLTRM	-	-	O	-	-	-	-	O	-	-
DATNAM1	-	-	-	-	-	-	Y	-	-	-
DATNAM2	-	-	-	-	-	-	O	O	O	-
DATTYP	-	-	-	-	-	-	Y	-	-	-
ACCTYP	-	-	-	-	-	-	Y	-	-	-
COMMAND	-	-	-	-	-	-	-	Y	Y	-
OBJECT1	Y	Y	Y	Y	Y	Y	-	O	O	-
OBJECT2	-	-	-	-	O	-	-	O	O	-
OBJECT3	-	-	-	-	-	-	-	O	-	-
CALLER	-	-	-	-	-	-	-	-	-	-
TACNAM	-	-	-	Y	O	Y	Y	Y	Y	-
TACIDEN	-	-	-	-	Y	Y	-	-	-	-
USER2	-	-	-	-	-	-	-	O	O	-
UTMNAME	-	-	-	-	-	-	-	O	-	Y
UTMTAID	-	-	Y	Y	Y	Y	Y	Y	Y	Y
UTMSTAT	-	-	-	-	-	Y	-	-	-	-
UTMREAS	-	-	Y	Y	Y	Y	Y	Y	Y	-
UTMOBJ4	-	-	-	-	-	-	-	O	-	Y
UMTOBJ5	-	-	-	-	-	-	-	O	-	-
UTMOBJ6	-	-	Y	-	-	-	-	O	-	Y
UTMHEX3	-	-	-	-	-	-	-	Y	-	-

The structure of the variable part of the log record is described in detail below for each event.

TASK-ON: Connect a task to the UTM application

UTMAPPL	Name of the active application.
UTMSUBC	TASK-ON
OBJECT1	F for the first task or N for a follow-up task (next task) or L is initiated with a program exchange or with PEND ER (load program).

TASK-OFF: Sign off a task from the UTM application

Only the normal termination of a task is logged.

UTMAPPL	Name of the active application.
UTMSUBC	TASK-OFF
OBJECT1	Last task: yes “Y” or no “N”

SIGN: Sign on a UTM user

APPLNAM	BCAM application name.
UTMUSER	Name of the user/client that initiates the event.
UTMAPPL	Name of the active application.
UTMSUBC	SIGN
LTERM	Name of the LTERM partner via which the user/client connects to the application.
PTERM	BCAM name of the user/client assigned to defined LTERM partners.
MUXLTRM	PTERM name of the MUX transport connection.
UTMTAID	Transaction identification or zero.
OBJECT1	BCAM processor name.
UTMREAS	KCRSIGN return field.
UTMOBJ6	Long processor name.

CHANGE-PW: Change password

CHANGE-PW is also initiated if a user password is modified by the UTM administrator.

UTMUSER	Name of the UTM user who initiated the event (possibly administrator ID).
UTMAPPL	Name of the active application.
UTMSUBC	CHANGE-PW
OBJECT1	Name of the user ID whose password is changed.
UTMREAS	KDCS return codes.
TACNAM	Transaction code of active program unit.
UTMTAID	Transaction identification or zero.

START-PU: Create a job or start a program unit

UTMUSER	Name of the UTM user who initiates the event.
UTMAPPL	Name of the active application.
UTMSUBC	START-PU (start program unit).
LTERM	Name of the defined LTERM partner or blank.
OBJECT1	If TACIDEN=G: TAC of the job.
	If TACIDEN=C/T/P: TAC of the active service.
OBJECT2	If TACIDEN=G: DPUT identification of the job created.
UTMREAS	KDCS return codes (if TACIDEN=G).
UTMTAID	Transaction identification of the active transaction or zero.
TACNAM	TAC of the active program unit.
TACIDEN	Transaction identifier. Possible values (the values G, C, T, P are mutually exclusive):
	G for generated job Dialog jobs are only logged as generated if they cannot be started immediately due to TAC class control.
	C for start of conversation A conversation begins with this program unit.
	T for start of transaction A follow-up transaction of a conversation begins with this program unit.
	P for start of a follow-up program unit within a transaction

The creation of messages to an LTERM partner is not logged.
A confirmation job (to a TAC) is only logged as generated when, on the basis of the result of the main job run, it is selected and converted to a main job. The destination of the executed main job is then output in the field LTERM or TACNAM.

END-PU: Terminate a program unit

UTMUSER	Name of the UTM user who initiates the event.
UTMAPPL	Name of the active application.
UTMSUBC	END-PU (end program unit).
LTERM	Name of the defined LTERM partner or blank.
OBJECT1	Transaction code of the active service.
UTMSTAT	The field is only defined if TACIDEN=T or C. It then contains the transaction status:
	C: Transaction logging (Commit)
	R: Roll back the transaction
UTMTAID	Transaction identification.
TACNAM	Transaction code of active program unit.
TACIDEN	Possible values:
	C: End of the program unit and of the conversation.
	T: End of the program unit and of the transaction; the conversation is continued.
	P: End of the program unit; the transaction is continued.
UTMREAS	KDCS return codes.

DATA-ACCESS: Access to a UTM storage area

UTMUSER	Name of the UTM user who initiates the event.
UTMAPPL	Name of the active application.
UTMSUBC	DATA-ACCESS
DATNAM1	Name of the UTM storage area addressed.
DATNAM2	If DATTYP=ULS: UTM user
	If DATTYP=TLS: LTERM partner for clients and printers, otherwise blank
DATTYP	Type of storage area:
	G: GSSB
	U: ULS
	T: TLS

ACCTYP	Type of storage access:
	READ: Read access
	WRITE: Write access
	C: Create
	D: Delete
UTMREAS	KDCS return codes.
UTMTAID	Transaction identification.
TACNAM	Transaction code of active program unit.

ADM-CMD: Call the administration program interface

UTMUSER	Name of the UTM user who initiates the event.
UTMAPPL	Name of the active application.
UTMSUBC	ADM-CMD
COMMAND	DADM (KDCS call) or call of the program interface for administration:
	CHNGAPPL / CREATE / CREASTMT / DELETE / DUMP / ENCRYPT /
	GETOBJ / LOCKMGMT / MODIFY / ONLIMP / PETTA / SENDMSG /
	SHUTDOWN / SPOOLOUT / SYSLOG / UPDIPADR / USLOG
UTMHEX3	Return code of administration program interface.
UTMTAID	Transaction identification.
USER2	Session, user or blank.

The fields DATNAM2, LTERM and OBJECT1 may be output as blank.

With some function calls of the program interface, various actions are possible. In this case, SAT writes a log record for each action and logs the parameters, whereby the parameter value is only output if the parameter has changed.

See also the openUTM manual “Administering Applications”.

In certain cases, the following additional fields are defined, depending on COMMAND:

• COMMAND: CHNGAPPL

  UTMOBJ4: Subopcode1 (NEW/OLD for PROGRAM)

• COMMAND: CREATE

  OBJECT3: Object type

  UTMNAME: Object name

• COMMAND: DELETE

  OBJECT3: Object type

  UTMOBJ4: Subopcode1 (DELAY/IMMEDIAT)

  UTMNAME: Object name

• COMMAND: ENCRYPT

  OBJECT1: Subopcode1 (CREATEK, ACTIVATK, DELETEK, REAACTK, REANEWK)

• COMMAND: LOCKMGMT

  OBJECT1: Subopcode1

• COMMAND: MODIFY

  OBJECT3: Object type or parameter type

  Additional fields are logged, depending on the object type or parameter type:

  Object type	Logged fields
  CLNODE	OBJECT1: Parameter UTMOBJ6: Parameter value
  CON	UTMOBJ6: Long processor name
  KSET	OBJECT1: Keys
  LOADMODU	OBJECT1: “Version” UTMOBJ6: Version UTMNAME: Name of load module to be modified
  LPAP	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of LPAP partner to be modified
  LSES	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of LSES and CON triplet to be modified UTMOBJ6: Long processor name
  LTAC	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of LTAC to be modified
  LTERM	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of LTERM partner to be modified UTMOBJ4: „FORMATATTR“ UTMOBJ5: Formata ttribute
  MUX	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of MUX triplet to be modified
  OSICON	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of OSI-CON to be modified
  OSILPAP	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of OSI-LPAP partner to be modified
  PTERM	PTERM: Name of client/printer to be modified (PRTM) OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of PTERM triplet to be modified UTMOBJ6: Long processor name
  TAC	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of TAC to be modified UTMOBJ6: Parameter value
  TACCLASS	OBJECT1: Parameter OBJECT2: Parameter value UTMNAME: Name of TACCLASS to be modified
  TPOOL	LTERM: LTERM prefix OBJECT1: Parameter1 OBJECT2: Parameter value1 UTMOBJ4: Parameter2 UTMOBJ5: Parameter value2 UTMNAME: Name of TPOOL to be modified (LTERM prefix, PRONAM, PTYPE, BCAMAPPL)
  USER	OBJECT1: Parameter OBJECT2: Parameter value UTMOBJ4: “FORMATTR” UTMOBJ5: Format attribute UTMNAME: Name of USER to be modified

  Parameter type	Logged fields
  CCURRPAR	OBJECT1: Parameter UTMOBJ4: Parameter value 1 UTMOBJ5: Parameter value 2
  CLPAR	OBJECT1: Parameter UTMOBJ4: Parameter value
  CURRPAR	OBJECT1: Parameter UTMOBJ6: Parameter value
  DIAGACCP	OBJECT1: Parameter OBJECT2: Parameter value 1 UTMOBJ6: Parameter value 2
  MAXPAR	OBJECT1: Parameter OBJECT2: Parameter value
  TASKSPAR	OBJECT1: Parameter OBJECT2: Parameter value
  TIMERPAR	OBJECT1: Parameter OBJECT2: Parameter value

• COMMAND: ONLIMP

  OBJECT1: „KC_ALL“

• COMMAND: SENDMSG

  LTERM: LTERM name or “KDCALL”

• COMMAND: SHUTDOWN

  OBJECT1: Subopcode1

  OBJECT2: Parameter value

• COMMAND: SPOOLOUT

  OBJECT1: “SPOOLOUT”

  OBJECT2: “ON”

• COMMAND: SYSLOG

  OBJECT1: Subopcode1

  UTMOBJ6: Parameter value

• COMMAND: UPDIPADR

  OBJECT1: Subopcode1

• COMMAND: USLOG

  OBJECT1: Subopcode1

SEL-CMD: Execute a preselection command

If the name or value of a parameter is longer than 8 characters, the abbreviation described in UTM-SAT administration is output in the log data field.

UTMUSER	Name of the UTM user who initiates the event.
UTMAPPL	Name of the active application.
UTMSUBC	SEL-CMD
COMMAND	Specification of the UTM-SAT administration command: MSATSEL or MSATPROT.
UTMREAS	Internal system return code.
UTMTAID	Transaction identification.
TACNAM	Transaction code of active program unit.
USER2	User or blank.

The fields DATNAM2, LTERM and OBJECT1 may be output as blank.

The following additional fields are defined, depending on COMMAND:

• MSATSEL (control preselection, command KDCMSAT SATSEL=...)

  A separate log data record is written for each name specified. Only one of the fields USER2, DATNAM2 or OBJECT1 is defined:

  USER2: UTM user as preselection object.

  DATNAM2: TAC as preselection object.

  OBJECT1: Event as preselection object.

  OBJECT2: Preselection value (NONE, SUCC, FAIL, BOTH or OFF).

• MSATPROT (Control SAT logging, command KDCMSAT SAT=...)

  OBJECT2: Logging switched on (ON) or off (OFF).

CHG-PROG: Exchange a load module

UTMAPPL	Name of the active UTM application.
UTMSUBC	CHG-PROG
UTMNAME	Name of the module to be exchanged.
UTMOBJ4	Load mode of the module to be exchanged.
UTMOBJ6	New module version.
UTMTAID	Transaction identification if UTMOBJ4=ON-CALL, otherwise zero.

For UTMOBJ4=ON-CALL, note that CHG-PROG is always logged as successful. The associated END-PU log data record indicates whether or not the exchange was successful. (In the event of an error, a PEND ER occurs with the corresponding KDCS return codes.) The initial loading is also logged as an exchange.