NWFragNCPExtensionRequest(3nw)


NWFragNCPExtensionRequest -- sends and receives information from an NCP extension handle

Synopsis

   #include <nwncpext.h> 
   #include <nwmisc.h> 
   or 
   #include <nwcalls.h> 
   

NWCCODE N_API NWFragNCPExtensionRequest( NWCONN_HANDLE conn, nuint32 NCPExtensionID, nuint16 reqFragCount, NW_FRAGMENT N_FAR * reqFragList, nuint16 replyFragCount, NW_FRAGMENT N_FAR * replyFragList);

Description

The parameters are as follows:

conn
(IN) Indicates the NetWare server connection handle.

NCPExtensionID
(IN) Indicates the ID of the NCP extension handler to use for the request.

reqFragCount
(IN) Indicates the number of request fragments.

reqFragList
(IN) Points to NW_FRAGMENT. Items may be modified by NWFragNCPExtensionRequest.

replyFragCount
(IN) Indicates the number of reply fragments.

replyFragList
(IN/OUT) Points to NW_FRAGMENT. Items may be modified by NWFragNCPExtensionRequest.

Notices

The fragment based protocol allows data up to 64K (a server imposed limitation) to be transferred to and from the NCP extension handler.

To increase packet efficiency, NWFragNCPExtensionRequest packs as many fragments as possible into a send buffer. On return, the data is scattered into replyFragList. Due to the internal operation of NWFragNCPExtensionRequest, fragAddress in the request and reply fragments may be changed. Upon return from NWFragNCPExtensionRequest, reqFragList and replyFragList data will be in an unknown state.

Services

NCP Extension

NCP calls

0x2222 23 17 Get File Server Information

References

NW_FRAGMENT
30 January 1998
© 1998 The Santa Cruz Operation, Inc. All rights reserved.