Name space specific information is maintained by the NLM that implements the name space. Much of this information may not be accessible as primary information. For example, huge data information is name space specific and must be returned by special requests
Consequently, name space includes specialized functions for accessing name space specific information. This approach requires a detailed understanding of the particular name space and the entry information it maintains.
Name space specific information is accessed by calling NWReadNSInfo and NWWriteNSInfo. Both functions refer to the entry using a NetWare entry index, which is maintained as NW_IDX. To initialize NW_IDX, call NWGetDirectoryBase and pass both a DOS directory entry (handle/path) and the target name space.
The following topics contain more detailed information:
NetWare uses a generic mechanism to represent the format of name space specific entry information. Query the NetWare server by calling NWGetNSInfo to find the format for a particular name space. NWGetNSInfo returns a set of bit masks as NW_NS_INFO. The structure indicates the size and arrangement of name space specific information.
NSInfoBitMask in NW_NS_INFO indicates all valid data items for an entry in the name space. NWGetNSInfo initializes the bit masks for a specific name space and computes the value of NSInfoBitMask.
NSInfoBitMask is derived by combining the fixed and reserved masks through a logical OR operation.
After NW_NS_INFO is initialized, use it in subsequent calls to NWReadNSInfo and NWWriteNSInfo to read or modify name space specific entry information.
The interpretation of the name space bit mask depends on which name space you are querying. For example, the DOS name space defines the following bits:
Under DOS, bit 0 represents the modify name. This is generally the case in other name spaces also. The modify name is read-only; don’t attempt to modify it.
These functions deal with name-space specific information: