Runtime for ClearPath OS 2200 Software Release Announcement

Migration Requirements
Preserve Session Data
The option to “Preserve Session Data” is no longer ignored when migrating data to
Runtime 31RA, as this option controls the S_T_N Records in Memory feature.
Consequently LINC 16R3 session data may be lost in migration. See “Runtime
Development Enhancements” on page 4–5.
Reference Material
Refer to the following documentation for more detailed information:
• Unisys e-@ction Enterprise Application Runtime for ClearPath OS 2200 Installation
and Configuration Guide for complete procedures on migrating your OS 2200 based
LINC 16R3 applications and application data.The various migration issues are outlined
in “Addressing Migration Issues”in this guide.
• Unisys e-@ction Enterprise Application Developer Installation and Configuration Guide
for information on extracting your 3R1A Application Model.
• Unisys e-@ction Enterprise Application Developer 3.1A Administration Guide, for
information on loading your Enterprise Application Model.
• RDMS documentation for detailed information about the RDMS utilities.
Migrating from 2200-based LINC Deployment 16R3
Having completed all pre-migration tasks, migrating your application and data from the
16R3 environment to the new 3R1A environment, involves the following steps:
1. Extract and Load
To extract your Specifications from release 16R3 and load them into release 3R1A,
use either:
• LCOPY
or
• CASE LOAD, but this will take longer than LCOPY.
2. Syntax-only and System Generate
After copying your Specification to release 3R1A, it is recommended that you:
• Perform a syntax-only generate of your System, with “Stop on first error” set to
N, before you generate the new System.
• When the database environment has been set up, use Host Builder 3R1A for
ClearPath OS 2200 to generate and deploy your Systems to the Runtime 3R1A
for ClearPath OS 2200 host.
If you wish to migrate LINC 16R2, you will first have to migrate to LINC 16R3 first.
3–2 78616414–000