HP NonStop G-Series - Manual (Page 38)

Installing and Configuring the Nomadic Disk
Manager
ServerNet Nomadic Disk (Release 2) User’s Guide — 523968-001
3 -4
Configuring the Nomadic Disk Manager
Example 3-1. Sample TACLCSTM File Included with the Nomadic Disk Manager
?TACL MACRO
#set #informat tacl
[#if not [#variableinfo /existence/ :nomad] |then|
#def :nomad directory shared $SYSTEM.NOMADIC.NOMADSEG
]== end if
#push ulist
#set ulist [#uselist]
[#if not [#charfind ulist 1 :utils.1:dp.1] |then|
#set #uselist [#uselist] :utils:dp
] == end if
[#if not [#charfind ulist 1 :nomad.1] |then|
#set #uselist [#uselist] :nomad
] == end if
#pop ulist
==
== This is how to override the default configuration file of
== $SYSTEM.NOMADIC.NDCONFIG
==
[#if not [#variableinfo /existence/ config^file] |then|
#push config^file
] == end if
#set config^file $SYSTEM.NOMADIC.NDCONFIG
#set #pmsearchlist [#pmsearchlist] #defaults
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.