MVSFORUMS.com

[Uttank]

I need a technical help in the area of CICS. I have written an online application that does the usual DIS/MOD/ADD/DEL functions on a table. This is a scrolling screen and we have a column for operation too, on the screen. The user can give A/M/D to add/mod/del individual records.

Problem comes when CICS is recycled or the screen is refreshed with CEMT. The screen abends quite consistently for initial 5-10 minutes with abend code DSNC or AEY9. After trying 5-10 times, the screen starts working fine without any problems, till the next time CICS is recycled. This is my observation of the timing of the problem, but I am unable to locate the exact cause. I have compared the program with other working similar online screens, but have not been able to locate any obvious reasons.

The IBM book manager points towards STORAGE VIOLATIONS as a possible cause of such an abend. I have also tried to look for a solution on the Internet, but we found that there is very little documentation available about storage violations, which never point to a specific possible cause. The code shown on the screen is DFHAC2206.

Please help.

[kolusu]

uttank,

DSNC is a DB2 transaction abend code.I think whenever CICS is recycled, the CICS-DB2 attachment facility is dropped. check this link for CICS Transaction Abend/Dump Code(DSNC)

Here is an explanation of AEY9

• An EXEC CICS command has been issued that is not supported by the EXEC interface program DFHEIP.
  
  
• A transaction has issued an EXEC CICS command which is supported in principle by the EXEC interface program DFHEIP, but for which the prerequisite function has not been included in the current CICS start-up.
  
  
• A non-CICS command has been issued via an application "stub" (expansion of a DFHRMCAL macro), and the program DFHERM has detected that the necessary non-CICS support is not available.
  
  
• An attempt has been made to use remote resources, but the local SYSID has been specified in an EXEC CICS command, or vice versa.
  
  
• An attempt has been made to use remote resources, but ISC is not supported.
  
  
• An EXEC CICS command contains an invalid AID or CONDITION identifier. This indicates that the EXEC CICS command has become corrupted.
  

System Action: The transaction is abnormally terminated with a CICS transaction dump.

User Response: Check that the sysid specified and the resource names were correct. If not, notify the system programmer. Either the command (or an application stub) has become corrupted, or the unavailable function needs to be generated (CICS command), ENABLEd (non-CICS command), or exceptionally the non-CICS support has suffered damage and is attempting to withdraw itself from the CICS system.

Modules: DFHEIP, DFHEEI

Hope this helps...

Cheers

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

[Mike Chantrey]

I would say you need to talk to your CICS sysprogs about how DB2 is getting reconnected after a CICS reload - 5-10 mins sounds like a long time; they should be able to get it to connect pretty much immediately on CICS startup.