3.6.4 How to set up views

• GUI Windows NT
• CLI UNIX, Windows NT

GUI Windows NT

Select [CONFIGURATION]-FILE SYSTEM VIEWS:

The dialog shows the default views configuration. Using this dialog, new views may be added and configured, and existing views may be changed, renamed, or removed.
By default, the 'Root' view is mapped to the drive letter Z: and contains two subviews 'views_pc' and 'views_rr' in the PC name format and the Rock Ridge name format, respectively. 'views_pc' is mapped to drive letter X:, and 'views_rr' is mapped to drive letter Y:.
Adding a new view:
Click on a view that has "contains views" selected. Click [NEW]. A new subview will be appended to the selected view. Now enter a name for the new view and confirm with 'RETURN'. If a view is to contain subviews contains views must be selected for this view. Otherwise click contains volumes.
Renaming a view:
Select the corresponding view and click [RENAME], or double-click the view. Enter a new name and press 'RETURN'.
Removing a view:
Please note that all subviews will be lost if a view is deleted. Select the appropriate view and click [REMOVE].
Assign a view a drive letter:
Select a view and a drive letter from the list Available as Drive. The drive letter can then be shared to the clients. If you select [none], the view will not be assigned a drive letter. Please note, that executables cannot be started from these drive letters on the server. To do this, the corresponding drive must additionally be mapped as a network drive on the server. This can be easily done with the Windows NT Explorer.
Setting up disk sets for a view:
The field visible volumes lists all disk names visible to the clients (all by default). The field excluded volumes lists all disk names, that will not be visible to the clients explicitly (none by default).
The specification can either be as meta characters in csh syntax (see "Table 4" on page 71) or explicitly by specifying a blank separated list of disk names. The [CONTENTS] dialog lists the disk names (see page 115). Please note that the name must be entered in the correct name format. As opposed to the original disk name, the disk name in one of the three name formats is always unique.
Setting up volume name space and file name filter:
Most installations use the appropriate file name filter for each volume name space. Therefore, the GUI only supports to configure both at the same time.Under "Format" you can set both the volume name space of a view and the file name filter to rr, for example. To select a different file name filter, use the CLI to edit the file server.cfg manually.
Confirming or discarding the views set-up:
Click [OK] to confirm the views set-up.
Click [CANCEL] to discard the changes.
Please note:
If you change a view name the changes will not become active unless 'RETURN' is pressed. In some cases the [OK] button can only be clicked if you click somewhere else in the view tree (e. g. Root).
The administration client saves the views configuration in the file server.cfg in the JUKEMAN directory.

CLI UNIX, Windows NT

Note: The file server.cfg must be modified for this task. A detailed description of the file can be found in "Configuration file server.cfg" on page 245. It is recommended that you make a backup copy of the file before editing it.

Open the file server.cfg with a text editor. The views are entered in the views {...} section. The first section that must be specified is list { }, containing the names of all views on top level. Following this section is the section roots { }, containing all views names and their definition. Each view that contains subviews has its own views { } section (with its own list { } and roots { } section).
Each view that is to contain disks can have the following sections:

Examples
A simple example is the file server.cfg used for new installations on Windows NT. These are the sections related to views:

fnfilters {
rr { upper_case { 0 } lower_case { 0 } no_version { 1 } rock_ridge { 1 } }
hs { upper_case { 0 } lower_case { 0 } no_version { 0 } rock_ridge { 0 } }
pc { upper_case { 1 } lower_case { 0 } no_version { 1 } rock_ridge { 0 } }
}
drive { Z }
views {
list { views_pc views_rr }
roots {
views_pc {
drive { X }
}
views_rr {
drive { Y }
format { rr }
}
}
}

The section fnfilters { } defines three file name filters. These filters are predefined in the server anyway, except for one little thing: The server internally predefines the pc filter to convert file names to lower case (upper_case { 0 } lower_case { 1 }). Thus iXOS-JUKEMAN remains compatible to earlier versions. It showed, that PC software rather expects upper case letters. This is why the new server.cfg overrides the pc filter's default settings. An old server.cfg is preserved if an existing installation is updated, so the clients still see lower case letters. The fnfilters section is missing on UNIX systems, so the internal settings of the server apply, i. e. lower case letters for the pc filter.
You may define additional file name filters with any name in the section fnfilters, or modify the properties of the existing filters. Each filter has four properties which can be switched on or off with 1 or 0 respectively:

A filter is case-sensitive, if both properties upper_case and lower_case are switched off. It will not open the file README.TXT if the user types readme.txt.
The section drive { Z } is an attribute of the root view. The whole tree of views appears under the drive letter Z:. The views { } section of the root contains the subviews views_pc and views_rr, which are listed in the list { } section. These views are defined in the roots { } section. The views appear as subdirectories views_pc and views_rr under drive letter Z:. The view views_pc also appears as drive X:, presenting all disks using the pc volume name space and file name filter. views_rr also appears as drive Y:, containing all disks using the rr volume name space and file name filter. Thus Z:\views_pc and Z:\views_rr contain the same disks as X: and Y:, respectively.
Suppose you wanted to export the following disk set: A view views_pc, containing all disks for PC clients in the pc format, a view views_rr, containing all disks for UNIX clients in the rr format, and a view find_easier, containing two subviews. One subview should contain all the disks starting with the letters a, b, c, ..., m in pc format and leave out all disks starting with archive. The other subview should contain all disks starting with the letters n-z:
drive { Z }
views {
list { views_pc views_rr find_easier }
roots {
views_pc { format { pc } discs { * } drive { X } }
views_rr { format { rr } discs { * } drive { Y } }
find_easier {
views {
list { a_m n_z }
roots {
a_m { format { pc } discs { [a-m]* } deny { archive*} }
n_z { format { pc } discs { [n_z]* } }
}
}
}
}
}

Please make sure that the number of opening brackets "{" matches the number of closing "}" brackets.
Save the file server.cfg when the set-up of the views is finished. On UNIX systems a directory must be created and shared for each view. How to do this is explained in the following section.