SNADS File Server Object APIs

The SNADS file server object APIs would be used if you were dealing with AnyMail/400 mail server framework (MSF) messages that contained SNADS attachments. You would use the file server object read API if the MSF message was originated by OfficeVision^(R) or object distribution. You would use the create and write APIs if the MSF message was destined for an OfficeVision or an object distribution user, or if you want to temporarily store attachments.

With the SNADS file server interface, you can create and manipulate either SNADS general file server objects or Document Interchange Architecture (DIA) file server objects. A file server object (FSO) in this context is used by SNADS and by applications like object distribution and OfficeVision to store data associated with a message (for example, an OfficeVision note).

Although SNADS general file server objects and DIA file server objects are manipulated using the same interface, they differ in content.

For additional information, see File Server Objects.

The SNADS file server object APIs are:

• Assign SNADS File Server Object Access ID (QZDASNID) assigns an access ID to a specific file server object (FSO).
• Create SNADS File Server Object (QZDCRFSO) allows a user to create an FSO on the server.
• List SNADS File Server Object Access IDs (QZDLSTID) lists the current accesses owned by the specified product.
• Read SNADS File Server Object (QZDRDFSO) provides functions for reading a file server object on the server.
• Retrieve SNADS File Server Object Access ID (QZDRTVID) allows the caller to retrieve information about one access ID.
• Revoke SNADS File Server Object Access ID (QZDRVKID) revokes an access ID to a specific file server object that was previously assigned.
• Write to SNADS File Server Object (QZDWTFSO) provides functions for writing to a file server object on the system.