Preparing the Database Server | ODBCLink/SE Reference Manual |
To change the network assurance parameters, you must bring the network down. The sequence of commands used to set network assurance parameters are as follows:
:HELLO MANAGER.SYS :NMMGR
Next, press the function keys in the sequence shown in the following example (these function key labels are for MPE/ iX 5.0):
F1 Open Config
F2 NS
F2 Unguided Config
F1 Go To Netxport
F2 Go To GPROT
F2 Go To TCP
:
Modify values for Connection Assurance Interval (e.g. 60) and Maximum Connection Assurance Retransmissions (e.g. 2).
:
F6 Save Data
Note: Connection assurance parameter values control polling times on all active server LAN connections (not just ODBCLink/SE connections). More frequent polling uses more server CPU time and increases LAN traffic.
Starting and Stopping the Listener
To start the listener on the HP3000 data base server, enter:
STREAM ODBCJOB.ODBCSE.SYS
Note: PM and NM capability is required to start the listener job, therefore it is normal for the job to be started by
MANAGER.SYS.
To start the listener on the HP9000 database server, enter:
/usr/bin/odbcse/odbclnse server | On a 9.x server |
/opt/allbase/bin/odbcse/odbclnse server | On a 10.x server and 11.x server |
Note: You should start the listener as root
Note: When the server is started it makes a call to sqlver and puts the output into a file called odbcver in the same directory that the server is running from. For this reason, upon startup, it may take 20 or more seconds for the program to return. The odbcver file is used to determine the DBMS version for a SQLGetInfo call. If the odbcver file is deleted the SQLGetInfo call for DBMS version will return “UNKNOWN”
| ODBCLink/SE |
8 | ©M.B. Foster Associates Limited |
