FS VERIFYUNCNAME: Difference between revisions
Created page with "{{DISPLAYTITLE:FS_VERIFYUNCNAM}} Used to poll installed UNC FSDs to determine server ownership. ==Syntax== int far pascal FS_VERIFYUNCNAME(flag, pName) ==Parameters== ; fla..." |
mNo edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE: | {{DISPLAYTITLE:FS_VERIFYUNCNAME}} | ||
Used to poll installed UNC FSDs to determine server ownership. | Used to poll installed UNC FSDs to determine server ownership. | ||
==Syntax== | ==Syntax== | ||
int far pascal FS_VERIFYUNCNAME(flag, pName) | int far pascal FS_VERIFYUNCNAME(flag, pName) | ||
==Parameters== | ==Parameters== | ||
; flag : indicates which ‘pass‘ of the poll the FSD is being called. | ;flag : indicates which ‘pass‘ of the poll the FSD is being called. | ||
:: | ::0x0000 indicates that this is a pass 1 poll. | ||
:: | ::0x0001 indicates that this is a pass 2 poll. | ||
;pName: is a pointer to the ASCIIZ name of the server in UNC format. The FSD does not need to verify this pointer. | |||
; pName: is a pointer to the ASCIIZ name of the server in UNC format. | |||
==Returns== | ==Returns== | ||
| Line 20: | Line 20: | ||
==Remarks== | ==Remarks== | ||
What the kernel expects from UNC FSDs for this entry point: | What the kernel expects from UNC FSDs for this entry point: | ||
For pass 1, the FSD will be called and passed a pointer to the UNC server name. It is to respond immediately if it recognizes (manages) the server with a NO_ERROR return code. This pass expects the that the FSD will be keeping tables in memory that contain the UNC names of the servers it is currently servicing . If the UNC name cannot be validated immediately, the FSD should respond with an error (non-zero) return code. The FSD SHOULD NOT send messages in an attempt to validate the server name. | For pass 1, the FSD will be called and passed a pointer to the UNC server name. It is to respond immediately if it recognizes (manages) the server with a NO_ERROR return code. This pass expects the that the FSD will be keeping tables in memory that contain the UNC names of the servers it is currently servicing. If the UNC name cannot be validated immediately, the FSD should respond with an error (non-zero) return code. The FSD SHOULD NOT send messages in an attempt to validate the server name. | ||
For pass 2, the FSD is permitted to do whatever is reasonable, including sending LAN ‘are you there‘ messages, to determine if they are able to service the request for UNC server. | For pass 2, the FSD is permitted to do whatever is reasonable, including sending LAN ‘are you there‘ messages, to determine if they are able to service the request for UNC server. | ||
[[Category:IFS]] | [[Category:IFS Interfaces]] | ||
Latest revision as of 05:59, 17 February 2020
Used to poll installed UNC FSDs to determine server ownership.
Syntax
int far pascal FS_VERIFYUNCNAME(flag, pName)
Parameters
- flag
- indicates which ‘pass‘ of the poll the FSD is being called.
- 0x0000 indicates that this is a pass 1 poll.
- 0x0001 indicates that this is a pass 2 poll.
- pName
- is a pointer to the ASCIIZ name of the server in UNC format. The FSD does not need to verify this pointer.
Returns
Sample
unsigned short flag; char far * pName; int far pascal FS_VERIFYUNCNAME(flag, pName)
Remarks
What the kernel expects from UNC FSDs for this entry point:
For pass 1, the FSD will be called and passed a pointer to the UNC server name. It is to respond immediately if it recognizes (manages) the server with a NO_ERROR return code. This pass expects the that the FSD will be keeping tables in memory that contain the UNC names of the servers it is currently servicing. If the UNC name cannot be validated immediately, the FSD should respond with an error (non-zero) return code. The FSD SHOULD NOT send messages in an attempt to validate the server name.
For pass 2, the FSD is permitted to do whatever is reasonable, including sending LAN ‘are you there‘ messages, to determine if they are able to service the request for UNC server.