A Strategy to Avoid
Job
XYZ Activation Group
CL *MODULE(X1)
RPG *MODULE(X2)
C *MODULE(Z1)
CL *MODULE(Z2)
*PGM(X)
*SRVPGM(Y)
*SRVPGM(Z)
RPG
Figure 10. Advanced Application
The calls from program X to service programs Y and Z are static calls.
See “Effect of ILE” on page 26 for details on the effects of ILE on the way your
application handles calls, data, files and errors.
Related Information
Two-step creation process Chapter 7, “Creating a Program with the
CRTRPGMOD and CRTPGM Commands”
on page 73
Activation groups “Managing Activation Groups” on page 109
ILE static binding Chapter 10, “Calling Programs and
Procedures” on page 127; also
ILE Con-
cepts
Exception Handling Chapter 12, “Handling Exceptions” on
page 217; also
ILE Concepts
Service programs Chapter 8, “Creating a Service Program” on
page 91; also
ILE Concepts
Updating a Program “Using the UPDPGM Command” on
page 87
A Strategy to Avoid
ILE provides many alternatives for creating programs and applications. However,
not all are equally good. In general, you should avoid a situation where an applica-
tion consisting of OPM and ILE programs is split across the OPM default activation
group and a named activation group. In other words, try to avoid the scenario
shown in Figure 11 on page 32.
Chapter 3. Program Creation Strategies 31
