Topic
  • 4 replies
  • Latest Post - ‏2017-09-13T22:06:20Z by MoragH
AG37
AG37
4 Posts

Pinned topic Intermitten Transfer failuer as Remote host '' not available, retry later.

‏2017-09-12T17:16:18Z | mq8

Scheduled transfer failing intermittently with below error captured at source server where MQ client is installed. But in when the transfer is re-triggered after few mins the messages getting processed. No issues from network perspective and backup process. Any idea what could be done to avoid failuer at 1st place? 

Process(25690.1) User(aabadm) Program(mqftssndc) 
Host(XX) Installation(Installation1) 
VRMF(7.5.0.0) 
AMQ9202: Remote host '' not available, retry later. 

EXPLANATION: 
The attempt to allocate a conversation using TCP/IP to host '' for channel 
SYSTEM.DEF.CLNTCONN was not successful. However the error may be a transitory 
one and it may be possible to successfully allocate a TCP/IP conversation 
later.

  • MoragH
    MoragH
    106 Posts

    Re: Intermitten Transfer failuer as Remote host '' not available, retry later.

    ‏2017-09-13T05:56:53Z  

    What is in the definition of the SYSTEM.DEF.CLNTCONN channel that you are trying to use? Your hostname appears to be empty. Are you using the default channel in a CCDT without updating it to be usable?

    Is it supposed to be using that entry in the CCDT? Should you have removed it? Should it be using another entry instead. Can you show us the contents of your CCDT if you are using one?

    Cheers,
    Morag
     

  • AG37
    AG37
    4 Posts

    Re: Intermitten Transfer failuer as Remote host '' not available, retry later.

    ‏2017-09-13T17:10:47Z  
    • MoragH
    • ‏2017-09-13T05:56:53Z

    What is in the definition of the SYSTEM.DEF.CLNTCONN channel that you are trying to use? Your hostname appears to be empty. Are you using the default channel in a CCDT without updating it to be usable?

    Is it supposed to be using that entry in the CCDT? Should you have removed it? Should it be using another entry instead. Can you show us the contents of your CCDT if you are using one?

    Cheers,
    Morag
     

    Hi Morag,

     

    CCDT is binary file so I'm not able read it but I did use "dis chl(*) chltype(clntconn) all" and can see CHANNEL(SYSTEM.DEF.CLNTCONN) is present alomg with one more channel with type clntconn, below details of SYSTEM.DEF.CLNTCONN channel

     

    AMQ8414: Display Channel details.
       CHANNEL(SYSTEM.DEF.CLNTCONN)            CHLTYPE(CLNTCONN)
       AFFINITY(PREFERRED)                     ALTDATE(XXXXX)
       ALTTIME(20.04.30)                       CERTLABL( )
       CLNTWGHT(0)                             COMPHDR(NONE)
       COMPMSG(NONE)                           CONNAME( )
       DEFRECON(NO)                            DESCR( )
       HBINT(300)                              KAINT(AUTO)
       LOCLADDR( )                             MAXMSGL(4194304)
       MODENAME( )                             PASSWORD( )
       QMNAME( )                               RCVDATA( )
       RCVEXIT( )                              SCYDATA( )
       SCYEXIT( )                              SENDDATA( )
       SENDEXIT( )                             SHARECNV(10)
       SSLCIPH( )                              SSLPEER( )
       TPNAME( )                               TRPTYPE(TCP)
       USERID( )

  • AG37
    AG37
    4 Posts

    Re: Intermitten Transfer failuer as Remote host '' not available, retry later.

    ‏2017-09-13T17:18:14Z  

    Also Application has CCDT file which contains CLNTCONN definition. The error we see at Source application where client is installed when inititate transfer is as : 
    KFT0002 Warning: MQSERVER environment variable not set 
    KFT0003 Failed: MQSeries comp code 2, reason 2058. Function MQCONN, on object

  • MoragH
    MoragH
    106 Posts

    Re: Intermitten Transfer failuer as Remote host '' not available, retry later.

    ‏2017-09-13T22:06:20Z  

    If you are using a CCDT (and I'm not 100% certain given your two posts), you can read it using a V8 runmqsc with the -n option, or with MQSCX (on any version of MQ).

    Do you know whether you are deliberately trying to use the SYSTEM.DEF.CLNTCONN channel? I assume not, but you did not confirm. I can see from your provided definition that indeed the CONNAME is empty, so this is root cause of your AMQ9202 error.

    To correct you need to confirm whether you are supposed to be using CCDT or MQSERVER. If CCDT, then to fix you can either remove the SYSTEM.DEF.CLNTCONN from your CCDT, or provide a QMNAME on the other CLNTCONN definition that you didn't show us, and ensure you specify that queue manager name in the connecting application.

    Cheers,
    Morag