Packaging › Basic Packaging Activities › Defining Load Modules › Add Procedure Steps

Add Procedure Steps

Select the procedure steps to be packaged in each load module from the list of all the unpackaged procedure steps defined for the business system. You do not explicitly package action blocks. By adding procedure steps to your load module, all action blocks used by the procedure step are also included in the load module by CA Gen, as well as all action blocks used by the action blocks.

• GUI Applications

  All procedure steps must be packaged into one or more load modules.

• Client Server Applications

  Procedure steps are packaged according to load module types. The load module types are server manager for the server procedures and window manager for the client procedures.

  For the server manager load module type, only the procedure steps that are online, with no display, appear in the list of all the unpackaged procedure steps defined for the business system.

  For the window manager load module type, the procedure steps that are to be packaged in window load modules are usually online with display.

  For the most part, flow definitions for a client server design are dependent on packaging options. That is, when you create a Dialog Flow Diagram, you do need to consider which procedures you will package as clients and which procedures you will package as servers. Therefore, cooperative packaging for client server applications tends to be dictated by the Dialog Flow Diagram.

• Batch Applications

  Flow definitions for batch procedure steps are limited to sequential transfers from one procedure step to the next, with no returns to prior procedure steps. Each batch procedure step must be packaged into a separate load module.

• Online Applications

  Flow definitions for online applications are independent of packaging options. That is, when you create a DLG, you do not need to consider how the procedures will be packaged. Conversely, packaging is not dictated by the dialog flow. However, an application runs most efficiently when each load module contains procedure steps that are to be used together.

• Components

  A collection of transactional or sub transactional operations are grouped together in CBD packaging. This collection, called an Operations Library, is packaged into a DLL or a shared library, which in turn is linked to (consumed by) one or more applications.