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

SQL/MX Statements
HP NonStop SQL/MX Release 3.2.1 Reference Manual691117-005
2-285
Manage System-Clustered Tables
ROLLBACK [WORK]
specifies that the operation should be terminated. The effect is the same as
issuing a separate RECOVER command with the CANCEL option. ROLLBACK
WORK may only be specified in the last on-error clause.
ONCOMMITERROR commit-options
specifies what action SQL/MX should take if a retryable error occurs during
Commit Phase. Retryable errors include file in use, lock request timeouts,
resource unavailability, and BEFORE/AFTER time window misses.
A nonretryable error always causes SQL/MX to cancel changes to the
database and terminate the operation, no matter what you specify in the
ONCOMMITERROR option.
ONCOMMITERROR is recursive because it appears within a COMMIT option
and specifies another COMMIT option. You can specify up to three COMMIT
options on a single statement; specifying four or more causes an error.
RECLAIM | NO RECLAIM
specifies whether SQL/MX should automatically start ORSERV processes
to reclaim unused freespace in affected partitions (RECLAIM) or whether
the user must manually perform FUP RELOAD operations (NO RECLAIM).
Partitions which contain unused freespace have the
UNRECLAIMEDSPACE (F) flag set in the file label. Until the freespace is
reclaimed the flag remains set and any new MODIFY, DUP, or BACKUP
operation you attempt to perform on the object will fail with error 20290
(operation still in progress). DML operations can be performed on the
object, but all other operations will fail. If omitted, the default for hash
partitioned objects is NO RECLAIM. The option will be ignored in situations
where MODIFY does not need to reclaim freespace.
Manage System-Clustered Tables
A system-clustered table has no primary key and no STORE BY clause. Its primary
key defaults to the SYSKEY.