|
View previous topic :: View next topic
|
| Author |
Message |
sijayapal
New User
.jpg)
Joined: 23 Dec 2008
Posts: 69
Location: India
|
|
|
|
Hi,
I am new to CICS. I face AEIP abend in a background transaction which runs once in a minute. This is a 24X7 application. The purpose of this transaction is to monitor the instances of other transactions set by the users. If the instances were greater than the value set by the user, an alert will be sent.
I found that AEIP abend happened because when the transaction was running the region came down and this resulted in AEIP ( i hope, i am right  ).
How can i handle this situation???? Is there any way i can check whether the region is UP???
Please suggest me with a solution... |
|
| Back to top |
|
 |
ofer71
Global Moderator
Joined: 27 Dec 2005
Posts: 2358
Location: Israel
|
|
|
|
I think you can use the INQUIRE CONNECTION command.
O. |
|
| Back to top |
|
|
Garry Carroll
Senior Member
Joined: 08 May 2006
Posts: 1193
Location: Dublin, Ireland
|
|
|
|
| Quote: |
I found that AEIP abend happened because when the transaction was running the region came down and this resulted in AEIP ( i hope, i am right ).
|
It's more likely the other way around and that your transaction is getting AEIP and shutting the region down, or the region coming down is coincidental.
If a region is down, you won't get to execute the transaction at all - once the region is down, it cannot produce any abend code.
AEIP in INVREQ - you need to find whjat the INVREQ is and add a HANDLE for that.
The business prupose of the transaction is suspect - you could possibly use transaction classes to restrict the instances of given transactions.
Garry. |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
| Why are you not using the RESP parameter on your EXEC CICS command? These days, not having RESP is very negligent -- almost criminally so! |
|
| Back to top |
|
|
sijayapal
New User
Joined: 23 Dec 2008
Posts: 69
Location: India
|
|
|
|
This is what i did........
I have used INQUIRE SYSTEM command to check the region status and then i will start a tran or link to a program. If the region is down,i will not perform any operation.
I have used the RESP option to capture the CICS response. Since the tran runs 24X7, it even tries to execute when the region comes down.
But i was unable to test my changes by bringing the region down. As per our company standards we are not allowed to use HANDLE Condition.
Pls suggest me a way to prevent this abend..... |
|
| Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA
|
|
|
|
Okay, I'm confused. From the manual:
| Quote: |
| The INQUIRE SYSTEM command returns information about the CICS system under which the task issuing the command is executing. |
So why do you need to know about the system you're running under? I thought you were looking at a different CICS region.
What command is getting the INVREQ? If it is the START for the transaction, check RESP2 and if it is 17 then you need to do CICS RETURN since the region is shutting down.
Otherwise, since the INVREQ can be trapped by the RESP code and returned to your program, you can definitely implement program logic to prevent the abend. How you do so, of course, depends upon the requirements for the system -- which we don't know. |
|
| Back to top |
|
|
|
|
