The packaging step generates a packaged image file. Upload this packaged image as binary to OS/390 and place it in your OS/390 image library (RECFM=FB, LRECL=80).
Edit ABT.V4R5M0.SABTJLIB(ABTCBLD) to build an executable CICS/ESA load module from the packaged image file. In ABTCBLD, find the correct PROC from the list below:
Remove the comments from all the parameters for the specified proc and provide the information requested. Note that the following parameters are not required for all the procedures.
Note: | Turning on performance monitoring increases the overhead for the job. |
Submit the JCL. The module produced is not different from any other C or COBOL CICS load module. If you receive an error while building the load module, see Appendix A, Messages and codes for more information.
Building a load module using the ABTCMF1B or ABTCMF2B procedure
Run the ABTCMF1B or ABTCMF2B procedure against each new application image only once. Once a load module is created for an application image, you can skip this step.
Use the ABTCMF1B or ABTCMF2B procedure during development to test your applications quickly, without needing to run JCL to build a load module from the packaged image. For a production library, however, use the other procedures, which incorporate the entire image into the load module, for better performance.
WARNING: When storage protection is active on a CICS region (SIT STGPROT=YES) and you intend to use these procedures, the CICS program definition (PPT) for your application program must specify EXECKEY=CICS. Because the ABTCMF1B and ABTCMF2B procedures are not considered appropriate for applications in production use, we recommend that you fully test your application with the ABTCMN1B or ABTCMN2B procedure with an EXECKEY=USER prior to implementing an application in production mode.
Like the other procedures that build a load module from a packaged image, ABTCMF1B and ABTCMF2B produce a load module in your load module library. Unlike the other procedures, the load module created by ABTCMF1B or ABTCMF2B contains only a pointer to the packaged image in an image library. This pointer allows you to repackage the application image without the need to build a load module from it. This is called a "load from file" load module.
The load module created will always have the same name as the packaged image and will always point to that image in the image library. The application image can be repackaged from the workstation and uploaded to OS/390, then run without having to rebuild a load module. In this way, the ABTCMF1B and ABTCMF2B procedures resemble the ABTVBLD program used to produce a DLL for CICS on the workstation.
Your packaged image must reside in an image library defined by your system programmer. See Obtaining information about a CICS load module to determine the characteristics of the image library set up by the system programmer.
You can use the ABTCMF1B procedure to build load modules of single images; ABTCMF2B builds load modules of dependent images. Load modules of base images cannot be built for this type of processing.
Consider the following example:
Now, consider this example:
Using these procedures for each new packaged application image allows you to forego the build step when you repackage the same application.