18.08.2013 Views

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

LINC Programming Reference Manual - Public Support Login - Unisys

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Introduction<br />

CALL<br />

For MCP based target hosts, using the BYFUNCTION; option with the CALL; command<br />

gives you access to common user libraries that have been installed using the SL system<br />

command. You do not have to embed the title of the library in the CALL; command that you<br />

use to access the libraries. Instead, your user-defined System Library names (as used in SL<br />

commands) can be used in the CALL; command, to identify the required library.<br />

For each of the library programs you want to access in this way, you must code an<br />

additional CALL; command that serves only to identify the library as called by function.<br />

This command is required once within each <strong>LINC</strong> Subsystem in which there is a CALL;<br />

command to a particular library, and once within each Report that calls that library.<br />

The initialization code associated with the command is unconditionally executed.<br />

Therefore, the Ispec or Global Logic containing the code does not need to be invoked to<br />

begin execution. The Ispec or Global Logic does, however, need to be included as part of<br />

your <strong>LINC</strong> System (or in a module of your <strong>LINC</strong> System).<br />

Reasons for Using BYFUNCTION; Command Option<br />

Reasons to use the BYFUNCTION; command option with the CALL; command are:<br />

$ You do not need to embed the Library title, including pack name, in your logic.<br />

$ You are not required to specify a usercode with the library name.<br />

Using the BYFUNCTION; Command Option<br />

In Reports, the BYFUNCTION; command option with the CALL; command is only valid in<br />

Main Logic (Frame 00). The actual CALL; commands can be anywhere in Report logic.<br />

If the command is included within your <strong>LINC</strong> Logic more than once (for example, because<br />

of Inserted Global Logics), then the initialization will be generated for each occurrence.<br />

Also, whenever a BYFUNCTION; command option is inserted, edited, or deleted,<br />

(including LCOPY operations), all Subsystems of the <strong>LINC</strong> Specification are regenerated<br />

when the <strong>LINC</strong> Specification is next generated.<br />

This creates overhead; thus it is recommended that you place this command in a standard<br />

location in your <strong>LINC</strong> Specification - for example, CLOSEDOWN Global Logic, where<br />

accidental maintenance can be avoided or minimized.<br />

Note: You must ensure that the libraries you call by function are first declared as<br />

System Libraries by using the SL command. If this is not done on site, the<br />

<strong>LINC</strong> program will be suspended, waiting for the library.<br />

When you wish to make changes to the functions of an SL library, you should consult with<br />

other users of the System Library, to prevent conflicting requirements.<br />

v 1-57

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!