IMS Sessions: Room G second floor

Session Evaluation

Checkpoints are good things for batch IMS applications to take; however, you can have too much of a good thing. Applications that take too many checkpoints are not easy to identify. They end with condition code 0 and produce the expected results. One checkpoint a second is a good rule of thumb, but we have seen programs taking 30, 50 even over 100 checkpoints a second, wasting CPU and elongating elapsed times. How can you identify offending programs and how can you eliminate unneeded checkpoints without changing the programs? This session will discuss a way to find the programs taking too many checkpoints and suggest some things you can do to address the problem.