SQL/MX 2.x Database and Application Migration Guide (G06.23+, H06.04+, J06.03+)

Falling Back to SQL/MX Release 1.8
HP NonStop SQL/MX Database and Application Migration Guide—540435-005
8-8
Reconfigure the NonStop ODBC/MX Server and
Driver
The mxinit script creates the PROCS and PARAMS tables, the MPALIAS and
DEFAULTS tables, and ODBC tables (ZONAM2ID, ZODS, ZODT, ZOAS2DS, ZORES,
ZOENV) in the same subvolume as the system catalog. These tables are registered in
the system catalog.
mxinit creates a link for MXCI from /usr/bin/ to /usr/tandem/sqlmx/bin/ so
you can enter commands without typing in the full path. For more information about
installing and configuring NonStop ODBC/MX and starting the NonStop ODBC/MX
server, see the
ODBC/MX Manual.
Reconfigure the NonStop ODBC/MX Server and Driver
Because the NonStop ODBC/MX server configuration is stored in different metadata
tables in SQL/MX Release 1.8 and SQL/MX Release 2.x, you do not have to create the
tables after fallback.
After installing a previous RVU, however, you must propagate the NonStop ODBC/MX
module files from T7970PAX and use the NonStop Software Manager to change the
ODBC/MX configuration tables as required. For more information, see the
ODBC/MX
Manual.
If necessary, reinstall the previous NonStop ODBC/MX driver from the ZMXODBC
subvolume after fallback. If you migrated client data sources, you must remove the
migrated data sources and create new data sources by using the reinstalled driver. For
more information, see the
ODBC/MX Manual.
Fall Back SQL/MX Release 2.x Applications and User Modules to
SQL/MX Release 1.8
For instructions, see Managing Module Files and Applications During Fallback From
SQL/MX Release 2.x on page 8-9.