|
View previous topic :: View next topic
|
| Author |
Message |
vasif
New User
Joined: 11 Feb 2008
Posts: 35
Location: Chennai
|
|
|
|
Hi.
I am getting DFHAC2206 04:39:06 CICT1327 Transaction KH09 failed with abend AEXZ. Updates to local recoverable resources backed out.
The scenario is like this. I have a cics sub-program called by a CA-Ideal calling program. I successfully compiled the sub-pgm. But when i do a CEMT I PROG(sub-pgm), the language is shown as 'Not Defined'. Whereas for other similar sub-pgms the language is shown as 'Cobol'.
What i am guessing is the abend is caused because the sub-pgm is either not available or is not of type cobol as shown by CEMT.
Please help out. |
|
| Back to top |
|
 |
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
From the CICS Messages and Codes manual:
| Quote: |
3.7.89 AEXZ
AEXZ
Explanation: A command has failed due to a serious failure in a CICS component (resource manager).
System Action: The transaction is abnormally terminated with abend code AEXZ. CICS takes a transaction dump, unless module DFHDUIO is not loaded.
User Response: Use the transaction dump to determine the cause of the failure. For further assistance, or if module DFHDUIO is not loaded and no transaction dump is available, contact your system programmer. |
Rather than guessing, why not either use the dump as recommended to find out the cause, or used CEDF (or other site debugging tool) to trace through the code to find out what the problem is.
You need to find out which command is having the problem before guessing the nature of the problem -- a little data goes a long way towards removing questions.
Personally, I suspect there's one or more messages that tell which resource had the problem ... before the AEXZ abend message. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
I wonder if this could be a Language Environment non-compliance issue between IDEAL and COBOL?
Is this interface something new?
When did the AEXZ begin occurring?
As far as the "Not Defined" language under the CEMT INQ PROG display, are you using PPT Autoinstall or does someone from your Tech Support group need to explicitly define this PPT entry, using a previously defined PPT entry as a template or perhaps, not?
Bill |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
In addition to defining the cobol module to IDEAL, you also have to treat the cobol module as any other cobol/cics program. If i understood the original post, this was the intention.
Try to call this module from another cobol module. If the same error happens, the module has not been properly defined to cics. Suggest you talk with the cics support people and make sure this module is defined the same as one that works. |
|
| Back to top |
|
|
vasif
New User
Joined: 11 Feb 2008
Posts: 35
Location: Chennai
|
|
|
|
Hi all,
Thank you all for your suggestions. when i asked the CICS support group, they suggested i use the command SNEW pgm-name which worked well. I am now able to get the Language (Cobol).
But the calling program (Ideal) is still abending exactly at the point of calling the sub-pgm. When i commented this call, it ran very well.
What exactly does the error "DFHAC2206 04:39:06 CICT1327 Transaction KH09 failed with abend AEXZ" mean? I cant even use CEDF as it is not a CICS transaction. Can somebody elaborate the probable reasons why this error is caused? |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
AEXZ means CICS had trouble with a resource. It could mean the subprogram is not defined correctly to CICS, or the load of the subprogram failed, or even CICS ran out of memory when attempting to load the program. Without looking at the dump, you cannot tell which resource was the problem and you cannot tell what the problem with the resource was.
This is the kind of problem you really need your site support group to assist in debugging, as the dump needs analysis (IPCS would be a way to do so, Abend Aid -- if installed -- would be another) and possibly some CICS table changes will be required. |
|
| Back to top |
|
|
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
I'm not sure I understand your situation.
If the program is defined to CICS as normal COBOL program ,
what kind of command are you issuing in the IDEAL program ?
Is it a "CALL" statement or a CICS LINK ? |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| Is it a "CALL" statement or a CICS LINK ? |
The IDEAL "call" syntax is like the call in cobol. . .
I don't remember how the called cobol code is invoked, but here is the rule for getting back 
| Quote: |
| In CICS, any return other than a normal EXEC CICS RETURN is prohibited. COBOL programs cannot use STOP RUN, EXIT PROGRAM, or GOBACK. |
A cobol "stub" is defined to IDEAL specifying that this is a cobol module. The called module is also referenced in what is called the Resource section of the IDEAL calling module.
As i asked before, can this new cobol module successfully be called by another cobol module?
| Quote: |
| I cant even use CEDF as it is not a CICS transaction. |
Yes, this is just another cics transaction (even if you use a local tran-id other than IDLX or IDEA, you are invoking an ideal transaction - ask your cics or ideal support person how this is defined in sc00tran - it might be an express or transparent signon). CEDF gets ugly . . . |
|
| Back to top |
|
|
|
|
