Upgrading CA XCOM for AIX r11.0 to r11.6 SP01

Document ID:  TEC1692437
Last Modified Date:  06/08/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details


  • CA XCOM Data Transport


  • CA XCOM Data Transport:Release:11
  • CA XCOM Data Transport:Release:11.0 SP01
  • CA XCOM Data Transport:Release:11.6 SP1


  • CA XCOM Data Transport for AIX:XCURS6

In the upgrade from r11.0 0603 or from r11.6 sp00,  /etc/inetd.conf retains the legacy txpi and txpis config statements:

txpi stream tcp nowait root /usr/lib/xcom/xcomtcp xcomtcp REMOTE 0
txpis stream tcp nowait root /usr/lib/xcom/xcomtcp xcomtcp REMOTE 0 SSL

added is , if it was not already there from r11.6 sp00 or if it came upgraded from r11.0 0603:

txpi6 stream tcp6 nowait root /opt/CA/XCOM/bin/xcomtcp xcomtcp REMOTE 0 NONE IPV6
txpis6 stream tcp6 nowait root /opt/CA/XCOM/bin/xcomtcp xcomtcp REMOTE 0 SSL IPV6

After upgrading to r11.6 SP01 the standard transmissions fail with a transmission error:
XCOMU0297E Error requesting header confirmation: Txpi 227: Socket received 0 bytes: partner closed socket. Last error: 0

XCOM r11.0, XCOM r11.6 SP01 for AIX

The cause, is that the legacy /etc/inetd.conf for txpi and txpis statements is retained:

txpi stream tcp nowait root /usr/lib/xcom/xcomtcp xcomtcp REMOTE 0
txpis stream tcp nowait root /usr/lib/xcom/xcomtcp xcomtcp REMOTE 0 SSL

BUT ....

the /usr/lib/xcom symbolic links are for backwards compatibility to r11.0 release:

lrwxrwxrwx 1 root system 24 May 02 13:14 xcomend -> /opt/CA/XCOM/cmd/xcomend
lrwxrwxrwx 1 root system 23 May 02 13:14 xcomlp -> /opt/CA/XCOM/cmd/xcomlp
lrwxrwxrwx 1 root system 25 May 02 13:14 xcomntfy -> /opt/CA/XCOM/cmd/xcomntfy
lrwxrwxrwx 1 root system 23 May 02 13:14 xcompp -> /opt/CA/XCOM/cmd/xcompp
lrwxrwxrwx 1 root system 24 May 02 13:14 xcompre -> /opt/CA/XCOM/cmd/xcompre

In /usr/lib/xcom there is no symbolic link for xcomtcp -> /opt/CA/XCOM/bin/xcomtcp to allow the backwards compatibility and given that the upgrade is not changing /etc/inetd.conf causing the failure of the transfer. 


CA XCOM r11.0 should be uninstalled cleanly, which includes clearing the /etc/inetd.conf file and refreshing the inetd service before installing r11.6 SP01.

We have updated the CA XCOM Data Transport Installation and Upgrading manual to provide the proper upgrade instructions.


Additional Information:

A few insights:

1) Upgrading from r11.0 to r11.6 SP01, r11.0 already present

If we upgrade from r11.0 to r11.6 SP01 directly without uninstalling r11.6 SP01, the direct upgrade is not supported. Therefore, before you proceed to upgrade you have to uninstall the r11.0 product by issuing the "installp -u xcom62" command, and clean the txpi entries from the /etc/inetd.conf file and refresh the inetd service.
If you do not uninstall the product before proceeding to an upgrade, the symbolic links will not be correct.

2) Upgrading from r11.0 to r11.6 SP01, with r11.0 uninstalled

The r11.0 uninstaller does not clean up /etc/inetd.conf file.
In case of r11.6 SP00, installer force updates the txpi information in /etc/inetd.conf file, but in case of r11.6 SP01, we have made some changes in installer to update the /etc/inetd.conf file only when it does not find txpi details. This is done in order to retain the user’s customized locations.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255


Not what you were looking for?

Search Again >

Product Information

Support by Product >


Join a Community >

Chat with CA

Just give us some brief information and we'll connect you to the right CA ExpertCA sales representative.

Our hours of availability are 8AM - 5PM CST.

All Fields Required


We're matching your request.

Unfortunately, we can't connect you to an agent. If you are not automatically redirected please click here.

  • {{message.agentProfile.name}} will be helping you today.

    View Profile

  • Transfered to {{message.agentProfile.name}}

    {{message.agentProfile.name}} joined the conversation

    {{message.agentProfile.name}} left the conversation

  • Your chat with {{$storage.chatSession.messages[$index - 1].agentProfile.name}} has ended.
    Thank you for your interest in CA.

    Rate Your Chat Experience.


agent is typing