HP NonStop G-Series - Manual (Page 33)

Installing and Configuring the Nomadic Disk
Manager
ServerNet Nomadic Disk User’s Guide—425485-001
3 -5
Configuring the Nomadic Disk Manager
Configuring the Nomadic Disk Manager
Each of the two nodes involved in a ServerNet Nomadic Disk implementation has its
own configuration. Furthermore, certain management duties must be performed when
the Nomadic volumes are not owned.
Nomadic Disk Configuration File
A Nomadic Disk configuration file is interpreted each time you start the Nomadic Disk
Manager. The Manager operates on the objects defined in that file. You must update this
EDIT file whenever the physical environment of the Nomadic Disk subsystem changes.
Updates to this file are automatically included whenever you start the Nomadic Disk
Manager.
•
Each configuration statement occupies a single line in the file.
•
No line can have more than one statement.
•
If the first nonblank character in a line is an exclamation point (!), the entire line is
treated as a comment; there are no embedded comments.
•
All syntactical items within a statement must appear in the exact order shown,
though the exact character position in a line is not important.
•
The order of statements is not important, except:
°
An ADD statement depends on preceding SET statements.
°
An ADD statement implicitly resets all preceding SET statements.
CONFIG^FILE
CONFIG^FILE is a TACL variable containing the name of a Nomadic Disk
configuration file:
•
If the variable CONFIG^FILE exists when you start the Manager and it is not blank,
the Manager assumes the variable contains a file name and attempts to open and
interpret that file.
•
If the variable CONFIG^FILE does not exist or if it is blank, then the default
configuration file is used. The default configuration file is
$SYSTEM.NOMADIC.NDCONFIG; however, this file name can be changed.
To change the default CONFIG^FILE, refer to Example 3-1, Sample TACLCSTM File
Included With the Nomadic Disk Manager, on page 3-4 .