openUTM creates a SAT log record for each event. Each log record transferred by openUTM to SAT comprises a part with a fixed structure and length, the SAT header, followed by a part with variable structure and length.
The SAT header contains the date and time, the BS2000 user, the TSN, the current BS2000 event, and its result. Only the following fields are defined by openUTM:
Field name | Meaning | Type |
EVT | Type of event | C string (1..3) |
RES | Result of event | Set: Success/Failure (“S” / “F”) |
The variable part contains individual UTM-specific data fields, each of which is preceded by a length field and a SAT identifier. The type and number of the individual data fields depends on the type of UTM event.
The following tables indicate the log data fields used by openUTM (arranged alphabetically), the meaning of the field contents, and its data type.
UTM events can be linked with the ALARM function of SAT. Apart from a few exceptions, the data type for SAT-ALARM matches the data type for SATUT. In the following table, the ALARM data type is specified in brackets () if it differs from the data type for SATUT.
Field name | Meaning | Type |
ACCTYP | Access type of UTM storage area | Set: C / D / READ / WRITE |
APPLNAM | BCAM application name | C string (1..8) |
CALLER | Address of caller | X string (1..4) |
COMMAND | Name of UTM-SAT administration command or administration program interface | C string (1..8) |
DATNAM1 | Name of UTM storage area | C string (1..8) |
DATNAM2 | Name of UTM object | C string (1..8) |
DATTYP | Type of UTM storage area | Set: G / T / U |
LTERM | LTERM partner name for clients and printers | C string (1..8) |
MUXLTRM | MUX transport connection | C string (1..8) |
OBJECT1 | Name of UTM object or administration program interface: name of modified field | C string (1..8) |
OBJECT2 | Name of UTM object or administration program interface: content of modified field | C string (1..8) |
OBJECT3 | Administration program interface: object type | C string (1..8) |
PTERM | BCAM name | C string (1..8) |
TACIDEN | Transaction identifier | Set: G/T/D/C/P |
TACNAM | Transaction code | C string (1..8) |
USER2 | UTM user name | C string (1..8) |
UTMAPPL | UTM application name | C string (1..8) |
UTMHEX3 | RC of administration program interface | C string (1..8) |
UTMNAME | Name of load module or administration program interface: name of UTM object | C string (1..32) |
UTMOBJ4 | Program load mode or administration program interface: subopcode1 or “FORMATTR” or field name | C string (1..8) |
UTMOBJ5 | Administration program interface: format attribute or field name | C string (1..8) |
UTMOBJ6 | Load module version or long processor name | C string (1..24) |
UTMREAS | KDCS return code 1 | C string (1..8) |
UTMSTAT | Transaction status | C string (1) |
UTMSUBC | UTM event | Set: CHANGE-PW / SIGN / |
UTMTAID | Transaction identification 2 | X string (1..4) |
UTMUSER | UTM user name | C string (1..8) |
1With the UTM events CHANGE-PW, START-PU, END-PU and DATA-ACCESS, the return code is made up of the compatible and the incompatible KDCS return code.
2The transaction identification (TA-ID) comprises a 2-byte service counter (within a session) and a 2-byte transaction counter (within a service). It is made available at the IUTMDB interface to the database for SAT logging of database events. The transaction identification is used to assign an event to the transaction which created it.