Filter
Top Products
If you customize the supplied control program, or write your own version, you
should note the following:
v Input:The first two fields of the parameter list are input-only fields and should not
be altered by your program.
v Output:The remaining fields on the parameter list are input/output or output only
fields, which you can use to specify attributes that override those of the model
definition.
v Some of the output fields in the parameter list are not applicable to mapsets or
partitionsets. CICS ignores any parameters you specify that are not applicable to
the type of object being installed.
v Any attributes you return to CICS in the parameter list are used to modify the
model definition, and CICS installs the modified definition. Once installed, the
definition can be modified normally using the EXEC CICS SET PROGRAM or
CEMT SET PROGRAM commands.
v If you modify your control program, you can make the new version available by
using the EXEC CICS SET PROGRAM NEWCOPY or CEMT SET PROGRAM
NEWCOPY command.
v You can discard definitions after they have been installed; they are reinstalled
when next referenced.
v You must ensure that the parameters you return to CICS are valid, and
consistent with other system attributes in your CICS region. For example:
– Do not return PGAC_LPA_YES on the PGAC_USE_LPA_COPY parameter if
CICS is running with the system initialization parameter LPA=NO.
– Do not return PGAC_USER_KEY (which is the default) on the
PGAC_EXECUTION_KEY parameter if the task for which your control
program is called is running with CICS-key task-lifetime storage.
You can determine the storage key for the task by testing the TASKDATAKEY
option in its transaction definition by means of the following EXEC CICS
commands:
- EXEC CICS ADDRESS EIB
- EXEC CICS INQUIRE TRANSACTION(eibtrans) TASKDATAKEY(...)
Important
When creating an autoinstalled program definition, CICS ignores the program
language specified on the model program definition. CICS determines the language
from the load module itself, when the autoinstalled program is invoked.
However, CICS does not deduce characteristics other than language from the load
module. These other program characteristics must be explicitly defined by the
autoinstall control program or by RDO. If your programs have varying
characteristics (varying AMODE or DATALOCATION requirements, for example),
you must be able to distinguish between the various types when using autoinstall.
You could do this by keeping a list of exceptions to the default characteristics, and
coding your autoinstall control program to refer to this list; or you might decide to
install explicit RDO definitions of the exceptions.
Resource definition
The autoinstall control program cannot itself be autoinstalled, nor can any program
it references. You must define a program resource definition in the CSD for the
control program and for any other programs it references. You must also ensure
these definitions are installed in the CICS region during startup by including the
Chapter 16. Writing a program to control autoinstall of programs 587