SQL/MX 2.x Reference Manual (H06.04+)

Introduction

HP NonStop SQL/MX Reference Manual—540440-003

1-5

Transactions in MXCI

A transaction can be user-defined or system-defined. If you attempt to exit an MXCI

session when either type of transaction is active, MXCI prompts you to specify whether

to commit or roll back the work of the transaction as follows:

There is an active transaction. Do you want to commit the

transaction?

Y to commit transaction

N to abort transaction

Any other key to resume:

During an MXCI session, if the input is read from a file rather than from the keyboard

and a transaction is active when MXCI reaches the end of the input file, that

transaction is rolled back. You must issue a COMMIT WORK or ROLLBACK WORK

explicitly within the command file (after the DML statements).

Query Interruption and Termination in MXCI

In MXCI, you can interrupt and terminate a statement or command by pressing the

MXCI break key. The MXCI break key can be either Ctrl-c, Ctrl-Break, or the

OutsideView Break icon, depending on your interface.

After you press the MXCI break key, the statement or command terminates, and MXCI

returns this message and prompts you to enter another statement or command:

***WARNING[15033] Break was received.

When you use the MXCI break key to terminate a transaction, the transaction might or

might not be rolled back. Execute the SHOW SESSION command to determine the

status of the transaction.

Security

Authorization to access SQL/MP objects is maintained by the Guardian environment

and checked by NonStop SQL/MP. Each object has associated security values that

determine who can read, write to, execute, and purge the object.

SQL:1999 uses authorization IDs to identify users during the processing of SQL

statements. An SQL/MX authorization ID is a valid Guardian user name, enclosed in

double quotes. Authorization ID is not case-sensitive.

SQL:1999 specifies two special authorization IDs:

•

PUBLIC - all authorization IDs known to the network at all times

•

SYSTEM - the implicit grantor of privileges to the creators of objects. You cannot

specify SYSTEM on any DDL statement. It is an internal mechanism, mentioned

here only because it is visible from a query of the metadata.