What to do if you cannot find the reason for a loop

If you cannot find the reason for a non-yielding or a yielding loop using the techniques outlined above, there are two more approaches that you can adopt.

About this task

Procedure

  1. Use the interactive tools that CICS® provides.
    • Use the execution diagnostic facility (CEDF) to look at the various parts of your program and storage at each interaction with CICS. If you suspect that some unexpected return code might have caused the problem, CEDF is a convenient way of investigating the possibility.
    • Use CECI and CEBR to examine the status of files and queues during the execution of your program. Programs can react unpredictably if records and queue entries are not found when these conditions are not tested for and handled accordingly.
  2. Modify the program, and execute it again. If the program is extremely complex, or the data path difficult to follow, you might need to insert additional statements into the source code.
    • Adding extra ASKTIME commands allow you to use EDF and inspect the program at more points.
    • Request dumps from within your program, and insert user trace entries, to help you find the reason for the loop.


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