IBM SC33-1683-02 - Manual (Page 11)

Rewriting user-replaceable programs . . . . . . . . . . . . . . . . 401
Assembling and link-editing user-replaceable programs. . . . . . . . . . 402
User-replaceable programs and the storage protection facility . . . . . . . 405
Execution key for user-replaceable programs . . . . . . . . . . . . 405
Data storage key for user-replaceable programs . . . . . . . . . . . 406
Chapter 6. Writing a program error program. . . . . . . . . . . . . 407
The sample programs and copy books . . . . . . . . . . . . . . . . 410
Chapter 7. Writing a transaction restart program . . . . . . . . . . . 411
The DFHREST communications area . . . . . . . . . . . . . . . . 412
The CICS-supplied transaction restart program. . . . . . . . . . . . . 414
Chapter 8. Writing a terminal error program . . . . . . . . . . . . . 415
Background to error handling for TCAM and sequential devices
. . . . . . 415
When an abnormal condition occurs. . . . . . . . . . . . . . . . 416
Terminal control program . . . . . . . . . . . . . . . . . . . . 416
Terminal abnormal condition program . . . . . . . . . . . . . . . 416
Terminal error program
. . . . . . . . . . . . . . . . . . . . 416
The communication area . . . . . . . . . . . . . . . . . . . . 417
Terminal abnormal condition line entry (TACLE)
. . . . . . . . . . . 417
The sample terminal error program . . . . . . . . . . . . . . . . . 417
Components of the sample terminal error program . . . . . . . . . . 418
Structure of the sample terminal error program . . . . . . . . . . . . 419
Sample terminal error program messages
. . . . . . . . . . . . . 423
Generating the sample terminal error program . . . . . . . . . . . . 425
User-written terminal error programs . . . . . . . . . . . . . . . . 437
Why write your own terminal error program? . . . . . . . . . . . . 438
Restrictions on the use of EXEC CICS commands . . . . . . . . . . 438
Addressing the contents of the communication area . . . . . . . . . . 438
Addressing the contents of the TACLE . . . . . . . . . . . . . . . 441
Example of a user-written terminal error program . . . . . . . . . . . 445
Chapter 9. Writing a node error program . . . . . . . . . . . . . . 449
Background to CICS-VTAM error handling
. . . . . . . . . . . . . . 450
Why use a NEP to supplement CICS default actions? . . . . . . . . . 450
An overview of writing a NEP . . . . . . . . . . . . . . . . . . 451
The default NEP . . . . . . . . . . . . . . . . . . . . . . . 452
The sample NEP . . . . . . . . . . . . . . . . . . . . . . . 452
Multiple NEPs . . . . . . . . . . . . . . . . . . . . . . . . 455
When an abnormal condition occurs. . . . . . . . . . . . . . . . . 457
The communication area . . . . . . . . . . . . . . . . . . . . 458
The sample node error program . . . . . . . . . . . . . . . . . . 465
Compatibility with the sample terminal error program . . . . . . . . . 466
Components of the sample node error program . . . . . . . . . . . 466
Generating the sample node error program . . . . . . . . . . . . . 469
User-written node error programs. . . . . . . . . . . . . . . . . . 475
Restrictions on the use of EXEC CICS commands . . . . . . . . . . 475
Entry and addressability . . . . . . . . . . . . . . . . . . . . 476
Coding for the 3270 ‘unavailable printer’ condition
. . . . . . . . . . 476
Coding for session failures . . . . . . . . . . . . . . . . . . . 477
Coding for specific VTAM sense codes. . . . . . . . . . . . . . . 478
Writing multiple NEPs . . . . . . . . . . . . . . . . . . . . . 478
DFHZNEPI macros . . . . . . . . . . . . . . . . . . . . . . 478
Handling shutdown hung terminals in the node error program . . . . . . 480
Using the node error program with XRF or persistent sessions . . . . . . . 480
Contents ix