SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Managing Database Applications
HP NonStop SQL/MX Installation and Management Guide—523723-004
11- 8
Distributing Programs Across Nodes
°
For an embedded SQL program in C, C++, or COBOL, run the
mxCompileUserModule utility on the production system to SQL compile an
embedded module definition:
mxCompileUserModule myprog.exe
Alternately, run the mxcmp command to SQL compile a module definition file:
mxcmp sqlprog.m
°
For an SQLJ program, run the SQLJ customizer on the production system to
recustomize each profile, and then run mxCompileUserModule to SQL
compile each embedded module definition:
java sqlj.tools.Sqlj MyProg.jar
mxCompileUserModule MyProg.jar
Alternately, run the SQLJ customizer to recustomize each profile and to initiate
SQL compilation of each module definition file:
java sqlj.tools.Sqlj -createMDF=true MyProg.jar
For more information, see the SQL/MX Programming Manual for C and COBOL
and the SQL/MX Programming Manual for Java.
The program is now ready for execution in the production environment.
Distributing Programs Across Nodes
This subsection provides guidelines for running programs in a distributed database
network.
See Section 13, Managing an SQL/MX Distributed Database, for comprehensive
information about managing a distributed database environment.
See the SQL/MX Programming Manual for C and COBOL and the SQL/MX
Programming Manual for Java for information about how to code programs to query
distributed database objects.
Versioning Issues for a Distributed Database Environment
In a distributed database environment that contains Release 2.1, Release 2.0, and
Release 1.8 nodes:
•
Applications compiled on a Release 1.8 node can run and access SQL/MP objects
on Release 2.1 and Release 2.0 nodes.
•
Applications compiled on a Release 2.1 node can query database objects on
Release 2.1 nodes and Release 2.0 nodes.
•
Applications compiled on a Release 2.0 node can query database objects on
Release 2.0 nodes and Release 2.1 nodes.