Technical data

Managing TCP/IP Services
1.2 Enabling PATHWORKS/Advanced Server and DECnet-over-TCP/IP Support
1.2 Enabling PATHWORKS/Advanced Server and
DECnet-over-TCP/IP Support
TCP/IP Services software includes the PATHWORKS Internet Protocol (PWIP)
driver and the PWIP ancillary control process (PWIP_ACP).
The PWIP driver allows OpenVMS systems that are running both the
Compaq PATHWORKS/Advanced Server and the TCP/IP Services software
to communicate with personal computers running PATHWORKS client software.
It also enables the DECnet-over-TCP/IP feature, which is included with the
DECnet-Plus for OpenVMS Version 6.0 and later software. For more information
about DECnet over TCP/IP, see the DECnet-Plus for OpenVMS documentation.
1.2.1 Starting and Stopping the PWIP Driver
The PWIP driver can be shut down and started independently. The following files
are provided:
• SYS$STARTUP:TCPIP$PWIP_DRIVER_STARTUP.COM allows you to start
up the PWIP driver.
• SYS$STARTUP:TCPIP$PWIP_DRIVER_SHUTDOWN.COM allows you to
shut down the PWIP driver.
To preserve site-specific parameter settings and commands, create the following
files. These files are not overwritten when you reinstall TCP/IP Services.
• SYS$STARTUP:TCPIP$PWIP_DRIVER_SYSTARTUP.COM can be used as a
repository for site-specific definitions and parameters to be invoked when the
PWIP driver is started.
• SYS$STARTUP:TCPIP$PWIP_DRIVER_SYSHUTDOWN.COM can be used
as a repository for site-specific definitions and parameters to be invoked when
the PWIP driver is shut down.
To start the PWIP driver, run TCPIP$CONFIG or enter the following command:
$ @SYS$STARTUP:TCPIP$PWIP_DRIVER_STARTUP.COM
To shut down the connection to the PWIP driver, enter the following command:
$ @SYS$STARTUP:TCPIP$PWIP_DRIVER_SHUTDOWN.COM
1.3 Setting Up User Accounts and Proxy Identities
You will need to set up accounts for local users, coordinate the establishment of
corresponding accounts on remote systems, and create accounts for remote users
who will be accessing server components on the local host.
When creating accounts for remote users, you can create one account for all
remote users, an account for groups of remote users, or accounts for individual
users. The strategy you use depends on your organization, system resources, and
security needs.
Certain product components (for example, LPD, RSH, RLOGIN, and NFS) act as
servers for remote clients. You control access to your system and to these services
by giving remote users proxy identities. A proxy identity maps a user account on
one host to an account on another host. The information you provide with each
entry, along with the privileges you set for the account, lets you specifically grant
or deny access to your system.
Managing TCP/IP Services 1–5