Tom-
You can avoid the batch job problem by updating to ALLBASE/SQL G.0,
which is available in the MPE/iX 5.0 Pull Release. It is also available
upon special request for 4.0 and 4.5 from the Response Center.
In G.0, there is one listener job that services all connections for the
entire server. Whenever a connection request comes in the listener job
spawns a background process that connects to the database. It then goes
back to listening.
regards, Kriss Rant, HP
Tom Stelter ([log in to unmask]) wrote:
: ----------
: From: Stephanie Evich
: To: Tom Stelter
: Subject: RE: ODBC access to HP3000
: Date: Thursday, December 15, 1994 3:35PM
: Tom - Please forward to HP Listserve: Thanks, Steph:
: Dear Mike:
: I too went thru the "learning experience" or frustration? of the
: incompatibility issues with ODBC & TCP/IP, etc.. LWP .DLL patches & had to
: back them out to lwp168 level. As well, I hit the same problem with the
: odbc.ini file needing to be altered to WS denoting sockets. I kept thinking
: this is it - when another error would hit. Anwyays, I wanted to pass on the
: next encounter I had hoping to help you before you get hit.
: There is an HP alternative solution avail. called the "Roller-coaster Fix"
: for Mpe/ix only to help performance. The PC API works like this :each user
: logging on from PC to HP thru ODBC is counted as 1 JOB DQ vs session CQ and
: runs "Hpipdvr.pub.sys" which you can see by doing a :showproc job=#your job
: num. This can cause 2 problems 1)job limit might not be high enough to
: handle your odbc users & it would be hard to justify opening your jobs to
: unlimited number (potential resource contention). If job limit doesn't
: accomodate odbc logon then when the user connects their job will sit in wait
: state (I believe) on HP & to user it will appear as a Hang. 2)Each ODBC
: connection will be in the Dque (as it's a batch job) which will cause
: performance lag on interactive work.
: The HP fix affords 2 individual work arounds 1)setup so that when ODBC logon
: it gets qued in CQ and 2)job limit can be automatically incremented+1 @ ODBC
: logon & auto decremented-1 @ODBC logoff.
: #1 is done by: :build hpipjlim.pub.sys;rec=-80,,f,ascii and :release
: hpipjlim.pub.sys
: :jobpri cs,ds
: #2 is done by: edit hpipjlim.pub.sys to look like:
: :getrin hpipjlim >hpipjlim.pub.sys
: :release hpipjlim
: 1. use the allow command to allow the ODBC
: jobs to have access to the Limit command.
: Also, HP response center has about 8 pages for public distribution on this
: fix. One note of caution is that this is UNSUPPORTED.
: GOOD LUCK. I hope this helps. Stephanie Evich, Mcare - Ann Arbor MI.
: 313-747-7425, ext. 317
: [log in to unmask]
: ----------
: From: Tom Stelter
: To: Stephanie Evich
: Subject: FW: ODBC access to HP3000
: Date: Thursday, December 15, 1994 02:38PM
: ----------
: From: owner-hp3000-l
: To: Multiple recipients of list HP3000-L
: Subject: ODBC access to HP3000
: Date: Wednesday, December 14, 1994 2:04PM
: Hi there,
: I am looking for some help or suggestions in order to set the HP ODBC driver
: to connect to an HP3000. I have installed the driver on my PC as prescribed
: by the HP instruction manuals. I have also made sure that the software that
: needs to be running on the 3000 is running. I also ran the 'odbcview'
: program against my dbe. The problem that I get when I try to access the
: data in Access 2.0 is the following error message:
: [Microsoft][ODBC DLL] Driver's SQLSetConnectOption failed (#0)
: Driver not capable (#0) PC Sockets Error: 61. (PCSockets !1)
: (#20362)
: The version numbers for the various things are as follows:
: HP3000-928
: MPE iX 4.0
: ALLBASE F0.67
: Image SQL
: ODBC Driver A.F0.17
: On the pc I am running Windows 3.1, connecting to a Novell file server using
: Novell's Lan WorkGroups for Dos. We have version 4.1 installed, but have
: also installed the patches up to and including LWP42T which makes it a 4.2
: version(effectively).
: The questions that I have are:
: Does ODBC work with MPE iX 4.0 and ALLBASE F0, or do either of these need to
: be upgraded to 5.0 or G0 respectively?
: Does anyone else have this running in either this configuration or with Lan
: WorkPlace? Was there anything special you had to do to get it working?
: Does using the GUPTA API make more sense?
: I have talked to HP and they are trying to find out what the problem is.
: However, at this time, their only suggestion is to roll Lan WorkGroups back
: to version 4.1 with patch LWP168 which I can not do.
: Any suggestions, comments or questions would be greatly appreciated.
: Thanks
: Mike Betker
|
