IBM Support

BAQR0405I z/OS Connect EE request timeout after CICS transaction abend

Question & Answer


Question

Why does a z/OS Connect Enterprise Edition (EE) request time out after 30 seconds instead of returning an error response when a CICS transaction abends? I have z/OS Connect Enterprise Edition accessing CICS Transaction Server for z/OS V5.2 through WebSphere Optimized Local Adapter (WOLA).

When transaction BBO# abends, the following is the response sent back to the REST client:
Status: 500 Internal Server Error
Error 500: BAQR0405I: The asynchronous service request under URL https://<hostname>:<portnumber>/CatalogManager/items/0010 has timed out after 30,000 milliseconds.

The CICS MSGUSR shows the transaction abending as follows:
DFHAC2236 04/15/2016 01:17:28 Transaction BBO# abend AAAA in program DFHEDFX term ????. Updates to local recoverable resources will be backed out.

There was no particular error message in the Liberty server joblog.

The abend above is created by capturing BBO# by EDF and explicitly abending it through the EDF interface. (I also also tried abending it by TRANCLASS MAXACTIVE - AKCC but the result was the same). I have collected some trace and dump.

FYI, when I do the same thing with z/OS Connect V1 on CICS Liberty, the following Fault is returned with the 500 Internal Server Error.

 {
     "Fault": {
         "faultstring": "Failure interacting with CICS",
         "detail": {
             "CICSFault": "Target program abended for WEBSERVICE
 'placeOrder_json'"
         }
     }
 }

I think z/OS Connect EE should return the same kind of fault response.

Answer

Whether or not the Liberty client interaction WOLA request times out or gets a response of the abend is dependent upon when the BBO# transaction abends. In the instance, described in the question where EDF was used to abend the BBO# transaction, the WOLA TRUE within CICS will check at end-of-task if the abend occurred after the application program logic was given control. If not, as in this case, the WOLA interaction will timeout.

If the application program logic had gotten control and then the BBO# transaction abended, then the WOLA end-of-task TRUE in CICS would return the following to the zCEE Liberty client request as a javax.resource.ResourceException with response messga:

BBOA8950I: Captured abend code: {1} in program {2}

 Explanation     Link invocation task abend handler intercepted an application abend.
 Action     Check the BBOQ log that is running CICS job messages for the BBOOUT for further messages. The abend code and application program involved with the abend are written there. An exception message is returned and thrown back to the calling 

Using the CICS Catalog Manager example and proceeding further into the target program with EDF and abending the BBO# link transaction, it returns the following.

Error 500: BAQR0404W: Service CatalogManager encountered an error while processing a request under URL https://<hostname>:<portnumber>/CatalogManager/items/0010. {&quot;FailureMessage&quot;:&quot;BAQR0452E: The catinqs service detected an error during the processing of WOLA request with target service: DFH0XCMN and register name: CICSREG.&quot;,&quot; StackTrace&quot;:&quot;com.ibm.zosconnect.spi.ServiceException: BAQR0452E: The catinqs service detected an error during the processing of WOLA request with target service: DFH0XCMN and register name: CICSREG.\n\tat com.ibm.zosconnect.wola.internal.WOLAServiceImpl. processInvoke&#40;Unknown Source&#41;\n\tat com.ibm.zosconnect.wola. internal.WOLAServiceImpl.invoke&#40;Unknown Source&#41;\n\tat com.ibm. zosconnect.internal.ZosConnectServiceImpl.apiInvoke&#40;Unknown Source&#41;\n\tat com.ibm.zosconnect.internal.ServiceManagerImpl. invoke&#40;Unknown Source&#41;\n\tat com.ibm.zosconnect.internal. ApiManagerImpl.invokeApi&#40;Unknown Source&#41;\n\tat com.ibm. zosconnect.internal.web.ServiceProxyServlet$1.run&#40;Unknown Source&#41;\n\tat com.ibm.ws.webcontainer.async.ServiceWrapper. wrapAndRun&#40;ServiceWrapper.java:202&#41;\n\tat com.ibm.ws. webcontainer.async.ContextWrapper.run&#40;ContextWrapper.java:29&#41; \n\tat com.ibm.ws.webcontainer.async.WrapperRunnableImpl.run&#40; WrapperRunnableImpl.java:74&#41;\n\tat java.util.concurrent. ThreadPoolExecutor.runWorker&#40;ThreadPoolExecutor.java:1157&#41; \n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run&#40; ThreadPoolExecutor.java:627&#41;\n\tat java.lang.Thread.run&#40;Thread. java:863&#41;\nCaused by: javax.resource.ResourceException: BBOA8950I Captured abend code: AAAA in program DFHEDFX \n\tat com.ibm.ws.zos. channel.wola.internal.WolaOutboundRequest.waitOnResponse&#40; WolaOutboundRequest.java:135&#41;\n\tat com.ibm.ws.zos.channel.wola. internal.WolaOutboundRequest.invoke&#40;WolaOutboundRequest.java:71&#41; \n\tat com.ibm.ws.zos.channel.wola.internal.WOLAEndpoint.jcaInvoke&#40; WOLAEndpoint.java:149&#41;\n\tat com.ibm.ws390.ola.jca.InteractionImpl. executeHere&#40;InteractionImpl.java:335&#41;\n\tat com.ibm.ws390.ola. jca.InteractionImpl.execute&#40;InteractionImpl.java:243&#41;\n\tat com. ibm.ws390.ola.jca.InteractionImpl.execute&#40;InteractionImpl.java: 440&#41;\n\t... 12 more\n&quot;}

A request to update the IBM z/OS Connect Enterprise Edition 2.0 documentation for WebSphere Application Server in the topic on Using WOLA in CICS as a provider has been submitted to clearly describe when the Liberty WOLA client request will timeout after a CICS abend in the BBO# link transaction and when the client will receive a response with details of the abend.

It is also suggested that an RFE (Request-For-Enhancement) be submitted to describe WOLA failure scenarios in CICS where you desire a detailed response be provided versus a timeout.

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Component":"","Version":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNPJM","label":"IBM z\/OS Connect"},"Platform":[{"code":"PF035","label":"z\/OS"}],"Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]

Product Synonym

CICS/TS CICSTS CICS TS CICS Transaction Server;zCEE

Document Information

Modified date:
14 February 2023

UID

dwa1271228