Load module packaging for target system implementation is an important consideration during the maintenance phase of the CA Gen application development life cycle. The load module definition determines the contents of each load module remote file. The control information is updated each time you change the load module packaging. Unless precautions are taken, an incorrect load module definition can overwrite a correct one on the target system once the remote file is transferred to the target system and processed.
Online load module packaging and member name assignment can be done in the encyclopedia using Host Construction. Packaging and member name information created in the encyclopedia is included when a subset is checked out. From CA Gen 8, online load module packaging and member name assignment can also be done in the Toolset using workstation construction and it will be uploaded and checked into the encyclopedia.
Cooperative load module packaging and member name assignment should be done in the Toolset using Workstation Construction. This packaging is always uploaded and checked in to the encyclopedia.
When creating a subset of the model for code generation, include all the elements necessary to regenerate a complete load module. To be sure that a subset includes all components of a load module, look at the packaging for that load module. Then, for each procedure step in the load module:
Important! The load module definition determines what is included in load module remote files. If you elect to generate and install only code changes, all of the elements of the load module that can be found by CA Gen are included in the remote file. Elements of a load module packaged having an associated Dynamically Link Packaging property set to Compatibility will only be included in the remote file when the option Process modules marked for Compatibility is selected.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|