|
View previous topic :: View next topic
|
| Author |
Message |
cicsknow
New User
Joined: 11 Mar 2009
Posts: 28
Location: India
|
|
|
|
Hi,
We are getting AEY9 abend in CICS region, and program using DB2 connection. I have checked DB2 connection and they are fine as well as TCB limit also.....but still we are finding this abend.
Please advice on it.... |
|
| Back to top |
|
 |
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
What have you tried to diagnose this? Try running the task in EDF to see what command is failing or examine the trace in a dump.
Garry. |
|
| Back to top |
|
|
aishwarya_20
New User
Joined: 19 Nov 2008
Posts: 57
Location: pune
|
|
|
|
| DB2 could be down, This is the only reason. Try after some time. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
In the explanation for AEY9, no specific mention is made of DB2, so DB2 being down is not the only reason.
| Quote: |
AEY9
Explanation: One of the following:
o
o An EXEC CICS command has been issued that is not supported by the EXEC
interface program DFHEIP.
o 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.
o 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.
o An attempt has been made to use remote resources, but the local SYSID
has been specified in an EXEC CICS command, or vice versa.
o An attempt has been made to use remote resources, but ISC is not
supported.
o 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.
Module(s): DFHEIP, DFHEEI |
Garry. |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
at the top of every page in this site is a 'download' button.
one of the offerings is something called ABEND Assistant.
I have found that it saves me a lot of time
when I am too lazy to look-up an error code in the manuals.
I think Garry's suggestion should be followed,
and
would like aishwarya_20 to explain his post:
| Quote: |
| DB2 could be down, This is the only reason. Try after some time. |
|
|
| Back to top |
|
|
aishwarya_20
New User
Joined: 19 Nov 2008
Posts: 57
Location: pune
|
|
|
|
From my hands on experience i have learnt that some times AEY9 could occur due to DB2 problem. In my case it was DB2 Bind which worked.
One of the explanation above indirectly points to this :-
An attempt has been made to use remote resources, but the local SYSID
has been specified in an EXEC CICS command, or vice versa. |
|
| Back to top |
|
|
cicsknow
New User
Joined: 11 Mar 2009
Posts: 28
Location: India
|
|
|
|
Thanks for your reply on it,
But as far as checking on this abend, we have monitored DB2 system and CICS system during connection started and both are up during that time and CICS successfully connected also to DB2 system..
But, still we are getting this abend, As far as this abend occur in program which provided by our vendor....and its in load module form so cant see a code also...
is there any possibility of SIT parameter or any CICS side setup........ |
|
| Back to top |
|
|
aishwarya_20
New User
Joined: 19 Nov 2008
Posts: 57
Location: pune
|
|
|
|
| You can debug it by using CEDF command..... and also try rebinding the program and then do NEWCOPY and submit. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Is this a new application that you're testing? If so, the configuration may not be right -- SYSID for example could be incorrectly specified. If it is an existing application, what changed? Start by identifying the changed components and how they impacted the system. |
|
| Back to top |
|
|
cicsknow
New User
Joined: 11 Mar 2009
Posts: 28
Location: India
|
|
|
|
Thanks a lot for help,
But we solved problem, because they need some IP socket config.
Thanks & regards |
|
| Back to top |
|
|
Raghu navaikulam
Active User
Joined: 27 Sep 2008
Posts: 193
Location: chennai
|
|
|
|
Hi cicsknow
Thanks for the last post regarding the solution of the problem.
But I am surprised that you are advised for a REBIND and NEWCOPY.
| Quote: |
| You can debug it by using CEDF command..... and also try rebinding the program and then do NEWCOPY and submit. |
What is the need for a REBIND in AEY9 abend. RE(BIND) is required for an SQLCODE of -805 because of the timestamp in the load module and the timestamp in the validated DBRM is not matching. In your case the transaction is not able to connect to DB2. Then there is no question of
RE(BIND). Actually we are doing a BIND not a REBIND. Repeatedly doing BIND is not REBIND. There are special situations where we go for a REBIND.
But debug using CEDF is a good advise.
Regards
Raghu |
|
| Back to top |
|
|
|
|
