HP-UX SNAplus2 R7 NOF Programmer's Guide

Introduction to the NOF API

NOF Verbs to Manage Speciﬁc SNAplus2 Functions

highest backup server available in either of the two domains if the master is inactive at this point) will become the

domain conﬁguration ﬁle across the LAN; this will overwrite any changes made to the domain conﬁguration ﬁle in

the other domain while the network was split. Because of this, do not attempt to make any changes to the domain

conﬁguration ﬁle in either of the two domains while the LAN connection is broken. Changes can be made to the

conﬁguration of individual nodes.

SNAplus2 stores information about the master server and backup servers in the ﬁle

sna.net, known as the SNA

network data ﬁle. The master copy of this ﬁle is stored on the master server; any changes made to it are automatically

copied to all other servers, in the same way that changes to the domain conﬁguration ﬁle are copied to backup

servers. You cannot edit the contents of the ﬁle directly; instead, SNAplus2 provides NOF verbs to access the ﬁle.

For more information about the SNA network data ﬁle, refer to the

HP-UX SNAplus2 Administration Command

Reference.

1.4.2 HP-UX Clients

A client computer does not contain any conﬁguration ﬁle or the SNA network data ﬁle; it holds only the information

it needs to access servers on the SNAplus2 LAN and relies on a server to provide the necessary con

ﬁguration

information.

The SNA network information required is held in the ﬁle /etc/opt/sna/sna_clnt.net. For more

information about this ﬁle, refer to the HP-UX SNAplus2 Administration Command Reference.

1.4.3 Windows Clients

You can run either a 16-bit version of the SNAplus2 client software (referred to in this guide as “Win16”)ora

32-bit version (referred to in this guide as “Win32”):

• The 16-bit version can be installed on machines running Windows 3.1 or Windows for Workgroups 3.11, or on

Win16 subsystems on Windows NT, Windows 95, or OS/2. SNA network information, and other conﬁguration

information required by Win16 clients, is held in the sna.ini ﬁle.

• The 32-bit version can be installed on machines running Microsoft Windows 2000, Windows XP, or Windows

Server 2003. Conﬁguration information required by Win32 clients is managed through the Windows Registry.

For more information about the sna.ini ﬁle and the Windows Registry, and about managing Windows clients,

refer to the HP-UX SNAplus2 Administration Guide.

1.5 NOF Verbs to Manage Speciﬁc SNAplus2 Functions

The following sections list the NOF verbs that are relevant to particular SNAplus2 functions. For more information

about individual verbs, see Chapter 3, NOF API Verbs.

1.5.1 Managing the Target (Node or File) for NOF Verbs

A NOF verb can be issued to a node, to the domain conﬁguration ﬁle, or to the SNA network data ﬁle. To access

the target node or ﬁle, use one of the following verbs:

• OPEN_FILE

• CONNECT_NODE

When you issue the verbs shown above to access the target, you are initially restricted to issuing verbs that query the

conﬁguration; you cannot issue verbs to modify it. If the NOF application is running on a server (not on a client),

you can obtain write access to the target node or ﬁle so that you can issue verbs that modify the conﬁguration. Use

the following verb::