What causes CICS AEZDabends when running Object Service Broker CICS Gateway transactions?

What causes CICS AEZDabends when running Object Service Broker CICS Gateway transactions?

book

Article ID: KB0086384

calendar_today

Updated On:

Products Versions
TIBCO Object Service Broker for z/OS -
Not Applicable -

Description

Resolution:
Executing TIBCO Object Service Broker CICS Gateway transactions may result in a CICS AEZD transaction abend.

Environment:
===========
Environments affected run all of the following software:
* CICS Transaction Server for z/OS
* TIBCO Object Service Broker CICS Gateway
* z/OS

Symptoms:
========
Execution of TIBCO Object Service Broker CICS Gateway transactions, particularly calling a user defined program may abend with a CICS AEZD transaction abend. The following message may be issued:
DFHAC2206 hh:mm:ss applid Transaction tttt failed with abend AEZD. Updates to local recoverable resources backed out.

Cause:
=====
An AEZD abend indicates that an attempt was made to run a program defined as EXECKEY(USER) as part of a transaction defined as TASKDATAKEY(CICS). The transaction specification TASKDATAKEY determines the key of storage used to build CICS areas such as the Execute Interface Block (EIB) and satisfy user storage requests. If a transaction is defined with TASKDATAKEY(CICS) then the EIB will be placed into CICS key storage. If a user program defined as EXECKEY(USER) is called, CICS will issue the AEZD abend because the execution of the program cannot be successful since the program cannot access the EIB and other critical storage areas.

Sample TIBCO Object Service Broker CICS Gateway transactions were defined with the overly restrictive TASKDATAKEY(CICS) specification. This meant that all programs and user external CICS routines had to be defined with EXECKEY(CICS) which may not be what customer would prefer.

Resolution:
==========
Sample transaction definitions will be changed in the next release of the TIBCO Object Service Broker CICS Gateway product to use the TASKDATAKEY(USER) specification although customers may still choose TASKDATAKEY(CICS) if they wish. Customers may also elect to make this change to their 5.0 definitions if so desired.


References:
==========
1) TIBCO® Object Service Broker for z/OS Installing and Operating Software Release 5.0
2) IBM CICS Transaction Server for z/OS Messages and Codes Version 3 Release 2
3) IBM CICS Transaction Server for z/OS Resource Definition Guide Version 3 Release 2

Issue/Introduction

What causes CICS AEZDabends when running Object Service Broker CICS Gateway transactions?