RSC/MP 7.2 Programming Manual

Sample Code Overview
HP NonStop Remote Server Call (RSC/MP) Programming Manual—522360-004
F-3
IDS Router Sample
The echo server is called TDDSVR. It simply echoes whatever data it receives.
Ordinarily, TDDSVR keeps a reference count of its openers in order to exit correctly
when running under PATHWAY control. This behavior can be suspended in order to
run TDDSVR as a standalone server by including any token on the invoking command
line. For example, to start TDDSVR using the process name $TDD (which is the
process name expected by the client samples), use the following command:
RUN TDDSVR /NAME $TDD, NOWAIT/ STANDALONE
In this example, the token “STANDALONE” indicates to TDDSVR that it should
continue running rather than exit when a PATHWAY server would.
The echo server sample is delivered as C source code (TDDSVRC) and the
corresponding pre-built executable (TDDSVR). These files are installed into the
product subvolume as part of the RSC/MP Host delivery.
IDS Router Sample
The IDS router sample is used mainly to verify correct configuration and operation of
the RSC/MP product. When used as a test utility, it fills the role of “application-specific
IDS requester” (as described in The IDS Session Type on page 4-3) in order to support
the client samples whose names start with “RSCTEST”.
RSC/MP supports custom IDS requesters in order to support existing applications that
make use of them. Due to inherent limitations in the IDS infrastructure, it is anticipated
that new applications will use PATHSEND (interprocess) sessions rather than IDS
sessions. Thus the IDS router sample includes only minimal code to support
RSCTEST. It echoes data directly to the client without ever using an actual PATHWAY
serverclass. Its source code is not well suited for adaptation into a useful custom IDS
requester.
The IDS router sample is delivered with the RSC/MP host software as SCOBOL
source code (IDSSAMPL) and the corresponding execution-related files (IDSCOD,
IDSDIR, IDSSYM). All four files are installed into the product subvolume as part of the
RSC/MP Host delivery.
Java Sample
The RSC/MP Java sample code is provided to demonstrate a way to access the
RSC/MP API using the Java programming language.
The Java sample code consists of four parts:
•
a sample Java Native Interface (JNI) library written in C
•
a set of sample framework classes written in Java
•
a sample application, “RscTestJ”, written in Java
•
a sample servlet, “RscSampleServlet1”, written in Java