APAR status
Closed as program error.
Error description
Mapping node may not map some XML schema elements, which contain type restriction. If custom ESQL transform input contains such element, the following error message will be displayed RecoverableException BIP4187E: Failed to call ESQL routine ''<Routine Name>'' because parameter number '<parameter number>' (the first parameter is number 1) is not of the correct type. All parameters that are supplied in the ESQL function must be of the correct type. Ensure that the parameters are of the correct type to call the ESQL routine. An example of the XML schema with type restriction elements - <xs:complexType name="ComplexTypeElement"> <xs:simpleContent> <xs:extension base="SimpleTypeElement"> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:simpleType name="SimpleTypeElement"> <xs:restriction base="xs:decimal"> <xs:totalDigits value="18"/> </xs:restriction> </xs:simpleType>
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of the IBM Integration Bus Mapping node, calling custom ESQL with arguments, which contain complex elements with type restrictions. Platforms affected: z/OS, MultiPlatform **************************************************************** PROBLEM DESCRIPTION: Mapping node may not map some XML schema elements, which contain type restriction. If custom ESQL transform input contains such element, the following error message will be displayed RecoverableException BIP4187E: Failed to call ESQL routine ''<Routine Name>'' because parameter number '<parameter number>' (the first parameter is number 1) is not of the correct type. All parameters that are supplied in the ESQL function must be of the correct type. Ensure that the parameters are of the correct type to call the ESQL routine. An example of the XML schema with type restriction elements - <xs:complexType name="ComplexTypeElement"> <xs:simpleContent> <xs:extension base="SimpleTypeElement"> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:simpleType name="SimpleTypeElement"> <xs:restriction base="xs:decimal"> <xs:totalDigits value="18"/> </xs:restriction> </xs:simpleType> There are a number of resource name changes between WebSphere Message Broker and IBM Integration Bus Version 9.0. For details visit http://pic.dhe.ibm.com/infocenter/wmbhelp/v9r0m0/topic/com.ibm.e tools.mft.doc/bb23814_.htm
Problem conclusion
The product has been modified to handle custom ESQL arguments correctly. --------------------------------------------------------------- The fix is targeted for delivery in the following PTFs: Version Maintenance Level v10.0 10.0.0.7 v9.0 9.0.0.7 The latest available maintenance can be obtained from: http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041 If the maintenance level is not yet available,information on its planned availability can be found on: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
PI70686
Reported component name
IB Z/OS
Reported component ID
5655IBB00
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-10-14
Closed date
2017-01-19
Last modified date
2017-02-23
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
IB Z/OS
Fixed component ID
5655IBB00
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"9.0","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 December 2020