A fix is available
APAR status
Closed as program error.
Error description
During a slow down of a CICS Transaction Server for VSE you get error DFHMN0002 with severe error code X'0223' in module DFHMNMN. . CICS internal trace shows that CICS doesn't process a lock correctly when the application timed out during a Syncpoint request. . It has to suspend when it tries to get a lock . EIP ENTRY SYNCPOINT MNMN ENTRY PERFORMANCE_DATA_PUT SYNCPOINT LMLM ENTRY LOCK 07D129B8,EXCLUSIVE DSSR ENTRY SUSPEND 00530005,NO,LOCK,NO . It takes too long to get the lock and the task is purged. . DSSR *EXC* SUSP_PURGED SUSPEND,00530005,NO,LOCK,YES DSSR EXIT SUSPEND/PURGED TASK_CANCELLED LMLM *EXC* THE TASK REQUESTING A LOCK HAS BEEN PURGED. LMLM EXIT LOCK/PURGED . Even though it never got the lock, CICS requests an unlock, which fails: . LMLM ENTRY UNLOCK 07D129B8,EXCLUSIVE LMLM EXIT UNLOCK/EXCEPTION NOT_LOCK_OWNER MNMN *EXC* Unlock request failed UNLOCK,EXCEPTION,NOT_LOCK_OWNER
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * All. * **************************************************************** * PROBLEM DESCRIPTION: * * Forcepurging a task results in message DFHMN0002 A severe * * error (code X'0223') has occurred in module DFHMNMN being * * issued. * **************************************************************** * RECOMMENDATION: * * . * **************************************************************** A CICS region has monitoring active. At least two tasks are attempting a syncpoint, which will lead to some monitoring data needing to be written and therefore the task will need exclusive control on the global monitoring lock. Since task 1 has the lock, any subsequent tasks will need to wait. One of these waiting tasks is purged. Having been purged, the task continues to process monitoring code including running any active program for user exit XMNOUT and then calls unlock. However since this task was purged it never had the global monitoring lock, so when it attempted to unlock it a severe error is issued. This results in trace entry MN 0223 and msgDFHMN0002 being issued. Additional Keywords: NOT_LOCK_OWNER MN0002 MN0223 LM0047 LM 0047 LMLM *EXC* TASK-REQUESTING-LOCK-HAS-BEEN-PURGED
Problem conclusion
DFHMNMN has been altered to ensure that if the monitoring global lock is not obtained during a syncpoint no further monitoring processing will occur.
Temporary fix
Comments
APAR Information
APAR number
PI64335
Reported component name
CICSTS FOR ZVSE
Reported component ID
5655VSE00
Reported release
B2P
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-16
Closed date
2016-09-29
Last modified date
2017-01-18
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
PI66269 UI41229
Modules/Macros
DFHMNMN
Fix information
Fixed component name
CICSTS FOR ZVSE
Fixed component ID
5655VSE00
Applicable component levels
RB2P PSY UI41229
UP17/01/18 I 1000
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":"2.1","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
18 January 2017