Filter
Top Products
Faster startup times
Warm and emergency starts
If you are using program autoinstall
with cataloging
, restart times are similar to
those of restarting a CICS region that is not using program autoinstall. This is
because, in both cases, resource definitions are reinstalled from the catalog during
the restart. The definitions after the restart are those that existed before the system
was terminated.
If you are using autoinstall
without cataloging
, CICS restart times are improved
because CICS does not install definitions from the CICS global catalog. Instead,
definitions are autoinstalled as required whenever programs, mapsets, and
partitionsets are referenced following the restart.
See the
CICS Recovery and Restart Guide
for information on cataloging.
Initial and cold starts
Startup times are faster than for a region that does not use program autoinstall,
because program definitions are installed singly, as required, rather than all together
at startup.
Requirements for autoinstall
To use autoinstall with programs, mapsets, and partitionsets, you must:
1. Write a customized version of the autoinstall control program for programs,
DFHPGADX (unless the supplied version is entirely suitable for your purposes).
2. Specify the name of your control program on the PGAIEXIT system initialization
parameter (the default name is DFHPGADX), or on a SET SYSTEM
PROGAUTOEXIT command.
3. Make program autoinstall active by specifying 'ACTIVE' on the PGAIPGM
system initialization parameter (or by issuing a SET SYSTEM
PROGAUTOINST(AUTOACTIVE) command).
4. Specify whether you want autoinstalled program definitions to be recorded on
the CICS global catalog, on the PGAICTLG system initialization parameter (or
on a SET SYSTEM PROGAUTOCTLG command).
5. Include the DFHPGAIP resource definition group in your CICS startup grouplist.
DFHPGAIP (which is already included in the CICS-supplied startup list,
DFHLIST) contains the default program, mapset, and partitionset model
definitions passed to the autoinstall control program, and a definition of
DFHPGADX (that you may need to amend).
6. Create any additional program, mapset, and partitionset model definitions that
you need, and add this group to your startup grouplist.
7. If you want to log messages associated with program autoinstall, define the
CSPL transient data (TD) queue.
For information about coding system initialization parameters, see the
CICS System
Definition Guide
. For information about defining programs, mapsets, partitionsets,
and TD queues, see the
CICS Resource Definition Guide
.
the autoinstall control program for programs
542
CICS TS for OS/390: CICS Customization Guide