Back to Top

Catching Looping Jobs

Jobs running in production environment is not supposed to start looping, but most installations have experienced the problem a few times. If GiAPA is active collecting data, such cases can be caught almost immediately.

CL command GIAPA110 used to submit the data collection includes the keyword LOOPTRAP, which may be used to define that GiAPA shall send a severity level 60 message to the system operator if a job uses more than xx % CPU during yy minutes without doing any data base reads.

Specifying CPU Limit for Looping Jobs

The message is shown below. Of course an exception list is available for job names which should be excepted from this check.

xWarning for Looping Job