Developer Pointers
Articles and Tips: article
01 Oct 1996
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)
Telephony Services
Private Data Issue With MakePredictiveCall
|
Author: |
SP |
|
Document ID: |
TID100761 |
|
Document revision: |
A |
|
Date: |
8-22-96 10:45 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
NTSPDERR.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Telephony SDK |
Abstract
An error can occur with cstaMakePredictiveCallwhen AT&T private data is used and the switch is not configured correctly.
Detailed Description
Problem
When using cstaMakePredictiveCallwhere calling device is an ACD device and called device is an outgoing line, the function returns GENERIC_SUBSCRIBED_RESOURCE_AVAILABILITYerror when private data is used on an AT&T G3V4 switch.
Note: This problem is not meaningful unless the AT&T switch-specific private data is being used. The generic TSAPI call does not include the use of private data, so this problem will not occur.
Solution
The AT&T G3 switch includes an option for answering machine detection (answerTreatfield). If using AT&T private data, this field is mandatory and must be set to AT_NONE(let switch set the value), AT_DROP(drop if answering machine is detected), or AT_CONNECT(connect if answering machine is detected). Using any one of these options requires that the PBX has enabled answering machine detection capabilities at the switch. You cannot use any of the private data functions if this switch feature is not enabled.
File Information
Self-Extracting File Name: NTSPDERR.EXE
|
Files Included: |
Size |
Date |
Time |
|
NTSPDERR.TXT |
(this file) |
User Entered Code Monitoring on Definity G3
|
Document ID: |
TID100507 |
|
Document revision: |
A |
|
Date and time: |
5-23-96 9:37 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
DNTS1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: Telephony |
SDK |
Abstract
The following document ATTUDATA describes how to monitor a VDN on a Definity G3 for user-entered data. This text was not included in the Definity Programmer's Guide for release 2.21, but should be included in future releases.
File Information
Self-Extracting File Name: DNTS1.EXE
|
Files Included: |
Size |
Date |
Time |
|
DNTS1.TXT |
(thisfile) |
||
|
ATTUDATA |
2979 |
5-23-96 |
8:35 AM |
Intelligent Routing Using TSAPI
|
Author: |
SP |
|
Document ID: |
TID100729 |
|
Document revision: |
A |
|
Date: |
08/20/96 2:05 p.m. |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
NTSROUTE.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Telephony SDK |
Abstract
Hunt groups and ACDs may not route intelligently. Here's how to use software to make agent selection for call routing.
Detailed Description
A hunt group or ACD forwards calls to agents based on priority, or availability. This does not allow for intelligent selection of call routing based on additional user information. How do you set up a phone system where incoming or predictive calls are passed to a custom software application, and information in those calls is used to select the agent to receive the call?
Application call routing requires that the switch be configured to direct calls to a special type of device known as the "routing device." When a call arrives at a routing device, the switch sends a message to the Telephony Server requesting a route for that call.
This description assumes that an AT&T G3V4 switch is being used. For switch-specific information, contact your PBX vendor. See the Telephony PBX Partner's list for PBX contacts.
On the switch, set up a VDN (Vector Directory Number) which represents the logical device for receiving incoming calls or originating outgoing calls. The VDN has an associated vector (script) to enable adjunct routing to CTI. The vector script should contain three steps:
Route to ASAI device
Wait 60 seconds (silence or ringback)
Stop
The custom software should use the Application Call Routing functions to register itself as a router to the VDN device. To make predictive calls, use the VDN as the calling device. When the call is established, it will automatically go to the CTI link as per the vector instructions. Once the call is directed to the CTI link, it will be routed to the custom application, which registered itself as a router. Based on private data or other information, the application can then search through its own information about available agents and make an intelligent selection. The software then routes the call to the appropriate agent.
Incoming calls work the same way. Customers call the VDN number, which receives the call and routes it to the CTI link. The CTI link requests a route from the custom software, which provides a route to an agent based on user provided information, calling device, etc.
AgentID Queries
|
Document ID: |
TID100509 |
|
Document revision: |
A |
|
Date: |
5-24-96 10:16 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
INTS.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Telephony SDK |
Abstract
Query Agent State Issues for G3 switch.
File Information
Self-Extracting File Name: INTS.EXE
|
Files Included: |
Size |
Date |
Time |
|
AGENTID |
1150 |
5-24-96 |
9:15 AM |
|
INTS.TXT |
(thisfile) |
CSTA Universal Error 44
Symptom
CSTA Universal Error 44 OUTSTANDING_REQUEST_LIMIT_EXCEEDEDerrors.
Solution
If the error occurs with AnswerCall, the problem may be that the user's configuration has more than one TSERVER accessing the same PBX and monitoring the same device. This problem occurs if you exceed the number of domain controls on the device (configurable on the PBX).
In one environment, however, the error was seen even though only one TSERVER was used. In this case, the problem was due to a fault in the driver. Lucent Technologies provides an updated driver that corrects this problem of inappropriate error 44 returns. Novell does not supply the PBX driver. Contact your Lucent representative for more information on the driver versions available.
List All Telephony Servers
|
Document ID: |
TID100430 |
|
Document revision: |
A |
|
Date: |
2-12-96 10:37 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
TSERVLST.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Telephony SDK |
Abstract
The sample code in this TID shows how to enumerate all available TServers on the network using the acsEnumServerNames()call.
File Information
Self-Extracting File Name: TSERVLST.EXE
|
Files Included: |
Size |
Date |
Time |
|
TSERVLST.TXT |
(thisfile) |
||
|
TSERVERS.TXT |
128 |
2-12-96 |
10:35 PM |
|
TSERVERS.C |
3496 |
9-22-94 |
4:30 PM |
Client Communications
Creating Slist With APIs
|
Author: |
SW |
|
Document ID: |
TID100646 |
|
Document revision: |
A |
|
Date: |
7-18-96 3:45 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
WMYSLIST.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
none |
Abstract
The sample code shows how to get a list of all NetWare servers on the network. It uses the bindery information stored on the default server to provide this listing.
File Information
Self-Extracting File Name: WMYSLIST.EXE
|
Files Included: |
Size |
Date |
Time |
|
WMYSLIST.TXT |
(thisfile) |
||
|
MYSLIST.C |
852 |
3-22-95 |
2:02 PM |
|
MYSLIST.DSK |
2382 |
5-23-95 |
8:17 AM |
|
MYSLIST.EXE |
19871 |
5-23-95 |
8:14 AM |
|
MYSLIST.OBJ |
2294 |
5-23-95 |
8:14 AM |
|
MYSLIST.PRJ |
6145 |
5-23-95 |
8:14 AM |
NWSIPX32 for NT Requires 4.0 Requestor
|
Author: |
KB |
|
Document ID: |
TID100662 |
|
Document revision: |
A |
|
Date: |
7-29-96 9:02 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
SIPX32NT.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN32 |
Abstract
The NWSIPX32.LIB, the 32-bit IPX/SPX library for NT that ships in the released area on Release 8 of the NetWare SDK, requires the 4.0 version of the NetWare Requestor for NT.
Detailed Description
The NWSIPX32.LIB, the 32-bit IPX/SPX library for NT that ships in the released area on Release 8 of the NetWare SDK, requires the 4.0 version of the NetWare Requestor for NT. This client was available in closed beta in July of 1996. The open beta of this client is slated for late summer or early fall of 1996. See the Novell Web site for release date details (http://www.novell.com).
File Information
Self-Extracting File Name: SIPX32NT.EXE
|
Files Included: |
Size |
Date |
Time |
|
IPX32NT.TXT |
(thisfile) |
TLI and Multiple Boards
|
Author: |
DS |
|
Document ID: |
TID100658 |
|
Document revision: |
A |
|
Date: |
7-29-96 8:53 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
TIDTLI01.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - OS/2 |
Abstract
The ODI specification defines a logical board as a NIC / Frametype combination. TLI was implemented to work on board 0.
Detailed Description
The ODI specification defines a logical board as a NIC / Frametype combination. TLI was implemented to work on board 0. That means, for instance, if you have Ethernet_802.2 and Ethernet_802.3 loaded on a NIC, in that order, TLI will only work across Ethernet_802.2. If you needed to communicate over Ethernet_802.3, and binding the frametypes in another order is not an option, you should choose another communication vehicle besides TLI. NWSIPX, for example, offers the capability to communicate over any of the loaded logical boards.
File Information
Self-Extracting File Name: TIDTLI01.EXE
|
Files Included: |
Size |
Date |
Time |
|
TIDTLI01.TXT |
(thisfile) |
Delphi 1.x Source to Send/Receive IPX Packets
|
Author: |
WS |
|
Document ID: |
TID100763 |
|
Document revision: |
A |
|
Date: |
8-23-96 11:33 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
TESTIPX.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
This Delphi 1.x source shows how to send or retrieve IPX packets via NWIPXSPX.DLL.
Used APIs:
IPXCloseSocketIPXGetInternetworkAddress
IPXGetLocalTarget
IPXInitialize
IPXListenForPacket
IPXOpenSocket
IPXRelinquishControl
IPXSendPacket
IPXSPXDeinit
Detailed Description
This Delphi 1.x source shows how to send or retrieve IPX packets via NWIPXSPX.DLL.
Used APIs:
IPXCloseSocketIPXGetInternetworkAddress
IPXGetLocalTarget
IPXInitialize
IPXListenForPacket
IPXOpenSocket
IPXRelinquishControl
IPXSendPacket
IPXSPXDeinit
The source illustrates the use of the import library NWIPXSPX.PAS and has been developed for and tested with Borland Delphi v1.x_it will not work with 32-bit Delphi v2.x since NWIPXSPX.DLL is 16-bit only.
To run the program, start it on two machines on the same network segment. While one station sends packets as the "send" button is pressed, the other station waits to receive packets if the "wait for packets" button is pressed.
File Information
Self-Extracting File Name: TESTIPX.EXE
|
Files Included: |
Size |
Date |
Time |
|
TESTIPX.TXT |
(thisfile) |
||
|
FCT.DOC |
194 |
8-22-96 |
4:14 PM |
|
MAIN.DCU |
6016 |
8-22-96 |
4:15 PM |
|
MAIN.DFM |
698 |
8-22-96 |
3:57 PM |
|
MAIN.PAS |
4638 |
8-22-96 |
4:14 PM |
|
NETWARE.ICO |
766 |
12-1-95 |
10:26 PM |
|
NWIPXSPX.DCU |
9376 |
8-22-96 |
4:05 PM |
|
NWIPXSPX.PAS1 |
2720 |
8-19-96 |
8:50 PM |
|
TESTIPX.DPR1 |
89 |
8-22-96 |
1:52 PM |
|
TESTIPX.DSK |
3641 |
8-22-96 |
4:15 PM |
|
TESTIPX.OPT |
279 |
8-22-96 |
4:15 PM |
|
TESTIPX.RES |
794 |
8-22-96 |
4:15 PM |
Delphi Source IPX/SAP: Battle Ships
|
Author: |
WS |
|
Document ID: |
TID100791 |
|
Document revision: |
A |
|
Date: |
9-4-96 11:21 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
SHIPS3.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN16 |
Abstract
SHIPS is an IPX/SAP-based Delphi 16-bit network version of the "Battle Ships" game. The source shows how to establish peer-to-peer comunications with SAP, IPX, and Broadcast Messages using Delphi and illustrates the interface to NWIPXSPX.DLL. The executable can also be found as SHIPS1.EXE on CompuServe/NovUser.
File Information
Self-Extracting File Name: SHIPS3.EXE
|
Files Included: |
Size |
Date |
Time |
|
SHIPS3.TXT |
(thisfile) |
||
|
DELPHI_U.PAS |
15041 |
9-3-96 |
2:56 PM |
|
HOW-TO.DOC |
4462 |
7-16-96 |
6:45 PM |
|
NWIPXSPX.PAS |
12981 |
9-3-96 |
2:16 AM |
|
READ.ME |
1685 |
9-3-96 |
3:11 PM |
|
SHIPS.CUR |
326 |
9-3-96 |
2:20 AM |
|
SHIPS.DPR |
514 |
9-3-96 |
1:32 AM |
|
SHIPS.ICO |
766 |
9-3-96 |
1:30 AM |
|
SHIPS.OPT |
315 |
9-3-96 |
2:59 PM |
|
SHIPS.RES7 |
94 |
9-3-96 |
2:59 PM |
|
U_FNDPRT.DFM |
1113 |
9-3-96 |
2:21 AM |
|
U_FNDPRT.PAS |
3615 |
9-3-96 |
2:55 PM |
|
U_MAIN.DFM |
2276 |
9-3-96 |
12:51 PM |
|
U_MAIN.PAS |
34226 |
9-3-96 |
2:25 PM |
|
U_SELSRV.DFM |
1155 |
9-3-96 |
12:27 AM |
|
U_SELSRV.PAS |
3443 |
9-3-96 |
1:35 AM |
|
U_VARS.PAS |
1254 |
8-19-96 |
9:02 PM |
Information: NCP Conn. Failure Detection
|
Author: |
AJ |
|
Document ID: |
TID100792 |
|
Document revision: |
A |
|
Date: |
9-5-96 3:20 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
IABJ9695.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
This Q&A explains NetWare's philosophy on how a NetWare client can determine if an NCP connection is operational.
Q. How can a NetWare client (including an NLM running on a local server) that has a connection to a remote NetWare server tell when the remote server connection has been terminated?
A. The NetWare server has resources allocated to support each active NCP connection. A server periodically sends an unsolicited NCP "watchdog" packet to the NetWare client in order to verify that the client is still alive. The client sends a watchdog reply back to the server. This must be done so that server resources can be released for dead clients.
There is no "reverse watchdog" NCP. In other words, NetWare clients do not send unsolicited packets to NetWare servers on a periodic basis to ensure that the server is still available. Rather than implement "reverse watchdog," a client simply assumes that the connection is always valid unless proven otherwise while corresponding normally with the server. Client algorithms are configurable, but will generally make several "retry attempts" when the server does not respond. These attempts sometimes include killing the current NCP connection and creating a new NCP connection with the server. All of this client "NCP retry attempt" technology is transparent to the user and the currently executing application unless all retry attempts fail.
Thus, the best way for a NetWare client to verify that the NCP connection is still valid is to cause the client to make an NCP request to the specific NetWare server. Many developers use a function like NWGetServerDateAndTime()or NWGetFileServerVersionInfo()to cause the client to issue an NCP request to the server. If such functions succeed, the NCP connection is operational. These functions are popular because they require minimal server resources to fulfill. Specifically, the server can simply copy the required information to a reply NCP packet and return the requested information to the client.
File Information
Self-Extracting File Name: IABJ9695.EXE
|
Files Included: |
Size |
Date |
Time |
|
IABJ9695.TXT |
(thisfile) |
General
Client32 No Longer Supports EOJ
|
Author: |
KB |
|
Document ID: |
TID100661 |
|
Document revision: |
A |
|
Date: |
7-29-96 8:58 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
CNT32EOJ.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN32 |
Abstract
The Client32 Requestor for DOS/Windows and Windows 95 does not support the EOJ (End of Job) parameter.
Detailed Description
Client32 does not issue an EOJ packet when an application terminates. This deviates from the behavior of previous clients such as Netx and VLMs. This discrepancy in behavior breaks third-party products such as software metering packages that key off this behavior to determine when an application has terminated. This has been entered as a bug against Client32 on 7/26/96.
File Information
Self-Extracting File Name: CNT32EOJ.EXE
|
Files Included: |
Size |
Date |
Time |
|
CNT32EOJ.TXT |
(thisfile) |
NWALaunchFSFlagBrowser() and Context String
|
Author: |
KB |
|
Document ID: |
TID100667 |
|
Document revision: |
A |
|
Date: |
7-29-96 9:50 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
FSFBRWSR.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Directory Services |
Abstract
The NWALaunchFSFlatBrowser()returns invalid information for thefsContextStrvariable. Upon return from NWALaunchFSFlatBrowser(), the value of this string should be the VOL:Path of the selected file system component.
Detailed Description
The NWALaunchFSFlatBrowser()returns invalid information for the fsContextStrvariable. Upon return from NWALaunchFSFlatBrowser(), the value of this string should be the VOL:Path of the selected file system component. Currently, with the NetWare Green River beta release of NWAdmin, this variable is set to the same value as dsContextStr. The NetWare 4.1 version of NWAdmin exhibits a different bug with this function. The values for fsContextStrand dsContextStrnever change from their original values when different locations are traversed and selected within the file system flat browser. This bug was not fixed in the NetWare 4.1 version of NWAdmin. The Green River versions of NWAdmin do change the dsContextstring to reflect the accurate location of the NDS volume object. The bug with fsContextStrhas been reported to engineering and should be fixed by the first customer shipping of the Green River version of NetWare.
File Information
Self-Extracting File Name: FSFBRWSR.EXE
|
Files Included: |
Size |
Date |
Time |
|
FSFBRWSR.TXT |
(thisfile) |
How to Execute a Login Script From Win95
|
Author: |
KB |
|
Document ID: |
TID100664 |
|
Document revision: |
A |
|
Date: |
7-29-96 9:10 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
LOGSCRPT.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Client SDK - WIN32 |
Abstract
The current NetWare SDK (Release 8) does not provide a login API that will execute a login script. The Novell Client32 GUI login WLOGIN95.EXE can be executed with appropriate command line parameters to execute a login script.
Detailed Description
The current NetWare SDK (Release 8) does not provide a login API that will execute a login script. The Novell Client32 GUI login WLOGIN95.EXE can be executed with appropriate command line parameters to execute a login script. This allows software developers to write their own login utility and launch Novell's WLOGIN95.EXE just to execute the script. Use the Win32 API CreateProcess()to spawn WLOGIN95.EXE with the following syntax: WLOGIN95 SERVER_NAME/USER_NAME /NA /CONT. The two command line parameters indicate to WLOGIN95 that the user specified on the command line is already authenticated to the specified server and to continue without displaying the GUI logon dialog. The script window will be displayed as the script is executed and then closed.
File Information
Self-Extracting File Name: LOGSCRPT.EXE
|
Files Included: |
Size |
Date |
Time |
|
LOGSCRPT.TXT |
(thisfile) |
NEST 1.2 Packet-Signing Fixes_Big Endian
|
Author: |
MG |
|
Document ID: |
TID100834 |
|
Document revision: |
A |
|
Date: |
9-6-96 5:18 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
MGTIDO.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
NEST SDK |
Abstract
READ ME file for fixes to NEST 1.2 for packet signing on big endian machines.
File Information
Self-Extracting File Name: MGTIDO.EXE
|
Files Included: |
Size |
Date |
Time |
|
MGTIDO.TXT |
(thisfile) |
||
|
REQ.LOG |
3270 |
9-6-96 |
2:31 PM |
|
SIGNFIX.ZIP |
23469 |
9-5-96 |
10:06 AM |
NDS Functions Return 0x889A on Client32
|
Author: |
KB |
|
Document ID: |
TID100831 |
|
Document revision: |
A |
|
Date: |
9-6-96 5:17 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
NDSC32.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Directory Services |
Abstract
Applications that use the NWDS API functions may return error code 0x889A (RESOLVE_SVC_PARTIAL)when the Client32 software is loaded. This error is equivalent to 0xFDA7(-601) NO SUCH ENTRY.
Detailed Description
Applications that use the NWDS API functions may return error code 0x889A (RESOLVE_SVC_PARTIAL)when the Client32 software is loaded. This error is equivalent to 0xFDA7(-601) NO SUCH ENTRY. In the event that this error is returned, ensure that the combination of the value for DCK_NAME_CONTEXTand of the object name passed to the NWDS function is a valid path to reference the object.
File Information
Self-Extracting File Name: NDSC32.EXE
|
Files Included: |
Size |
Date |
Time |
|
NDSC32.TXT |
(thisfile) |
Example for NWDSReadObjectInfo()
|
Author: |
MO |
|
Document ID: |
TID100833 |
|
Document revision: |
A |
|
Date: |
9-6-96 5:18 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XDSAG.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
NWDSReadObjectInfo()allows a user to be able to determine if an object exists or not. This is a simple example to show usage for this call.
File Information
Self-Extracting File Name: XDSAG.EXE
|
Files Included: |
Size |
Date |
Time |
|
XDSAG.TXT |
(thisfile) |
||
|
ROI.C |
4772 |
9-6-96 |
1:58 PM |
|
ROI.NLM |
1955 |
12-20-95 |
12:43 PM |
Base Schema Extensions Are Nonremovable
|
Author: |
KB |
|
Document ID: |
TID100674 |
|
Document revision: |
A |
|
Date: |
7-31-96 8:00 AM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
SCHMRMOV.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Directory Services |
Abstract
NDS Schema Extensions made to the base NDS schema cannot be removed.
Detailed Description
NDS Schema Extensions made to the base NDS schema cannot be removed. For example, if the NDS Schema API functions are used to add a new attribute class definition such as "Photo" to the exising base class "User," this attribute class definition cannot be removed from the object class "User." Attribute class definitions that are added to new, extended object classes can be removed. For example, if the NDS Schema API functions are used to extend the NDS schema to include a new object class "Fax Server" and a new attribute class definition "Operator" is added to object class "Fax Server," this attribute class definition can be removed at a later time. This is true for the implementation of the NDS database up to and including NetWare 4.1 and the Green River release of NetWare.
File Information
Self-Extracting File Name: SCHMRMOV.EXE
|
Files Included: |
Size |
Date |
Time |
|
SCHMRMOV.TXT |
(thisfile) |
CLX Connection Calls
|
Author: |
MO |
|
Document ID: |
TID100828 |
|
Document revision: |
A |
|
Date: |
9-6-96 5:16 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XCLX1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
This sample code demonstrates how to use the CLX connection calls on the NLM platform. NWCCOpenConnByName(), CCSysCloseConnRef(), NWCCCloseConn(), and NWCCUnlicenseConn()are all represented. Each call has its own personality and function to handle connection caching from discrete vantage points. The attached file xclx1.zip needs to be unzipped with a -d option to preserve directories.
File Information
Self-Extracting File Name: XCLX1.EXE
|
Files Included: |
Size |
Date |
Time |
|
XCLX1.TXT |
(thisfile) |
||
|
XCLX1.ZIP |
67977 |
9-6-96 |
1:42 PM |
DCK_NAME_CONTEXT and Canonicalizing
|
Author: |
MO |
|
Document ID: |
TID100832 |
|
Document revision: |
A |
|
Date: |
9/6/96 5:17 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XDSC1.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
NWDSCanonicalizeName()leverages the DCK_NAME_CONTEXTto resolve a relative distinguished name to a distinguished name. This sample helps the learning process and demonstrates how these two components interact.
File Information
Self-Extracting File Name: XDSC1.EXE
|
Files Included: |
Size |
Date |
Time |
|
XDSC1.TXT |
(thisfile) |
||
|
CANON.C |
3643 |
9-6-96 |
1:52 PM |
|
CANON.NLM |
1845 |
9-6-96 |
1:52 PM |
NDS Replica List Dump
|
Author: |
MO |
|
Document ID: |
TID100825 |
|
Document revision: |
A |
|
Date: |
9-6-96 5:15 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XDSM2.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
This example demonstrates how to get to an NDS replica list for a partition. This example is unicode enabled and takes as a command line parameter whether to work in unicode or in xlated strings. It is a good reference piece to take unicode handling to other applications.
File Information
Self-Extracting File Name: XDSM2.EXE
|
Files Included: |
Size |
Date |
Time |
|
XDSM2.TXT |
(thisfile) |
||
|
DSACCESS.C |
33837 |
4-13-95 |
8:25 AM |
|
DSACCESS.H |
4407 |
4-12-95 |
7:38 PM |
|
REPLICA.C |
8525 |
9-6-96 |
1:00 PM |
|
REPLICA.H |
708 |
3-8-95 |
8:58 AM |
|
REPLICA.NLM |
7886 |
4-13-95 |
9:30 AM |
Dumps Class and Attribute Definitions to File
|
Author: |
MO |
|
Document ID: |
TID100826 |
|
Document revision: |
A |
|
Date: |
9-6-96 5:16 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XDSS5.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
This example is another demonstration of reading NDS schema. This particular example dumps the schema names only to a file. This example can easily be modified to dump all definition information. XDSS1.exe, however, provides a NWSNUT interface to schema that displays schema definitions in a more user-friendly way.
File Information
Self-Extracting File Name: XDSS5.EXE
|
Files Included: |
Size |
Date |
Time |
|
XDSS5.TXT |
(thisfile) |
||
|
SCHEM.C |
4511 |
12-7-95 |
3:22 PM |
|
SCHEM.NLM |
2212 |
12-7-95 |
3:23 PM |
Demonstration on Adding a Schema Class Def
|
Author: |
MO |
|
Document ID: |
TID100829 |
|
Document revision: |
A |
|
Date: |
9-6-96 5:16 PM |
|
Alert status: |
Yellow |
|
Information type: |
Issue |
|
Readme for: |
XDSS6.EXE |
|
Novell product class: |
NetWare API |
|
Novell product and version: |
NetWare SDK 1.0e |
|
Category: |
Server |
Abstract
NDS schema can be extended in NDS. This example shows the sequence of APIs necessary to create a simple class definition devsup:test. Notice that the schema name includes a "devsup:" prefix ending in a colon. Novell keeps an NDS schema registry to ensure unique names in the flat schema name space. See http://developer.novell.comfor information on registering schema.
File Information
Self-Extracting File Name: XDSS6.EXE
|
Files Included: |
Size |
Date |
Time |
|
XDSS6.TXT |
(thisfile) |
||
|
CRCLS.C |
6490 |
9-6-96 |
1:21 PM |
|
CRCLS.NLM |
2572 |
9-6-96 |
1:21 PM |
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.