If you want to use OSI TP to connect your UTM applications with transaction applications of other manufacturers you have to consider the following points:
User data when establishing associations:
When the connection is being established, only the user data necessary for OSI TP and CCR is exchanged. Other user data is not sent and is ignored when received.User syntaxes and CCR association setup:
openUTM does not permit syntaxes generated by openUTM to be rejected by the Additionally, these syntaxes must be offered with the association setup request. In such cases, openUTM rejects the association setup.Disconnection with A-ABORT:
openUTM uses A-ABORT to disconnect, not A-RELEASE.Channels:
"Two-way-recovery" channels are not supported by openUTM.User data for TP-BEGIN-DIALOGUE-RI:
You can only use TP-BEGIN-DIALOGUE-RI to exchange user data necessary for UTMSEC. Application programs have no direct access to this user data. Other user data is not sent and is ignored when received.No user data for TP-BEGIN-DIALOGUE-RC, TP-ABORT-RI:
openUTM does not send user data with the protocol elements. Received user data is ignored.No Shared Control functional unit:
openUTM does not support the Shared Control functional unit (i.e. does not support the profiles ATP12, ATP22, ATP32).Unchained Transactions functional unit:
openUTM does not support this functional unit as a job submitter. Conversely, you can select the functional unit in a partner application if the partner application acts as job submitter. However, the partner application has to start the distributed transaction before the first send authorization transfer in the dialog. The dialog must terminate with the first transaction, as otherwise openUTM terminates the dialog abnormally.Recipient TPSU-Title:
A Recipient TPSU-Title is always necessary when using TP-BEGIN-DIALOGUE-RI. If openUTM is the receiver, the title must not exceed 8 characters in length and cannot be of the type "integer".REQUEST-CONTROL-RI, HANDSHAKE-RI:
openUTM does not send the protocol elements. If a dialog service receives TP-HANDSHAKE-RI it is terminated abnormally.maximum user data length: 32767 octets:
openUTM sends a maximum of 32767 octets of user data in a protocol element. If user data with a length of more than 32767 octets is received, openUTM disconnects the link.End of dialog without Commit:
No TP-END-DIALOGUE-RI should be sent to a dialog job-receiving service (end of dialog from "above"), as otherwise openUTM terminates the service abnormally. openUTM only uses "Confirmed End Dialogue" for the transfer of asynchronous messages.