Distributed Name Service (DNS) Management Programming Manual

Stopping DNS
Communicating with the DNS Name Manager
46958 Tandem Computers Incorporated 2–7
The fourth line (error := FILE_OPEN_ ...) calls the Guardian 90 FILE_OPEN_
procedure, passing the file name and file number word. The first “1” indicates that the
name manager is being opened for NOWAIT operations. The second “1” indicates the
Guardian 90 file system automatically retries any operation that results in a path
failure.
The fifth line (IF error = 0 THEN) tests the result of the FILE_OPEN_ call.
See the next subsection, “Guardian 90 Procedure Considerations,” for special
considerations for using Guardian 90 procedures.
Open Errors In response to an open request, the name manager might return one of the file errors
listed by number and name in Table 2-1.
Table 2-1. Open Errors for Name Manager
Error Meaning
0 (FEOK) The process has accepted the open.
12 (FEINUSE) The process already has as many openers as it is
designed to handle.
28 (FETOOMANY) The nowait depth or sync depth > 1 was specified.
48 (FESECVIOL) The opener does not have READ authority to DNS.
61 (FEOPENSTOP) DNS is in the STOPPING state.
100 (FENOTREADY) The process is still reading its startup message.
Closing the DNS Name
Manager Process
Management applications (including DNSCOM) open a name manager process and
send it commands. When an application is finished communicating with a name
manager, it calls the FILE_CLOSE_ procedure (CLOSE for C-series Guardian 90) to
close a name manager process.
Stopping DNS Using DNSCOM, the interactive STOP DNS command initiates an orderly shutdown
of the DNS subsystem. This command is described in the Distributed Name Service
(DNS) Management Operations Manual.
The programmatic STOP command has the same result as the interactive STOP DNS
command and is discussed in Section 6.