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

C/C++ Program Compilation
HP NonStop SQL/MX Programming Manual for C and COBOL—523627-004
15-50
Deploying a Static SQL Application to an RDF
System
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.
1. Suppose that the RDF primary system is \APPLE. On \APPLE, suppose that you
want all your user modules to use the schema ‘telco.modules’.
2. Suppose that the RDF backup system is \indus. On \indus, suppose that you are
constrained by SQL/MX Release 2.x RDF rules to use the schema ‘comms.mods’.
3. On the development system \robin, create a development (possibly, zero-row or
empty) copy of your application’s SQL/MP tables (and their statistics) from the RDF
primary system \APPLE. You need not make local copies of the backup system’s
corresponding tables because they will always be similar to the primary system’s
tables.
Table 15-2. Module Schemas and Export Files for RDF SQL Application
Deployment Example
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
OSS
directory for
backup
/usr/backup /usr/beta
=debits
DEFINE for
primary
$data07.ccards.debits $plat.charges.buys
=debits
DEFINE for
backup
$data07.ccards.debits $gold.cards.debits
=credits
DEFINE for
primary
$data17.ccards.credits $plat.charges.pays
=credits
DEFINE for
backup
$data17.ccards.credits $gold.cards.credit