When migrating your existing OPM COBOL/400 programs and applications to ILE COBOL,
the following migration strategy is recommended:
Migrate an entire application (or COBOL run unit) at one time to a pure ILE environment
instead of migrating one program at a time.
Map a COBOL run unit to an ILE activation group. For example, for
a COBOL run unit that contains a number of COBOL programs, you can do
one of the following to preserve the COBOL run unit semantics:
Create all of the COBOL programs using the CRTBNDCBL command. In this
case, all of the programs will run in the QILE activation group.
Create all of the COBOL programs using the CRTCBLMOD command followed
by CRTPGM with ACTGRP(anyname). In this case, all of the programs will run
in the activation group named "anyname".
Create the first COBOL program with ACTGRP(*NEW) using the CRTPGM command
and create the rest of the programs in the application with ACTGRP(*CALLER).
In this case, all of the programs will run in the *NEW activation group of
the first COBOL program.
Ensure that the caller of programs created with the ACTGRP(*CALLER) option
on the CRTPGM command are not OPM programs.
Note:
Mixing OPM COBOL/400 and ILE COBOL programs
in the same run unit is not recommended.
Pay special attention to system functions that allow different scoping
options. For example, default scoping of the following system functions is
changed to *ACTGRPDFN (the activation group level) when used in an ILE activation
group whereas they have other defaults, such as *CALLLVL (the call level),
when used in OPM programs.
For OPNDBF and OPNQRYF, you may need to change OPNSCOPE depending on the
application. For example, if the application is running in different activation
groups and need to share files, you will need to change the scope to *JOB.
Overrides.
Commitment Control.
RCLRSRC has no effect on ILE activation groups. Instead, use RCLACTGRP
to clean up ILE activation groups.
(C) Copyright IBM Corporation 1992, 2006. All Rights Reserved.