We have a challenge that our DSN's and Database Names change often and we want to provide redundancy for that. 

We see we can configure Pervasive Engines to point to DBNAMES.CFG on a Netware 6.5sp7 clustered volume.  We have that engine configuration option pointed succesffuly to the file copied into a folder we created named VOL1:\PVSW\BIN, and it works great.

 But....

Redundancy is incomplete if we can not also put ODBC.INI on the same shared cluster volume.

We have tried many options to place ODBC.INI on the shared cluster volume VOL1: and changed MGRSTART.NCF to point to ODBC.INI placed in our manually created VOL1:\ODBC  redundant location.  No matter what we do NWSQLMGR.NLM compalins it can't find the database names file when it loads.  Even when we just move this one file.  The location named in that load line is valid and VOL1 is mounted before the load attempt. 

This works (stock):   load nwsqlmgr sys:\odbc\odbc.ini 

This does not (desired) :  load nwsqlmgr vol1:\odbc\odbc.ini

Seems easy and logical.  Doesn't work.  How can we convince NWSQLMGR.NLM to load using ODBC.INI on a volume other than SYS:?  Without that we do not have full database names/dsn real-time redundancy.  And it gets a little ugly keeping dbnames.cfg and odbc.ini in sync.  Many thanks, Jim

The location of the odbc.ini appears to be hardcoded in the nwsqlmgr.nlm   It will start even if the parameter is not provided.

Jose 

If it is truly hard-coded, then an enterprising user could ensure that the name of the "cluster" volume is also three characters and then just edit the NWSQLMGR.NLM file to change that file to the new location.  Might cause problems with patching later on, but if you can put the old file back for any future updates, it sounds like it would work...