OpenTP1 Version 7 Programming Guide
5.1.5 Notes on using xatmi interface for communication under OpenTP1
When using the XATMI interface for communication under OpenTP1, note the following:
- The following value must be specified in the user service definition of the user server which uses the XATMI interface.
server_type = "xatmi"
- The XATMI interface does not have the concept of service groups. To use the XATMI interface for communication under OpenTP1, however, a service group should be specified in the UAP user service definition.
- The following values must be specified in the user service definition or user service default definition when the XATMI interface is to be used under a transaction:
trn_expiration_time = non-zero value
trn_expiration_time_suspend = Y
- If blocking occurs when the function tpcall(), tpacall(), tpconnect(), or tpsend() sends data and is not removed within the specified period, TPESYSTEM is returned regardless of whether the TPENOBLOCK flag is set. The period until the function returns with a TPESYSTEM error is determined by the service request retry count and interval specified in the definition.
- If a transaction timeout occurs, the process terminates abnormally without returning TPETIME.
- When a UAP calls an XATMI interface function (e.g., tpcall()) after the UAP has been called by the function dc_rpc_call(), the UAP should be linked to a stub created by specifying client definitions both in the RPC interface definition and the XATMI interface definition. See the applicable OpenTP1 Programming Reference manual.
- If the transaction is settled by the function tx_commit() or other similar means, all data yet to be received becomes invalid.
- Before the internode load-balancing facility and the extended internode load-balancing facility can be used, as in the case of the function dc_rpc_call(), multiple SPP service group names must match in the user service definition. For this purpose, specify the service names and executable file names in the user service definition so that they match. If service names do not match, the function tpcall(), tpacall(), or tpconnect() may fail. If executable file names do not match, the result varies depending on which server UAP is scheduled.
- The maximum data length that can be transferred via the XATMI interface API is 500 Kbytes.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.