|
|
|
|
Use the following operational guidelines for writing TP servers:
Use REGISTER_TP_SERVER to register the application as a TP server. The REGISTER_TP_SERVER verb provides the address of a callback function used in later Attach notifications.
Use REGISTER_TP to register the TP names and local and remote LUs for which the TP server wishes to process Attaches. The TP server can use wildcards for both TP names and LU names so that it can choose to process Attaches from a TP over a particular pair of LUs or to Attaches for all TPs over all LUs, or any combination of those conditions.
Use QUERY_ATTACH (with the unique identifier received when the notification callback is made after an Attach is received for the registered TP or LU) to query the Attach parameters to determine whether and how to process the Attach. The TP server can reject the Attach using REJECT_ATTACH or accept the Attach using ACCEPT_ATTACH and start a suitable application to process the Attach.
Issue the standard RECEIVE_ALLOCATE call to retrieve the Attach. The previously reserved dload_id parameter is used to specify the unique identifier of the Attach.
Use ABORT_ATTACH to cancel any further processing if, after issuing ACCEPT_ATTACH, an error is encountered.
Deregister the TP server for any of the previously registered TPs and LUs using UNREGISTER_TP.
Deregister the application as a TP server using the UNREGISTER_TP_SERVER verb.
When a TP server handles an Attach, the TP server inherits a number of responsibilities normally performed by the SNAP-IX Attach Manager. These responsibilities include the following:
Starting TPs to handle the conversations if a TP is configured to be automatically started
Handling conversation security including parsing the Attach data returned on QUERY_ATTACH
Conveying information from the Attach to the TP that the TP server starts to process the ensuing conversation
SNAP-IX provides a default TP server, snatpsrvd, that is installed on all systems. This TP server uses the sna_tps file as the source for the configuration of the TPs that it can load. Other TP servers can modify and use this file by using DEFINE_TP_LOAD_INFO verbs. For more information about the DEFINE_TP_LOAD_INFO verb, refer to the SNAP-IX NOF Programmer's Guide. APPC provides the tp_file_updates parameter on a REGISTER_TP verb so that a TP server is notified when a change has been made to the sna_tps file and can take the required action.
|
|
|
 |
|