A fix is available
APAR status
Closed as program error.
Error description
All messages were going to SMDS. Based on the offload rules when the structure reached 70% the messages should have been offloaded to SMDS. Instead every message was going to SMDS. In this scenario, the following offload rules were used: CFSTRUCT(structureName) DESCR( ) CFLEVEL(5) RECOVER(YES) OFFLOAD(SMDS) OFFLD1TH(70) OFFLD1SZ(32K) OFFLD2TH(80) OFFLD2SZ(64K) OFFLD3TH(90) OFFLD3SZ(64K) DSGROUP(MQS.xxxxxx.TEST.*.SMDS) DSBLOCK(256K) DSBUFS(100) DSEXPAND(YES) RECAUTO(YES) CFCONLOS(ASQMGR) ALTDATE(2014-07-11) ALTTIME(14.52.56) . The change team found that a EEPLALTEREND event is being processed by CSQESEX and the EEPL block being processed fields EEPLALTERENDELEMCOUNT and EEPLALTERENDENTRYCOUNT were all zeros causing the observed behavior.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All Users of WebSphere MQ for z/OS Version 7 * * Release 1 Modification 0. * **************************************************************** * PROBLEM DESCRIPTION: When using CF structures with SCM and * * offload rules, it may occur that * * messages matching the size limit of at * * least one of the rules get offloaded, * * even though the threshold condition is * * not met. * **************************************************************** * RECOMMENDATION: * **************************************************************** With SCM enabled, an alteration of the structure causes only the available SCM storage to be altered, but leaves the real storage entry and element counts unchanged. An EEPLAlterEnd event is triggered containing EeplAlterEndElemCount and EeplAlterEndEntryCount values of 0. This is not expected by the event exit in the queue manager, causing offload thresholds to be calculated incorrectly. Keywords: MQSMDS/K E2827/K
Problem conclusion
The structure event exit processing in the queue manager has been changed to correctly handle null values for entry and element counts. 100Y CSQESEX
Temporary fix
Comments
APAR Information
APAR number
PI21909
Reported component name
WMQ Z/OS V7
Reported component ID
5655R3600
Reported release
100
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-07-11
Closed date
2014-07-31
Last modified date
2014-10-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI20147 PI27592
Modules/Macros
CSQESEX
Fix information
Fixed component name
WMQ Z/OS V7
Fixed component ID
5655R3600
Applicable component levels
R100 PSY UI20147
UP14/08/30 P F408
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 October 2014