Hello All,

Can you please help me with my sender channel in linux/rhel. The receiver is not coming up at mainframe system. Firewall is allowed and it gives us server reset in splunk log.

When I started sender from mainframe queue manager my receiver came up running.

Is there a security that is stoping receiver to come up at mainframe system.? 

09/11/2025 12:33:54 PM - Process(681578.1) User(mqm) Program(runmqchl)
                    Host(eqmqhost01) Installation(Installation1)
                    VRMF(9.4.0.5) QMgr(TEST)
                    Time(2025-09-11T16:33:54.598Z)
                    ArithInsert1(111) ArithInsert2(111)
                    CommentInsert1(Mainframe (10.145.22.10) (1467))
                    CommentInsert2(TCP/IP)
                    CommentInsert3(TEST.MQ.IP)

AMQ9202E: Remote host not available, retry later.

EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'Mainframe
(10.145.22.10) (1467)' for channel TEST.MQ.IP was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a TCP/IP conversation later.

In some cases the remote host cannot be determined and so is shown as '????'.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
111 (X'6F'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'Mainframe (10.145.22.10) (1467)' was not running.  If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.

Thanks

KP

Hi,

It looks like you have "Mainframe (10.145.22.10) (1467)" in your conname on your linux queue manager.

Try "10.145.22.10(1467)"

Regards, Matt.

Hello All,

Can you please help me with my sender channel in linux/rhel. The receiver is not coming up at mainframe system. Firewall is allowed and it gives us server reset in splunk log.

When I started sender from mainframe queue manager my receiver came up running.

Is there a security that is stoping receiver to come up at mainframe system.? 

09/11/2025 12:33:54 PM - Process(681578.1) User(mqm) Program(runmqchl)
                    Host(eqmqhost01) Installation(Installation1)
                    VRMF(9.4.0.5) QMgr(TEST)
                    Time(2025-09-11T16:33:54.598Z)
                    ArithInsert1(111) ArithInsert2(111)
                    CommentInsert1(Mainframe (10.145.22.10) (1467))
                    CommentInsert2(TCP/IP)
                    CommentInsert3(TEST.MQ.IP)

AMQ9202E: Remote host not available, retry later.

EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'Mainframe
(10.145.22.10) (1467)' for channel TEST.MQ.IP was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a TCP/IP conversation later.

In some cases the remote host cannot be determined and so is shown as '????'.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
111 (X'6F'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'Mainframe (10.145.22.10) (1467)' was not running.  If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.

Thanks

KP

Hello All,

Can you please help me with my sender channel in linux/rhel. The receiver is not coming up at mainframe system. Firewall is allowed and it gives us server reset in splunk log.

When I started sender from mainframe queue manager my receiver came up running.

Is there a security that is stoping receiver to come up at mainframe system.? 

09/11/2025 12:33:54 PM - Process(681578.1) User(mqm) Program(runmqchl)
                    Host(eqmqhost01) Installation(Installation1)
                    VRMF(9.4.0.5) QMgr(TEST)
                    Time(2025-09-11T16:33:54.598Z)
                    ArithInsert1(111) ArithInsert2(111)
                    CommentInsert1(Mainframe (10.145.22.10) (1467))
                    CommentInsert2(TCP/IP)
                    CommentInsert3(TEST.MQ.IP)

AMQ9202E: Remote host not available, retry later.

EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'Mainframe
(10.145.22.10) (1467)' for channel TEST.MQ.IP was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a TCP/IP conversation later.

In some cases the remote host cannot be determined and so is shown as '????'.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
111 (X'6F'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'Mainframe (10.145.22.10) (1467)' was not running.  If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.

Thanks

KP

Hello All,

Can you please help me with my sender channel in linux/rhel. The receiver is not coming up at mainframe system. Firewall is allowed and it gives us server reset in splunk log.

When I started sender from mainframe queue manager my receiver came up running.

Is there a security that is stoping receiver to come up at mainframe system.? 

09/11/2025 12:33:54 PM - Process(681578.1) User(mqm) Program(runmqchl)
                    Host(eqmqhost01) Installation(Installation1)
                    VRMF(9.4.0.5) QMgr(TEST)
                    Time(2025-09-11T16:33:54.598Z)
                    ArithInsert1(111) ArithInsert2(111)
                    CommentInsert1(Mainframe (10.145.22.10) (1467))
                    CommentInsert2(TCP/IP)
                    CommentInsert3(TEST.MQ.IP)

AMQ9202E: Remote host not available, retry later.

EXPLANATION:
The attempt to allocate a conversation using TCP/IP to host 'Mainframe
(10.145.22.10) (1467)' for channel TEST.MQ.IP was not successful.
However the error may be a transitory one and it may be possible to
successfully allocate a TCP/IP conversation later.

In some cases the remote host cannot be determined and so is shown as '????'.
ACTION:
Try the connection again later. If the failure persists, record the error
values and contact your systems administrator. The return code from TCP/IP is
111 (X'6F'). The reason for the failure may be that this host cannot reach the
destination host. It may also be possible that the listening program at host
'Mainframe (10.145.22.10) (1467)' was not running.  If this is the case, perform
the relevant operations to start the TCP/IP listening program, and try again.

Thanks

KP