NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
F-30
Examples—Filesets
Notice that a single Guardian name that includes wild-card characters can represent a
fileset that includes many files. You cannot use a wild-card in the node portion of a
Guardian name that specifies a fileset.
You can use a DEFINE to specify a fileset, but you cannot use wild-card characters in
the DEFINE name or in the file name you specify on the DEFINE. As a result, a fileset
you specify with a DEFINE always consists of a single object or file.
Many SQLCI commands allow you to use filesets or fileset lists to specify a set of tables
and files for the command. A fileset list can be a simple fileset list or a qualified fileset
list.
A simple fileset list is a list of one of more filesets in the following form:
{ fileset }
{ ( fileset [ , fileset ] ... ) }
A qualified fileset list can include clauses that restrict the files in the set in various ways.
See Qualified Fileset List
on page Q-1 for details.
Examples—Filesets
•
The following FILEINFO command requests information about the fileset that
includes all files on subvolume \NY.$HDQTR.HR:
FILEINFO \NY.$HDQTR.HR.*;
•
The following PURGE command purges the fileset that includes all files on
subvolume SV3 with names that end in X:
PURGE SV3.*X;
FREE RESOURCES Statement
FREE RESOURCES is a DCL statement that releases locks, closes cursors, and flushes
insert/update buffers for audited and, optionally, nonaudited objects.
The exact effect of FREE RESOURCES depends on how the locks were acquired,
whether the affected objects are audited or nonaudited, and whether a transaction is in
progress, as explained later in this entry.
You can use FREE RESOURCES instead of explicit UNLOCK TABLE or CLOSE
CURSOR statements. COMMIT WORK and ROLLBACK WORK automatically
perform all the operations of FREE RESOURCES.
AUDITONLY
directs SQL to retain existing locks on nonaudited objects.
FREE RESOURCES [ AUDITONLY ] | [ CLOSE TABLES ]