Filter
Top Products
Chapter 15. Writing a program to control autoinstall of
programs
Considerations common to all user-replaceable programs
Note that the comments contained in “Chapter 5. General notes about
user-replaceable programs” on page 401 apply to this chapter.
This chapter describes the user-replaceable program that controls the automatic
installation of programs, mapsets, and partitionsets.
Note: In this chapter, the term “program autoinstall” is used to mean autoinstall of
all three program types (program, mapset, and partitionset) unless otherwise
specified.
The chapter is divided into the following sections:
1. “Preliminary considerations”
2. “Benefits of autoinstall” on page 541
3. “Requirements for autoinstall” on page 542
4. “The autoinstall control program at INSTALL” on page 543
5. “The sample autoinstall control program for programs, DFHPGADX” on
page 546.
Preliminary considerations
As well as terminals and APPC connections, you can autoinstall:
v User programs
v Mapsets
v Partitionsets.
If the autoinstall program function is enabled, and an implicit or explicit load request
is issued for a previously undefined program, mapset, or partitionset, CICS
dynamically creates a definition, and installs and catalogs it, as appropriate. An
implicit or explicit load occurs when:
v CICS starts a transaction.
v An application program issues one of the following commands:
EXEC CICS LINK—see “Autoinstalling programs invoked by EXEC CICS
LINK commands” on page 540
EXEC CICS XCTL
EXEC CICS LOAD
EXEC CICS ENABLE (for a global user exit, or task-related user exit,
program)
EXEC CICS RECEIVE or SEND MAP
EXEC CICS SEND PARTNSET
EXEC CICS RECEIVE PARTN.
v A program abend occurs, and CICS transfers control to the program named on
an EXEC CICS HANDLE ABEND command.
© Copyright IBM Corp. 1977, 1999 539
|
|