GI76847 recommends a Runaway Interval setting of 5.
-What does the IDMS system do when a task exceeds that?
IDMS relies on an independent ticker subtask (RHDCTCKR) to check for runaway tasks, in addition to other Timer related things. Depending on the TICKER INTERVAL specified, we recommend 1, that subtask will wakeup every 1 second and check all tasks against the runaway interval, and marks tasks accordingly. If a task is in system mode, IDMS won’t abend the task…but if that task returns to the program, at that time IDMS will abend the task with DC002001 RUNAWAY TASK DETECTED IN SYSTEM MODE. If the task is in user mode, we will abend the task with a D004 at the time ticker identifies it as runaway. From the Messages and Codes manual:
The DC task/run unit has been terminated because it has executed longer than the time specified in the system generation SYSTEM statement RUNAWAY INTERVAL parameter without an intervening wait. A possible cause of this error is a loop in the application program; the DCUF user trace facility may be helpful in detecting application-related problems. If no application-related problems are found, divide the abended task/run unit into several shorter tasks/programs or increase the runaway interval.
his would display in the CV log as:
D004 for user programs
DC002001 for runaways in system mode.
Release: IDADSO00100-18.5-ADS-for CA-IDMS