HRNDR069E CPE CONNECT PROCESSING FAILED FOR XXHRERELAYRC=XX08 CPE HEX DUMP FOLLOWS
Article ID: KB0084688
Updated On:
| Products | Versions |
|---|---|
| TIBCO Object Service Broker for z/OS | - |
| Not Applicable | - |
Description
Resolution:
Description:
===========
The following sequence of messages can appear, apparently randomly and in batches, in the Execution Environment (EE) joblog
HRNDR069E CPE CONNECT PROCESSING FAILED FOR XXHRERELAYRC=XX08 CPE HEX DUMP FOLLOWS
HRNDR073E 7A00008000000000C8EAB1BA321C90C4006DEBB00000000000000000000000000000000000000000
HRNDR073E 00000000000000003C037AD0C8D9C5D9C5D3C1E88036020100060102100803D3E3C1F0F0F0F0F108
HRNDR073E 04D6D4D9C8E4D9F0F0194083D3E2E3C140404040D3E2E3C1D5E3F0F04040404040404040
HRNRA017E RELAY connection failed with RC=2816; TCP/IP connection closed
Environment:
============
o all z/OS versions of Object Service Broker EEs
Symptoms:
=========
The symptoms are one or more sets of the above messages. Nothing abends or appears to fail
Cause:
======
This is normally caused by a remote Data Object Broker (DOB) trying to make peer connections to the wrong TCPIP port. I.e. to an EE port. A DOB can only PEER connect to another DOB, not an EE.
Resolution:
===========
Correct the HURON.DIR (open platforms) or S6BRELAY file (z/OS) on the remote system to assign the correct port for the local DOB.
Description:
===========
The following sequence of messages can appear, apparently randomly and in batches, in the Execution Environment (EE) joblog
HRNDR069E CPE CONNECT PROCESSING FAILED FOR XXHRERELAYRC=XX08 CPE HEX DUMP FOLLOWS
HRNDR073E 7A00008000000000C8EAB1BA321C90C4006DEBB00000000000000000000000000000000000000000
HRNDR073E 00000000000000003C037AD0C8D9C5D9C5D3C1E88036020100060102100803D3E3C1F0F0F0F0F108
HRNDR073E 04D6D4D9C8E4D9F0F0194083D3E2E3C140404040D3E2E3C1D5E3F0F04040404040404040
HRNRA017E RELAY connection failed with RC=2816; TCP/IP connection closed
Environment:
============
o all z/OS versions of Object Service Broker EEs
Symptoms:
=========
The symptoms are one or more sets of the above messages. Nothing abends or appears to fail
Cause:
======
This is normally caused by a remote Data Object Broker (DOB) trying to make peer connections to the wrong TCPIP port. I.e. to an EE port. A DOB can only PEER connect to another DOB, not an EE.
Resolution:
===========
Correct the HURON.DIR (open platforms) or S6BRELAY file (z/OS) on the remote system to assign the correct port for the local DOB.
Issue/Introduction
HRNDR069E CPE CONNECT PROCESSING FAILED FOR XXHRERELAYRC=XX08 CPE HEX DUMP FOLLOWS
Feedback
Yes
No
Powered by
