Fixes are available
APAR status
Closed as program error.
Error description
When using a Message Validator primitive some invalid messages which may cause exceptions when being parsed were not being caught as part of the validation process. Instead of firing the fail terminal of the Message Validator primitive as expected these exceptions resulted in the flow stopping.
Local fix
Problem summary
Before the Message Validator primitive can validate a message it needs to parse it may need to parse that message. If this parsing fails, for example due to a non-Boolean value in a Boolean field, then the primitive would fail through an exception and not fire the Fail terminal as it does with other validation errors.
Problem conclusion
The code was modified such that the Message Validator primitive will fire the Fail terminal when these parsing errors are seen in the primitive. The code was targeted to be included in the following Fix Packs. 7.5.1 Fix Pack 3 (v7.5.1.3) 8.0.1 Fix Pack 3 (v8.0.1.3)
Temporary fix
Comments
APAR Information
APAR number
IC99783
Reported component name
WEB ESB FOR WIN
Reported component ID
5724I8200
Reported release
751
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-03-03
Closed date
2014-03-31
Last modified date
2014-03-31
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEB ESB FOR WIN
Fixed component ID
5724I8200
Applicable component levels
R751 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7J6S","label":"WebSphere Enterprise Service Bus"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"751","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
30 March 2023