TRANSFER Installation and Management Guide

TISERV
Customizing a TRANSFER System
7–12 068837, Update 1 to 013198 Tandem Computers Incorporated
Using TISERV Outside the PATHWAY Environment
Although most TRANSFER clients are written as SCREEN COBOL programs that
execute within PATHWAY TCPs, you can start a TISERV process for use outside the
PATHWAY environment with clients written in COBOL, FORTRAN, TAL, C, or
Pascal. You must observe the following rules:
TISERV must run with the same user ID as that used to initialize the TRANSFER
database. If your client runs under a different user ID, create a copy of the TISERV
program file owned by the user ID that initialized the TRANSFER database and
set the PROGID flag. Use the FUP LICENSE command to license this copied file.
Before starting a TISERV process, the Name server and Text server processes must
be running.
To prevent warnings when the TISERV process is doing many kinds of useful
work, the TRANSFER scheduler process must be running.
When calling the NEWPROCESS procedure, either omit the memory pages
parameter or specify a value of zero for that parameter. This causes the TISERV
process to be created with its default virtual memory size.
TISERV interprets the startup message as follows:
Default subvolume—ignored
In file name—ignored
Out file name—used to write serious error messages
(These messages usually indicate a problem in the database or the
operational environment, not in the client.)
Parameter string—ignored
If TISERV encounters a fatal error, it attempts to write one or more messages to the
OUT file (or the home terminal if the OUT file cannot be opened) and then ABENDs.