Communication Horizons Knowledgebase: N01024

© Copyright 2001 Communication Horizons LLC.
“NetLib” and “Encryptionizer” are Registered Trademarks of Communication Horizons.
US and international patents pending.
Updated 29 Dec 2001

Knowledgebase

>>ITEM: N01024

>>DATE: July 28, 1998

>>TYPE: Information

>>TITLE: Information on N_CAPSET/GET and N_D_CAPSET/GET

>>PRODUCT(S):
NetLib 2.5x for FoxPro Windows
NetLib 2.5x for FoxPro DOS
NetLib 5.0 for VFP
NetLib 6.5x for Clipper

>>PLATFORM(S):
Netware

>>SUMMARY:
N_CAPSET/GET is for use with Netware 3.x., as well as smaller Netware 4.x installations, where there is a single or primary context. N_D_CAPSET/GET is for use with NetWare 4.x networks, particularly where there are multiple contexts.

>>MORE INFORMATION:

N_CAPSET/GET

N_CAPSET/GET can be used on Netware 3.x installations, as well as small to medium Netware 4.x installations. Under Netware 4.x, the context(s) of the queue users and the context(s) of the print queues must be specified in the "Set Bindery Context" in AUTOEXEC.NCF, e.g., ; single context Set Bindery Context = O=Myorg
; multiple contexts, up to 32 Set Bindery Context = O=Myorg;OU=Mydept1.O=Myorg;OU=Mydept2.O=Myorg

Note: This bypasses NDS authorization which may need to be approved by your System Administrator.

The queue name must be less than 48 characters long, and may contain only letters, numbers and underscores ('_'). It may not contain embedded blanks. If otherwise, please use N_D_CAPSET/GET.

In both Netware 3.x and 4.x, you must include the name of the file server on which the queue resides, if it is not the "preferred server", e.g.,
N_CAPSET(1,CAP_QUEUE,"FileServer1/Laser5")

The preferred server is typically the one where the shell first logs you on. Calling NetLib's N_SERVER() function with no parameters returns your preferred server.

It is not necessary for the queue to be in the same context as the user. However, both the user's context and the queue's context must be specified as Bindery Contexts.

N_D_CAPSET/GET

Use N_D_CAPSET/GET if the user's context and/or the print queue's context are not specified as Bindery Contexts in AUTOEXEC.NCF. This is true even if they are both on the same file server.

For example, the user may be in context "O=myorg." and the print queue in context "OU=mydept1.O=myorg". If only "O=myorg." is specified as a Bindery Context, you must use N_D_CAPSET/GET. N_CAPSET/GET will not recognize the queue.

In addition, you must use N_D_CAPSET/GET if the print queue name contains any embedded blanks or special characters other than underscore ('_'). For example, if the queue name is: "Queue #1" you must use N_D_CAPSET/GET, since N_CAPSET/GET will not recognize it as a valid name.

>>RESOLUTION/FIX:
If you have a small or medium-sized network, with a single or small number of contexts, we recommend using N_CAPSET/GET unless you have a specific reason not to do so (as discussed above.)

>>EXAMPLE(S):

>>SEE ALSO: N00068, N01023

Knowledgebase Top Home