Chapter 5 - Managing VINES Files
Overview of Managing the VINES Files Service
This chapter explains how to manage the VINES Files service. The VINES Files service is a special file service containing client software for Banyan workstations.
This file service is called VINES Files@servername@Servers, where servername is the name of the Banyan server where the service resides. When a user logs in to the network, drive Z of their workstation is automatically set to a VINES Files service containing software that corresponds to the client revision of the workstation.
VINES Files administration is open to members of the AdminList@servername@Servers, where servername is the name of your server. VINES Files administrators can perform the following operations on the VINES Files file service:
![]()
Control and change access ![]()
Add files ![]()
Delete files ![]()
Create new subdirectories ![]()
Move files Caution: Avoid modifying VINES Files if possible. Modifying the system and network files in this file service makes it more difficult to manage and upgrade your server. Follow the rules and precautions in this chapter when modifying VINES Files, and maintain a written record of any changes you make. You will need this information to properly back up and restore VINES Files.
You can upgrade files in the VINES Files service by applying a VINES Files patch to a VINES server on your network and then copying the appropriate files to the StreetTalk for Windows NT server.
The VINES Files service on a StreetTalk for Windows NT server is identical to the VINES Files service on other Banyan servers.
Banyan client program files are stored in a directory tree in the VINES Files service. Every Banyan workstation automatically maps drive Z to VINES Files. These program files are located in the root directory of the VINES Files service, and in the \PCINIT subdirectory. Corresponding help and message files are in the HLPFILES and MESSAGES subdirectories respectively. Figure 5-1 illustrates this directory structure.
In Figure 5-1, the three subdirectories, \DOS, \OS2, and WIN32, each contain versions of the Banyan client files to support different workstation operating systems. VINES Files supports the DOS, OS/2, Windows, Windows 95/98, and Windows NT operating environments (Table 5-1).
VINES Files Subdirectory Supported Workstations DOS DOS, Windows 3.x, Windows 95/98, Windows NT OS2 OS/2 WIN32 Windows 95/98, Windows NT
The Windows Dynamic Link Libraries (for example, VNSAPI.DLL) are in the DOS directory.
Location refers to the language version of the Banyan client software. USA (English) is the default location although other locations (for example, France) may also exist on your server. If you installed versions of VINES Files that support non-English clients, the directory structure for each of these versions corresponds to the structure of the USA directory.
Refer to "Determining the VINES Files Version of a Client or Server," which follows, for information about how to determine the current version of VINES Files on a client or server.
Determining the VINES Files Version of a Client or Server
From a client, you can verify the VINES Files locations available on a StreetTalk for Windows NT server, and the VINES Files version running on the client.
Determining the VINES Files Version on a Server
Verifying the VINES Files versions available on a server can provide two types of information:
![]()
The VINES Files version available on a specific server ![]()
The VINES Files versions to which your client has access
You obtain this information from two different programs, as follows.
To Determine the VINES Files Versions Available on a Specific Server
From the command prompt, enter:
SHOWREVS servername
where servername is the name of the server for which you want to obtain information. The following information for the VINES Files on the selected server appears:
![]()
Client versions (DOS, OS/2, or WIN32) ![]()
Language location for each client version (USA, France, Spain, and so forth) ![]()
Revision levels for each language location
Refer to your the Command Reference for more information about using SHOWREVS.
To Determine the VINES Files Versions to Which Your Client Has Access
From the command prompt of a DOS client, enter:
NEWREV /L
A list appears, containing the name, VINES Files version, and VINES Files revision level of the currently available servers.
You may obtain different results each time you enter the command. Network traffic can prevent servers from responding.
Determining the VINES Files Version on a Client
The following tools exist for determining the version of VINES Files to which your client is currently mapped: the WHATZ command or the SETDRIVE /L command.
To Determine the VINES Files Service Currently Mapped to Drive Z
From the command prompt, enter:
SETDRIVE /L
A list of the drives currently mapped to Banyan file services appears. The listing for drive Z indicates the workstation's VINES Files version and language location as follows:
Drive Z: => VINES Files /ROOT:DOS\USA
Executables in the Root Directory
The root directory for each VINES Files language location includes executable files for the following frequently used programs:
LOGOUT | MANAGE |
MGROUP | MLIST |
MNICK | MORG |
MSERVICE | MUSER |
OPERATE | SEND |
SETARL | SETATTR |
SETDRIVE | SETNETB |
SETPRINT | WHATZ |
WHOAMI |
The OPERATE program is not supported for use with StreetTalk for Windows NT servers.
For clients using the DOS version of VINES Files, the PCINIT subdirectory includes executable files for the following:
BAN command | LAN drivers |
LAN diagnostics | DOS redirectors |
LOGIN command | NEWREV command |
PCCONFIG command |
For clients using the WIN32 version of VINES Files, the equivalent of most of these files exist in the directory PCINIT\WINDOWS.
The HLPFILES directories contain .HLP files. Users press the F1 key while in a program to display these help messages.
There are two HLPFILES directories. The help files in the Z:\HLPFILES and the Z:\PCINIT\HLPFILES (or PCINIT\WINDOWS\HLPFILES ) are associated with the VINES program files in the Z:\ and Z:\PCINIT subdirectories, respectively.
Programs that you run from drive Z, such as SETDRIVE, generate client messages. The MESSAGES subdirectories contain .MSB files, which contain the client program messages.
There are two MESSAGES directories. The .MSB files in the Z:\MESSAGES and Z:\PCINIT\MESSAGES directories are associated with VINES program files in the Z:\ and Z:\PCINIT subdirectories, respectively.
Each MESSAGES directory also contains an INTLDATA.BIN file. VINES programs use these files to alphabetize, collate, and sort data that is dependent on your location (language) version.
SYSERROR and LOGFILES Directories
The SYSERROR directory, located in the root of drive Z, contains .ERR files and .HLP files.
The .ERR files are error messages that services, such as StreetTalk and print services, generate. Use the VNSERR command to display these messages. Refer to your the Command Reference for a description of the VNSERR command. The .HLP files contain help messages for the service error messages.
To view the SYSERROR and LOGFILES directories, from a DOS, Windows, or OS/2 workstation, map a drive other than drive Z to the VINES Files service as follows.
To View Files in LOGFILES and SYSERROR Directories
1. Enter SETDRIVE with any letter other than Z and the name of the file service. For example, enter:
setdrive x " files@server1@servers"
2. At the command prompt, enter the drive designator. For example, enter:
X:
3. Enter CD directory-name to move to the directory you want to view. For example, enter:
CD LOGFILES
or
CD SYSERROR
4. Enter DIR to list the contents of the directory.
DOS User's View of VINES Files
Drive Z of a DOS client is mapped to different directories depending on whether a user is logged in. As a result, a user who is logged in at a DOS client has a different view of VINES Files, and access to different directories and files.
View of VINES Files When Not Logged In
By default, when a user is not logged in to the Banyan network, drive Z is mapped to the \PCINIT subdirectory for their language version and client type. For example, for an English-speaking user at a DOS workstation, the root of drive Z is mapped to the \DOS\USA\PCINIT subdirectory of VINES Files. They have Read access to all files in the /PCINIT subdirectory and the /HLPFILES and /MESSAGES subdirectories below it.
View of VINES Files When Logged In
By default, when a user is logged in to the Banyan network, drive Z is mapped to the root directory for the user's language version and client type. For example, for an English-speaking user at a DOS workstation, the root of drive Z is mapped to the \DOS\USA subdirectory of VINES Files. Users who are logged in at a DOS client have the following access to objects in VINES Files:
![]()
In the Z:\ directory - Execute and Read access to system and network files ![]()
In the subdirectories /PCINIT, /MESSAGES, /HLPFILES - Search and Read access ![]()
For files in these subdirectories - Execute and Read access
When a user attempts to log in to the Banyan network, the security service verifies that the user is entitled to the VINES Files access rights granted to all users (the World field in the ARL for VINES Files). The World entry in the ARL must allow Search and Read access to the \PCINIT directory and its subdirectories, and Execute and Read access to all files in these subdirectories.
The drive designation Z:\ is placed automatically in the search path for all DOS users.
You can set drive Z to network file services other than VINES Files. However, the file service that you designate must contain the directories \PCINIT and \HLPFILES, their contents, and the program LOGOUT.EXE in its root directory.
Note: If you map drive Z to a file service other than VINES Files, do not upgrade the software revision on your workstation unless you upgrade the contents of that file service at the same time.
The default ARL for the VINES Files service allows users search and read access to the directory. This prevents users from modifying the service. You can change the default ARL to any ARL that you want.
If you make the ARL less restrictive (by assigning Control, Write, or Delete access rights), users can add files to and delete files from these directories. If you make access more restrictive (Search only or no access at all), users cannot execute commands. It is recommended that you keep the default access rights to the directories that contain VINES Files.
Refer to Chapter 4 for information on ARLs and how to set them.
Caution: If required, you can modify user access rights to VINES Files. However, do not remove the Search and Read access rights to VINES Files. Users may lose access to the network if you remove Search and Read access to VINES Files.
You can create subdirectories and move files between directories in VINES Files. If you modify VINES Files and later want to return to the default structure, you can restore VINES Files from release media.
You can modify VINES Files locally at the Windows NT Server, or remotely from a Banyan client. To modify VINES Files remotely, the VINES Files service must be running. Modifying VINES Files may disrupt users who are in the process of executing client programs you are modifying.
Caution: Carefully plan any changes to VINES Files. Moving or deleting files from VINES Files can prevent software from operating properly.
Before modifying VINES Files:
![]()
Warn users that you are modifying VINES Files. ![]()
Change the ARL protecting VINES Files to give you complete access if you do not already have it (Control, Search, Read, Write, and Delete). ![]()
Verify whether a file being moved needs to be moved in conjunction with other related programs. Refer to "Moving Linked Programs" for a list of linked programs.
In addition, the following rules apply when modifying VINES Files
![]()
Do not rename the \PCINIT directory, or the \HLPFILES or \MESSAGES subdirectories. VINES Files do not work correctly if you rename these subdirectories. ![]()
Do not move help or message files from the \HLPFILES, \MESSAGES, \PCINIT\HLPFILES, or \PCINIT\MESSAGES subdirectories. VINES Files executables require that these files remain in their installed locations. ![]()
Do not move the INTLDATA.BIN files in the \MESSAGES and \PCINIT\MESSAGES subdirectories. ![]()
Do not move the NEWREV and XREV files in the \PCINIT directory. ![]()
Do not change the names of VINES Files programs. If you want users to execute a command under another name, create a batch file that refers to the program file. (For example, a batch file named MENU.BAT could invoke MUSER.COM.) ![]()
If you create new directories and move programs to them, change the PATH command entries in user profiles so that users can execute these commands. ![]()
Keep a record of any program files that you have moved or modified. You need this information when you back up and restore VINES Files.
The following programs work together and must be moved in groups:
![]()
ASYNCH.COM, XASYNCH.EXE, TASYNCH.EXE, and RASYNCH.EXE ![]()
GA3270.COM, I3270.COM, KB3270.EXE, R3270.COM, and T3270.COM ![]()
HOSTS.COM and XBCOMM.EXE ![]()
LOGGEN.COM, XLOGGEN.EXE, OLOGGEN.COM, and OXLOGGEN.EXE ![]()
MAIL.EXE, XMAIL.EXE, XMLOGO.EXE, and ADDRBOOK.EXE ![]()
MANAGE.COM and XMAN.EXE ![]()
MGROUP.COM and XMGROUP.EXE ![]()
MORG.COM and XMORG.EXE ![]()
MSERVICE.COM, ADDSVC.COM, ADDSNA.EXE, XMSERVIC.EXE, and XADDSVC.EXE ![]()
MUSER.COM, XMUSER.EXE, and XMUSEC.EXE ![]()
OPERATE.COM and XOPR.EXE ![]()
REPORT.COM, XREPORT.EXE, and XREPVA.EXE, XREPST.EXE ![]()
SETDRIVE.COM, XSDARG.EXE, and XSDFORM.EXE ![]()
.COM and X.EXE
Restricting Access to Client Programs
If you want to restrict access to certain client programs in the VINES Files directory, you can place the restricted programs in a new directory and set the access rights for that directory. You can modify the directory structure from a client workstation, or from the Windows NT Server.
For example, you can prevent non-administrators from using the programs for changing drive settings (SETDRIVE) and access permissions (SETARL) as follows:
1. In the VINES Files subdirectory for the appropriate client and language version, create a new subdirectory named \ADMIN.
2. Copy all the executable files for the SETARL and SETDRIVE programs to the \ADMIN subdirectory and delete them from the source directory.
Note: Help files and message files used by SETDRIVE and SETARL must remain in the \HLPFILES and \MESSAGES directories. Do not move them to the \ADMIN directory.
4. Deny access to non-administrators by setting the ARL on the \ADMIN directory as follows:
- Enter your StreetTalk name in place of the default Owner entry and give this entry all access rights (Control, Search, Read, Write, and Delete).
- Give the Group and World entries no access.
Refer to Chapter 4 for information about how to set access rights.
5. Change the PATH command in your user profile and the profiles of other administrators so that the new ADMIN subdirectory is searched when executing SETARL and SETDRIVE.
Identifying Changes to VINES Files
A StreetTalk for Windows NT server does not automatically log changes to the contents of the VINES Files service. However, you can identify modifications to VINES Files, by running a VINES Files consistency check.
A consistency check generates a log file that provides information about each of the VINES Files client versions and language locations installed on the server. The consistency check log identifies those files in each of the VINES Files subdirectories that have been modified or moved, or are missing.
If a file has been changed, the log reports the path and name of the file. If you change the name of a file or move the file to another directory, the log reports that the file is missing.
Generating a VINES Files Consistency Report
If you installed VINES Files on your StreetTalk for Windows NT server, you can check the VINES Files directory on the server to determine whether files have been modified or removed.
A VINES Files Consistency Report provides information only; it does not automatically add or remove files to ensure consistency.
To Generate a VINES Files Consistency Report
1. From the command prompt of your StreetTalk for Windows NT server, make the directory containing your StreetTalk File software the active directory. For example, if you installed your StreetTalk File software to the default location, enter:
cd c:\Program Files\Banyan\File
2. Enter:
ck_data
A log file is generated and the following messages appear for each client version and language location installed:
Running data consistency check on Vfiles.
This may take a while. Please be patient.Checking DOS files for USA location
Checking OS\2 files for USA location
Checking WIN32 files for USA locationPlease review the file cklog for any errors
3. Use a text editor to view the cklog file. If you installed your StreetTalk software to the default location, the path to this file is as follows:
C:\Program Files\Banyan\File\cklog