Use the ABTBMF1B or ABTBMF2B 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 ABTBMN1B or ABTBMN2B procedure, which incorporates the entire image into the load module, for better performance.
Like the ABTBMN1B or ABTBMN2B procedure that builds a load module from a packaged image, ABTBMF1B or ABTBMF2B produces a load module in your load module library. Unlike the other procedures, the load module created by ABTBMF1B or ABTBMF2B 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 module 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.
Your packaged image must reside in an image library defined by your system programmer. See Obtaining information about an OS/390 load module to determine the characteristics of the image library setup by the system programmer.
You can use the ABTBMF1B or ABTBMF2B procedure to build load modules of single images.
Consider the following example:
Now, consider this example:
Using ABTBMF1B or ABTBMF2B for each new packaged application image allows you to forego the build step when you repackage the same application.