ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-48
Configuring NonStop ODBC Server Catalogs
tables are created. The logical database name is generated as a formatted name,
node_volume_subvolume. Components are taken from the fully-qualified Guardian
subvolume name provided.
Alternatively, you can customize a catalog implicitly using the TSQL CREATE
DATABASE command within a client application, as follows:
CREATE DATABASE database-name [ON disk ]
Database-name is the logical database name visible to clients. If disk is specified, it
must be a Guardian subvolume name. Substitutions for missing subvolume name
are made from the current user environment. If disk is not provided, the database
is created in the user’s current subvolume.
Similarly, as the database administrator you can issue the NOSCOM command,
specifying the logical name:
USERCAT INSTALL Guardian-subvolume AS database-name
The AS clause lets the user set the logical database name to an identifier other
than the previously described formatted database name.
The preceding two commands have equivalent actions. Both build an association
between a logical database name and a SQL/MP catalog, creating the NonStop ODBC
Server configuration and mapping tables and populating these meta-data tables.
To customize an SQL/MP catalog on \NODE.$VOL1.SUB2 and give it the logical name
NODE_VOL1_SUB2, use any of the following commands:
CREATE DATABASE NODE_VOL1_SUB2 ON \NODE.$VOL1.SUB2
USERCAT INSTALL \NODE.$VOL1.SUB2 AS NODE_VOL1_SUB2
USERCAT INSTALL \NODE.$VOL1.SUB2
Using NOSCOM to Install and Deinstall Catalogs
Corresponding commands to de customize (deinstall) an SQL/MP catalog are also
available.
NOSCOM can be used to install and deinstall the system catalog. Typically, NOSINST
installs the system catalog so you do not need to do so. Deinstalling the system
catalog essentially removes the NonStop ODBC Server from the NonStop system.
If you have an earlier version of the NonStop ODBC Server installed and you run
NOSINST with the UPGRADE option, the NOSINST macro upgrades the NonStop
ODBC Server system catalog, but it does not upgrade any of the NonStop ODBC
Note. NonStop ODBC Server applications and SQL/MP applications (such as Pathway
programs) can share SQL/MP catalogs and the objects they contain. If SQL data definition is
done from NonStop ODBC Server clients, the NonStop ODBC Server catalogs are kept
current. If SQL data definition is done from the SQL/MP applications, NonStop ODBC Server
catalogs are not kept current—they must be periodically refreshed by using the utility statement
REFRESH.