TS/MP 2.5 Pathsend and Server Programming Manual

To communicate directly with a NonStop Tuxedo server by calling the ATMI functions, a Pathsend
requestor must also act as a NonStop Tuxedo client, as follows:
• It must be compiled as an OSS process; therefore, it must be written in an HP language that
supports OSS (such as HP C for NonStop systems ).
• It must link in the ATMI functions. For example, if the requestor is an HP C program, it can be
linked to the ATMI functions by being compiled with the buildclient command.
• It must join a NonStop Tuxedo application by calling the tpinit() ATMI function or one of the
ATMI functions that implicitly calls tpinit(), such as tpalloc() or tpcall().
• It must follow the restrictions on Pathsend procedure calls that apply to NonStop Tuxedo clients:
namely, it cannot make nowait calls (calls with bit 15 of the flags parameter set to 1) to the
SERVERCLASS_SEND_, SERVERCLASS_DIALOG_BEGIN_, and SERVERCLASS_DIALOG_SEND_
procedures.
A requestor using this method of interoperation can use request/response messages, conversations,
or both.
For more information about writing a NonStop Tuxedo client and calling the ATMI functions, see
the NonStop TUXEDO System Application Development Guide. For the syntax of the ATMI function
calls, see the NonStop TUXEDO System Reference Manual.
To communicate indirectly with a NonStop Tuxedo server by using the Pathway translation server,
a Pathsend requestor program (or a SCREEN COBOL requestor program) must be written according
to the guidelines in the NonStop TUXEDO System Pathway Translation Servers Manual. see that
manual for further information. A Pathsend requestor using the translation server must use context-free
Pathsend calls (calls to SERVERCLASS_SEND_); the translation server does not support dialogs
(conversations).
60 Writing Pathsend Requestors