RDF System Management Manual for H-Series RVUs (RDF 1.8)

You should specify only the desired volume to allow NonStop SQL/MX to generate the
complete Guardian filenames. This is true for non-partitioned objects as well as for
partitioned objects. Thus, you specify only the volume name in the LOCATION clause,
and NonStop SQL/MX constructs the fully qualified Guardian name for the object,
using:
• The volume you specified for the object in the LOCATION clause.
• The subvolume associated with the object's ANSI schema (as indicated in that portion
of the object's ANSI name).
• The system-generated Guardian filename. In this case, you must obtain the underlying
Guardian filename using SHOWDDL or a metadata query before you can set up your
backup database.
Now, the full CREATE TABLE statement for CAT.SCH.TAB1, including the full Guardian
names of the partitions, can be displayed in MXCI by using the command:
SHOWDDL PCAT.SCH.TAB1;
Assume the system generates these Guardian file names:
$DATA02.ZSDXYZ3A.KQY8KY00
$DATA03.ZSDXYZ3A.KQY8RK00
$DATA04.ZSDXYZ3A.KQY8YG00
The volumes specified in the LOCATION clauses of the CREATE TABLE statement are
used and that the subvolume is the subvolume created by the CREATE SCHEMA
statement in Step 3.
If you want to specify the complete Guardian filename for your object yourself, you
must use the LOCATION clause specifying the volume on which you want the object
placed and using the Guardian subvolume associated with the object's schema. The
Guardian filename must be exactly eight characters long and end in "00" (zero-zero).
You cannot specify a volume and subvolume portion without also specifying the
filename. All NonStop SQL/MX partitions for a table must have the same Guardian
subvolume name but the Guardian filename will not normally be the same, even if the
partitions are on different volumes.
298 NonStop SQL/MX and RDF