HP NonStop SQL/MX Remote Conversational Interface (RMXCI) Guide HP Part Number: 663862-001 Published: October 2011 Edition: HP NonStop SQL/MX Release 3.
© Copyright 2011 Hewlett-Packard Development Company, L.P. Legal Notice Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Contents About this document......................................................................................6 Intended audience....................................................................................................................6 Document organization.............................................................................................................6 New and changed information in this edition...............................................................................
LABEL command.....................................................................................................................71 LOCALHOST command...........................................................................................................71 LOG command......................................................................................................................72 OBEY command............................................................................................................
B Supported SQL statements.......................................................................119 C Error messages......................................................................................121 Index.......................................................................................................
About this document This guide describes how to install and use the HP NonStop SQL/MX Remote Conversational Interface (RMXCI), installed on a client workstation, to manage SQL/MX 3.x database on a NonStop platform. RMXCI enables you to perform daily administrative tasks by running SQL statements interactively or from script files. In this release, RMXCI is supported on Linux platform.
Computer Type Computer type letters within text indicate case-sensitive keywords and reserved words. Type these items exactly as shown. Items not enclosed in brackets are required. For example: myfile.sh [ ] Brackets Brackets enclose optional syntax items. For example: DATETIME [start-field TO] end-field A group of items enclosed in brackets is a list from which you can select one item or none.
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a required character that you must type as shown. For example: "{" module-name [, module-name]... "}" Item Spacing Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: DAY (datetime-expression) DAY(datetime-expression) If there is no space between two items, spaces are not permitted.
• Connectivity manuals SQL/MX Connectivity Service Manual Describes how to install and manage SQL/MX Connectivity Service (MXCS), which enables ODBC and other connectivity APIs to use NonStop SQL/MX. SQL/MX Connectivity Service Administrative Command Reference Describes the SQL/MX Administrative Command Library (MACL) available with the SQL/MX conversational interface (MXCI).
NSM/web Help Context-sensitive help topics that describe how to use the NSM/web management tool. Visual Query Planner Help Context-sensitive help topics that describe how to use the Visual Query Planner graphical user interface. Publishing history Part Number Product Version Publication Date 663862-001 HP NonStop SQL/MX Release Sep 2011 3.1 HP encourages your comments HP encourages your comments concerning this document. We are committed to providing documentation that meets your needs.
1 Introduction to RMXCI HP NonStop SQL/MX Remote Conversational Interface (RMXCI) is a command-line interface, which you can download and install on a client workstation that has a NonStop JDBC Type 4 Driver. The NonStop JDBC Type 4 Driver connects RMXCI on a Linux client workstation to an SQL/MX 3.x database on a NonStop platform. Figure 1 RMXCI connected to the NonStop environment NOTE: RMXCI interacts only with NonStop SQL/MX 3.x databases.
2 Installing RMXCI The hardware and software requirements for RMXCI are described in the softdoc file delivered with the product, either through the product CD or the Scout website for NonStop servers through HP NonStop eServices portal (https://onepoint.nonstop.compaq.com/). Read the softdoc file before installing the product. RMXCI installation requirements include: SQL/MX Release 3.x installed on the NonStop system The following software installed on the client workstation: • JDK 1.
Installing a supported Java version To install one of the supported Java versions on the client workstation, follow the instructions on the Oracle website: http://www.oracle.com/technetwork/java/javase/downloads/index.html After installing the Java version, proceed with “Verifying the Java version” (page 13).
1. Change the directory to the lib directory, which contains the NonStop JDBC Type 4 Driver JAR file. From the client terminal window, run the following command: /home:cd jdbc-installation-directory/lib where: jdbc-installation-directory is the NonStop JDBC Type 4 Driver install directory. 2. To view the version information, enter the following command: java -jar t4sqlmx.jar For example: /usr/home/install/t4jdbc/lib/:java -jar t4sqlmx.
NOTE: The -silent option installs the client without prompting you for options, for example: java -jar rmxciInstaller.jar -silent -jdbcFile /usr/local/rmxci/t4sqlmx.jar -installDir /usr/local The -jdbcFile and -installDir are optional parameters, and the defaults are listed in the following table: Table 1 Installation Defaults OS jdbcFile installDir LINUX /usr/local/rmxci/t4sqlmx.jar /usr/local NOTE: In the following steps, all items in square brackets are default values.
Enter the proxy port: 8080 11. Select the components which you want to download and install: Install Perl JavaServer extensions? [Y]: Perl JavaServer requires 3 files: Java.pm, JavaArray.pm, and JavaServer.jar URL of the folder which contains these files [http://search.cpan.org/src/METZZO/Java-4.7/]: Install Perl XML SAX Module? [Y]: Perl SAX XML Module URL (PerlSAX.pm) [http://search.cpan.org/src/KMACLEOD/libxml-perl-0.08/lib/XML/Parser/PerlSAX.
Table 2 Locations of RMXCI Software Files Directory Files Description rmxci.sh Linux launch file rmxci.pl Perl wrapper script rmxci.py Python wrapper script. (To run the script , see “Perl and Python wrapper scripts” (page 52).) install-directory/rmxci/lib rmxci.jar Product JAR file install-directory/rmxci/lib/perl Session.pm Product file install-directory/rmxci/lib/python Session.py Product file install-directory/rmxci/samples arrayDML.
2. To obtain the version information, enter the following command: java -jar rmxci.jar For example: /home:cd install/rmxci/lib /home/install/rmxci/lib:java -jar rmxci.jar The following is a sample output: T0744_V31_30AUG11_HP_NONSTOP(TM)_RMXCI_2011_04_28 /home/install/rmxci/lib: If the JAR file is inaccessible or the returned version is not supported, see “Installation procedure” (page 14).
Welcome to the NonStop(TM) SQL/MX Remote Conversational Interface (c) Copyright 2006-2011 Hewlett-Packard Development Company, LP. SQL>SET SCHEMA NONSTOP.RMXCI_SAMPLE; --- SQL operation complete. SQL> To display the SQL status messages in SQLPlus look-and-feel, set the -DrmxciLF property value to SQLPlus.
Setting the Look-and-Feel Type You can set the look-and-feel option either from a command-line prompt or in the user profile. • To set the _JAVA_OPTIONS environment variable for each session in a command-line prompt: Run the following command from the client terminal window: export _JAVA_OPTIONS=-DrmxciLF=look-and-feel-type where: look-and-feel-type is one of the “Supported Look-and-Feel Types” (page 18).
Picked up _JAVA_OPTIONS: -DrmxciLF=BTEQ Welcome to the NonStop(TM) SQL/MX Remote Conversational Interface (c) Copyright 2006-2011 Hewlett-Packard Development Company, LP. Host Name/IP Address: nsksys.ind.hp.com:18650 User Name: super.super Password: Data Source Name [TDM_Default_DataSource]: Connected to Data Source: TDM_Default_DataSource SQL> • If you cannot connect to the database, verify whether: 1.
3 Launching RMXCI This chapter describes how to launch RMXCI : • “Launching RMXCI ” (page 22) • “Logging in to the database platform” (page 23) • “Using optional launch parameters” (page 26) • “Launching RMXCI without connecting to the database” (page 31) • “Running RMXCI with -version” (page 31) • “Running RMXCI with -help” (page 31) • “Exiting RMXCI” (page 32) For information about launching RMXCI from Perl or Python, see Chapter 6 (page 51).
4. To launch RMXCI, from the client terminal window, run rmxci.sh: /home:rmxci.sh RMXCI appears, prompting you to enter the host name or IP address of the NonStop database system, user name, password and a data source name. For more information, see “Logging in to the database platform” (page 23). NOTE: To enable all users to launch RMXCI anywhere on the system, create a symbolic link to the rmxci.sh file in the /usr/bin or /usr/local/bin directory: /home:ln -s .
Host Name/IP Address: Enter a host name: host-name[:port-number] • Enter a host name: host-name[:port-number] • If you do not specify a port number, RMXCI uses the default port number18650. Ensure that a service has started on port 18650. Or enter an IP address: IP-address[:port-number] 2. 3. 4. Enter your user name. Enter your password. Enter the name of a data source that is available and started. If you do not enter a data source, by default, RMXCI connects to TDM_Default_DataSource.
Any sessions using redirected or piped input are not prompted for retries. • This example shows an invalid host name. RMXCI then prompts for the host name, followed by the user name and password, as shown: rmxci –h dd Welcome to the NonStop(TM) SQL/MX Remote Conversational Interface (c) Copyright 2006-2011 Hewlett-Packard Development Company, LP. Unknown Host: dd Host Name/IP Address: 172.16.1.1 User Name: super.
Welcome to the NonStop(TM) SQL/MX Remote Conversational Interface (c) Copyright 2006-2011 Hewlett-Packard Development Company, LP. Invalid authorization specification User Name: super.super Password:abc Connected to DataSource: TDM_Default_DataSource SQL> After you finish logging in to the NonStop SQL/MX database, the SQL prompt appears, as shown: Welcome to the NonStop(TM) SQL/MX Remote Conversational Interface (c) Copyright 2006-2011 Hewlett-Packard Development Company, LP. Host Name/IP Address: nsksys.
Launch Parameter Description {-q | -sql} "command" Specifies that an SQL statement or a RMXCI command be run when launching the SQL/MX Remote Conversational Interface. You cannot specify this parameter at the same time as the -s or -script parameter. For more information, see “Running a command when launching RMXCI” (page 28). {-s | -script} script-file-name Specifies that a script file be run when launching RMXCI in interactive mode.
Welcome to the NonStop(TM) SQL/MX Remote Conversational Interface (c) Copyright 2006-2011 Hewlett-Packard Development Company, LP. Connected to DataSource: TDM_Default_DataSource SQL> Running a command when launching RMXCI To run an SQL statement or an RMXCI command when launching the SQL/MX Remote Conversational Interface, use the -q or -sql command line parameter. This parameter enables you to run a single command on the command-line without having to enter commands in RMXCI.
Host Name/IP Address: nsksys.ind.hp.com:18650 User Name: super.super Password: DataSource Name [TDM_Default_DataSource]: --- SQL operation complete. Example of running an RMXCI command with -q or -sql To run multiple script files simultaneously from the command line, use -q or -sql options with the prun command.
rmxci-installation-directory is the location where you have installed the RMXCI software files, for example: /home/usr/rmxci. /home/usr/rmxci/bin:./rmxci.sh -s settings.txt Specify the full path of the script file if it is outside the directory of rmxci.sh.
Welcome to the NonStop(TM) SQL/MX Remote Conversational Interface (c) Copyright 2006-2011 Hewlett-Packard Development Company, LP. Host Name/IP Address: nsksys.ind.hp.com:18650 User Name: super.super Password: DataSource Name [TDM_Default_DataSource]: Connected to DataSource: TDM_Default_DataSource SQL>SET IDLETIMEOUT 0 SQL>SET SQLPROMPT * *SET TIME ON * 14:14:57 *SET TIMING ON 2:14:57 PM *SET SQLTERMINATOR .
Example of running RMXCI with -help From the client terminal window,run these commands: /home:cd rmxci-installation-directory/rmxci/bin where: rmxci-installation-directory is the location where you have installed the RMXCI software files, for example: /home/usr/rmxci. /home/usr/rmxci/bin:./rmxci.
4 Interactively running commands in RMXCI After launching the HP NonStop SQL/MX Remote Conversational Interface, you can run SQL statements and RMXCI commands in the interface.
For more information, see the concatenation operator in the SQL/MX Release 3.x Reference Manual. To terminate an SQL statement that spans multiple lines, use the SQL terminator for the session. A syntax error is returned, if more than one SQL statement is included in the same line. For more information, see “Setting and showing the SQL terminator” (page 36). Case sensitivity In the RMXCI interface, you can enter SQL statements and RMXCI interface commands in uppercase, lowercase, or mixed-case characters.
SQL>session COLSEP " " DATASOURCE TDM_Default_DataSource HISTOPT DEFAULT [No expansion of script files] IDLETIMEOUT 0 min(s) [Never Expires] LIST_COUNT 0 [All Rows] LOG OFF LOOK AND FEEL RMXCI MARKUP RAW PROMPT SQL> CATALOG NONSTOP_SYSTEM_NSK SCHEMA PUBLIC_ACCESS_SCHEMA SERVER nsksys.ind.hp.com:18650 SQLTERMINATOR ; STATISTICS OFF TIME OFF TIMING OFF USER super.super SQL> For more information, see the “ENV command” (page 61) or “SHOW SESSION command” (page 109).
SQL ENTER> For more information, see the “SET PROMPT command” (page 93). SET TIME command The set time on command causes the current time of the client workstation to appear in the prompt: SQL ENTER>set time on 20:32:26 SQL ENTER> The set time off command removes the current time from the prompt: 20:32:26 SQL ENTER>set time off SQL ENTER> For more information, see the “SET TIME command” (page 97). Setting and showing the SQL terminator The SQL terminator symbolizes the end of an SQL statement.
Setting and showing the current schema By default, the schema of the session is PUBLIC_ACCESS_SCHEMA and catalog is NONSTOP_SYSTEM_NSK. The SQL statement set schema, allows you to set the schema for the RMXCI session. For example, the following set schema command changes the default schema to PERSNL for the session: SQL>set schema persnl; --- SQL operation complete. SQL>delete from employee where first_name='TIM' and last_name='WALKER'; --- 1 row(s) deleted.
For more information, see the “SET LIST_COUNT command” (page 87) and the “SHOW LIST_COUNT command” (page 104). Showing information about SQL database objects • “Showing the schemas” (page 38) • “Showing the tables in a schema” (page 38) • “Showing the dependent objects of a table” (page 38) • “Showing the views in a schema” (page 38) Showing the schemas The show schemas command displays the schemas that exist in the current catalog.
SQL>set catalog CAT1; -- SQL operation complete. SQL>set schema invent; --- SQL operation complete. SQL>show schema SCHEMA INVENT SQL>show views VIEW NAMES ---------------------------------------------------------------VIEW207 VIEW207N VIEWCS VIEWCUST For more information, see the “SHOW VIEWS command” (page 114). Displaying run commands To display commands that were recently run in the RMXCI session, run the history command.
Obtaining help To display help text for a command that is supported in RMXCI, run the help command. For example, the following command displays syntax and examples for the fc command: SQL>help fc For more information, see the “HELP command” (page 68). Running SQL statements In RMXCI, you can run SQL statements interactively. For a list of these statements, see Appendix B (page 119).
SQL>/ SALARY ---------175500.00 137000.10 139400.00 138000.40 75000.00 90000.00 118000.00 80000.00 70000.00 90000.00 56000.00 --- 11 row(s) selected. For more information, see the “/ command” (page 57), “RUN command” (page 82), or “REPEAT command” (page 80). Preparing and executing SQL Statements You can prepare or compile an SQL statement by using the prepare statement, and then you can run the prepared SQL statement later by using the execute statement.
To specify a parameter to be supplied later, either for a set param statement or for a using clause for an execute statement, use one of these types of parameters in the SQL statement: • Named parameter, which is represented by ?param-name • Unnamed parameter, which is represented by a question mark (?) character For example, the following prepared SELECT statement specifies unnamed parameters for salary and job code: SQL>prepare findemp from +>select * from persnl.
Resetting the parameters To change the value of a parameter, specify the name of the parameter in the reset param command, and then use the set param command to change the setting. For example, suppose that you want to change the salary parameter to 80000.00: SQL>reset param ?sal SQL>set param ?sal 80000.00 Running the reset param command without specifying a parameter name clears all parameter settings in the session, for example: SQL>reset param SQL>show param *** ERROR[29428] No parameters found.
SQL>execute empcom; FIRST_NAME LAST_NAME DEPTNUM --------------- -------------------- ------ALAN TERRY 3000 DAVID TERRY 2000 PETE WELLINGTON 3100 JOHN CHOU 3500 MANFRED CONRAD 4000 DINAH CLARK 9000 DAVE FISHER 3200 GEORGE FRENCHMAN 4000 KARL HELMSTED 4000 JOHN HUGHES 3200 WALTER LANCASTER 4000 MARLENE BONNY 4000 BILL WINN 2000 MIRIAM KING 2500 GINNY FOSTER 3300 MARIA JOSEF 4000 HERB ALBERT 3300 RICHARD BARTON 1000 XAVIER SEDLEMEYER 3300 DONALD TAYLOR 3100 LARRY CLARK 1000 JIM HERMAN 3000 GEORGE STRICKER 310
SQL>create trigger handlecheckout +> after insert on checkout +> referencing new as newr +> for each row +> update member set dues = dues + 10 +> where memberid = newr.memberid; +> / For the syntax of the create trigger statement, see the SQL/MX Release 3.x Reference Manual. Logging output To log a RMXCI session, use the spool or log command. These commands record into a log file the commands that you enter in the RMXCI interface and the output of those commands.
Logging concurrent RMXCI sessions If you plan to run two or more RMXCI sessions concurrently on the same workstation, use the spool log-file or log log-file command and specify a unique name for each log file. Otherwise, each session writes information to the same log file, making it difficult to determine which information belongs to which session.
For information about error messages that might appear in the log file, see the “Error messages” (page 121).
5 Running scripts in RMXCI In RMXCI, you can perform the following tasks with script files: • “Creating a script file” (page 48) • “Running a script file” (page 49) • “Logging output” (page 50) • “Running scripts in parallel” (page 50) Creating a script file A script file which you run in RMXCI must be an ASCII text file, which contains only the following elements: • “Supported SQL statements in script files” (page 48) • “Permitted RMXCI commands in script files” (page 48) • “Comments” (page 48
in the @ or obey command. For more information, see the“@ command” (page 57) or the “OBEY command” (page 74). Example of a script file This script file creates tables in the inventory schema. Running a script file To run a script file in RMXCI, use the @ or obey command. These commands run one script file at a time in the SQL/MX Remote Conversational Interface. To run a script file when launching RMXCI, see “Running a script file when launching RMXCI” (page 29).
SQL>CREATE SCHEMA INVENT; --- SQL operation complete. SQL>-- CREATE TABLES/VIEWS in SCHEMA INVENT SQL>SET SCHEMA INVENT; --- SQL operation complete. SQL>CREATE TABLE INVENT.
6 Running RMXCI from Perl or Python You can run SQL statements in Perl or Python by invoking the RMXCI Perl or Python wrapper script. To use the wrapper scripts, see: • “Login environment variables” (page 51) • “Perl and Python wrapper scripts” (page 52) • “Launching RMXCI from the Perl or Python command-line” (page 52) These instructions assume that you have installed the RMXCI product. For more information, see Chapter 2 (page 12).
Perl and Python wrapper scripts The wrapper scripts enable you to run SQL statements and script files using a single connection or multiple connections within Perl or Python programs. The Perl wrapper script is rmxci.pl, and the Python wrapper script is rmxci.py. By default, these wrapper scripts are located in the bin directory as shown below: rmxci-installation-directory/rmxci/bin rmxci-installation-directory is where you installed the RMXCI software files. For more information, see Table 2 (page 17).
import os import sys ## Modify this path sys.path.append("/usr/home/rmxci/lib/python") import Session # create a session object sess = Session.Session() # Connect to the database x=sess.__connect__("super.services","password", "nsksys.ind.hp.com", "18650","TDM_Default_DataSource") # Execute sample queries # __execute takes the query string as parameter setSchema selectTable getStats = "set schema RMXCI.
A RMXCI commands The NonStop SQL/MX Remote Conversational Interface supports these commands in RMXCI or in script files. See the README for the HP NonStop SQL/MX Remote Conversational Interface for syntax, considerations, and examples regarding conditional statements. 54 Command Description @ Runs the SQL statements and RMXCI See the “@ command” (page 57). commands contained in a specified script file. This command is disallowed from Perl and Python programs. / Runs the previously run SQL statement.
Command Description Syntax OBEY Runs the SQL statements and RMXCI interface commands contained in a specified script file. See the “OBEY command” (page 74). PRUN Runs script files in parallel. See the “PRUN command” (page 77). QUIT Disconnects from and exits RMXCI. See the “QUIT command” (page 79). RECONNECT Creates a new connection to the NonStop platform using the login credentials of the last successful connection. See the “RECONNECT command” (page 79). REPEAT Reruns a command.
Command Description Syntax SET TIME Causes the local time of the client workstation to be displayed as part of the interface prompt. See the “SET TIME command” (page 97). SET TIMING Causes the elapsed time to be displayed See the“SET TIMING command” after each SQL statement is run. (page 98). SHOW ACTIVITYCOUNT Functions as an alias of “SHOW RECCOUNT command” (page 107). SHOW ALIAS Displays all or a set of aliases available See the “SHOW ALIAS command” in the current RMXCI session. (page 99).
Command Description Syntax SHOW SQLTERMINATOR Displays the SQL statement terminator of the current session. See the “SHOW SQLTERMINATOR command” (page 111). SHOW STATISTICS Displays if statistics has been enabled or disabled for the current session See the “SHOW STATISTICS command” (page 112) SHOW TIME Displays the setting for the local time in See the “SHOW TIME command” the SQL prompt. (page 113). SHOW TIMING Displays the setting for the elapsed time. See the “SHOW TIMING command” (page 113).
--- 1 row(s) selected. SQL>/ (EXPR) -------------------62 --- 1 row(s) selected. ALIAS command The alias command allows you to map a string to any RMXCI or SQL command. The syntax of the RMXCI or SQL command is checked when you run the mapped string. This command replaces only the first token of a command string which allows the rest of the tokens to be treated as parameters. Syntax ALIAS value AS command SQL-terminator value is a case-insensitive string without spaces. Value cannot be an RMXCI command.
GOTO statement executed, ignoring all commands until a 'LABEL MYLABEL' command is encountered. The following command creates an alias named USE to perform the set schema operation, uses the alias to set the schema to MX.USR, and checks the current schema to verify that the alias works correctly: SQL>alias use as "SET SCHEMA"; SQL>use MX.USR; SQL>show schema SCHEMA USR CLEAR command The clear command clears the interface window so that only the prompt appears at the top of the window.
Considerations • You must enter the command in one line. • If RMXCI was invoked with the -noconnect launch parameter, RMXCI prompts you for the values. Examples The following commands create a new connection to the database platform from the current or existing RMXCI session: SQL>connect SQL>User Name:super.super SQL>Password: Connected to DataSource TDM_Default_DataSource. SQL>connect super.super/password Connected to DataSource TDM_Default_DataSource. SQL>connect super.
DISCONNECT command The disconnect command terminates the connection to the database platform. The RMXCI session remains open even after this command is run. Syntax DISCONNECT [WITH][status][IF{condition}] status is any 1-byte integer. The status is a shell return value, and the range of allowable values is platform dependent. condition is the same as the condition parameter defined for the “IF...THEN command” (page 69). See “Condition Parameter” (page 69).
LIST_COUNT Current list count, which is the maximum number of rows that can be returned by SELECT statements. By default, the list count is all rows. For more information, see “SET LIST_COUNT command” (page 87). LOG Current log file and the directory containing the log file. By default, logging during a session is turned off. For more information, see “Logging output” (page 45) and “LOG command” (page 72) or “SPOOL command” (page 115). LOOK AND FEEL Current look-and-feel of RMXCI.
SQLTERMINATOR ; STATISTICS OFF TIME OFF TIMING OFF USER super.super SQL> • The following env command shows the effect of setting various session attributes: SQL>env COLSEP " " DATASOURCE TDM_Default_DataSource HISTOPT DEFAULT [No expansion of script files] IDLETIMEOUT 0 min(s) [Never Expires] LIST_COUNT 0 [All Rows] LOG /usr/home/examples.log LOOK AND FEEL RMXCI MARKUP RAW PROMPT 4:16:49 PM > CATALOG NONSTOP_SYSTEM_NSK SCHEMA PERSNL SERVER nsksys.ind.hp.
Examples • The following command disconnects and exits from RMXCI: SQL>exit • If the previously run command returns the error code 4082, the conditional exit command stops the execution of the script file and then disconnects and exits from RMXCI. SQL>log /usr/home/errorCode.log SQL>select * from employee; SQL>exit if errorcode=4082 SQL>log off The following results are logged on getting error code 4082: SQL>select * from employee; *** ERROR[4082] Table, view or stored procedure SCH.USR.
Considerations • You must enter the command in one line. • You cannot run this command in a script file. You can run this command only at a command prompt. • As each line of the command appears, you can modify the line by entering these editing commands (in uppercase or lowercase letters) in the line below the displayed command-line: D Deletes the character immediately above the letter D. Repeat to delete more characters.
SQL>selt * fromm persnl.employee; *** ERROR[15001] A syntax error occurred at or before: selt * fromm persnl.employee; ^ SQL>fc SQL>selt * fromm persnl.employee; .... iec// d SQL>select * from persnl.employee; .... Pressing Enter runs the corrected SELECT statement. • The following example modifies a previously run statement by replacing a column name in the select list with another column name: SQL>select first_name, last_name +>from persnl.
Description of Returned Values: Records Accessed number of rows returned by disk process to EID (Executor In Disk process). Records Used number of rows returned by EID after selection. Disk IOs number of actual disk IOs performed by disk process. Message Count number of messages sent or received between filesystem and disk process. Message Bytes number of message bytes sent or received between filesystem and disk process. Lock Escl number of lock escalations. Lock Wait number of lock waits.
Syntax GOTO {label} label is a string of characters without quotes and spaces, or a quoted string. Considerations • You must enter the command in one line. • The goto command cannot jump back in the command history; it is a forward only command.
Syntax HISTORY [number] number is the number of commands to display. The default number is 10. The maximum number is 100. Considerations • You must enter the command in one line. • You can use the fc command to edit and rerun a command in the history buffer, or use the repeat command to rerun a command without modifying it. See the “FC command” (page 64) or the “REPEAT command” (page 80).
operator is one of: Operator Meaning == | = equal to <> | != | ~= | ^= not equal to > greater than >= greater than or equal to < less than <= less than or equal to Action Parameter The action parameter (action) is any RMXCI command or SQL/MX statement mentioned in this manual. SQL Terminator The SQL terminator (SQL-terminator) is the default terminator (;) or a string value defined for the statement terminator by the “SET SQLTERMINATOR command” (page 96).
SQL> LABEL insertBob SQL> INSERT INTO Employees(SSN, FName, LName) VALUES(123456789, 'Bob', 'Smith'); SQL> EXIT LABEL command The label command marks a point in the command history that you can jump to by using the goto command. For more information, see the “GOTO command” (page 67). Syntax LABEL {label} label is a string of characters without quotes and spaces, or a quoted string. Considerations You must enter the command in one line.
SQL>set timing on SQL>localhost ls rmxci-perl.pl rmxci-python.py rmxci.cmd rmxci.pl rmxci.py rmxci.sh Elapsed :00:00:00.078 LOG command The log command logs the entered commands and their output from RMXCI to a log file. If this is an obey script file, then the command text from the obey script file is shown on the console. Syntax LOG { ON [CLEAR, QUIET, CMDTEXT {ON | OFF}] | log-file [CLEAR, QUIET, CMDTEXT {ON | OFF}] | OFF } ON starts the logging process and records information in the sqlspool.
SQL>log on • The following command starts the logging process and appends new information to an existing log file, persnl_updates.log, in the local directory: SQL>log persnl_updates.log • The following command starts the logging process and appends new information to a log file, sales_updates.log, in the specified directory on client workstation: SQL>log ./log_files/sales_updates.
Output of /usr/home/b.txt ==================== JOBCODE JOBDESC ------- -----------------100 MANAGER 450 PROGRAMMER 900 SECRETARY 300 SALESREP 500 ACCOUNTANT 400 SYSTEM ANALYST 250 ASSEMBLER 420 ENGINEER 600 ADMINISTRATOR 200 PRODUCTION SUPV --- 10 row(s) selected The following command stops the logging process: SQL>log off For more information, see “Logging output” (page 45). OBEY command The obey command runs the SQL statements and RMXCI commands of a specified script file or an entire directory.
Considerations • You must enter the command in one line. • Put a space between obey and the first character of the filename. • You can run this command in a script file. • Before putting dependent SQL statements across multiple files, consider the order of the file execution. If a directory is not passed to the obey command, the file or wildcard is assumed to be in the current directory. • If the (*) is issued in the obey command, all files are run in the current directory.
purgedata course; To run only the commands in section create, run the command : SQL>obey /usr/home/course.sql (create) SQL>?section create SQL>CREATE TABLE COURSE +>( +> CNO VARCHAR(3) +> CNAME VARCHAR(22) +> CDESCP VARCHAR(25) +> CRED INT, +> CLABFEE NUMERIC(5,2), +> CDEPT VARCHAR(4) +> primary key (cno) +>) ; NOT NULL, NOT NULL, NOT NULL, NOT NULL, --- SQL Operation complete. To run only the commands in the insert section, run the command : SQL>obey /usr/home/course.
The following command prompts the user to enter the script filename or a pattern. The default value is *.sql. SQL>obey; Enter the script filename [*.sql]: PRUN command The prun command runs script files in parallel. Syntax PRUN [-d | -defaults] | PRUN [-sd [-e [-ld [-o [-c | | | | | -scriptsdir directoryName] -extension extension] -logsdir logDirectory] -overwrite {y | n}] -connections num] scriptsdir In this directory, prun processes every file with the specified extension.
Example • Enter the prun command in RMXCI: SQL>prun Enter * as input to stop the current prun session -------------------------------------------------Enter the Enter the Enter the Overwrite Enter the scripts directory : script file extension[sql] : logs directory[scripts dir] : the log files (y/n)[n]? : number of connections(2-248)[2]: /usr/home/rmxci/ddl_scripts /usr/home/rmxci/log y 3 After you enter the number of connections, prun starts to process the script files and displays this status: Status:
PRUN options are -scriptsdir -logsdir -extension -overwrite -connections Status: Complete /usr/home/rmxci/prun /usr/home/rmxci/prun/logs sql yes 5 For a summary of all errors and warnings that occurred during the prun operation, go to the error subdirectory in the same directory as the log files (for example, /usr/home/rmxci/log/error) and open the prun.err.log summary file. For details about the errors that occurred during the execution of a script file, open each individual log file (.
Syntax RECONNECT Considerations The host name or IP address and port number, credentials (user name and password) and the data source name values are used from information previously entered. This is the information specified at launch or when the last connect command was run. If RMXCI was invoked with the -noconnect launch parameter, RMXCI prompts you for the values.
4> 5> 6> 7> 8> select * from employee; show views select * from dept; show views select * from emplist; SQL> SQL>repeat -2 show views VIEW NAMES ------------------------------------------------------------EMPLIST MGRLIST SQL> • The following example reruns the seventh command in the history buffer: SQL>repeat 7 show views VIEW NAMES ------------------------------------------------------------EMPLIST MGRLIST SQL> • The following example reruns the show views command: SQL>repeat show show views VIEW NAM
RESET PARAM command The reset param command clears all parameter values or a specified parameter value in the current session. Syntax RESET PARAM [param-name] param-name is the name of the parameter for which you specified a value. Parameter names are case-sensitive. For example, the parameter ?pn is not equivalent to the parameter ?PN. param-name can be preceded by a question mark (?), such as ?param-name.
-------------------62 --- 1 row(s) selected. SQL> SAVEHIST command The savehist command saves the session history in a user specified file. The session history contains a list of commands that were run in the RMXCI session before the savehist command. Syntax SAVEHIST file-name [CLEAR] file-name is the name of a file into which RMXCI stores the session history.
Considerations • You must enter the command in one line. • The command needs an SQL terminator. • If catalog name is not specified, the command uses the default catalog NONSTOP_SYSTEM_NSK. Examples • The following example illustrates the usage of this command: SQL>create catalog cat11; --- SQL operation complete SQL> fc; SQL>create catalog cat12; --- SQL operation complete SQL>create schema cat1.
Considerations • You must enter the command in one line. • The set colsep command has no effect if the markup is set to HTML, XML, or CSV.
SET HISTOPT command The set histopt command sets the history option and controls how commands are added to the history buffer. By default, commands within a script file are not added to history. If the history option is set to ALL, all the commands in the script file are added to the history buffer. If no options are specified, DEFAULT is used. Syntax SET HISTOPT [ALL|DEFAULT] Considerations You must enter the command in one line.
SQL> history; 1> show histopt 2> obey /usr/home/scripts/nobey/insert2.sql 3> history; 4> set histopt all 5> set schema cat1.sch; 6> INSERT INTO COURSE1 VALUES ('C11','INTRO TO CS','FOR ROOKIES',3, 100, 'CIS'); 7> INSERT INTO COURSE1 VALUES ('C55','COMPUTER ARCH.','VON NEUMANN''S MACH.',3,100,'CIS'); SET IDLETIMEOUT command The set idletimeout command sets the idle timeout value for the current session. The idle timeout value of a session determines when the session expires after a period of inactivity.
Syntax SET LIST_COUNT num-rows num-rows is a positive integer that specifies the maximum number of rows of data to be displayed by SELECT statements that are run after this command. Zero means that all rows of data are returned. Considerations • You must enter the command in one line.
SET MARKUP command The set markup command sets the markup format and controls how results are displayed by RMXCI. Syntax SET MARKUP [RAW|HTML|XML|CSV|COLSEP] The supported options enable results to be displayed in XML,HTML,CSV(Comma Separated Values) and COLSEP formats. The default format is RAW. Considerations • You must enter the command in one line. • If the markup format is CSV or COLSEP, the column header information and status messages are not displayed.
SQL>select c.custnum, c.custname,ordernum,order_date, +>from customer c, orders o where c.custnum=o.custnum;
| Error Id | Error Code | Error Message |
| 1 | 4082 | Object CAT.NVS.CUSTOMER does not exist or is inaccessible. 91111 Bjarne Stroustrup 444444 John Steinbeck 2323423 Irwin Shaw 93333 Martin Fowler 92222 Grady Booch 84758345 75|TIM 11|ROGER 93|DONALD |WALKER |GREEN |TAYLOR |3000|300|320000.00 |9000|100|175500.00 |3100|300|33000.00 SET PARAM command The set param command associates a parameter name with a parameter value in the current session. SQL>set param ?sal 40000.00 • The following command sets a character string value, GREEN, for the ?lastname parameter: SQL>set param ?lastname GREEN • The following commands set values for named parameters used in a subsequent SELECT statement: SQL>set param ?sal 80000.00 SQL>set param ?job 100 SQL>select * from persnl. Examples • The following command sets the prompt to ENTER>: SQL>set prompt Enter> ENTER> • The following command displays the session user name for the prompt: SQL>set prompt %user> usr> • The following command displays the session host name and port number for the prompt: SQL>set prompt %server> nsksys.ind.hp. %SCHEMA displays the session schema as the prompt. %DATASOURCE displays the session data source as the prompt. Considerations • You must enter the command in one line. SET SQLTERMINATOR command The set sqlterminator command sets the SQL statement terminator for the current RMXCI session. The default is a semicolon (;). Syntax SET SQLTERMINATOR string string is a string value for the SQL terminator. The string may contain any characters except spaces. Spaces are disallowed even if you enclose the string in double quotes. Lowercase and uppercase characters are accepted, but the SQL terminator is always shown in uppercase. Examples This command shows the default output format as PERTABLE: SQL>set statistics on SQL>select * from job; JOBCODE JOBDESC ------- -----------------100 MANAGER 1234 450 PROGRAMMER 900 SECRETARY 300 SALESREP 500 ACCOUNTANT 400 SYSTEM ANALYST 250 ASSEMBLER 420 ENGINEER 600 ADMINISTRATOR 200 PRODUCTION SUPV --- 11 row(s) selected. Start Time End Time Elapsed Time Compile Time Execution Time Table Name CAT.TOI.JOB 2007/09/18 21:45:34.082329 2007/09/18 21:45:34.300265 00:00:00.217936 00:00:00. SQL>set time on 12h 2:17:17 PM SQL> • The following command turns off the local time in the SQL prompt: 2:17:17 PM SQL>set time off SQL> SET TIMING command The set timing command displays the elapsed time after each SQL statement is run. This command does not display the elapsed time of RMXCI commands. By default, the elapsed time is off. Syntax SET TIMING [ ON | OFF ] ON specifies the elapsed time be displayed after each SQL statement is run. For a list of these statements, see Appendix B (page 119). SHOW ALIAS command The show alias command displays all or a set of aliases available in the current RMXCI session. If a pattern is specified, all aliases matching the pattern are displayed. By default, all aliases in the current session are displayed. Syntax SHOW ALIAS [alias-name | wild-card-pattern] alias-name is any alias name that is used with the ALIAS command. See “ALIAS command” (page 58). SHOW ALIASES command The show aliases command displays all the aliases available in the current RMXCI session. Syntax SHOW ALIASES Considerations You must enter the command in one line. Examples The following command displays all the aliases in the current RMXCI session: SQL> show aliases .OS AS LH .GOTO AS GOTO USE AS SET SCHEMA SHOW CATALOG command The show catalog command displays the current catalog. Syntax SHOW CATALOG Considerations You must enter the command in one line. quotes. To look for similar values, specify only part of the characters of wild-card-pattern combined with these wild-card characters: % Use a percent sign (%) to indicate zero or more characters of any type. For example, %art% matches SMART, ARTIFICIAL, and PARTICULAR but not smart or Hearts. "%art%" matches smart and Hearts but not SMART, ARTIFICIAL, or PARTICULAR. * Use an asterisk (*) to indicate zero or more characters of any type. Examples • The following command displays the column separator: SQL> show colsep COLSEP " " SQL> set colsep * SQL> show colsep COLSEP "*" SHOW ERRORCODE command The show errorcode command is an alias for the show lasterror command. For more information, see “SHOW LASTERROR command” (page 104). Syntax SHOW HISTOPT Considerations • You must enter the command in one line. • If the set timing command is set to on, the elapsed time information appears. Examples The following commands display the value set for the history option: SQL>show histopt HISTOPT DEFAULT [No expansion of script files] SQL>set histopt all SQL>show histopt HISTOPT ALL SHOW IDLETIMEOUT command The show idletimeout command displays the idle timeout value of the current RMXCI session. IDLETIMEOUT 0 min(s) [Never Expires] Elapsed time:00:00:00:078 For more information, see “Setting and showing the idletimeout value for the session” (page 35). SHOW LASTERROR command The show lasterror command displays the error returned from the execution of the last SQL statement. The command returns zero, if the last SQL statement was successfully run. Syntax SHOW LASTERROR Considerations • You must enter the command in one line. SHOW MARKUP command The show markup command displays the value set for the markup option. Syntax SHOW MARKUP Considerations • You must enter the command in one line. • If the set timing command is set to on, the elapsed time information appears. Examples The following command displays the value set for the markup option: SQL>show markup MARKUP RAW Elapsed time:00:00:00:078 SHOW PARAM command The show param command displays the parameters that are set in the current RMXCI session. SHOW PREPARED command The show prepared command displays the prepared statements in the current RMXCI session. If a pattern is specified, all prepared statements matching the prepared statement name pattern are displayed. By default, all prepared statements in the current session are displayed. Syntax SHOW PREPARED [stmtNamePattern] Considerations • You must enter the command in one line. • If the set timing command is set to on, the elapsed time information appears. within double quotes. To look for similar values, specify only part of the characters of wild-card-pattern combined with these wild-card characters: % Use a percent sign (%) to indicate zero or more characters of any type. For example, %art% matches SMART, ARTIFICIAL, and PARTICULAR but not smart or Hearts. "%art%" matches smart and Hearts but not SMART, ARTIFICIAL, or PARTICULAR. * Use an asterisk (*) to indicate zero or more characters of any type. SQL> select * From employee; SQL>show reccount RECCOUNT 3 SHOW SCHEMA command The show schema command displays the current schema of the RMXCI session. Syntax SHOW SCHEMA Considerations • You must enter the command in one line. • If the set timing command is set to on, the elapsed time information appears. Example The following command shows that the current schema of the session is PERSNL: SQL>show schema SCHEMA PERSNL For more information, see “Setting and showing the current schema” (page 37). • If you specify a wildcard pattern in a show schemas command, RMXCI displays only the schema names that match the wild-card pattern. • If the set timing command is set to on, the elapsed time information appears. IDLETIMEOUT Current idle timeout value, which determines when the session expires after a period of inactivity. By default, the idle timeout is 30 minutes. For more information, see “Setting and showing the idletimeout value for the session” (page 35) and “SET IDLETIMEOUT command” (page 87). LIST_COUNT Current list count, which is the maximum number of rows that can be returned by SELECT statements. By default, the list count is all rows. For more information, see “SET LIST_COUNT command” (page 87). TIMING USER • OFF sch.usr The following command shows the effect of setting various session attributes: SQL>session COLSEP " " DATASOURCE TDM_Default_DataSource HISTOPT ALL IDLETIMEOUT 30 min(s) LIST_COUNT 0 [All Rows] LOG OFF LOOK AND FEEL SQLPlus MARKUP RAW PROMPT SQL > CATALOG CAT1 SCHEMA SCH1 SERVER test.acme.com:18650 SQLTERMINATOR ; STATISTICS OFF TIME OFF TIMING OFF USER sch1.usr SHOW SQLPROMPT command The show sqlprompt command displays the value of the SQL prompt for the current RMXCI session. Example The following command shows that the SQL terminator for the current session is a period (.): SQL>show sqlterminator SQLTERMINATOR . For more information, see “Setting and showing the SQL terminator” (page 36). SHOW STATISTICS command The show statistics command displays whether statistics are enabled or disabled for the current session. Syntax SHOW STATISTICS Considerations • You must enter the command in one line. Considerations • You must enter the command in one line. • If you do not specify a wildcard pattern in a show tables command, RMXCI displays all the tables that exist in the current schema. • If you specify a wildcard pattern in a show tables command, RMXCI displays only the table names that match the wildcard pattern. • If the set timing command is set to on, the elapsed time information appears. Syntax SHOW TIMING Considerations • You must enter the command in one line. • If the set timing command is set to on, the elapsed time information appears. Example • The following command displays the elapsed time information because the set timing command is enabled: SQL>set timing on SQL>show time TIME OFF Elapsed :00:00:00.000 SHOW VIEWS command The show views command displays all or a set of views that exist in the current catalog and schema for the RMXCI session. Examples • The following command shows all the views that exist in the current schema, invent: SQL>show schema SCHEMA INVENT SQL>show views VIEW NAMES ------------------------------------------------------------VIEW207 VIEW207N VIEWCS VIEWCUST SQL> • The following command shows the views in the current schema, invent, in which their names begin with, VIEW: SQL>show views view% VIEW NAMES ------------------------------------------------------------VIEW207 VIEW207N VIEWCS VIEWCUST SQL> For more informatio OFF stops the logging process. Considerations • You must enter the command in one line. • Use a unique name for each log file to avoid writing information from different RMXCI sessions into the same log file. Examples • The following command starts the logging process and records information in the sqlspool.lst file in the RMXCI install directory: SQL>spool on • The following command starts the logging process and appends new information to an existing log file, persnl_updates. 200 PRODUCTION SUPV --- 10 row(s) selected. SQL> log off Output of /usr/home/tmp/a.txt ==================== JOBCODE JOBDESC ------- -----------------100 MANAGER 450 PROGRAMMER 900 SECRETARY 300 SALESREP 500 ACCOUNTANT 400 SYSTEM ANALYST 250 ASSEMBLER 420 ENGINEER 600 ADMINISTRATOR 200 PRODUCTION SUPV --- 10 row(s) selected • The following command starts the logging process, clears existing information from the log file, and instructs that no output appear on the console window: SQL>log /usr/home/tmp/b. Considerations You must enter the command in one line. Example • The following command shows versions of the database platform, NonStop JDBC Type 4 Driver and RMXCI: SQL>version NonStop SQLMX Version: 3. B Supported SQL statements RMXCI supports these SQL statements, SQL utilities, and other SQL-related commands. For more information about these statements, see the SQL/MX Release 3.x Reference Manual. SQL Statement Description ALTER INDEX Modifies an SQL/MX index by changing one or more file attributes of the index. ALTER SQLMP ALIAS Changes the physical name of an SQL/MP table to which an existing alias is mapped. ALTER TABLE Adds a column to a table or renames a table. SQL Statement Description POPULATE INDEX Loads a specified index with data from a specified table. PREPARE Compiles an SQL statement for later use with the EXECUTE statement. PURGEDATA Deletes all data from a table and its related indexes. REVOKE Revokes access privileges for a table or view from specified users. REVOKE EXECUTE Revokes privileges for executing a stored procedure from specified roles. C Error messages RMXCI commands can return the following error messages. By default, the error messages are displayed in the RMXCI window. They are logged to a log file, if log command is used to log the output. 29400 Could not initialize the console reader. Cause: An Input Output Exception was received while initializing the Input Stream. Effect: RMXCI does not launch. Recovery: Retry launching RMXCI. Recovery: Verify that there is a valid NonStop JDBC Type 4 Driver in the location specified during RMXCI installation or reinstall RMXCI by selecting a valid driver. 29407 Failed to connect to the database. Connection limit exceeded. Cause: Database connection limit was exceeded. Effect: RMXCI fails to connect to the database and start a new session. Recovery: Re-configure the client data sources to increase the connection limit and retry the command. 29408 SET command must have an option specified. 29419 No views found. Cause: There were no views present in the current catalog and schema or there were no views that matched the specified pattern. Effect: The show views command does not return any entries. Recovery: Verify that you are in the correct catalog and schema by issuing an env or a show catalog and show schema commands. Set the correct catalog and schema. 29423 No procedures found. Effect: The statement fails to run. Recovery: To view the list of the prepared statements in the current session, run the show prepared command. 29432 Invalid number of parameters for prepared statement stmt name . Where stmt name is the statement name used in the prepare statement. Cause: An incorrect number of parameters were specified for executing a prepared statement. Effect: The statement fails to run. Recovery: Specify the correct number of parameters and retry the command. Recovery: Not applicable. 29439 The query buffer is empty. Cause: An attempt was made to repeat a previously run SQL statement using /,repeat or run commands, when there were no SQL statements in history buffer. Effect: None. Recovery: Not applicable. 29440 Directory not found or does not have READ/WRITE permissions. Cause: An invalid directory was specified for script files or log file in prun command. Effect: : The command fails to run. 29446 Number of connections entered is not within the allowable range. Cause: The number of connections specified for prun command was not within the range supported by the data source. Effect: The command fails to run. Recovery: Specify a valid value for the number of connections and retry the command. 29447 Incorrect value specified for overwrite option. Cause: An incorrect value was specified for -o or -overwrite option in prun command. Effect: The command fails to run. Cause: An invalid directory was specified for script files in prun command. Effect: The command fails to run. Recovery: Specify a valid directory and retry the command. 29459 Scripts Directory not found or does not have READ/WRITE permissions. Cause: An invalid directory was specified for the script files in prun command. Effect: The command fails to run. Recovery: Specify a valid directory and retry the command. Cause: An obey file with an infinite loop was run. This loop was caused by a nested obey either directly by obeying itself or indirectly (for example, by obeying another file, which in turn obeys the original). Effect: The obey command is halted. No other obey files are run and control returns to the session prompt. Recovery: Reduce the depth of nested obey and then run the script. Ensure that there are no loops in your nested obey calls. For example: Consider files A.sql, B.sql, and C.sql. You obey A. 29475 Invalid delay time specified. The value must be in the range 0-3600 seconds. Cause: An out of range value was specified for time in delay command. Effect: The command fails to run. Recovery: Specify a valid value for time and retry the command. 29478 Skipping command until a matching 'LABEL ' command is encountered. Cause: A goto command was run and all commands will be skipped until the matching label is found. Effect: This warning appears for all skipped commands. Recovery: Not applicable. 29484 Invalid fetch size value. The value must be in the range 0-2147483647. Cause: An invalid value was specified for the size in set fetchsize command. Effect: The command fails to run. Recovery: Specify a valid fetch size and retry the command. 29488 Invalid parameter value. Cause: An invalid parameter value was specified in set param command. Effect: The command fails to run. Recovery: Specify a valid parameter value and retry the command. Index Symbols D -DrmxciLF property, 18 -dsn parameter, 26 -h parameter, 26 -help, 27 -host parameter, 26 -noconnect parameter, 27 -p parameter, 26 -password parameter, 26 -q parameter description of, 27 examples of, 28, 29 -s parameter description of, 27 -script parameter, 27 -sql parameter, 27 -u parameter, 26 -user parameter, 26 -version, 27 / command example of, 40 syntax of, 57 @ command example of, 49 syntax of , 57 _JAVA_OPTIONS environment variable setting at a command-line prompt, 20 setting in th J JDBC driver installation, 13 verifying the version, 13 JDBC Type 4 driver see JDBC driver L LABEL command, 71 Launch files, location of, 16 Launch parameters descriptions of, 26 presetting on Linux or UNIX, 23 lib directory, 16 Linux launch file, location of, 16 LOCALHOST command, 71 LOG command, 72 Log files, 46 PRUN operation, 77 Logging in default method, 23 using login parameters, 27 Logging output concurrent sessions, 46 script file execution, 50 starting, 45 stopping, 46 viewing a log file, 46 Logi running multiple files in parallel, 50 running one file at a time, 49 running when launching SQL/MX Remote Conversational Interface, 29 SELECT statement description of, 120 example of, 40 Session, 35 SESSION command, 109 SET COLSEP command, 83, 84 SET commands, in a script file, 29 SET FETCHSIZE command, 85 SET HISTOPT command, 86 SET IDLETIMEOUT command syntax of, 87 SET LIST_COUNT command, 87 SET MARKUP command, 89 SET PARAM command examples of, 42, 43 syntax of, 92 SET PROMPT command example of, 35 synta DROP TRIGGER statement, 119 DROP VIEW statement, 119 EXECUTE statement, 119 EXPLAIN statement, 119 GRANT EXECUTE statement, 119 GRANT statement, 119 INSERT statement, 119 LOCK TABLE statement, 119 POPULATE INDEX utility, 120 PREPARE statement, 120 PURGEDATA utility, 120 REVOKE EXECUTE statement, 120 REVOKE statement, 120 ROLLBACK WORK statement, 120 SELECT ROW COUNT statement, 120 SELECT statement, 120 SET CATALOG statement, 120 SET MPLOC statement, 120 SET NAMETYPE statement, 120 SET SCHEMA, 120 SET TABLE |
