A fix is available
APAR status
Closed as program error.
Error description
The problem appears to be where DFHMAVCP does a link to DFHL3270. This in turn spawns another link, this time, to DFHBRMP and this fails with a ADCI abend. Control eventually returns to DFHMAVCP via the LINK DFHL3270 EXIT and DFHMAVCP tests the RESP and RESP2 values. Both are '0' because the LINK has in fact worked, it is the backend Transaction that failed. . From looking at TRACE in a Dump, the Key Entries issued are: . EIP ENTRY LINK('DFHL3270') < called from DFHMAVCP +131A2 RUN_TRANSACTION(TRAN) EIP ENTRY LINK('DFHBRMP') < called from DFHL3270 +EA6 EIP EXIT LINK('DFHBRMP') < at this trace entry, the ADCI abend has been detected and is at offset x'8b' in data '1' of the Trace Entry. BRMR EXIT < reports failure details of TRAN EIP EXIT LINK('DFHL3270') < resp=0 resp2=0 . So now, back in DFHMAVCP, the LINK has been done and now the TEST on the RESP codes is performed. Since CICS-RESP is '0' there will be NO Error Handling performed. It appears that the code for CICS-RESP need's to be enhanced to check on the BRIH- ABENDCODE field to see if it's been populated with an Abend, and if so, drive the Error Handling Code.
Local fix
Additional Symptom(s) Keyword(s): KIXREVSCB
Problem summary
**************************************************************** * USERS AFFECTED: All. * **************************************************************** * PROBLEM DESCRIPTION: Abend code not passed back to SFF * * driver program. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the reported problem a front end application was interfacing to a backend application running on CICS via the SFR (Service Flow Runtime) and DFHL3270. The backend application abended due to a database being unavailable. The details of the abend were available in the DFHL3270 exit data but the SFR code did not pass this abend to the front end application by way of populating field DFHMAH-ABENDCODE in the Service Flow message header (DFHMAH). As a consequence, the front end application was unable to determine the correct recovery action(s).
Problem conclusion
DFHMAVCP and DFHMAMGR have been modified to detect an abend at DFHL3270 exit and to make the abend available to the front end application by populating DFHMAH-ABENDCODE in the Service Flow Runtime message header (DFHMAH).
Temporary fix
Comments
APAR Information
APAR number
PK75711
Reported component name
SERVICE FLOW FE
Reported component ID
5655M1502
Reported release
200
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-11-14
Closed date
2009-01-13
Last modified date
2009-02-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK43093
Modules/Macros
DFHMADPL DFHMAMGR DFHMAMLA DFHMAMSS DFHMAVCP DFHMAXLA
Fix information
Fixed component name
SERVICE FLOW FE
Fixed component ID
5655M1502
Applicable component levels
R300 PSY UK43093
UP09/01/22 P F901
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSC5SJS","label":"Service Flow Feature"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 February 2009