APAR status
Closed as program error.
Error description
Due to connection error to the federated target, Admin thread came down. So any further commands to the program (like stopq / startq) would not be accepted since it is the Admin thread's responsibility. The browser thread got a connection error while updating IBMQREP_RECVQUEUES table, hence it could not update the state to I after ASN7627E was issued. We can take a bug that for federation targets, if the admin thread and all browsers get an error and come down, regardless of term, QAPPLY is able to gracefully come donw.
Local fix
Problem summary
The reason was that the error code from admin thread was not getting propagated to the main thread for the program to stop.
Problem conclusion
The problem has been fixed to honor connection errors from Admin thread and monitor threads bringing Q Apply down. For federated target, if term=N, Q Apply may still come down depending on the type of sqlcode returned by the federation server whether it is a connection error or a generic error code.
Temporary fix
Comments
APAR Information
APAR number
JR47831
Reported component name
WS Q-REPLIC LUW
Reported component ID
5724N9801
Reported release
A13
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-09-17
Closed date
2013-09-17
Last modified date
2013-09-17
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
WS Q-REPLIC LUW
Fixed component ID
5724N9801
Applicable component levels
RA13 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A13","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
17 September 2013