A fix is available
APAR status
Closed as program error.
Error description
Server related issues found: 1) Client will not wait more than 2 minutes on response from server. 2) ABEND0C4 in server when client has timed out. 3) Client hangs if no response is sent back to the client from the server. In this case we need to end the client. The symptom is the server continues to send requests to the control region. CPU time builds and both go into a loop and the request is never sent back to the client. Keywords: ABENDS0C4 loops looping hang hanging
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of QCF3.1. * **************************************************************** * PROBLEM DESCRIPTION: 1. Client will not wait long enough on * * requested function to end. * * 2. ABEND0C4 in server when client has * * been timed out. * * 3. Client hangs if no response is sent * * back from IMS - only an error text. * * In this case we need to check the * * error text and stop processing. * * The symptom is the server continues * * to send requests to the * * control region. CPU time builds and * * and the error is never sent back * * to the client. * **************************************************************** * RECOMMENDATION: * **************************************************************** Programs have been changed to avoid 0C4, hang and time out. 1. Client waits up to 3 minutes on the request to finish and response to be sent back. To avoid client hang for a very long time, client is timed out after 3 minutes. After client time out- the client has to be restarted in order to create a new communication connection to server ( the old remains occupied by the not answerred request and can not be used for other requests). Please, do not issue requests that will copy the whole message queue in client's files - issue fast query requests and browse requests with includes to restrict the response time and transfer volumes. 2. Before sending response to client , a check is done in server - to verify the client is still active. 3. If there is an error message response back from control region to server, the error response is send back to client and function is terminated with RC=16.
Problem conclusion
The programs have been changed to fix the problems.
Temporary fix
Comments
APAR Information
APAR number
PK60555
Reported component name
IMS QUEUE CNTL
Reported component ID
5697E9900
Reported release
310
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2008-02-05
Closed date
2008-02-25
Last modified date
2008-03-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK33999
Modules/Macros
IQCBTQCF IQCCTIME IQCC010 IQCLOD61 IQCP0000 IQCQMRA9 IQCQMREA IQCQMREX IQCQMRE8 IQCXCTRL IQCZRSP0
Fix information
Fixed component name
IMS QUEUE CNTL
Fixed component ID
5697E9900
Applicable component levels
R310 PSY UK33999
UP08/02/26 P F802
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":"SSCX8A6","label":"IMS Queue Control Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0"}]
Document Information
Modified date:
04 October 2020