Process Software: TCPware FAQ: Configuration

Why does TCPware hang after installing VMS ECO?

A change included in the VMS LAN ecos (LAN eco 0700 for VMS 7.3-2, the corresponding UPDATE ecos, and likely others for VMS 8.x) can cause all versions of TCPware to hang. This problem is fixed in DRIVERS eco DRIVERS_V5092P020 for TCPware 5.9-2 and up.

This problem appears as TCPware being unable to receive any network packets after having received 5000 packets. Problems can also appear after receiving 5000 ARP or RARP packets.

This problem is easily worked around by setting bit 16 (0x10000 hex) in the system parameter LAN_FLAGS using SYSGEN or SYSMAN as appropriate. Fortunately, this parameter is dynamic and therefore a system reboot is not required.

How can I remove TCPware after it has been installed?

You must execute the command procedure TCPWARE_REMOVE.COM. To remove all of TCPware you would do the following:

@TCPWARE:TCPWARE_REMOVE TCPware

Can an IP address be changed without having to re-install TCPware?

The following outlines how to change an IP address.

Before changing the address by running CNFNET you should make a copy of your TCPPWARE_CONFIGURE.COM and your HOSTS. file.
Shutdown TCPware. ($@TCPWARE:SHUTNETi)
Execute the CNFNET procedure and change your IP address. ($@TCPWARE:CNFNET TCP)
If necessary make changes to your HOSTS. file and any changes needed in DNS.
Start TCPware. ($@TCPWARE:STARTNET)

How can I change my subnet mask from a class C mask (255.255.255.0) to a class B mask (255.255.0.0)?

Run the TCPware configuration program ($@TCPWARE:CNFNET TCP) and change the mask when prompted.

Is TCPware affected by the same limitations that require OpenVMS system managers to patch their systems for the Delta Time problem?

TCPware is affected by this limitation in only two instances:

In Line Printer Services: if the user sets a queue timeout/retry to be more than 9,999 days.
In FSS-OpenVMS: if the user sets up a password expiration to be more than 9,999 days.

If you might be affected, contact HP for distribution channels and other information.

Does TCPware support the Digital EtherWorks (DE602) PCI Ethernet Card?

Yes, but you must define a logical so TCPware can recognize the new EIA0 device name.

You can define a logical for a supported device that references the unsupported EIA0 device and then configure TCPware to use the supported device. To configure the card:

Define the logical:
```
$ DEFINE/SYSTEM/EXEC EWA0 EIA0
```
Then configure TCPware to use device EWA0. If your system has an EWA0 device already defined, define the logical EWB0 to reference EIA0.
Then configure TCPware to use device EWA1. If your system has an EWB0 device already defined, define the logical EWC0 to reference EIA0.
Then configure TCPware to use device EWA3.

When you use CNFNET and it asks "Enter the line identifications" the default that CNFNET gives will not include the new line and you will have to enter the lines you want configured manually.

How do I configure the EIA0 (DE602) Ethernet card?

TCPware supports the Digital EtherWorks (DE602) PCI Ethernet Card.

You can define a logical for a supported device that references the unsupported EIA0 device and then configure TCPware to use the supported device.

Follow these instructions to configure the card.

Define the logical:
```
$ DEFINE/SYSTEM/EXEC EWA0 EIA0
```
Then configure TCPware to use device EWA0.
If your system has an EWA0 device already defined, define the logical EWB0 to reference EIA0. Then configure TCPware to use device EWA1.
If your system has an EWB0 device already defined, define the logical EWC0 to reference EIA0. Then configure TCPware to use device EWA2.
When you use CNFNET and it asks to "Enter the line identifications" the default given by CNFNET will not include the new line so you have to enter the lines you want configured.
```
VMS Device	TCPware Device
EIA0		EWA-0
EIB0		EWA-1
EIC0		EWA-2
```

Note: Please use this configuration method for all EIA Ethernet cards on your system.

What has to be done to enable UCX emulation in TCPware?

UCX emulation is enabled by default when TCPware starts. You can confirm this doing a SHOW DEVICE BG. If a BG0 devices has been created, then UCX emulation has been started.

Setting up TCPware in a mixed platform cluster

The cluster needs to be set up to share the data files. This can be done by having separate TCPWARE_LOGICALS.COM files for the Alpha nodes and the VAX nodes.

On the VAX nodes, the TCPWARE_LOGICALS.COM file would look something like this:

$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_COMMON SYS$COMMON:,ALPHA$DKA300:[VMS$COMMON.]
$ !
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_SPECIFIC SYS$SPECIFIC:
$ !
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT SYS$SYSROOT:,ALPHA$DKA300:[VMS$COMMON.]
$ !
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE "TCPWARE_ROOT:[TCPWARE]"
$ DEFINE/SYSTEM/NOLOG TCPWARE_INCLUDE "TCPWARE_ROOT:[TCPWARE.INCLUDE]"

On the Alpha nodes, the TCPWARE_LOGICALS.COM file would look something like this (this is the "normal" one):

$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_COMMON SYS$COMMON:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_SPECIFIC SYS$SPECIFIC:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE_ROOT SYS$SYSROOT:
$ DEFINE/SYSTEM/NOLOG/EXEC TCPWARE "TCPWARE_ROOT:[TCPWARE]"
$ DEFINE/SYSTEM/NOLOG TCPWARE_INCLUDE "TCPWARE_ROOT:[TCPWARE.INCLUDE]"

The common files reside on Alpha's system disk (ALPHA$DKA300:[VMS$COMMON.TCPWARE...).

Keep in mind the following:

When installing a new version, "restore" the logicals to their original values on the VAX's when doing the installation.
After installing, DELETE (or rename) the SYS$SYSROOT:[TCPWARE...]*_CONTROL.COM files on the VAX systems. If this isn't done, TCPware will fail to start because it will find two sets of all the control files and will try to execute them twice which will cause problems.
After installing, clean up any of the data files that TCPware creates during installation if it doesn't find them (since it won't find them since the logical no longer points to include them). This is on the VAX system.
Restore the TCPWARE_LOGICALS.COM to that shown above for the VAX.