LINC Programming Reference Manual - Public Support Login - Unisys

SWITCH.TO (SWT)
Syntax
$ On UNIX and MCP based LINC Systems, you cannot switch to the LINC Report Output
Control System (ROC) or LINC Ad Hoc Inquiry Utility. Use the ROC.MODE; or
ADHOC.MODE; commands instead.
$ On OS 2200 based LINC Systems you can switch to the LINC Report Output Control
System (ROC).
$ For an MCP based LINC System you cannot use the DATA; command option when
switching to a LINC Release 15 System.
The SWITCH.TO; command has the following syntax:
DD DD DBDDDDDDDDDDDDDDDDDDDDDDBDDDDDDDDDDDDDD
3 3
@D DD DY
DBDDDDDDDDDDDDDDDDDDDDDDDDBDBDDDDDDBDBDDDDDDDDBDBDDDDDDDDDDBDD4
3 33 33 33 3
@ D Y@ Y@ Y@ Y
system
An alphanumeric data item or literal specifying the destination system, as follows:
$ For an MCP based LINC System, a valid window name, or an asterisk (*) for the
default window name.
$ For an OS 2200 based LINC System, a valid transaction id.
$ For a UNIX LINC System, the name of the LINC Database for the target LINC System.
If you enter an invalid system name, the current screen of your sending LINC System is
displayed with a message informing you of the unavailability of the target system.
DATA; data name
Specifies an alphanumeric data item or literal whose value is to be passed to the target
LINC System. Up to 1850 characters (1884 on UNIX LINC Systems) may be passed. DATA
may be abbreviated as DA.
$ If the first 5 characters of the data make up the name of a valid Ispec, and are followed
by data in NOF format, normal Pre-LINC and Main Logic of that Ispec is performed.
NOF format in MCP and OS 2200 environments is defined by the LINCOFF file, while
on UNIX LINC Systems it is defined by the LINCNOF file. See your UNIX LINC
Administration and Operations Guide for details of creating the LINCNOF file.
$ If the first 5 characters of the data make up the name of a valid Ispec, and the sixth
character is not a T, normal Pre-Screen logic of that Ispec is performed.
1-250 v