Establishing Multiple Environments › Transporting Entities

Transporting Entities

There are three mechanisms used for transporting CA Ideal entities between environments.

• Source transport-Used to move programs, panels, reports, unmodeled dataviews and members. It creates (or updates) dictionary entries at the receiving end.
• Object transport-Used to move programs and their corresponding panels between environments. The programs must be in PROD status. It does not update the dictionary.
• Load modules may also be moved and identified to the dictionary in the receiving environment.
• Panels are both source and object, so they can be moved by both Source and Object transport; it is important to note the differences between the two methods. When a panel is used in a RUN, the date is checked against the value compiled into the program using it, and a discrepancy will end the run immediately. This is done to prevent buffer overruns which could result from the panel size changing.
• Source transport creates a new panel on the target environment, with a changed date of last modification. Object transport creates an exact copy of the panel, retaining the original date of last modification. This means that a panel transported as source cannot be used until the program is recompiled, so if both source and object transport are used, either the panels should only be included in the object transport, or the object should be transported after the source.
• Note: HELP panels may remain in TEST status for the convenience of future text updates. Use Source Transport instead of Object Transport to move TEST status HELP panels into production environments. The HELP panels left in TEST status must remain in VLS format even if the rest of the production application is in load module format.