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.

LDA Syntax<br />

Caution<br />

If the EXTERNAL; command option is used, the called routine must not attempt to<br />

read from or write to the terminal.<br />

CALL<br />

The value of the System Data item GLB.PARAM is used as an argument to this process.<br />

GLB.PARAM is also used to return data, as described previously for the data name 2 value.<br />

DDDD DDD DDD DDDDDD4<br />

literal 1<br />

The name of your function (routine), up to 18 characters long.<br />

literal 2<br />

An alphanumeric Literal value of up to 18 characters containing the DOS pathname of your<br />

DLL. In cases where the DLL pathname is longer than 18 characters, open a DOS session<br />

and execute the following DOS command to associate the long path with a drive letter,<br />

before executing this <strong>LINC</strong> command. For example:<br />

<br />

If literal 2 does not include a period (.) then LDA will automatically append the suffix<br />

‘‘.DLL’’. Because the period character causes an error in an MCP based COBOL compile,<br />

you should leave the addition of the ‘‘.DLL’’ suffix to LDA. For example:<br />

<br />

willbeconvertedinLDARunTimeto:<br />

<br />

Note: The GLB.PARAM parameter is a character buffer. Numeric fields (like alpha<br />

fields) can be passed by using the ATTACH; Logic command or the DETACH;<br />

Logic command to add or remove them from GLB.PARAM, respectively.<br />

Using the CALL; Command in LDA<br />

The CALL; command provides an interface to non-<strong>LINC</strong> routines that are held in a Dynamic<br />

Link Library (DLL). It is your responsibility to ensure that the DLL being called exists.<br />

Each CALL to the same DLL will cause the DLL to be loaded; therefore, do not assume that<br />

values set within the DLL in a previous CALL; of the Library will be retained for the current<br />

CALL;.<br />

v 1-55

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

Saved successfully!

Ooh no, something went wrong!