Gentle listers -

The only outstanding item on my list of upgrade MPE/iX 5.5pp7 to MPE/iX
6.0pp2 is ODBClink/SE "problems".

Our production box is running MPE/iX 5.5pp7, with ODBCLink/SE version
E.55.02, all is fine.

The version bundled in MPE/iX 6.0 (not sure exactly which tape etc, but...)
is labelled both 5.57.08 and E.57.08; that's fine too.

Upgrading the client boxes' is required to use the new host version, and my
DBA tells me his testing showed that the new version (client side) is not
backward-compatible either.  The upgrade's pretty simple, but (I think) this
presents me with a timing problem, as there are several client boxes which
will be expected up and running immediately after our production e3000
upgrade.

Per HPREADME.ODBCSE.SYS,
===================
This is the README file for ODBCLink/SE Version E.57.08. To
install this version of the product, stream I00IODBC.ODBCSE.SYS.

** IMPORTANT NOTICE: I00IODBC.ODBCSE.SYS will purge files
belonging to the installed version of the product from ODBCSE.SYS
and install new files. You may need to upgrade ODBCLink/SE drivers
on your client PCs to work with the new version of the server.

I don't remember manually streaming this job when I upgraded the dev box to
6.0, so I'm left assuming it's one of the seemingly hundreds "automagically"
streamed during the checklist G procedure, but I'm not sure knowing that
will resolve the timing issue anyway. (Shall I make that question #1?)

Is there some way I can
1) demonstrate that 5.57.02 actually IS backward compatible (in which case
we simply upgrade the clients in advance of the server), or
2) arrange for the clients to automagically swap DLL's when they see the
"5.57" required, 5.55 found; upgrade your client!" message?
3) dynamically support both client versions from the host?


K Tracy Pierce, Systems Programmer
Golden Gate Bridge, Hwy & Trnsp Dist
PO Box 9000, Presidio Station
San Francisco, CA  94129-0601
mailto:[log in to unmask]
415-923-2266