A single load module configuration exists when all the classes and applications are packaged together into an image that will be converted into a single, executable load module.
The figure belows shows a single image configuration for a packaged
application that will run on MVS. The Smalltalk virtual machine exists
as its own load module, and your single load module dynamically links to the
Smalltalk virtual machine at program load time.
Though your packaged server image must be deployed with the VisualAge Smalltalk Server feature, you can test your packaged image using files provided by the VisualAge Smalltalk Server Workbench feature, as most runtime files are included with the Server Workbench to allow for testing and debugging.
The procedure below describes how to package your image as a single module.