Distributed Name Service (DNS) Management Programming Manual

Opening the Name Manager
Communicating with the DNS Name Manager
2–6 46958 Tandem Computers Incorporated
After your application starts the name manager process, it must send the process a
startup message that includes any additional desired startup parameters, as described
in the GUARDIAN 90 Operating System Programmer’s Guide. The IN file must use the
name of the configuration file that the name manager is to use and the OUT file must
use the name of the file where the name manager is to send its EMS events.
If you wish to direct the name manager to run as a NonStop process pair, you must
specify the backup CPU number in the parameter string of the startup message. If no
backup CPU is specified, the name manager will not run as a process pair.
Opening the Name
Manager
Communication with a DNS name manager process is established using open requests
sent to the name manager. The DNS name manager accepts up to 64 opens from
DNSCOM or other management applications. These opens can be received through
either an interactive or programmatic interface.
Opening the Name Manager
Interactively
To establish communication with a DNS name manager process interactively, use
DNSCOM’s OPEN command at the DNSCOM prompt. Running DNSCOM is
discussed in more detail in the Distributed Name Service (DNS) Management Operations
Manual.
Opening the Name Manager
Programmatically
To establish communication with a DNS name manager process programmatically, a
management application simply opens $ZDNS. Below is an example of opening a
name manager programmatically from a management application.
EXAMPLE: Opening a Name Manager Process Programmatically
STRING name^manager[0:11] := ["$ZDNS.#ZSPI"];
INT dns^fnum;
INT error;
error := FILE_OPEN_(name^manager, dns^fnum, , , 1, 1);
IF error = 0 THEN
Open successful
ELSE
Open failed
In this example the first line (STRING name^manager... ) allocates an array in memory
containing the name of the file ($ZDNS.#ZSPI) to be opened. (The file name
$ZDNS.#ZSPI is in external format.)
The second line (INT dns^fnum) allocates a word of memory to hold the file number
returned by the FILE_OPEN_ procedure. The file number serves as a handle for the
file in subsequent file operations.
The third line (INT error) allocates a word in memory to hold the result of the call to
FILE_OPEN_ in the fourth line.