SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—540440-003
5-67
Considerations for MXGNAMES
-HELP
displays help for the utility.
Considerations for MXGNAMES
You must have READ/WRITE access to the Guardian subvolume where you are
executing MXGNAMES.
Input and output of MXGNAMES is in standard Guardian EDIT files, which have these
characteristics:
•
Guardian file code of 101
•
Maximum line length of 255 characters
You can use other tools or programs to capture data for use with MXGNAMES. To use
the captured data with MXGNAMES, you might need to convert the file to the EDIT
format. You can use tools such as CTOEDIT to perform the conversions.
Temporary Work Files
MXGNAMES might generate temporary workfiles during execution. These files are
placed in the current volume and subvolume. You must have authority to read and
write to this location, or MXGNAMES generates an error and halts execution.
Examples of MXGNAMES
•
Suppose that these SQLMX tables and indexes exist on the system:
create table CAT.SCH.T126A
( c1 int not null
, c2 timestamp default current_timestamp not null
, c3 char(4) default 'abcd'
, c4 smallint not null
, primary key (c1,c2) )
location $VOL1.ZSDA126A.BXNL1R00
partition
( add first key (1r00) location $VOL2.ZSDA126A.BXNL2R00
, add first key (2r00) location $VOL3.ZSDA126A.BXNL3R00
, add first key (3r00) location $VOL4.ZSDA126A.BXNL4R00
, add first key (4r00) location $VOL5.ZSDA126A.BXNL5R00
, add first key (5r00) location $VOL6.ZSDA126A.BXNL6R00 )
store by primary key;
create index T126A_NDX1 on CAT.SCH.T126A(c4)
location $vol1.ZSDA126a.qdxwg100
partition
( add first key (100) location $VOL2.ZSDA126A.QDXWG200
, add first key (500) location $VOL3.ZSDA126A.QDXWG300
, add first key (700) location $VOL4.ZSDA126A.QDXWG400 )
;
create table CAT.SCH.T126B
( c1 timestamp default current_timestamp not null
, c2 int not null
, c3 varchar (30)
, c4 smallint not null
, primary key (c4, c1) )