Pathway/iTS TCP and Terminal Programming Guide

Processing Unsolicited Messages
Compaq NonStop™ Pathway/iTS TCP and Terminal Programming Guide—426751-001
7-3
The PW-TCP-SYSTEM-NAME and PW-TCP-
PROCESS-NAME Special Registers
The PW-TCP-SYSTEM-NAME and PW-TCP-
PROCESS-NAME Special Registers
The read-only special registers, PW-TCP-SYSTEM-NAME and PW-TCP-PROCESS-
NAME, contain the system name and Guardian process name of the requester's TCP.
They are intended for use by a requester, in conjunction with the LOGICAL-
TERMINAL-NAME special register, when the requester is identifying itself to a process
that is a member of an active Pathway server class.
A requester can identify itself to such a process by formatting a message containing the
TCP system name and process name and the requester's name and passing the message
to the server process through a SEND statement. The server process can then use those
values in the UMP header of unsolicited messages to communicate with the requester.
Programs attempting to modify the content of either of these special registers are flagged
at compilation with the following message:
** ERROR 454 ** READ-ONLY SPECIAL REGISTER; MAY NOT BE ALTERED
These registers have the following implicit declarations. (The VALUE clauses are for
illustrative purposes only.)
PW-TCP-SYSTEM-NAME PIC X(8) VALUE "\STLOUIS".
PW-TCP-PROCESS-NAME PIC X(6) VALUE "$STCP".
The PW-USE-NEW-CURSOR Special Register
For all terminals supported by Pathway/iTS, except the 6510, information is displayed
on the screen without altering the location of the visible cursor. Terminals other than
the 6510 have a buffer pointer, independent of the visible cursor, whose value
determines where information is displayed on the screen; the visible cursor position is
altered separately. Thus, when PW-USE-NEW-CURSOR is set to NO, the visible
cursor can be left unchanged.
The 6510 visible cursor functions as both a user next-character marker and a buffer
pointer; consequently, there is no way to avoid altering the cursor position when writing
to the screen on a 6510. Because of this, the PW-USE-NEW-CURSOR special register
has no effect on 6510 terminal operation. The TCP performs all I/O operations on a
6510 as if PW-USE-NEW-CURSOR had the YES value
You can use basically the same source code for program units of different terminal
types, changing only the terminal type in the Environment Division
For example, the following code is acceptable to either 6510 or other terminals:
For example, the following code is acceptable to any supported terminal:
SET NEW-CURSOR AT a-field.
MOVE "NO" TO PW-USE-NEW-CURSOR.
ACCEPT field names.