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- 7
Moving a Program Without Compiled Modules
•
The development node catalogs and schemas are not visible from the production
node and vice versa. To ensure this, do not use the REGISTER CATALOG
statement from either node to create an empty catalog reference on the other
node. For more information, see Using REGISTER CATALOG to Access Objects
on Remote Nodes on page 11-9.
•
The program is a single file named myprog.exe for a C, C++, or COBOL program
and MyProg.jar for an SQLJ program. For information about creating a single-
file application for deployment, see the SQL/MX Programming Manual for C and
COBOL and the SQL/MX Programming Manual for Java.
•
The program is in the OSS directory /usr/bin on the development system, and it
will be moved to a directory of the same name on the production system.
Instructions
To move a program without compiled modules to a production system:
1. Copy required program files and executables from a directory on the development
system to an OSS directory on the production system:
°
Issue this OSS command to copy the executable of an embedded SQL
program in C, C++, or COBOL to the production system:
cp /E/DEV/usr/bin/myprog.exe \
/E/PROD/usr/bin/
°
Issue this OSS command to copy an SQLJ program packaged in a JAR file to
the production system:
cp /E/DEV/usr/bin/MyProg.jar \
/E/PROD/usr/bin/
For a list of the program files required for execution, see the SQL/MX
Programming Manual for C and COBOL and the SQL/MX Programming Manual for
Java.
2. If the application refers to SQL/MP tables or views by using DEFINEs, use the
OSS add_define command or the TACL ADD DEFINE command to set up the
class MAP DEFINEs in the production environment. See Setting DEFINEs on
page 11-11.
3. If the application refers to SQL/MP tables or views by using SQL/MP aliases,
create the SQL/MP aliases in the production environment. See Setting SQL/MP
Aliases on page 11-12.
4. Generate a new module or modules for the program:
Note. If you generated a module definition file (.m), make sure to copy that file to the
production system as well.