Developer Pointers
Articles and Tips: article
01 Aug 1998
Novell Technical Information Documents
All of the Technical Information Documents (TIDs) discussed below are available at the following locations:
The Novell Technical Solutions Database on CompuServe (GO NTID)
The DeveloperNet Support World Wide Web site (http://devsup.novell.com)
The DeveloperNet Support Bulletin Board (801-861-5836)
CLIB & ANSI Compliance
|
Author: |
AJ |
|
Document ID: |
TID101694 |
|
Document revision: |
A |
|
Date: |
1998/05/29 2:26 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IABJ529.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Concerning the non-ANSI-compliant nature of fputs()insofar as how it is documented (SDK CD Rel 15).
Detailed Description
Full ANSI compliance in CLIB is achieved by linking NWPRE.OBJ instead of PRELUDE.OBJ. There are a number of backward-compatible features that are eliminated when PRELUDE.OBJ is replaced by NWPRE.OBJ. Novell Developer Support does not have a list; but basically, if it was broken and developers had to code around it, the "broken-ness" is preserved in PRELUDE.OBJ.
fputs() is probably the most glaring example of non-ANSI-compliance which is fixed by using NWPRE.OBJ.
File Information
Self-Extracting File Name: IABJ529.EXE
|
Files Included: |
Size |
Date |
Time |
|
IABJ529.TXT |
(this file) |
||
|
IABJ529.MSG |
102 |
5-29-98 |
2:24 PM |
3Com mibs from Transcend Enterprise for Windows Modified to Compile with ManageWise MIB Compiler
|
Author: |
SP |
|
Document ID: |
TID101695 |
|
Document revision: |
A |
|
Date: |
1998/05/29 4:17 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XMWS016.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
3Com MIBs from Transcend Enterprise for Windows were modified to compile with ManageWise MIB compiler in attached 3CMIBMOD.ZIP.
Detailed Description
3Com MIBs from Transcend Enterprise for Windows were modified to compile with ManageWise MIB compiler to fix errors:
Removed illegal characters ("-", "") from Object names and named values.
Corrected problems with capitalization with object names and values.
Renamed *.MIB to *.NOP where MIB redefines objects.
Added IMPORTS where necessary.
Converted from SNMPv2 to SNMPv1 since ManageWise supports SNMPv1 only.
The conversion utility used was a public domain tool at mib-v2tov1@dbc.mtview.ca.us. The v2 version MIBs are renamed to *.v2, and the converted v1 MIBs are located in V2CONV directory. One of the v2 MIBs (IF-MIB) failed to convert due to the use of 64-bit counter.
Note: Some functionality may be lost when SNMP v2 functionality cannot be defined within v1 syntax. Check the MIB after conversion to check for functionality changes.
File Information
Self-Extracting File Name: XMWS016.EXE
|
Files Included: |
Size |
Date |
Time |
|
XMWS016.TXT (this file) |
|||
|
XMWS016.MSG |
123 |
5-29-98 |
4:16 PM |
Classpath problem of OSA SDK 1.0 and NetWare 5
|
Author: |
MM |
|
Document ID: |
TID101698 |
|
Document revision: |
A |
|
Date: |
1998/06/2 9:12 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IMMJAR.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
This TID provides a new JAVA.CFG and RUNCSHELL.NCF so that a customer can add his own jars to the classpath.
Detailed Description
The combination of the OSA SDK 1.0 and NetWare 5 Beta 3 has a bug which will be very frustrating for Java developers on NetWare. The following illustrates the problem.
Symptom of Problem: A customer creates his own .JAR file and adds it to the JVM CLASSPATH by editing the file SYS:\ETC\JAVA.CFG on the server. He then downs the server and brings it back up fully expecting to see the new .JAR file in the CLASSPATH. He types envset on the server console to verify that the new .JAR is now in the current classpath. It doesn't show up. The ramification is that a customer cannot add his own jars to the classpath.
What is Really Happening: When the Java Virtual Machine is started on the server the file SYS:\ETC\JAVA.CFG is read and the CLASSPATH is set as stated in that file. However, ConsoleOne then comes up which permanently obliterates the CLASSPATH setup in JAVA.CFG. ConsoleOne sets up the CLASSPATH for .JAR files it needs to run.
How This Happens: In SYS:\SYSTEM\AUTOEXEC.NCF there is the line C1START.NCF. The C1START.NCF file then calls the file SYS:\MGMT\CONSOLE1\RUNSHELL.NCF. In RUNSHELL.NCF, the CLASSPATH is obliterated and redefined for ConsoleOne.
How to Fix This: We provide tech support with two patches:
A new JAVA.CFG file
A new RUNSHELL.NCF file
The file JAVA.CFG needs to replace the JAVA.CFG in SYS:\ETC. The file RUNCSHELL.NCF needs to replace the RUNSHELL.NCF in SYS:\MGMT\CONSOLE1.
After copying these files to these locations, the customer needs to down his server and bring it back up. At this point, any additions to the classpath can be made to JAVA.CFG. This will be fixed for NetWare 5 FCS!
File Information
Self-Extracting File Name: IMMJAR.EXE
|
Files Included: |
Size |
Date |
Time |
|
IMMJAR.TXT |
(this file) |
||
|
JAVA.CFG |
705 |
6-2-98 |
8:50 AM |
|
RUNSHELL.NCF |
96 |
6-2-98 |
8:50 AM |
|
IMMJAR.MSG |
110 |
6-2-98 |
8:50 AM |
Sample code - GetServerInformation(), GetFileServerDescriptionStrings()
|
Author: |
CM |
|
Document ID: |
TID101701 |
|
Document revision: |
A |
|
Date: |
1998/06/3 4:52 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XSES1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Lists servers, NetWare versions, and companies.
Detailed Description
Lists servers, their NetWare versions, and their companies, using ScanBinderyObject to obtain server names, GetServerInformation to get NetWare version and subversion, and GetFileServerDescriptionStrings to get company name. This is all done through a while loop until the user presses escape to discontinue.
File Information
Self-Extracting File Name: XSES1.EXE
|
Files Included: |
Size |
Date |
Time |
|
XSES1.TXT |
(this file) |
||
|
VERSION.NLM |
7266 |
6-3-98 |
4:51 PM |
|
VERSION.C |
9587 |
6-3-98 |
4:51 PM |
|
XSES1.MSG |
49 |
6-3-98 |
4:51 PM |
Revised sample code - Demonstrates NWDSIsDSServer()
|
Author: |
CM |
|
Document ID: |
TID101699 |
|
Document revision: |
A |
|
Date: |
1998/06/2 9:13 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XNDS2.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Revised from XDSA6. Imports NWDSIsDSServer() which tells whether or not a server supports NDS or Bindery.
Detailed Description
Contains sample code and NLM executable which demonstrates an implementation of the NWDSIsDSServer() function. The application lists all known servers and whether or not they support NetWare Directory Services. If NDS is supported, the tree-name is displayed.
Checks to see if NDS is supported by importing the function, NWDSIsDSServer() .
File Information
Self-Extracting File Name: XNDS2.EXE
|
Files Included: |
Size |
Date |
Time |
|
XNDS2.TXT |
(this file) |
||
|
ISDS.C |
11338 |
6-2-98 |
9:08 AM |
|
ISDS.NLM |
6229 |
6-2-98 |
9:08 AM |
|
XNDS2.MSG |
108 |
6-2-98 |
9:08 AM |
Delphi Sample: Get Server LAN Information
|
Author: |
WS |
|
Document ID: |
TID101705 |
|
Document revision: |
A |
|
Date: |
1998/06/9 2:52 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
D3LAN.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
D3LAN is a Delphi 1.x/2.x/3.x application that illustrates the use of Delphi with NetWare APIs. It will retrieve LAN information for the selected server. General information on how to use Delphi with the NetWare SDK can be found in the HOW-TO.DOC file. To run the application, you need access to the 16-bit or 32-bit NetWare DLLs as provided in the NetWare Client software:
CALWINxx.DLLNETWINxx.DLL
CLXWINxx.DLL
LOCWINxx.DLL
where xx stands for `16' or `32'.
Platform: Windows 3.x/Win95/WinNT Compilers: Borland Delphi 3.x
Functions Used: D3LAN demonstrates the following NetWare API functions:
NWCCOpenConnByRefNWCCScanConnRefs
NWDSGetBinderyContext
NWDSGetServerDN
NWGetActiveLANBoardList
NWGetFileServerInformation
NWGetLANConfigInfo
NWGetLoadedMediaNumList
NWGetMediaMgrObjChildrenList
NWGetMediaMgrObjInfo
NWGetMediaMgrObjList
NWGetMediaNameByMediaNum
NWGetNLMInfo
NWGetNLMLoadedList
NWGetProtocolStackConfigInfo
NWGetProtocolStkNumsByLANBrdNum
NWGetProtocolStkNumsByMediaNum
File Information
Self-Extracting File Name: D3LAN.EXE
|
Files Included: |
Size |
Date |
Time |
|
D3LAN.TXT |
(this file) |
||
|
READ.ME 1088 |
6-9-98 |
2:48 PM |
|
|
LANINFO.PAS |
15685 |
6-9-98 |
2:48 PM |
|
LANINFO.DFM |
3787 |
6-9-98 |
2:48 PM |
|
LANINFO.DCU |
14827 |
6-9-98 |
2:48 PM |
|
HOW-TO.DOC |
6143 |
6-9-98 |
2:48 PM |
|
D3LAN.RES |
876 |
6-9-98 |
2:48 PM |
|
D3LAN.DSK |
2540 |
6-9-98 |
2:48 PM |
|
D3LAN.DPR |
277 |
6-9-98 |
2:48 PM |
|
D3LAN.DOF |
942 |
6-9-98 |
2:48 PM |
|
D3LAN.TXT |
2856 |
6-9-98 |
2:48 PM |
|
DELPHI_U.PAS |
41044 |
6-9-98 |
2:48 PM |
|
D3LAN.MSG |
1070 |
6-9-98 |
2:48 PM |
Sample Code - Connection Number of Trustee_Change_Event
|
Author: |
BC |
|
Document ID: |
TID101707 |
|
Document revision: |
A |
|
Date: |
1998/06/9 3:19 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XCON6.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Sample code demonstrates how to get the connection number of the user that triggered the event - trustee_change. Only known to work on the NetWare 4.11 OS platform.
Detailed Description
[When in doubt, give it out. . . .]
Although this is not documented, and disagrees with nwadv.h, it may be useful for some. It has (currently) only been tested on NW 4.11, and is known not to function on NW 3.12.
Where it works, it is an extension to the EventTrustChangeStruct. The structure EventTrustChangeStruct is revised as following:
structure EventTrustChangeStruct2{
"LONG objectID;
"LONG entryID;
"LONG volumeNumber;
"LONG changeFlags;
"LONG newRights;
"LONG unreleased; /* revised part NW 4.11 only */
"LONG connectionNumber; /* Conn number that triggered event */
"}
There is only limited support for this newer structure from Novell.
File Information
Self-Extracting File Name: XCON6.EXE
|
Files Included: |
Size |
Date |
Time |
|
XCON6.TXT |
(this file) |
||
|
TRUSTEE.C |
7618 |
6-9-98 |
3:18 PM |
|
TRUSTEE.NLM |
6178 |
6-9-98 |
3:18 PM |
|
XCON6.MSG |
168 |
6-9-98 |
3:18 PM |
Sample Code - NWDSEGetLocalEntryID()
|
Author: |
BC |
|
Document ID: |
TID101706 |
|
Document revision: |
A |
|
Date: |
1998/06/9 2:52 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XCON7.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Demonstrates the use of NWDSEGetLocalEntryID() in combination with (required) unicode-format input.
Detailed Description
SDK CD Rel. 15 documentation is unclear regarding the required use of unicode as an input parameter for the NWDSEGetLocalEntryID() . This code demonstrates proper use of this function.
File Information
Self-Extracting File Name: XCON7.EXE
|
Files Included: |
Size |
Date |
Time |
|
XCON7.TXT |
(this file) |
||
|
GETID.C |
10384 |
6-9-98 |
2:50 PM |
|
GETID.NLM |
7589 |
6-9-98 |
2:50 PM |
|
XCON7.MSG |
100 |
6-9-98 |
2:50 PM |
Sample Code - Revised How to create an NDS Queue
|
Author: |
CM |
|
Document ID: |
TID101708 |
|
Document revision: |
A |
|
Date: |
1998/06/9 3:44 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XNDS3.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Revised sample code XDSAE. Format changed and changed obsolete functions such as NWDSCreateContext to NWDSCreateContextHandle. Also printed out results of what was added to buffer (Buf_T addBuffer).
Detailed Description
Queues in NetWare 4.x are nothing more than NDS objects of the class type Queue. This example demonstrates how to create a queue with the appropriate attributes to successfully instantiate the object. Further filling out of a queue's attributes might be necessary to actually be useful, but could be done by extending this code.
File Information
Self-Extracting File Name: XNDS3.EXE
|
Files Included: |
Size |
Date |
Time |
|
XNDS3.TXT |
(this file) |
||
|
CRQUEUE.C |
16504 |
6-9-98 |
3:42 PM |
|
CRQUEUE.NLM |
9216 |
6-9-98 |
3:42 PM |
|
XNDS3.MSG |
202 |
6-9-98 |
3:42 PM |
Sample Code - NWCCOpenConnByName(), NWDSAuthenticateConn()
|
Author: |
BC |
|
Document ID: |
TID101709 |
|
Document revision: |
A |
|
Date: |
1998/06/10 3:12 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XCON8.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Authenticate the connection to the file server.
Detailed Description
The sample code demonstrates the way to connect to the file server and authenticate the connection through NDS.
File Information
Self-Extracting File Name: XCON8.EXE
|
Files Included: |
Size |
Date |
Time |
|
XCON8.TXT |
(this file) |
||
|
CONNECT.C |
9241 |
6-10-98 |
3:11 PM |
|
CONNECT.NLM |
7128 |
6-10-98 |
3:11 PM |
|
XCON8.MSG |
48 |
6-10-98 |
3:11 PM |
Using the DSI flags to obtain an NDS object's creation time
|
Author: |
KB |
|
Document ID: |
TID101710 |
|
Document revision: |
A |
|
Date: |
1998/06/10 6:02 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
INDSKBI.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
The DSI Flags affect the information returned by the NWDSSetContext, NWDSGetContext, NWDSReadObjectInfo, NWDSList, NWDSReadObjectDSIInfo, and NWDSGetDSIInfo APIs. This Sample code will show how to return an object's creation and last modification date using DSI flags.
Detailed Description
The DSI Flags affect the information returned by the NWDSSetContext, NWDSGetContext, NWDSReadObjectInfo, NWDSList, NWDSReadObjectDSIInfo, and NWDSGetDSIInfoAPIs. This Sample code will show how to return an objects creation and last modification date using DSI flags.
If you remove the default flags from the context handle, the NWDSReadObjectInfo and NWDSGetDSIINfo APIs that follow the NWDSList API will be affected.
If you add flags to the context handle, you can access the additional information by calling the NWDSReadObjectDSIInfo API or by calling the NWDSlist , NWDSGetObjectNameAndInfo , and NWDSGetDSIInfo APIs in this specific order.
The attached code can be used as a model for returning all other information about an object and from various other APIs. DSI flags apply to all versions/variants of NWDSList , NWDSRead , NWDSReadObjectInfo , and NWDSSearch . The attached code, readdsinfo , requires a object on the command line: readdsinfo.
The program outputs the following:
Distinguished Name--> >CN=Admin.OU=Widget.O=Novell>> Creation Timestamp--> Tue Jun 10 18:15:25 1998> Modification TimeStamp--> Wed Jun 11 18:35:20 1998> Base Class--> >User>>
Note: The attached libraries must be placed in the same directory as READDSINFO.EXE.
File Information
Self-Extracting File Name: INDSKBI.EXE
|
Files Included: |
Size |
Date |
Time |
|
INDSKBI.TXT |
(this file) |
||
|
READDSIINFO.EXE |
94720 |
6-10-98 |
6:00 PM |
|
CLNWIN32.DLL |
61440 |
6-10-98 |
6:00 PM |
|
NETWIN32.DLL |
119296 |
6-10-98 |
6:00 PM |
|
NCPWIN32.DLL |
140800 |
6-10-98 |
6:00 PM |
|
READDSIINFO.C |
3668 |
6-10-98 |
6:00 PM |
|
INDSKBI.MSG |
270 |
6-10-98 |
6:00 PM |
Pre-release NLM libraries for NW 4.x
|
Author: |
AJ |
|
Document ID: |
TID101711 |
|
Document revision: |
A |
|
Date: |
1998/06/11 4:48 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
PLIB4X09.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
11-06-98 Pre-release builds of NLM libraries for NetWare 4.x. These files are not fully tested and should not be used in production environments. Rather, they are intended to be used by NLM developers to test applications for compatibility.
File Information
Self-Extracting File Name: PLIB4X09.EXE
|
Files Included: |
Size |
Date |
Time |
|
PLIB4X09.TXT |
(this file) |
||
|
THREADS.NLM |
89187 |
6-11-98 |
4:46 PM |
|
STREAMDU.NLM |
416 |
6-11-98 |
4:46 PM |
|
REQUESTR.NLM |
47659 |
6-11-98 |
4:46 PM |
|
CLIB.NLM |
83678 |
6-11-98 |
4:46 PM |
|
NLMLIB.NLM |
91636 |
6-11-98 |
4:46 PM |
|
NIT.NLM |
47869 |
6-11-98 |
4:46 PM |
|
MATHLIBC.NLM |
426 |
6-11-98 |
4:46 PM |
|
MATHLIB.NLM |
417 |
6-11-98 |
4:46 PM |
|
GLOBAL.NLM |
407 |
6-11-98 |
4:46 PM |
|
FPSM.NLM |
16504 |
6-11-98 |
4:46 PM |
|
NMX.NLM |
426 |
6-11-98 |
4:46 PM |
|
PLIB4X09.MSG |
253 |
6-11-98 |
4:48 PM |
Sample code for api, NWDSReadObjectInfo()
|
Author: |
CM |
|
Document ID: |
TID101696 |
|
Document revision: |
A |
|
Date: |
1998/06/1 11:14 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XNDS1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
This updated version of previous sample code, XDSAG, initializes libraries, creates context handle, logs in, opens a connection, and calls readobjectinfo. Lastly, it prints out the structure from NWDSReadOjbectInfo .
Detailed Description
This is a sample code for the function NWDSReadObjectInfo() , which returns object information. The function returns the following information: object flags, the number of objects subordinate to the object, the date the object was last modified, and lastly the class (i.e. the user).
The previous code did not initialize libraries. NWCallsInit() and NWCLXInit() initializes libraries. Next, NWDSCreateContextHandle is used instead of NWDSCreateContext() which was made obsolete 03/97. NWDSLogin() is the same. The username, password, and context handle (passed out by NWDSCreateContextHandle ) are passed into this function.
After logging in, I open a connection using NWCCOpenConnByName . This was not done in the original code, but is necessary to establish a connection. Next, I call my own function DSReadObjectInfo() which calls NWDSReadObjectInfo and prints out the results of that function. The structure that the function returns is described above. Lastly, I close and free up memory.
File Information
Self-Extracting File Name: XNDS1.EXE
|
Files Included: |
Size |
Date |
Time |
|
XNDS1.TXT |
(this file) |
||
|
READOBJ.C |
9165 |
6-1-98 |
11:09 AM |
|
READOBJ.NLM |
7277 |
6-1-98 |
11:09 AM |
|
XNDS1.MSG |
210 |
6-1-98 |
11:09 AM |
Virtual Resources Listing (IPX SAP, IPX Sockets & NCP Extension Names)
|
Author: |
AJ |
|
Document ID: |
TID101717 |
|
Document revision: |
A |
|
Date: |
1998/06/15 9:27 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
VR_LIST.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
Printed (MST): Fri Jun 12 16:07:11 1998.
Novell's Virtual Resources include IPX/SAP Service Types, IPX Static Socket Numbers, NCP Extension Names and IDs, NDS Schema Name Prefixes, NLM Names, and NLM Library Function Prefixes. (See http://developer.novell.com/devres/ss/resource.htm for detailed definitions.)
Detailed Description
Novell Virtual Resources Registry Public Records Report Printed (MST): Fri Jun 12 16:07:11 1998
Novell has introduced many standards for the networking environment. Some of these standards include Virtual Resources assigned by Novell. Novell's Virtual Resources include IPX/SAP Service Types, IPX Static Socket Numbers, NCP Extension Names and IDs, NDS Schema Name Prefixes, NLM Names, and NLM Library Function Prefixes. (See http://developer.novell.com/devres/ss/resource.htm for detailed definitions.)
Novell Developer Support maintains the registry for Novell's Virtual Resources. Application developers can contact Novell Developer Support to request that a Virtual Resource be assigned to their product. (http://devsup.novell.com, subject: VIRTUAL RESOURCE REQUEST)
When a request for a Virtual Resource is granted, the applicant can elect to make their registry data (or a portion thereof) public or private. This file lists all "public" records in the registry. "Private" records are not published.
Send questions or comments about this list to the e-mail address: http://devsup.novell.com(and place "VR_LIST" in the e-mail subject line).
Copyright (C) 1998, Novell Inc., Provo, Utah. All rights reserved.
Novell, Inc. makes no representations or warranties with respect to the contents or use of this document or of any of the third-party products mentioned. Novell reserves the right to revise this document and make changes to its content at any time, without obligation to notify any person or entity of such revisions or changes. This document does not constitute an endorsement of the third-party product or products that are listed.
You must obtain permission before reproducing any material from this list. To quote from or reprint any portion of this document, send a written request to Novell Developer Support, MS:PRV-F-121, 122 East 1700 South, Provo, UT 84606.
File Information
Self-Extracting File Name: VR_LIST.EXE
|
Files Included: |
Size |
Date |
Time |
|
VR_LIST.TXT |
(this file) |
||
|
VR_LIST.DOC |
1790826 |
6-15-98 |
9:23 AM |
|
VR_LIST.MSG |
320 |
6-15-98 |
9:23 AM |
Monitor's Connection Status - an explanation
|
Author: |
KB |
|
Document ID: |
TID101713 |
|
Document revision: |
A |
|
Date: |
1998/06/11 5:15 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
INDSKBJ.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
In NetWare's Monitor utility, selecting Connections from the Available Options box show all the active connections in the Active Connection box. This TID covers the possible states of these connections.
Detailed Description
In NetWare's Monitor utility, selecting Connections from the Available Options box shows all the active connections in the Active Connection box. This TID covers the possible states of these connections.
The help file in Monitor states the following: Licensed connections are authenticated, logged in, and consume one of the server's licenses. Unlicensed connections--indicated by an asterisk (*)--are authenticated, but do not count against a server's licenses because they are not yet logged in. They can access the NDS database, but no other server resources.
Using MONITOR.NLM to look at the connection table, some connections are marked with an (*) asterisk. The definition of these is that they are 'authenticated but not logged in.'
Another way to explain the (*) is that the user has a connection but is not using a license. This would happen if NDS walked the tree for some reason, such as reading a replica.
You cannot NWDSAuthenticate() without having first done a NWDSLogin(). You have to be logged into the tree before you can authenticate to a connection. You may want to think of NWDSLogin() as a tree-oriented API and NWDSAuthenticate() as connection-oriented. You could NWDSLogin() to a tree then use some API to get a connection to a server, checkout monitor, then NWDSAuthenticate()the connection and recheck monitor. You should be able to see the changes to the connection state. Supposedly, a connection should remain unlicensed unless a resource, like a mapped drive or captured printer, is used.
I had been checking monitor after login, but before doing anything. I understand that I won't see anything in monitor until I read from NDS, so it's a dynamic sort of thing. Now I run NWDSLogin and start reading the tree and I see a (*) by my user name.
The help is kind of misleading, since it says that the (*) means you're authenticated but not logged in but the way that translates into API use is you run NWDSLogin but not NWDSAuthenticate .
In summary, there are three states that a connection can have on a server. The not-logged is where a connection is made and nothing else is done. The (*) is an authenticated state, like the Monitor doc says. This state allows certain DS access to the server, normally no file services. The last state is like bindery where a license is used and the connection can get to not only NDS but the file system.
File Information
Self-Extracting File Name: INDSKBJ.EXE
|
Files Included: |
Size |
Date |
Time |
|
INDSKBJ.TXT |
(this file) |
||
|
INDSKBJ.MSG |
205 |
6-11-98 |
5:10 PM |
Sample Code - NWGetVolumeInfoWithNumber
|
Author: |
AJ |
|
Document ID: |
TID101714 |
|
Document revision: |
A |
|
Date: |
1998/06/12 9:47 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XVOL3.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
NLM sample code that logs into a remote server using cross platform calls. It prints out volume information for the requested server.
Detailed Description
The following steps are needed to log into a remote server and getting volume information for that specific server using NWGetVolumeInfoWithNumber() :
Initialize library (NWCallsInit()).
Create Context (NWDSCreateContextHandle()).
Set Context to the requested tree (NWDSSetContext()).
Login to a specific file server (NWDSLogin()).
Open Connection (NWCCOpenConnByName()).
Authenticate (NWDSAuthenticateConn()).
Get the volume number by using volume name (for example volume name = sys) (NWGetVolumeNumber() ).
Get Volume Information from the number obtained by the previous step (NWGetVolumeInfoWithNumber() ).
This program is an example of the steps above and it prints out the volume information. The function NWGetVolumeInfoWithNumber (along with other similar cross platform volume requests) requires an authenticated connection to the server.
File Information
Self-Extracting File Name: XVOL3.EXE
|
Files Included: |
Size |
Date |
Time |
|
XVOL3.TXT |
(this file) |
||
|
GETVOLIN.C |
14471 |
6-12-98 |
9:43 AM |
|
GETVOLIN.NLM |
8022 |
6-12-98 |
9:43 AM |
|
XVOL3.MSG |
136 |
6-12-98 |
9:43 AM |
Object API: Send Multiple Attachments (Delphi)
|
Author: |
WS |
|
Document ID: |
TID101726 |
|
Document revision: |
A |
|
Date: |
1998/06/19 3:26 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
D3GWATTC.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
D3GWAttc is a Delphi 2.x/3.x application that illustrates the use of Delphi to send multiple file attachments. To run the application, you need the GroupWise v5.x Client installed on your workstation.
|
Platform: |
Win95 / WinNT |
|
|
Tested with: |
Win95 / Delphi 2.01 & 3.0 / GW 5.22 |
|
|
Compilers: |
Borland Delphi 2.x/3.x |
|
|
Functions Used: |
D3GWMsgR demonstrates the following GroupWise Objects: |
|
|
Account |
||
|
Attachments |
||
|
Message |
File Information
Self-Extracting File Name: D3GWATTC.EXE
|
Files Included: |
Size |
Date |
Time |
|
D3GWATTC.TXT |
(this file) |
||
|
READ.ME |
453 |
6-19-98 |
3:23 AM |
|
MAIN.PAS |
4004 |
6-19-98 |
3:23 AM |
|
MAIN.DFM |
1605 |
6-19-98 |
3:23 AM |
|
MAIN.DCU |
4862 |
6-19-98 |
3:23 AM |
|
D3GWATTACH.RES |
876 |
6-19-98 |
3:23 AM |
|
D3GWATTACH.DOF |
932 |
6-19-98 |
3:23 AM |
|
D3GWATTACH.DSK |
1372 |
6-19-98 |
3:23 AM |
|
D3GWATTACH.DPR |
188 |
6-19-98 |
3:23 AM |
|
D3GWATTACH.EXE |
221696 |
6-19-98 |
3:23 AM |
|
D3GWATTC.MSG |
453 |
6-19-98 |
3:23 AM |
C++ Builder sample shows how to obtain a serial number
|
Author: |
HM |
|
Document ID: |
TID101712 |
|
Document revision: |
A |
|
Date: |
1998/06/11 5:09 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
CSER01.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
C++ Builder sample shows how to obtain a serial number on NetWare 3.x and 4.x (5.x will not support this feature) in a 32-bit environment.
Note: You will not be able to recompile this sample unaltered unless you are using C++ Builder 3. Remember to change the paths to the SDK in the project option.
File Information
Self-Extracting File Name: CSER01.EXE
|
Files Included: |
Size |
Date |
Time |
|
CSER01.TXT |
(this file) |
||
|
SERIALNUM.RES |
876 |
6-11-98 |
5:07 PM |
|
SERIALNUM.OBJ |
21973 |
6-11-98 |
5:07 PM |
|
SERIALNUM.EXE |
23552 |
6-11-98 |
5:07 PM |
|
SERIALNUM.DSK |
2636 |
6-11-98 |
5:07 PM |
|
SERIALNUM.CPP |
823 |
6-11-98 |
5:07 PM |
|
SERIALNUM.BPR |
5239 |
6-11-98 |
5:07 PM |
|
SERIALNUM.~CP |
823 |
6-11-98 |
5:07 PM |
|
SERIAL.~CP |
5639 |
6-11-98 |
5:07 PM |
|
SERIAL.OBJ |
48030 |
6-11-98 |
5:07 PM |
|
SERIAL.H |
929 |
6-11-98 |
5:07 PM |
|
SERIAL.DFM |
647 |
6-11-98 |
5:07 PM |
|
SERIAL.CPP |
5354 |
6-11-98 |
5:07 PM |
|
SERIAL.~H |
929 |
6-11-98 |
5:07 PM |
|
SERIAL.~DF |
647 |
6-11-98 |
5:07 PM |
|
SERIALNUM.~BP |
5239 |
6-11-98 |
5:07 PM |
|
CSER01.MSG |
302 |
6-11-98 |
5:07 PM |
The Meaning of MONITOR.NLM Connection Information Entries
|
Author: |
SP |
|
Document ID: |
TID101725 |
|
Document revision: |
A |
|
Date: |
1998/06/18 4:10 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
INWS001.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
An overview of the connection types visible in MONITOR.NLM.
Detailed Description
There are three types of connections listed in the Active Connections list:
NOT-LOGGED-IN
Where a connection is made (NWCCOpenConnByName()etc.) and nothing else is done.
*User
The * means that user has logged into the tree, and is performing NDS operations such as a tree walk. But the user has not authenticated the connection and is not using a license.
This state allows certain DS access to the server, but typically not file services. The user has a connection but is not using a license. Programmatically, the user program has called NWDSLogin() but not NWDSAuthenticate().
A connection should remain unlicensed unless a resource, like a mapped drive or captured printer, is used.
User
(No Asterisk) A connection has been made and authenticated. A license is used and the connection can get to not only NDS but the file system.
You cannot NWDSAuthenticate()without having first done a NWDSLogin()since you have to be logged into the tree before you can authenticate to a connection.
NWDSLogin()is a tree-oriented API and NWDSAuthenticate()is connection-oriented. So this user has logged into the tree and authenticated the connection.
File Information
Self-Extracting File Name: INWS001.EXE
|
Files Included: |
Size |
Date |
Time |
|
INWS001.TXT |
(this file) |
||
|
INWS001.TXT |
2690 |
6-18-98 |
4:06 PM |
|
INWS001.MSG |
60 |
6-18-98 |
4:06 PM |
Childthread Status
|
Author: |
BC |
|
Document ID: |
TID101718 |
|
Document revision: |
A |
|
Date: |
1998/06/16 8:38 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XTHD1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
These sample codes demonstrate the way to watch the child thread status.
Detailed Description
There are two sample codes, each of which demonstrates the way to watch up the child thread current status. One suspends the main thread; others set the flag for child thread.
File Information
Self-Extracting File Name: XTHD1.EXE
|
Files Included: |
Size |
Date |
Time |
|
XTHD1.TXT |
(this file) |
||
|
CHILDT2.C |
5388 |
6-16-98 |
8:35 AM |
|
CHILDT1.C |
5369 |
6-16-98 |
8:35 AM |
|
CHILDT1.NLM |
5578 |
6-16-98 |
8:35 AM |
|
CHILDT2.NLM |
5452 |
6-16-98 |
8:35 AM |
|
XTHD1.MSG |
73 |
6-16-98 |
8:35 AM |
Sample Code -- ScheduleSleepAESProcessEvent
|
Author: |
BC |
|
Document ID: |
TID101723 |
|
Document revision: |
A |
|
Date: |
1998/06/18 2:04 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XAES1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
The sample code shows the way to call an event that is scheduled to to be activated after a certain amount of time.
Detailed Description
The sample code demonstrates the way to register a procedure that is to be called by the Asynchronous Scheduler (AES) after a specified delay.
Also it shows the way to allocate the resource.
File Information
Self-Extracting File Name: XAES1.EXE
|
Files Included: |
Size |
Date |
Time |
|
XAES1.TXT |
(this file) |
||
|
SLEEP.NLM |
6204 |
6-18-98 |
2:02 PM |
|
SLEEP.C |
6164 |
6-18-98 |
2:02 PM |
|
XAES1.MSG |
118 |
6-18-98 |
2:02 PM |
Using NWDir with NAL
|
Author: |
MA |
|
Document ID: |
TID101697 |
|
Document revision: |
A |
|
Date: |
1998/06/1 11:24 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
NALCODES.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK |
|
Category: |
None |
Abstract
currententry.GetFieldValue('App:Associations', '', True) returns values with Novell Application Launcher.
Detailed Description
When using the NWDir control and executing currententry.GetFieldValue('App:Associations','',True), you receive an array of applications associated with the group in the format app.tree,number,number.
The last number is always zero and is reserved. The first number is a flag for the Application Launcher with the following values:
|
Place Application on Launcher |
1 |
|
Force Run |
2 |
|
Start Menu |
4 |
|
Desktop |
8 |
|
System Tray |
32 |
Seems a value of 16 should be there but . . . ?
File Information
Self-Extracting File Name: NALCODES.EXE
|
Files Included: |
Size |
Date |
Time |
|
NALCODES.TXT |
(this file) |
||
|
NALCODES.MSG |
82 |
6-1-98 |
11:22 AM |
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.