IBM Mainframe Forum

Hi,
We have a sandbox system where in the system hangs when the CEDF command is invoked and the system resumes only after the task is purged. What could be the reason for this. And how this can be solved. Can anyone please guide me on this. Apologies if m wrong.


Regards,
V

Hello,

How do you "purge the task" if the system is hung. . .

If the LPAR is running on a single CPU, and the task is in a "hard hang" where no CICS commands can be executed, the most likely way to successfully recover is to IPL the LPAR.

If the LPAR is running on multiple CPUs with a "hard hang", you should be able to get in and purge (forcepurge) the region to recover.

If there truly is a task in a loop with no CICS commands, I cannot think of any ways in CICS to end the task since CICS is devoting all its time to that one task.

Robert: thanks a lot for your post!! really helped me...
Dick: the task was cancelled through a different RACF ID( i mean from another sys prog)

Hello,

So the cics region was not "hung" - only the problem transaction?

If this is a test cics, suggest you have the cics support people reduce the amount of time a transaction is permitted. Then it will time-out and use no more resources.

If the CICS system is in a true looping condition due to task, the only (and even then it is not assured) is to KILL the Transaction cross memory from outside CICS.
Omegamon provided such a means.

Yes. CICS has a CPU limit that allows a task to be purged with abend AICA when it is exceeded; the only problem is that this count gets reset when the program does an EXEC CICS command, so if that is part of your loop you are a bit stuck. Omegamon, Mainview and other CICS monitoring tools can kill tasks automatically when they hit thresholds of CPU, storage allocation, and I/O calls - your sysprogs should have these set already in your test regions to stop runaway tasks, and if they haven't you could ask them to set them up.