Previous PageNext Page

Chapter 6 - Managing the VINES Files Volume

Introduction to Managing the VINES Files Volume

VINES Files on Drive Z

Figure 6-1. Directory Structure of VINES Files

Determining Your Location Version

Drive E: => PublicRelations@Mkt@WCTUS
Drive F: => AcctRecd@Fin@WCTUS
Drive Z: => VINES Files /ROOT:DOS\USA

Figure 6-2. Example of NEWREV /L Screen

Z:\ Directory

LOGOUT
MANAGE
MGROUP
MLIST
MNICK
MORG
MSERVICE
MUSER
OPERATE
SEND
SETARL
SETATTR
SETDRIVE
SETNETB
SETPRINT
WHATZ
WHOAMI

PCINIT Subdirectory

BAN command
LAN drivers
LAN diagnostics
DOS redirectors
LOGIN command
NEWREV command
PCCONFIG command

HLPFILES Subdirectory

MESSAGES Subdirectory

SYSERROR and LOGFILES Directories

To View Files in LOGFILES and SYSERROR Directories

1. Enter SETDRIVE with any letter other than Z and the name of the VINES file volume. For example, enter:

setdrive x "vines files@server1@servers"

2. At the system prompt, type 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.

User's View of VINES Files

Setting Drive Z

Access Rights to VINES Files

Modifying VINES Files

Some VINES programs execute other VINES programs using the DOS PATH command. Therefore, if you move a VINES program, you must move any programs associated with it. See "Moving Grouped Programs" for a list of effected programs.
Do not rename the \PCINIT directory, or the \HLPFILES or \MESSAGES subdirectories. If you rename these subdirectories, VINES Files do not work correctly.
Do not move help or message files from the \HLPFILES, \MESSAGES, \PCINIT\HLPFILES, or \PCINIT\MESSAGES subdirectories. These files correspond to executable files in the Z:\ directory and the \PCINIT subdirectories and must stay where they are installed.
Do not move the INTLDATA.BIN files in the \MESSAGES and \PCINIT\MESSAGES subdirectories.
Leave the NEWREV and XREV files in the Z:\PCINIT directory.
Do not change the names of programs in the VINES Files file volume. If you want users to execute a VINES command under another name, create a batch file that refers to the VINES program file. (For example, a batch file named MENU.BAT could invoke MUSER.COM.)
If you create new directories and move VINES programs to them, change the PATH command entries in user profiles so that users can execute these commands.
Keep a record of any VINES program files that you have moved or modified. You need this information when you back up and restore VINES Files.

Moving Grouped Programs

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
VINES.COM and XVINES.EXE

Example Moving VINES Files

Create a new subdirectory named ADMIN in Z:\
Put SETDRIVE and SETARL in that directory
Deny non-administrators access to the ADMIN directory

1. Warn users that you are modifying VINES Files.

2. Change the ARL protecting VINES Files to give you complete access if you do not already have it (Control, Search, Read, Write, and Delete).

3. Use the DOS MKDIR command to create the ADMIN directory.

4. Copy all the executable files for the SETARL and SETDRIVE programs to the ADMIN subdirectory and delete them from Z:\.

5. Set the ARL on Z:\ADMIN as follows:

- You are the Owner with complete access (Control, Search, Read, Write, and Delete).

- Group and World (*@*@*) have no access.

6. Change the PATH command in your user profile and the profiles of other administrators so that the new ADMIN subdirectory is searched when the SETARL and SETDRIVE commands are executed.

Figure 6-3. Example of Modified VINES Files

New or Modified Programs on Drive Z

Unable to verify consistency of VINES Files!

PCINIT subdirectory NOT FOUND.

Example Log Consistency Report

Figure 6-4. Example of VINES Files Consistency Report

Previous PageTop Of PageNext Page