AUGUST/SEPTEMBER 1992 VOLUME 4 NUMBER 8

INDEX

• MAD'S COLUMN
• ARTICLE
• TECHNICAL INSIGHTS
• NIBBLES AND BITS
• PATCH LISTINGS
• NOVELL EDUCATION
• FUN & FACTS
• CONTACTING NOVELL
• ACKNOWLEDGEMENTS

MAD'S COLUMN

It is my belief that the Novell developer is breaking away--breaking away from the single-platform application. More and more developers are expanding applications to include more than one platform of choice. Two years ago, how many developers were seriously writing to DOS and the Windows, OS/2 or NetWare Server (NLM) platforms? From watching the class and type of logged new incident calls to Developer Support, I see this trend becoming the norm.

I'm sure you have noticed the survey encasing this month's Bullets. In the next couple of months you may receive multiple surveys from Novell. Some of the questions may seem esoteric in nature, but we're looking to our customers for insight for planning our budgets and strategic commitments for Fiscal Year 1993.

If you have ever heard Ray Norda speak, somewhere in his message were the words "Customer driven and loving it" --a powerful message and directive for Novell Support/Services. A colleague from Sunnyvale, Kraig Ellis, recently added the twist: "Customer loving and driving it." As a support provider, Kraig knows that implementation is nine-tenths of the directive. Every member of the Novell Support/Services organization is now driving this directive, breaking-away to keep our support teams on the developing edge.

Happy_Programming!

Mad Poarch
Director
Developer Support/Service

ARTICLE:

NLMs: From "Hello World" to World-Class Computing (Part III)

FIGURE 1: Components of a Distributed Application

         SERVER                             CLIENT
____________________________________________________________
   Server Application                 Client Application
           |                                  |
 Distributed Application            Distributed Application
      Protocol (DAP)                     Protocol (DAP)
           |                                  |
 Communication Protocol             Communication Protocol
           |                                  |
   Communication Media                Communication Media
____________________________________________________________

End of Figure 1

Required Novell Programming Components

• The NetWare C Interface for Windows v1.22 or later (v1.3 if you are using Windows v3.1)
• Novell's Windows Workstation Kit, which contains all the components you need to run a Windows workstation on NetWare.

Sidebar -- Common Questions

A - IPX.COM v3.10 or higher; NETX.COM v3.26 or higher; IPXODI.COM v1.20 or higher. Download DOSUP5.ZIP from NOVLIB LIB 5 to get these files.

Q - Where do I get the latest versions of VNETWARE.386, NETWARE.DRV and VIPX.386?

A - For Windows v3.1, use the drivers that came with Windows v3.1. The drivers for Windows v3.0 are available on NetWire in either WINUP6.ZIP (NOVLIB, LIB 5) or W30DRV.ZIP (NDEVREL, LIB 10).

Q - What do I need to run in Enhanced mode?

A - Windows will load the VIPX.386 in your SYSTEM.INI under the section [386Enh]. Make sure that you use the latest version of VIPX.386.

Q - What is the difference between VNETWARE.386 and VIPX.386?

A - VIPX.386 is the enhanced mode, virtual IPX driver. VNETWARE.386 is the enhanced mode, virtual NetWare Shell driver.

Q - What DLLs should I use?

A - The NetWare C Interface for Windows v1.22 DLLs may not support Windows v3.1. For compatibility with both Windows v3.0 and Windows v3.1, use the DLLs that come with the NetWare C Interface for Windows v1.3.

Q - I don't have a CompuServe account, and I need the latest NetWare shells and drivers for Windows. Where can I get them?

A - Contact your local Novell office or, in the US, call 1-800-UPDATE1 to order the documentation and disks.

Q - What should I do with an old program built with the NetWare C Interface for Windows SDK 1.22?

A - You may need to rebuild these programs and give your clients new copies of the applications and v1.3 of Novell's Windows DLLs. Most applications will only need to be relinked.

Q - When running Windows v3.0a, I get the message "Can't find NETWARE.DLL". How can I obtain this driver?

A - NETWARE.DLL is the same thing as NETWARE.DRV. Place NETWARE.DRV in the proper path and Windows will find it.

END OF SIDEBAR

Other Programming Tools

Porting the DAX Code

Barring a change in the user interface, the client application should not require any modifications at all. Finally, the engine won't require any changes to support the new client.

Remember that the DAX client application is made up of three separate components:

• CP.LIB - library of Communication Protocol APIs
• DAP.LIB - library of Distributed Application Protocol APIs
• xxx.OBJ - client application object modules (e.g., STRESS.OBJ, INOUT.OBJ)

To set up your environment to run Borland's C++ command line compiler, you will need a TURBOC.CFG file that contains the INCLUDE and LIBRARY paths needed for compiling. This file is created from within the MAKEFILE to ensure that the correct system paths are used (see the README.1ST file included with the DAXn.ZIP file for a discussion on MAKEINIT). For the client software, you can use Borland's IDE to create the application. The project and desktop files have been included in the corresponding WIN directories to simplify the setup process.

Porting the CP Layer

• Define a Manifest Constant
• Generate a Windows version of HELPER.H header file
• Include the WINDOWS.H header file
• Add a parameter called TASKID to all IPX APIs

For example, the module CPSEND.C contains an API, CPInitSendPacket, which contains some platform specific code for DOS and NLMs.

#if defined(DOSCLIENT)
    packet->destination =
    *destination;
#elif defined(NLMCLIENT)
    *(IPXAddress *)&packet->destNet
    = *destination;
#endif

#if defined(DOSCLIENT) ||
    defined(WINCLIENT)
    packet->destination =
    *destination;
#elif defined(NLMCLIENT)
    *(IPXAddress *)&packet->destNet
    = *destination;
#endif

#if defined(WINCLIENT)
    #include 
#endif

For example, Borland C++ includes the WINDOWS.H header file. For the CP Layer, add this code fragment to the CPC.H header file. CPC.H is included by all of the modules that make up the client portion of the CP layer.

Supporting IPX under Windows is similar to supporting IPX in the DOS environment; there are only a few minor coding differences. First, an additional parameter, TASKID, is required for each of the APIs. TASKID contains a virtualized identifier that the NetWare DLLs use to track resources in use by a given IPX application. The TASKID parameter is returned by the initialization API called IpxInitialize(), and is subsequently used on all API calls to IPX.

Using HELPER.H and macros for the IPX APIs, you can completely hide the TASKID parameter from the example program (See Figure 4 below).

The second requirement that is unique to the Windows environment is a special API named IPXDeInitialize that must be called prior to terminating the Windows client application (see Figure 2). This API frees the resources allocated to the client when IPXInitialize() is called. Again, this concept is unique to Windows, and is not required for either the DOS or NLM environments.

FIGURE 2: Deinitializing IPX in Windows

void    CPDeInitialize(CPDATA *CPid)
{
    if( CPid ){
        if( CPid->skt ) IPXCloseSocket(CPid->skt);
        CPDeInitializeRecvLogic(CPid);   // Clean up receive logic

        CPDeInitializeSendLogic(CPid);   // Clean up send logic
        CPDeInitializeConnLogic(CPid);   // Tear down the conn.
        memset(CPid,NULL,sizeof *CPid);
        #if defined(WINCLIENT)           // Only Windows clients

            IPXDeInitialize();           //   need to shutdown IPX

        #endif                           //
        #if defined(DYNAMICMEM)
            free(CPid);                  // Free client memory
        #endif
    }
}

End of Figure 2

FIGURE 3: Hiding the IPXDeInitialize API

void    CPDeInitialize(CPDATA *CPid)
{
  if( CPid ){
      if( CPid->skt ) IPXCloseSocket(CPid->skt);
      CPDeInitializeRecvLogic(CPid);
      CPDeInitializeSendLogic(CPid);
      CPDeInitializeConnLogic(CPid);
      memset(CPid,NULL,sizeof *CPid);
      IPXDeInitialize();      // only calls shutdown if WIN client

      #if defined(DYNAMICMEM) // expands only for WIN clients
            free(CPid);
        #endif
    }
}

End of Figure 3

#include 
#include 

#define  WINCLIENT
#define  LONG_LIVED      (0xFF)
#define  SHORT_LIVED     LONG_LIVED

     #define  ECBISINUSE(ecbp)         ((ecbp)->inUseFlag)
#define  INUSEFLAG(ecbp)          ((ecbp)->inUseFlag)
#define  COMPLETIONCODE(ecbp)     ((ecbp)->completionCode)
#define  ECBSOCKET(ecbp)          ((ecbp)->socketNumber)
#define  ECBFRAGCOUNT(ecbp)       ((ecbp)->fragmentCount)
#define  ECBFRAGADDR(ecbp,x)
((ecbp)->fragmentDescriptor[x].address)
#define  ECBFRAGSIZE(ecbp,x)      ((ecbp)->fragmentDescriptor[x].size)
#define  IPXDESTNETP(ipxp)        ((ipxp).network)
#define  IPXDESTNODEP(ipxp)       ((ipxp).node)
#define  IPXDESTSOCKETP(ipxp)     ((ipxp).socket)

extern   DWORD   _TASKID;
#define  MAXECBS     10
#define  MAXSIZE     576

#define  IPXReceive(ecbp)         IPXListenForPacket(_TASKID,ecbp)
#define  IPXSend(ecbp)            IPXSendPacket(_TASKID,ecbp)
#define  IPXInitialize()
(IPXInitialize)(&_TASKID,MAXECBS,MAXSIZE)
#define  IPXOpenSocket(skt,typ)   (IPXOpenSocket)(_TASKID,(WORD *)skt,type)
#define  IPXCloseSocket(skt)      (IPXCloseSocket)(_TASKID,skt)
define   IPXCancelEvent(ecb)      (IPXCancelEvent)(_TASKID,ecb)
#define  IPXGetIntervalMarker()   (IPXGetIntervalMarker)(_TASKID)
#define  IPXGetLocalTarget(x,y,z) (IPXGetLocalTarget)(_TASKID,x,y,z)
#define  IPXDeInitialize()        (IPXSPXDeinit)(_TASKID)

End of Figure 4

DAP Port

One change required to port the DAP layer to Windows is the inclusion of the WINDOWS.H header file. For this layer, you can include this file from DAPSYS.H, a header file included by all modules in the DAP Layer.

Finally, an API called delay() has been added to the module DAPSEND.C, since there is no corresponding Windows API available in the Borland environment. In this implementation, you do not need to be too concerned over the accuracy of delay() (i.e., it does not need to delay for exactly the number of milliseconds specified). This API is used by the DAPSendRequest API while waiting for the application server to finish servicing its request. You may notice that the example uses IPXYield() rather than IPXRelinquishControl( ); IPXYield( ) truly yields control back to Windows while IPXRelinquishControl( ) yields to the LAN driver.

You will find IPXYield( ) in the NetWare C Interface for Windows SDK v1.3 in IPXYIELD.C.

The Client Application

As described here, porting the DAX example program to the Windows environment is very straightforward, since no complicated user interface is required. As with any GUI environment, the user interface is always a primary consideration in an application porting process. After examining the changes made to support the Windows environment, you should be able to port the DAX example and other distributed applications which follow a similar design philosophy to other environments with a minimum of difficulty.

TECHNICAL INSIGHTS:

Multiple VIEW.DDFs

NetWare SQL v3.0

When you create a named database with NDBSETUP, only one path can be specified for a set of DDF files. Therefore, it is not possible to specify multiple paths for different VIEW.DDF files relating to the field, file, and index DDFs for the named database.

NetWare SQL Documentation Correction

NetWare SQL v3.0

The NetWare SQL v3.0 Installation and Operation manual incorrectly describes the use of the XQLLOCAL.DLL file for OS/2 workstations. On page 2-44, the manual states:

"XQLLOCAL.DLL provides support for data that resides on the local hard drive. An application at an OS/2 workstation cannot access local files using the requester alone."

A NetWare SQL application can not access files located on a local hard drive. Since NetWare SQL utilizes NetWare Btrieve, the server-based version of the Btrieve record manager, for all file I/O, the data files must be located on the server for NetWare Btrieve to access them.

Extended Attributes Return Values Not Documented

Network C for NLMs v2.0(b)

FIGURE 5: Possible return codes for extended attribute functions

ERR_MISSING_EA_KEY                 200
ERR_EA_NOT_FOUND                   201
ERR_INVALID_EA_HANDLE_TYPE         202
ERR_EA_NO_KEY_NO_DATA              203
ERR_EA_NUMBER_MISMATCH             204
ERR_EXTENT_NUMBER_OUT_OF_RANGE     205
ERR_EA_BAD_DIR_NUM                 206
ERR_INVALID_EA_HANDLE              207
ERR_EA_POSITION_OUT_OF_RANGE       208
ERR_EA_ACCESS_DENIED               209
ERR_DATA_PAGE_ODD_SIZE             210
ERR_EA_VOLUME_NOT_MOUNTED          211
ERR_BAD_PAGE_BOUNDARY              212
ERR_INSPECT_FAILURE                213
ERR_EA_ALREADY_CLAIMED             214
ERR_ODD_BUFFER_SIZE                215
ERR_NO_SCORECARDS                  216
ERR_BAD_EDS_SIGNATURE              217
ERR_EA_SPACE_LIMIT                 218
ERR_EA_KEY_CORRUPT                 219
ERR_EA_KEY_LIMIT                   220
ERR_TALLY_CORRUPT                  221

End of Figure 5

Status 84 and Insert Operations

NetWare Btrieve (NLM) v6.0

To avoid this situation, design your applications to trap for status 84s and retry the Insert operation.

Print Server Printer Status Codes

NetWare C Interface for DOS v1.2

• PSTAT_WAITING_FOR_JOB indicates that the printer is available and ready for a print job.
• PSTAT_WAITING_FOR_FORM indicates that the printer is waiting for a new form to be mounted.
• PSTAT_PRINTING_JOB indicates that the printer is currently printing a print job.
• PSTAT_PAUSED indicates that the printer has been paused and will continue to print the active job when started.
• PSTAT_STOPPED indicates that the printer has been stopped and the current job aborted. When the printer is started it will begin to look for another job to print.
• PSTAT_MARK_EJECT indicates that someone has paused or stopped the printer and sent a mark top of form or a page eject. The print is in the state of executing the request.
• PSTAT_READY_TO_GO_DOWN does indicate that the printer has finished printing any currently active job and is ready to go down.
• PSTAT_NOT_CONNECTED indicates the printer is not currently connected to the print server.
• PSTAT_PRIVATE indicates that a remote printer is not currently available as a network printer. This happens when a command is sent to the print server telling it to release the printer.

Diagnostic Functions Not Returning Data

NetWare C Interface for Windows v1.3

FIGURE 6: Modifications to NetWare C Interface for DOS

~
~
~
void FAR * FAR PASCAL NWMemmove( char far *toBlock,
                                 char far *fromBlock,
                                 unsigned int len )
   {
   WORD  i;                            // This was a BYTE.

   if( fromBlock == toBlock )
      {
      return( toBlock );
      }
   for( i = 0; i < len; i++ )          // len was cast to a BYTE
      *(toBlock + i) = *(fromBlock + i);

   return( toBlock );
   }
~
~
~
End of Figure 6

Storing and Recalling Views

NetWare SQL v3.0

NetWare Runtime, NetWare SQL v3.0 & Applications

NetWare SQL v3.0

Two restrictions for running database applications on a NetWare Runtime server are briefly described in the NetWare SQL v3.0 Installation and Operation manual on page 2-38.

First, a NetWare Runtime server can not accept direct Btrieve calls from an application. Although NetWare SQL does not require a NetWare connection, NetWare Btrieve does. Therefore, an application which makes only Btrieve calls, or makes both Btrieve and NetWare SQL calls can not be run against files on a NetWare Runtime server.

The second restriction is that the application must use a named database. Since users do not have a connection, they cannot access data dictionaries and data files via drive mappings. A named database must be defined on the NetWare Runtime server using the NetWare SQL Setup Utility, thus indicating which directories contain the database files and dictionaries. The application can then use this database name to login to NetWare SQL and access the data files.

If the application or the data dictionary contains references to drive mappings, a NetWare SQL Requester Configuration File can be defined to indicate what directories on the NetWare Runtime server should be used whenever a particular drive mapping is encountered by the application.

This is described in more detail in the same manual on pages 2-47 and 2-48.

SubmitAccountCharge API Truncates Comment

NetWare C Interface for DOS v1.2

  BYTE CommentLen;
  .
  .
  .
  CommentLen = MIN(
   (BYTE)(strlen(comment)), 255 );

Active Named Databases

NetWare SQL v3.0

ReturnSpaceRestrictionForDirectory API Returns -1

Network C for NLMs v2.0(c)

QueryServices API Returns Invalid Node Address

NetWare C Interface for Windows v1.3

  00 11 22 33 44 55

  44 55 00 11 22 33

  BYTE *FixNode(BYTE *node)
  {
     BYTE temp[2];

     temp[0] = node[5];
     temp[1] = node[4];
     node[5] = node[3];
     node[4] = node[2];
     node[3] = node[1];
     node[2] = node[0];
     node[1] = temp[0];
     node[0] = temp[1];
     return node;
  }

  FixNode(sapBuffer.Node);

Disappearing Attributes

Xtrieve PLUS for DOS v4.10

NIBBLES AND BITS

Fast Answers to Common Questions

NetWare SQL

"There is no quick way to remove RI. Deleting RELATE.DDF will not remove RI because there will still be an entry in FILE.DDF and the table definitions will still contain referential constraints. Also, you cannot drop x$Relate from the dictionaries.To successfully remove RI, you must alter all table definitions."

There is a fast way to disable Referential Integrity. In the NDBSETUP utility the switch, "Enable/Disable RI," toggles to set a flag that enables or disables RI. Since RI is enforced at the NetWare Btrieve level, NetWare Btrieve v6.0 (a component of NetWare SQL v3.0) checks this flag before doing anything else. When the flag is set to "Disable," NetWare Btrieve will not enforce RI, even though the constraints still exist.

General

               MAP ROOT INS S16:=
          SERVER\VOLUME:C7\BIN

NetWare System Calls for DOS

A - You can increase the maximum number of NetBIOS names for a workstation by using an undocumented SHELL/NET.CFG parameter. The syntax is outlined below:

          NETBIOS NAMES=

NetWare C Interface for DOS

A - The ScanSalvagableFiles() function returns the size of a deleted file in the dataForkSize field. Although this field is documented as being for the Macintosh, the size of any file can be returned in this field.

Q - Why can't I initialize SPX under NetWare Lite?

A - By default, NetWare Lite disables SPX and diagnostic capabilities of IPXODI. This makes it impossible to run SPX and diagnostic applications. To enable these applications, remove /A parameter from the IPXODI load line.

NetWare C Interface for Windows

A - When the NetWare C Interface for Windows v1.3 SDK was introduced and the DLLs were restructured, the ordinal numbers no longer matched those listed in the documentation. You will find the correct ordinal numbers in the .DEF files on the distribution disks under the \SRC directories. The files are NWIPXSPX.DEF (communications, diagnostics and SAP), NWNETAPI.DEF (all noncommunication services), and NWPSREV.DEF (print server services).

Network C for NLMs

A - No. Named Pipes is currently supported on DOS, OS/2 and Windows clients only.

Q - I opened a file with the name "log," and CLib returned a handle, but when I call read( ) with that handle, the function blocks and never returns. Why is this happening?

A - STREAMS is returning the file handle when you pass it this filename. CLib calls the STREAMS open API first, and when STREAMS returns the handle, CLib links it into your open file list and returns it to you. In this situation, you have two options.

• Avoid passing in lower case names to CLib (i.e., call strupr( ) first)
• Pass full volume path specifications instead (i.e., SYS:LOG)

NetWare OS/2 Requester

A - Yes. In the NET.CFG file, you will find a parameter called "sessions." If you set this parameter to a number between eight and twenty, NetWare will support that number of sessions.

Q - Can I load NetBIOS if I am using a virtual DOS box under the NetWare OS/2 requester v2.0?

A - Yes, but only if the NBDAEMON is not loaded in the OS/2 machine's CONFIG.SYS file. Either load the DOS version or the OS/2 version, but never load both versions.

Btrieve

A - This situation is caused by a current limitation of SPX. To avoid the problem affecting Brequest, unload Brequest before terminating a DOS session.

Q - Can BREBUILD rebuild Btrieve files created in the Btrieve v3.x format, or do you need to run another upgrade utility first?

A - You should be able to rebuild Btrieve v3.x files using BREBUILD, unless they have been extended across a volume. If the files have been extended, you should run CONVERT4 to translate the Btrieve v3.x file into v4.x format, then run BREBUILD. Any Btrieve v4.x and v5.x files can be rebuilt using BREBUILD.

Q - Will Brequest work in an OS/2 v2.0 DOS Box?

A - Brequest v5.16 and NetWare Btrieve (NLM) v5.15 will not run properly in multiple private DOS boxes. The system halts. Brequest v5.16 and NetWare Btrieve (NLM) v5.15 do not work in a global DOS box either. Trap D occurs when Btrieve calls are made. Both of these situations have been reported to Novell Development.

Q - Why is the NetWare Btrieve NLM returning a status 18 (Disk Full) when I still have plenty of disk space left?

A - The NetWare Btrieve NLM is attempting to expand a file and the file does not have an owner name. This normally occurs when the user (bindery object) who created the file is deleted from the bindery.

Use NDIR to determine which files do not have owner names. Then, use the NetWare FILER utility to assign an owner name to these files.

PATCH LISTINGS:

Btrieve for DOS v5.10 Patches

116. Btrieve (DOS)

• Patch #79 has been applied,
• Btrieve operates on a NetWare Lite network,
• The .TRN file is redirected over the network and is used by another instance of Btrieve, a simple series of operations will either fail or hang the workstation, depending on which version of NetWare Lite you are using. This patch corrects the situation. (This patch also resolves problems fixed in patch 79.)

Grow Patch (DOS, Windows, OS/2)

117. Btrieve (DOS, Windows, OS/2, VAP)

NOVELL EDUCATION:

Course Update

904: Btrieve: An Overview

This new course provides a general overview of NetWare Btrieve v6.x and its new features. 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, including COBOL. 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. 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. 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. 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. 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.

For information on availability, location, and prices of classes outside of the US, contact your local Novell office.

FUN & FACTS:

Developer Trivia

1.   What key is used to bring up the Remote Console "Available Options" menu ?
     A.   <*> on the number pad
     B.   Shift <*>
     C.   Alt + Esc
     D.   <+> on the number pad
2.   What status code will be returned if you try to access a NetWare Btrieve v6.0 file with
NetWare Btrieve v5.x?
     A.   2 (I/O Error)
     B.   3 (File Not Open)
     C.   0 (Successful Operation)
3.   What are the names of two modes of services provided by the Transport Layer Interface
(TLI)?
     A.   Connection mode & Connectionless mode
     B.   Real mode & Standard mode
     C.   Connect mode & Disconnect mode
4.   The command file used for NSUTIL, RIUTIL or BUTIL cannot contain lines that are
longer than ________.
     A.   80 characters
     B.   130 characters
     C.   1024 characters
5.   What is the difference between BUTIL.NLM v5.x Recover option and the BUTIL.NLM
v6.x Recover option (shipped with NetWare SQL v3.0)?
     A.   BUTIL v6.0 is faster
     B.   BUTIL v6.x uses Get operations, but BUTIL v6.x uses Step operations
     C.   BUTIL v6.x checks the Page Allocation Table (PAT) pages and reconstructs them if
necessary.
6.   The Btrieve requester (BREQUEST.EXE) will not run in an OS/2 v1.3 DOS Box.
     A.   True
     B.   False
7.   What new data type has been introduced in NetWare SQL v3.0?
     A.   NumericSTS
     B.   Byte
     C.   None
8.   How many simultaneous Named Pipes connections does the OS/2 Requester v1.3
support?
     A.   245
     B.   250
     C.   255
FUN & FACTS ANSWERS
1.   A
2.   A
3.   A
4.   B
5.   C
6.   A
7.   A
8.   C

CONTACTING NOVELL

Developer Support

Voice

Fax

Developer BBS

E-mail: CompuServe

E-mail: MHS

E-mail: Internet (SMTP)

NetWire on CompuServe

Novell Products and SDKs

DeveloperNet Labs

Novell Developer Relations

Voice

Fax

NetWire on CompuServe

E-mail: MHS or Internet (SMTP)

ACKNOWLEDGEMENTS

Contributors: Linda Anderson, Vitek Boruvka, Steve Cannon, Michael Eisa, Neda Eslami, Kumar Gaddam, David Harris, Laura Heater, Ken Lowrie, Diane Klinetob, Nancy Kromar, Clint McVey, Paige Parker, Randy Reddy, Glenn Stephens, Brenda Wallace

Special thanks to the Developer Support, Development, Developer Relations, Product Marketing, and Marketing Communications staff who contributed time and valuable input.

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

Novell, the N design, NetWare, Btrieve, XQL and LAN WorkPlace are registered trademarks, NetWare Lite, NetWare System Calls for DOS, NetWare Loadable Module (NLM), NetWare SQL, NetWare Btrieve, Xtrieve PLUS, NetWare C Interface for DOS, NetWare System Interface Technical Overview, NetWare RPC, NetWare RPC 386, NetWare LU6.2, Report Executive, and Professional Development Series (PDS) are trademarks, and NetWire and Professional Developers' Program (PDP) are servicemarks of Novell, Inc. Apple, Macintosh and AppleTalk are registered trademarks of Apple Computer, Inc. Borland is a registered trademark of Borland International, Inc. CompuServe is registered trademark of CompuServe Corporation. Microsoft is a registered trademark, and Windows and Visual Basic are trademarks of Microsoft, Inc. IBM and OS/2 are registered trademarks, and NetBIOS and SAA are trademarks of International Business Machines Corporation. Sun Microsystems and NFS are registered trademarks of Sun Microsystems, Inc. WATCOM is a trademark of WATCOM Systems, Inc.