NET/MASTER Network Control Language (NCL) Reference Manual

CALL
Core Statements
106126 Tandem Computers Incorporated 2–7
Considerations
If the called procedure is not found, NCL generates a LOADFAIL_ERROR. If the
FINDRC operand of the CONTROL verb is specified, and a called procedure is not
found, NCL sets an error return code of 100 in the &SYS.RETCODE system
variable instead of generating the error. See Section 3, “Verbs,” for a description of
the CONTROL verb. The LOADFAIL_ERROR indicates a failure to load a
procedure or function. See the ON core statement, later in this section, to find out
how to trap or intercept errors.
The called procedure can overwrite whatever was displayed by the calling
procedure. This can happen if the called procedure and the caller share access to
an Operator Control Services (OCS) window.
See Section 5, “System Variables,” for a description of the &SYS.PARMCNT
system variable, that contains the number of arguments provided to an NCL
procedure.
For a full discussion of the sharing of variables between NCL procedures and
functions, refer to the NonStop NET/MASTER NCL Programmer's Guide.
See also the CONTROL verb in Section 3, “Verbs.” The CONTROL operands
SHRVARS/NOSHRVARS and FINDRC/NOFINDRC can affect the performance
of CALL.
See also DO, GOSUB, ON, PROCEDURE, and RETURN. These core statements
can affect the sharing of variables and the nesting of callable DO groups, ON
blocks, and procedures.
Example
The following example calls a procedure (PROC002) and passes the variables &A, &B,
and &C as arguments to it. The variables &VAR1 and &REC are shared:
CALL PROC002 (&A,&B,&C) SHARE &VAR1, &REC