TS/MP Pathsend and Server Programming Manual (G06.24+, H06.03+)

Writing Pathway Servers
NonStop TS/MP Pathsend and Server Programming Manual–132500
4-17
Writing Pathway Servers That Interoperate With
TUXEDO Requesters
either FEOK (0) or FEEOF (1); these values direct the LINKMON process to release the
link for re-use.
If a processor or network failure occurs, it is possible to have a dialog abort but not
receive a Pathsend dialog abort message. Therefore, to monitor all aborted dialogs, your
server must also monitor CPU down, remote CPU down, and loss of communication
with network node system messages if it uses FILE_GETRECEIVEINFO_, or CLOSE
system messages if it uses CRE_Receive_Read_ or the COBOL85 or FORTRAN
language. The server should treat such messages as dialog aborts.
Servers can monitor CPU down, remote CPU down, and loss of communication with
network node system messages by calling the Guardian procedures MONITORCPUS
and MONITORNET, which are described in the Guardian Programmer’s Guide.
It is also possible to get Pathsend dialog abort messages that do not represent actual
aborted dialogs. A server can receive such a message if the requester calls
SERVERCLASS_DIALOG_BEGIN_ and then cancels the message. In that case, the
LINKMON process sends the Pathsend dialog abort message even though the server
might not have received the first message in the dialog. Similarly, if the requester calls
SERVERCLASS_SEND_ with the nowait option and then cancels the operation before
being notified of completion of the operation through the AWAITIOX procedure, the
server receives the Pathsend dialog abort message even if it has already replied to the
last send operation.
A cancel operation can also occur if the requester abends while a server-class send
operation is in progress, whether or not the send operation was invoked with the nowait
option.
Writing Pathway Servers That Interoperate With
TUXEDO Requesters
A Pathway server can service requests from TUXEDO requesters (TUXEDO clients or
TUXEDO servers acting as clients). Such requesters can make their requests to a
Pathway server in either of two ways:
•
Directly, by making calls to the Pathsend procedures described in this manual
•
Indirectly, by using the TUXEDO to Pathway (TUX2PWY) translation server
Only those TUXEDO requesters that are NonStop TUXEDO native System /T clients
can make direct requests by using Pathsend procedure calls. For more information, refer
to the NonStop TUXEDO System Application Development Guide.
Native System /T clients, remote TUXEDO requesters using System /Domain, and non-
native TUXEDO workstation clients can indirectly invoke the services of a Pathway
server by using the TUXEDO to Pathway translation server. If you use this translation
server, special guidelines apply, and you might need to modify the code of existing
Pathway servers. For further information, refer to the NonStop TUXEDO System
Pathway Translation Servers Manual.