LINC Programming Reference Manual - Public Support Login - Unisys

CALL
Syntax
$ ‘‘Using BYFUNCTION; with the CALL; Command’’ (for MCP based LINC Systems),
later in this subsection
$ ‘‘Using Coroutines with the CALL; Command’’ (for MCP based LINC Systems), later in
this subsection
$ Your OS 2200 Based LINC Administration and Operations Guide (for OS 2200 based
LINC Systems)
$ The Interfaces section of your LINC Administration and Operations Guide for the
relevant host type
$ " CALL" in the LDA online help
Note: The syntax of the CALL; command is different for UNIX, MCP and OS 2200
based LINC Systems. The syntax for each host type is given separately in the
following subsections.
MCP Based Syntax
D B D BDBDDDDDDDDDDDDDDBDDBD4
3 33 3 3
CDDDDDD DD DDDDDY@ Y 3
3 3
@DDDDDDDDDD DDD DDDDDDDDDDY
literal 1
A literal value containing the Procedure name. For COBOL routines, this value is always
PROCEDUREDIVISION. The entry point identified by literal 1 is interpreted as being a
function provided by the System Library. The CALL; command passes the contents of
GLB.PARAM to that function, and causes the function to be performed.
literal 2
A literal value containing the name of the Library. Total length of literal 1 and 2 is not
greater than 50 characters
literal 3
The literal value is the name of the Library (up to 50 characters), and must be the same as
literal 2 in any CALL; commands that invoke functions in the Library.
In the MCP SL command, you must specify the actual file title associated with this value.
This parameter is ignored on other target host types.
For more information, see ‘‘Using BYFUNCTION; with the CALL; Command’’, later in this
section.
1-52 v