NonStop Server for Java 7.0 Programmer's Reference

JI client with a legacy TS/MP serverclass for context-free communication
The client socket in the mapping file needs to be configured with the attribute
pathsend_qualifier set to **CONTEXT-FREE**.
For example, pathsend_qualifier=**CONTEXT-FREE**.
Internally no operations are performed during the connect operation. When the client application
invokes the flush method on the output stream of the socket, or invokes the write method on
the NIO channel, data is sent to the server through a SERVERCLASS_SEND_ call. The response
from the server can be read through the input stream of the socket or the read method of the NIO
channel.
It has to be noted that the amount of data that can be sent to the server depends on the internal
buffer size of the socket. If the TS/MP version supports large data transfer then the maximum data
that can be sent to the server is 2 MB, else the limit for data transfer is 32 KB.
JI client with a legacy TS/MP serverclass for dialog based communication
The client socket in the mapping file needs to be configured with the attribute
pathsend_qualifier set to **CONTEXT-SENSITIVE**.
For example, pathsend_qualifier=**CONTEXT-SENSITIVE**.
Internally no operations are performed during the connect operation. The client application can
write any amount of data through the output stream or the write method of the NIO channel. As
and when the internal buffer of the socket gets full, data is sent to the serverclass once through the
invocation of dialog begin call and subsequently through the dialog send calls. All invocations of
the dialog API until the client application explicitly invokes a flush has the MAX_REPLY_LEN
attribute set to 0. This is an indication to the server that the message transfer is incomplete. Upon
invocation of the flush, remaining data is sent to the server with the MAX_REPLY_LEN attribute
of the dialog API set to a positive value greater than 0. This value is equal to the receive buffer
size of the socket. The server can use the file system code FECONTINUE (70) to indicate incomplete
data transfer. The JI library keeps the dialog open if the file system code received is 70. It ends
the dialog if the code is 0, and aborts the dialog if the file system code is other than 0 or 70.
Legacy client with a JI server
When a legacy client wants to communicate with a JI server, the server socket configuration in the
mapping file must have pathsend_qualifier set to **ANY-DIALOG**, and open_qualifier
set to **ANY-QUALIFIER**.
For example, pathsend_qualifier=**ANY-DIALOG** and
open_qualifier=**ANY-QUALIFIER**.
A server socket with this configuration creates a new socket for any open file, context free message,
or dialog message that are not handled by any other server socket definitions. There can be only
one server socket defined with these unique qualifier values.
In case the client wants to transfer large amount of data (greater than what is permitted per
invocation of the API call that is used for transfer) it can perform so by setting the MAX_REPLY_LEN
attribute of the API call to 0. When the JI library notices this value, it assumes that more data transfer
can be expected.
Communicating with non JI components 81