SQL/MX 2.x Installation and Management Guide (G06.24+, H06.03+)

Planning Database Security and Recovery
HP NonStop SQL/MX Installation and Management Guide—523723-004
5-19
TMF Considerations in Using MXCI
The corresponding DUMP FILES command to dump only the files in this table would
be:
DUMP FILES &
( &
$DATA1.ZSDADLON.NSPD2Q00,&
$DATA2.ZSDADLON.N0FK2Q00,&
$DATA3.ZSDADLON.N75R2Q00,&
$DATA4.ZSDADLON.OFVY2Q00,&
$DATA5.ZSDADLON.ONL42Q00,&
$DATA1.ZSDADLON.R70U5Q00,&
$DATA2.ZSDADLON.SFQ15Q00,&
$DATA3.ZSDADLON.SNG85Q00,&
$DATA1.ZSDADLON.NSPD2Q01,&
$DATA2.ZSDADLON.N0FK2Q01,&
$DATA3.ZSDADLON.N75R2Q01,&
$DATA4.ZSDADLON.OFVY2Q01,&
$DATA5.ZSDADLON.ONL42Q01,&
$DATA1.ZSDADLON.R70U5Q01,&
$DATA2.ZSDADLON.SFQ15Q01,&
$DATA3.ZSDADLON.SNG85Q01 &
)
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
starts 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.