HP3000-L Archives

May 1995, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Peggy Lacy <[log in to unmask]>
Reply To:
Peggy Lacy <[log in to unmask]>
Date:
Wed, 10 May 1995 18:40:03 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
There are several different data communication servers and PC API servers.
 
How you invoke these servers is dependent on the version of allbase you are
running,  the version of pc api you are running on the client, and the network
stack/library you are using for data communication between the client/server.
 
Judging from the error message you are receiving, you are trying to use the
Novell ipx/spx stack to communicate to your server. (The server better be a
3000 because we do not support connections to portable netware on HP-UX.)  If
you are trying to use native ipx/spx, you must be running Netware/iX on the
3000.  Currently api connection on ipx/spx are only supported on MPE/iX 4.0.
 
You must first bring up netware transport on the server by logging in as
MGR.NETWARE and issuing the NW START command.  This will stream a job,
NETWARE,MGR.NETWARE.  Wait a few minutes for initialization.  Issue the NW
STATUS command until both Transport and Server show up as active.
 
Now you must start the pc api listener:
Logon as MANAGER.SYS and issue the NWSTART command.
 
 
Another hint is:  If you have more than one netware server on your network, you
must specify the network and node name of your api server in your ODBC.INI
file.
This documented in the manual and the readme.hp file.
 
Please call the Response Center if you have any additional questions.

ATOM RSS1 RSS2