OSI/TS Management Programming Manual

Running a TSP Process
Communicating with OSI/TS (TSP) Processes
056786 Tandem Computers Incorporated 2–3
The TSP process also supports a number of PARAM commands. Refer to the OSI/TS
Manual for details.
Running TSP
Programmatically With a
NEWPROCESS or
PROCESS_CREATE_ Call
An application can create the TSP process by calling the NEWPROCESS or
NEWPROCESSNOWAIT procedure provided by the Guardian 90 C-series system
operating system; for D-series systems the equivalent procedure is the
PROCESS_CREATE_ procedure. The complete syntax of these procedures is provided
in the System Procedure Calls Reference Manual, and further information about how to
use them is given in the Guardian 90 Operating System Programmer’s Guide.
The Guardian 90 owner ID of your application must be in the super group (group ID
255) when the application calls the NEWPROCESS or PROCESS_CREATE_ procedure
to run the TSP process. Otherwise, requests from the TSP process to an underlying
X25AM or TLAM I/O process will fail with a security error.
Special considerations for using NEWPROCESS and NEWPROCESSNOWAIT or
PROCESS_CREATE_ to run TSP are discussed in the following paragraphs.
In the first 12 words of the filenames parameter, specify the TSP object file.
If your application uses a large amount of stack space, the swap-file or swap-volume
option, which you specify in the last 12 words of the filenames parameter, can be
useful. This option allows you to move the swap file to a disk volume other than the
volume on which the program file resides.
You must include the name parameter; the Guardian 90 operating system will not start
an TSP process unless a name is specified. The TSP process name can be up to 6
characters (the $ sign followed by 5 characters). For example:
$TSP10
$TSP12
If two or more TSP processes share the same X25AM line, the first 4 characters after
the $ sign are used by TSP to build the SU name and must be unique. For example:
$TSP10
$TSP20
$TSP30
TSP processes on D-series systems that communicate with applications on remote C-
series systems can have names up to 5 characters (the $ sign followed by 4 characters).
For example:
$TSP1
$TSP2
After your application creates the TSP process, it must send the TSP process a startup
message, including any additional desired startup parameters, as described in the
Guardian 90 Operating System Programmer’s Guide.
In the parameter string of the startup message, you should always specify the backup
CPU number parameter, so that the TSP process will run as a NonStop process pair.
Otherwise, if the CPU in which the process is running fails, you will be unable to