To prevent deadlock info in logs

[chenna kotlo]

Hi,

I've a requirement like this. We frequently get deadlocks in our project while performing 'STORE' command(IDMS). And the deadlock information(dump) is filled up in CICS logs which is consuming more space. I'd like to prevent writing the deadlock info(dump) in CICS log(let the deadlock happen). How can I achieve this?
Note: I can see the STORE command has 'perform IDMS-STATUS' para called in it when it is expanded in cobol listing. I think 'perform IDMS-STATUS' is writing the dump.

[dick scherrer]

Hello,

I think 'perform IDMS-STATUS' is writing the dump.

Then why not change this so that the dump is not written?

More to the point - why not fix the deadlock problem . . .

[chenna kotlo]

Hi Dick Scherrer,

perform IDMS-STATUS is called internally from STORE command when the compiler expanding it. I don't have control on it.
Avoiding deadlocks causing many issues. Since we've only space constraint, we are thinking to avoid dump of deadlock.

[dick scherrer]

Hello,

Avoiding deadlocks causing many issues.

If you are saying this may be difficult to fix, i'd agree. But it still needs to be fixed . . .

Even if you get around the space issue, there will probably be other "opportunities" that have to be resolved.

I don't have control on it.

What does Support say?

[chenna kotlo]

Thanks Dick Scherrer for the responses.

What does Support say?

You mean to say 'Support team'?

[dick scherrer]

I was thinking of CA Support.

They should be able to provide direction if what you want to do can be done.

There may be a site-specific ptf that can be applied.

Good luck,

d

[chenna kotlo]

Thanks D.Sch. I will check that.

[Ed Goodman]

I work in a razor blade factory.
When people get cut, they throw their bandages in the trash. That takes up a lot of space.
Is there a way to keep the trash can from filling up?

[NicC]

Is there a way to keep the trash can from filling up?

Yes!! Get a trash can of infinite capacity!