A fix is available
APAR status
Closed as program error.
Error description
PE33761-F803 ATTACH failures on the first call to the application. Subsequent calls do not fail. The failure is indicated by message: . DFHDS0002 A severe error (code X'0137') has occurred in module DFHDSIT. . The problem occurs after the application issues it's first DB2 request, and CICS attempts to attach an L8 TCB. MVS system trace shows that the ATTACHX call fails with RC20 indicating: ------------------------------------------------------------- 20 - The task making an Attach ADDRENV=SUBSP request was not processing with Subspace active. ------------------------------------------------------------- The RC20 is returned because CICS is running in BASESPACE mode when the ATTACH SVC is issued, but should have been in SUBSPACE mode. System trace shows that prior to the ATTACH is a BSG instruction from CPSM module, EYU9NLME. This BSG request was added by PK56992 to address a problem with GLUEs not getting control in BASESPACE mode. If needed, EYU9NLME switches to BASESPACE mode, and relies on DFHUEH / DFHSUEX to switch back to SUBSPACE mode. . The problem is with the DFHSMSRI macro added to EYU9NLME by PK56992. Since CPSM 3.2 is being used, the expansion of the DFHSMSRI macro uses the TXN +x'108' to address the SMX control block (field XM_TXN_SM_TOKEN ). But the CICS region is CICS 3.1, and the XM_TXN_SM_TOKEN is found at offset x'F0'. So EYU9NLME uses the wrong offset, obtains zeroes, and then bypasses the code which would turn the SMX_SUBSPACE_ACTIVE flag off. . DFHSUEX, on return from EYU9NLME, then checks the SMX_SUBSPACE_ACTIVE flag to determine if a subspace switch was done. Since this flag was never turned on by EYU9NLME, DFHSUEX bypasses the subspace switch and doesn't put the task back in SUBSPACE mode. Eventually the ATTACHX SVC will be issued and it will fail because CICS is not in SUBSPACE mode. Additional Symptom(s) Search Keyword(s): KIXREVSXY
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICSPlex SM V3R2M0 Users. * **************************************************************** * PROBLEM DESCRIPTION: After applying PTF UK34398, if the * * CICSPlex SM V3R2M0 MAS agent is * * running in a CICS TS R640 (or earlier) * * system and transaction isolation is * * active then tasks may not switch back * * to subspace mode after CICSPlex SM * * Global user exits are invoked. * * * * Symptoms may vary depending on the * * facilities invoked. In the reported * * case an attempt to use DB2 caused * * message: * * * * DFHDS0002 A severe error (code * * X'0137') has occurred in module * * DFHDSIT. * * * **************************************************************** * RECOMMENDATION: After applying the PTF that resolves this * * APAR, all MASes must be recycled to pick * * up the new code. Note that the restarts * * do not need to be done at the same time. * * * * PTF UK43094 (for CICS TS 650 APAR PK77484) * * must be installed prior to using the PTF * * that resolves this APAR on a CICS TS 650 * * MAS. * **************************************************************** The CICSPlex SM Global User exits use an inline function to switch to Basespace mode if a task is subject to transaction isolation. The inline request is dependant on the location of various CICS control blocks. XM_TXN_SM_TOKEN is used to locate the CICS SMX control block, which contains the SMX_SUBSPACE_ACTIVE flag. The inline function call updates SMX_SUBSPACE_ACTIVE to indicate the Subspace mode of the task. After the Global User exit is invoked, DFHSUEX inspects SMX_SUBSPACE_ACTIVE to see if the exit switched Subspace mode. If necessary DFHSUEX will make the necessary calls to return the task to the correct Subspace mode. When the CICSPlex SM V3R2M0 code executes on a CICS TS 640 system (or earlier), the XM_TXN_SM_TOKEN is located at a different offset than CICS TS 650. This causes the inline call to fail to update SMX_SUBSPACE_ACTIVE. This means that DFHSUEX does not return the task to the correct Subspace mode, causing the reported symptom.
Problem conclusion
The CICSPlex SM Global User Exit programs have been changed to use the CICS XPI facilities to switch to Basespace mode. This removes the dependency on the location of the CICS control blocks used by the inline requests.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK78474
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
50M
Status
CLOSED PER
PE
YesPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-12
Closed date
2009-01-30
Last modified date
2009-03-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
EYU9NLDC EYU9NLDR EYU9NLID EYU9NLME EYU9NLSO EYU9NMST EYU9NMTE EYU9XLGR EYU9XLME EYU9XLSR
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R50M PSY UK43641
UP09/02/06 P F902 ®
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 March 2009