SQL/MX Programming Manual for C and COBOL (H06.10+, J06.03+)

C/C++ Program Compilation
HP NonStop SQL/MX Programming Manual for C and COBOL—544617-003
15-54
Deploying a Static SQL Application to an RDF
System
8. Repeat Step 1 to Step 7 until the program is ready for deployment or until you
cannot find any more bugs, whichever comes first. Transfer the program to its
target deployment NonStop system (for example, \batman):
/usr/prod/sprog.
9. Set up needed DEFINEs (none in this case), and run the SQL/MX compiler on the
application executable:
mxCompileUserModule –e –v –d CATALOG=bread –d \
SCHEMA=basket /usr/prod/sprog
This step generates plans that reference tables named bread.basket.seeds,
bread.basket.trees, and bread.basket.crops in the modules named
cat.sch.s1m, cat.sch.s2m and cat.sch.s3m.
10. Set up needed DEFINEs (none in this case), and run and test the program:
/usr/prod/sprog
Deploying a Static SQL Application to an RDF System
This example shows a method to develop and deploy a static SQL C/C++ application
in an SQL/MX Release 2.x RDF system. In SQL/MX Release 2.x, the RDF primary
system’s SQL/MX catalog and schema names might be different from the
corresponding SQL/MX catalog and schema names on the backup system.
Suppose that you want to do all development and module compilations only on the
development system, and you do not want to do module compilations on the RDF
systems if possible. Suppose that you have all your data in SQL/MP tables. To get data
location independence, suppose that you prefer to use class MAP DEFINEs instead of
PROTOTYPE host variables for your application’s table names. Table 15-2 lists the
module schemas and export files used in the following discussion.
Table 15-2. Module Schemas and Export Files for RDF SQL Application
Deployment Example (page1of2)
Development RDF Primary RDF Backup
Node name \ROBIN \APPLE \INDUS
Module
schema for
primary
TELCO.MODULES TELCO.MODULES
Module
schema for
backup
COMMS.MODS COMMS.MODS
OSS
directory for
primary
/usr/primary /usr/alpha