A fix is available
APAR status
Closed as program error.
Error description
CICS events not recognised by WebSphere Business Monitor unless a User Tag is specified. This problem is seen when using the CICS Explorer to create CICS event bindings, deploying the events into CICS Transaction Server V4.1 and using CICS event processing support to emit the events to Websphere Business Monitor (WBM). If you use CICS Explorer version 1.0.0.5 or above, the symptoms are: The Monitor Model Editor does not report an error, but events from CICS are not recognized by WebSphere Business Monitor at run time. This problem is only seen if you choose not to provide a User Tag for the event binding, and also only if you use the 'Common Base Event (XML)' format for the events within the event binding. The User Tag is a field on the Event Binding tab of the CICS event binding editor, and the Common Base Event format is an option on the Adapter tab. Also on the Adapter tab is a button to 'Export Event Specifications...' which exports dynamic shchemas for each event in the event binding when the format is Common Base Event. If looking at the XML for an event binding, the User Tag appears in the eventBinding part as a userTag element. A symptom of the problem is that the event as emitted by CICS will contain an element of the form <data:payload xmlns:data=" http://www.ibm.com/prod/cics//eventname"> where eventname is the name of the event, and the two successive '/' characters indicate an empty (unspecified) user tag. The dynamic schema exported by the CICS event binding editor represents the empty user tag by a single '/' character, resulting in a mismatch between the expected event format and the format that is emitted by CICS. Slightly different symptoms would be seen if using CICS Explorer version 1.0.0.4 or earlier, where having used the CICS event binding editor to export dynamic schemas for the events within an event binding, if the an event format is Common BaseEvent event binding, if the event format is Common Base Event (CBE), then when you attempt to use the schema(s) to create a Monitor Model using the Monitor Model Editor of the WebSphere Business Monitor Development Toolkit in WID, you get an error such as 'CWMMV0722E: The event part type <namespacePrefix>:payload could not be found', where <namespacePrefix> is normally the name of the event. . Workaround: The problem can be easily worked around by ensuring that, if you are sending events from CICS to WebSphere Business Monitor, the event bindings have a value for the User Tag. The User Tag is a string of 1-8 bytes, which for example can be used to provide identification information for the event binding, so you can use any 1-8 byte that you choose to associate with this event binding. The CICS event binding editor ensures that you use the valid characters which are A-Z, a-z, 0-9, and _ (underscore). After adding a User Tag value to the event binding, repeat the steps to 'Export Event Specifications' and import the new versions into the WebSphere Business Monitor Development Toolkit, and to export the bundle to zFS and install it into your CICS system in place of any previous version. keywords: CWMMV0722E msgCWMMV0722E CWMMV0722 msgCWMMV0722
Local fix
See workaround in Error Description.
Problem summary
**************************************************************** * USERS AFFECTED: All. * **************************************************************** * PROBLEM DESCRIPTION: CICS Events ignored by WBM ( Websphere * * Business Monitor ). * **************************************************************** * RECOMMENDATION: * **************************************************************** CICS events are not recognised by WBM ( WebSphere Business Monitor ) unless an optional User Tag is specified on the Event Binding. . This problem presents when using the CICS Explorer to create CICS event bindings, ( in Common Base Event XML format ) and deploying the events into CICS Transaction Server and using CICS event processing support to emit the events to WBM. . When an optional user tag is not specified, DFHEPAS is representing an empty ( unspecified ) user Tag as '//' but the dynamic schema exported by the CICS event binding editor represents the empty usertag as a single '/'. This results in a mismatch between the expected event format and the actual event format emitted by CICS.
Problem conclusion
DFHEPAS has been modified and will now represent an unspecified UserTag with a single '/' thus matching the dynamic schema exported by the CICS event binding editor.
Temporary fix
FIX AVAILABLE BY PTF ONLY
Comments
APAR Information
APAR number
PM09192
Reported component name
CICS TS Z/OS V4
Reported component ID
5655S9700
Reported release
600
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-03-08
Closed date
2010-03-17
Last modified date
2010-04-03
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK55232
Modules/Macros
DESEPAS DFHEPAS
Fix information
Fixed component name
CICS TS Z/OS V4
Fixed component ID
5655S9700
Applicable component levels
R600 PSY UK55232
UP10/03/19 P F003
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":"4.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":"4.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
03 April 2010