Because CA Culprit system programs are written in the Assembler, each invocation of a COBOL program is normally treated as an entry into a main program. Special procedures must be used in order for the COBOL program to act as a subroutine. This is necessary, for example, if a file is opened on the first call to the COBOL program and that file is accessed in subsequent calls.
Use either of two methods shown below to establish linkage to a COBOL procedure module. Use method 2 to establish linkage to a COBOL input or output module.
METHOD 1: Call CULLUS00 as documented in The Universal Interface (CULLUS00). CULLUS00 will automatically create the COBOL environment before calling the target procedure module. Since CULLUS00 is only used for calling procedure modules, this method will not work for input or output modules.
If this method is used, the target procedure module can be linked with any desired AMODE or RMODE under z/OS, z/VM or z/VSE operating systems. If running under IBM Language Environment, the procedure module must be linked AMODE(31).
METHOD 2: Calling the COBOL module directly. This method can be used with modules compiled under VS COBOL, VS COBOL II, LE-compliant COBOL compilers (such as COBOL for and z/VM or COBOL/VSE) COBOL. To implement this method, perform the following steps:
where CEEUOPT names a file that contains a CEEUOPT module which was compiled specifying RTEREUS=YES.
Note:
where IGZEOPT names a file which contains an IGZEOPT module which was compiled specifying RTEREUS=YES. See the VS COBOL II Application Programming Guide for information on creating an application-specific version of IGZEOPT.
Copyright © 2014 CA.
All rights reserved.
|
|