ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-56
Configuring SQL/MP
called MYPROC implemented in server class SPROCS on a Pathway system with
Pathmon $PMON1, issue the following command:
NOSCOM> ADD PROCEDURE myproc $pmon1 scprocs
See “Managing Customized Catalogs,” in the NonStop ODBC Server Reference
Manual for an explanation of the full set of parameters of ADD PROCEDURE. A stored
procedure name can be registered in any number of NonStop ODBC Server catalogs.
Stored procedure entries in several NonStop ODBC Server catalogs can all refer to the
same service in the same server class of the same Pathway system. Stored
procedures registered in NonStop ODBC Server catalogs can refer to several different
Pathway systems.
Registration of the stored procedure in the NonStop ODBC Server catalog should be
the last step in the configuration procedure, because after it has been completed,
clients can start executing stored procedures.
A NonStop ODBC Server catalog from a previous version of the NonStop ODBC
Server must first be upgraded before a stored procedure can be registered in it.
Configuration of the Pathway system (server class definition, for example) is
independent of the NonStop ODBC Server. If the Pathway system configuration is
changed in any way, necessary changes in the NonStop ODBC Server catalogs must
be done manually. For example, if the server class name in the preceding example
were changed from SPROCS to NEWSPROCS in the Pathway system, the stored
procedure name would have to be dropped from the NonStop ODBC Server catalog or
catalogs by using REMOVE PROCEDURE and registered again with the proper server
class name.
The NonStop ODBC Server system does not monitor the state of the Pathway system.
When a client executes a stored procedure, the NonStop ODBC server process simply
builds and issues a ServerClass_Send. If the Pathway system is down or
misconfigured, the NonStop ODBC server receives an error, which it returns to the
client.
Configuring SQL/MP
Some SQL/MP configuration is done by executing special statements from the
application. For example, you can issue a CONTROL statement to turn parallel
execution on or off. See the NonStop SQL/MP Reference Manual for a full list of
configuration statements.
The NonStop ODBC Server client application can do the same configuration by issuing
the necessary SQL/MP statements in the pass-through mode. This technique is useful
only for client applications that can be extended to issue the extra statements. It is not
useful for self-contained client applications that build the SQL statements for the user.
To extend the ability of the NonStop ODBC Server user to configure SQL/MP, some of
the configuration can now be done by setting DEFINEs on the NonStop system; the
client application is not changed at all. Any DEFINEs available to SQL/MP can be
used.