A fix is available
APAR status
Closed as program error.
Error description
This APAR addresses these problems: 1. ABEND0C4 in module CEXEXRTR subroutine UIMMST if the message exit fails to set OMUSR_DESTID and leaves it as nulls. 2. The A9 event for XML input data trace was not separating the IRM section from the XML payload section. 3. APAR PK65530 closed a loophole where the CEX Service Exit message header could be in ASCII while the reset of the message in EBCDIC. This required a USERMOD to support the ASCII message header. 4. ABEND0C4 in module CEXTECL routine OTMA63 if a PING is sent to message exit HWSJAVA0 at APAR level PM29137. PM28139 is PE as it returns an invalid length for the PING response. The error in PM29137 caused IMS Connect module HWSSREC0 to ABEND0C4 but with CEX active, module CEXTECL saw the bad length first and since the CEX trace was active, it abended.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IMS Connect Extensions V2.3 * **************************************************************** * PROBLEM DESCRIPTION: ABEND0C4 IN CEXEXRTR, ABEND0C4 IN * * CEXTECL * **************************************************************** * RECOMMENDATION: * **************************************************************** This APAR addresses the following problems: 1. An 0C4 can occur in module CEXEXRTR subroutine UIMMST if the message exit fails to set OMUSR_DESTID and leaves it as nulls. 2. The A9 event for XML input data trace was not separating the IRM section from the XML payload section. 3. In IMS Connect Extensions V2.1 a Service Exit message header could be in ASCII while the rest of the message was in EBCDIC This could cause errors if clients were not coded to handle it. APAR PK65530 resolved this by requiring inbound message headers to be encoded in EBCDIC. However, this required customers to install a USERMOD if they wanted to continue processing ASCII message headers. 4. An 0C4 can occur in module CEXTECL routine OTMA63 if a Ping is sent to message exit HWSJAVA0 and HWSJAVA0 is at APAR level PM29137. This APAR is PE as it returns an invalid length for the Ping response. The error in PM29137 caused IMS Connect module HWSSREC0 to abend 0C4 but with IMS Connect Extensions active, module CEXTECL saw the bad length first and since the IMS Connect Extensions trace was active, it abended. 5. The CEX trace buffer maximum size of 7K is not big enough to capture some of the larger XML payloads sent from the Soap Gateway.
Problem conclusion
The following changes have been made for the above problems: 1. Module CEXEXRTR is changed to detect that OMUSR_DESTID has not been set by the message exit and to treat the value as if if it is set to blanks instead of nulls 2. Changed module CEXTECL to increase the x'A9' event to APAR level of 2 and separate the IRM section from the XML payload section. This allows IMS PI to translate the XML payload section from ASCII to EBCDIC. 3. New CEXCTLIN command SERVICE_EXIT removes the need for customers to instal a USERMOD to support ASCII message headers. 4. Code is added to the OTMA trace routine to do a better job of validating the message lengths on a returned message in order to survive coding errors in the message exits. 5. Changed the options module for the CEXCTLIN dataset to allow a maximum trace length of 20K instead of the current 7K limit.
Temporary fix
Comments
×**** PE14/06/23 PTF IN ERROR. SEE APAR PI20500 FOR DESCRIPTION
APAR Information
APAR number
PI14688
Reported component name
IMS CONNECT EXT
Reported component ID
5655K4800
Reported release
230
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-03-27
Closed date
2014-04-08
Last modified date
2014-08-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI16863
Modules/Macros
CEXCPSR CEXEVTPR CEXEXRTR CEXMAIN CEXMSGCM CEXMSGL CEXR169 CEXSVC01 CEXTECL
| SC19281702 |
Fix information
Fixed component name
IMS CONNECT EXT
Fixed component ID
5655K4800
Applicable component levels
R230 PSY UI16863
UP14/04/11 P F404
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.
[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX88S","label":"IMS Connect Extensions"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.3.0"}]
Document Information
Modified date:
22 October 2020