NWWritePropertyValue(3nw)

NWWritePropertyValue -- writes property data of bindery object on NetWare server associated with connection handle

Synopsis

#include <nwbindry.h> or #include <nwcalls.h>

NWCCODE N_API NWWritePropertyValue (NWCONN_HANDLE conn, pnstr8 objName, nuint16 objType, pnstr8 propertyName, nuint8 segmentNum, pnuint8 segmentData, nuint8 moreSegments);

Description

The parameters are as follows:

conn: (IN) Specifies the NetWare server connection handle.
objName: (IN) Points to the object's name.
objType: (IN) Specifies the object's bindery type.
propertyName: (IN) Points to the object's property name.
segmentNum: (IN) Specifies the segment number of the written data (128-byte blocks).
segmentData: (IN) Points to the 128-byte buffer containing the data.
moreSegments: (IN) Specifies whether more segments are being written.

Return values

0x0000: SUCCESSFUL
0x8801: INVALID_CONNECTION
0x8996: SERVER_OUT_OF_MEMORY
0x89E8: WRITE_PROPERTY_TO_GROUP
0x89EC: NO_SUCH_SEGMENT
0x89F0: WILD_CARD_NOT_ALLOWED
0x89F8: NO_PROPERTY_WRITE_PRIVILEGE
0x89FB: N0_SUCH_PROPERTY
0x89FC: NO_SUCH_OBJECT
0x89FE: BINDERY_LOCKED
0x89FF: HARDWARE_FAILURE

Notices

A client must have Write access to the property to call NWWritePropertyValue.

segmentNum indicates which segment of data is being written and should be assigned a value of 1 for the first segment. In addition, moreSegments should contain 0xFF, to indicate more segments can exist. To signal NetWare that the last segment is being written, assign 0x00 to moreSegments. When done any remaining segments are truncated and the extra segments discarded.

Create property value segments sequentially. Before segment N can be created, all segments from 1 to N-1 must be created. However, once all segments of a property value have been established, segments can be written at random. If the segment data is longer than 128 bytes, it is truncated and the 128th byte is NULL.

NOTE: Keep property values to a single segment (128 bytes) to improve bindery efficiency.

objName, objType, and propertyName must uniquely identify the property and cannot contain wildcard characters.

Following are the bindery object types in high-low order:

0xFFFF: OT_WILD
0x0000: OT_UNKNOWN
0x0100: OT_USER
0x0200: OT_USER_GROUP
0x0300: OT_PRINT_QUEUE
0x0400: OT_FILE_SERVER
0x0500: OT_JOB_SERVER
0x0600: OT_GATEWAY
0x0700: OT_PRINT_SERVER
0x0800: OT_ARCHIVE_QUEUE
0x0900: OT_ARCHIVE_SERVER
0x0A00: OT_JOB_QUEUE
0x0B00: OT_ADMINISTRATION
0x2100: OT_NAS_SNA_GATEWAY
0x2600: OT_REMOTE_BRIDGE_SERVER
0x2700: OT_TCPIP_GATEWAY

The bindery makes no attempt to coordinate activities among multiple workstations concurrently reading or writing data to a single property. This means that one workstation might read a partially updated property and get inconsistent data if the property's data extends across multiple segments. If this presents a problem, coordination of Reads and Writes must be handled by application programs. Logical record locks can be used to coordinate activities among applications.

Services

Bindery

NCP calls

0x2222 23 62 Write Property Value

References

NWReadPropertyValue(3nw)