Server Guide
The packaging step generates a packaged image file. Upload this
packaged image as binary to MVS and place it in your MVS image library
(RECFM=FB, LRECL=80).
Edit ABT.V6R0M0.SABTJLIB(ABTCBLD) to build an executable CICS
Transaction Server load module from the packaged image file. In
ABTCBLD, find the correct PROC from the list below:
- ABTCMF1B
- Builds a "load from file" load module for a CICS single image.
ABTCMF1B creates a load module that points to a packaged image, so that the
load module needs to be built only once for each new application image.
See *** for more information.
- ABTCMF2B
- Builds a "load from file" load module for a CICS dependent image.
ABTCMF2B creates a load module that points to a packaged image, so that the
load module needs to be built only once for each new application image.
See *** for more information.
- ABTCMN1B
- Builds a statically linked load module for a CICS single image.
- ABTCMN2B
- Builds a statically linked load module for a CICS dependent image.
When using this procedure, you must first run the ABTCVM2B procedure for the
base image. ABTCMN2B executes the base image created by
ABTCVM2B.
- ABTCVM2B
- Builds a load module for a CICS base image.
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.
- For BASE, specify the member name of the base load module.
- For BASELIB, specify the data set containing the base load module.
- For IMAGE, specify the member name of the image you uploaded and resulting
load module.
- For INFILE, specify the data set where the packaged image resides.
- For OUTFILE, specify a data set available to CICS from which you can run
the application.
- For STAKDUMP, specify the data set to be used for a stack dump.
- For CLA, specify any command line arguments to be used with the
image. See IBM Smalltalk User's Guide for a description
of the valid command line arguments you can specify. You cannot specify
-iIMAGENAME or -lFILENAME.
- For PERFIS, specify either a 0, to turn off SMF event monitoring, or a 1,
to turn on SMF event monitoring. See the appropriate Program Directory
for more information about the SMF records and the event monitoring points
that will be monitored. This switch is used to activate Smalltalk
product-specific SMF record generation. If you are using the
setTracePoint:forEntry: method to record a user-defined
monitoring point, you do not need to turn this switch on.
- 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 MVS,
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:
- A programmer packages and uploads a single image called MYSAMPLE.
- The programmer uses the procedure ABTCMN1B to build a load module for the
packaged image MYSAMPLE.
- The programmer can then define, install, and test MYSAMPLE.
- The programmer returns to the workstation and makes changes to MYSAMPLE,
based on testing.
- The programmer repackages the application and uploads it to MVS as a
packaged image again. The load module MYSAMPLE contains the old
application.
- The programmer must run the JCL to rebuild the load module for
MYSAMPLE.
- The programmer can now test MYSAMPLE again.
Now, consider this example:
- A programmer packages and uploads a single image called MYSAMPLE.
- The programmer uses the procedure ABTCMF1B to build a load module for the
packaged image MYSAMPLE. The load module created by this job step
points to the packaged image.
- The programmer can then define, install, and test MYSAMPLE.
- The programmer returns to the workstation and makes changes to MYSAMPLE,
based on testing.
- The programmer repackages the application and uploads it to MVS as a
packaged image again. The load module is still pointing to MYSAMPLE,
but MYSAMPLE is now the new application.
- The programmer can test MYSAMPLE again without rebuilding the load
module.
Using these procedures for each new packaged application image allows you
to forego the build step when you repackage the same application.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]