Auditing and tracking with z/OS Connect
Audit and track requests with z/OS® Connect, which includes an interceptor that records data to the z/OS SMF data store.
About this task
The SMF data in the 120-11 record contains the standard header for SMF records. Then, there are two triplets. The first triplet points to the server identification section of which there is one instance. The second triplet points to the user data section of which there can be multiple instances.
- The server data section consists of the following parameters: (values in decimal)
-
- Offset Length Data
- 0 4 Version (1)
- 4 8 System name
- 12 8 Sysplex name
- 20 8 Job id(jsabjbid)
- 28 8 Job name (jsabjbnm)
- 36 8 SToken (assbstkn)
- The user data consists of the following parameters (values in decimal):
-
- Offset Length Data
- 0 4 Version (1)
- 4 4 Type
- 8 4 Length of data (user data sections are 2 K, this field indicates how much of that is used)
- 12 ? Data
- The user data consists of the following parameters (values in decimal):
-
For z/OS Connect the user data type is 102 (decimal). The data contains the following parameters:
- Offset length Data
- 0 4 Version (3)
- 4 8 Arrival time (STCK format)
- 12 8 Completion time (STCK format)
- 20 64 Target URI (EBCDIC, right-padded with blanks)
- 84 4 Input payload length in bytes
- 88 64 Service name (EBCDIC, right-padded with blanks)
- 152 8 Method (EBCDIC)
- 160 4 Respond length in bytes
- 164 64 User name (EBCDIC, right-padded with blanks)
- 228 23 Request id (bytes, right-padded with zeros)
- 251 1 Boundary padding (zero)
- 252 64 Service grouping name (EBCDIC, right-padded with blanks)
- 316 8 Mapped user name (EBCDIC, right-padded with blanks) Only valid on version 3 or later.