## TCPware V5.7 Management Guide

- Introduction
- PATHWORKS Version 4 Server
- PATHWORKS Version 5 Server
- On the PC
- Troubleshooting
  - Version 4
  - Version 5

Chapter 27

PATHWORKS Support

# Introduction

You can use TCPware for OpenVMS as a transport for HP's PATHWORKS product running between the OpenVMS system and a personal computer (PC).

You do not need to perform special configuration steps on either the OpenVMS system or the PC to use TCPware with PATHWORKS. However, the following information about PATHWORKS and TCPware may be helpful.

See Troubleshooting for troubleshooting tips.

# PATHWORKS Version 4 Server

The VAX, Alpha or I64 system runs the PATHWORKS server software. It resides in the SYS$COMMON:[PCSA] directory. When you use TCPware and PATHWORKS, note the following:

• TCPware writes error logs to the SYS$SYSROOT:[PCSA] directory.

• Make sure that you start TCPware before starting PATHWORKS.

• Make sure that you use the following command when you start PATHWORKS on the VAX, Alpha or I64 system:

$ @SYS$STARTUP:PCFS_STARTUP TCP

After you start PATHWORKS on your VAX/Alpha/I64 system:

• The OpenVMS DCL command SHOW SYSTEM lists two processes:

– NBNS

– PCFS_SERVER

• The SHOW CONNECTIONS command in TCPware Network Control Utility (NETCU) shows the following two PATHWORKS-related services:

ID 1 | RecvQ | SendQ | Local address... | Foreign address... | State...
BGnn | 0 | 0 | *.netbios-ssn | *.* | LISTEN
BGnn | 0 | 0 | *.netbios-ns | *.* |
1 The actual values may be different |  |  |  |  |

# PATHWORKS Version 5 Server

The VAX, Alpha or I64 system runs the PATHWORKS server software. When you use TCPware and PATHWORKS, note the following:

• Make sure that you start TCPware before starting PATHWORKS

• Configure the PATHWORKS Server to use TCP/IP as a transport

After you start PATHWORKS on the VAX/Alpha/I64 system:

• The OpenVMS DCL command SHOW SYSTEM lists the PATHWORKS master process PWRK$MASTER and several other PATHWORKS processes.

• The TCPware SHOW CONNECTIONS command in NETCU shows the following PATHWORKS-related services:

ID 1 | RecvQ | SendQ | Local address... | Foreign address... | State...
INETnn | 0 | 0 | *.netbios-ssn | *.* | LISTEN
INETnn | 0 | 0 | *.netbios-ns | *.* |
INETnn | 0 | 0 | *.netbios-dgm | *.* |
1 The actual values may be different |  |  |  |  |

# On the PC

TCPware and PATHWORKS were tested together with several third party PC TCP/IP products and LAN adapters, including the following:

• PATHWORKS for DOS (TCP/IP) software with an HP DEPCA adapter

• Ungermann-Bass's LAN Manager 2.0 and TCP BNS 16.51 software with an Ungermann-Bass NIUpc/EOTP1 adapter

When you install and configure the PC software:

• PATHWORKS Version 4 updates the CONFIG.SYS and AUTOEXEC.BAT files.

• PATHWORKS Version 4 and Version 5 create either a PROTOCOL.INI or LANMAN.INI file.

• Some PC software products may require that you specify the VAX server name in all uppercase when you use the USE or NET USE command.

• When using Ungermann-Bass's PC software, you may need to use the NBUTIL utility to specify the name and internet address of the OpenVMS system.

1 NIUpc is a registered trademark of Ungermann-Bass, Inc.

# Troubleshooting

## Version 4

If you cannot make a complete connection between the workstation and the OpenVMS system using PATHWORKS Version 4, do the following:

• Check the TCPWARE:HOSTS. file on the OpenVMS system. Make sure that the workstation's name and internet address are in the file.

• Do a SHOW SYSTEM on the OpenVMS system. Make sure that the NBNS and PCFS_SERVER processes are running; if not, start PATHWORKS on the OpenVMS system.

• Issue the NETCU SHOW CONNECTIONS command on the OpenVMS system. Verify that the *.netbios-ssn and *.netbios-ns services are listed.

• If these services are not listed, make sure that you start TCPWare before PATHWORKS.

• Look in the SYS$SYSROOT:[PCSA] directory on the OpenVMS system, to see if any of the error log files contain useful information.

• On the workstation, check that the PROTOCOL.INI or LANMAN.INI file has the correct configuration information for your workstation.

• On the workstation, verify that the syntax of your USE or NET USE command is correct. (Note the use of uppercase characters.)

• Make sure that the service specified in the USE or NET USE command is listed in the SYS$SYSROOT:[PCSA]PCFS$SERVICE_DATABASE.DAT file on the OpenVMS system.

## Version 5

If you cannot make a complete connection between the workstation and the OpenVMS system using PATHWORKS Version 5, do the following:

• Make sure TCPware knows how to map the workstation's host name to its internet address. Check this using NSLOOKUP hostname. NSLOOKUP should report the internet address for the host. If it does not, update your primary DNS server so it can resolve the workstation name (or add an entry for the workstation in the OpenVMS system's TCPWARE:HOSTS. file).

• Do a SHOW SYSTEM on the OpenVMS system. Make sure that the PWRK$MASTER, NETBIOS, and other PWRK$ processes are running. If they are not, start PATHWORKS on the OpenVMS system.

• Issue the NETCU SHOW CONNECTIONS command on the OpenVMS system. Verify that the *.netbios-ssn, *.netbios-ns, and *.netbios-dgm services are listed. If these services are not listed, make sure that you start TCPware before PATHWORKS.

• Look in the PWRK$ROOT:[LOGS] directory on the OpenVMS system to see if any of the error log files contain useful information. See specifically the file PWRK$KNBDAEMON_node.LOG, where node is the particular PATHWORKS node. This contains the TCP/IP binding information.

• On the workstation, check that the PROTOCOL.INI or LANMAN.INI file has the correct configuration information for your workstation.

• On the workstation, verify that the syntax of your USE or NET USE command is correct. (Note the use of uppercase characters.)

• Make sure that the service specified in the USE or NET USE command is available on the OpenVMS system.