When a list is output to a printer, the counter values in the COUNTER and STATUS masks are combined.
In addition, information on UDS-D can be output from the TRANSACTION and CONNECT monitor masks. This output is controlled by means of the UDSMON command MEDIUM=L,n,D (D=distributed).
Generally, the content of the list output corresponds to the output at the data display terminal (see chapter "Description of UDS/SQL monitor output to data display terminal"). There are, however, the following differences:
In the case of the STATUS, TRANSACTION and CONNECT monitor masks there is no interval counter (IV) information line. Information on all active transactions is output.
In the case of openUTM transactions, the "*" character is output after the TSN in the TSN column of the STATUS mask.
If a transaction in OSI TP is distributed globally with "Functional Unit Commit", up to 64 bytes of the Atomic Action Identifier (AAID) are output in hexadecimal format for this transaction in an additional line of the list output. In the case of transactions which are distributed via UDS-D, output takes place only in the configuration of the primary subtransaction, in other words in the configuration in which the UTM application concerned is connected.
The AAID is generated by an OSI-TP application which controls the transaction as a partner of a UTM application.
This controlling OSI-TP application can be for example UTM (on BS2000 or other platforms), the LU6.2 gateway or the generic BeanConnect-Proxy UTM application on Linux
This AAID is generated in the OSI-TP gateway at the start of the transaction (e.g. in theopenUTM-LU62 gateway).
Generation of the AAID is logged in the gateway’s corresponding instance trace. This enables the transaction to be assigned to the controlling transaction in the foreign system.