| Previous | Contents | Index |
When ODS-5 disk volumes are used for client file access, you manage them the same way you manage shares on ODS-2 disk volumes. In addition, you can:
The following sections describe the procedures for managing ODS-5 disk
volumes.
4.4.3.1 Displaying Shares and Files on ODS-5 Disk Volumes
You can display information about a share, including the disk device on which the share is stored, using the SHOW SHARES command with the /FULL qualifier. For example, to display information about the share STATES, enter the following command:
LANDOFOZ\\TINMAN> SHOW SHARES STATES/FULL
Shared resources on server "TINMAN":
Name Type Description
------------ --------- -----------------------------------------
STATES Directory
Path: AABOUT$MDA1::[STATES]
Connections: Current: 1, Maximum: No limit
RMS file format: Stream
Directory Permissions: System: RWED, Owner: RWED, Group: RWED, World: RE
File Permissions: System: RWD, Owner: RWD, Group: RWD, World: R
Share Permissions:
Everyone Full Control
Total of 1 share
|
You can display the files in a share on the ODS-5 disk volume using the ADMINISTER command SHOW FILES. To display the contents of subdirectories as well, include the /SUBDIRECTORIES qualifier. For example, if the share STATES is on an ODS-5 disk volume, display the files in the directory [STATES.KANSAS], as well as all files in all subdirectories by entering the following command:
LANDOFOZ\\TINMAN> SHOW FILES STATES\KANSAS\* /SUBDIRECTORIES
Files in: \\TINMAN\STATES\KANSAS
FILE1.DAT
Permissions:
Administrators Full (All)
Everyone Change (RWXD)
Server Operators Change (RWXD)
SYSTEM Full (All)
Audit Events: (None specified)
Owner: Scarecrow
FILE2.DAT
Permissions:
Administrators Full (All)
Everyone Change (RWXD)
Server Operators Change (RWXD)
SYSTEM Full (All)
Audit Events: Success Failure
Everyone RW---- RWXDPO
Owner: Scarecrow
Total of 2 files
|
This example displays auditing, permissions, and owner information
about all files in the shared directory KANSAS in the share STATES,
including subdirectories.
4.4.3.2 Converting File Names
After a disk volume has been converted to ODS-5, it may contain file names with ODS-2 escape-encoded characters. These file names should be converted to the ODS-5 nonencoded character set, using the PWCONVERT utility, as described in Advanced Server for OpenVMS Server Installation and Configuration Guide.
A client computer that supports UNICODE can create files with characters in the file name that are not part of the ISO Latin-1 character set. However, these file names cannot be used to store files on the Advanced Server. In this case, the client attempting to save the file receives the following error message:
Cannot copy xxnnn: No mapping for the Unicode character exists in the target multi-byte code page. |
The UNICODE character that is not supported is specified by its
character code xxnnn.
4.4.3.3 Displaying the Disk Volume Type
To determine whether a specific disk volume is an ODS-5 disk volume, use the OpenVMS command SHOW DEVICE/FULL command, as follows:
$ SHOW DEVICE MDA1:/FULL
Disk AABOUT$MDA1:, device type RAM Disk, is online, allocated, deallocate
on dismount, mounted, file-oriented device, shareable.
Error count 0 Operations completed 155
.
.
.
Volume Status: ODS-5, subject to mount verification, file high-water
marking, write-back caching enabled.
$
|
The summary display line shows the type of disk volume (in this case,
ODS-5).
4.4.3.4 Specifying File Names in ADMINISTER Commands
When you specify a file name as part of an ADMINISTER command line, you can enter the file name as it appears on the client computer. Be sure to enclose the file name in quotation marks if it contains a space or nonalphanumeric character. For example, to change the file permissions of a file named My File.Txt in the share LIONTAIL, use the following ADMINISTER command:
LANDOFOZ\TINMAN>SET FILE \LIONTAIL\"My File.Txt" SCARECROW\PERMISSIONS=READ |
When you specify this file in a DCL command line, you must specify the file name with character codes. To display the encoded file name, enter the DCL command DIRECTORY. For example, to display the file name My File.Txt in the LIONTAIL share, enter the following OpenVMS command:
$ DIRECTORY MDA:[LIONTAIL] Directory AABOUT$MDA:[LIONTAIL] My^__File.Txt Total of 1 file. |
To display the contents of My File.Txt, enter the following OpenVMS command:
$ TYPE MY^__FILE.TXT |
When clients store files on ODS-5 disk volumes, the length and characters included in the file name depend on the limitations of the software that created the file. For example, on MS-DOS clients, file names are limited to the "8.3" convention: file names can be no longer than eight characters, there must be one period to separate the file name from the file extension, and the file extension can be up to three characters. Therefore, MS-DOS clients do not take advantage of the full capabilities of the ODS-5 disk volume. However, the ODS-5 disk volume supports these types of files.
Windows 95 and Windows 98 clients can write longer file names, which may contain more than one period, and have file extensions of any length within the file name length limit. Therefore, Windows 95 and Windows 98 clients take advantage of the features of ODS-5 disk volumes. These features are not available on ODS-2 disk volumes, which truncate and encode file names as necessary.
The following sections describe each type of supported client computer
and the file naming conventions for each.
4.4.3.5.1 MS-DOS and Windows File Naming
If you are using the Advanced Server in an environment where long file names are not always supported, users must continue using MS-DOS file naming conventions. For example, if your clients are running Windows 3.11, or older Windows applications that only recognize the 8.3 file format, file names must follow the 8.3 file-naming convention; if your clients are running Windows 95 or Windows 98, they can use long file names.
File and directory resources shared from an ODS-2 disk volume are limited to the file-naming conventions listed in Table 4-10, MS-DOS File-Naming Conventions.
| MS-DOS File Naming Convention | Supported on ODS-2 | Supported on ODS-5 |
|---|---|---|
| The name of a file or directory can have two parts: a name and an optional extension. The two parts are separated by a period. | Yes | Yes |
| The name can contain up to eight characters, and the extension can contain up to three characters (8.3 convention). | Yes | Yes |
|
The name must start with either a letter or number. It can contain any
upper or lowercase alphanumeric characters except for the following:
? " / \ < > * | : [ ] ; = , + The name cannot contain any spaces. |
Yes | Yes |
|
The following names are reserved and cannot be used for files or
directories:
AUX, COM1, COM2, COM3, COM4, CON, LPT1, LPT2, LPT3, NUL, PRN |
Yes | Yes |
| Character set defined by code page setting 1 | Yes | Yes |
From a Windows NT system, file names follow the conventions listed in Table 4-11, Windows NT File-Naming Conventions.
| Convention | Supported on ODS-2 | Supported on ODS-5 |
|---|---|---|
| The name of a file or directory can have two parts: a name and an optional extension. The two parts are separated by a period. | Yes | Yes |
| The name can contain up to 255 characters, and the extension can contain any number of characters within the 255 character limit. | No | No |
| Names preserve uppercase and lowercase characters, but are not case sensitive. | No | Yes |
|
The name must start with either a letter or number. It can contain any
uppercase or lowercase alphanumeric characters except for the following:
? " / \ < > * | : The name cannot contain any spaces. |
Yes | Yes |
|
The following names are reserved and cannot be used for files or
directories:
AUX, COM1, COM2, COM3, COM4, CON, LPT1, LPT2, LPT3, NUL, PRN |
Yes | Yes |
| Directory levels up to 255 deep. | No | Yes |
| Supports UNICODE character set. | No | Yes 1 |
From a Windows 95 or Windows 98 system, file names follow the conventions listed in Table 4-12, Windows 95 and Windows 98 File-Naming Conventions.
| Convention | Supported on ODS-2 | Supported on ODS-5 |
|---|---|---|
| The name of a file or directory can have two parts: a name and an optional extension. The two parts are separated by a period. | Yes | Yes |
| The name and extension can contain a total of up to 255 characters. | No | No |
|
The name must start with either a letter or number. It can contain any
alphanumeric characters except for the following:
? " / \ < > * | : The name can contain spaces. |
Yes | Yes |
| File names preserve upper and lowercase characters but are not case sensitive. | No | Yes |
|
The following names are reserved and cannot be used for files or
directories:
AUX, COM1, COM2, COM3, COM4, CON, LPT1, LPT2, LPT3, NUL, PRN |
Yes | Yes |
| Directory levels up to 255 deep. | No | Yes |
| Supports UNICODE character set. | No | Yes 1 |
Advanced Server software lets you share printers connected to the network. You can create an Advanced Server print share for any OpenVMS print queue and assign access permissions to that share. Users can then send print jobs to the queue specified by the share as though they were using a local printer.
The procedures you use to manage shared printers are:
The Advanced Server makes printers available to network users through shared print queues. A print queue stores print jobs as users submit them. When a printer associated with the queue becomes available, Advanced Server routes a job to that printer.
To share a printer, you create an Advanced Server print share and assign the share name to a queue that points to the printer. Because Advanced Server is based on the OpenVMS operating system, the print queues and the printers that you share can be OpenVMS print queues and printers.
This chapter describes how to share printers that are physically
connected to a server system. You can also share local printers
connected to client workstations.
5.0.1 OpenVMS Print Queues
See the OpenVMS OpenVMS System Manager's Manual for information about setting up print queues on OpenVMS systems.
OpenVMS systems use execution queues and generic queues to provide access to printers as follows:
The Advanced Server allows you to create print queues using the ADD PRINT
QUEUE command, as described later in this guide.
5.0.2 Types of Advanced Server Print Queues
An Advanced Server print queue can be either of the following:
To support the printing needs of your users, plan print queues and
print shares to meet their requirements. You can set up printers as
shared devices, and you can establish constraints on print queues.
5.1.1 Sharing Printers and Print Queues
The way you make printers available to Advanced Server users depends on your server installation and whether you want to share existing print queues or create new ones.
Advanced Server users access the print queue by specifying a print share.
To make a print share operational, a print queue much be established first. To establish both a print queue and a print share, first set up the print queue, then set up the print share.
You create a print share so that users can send print requests to the print share rather than to individual print queues. For Windows NT, Windows 95, and Windows 98, the share name and the queue name must be the same; for other clients, like Windows 3.11, the share and queue names can be different. Multiple print shares can point to the same print queue.
The Advanced Server print queue name is limited to no more than 12 characters. If the OpenVMS print queue name has more than 12 characters, you can define an OpenVMS logical name for the print queue, to translate the queue name. You might use a logical name that is the same as the share name.
For example, the following OpenVMS command defines a logical name GLENDA for the OpenVMS print queue GLENDASPRINTER:
$ DEFINE/SYSTEM GLENDA GLENDASPRINTER |
Then you can use the logical name to specify the print queue when you
create a print share for it.
5.2 Setting Up a New Printer
The information in this section applies only to printers supported by the OpenVMS operating system. If you start with no OpenVMS queue and create an Advanced Server queue, Advanced Server creates the OpenVMS print queue.
To set up a new printer to make it available to Advanced Server clients:
To share a PostScript printer, you must use DECprint Supervisor for OpenVMS software to create the queue, then create an Advanced Server print share for the queue.
Printers supported by Advanced Server software include:
To display the printers that are supported, enter the following command:
LANDOFOZ\\TINMAN>HELP ADD PRINT QUEUE /TYPE |
When you connect your printer, make a note of the printer type and the name of the physical device or port to which it is connected.
The list of physical device connectors includes:
For example, the type of printer may be a DL3200 (a DEClaser 3200), and
the physical device or port to which it is connected may be an LTA201.
5.2.3 Creating an Advanced Server Print Queue
You can create a printer queue, and, optionally, a routing queue that points to one or more printer queues. This is useful if you need to set different print queue characteristics for a printer. You can also set up an Advanced Server print queue to point to multiple printers. When a job reaches the start of the queue, the queue sends it to the first available printer.
To create print queues, you must be logged on to a user account that is a member of one of the following groups:
Use the ADD PRINT QUEUE command. Use the SET PRINT QUEUE command to change the characteristics of an existing queue.
For each Advanced Server print queue, you must specify whether it is a printer queue or a routing queue. For a printer queue, you can specify the printer device type and the port to which the printer is connected to the OpenVMS system. For a routing queue, you can specify one or more printer queues to which the print jobs in the routing queue will be sent.
For example, the following command creates a printer queue called GLENDA1 for the DEClaser 3200 printer that is connected to LTA201:
LANDOFOZ\\TINMAN> ADD PRINT QUEUE GLENDA1 /PRINTER - _LANDOFOZ\\TINMAN> /DEVICE=LTA201/TYPE=DL3200 %PWRK-S-QUEADD, queue "GLENDA" added on server "TINMAN" |
The following command sets up or establishes the routing queue called GLENDA. Print jobs sent to GLENDA go to either of the two printer queues, GLENDA1 or GLENDA2. The description of the routing queue is "Glenda's routing queue."
LANDOFOZ\\TINMAN> ADD PRINT QUEUE GLENDA /ROUTETO=(GLENDA1,GLENDA2) - _LANDOFOZ\\TINMAN> /DESCRIPTION="GLENDA's routing queue" %PWRK-S-QUEADD, queue "GLENDA" added on server "TINMAN" LANDOFOZ\\TINMAN> |
This section provides information about displaying, modifying, and managing print queues. To manage print queues, you must be logged on to a user account that is a member of one of the following groups:
There are no special requirements for displaying print queue
information.
5.3.1 Displaying Print Queue Information
You can display a list of the server's print queues, information about a specific queue, or information about the print jobs in each queue. To display information about the print queues on a server, use one of the following procedures.
To display information about all print queues on a server:
Use the SHOW PRINT QUEUES command. For example:
LANDOFOZ\\TINMAN> SHOW PRINT QUEUES
Name Jobs Status Printer/Routing Description
---------------- ------ ------ --------------- --------------
User_PRNT 2 destination LRA0:GENERIC
paused
GLENDA 0 PAUSED
LANDOFOZ\\TINMAN>
|
The Advanced Server displays the queue name and status of each queue.
To display information about a single print queue:
Use the SHOW PRINT QUEUE command. For example:
LANDOFOZ\\TINMAN> SHOW PRINT QUEUE TOTO Name Jobs Status Printer/Routing Description ----------- ---- ------------ --------------- ---------------- TOTO 1 printing LRA0:GENERIC LANDOFOZ\\TINMAN> |
The Advanced Server displays the queue name and status of the queue and the number of print jobs currently in the queue.
| Previous | Next | Contents | Index |