Except in multiple resilience configurations there is exactly one record in the Network Status table. This record has both key fields set to 0. You can read the record with a call to rec_fetch_main(EQUAL,...). This allows you to discover the networking configuration by examining the values in the resil_type and err_mode fields.
Although the software does not prevent it, there is no point in posting to the network status table unless you are using DP4 in a Multiple Resilience Configuration. Updates have no effect on the operation of DP4 in these configurations.
‡From 4.621, and currently on Win32 platforms only, when Named Connection configuation is in use the network status will be returned differently according to how requests to the database manager are routed. Connections to the local machine will return the network status information as though the system was running in standalone mode. Connections to a remote machine will return the network status information as though the system was running simple client server networking. On other platforms the network status will currently always indicate a network connection. This is reasonable, because on those platforms the requests are sent to the network. DP4 detects whether a connection is local or remote by attempting to bind a socket to the IP address of the server. This will only succeed if the server is local.