#pragma pack 1

Memory Allocation

Linking Mixed-Address Applications

IPX/SPX Communication Services under OS/2 and its dependents (as well as Novell's implementations of NetBIOS and Named Pipes) make use of 16-bit semaphores. When linking these types of applications, the migration libraries which contain 16-bit semaphores should be used (i.e., OS2386.LIB which comes with IBM's CSET/2 compiler).

For More Information

To purchase this SDK or any other Novell development tools, contact Novell Developer Relations at 1-800-NETWARE or 1-801- 429-5588.

TECHNICAL INSIGHTS:

New AIOCOMX.NLM Driver Available (Network C for NLMs v2.0 (d))

Outer Joins on Computed Fields (NetWare SQL v3.0)

        CREATE VIEW Test (T1, T2)
        AS SELECT F1, 100 FROM Tbl1

        SELECT * FROM Test, Tbl2
        WHERE Test.T2 = Tbl2.fld(+)

Currently, a problem associated with NetWare SQL v3.0b causes the above SELECT statement to return an status 875 (Only a right Outer Join Is Supported), even if "Tbl2.fld" is a four- byte integer and an index.

To alleviate this problem, create the view at the Relational Primitive level instead of using SQL statements. Use the xCompute function to specify the computed field, since the xCompute function has parameters that allow the application to specify both the type and size of the resulting field. In this case, the computed field can be created as either a two- or four-byte integer, whichever is needed for the outer join.

Using the T_MORE Flag with SPX Protocol (Network C for NLMs v2.0 (e))

The T_MORE flag determines how the t_rcv() returns. If you call t_snd() with the T_MORE flag clear, t_rcv() will return with only a portion of its buffer filled. If you set the T_MORE flag, t_rcv() will not return, and will wait for more of its buffer to be filled.

Network C for NLMs Documentation Error (Network C for NLMs v2.0 (x))

When creating the globalString global variable assign a value to the string. Doing so will prevent the string from being set to NULL before the program executes.

Correct Usage of Btrieve Operation 42 (NetWare Btrieve (NLM) v6.0)

NetWare System Calls Doumentation Update (NetWare System Calls for DOS v1.2)

Closing Temporary Socket in BeginDiagnostics() (NetWare C Interface for DOS v1.2)

To prevent failure of BeginDiagnostics(), modify the source code for DIAG.C as shown in Figure 6, so that IPXCloseSocket() is called when an error occurs.

FIGURE 6: Required modifications to DIAG.C

int BeginDiagnostics(destination, connectionID, componentList )
*
 /* first open a socket then init receive ECB's */
 tempSocket = (WORD)0x00;    /* let IPX pick socket number */
  ccode = IPXOpenSocket((BYTE)&tempSocket, 0);

  /* call to function */
  if( (ccode = GetRemoteSPXSocket(destination,componentList))
!= 0 )
   Error = COULD_NOT_OPEN_SOCKET;
  else
  {
    for (i=0; i

File in DOS Partition Fails to Truncate (Network C for NLMs v2.0 (d))
Specifying a length that is shorter than the file length on a call to DOSWrite() does not
cause the file to truncate to the new length. To illustrate, consider the following sequence of
events:
  DOSOpen(), DOSRead(), DOSClose()
 Data was modified
 DOSOpen(), DOSWrite(), DOSClose()
 Examination of file reveals no change in file length has occured
In this example, a file in the DOS partition of a NetWare file server that contains five
lines. The application NLM reads the five lines and modifies the data to only have four lines and
writes it back out. Later, viewing the file again indicates that the fifth line is still in the file.

The DOSWrite API writes data to a particular offset for a particlar length. In order to
"rewrite" a file, the second DOSOpen() call listed in above example must be changed to
DOSCreate(). The NLM Reference, Volume 2 states that DOSCreate() will truncate an existing
file or create a file if it does not exist. The call to DOSCreate() returns a file handle that can be
used on subsequent calls to DOSWrite() and DOSClose().

Brequest v6.0 /L Option (NetWare Btrieve (NLM) v6.00x)
In Brequest v6.0x, an new undocumented load option, /L, allows you to load another
instance of Brequest even if Brequest is already loaded. This option is useful if you want to run
Windows applications utilizing the Btrieve requester while running DOS VM applications that
use Brequest.

To run Windows applications that use the Btrieve requester, Brequest must be loaded before
starting Windows. In order to run DOS applications in Windows, Brequest must be loaded in
each DOS session. However, if Brequest is loaded outside of Windows, it cannot be loaded again
in a DOS session.

For Windows applications utilizing the Btrieve requester, load Brequest outside of Windows. In
each Windows DOS session that will be running a Btrieve application, load Brequest with the /L
option. Doing so will load another instance of Brequest that is only available to the DOS session.
Doing so provides the DOS session with its own copy of Brequest and prevents the DOS session
from using the instance of Brequest that was loaded before Windows was started.

TTSTransactionStatus() Requires LongSwap() (Network C for NLMs v2.0 (e))
When using TTSTransactionStatus() on a local server, CLib does not long swap the
transaction number. An incorrect transaction number will result in one of two problems. Either
the TTSTransactionStatus() call will erroneously report that the transaction has completed, or it
will show that the transaction has never completed.

With CLib v3.11(d) and earlier, when using the TTSTransactionStatus() call on a local server,
LongSwap() the transaction number to avoid this situation.

NetWare SQL Updates & Indexed Fields (NetWare SQL v3.00b)
If you send NetWare SQL an UPDATE SQL statement with a restriction based on a field
that is an index, only the first record matching the restriction will be updated. For example,
        UPDATE Appointments SET
        Amount^Due = 0.00 WHERE ID > 0

will only update the first record having ID > 0, if ID is an index in the "Appointments" table. No
other records will be updated.
This situation was introduced by the NetWare SQL December patch release (v3.00b) and will be
fixed in patch release v3.00c. Currently, the only workaround is to use NetWare SQL with the
September patch release installed (v3.00a).

Mux Semaphores and SPX (NetWare OS/2 Developer's Kit v2.0)
Under OS/2, if you issue a "wait" command on mux semaphores with one of the
semaphores in the mux list being the ECB semaphore, the apparent result is that the ECB
semaphore never clears. Actually, the semaphore is cleared and reset by SPX, but the application
is never notified. This situation results in the "wait" never returning if it is set to "infinite."

The situation does not occur with event or mutex semaphores. If you need to wait on more than
one semaphore, create multiple threads that individually block one each on each semaphore.

File Level Access with Brequest v5.16 & v6.0 (NetWare Btrieve (NLM) v6.0)
With Brequest v5.16, users are allowed to write to a Btrieve file if the user has "Write"
access to the directory, even if the user does not have "Write" access to the file.

This situation does not occur with Brequest v6.0, since Brequest v6.0 uses file-level access rather
than directory- level access. If a user has "RWCEMFA" access to a directory but only "RF" (read
and file scan) access to a file, Brequest v6.0 returns a status 94 (Permission Error) on the Open
operation.

"Supervisor" access to a directory works differently. If a user has "Supervisor" access, any file
can be opened regardless of which requester is in use. "Supervisor" rights override all inherited
rights masks in subdirectories and files.

Driver Load Order with LANSUP and OS/2 v2.0 (NetWare OS/2 Requester v2.0)
When using the OS/2 driver LANSUP (the Open DataLink Interface that allows multiple
protocols on an OS/2 machine from IBM), the order in which the drivers are loaded is different
than if ODINSUP is used. If you load the drivers in the wrong order, one of three situations will
result:
  The machine fails to load the operating system.
 The machine successfully loads the operating system, but reports numerous driver errors.
 The machine sucessfullly initializes (without errors), but no NetWare services are
available because the wrong protocols have been bound to the NIC.
To avoid problems with LANSUP, load the drivers in CONFIG.SYS in the order shown in
Figure 7.
    FIGURE 7: Correct driver load order when using LANSUP driver
device=lsl.sys
run=ddaemon.exe
DEVICE=LANSUP.SYS
device=ipx.sys
device=spx.sys
run=spdaemon.exe
device=nmpipe.sys
device=npserver.sys
run=npdaemon.exe
...

END of FIGURE 7


Int 21 Function 3F Bug in NETX.EXE (NetWare Shell (NETX.EXE) v3.31)
If a section of a file is locked with Int 21 function 5C00 and another workstation using that
file tries to read from the locked area, the call appears to succeed, even though it should fail. The
carry flag should be set and an error code should be returned in the AX register. The error code
(5, in this case) is being returned, but the carry flag is not being set, so the contents of the AX
register are processed as the number of bytes read rather than as an error code. In this case, it is
impossible to tell if an error has occurred.

This bug has been detected in v3.26 and v3.31 of NETX.EXE, and may exist in others versions.

Continuous Operations and File Logging (NetWare SQL v3.0)
File logging and backups can both be used to rebuild Btrieve files after a system failure.
However, file logging and Continuous Operations mode should never be used simultaneously.

Btrieve v6.0 Continuous Operations mode allows continuous access to Btrieve files while the
files are being backed up. When a file is open in Continuous Operation mode, the log file is still
being updated. If you activate logging and place the file in Continuous Operations mode, at some
point the file will no longer be synchronized with the log file.

To illustrate, consider the following sequence of events:
  A Btrieve file is backed up
 File logging is activated
 The file is modified (update, delete, or insert operation)
 The file is placed in Continuous Operations mode
 The file is modified again
 Backup completes and the file is removed from Continuous Operations mode
At this point, if a a backup was required, the backup from step 4 would be restored. The
backup would reflect all the changes that were made in step 3. The log file, however, would
contain both the changes made in step 3 and step 5. If you used the log file at a later date, you
would be making the same modifications to the file and such duplication could result in errors.

ScrollScreenRegionUp() overwrites memory (Network C for NLMs v2.0 (e))
ScrollScreenRegionUp() can overwrite memory if used on line 0, with the title bar
active.In other words, ScrollScreenRegionUp(0,1) while you have the  key down will
cause this to occur. If you scroll more than one line, the problem does not occur.

To prevent memory overwrites, either write spaces to line 0, or always scroll more than one line.

XQL and .SHR Files (XQL for DOS v2.11)
In the December 1992 issue of Bullets, "Handle Usage with User Rights & XQL Load"
described how XQL creates and maintains a .SHR file. Another anomaly has been found
regarding this issue.

If XQL is patched so that it can be accessed from within Windows, and then is loaded from the
WINSTART.BAT file, XQL's .SHR file is created in the user's current directory when Windows
is started. Later, if a user opens a DOS session and tries to load XQL again from the same
directory, one of two situations will occur:
  If DOS SHARE was loaded before Windows, a Sharing Violation Error will be
returned and XQL will not load.
 If DOS SHARE was not loaded, XQL will overwrite the .SHR file already present with a
new .SHR file. Subsequently unloading XQL from this DOS session will cause this .SHR file to
be deleted, leaving the XQL that was loaded by WINSTART.BAT without an .SHR file to use.
This situation will eventually cause status 202 or 821 (Invalid Cursor ID) errors to be returned.
The previous situations occur only when the .SHR files are created on a local drive. If the
current working directory is a NetWare drive, neither situation occurs; two .SHR files are
properly created and maintained in the same NetWare directory.

If using a local drive, either load XQL inside the DOS session from a different directory than the
current working directory from which Windows was started, or specify an /x: parameter on the
XQL load line pointing to a different directory. For more information on the /x: parameter,
consult the December 1992 issue of Bullets.

Events Cannot Be Unregistered While In Progress (Network C for NLMs v2.0)
When you register for an event "Down File Server", you provide it with a report procedure
and a "warn" procedure to execute. If you attempt to call UnRegisterForEvent() for "Down File
Server" in either of these functions, it will fail with a return code of (-1).

You cannot call UnRegisterForEvent() while the event is occurring. In the case of the "Down
File Server" event, it is unnecessary to unregister the event if the file server is going down.

min() & max() are Both Macros and Functions (Network C for NLMs v2.0 (d))
The functions min() and max() are defined as macros in STREAM.H, but are prototyped
as functions in STDLIB.H. If STREAM.H is included before STDLIB.H, the compiler attempts
to expand the prototype in STDLIB.H with the macro from STREAM.H. This situation results in
syntax errors in STDLIB.H.

To avoid problems, either always include STREAM.H after STDLIB.H, or modify STDLIB.H
by replacing the prototypes with copies of the macro definitions from STREAM.H.

NWSTRM.H Header File Redefines delay() (Network C for NLMs v2.0)
NWSTRM.H redefines delay() to be streamdelay() which takes ticks instead of
milliseconds. Thus, a call to delay(55) will not delay for one tick, but will delay for 55 ticks.

Currently, there is no "clean" workaround for this situation. Until further notice, call delay() from
a module that does not include NWSTRM.H. Otherwise, you will need to modify the header file.

Blank Users Cause Security Problems (Xtrieve PLUS v4.1x)
Recent versions of Xtrieve PLUS do not support blank users; if a blank user exists in the
USER.DDF data dictionary file, then whenever Xtrieve PLUS is loaded, a status 205 (Invalid
Password) will be returned.

This error message is returned when Xtrieve PLUS logs into a set of .DDF files. Xtrieve PLUS
first attempts an xLogin to the dictionaries. If a status 209 (Invalid User) is returned, Xtrieve
PLUS attempts another xLogin, prompting for a username and a password. If anything other than
a status 209 is returned on the first xLogin call, Xtrieve PLUS will not prompt the user for the
username and password.

When Xtrieve PLUS attempts its first xLogin call, it always passes a blank username and a blank
password. Normally, this would return status 209 on a dictionary with security installed, but
since there is actually a blank entry in the USER.DDF file, a status 205 is returned instead. Since
Xtrieve PLUS does not trap for anything but a status 209 on the xLogin, the status 205 would be
relayed to the Xtrieve PLUS user.

It is interesting to note that XQLI will prompt for a username and password if security is
installed on the data dictionary files, without attempting an initial XQLLogin call. XQLI will
prompt the user for a password even if the user name is blank. So, the status 205 will not occur
when logging in through XQLI, unless the password specified is actually invalid.

To prevent the status 205, remove the blank user from USER.DDF using BSIM.EXE, B.EXE, or
any utility that provides Btrieve or XQLP function calls. The .DDF files have Btrieve owner
names defined for them when security is installed. The Btrieve owner name on the .DDF files is
the same as the Master password specified when security was installed. You can check
USER.DDF for a blank user by generating an ASCII file with BUTIL -SAVE on key path 0. If
there is a blank user, then read and delete the record with the blank user using a Btrieve or XQL
utility.

NSD201 Interferes with NWTools (NetWare OS/2 Requester v2.0)
'NWTools script files (.NWS files) created with version 2.0a of the OS/2 Requester will
not run properly after the drivers are updated with the OS/2 v2.0 requester patch file (NSD201).
Specific examples include not being able to attach to a server with an .NWS file.
This situation is apparently caused by NWTOOLS.EXE and NWTOOLS.DLL, which are
included with NSD201. New script files may also function incorrectly. To ensure that script files
work properly, save a backup of NWTOOLS.EXE and NWTOOLS.DLL before installing
NSD201. Otherwise, install the latest version, NSD202, which is fully compatible with the files
mentioned above.
NIBBLES AND BITS
Fast Answers to Common Questions
Network C for NLMs
Q -  When I try to retrieve the status for a Macintosh file in the root directory, the
stat() function returns "0" rather than "1" for the st_originatingNameSpace field. What should I
do?
A -    If you need to obtain originating name space for a Macintosh file, use
AFPDirectoryEntry() instead.
NetWare C Interface for DOS
Q -  How can I get the System UP time for a NetWare v3.11 server from a client
application?
A -    In the NetWare 3.x and 4.0 environments, you have to write an NLM to be placed
in the AUTOEXEC.NCF file that reads the system time and writes it to a text file. Then, the
client applcation must read this text file and the current system time on the fileserver and subtract
the current time from the time that was recorded by the NLM.
NetWare C Interface for Windows
Q -  No matter what structure size I specify in GetServerInformation() under
Windows, it always returns 128 bytes of data. What should I do?
A -    Always allocate at least 128 bytes for the received statistics buffer to avoid
overwriting memory.
NACS/NASI
Q -  My NASI application has run fine under NACS/NASI v2.x, but seems to hang
under NACS/NASI v3.x.
A -    The reply buffer to the call Query Name Service (function 0x21) is 32 bytes long.
The current documentation (Sept. 1988, Rev. 2.06) shows the reply buffer as 30 bytes. The extra
two bytes are at the end of the reply buffer and have the following values:
31: Port number located by query
32: Port status:

     0x00:Port Idle

     0x01:Port Down (hardware fail)

     0x02:Port Connected (no data transfer yet)

     0x03:Port Suspended (on hold)

     0x04:Port Busy (data being transfered)
Q -   Under NACS/NASI v3.00, a call to Query Name Service (function 0x21)
returns only those ports which are not connected. How can I retrieve all ports?
A -    Download the PTF-359 patch file from CompuServe (NOVLIB, LIB 9). This
patch will add the necessary functionality to the Query Name Service call. Then, when the Query
Name Service is called, all ports will be returned and the 32nd byte of the Query Name Service
reply buffer will indicate the port status:
0x00:Port Idle
0x01:Port Down (hardware failure)

0x02:Port Connected (no data transfer yet)

0x03:Port Suspended (on hold)

0x04:Port Busy (data being transferred)
NetWare OS/2 Developer's Kit
Q -  When I call PeekPipe() and ReadPipe() with a zero buffer length specified, the
pipe is disconnected and error 109, "Pipe Broken," is returned, even on a valid pipe. What should
I do?
A -    Specify that a buffer of at least one byte is used. In the case of the peek, doing so
will not cause a problem, since the contents are left in the pipe anyway.
NetWare Btrieve
Q -  What version of the Btrieve reques-ter should I use with BSERVER.VAP v5.15
on NetWare 2.2?
A -    For all versions of NetWare Btrieve (VAP or NLM), you should have the latest
Btrieve requester loaded at each workstation. The latest versions are:
  Btrieve Requester for DOS (BREQUEST.EXE) v6.00b
 Btrieve Requester for OS/2 (BTRCALLS.DLL) v6.00b
 Btrieve Requester for Windows (WBTRCALL.DLL) v6.00c
Windows
Q -  How can I determine if a DOS application is running under Windows?
A -    The assembly code in Figure 8 demonstrates an interrupt that determines if a DOS
application is running under Windows v3.1.

    FIGURE 8: Determining if a DOS application is running under Windows v3.1
mov     ax, 160ah     ;
int     2fh           ; Check if in Windows 3.1 DOS box
or      ax, ax        ;
jz      Windows31     ; Jump if Windows 3.1

END of FIGURE 8
This function call also will determine if Windows v3.1 is running in 386 Enhanced Mode
or Standard Mode. If the function determines that Windows v3.1 is running, it sets CX equal to
two if Windows is running in Standard Mode. If Windows is running in Enhanced mode, it sets
CX equal to three.
BRAINSHARE  1993
March 22-26

Salt Lake City, Utah

A special supplement to

Novell Professional Developer B U L L E T S

BrainShare '93 is your chance to hook up with the leading technical experts in the network
computing industry. This technical development conference brings together the industry's top
minds in development, integration and support with the top technical minds at Novell for the
most informative, comprehensive event of its kind in the network computing industry. More than
2,000 people attended BrainShare '92, and BrainShare '93 promises to be bigger and better than
ever. 
Who Should Attend
BrainShare '93 offers a valuable opportunity to anyone who develops or supports network
computing solutions. If you're a software or hardware developer, member of a support staff,
systems integrator or consultant, Certified NetWare Engineer, Certified NetWare Instructor, or
company executive, you shouldn't miss this gathering of network computing professionals.
Technical Content
The conference features more than 235 technical breakout sessions dealing with all phases
of NetWare development, integration and support. These sessions are presented by the Novell
architects and engineers who write and support NetWare, so you get the information you need
straight from the experts. NetWare v4.0, the industry's first distributed operating system for local
area networks, will be a featured topic.

Breakout sessions will be presented at BrainShare on the following topics:

Accessing host systems
Building a secure and reliable network
Certified NetWare Instructors
Client application development
Client-server development
Communications
Database technologies
Directory Services
Hardware support issues
International issues
Macintosh connectivity
Messaging and E-mail
The NetWare desktop
NetWare hubs and routers
NetWare Loadable Module development
The NetWare operating system
NetWare transports and protocols
Network management
New NetWare technologies
Service and support
Systems integration issues
UNIX
UnixWare
Wide area networks

BrainShare '93 will be held on the University of Utah campus. The conference will take over a
majority of the campus, utilizing 25 classrooms for the technical breakout sessions. In response
to requests from last year's conference attendees, many of the sessions have been extended in
length, to allow for greater technical content. Technical breakout sessions have also been
extended into Friday afternoon, giving you more access to the sessions.
BrainShare Scheduler Utility
With over 235 breakout sessions from which to choose, scheduling your week could be a
nightmare. To make scheduling your week easier, BrainShare provides the BrainShare
Scheduler. This GUI utility, available for Windows v3.1 and OS/2 v2.0, allows to interactively
schedule the breakout sessions you want to attend. With it you can access all session abstracts,
with cross referencing tools and filters available.

The result of using the utility is a printed schedule. After returning the printed schedule to the
BrainShare registration office, you will receive tickets to the sessions you have selected. These
tickets give you priority access to the sessions. Attendees without tickets will not be allowed into
the classrooms until five minutes before the start of each session. This insures that you get the
technical information you need and get the most from the BrainShare conference.
Keynotes
BrainShare '93 features outstanding industry luminaries. Here's the lineup:
Monday          Bob Supnik      V.P. & Tech. Director of Engineering
                                Digital Equipment Corporation

Tuesday         John Landry     Chief Tech. Officer & VP Development
                                Lotus Development Corporation

Wednesday       Philippe Kahn   President & Chief Executive Officer
                                Borland International, Inc.

Thursday        John Sculley    Chairman, CEO & Technology Officer
                                Apple Computer, Inc.

Friday          John Edwards    Executive V.P. & General Manager,
                                Desktop Systems Group, Novell, Inc.

                 Drew Major      Senior Scientist & Systems Architect
                                 Novell, Inc.
Friday's General Session
There are a few suprises in store for attendees at Friday's general session. John Edwards
will start the morning with a strategic perspecitive on Novell and NetWare, especially as they are
affected by the USL announcement. Drew Major will again be giving us his vision on the future
of the NetWare operating system.

The Management Q & A Panel is your best opportunity to get direct feedback from Novell
executives. At the conclusion of the Management Q & A there will be several valuable prizes
awarded to attendees. Since you must be present to win, you won't want to miss this opportunity.
NetWare 4.0
NetWare 4.0 will be a major topic of discussion at BrainShare '93. As an added bonus, all
attendees will receive a CD containing NetWare 4.0. This limited-used version will give you the
head start you need in developing enterprise-wide applications or learning to install and maintan
this next generation operating system.
Labs
BrainShare '93 retains many of the features of past Novell technical conferences. The
BrainShare Lab will again demonstrate solutions to real customer problems, using the latest
NetWare technologies and products.

One of the most exciting new features of BrainShare '93 is the addition of the Certified NetWare
Engineer Professional Association (CNEPA) Hands-On Lab. Hands-on sessions will cover a
variety of subjects, including:

Advanced NetWare printing
Tuning and optimization
PC/UNIX connectivity
NetWare SFT Level III
Dial-in/dial-out connectivity
Network support tools
Analyzing the LAN using LANalyzer for Windows
Multiple protocol routing
NetWare 4.0
UnixWare and NetWare

The labs are conducted by CNEs and run concurrently with the breakout sessions. They allow
you to experience many of the technologies you will be learning about in the classroom.
Sponsor Hospitality Night
One of the most popular BrainShare events is Monday's Sponsor Hospitality Night. This
provides a forum for Novell's industry partners to present technologies and products of interest to
you. Sponsor Hospitality Night is again split between the Marriott and Red Lion Hotels.
Confirmed sponsors include:

3Com
Blue Lance
Borland
Digital Equipment
Hewlett-Packard
IBM
Intel
Lotus
Micropolis
Microsoft
OURS
SMC
Storage Dimensions
Thomas-Conrad
Univel
Wang
WordPerfect
Save $300 on Registration Fees
Between now and March 20, the registration price for the conference is $1,295.
Registration at the door is $1,595.
$100 Discount
If you are a member of a Novell program such as the CNE, CNI or Novell Professional
Developers' Program, you receive a $100 discount off the registration price, no matter when you
register.
Register Today!
Register by phone, fax or mail:
BrainShare '93                  Phone: 1-800-253-2819, code 104
1395 N. Highway Dr.             or 1-314-827-5629
Fenton, MO 63099                Fax: 1-314-827-6858
BrainShare International
Novell is taking BrainShare on the road -make your plans now for BrainShare Europe and
BrainShare Japan.
BrainShare Europe '93   BrainShare Japan '93
May 12-14               June 22-24
Nice, France            Tokyo, Japan
CURRENT PATCHES FOR NOVELL
DEVELOPMENT TOOLS
Many problems encountered by Novell developers can be resolved by using the current drivers
and applying the latest patches. In many cases, proper patching can save you a call to the
Developer Support Group.
NetWire
The latest NetWare drivers, example code for NetWare API development tools, OS/2
requester patches, and patches for Novell's database products are available on Novell's NetWire
forum on CompuServe. Back issues of Bullets and developer FYIs are also available (NOVLIB,
library 11).

New information is first stored in NOVLIB library 1, and moved to library 7 after a period of 30
days. If you do not have access to CompuServe, request these files from Novell's Developer
Support Group at 1-800-NETWARE (1-800-638-9273) or 1-801-429-5588.

When you call, be ready to provide a shipping address, disk preference (5.25", 3.5", HD, or DD)
and, if you prefer overnight delivery, your company's Federal Express account number. If you do
not provide a Federal Express account number, the patch disk will be sent to you via regular
mail.
NDEVREL
Updated NetWare API SDK components can be obtained from Novell's NDEVREL forum
on CompuServe. For more information on Novell developer programs contact Novell at
1-800-NETWARE (1-800-638-9273) or 1-801-429-5588.
For a Complete List...
A document describing available patches and other files and their location on CompuServe is
available through Novell Developer Relation's Automated Fax System (AFS). This system can
provide you other useful information as well.

To use the AFS, call 1-800-RED-WORD (1-800-733-9673) or 512- 794-1796 from a touchtone
phone. Then, choose the option for the Automated Fax System, select the documents you wish to
receive, and supply your fax number (the fax number to which you want the document(s) sent).
Document #7805 describes the patches. Document #1 lists all other documents available through
the Automated Fax System. Up to five documents can be requested per call.
NOVELL DEVELOPER EDUCATION
Novell Developer Education offers several courses for developers who use Novell's development
& database tools, including NetWare SQL, Btrieve, Xtrieve PLUS, and the NetWare Client APIs.
904:    Btrieve: An Overview
This new course provides a general overview of NetWare Btrieve v6.x and its new
features. It covers file structures, indexing, data integrity, record and file locking, caching,
operating modes, segmented keys, backward compatibility and utilities.
905:    Programming with Btrieve
This course has been enhanced to cover all Btrieve operations & environments. It provides
a complete introduction to Novell's server-based record manager. 50% of class time is spent in
programming workshops. Working knowledge of C, BASIC, Pascal, or COBOL required.
Prerequisite: 904: Btrieve: An Overview
907:    Xtrieve PLUS
This course has been updated to include new features introduced with NetWare SQL v3.0.
It teaches developers to use Xtrieve PLUS as a Btrieve or NetWare SQL programming utility.
Trains users of Btrieve- or NetWare SQL-based database applications to work effectively with
this menu driven utility.
911:    NetWare Database Administrator
This new course gives a complete, hands-on look at installing and configuring NetWare
SQL and NetWare Btrieve. It covers the basics of ANSI Standard Structured Query Language
(SQL), focusing on NetWare SQL and key database features like security, referential integrity
(RI), database design, data normalization and performance.
912:    Programming with NetWare SQL
This new course is designed for developers and experienced network and database
administrators who will be developing NetWare SQL applications or enhancing existing Btrieve
applications with NetWare SQL. It provides an in-depth look at the functionality of NetWare
SQL and discusses optimizing database systems for development of efficient applications using
Novell database tools.
930:    Developing NetWare Loadable Modules (NLMs)
This course introduces C programmers to server-based application development in the
32-bit NetWare 3.x environment. It covers basic concepts for writing server- based C
applications that access the NetWare 3.x C library (CLib). Requires working knowledge of the C
language.
940:    NetWare Programming: Basic Services
This new lab-oriented class (40 percent lab work) introduces NetWare programming
concepts. It covers topics such as bindery services, file system services, print services, queue
management, connection and file-server services, and accounting and synchronization services.
This class requires knowledge of the C programming language.
945:    NetWare Programming: Protocol Support
This new class covers protocol support features. It also discusses network programming
concepts and techniques for developing client-side applications, including Service Advertising
Protocol (SAP) IPX/SPX, diagnostics, NetBIOS, TLI, and Named Pipes. This class requires
strong knowledge of the C programming language.

To obtain information on pricing, location, scheduling, & course content for classes held in the
US, call 1-800-233- 3382, 1-801-429-5508 or 1-800-NETWARE. Customers outside of the U.S.
should call 1-801-429-5508. For information on availability, location, and prices of classes
outside of the U.S., contact your local Novell office.
FUN AND FACTS
Developer Trivia
Test your developing skills with the development products by taking our Fun & Facts
quiz. (See the end of this section for answers.)
1.   With Btrieve 5.x, can you create a supplemental index at the same time you create
the file?
A.   Yes
B.   No
2.   What error message does OS/2 v1.3 return if you try to run Brequest in a Global DOS
box?
A.   Error: Sys2090
B.   "The system has encountered an error and cannot continue."
C.   IpxOpenSocketFailed
3.   What is the syntax for thunking in OS/2 when thunking pointers to 16 bit pointers?
A.   _Seg16
B.   (thunk)
C.   (far16)
4.   How large is an OS/2 SPX header?
A.   36 bytes
B.   42 bytes
C.   43 bytes
5.   Under DOS, SPX uses Event Service Routines (ESRs) to perform certain requests when
interrupted. What does OS/2 use to fulfill these types of requests?
A.   ESRs
B.   semaphores
C.   pipes
6.   Xerox has assigned Novell a set of sockets to be used by NetWare. What is socket 456
used for?
A.   Diagnostics
B.   NetBIOS
C.   Named Pipes
7.   Currently, three data streams are defined for NetWare. What are they?
A.   DOS, MAC, & OS/2
B.   DOS, MAC, & UNIX (NFS)
C.   DOS, MAC, & FTAM
FUN AND FACTS ANSWERS
1.   B
2.   C
3.   A
4.   B
5.   B
6.   A
7.   C



CONTACTING NOVELL
Developer Support
Developers in the U.S. and Canada may contact Novell Developer Support via telephone, fax,
BBS or electronic mail via CompuServe, MHS or the Internet.
Voice
For both presales and postsales support, call Novell Developer Support between 8:00 a.m. and
5:00 p.m. Mountain Time at  1-801-429-5588. Many calls to Novell Developer Support are
passed to a software support engineer immediately. Calls to Novell Developer Support generally
will be acknowledged or answered within four hours.
Fax
If you prefer, you may contact Novell Developer Support via fax at 1-801-429-2990. Faxed
questions are acknowledged or answered within 24 hours.
Developer BBS
If you do not have access to either CompuServe or the Internet, send test cases to our BBS. Set
your communication software to N-8-1 and call 1-801-429-5836.
E-mail: CompuServe
Post your messages in the appropriate section addressed to Novell at 76701,171. These messages
will receive a response within 24 hours.
E-mail: MHS
You may direct your questions and comments to Novell Developer Support via Novell's Message
Handling Service E-mail facility. Address your messages to devsup@novell. These messages
will receive a response within 24 hours.
E-mail: Internet (SMTP)
An alternative method of contacting Novell Developer Support is through the Internet E-mail
system. Send your messages to devsup@novell.com. These messages will receive a response
within 24 hours.
NetWire on CompuServe
Novell's NetWire forum is open to all registered CompuServe subscribers. Through the
NDEVSUP forum, professional developers writing applications with Novell development tools
can gain access to information specific to Novell development. Support, patches, periodicals and
product information, as well as information on all of the programs and services provided for
Novell developers are accessible through this forum. Post your messages in the appropriate
section addressed to Novell at 76701,171. Technical questions will be acknowledged or
answered by Novell Developer Support within 24 hours.
Novell Products and SDKs
Novell products on the "Currently Shipping Developer Products" list (see page 15 of this
issue), including the Red Box Products, are available to Novell Professional Developer's
Program members. Call 1-800-RED-WORD (1-800-733-9673) or 1-303-894-4135 to order these
products or to receive additional information. To order other Red Box Products not listed,
contact your local Novell office or Novell Authorized Reseller.
DeveloperNet Labs
For information on DeveloperNet Labs development tools, education classes and product certification,
in the U.S. and Canada call 1-800-453-1267 ext. 5544 or 1-801-429-5544, or call your local
Novell office (see back cover of this issue).
Novell Developer Relations
Novell Professional Developers or those wishing to become members may contact Novell
Developer Relations via telephone, fax, or electronic mail via Compuserve, MHS or the Internet.
Voice
For general information or questions on Novell Developer Relations programs, in the U.S.
or Canada call 1-800-RED-WORD (1-800-733-9673). All others call 1-801-429-5281.
Fax
If you prefer, you may contact Novell Developer Relations via fax at 1-801-429-7207.
NetWire on CompuServe
Novell's NetWire forum is open to all registered Compuserve subscribers.  Through the
NDEVREL forum, Novell Professional Developer's Program-related issues or general questions
may be posted. Through the NDEVINFO forum, customers who do not have products may post
pre-sales product information questions on all Novell SDKs.
E-mail: MHS or Internet (SMTP)
You may direct your questions and comments to Novell Developer Relations via Novell's
Message Handling Service E-mail facility. Address your messages to devprog@novell.com. Use
the same address when going through the Internet E-mail system.


ACKNOWLEDGEMENTS

Publisher:       Mad Poarch


Editor:             Kirk R. Humphries


Design:             Creative Services, Provo

Feature Articles:   Ron Cully and Vicki L. Smith

Contributors:       Gaurang Amin, Linda Anderson, Neda Eslami,
               John King, Nancy Kromar, Rudy McNeese,
               Chris Ojeda, Matt Pinsonneault, Bill Prentice,
               Bob Quinlan, Drue Reeves, Michael A. Spano,
               Howard Thamm, Aslam Tejani, and Brenda Wallace

Bullets is a publication from Novell's Developer Support Group. Special thanks to the Developer
Support, Development, Developer Relations, Product Marketing, and Marketing
Communications staff who contributed time and valuable input.

(c) 1993 Novell, Inc. All rights reserved.

(c) 1992 Novell, Inc. All rights reserved. Novell, the N design, NetWare, Btrieve, XQL, LAN
WorkPlace and LANalyzer are registered trademarks; NetWare Loadable Module (NLM),
NetWare Global Messaging, NetWare System Calls for DOS, NetWare Runtime, NetWare SQL,
NetWare Btrieve, NetWare C Interface for DOS, NetWare System Interface Technical Overview,
NetWare for SAA, NetWare RPC, NetWare RPC 386, NetWare LU6.2, Report Executive,
NetWare MHS, NetWare Asynchronous Communication Services (NACS), NetWare
Management System, NetWare 3270 LAN Workstation, LANtern and Xtrieve PLUS are
trademarks; and NetWire and Professional Developers' Program are service marks of Novell, Inc.
IBM and OS/2 are registered trademarks, and NetBIOS and SAA are trademarks of International
Business Machines Corporation. Microsoft is a registered trademark, and Windows is a
trademark of Microsoft Corporation. Macintosh and AppleTalk are registered trademarks of
Apple Computer, Inc. CompuServe is a registered trademark of CompuServe Corporation. NFS
is a registered trademark of Sun Microsystems, Inc.