On the first occasion in an Adhoc_IT session that you attempt to execute a program and after any changes have been made to the Library List, TestBench will execute a Pre-Check. This will be identical to the way that a Test Case is pre-checked if the Data Protection has been set to the program (*PGM) level. (For a full description of this process please refer to the Test Data Protection, Analysis and Saving section.)

Execution Steps
The following processes occur when a program execution commences:

  1. The requested Local Data Area value is set.
  2. The details of the program and its environment are logged for the current user.
  3. A message is placed in your job log indicating that the program test has commenced.
  4. The current job statistics are recorded.
  5. The program under test is called.
  6. The job statistics are retrieved and compared to the earlier values.
  7. A message is placed in your job log indicating that the program test has completed.
  8. If the program under test completed abnormally, the last exception message is retrieved for display.
  9. The Local Data Area is retrieved, stored, reset to its starting value and checked for changes.
  10. Parameter values are compared to identify those which have changed during the course of the program execution.

Errors During Execution
If the program under test crashes, or you need to use System Request option 2 (End Request) to force it to end, Adhoc_IT as a request handler will take control and Post Execution processing will occur in an orderly fashion.

Post Execution

The following facilities are provided irrelevant of whether the program ended normally or abnormally.

  1. The Local Data Area will be checked to determine if its value has altered during the course of the program execution, and the individual changes within the Local Data Area can be viewed by keying option 1 against Local Data Area.
  2. Option 1 against the Job Log will access the TestBench enhanced Job Log facility. (For more information please refer to the Global Facilities section.)
  3. The start and returned parameter values can be viewed.
  4. A performance bar will be presented in the centre of the screen showing the elapsed duration of the program execution, the number of auxiliary input / output operations and the number of CPU milli-seconds used. Please consult the relevant IBM manual for a full.