A fix is available
APAR status
Closed as program error.
Error description
These issues will be addressed via the APAR: 1. Write event record to journal when a command has been issued to drain or resume a datastore, or a datastore has been "autoresumed". 2. Provide a way to report the number of outstanding responses for a datastore. 3. Type 1 commands issued via IMS Connect Extensions being routed to wrong IMS Connect. 4. Incorrect data transmitted to Operations Console GUI client for some ODBM sessions. 5. Reduce the time that the Publisher API Buffer Lock is held by CEX. 6. The PROC= field for the type 41 event record from the Print Utility can contain blanks. New flag bits have been added to OMCTLPFG that are not supported by the print utility. 7. An abend0C4 may occur in module CEXEXRTR routine TRCDATA if called by routing FGBL. The TRCDATA routine is doing trace in a environment that has not been initialized for trace. 8. If a datastore is drained while a Resume Tpipe is active with the Auto option, the datastore may not completely drain if the Rtpipe time-out value is very long. 9. The contents of MODNAME is the SVT section of the x'3E' event record is incorrect when an RTPIPE is requested from the client. ( For problems #1 - #6 in CEX R220 see APAR PM77548, and for problem #7 in CEX 220 see APAR PM79725 )
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of IMS Connect Extentions V2.3 * **************************************************************** * PROBLEM DESCRIPTION: Write event record to journal when a * * command has been issued to drain or * * resume a datastore, or a datastore has * * been "autoresumed". * **************************************************************** * RECOMMENDATION: * **************************************************************** The following issues will be addressed via this APAR: 1. Write event record to journal when a command has been issued to drain or resume a datastore, or a datastore has been "autoresumed". 2.Provide a way to report the number of outstanding responses for a datastore. 3.Type 1 commands issued via IMS Connect Extensions being routed to wrong IMS Connect. 4.Incorrect data transmitted to Operations Console GUI client for some ODBM sessions 5.Reduce the time that the Publisher API Buffer Lock is held by CEX. 6.The PROC= field for the type 41 event record from the Print Utility can contain blanks. New flag bits have been added to OMCTLPFG that are not supported by the print utility. 7.An abend 0C4 may occur in module CEXEXRTR routine TRCDATA if called by routing FGBL. The TRCDATA routine is doing trace in a environment that has not been initialized for trace 8.If a datastore is drained while a Resume Tpipe is active with the Auto option, the datastore may not completely dain if the Rtpipe time-out value is very long. 9.The contents of MODNAME is the SVT section of the x'3E' event record is incorrect when an RTPIPE is request from the client.
Problem conclusion
The following changes have been made for the above issues: 1.Changes made to write an event record when a command to drain/resume a datastore has been issued, or the datastore has been "autoresumed". 2.Changes to the QUERY command made to report the number of of outstanding responses for a datastore or list of datastores. See the technote 'Query Datastore Outstanding Sessions': (http://www.ibm.com/support/docview.wss?uid=swg21622627) 3.Changes made to allow a specified TCP/IP port number to be used by IMS Connect Extensions when issuing Type 1 commands to a IMS Connect region. See the technote 'SHELL Batch Command and ICON_CONTROL PORT Control Option': (http://www.ibm.com/support/docview.wss?uid=swg21624191) 4.Corrected data sent to Operations Console GUI client. 5.Added additional latch to allow the CEX API server to reduce the amount of time it holds the Asynchronous buffer latch while moving event records to the buffer 6.To be consistent with the rest of the report the PROC= is changed to contain a value of NONE when OMCTLPFG does not have an flag bits set 'on'. Support for new flag bit setting is also added. 7. Removed the trace code from CEXEXRTR routine TRCDATA. 8.A change has been made to detect Resume Tpipe requests for a a drained datastore and reduce the time-out value foran acknowledge to the lowest possible value. This causes the Resume Tpipe to time-out. A well behaved ICON client will re-issue the Resume Tpipe which will then be routed to an active datastore if one exists. 9.MODNAME is not a valid consideration for an RTPIPE operation. Changed code to zero MODNAME field in the event record when the operation is RTPIPE.
Temporary fix
Comments
APAR Information
APAR number
PM77360
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
2012-11-19
Closed date
2013-02-25
Last modified date
2013-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK91972
Modules/Macros
CEX#MDSB CEX#MDS1 CEXACLR1 CEXACL10 CEXAPIUT CEXAPMT1 CEXBCMD CEXBCMD0 CEXBCMD1 CEXCDSTP CEXCERE CEXCMDEV CEXCMDT CEXCOMM CEXCONS CEXCONSC CEXCONSP CEXCONSS CEXCPSR CEXCR00 CEXCR61 CEXCR62 CEXCVDB CEXDFN1 CEXEFW CEXEPR CEXEVTPR CEXEVT01 CEXEVWTR CEXEXRTR CEXFUNCM CEXGUIW CEXIICB CEXJRNEX CEXMAIN CEXMAPI CEXMSGCM CEXMSGL CEXMSGT CEXPBAC CEXPC01 CEXPRED0 CEXPRED1 CEXPUBMN CEXRAPR CEXREAD CEXRSNT CEXR172 CEXSALUT CEXTECL CEXTECL1 CEXTPXML H28S230J
Fix information
Fixed component name
IMS CONNECT EXT
Fixed component ID
5655K4800
Applicable component levels
R230 PSY UK91972
UP13/02/28 P F302
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