Documentation and test plans

During internal design, consider how to document and test the defined recovery and restart programs, exits, and procedures.

Recovery and restart programs and procedures usually relate to exceptional conditions, and can therefore be more difficult to test than those that handle normal conditions. However, they should be tested as far as possible, to ensure that they handle the functions for which they are designed.

CICS® facilities, such as the execution diagnostic facility (CEDF) and command interpreter (CECI), can help to create exception conditions and to interpret program and system reactions to those conditions.

The installed CICS system, application programs, operators, and terminal users must be able to cope with exception conditions. Therefore, the designer and implementer need to forecast the exceptional conditions that can be expected, and then document the operator and user actions in the process of recovery. Documentation should include escape procedures for problems or errors that persist.

Conditions that need documented procedures include the following:
  • Power failure in the processor
  • Failure of CICS
  • Physical failure of data sets
  • Transaction abends
  • Communication failures, such as the loss of telephone lines, or a printer that is out of service
  • Shunted units of work that are caused by communication or backout failures

It is essential that recovery and restart procedures are tested and rehearsed in a controlled environment by everyone who might have to cope with a failure. This is especially important in installations that have temporary operators.



dfht2kt.html | Timestamp icon Last updated: Monday, 5 June 2017