IBM SC34-6814-04 - Manual (Page 10)

Coding for specific VTAM sense codes . . . . . . . . . . . . . . 508
Writing multiple NEPs . . . . . . . . . . . . . . . . . . . . . 508
DFHZNEPI macros . . . . . . . . . . . . . . . . . . . . . . 508
Handling shutdown hung terminals in the node error program . . . . . . 510
Using the node error program with XRF or persistent sessions . . . . . . . 510
The node error program in an XRF environment . . . . . . . . . . . 510
The node error program with persistent session support . . . . . . . . 511
Changing the recovery notification . . . . . . . . . . . . . . . . 511
Changing the recovery message . . . . . . . . . . . . . . . . . 512
Changing the recovery transaction . . . . . . . . . . . . . . . . 512
Using the node error program with VTAM generic resources. . . . . . . . 512
Chapter 10. Writing a program to control autoinstall of terminals . . . . 515
Autoinstalling terminals—preliminary considerations . . . . . . . . . . . 515
Coding entries in the VTAM LOGON mode table . . . . . . . . . . . 516
Using model terminal support (MTS)
. . . . . . . . . . . . . . . 516
The autoinstall control program for terminals . . . . . . . . . . . . 517
The autoinstall control program at INSTALL . . . . . . . . . . . . . . 517
The communication area at INSTALL for terminals . . . . . . . . . . 518
How CICS builds the list of autoinstall models . . . . . . . . . . . . 519
Returning information to CICS . . . . . . . . . . . . . . . . . . 520
CICS action on return from the control program . . . . . . . . . . . 523
The autoinstall control program at DELETE . . . . . . . . . . . . . . 525
The communication area at DELETE for terminals . . . . . . . . . . 525
Naming, testing, and debugging your autoinstall control program . . . . . . 526
Finding the name of an autoinstall control program . . . . . . . . . . 526
Testing and debugging
. . . . . . . . . . . . . . . . . . . . 526
The sample autoinstall control programs for terminals . . . . . . . . . . 527
Customizing the sample program. . . . . . . . . . . . . . . . . 528
Chapter 11. Writing a program to control autoinstall of consoles . . . . 535
Autoinstalling consoles—preliminary considerations . . . . . . . . . . . 535
Leaving it all to CICS . . . . . . . . . . . . . . . . . . . . . 535
Using an autoinstall control program
. . . . . . . . . . . . . . . 535
The autoinstall control program at INSTALL . . . . . . . . . . . . . . 536
The communication area at INSTALL for consoles . . . . . . . . . . 536
How CICS builds the list of autoinstall models . . . . . . . . . . . . 538
Returning information to CICS . . . . . . . . . . . . . . . . . . 538
CICS action on return from the control program . . . . . . . . . . . 540
The autoinstall control program at DELETE . . . . . . . . . . . . . . 540
The sample autoinstall control programs for consoles . . . . . . . . . . 541
Chapter 12. Writing a program to control autoinstall of APPC connections 543
Autoinstalling APPC connections—preliminary considerations . . . . . . . 543
Local APPC single-session connections initiated by CINIT . . . . . . . 543
Local APPC parallel-session and single-session connections initiated by
BIND . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Autoinstall templates for APPC connections . . . . . . . . . . . . . 544
Benefits of autoinstall . . . . . . . . . . . . . . . . . . . . . 544
Requirements for autoinstall
. . . . . . . . . . . . . . . . . . 544
The autoinstall control program for APPC connections . . . . . . . . . 545
Recovery and restart . . . . . . . . . . . . . . . . . . . . . 545
The autoinstall control program at INSTALL . . . . . . . . . . . . . . 545
The communication area at INSTALL for APPC connections . . . . . . . 545
The autoinstall control program at DELETE . . . . . . . . . . . . . . 549
When autoinstalled APPC connections are deleted . . . . . . . . . . 549
viii Customization Guide