Digital PDFs

AA-JU51A-TE

December 1987

133 pages

Original

6.1MB

Document:	VAXmate VAX VMS Server Guide Jan1987
Order Number:	AA-JU51A-TE
Revision:
Pages:	133
Original Filename:	http://bitsavers.org/pdf/dec/vaxmate/AA-JU51A-TE_VAXmate_VAX_VMS_Server_Guide_Jan1987.pdf

OCR Text

AA-JU51A-TE

VAXjVMS

Server Guide

software

--~---------

mate
VAXjVMS

Server Guide
(j

(

, , - - - ----~----. - - ----~--~~

-~~~--~~.-

First Printing, January 1987

© Digital Equipment Corporation 1987. All Rights Reserved.
The information in this document is subject to change without notice and should not be
construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document.
The software described in this document is furnished under a license and may only be used or
copied in accordance with the terms of such license.
No responsibility is assumed for the use or reliability of software on equipment that is not
supplied by DIGITAL or its affiliated companies.
Several Program Information Files and device drivers are supplied for use with non-DIGITAL
products and referenced in this document. These are provided on an "AS IS" basis without any
warranty of any kind, either expressed or implied.
IBM is a registered trademark of International Business Machines, Inc.

The following are trademarks of Digital Equipment Corporation:

mamaa!a

DEC
DECconnect
DECmate
DECsystem-l0
DECSYSTEM-20
DECUS
DECwriter
DEMPR
DESTA

Printed in U.SA.

DEINI
DlBOL
MASSBUS
PDP
PjOS
Professional
Rainbow
RSTS
RSX
UNIBUS

VAX
VAXmate
VMS
VT
VT220
VT240
Work Processor

Contents

Preface ..

vii

Chapter 1
Installing the VAXNMS Server ................. .
Installing the VAXNMS Server Software . . . . . . . . . . . . .
Adding VAXNMS Server Information to the Network Start-Up
File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding VAXNMS Server Information to the System
Administrator's Log-In File . . . . . . . . . . . . . . . . . . .
Preparing the VAXNMS Server for Workstation Software
Creating Workstation System Accounts and Directories
Registering the First Node. .
. .......... .
Adding the First User . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2
VAXIVMS Server Operations.................. .
Starting the VAXNMS Server. . . . . . . .
. . . . .
Stopping the VAXNMS Server . . . . . . .
. . . . . .
. . . . . .
Adding a User .... . . . . . .
Removing a User. . . . . . . . . . . . . . . .
. . . .. .
an
Application.
.
.
.
.
.
.
.
.
.
.
.
.
. . . . .
Installing
Unrestricted Applications. . . . . . . . . . . . . . . . . . . .
Restricted Applications. .
. .............. .
Removing an Application . ..
.. . . . . . . . . . . . . . . .
Unrestricted Applications.
.. . . . .
. . . . .
Restricted Applications . . . . . . . . . . . . . . . . . . . . .

1- 1

1- 2
1- 10
1- 11
1- 11
1- 12
1- 15
1- 16

2- 1
2- 2
2- 2
2- 4
2- 6
2- 6
2- 7
2- 8
2- 10
2- 10
2- 10

Contents iii

Adding a Printer . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removing a Printer. . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a Common Directory . . . . . . .
Removing a Common Directory . . . . . . . . . . . . .
Modifying the Information System . . . . . . . . . . . .
Backing Up the VAXNMS Server .. .
Maintaining the Server Log File . . . .

Chapter 3
VAXNMS Server Commands
The VAXNMS Server Operator Interface . . . . . . .
Allowing Connections to the VAXNMS Server .. .... .
Allowing Unregistered Nodes . . . . . . . . . . .. .... .
Closing a Connection . . . . . . . . . . . . . . ..
. . . . .
Closing a File. . . . . . . . . . . . . . . . . . . ..
. . . . .
. . . . .
Closing A Session . . . . . . . . . . . . . . . . ..
Returning to the VAXNMS Operating System .
. . . . .
Getting Help . . . . . . . . . . . . . . . . . . . . .
. . . . .
Changing the VAXNMS Server Limits. . . . . .. .... .
Limiting the Number of Connections . . . . . . . . . . . .
Limiting the Number of Open Files ..
Limiting the Number of Sessions .
Logging Network Events ....
Refusing Connections . . .. . . . .
Refusing Unregistered Nodes . . . . . . . . . . . . . . . . . .
Setting the Attributes for Workstation Access . . . . . . . .
Changing the Log File. . . . . . . . . . . . . . . . . . . . . . .
Showing the Connections to the VAXNMS Server. . . . . .
Showing the Open Files. . . . . . . . . . . . . . . . . . . . . .
Showing the Limits . . . . . . . . . . . . . . . . . . . . . . . .
Showing the Log File Name . . . . . . . . . . . . . . . . . . .
Showing the Sessions . . . . . . . . . . . . . . . . . . . . . . .
Showing the Status of Server Connections. . . . . . . . . . .
Showing the VAXNMS Server's Version Number . . . . . .
Restarting the VAXNMS Server . . . .
. . . . . . . .
Stopping the VAXNMS Server . . . . . . . . . . . . . . . . .

Contents iv

2- 11
2- 15
2- 16
2- 17
2- 17
2- 18
2- 19

3- 1
3- 1
3- 4
3- 5
3- 6
3- 8
3- 10
3- 12
3- 13
3- 14
3- 16
3- 18
3- 19
3- 20
3- 23
3- 24
3- 25
3- 26
3- 28

3- 29
3- 30
3- 31
3- 32
3- 33
3- 34
3- 35
3- 36

Chapter 4
VAXNMS Server Configuration ........ .
The PCFS STARTUP.COM File . . . . . . . . . .
Including Operator Interface Commands. . . .
Changing VAXNMS Limits and Quotas
. . . . .
VAXNMS Input/Output Channels. . .
Adding and Removing Resources.
. . . . . . . . . .
Adding a User . . . . . . . . . . . . . . . . . .. . . . . .
Adding a Common Directory. . . . . . . . . . .
Adding an Application. . . . . . . . . . . . . . .
Adding a New Printer Form . . . . . . . . . . .
Adding Another Printer. . . . . . . . . . . . . .
Removing a User. . . . . . . . . . . . . .
Removing a Common Directory . . . . . . . . .
Removing an Application. . . . . . . .
Removing a Printer Queue . . . . . . . . . . . . . . . . . . .

Chapter 5
VAX/VMS Server Messages ..
Messages in the Log File . . . . . . . . . . . . . . . . . . . . . ..
Messages from the VAXNMS Server Operator Interface

4- 1
4- 1
4- 4
4- 5
4- 6
4- 7
4- 8
4- 9
4- 10
4- 12
4- 15
4- 18
4- 19
4- 19
4- 20

5- 1
5- 2
5- 15

Tables
Table 1-1
Table 2-1
Table 2-2
Table 3-1
Table 3-2

Accounts Created by VMSINSTAL . . . .
VAXNMS Printers and Forms. . . . . . .
VAXNMS Server Directories to Back Up.
VAXNMS Server Operator Interface Commands . .
VAXNMS Server Events You Can Log. . . . . . . .

1-10
2-12
2-19
3-2
3-20

Directory Structure Created by VMSINSTAL . . .
Directory Structure Created by Option 1. . . . . . .

1-10
1-15

PCFS Administration Utility . . . . . . . . . . . . .

1-12

Figures
Figure 1-1
Figure 1-2

Screens
Screen 1-1

Contents v

Preface

The purpose of this guide is to help the system administrator install and
maintain the VAXNMS server.
This guide assumes the network, including cables, workstations, and other
hardware, is physically connected.

Conventions Used
(

Follow these conventions while using this guide:
•

In examples of dialog between you and the computer, what the
computer displays on the screen is in black. The characters you
type from the keyboard are in color.

•

Type all spaces and punctuation marks exactly as they are printed.

•

When you see Ctrl/C, press and hold the Ctrl key and press the C
key.

•

Square brackets in a command line ( [ ] ) indicate optional command qualifiers. Do not type the brackets when specifying information enclosed in the brackets. For example, you can type HELP, or
you can type HELP and a topic:
HELP [topic]

•

A vertical bar ( I ) indicates you have a choice between two or more

Preface vii

entries. You must select one entry, unless the entries are optional.
For example, when you use the CLOSE CONNECTION command,
you must select an alias or a connection identifier:
CLOSE CONNECTION alias I lID-connection identifier

•

All numbers in this guide are in decimal form unless otherwise

C;
./

Preface viii

Chapter 1
Installing the VAX/VMS
Server
This chapter tells you how to install the VAXNMS server. When you complete the installation procedure in this chapter, you should be able to
access the VAX/VMS server from a workstation using a key diskette.
This installation procedure assumes that:
•

The VAX/VMS operating system and DECnet-VAX are installed
and running on your VAX computer. For instructions on installing
these systems, see the VAX/VMS Release Notes and the
VAXNMS Guide to Software Installation.

•

If you have a MicroVAX computer, all components of MicroVMS
are installed. If they are not, see the MicroVAX User's Guide.

•

If you want to use the VAXmate terminal emulators with the

(

VAX/vMS server, the Local Area Transport (LAT) software is installed and running on your VAX computer.
If an error message is displayed during this procedure, see the Messages

section of this guide or the VAXmate User's Guide, Volume 2.
Follow the installation procedure in the order in which it is presented. The
installation procedure includes:

1- 1

Installing the VAXNMS Server
1.

Installing the VAXNMS server software on the VAX computer

Adding information about the VAXNMS server to the network
start-up file

Adding information about the VAXNMS server to the system administrator's log-in file

Preparing the server for the workstation software
Adding the first user

These procedures are described in the remainder of this chapter.

Installing the VAX/VMS Server Software
This installation procedure, including the installation verification procedure, takes approximately 5 minutes and 1000 blocks of disk space to
complete. After the VAXNMS server is installed, it requires approximately 800 blocks of disk space.
NOTES
Do not install a new version of the VAXNMS server software until all users are disconnected from the server. Use
the PCSERVER SHOW CONNECTIONS command to see
if users are connected. If users are connected, use the
PCSERVER REFUSE CONNECTIONS command to disallow further connections. Then wait until the remaining
users are disconnected.
If disk quota checking is enabled, and you want to run the

Installation Verification Procedure (IVP) portion of the
server installation, first make sure the permanent disk
quota assigned to the system User Identification Code (that
is, UIC [1,4]), is greater than the current usage. If it is not,
the following message may be displayed: "Function
CREATE DIRECTORY: Expected: 0-0, Received: 1-5."
To install the VAXNMS server software:
1.

Set the default directory by typing:
$ SET DEFAULT SYS$UPDATE<Return>

1- 2

Installing the VAXNMS Server

(

NOTE
The following dialog is an example of installing the
VAXNMS server. The dialog that occurs during your installation can differ slightly depending on the configuration
of your VAX computer.
3.

Start VMSINSTAL by typing:
$ ~VMSINSTAL PCFS ddcu<Return>

Where:
PCFS
ddcu

Is the VAXNMS facility name for the VAXNMS server.
Names the device on which the VAXNMS server distribution medium is mounted and where:
dd

Is the device name (for example, CS, MU, DU).

Is the controller J.D. (for example, A, B, C).

Is the unit 'number (for example, 0, 1, 2).

For example, to specify a TK50 tape device, type:

(

$ ~VMSINSTAL PCFS MUAO<Return>

VMSINSTAL displays:
VAX/VMS Software Product Installation Procedure Vl.l

It is 9-MAY-1986 at xx:xx.
Enter a question mark (?) at any time for help.
%VMSINSTAL-W-DECNET, Your DECnet network is up and running.
If there are any other active processes, VMSINSTAL displays:
%VMSINSTAL-W-ACTlVE, The following processes are still active:

A list of active processes is displayed.
4.

Whether or not active processes are displayed, VMSINSTAL asks:

Do you want to continue anyway [NO]?

1- 3

Installing the VAXNMS Server
VMS INSTAL allows you to continue installing the VAXNMS
server with active processes. VMSINSTAL does not interfere with
an active process, and an active process does not interfere with
VMSINSTAL. However, to stop a process before continuing with
the VAXNMS server installation, you can stop the installation.
•

To continue, type:
YES <Return>

•

To stop the installation, press:
<Return>

5. VMSINSTAL asks:

* Are you satisfied with the backup of your system disk [YES]?
•

If you are satisfied with your backup, press:
<Return>

Note that if you fail to back up the system disk, and the
system stops abnormally, you will lose all your system files.
•

If you failed to make a backup or are unsatisfied with the
backup you made, you can return to the VAXNMS DeL
prompt and make a fresh backup by typing:
NO<Return>

Before VMSINSTAL tries to mount the distribution medium, it
asks you to ready the medium on the device you specified in step
3. Be sure you have put the device on-line. VMSINSTAL displays:
Please mount the first volume of the set on [ddcu]:
* Are you ready?

When you have mounted the volume, type:
YES <Return>

If mounting is successful, VMSINSTAL displays:

1- 4

Installing the VAXNMS Server
%MOUNT-I-MOUNTED, PCFS mounted on [ddcu]:
The following products will be processed:
PCFS

V1.1

Beginning installation of PCFS V1.1 at xx:xx
%VMSINSTAL-l-RESTORE,

Restoring product saveset A. .

VMSINSTAL displays:

* Do you want to run the IVP after the installation [YES]?
We recommend you run the IVP, which checks that the VAXNMS
server was installed correctly.

•

To run the IVP after the installation procedure, .press:
<Return>

(
•

To skip the Installation Verification Procedure (IVP), type:
NO<Return>

VMSINSTAL asks:

* Do you want to purge files replaced by this installation [YES]?
•

To purge files replaced by the installation, press:
<Return>

When VMS INSTAL purges files, it deletes old versions of the
VAXNMS server software, if any exist, and therefore saves
disk space.
•
(-'

To save old versions of files replaced by the installation, type:
NO<Return>

1- 5

Installing the VAXNMS Server
i--",
If you tell VMSINSTAL not to purge the old version of the files
and VMSINSTAL does not succeed in installing the new version,
you can recover the old version of the server files.

If you are installing the VAXNMS server for the first time,
VMSINSTAL asks:

* Disk Name for PCFS software [SYS$SYSDEVICE]:
The displayed name is the name of the device that holds VXSYS,
ISSYS, PCAPP, and PCFS SPOOL. Press the Return key to
accept the default, or specifY another device name.

* File version limit for PCFS software [1]:
The displayed number is the number of file versions saved in the
xxSYS, PCAPP, and PCFS SPOOL directories. Press the Return
key to accept the default, or specify another number.

* Password for PCWAPP account [MAINTAIN]:
The displayed password is the password for the PCWAPP account.
Press the Return key to accept the default, or specify another
password.

* Disk Name for PERSONAL/COMMON accounts [SYS$SYSDEVICE]:
The displayed name is the name of the device that holds
VXUSERS, VXAPP, and PCCOMMON. Press the Return key to
accept the default, or specify another device.

* File version limit for PERSONAL/COMMON accounts [1]:
The displayed number is the number of file versions saved in the
PERSONAL/COMMON directories. Press the Return key to accept
the default, or specify another number.

* Password for PCCOMMON account [NONE]:
1- 6

Installing the VAXfVMS Server

(

The displayed information is the default for the PERSONALI
COMMON directories. Press the Return key to accept the default
(no password), or specify a password.

* Group number for PCFS software directories [360]:
The displayed number is the group UIC for the PCFS software directories. Press the Return key to accept the default, or specify another group UIC.
10. VMSINSTAL displays:
%PCFS-I-VERSION, Checking for VMS V4.2 or greater
%PCFS-I-DECNET, Checking for DECnet
%PCFS-I-FREE, Checking for 1000 free blocks
%PCFS-I-LINKING, Linking to produce the installed image SETUIC.EXE
%PCFS-I-DlRECTORY, Checking for [PCFS] on the system disk
If this is the first time you are installing the VAXNMS server,

VMSINSTAL creates the [PCFS) directory on SYS$COMMON and
displays:

(

%VMSINSTAL-I-SYSDIR, This product creates system directory [PCFS].

VMSINSTAL continues:
%PCFS-I-SPECIFY, Specifying target directories for the appropriate
files
%PCFS-I-INITIAL, Creating the initial Server directory structure
%VMSINSTAL-I-SYSDISK, This product creates system disk directory
SYS$SYSDEV
%VMSINSTAL-I-SYSDISK, This product creates system disk directory
SYS$SYSDEV
%VMSINSTAL-I-SYSDISK, This product creates system disk directory
SYS$SYSDEV
%VMSINSTAL-I-SYSDISK, This product creates system disk directory
SYS$SYSDEV
%VMSINSTAL-I-SYSDISK, This product creates system disk directory
SYS$SYSDEV
%PCFS-I-IGNORE, Please ignore all warning messages that follow

(-,

%VMSINSTAL-I-ACCOUNT, This installation creates an account named
PCAPP.

1- 7

Installing the VAXNMS Server
%UAF-I-ADDMSG, user record successfully added
%DCL-I-NEGATED, entity explicitly negated in command string
%VMSINSTAL-W-BADACC, Unable to CREATE/MODIFY account PCAPP.
VMSINSTAL-I-ACCOUNT, This installation creates an account named
PCAPP.
%UAF-I-ADDMSG, user record successfully added
%DCL-I-NEGATED, entity explicitly negated in command string
%VMSINSTAL-W-BADACC, Unable to CREATE/MODIFY account PCWAPP.
%VMSINSTAL-I-ACCOUNT, This installation creates an account named
PCCOMMON.
%UAF-I-ADDMSG, user record successfully added
%DCL-I-NEGATED, entity explicitly negated in command string
%VMSINSTAL-W-BADACC, Unable to CREATE/MODIFY account PCCOMMON.

System Manager:
Upon completion of this installation, you must edit
the network start-up file to allow the VAX/VMS Server for
MS-DOS to be invoked during system booting.
Please refer to the VAX/VMS Server Guide for
further information.
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target
directories ...
%RUN-S-PROC_ID, identification of created process is xxxxxxxx

,/- ,

(

',,---j

11. If you answered "yes" to step 7 (that is, to run the IVP),
VMSINSTAL displays:
Beginning the VAX PCFS Installation Verification Procedure.

The IVP tests the VAXNMS server functions. If the tests are successful, the IVP displays:
%UAF-I-ADDMSG, user record successfully added
%DCL-W-NEGATED, entity explicitly negated in command string
Testing ...... Buffer size: 4398. Server type: VAX.
Negotiate protocol & tree connect ... OK
Directory ......... OK
File open ........... OK
Read/write .............. OK
Seek ...... OK

1- 8

C~,)

Installing the VAXNMS Server
Lock ................. OK
Process exit ......... OK
Set/get attributes .............. OK
File search ....... OK
Compatibility mode .................. OK
Deny mode ..................... OK
Rename and delete ................ OK

(

When the IVP finishes successfully, it displays:
Cleaning up .. PCFSTEST successfully finished.
%UAF-I-REMMSG, record removed from SYSUAF.DAT
Installation of PCFS Vl.l completed at xx:xx

If the IVP unsuccessful, it displays some messages, followed by:
%VMSINSTAL-F-UNEXPECTED, Installation terminated due to unexpected
event

If VMSINSTAL displays this message, refer to the Guide to
VAXNMS Software Installation. If you have an old version of the
VAXNMS server and you chose to leave the old version files, you

may be able to return to the old version by deleting the most
recent version of the server files. These files are:
•
•
•
•
•
•
•
•

SYS$SYSTEM:PCFS SERVEREXE
SYS$SYSTEM:PCFS-OPERATOREXE
SYS$SHARE:SETUIC.EXE
SYS$HELP:PCFS011.RELEASE NOTES
SYS$HELP:PCFS OPERATORHLB
SYS$MANAGER:PCFS STARTUP.COM
SYS$MANAGER:PCFS-ADMIN.COM
SYS$TEST:PCFSTEST:-EXE

12. VMSINSTAL displays:
VMSINSTAL procedure done at xx:xx

13. If you are using the console device and have removed the console
volume, remount it when VMSINSTAL prompts you.

1- 9

Installing the VAXIVMS Server
Figure 1-1 shows the directory structure created by VMSINSTAL.

[VXAPP]--(PCCOKKON]--(PCAPP]--[PCPS_SPOOL]--(VXUSERS]
Figure 1-1 Directory Structure Created by VMS INSTAL
Table 1-1 describes the accounts created by VMSINSTAL.
Table 1-1

Accounts Created by VMSINSTAL

Account·
Name

Description

PCAPP

This account is the read-only alias for the unrestricted applications directory. Therefore, when users specify the PCAPP
alias, they cannot delete or destroy files.

PCWAPP

This account is the writeable alias for the unrestricted applications directory. This is the alias you, the system administrator, use to maintain the applications that come with the
VAXmate system software.

PCCOMMON This account is the read, write. and create alias for the
common directory. This alias allows multiple users to store
files that are accessible to all.

Adding VAX/VMS Server Information to
the Network Start-Up File
To start the VAXNMS server automatically each time you restart the network, edit your network start-up file, SYS$MANAGER:STARTNET.COM.
After the line:
$ OSYS$MANAGER:RTTLOAD

1- 10

Installing the VAXNMS Server

add:
$ IF F$SEARCH("SYS$SYSTEM:PCFS_SERVER.EXE") .NES. '"' THEN aSYS$MANAGER:PCFS_STARTUP

NOTE
If you do not want to start the VAXNMS server automati-

cally each time you start the network, see Chapter 2.

Adding VAX/VMS Server Information to
the System Administrator's Log-In File
To define the command symbol for the operator interface, add the following line to the system administrator's log-in file,
SYS$MANAGER:LOGIN.COM.
$ PCSERVER :== $PCFS_OPERATOR

(

The VAXNMS server recognizes the command symbol after the system
administrator's log-in file is run again.

Preparing the V AX/VMS Server for
Workstation Software
To prepare the VAXNMS server for the workstation software, you must:
•

Create accounts and directories on the server. The accounts provide access to the workstation software. The directories are to contain the workstation software.

•

To create the accounts and directories and register the first node, use the
PCFS Administration utility.

NOTE
To use the PCFS Administration utility, you must have the
. SYSPRV privilege and write access to the Master File
Directory (MFDI.

1- 11

Installing the VAXNMS Server

Creating Workstation System Accounts and
Directories
To create the workstation software accounts and directories:
1.

From a terminal connected to the VAX computer, invoke the
PCFS Administration utility by typing:
$ ~SYS$MANAGER:PCFS_ADMIN<Return>

The PCFS Administration utility displays the Management Options
menu, Screen 1-1.

PCFS Administration Utilit~ V1.1
1 - CREITE Client systeR Directory/Account
2 - aDD a Perlonal Directory/Account
3 - IDD a Hode Registration Entry
4 - IDD a CORRon Directory/Account
5 - IDD an APplication Directory/Account
6 - aDD a Printer Queue Directory/Account
7 - DELETE a Personal Directory/Account
8 - DELETE a Hode Registration Entry
, - DELETE a COmRon Directory/Account
10 - DELETE an Application Directory/Account
11 - DELETE a Printer Queue Directory/Account
CTIL/Z - Exit frOR this Utility
Your selection? •

Screen 1-1 Management Options Menu
2.

Select option 1, CREATE Client system Directory/Account
Structure, from the Management Options menu.
This option creates directories and two accounts for the workstation software. Some defaults are set automatically and some you
can specify when prompted.

1- 12

()

Installing the VAXNMS Server
After selecting option 1, the PCFS Administration utility displays
the Client Selection Menu, which has three options:
•

Select option 1 to create a VAXmate system directory.

•

Select option 2 to create an industry-standard system directory.

•

Select option 3 for the type hardware supported by this system
directory.

Select one of these options and press the Return key.
3.

(

After you press the Return key, the PCFS Administration utility
prompts you for the following information:
•

The file version limit for the files in the system directories.
The default limit is the version limit used for the PCFS system
files. You specified this file version limit when you installed the
server. To accept the default, press the Return key.

•

The password for the system directory's writeable account. This
account is the writeable alias for the directory that contains the
unrestricted applications. The default password is MAINTAIN.
To accept the default, press the Return key.

Next, the PCFS Administration utility displays some VAXIVMS
utility messages while it creates the system directory and read-only
and writeable accounts. The read-only account name and directory
name are the two letter codes you specified for the system, with
"SYS" appended to them. For example, if you specified VAXmate,
the PCFS Administration utility creates the accounts:
VXSYS

The read-only alias for the system directory. which contains the MS-DOS operating system, the VAXmate
network software, and MS-Windows. Therefore, when
users specify the VXSYS alias, they cannot delete or
destroy files.

VXWSYS

The writeable alias for the system directory, which contains the MS-DOS operating system, the VAXmate
network software, and MS-Windows. Use this alias to
connect to the directory when you need to write to the
directory. To protect the files in the [VXSYS] directory. only authorized system administrators should
know this alias and password

If you specified IBM, the PCFS Administration utility creates the

accounts:

1- 13

Installing the VAXNMS Server
ISSYS

The read-only alias for the system directory, which contains the MS-DOS operating system, the network software, and MS-Windows. Therefore, when users specify
the ISSYS alias, they cannot delete or destroy files.

ISWSYS

The writeable alias for the system directory, which contains the MS-DOS operating system, the network software, and MS-Windows. Use this alias to connect to
the directory when you need to write to the directory.
To protect the files in the [ISSYS] directory, only
authorized system administrators should know this
alias and password.

Before you allow users to connect to the read-only alias for a system directory, you must set that system directory to read only.
To set the system directory to read-only:
1.

Edit the file PCFS STARTUP.COM.

Advance to the lines that begin:
$ MCR PCFS_OPERATOR
SET ALIAS PCAPP /READ
$
SET ALIAS VXSYS /READ
$
SET ALIAS ISSYS /READ
$
SET ALIAS RBSYS /READ

1- 14

Remove the dollar sign ($) and exclamation point (!) from the appropriate command line. For example, if you added an industrystandard system account, remove the dollar sign and exclamation
point from the command line for ISSYS.

Installing the VAXNMS Server

(

Figure 1-2 shows the directory structure created by option 1 of the
Management Options Menu.

[VXSYS]

[.SYSTEM] [.COUNTRY]

I
I

[ .VIN]

[ • STD] (. trrIL]

[ .DECAPP]

[ .PIF]

[ .DRV]

Figure 1-2 Directory Structure Created by Option 1

Registering the First Node
To register the first node, you must know its DECnet node name and
address. You should write down this information now.
NOTE

(

If you are responsible for assigning DECnet node names

and addresses for your network, use the NCP SHOW
KNOWN NODE command to list the nodes defined on
your network. Then assign a DECnet node name and address that are not on the list of known nodes.
If you are not responsible for assigning DECnet node

names and addresses for your network, see the person in
your organization who is.
To register the first node:
1.

Select option 3, ADD a Node Registration Entry, from the
Management Options menu.
The PCFS Management utility prompts you for:

(

•

The DECnet node name of the workstation you want to
register

•

The DECnet node address of the workstation you want to
register

1- 15

Installing the VAXIVMS Server
2. Type the DECnet node name and node address of the first
workstation to connect to the VAXNMS server.
This option registers the DECnet node name and address with the
server's permanent database and volatile database. The permanent
database, stored on disk, defines the network to the local node,
which is the VAXNMS server. The volatile database, stored in
memory, contains the current network configuration parameters, including node names that are defined for DECnet.
3. To return to the main menu, press the Return key. To exit from
the PCFS Administration utility, press the Ctrl/Z keys.
To install VAXmate workstation software or IBM workstation software,
see the Personal Workstation Configuration Guide.

Adding the First User
Adding users to the server is a common task that you may perform many
times. It is recommended that the first user you add to the network is
yourself. The following procedure tells you how to add yourself to the
server.
1.

Determine your personal directory name.
A personal directory is a directory exclusively reserved for one user
and is the key diskette's default directory. A WIN.INI file is stored
in each personal directory so each user can run a tailored version
of MS-Windows. When a user creates a file, it is stored in the personal directory by default.
The VAXNMS server requires that each user has at least one of
the three types of personal directories:
• A personal directory set up specifically for use with the
VAXNMS server. You can create this kind of personal directory with the PCFS Administration utility. A user cannot
"login" to this directory using a terminal emulator.
• A personal directory on a workstation hard disk. To use this
personal directory, you must have installed and formatted the
hard disk.
•

1- 16

A personal directory that is a current VAXNMS user directory.
This directory is normally used with the VAXNMSoperating
system. A user can "login" to this directory using a terminal
emulator.

Installing the VAXNMS Server

(

You should note your personal directory name now.
2.

If the first workstation does not have a hard disk or you do not

already have a directory and account on the VAX computer, create
a personal directory on the VAX as follows:
a.

From a terminal connected to the VAX computer, invoke the
PCFS Administration utility by typing:
$ ~SYS$MANAGER:PCFS_ADMIN<Return>

Select option 2, ADD a Personal Directory/Account, from the
Management Options menu.

Type the VAXIVMS account name for your personal directory
and press the Return key. For example, if your name is John
Smith, you can type:
SMITH<Return>

(

Type the password you want to assign to your account and
press the Return key. If you omit the password, the account is
assigned the default password WELCOME.

Type the file version limit for your personal directory and press
the Return key. If you omit the file version limit, the PCFS
Administration utility assigns the default file version limit for
personal and common directories. The default file version limit
is 1, unless you changed the default when you created the
VAXIVMS server directory structure.

The PCFS Administration utility displays some VAX/VMS utility
messages while it creates your directory and updates the User
Access File (UAF) to include your account.
The PCFS Administration utility creates your directory in the
(VXUSER) directory and assigns the same name as the account
name. For example, if you specified your account name as SMITH,
the PCFS Administration utility creates the directory
(VXUSER.SMITH).
To exit from the PCFS Administration utility, press the Return
key to return to the main menu, then press the Ctrl/Z keys.

1- 17

Installing the VAXIVMS Server

NOTE
Normally, when you add users, you must register the
DECnet node name for the' user's workstation with the
VAXIVMS server. You registered the node name for the
first workstation when you created the initial directory
structure.
To install client software, see the Personal Workstation Configuration
Guide.

1- 18

Chapter 2
VAX/VMS Server Operations
This chapter describes tasks that help you maintain your VAXNMS
server and your network. You may perform some of these tasks daily and
some not at all, depending on your network configuration and the needs of
your users. The tasks are:

(

•
•
•
•

Starting the VAXNMS server
Stopping the VAXNMS server
Adding a user
Removing a user

•

Installing an application

•
•
•
•
•
•
•
•

Removing an application
Adding a printer
Removing a printer
Creating a common directory
Removing a common directory
Modifying the Information System
Backing up the server
Maintaining the server log file
NOTE
Before you perform any of these tasks, make sure that you
created a VAXNMS server directory structure as described
in Chapter 1.

2- 1

VAXNMS Server Operations

Starting the VAX/VMS Server
The VMSINSTAL procedure in Chapter 1 starts the VAXNMS server.
The VAXNMS server continues to run as long as the VAX computer
runs.
If you specified the PCFS_STARTUP.COM file in the network start-up
file, the VAXNMS server automatically starts each time you restart the
network.
If you did not specify the PCFS STARTUP.COM file in the network
start-up file or if you stop the VAxNMS server process, start the server
with the PCFS_STARTUP.COM procedure. This procedure:

•

Starts the VAXNMS server, which runs as a privileged process on
the VAX computer. (If the VAXNMS server is already running
when the PCFS STARTUP. COM procedure is run, this procedure
stops the server-process and starts another server process. This
procedure also disconnects all current connections.)
Defines any commands that you want to execute each time you
start the VAXNMS server. You place these commands in the
PCFS STARTUP.COM file.

To run this procedure, log into a privileged account and type:
$ GSYS$MANAGER:PCFS_STARTUP

When the VAXNMS server starts, the following message is displayed:
%RUN-S-PROC_ID. identification of created process is xxxxxxxx

For more information about the PCFS STARTUP.COM file, see Chapter
4.

StQPping the VAX/VMS Server
You can stop the VAXNMS server in one of three ways. You can stop:
•

2- 2

Users from connecting to the server
Use the PCSERVER REFUSE CONNECTIONS command, which
prevents users from connecting to the VAXNMS server. Users already connected to the server remain connected.
To use the REFUSE CONNECTIONS command, type:

/ "

l,,-~)

VAXNMS Server Operations
$ PCSERVER REFUSE CONNECTIONS

(

To allow users to reconnect to the server, use the PCSERVER
ACCEPT CONNECTIONS command:
$ PCFSSERVER ACCEPT CONNECTIONS

•

Existing connections to the server
Use the PCSERVER STOP SERVER command, which disconnects
all current users from the server and prevents other users from
connecting to the server.
To use the STOP SERVER command, type:
$ PCSERVER STOP SERVER

Any workstations connected to the server remain connected until
they choose to disconnect.
The server image continues to run, but no more workstations can
connect to the server.

(

To allow users to reconnect to the server, use the PCSERVER
START SERVER command. For more information about the
PCSERVER STOP SERVER command or the PCSERVER
START SERVER command, see Chapter 3.

•

The server process
Determine the server process identification number by using the
VAXNMS SHOW SYSTEM command. Look for the identification
number for the process PCFS _SERVER.
To stop the server process, type:
$ STOP /ID=number
If you stop the server process, all existing connections to the

server are disconnected, and the server image is terminated. To
restart the server process, use the PCFS_STARTUP.COM file and
type:
$ CSYS$MANAGER:PCFS_STARTUP.COM

2- 3

VAX/VMS Server Operations

Adding a User
You can add users to the VAXNMS server at any time. Usually you add
users when you first set up the VAXNMS server and when new users
come into your organization.
NOTE
If the VAXNMS server no longer recognizes a node you

already defined, delete the node using the PCFS
Administration utility and specify option 8. Redefine the
node use the PCFS Administration utility and specify
option 3.
To add a user to the VAXNMS server:
1.

Make sure the user has a personal directory on either the workstation or on the VAXNMS server. If the user's workstation does not
have a hard disk that contains a personal directory or if the user
does not have an existing VAXNMS account and directory, create
a personal directory and account for the user.
To create a personal directory and account on the VAXNMS
server:
a.

Invoke the PCFS Administration utility by typing:
$ ~SYS$MANAGER:PCFS_ADMIN

Select option 2, ADD a Personal Directory/Account, from the
Management Options menu.

Type the user's account name.

d. Type the user's account password. If you do not type a
password, the default password "WELCOME" is assigned. If
the default password is chosen, remind the user to change it to
a unique password.
e.

2- 4

Type the file version limit for the user's directory. If you do
not specify a file version limit, the PCFS Administration utility
assigns the default file version limit for personal and common

VAXNMS Server Operations
directories. The default limit is 1, unless you changed the
default when you created the VAXNMS server directory
structure.
f.

If disk quotas are enabled on the disk where the personal accounts are created, type the disk quota limit for the account.
The default disk quota is 10,000 blocks, which is approximately
5 megabytes of storage space.

The PCFS Administration utility displays some VAXNMS utility
messages while it creates the user's directory and updates the UAF
to include the user's account. The PCFS Administration utility
creates the user's subdirectory in the VXUSER directory and
assigns the same name as the account name. The PCFS
Administration utility also assigns the UIC with the default group
number and a unique member number within the group.
2.

(

Add the DECnet node name and DECnet node address for the
user's workstation to the DECnet database using the PCFS
Administration utility:
a.

Select option 3, ADD a Node Registration Entry, from the
Management Options menu.

Type the user's DECnet node name. Make sure you type a
unique DECnet node name.

Type the user's DECnet node address. Make sure you type a
unique DECnet node address.

The PCFS Administration utility enters the information into the
permanent database and the volatile database. To return to the
main menu, press the Return key. To exit from the PCFS
Administration utility from the main menu, press the Ctrl/Z keys.
3.

Create a key diskette for the user. For more information about
creating a key diskette, see the Personal Workstation
Configuration Guide.

2- 5

VAXNMS Server Operations

Removing a User
To remove a user from the network and the VAXNMS server:
1.

If the user has a personal directory, which was created by the

PCFS Administration utility, on the VAXNMS server, use the
VMS BACKUP utility to back up the files in the user's personal
directory to some removable media.
2.

Use the PCFS Administration utility to delete the files, the directory, and the UAF entry for the account:
a.

Type:
$ ~SYS$MANAGER:PCFS_ADMIN

Select option 7, DELETE a Personal Directory/Account, from
the Management Options menu.

Type the name of the user's account that you want to delete.

The PCFS Administration utility displays some VAXNMS utility
messages while it deletes the directory, the files, and the UAF
entry for the user's account.

)

Delete the user's DECnet node registration entry from the network
database, using the PCFS Administration utility:
a.

Select option 8, DELETE a Node Registration Entry, from the
Management Options menu.

Type either the DECnet node name or the DECnet node address when prompted for the node identifier.

The PCFS Administration utility displays some VAXNMS utility
messages while it deletes the node from the network database. To
return to the main menu, press the Return key. To exit from the
main menu, press the Ctrl/Z keys.

Installing an Application
An MS-DOS application directory stores applications for remote access.

You can set applications to be unrestricted or restricted.

2- 6

VAXNMS Server Operations

(

Unrestricted Applications
Unrestricted applications have no restrictions on the number of users that
can connect to that application's directory at one time.
You install unrestricted applications in the PCAPP directory, which is
created as part of the VAXNMS server directory structure. Some unrestricted applications are automatically installed in this directory as part
of the VAXmate system software installation.
The PCAPP directory has two aliases or accounts: one (PCAPP) with readonly access for the application users and one (PCWAPP) with read and
write access for the system administrator. Both accounts were created
when you installed the VAXNMS server.
NOTE
The VAXmate system software also includes unrestricted
applications that are hardware dependent. These are installed in the [VXSYS.DECAPP] directory. You should not
need to add other applications to this directory.
To install an unrestricted application on the VAXNMS server:
From your workstation, insert the system administrator's key
diskette into drive A and turn on (or reset) the workstation.
2. Expand the MS-DOS Executive icon. You may have to exit from
MS-Windows to install some applications.
3. Connect to the PCAPP directory.
4. Create a subdirectory for the application.
5. Install the application into the subdirectory in the PCAPP directory
according to the instructions provided with the manufacturer's
documentation. PCAPP is drive K on your key diskette.
6. If the application requires a Program Information File (PIF), copy
or create the PIF in the application directory. A PIF is required if
the application is to be used with MS-Windows and was not designed for MS-Windows. For more information on PIFs, see the
VAXmate Operating Environment Release Notes and the VAXmate
User's Guide.
1.

To offer the application to users, add the application to the Configuration
Aide application database and specify the application on the user's key
diskette. For more information about adding an application with the
Configuration Aide, see the Personal Workstation Configuration Guide.

2- 7

VAXNMS Server Operations

Restricted Applications
Restricted applications have a password, a limit to the number of users
that can connect to the application at one time, or both.
You install restricted applications in subdirectories of the VXAPP directory, which was created as part of the VAXNMS server directory
structure.
A restricted application must have two aliases or accounts: one for readonly access for the application users and one for read and write access for
the system administrator. Both of these accounts are created with the
PCFS Administration utility.
You can limit the number of users that connect to a directory with the
PCSERVER LIMIT CONNECTIONS /ALIAS command. Be sure to
specify this command in the PCFS STARTUP. COM or each time you
restart the VAX computer. For more information about the LIMIT commands, see Chapter 3.
NOTE
Various DIGITAL and industry-standard applications can
be installed on the VAXNMS server. Check the application's license agreement to be sure you have the correct license and permission to install and operate the application
on the server.
You are responsible for ensuring that correct licenses are
obtained prior to installing and operating a restricted
application.
To install a restricted application on the VAXNMS server:
1.

Invoke the PCFS Administration utility by typing:
$ OSYS$MANAGER:PCFS_ADMIN

Select option 5, ADD an Application Directory/Account, from the
Management Options menu.

3. Type the name of the application.
4. Type the password for the application's writeable account. If you do
not specify a password, the PCFS Administration utility assigns
the default password MAINTAIN.

2- 8

(\
I"'-_./
. /

VAXfVMS Server Operations

(

Type the password for the application's read-only account. If you
do not specify a password, the PCFS Administration utility assigns
no password to this account.
The PCFS Administration utility displays some VAXNMS utility
messages while it creates the application directory and read-only
and writeable accounts.
The read-only account name and the directory name are the name
you specified for the application. The writeable account name is the
application name with a W appended to the end. For example, if
you type the application name RBASE, the PCFS Administration
utility creates a read-only account RBASE, a writeable account
RBASEW, and a directory [VXAPP.RBASE).
To return to the main menu, press the Return key. To exit from
the PCFS Administration utility from the main menu, press the
CtrllZ keys.

Issue the following operator interface command:
$ PCSERVER SET ALIAS name /READ

(

Where:
name

Is the name of the application directory you created.

Add this line to the server start-up file, so that it takes effect each
time the server is started.
7.

From your workstation, insert the system administrator's key
diskette into drive A and turn on (or reset) the workstation.

Expand the MS-DOS Executive icon. You may have to exit from
MS-Windows to install some applications.

Connect drive L: to the VAXNMS server with the NET USE command and specify the application's writeable alias. If drive L: is already in use, specify an unused drive. For example, to install the
application RBASE on the VAXNMS server with node name
BOSTON, type:
A>NET USE L: \\BOSTON\RBASEW password

2- 9

VAXIVMS Server Operations

10. Install the application into the subdirectory in the VXAPP directory according to instructions provided with the manufacturer's
documentation. VXAPP is drive L on your key diskette, or the
drive you specified in step 9.
11. If the application requires a Program Information File (PIF), copy
or create the PIF in the application directory. A PIF is required if
the application is to be used with MS-Windows and was not designed for MS-Windows. For more information on PIFs, see the
VAXmate Operating Environment Release Notes and the VAXmate
User's Guide.
To offer the application to users, add the application to the Configuration
Aide application database and specify the application on the user's key
diskette. For more information about adding an application with the
Configuration Aide, see the Personal Workstation Configuration Guide.

Removing an Application
You can remove access to unrestricted and restricted applications.

Unrestricted Applications
To remove an unrestricted application from the VAXNMS server:
1.

Back up the application's files in the application's directory to
some removable media.

Delete the application's files from the application's directory.

Delete the application's directory from the PCAPP directory.

Remove the application from the Configuration Aide application database
and update any key diskette that accessed the application. For more information, see the Personal Workstation Configuration Guide.

Restricted Applications
To remove an unrestricted application from the VAXNMS server:
1.

Back up the application's files in the application's directory to
some removable media.

Use the PCFS Administration utility to delete the directory, the
files, and the UAF entry for the account.

2- 10

VAXNMS Server Operations
a.

Type:
$ ~SYS$MANAGER:PCFS_ADMIN

Select option 10, DELETE an Application Directory/Account,
from the Management Options menu.

Type the name of the application the you want to delete.

The PCFS Administration utility displays some VAXNMS utility
messages while it deletes the files, the directory, and the UAF entry for
the application account.
To return to the main menu, press the Return key. To exit from the main
menu, press the Ctrl/Z keys.
Remove the appropriate SET ALIAS command line from the server startup file.

(

Adding a Printer
The VAXNMS server allows users access to printers connected to the
VAX computer and to print files using various forms. The VAXNMS
server provides default forms and device control libraries for some of the
printers that it supports. You use the PCFS Administration utility to set
up the printer queues and create the necessary account and directories.
The PCFS Administration utility supports four printers and provides a
device control library for each printer and eight default forms.
Table 2-1 lists the default forms and device control library for each printer
that the PCFS Administration utility supports. The .TLB files are stored
in SYS$LIBRARY.

('
2- 11

VAXIVMS Server Operations
Table 2-1

VAXIVMS Server Printers and Forms

Printer

Default Forms

Device Control Library

DEC LN03

DEC Portrait Mode
DEC Landscape Mode

PCFS LN03 DEVCTL.TLB

DEC LN03
PLUS

DEC Portrait Mode
PCFS LN03PLUS DEVCTL.TLB
DEC Landscape Mode
Industry-standard Portrait Mode
Industry-standard Landscape
Mode

DEC LA50

DEC 80 column Mode
DEC 132 column Mode

PCFS LA50 DEVCTL.TLB

DEC LA75
Companion

DEC 80 column Mode
DEC 132 column Mode
Industry-standard 80 column
Mode
Industry-standard 132 column
Mode

PCFS LA75 DEVCTL.TLB

The default printer queue that is created when you install a printer is
named according to the printer type:
•

For a DEC LN03, the printer queue name is PCFS$LN03.

•

For a DEC LN03 PLUS, the printer queue name is PCFS$LN03P.

•

For a DEC LA50, the printer queue name is PCFS$LA50.

•

For a DEC LA75 Companion, the printer queue name is
PCFS$LA75.

You can also use the VAXNMS server with an existing generic printer
queue, which is described later in this chapter.
Before you add a printer, make sure the printer is physically connected to
the VAX computer. For more information on connecting the printer, see
the printer documentation.
To add a printer to the VAXNMS server:

2- 12

VAXNMS Server Operations
1.

Invoke the PCFS Administration utility by typing:
$ GSYS$MANAGER:PCFS_ADMIN

Select option 6, ADD a Printer Queue Directory/Account, from the
Management Options menu.

Select the number corresponding to the printer you want to add.

If you select the LN03, LN03PLUS, LA75, or LA50 printers:

Type the physical device name for the printer port.

NOTE
To change the printer port, select option 11, DELETE a
Printer Queue Directory/Account, from the Management
Options menu to delete the printer, then select option 6
again to enter the correct printer port.
The PCFS Administration utility prompts you for the physical
device again. If you only have one printer of the specified type (for
example, one LN03 PLUS), press the Return key to continue.

(

If you have more than one printer of the specified type, specify the
physical device name for each of the other printers. Press the
Return key to continue.

For example, if you have two LN03 printers, specify the physical
device TXAO: for one printer and the physical device TXBO: for the
other printer.
b.

Type the password for the printer account. To specify no
password, press the Return key.
•

The PCFS Administration utility displays some VAXNMS
utility messages while it creates:
A generic printer queue for the printer type. The generic queue name is the string "PCFS$" with the
printer type appended to the end.
A physical printer queue for each printer of the specified type. The physical queue name is the physical
device name that you specified.
A subdirectory in the PCFS SPOOL directory for the
printer type. The directory name is the name of the
printer type.

2- 13

VAXIVMS Server Operations
A subdirectory in the [PCFS SPOOL.printer] directory
for each form that the printer supports. Each directory
name is the name of the form.
An account for each form that the printer supports.
Each account name is specified by the printer type, an
underscore, and the form name.
For example, if you add an LA75 Companion printer that has
the physical device name TTAO:, the PCFS Administration utility creates:
•

A generic queue called PCFS$LA75

•

A physical queue called TTAO:

•

A directory called [PCFS_SPOOL.LA75]

•

Four subdirectories:
[PCFS SPOOL.LA75.STD 80]
[PCFS-SPOOL.LA75.STD-132]
[PCFS-SPOOL.LA 75.DEC-80]
[PCFS=SPOOL.LA75.DEC=132]

•

Four accounts:
LA75 S80
LA75-S132
LA75-D80
LA75-D132

The UIC assigned to all printer queue directories and accounts
has the default group number and the member number 77. The
default group number is 360 unless you changed it when you
created the VAXNMS server directory structure.
The PCFS Administration utility reminds you to add a line to
the SYSTARTUP.COM file:
$ aSYS$MANAGER:PCFS_PRINT.COM

When you restart the VAX computer with the
SYSTARTUP.COM file. it runs the PCFS PRINT.COM file,
which defines forms and initializes the printer queues. The
PCFS PRINT.COM file is created by the PCFS Administration
utility-when you add the first printer.

r"\

2- 14

VAXNMS Server Operations

(

If you select the existing generic queue:

•
•

Type the existing printer queue name.
Type the password for the printer queue. To specify no
password, press the Return key.
The PCFS Administration utility creates a directory and an account with the name of the printer queue. The directory is created
in the PCFS _SPOOL directory.
NOTE
If a user is connected to the VAXNMS server and issues
the NET PRINT \\nodename command, it returns information about the generic queue SYS$PRINT. If the
SYS$PRINT queue is not enabled, you can enable it in
your site-specific start-up file. For more information about
your site-specific start-up file, see the Guide to VAXIVMS
System Management and Daily Operations.
To return to the main menu, press the Return key. To exit from the
PCFS Administration utility, press the CtrllZ keys.
To offer the printer to users, you must specify the printer on the user's
key diskette. For more information about adding a printer to a key
diskette, see the Personal Workstation Configuration Guide.

Removing a Printer
To remove a printer from the VAXNMS server, use the PCFS
Administration utility to delete the printer queue, the directory, and the
UAF entry for the account. To remove a printer:
1.

Type:
$ GSYS$MANAGER:PCFS_ADMIN

Select option 11, DELETE a Printer Queue Directory/Account,
from the Management Options menu.

Select the number corresponding to the printer that you want to
delete.

The PCFS Administration utility displays some VAXNMS utility
messages while it deletes the printer queue, the directory, and the UAF
entry for the printer queue account.

2- 15

VAXNMS Server Operations

(\
To return to the main menu, press the Return key. To exit from the main
menu, press the CtrllZ keys.

Creating a Common Directory
A common directory contains files to which users have write access. Each
common directory is a subdirectory of the PCCOMMON directory, which
was created as part of the VAXNMS server directory structure.
To create a common directory on the VAXNMS server:
1.

Invoke the PCFS Administration utility by typing:
$ GSYS$MANAGER:PCFS_ADMIN

Select option 4, ADD a Common Directory/Account, from the
Management Options menu.

3. Type the name for the common account.
4. Type the password for the account. To specify no password, press
the Return key.
5. Type the file version limit for the common directory. If you do not
specify a file version limit, the PCFS Administration utility assigns
the default file version limit for personal and common directories.
The default file version limit is 1, unless you changed the default
when you created the VAX/VMS server directory structure.
6. If disk quotas are enabled on the disk where the common account
is created, type the disk quota limit for the account. The default
disk quota is 10,000 blocks, which is approximately 5 megabytes of
storage space.
The PCFS Administration utility displays some VAXNMS utility
messages while it creates the common directory and account. The common
directory has the same name as the account. The UIC assigned to all
common directories has the default group number and a unique member
number. The default group number is 360, unless you changed it when you
created the VAXNMS server directory structure.
To return to the main menu, press the Return key. To exit from the
PCFS Administration utility from the main menu, press the Ctrl/Z keys.

2-16

\_J

VAXfVMS Server Operations

(

To offer a common directory to users, you must specify the common directory on the user's key diskette. For more information about adding a
common directory to a user's key diskette, see the Personal Workstation
Configuration Guide.

Removing a Common Directory
To remove a common directory and account from the VAXNMS server:
1.

Back up the files in the common directory to some removable
media.

Use the PCFS Administration utility to delete the directory, the
files, and the UAF entry for the account.
a.

Type:
$ CSYS$MANAGER:PCFS_ADMIN

Select option 9, DELETE a Common Directory/Account, from
the Management Options menu.

Type the account name for the common directory that you
want to delete.

The PCFS Administration utility displays some VAXNMS utility
messages while it deletes the directory, the files, and the UAF entry for
the account.
To return to the main menu, press the Return key. To exit from the main
menu, press the Ctrl/Z keys.

Modifying the Information System
You can add new information or notes to the Information System for
users. This information can include:
•

A list of the network resources that are available to users

•

Your name, location, and phone extension so that users may contact you when they have a problem

•

Where to pick up listings printed on network printers

To add information:

2- 17

VAXIVMS Server Operations
1.

From your workstation, insert the system administrator's key
diskette into drive A and turn on (or reset) the workstation.

The workstation should display the Information System.
2.

Expand the MS-DOS Executive icon.

3. Create a text file called INFOUSER.TMP that contains the information you want displayed when a user selects the "Notes From
Your System Administrator" topic. If you use the Notepad editor,
you see the information as it is displayed.
4.

Use the MS-DOS ATTRIB command to remove the read-only at·
tribute from the H:\DECAPP\lNFOUSER.IOO file.

Copy the INFOUSER.TMP file to the file name
H:\DECAPP\lNFOUSER.IOO.

Use the MS·DOS ATTRIB command to mark the
H:\DECAPP\lNFOUSER.IOO file read-only.
7. From the Information System main menu, select the "Notes From
Your System Administrator" topic. You should see the information
you created.

You can update this file at any time. However, be sure that no users are
accessing this Information System topic. If you receive an error message
when copying the file, a user may be reading the topic.

Backing Up the VAX/VMS Server
You should back up the VAXNMS server:
•

As part of your regular back-up process

•

On other occasions, depending on the specific component of the
server:
The VAXNMS server software, the VAXmate system software,
and MS·DOS applications
These should be backed up if you install a new version of the
VAXNMS server software, the VAXmate system software, or a
new version of an application.
.
The VAXmate common directories and personal directories
Because users can change the files in these directories, the files
should be backed up on a daily basis.

(~\
"-~/

2- 18

VAXIVMS Server Operations
NOTE
If you use the VAXIVMS server to modify a file, do not

back up the file using the BACKUP command with the
IMODIFIED qualifier.

Table 2-2 lists the specific directories you should back up for the
VAXIVMS server.
Table 2-2

(

VAXIVMS Server Directories to Back Up

VAXNMS Server Component

Disk or Directory to Back Up

VAXNMS server software

System disk

VAXmate system software

[VXSYS], [PCAPP], [PCFS SPOOL]
directories
-

MS-DOS applications

[VXAPP] directory

Common and user directories

[PCCOMMON] and [VXUSER]
directories

VAXmate system software is divided into two components:
System independent software, which is stored in [PCAPP] and in
[PCFS _SPOOL].
2. System dependent software, which is stored in one or more of the
following directories (depending on the workstations being used}:
1.

•

[VXSYS]

•

[ISSYS]

For more information about the VAXNMS Backup utility, see the
VAXIVMS Backup Utility Reference ManuaL

Maintaining the Server Log File
The VAXIVMS server records logged events in the file
SYS$SPECIFIC:[PCFS]PCFS_ SERVER.LOG.
The log file is a standard text file that contains one or more messages.
The messages describe network events that occur during operation of the
VAXNMS server.

2- 19

VAXIVMS Server Operations

NOTE
It is not uncommon for a log file to contain a number of
"link aborted" messages. You do not have to respond to
these messages unless users are complaining about losing
links to the serer.

The VAXIVMS server updates the log file once every 60 seconds. After an
event occurs, the event is logged within the next minute.
To display the name of the current log file in the SYS$SPECIFIC:[PCFS]
directory, use the PCSERVER SHOW LOG FILE command.
To display the messages that are in the log file, use the VAXlVMS TYPE
command.
You cannot use the VAXIVMS COPY command to copy the log file while
the server has it open. Therefore, to copy the log file, close it using the
PCSERVER SET LOG FILE. You can omit the file name in the SET
LOG FILE command, in which case the default, PCFS SERVER.LOG, is
used. If the server was using the specified file name, a new file is created.
To close the current log file and create a new one, use the PCSERVER
SET LOG FILE command. You might want to close the log file so you
can edit it to see the messages it contains. For an explanation of the
messages in the log file, see Chapter 5.

NOTE
The VAXIVMS server automatically creates a new log file,
named SYS$SPECIFIC:[PCFS]PCFS SERVER.LOG, each
time you start the server.
The PCSERVER SET LOG FILE command:
•

Closes the current log file.

•

Creates a new version of the file name specified on the command
line.

•

Begins using the specified file as a log file.

You can control which events the VAXIVMS server logs with the
PCSERVER LOG command. For more information about the PCSERVER
LOG command or the PCSERVER SET LOG command, see Chapter 3.

2- 20

(' "'.

~--j

(

Chapter 3
VAX/VMS Server Commands
This chapter tells you how to manage the VAXNMS server with the
server operator interface. The operator interface processes commands that
allow you to control and monitor the daily use of the VAXNMS server.

The VAX/VMS Server Operator Interface
Before you use the VAXNMS server operator interface:

(

•

You must have OPER and SYSPRV privileges.

•

The VAXNMS server must be installed and executing.

•

You must define the "PCSERVER" symbol for the operator interface in the system administrator's log-in file and run the log-in file
again. If you have not already done this, see Chapter 1.

To use the operator interface, type:
$ PCSERVER
If the operator interface displays any error messages, see Chapter 5 for an

explanation of the message.
You can enter commands when the VAXNMS server displays the prompt:
PCFS>

Table 3-1 lists the tasks you can perform with the operator interface. The
tasks are listed alphabetically according to the command you use.

3- 1

VAXNMS Server Commands
/~~

Table 3-1 VAXNMS Server Operator Interface Commands
If you want to ...

Use the command ...

Allow registered workstations to connect to the
VAXNMS server

ACCEPT CONNECTIONS 3-4

Allows any workstation to ACCEPT
connect to the VAXNMS UNREGISTERED
server

3-5

CLOSE CONNECTION

3-6

Close an open file

CLOSE FILE

3-8

Close a session

CLOSE SESSION

3-10

Exit to the VAXNMS op- EXIT
erating system

3-12

Get help

3-13

Change the limits imposed LIMIT CONNECTIONS
by the VAXNMS server
LIMIT FILES
LIMIT SESSIONS

3-16

Display network events
LOG
that the VAXNMS server
is logging

3-20

3-18
3-19

Refuse connection
requests to the server
from registered
workstations

REFUSE CONNECTIONS 3-23

Refuse connection
requests to the server
from unregistered
workstations

REFUSE
UNREGISTERED

3-24

Setting restrictions for an
offering

SET ALIAS

3-25

Open a file to log network SET LOG FILE
events

On page

Close a connection

HELP

3-26
(~"i

"'-_/
3- 2

VAXNMS Server Commands
Table 3-1 VAXNMS Server Operator Interface Commands (cont.)

(

If you want to ...

Use the command ...

On page

Display information about
the VAXNMS server

SHOW CONNECTIONS

3-28

SHOW FILES
SHOW LIMITS
SHOW LOG FILE
SHOW SESSIONS
SHOW STATUS
SHOW VERSION

3-29
3-30
3-31
3-32
3-33
3-34

Allow workstations to establish sessions with the
VAXNMS server

START SERVER

3-35

Disconnect all existing
connections to the
VAXNMS server

STOP SERVER

3-36

If you want to remove a workstation from the network database, or add a
workstation to the network database, use the PCFS Administration utility.

3- 3

ACCEPT CONNECTIONS

Allowing Connections to the VAX/VMS Server
To allow the VAXNMS server to accept connections from one or more
workstations, use the ACCEPT CONNECTIONS command.
After issuing the REFUSE CONNECTIONS command, use the ACCEPT
CONNECTIONS command to reaccept connection requests.
Form,at

ACCEPT CONNECTIONS
Example

To allow the VAXNMS server to accept connections, type:
PCFS>ACCEPT CONNECTIONS
PCFS>

3- 4

ACCEPT UNREGISTERED

(

Allowing Unregistered Nodes
To accept connections from a workstation that is not registered in the
volatile DECnet node name database, use the ACCEPT
UNREGISTERED command.
The volatile database, which is stored in memory, contains the node
names that are registered with DECnet and are recognized by the
VAXNMS server. By default, only registered DECriet nodes can connect
to the VAXNMS server. However, you can issue the ACCEPT
UNREGISTERED command to allow other nodes to connect to the
VAXNMS server.
NOTE
To register a node with the DECnet databases, use the
PCFS Administration utility. For more information, see
Chapter 2.

(

To allow unregistered nodes to connect to the VAXNMS server, you can
place the ACCEPT UNREGISTERED command in the file
PCFS STARTUP.COM. The next time you start the VAXNMS server,
unregistered nodes can connect to the server. Unregistered nodes can connect until you issue a REFUSE UNREGISTERED command or remove
the line from the PCFS STARTUP. COM file and restart the VAXNMS
server.
To determine if the VAXNMS server accepts connections from unregistered users, use the SHOW STATUS command.

Format
ACCEPT UNREGISTERED

Example
To allow the VAXNMS server to accept unregistered nodes, type:
PCFS>ACCEPT UNREGISTERED
PCFS>

3- 5

CLOSE CONNECTION

Closing a Connection
To disconnect a workstation connection to the VAXNMS server, use the
CLOSE CONNECTION command. You can close a connection if a user
leaves a workstation unattended while still connected to a restricted alias.
You can specify the connection by either its alias or its connection
identifier.
The VAXNMS server asks you to verify that you want to close the specified connection. If you verify your request, the VAXNMS server closes
the connection and any files opened from the connection.
Use the SHOW CONNECTIONS command to display a list of all connections maintained by the VAXNMS server, including the alias and the connection identifier for each.
Format
CLOSE CONNECTION alias I /ID=connection identifier

Where:
alias

Is the VAXNMS account name associated with
the connection. If you specify the alias, the
VAXNMS server disconnects all connections to
that alias for all sessions.

connection identifier

Is the number the VAXNMS server assigns to the
connection when it is established. The VAXNMS
server assigns a unique identifier to each connection, even if more than one workstation establishes connections to the same alias. If you specify
the identifier, the VAXNMS server disconnects
only that specific connection. To determine the
connection identifier, use the SHOW
CONNECTIONS command.

/\
~-)

(

Example 1

To disconnect connections specified by the alias JONES, type:
PCFS>CLOSE CONNECTION JONES
Do you want to close the connection JONES? [N]:y
PCFS>

3- 6

CLOSE CONNECTION
(.

Example 2

To disconnect the connection specified with the connection identifier 1,
type:
PCFS>CLOSE CONNECTION /ID=1
Do you want to close the connection 11 [N]:y
PCFS>

(

3- 7

CLOSE FILE

Closing a File
To close a file that a workstation opened, use the CLOSE FILE command. You can close a file if a user leaves the workstation unattended
with a file opened in such a way that no other workstations can open it.
You can specify the file by either the file identifier or the file name.
The VAXNMS server asks you to verify that you want to close the specified file. If you verify your request, the VAXNMS server closes the file.
Use the SHOW FILES command to display a list of all open files, including the file name and file identifier for each.
Form,at

CLOSE FILE filename I /ID~file identifier

Where:
filename

Is the name that the workstation specifies when the
VAXNMS server opens the file, in the form:
dev:[directory]filename.ext
If you specify the file name, the VAXNMS server

closes all instances of that open file for all connections.
file identifier

Is the number the VAXNMS server assigns when it
opens the file. The VAXNMS server assigns a unique
file identifier to each open file, even if that file is currently open by another workstation. If you specify the
file identifier, the VAXNMS server closes only that
specific file. To determine the file identifier, use the
SHOW FILES command.

Example 1

To close all instances of the open file WRK:[SMITH]REPORT.TXT, type:
PCFS>CLOSE FILE REPORT.TXT
Do you want to close the file WRK:[SMITH]REPORT.TXT? [N]:y
PCFS>

3- 8

CLOSE FILE

(

Example 2
To close the file with the file identifier 1, type:
PCFS>CLOSE FILE /10=1
Do you want to close the file 11 [N]:y
PCFS>

(

3- 9

CLOSE SESSION

Closing A Session
To close a session that the VAXNMS server established with a workstation, use the CLOSE SESSION command. You can use the CLOSE
SESSION command to terminate an open session before stopping the
VAXNMS server.
You can specify the session by either the workstation or the workstation
identifier.
The VAXNMS server asks you to verify that you want to close the specified session. If you verify your request, the VAXNMS server closes the
session and any files and connections established during the session.
Use the SHOW SESSIONS command to display a list of sessions currently established by the VAXNMS server.
Format
CLOSE SESSION workstation I /ID=workstation identifier

Where:
workstation

Is the DECnet node name for the workstation
that provides the user's link to the VAXNMS
server.

workstation identifier

Is the number assigned by the VAXNMS server
when it established the session. To determine the
workstation identifier, use the SHOW SESSIONS
command.

Example 1

To close a session for a workstation named GREEN, type:
PCFS>CLOSE SESSION GREEN
Do you want to close the session GREEN? [N]:y
PCFS>

3- 10

CLOSE SESSION

(

Exampie2
To close a session with the workstation identifier 1, type:
PCFS>CLOSE SESSION /10=1
Do you want to close the session 11 [N]:y
PCFS>

(

3- 11

EXIT

Returning to the VAX/VMS Operating System
To leave the operator interface and return to the VAXNMS operating
system, use the EXIT command. The VAXNMS server continues to run
in the state you left it when you exited.
Format
EXIT

Example
To exit from the operator interface, type:
PCFS>EXIT
$

3- 12

HELP

(

Getting Help
To display a list of VAXNMS server topics for which you can get help,
use the HELP command. If you specify a topic in the command line, you
receive help for that topic. If you specify a topic and a subtopic in the
command line, you receive information for that subtopic.
Format
HELP [topic [subtopic]]

Example

To display help for the EXIT command, type:
PCFS>HELP EXIT
EXIT

Exits the PCSERVER utility and returns to the VAX/VMS operating system. The
VAX/VMS server for MS-DOS will continue to run in the state it was left in at
the time the operator exited.
Format:
EXIT
Topic?

3- 13

LIMIT

Changing the VAXIVMS Server Limits
To change the default limits imposed by the VAXNMS server, use the
LIMIT commands.
You can change the default limits based on the performance of your VAX
computer. For example you can limit the number of connections to the
VAXNMS server. This prevents too many users from accessing the
VAXNMS server and degrading the performance of the computer. You
should base the limit on:
•

The number of workstations that use the VAXNMS server

•

The demands placed on the VAX computer by users (local users,
for example) other than workstation users

•

The disk throughput requirements of the local users

The VAXNMS server parameters that you can limit are:
•

The total number of connections to the VAXNMS server, with the
CONNECTIONS parameter

•

The number of connections to anyone alias, with the
CONNECTIONS/ALIAS=name parameter

•

The number of files the VAXNMS server can open, with the
FILES parameter

•

The number of workstations from which the VAXNMS server can
accept logical links, with the SESSIONS parameter
NOTE
You may not be able to set some server parameters to extremely high limits because of resource constraints in the
VAXNMS operating system.

If you change a limit, the new limit becomes effective immediately. If you

reduce a limit to less than the current limit and the VAXNMS server is
currently beyond the new limit, the workstations beyond the new limit are
not affected. For example, assume that the default limit for the total
number of connections is 10, and 9 workstations are connected to the
server. If you change the total number of connections to 5, the 9 workstations remain connected. However, the VAXNMS server allows no more
connections until at least 5 workstations disconnect.

3- 14

LIMIT

To display a list of the current limits imposed by the VAXNMS server,
use the SHOW LIMITS command.
To set the limits automatically each time you start the VAXNMS server,
add the commands to the PCFS STARTUP. COM file. For information
about the PCFS_STARTUP.COM file, see Chapter 4.
The next three commands tell you how to change the limits for the
number of connections, open files, or sessions.

3- 15

LIMIT CONNECTIONS

Limiting the Number of Connections
To set the maximum number of connections that the VAXNMS server
can establish, use the LIMIT CONNECTIONS command.
You can limit the number of connections for:
•

All workstations

•

One session or workstation

•

A specific alias

You can issue multiple LIMIT CONNECTIONS commands. However,
when two limits are imposed, the most restrictive limit applies. For example, you can limit the total number of connections to 10 connections, and
limit the number of connections for one workstation to 11 connections. If
one workstation establishes 10 connections, the VAXNMS server accepts
no further connection requests, even though the connection limit for one
workstation is not satisfied.
The default for the number of connections is "No limit".
Format

LIMIT CONNECTIONS [/TOTAL I /SESSION I /ALIAS=name] nnn

Where:
ITOTAL

Specifies that you want to limit the total number of connections to the VAXNMS server. This is the default.

ISESSION

Specifies that you want to limit the number of connections to the VAXNMS server for anyone workstation.

IALIAS=name Specifies that you want to limit the number of connec-

tions for the specified alias. The. "name" is the name of
an account, specified in the user access file, for the
VAXmate system software, a user, an application, a
common directory, or a printer queue. This qualifier is
useful for limiting the number of users who can connect
to one directory at the same time. For example, if a directory contains a restricted application, you can specify
the IALIAS qualifier to limit the number of users who can
connect at one time.

3- 16

LIMIT CONNECTIONS
nnn

Is the number to which you want to limit the connections.
The number can be a positive integer or the keyword
"No limit". The largest number you can specify is limited
by the VAXNMS working set size. For more information
about the working set size, see Chapter 4.

If you do not specify a qualifier for the LIMIT CONNECTIONS command, the default is the ITOTAL qualifier.

Example 1

To limit the total number of workstations that can connect to the
VAXIVMS server at one time to 30, type:
PCFS>LIMIT CONNECTIONS /TOTAL 30
PCFS>

Example 2

To limit the number of connections for one workstation to 20, type:
PCFS>LIMIT CONNECTIONS /SESSION 20
PCFS>

Example 3

To limit the number of connections to the alias SMITH to 10, type:
PCFS>LIMIT CONNECTIONS /ALIAS=SMITH 10
PCFS>

3- 17

LIMIT FILES

Limiting the Number of Open Files
To set the maximum number of files that the VAXNMS server can open,
use the LIMIT FILES command.
You can limit the number of open files for:
•

All workstations

•

One workstation or session

The default for the number of open files is 1024 files.
Fonnat

LIMIT FILES [/TOTAL I /SESSION] nnn

Where:
!TOTAL

Specifies that you want to limit the total number of files
that the VAXNMS server can open for all workstations.
This is the default.

ISESSION

Specifies that you want to limit the number of files that the
VAXNMS server can open for one workstation or session.

nnn

Is the number to which you want to limit the number of
open files. The maximum number of open files is 1024 files.

If you do not specify a qualifier for the LIMIT FILES command, the
default is the !TOTAL qualifier.

Example 1

To limit the total number of files open at one time to 60, type:
PCFS>LIMIT FILES /TOTAL 60
PCFS>

Example 2

To limit the number of open files for a session to 40, type:
PCFS>LIMIT FILE /SESSION 40
PCFS>

3-18

LIMIT SESSIONS

(

Limiting the Number of Sessions
To set the maximum number of sessions or workstations for which the
VAXNMS server can establish a logical link, use the LIMIT SESSIONS
command.
The default number of sessions is 32 sessions.
If you increase the number of sessions, you must increase the number of

logical links that DECnet-VAX allows using the NCP SET EXECUTOR
MAXIMUM LINKS command. For information about this command, see
the VAXIVMS Network Control Program Reference Manual.
Also, make sure the number of input/output (I/O) channels that the server
can open at one time is lar,8'e enough to allow the server to establish a
large number of sessions. For more information about changing the
number of I/O channels, see Chapter 4.
Format

LIMIT SESSIONS nnn

(

Where:
nnn

Is the number to which you want to limit the number of
sessions. The maximum number of sessions is 960 sessions.
While the VAXNMS server allows more than 960 sessions, the
VAXNMS operating system does not accept more than 960 logical links.

Example

To limit the number of sessions for which the VAXNMS server can establish a logical link to 25 sessions or workstations, type:
PCFS>LIMIT SESSIONS 25
PCFS>

3- 19

LOG

Logging Network Events
To instruct the VAXNMS server to log server events, use the LOG
commands.
You can log VAXNMS server events to monitor the VAXNMS server
usage. This allows you to:
•

Determine how much the VAXNMS server is used

•

Track errors that the VAXNMS server generates, which can help
when solving a problem with the VAXNMS server or the network.

Table 3-2 describes the VAXNMS server events that you can log.
Table 3-2 VAXNMS Server Events You Can Log
Event Name

Description

ALL

Logs (or stops logging) all events that the VAXNMS
server can log. This command has the same effect as
turning on (or turning off) logging for all possible LOG
commands.

CONNECTIONS Logs (or stops logging) all connection and disconnection
requests.
ERRORS

Logs (or stops logging) all nonfatal errors. Nonfatal
errors are errors from which the VAXNMS server can
still recover.

FATAL

Logs (or stops logging) all fatal VAXNMS server
errors. Fatal errors are errors that cause the
VAXNMS server to stop its normal operation. The
VAXNMS server logs the error condition before the
VAXNMS server stops.

LOCKS

Logs (or stops logging) all file lock and unlock requests.

OPENS

Logs (or stops logging) all file open and close requests.

OPERATOR

Logs (or stops logging) operator actions, such as SET
ALIAS.

3- 20

C~:

LOG

(

PROTOCOL

Logs (or stops logging) all protocol errors and session
aborts. Protocol errors are errors that occur any time a
workstation sends an invalid or partial message to the
VAXNMS server. Session aborts occur when a
workstation disconnects its session abnormally (for example, a user may turn off the workstation without
disconnecting it from the VAXNMS server).

READS

Logs (or stops logging) all file read and write requests.

SECURITY

Logs (or stops logging) all attempted security breaches.
This command logs any time a workstation attempts to
connect to a nonexistent account or supplies an incorrect password with a valid user name.

SESSIONS

Logs (or stops logging) all requests to start or stop a
session.

The events that are logged by default are nonfatal errors, fatal errors,
protocol errors, and security errors. You should only log other events that
you need to know about. The fewer events you ask the VAXNMS server
to log, the better the performance of the server.
If you specify the event name with the ON parameter or with no parameters, the VAXNMS server logs the specified event. If you specify the

event name with the OFF parameter, the VAXNMS server stops logging
the specified event. If you specify only the event name, the VAXNMS
server logs the event. If you do not specify the event name, the
VAXNMS server displays a list of the current log settings.
Format

LOG [eventname [ON I OFF]]

Where:
eventname

Is the name of the VAXNMS server event that you want to
log.

3- 21

LOG
Example 1

To display a list of the current log settings, type:
PCFS>LOG
Current Log Settings

-------------------CONNECTIONS
ERRORS
FATAL
LOCKS
OPENS
PROTOCOL
READS
SECURITY
SESSIONS

OFF
ON
ON
OFF
OFF
ON
OFF
ON
OFF

PCFS>
Example 2

To log all connection and disconnection requests, type:

( --')
\

~ .. j

. i

PCFS>LOG CONNECTIONS ON
PCFS>
Example 3

To stop logging all file open and close requests, type:
PCFS>LOG OPENS OFF
PCFS>

c
3- 22

REFUSE CONNECTIONS

(

Refusing Connections
To have the VAXNMS server refuse any further connection requests from
workstations, use the REFUSE CONNECTIONS command.
You can refuse connections in preparation for stopping the VAXNMS
server. This way, no other workstations can connect while you wait for
other workstations to disconnect.
The VAXNMS server maintains all existing connections with workstations. When the last workstation disconnects, the VAXNMS server waits
until you issue an ACCEPT CONNECTIONS or START SERVER command.
You can see if the VAXNMS server is accepting connections with the
SHOW STATUS command.
Format
REFUSE CONNECTIONS

Example

To have the VAXNMS server refuse any further connection requests,
type:
PCFS>REFUSE CONNECTIONS
PCFS>

3- 23

REFUSE UNREGISTERED

Refusing Unregistered Nodes
To have the VAXNMS server refuse a connection request from a workstation that is not registered in the volatile DECnet node name database, use
the REFUSE UNREGISTERED command.
The volatile database, which is stored in memory, contains the node
names that are registered with DECnet and are recognized by the
VAXNMS server and other information about the current state of the
network. By default, only registered DECnet nodes can connect to the
VAXNMS server.
NOTE
To register a node with the DECnet databases, use the
PCFS Administration utility. For more information, see
Chapter 2.
When you issue the REFUSE UNREGISTERED command, the
VAXNMS server maintains all existing connections with workstations, including unregistered workstations.
You can allow unregistered DECnet nodes to connect to the VAXNMS
server with the ACCEPT UNREGISTERED command. For more information, see Chapter 3.

Format
REFUSE UNREGISTERED

Example

To refuse connection requests from unregistered nodes, type:
PCFS>REFUSE UNREGISTERED
PCFS>

o
3- 24

SET ALIAS

( .

Setting the Attributes for Workstation Access
To set the permission on an alias, use the SET ALIAS command.
You can use the SET ALIAS command to restrict user access to different
levels of a directory structure. For example, you can set an entire directory structure to read access, then set less restrictive access to individual subdirectories. The default protection for an alias is read, write, and
create privileges.

Format
SET ALIAS alias [/READ] [/WRITE] [/CREATE]
Where:

(

alias

Is the VAXNMS account name associated with the
connection.

{READ

Gives the client read access for the alias.

{WRITE

Gives the client write access for the alias.

{CREATE

Gives the client create access for the alias.

Example 1
To restrict the alias JONES to read-only permission, type:
PCFS>SET ALIAS JONES /READ

Example 2
To restrict the alias JONES to read and write permissions, type:
PCFS>SET ALIAS JONES /READ /WRITE

(

.. ~.\

3- 25

SET LOG FILE

Changing the Log File
To close the current log file and create a new log file, use the SET LOG
FILE command.

NOTE
The VAXNMS server automatically creates a new log file
named SYS$SPECIFIC:[PCFS]PCFS SERVER.LOG each
time you start the server.
The log file is a standard text file that contains one or more messages.
The messages describe network events that occur during the operation of
the VAXNMS server.
To display the name of the current log file in the SYS$SPECIFIC:[PCFS]
directory, use the SHOW LOG FILE command.
The VAXNMS server updates the log file once every 60 seconds. After an
event occurs, the event is logged within the next minute.
To display the messages that are in the log file, use the .VAXNMS TYPE
command. You can also change the log file and edit the original log file to
see the messages. For an explanation of the messages in the log file, see
Chapter 5.
The SET LOG FILE command:
•

Closes the current log file

•

Creates a new version of the file name specified on the command
line

•

Begins using that file as a log file

You can control which events the VAXNMS server logs with the LOG
command.
Format
SET LOG FILE filename

Where:
filename

3- 26

Is the name of the log file. The default file name is
PCFS SERVER.LOG.

/' \
(;
~-~

- - - - ._ ... _--_.- - - - - -

SET LOG FILE

(

Example
To change the log file name to NEWFILE.LOG, type:
PCFS>SET LOG FILE NEWFILE.LOG
PCFS>

(

3- 27

SHOW CONNECTIONS

Showing the Connections to the VAX/VMS Server
To display the status of the connections recognized by the VAXNMS
server, use the SHOW CONNECTIONS command. The status of the connections includes:
•

Connection ID, which is the number the VAXNMS server assigned
to the connection when it was established

•

UIC, which is the User Identification Code for the account that
established the connection with the VAXNMS server

•

Alias, which is the account name assigned to the device and directory to which the workstation has connected

•

Workstation, which is the DECnet node name assigned to the
user's workstation

•

Path, which is the device and directory to which the workstation is
connected

Use the CLOSE CONNECTION command to disconnect a connection.
Format
SHOW CONNECTIONS

Example
To display information about the connections recognized by the VAXNMS
server, type:
PCFS>SHOW CONNECTIONS
Connection

ID UIC
0
1
2
3
4

PCFS>

[360,010]
[360,103]
[360,250]
[360,016]
[200,023]

Alias

Workstation

Path

VXSYS
ISSYS
SALES
PCAPP
SMITH

ORANGE
YELLOW
ORANGE
ORANGE
GREEN

DVL: [VXSYS]
WRK: [ISSYS]
WRK:[PCCOMMON.SALES]
DVL: [PCAPP]
WRK: [SMITH]

C)
-'

3- 28

SHOW FILES

(

Showing the Open Files
To display the status of open files, use the SHOW FILES command. The
status of open files includes:
•

File ID, which is the number that the VAXNMS server assigned
to the file when it was opened

•
•

File size, which is the size of the open file in bytes
Locks, which is the number of locks that workstations have imposed on the open file

•

Workstation, which is the DECnet node name assigned to the
workstation from which the user opened the file
File name, which is the name of the open file, including the device
and the directory

•

Format
SHOW FILES

[dey: [directory]filename.ext]

Where:

(

dev
directory

filename. ext

Is the device name.
Is the directory name, including any subdirectories. If you
specify a directory name, it must be enclosed in square
brackets.
Is the file name and file extension.

If you do not specify the device, directory, or file name, or you specify an

asterisk, the VAXNMS server displays the status for all open files in the
default directory on the default device.
Example
To display a list of all open files, type:
PCFS>SHOW FILES
File
10
File Size

o
1

1201
9823

Locks

o
o

Workstation

File Name

ORANGE
GREEN

WRK:[PCCOMMON.SALES]OCT.TXT
WRK:[SMITH]REPORT.TXT

PCFS>

3- 29

~~~~~~----------~

SHOW LIMITS

Showing the Limits
To display a list of current limits imposed by the VAXNMS server, use
the SHOW LIMITS command. The limits imposed by the VAXNMS
server include:
•

Total sessions per V AXNMS server

•

Total connections per V AXNMS server

•

Total open files per V AXNMS server

•

Maximum connections per session

•

Maximum open files per session

•

Maximum connections per alias

See the LIMIT command for an explanation of each limit or to change a
limit.

Format
SHOW LIMITS

Example
To display a list of the current d~fault limits, type:
PCFS>SHOW LIMITS
Total sessions per server
Total connections per server
Total open files per server
Maximum connects per session
Maximum open files per session
Alias

Limit

SMITH
VXSYS
RBASE

1
10
3

PCFS>

3- 30

32
No limit set
No limit set
No limit set
No limit Bet

SHOW LOG FILE

Showing the Log File N arne
To display the name of the current log file, use the SHOW LOG FILE
command. The log file is in the directory SYS$SPECIFIC:[PCFS).
You can change the log file with the SET LOG FILE command.

Format
SHOW LOG FILE

Example
To display the name of the current log file in the SYS$SPECIFIC:[PCFS)
directory, type:
PCFS>SHOW LOG FILE
Current server log file is PCFS_SERVER.LOG
PCFS>

3- 31

SHOW SESSIONS

Showing the Sessions
To display the status of the sessions recognized by the VAXNMS server,
use the SHOW SESSIONS command. The session status includes:
•

Workstation ID, which is the number that the VAXNMS server
assigns to a workstation when its session is established

•

Workstation, which is the DECnet node name assigned to the
workstation from which the user connected to the VAXNMS
server

•

Connections, which is the number of connections made by the
workstation to the VAXNMS server

•

Open Files, which is the number of files that the workstation has
open

Format
SHOW SESSIONS

Example
To display information about the current workstations for which the
VAXNMS server has established logical links, type:
PCFS>SHOW SESSIONS
Workstation
ID

Workstation

ORANGE
GREEN

Connections

Open Files

6
1

1
1

PCFS>

c
3- 32

SHOW STATUS

(

Showing the Status of Server Connections
To display what kind of connection requests the VAXNMS server is accepting (registered or unregistered), use the SHOW STATUS command.
You can allow the VAXNMS server to accept connection requests with
the START SERVER command. You can limit the number of connections
that the VAXNMS server accepts with the LIMIT CONNECTIONS command.
Use the ACCEPT UNREGISTERED command to allow the VAXNMS
server to accept connection requests from workstations whose names are
not registered in the volatile DECnet node name database. Use the
REFUSE UNREGISTERED command to disallow server acceptance of
connection requests.

Format
SHOW STATUS

Example
To determine whether the VAXNMS server is accepting connection
requests, type:
PCFS>SHOW STATUS
Server is accepting connection requests.
Server will refuse unregistered users.

PCFS>

3- 33

SHOW VERSION

Showing the VAXNMS Server's Version Number
To display the version number for the VAXNMS server, use the SHOW
VERSION command.
Format

SHOW VERSION
Example

To display the version number, type:
PCFS>SHOW VERSION
VAX/VMS Server for MS-DOS Vl.l
PCFS>

o
3- 34

START SERVER

Restarting the VAXNMS Server

(....

Use the START SERVER command to:
•

Allow the VAXNMS server to establish sessions with one or more
workstations

•

Restart the VAXNMS server after the STOP SERVER or
REFUSE CONNECTIONS command

Format
START SERVER

Example
To start the VAX/VMS server, type:
PCFS>START SERVER
PCFS>

(

3- 35

--_.

~~.-~~~-------

------

STOP SERVER

Stopping the VAX/VMS Server
To force the VAXNMS server to stop all sessions, use the STOP
SERVER command.
.
The VAXNMS server asks you to verify that you want to stop the
VAXNMS server. If you verify your request, the VAXNMS server disconnects all current connections to any workstation and closes all files opened
by that session.
If users attempt to access the VAXNMS server an error message is

displayed.
The STOP SERVER command does not stop the VAXNMS server
process.
Format
STOP SERVER

Example

To stop the VAXNMS server, type:
PCFS>STOP SERVER

Do you want to stop the server? [N]:y

PCFS>

c
3- 36

(

Chapter 4
VAX/VMS Server
Configuration
This chapter tells you how to configure the VAXNMS server to:

•

Set start-up defaults for the VAXNMS server

•

Change limits and quotas imposed by the VAXNMS operating
system

You can set start-up defaults for the VAXNMS server and change some
limits imposed by the VAXNMS operating system in the
PCFS STARTUP.COM file.
This chapter also tells you how to:
•

Change the VAXNMS operating system limit on the number of
input/output (110) channels

•

Add and remove resources, such as applications and printers

The PCFS STARTUP.COM File
The PCFS STARTUP.COM file is a command file that starts the
VAXNMS-server and executes specified operator interface commands.
The default PCFS_STARTUP.COM file is displayed on the following
pages.

NOTE
If you run the PCFS STARTUP. COM file while the
VAXNMS server is running, the procedure in the file stops

the server, which stops all sessions established with the
server.

(
4- 1
---

~---

-~.--~~~~~-

VAXIVMS Server Configuration
$

II , II ! ! I ! ! ! II ! ! ! I ! ! II ! I ! , I II! ! II 1111 ! ! IIIII IIII ! I ! III III I! I ! I ! II I I I II

VAX/VMS Server for MS-DOS (PCFS) Startup Command File

$
$
$
$
$

!!!!!!!!!!!!!!!!!!!!!! I!! II!!!!! I!!!!! I!!!!! III!! I!!!!! I! 11111 III II! I

$
$
$

$
$
$
$
$
$

$
$

$
$
$
$
$
$

THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND
COPIED ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH
THE INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY
OTHER COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY TRANSFERRED.
THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT
NOTICE AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL
EQUIPMENT CORPORATION.
DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT THAT IS NOT SUPPLIED BY DIGITAL.

(' "\
~)

!!!!!!! I! III II! II'I!!!' 1111 ! I'!!' " " ! , ,! 1111111 !! III! 'III! 1111111111

$
$

!!!!! II ! II !!!!!! !!!! !!!!!!!!! I!!!!!!!!!!! ! I! ! I!!! ! II! 1'1" 11'1111' 'III
,

Ensure that the correct privileges are enabled.

$
$
$
$

II II ! ! II ! II II II II II II ! ! I II ! ! II II ! ! II II ! ! " II II ! ! , II ! I ! ! I II ! II II II ! ! I I I

$ PCFS$PRIVS = "BYPASS, CMEXEC, CMKRNL, DETACH, EXQUOTA, GROUP, LOG_IO,NETMBX, OPER, PHY_IO, PRMMBX, SYSNAM, SYSPRV, TMPMBX, WORLD"
$ SAVE$PRIVS = F$SETPRV(PCFS$PRIVS)
$ IF .NOT. F$PRIV(PCFS$PRIVS) THEN EXIT 36
I No privilege error code
$

$
$
$
$

!!! I!!! I! II! III! IIII! I! I!! I! II!! III I! 11111 11111 I! I! I!!!!! III! III I! I! !.I
I

If a version of the server is already running, stop it.
!!!!!!!!!!! I!! I!! I!! II! I!'!!!!!!!!!!!!! I!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

4- 2

VAXNMS Server Configuration
$ CONTEXT '"' ""
$ LOOP:
$
PID = F$PID (CONTEXT)
$
IF PID . EQS. "" THEN GOTO DONE
$
NAME = F$GETJPI (PID, "PRCNAM")
$
IF NAME ".NES. "PCFS_SERVER" THEN GOTO LOOP
$
STOP /ID='PID'
$ DONE:
$ WAIT 00:00:03
Wait for process deletion
$
$
$

$
$
$

I!!! I ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! I ! ! ! ! ! ! ! ! ! ! I ! I ! ! ! ! ! ! I ! II ! 1111 ! III! ! ! ! ! ! ! ! II ! ! ! I ! I

Start up the current version of the server.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I!!!! I!!!!!!!!!!!!!! I! I! III I!!! IIII

(

$ PCFS$CURRENT = F$TRNLNM("SYS$DISK")+F$DIRECTORYO
$ SET DEFAULT SYS$SPECIFIC: [PCFS]
$ RUN
SYS$SYSTEM:PCFS_SERVER.EXE/DETACH /INPUT=NL: /OUTPUT=SYS$SPECIFIC:[PCFS]PCFS_OUTPUT.LOG
/ERROR=SYS$SPECIFIC: [PCFS]PCFS_ERROR.LOG /PROCESS=PCFS_SERVER /DUMP /AST_LIMIT=100 /BUFFER_LIMIT=300000 /FILE_LIMIT=1024 /IO_BUFFERED=65 /IO_DIRECT=1024 /MAXIMUM_WORKING_SET=2048 /QUEUE_LIMIT=20 /PAGE_FILE=10000 /WORKING_SET=1024
$ SET DEFAULT 'PCFS$CURRENT'
$ WAIT 00:00:03
! Wait for process startup
$
$

!!!!! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !! ! ! I ! ! ! ! ! ! ! ! !! ! ! ! ! ! ! ! I ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! !

Put startup specific operator interface commands here.

$
$
$

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! I ! !

4- 3

VAXNMS Server Configuration
$ MCR PCFS_OPERATOR
SET ALIAS PCAPP /READ
Set the PC Applications alias R/O
SET ALIAS VXSYS /READ
Set the VAXmate system alias R/O
SET ALIAS ISSYS /READ
Set the industry-standard alias R/O
SET ALIAS RBSYS /READ
Set the Rainbow system alias R/O
ACCEPT UNREGISTERED , Accepts unregistered connects

$
$
$
$
$

$
$

!!,!"!!!'" I!!! III'!!!!! I!!! I! II!!!! II!! I! 11111 III!! II'! III II! III'II!
I

Reset this process' initial privileges.

$
$
$
$

! IIIII ! I ! ! ! ! I ! ! II ! II ! ! ! I ! I ! ! ! ! ! ! ! ! ! ! III! ! ! ! III! IIII !! ! 111111 , I , ! ! III! I

$ PCFS$PRIV = F$SETPRV(SAVE$PRIVS)

You can edit the PCFS STARTUP.COM file to:
•

Include commands that will be executed each time you start the
VAXNMS server

•

Change the default limits imposed with the RUN command
qualifiers

Including Operator Interface Commands
The following operator interface commands are the ones most commonly
added to the PCFS STARTUP. COM file:
•
•
•
•

The LIMIT commands
The ACCEPT UNREGISTERED command
The SET LOG FILE command
The SET ALIAS command

For more information about these commands, see Chapter 3.
To include an operator interface command, type the command at the
bottom of the file, under the example command:
ACCEPT UNREGISTERED

! Accepts unregistered connects

For example, to set the limit for the number of connections to the alias
SALES, add the following line to the appropriate place in the
PCFS STARTUP. COM file:

4- 4

VAXNMS Server Configuration
$ LIMIT CONNECTIONS /ALIAS=SALES 10

Changing V AX/VMS Limits and Quotas
The PCFS STARTUP.COM file includes some VAXNMS RUN command
qualifiers that allow you to change some VAXNMS limits and quotas. The
command qualifiers are set when the PCFS SERVER.EXE file is run.
The PCFS STARTUP.COM file, including the default values for the RUN
command qualifiers is displayed earlier in this chapter.
You can edit the PCFS STARTUP.COM file and change the following
command qualifiers:
•

AST LIMIT, which specifies the maximum number of outstanding
Asynchronous System Traps (AST) that the VAXNMS server can
have. The number of ASTs should be greater than or equal to the
maximum number of workstations plus 12. Use the PCSERVER
LIMIT SESSIONS command to limit the number of workstations.
If users make more requests than the AST LIMIT supports, users

making the extra requests receive an error message.

(

•

BUFFER LIMIT, which specifies the maximum amount of nonpaged system memory (in bytes) that the VAXNMS server can
use. The system memory is used for:

110 buffering
DECnet request messages
File control blocks
The system memory, in bytes, should equal:
[maximum number of workstations'" 4398] + 12000
•

10 BUFFERED, which specifies the maximum number of
outstanding buffered 1/0 operations that the VAXNMS server can
have at one time.

The 10_BUFFERED limit should be greater than or equal to:
[maximum number of workstations'" 2] + 1
If you change the values assigned to any command qualifiers in the

(-/

PCFS STARTUP.COM file, run the PCFS STARTUP.COM file so the
VAXNMS server recognizes the new values assigned to the qualifiers.

4- 5

VAXIVMS Server Configuration
The PCFS STARTUP.COM file includes other command qualifiers with
default values. It is recommended that you do not change the default
values for these command qualifiers:
•

•

f\
U

FILE LIMIT, which specifies the maximum number of files that
the VAxNMS server can have open at anyone time. This command qualifier has essentially the same function as the
PCSERNER LIMIT FILES command.
10 DIRECT, which specifies the maximum amount of outstanding
system memory (in bytes) for direct I/O operations that the
VAXNMS server can have at one time.

•

MAXIMUM WORKING SET, which specifies the maximum
number of pages to which the VAXNMS server can increase its
working set size.

•

PAGE FILE, which specifies the maximum number of pages allocated in. the paging file for the VAXNMS server.

•

WORKING SET, which specifies the default working set size for
the created process. The default working set size is the number of
pages of main memory the VAXIVMS server can use for its working set.
NOTE
For more information about these VAXNMS command
qualifiers, see the RUN (process) command in the
VAXNMS DeL Dictionary.

VAX/VMS Input/Output Channels
The VAXNMS operating system imposes a limit on the number of inputl
output channels that a process can open at one time. The default value is
127 channels.
You can change this limit by modifying the CHANNELCNT parameter
using SYSGEN. You can have up to 2047 channels.
The VAXNMS server requires one channel for:
•

Each workstation

•
•

Each open file
Each opening of a nonstream file

•

The log file

4- 6

VAXNMS Server Configuration
The VAXNMS server also requires two channels to manage its DECnet
links.
To determine the number of channels that your VAXNMS server needs to
open, multiply the number of open files per workstation plus one, times
the number of workstations, then add three.
[(OPEN FILES per WORKSTATION + 1) * NUMBER OF
WORKSTATIONS] + 3
For example, if 50 workstations can connect to the VAXNMS server and
you want to allow each workstation to open 4 files, the number of channels is as follows:
[(4 + 1)

* 50] + 3 = 253 channels

Adding and Removing Resources
The VAXNMS server includes the PCFS Administration utility, which
creates directories and accounts for resources on the VAXNMS server. It
is recommended that you use this command file to add and remove resources.
However, if you use VAXNMS utilities to create directories and accounts
and install printer queues, use this section to determine the resource
requirements for the VAXNMS server.
NOTE
The resources that you add to or remove from the server
using VAXNMS utilities are not recognized by the PCFS
Administration utility. Therefore, be sure that anything you
add to the server using VAXNMS utilities is removed
using VAXNMS utilities.
To add and remove resources, you must access an account that has OPER
and SYSPRV privileges. To determine the privileges for an account, use
the SHOW PROCESS/PRIVILEGES command.
When you installed the VAXNMS server, you specified a group number
for UICs associated with the VAXNMS server. The default number is
360. The PCFS Administration utility requires an exclusive UIC for the
directories and accounts it creates. You can create directories and accounts with this UIC or with another UIC. The examples presented here
assume that the group UIC is 360.

4- 7

VAXNMS Server Configuration
NOTE
The qualifiers and parameters described in this section are
the minimum requirements for the VAXNMS server. You
can add other qualifiers or parameters as needed.
These instructions ONLY describe the portion of a task
that requires the VAXNMS operating system. Some tasks
also require that you use the MS-DOS operating system
from a workstation. For a complete description of all tasks,
see Chapter 2.
For more information about any of the VAXNMS utilities described in
this section, refer to the VAXNMS documentation set.

Adding a User
To add a user, it is recommended that you create a personal directory and
alias and register the user's DECnet node.
1.

Create a directory. Set the directory protection so the owner has
RWED privileges and assign a unique owner UIC. You can create
the directory as a subdirectory of the VXUSERS directory, which
was created when you installed the VAXNMS server directory
structure.

(.---"\\

For example, to add a user SMITH, you can create a directory
using the CREATEIDIRECTORY command:
$ CREATE/DIRECTORY DVL: [VXUSERS.SMITH]
/PROTECTION=[O:RWED]
/OWNER=[360,120]

2. Create an account. The account for the personal directory is the
alias the user specifies to connect to the directory. The UIC must
be the same UIC you assigned when you created the directory.
For example, to create the account for user SMITH, you can use
the AUTHORIZE program:
UAF> ADD SMITH
/PASSWORD=JOHN
/UIC=[360,120]
/DEVICE=DVL:
/DIRECTORY=[VXUSERS.SMITH]

4- 8

VAXNMS Server Configuration
/NOBATCH
/NOINTERACTIVE
/FLAGS=(CAPTIVE,DISCTLY,DISMAIL,DISRECONNECT)/PWDLIFE=O

(

3. If disk quotas are enabled for the volume where you created the
directory, add an entry to the quota file.
For example, if disk quotas are enabled for device DVL where you
created a directory for user SMITH, you can use the DISK
QUOTA utility:
DISKQ>USE DVL:
DISKQ>ADD [360,120]/PERMQUOTA=2000/0VERDRAFT=100

(

Register the DECnet node name and address of the user's workstation. Each workstation must be registered with the permanent and
volatile databases.
For example, if a workstation DECnet node name is BOSTON and
the DECnet node address is 9.222, you can use NCP:
NCP>SET NODE 9.222 NAME BOSTON
NCP>DEFINE NODE 9.222 NAME BOSTON

Adding a Common Directory
To add a common directory, it is recommended that you create the directory and an alias for the directory. To add a common directory:
1.

Create a directory. Set the directory protection so the owner and
the group have RWED privileges, and assign a unique owner UIC.
You can create the directory as a subdirectory of the PCCOMMON
directory, which was created when you installed the VAXNMS
server directory structure.
For example, to add the common directory SALES, you can create
a directory using the CREATEIDIRECTORY command:

(

$ CREATE/DIRECTORY DVL: [PCCOMMON.SALES]
/PROTECTION=[O:RWED,G:RWED]
/OWNER=[360,130]

4- 9

VAXNMS Server Configuration
2.

Create an account. The account for the common directory is the
alias that users specify to connect to the directory. A password is
optional for this account. The UIC must be the same UIC you
assigned when you created the directory.
For example, to create the account for a common directory
SALES, you can use the AUTHORIZE program:
UAF>ADD SALES
/NOPASSWORD
/UIC=[360,130]
/DEVICE=DVL:
/DIRECTORY=[PCCOMMON.SALES]
/NOBATCH
/NOINTERACTIVE
/FLAGS=(CAPTlVE,DISCTLY,DISMAIL,DISRECONNECT)/PWDLIFE=O

If disk quotas are enabled for the volume where you created the
directory, add an entry to the quotas file. For example, if disk
quotas are enabled for device DVL where you created a common
directory, you can use the DISK QUOTA utility:

(' '\
~~)

DISKQ>USE DVL:
DISKQ>ADD [360,130]/PERMQUOTA=2000/0VERDRAFT=100

Adding an Application
To add an application, it is recommended that you create the directory
and two aliases: one alias is read-only, and the other is writeable. A readonly alias allows users to access the applications without accidentally deleting or modifying them. A writeable alias allows you, the system administrator, to maintain the directory. To add an application:
1.

Create a directory. Set the directory protection so the owner has
RWED privileges. Assign a unique owner UIC (this is the UIC for
the writeable alias). You can create the directory as a subdirectory
of the VXAPP directory, which was created when you installed the
VAXIVMS server directory structure.
For example, to add the application RBASE, you can create a directory using the CREATEIDIRECTORY command:

4-10

----.-.~~~

VAXNMS Server Configuration
$ CREATE/DIRECTORY DVL: [VXAPP.RBASE]
/PROTECTION=[O:RWED,G:R]
/OWNER=[360,12]

Create two accounts. One account is the read-only alias that users
specify to connect to the directory. The other account is the writeable alias that you, the system administrator, can specify to connect to the directory.
For example, to create the account for the writeable alias for the
application RBASE, you can use the AUTHORIZE program. The
UIC must be the same UIC you assigned when you created the
directory. Specify the account name in a way that you will recognize it as the writeable alias. The PCFS Administration utility appends a W to the end of the read-only alias. Type:
UAF>ADD RBASEW
/PASSWORD=PRIVATE
/UIC=[360,12]
/DEVICE=DVL
/DIRECTORY=[VXAPP.RBASE]
/NOBATCH
/NOINTERACTIVE
/FLAGS=(CAPTIVE,DISCTLY,DISMAIL,DISRECONNECT)/PWDLIFE=O

To create the account for the read-only alias for the application
RBASE, you can use the AUTHORIZE program. Type:
UAF>ADD RBASE
/PASSWORD=SECRET
/UIC= [360,12]
/DEVICE=DVL
/DIRECTORY=[VXAPP.RBASE]
/NOBATCH
/NOINTERACTIVE
/FLAGS=(CAPTIVE,DISCTLY,DISMAIL,DISRECONNECT)/PWDLIFE=O

Add the appropriate SET ALIAS IREAD command to the server start-up

(

file.

4- 11

VAXIVMS Server Configuration

Adding a New Printer Form
The PCFS Administration utility supports four printers and eight forms
for these printers. You can add another form for one of the four printers
or for a printer that you added yourself.

For example, if you use an LA50 printer with the VAXNMS server and
want to allow users to print files in enhanced print mode, you can create a
new form for this mode.
The eight forms that the PCFS Administration utility automatically defines are:
•

PCFS _ STD_PORTRAIT, which is industry-standard portrait mode

•

PCFS STD LANDSCAPE, which is industry-standard landscape
mode -

•

PCFS_DEC_PORTRAIT, which is DIGITAL portrait mode

•

PCFS_DEC_LANDSCAPE, which is DIGITAL landscape mode

•

PCFS _ STD_80, which is industry-standard 80-column mode

•

PCFS _ STD_132, which is industry-standard 132-column mode

•

PCFS_DEC_80, which is DIGITAL 80-column mode

•

PCFS_DEC_132, which is DIGITAL 132-column mode

To create a new form for a printer:
1.

With a text editor, create a file to contain the escape sequence required for the new form. For LA50 enhanced print mode, create a
file called DEC ENHANCED.TXT, and add the sequence
<ESC>[2"z to-the file.

2. Add the file to the device control library for the printer. For example, to add the file DEC ENHANCED.TXT to the LA50 device
control library, type:
$ LIBRARY/INSERT SYS$LIBRARY:PCFS_LA50_DEVCTL.TLB DEC_ENHANCED

4- 12

Create a directory for the new form. Be sure that the directory
name is identical to the file name that you added to the device
control library. Specify the device on which you created the
VAXNMS server directory structure. For the LA50 enhanced print
form, type:

VAXNMS Server Configuration
$ CREATE/DIRECTORY dev: [PCFS_SPOOL. LASO. DEC_ENHANCED]
/OWNER=[360,77]
/PROTECTION=[O:RWED,S:RWED,W)

(
4.

Determine the form name by appending the file name that you
added to the device control library to the "PCFS " string. The
form name for the LA50 enhanced print mode is PCFS- DEC- ENHANCED.

Define the new form and specify an unused form number. (To
display a list of used form numbers, use the SHOW/QUEUE/
FORM command.) For the LA50 enhanced print mode, type:
$ DEFINE/FORM PCFS_DEC_ENHANCED nnnnn/SETUP=DEC_ENHANCED /STOCK=DEFAULT/NOWRAP/WIDTH=BO/NOTRUNCATE

Where:
nnnnn Is the unique form number assigned to the Iiew form.
6.

(

Create an account for the new form by adding an entry in the
UAF. Using the AUTHORIZE utility, copy an existing UAF entry
for another form for the same printer. Be sure you specify the
[PCFS SPOOL.] directory you created for the new form. For the
LA50 enhanced print mode, type:
UAF>COPY LASO_DBO LASO_LQ/DIRECTORY=[PCFS_SPOOL.LASO.DEC_ENHANCED]

To define the new form permanently, add the DEFINE/FORM command
to the SYS$MANGER:PCFS PRINT. COM file. You should add the command after the other DEFINE/FORM commands in the file. When you
restart the VAX computer, the new form is automatically defined.
A PCFS PRINT.COM file is displayed on the following page. The
PCFS PRINT. COM file that you have will differ depending on the print
queues and forms that you add.

4- 13

VAX/VMS Server Configuration

$!
$! Define forms used for PCFS printers
$!
$DEFINE/FORM PCFS_DEC_PORTRAIT
10000/SETUP=DEC_PORTRAIT/NOWRAP/STOCK=DEFAULT/WIDTH-80
$DEFINE/FORM PCFS_DEC_LANDSCAPE
10001/SETUP=DEC_LANDSCAPE/NOWRAP/STOCK=DEFAULT/WIDTH=132
$DEFINE/FORM PCFS_STD_PORTRAIT
10002/SETUP=STD_PORTRAIT/NOWRAP/STOCK=DEFAULT/WIDTH=80
$DEFINE/FORM PCFS_STD_LANDSCAPE
10003/SETUP=STD_LANDSCAPE/NOWRAP/STOCK=DEFAULT/WIDTH=132
$DEFINE/FORM PCFS_DEC_80 10004/SETUP=DEC_80/NOWRAP/STOCK-DEFAULT/WIDTH=80
$DEFINE/FORM PCFS_DEC_132 10005/SETUP=DEC_132/NOWRAP/STOCK-DEFAULT/WIDTH=132
$DEFINE/FORM PCFS_STD_80 10006/SETUP=STD_80/NOWRAP/STOCK-DEFAULT/WIDTH-80
$DEFINE/FORM PCFS_STD_132 10007/SETUP-STD_132/NOWRAP/STOCK-DEFAULT/WIDTH-132
$DEFINE/FORM PCFS_DEC_OFFSET 10010/SETUP=DEC_OFFSET/STOCK-DEFAULT/WIDTH-132
$DEFINE/FORM PCFS_DEC_LQ80 10011/SETUP=DEC_LQ80/STOCK-DEFAULT/WIDTH-80
$!
$! *******NOTE WELL*******
$!
$! The order of printer queue records must be as follows.
$!
in order for the PCFS ADMINISTRATION UTILITY - DELETE PRINTER
$!
function to work properly:
$
$
$
$
$
$

$!printer type
init queue commands
$!
$!next printer

$
$
$
$
$
$

the string $!printertype must be immediately followed
by the init queue commands. etc. no comment lines allowed
between commands associated with this printer

$ LN03 - ADD printer
SET TERM/PERM/WIDTH=132/NOWRAP/PASTHRU/TTSYNC/SPEED=4800/DEVICE_TYPE-LN03 /FORM/TAB TXA3:
$SET DEVICE/SPOOLED TXA3:
$INITIALIZE/QUEUE/START/LIBRARY=PCFS_LN03_DEVCTL /SEPARATE=(FLAG. RESET-(RESET» TXA3:
(-\.
$INITIALIZE/QUEUE/START/GENERIC=(TXA3:) PCFS$LN03
~J'

4-14

VAXNMS Server Configuration

(

$1
$1
$1

$ILA7S - ADD printer
SET TERM/PERM/WIDTH=132/NOWRAP/PASTHRU/TTSYNC/SPEED=4800/DEVICE_TYFE-UNKNOWN /FORM/TAB TXA4:
$SET DEVICE/SPOOLED txa4:
$INITIALIZE/QUEUE/START/LIBRARY=PCFS_LA7S_DEVCTL/SEPARATE=(FLAG,
RESET=(RESET» txa4:
$INITIALIZE/QUEUE/START/GENERIC=(txa4:) PCFS$LA75

When you update the printer connections for a user's key diskette, specify
the alias as the account you created for the new form. For the LA50 enhanced print mode, the alias is LA50 _ LQ.

Adding Another Printer
You can use a printer with the VAX/VMS server that is not supported by
the PCFS Administration utility. For example, if you have a LN01 printer
that you want to use with the VAXNMS server, you can create a device
control library and a print queue.
To use another printer:
1.

Create a file to contain the escape sequence required for the form.
For more information on escape sequences, see your printer
documentation.
For example, to create files for portrait and landscape modes for
an LN01 printer, you can type:
$ CREATE SYS$MANAGER:DEC_PORTRAIT.TXT
<ESC>[?20 J<ESC>[10m«Ctrl/Z»
$ CREATE SYS$MANAGER:DEC_LANDSCAPE.TXT
<ESC>[?21 J<ESC>[15m«Ctrl/Z»
$ CREATE SYS$MANAGER:RESET.TXT
<ESC>[lp«Ctrl/Z»

4- 15

VAXNMS Server Configuration
(\\

Create a device control library for the printer. The device control
library must be created in the SYS$LIBRARY directory. Insert
into the printer device control library, all files that contain the
escape sequences for the forms the printer supports.

For example, to create a device control library and insert files for
an LNOI printer, type:
$ LIBR/CREATE/TEXT SYS$LIBRARY:PCFS_LN01_DEVCTL.TLB
$ LIBR/INSERT SYS$LIBRARY:PCFS_LN01_DEVCTL.TLB SYS$MANAGER:DEC_PORTRAIT
$ LIBR/INSERT SYS$LIBRARY:PCFS_LN01_DEVCTL.TLB SYS$MANAGER:DEC_LANDSCAPE
$ LIBR/INSERT .SYS$LIBRARY:PCFS_LN01_DEVCTL.TLB SYS$MANAGER:RESET

Set the terminal characteristics for the printer you want to add.
For an LNOI printer, type:
$ SET TERM/PERM/WIDTH=132/NOWRAP/SPEED=4BOO/DEVICE_TYPE=LNOl TTAO:

Set the device characteristics for the printer you want to add. For
an LNOI printer, type:
$ SET DEVICE/SPOOLED TTAO:

Define a generic printer queue. The queue name must begin with
PCFS$ and end with the printer type. For example, to add an
LNOI printer that is connected to the device TTAO:, type:
$ INITIALIZE/QUEUE/START/GENERIC=(TTAO:) PCFS$LNOl

Define a physical queue for each device specified with the /
GENERIC qualifier when you defined the generic queue. For example, if you specified the device TTAO for an LNOI printer, define
the physical queue by typing:
$ INITIALIZE/QUEUE/START/LIBRARY=PCFS_LN01_DEVCTL
/SEPARATE=(FLAG, RESET=(RESET»

NOTE
To initialize the queues each time you restart the VAX
computer, add the INITIALIZE/QUEUE commands to a
system start-up file or to a printer start-up file. If you add
the commands to the PCFS PRINT. COM file, follow the
instructions in the file.
-

4-16

TTAO:

VAXIVMS Server Configuration
7. Create a directory for the printer. You must create the directory as
a subdirectory of [PCFS SPOOL], which was created when you installed the VAXNMS server directory structure. For example, to
create a directory for an LN01 printer, type:
$ CREATE/DIRECTORY DVL: [PCFS_SPOOL.LN01]
/OWNER=[360,77]
/PROTECTION=(O:RWED,G,S:RWED,W)

Create a directory for each form that the printer supports. You
must create each directory as a subdirectory of the printer directory. The directory name must be the form name without the
"PCFS_" string.
For example, to create a directory for the PCFS DEC PORTRAIT
and PCFS _DEC_LANDSCAPE forms that the eNOl supports,
type:
$ CREATE/DIR DVL: [PCFS_SPOOL. LN01. DEC_PORTRAIT]

/OWNER=[360, 77]
/PROTECTION=(O:RWED,G,S:RWED,W)

$ CREATE/DIR DVL: [PCFS_SPOOL.LN01.DEC_LANDSCAPE]
/OWNER=[360,77]
/PROTECTION=(O:RWED,G,S:RWED,W)

9. If you created a file for the escape sequence for a form, you must
define the form. Specify an unused form number. The form name
must combine the "PCFS " string and the file name you added to
the device control library.For example, to define the forms for an LN01 printer, type:
$ DEFINE/FORM PCFS_DEC_PORTRAIT nnnnn/SETUP=DEC_PORTRAIT /STOCK=DEFAULT/NOWRAP/WIDTH=80/NOTRUNCATE
$ DEFINE/FORM PCFS_DEC_LANDSCAPE nnnnn/SETUP=DEC_LANDSCAPE /STOCK=DEFAULT/NOWRAP/WIDTH=132/NOTRUNCATE

10. Create an account for each form the printer supports. Each account is the alias that the user specifies to print a file with a particular form. Specify the directory to be the directory you created
for a particular printer form.
For example, to create an account that the LN01 printer supports,
for the PCFS_DEC_PORTRAIT form, type:

4- 17

VAXNMS Server Configuration
$ UAF ADD LN01_DPORT
/NOPASSWORD
/UIC=[360,77]
/DEVICE=DEV
/DIRECTORY=[PCFS_SPOOL ..LN01.DEC_PORTRAIT] /NOBATCH
/NOINTERACTIVE
/NOADD_IDENTIFIER
/FLAGS=(CAPTIVE,
DISCTLY,
DISMAIL,
DISRECONNECT)
/PWDLIFE=NONE
11. To create an account for the PCFS DEC LANDSCAPE form that
the LNOI printer supports, type:
$ UAF ADD LN01_DLAND
/NOPASSWORD
/UIC=[360,77]
/DEVICE=DEV
/DIRECTORY=[PCFS_SPOOL.LN01.DEC_LANDSCAPE] /NOBATCH
/NOINTERACTIVE
/NOADD_IDENTIFIER
/FLAGS=(CAPTIVE,
DISCTLY,
DISMAIL,
DISRECONNECT)
/PWDLIFE=NONE

Removing a User
To remove a user, the V AXNMS server requires that you delete the
user's personal directory, alias, and DECnet node registration.
NOTE
If you added the user with the PCFS Administration util-

ity, you should remove the user with that utility.
Delete the files in the user's personal directory and delete the
directory.
2. Delete the UAF entry for the user's alias. For example, to delete
the entry for the user SMITH, you can use the AUTHORIZE
command:

4-18

VAXIVMS Server Configuration
UAF>REMOVE SMITH

Remove the user's DECnet node registration entry from the network database. For example, to remove the DECnet node
BOSTON, use NCP:
$ NCP PURGE NODE BOSTON
$ NCP CLEAR NODE BOSTON

Removing a Common Directory
To remove a common directory, the VAXNMS server requires that you
delete the common directory and alias.
NOTE
If you created the common directory with the PCFS

Administration utility, you should remove the common directory with that utility.
1.

Delete the files in the common directory and delete the directory.

Delete the UAF entry for the common directory alias. For example, to delete the entry for the common directory SALES, you can
use the AUTHORIZE command:
UAF>REMOVE SALES

Removing an Application
To remove an application, the VAXNMS server requires that you delete
the application directory and aliases.
NOTE
If you added the application with the PCFS Administration

utility, you should remove the application with that utility.

Delete the files in the application directory and delete the
directory.

Delete the UAF entry for the read-only alias for the application.
For example, to delete the entry for the read-only alias for the application RBASE, you can use the AUTHORIZE command:
UAF>REMOVE RBASE

4- 19

VAXNMS Server Configuration
3.

Delete the UAF entry for the writeable alias for the application.
For example, to delete the entry for the writeable alias for the application RBASE, you can use the AUTHORIZE command:
UAF>REMOVE RBASEW

Remove the appropriate SET ALIAS command from the server
start-up file.

Removing a Printer Queue
To remove a printer queue, the V AXNMS server requires that you delete
the directory and aliases for the printer and delete the generic queue and
the physical queue.
NOTE
If you .added the printer queue with the PCFS
Administration utility, you should remove the printer queue
with that utility.
1.

Delete the directory for the printer, including all subdirectories
created for the printer forms.

Delete all UAF entries for the printer aliases. For example, to
delete the entry for the alias for LNOl portrait mode, you can use
the AUTHORIZE command:
UAF>REMOVE LN01_DPORT

Stop and delete the generic print queue. For example, to stop and
delete the generic queue for an LNOl printer, type:
$ STOP/QUEUE PCFS$LNOl
$ DELETE/QUEUE PCFS$LNOl

Stop and delete the physical print queue. For example, to stop and
delete the physical queue for the device TXAO:, type:
$ STOP/QUEUE/RESET TXAO:
$ DELETE/QUEUE TXAO:

4- 20

VAXIVMS Server Configuration

Delete the device control library for the printer. For example, to
delete the device control library for an LNOI printer, type:
$ SET DEF SYS$LIBRARY:
$ DELETE PCFS_LN01_DEVCTL.TLB;*

4- 21

Chapter 5
VAX/VMS Server Messages
This chapter lists the messages that the VAXNMS server can generate.
The messages fall into two sections:
•

Messages found in the log file. The default log file that contains
these messages is SYS$SPECIFIC:[PCFS]PCFS SERVER LOG.
The messages are listed alphabetically, and followed by an explanation, if necessary, advice and, in parenthesis, the LOG command
that must be turned on to display the message. For more information about a LOG command, see Chapter 3.

•

Messages generated by VAXNMS server operator interface. The
messages are listed alphabetically, and followed by an explanation
and advice.

IMPORTANT
If you are unfamiliar with any of the solutions required for

these messages, refer to the appropriate person in your organization. Otherwise, DIGITAL offers training and consulting services that can help you solve these problems. For
more information about the services that DIGITAL offers,
see the Software Product Description.

5- 1

VAXNMS Server Messages

Messages in the Log File
Account for user 'name' has expired
The time period in the UAF for the specified user's account has expired. Use the VAXNMS AUTHORIZE utility to reactivate the account. (LOG ERRORS)
Account for user 'name' is disabled
The specified user can no longer connect to the associated account.
The IFLAGS=DISUSER qualifier is specified for that account in the
UAF. Use the VAXNMS AUTHORIZE utility to reactivate the account. (LOG ERRORS)
Account for user 'name' is disabled for current time
The specified user cannot connect to the associated account at the
current time. The account has been set to deny the user access. Use
the IACCESS qualifier in the VAXNMS AUTHORIZE utility to
change the access to the account. (LOG ERRORS)
Attempted seek beyond range of file 'name' by client 'nodename'
The workstation attempted to seek beyond the range of the specified
file. The workstation should attempt to seek within the file. (LOG
ERRORS)
Can't close file 'name' for client 'nodename'
The VAXNMS server cannot close the specified file for the workstation. The disk where the file is stored may be full, write-protected, or
off-line. Check these possibilities, then close the file with the CLOSE
FILE command. (LOG ERRORS)
Can't create file 'name' for client 'nodename'
The VAXNMS server cannot create the specified file for the workstation. The disk where the file is stored may be full, write-protected, or
off-line. The user may not have the correct privileges to write to the
directory or may have attempted to create a file through a read-only
connection. You should check the disk, the user's authorization, and
the directory protection codes. (LOG ERRORS)

5- 2

VAXNMS Server Messages
(

Can't delete file 'name' for client 'nodename'
The VAXNMS server cannot delete the specified file for the specified
workstation. The disk may be write-protected or off-line. The user
may not have the correct privileges to delete the file. You should
check the disk, the user's authorization, and the directory protection
codes. (LOG ERRORS)
Can't locate file handle 'number' for client 'nodename'
The workstation sent a server message block (SMB) to the
VAXNMS server to access a previously opened file, but the server
cannot find the file handle in its database. If the workstation passed
data directly to the session layer rather than through the redirector,
see the VAXmate Technical Reference Manual to check that the
5MB is in the correct format. Correct the 5MB and pass it again.
(LOG ERRORS)
Can't locate tree 'name' for client 'nodename'
The VAXNMS server established a connection and passed back a
value for the connection to the workstation. In a successive 5MB
request, the workstation requested an unrecognized value for the connection. If the workstation passed data directly to the session layer
rather than through the redirector, see the VAXmate Technical
Reference Manual to check that the 5MB has the correct format.
Correct the 5MB and pass it again. (LOG ERROR)
Can't lock/unlock byte range in file 'name' for client 'nodename'
The workstation attempted to lock or unlock a byte range in the
specified file. The byte range in the specified file is locked by another
workstation. The workstation that locked the byte range must unlock
it before another workstation can access it.
If the workstation passed data directly to the session layer rather
than through the redirector, see the VAXmate Technical Reference
Manual to check that the 5MB has the correct format. Correct the
5MB and pass it again. (LOG ERRORS)

(_~'

Can't process queue information for client 'nodename'. Queue 'name' is

5- 3

VAXNMS Server Messages
stopped.
The workstation requested queue information from the VAXNMS
server. The server cannot access queue information because the
queue is stopped. Use the VAXNMS START/QUEUE command to
restart the queue. (LOG ERRORS)
Can't read from file 'name' for client 'nodename'
The VAXNMS server cannot read the specified file and received an
error the VAXNMS operating system. The disk where the file is
stored may be off-line. The user may not have the correct privileges
to read the directory. Check the disk, the user's authorization, and
the directory protection codes. (LOG ERRORS)
Can't rename file 'name' for client 'nodename'
The VAXNMS server cannot rename the specified file. The disk
where the file is stored may be off-line or write-protected. The user
may not have the correct privileges to write to the directory. Check
the disk, the user's authorization, and the directory protection codes.
(LOG ERRORS)

C'\

Can't write to file 'name' for client 'nodename'
The VAXNMS server cannot write data to the specified file. The
disk may be full, write-protected, or off-line. The user may not have
the correct privileges to write to the directory or may have attempted
to write to a read-only file. Check the disk, the user's authorization,
and the directory protection codes. Make sure the user is not over
quota. (LOG ERRORS)
Can't write to print spooler
The VAXNMS server cannot print a file because the server cannot
write to the print spooler directory. Check that the print spooler directory is large enough. Make sure users have write privileges to the
printer queue directory. For more information about the printer
queue directory and alias, see Chapter 2 or Chapter 4. (LOG
ERRORS)

5- 4

VAXNMS Server Messages
Closed file 'name' for client 'nodename'
The VAXNMS server closed the specified file as requested by the
workstation. (LOG OPENS)
Connection from client 'nodename' refused
The VAXNMS server refused the workstation NET USE command
to establish a connection. The workstation may not have the correct
privileges or may be unregistered. (LOG CONNECTIONS)
Could not re-open LOG file 'name' for PC File Server
The VAXNMS server failed to reopen the log file after the server
closed it for a scheduled update. Check the disk where the log file is
stored to see if it is write-protected or off-line. The VAXNMS server
process stops if this situation occurs. (LOG FATAL)

(

Created file 'name' for client 'nodename'
The VAXNMS server created the specified file as requested by the
workstation. (LOG READS)
DECnet shutting down, server exiting
The VAXNMS server is stopping because DECnet is stopping. (LOG
OPERATOR)
Error processing job info on queue 'name' by client 'nodename'
The VAXNMS server cannot read the print queue. For more information about print queues, see the VAXIVMS Guide to System
Management and Daily Operations. (LOG ERRORS)
File still open for client 'nodename'
The workstation disconnected its session while a file was open. The
VAXNMS server closes the file and logs this message for your information. (LOG ERRORS)

5- 5

VAXNMS Server Messages
File 'name' is not a STREAM file (client 'nodename')
The workstation requested that the VAXNMS server open a
nonstream file for writing. The VAXNMS server can only write to
stream files, which are usually created by the server. (LOG
ERRORS)
Function 'SMBname' took 'number' msec
The function took the VAXNMS server the specified amount of time
to execute. (LOG TIMINGS)
Invalid context for Find Next from client 'nodename'
The workstation was using the find first and find next calls for the
MS-DOS operating system incorrectly. The workstation should try
the procedure again using the corrected calls. (LOG ERRORS)
Invalid mailbox message type 'number'
The VAXNMS server received an undefined message from DECnet.
For more information about mailbox messages, see the DECnet-VAX
User's Guide. (LOG ERRORS)

Invalid NCB received
The VAXNMS server cannot read a network control block (NCB)
from DECnet, because the NCB is in an incorrect format. For more
information about network control blocks, see the DECnet-VAX
User's Guide. (LOG ERRORS)
Invalid number of jobs requested from queue 'name' by client 'nodename'
The workstation passed a server message block request (SMB) that
contains an invalid maximum count for the queue entries. Correct the
5MB, and pass it again. (LOG ERRORS)
Invalid object value specified by Operator
The VAXNMS server received a server message block (SMB) request
to limit or close an unknown object (a session or a connection, for
example). Correct the 5MB and pass it again. (LOG ERRORS)

(\
\

5-6

,,---j

VAXNMS Server Messages
(-

Invalid path 'name' from client 'nodename'
The workstation specified an invalid path name in a command that
sent a server message block (SMB) to the VAXIVMS server. The
workstation should issue the command again using a valid path
name. (LOG ERRORS)
Invalid Protocol from client 'nodename'
A workstation tried to negotiate protocol with the VAXIVMS server,
and the server did not recognize any of the protocol strings. The
workstation is probably not using the VAXmate network software.
(LOG ERRORS)
Invalid queue 'name' specified in request by client 'nodename'
The workstation requested print queue information for an invalid
print queue. The workstation should make the request again using a
valid print queue name. (LOG ERRORS)
Invalid 5MB
The VAXIVMS server received a server message block (SMB) that
the server cannot read. The 5MB is in an incorrect format. The
VAXIVMS server process stops if this situation occurs. (LOG
FATAL)
Invalid 5MB format from client 'nodename'
The workstation passed a server message block (SMB) to the
VAXIVMS server in an invalid format.
If the workstation passed data directly to the session layer rather

than through the redirector, see the VAXmate Technical Reference
Manual to check that the 5MB has the correct format. Correct the
5MB and pass it again. (LOG ERRORS)
Invalid UsernamelPassword for client 'nodename'

(

A NET USE command specified an unrecognized user name or an
illegal password. The user should request the connection specifying
the correct user name and password. (LOG ERRORS)

5- 7

VAXIVMS Server Messages
LIB$ASN_ WITH_MBX failed, status = 'number'
The VAXNMS server failed to initialize itself when it was started.
Make sure the VAXNMS server is started in a privileged account
and that DECnet is running, (LOG FATAL)
Locked range 'number' to 'number' in file 'name' for client 'nodename'
The VAXNMS server locked the specified range in the file as requested by the workstation. (LOG LOCKS)
Opened file 'name' for client 'nodename'
The VAXNMS server opened the specified file as requested by the
workstation. (LOG OPENS)
OPER or SYSPRV pt1vilege required to perform operator functions
Someone tried to use the VAXNMS server operator interface from
an account that does not have OPER or SYSPRV privileges. Use the
VAXNMS server operator interface from an account with these privi( -'\
leges. (LOG E R R O R S ) , , )
Read 'number' characters from file 'name' for client 'nodename'
The VAXNMS server read the specified characters from the file as
requested by the workstation. (LOG READS)
Requested range in file 'name' locked against client 'nodename'
The workstation cannot access the range of the specified file because
another workstation has already locked that range. The range must
be unlocked by the workstation that locked it before another workstation can access that range. You can also use the CLOSE SESSION
command to disconnect the workstation and remove the lock. (LOG
ERRORS)
Server started on node 'name'
The VAXNMS server started on the specified DECnet node. This is
the first message in the log file when the server starts.

5-8

VAXIVMS Server Messages
SYS$ASSIGN failed for device NAME, status = 'number'
The VAXNMS server cannot assign a unit number to a session. For
more information about the ASSIGN system service, see the
DECnet-VAX User's Guide. (LOG ERRORS)
SYS$QIO(IO$_ READVBLK) failed for mailbox, status = 'number'
The VAXNMS server attempted to read a DECnet message that
does not exist. For more information about mailbox messages, see
the DECnet-VAX User's Guide. (LOG FATAL)
SYS$QIOW(IO$~CPCONTROL) failed, status = 'number'

The VAXNMS server failed to initialize itself when it was started.
Make sure the VAXNMS server is started in a privileged account
and that DECnet is running. When status=20, the
PCFS STARTUP. COM file may have tried to start the VAXNMS
server-process when another server process is running. Make sure
the new server process is started from the same group as the first
server process. (LOG FATAL)
Too much data requested by client 'nodename', virtual circuit aborted
The workstation asked the VAXNMS server for too much data, and
the server disconnected the workstation session.
If the workstation passed data directly to the session layer rather

than through the redirector, see the VAXmate Technical Reference
Manual to check that the 5MB has the correct format. Correct the
5MB and pass it again. (LOG ERRORS)
Tree connect for client 'nodename' to directory 'name'
The VAXNMS server established a connection to the specified directory as requested by the workstation NET USE command. (LOG
CONNECTIONS)
Tree disconnect for client 'nodename' from directory 'name'

(;

The VAXNMS server disconnected a connection to the specified directory as requested by the workstation NET USE ID command.
(LOG CONNECTIONS)

5- 9

VAXNMS Server Messages
Tree 'name' still connected to client 'nodename'

The workstation unexpectedly disconnected its session when it still
had an active connection with the VAXNMS server. The VAXNMS
server closes the active connection automatically. (LOG ERRORS)
Unit 'number': can't create ACE for file 'name'
There was not enough memory to create an ACE for the file.
Unit 'number': can't create file 'name' on top of directory
A workstation requested the VAXNMS server to create the specified
file. The VAXNMS server cannot create the file because a subdirectory with the same name already exists. The user should request
the file creation again and specify a unique file name. (LOG
ERRORS)
Unit 'number': can't open file 'name'
The VAXNMS server did not open the specified file for a workstation. The user may not have the correct privileges to open the file.
The ddiskhmaf'!fl b~ write-prohtected 0lr doff-line. hA process mfay have .
opene t e l e In a way t at prec u es anot er process rom opemng
it. Check these possibilities, and try to open the file again. (LOG
ERRORS)

C
. .)

Unit 'number': connect accept (SYS $QIOW(IO $ACCESS)) failed, status
= 'number'
- The VAXNMS server received a request to connect from a workstation, but DECnet does not allow the VAXNMS server to make the
connection. Check that the workstation session is still active and that
the DECnet is functioning properly. (LOG ERRORS)
Unit 'number': connect accepted
A workstation requested a connection that the VAXNMS server accepted. (LOG CONNECTIONS)
Unit 'number': connect requested, process 'number'
A workstation requested a connection to the VAXNMS server. The
workstation mayor may not have been connected. (LOG
CONNECTIONS)

5- 10

VAXNMS Server Messages
(

Unit 'number': DECnet read AST returned error status 'number'
The VAXNMS server requested its next message from DECnet, and
the VAXNMS operating system returned an error. Check that
DECnet is functioning properly. You may have exceeded the AST
limit. For more information about the AST limit, see Chapter 4.
(LOG ERRORS)
Unit 'number': DECnet read QIO returned error status 'number'
DECnet cannot read what it was attempting to read. Make sure
DECnet is functioning properly. For more information about QIO
error status, see the DEGnet-VAX User's Guide. .(LOG ERRORS)
Unit 'number': directory 'name' already exists
The VAXNMS server cannot create a directory for the specified user
because the directory already exists. The user should create the directory again using another name. (LOG ERRORS)

( ..

Unit 'number': directory create for 'name' failed, errno = 'number'
The operation failed because you do not have the privileges required
to create the directory.
Unit 'number': disconnect initiated by client
A workstation requested to be disconnected from the VAXNMS
server. The workstation mayor may not have been disconnected.
(LOG CONNECTIONS)
Unit 'number': first four bytes of 5MB I=OxFF 's' 'M' 'B'

(

The workstation passed a server message block (SMB) that does not
begin with the correct four bytes: FF, 'S', 'M', 'B'. The VAXNMS
server disconnects the workstation session. If the workstation passed
data directly to the session layer rather than through the redirector,
see the VAXmate Technical Reference Manual to check that the
5MB has the correct format. Correct the 5MB, and pass it again.
(LOG ERRORS)

5- 11

~~~-.

--.~.---.----

...-.--

----------~-

VAXNMS Server Messages
Unit 'number': Invalid 5MB byte data type 'number'
The workstation passed a server message block (SMB) with an invalid type of data field.
If the workstation passed data directly to the session layer rather
than through the redirector, see the VAXmate Technical Reference
Manual to check that the 5MB has the correct format. Correct the
5MB, and pass it again. (LOG ERRORS)
Unit 'number': invalid 5MB received
The VAXNMS server received a server message block (SMB) from
the workstation that the server did not understand.
If the workstation passed data directly to the session layer rather
than through the redirector, see the VAXmate TechnicalReference
Manual to check that the. 5MB has the correct format. Correct the
5MB, and pass it again. (LOG ERRORS)
Unit 'number': link aborted
A workstation unexpectedly disconnected its session without specifying the NET USE device ID command. The workstation may have
( )
been turned off or reset while still connected to the server. ( L O G - ERRORS)
NOTE
It is not uncommon for a log file to contain a number of

"link aborted" messages. You do not have to respond to
these messages unless users are complaining about losing
links to the server.
Unit 'number': link abort failed, status = 'number'
The workstation unexpectedly disconnected its session with the
VAXNMS server. The VAXNMS server could not disconnect the
session. For more information about the link abort, see the DECnet·
VAX User's Guide. (LOG ERRORS)
NOTE
It is not uncommon for a log file to contain a number of
"link aborted" messages. You do not have to respond to
these messages unless users are complaining about losing
links to the server.

5-12

VAXNMS Server Messages
Unit 'number': link close failed status = 'number'
The workstation requested to close a session. The VAXNMS server
could not deassign the unit and close the session. For more information about the failure, see the DECnet-VAX User's Guide. (LOG
ERRORS)
Unit 'number': link disconnected by 3rd party
A workstation session was unexpectedly disconnected by a party
other than the workstation or the VAXNMS server. Use the network
control program (NCP) to see if the network is still active. Check
that the network hardware is working properly. After checking these,
the workstation should re-establish the session with the NET USE
command. (LOG ERRORS)
Unit 'number': path to client lost
A workstation session with the VAXIVMS server was disconnected.
The session time probably expired. The workstation should issue the
NET USE command again to re-establish the session. (LOG
ERRORS)
Unit 'number': Requested access for file 'name' denied
The VAXIVMS server did not allow the workstation to access the
specified file. The workstation does not have the correct privileges to
access the file. You can either change the privileges to allow access
to the file or tell the user about the file restricted access. (LOG
ERRORS)
Unit 'number': 5MB byte data should be null-terminated but isn't
The workstation passed a server message block (SMB) containing
string information that did not end with a zero. If the workstation
passed data directly to the session layer rather than through the redirector, see the VAXmate Technical Reference Manual to check that
the 5MB has the correct format. Correct the 5MB, and pass it
again. (LOG ERRORS)

Unit 'number': 5MB claims to be bigger ('number' bytes) than containing

5- 13

VAXJVMS Server Messages
message ('number' bytes)
The workstation passed a server message block (SMB) with a number
of byte parameters greater than the total byte parameters in the received message.
If the workstation passed data directly to the session layer rather
than through the redirector, see the VAXmate Technical Reference
Manual to check that the 5MB has the correct format. Correct the
5MB and pass it again. (LOG ERRORS)
Unit 'number': 5MB claims word parameters longer than message
The workstation passed a server message block (SMB) with the
number of word parameters greater than the total word parameters
in the received message.
If the workstation passed data directly to the session layer rather
than through the redirector, see the VAXmate Technical Reference
Manual to check that the 5MB has the correct format. Correct the
5MB and pass it again. (LOG ERRORS)
Unit 'number': stunted 5MB received
The workstation passed a server message block (SMB) with total
parameters greater than the total parameters of the received
message.
If the workstation passed data directly to the session layer rather
than through the redirector, see the VAXmate Technical Reference
Manual to check that the 5MB has the correct format. Correct the
5MB and pass it again. (LOG ERRORS)
Unit 'number': SYS$DASSGN failed, status = 'number'
The workstation disconnected its session with the VAXNMS server,
but the server cannot deassign the unit number associated with that
session. For more information about the $DASSGN system service,
see the DECnet-VAX User's Guide. (LOG ERRORS)
Unit 'number': SYS$QIOW(IO$ WRITEVBLK) failed, unit = 'number',
status = 'number'
The VAXNMS server cannot write a message to reply to DECnet.
For more information about the 10$ WRITEVBLK system service,
see the DECnet-VAX User's Guide. (LOG ERRORS)

5-14

VAXNMS Server Messages
(

Unit 'number': virtual circuit aborted by server
The VAXNMS server disconnected a workstation session with the
server, because the workstation passed an incorrect server message
block (SMB). (LOG SESSION)
Unlocked range 'number' to 'number' in file 'name' for client 'nodename'
The VAXNMS server unlocked the specified range in the file as requested by the workstation. (LOG LOCKS)
Wrote 'number' characters to file 'name' for client 'nodename'
The VAXNMS server wrote the specified characters to the file as
requested by the workstation. (LOG READS)

Messages from the V AX/VMS Server
Operator Interface
You can see these messages when you use the VAXNMS server operator
interface.
%PCFS-E-BAD_ INT, invalid .numeric value -

supply an integer

You entered an incorrect value in a LIMIT command. Type the command again using a positive integer or "NO_LIMIT".
%PCFS-E-BADREAD, read from net link failed
The operator interface could not read the response from the server.
%PCFS-E-BADWRITE, write to net link failed
The operator interface could not write a request to the server.
%PCFS-E-BAD_PACKET, unrecognizable data received
The response from the server was not of the proper format.

5- 15

VAXIVMS Server Messages

%PCFS·E·BAD_PROT, protocol refused
The DECnet parameters (possibly the node name or node number)
for the VAX computer are not in agreement with the DECnet para·
meters known to the server. Reconfigure the DECnet parameters.
For more information about DECnet parameters, see the DECnetVAX User's Guide.
o/cPCFS·E·INVFILNAM, invalid filename -

no wildcards are allowed

You specified an asterisk(*) or a percent sign (%) in the SET LOG
FILE or CLOSE FILE command. Wildcards are not allowed. Type
the command again without specifying a wildcard.
%PCFS·E·LONG _FILENAME, invalid file specification· respecify
The file name specified in the operator interface command was too
long to be a valid VMS file name.
%PCFS·E.NO_ITEM, item to CLOSE did not exist
You specified an invalid name or ID with a CLOSE command. Type
the CLOSE command again specifying a valid name or 10.

(. . J\

%PCFS·E·NO_MEM, out of memory
The operator interface could not allocate enough virtual memory to
do the requested operation.
%PCFS·E·NO_SERVER, server process may have terminated
The VAXNMS server encountered a fatal error or the network
became unavailable. Use the VAXNMS SHOW SYSTEM command
to see if the VAXNMS server image is still active. If it is not active,
restart the VAXNMS server and issue the command again.
%PCFS·E·SERVER DIED, server encountered a fatal error· check server
log file
The server terminated with a fatal error; the operator interface can
no longer communicate with it.

5-16

VAXNMS Server Messages

O/OPCFS-F-FATAL, fatal internal error -

'reason'

The VAXNMS server encountered a fatal error that caused it to stop
running. Check the log file to see what the error is. Then check the
first part of this chapter for a list of errors that can be displayed in
the log file.
%PCFS-F-NO_LINK, connect failed -

server image may not be running

You attempted to use the VAXNMS server operator interface on a
DECnet node that is not running the VAXNMS server image. If the
VAXNMS server is installed on that node, run the
PCFS STARTUP.COM program. If the VAXNMS server is not installed-on the DECnet node, see Chapter 1.
%PCFS-F-NO_PRVS, insufficient privileges

(

The account from which you are trying to run the VAXNMS server
operator interface does not have OPER or SYSPRV privileges turned
on. You can only use the VAXNMS server operator interface from
an account with these privileges.

5- 17

Index
A

ACCEPT CONNECTIONS command 3-2, 3-4
ACCEPT UNREGISTERED
command 3-2, 3-5, 4-4
Account
as a server alias 1-17
created by PCFS
Administration utility 1-12
created with the PCFS
Administration utility 1-12
creating with AUTHORIZE
4-8

Adding
another printer form 4-12
application 2-6
application without PCFS
Administration utility 4-10
common directory 2-16
common directory without
PCFS Administration utility 4-9
first user 1-16
node 2-5
node with NCP 4-9
personal directory 2-4
personal directory without
PCFS Administration utility 4-8

printer 2-11
printer without PCFS
Administration utility 4-15
resource without PCFS
Administration utility 4-7
user 2-4
user without PCFS
Administration utility 4-8
Alias
common directory 2-16
creating with AUTHORIZE
4-8

personal directory 1-17, 2-4
restricted applications 2-8
system directory (VXSYS)
1-6, 1-13, 1-14, 1-15
unrestricted applications 2-7
unrestricted applications
(PCAPP) 1-6, 1-10, 1-14
Applications
adding 2-6
adding without PCFS
Administration utility 4-10
backing up 2-18
installing 2-6
licensing 2-8
removing 2-10
removing without PCFS
Administration utility 4-19

Index 1

restricted 2-8
unrestricted 2-7
AST limit 4-5
Asynchronous System Traps
(AST) 4-5
ATTRIB command
for MS-DOS used with the
server 2-18
AUTHORIZE program
for the VAXNMS operating
system 4-8
B

Backing up
server 2-18
Buffer limit 4-5
C
Changing
default limits 3-14
log file 3-26
VAXNMS limits and quotas
4-5
CHANNELCNT parameter
modifying with SYSGEN 4-6
CLOSE CONNECTION command 3-2, 3-6
CLOSE FILE command 3-2,3-8
CLOSE SESSION command
3-2, 3-10
Common directory
adding 2-16
backing up 2-18
created without PCFS
Administration utility 4-9
removing 2-17
removing without PCFS
Administration utility 4-19
Configuring
server 4-1
Connections
accepting 3-4
closing 3-6
limiting 3-16
refusing 3-23
showing 3-28

showing limit 3-30
showing type of 3-33
unregistered nodes 3-4, 3-5,
3-24
CREATE/DIRECTORY
command
for VAXNMS operating
system 4-8
Creating directory structure
1-12

Database
permanent 1-16
volatile 1-16, 3-4, 3-24
DEFINE/FORM command
for the VAXNMS operating
system 4-13
Deleting
application 2-10
common directory 2-17
node 2-6
personal directory 2-6
printer 2-15
user 2-6
Device control libraries 2-11
creating 4-16
Directories
backing up 2-18
common directory 2-16
directory structure 1-10
PCAPP 1-6, 1-10, 1-14, 2-7,
2-10, 2-19
PCCOMMON 1-6, 1-10
PCFS SPOOL 1-6, 1-10, 2-13
personal 1-6, 1-17, 4-8
printers 2-14
restricted applications directory 2-8
unrestricted applications directory 1-10, 2-7
VXAPP 1-6, 1-10, 1-13, 1-14,
1-15, 2-8, 2-10
VXSYS 1-6, 1-13, 1-14, 1-15
VXUSERS 1-6, 1-10

/~':
l
.;/
'---

Index 2

(

DISK QUOTA utility 4-9
Disk quotas
checking 1-2
common directory 2-16
personal directory 2-5
E

(

Errors 5-1
displaying the server's log file
2-20
server event log 3-26
Event log
for VAXmate server 2-20
EXIT command 3-2, 3-12
F
File version limit
common directory 1-6, 2-16
personal directory 1-6, 1-17,
2-4
system directory 1-6
Files
closing 3-8
INFOUSER.IOO 2-18
limiting open 3-18
log file 3-26
PCFS PRINT. COM 2-14
'
4-13
PCFS _ SERVER.LOG 2-20
PCFS_STARTUP.COM 2-2,
4-1
showing limit 3-30
showing log file name 3-31
showing open 3-29
SYSTARTUP.COM 2-14
VAXNMS limit 4-6
WIN.INI 1-16
G
Generic print queue 2-14
without PCFS Administration
utility 4-16
H

(

HELP command 3-2, 3-13
I
Information System

modifying 2-17
INFOUSER.IOO file 2-18
INITIALIZE/QUEUE command
4-16
Input/output channels 4-6
Installation Verification
Procedure 1-2, 1-5
Installing an application 2-6
Installing the VAXNMS server
1-1
10 buffered limit 4-5
10 direct limit 4-6
L
LA50 printer 2-12
LA75 Companion printer 2-12
Leaving the operator interface
3-12
License
for server applications 2-8
LIMIT command 3-2, 3-14, 4-5
LIMIT CONNECTIONS command 2-8, 3-2, 3-16
LIMIT FILES command 3-2,
3-18, 4-6
LIMIT SESSIONS command
3-2, 3-19, 4-5
Limits
AST limit 4-5
buffer limit 4-5
connections 3-16
file limit 4-6
files 3-18
input/output channels 4-6
10 buffered limit 4-5
10 direct 4-6
maximum working set 4-6
page size 4-6
sessions 3-19
showing 3-30
VAXNMS operating system
4-5
working set limit 4-6
LNOI printer 4-15
LN03 PLUS printer 2-12

Index 3

· LN03 printer 2-12
LOG command 2-20, 3-2, 3-20
Log file 3-26
displaying 2-20, 3-26
maintaining 2-20
messages 5-2
showing file name 3-31
M

Maintaining the log file 2-20
Maximum working set limit 4-6
Memory
amount 4-6
for direct 110 operations 4-6
Messages 5-1
Modifying the Information
System 2-17
MS-DOS commands
ATTRIB 2-18
N

NCP SHOW KNOWN NODE
command
for DECnet-VAX 1-15
Network events logging 3-20
Network performance 3-14
Network start-up file 1-10
Node
adding the first 1-15
adding to the server 2-5
adding without PCFS
Administration utility 4-8
assigning 1-15
deleting from the server 2-6
Notes from system administrator 2-18

o
Operator interface 3-1
leaving 3-12
messages 5-15
PCFS STARTUP.COM file
4-1P

Page file limit 4-6
Passwords

Index 4

setting for application alias
2-8
setting for common directory
2-16
setting for PCWAPP alias 1-6
setting for personal directory
1-17, 2-4
setting for printer alias 2-13
setting for VXWSYS alias
1-13
PCAPP
alias 1-6, 1-10, 1-14, 2-7
directory 1-6, 1-10, 1-14
PCCOMMON
directory 1-6, 1-10
PCFS Administration utility
1-11
ADD a Common Directory/
Account 2-16
ADD a Node Registration
Entry 1-15, 2-5
ADD a Personal Directory/
Account 1-17, 2-4
ADD a Printer Queue
Directory/Account 2-13
ADD an Application
Directory/Account 2-8
adding and removing resources without 4-7
CREATE Client system
Directory/Account 1-12
default accounts created 1-15
default device control libraries
2-11
default printer forms 2-11
DELETE a Common
Directory/Account 2-17
DELETE a Node
Registration Entry 2-6
DELETE a Personal
Directory/Account 2-6
DELETE a Printer Queue
Directory/Account 2-15
DELETE an Application

Directory/Account 2-11
PCFS facility name 1-3
PCFS PRINT.COM file 2-14
adding a new form 4-13
PCFS _SERVER process
stopping 2-3
PCFS _ SERVER.LOG file 2-20
PCFS _SPOOL directory 1-6,
1-10, 2-13
PCFS- STARTUP.COM file 2-2 ,
4-1

(

PCSERVER command 3-1
leaving 3-12
symbol 1-11
PCWAPP
alias 1-6, 1-10, 2-7
Performance of the network
3-14
Permanent database 1-16
Personal directory 1-6
adding 2-4, 4-8
backing up 2-18
deleting 2-6
Physical printer queue 2-14
adding without PCFS
Administration utility 4-16
Printer forms 2-11
adding 4-12
Printers
adding 2-11
adding without PCFS
Administration utility 4-15
directory 2-14
generic print queue 2-14
generic queues 2-14
initializing queues 4-16
physical printer queue 2-14
queue names 2-12
removing 2-15
removing without PCFS
Administration utility 4-20
supported by PCFS
Administration utility 2-11
Problems 5-1

displaying the server's log file
2-20
server event log 3-26
Prompt
server 3-1

Q
Quotas of the VAXNMS operating system 4-5
R

Read-only alias
restricted applications 2-8
unrestricted applications 2-7
REFUSE CONNECTIONS
command 3-2, 3-23
REFUSE UNREGISTERED
command 3-2, 3-24
Registering the first node 1-15
Removing
application 2-10
application without PCFS
Administration utility 4-19
common directory 2-17
common directory without
PCFS Administration utility 4-19
node 2-6
node without PCFS
Administration utility 4-18
personal directory 2-6
personal directory without
PCFS Administration utility 4-18
printer 2-15
printer without PCFS
Administration utility 4-20
user 2-6
user without PCFS
Administration utility 4-18
without PCFS Administration
utility 4-7
Restarting the server 3-35
Restricted applications 2-8
read-only alias 2-9

Index 5

writeable alias 2-9
RUN command
for the VAXNMS operating
system 4-5
S
Server files for the VAXNMS
server 1-9
Sessions
allowing 3-35
closing 3-10
limit 3-19
showing 3-30
showing limit 3-30
stopping 3-36
SET ALIAS command 3-2, 3-25
SET LOG FILE command 2-20,
3-2, 3-26, 4-4

SHOW CONNECTIONS command 3-3, 3-28
SHOW FILES command 3-3,
3-29

SHOW LIMITS command 3-3,
3-30

SHOW LOG FILE command
2-20, 3-3, 3-31

SHOW SESSIONS command
3-3, 3-32

SHOW STATUS command 3-3,
3-33

SHOW VERSION command
3-3, 3-34

Site-specific start-up file 2-15
START SERVER command 3-3,
3-35

Starting the server 2-2, 3-35,
4-1

automatically 1-10
STARTNET.COM 1-10
Status
showing 3-33
STOP command 2-3
STOP SERVER command 3-3,
3-36

Stopping the server 2-2, 3-36

SYS$MANAGER:LOGIN.COM
file 1-11
SYS$SYSDEVICE 1-6
SYSGEN 4-6
SYSTARTUP.COM file 2-14
Sysi;lm manager's log-in file
1-11
U

, I

Unregistered DECnet nodes 3-5
Unrestricted applications 2-7
directory 1-10, 1-13
read-only alias 2-7
writeable alias 2-7
User access file (UAF) 1-17
User identification code (UIC)
1-2, 1-7, 2-5, 3-28, 4-8

Users of the server
adding 2-4
adding the first 1-16
removing without PCFS
Administration utility 4-18
V

VAXNMS limits and quotas 4-5
VAXNMS server commands
ACCEPT CONNECTIONS

(
-

'\,

--./,/

3-2, 3-4

ACCEPT UNREGISTERED
3-2, 3-5, 4-4

CLOSE CONNECTION 3-2,
3-6

CLOSE FILE 3-2, 3-8
CLOSE SESSION 3-2, 3-10
EXIT 3-2, 3-12
HELP 3-2, 3-13
LIMIT 3-2, 3-14, 4-5
LIMIT CONNECTIONS 2-8,
3-2, 3-16

LIMIT FILES 3-2, 3-18, 4-6
LIMIT SESSIONS 3-2, 3-19,
4-5

LOG 2-20, 3-2, 3-20
REFUSE CONNECTIONS
2-2, 3-2, 3-23

(>
,,=-/

Index 6

REFUSE UNREGISTERED
3-2, 3-24

SET ALIAS 3-2, 3-25
SET LOG FILE 2-20, 3-2,
3-26, 4-4

SHOW CONNECTIONS 3-3,
3-28

SHOW FILES 3-3, 3-29
SHOW LIMITS 3-3, 3-30
SHOW LOG FILE 2-20, 3-3,
3-31

SHOW SESSIONS 3-3, 3-32
SHOW STATUS 3-3, 3-33
SHOW VERSION 3-3, 3-34
START SERVER 3-3, 3-35
STOP SERVER 2-3, 3-3,
3-36

(

summary 3-2
VAXNMS server files 1-9
VAXNMS server software
backing up 2-18
installing 1-1
VAXNMS server
accepting connections 3-4
accepting unregistered nodes
3-5

adding a application 2-6
adding a application without
PCFS Administration utility 4-10
adding a common directory
2-16

adding a common directory
without PCFS
Administration utility 4-9
adding a new printer form
4-12

adding a node 2-5
adding a node without PCFS
Administration utility 4-9
adding a personal directory
2-4

adding a printer 2-11

adding a printer without
PCFS Administration utility 4-15
adding a user 2-4
adding a user without PCFS
Administration utility 4-8
AST limit 4-5
backing up 2-18
buffer limit 4-5
changing the log file 3-26
closing connection to 3-6
closing file 3-8
closing session to 3-10
configuring 4-1
deleting a node 2-6
deleting a personal directory
2-6

directory structure 1-10
exiting 3-12
file limit 4-6
help with operator interface
3-13

input/output channels 4-6
installing an application 2-6
10 buffered limit 4-5
10 direct limit 4-6
leaving 3-12
limiting connections, files,
and sessions 3-16
limits and quotas 4-5
log file messages 5-2
log network events 3-20
maintaining the log file 2-20
maximum working set size
4-6

messages 5-1
modifying the Information
System 2-17
notes from system administrator 2-18
page size limit 4-6
PCAPP 1-6, 1-10, 1-14
PCAPP alias 2-7

Index 7

PCCOMMON 1-6, 1-10
PCFS PRINT. COM 2-14
PCFS-SPOOL directory 1-6,
I-H)
PCWAPP alias 2-7
read-only alias for a restricted
application 2-9
refusing connections to 3-23
refusing unregistered nodes
3-24

removing a application 2-10
removing a application without PCFS Administration
utility 4-19
removing a common directory
2-17

removing a common directory
without PCFS
Administration utility 4-19
removing a printer 2-15
removing a printer without
PCFS Administration utility 4-20
removing a user 2-6
removing a user without
PCFS Administration utility 4-18
restricted applications 2-8
showing connections 3-28
showing files 3-29
showing limits 3-30
showing log file 3-31
showing sessions 3-32
starting 2-2, 3-35, 4-1
status 3-33
stopping 2-2, 3-36
SYSGEN 4-6
SYSTARTUP.COM 2-14
unregistered nodes 3-5, 3-24
unrestricted applications 2-7

Index 8

version 3-34
VXAPP 1-6, 1-10
VXSYS 1-6, 1-13, 1-14, 1-15
VXUSERS 1-6, 1-10
working set limit 4-6
writeable alias for a restricted
application 2-9
VAXNMS user account
as a server alias 1-17
VAXmate system software
backing up 2-18
Version of the server
showing 3-34
VMSINSTAL 1-3
Volatile database 1-16, 3-5, 3-24
VXAPP
directory 1-6, 1-10
VXSYS
alias 1-6, 1-13, 1-14, 1-15
directory 1-6, 1-13, 1-14, 1-15
VXUSERS
directory 1-6, 1-10 1-6, 1-10
VXWSYS
alias 1-13
W

WIN .INI file 1-16
Working set limit 4-6
Workstation
adding to the server 2-4
adding to the server without
PCFS Administration utility 4-7
removing from the server 2-6
removing from the server
without PCFS
Administration utility 4-18
Writeable alias
restricted applications 2-8
unrestricted applications 2-7

VAX/VMS
Server Guide
AA-]U51A-TE

Reader's Comments

Your comments on this manual will help improve our product quality and usefulness.
Please indicate the type of reader you most closely represent.

o First-time user
o Application user

o Programmer
o Other (please specify)

o Experienced user

How would you rate this manual for:

(

Completeness of Information
Accuracy of Information
Easy to Read/Use
Usefulness of Examples
Number of Examples
Illustrations
Table of Contents
Index
Format
Binding Style
Print Quality

Excellent
0
0
0
0
0
0
0
0
0
0
0

Good
0
0
0
0
0
0
0
0
0
0
0

Fair
0
0
0
0
0
0
0
0
0
0
0

Poor
0
0
0
0
0
0
0
0
0
0
0

Did you find any errors in this manual? Please specify by page and paragraph.
Incorrect information:
Information left out:
Hard to understand:

What suggestions do you have for improving this manual? Attach a second sheet if
necessary.

(

Name
Company
Street
State/Country
Telephone

Title
Dept.
City
Postal/Zip Code
Date

Do Not Tear - Fold Here and Tape No Postage
Necessary
if Mailed in the
United States

BUSINESS REPLY MAIL
FIRST CLASS PERMIT NO_33 MAYNARD MASS_

POSTAGE WILL BE PAID BY ADDRESSEE

SOFTWARE PUBLICATIONS

200 FOREST STREET

MR01-2 L12

MARLBOROUGH, MA

01752

111"",11,11""11""1,11,1,,1,1,,1,1,,11,,,,,1,11

I
-

DoNotTear-FoldHere

- - - - - - - -I
1

I
I