RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

CREATE CATALOG BCAT LOCATION $DATA01;
3. If you want each catalog to be seen from both systems, register your primary and backup
catalogs.
To register the primary catalog on the backup system, issue a REGISTER CATALOG command
on the primary system.
To register the backup catalog on the primary system, issue a REGISTER CATALOG command
on the backup system.
The format of the REGISTER CATALOG command is:
REGISTER CATALOG catalog ON node.volume;
Where catalog is the local catalog, node is the remote system where you want the local
catalog registered, and volume is where the local catalog is to be registered on the remote
system.
For example, this command (if executed on the primary system) registers the primary catalog
on volume $DATA00 of the backup system:
REGISTER CATALOG pcat ON \bnode.$data00;
This command (if executed on the backup system) registers the backup catalog on volume
$DATA00 of the primary system:
REGISTER CATALOG bcat ON \pnode.$data00;
4. Create the schema on the primary system.
If you do not use the LOCATION clause, NonStop SQL/MX will set the subvolume itself. In
that case, you must query NonStop SQL/MX to obtain the subvolume name because the
subvolume name is needed when creating the schema on the backup system.
If you specify the LOCATION clause, the subvolume name must start with "ZSD" and the entire
name must be eight characters in length.
For example, if issued on the primary system, this command (without a LOCATION clause)
creates a schema called PCAT.SCH on the primary system:
CREATE SCHEMA PCAT.SCH;
If you omit the LOCATION clause, then, after creating the schema, you must use this query to
obtain the subvolume of the schema (where you fill in the correct node-name, schema-name,
and catalog-name):
SELECT S.schema_subvolume
FROM NONSTOP_SQLMX_node-name.system_schema.schemata S,
NONSTOP_SQLMX_node-name.system_schema.catsys C
WHERE S.schema_name = 'schema-name' AND
C.cat_name = 'catalog-name' AND
S.cat_uid = C.cat_uid;
Node-name is a Guardian system name that excludes the backslash (\).
In this example, the node-name is PNODE, the schema-name is SCH, and the catalog-name
is PCAT.
SELECT S.schema_subvolume
FROM NONSTOP_SQLMX_PNODE.system_schema.schemata S,
NONSTOP_SQLMX_PNODE.system_schema.catsys C
WHERE S.schema_name = 'SCH' AND
C.cat_name = 'PCAT' AND
S.cat_uid = C.cat_uid;
For the rest of this procedure assume that the above query returns the value ZSDXYZ3A.
5. Create the schema on the backup system using the same schema name and the same subvolume
name as on the primary system.
Because RDF is replicating based on the underlying Guardian file locations, you must use the
LOCATION clause. If you specified the LOCATION clause when creating the primary system's
308 NonStop SQL/MX and RDF