SQL/MX 3.2.1 Management Manual (H06.26+, J06.15+)

NOTE: Because of the 239-character limit for EDIT files, MXGNAMES cannot support table names
in the input file whose overall length is greater than 239 characters, including the dots separating
the catalog, schema, and table name portions. Such names have to be specified individually on
the MXGNAMES command line.
SHOWDDL File
SHOWDDL output is commonly saved to an OSS format text file, which has to be converted using
CTOEDIT before being used as input to MXGNAMES.
NOTE: The SHOWDDL file cannot be converted to an EDIT file if it contains an ANSI table name
whose overall length is greater than 239 characters, including the dots separating the catalog,
schema, and table name portions. Such names have to be removed from the file, and submitted
individually to MXGNAMES by the command line.
MXGNAMES Output Files
If MXGNAMES generates multiple output files, duplicate file names can result. To help avoid such
problems:
• Specify shorter file names so that extra digits can be appended without overwriting characters
from the original name.
• Avoid using digits at the end of the output file name.
Using Output Files With RESTORE to Create an RDF Backup Database
For the RESTORE command of Backup and Restore 2, LOCATION clauses contain both the source
and target file names. For RDF backup database creation, the source and target file names must
match in the volume, subvolume, and file name portions. Only the node names can differ.
Using Output Files With TMF
The output format for TMF is designed to meet the definition of the file set command line argument.
TMF defines certain limits for a specified file set:
• TMF limits the size of a command file and the number of files that can be specified. The
maximum size of a command file is 28000 bytes. You can use the -length option to control
the size of the output file, while allowing for other text to be manually added to the command
file without exceeding the 28000 byte limit.
• TMF commands allow a maximum of 900 file names. If a -length option is specified,
MXGNAMES starts a new file when either that length or 900 file names is reached, whichever
comes first.
Resource forks must be explicitly dumped and recovered, so file names are listed as wild cards
that include the resource forks.
Non-Local File Names With TMF
If you use the -nocomment option with the -TMF option, nonlocal file names are included as
comments in the output file, and the relevant nodes are displayed as warnings to standard output.
For example, if the local node is called \PNODE, any files on node \XNODE are listed as
comments.
Regardless of the -nocomment option, and whether -TMF or -RDF is specified, the standard
output will receive a list of all remote nodes that were encountered during the processing of the
command.
MXGNAMES Examples
For these MXGNAMES examples, suppose that these SQL/MX tables and indexes exist on the
system:
310 Using Guardian Names with TMF, RDF, and Measure