SEPTEMBER 1994 VOLUME 6 NUMBER 4

INDEX

• ARTICLES
• DEVELOPER NEWS
• TECHNICAL INSIGHTS
• TELETIPS
• NOVELL PROFESSIONAL DEVELOPERS' PROGRAM
• FROM THE COCKPIT
• DEVELOPER EDUCATION
• CONTACTING NOVELL

ARTICLES

Telephony SDK Services for PC Telecommunications

I'm not going to describe all of the requirements for running Novell NetWare Telephony Services on Novell NetWare. These requirements are fully explained in the January and February, 1994 editions of Novell's Application Notes. (Call 1-800-377-4136 for information on Application Notes). Once you have the NetWare Telephony Services (TSERVer) installed and functioning, assuming you have the Telephony Services API (TSAPI) SDK, you can begin writing TSAPI applications. What fun it is to run a program that can call someone from your desk without even touching your phone! And what frustration fellow engineers feel as you ring their phones over and over again just to see your program in action! But enough of that--what can the Telephony SDK actually do?

How TSAPI Works

The TSERVer NLM and the PBX driver work together to provide telephony functionality, but some of these features are not available on all PBXs. For example, although the TSERVer supports predictive dialing, many PBXs do not. Therefore, when you begin programming you will need to decide which specific PBX you will work with. The alternative is to decide on a smaller set of basic TSERVer functions to implement, most likely available from all PBXs. Every PBX driver will come with a programmer's manual describing which TSERVer function calls are available and implemented by their specific PBX driver.

Currently, the TSAPI supports two platforms: Windows and server NLMs. Applications written for either of these platforms can make TSAPI requests from the TSERVer. In the future other platforms will be supported.

TSAPI provides many services including making a call from one device (typically a telephone) to another; putting calls on hold; transferring calls to another device; making conference calls; and hanging up or clearing a call. Other services include advanced features such as predictive dialing.

The NetWare Telephony Services SDK includes a sample application using many of the basic call control features. For instance, the included rolodex-type program (TSCALL.EXE) lets you click on a name and push a "dial" button to connect your phone with theirs.

From there, the ideas are up to you! You could write applications for a software controlled "hunt group" for sales people or a call control center. An administrative assistant may even use your yet-to-be-written program to conference with several members of your department. Most of the basic features and some of the advanced features of phone systems have already been implemented, and more changes are scheduled for the future.

SDK Debugging Tools

Another debugging tool is CSTASPY, which can track all incoming and outgoing telephony messages as they occur. When something doesn't appear to be working as desired, check this log to see if the events that actually occurred are the same as the events you desired.

If you need developer support, call 1-800-NETWARE. In this and future issues of Bullets, read "TeleTips." Look for telephony articles in future Developer Notes as well as our fax server. If you have questions or comments feel free to leave them with us. As you begin telephony coding, remember Novell's Developer Support department will help you get your cutting-edge programs to the market, and we're always open to suggestions and comments to make our product more useful to you.

Developing in the UnixWare Environment

The Novell UnixWare Developer Support group has found that many UNIX developers encounter common problems. Novell intends to help UnixWare developers get going in the right direction by covering various aspects of the UnixWare development environment, common development problems and possible solutions.

To develop on UnixWare, you need (in addition to either a Novell UnixWare Application Server or UnixWare Personal Edition) the Novell UnixWare Software Developers Kit version 1.1. The SDK has everything you need to develop Motif GUI applications, Windowing Korn Shell (wksh) applications, device drivers, networking applications and character-based applications. The SDK also includes online documentation, a Pentium(TM) C compiler, an enhanced debugger and sample source of drivers and applications.

Installing UnixWare

After installing the UnixWare SDK and reading the online documentation system, you should consult the sample source. It is easier to start from a sample application or driver than to start development from scratch. Sample source is available in several directories, although the primary directory for sample source is the /usr/src directory. Two subdirectories are under /usr/src: the ihvsrc directory, containing sample device drivers; and the isvsrc directory, containing a sample OpenLook GUI application. For Motif GUI sample applications look into the /usr/X/lib/ motifdemos directory and for Windowing Korn Shell samples look into the /usr/X/lib/wksh directory.

Compiling Sample Motif Applications

To run the "make" command to build the hellomotif binary, you need a "Makefile." To convert the Imakefile into a Makefile, run the /usr/X/lib/config/xmkmf in Figure 3. Executing the ls-l command will show the resulting Makefile (see Figure 4).

Now you can execute the "make" command and get the results in Figure 5. The hellomotif Motif application should now be successfully compiled.

Library Search Functions

$ searchlib bind
/usr/lib/libsocket.a:0x000000c0 T bind

/usr/lib/libsocket.so:0x00008050T bind

Debugging Applications

Compiling Large Binaries

SFSZLIM: Soft file size limit
HFSZLIM: Hard file size limit

SDATLIM: Soft data limit
HDATLIM: Hard data limit

SSTKLIM: Soft stack limit
HSTKLIM: Hard stack limit

SVMMLIM: Soft Virtual Memory limit
HVMMLIM: Hard Virtual Memory limit

# cd /etc/conf/bin
# ./idtune SFSZLIM 0x7FFFFFFF

The first value is the current setting, the second is the default setting, the third is the minimum value and the last is the maximum value.

After you have changed all tunable parameters, you need to rebuild the kernel and shut down the system:

# ./idbuild -B
# cd / ; shutdown -g0 -y

This overview of the UnixWare development environment and the frequently-encountered problems and their solutions should give you a good start developing for UnixWare. Although you will undoubtedly encounter your own problems, we hope an understanding of the available tools and problems of other developers will be of great assistance in the development process.

Figure 2: Changing to the sample directory

$ ls -l
total 50
-r--r--r--   1 root     other     1036 May 20  1993 Imakefile
-r--r--r--   1 root     other     4020 May 20  1993 hellomotif.c
-r--r--r--   1 root     other     1119 May 20  1993 hellomotif.uil
$

$ /usr/X/lib/config/xmkmf
imake -DUseInstalled -I/usr/X/lib/config

$ ls -l
total 50
-r--r--r--   1 root     other     1036 May 20  1993 Imakefile
-rw-r--r--   1 darrend  other    17327 Aug 3  09:26 Makefile
-r--r--r--   1 root     other     4020 May 20  1993 hellomotif.c
-r--r--r--   1 root     other     1119 May 20  1993 hellomotif.uil
$

$ make
        /bin/rm -f hellomotif.o
        cc -c -O -Xa -I. -I/usr/X/X11 -I/usr/X/X11 -I///usr/X/
include -I///usr/X/include/X11 -I/usr/include -I//usr/X/include
-I. -DSVR4 -DSYSV386 -DI18N -DFUNCPROTO=15 -DNARROWPROTO
-DLIBDIR=\"/usr/X/lib\" -DDESTDIR=\"/usr/X\"  hellomotif.c
        /bin/rm -f hellomotif
        cc -o hellomotif hellomotif.o -O -Xa  -T 0x8300000
-L//usr/X/lib  /usr/X/lib/libMrm.so /usr/X/lib/libXm.so -lXt
-lXext -lX11  -lgen  -lnsl -ldl -lsocket -z nodefs
$

$ nm /usr/lib/libc*

Symbols from /usr/lib/libc.so.1:
[Index]   Value      Size    Type  Bind  Other Shndx   Name
...
[1600]  |    209428|       4|OBJT |GLOB |0    |12     |_daylight
[1601]  |    132435|       0|FUNC |WEAK |0    |8      |execve
[1602]  |    176976|      88|FUNC |WEAK |0    |8      |unlockpt
[1603]  |    155120|     128|FUNC |GLOB |0    |8      |vfprintf
[1604]  |    129200|       0|FUNC |GLOB |0    |8      |_ioctl
[1605]  |    133616|     328|FUNC |WEAK |0    |8      |lockf
[1606]  |    192211|       0|FUNC |WEAK |0    |8      |auditevt
[1607]  |     70670|       0|FUNC |GLOB |0    |8      |_read
[1608]  |    132396|       0|FUNC |WEAK |0    |8      |execv
[1609]  |    133508|       0|FUNC |WEAK |0    |8      |getmsg
[1610]  |    156320|     480|FUNC |GLOB |0    |8      |_execvp
[1611]  |    133571|       0|FUNC |WEAK |0    |8      |getrlimit
[1612]  |    112784|      40|FUNC |GLOB |0    |8      |_toupper
[1613]  |    132120|       0|FUNC |GLOB |0    |8      |_cerror
[1614]  |    124608|      16|FUNC |GLOB |0    |8      |ferror
[1615]  |    159440|     148|FUNC |WEAK |0    |8      |tsearch
[1616]  |    192344|       0|FUNC |WEAK |0    |8      |lvlequal

#!/bin/sh
if [ $# -ne 1 ]
then
        echo "Usage: searchlib function_name" >&2
        exit 1
fi
# You may need to add library directories to this list.
LIBDIRS="
        /usr/lib
        /usr/ccs/lib
        /usr/X/lib
        /usr/ucblib"
for dir in $LIBDIRS
do
        for lib in $dir/*.a $dir/*.so
        do
                if [ -r "$lib" ]
                then
                        nm -px $lib | \
                         sed -n `/T \<'$1'\>/p' 2>/dev/null |
                        while read ans
                        do
                                echo $lib:$ans
                        done
                fi
        done
done

Figure 8: Sample output of truss command
$ truss hello
execve("./hello", 0x08047C58, 0x08047C60)  argc = 1
getuid()                                        = 30069  [ 30069 ]
getuid()                                        = 30069  [ 30069 ]
getgid()                                        = 1  [ 1 ]
getgid()                                        = 1  [ 1 ]
procpriv(4, 0x00000000, 0)                      = 0
sysi86(SI86FPHW, 0x80035FE4, 0x800353A4, 0x8000E295) = 0x00000000
ioctl(1, TCGETA, 0x0804668A)                    = 0
Hello, World
write(1, " H e l l o ,   W o r l d".., 13)      = 13
_exit(13)
$

ld: libelf error: memory error: output file     space elf_update
error code 1 (bu21).

# ./idtune -g SFSZLIM
0x1000000       0x1000000       0x2000  0x7FFFFFFF

$ ulimit -a
time(seconds)                 unlimited
file(blocks)                  unlimited
data(kbytes)                  unlimited
stack(kbytes)                 unlimited
coredump(blocks)              2048
nofiles(descriptors)          256
vmemory(kbytes)               unlimited
$

DEVELOPER NEWS

AppWare Foundation Release

• The AppWare Foundation for Macintosh 1.90 includes a prerelease SDK for native support of the Power Macintosh using Metroworks compilers.
• The AppWare Foundation for MS Windows 1.90 includes a developer prerelease SDK for support of MS Windows NT so you can develop and deploy applications on MS Windows NT and MS Chicago when it is available.
• The AppWare Foundation for OS/2 PM 0.85 Developer Prerelease SDK.

We're also launching the Early Experience Program for OW/AF. This program will allow you to take advantage of early releases of Novell and Borland's new cross-platform application framework at a lower cost (no "beta site" commitment). For more information on the OW/AF bundled SDKs or the Early Experience Program call 1-408-431-5172.

TECHNICAL INSIGHTS

Hints for Accessing Files Quickly from the NetWare NLM SDK

• AsyncRead: this reads the file directly from the file server's cache memory (if the file is already in cache)
• qread: low overhead read operation
• qwrite: low overhead write Note: These files are using NetWare's disk caching and transaction tracking if active. Default Disk caching on a 3.x server is 4k. On 4.x it is configurable, starting at 4k (8k, 16k, 32k or 64k). This happens at install time. All files are open in normal mode. If you want to bypass NetWare disk caching and Transaction Tracking System it enabled, Novell does not recommend using the Direct File System (DFS) calls unless:
• Your application is doing its own caching and transaction tracking and you are experiencing performance degradation when you have both NetWare and your application's transaction tracking and disk caching.
• Backup applications often access large amounts of data not being accessed by other applications. If these accesses are made through caching, the cache becomes nonrelevant for all other accesses, and general server performance suffers for other users.

Use any of the following API calls:

• DFSOpen
• DFSClose
• DFSCreate
• DFSExpandFile
• DFSFreeLimboVolumeSpace
• DFSRead: reads sectors from a file in direct file mode (sleeps until completion)
• DFSReadNoWait: reads sectors from a file in direct file mode (returns immediately after initiation)
• DFSReturnFileMappingInformation: returns file extents, each with number of blocks and starting file and volume block numbers
• DFSReturnVolumeMapping: Information: returns information about a volume required for allocation
• DFSSetEndOfFile: sets the file size
• DFSsopen: opens a file in direct file mode
• DFSWrite: writes sectors into a file using DFS (sleeps until completion)
• DFSWriteNoWait: writes sectors into a file using DFS (returns immediately after initiation)

Operating System I/O calls perform non-buffered I/O operations. Files opened at the operating-system level (with open, sopen, and create functions) are opened at the stream level.

Note: These files are using NetWare's disk caching and transaction tracking if active. Default Disk caching on a 3.x server is 4k. On 4.x it is configurable starting at 4k (8k, 16k, 32k or 64k). This happens at install time. All files are open in normal mode.

File Engine (FE) Services are used to service non-DOS file systems such as Apple's Appletalk Filing Protocol (AFP) and Sun Microsystem's Network File System (NFS). These APIs can be referenced in the NLM Library Reference Volume I (FECreat, FEFlushWrite, Fesopen and so on).

Note: These files are using NetWare's disk caching and transaction tracking if active. Default Disk caching on a 3.x server is 4k. On 4.x it is configurable, starting at 4k (8k, 16k, 32k or 64k). This happens at install time. All files are open in normal mode.

Stay tuned next month for some sample source.

Gotchas in Event Monitoring

You can monitor two main areas of events: system events or file system events. The two APIs for these are RegisterForEvent and NWAddFSMonitorHook, respectively. These two functions work in a similar manner; they take parameters that specify the event type you wish to monitor and the routine to be invoked when that event is generated. The routine that you provide to these event services become callback routines to the OS.

Callback routines and OS Threads

In the callback routine use something like the example in Figure 13. These operations will ensure that your routine is in the proper context for execution. You can find more details in the NetWare NLM Development and Tools Overview manual in the section "NLM Program Coding Issues."

Sleeping Dogs versus Sleeping Threads

The first routine is the actual callback routine itself. In this routine I set the thread context (as shown above), copy any data passed to the callback routine to a global data structure, then SignalLocalSemaphore and exit the routine. I spin off the other routine as a independent thread somewhere in my main module. The only thing it does is WaitOnLocalSemaphore. Once the semaphore has been signaled, this routine will take the data from the global data structure and process it according to the needs of my NLM.

This may cause some additional work, but it makes a more consistent design and eases implementation of event callback routines.

Notes on RegisterForEvent API

 
Figure 12: Specify the context for the execution
#include 
int globalThreadGroupID;
main()
{

globalThreadGroupID = GetThreadGroupID();
    ...
}

int    oldTGID;
oldTGID = SetThreadGroupID( globalThreadGroupID );
/* Do work */
SetThreadGroupID( oldTGID );
/* always set back the thread group ID */

TELETIPS

TeleTip #1

All of the TeleTips may not appear in Bullets. If you notice you are missing any (they will be numbered consecutively, beginning with TeleTip #1) you can get them from our fax service or from CompuServe.

Cross-Dressed diskettes

TeleTip #2

Where's the Code?

/**************************************************
**   Include headers, macros, function prototypes, etc.
/*-------------------------------------------------
     **   ANSI
     */
     #include 
     #include 

     /*-------------------------------------------------
     **   Windows
     */
     #include 

     /*-------------------------------------------------
     **   Telephony
     */
     #include 
     #include 

/**************************************************
**   This function is the entire program; it is very
**   simple.
**   Prompt user for input, open a stream, make a
**   call and close the stream.
*/
void main(void)
{
     /*--------------------------------------------------
     The following are defined for the first call, acsOpenStream
     */
ACSHandle_t         acsHandle;
InvokeIDType_t      invokeIDType;
InvokeID_t               invokeID;
StreamType_t        streamType;
ServerID_t               serverID;
LoginID_t           loginID;
Passwd_t            passwd;
AppName_t           applicationName;
Level_t                  acsLevelReq;
Version_t           apiVer;
unsigned short      sendQSize;
unsigned short      sendExtraBufs;
unsigned short      recvQSize;
unsigned short      recvExtraBufs;
PrivateData_t       *privateData;
RetCode_t           rCode;
     /*---------------------------------------------------
     **The following are additional variables necessary for
     **acsGetEventBlock
     */
CSTAEvent_t                   eventBuffer;
unsigned short      eventBufferSize;
unsigned short      numEvents;
/*-------------------------------------------------
**The following are for the cstaMakeCall
*/
DeviceID_t                         caller,callee;
/*-------------------------------------------------
**Miscellaneous variables
*/
short done=0;

/*-------------------------------------------------
**Setup parameters for call to open stream. Also prompt user for
**input.
*/
invokeIDType=LIB_GEN_ID;
invokeID=0;                   /*don't need it, but set to zero anyway*/
streamType=ST_CSTA;           /*want to use csta functions*/

strcpy(serverID,"ATT#G3_SWITCH#CSTA#PRV-NMS");

printf("\nEnter your user name:");
scanf("%s",loginID);
printf("\nEnter your password:");
scanf("%s",passwd);
printf("\nEnter your extension:");
scanf("%s",caller);
printf("\nEnter the extension you want to call:");
scanf("%s",callee);

strcpy(applicationName,"Simple App");
acsLevelReq=ACS_LEVEL1;
strcpy(apiVer,CSTA_API_VERSION);
sendQSize=0;             /*default size queue*/
sendExtraBufs=0;         /*use default number*/
recvQSize=0;             /*use default size*/
recvExtraBufs=0;         /*use default number*/
privateData=NULL;   /*no private data*/
/*-------------------------------------------------
**Open the stream with above parameters
*/
rCode=acsOpenStream(&acsHandle,invokeIDType,invokeID,streamType,
serverID,loginID,passwd,applicationName,acsLevelReq,
          apiVer,sendQSize,sendExtraBufs,recvQSiz,recvExtraBufs,
          privateData);

if (rCode < 0)
{
     printf("acsOpenStream failure...");
     return;
}
else
{
     printf("acsOpenStream success\n");
     invokeID=rCode;
}
/*-------------------------------------------------
**Block until the confirmation has been received that the stream
**was successfully opened. Just because NetWare returned the
**function code doesn't mean the stream has been opened yet.
*/
eventBufferSize=sizeof(CSTAEvent_t);
rCode=acsGetEventBlock(acsHandle,&eventBuffer,&eventBufferSize,
          privateData,&numEvents);
if(rCode==ACSPOSITIVE_ACK)
{
     if(eventBuffer.eventHeader.eventType == ACS_OPEN_STREAM_CONF)
     {
          printf("ACS_OPEN_STREAM_CONF message has been received\n");
     }
     else
     {
          printf("event type is incorrect...");
          return;
     }
}
else
{
     printf("acsGetEventBlock failure...");
     return;
}

/*-------------------------------------------------
**Now that the stream has been successfully opened,go ahead and
**issue the make call function.
*/
rCode=cstaMakeCall(acsHandle,invokeID,caller,callee,
privateData);

/*--------------------------------------------------
**Now we need to poll for events until a confirmation has been
**received that the PBX has been able to make the call. Note
**that if something is invalid, the program will enter an
**infinite loop, as this simple program just sits and waits
**until a confirmation returns that is successful.
*/
while (!done)
{
     rCode=acsGetEventPoll(acsHandle,&eventBuffer,&eventBufferSize,
               privateData,&numEvents);

     if(rCode==ACSPOSITIVE_ACK)
     {
          if(eventBuffer.eventHeader.eventType == CSTA_MAKE_CALL_CONF)
          {
               printf("CSTA_MAKE_CALL_CONF message has been received\n");
                    done=1;
          }
               else
               {
                    printf("event type is incorrect...");
               }
               }
     }
/*-------------------------------------------------
**All done! Time to close the stream now.
*/
rCode=acsCloseStream(acsHandle,invokeID,privateData);

if (rCode < 0)
{
     printf("acsCloseStream failure...");
     return;
}
else
{
     printf("acsCloseStream success\n");
}
return;
}

TeleTip #3

Don't Walk Through a Closed Door

To open the stream, a program calls acsOpenStream(), which is passed several parameters regarding the type of stream the program wishes to open. The TSERVer returns a completion code to your program. However, this doesn't mean that the stream has been successfully opened. Two components are involved in TSAPI programming.

The first component is the TSERVer, which returns the completion code as a return value in TSAPI function calls. This code tells whether or not the TSERVer was able to accept your function call.

The second component of TSAPI is the telephone switch box (PBX) driver. It handles many of the API requests. To know when the PBX driver has performed an action, Events are passed to a program. These events come in many shapes and sizes (I suggest printing out the .H header files to become familiar with the overwhelming amount of structures) and can be either "solicited" or "unsolicited," depending on whether or not your program specifically requested them.

Receiving Confirmation Events

As a human, I don't notice a difference in the delay, but I guess my computers are more picky regarding "immediate" and "delay." Because I have to cater to my computer when I program, I guess it is important to consider the confirmation events receiving time. For example, I may have one function call that needs to be complete before others can be made. In this case my program needs to pause and wait to receive the confirmation event from that function call.

In future Teletips we will discuss four methods of receiving confirmation. Look for it on the fax server, CompuServe, future issues of Bullets or call 1-800-NETWARE for technical support.

Now that you have a little background about events, let's think about the acsOpenStream function call. If the stream has to be open before any other TSAPI calls can be made, but you don't know how long it will take to receive the confirmation event, how long should you pause your program before attempting to make other calls? If you use the acsGetEventBlock() function, your program will pause until a confirmation event is received. Since the first event that can be received is guaranteed to be an openStream confirmation event (type ACS_OPEN_STREAM_CONF), your program will pause until the stream has been opened. The only other type of event that can be received at this point in the program will indicate that the stream was not able to be opened, and your program cannot proceed to make other TSAPI calls.
Tip: By "blocking" or using the acsGetEventBlock() function after you try to open a stream with acsOpenStream, you can make sure your door is open before trying to walk through it.

Teletip #4

Did You Check All the Books?

After a little time on my part, I decided to look in the DEFINITY System Programmer's Guide, where I probably should have started in the first place. I couldn't find the csatMakeConsultationCall() function documented anywhere. It turns out that the driver doesn't support this call. So I had to program the equivalent of the cstaMakeConsultationCall() myself, first placing the already connected call on hold, and then making a second call.

The bottom line is this: if I would have checked the DEFINITY System Programmer's Guide first, I would have saved myself a lot of time.
Tip: Though the TSAPI programmer's guide lists the functions provided by TSERVer, it is important to use the programmer's guide for your specific PBX as the reference of what is supported by your driver. Just because TSAPI provides it doesn't mean the service is available through your driver.

© 1994 Novell, Inc. All rights reserved. Novell, the N design, NetWare, DR DOS, Btrieve, XQL and LANalyzer are registered trademarks; LAN WorkShop, NetWare SFT III, NetWare Loadable Module, NLM, Global MHS, NetWare MHS, NetWare System Calls for DOS, NetWare Runtime, NetWare SQL, NetWare Btrieve, Report Executive, NetWare Asynchronous Services Interface (NASI), NetWare Management System, Xtrieve PLUS, Novell Labs, UnixWare, AppWare, AppWare Foundation, ALM, Visual AppBuilder, IPX, and MacIPX 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 and Visual Basic are trademarks of Microsoft Corporation. Macintosh is a registered trademark of Apple Computer, Inc. CompuServe is a registered trademark of CompuServe Corporation. NFS is a registered trademark of Sun Microsystems, Inc. UNIX is a trademark of UNIX Systems Laboratories, Inc. in the USA and other countries. UNIX Systems Laboratories is a wholly-owned subsidiary of Novell, Inc. WATCOM is a registered trademarks of WATCOM Systems, Inc. Novell, Inc. makes no representations or warranties with respect to any NetWare software and specifically disclaims any express or implied warranties of merchantability, title or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program or claims by any party other than you. Novell strongly recommends you make a backup before any software is installed. Technical support for this software may be provided at the discretion of Novell.

NOVELL PROFESSIONAL DEVELOPERS' PROGRAM

How to Become One of Our Developers

This program is designed for a wide range of developers who design and create commercially available solutions. This includes commercial developers, called Independent Software Vendors (ISVs), and vertical application developers who create applications for specialized markets such as manufacturing, medicine and law.

Key Features

• Co-Marketing Support
  Members can participate in the YES Program, which offers a variety of co-marketing opportunities as well as ongoing information about Novell's direction. The ultimate goal of the YES Program is to make it easy for customers to identify and purchase products that are optimized for Novell platforms.
• Technical Support
  To obtain product information and technical support, phone 1-800-RED-WORD (1-800-733-9673) or 1-801-429-5281.
• Skills Transfer
  Members may participate in the Skills Transfer Workshops conducted by a Novell specialist. The workshops offer cutting-edge training on solution design, development and implementation. Members may also attend Novell Compass Special Interest Groups, where they have the chance to review products and provide feedback directly to Novell development teams.
• Project/Opportunity Services
  Members have access to Novell expertise through the developer forums on CompuServe. These forums address developer issues including technical information and support for Novell products and development tools.
• Information Services
  As a developer, you receive Novell Developer Notes, a publication targeted at network software developers. Other publications are also available: Bullets, a monthly technical journal; Appnotes (subscription only), a technical journal for network design; and the annual Developer Guide to Programs, Products, and Services. Members also get access to Novell's NDEVSUP CompuServe forum_an electronic meeting place where developers can exchange information with each other and with Novell staff members.
• No Program Fees
  Membership in this program is free of charge and open to all developers. If you would like further information about the Professional Developers' Program or would like to apply for membership, please phone 1-800-RED-WORD (1-800-733-9673) or 1-801-429-5281. If you would like to order Novell development tools, please call 1-800-RED-WORD. You may also contact the program administrator by E-mail at the following address: devprog@novell.com.

FROM THE COCKPIT

Why isn't Mad Poarch writing this column? Novell has experienced some significant changes over the past several months. First, we have completed the spin-off of the Btrieve and NetWare SQL technologies to a newly formed company, Btrieve Technologies, Inc. in Austin, Texas. Quite a few of Novell's Austin-based employees have become part of the BTI Developer Support organization including the former Director of Developer Support, Mad Poarch. Novell wishes them the very best!

We have relocated the Developer Support function as well as Developer Programs from Austin, Texas to Provo, Utah. As the new head of the Developer Support group, I want to share a few of my thoughts about our new organization and what you can expect of us in the future.

Of course, the BTI spin-off has not only affected Novell internally, but has also had an effect on our ability to be responsive to you, our development partner. During the past several months we have re-established the expertise lost in the spin-off. We are now prepared to support users of our SDKs and toolkits, including the new Telephony technology, AppWare Foundation, UnixWare and of course our traditional client and server APIs.

BTI is now the sole source of support for Btrieve products and development tools, Xtrieve and SQL. Call BTI at 1-800-BTRIEVE for customer support of these database products. With the formation of BTI and the completed transfer of the Btrieve technologies to BTI, Novell's Developer Support organization is now concentrating on supporting the Novell APIs as delivered in SDK form. We have many ways you can contact us, including a newly enabled e-mail mechanism:

     Voice:    1-800-NETWARE
          (or 1-801-429-5588)
     CompuServe/NetWire: GONetWire, Developer Support Forum
     -or- Post directly to
     Novell DevSup @ 76701,171
     Fax: 1-801-429-2990
     E-mail: DEVSUP@NOVELL (MHS)
     DevSup@Novell.com (SMTP)
     FaxBack Info:  1-800-NETWARE
          (or 1-801-429-5588)
          1-800-RED-WORD

You will notice that this issue is number 4 even though it is the September issue. With the Austin-to-Provo transition, we saw four months pass without producing an issue. Now that the transition is complete, you can expect to see regular, monthly publication of future issues of Bullets.

Many of us are new to this effort, but you will find that we're excited to work with you. We believe our opportunity for growth with you is vast and encouraging. In addition, we will be a strong and supportive advocate for your needs to the rest of the Novell organization. Jared Blaser Director Developer Support/Services

DEVELOPER EDUCATION

Available Novell Developer Education Courses

930 - Developing NetWare Loadable Modules  (NLMs)
940 - NetWare Programming: Basic Services
941 - Directory Services
945 - NetWare Programming: Protocol Support
950 - Visual AppBuilder
954 - -ALM Development
958 - The AppWare Foundation

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

Novell Labs

Novell Developer Relations

Voice

Fax

NetWire on CompuServe

E-mail: MHS or Internet (SMTP)