TS/MP Pathsend and Server Programming Manual (H06.05+, J06.03+)

3 Writing Pathsend Requesters
This section explains how to write programs that use Pathsend procedure calls to make requests
to Pathway servers. These programs can be either one of these:
Standard requesters—programs that initiate application requests
Nested servers—servers that act as requesters by making requests to servers in other server
classes
Nested servers are described further in Section 4, “Writing Pathway Servers” (page 62). However,
this section (Section 3) describes the use of Pathsend procedure calls to perform requester functions,
whether by a standard requester or a nested server. The terms Pathsend program and Pathsend
process are used to refer to any program or process that uses Pathsend calls, whether it is a standard
requester or a nested server.
Pathsend programs are Guardian requesters, as described in the Guardian Programmer’s Guide.
You can write Pathsend programs in C, C++, COBOL85, Pascal, pTAL, or TAL. You should be
familiar with the Guardian requester/server model as implemented in the programming language
you are using.
In addition, if you are using the TMF subsystem, you should be familiar with the programming
guidelines and considerations for TMF requesters, as described in the HP NonStop Transaction
Management Facility (TMF) Application Programmer’s Guide . Note that the HP NonStop Transaction
Management Facility (TMF) Application Programmer’s Guide describes requesters that use calls
to Guardian procedures rather than Pathsend procedures. In Pathsend requesters that use the TMF
subsystem, calls to Pathsend procedures are used instead of calls to WRITEREAD and associated
Guardian procedures, and there are other differences as described in this section.
An example of a Pathsend requester program that is also a nested server is given in Example
3 (page 130).
The Pathsend Procedure Calls
Pathsend programs use six procedures that are part of the Guardian procedure library:
SERVERCLASS_SEND_
SERVERCLASS_SEND64_
SERVERCLASS_DIALOG_ABORT_
SERVERCLASS_DIALOG_BEGIN_
SERVERCLASS_DIALOG_END_
SERVERCLASS_DIALOG_SEND_
SERVERCLASS_DIALOG_SEND64_
SERVERCLASS_DIALOG_BEGIN64_
SERVERCLASS_SEND_INFO_
SERVERCLASS_SEND_INFO64_
For enabling 64-bitt user space features in the TS/MP application, call 64-bit user space APIs in
the OSS environment and with LP64 memory option. For enabling 64-bit user space in the Guardian
environment call 64-bit user space APIs using the mixed data-model programming.
NOTE: The mixed data-model programming uses 64-bit pointers generated by
SEGMENT_ALLOCATE64_ and the same pointers are used in the ILP32 memory model. In this
way, 64-bit APIs can be used on the Guardian environment.
Later parts of this section describe how to use these procedures in context-free and context-sensitive
Pathsend programs. Section 5, “Pathsend Procedure Call Reference” (page 75), gives detailed
syntax and usage considerations for the procedures.
The Pathsend Procedure Calls 51