A fix is available
APAR status
Closed as program error.
Error description
1). Pending response/Waiting reply total is calculated incorrectly where a client has set a TIMER value of 'E9' on an ACK request. In this situation there is no read following the ACK so it was being incorrectly counted as a message waiting on OTMA, and the predicted status in active sessions was showing as 'P002 - Waiting for reply from datastore' 2). Pending response/Waiting reply total is calculated incorrectly where a client has set the IRM_F5 flag to AUTO, DEFAULT or SWAIT for a RTPIPE command. In these situations the messages were incorrectly counted as a message waiting on OTMA and the predicted status in active sessions was showing as 'P002 - Waiting for reply from datastore' This is the forward-fit for APAR PH03211.
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: Pending response/Waiting reply total * * showing higher value than expected. * **************************************************************** 1. Pending response/Waiting reply total is calculated incorrectly where a client has set a TIMER value of 'E9' on anACK request. In this situation there is no read following the ACK so it was being incorrectly counted as a message waiting on OTMA, and the predicted status in active sessions was showing as 'P002 - Waiting for reply from datastore'. 2. Pending response/Waiting reply total is calculated incorrectly where a client has set the IRM_F5 flag to AUTO, DEFAULT or SWAIT for a RTPIPE command. In these situations the messages were incorrectly counted as a message waiting on OTMA and the predicted status in active sessions was showing a 'P002 - Waiting for reply from datastore'.
Problem conclusion
1. Corrected Pending response/Waiting reply counts to exclude situations where an ACK Message has been sent to OTMA with a TIMER value of 'E9'. For this situation the predicted status in active sessions now shows as 'P013 - Waiting in read prepare process'. 2. Corrected Pending response/Waiting reply counts to exclude situations where an RTPIPE type request of AUTO, DEFAULT or SWAIT are found. For these situations the predicted status in active sessions now shows as 'P043 - RTPIPE waiting on asynchronous output'.
Temporary fix
Comments
APAR Information
APAR number
PH09156
Reported component name
IMS CONNECT EXT
Reported component ID
5655K4800
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-02-27
Closed date
2019-03-20
Last modified date
2019-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI62025
Modules/Macros
CEX#ABOU CEXCONS CEXCONSS CEXCSKT CEXEVT01 CEXEVTPR CEXEVTSR CEXEVWTR CEXI09 CEXMAIN CEXOPSES CEXPRED0 CEXPRED1 CEXPREDC CEXPUBMN CEXPUCLI CEXR168 CEXRXADR CEXSALUT CEXSMSES CEXSMSET CEXSMSMF CEXSMSML CEXSMSNS CEXSMSRP CEXTECL CEXTPXML
Fix information
Fixed component name
IMS CONNECT EXT
Fixed component ID
5655K4800
Applicable component levels
R310 PSY UI62025
UP19/03/27 P F903
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":"3.1.0"}]
Document Information
Modified date:
22 October 2020