HP NonStop G-Series Guia do Utilizador descarregar pdf (Página 22)

MXCS Architecture Overview

SQL/MX Connectivity Service Administrative Command Reference—526350-005

1-4

User Interface With MXCI

The MXCI interface with MXCS administrative commands is similar to its interface for

the report writer or SQL command handlers. The basic features are:



MXCS commands terminate with a semicolon (;), with command input occurring

only after the semicolon is entered. Enclose embedded semicolons in single or

double quotation marks.



If the MXCS mode is set, the prompt changes from >> to CS> for terminal users,

but not for log file or non-tty input streams. After you set the MXCS mode, all

commands go to MACL until you either reset the mode or enter exit. In MXCS

mode, basic SQL commands generate syntax errors.



MXCI manages batch input files and output log files as usual, but now these files

can contain MXCS commands (preceded by the mode command).



MXCI passes a break event to MACL for handling. If a command is in progress,

MACL stops generating report and error messages.



No support exists for critical section or rollback events for MACL commands.

These commands immediately complete. When a command initiates change in the

MXCS environment, a break event arrival could interrupt the process. To determine

if a break event is successful, check state information for the object in the current

command.



If an outstanding transaction exists, attempts to switch to the MXCS mode in MXCI

fail with an error message. For example, executing queries with autocommit set

to off (default is on) or having an open BEGIN WORK transaction causes failures.



MACL supports no variable expansion in its input commands.

General Features



Asterisk (*) is the only wild card supported in command names, but only for specific

commands. No patterns are supported. Wild card *xyz or a?b causes an error.



The asterisk (*) wild card applies only to objects on the specific system supporting

the MXCI process. See Command Rules and General Syntax on page 2-3.



Object name defaulting is supported to reduce typing. The most recent object

named of each type persists until it is changed.



Commonly used commands for the EVAR object have defaults to reduce typing.

See Default Object Name

on page 2-7.



Each DS, EVAR, and user is checked for uniqueness. A duplicate causes failure of

the ADD command. ALTER or DELETE commands act on the first match they

detect and generate a warning about the successive duplicates.



The INFO command displays duplicate objects, but does not issue a warning.

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 102 103

Comentários a estes Manuais

Sem comentários

HP NonStop G-Series Guia do Utilizador Página 22

Comentários a estes Manuais

Manuais e produtos relacionados com Software HP NonStop G-Series