The Remote Subroutine Server (also known as LRSS) enables Debugger to call subroutines from host Runtime platforms.
There are two methods of installing Remote Subroutine Server:
You can install it as part of the standard installation of Runtime software (refer to Installing the MCP Runtime Software).
You can install it independently using the LRSS install WFL.
Independent Installation
To install the Remote Subroutine Server, enter the following command:
START NGEN28/SAMPLE/LRSS/INSTALL ("usercode","packname")
The location of the files is based on the current directory. A Usercode and Pack name might be provided as optional parameters to the install job.
The install job performs the following:
Registers the Remote Subroutine Server as a Distributed System Services (DSS) provider
Maps the Support Library (SL) function names for Remote Subroutine Server
Alternatively, the installation can be performed manually. Use the following commands from the system console or a suitably privileged station:
To register Remote Subroutine Server as a DSS provider enter the following command:
NA LOAD COMMANDS LRSS/DSS/REGISTER
To map Support Library (SL) function names for Remote Subroutine Server enter the following command:
SL LRSSSUPPORT= SYSTEM/LRSS/SUPPORT: TRUSTED, LINKCLASS= 1 SL LRSSPDUSUPPORT= SYSTEM/LRSS/PDUSUPPORT: TRUSTED, LINKCLASS= 3
Note: Usercode and Pack names might need to be inserted into the above commands as applicable.
Configuration
To configure Remote Subroutine Server you need to set the options in the configuration file that is read at startup. The file is at LRSS/CONFIG and all options have default settings, so users only need to change them if the need arises.
The options are:
PORT = | <Integer, 0 to 65535, default 6004> |
CONNECTIONS = | <Integer, 1 to 4000, default 12> |
MAXOFFER = | <Integer, 1 to 99, default 1> |
INACTIVITY = | <Integer, 1 to 1440, default 10 minutes> |
TIMEOUT = | <Integer, 1 to 1440, default 60 minutes> |
ERRORS = | <File name, default LRSS/ERRORS> |
TRACE = | {ON | OFF (default) [[TO] <File name, default LRSS/TRACE/#>]} |
These options are:
PORT
The Port is the TCP/IP communications service number used to establish incoming connections from prospective clients.
CONNECTIONS
Connections is used to limit the total number of concurrent sessions available.
MAXOFFER
MaxOffer controls the number of listening port subfiles that are available. The range is either 1 through 99, or 1 through the number of connections allowed (if less than 99).
INACTIVITY
Inactivity is the interval of time between when TCP/IP keep alive packets are exchanged with the client. The inactivity value is mapped to the port file attribute DialogCheckInterval.
TIMEOUT
Timeout is the duration for which TCP/IP keep alive packets can continue to be sent before a connection is closed. The range is as applicable for the port file attribute BlockedTimeout.
ERRORS
The Errors option locates the filename for any configuration problems found. Messages are logged to the error file with a reference to the problem line in the configuration file.
TRACE
Trace is available for observing Remote Subroutine Server behavior or diagnosing problems. Tracing can be turned on or off, and the title of the trace file can also be set. The default value is off and the default title is LRSS/TRACE/#, where # is a numerator starting at zero. Each time the server starts, the trace file name's numerator restarts at zero.
Comments
Comments can be placed anywhere in the text stream and are terminated by the end of each line. A comment is denoted by the presence of either a percent or an asterisk character in the text stream except when enclosed by quotation marks.
The syntax is as follows:
% this is a comment* and so is this
Operations
Remote Subroutine Server can be controlled through the Network Application (NA) interface. You can start, stop, show status or change trace options. These commands are:
Action | Command |
---|---|
Start | NA LRSS + |
Stop | NA LRSS - |
Show Status | NA LRSS STATUS |
Trace | NA LRSS TRACE [ON | OFF | Release] |
When the Release option is used on the trace command, the existing trace file is closed and a new trace file is opened with an increment to the numerator portion of the trace file title.
If Remote Subroutine Server is not running, it starts automatically when an incoming connection is attempted on the port service number registered through DSS for Remote Subroutine Server.
Monitoring
A facility exists in Remote Subroutine Server to monitor remote method calls made from its clients. The monitor facility is programmatically interfaced and provision is given to veto any remote procedure calls at hand.
Monitoring depends on the entry point within a user written application. For the monitor to work a Support Library (SL) named LRSSMONITOR must exist. This SL is checked for at startup.
The entry point is described, and an example given, in the sample source file LRSS/MONITOR.