Previous PageNext Page

Chapter 7 - VINES System Software and Special Applications


Utility services
Special services
Resource-sharing services
Optional services

Utility Services

Server Service

Network Time

VINES Security Service


Directory Structure of VINES Files

Figure 7-1. VINES Files Directory Structure

Figure 7-2. Directory Structure of the USA Location

Directories and Subdirectories on Drive Z

Login Process


User's View

Modifying Access Rights to Drive Z

Customizing Drive Z

Guidelines for Modifying VINES Files

Do not remove default access rights from drive Z.
Do not delete any files from drive Z. Deleting files can prevent VINES from operating properly.
To prevent users from executing some VINES programs, you can move VINES executable files to a subdirectory on drive Z. Then use the SETDRIVE command with the /ROOT switch to keep them out of Z:\. Identify the subdirectory in their profiles with the PATH command. You can also run StreetTalk Explorer or the MUSER program to stop users from editing their own profiles.
You can create subdirectories and move files between directories in VINES Files. However, some VINES programs execute other VINES programs using the PATH command. Therefore, if you move a VINES program, you must move any programs associated with it. Managing VINES Services has a list of these programs.
Some files must not be moved. For example, do not move help or message files from HLPFILES or MESSAGES subdirectories.
Do not rename the PCINIT directory, or the HLPFILES, or MESSAGES subdirectories. If you rename these subdirectories, VINES Files does not work correctly and users may not be able to log in.
Do not change the names of programs in the VINES Files 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.
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.
Do not add any non-commercial software to VINES Files or any other file service unless you have tested the software on a stand-alone (non-networked) workstation. Develop guidelines for adding non-commercial software and distribute those guideline to all administrators and users.

Special Services

Netbios service

Netbios Services

Figure 7-3. VINES Name Registration Service


Resource Sharing Services

AppleTalk Filing Protocol (AFP) Service
File services
Print services

Note: StreetTalk for Windows NT does not support the AFP Service.

AppleTalk Filing Protocol (AFP) Service

File Services

Print Services

Naming and Assigning Services

Performance Considerations

Figure 7-4. Service and Group on One Server

Figure 7-5. Service and Group on Two Servers

Worksheet for Service Planning

Figure 7-6. Service Planning Worksheet


Macintosh Naming Rules

Administrator's Check List

Decide what access users will have to drive Z, the volume that stores VINES Files.
In a multilingual environment, make sure that all necessary locations are available to users.
If you intend to modify VINES Files, begin to plan those modifications.
Think about where you will put special services, especially file and print services, that you will require.
Stop the AFP service on a native VINES server if your network does not have any Macintosh computers. Monitor its memory usage if you must run it.
Read Chapter 11, which describes other optional services (for example, Asynchronous Terminal Emulation and 3270/SNA) you might require.

Key Terms

Further Reading

Previous PageTop Of PageNext Page