CICS transaction fails if not CEDX used

bhavant · New User Joined: 24 Aug 2007 Posts: 5 Location: India

Hi,

A CICS transaction in our system seems to be looping in one part of the program.

The major problem is when the same transaction is run with CEDX turned on, for de-bugging, it starts to work fine and does not fail! The program works fine if run in INTER TEST. The transaction fails if either of the above is not used. Due to this behavior I am not able to find the exact problem location.

Can anybody suggest any other way to debug or any suggestion please?

It was working fine for the last 10 years! until the CICS upgrade and few system maintenance activities which sadly will not be reverted back!!

Thanks..

dick scherrer · Posted: Tue Jan 11, 2011 9:38 pm

Hello and welcome to the forum,

Does this program now go into the loop every time it is executed "normally" or only some of the time?

Was the program recompiled/linked as part of the upgrade?

Bill O'Boyle · Posted: Tue Jan 11, 2011 9:47 pm

Just a guess, but it could be "suspicious" code that CICS would let you get away with in earlier version/releases, but now, it causes problems.

Have any of the CEDA/RDO definitions been changed?

What was the old version/release and what did you upgrade to?

Bill

bhavant · New User Joined: 24 Aug 2007 Posts: 5 Location: India

Hi Dick,

Once in a while it executes without any issues, but max number of times it does not. But it always works fine with CEDX turned on.

I recompiled it once, hoping to resolve the issue but no change.

Thanks..

bhavant · New User Joined: 24 Aug 2007 Posts: 5 Location: India

It was upgraded from 1.1 to 2.3..

Would the behavior of the code change due to CEDX or INTER TEST?

dick scherrer · Posted: Tue Jan 11, 2011 10:03 pm

Hello,

Bill O'Boyle · Posted: Tue Jan 11, 2011 10:05 pm

No, I doubt a version/release upgrade would cause a major change in these Products, but verify this with the Vendor(s).

There were some changes in TS 2.x (from TS 1.x), mainly additional Threadsafe compliant API's, but nothing which would cause this issue.

If you had upgraded from CICS/ESA to CICS/TS then I would become suspicious.

Are there any Assembler modules involved?

Bill

Robert Sample · Posted: Tue Jan 11, 2011 10:12 pm

Work with your CICS support group to capture a dump from when the program is looping and debug it from the dump. The behavior you are describing is pretty common -- the debugger stops the looping to display data on the terminal, hence the loop abend no longer occurs ....