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

Note how individual resource fork names are accounted for. Alternately, the same list could have
been specified:
DUMP FILES &
( &
$DATA1.ZSDADLON.NSPD2Q0?,&
$DATA2.ZSDADLON.N0FK2Q0? &
$DATA3.ZSDADLON.N75R2Q0?,&
$DATA4.ZSDADLON.OFVY2Q0?,&
$DATA5.ZSDADLON.ONL42Q0?,&
$DATA1.ZSDADLON.R70U5Q0?,&
$DATA2.ZSDADLON.SFQ15Q0?,&
$DATA3.ZSDADLON.SNG85Q0? &
)
In this case, the final question mark (.SNG85Q0?) includes both the data fork and the resource
fork.
TMF Considerations in Using MXCI
• For DML statements, MXCI generates TMF transactions for individual statements if the
AUTOWORK session option is set to ON. If you set AUTOCOMMIT to OFF, disabling automatic
transaction generation for DML statements, NonStop SQL/MX will start a transaction for you
if necessary. The SQL/MX statements that explicitly control transactions are BEGIN WORK,
COMMIT WORK, and ROLLBACK WORK. AUTOCOMMIT ON is the default.
• With AUTOCOMMIT set to either ON or OFF, you can explicitly define a TMF transaction,
also called a user-defined TMF transaction. Use a user-defined TMF transaction to ensure that
several statements are either all executed successfully or all rolled back.
These commands and statements make up a complete user-defined TMF transaction:
◦ BEGIN WORK;
◦ SELECT...;
◦ INSERT...;
◦ DELETE...;
◦ COMMIT WORK;
• For many utility statements, the utility operation generates the appropriate number of TMF
transactions for the operation, reducing the overhead associated with TMF audit trails and
ensuring that the necessary locks are acquired for the operations. These operations do not
allow or do not recommend using user-defined TMF transactions and work the same way
regardless of the value of AUTOCOMMIT. Utilities include DUP, FASTCOPY, MODIFY,
POPULATE INDEX, PURGEDATA, RECOVER, and UPDATE STATISTICS.
• It is not recommended that user-defined transaction be started certain for DDL operations
including CREATE INDEX, ALTER TABLE ADD CONSTRAINT, ALTER TABLE ADD COLUMN,
compound CREATE SCHEMA, or DROP SCHEMA.
• Only one user-defined TMF transaction can be active at a time in an MXCI session. You must
commit or roll back the current user-defined transaction before starting another.
Using TMF In Recovery Operations
All SQL/MX files are audited by TMF. Therefore TMF provides the most comprehensive and robust
means of recovery. With TMF volume recovery and file recovery mechanisms, you can recover
SQL/MX catalogs and objects after a system or disk volume failure. You can also use file recovery
to recover a dropped object or a database to a specified time. These recovery operations, and
Using TMF for Transaction Recovery, Database Consistency, and Database Recovery 55