CRE Programmer's Guide

Using the Common Language Utility (CLU) Library
Common Run-Time Environment (CRE) Programmer’s Guide—528146-004
5-2
Compiling and Binding or Linking Programs That
Use the CLU Library
Compiling and Binding or Linking Programs
That Use the CLU Library
For the TNS CRE, you must explicitly bind into your program’s object file all CLU
functions referenced by your program. To bind the CLU functions into your object file,
specify the following Binder command:
SELECT SEARCH $SYSTEM.SYSTEM.CLULIB
To call CLU functions directly, TAL routines must also source-in CLUDECS, the
external declarations file for the CLU functions. CLUDECS is located in
$SYSTEM.SYSTEM by default.
For the TNS/R or TNS/E CRE, pTAL routines must source in CLURDECS, a file
located by default in $SYSTEM.SYSTEM.
ECOBOL and NMCOBOL programs can call only the Saved Message Utility functions
listed in Table 5-2
on page 5-3. These functions are in the library file ZCRESRL on
G-series systems and ZCREDLL on H-series systems.
Creating Processes
To create a process, routines can use the CLU_Process_Create_ function. Using this
function, a process is created using the conventions of the TACL RUN command. This
function is available to any CRE program and to COBOL or FORTRAN programs
compiled for execution in a non-CRE environment—that is, with ENV OLD specified or
assumed by default. See the definition of this routine in Section 9, Common Language
Utility (CLU) Library Functions, for more details.
Locating and Identifying File Connectors
A file connector is an abstract entity through which a program accesses a file. It is
physically represented by a run-time data object called a File Control Block (FCB).
Each file connector has a logical file name and a physical file name (called the
Guardian file name or TANDEMNAME).
To locate and identify file connectors, COBOL and FORTRAN routines can use the
CLU_Process_File_Name_ function. Using this function, your routine can locate a file
connector, obtain its identity, and optionally alter the Guardian file name value. See the
definition of this routine in Section 9, Common Language Utility (CLU) Library
Functions, for more details.
The native CRE does not support functions that locate and identify file connectors.
Using the Saved Message Utility Functions
The Saved Message Utility (SMU) functions listed in Table 5-2 on page 5-3 enable
routines to manipulate saved startup, ASSIGN, and PARAM messages that are sent to