APAR status
Closed as documentation error.
Error description
When collecting Accounting and Statistics messages using SMF names of long message flows can be truncated as SMF117 records only allow 32 characters. In cases where a common prefixes or suffixes are use this can prevent the unique identification of a flow from an SMF record. In order to customise how this truncation is performed the following environment variables were introduced but these were not added to the Knowledge Center: MQSI_SMF_FLNM MQSI_SMF_NDNM This APAR will add the following descriptions to the Knowledge Center: MQSI_SMF_FLNM allows an administrator to configure which section of a message flow name is used to populate the imflmfnm field in the SMF 117 records when Message Broker Accounting and Statistics is enabled. When MQSI_SMF_FLNM is set as a positive integer and the flow name is greater than 32 characters, this is the absolute starting point for the name reported in the SMF 117 imflmfnm field, up to the total length of the message flow name. When MQSI_SMF_FLNM equals -1 and the flow name is greater than 32 characters then the last 32 characters of the message flow name are used to populate the SMF 117 imflmfnm field. In this case the starting point of the reported name is relative to the end point of the message flow name. In all cases where the message flow name is less than or equals 32 characters the default behaviour is restored and the entire message flow name is reported in the SMF 117 imflmfnm field. For example. If we consider the following message flow names, where the first 3 names are 42 characters long, and the last name is 28 characters long: msgflownamenotunique1111111111111222222222 msgflownamenotunique1111111111111333333333 msgflownamenotunique1111111111111444444444 unique1111111111111555555555 When MQSI_SMF_FLNM=15 the flow names reported in the imflmfnm field will start at character 15, except for the last name which is less than 32 characters and so the whole name is reported. unique1111111111111222222222 unique1111111111111333333333 unique1111111111111444444444 unique1111111111111555555555 When MQSI_SMF_FLNM=34 the flow names reported in the imflmfnm field will start at character 34. The last name is less than 32 characters so the whole name is reported. 222222222 333333333 444444444 unique1111111111111555555555 When MQSI_SMF_FLNM=-1 the flow names reported in the imflmfnm field will be the last 32 characters. The last name is less than 32 characters so the whole name is reported. enotunique1111111111111222222222 enotunique1111111111111333333333 enotunique1111111111111444444444 unique1111111111111555555555 MQSI_SMF_NDNM This operates in the same way as MQSI_SMF_FLNM but allows the logic to be applied to the Node name of SMF records rather than the flow name.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of IBM Integration Bus version 10 using Accounting and Statistics. Platforms affected: z/OS **************************************************************** PROBLEM DESCRIPTION: <span style="background-color:rgb(255, 255, 255)">When collecting Accounting and Statistics messages using SMF </span><span style="background-color:rgb(255, 255, 255)">names of long message flows can be truncated as SMF117 records </span><span style="background-color:rgb(255, 255, 255)">only allow 32 characters. In cases where a common prefixes or </span><span style="background-color:rgb(255, 255, 255)">suffixes are use this can prevent the unique identification of </span><span style="background-color:rgb(255, 255, 255)">a flow from an SMF record. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">In order to customise how this </span><span style="background-color:rgb(255, 255, 255)">truncation is performed the following environment variables </span><span style="background-color:rgb(255, 255, 255)">were introduced but these were not added to the Knowledge </span><span style="background-color:rgb(255, 255, 255)">Center: </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">MQSI_SMF_FLNM </span> <span style="background-color:rgb(255, 255, 255)">MQSI_SMF_NDNM </span> <span style="background-color:rgb(255, 255, 255)"> </span>
Problem conclusion
<span style="background-color:rgb(255, 255, 255)">This APAR will add the </span><span style="background-color:rgb(255, 255, 255)">following descriptions to the Knowledge Center: </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">MQSI_SMF_FLNM </span><span style="background-color:rgb(255, 255, 255)">allows an administrator to configure which section of a message </span><span style="background-color:rgb(255, 255, 255)">flow name is used to populate the imflmfnm field in the SMF 117 </span><span style="background-color:rgb(255, 255, 255)">records when Message Broker Accounting and Statistics is </span><span style="background-color:rgb(255, 255, 255)">enabled. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">When MQSI_SMF_FLNM is set as a positive integer and </span><span style="background-color:rgb(255, 255, 255)">the flow name is greater than 32 characters, this is the </span><span style="background-color:rgb(255, 255, 255)">absolute starting point for the name reported in the SMF 117 </span><span style="background-color:rgb(255, 255, 255)">imflmfnm field, up to the total length of the message flow </span><span style="background-color:rgb(255, 255, 255)">name. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">When MQSI_SMF_FLNM equals -1 and the flow name is </span><span style="background-color:rgb(255, 255, 255)">greater than 32 characters then the last 32 characters of the </span><span style="background-color:rgb(255, 255, 255)">message flow name are used to populate the SMF 117 imflmfnm </span><span style="background-color:rgb(255, 255, 255)">field. In this case the starting point of the reported name is </span><span style="background-color:rgb(255, 255, 255)">relative to the end point of the message flow name. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">In all </span><span style="background-color:rgb(255, 255, 255)">cases where the message flow name is less than or equals 32 </span><span style="background-color:rgb(255, 255, 255)">characters the default behaviour is restored and the entire </span><span style="background-color:rgb(255, 255, 255)">message flow name is reported in the SMF 117 imflmfnm field. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">For example. If we consider the following message flow names, </span><span style="background-color:rgb(255, 255, 255)">where the first 3 names are 42 characters long, and the last </span><span style="background-color:rgb(255, 255, 255)">name is 28 characters long: </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">msgflownamenotunique1111111111111222222222 </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">msgflownamenotunique1111111111111333333333 </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">msgflownamenotunique1111111111111444444444 </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">unique1111111111111555555555 </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">When MQSI_SMF_FLNM=15 the flow </span><span style="background-color:rgb(255, 255, 255)">names reported in the imflmfnm field will start at character </span><span style="background-color:rgb(255, 255, 255)">15, except for the last name which is less than 32 characters </span><span style="background-color:rgb(255, 255, 255)">and so the whole name is reported. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">unique1111111111111222222222 </span> <span style="background-color:rgb(255, 255, 255)">unique1111111111111333333333 </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">unique1111111111111444444444 </span> <span style="background-color:rgb(255, 255, 255)">unique1111111111111555555555 </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">When MQSI_SMF_FLNM=34 the flow names reported in the imflmfnm </span><span style="background-color:rgb(255, 255, 255)">field will start at character 34. The last name is less than 32 </span><span style="background-color:rgb(255, 255, 255)">characters so the whole name is reported. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">222222222 </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">333333333 </span> <span style="background-color:rgb(255, 255, 255)">444444444 </span> <span style="background-color:rgb(255, 255, 255)">unique1111111111111555555555 </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">When </span><span style="background-color:rgb(255, 255, 255)">MQSI_SMF_FLNM=-1 the flow names reported in the imflmfnm field </span><span style="background-color:rgb(255, 255, 255)">will be the last 32 characters. The last name is less than 32 </span><span style="background-color:rgb(255, 255, 255)">characters so the whole name is reported. </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">enotunique1111111111111222222222 </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">enotunique1111111111111333333333 </span><span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">enotunique1111111111111444444444 </span> <span style="background-color:rgb(255, 255, 255)">unique1111111111111555555555 </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">MQSI_SMF_NDNM </span> <span style="background-color:rgb(255, 255, 255)"> </span> <span style="background-color:rgb(255, 255, 255)">This operates in the same way as MQSI_SMF_FLNM </span><span style="background-color:rgb(255, 255, 255)">but allows the logic to be applied to the Node name of SMF </span><span style="background-color:rgb(255, 255, 255)">records rather than the flow name. </span>
Temporary fix
Comments
APAR Information
APAR number
PH28421
Reported component name
IIB Z/OS
Reported component ID
5655AB100
Reported release
A00
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-08-12
Closed date
2021-02-04
Last modified date
2021-02-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSNQH8","label":"IBM Integration Bus for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0"}]
Document Information
Modified date:
05 February 2021