Filter
Top Products
Using an autoinstall control program
If you choose to have your autoinstall control program invoked for consoles, follow
these steps:
v Use the default autoinstall control program for terminals (DFHZATDX or
DFHZATDY), or write your own program, using the source code of the default
program and the customization examples in this chapter as a basis.
Notes:
1. If you use a VS COBOL II or later COBOL compiler to compile your
autoinstall control program (or to compile the sample COBOL version,
DFHZCTDX) run the program under Language Environment for MVS.
2. You can have only one active autoinstall control program to handle terminals,
consoles, and APPC connections. You specify the name of the active
program on the AIEXIT system initialization parameter.
3. Your autoinstall program must be able to recognise the console INSTALL and
DELETE parameter lists and return a model name, termid and return code.
v Enable the CICS AUTOINSTALL function for consoles. You can do this either by
specifying AICONS=YES as a system initialization parameter, or by issuing a
SET AUTOINSTALL CONSOLES(PROGAUTO) command.
v Specify the AIEXIT system initialization parameter to define your autoinstall
control program to CICS.
If AICONS=YES is specified, or a CEMT (or EXEC CICS) SET AUTOINSTALL
CONSOLES(PROGAUTO) has been issued, CICS invokes your autoinstall control
program when:
v An autoinstall INSTALL request is being processed.
v An autoinstall request has previously been accepted by the autoinstall control
program, but the subsequent INSTALL process has failed.
v The delay period since the console was last used has elapsed.
The autoinstall control program at INSTALL
If autoinstall is operative, you can specify that CICS is to invoke the autoinstall
control program for MVS consoles, in addition to those devices listed on page 487.
To enable CICS to invoke the autoinstall control program for consoles, specify
AICONS=YES as a system initialization parameter, or issue a SET AUTOINSTALL
CONSOLES(PROGAUTO) command.
On each invocation of the autoinstall control program, CICS passes a parameter list
to the control program by means of a communication area addressed by
DFHEICAP. This section describes only the install function of console definitions.
The control program is invoked at INSTALL for a console when:
v CICS has received a MODIFY command from an MVS console whose console
name or console id is not defined in the TCT.
v CICS has completed autoinstall processing to a point where it needs a terminal
identifier and autoinstall model name, from the autoinstall control program, in
order to process the CICS transaction passed on the MVS modify command.
the autoinstall control program for consoles
506
CICS TS for OS/390: CICS Customization Guide
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|