IPX/SPX Programming Manual

Programming Using the Socket Interface
HP NonStop IPX/SPX Programming Manual528022-001
3-13
Programming Considerations
Programming Considerations
When programming your applications, you should consider the following naming
convention for the processes and for the handling of buffers in data transfers.
Process Names
If you are running more than one NonStop IPXPROTO process in a system and wish to
locate all processes by name, the recommended form is $ZNVx, where x is a letter or
a numeric digit. In addition, all processes have a device type (19 for IPXPROTO) and
support calls to the FILE_GETINFOBYNAME_ procedure. This provision allows
applications to scan for all devices of a specified type, thereby finding all appropriate
processes in a system.
Service Names (SAP Table)
When naming a service to advertise in the Service Advertising Protocol (SAP) table,
use the following naming convention:
Name the service using the name of the NonStop system where the service
resides, such as “NYC”.
Specify a hierarchical name such as “NYC.$ODBC1” to distinguish between
multiple servers on the same system.
Follow the SAP naming conventions defined by Novell. Novell SAP naming
conventions are discussed in Section 5, Library Routines.