Preprocessing, Compiling, and Linking

COOL Messages and CICS Applications

When you use COOL to link a CICS application, you receive COOL messages noting the missing CICS Execution Interface stubs. Under CMS, you receive the following messages:

LSCL102  Warning: Can't open file during autocall: %TXTLIB(DFHEI1)
LSCL102  Warning: Can't open file during autocall: %TXTLIB(DFHEAI)
LSCL102  Warning: Can't open file during autocall: %TXTLIB(DFHEAI0)

Under OS/390, you receive similar messages that refer to members of the SYSLIB library (instead of the CMS TXTLIB library). These messages are expected; the output object file from COOL must subsequently be linked with the CICS Execution Interface stubs. This subsequent link must be performed under OS/390, which means that if you are running under CMS, your output file (COOL370 TEXT) must be transmitted to an OS/390 system before it can be linked with the CICS Execution Interface stubs.

Note: Because final link-editing with the CICS execution interface stubs must be performed on the target operating system, if your application is targeted for a CICS/VSE system, refer to the next section. [cautionend]

Chapter Contents
Previous
Next
Top of Page