A fix is available
APAR status
Closed as program error.
Error description
The first BFBE on the keep chain is not in the correct state to be deleted. This causes the whole of the garbage collection process to end. None of the other eligible BFBEs get deleted. . Additional keywords short on storage creep leak
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All CICS users. * **************************************************************** * PROBLEM DESCRIPTION: Garbage collection fails to delete * * expired BFBEs leading to SOS in ECDSA. * **************************************************************** * RECOMMENDATION: * **************************************************************** A LINK3270 BFBE is placed on the keep chain when a bridge transaction terminates. This contains a reference to a bridge message block which has a bmb_state set to X'01' - BMB_ALLOCATED. This is normally a transient state which will change to X'02' - BMB_OUTPUT when the waiting LINK3270 driver task wakes up and obtains the message. If the LINK3270 driver terminates abnormally due to for example an operator purge, the bmb_state remains set to BMB_ALLOCATED. This BFBE will eventually rise to the top of the timeout queue which is processed by DFHBRFM garbage collection. Any BFBE with a state of BMB_ALLOCATED is ignored by garbage collection. However, instead of skipping over a BFBE with a BMB_ALLOCATED state, garbage collection is terminated. This means that other BFBEs with the expected state of BMB_OUTPUT are never deleted by garbage collection. This leads to a build up of storage allocated to the BRGENRAL subpool which can lead to a SOS condition. ADDITIONAL KEYWORDS :- MSGDFHSM0133 DFHSM0133 SM0133
Problem conclusion
DFHBRFM routine garbage_collect has been changed to skip over BFBEs with a message block state of BMB_ALLOCATED rather than terminating garbage collection when one is encountered.
Temporary fix
********* * HIPER * ********* FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PK96072
Reported component name
CICSTS V3 Z/OS
Reported component ID
5655M1500
Reported release
400
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt
Submitted date
2009-09-14
Closed date
2009-09-25
Last modified date
2009-10-02
APAR is sysrouted FROM one or more of the following:
PK96064
APAR is sysrouted TO one or more of the following:
UK50513
Modules/Macros
DESBRFM DFHBRFM
Fix information
Fixed component name
CICSTS V3 Z/OS
Fixed component ID
5655M1500
Applicable component levels
R400 PSY UK50513
UP09/09/30 P F909
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.1","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.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 October 2009