HP Hewlett Packard Computer Accessories 544530 001 User Manual
HP Neoview Script Guide  
HP Part Number: 544530-001  
Published: May 2007  
Edition: HP Neoview Release 2.1  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Table of Contents  
About This Document.......................................................................................................15  
Intended Audience................................................................................................................................15  
New and Changed Information in This Edition...................................................................................15  
Document Organization.......................................................................................................................15  
Notation Conventions...........................................................................................................................16  
General Syntax Notation.................................................................................................................16  
Related Documentation........................................................................................................................17  
Neoview Customer Library.............................................................................................................18  
Neoview Support Library................................................................................................................18  
Publishing History................................................................................................................................19  
HP Encourages Your Comments..........................................................................................................19  
1 Introduction to Neoview Script...................................................................................21  
2 Installing Neoview Script.............................................................................................23  
Preinstallation Procedures....................................................................................................................23  
Installing and Verifying the Java Runtime Environment (JRE)......................................................23  
Installing a Supported Java Version...........................................................................................23  
Verifying the Java Version..........................................................................................................24  
Setting the PATH to a Supported Java Version on Windows....................................................24  
Setting the PATH to a Supported Java Version on Linux or UNIX............................................26  
Installing and Verifying the Neoview JDBC Type 4 Driver............................................................26  
Installing the JDBC Driver.........................................................................................................26  
Verifying the JDBC Driver..........................................................................................................26  
Installing Perl or Python..................................................................................................................27  
Installation Procedures.........................................................................................................................27  
Downloading the Installer...............................................................................................................27  
Verifying the Version of the Installer File........................................................................................28  
Running the Installer.......................................................................................................................28  
Installer Wizard Steps................................................................................................................28  
Launching the Installer Wizard............................................................................................28  
Using the Installer Wizard....................................................................................................29  
Command-Line Installation Steps..............................................................................................33  
Postinstallation Procedures...................................................................................................................34  
Verifying the Installed Software Files..............................................................................................34  
Verifying the Installed Version of Neoview Script..........................................................................35  
Setting the Look and Feel of the Neoview Script Interface.............................................................35  
Supported Look-and-Feel Types................................................................................................36  
Setting the Look and Feel at a Command-Line Prompt............................................................37  
Setting the Look and Feel in the System Properties on Windows.............................................37  
Setting the Look and Feel in the User Profile on Linux or UNIX..............................................39  
Testing the Launch of Neoview Script............................................................................................39  
3 Launching the Neoview Script Interface....................................................................41  
Launching the Neoview Script Interface on Windows.........................................................................41  
Creating a Shortcut to hpnvs.cmd...................................................................................................41  
Launching the Neoview Script Interface on Linux or UNIX................................................................44  
Setting the PATH of hpnvs.sh..........................................................................................................44  
Table of Contents  
3
Download from Www.Somanuals.com. All Manuals Search And Download.  
Presetting the Optional Launch Parameters....................................................................................45  
Logging In to the Database Platform....................................................................................................45  
Default Login...................................................................................................................................45  
Login Parameters.............................................................................................................................46  
Using Optional Launch Parameters................................................................................................46  
Logging In When Launching Neoview Script...........................................................................47  
Running a Command When Launching Neoview Script..........................................................47  
Example of Running an SQL Statement With -q or -sql.......................................................48  
Example of Running a Neoview Script Interface Command With -q or -sql.......................48  
Running a Script File When Launching Neoview Script...........................................................48  
Example of a Script File........................................................................................................49  
Example of Running a Script File With -s or -script.............................................................49  
Launching Neoview Script Without Connecting to the Database.............................................49  
Example of Launching Neoview Script File With -noconnect..............................................50  
Exiting the Neoview Script Interface....................................................................................................50  
4 Running Commands Interactively in the Neoview Script Interface.........................51  
Neoview Script Interface......................................................................................................................51  
Product Banner................................................................................................................................51  
Interface Prompts............................................................................................................................51  
Breaking the Command Line...........................................................................................................51  
Case Sensitivity................................................................................................................................52  
Using Neoview Script Interface Commands........................................................................................52  
Showing the Session Attributes.......................................................................................................52  
Setting and Showing the Idle Timeout Value for the Session.........................................................53  
Customizing the Standard Prompt..................................................................................................53  
SET PROMPT Command...........................................................................................................53  
SET TIME Command.................................................................................................................53  
Setting and Showing the SQL Terminator.......................................................................................54  
Displaying the Elapsed Time...........................................................................................................54  
Setting and Showing the Current Schema.......................................................................................55  
Limiting the Result Set of a Query..................................................................................................55  
Showing Information About SQL Database Objects.......................................................................55  
Showing the Schemas.................................................................................................................56  
Showing the Tables in a Schema................................................................................................56  
Showing the Dependent Objects of a Table................................................................................56  
Showing the Views in a Schema.................................................................................................57  
Showing the Synonyms in a Schema.........................................................................................57  
Displaying Executed Commands....................................................................................................58  
Editing and Reexecuting a Command.............................................................................................58  
Clearing the Interface Window.......................................................................................................58  
Obtaining Help................................................................................................................................58  
Running SQL Statements......................................................................................................................59  
Executing an SQL Statement...........................................................................................................59  
Repeating an SQL Statement...........................................................................................................59  
Preparing and Executing SQL Statements......................................................................................60  
Preparing an SQL Statement......................................................................................................60  
Setting Parameters......................................................................................................................61  
Displaying the Parameters of the Session..................................................................................61  
Resetting the Parameters............................................................................................................61  
Executing a Prepared SQL Statement........................................................................................62  
Logging Output....................................................................................................................................63  
Starting the Logging Process...........................................................................................................63  
SPOOL ON or LOG ON Command...........................................................................................63  
4
Table of Contents  
Download from Www.Somanuals.com. All Manuals Search And Download.  
SPOOL log-file or LOG log-file Command................................................................................64  
Using the CLEAR Option...........................................................................................................64  
Logging Concurrent Neoview Script Sessions...........................................................................64  
Stopping the Logging Process.........................................................................................................64  
Viewing the Contents of a Log File.................................................................................................64  
5 Running Scripts in the Neoview Script Interface.......................................................67  
Creating a Script File.............................................................................................................................67  
Supported SQL Statements in Script Files.......................................................................................67  
Permitted Neoview Script Interface Commands in Script Files......................................................67  
Disallowed Interface Commands in Script Files........................................................................67  
Comments........................................................................................................................................67  
Section Headers...............................................................................................................................67  
Example of a Script File...................................................................................................................68  
Running a Script File.............................................................................................................................68  
Logging Output....................................................................................................................................69  
Running Scripts in Parallel...................................................................................................................69  
6 Running Neoview Script From Perl or Python............................................................71  
Setting the Login Environment Variables.............................................................................................71  
Setting the Login Environment Variables on Windows..................................................................71  
Setting Login Environment Variables on the Command Line...................................................71  
Setting Login Environment Variables in the System Properties................................................72  
Setting the Login Environment Variables on Linux or UNIX.........................................................73  
Setting Login Environment Variables on the Command Line...................................................73  
Setting Login Environment Variables in the User Profile..........................................................74  
Perl and Python Wrapper Scripts.........................................................................................................74  
Launching Neoview Script From the Perl or Python Command Line.................................................74  
Perl and Python Commands on Windows......................................................................................75  
Perl and Python Commands on Linux or UNIX.............................................................................75  
Launching Neoview Script From a Perl or Python Program...............................................................76  
Setting the Login Environment Variables........................................................................................76  
Using SQL Statements in a Perl or Python Program.......................................................................76  
Example of a Perl Program (example.pl)...................................................................................76  
Example of a Python Program (example.py).............................................................................77  
Running the Perl or Python Program..............................................................................................77  
A Neoview Script Interface Commands........................................................................79  
@ Command..........................................................................................................................................81  
Syntax..............................................................................................................................................81  
Considerations.................................................................................................................................82  
Examples..........................................................................................................................................82  
/ Command...........................................................................................................................................82  
Syntax..............................................................................................................................................82  
Considerations.................................................................................................................................82  
Example...........................................................................................................................................82  
CLEAR Command................................................................................................................................83  
Syntax..............................................................................................................................................83  
Considerations.................................................................................................................................83  
Example...........................................................................................................................................83  
CONNECT Command..........................................................................................................................83  
Syntax..............................................................................................................................................83  
Considerations.................................................................................................................................83  
Table of Contents  
5
Download from Www.Somanuals.com. All Manuals Search And Download.  
Examples..........................................................................................................................................84  
DISCONNECT Command....................................................................................................................84  
Syntax..............................................................................................................................................84  
Considerations.................................................................................................................................84  
Examples..........................................................................................................................................84  
ENV Command.....................................................................................................................................85  
Syntax..............................................................................................................................................85  
Considerations.................................................................................................................................85  
Examples..........................................................................................................................................86  
EXIT Command....................................................................................................................................86  
Syntax..............................................................................................................................................86  
Considerations.................................................................................................................................87  
Examples..........................................................................................................................................87  
FC Command........................................................................................................................................87  
Syntax..............................................................................................................................................87  
Considerations.................................................................................................................................88  
Examples..........................................................................................................................................88  
HELP Command...................................................................................................................................90  
Syntax..............................................................................................................................................90  
Considerations.................................................................................................................................90  
Examples..........................................................................................................................................90  
HISTORY Command............................................................................................................................90  
Syntax..............................................................................................................................................91  
Considerations.................................................................................................................................91  
Example...........................................................................................................................................91  
LOG Command.....................................................................................................................................91  
Syntax..............................................................................................................................................91  
Considerations.................................................................................................................................92  
Examples..........................................................................................................................................92  
MODE Command.................................................................................................................................92  
Syntax..............................................................................................................................................92  
Considerations.................................................................................................................................93  
Examples..........................................................................................................................................93  
OBEY Command...................................................................................................................................93  
Syntax..............................................................................................................................................93  
Considerations.................................................................................................................................94  
Examples..........................................................................................................................................94  
PRUN Command..................................................................................................................................95  
Syntax..............................................................................................................................................95  
Considerations.................................................................................................................................96  
Example...........................................................................................................................................96  
QUIT Command...................................................................................................................................97  
Syntax..............................................................................................................................................97  
Considerations.................................................................................................................................97  
Examples..........................................................................................................................................97  
RECONNECT Command.....................................................................................................................98  
Syntax..............................................................................................................................................98  
Considerations.................................................................................................................................98  
Examples..........................................................................................................................................98  
REPEAT Command...............................................................................................................................98  
Syntax..............................................................................................................................................98  
Considerations.................................................................................................................................99  
Examples..........................................................................................................................................99  
RESET PARAM Command...................................................................................................................99  
Syntax.............................................................................................................................................100  
6
Table of Contents  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Considerations...............................................................................................................................100  
Example.........................................................................................................................................100  
RUN Command..................................................................................................................................100  
Syntax.............................................................................................................................................100  
Considerations...............................................................................................................................100  
Example.........................................................................................................................................100  
SAVEHIST Command.........................................................................................................................101  
Syntax.............................................................................................................................................101  
Considerations...............................................................................................................................101  
Examples........................................................................................................................................101  
SET COLSEP Command.....................................................................................................................101  
Syntax.............................................................................................................................................102  
Considerations...............................................................................................................................102  
Examples........................................................................................................................................102  
SET HISTOPT Command....................................................................................................................102  
Syntax.............................................................................................................................................102  
Considerations...............................................................................................................................102  
Examples........................................................................................................................................102  
SET IDLETIMEOUT Command..........................................................................................................103  
Syntax.............................................................................................................................................103  
Considerations...............................................................................................................................104  
Examples........................................................................................................................................104  
SET MARKUP Command...................................................................................................................104  
Syntax.............................................................................................................................................104  
Considerations...............................................................................................................................104  
Examples........................................................................................................................................104  
SET LIST_COUNT Command............................................................................................................106  
Syntax.............................................................................................................................................106  
Considerations...............................................................................................................................106  
Examples........................................................................................................................................107  
SET PARAM Command......................................................................................................................107  
Syntax.............................................................................................................................................108  
Considerations...............................................................................................................................108  
Examples........................................................................................................................................108  
SET PROMPT Command....................................................................................................................109  
Syntax.............................................................................................................................................109  
Considerations...............................................................................................................................109  
Examples........................................................................................................................................109  
SET SQLPROMPT Command.............................................................................................................110  
Syntax.............................................................................................................................................110  
Considerations...............................................................................................................................111  
Examples........................................................................................................................................111  
SET SQLTERMINATOR Command....................................................................................................112  
Syntax.............................................................................................................................................112  
Considerations...............................................................................................................................112  
Examples........................................................................................................................................112  
SET TIME Command..........................................................................................................................112  
Syntax.............................................................................................................................................112  
Considerations...............................................................................................................................112  
Examples........................................................................................................................................113  
SET TIMING Command.....................................................................................................................113  
Syntax.............................................................................................................................................113  
Considerations...............................................................................................................................113  
Examples........................................................................................................................................113  
SHOW COLSEP Command................................................................................................................113  
Table of Contents  
7
Download from Www.Somanuals.com. All Manuals Search And Download.  
Syntax.............................................................................................................................................114  
Considerations...............................................................................................................................114  
Examples........................................................................................................................................114  
SHOW HISTOPT Command..............................................................................................................114  
Syntax.............................................................................................................................................114  
Considerations...............................................................................................................................114  
Examples........................................................................................................................................114  
SHOW IDLETIMEOUT Command.....................................................................................................114  
Syntax.............................................................................................................................................114  
Considerations...............................................................................................................................114  
Examples........................................................................................................................................115  
SHOW LIST_COUNT Command.......................................................................................................115  
Syntax.............................................................................................................................................115  
Considerations...............................................................................................................................115  
Examples........................................................................................................................................115  
SHOW MARKUP Command..............................................................................................................115  
Syntax.............................................................................................................................................115  
Considerations...............................................................................................................................115  
Examples........................................................................................................................................116  
SHOW MODE Command...................................................................................................................116  
Syntax.............................................................................................................................................116  
Considerations...............................................................................................................................116  
Example.........................................................................................................................................116  
SHOW MVGROUPS Command.........................................................................................................116  
Syntax.............................................................................................................................................116  
Considerations...............................................................................................................................117  
Examples........................................................................................................................................117  
SHOW MVS Command......................................................................................................................117  
Syntax.............................................................................................................................................117  
Considerations...............................................................................................................................118  
Examples........................................................................................................................................118  
SHOW PARAM Command.................................................................................................................118  
Syntax.............................................................................................................................................119  
Considerations...............................................................................................................................119  
Example.........................................................................................................................................119  
SHOW PREPARED Command...........................................................................................................119  
Syntax.............................................................................................................................................119  
Considerations...............................................................................................................................119  
Examples........................................................................................................................................120  
SHOW SCHEMA Command..............................................................................................................120  
Syntax.............................................................................................................................................120  
Considerations...............................................................................................................................120  
Example.........................................................................................................................................120  
SHOW SCHEMAS Command............................................................................................................120  
Syntax.............................................................................................................................................120  
Considerations...............................................................................................................................121  
Examples........................................................................................................................................121  
SHOW SESSION Command...............................................................................................................122  
Syntax.............................................................................................................................................122  
Considerations...............................................................................................................................122  
Examples........................................................................................................................................123  
SHOW SQLPROMPT Command........................................................................................................123  
Syntax.............................................................................................................................................123  
Considerations...............................................................................................................................124  
Example.........................................................................................................................................124  
8
Table of Contents  
Download from Www.Somanuals.com. All Manuals Search And Download.  
SHOW SQLTERMINATOR Command...............................................................................................124  
Syntax.............................................................................................................................................124  
Considerations...............................................................................................................................124  
Example.........................................................................................................................................124  
SHOW SYNONYMS Command.........................................................................................................124  
Syntax.............................................................................................................................................124  
Considerations...............................................................................................................................125  
Examples........................................................................................................................................125  
SHOW TABLE Command...................................................................................................................125  
Syntax.............................................................................................................................................126  
Considerations...............................................................................................................................126  
Examples........................................................................................................................................126  
SHOW TABLES Command.................................................................................................................127  
Syntax.............................................................................................................................................127  
Considerations...............................................................................................................................128  
Examples........................................................................................................................................128  
SHOW TIME Command.....................................................................................................................128  
Syntax.............................................................................................................................................129  
Considerations...............................................................................................................................129  
Example.........................................................................................................................................129  
SHOW TIMING Command................................................................................................................129  
Syntax.............................................................................................................................................129  
Considerations...............................................................................................................................129  
Example.........................................................................................................................................129  
SHOW VIEWS Command...................................................................................................................129  
Syntax.............................................................................................................................................129  
Considerations...............................................................................................................................130  
Examples........................................................................................................................................130  
SPOOL Command...............................................................................................................................130  
Syntax.............................................................................................................................................130  
Considerations...............................................................................................................................131  
Examples........................................................................................................................................131  
VERSION Command..........................................................................................................................131  
Syntax.............................................................................................................................................131  
Considerations...............................................................................................................................132  
Example.........................................................................................................................................132  
B Supported SQL Statements.......................................................................................133  
C Connectivity Service Commands.............................................................................135  
INFO DS Command............................................................................................................................135  
Syntax.............................................................................................................................................135  
Considerations...............................................................................................................................135  
Example.........................................................................................................................................135  
Index...............................................................................................................................137  
Table of Contents  
9
Download from Www.Somanuals.com. All Manuals Search And Download.  
10  
Download from Www.Somanuals.com. All Manuals Search And Download.  
List of Figures  
1-1  
Neoview Script Within a Neoview Platform Network.................................................................21  
11  
Download from Www.Somanuals.com. All Manuals Search And Download.  
12  
Download from Www.Somanuals.com. All Manuals Search And Download.  
List of Tables  
2-1  
Locations of Neoview Script Software Files..................................................................................34  
13  
Download from Www.Somanuals.com. All Manuals Search And Download.  
14  
Download from Www.Somanuals.com. All Manuals Search And Download.  
About This Document  
This manual describes how to use the Neoview Script command-line interface on a client  
workstation to manage a database on a Neoview data warehousing platform. Neoview Script  
enables you to perform daily administrative tasks by running SQL statements interactively or  
from script files.  
Intended Audience  
This manual is intended for database administrators and support personnel who are maintaining  
and monitoring a Neoview database.  
New and Changed Information in This Edition  
Chapter or Appendix  
New or Changed Information  
“Setting the Look and Feel of the There is a new look and feel property value, BTEQ(to support Teradata). This  
Neoview Script Interface” (page 35) property affects the formatting of status messages. The look and feel property  
value Oracleis no longer available, but is supported for backward compatibility.  
For more information, see “Setting the Look and Feel of the Neoview Script  
Interface” (page 35).  
“Launching the Neoview Script  
Interface” (page 41)  
There is a new optional launch parameter -noconnect. For more information,  
see“Launching Neoview Script Without Connecting to the Database” (page 49).  
Appendix A: Neoview Script  
Interface Commands  
This appendix describes these new interface commands:  
• CONNECT  
• RECONNECT  
• SET MARKUP  
• SET COLSEP  
• SET HISTOPT  
• SHOW COLSEP  
• SHOW HISTOPT  
• SHOW MARKUP  
• SHOW PREPARED  
This appendix also includes changes these existing interface commands:  
• DISCONNECT  
• ENV  
• PRUN  
• SESSION  
• SET TIME  
• SHOW TABLE  
• SHOW SESSION  
Document Organization  
Chapter 1: Introduction to  
Neoview Script  
Introduces Neoview Script and describes its capabilities.  
Chapter 2: Installing Neoview  
Script  
Describes how to install Neoview Script on the client workstation.  
Chapter 3: Launching the Neoview Describes how to launch, log in to, and exit the Neoview Script interface on a  
Script Interface client workstation.  
Chapter 4: Running Commands Describes how to run commands interactively in the Neoview Script interface.  
Interactively in the Neoview Script  
Interface  
Chapter 5: Running Scripts in the Describes how to run script files in the Neoview Script interface.  
Neoview Script Interface  
Intended Audience  
15  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Chapter 6: Running Neoview  
Script From Perl or Python  
Describes how to run Neoview Script from Perl or Python.  
Appendix A: Neoview Script  
Interface Commands  
Provides syntax, considerations, and examples for Neoview Script interface  
commands.  
Appendix B: Supported SQL  
Statements  
Lists the SQL statements that Neoview Script supports.  
Appendix C: Connectivity Service Provides syntax, considerations, and examples for connectivity service commands.  
Commands  
Notation Conventions  
General Syntax Notation  
This list summarizes the notation conventions for syntax presentation in this manual.  
UPPERCASE LETTERS  
Uppercase letters indicate keywords and reserved words. Type these  
items exactly as shown. Items not enclosed in brackets are required.  
For example:  
SELECT  
Italic Letters  
Italic letters, regardless of font, indicate variable items that you  
supply. Items not enclosed in brackets are required. For example:  
file-name  
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  
choose one item or none. The items in the list can be arranged either  
vertically, with aligned brackets on each side of the list, or  
horizontally, enclosed in a pair of brackets and separated by vertical  
lines. For example:  
DROP SCHEMA schema [CASCADE]  
[RESTRICT]  
DROP SCHEMA schema [ CASCADE | RESTRICT ]  
{ } Braces  
Braces enclose required syntax items. For example:  
FROM { grantee[, grantee]...}  
A group of items enclosed in braces is a list from which you are  
required to choose one item. The items in the list can be arranged  
either vertically, with aligned braces on each side of the list, or  
horizontally, enclosed in a pair of braces and separated by vertical  
lines. For example:  
INTERVAL { start-field TO end-field }  
{ single-field }  
INTERVAL { start-field TO end-field | single-field }  
16  
About This Document  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
| Vertical Line  
… Ellipsis  
A vertical line separates alternatives in a horizontal list that is enclosed  
in brackets or braces. For example:  
{expression | NULL}  
An ellipsis immediately following a pair of brackets or braces indicates  
that you can repeat the enclosed sequence of syntax items any number  
of times. For example:  
ATTRIBUTE[S] attribute [, attribute]...  
{, sql-expression}...  
An ellipsis immediately following a single syntax item indicates that  
you can repeat that syntax item any number of times. For example:  
expression-n…  
Punctuation  
Parentheses, commas, semicolons, and other symbols not previously  
described must be typed as shown. For example:  
DAY (datetime-expression)  
@script-file  
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. In  
this example, no spaces are permitted between the period and any  
other items:  
myfile.sh  
Line Spacing  
If the syntax of a command is too long to fit on a single line, each  
continuation line is indented three spaces and is separated from the  
preceding line by a blank line. This spacing distinguishes items in a  
continuation line from items in a vertical list of selections. For  
example:  
match-value [NOT] LIKE pattern  
[ESCAPE esc-char-expression]  
Related Documentation  
The HP Neoview Library consists of:  
•
•
“Neoview Customer Library”  
“Neoview Support Library” (page 18)  
Related Documentation  
17  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Neoview Customer Library  
This manual is part of the Neoview customer library:  
•
Administration  
Neoview Database Administrator’s Guide  
Information about how to load and manage the Neoview database  
by using the Neoview DB Admin and other tools.  
Neoview DB Admin Online Help  
Context-sensitive help topics that describe how to use the HP  
Neoview DB Admin management interface.  
Neoview Management Dashboard Client  
Guide for Database Administrators  
Information on using the Dashboard Client, including how to install  
the Client, start and configure the Client Server Gateway (CSG), use  
the Client windows and property sheets, interpret entity screen  
information, and use Command and Control to manage queries from  
the Client.  
Neoview Owner’s Manual  
Neoview Script Guide  
Site-planning information and basic hardware information.  
Information about using the HP Neoview Script command-line  
interface to run SQL statements interactively or from script files.  
Neoview Script Online Help  
Command-line help that describes the interface commands supported  
in the current operating mode of Neoview Script.  
•
•
Reference  
Neoview SQL Reference Manual  
Reference information about the syntax of SQL statements,  
functions, and other SQL language elements supported by the  
Neoview database software.  
Neoview Messages Manual  
Cause, effect, and recovery information for error messages.  
README for Neoview Platform for  
Release 2.1  
Information about known problems that are visible to customers.  
Connectivity  
Neoview JDBC Type 4 Driver API Reference Reference information about the HP Neoview JDBC Type 4 Driver  
API.  
Neoview JDBC Type 4 Driver Programmer’s Information about using the HP Neoview JDBC Type 4 driver,  
Reference  
which provides Java applications on client workstations access a  
Neoview database.  
Neoview ODBC Drivers Manual  
ODBC Client Administrator Online Help  
README files  
Information about using HP Neoview ODBC drivers on a client  
workstation to access a Neoview database.  
Context-sensitive help topics that describe how to use the ODBC  
client interface.  
— README for HP JDBC Type 4 Driver  
— README for HP ODBC Driver for Windows  
— README for HP ODBC Driver for Linux and HP-UX  
— README for HP Neoview Script  
Neoview Support Library  
Boot Application Online Help  
Reference information for using the boot software.  
Neoview Database Support Guide  
Procedures and reference information that are unique to the Neoview  
database software or not documented in other HP manuals.  
18  
About This Document  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Neoview Hardware Installation and Support  
Guide  
Installation and replacement procedures.  
Neoview Management Dashboard Support Guide Information on managing and configuring Dashboard from the  
Dashboard Server and Client, including starting and running  
Dashboard, using Discrete Object Thresholds (DOTs), using Dashboard  
Command Interpreter commands, using the Entity Definition Language  
(EDL), and using Dashboard data definitions and record declarations.  
Neoview Migration and Upgrade Guide  
Procedures for adding hardware, installing RVUs and updating other  
software and firmware.  
Neoview ODBC and JDBC Troubleshooting  
Guide  
Guidelines for troubleshooting ODBC and JDBC connectivity to an  
HP Neoview data warehousing platform.  
Neoview SQL Metadata Quick Reference  
Neoview System Console Installer Guide  
Neoview Query Support Guide  
Quick guide to schemas, tables, columns, and data types for Version  
2000 Neoview SQL metadata.  
Information about installing and configuring applications on the  
Neoview system console  
Information related to query execution plans and how to affect the  
query performance of Neoview databases  
Neoview Virtual TapeServer Installation and  
Support Guide  
Information about installing and maintaining the Neoview Virtual  
TapeServer (VTS).  
Neoview Workload Management Services Guide Information about using Neoview Workload Management Services  
(NWMS) to manage workload and resources on a Neoview data  
warehousing platform.  
Publishing History  
Part Number  
Product Version  
Publication Date  
August 2006  
October 2006  
November 2006  
March 2007  
542714-003  
543708-001  
543707-001  
544356-001  
544530-001  
HP Neoview Release 1.0  
HP Neoview Release 1.1  
HP Neoview Release 1.2  
HP Neoview Release 2.0  
HP Neoview Release 2.1  
May 2007  
HP Encourages Your Comments  
HP encourages your comments concerning this document. We are committed to providing  
documentation that meets your needs. Send any errors found, suggestions for improvement, or  
compliments to:  
[email protected]  
Include the document title, part number, and any comment, error found, or suggestion for  
improvement you have concerning this document.  
Publishing History  
19  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
20  
Download from Www.Somanuals.com. All Manuals Search And Download.  
1 Introduction to Neoview Script  
Neoview Script is a command-line interface that you download and install on a client workstation  
that has the Neoview JDBC Type 4 Driver installed. Operating systems that support the JDBC  
driver include Windows, Linux, and UNIX. The JDBC driver connects Neoview Script on a client  
workstation to a Neoview database on a Neoview data warehousing platform.  
Figure 1-1 Neoview Script Within a Neoview Platform Network  
Neoview Script enables you to perform daily administrative and database management tasks  
by running SQL statements interactively or from script files. You can also run Neoview Script  
from a Perl or Python command line or from Perl or Python programs. Neoview Script supports  
many SQL statements. For a list of these statements, see Appendix B (page 133).  
Neoview Script does not support:  
•
•
•
Adding, modifying, and deleting users  
Changing user passwords  
Job scheduling  
21  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
22  
Download from Www.Somanuals.com. All Manuals Search And Download.  
2 Installing Neoview Script  
NOTE: If you are manually installing Neoview Script on a Linux platform that has the Neoview  
data loader installed, use the services or sysadmin ID instead of root, which has been frozen for  
the loader. The best way to install Neoview Script on the loader platform is by using the Neoview  
Loader Supplemental executive (Installsuppkt). For more information, see the Neoview Migration  
and Upgrade Guide.  
To install Neoview Script, follow these procedures:  
1. Preinstallation procedures:  
•
•
•
“Installing and Verifying the Java Runtime Environment (JRE)” (page 23)  
“Installing and Verifying the Neoview JDBC Type 4 Driver” (page 26)  
“Installing Perl or Python” (page 27)  
2. Installation procedures:  
•
•
•
“Downloading the Installer” (page 27)  
“Verifying the Version of the Installer File” (page 28)  
“Running the Installer” (page 28)  
3. Postinstallation procedures:  
•
•
•
•
“Verifying the Installed Software Files” (page 34)  
“Verifying the Installed Version of Neoview Script” (page 35)  
“Setting the Look and Feel of the Neoview Script Interface” (page 35)  
“Testing the Launch of Neoview Script” (page 39)  
Preinstallation Procedures  
•
•
•
“Installing and Verifying the Java Runtime Environment (JRE)” (page 23)  
“Installing and Verifying the Neoview JDBC Type 4 Driver” (page 26)  
“Installing Perl or Python” (page 27)  
Installing and Verifying the Java Runtime Environment (JRE)  
Neoview Script and the Neoview JDBC Type 4 Driver require a compatible Java version to be  
installed on the client workstation. The supported Java versions are:  
•
•
JRE 1.4.2  
JRE 1.4.2_01, 1.4.2_02, 1.4.2_03, 1.4.2_04, 1.4.2_05, 1.4.2_06, 1.4.2_07, 1.4.2_10, and 1.4.2_11  
These Java versions are not supported:  
•
•
Versions before 1.4.2  
Version 1.5  
If you are using U.S. Daylight Savings Time (DST), be aware that the start and stop dates for  
DST will change from the first Sunday in April to the second Sunday in March and from the last  
Sunday in October to the first Sunday in November, starting in 2007. To avoid using incorrect  
times, make sure that your Java Runtime Environment uses the correct DST rules. JRE 1.4.2_11  
and later versions support the new DST rules.  
Installing a Supported Java Version  
To install one of the supported Java versions on the client workstation, follow the instructions  
on the Sun Microsystems Web site:  
http://java.sun.com/j2se/desktopjava/jre/index.jsp  
Preinstallation Procedures  
23  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
After installing the Java version, proceed with “Verifying the Java Version” (page 24).  
Verifying the Java Version  
To display the Java version of the client workstation on the screen, enter:  
java -version  
For example:  
C:\>java -version  
java version "1.4.2_10"  
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03)  
Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode)  
C:\>  
If the returned version is not supported or is unavailable, see:  
•
•
“Setting the PATH to a Supported Java Version on Windows” (page 24)  
“Setting the PATH to a Supported Java Version on Linux or UNIX” (page 26)  
Setting the PATH to a Supported Java Version on Windows  
1. Right-click the My Computer icon on your desktop, and then select Properties:  
2. In the System Properties dialog box, click the Advanced tab.  
3. Click the Environment Variables button:  
24  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
4. Under System variables, select the variable named Path, and then click Edit:  
Preinstallation Procedures  
25  
Download from Www.Somanuals.com. All Manuals Search And Download.  
5. Place the cursor at the beginning of the Variable Value field and type the path of the Java  
bindirectory, ending with a semicolon (;):  
For example:  
"C:\Program Files\Java\j2re1.4.2_10\bin";  
NOTE: Check that no space is after the semicolon (;) in the path. If there are spaces in the  
directory name, delimit the entire directory path in double quotes (") before the semicolon.  
6. Click OK.  
7. Verify that the updated Path appears under System variables, and click OK.  
8. In the System Properties dialog box, click OK to accept the changes.  
Setting the PATH to a Supported Java Version on Linux or UNIX  
1. Open the user profile (.profileor .bash_profilefor the Bash shell) in the /home  
directory. For example:  
vi .profile  
2. In the user profile, set the PATH environment variable to include the path of the Java bin  
directory. For example:  
export PATH=/opt/java1.4/jre/bin:$PATH  
NOTE: Place the path of the Java bindirectory before $PATH, and check that no space is  
after the colon (:) in the path. In the C shell, use the setenvcommand instead of export.  
3. To activate the changes, either log out and log in again or execute the user profile. For  
example:  
. .profile  
Installing and Verifying the Neoview JDBC Type 4 Driver  
Neoview Script requires a compatible JDBC driver to be installed on the client workstation. For  
Neoview Release 2.1, Neoview Script requires the JDBC Type 4 Driver for Neoview Release 2.1.  
Installing the JDBC Driver  
To install the JDBC driver:  
1. Download and extract the product distribution file.  
2. Set the CLASSPATH to the product JAR file.  
For information about how to install, verify, and use the JDBC driver, see the Neoview JDBC Type  
4 Driver Programmer’s Reference or the product README.  
Verifying the JDBC Driver  
To display the version of the JDBC driver that is already installed on the client workstation:  
26  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
1. Change the directory to the libdirectory, which contains the JDBC driver JAR file:  
•
On Windows, enter this command:  
cd jdbc-installation-directory\lib  
jdbc-installation-directoryis the directory where you installed the JDBC  
driver.  
•
On Linux or UNIX, enter this command:  
cd jdbc-installation-directory/lib  
jdbc-installation-directoryis the directory where you installed the JDBC  
driver.  
2. Enter this command to return version information:  
java -jar hpt4jdbc.jar  
For example:  
C:\>cd install\hpt4jdbc\lib  
C:\install\hpt4jdbc\lib>java -jar hpt4jdbc.jar  
T1249_N24_AAK(R2.1)_11MAY07_HP_JDBCT4_2007_04_05  
C:\install\hpt4jdbc\lib>  
If the JAR file is inaccessible or the returned version is not supported, see “Installing the JDBC  
Driver” (page 26).  
Installing Perl or Python  
If you plan to use Perl or Python scripts with Neoview Script, verify that you have Perl or Python  
installed on the client workstation. Neoview Script supports these versions of Perl and Python:  
•
•
Perl version 5.6.1  
Python version 2.3.4  
If you do not have Perl or Python, download it from any open source software provider. You  
can perform this installation procedure anytime before or after installing Neoview Script.  
NOTE: Neoview Script provides a beta version of enhanced support for Perl and Python  
programs. This beta version requires Jython (for Python programs) and a different version of  
Perl to be installed on the client workstation. For more information, see the README in the  
Neoview Script samplesdirectory.  
Installation Procedures  
NOTE: Before following the installation procedures, you must install the Neoview JDBC Type  
4 Driver on the client workstation. For more information, see “Preinstallation Procedures”  
(page 23).  
•
•
•
“Downloading the Installer” (page 27)  
“Verifying the Version of the Installer File” (page 28)  
“Running the Installer” (page 28)  
Downloading the Installer  
The Neoview Script software is available as a downloadable installer file, hpnvsInstaller.jar,  
on the Software Depot site.  
Installation Procedures  
27  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
1. Locate or create a directory or folder for the installer file anywhere on the client workstation.  
2. On the client workstation, start a Web browser and navigate to the download site:  
http://www.software.hp.com  
3. Enter “Neoview Script” in the search box in the upper right corner of the Software Depot  
home page.  
4. Click the HP Neoview Script link that appears in the search results.  
5. Follow instructions to download HP Neoview Script, which includes the  
hpnvsInstaller.jarfile, to the directory or folder in Step 1.  
NOTE: In the File Download dialog box, make sure to select the Save or Save this file to  
disk option.  
Verifying the Version of the Installer File  
To display the version of the downloaded installer file:  
1. Change to the directory where you downloaded the Neoview Script installer file:  
cd installer-directory  
installer-directoryis the directory where you downloaded the installer.  
2. Enter this command to return version information:  
java -jar hpnvsInstaller.jar v  
For example:  
C:\>cd download  
C:\download>java -jar hpnvsInstaller.jar v  
T0774_N24_AAC(R2.1)_11MAY07_HP_hpnvs_2007_04_12  
C:\download>  
Running the Installer  
NOTE: Before running the installer, you must install the Neoview JDBC Type 4 Driver on the  
client workstation. For more information, see “Preinstallation Procedures” (page 23).  
You have a choice of running the installer from the Installer Wizard Graphical User Interface  
(GUI) or from the command line:  
•
•
“Installer Wizard Steps” (page 28)  
“Command-Line Installation Steps” (page 33)  
Installer Wizard Steps  
NOTE: On Linux or UNIX, to run the Installer Wizard, you must have the X Window system  
installed on the client workstation. If the client workstation does not have the X Window system,  
see the “Command-Line Installation Steps” (page 33).  
Launching the Installer Wizard  
1. Locate the hpnvsInstaller.jarfile in the folder where you downloaded the installer.  
2. Verify that the hpnvsInstaller.jarfile appears as an Executable JAR File.  
If not, skip the next two steps and go to Step 5.  
3. Double-click the hpnvsInstaller.jarfile icon to launch the Installer Wizard.  
4. Proceed to “Using the Installer Wizard” (page 29).  
28  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
5. At a command prompt, change to the directory where you downloaded the installer:  
cd installer-directory  
installer-directoryis the directory where you downloaded the installer file,  
hpnvsInstaller.jar.  
6. Launch the Installer Wizard by entering:  
java -jar hpnvsInstaller.jar  
7. Proceed to “Using the Installer Wizard” (page 29).  
Using the Installer Wizard  
When you execute hpnvsInstaller.jar, the Installer Wizard appears:  
1. To locate the JDBC driver JAR file, click Browse next to HP Neoview JDBC Type 4 Driver  
JAR file:  
2. Select the lib folder of the JDBC driver, and then click Open:  
Installation Procedures  
29  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
3. Select hpt4jdbc.jar so that it appears in the File Name box, and then click Select:  
The Installer Wizard now displays the path of the JDBC driver JAR file:  
30  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
4. To find an installation location for Neoview Script, click Browse next to HP Neoview Script  
installation directory:  
5. Select the folder where you want to install Neoview Script so that the directory path appears  
in the File Name box, and then click Select:  
Installation Procedures  
31  
Download from Www.Somanuals.com. All Manuals Search And Download.  
The Installer Wizard displays the directory where the Neoview Script will be installed.  
6. Click Install to start the installation:  
32  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
The Installation Status dialog box appears on the screen, indicating how many files are  
installed in the installation directory:  
The number of files that are extracted and installed is 15. All these files are stored in the  
nvscriptsubdirectory within the installation directory.  
7. Click OK, and proceed with “Verifying the Installed Software Files” (page 34).  
Command-Line Installation Steps  
1. At a command prompt, change to the directory where you downloaded the installer:  
cd installer-directory  
installer-directoryis the directory where you downloaded the installer.  
2. Launch the command-line installer by entering:  
java -jar hpnvsInstaller.jar cm  
The command-line installer starts and prompts you to enter the location of the JDBC driver  
JAR file:  
3. Enter the full directory path and file name of the JDBC driver JAR file, hpt4jdbc.jar,  
which is located in the JDBC driver libdirectory:  
HP Neoview JDBC Type 4 Driver JAR File  
--------------------------------------  
Enter the location and file name: c:\install\hpt4jdbc\lib\hpt4jdbc.jar  
Installation Procedures  
33  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
4. Enter an existing directory where you would like to install Neoview Script:  
HP Neoview Script  
--------------------------------------  
Enter the installation directory: c:\install  
The installation status appears, indicating how many files are installed in the installation  
directory:  
HP Neoview Script  
--------------------------------------  
Enter the installation directory: c:\install  
Extracted 15 files from the  
/C:/download/hpnvsInstaller.jar  
archive into the  
c:\install  
directory.  
Installation Complete.  
C:\download>  
The number of files that are extracted and installed is 15. All these files are stored in the  
nvscriptsubdirectory within the installation directory.  
5. Proceed with “Verifying the Installed Software Files” (page 34).  
Postinstallation Procedures  
•
•
•
“Verifying the Installed Software Files” (page 34)  
“Verifying the Installed Version of Neoview Script” (page 35)  
“Testing the Launch of Neoview Script” (page 39)  
Verifying the Installed Software Files  
After downloading and running the installer file, hpnvsInstaller.jar, verify that the Neoview  
Script software files are installed in the correct locations. See Table 2-1 (page 34).  
Table 2-1 Locations of Neoview Script Software Files  
Directory  
Files  
Description  
install>nvscript>bin  
hpnvs.cmd  
hpnvs.pl  
Windows launch file  
Perl wrapper script  
hpnvs.py  
Python wrapper script  
Linux or UNIX launch file  
Beta version Perl wrapper script  
hpnvs.sh  
1
hpnvs-perl.pl  
hpnvs-python.py  
hpnvs.jar  
Session.pm  
Session.py  
README  
1
Beta version Python wrapper script  
Product JAR file  
install>nvscript>lib  
install>nvscript>lib>perl  
install>nvscript>lib>python  
install>nvscript>samples  
Product file  
Product file  
Readme file that describes how to use  
the sample scripts  
sample.pl  
sample.py  
sample.sql  
Sample Perl program  
Sample Python program  
Sample SQL script  
34  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Table 2-1 Locations of Neoview Script Software Files (continued)  
Directory  
Files  
Description  
1
sample-beta.pl  
sample-beta.py  
Beta version of sample Perl program  
Beta version of sample Python  
1
program  
1
Neoview Script provides a beta version of enhanced support for Perl and Python programs. This functionality enables  
multiple SQL statements to run in one database connection from a Perl or Python program. For more information,  
see the README in the Neoview Script samplesdirectory.  
Verifying the Installed Version of Neoview Script  
To display the installed version of Neoview Script without launching Neoview Script and  
connecting to the database platform:  
1. Change to the libdirectory, which contains the Neoview Script JAR file:  
•
On Windows, enter:  
cd hpnvs-installation-directory\nvscript\lib  
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files.  
•
On Linux or UNIX, enter:  
cd hpnvs-installation-directory/nvscript/lib  
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files.  
2. Enter this command to return version information:  
java -jar hpnvs.jar  
For example:  
C:\>cd install\nvscript\lib  
C:\install\nvscript\lib>java -jar hpnvs.jar  
T0774_N24_AAC(R2.1)_11MAY07_HP_hpnvs_2007_04_12  
C:\install\nvscript\lib>  
If the JAR file is inaccessible or the returned version is not supported, see “Installation  
Procedures” (page 27).  
To display the installed versions of Neoview Script and the JDBC Type 4 Driver in the Neoview  
Script interface:  
1. Launch the Neoview Script interface. See Chapter 3 (page 41).  
2. Enter the VERSION command to display information about the build versions:  
SQL>version  
Neoview Script Build Version  
: T0774_N24_AAC(R2.1)_11MAY07_HP_hpnvs_2007_04_12  
JDBC Type 4 Driver Build Version : T1249_N24_AAK(R2.1)_11MAY07_HP_JDBCT4_2007_04_05  
SQL>  
If the returned version is not supported, see “Installation Procedures” (page 27).  
Setting the Look and Feel of the Neoview Script Interface  
To determine the look and feel of the Neoview Script interface, set the -DhpnvsLFproperty by  
using the _JAVA_OPTIONS environment variable. This property affects the formatting of status  
messages. This property does not restrict the SQL statements, commands, or syntax that you can  
Postinstallation Procedures  
35  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
execute in the Neoview Script interface. Each look-and-feel type accepts all the SQL statements,  
commands, and syntax that Neoview Script currently supports.  
Supported Look-and-Feel Types  
Currently, Neoview Script supports the SQLPlus and Teradata look-and-feel types, in addition  
to the default look and feel, Neoview SQL. The default look and feel, Neoview SQL, appears as  
shown below:  
Welcome to the HP Neoview Script Interface 2.1  
(c) Copyright 2006, 2007 Hewlett-Packard Development Company, LP.  
Connected to DataSource: TDM_Default_DataSource  
SQL>create view persnl.salarylist  
+>as select salary from persnl.employee;  
--- SQL operation complete.  
SQL>  
The -DhpnvsLFproperty value for setting the SQLPlus look and feel is SQLPlus. The SQLPlus  
look and feel appears as shown below:  
Picked up _JAVA_OPTIONS: -DhpnvsLF=SQLPlus  
Welcome to the HP Neoview Script Interface 2.1  
(c) Copyright 2006, 2007 Hewlett-Packard Development Company, LP.  
Connected to DataSource: TDM_Default_DataSource  
SQL>create view persnl.salarylist  
+>as select salary from persnl.employee;  
View created.  
SQL>  
NOTE: The look and feel property value Oracleis supported for backward compatibility.  
The -DhpnvsLFproperty value for setting the Teradata look and feel is BTEQ. Setting this  
property results in a Teradata personality for the messages logged for all SQL operations within  
Neoview Script. The Teradata look and feel appears as shown below:  
SQL>set schema sch;  
*** Schema has been set.  
*** Total elapsed time was 16 second(s).  
SQL>select * from book;  
BOOKID  
BOOKTITLE  
BOOKAUTHORID ISCHECKEDOUT  
----------- ------------------------------ ------------ ------------  
13333 UML Simplified  
11111 C++ Internals  
12222 Object Oriented Design  
93333  
91111  
92222  
0
0
0
*** Query completed. 3 rows found. 4 columns returned.  
*** Total elapsed time was 1 second(s).  
SQL>  
To set the look and feel, see:  
•
•
•
“Setting the Look and Feel at a Command-Line Prompt” (page 37)  
“Setting the Look and Feel in the System Properties on Windows” (page 37)  
“Setting the Look and Feel in the User Profile on Linux or UNIX” (page 39)  
36  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
If you do not set a look and feel, the default is Neoview SQL.  
Setting the Look and Feel at a Command-Line Prompt  
To set the _JAVA_OPTIONS environment variable for each session at a command-line prompt:  
•
On Windows, enter this command:  
set _JAVA_OPTIONS=-DhpnvsLF=look-and-feel-type  
look-and-feel-typeis one of the “Supported Look-and-Feel Types” (page 36). For  
example:  
set _JAVA_OPTIONS=-DhpnvsLF=SQLPlus  
set _JAVA_OPTIONS=-DhpnvsLF=BTEQ  
•
On Linux or UNIX, enter this command:  
export _JAVA_OPTIONS=-DhpnvsLF=look-and-feel-type  
look-and-feel-typeis one of the “Supported Look-and-Feel Types” (page 36). For  
example:  
export _JAVA_OPTIONS=-DhpnvsLF=SQLPlus  
export _JAVA_OPTIONS=-DhpnvsLF=BTEQ  
To return to the default look and feel, Neoview SQL, set the -DhpnvsLFproperty value to nvs.  
If you specify an invalid value, a warning message is displayed and the property value is set to  
nvs.  
Setting the Look and Feel in the System Properties on Windows  
1. Right-click the My Computer icon on your desktop and then select Properties.  
2. In the System Properties dialog box, select the Advanced tab and click Environment  
Variables.  
Postinstallation Procedures  
37  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
3. If _JAVA_OPTIONS does not appear among the environment variables, click New under  
System or User variables. If _JAVA_OPTIONS already exists, click Edit.  
4. Type _JAVA_OPTIONS for the Variable Name and the -DhpnvsLFproperty value for the  
Variable Value, and click OK.  
The Variable Value must include:  
-DhpnvsLF=look-and-feel-type  
look-and-feel-typeis one of the “Supported Look-and-Feel Types” (page 36). For  
example:  
-DhpnvsLF=SQLPlus  
5. Verify that the new or updated _JAVA_OPTIONS appears under System or User variables  
and click OK.  
38  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
6. In the System Properties dialog box, click OK to accept the changes.  
To return to the default look and feel, Neoview SQL, set the -DhpnvsLFproperty value to nvs.  
Setting the Look and Feel in the User Profile on Linux or UNIX  
1. Open the user profile (.profileor .bash_profilefor the Bash shell) in the /home  
directory. For example:  
vi .profile  
2. Add this exportcommand (or a setenvcommand for the C shell) to the user profile. For  
example:  
export _JAVA_OPTIONS=-DhpnvsLF=look-and-feel-type  
look-and-feel-type is one of the “Supported Look-and-Feel Types” (page 36). For  
example:  
export _JAVA_OPTIONS=-DhpnvsLF=SQLPlus  
export _JAVA_OPTIONS=-DhpnvsLF=BTEQ  
3. To activate the changes, either log out and log in again or execute the user profile. For  
example:  
. .profile  
To return to the default look and feel, Neoview SQL, set the -DhpnvsLFproperty value to nvs.  
Testing the Launch of Neoview Script  
1. Launch the Neoview Script interface and verify that you can connect to the database. For  
instructions, see Chapter 3 (page 41).  
This window should appear:  
Postinstallation Procedures  
39  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
2. If you cannot connect to the database, verify that:  
1. The database platform is available and running, the port number is correct for the  
database platform, and you are authorized to log in to that database platform. To create  
a user ID to log in to the database, see the Neoview Database Administrator’s Guide.  
2. The version of the Neoview JDBC Type 4 Driver is compatible with the Java Runtime  
Environment (JRE) of the workstation. See “Installing and Verifying the Java Runtime  
Environment (JRE)” (page 23).  
3. You installed the Neoview Script software files correctly. See “Verifying the Installed  
Software Files” (page 34).  
40  
Installing Neoview Script  
Download from Www.Somanuals.com. All Manuals Search And Download.  
3 Launching the Neoview Script Interface  
This chapter describes how to launch the Neoview Script interface from the Windows, Linux, or  
UNIX environment:  
•
•
•
•
•
•
“Launching the Neoview Script Interface on Windows” (page 41)  
“Launching the Neoview Script Interface on Linux or UNIX” (page 44)  
“Logging In to the Database Platform” (page 45)  
“Using Optional Launch Parameters” (page 46)  
“Launching Neoview Script Without Connecting to the Database” (page 49)  
“Exiting the Neoview Script Interface”  
For information about launching Neoview Script from Perl or Python, see Chapter 6 (page 71).  
Launching the Neoview Script Interface on Windows  
1. Find the Windows launch file, hpnvs.cmd, in the Neoview Script binfolder:  
2. Double-click the hpnvs.cmdfile.  
The Neoview Script interface appears, prompting you to enter the host name or IP address  
of the database platform, your user name, password, and a data source name. See “Logging  
In to the Database Platform” (page 45).  
Creating a Shortcut to hpnvs.cmd  
To enable a user to launch Neoview Script from a shortcut icon on the desktop:  
1. Right-click the desktop and select New > Shortcut:  
Launching the Neoview Script Interface on Windows  
41  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
2. Type the location of hpnvs.cmdwithin double quotes (“) or click Browse to locate that file,  
and then click Next:  
For the location of the Neoview Script software files, see Table 2-1 (page 34).  
3. Type a name for the shortcut and click Finish:  
42  
Launching the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
4. If desired, specify optional launch parameters for the shortcut:  
a. Right-click the shortcut icon and select Properties:  
b. Click the Shortcut tab.  
c. In the Target box, insert a space after "...\nvscript\bin\hpnvs.cmd"and add  
the optional launch parameters:  
Launching the Neoview Script Interface on Windows  
43  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
For more information, see “Using Optional Launch Parameters” (page 46).  
d. Click OK.  
5. To launch Neoview Script, double-click the shortcut icon.  
The Neoview Script interface appears. If you did not set the optional launch parameters,  
the Neoview Script interface prompts you to enter the host name or IP address of the database  
platform, your user name, password, and a data source name. See “Logging In to the Database  
Platform” (page 45).  
Launching the Neoview Script Interface on Linux or UNIX  
In the terminal window, enter:  
./hpnvs-installation-directory/nvscript/bin/hpnvs.sh  
hpnvs-installation-directoryis the directory where you installed the Neoview Script  
software files. For more information, see Table 2-1 (page 34).  
Setting the PATH of hpnvs.sh  
To enable a user to launch Neoview Script anywhere on the client workstation:  
1. Open the user profile (.profileor .bash_profilefor the Bash shell) in the /home  
directory. For example:  
vi .profile  
2. In the user profile, set the PATH environment variable to include the path of the hpnvs.sh  
file. For example:  
export PATH=/hpnvs-installation-directory/nvscript/bin/:...  
44  
Launching the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files. For more information, see Table 2-1 (page 34). Check that no space is  
after the colon (:) in the path.  
NOTE: In the C shell, use the setenvcommand instead of export.  
3. To activate the changes, either log out and log in again or execute the user profile. For  
example:  
. .profile  
4. On the command line, execute the hpnvs.shfile to launch Neoview Script:  
hpnvs.sh  
The Neoview Script interface appears, prompting you to enter the host name or IP address  
of the database platform, your user name, password, and a data source name. See “Logging  
In to the Database Platform” (page 45).  
NOTE: To enable all users to launch Neoview Script anywhere on the system, create a  
symbolic link to the hpnvs.shfile in the /usr/binor /usr/local/bindirectory:  
ln -s ./hpnvs-installation-directory/nvscript/bin/hpnvs.sh /usr/bin/hpnvs.sh  
Presetting the Optional Launch Parameters  
To preset the optional launch parameters for each session, use an alias command. For example:  
alias hpnvs='hpnvs.sh -h sys0101.mylab.mycorp.net:18650 -u dba1 -p xxxxxx -dsn DataSourceName'  
You can add the alias, hpnvs, to the user profile, or you can enter it at a command prompt. For  
more information about the optional launch parameters, see “Using Optional Launch Parameters”  
(page 46).  
Logging In to the Database Platform  
•
•
“Default Login” (page 45)  
“Login Parameters” (page 46)  
Default Login  
NOTE: You must be authorized to log in to the database platform. To create a user ID to log in  
to the database, see the Neoview Database Administrator’s Guide.  
1. After you launch the Neoview Script interface, Neoview Script prompts you to enter the  
host name or IP address of the database platform:  
Host Name/IP Address: _  
Enter a host name:  
host-name[.domain-name][:port-number]  
•
If you do not specify the domain name, Neoview Script uses the domain of the client  
workstation.  
•
If you do not specify a port number, Neoview Script uses the default port number,  
which is 18650.  
Or enter an IP address:  
IP-address[:port-number]  
2. Enter your user name.  
Logging In to the Database Platform  
45  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
3. Enter your password.  
4. Enter the name of a data source that is available and running (that is, started).  
If you do not enter a data source, Neoview Script connects to Admin_Load_DataSource  
by default. Admin_Load_DataSourceis the recommended data source for Neoview Script  
connections. If Admin_Load_DataSource(or any data source that you specify) is not  
started, Neoview Script returns an error and prompts you to close the session. If you specify  
a data source that does not exist, Neoview Script returns a warning and connects to  
TDM_Default_DataSourceinstead.  
After you finish logging in to the database platform, the SQL prompt appears.  
Host Name/IP Address: sys0101.mylab.mycorp.net:18650  
User Name: dba1  
Password:  
DataSource Name [Admin_Load_DataSource]:  
Welcome to the HP Neoview Script Interface 2.1  
(c) Copyright 2006, 2007 Hewlett-Packard Development Company, LP.  
Connected to DataSource: Admin_Load_DataSource  
SQL>  
At the prompt, you can enter an SQL statement or a Neoview Script interface command. For  
more information, see Chapter 4 (page 51).  
Login Parameters  
Instead of the default method of logging in to the database platform, use the login parameters  
-h(or -host), -u(or -user), -p(or -password), and -dsnwhen launching Neoview Script.  
For more information, see “Logging In When Launching Neoview Script” (page 47).  
Using Optional Launch Parameters  
To customize how you launch and log in to the Neoview Script interface, use these optional  
parameters:  
Launch Parameter  
Description  
{-h | -host} host-name[:port-number]{-h | Specifies the host name or IP address of the database  
platform to which you want the client to connect. The  
host-nameshould include the domain name of the  
database platform if it is different from the domain of the  
client workstation. If you do not specify a port number,  
Neoview Script uses the default port number, which is  
18650. For more information, see “Logging In When  
Launching Neoview Script” (page 47).  
-host} IP-address[:port-number]  
{-u | -user} user-name  
{-p | -password} password  
-dsn data-source-name  
Specifies the user name to log in to the database platform.  
For more information, see “Logging In When Launching  
Neoview Script” (page 47).  
Specifies the password of the user to log in to the database  
platform. For more information, see “Logging In When  
Launching Neoview Script” (page 47).  
Specifies the name of a data source. The recommended  
data source for Neoview Script connections is  
Admin_Load_DataSource. If  
Admin_Load_DataSource(or any data source that you  
specify) is not started, Neoview Script returns an error  
and prompts you to close the session. If you specify a data  
source that does not exist, Neoview Script returns a  
warning and connects to TDM_Default_DataSource  
instead. For more information, see “Logging In When  
Launching Neoview Script” (page 47).  
46  
Launching the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
Launch Parameter  
Description  
{-q | -sql} "command"  
Specifies that an SQL statement or a Neoview Script  
interface command be run when launching the Neoview  
Script interface. You cannot specify this parameter at the  
same time as the -sor -scriptparameter. For more  
information, see “Running a Command When Launching  
Neoview Script” (page 47).  
{-s | -script} script-file-name  
Specifies that a script file be run when launching the  
Neoview Script interface. You cannot specify this  
parameter at the same time as the -qor -sqlparameter.  
For more information, see “Running a Script File When  
Launching Neoview Script” (page 48).  
-noconnect  
Launches a Neoview script session without connecting to  
the Neoview platform (database).For more information,  
see “Launching Neoview Script Without Connecting to  
the Database” (page 49).  
Logging In When Launching Neoview Script  
To avoid entering a host name, user name, password, or data source when the Neoview Script  
interface launches, use the -h(or -host), -u(or -user), -p(or -password), or -dsn  
command-line parameters.  
NOTE: You can include these parameters in a shortcut to the hpnvs.cmdfile or in a launch  
file for the hpnvs.shfile. For more information, see “Creating a Shortcut to hpnvs.cmd” (page 41)  
or “Presetting the Optional Launch Parameters” (page 45), respectively.  
•
On Windows, in the Command Prompt window, enter:  
cd hpnvs-installation-directory\nvscript\bin  
hpnvs.cmd -h sys0101.mylab.mycorp.net:18650 -u dba1 -p xxxxxx  
-dsn DataSourceName  
•
On Linux or UNIX, in the terminal window, enter:  
cd hpnvs-installation-directory/nvscript/bin  
./hpnvs.sh -h sys0101.mylab.mycorp.net:18650 -u dba1 -p xxxxxx  
-dsn DataSourceName  
The Neoview Script interface launches and prompts you to enter an SQL statement or a Neoview  
Script interface command:  
Welcome to the HP Neoview Script Interface 2.1  
(c) Copyright 2006, 2007 Hewlett-Packard Development Company, LP.  
Connected to DataSource: Admin_Load_DataSource  
SQL>  
Running a Command When Launching Neoview Script  
To execute an SQL statement or a Neoview Script interface command when launching Neoview  
Script, use the -qor -sqlcommand-line parameter. This parameter enables you to run a single  
command on the command line without having to enter commands in the Neoview Script  
interface.  
NOTE: You cannot specify this parameter at the same time as the -sor -scriptparameter.  
When using -qor -sql, you must enclose the command in double quotes. The SQL terminator  
is not required at the end of an SQL statement and is disallowed after a Neoview Script interface  
command.  
Logging In to the Database Platform  
47  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Although you can run any of the Neoview Script interface commands with -qor -sql, the @,  
OBEY, and PRUN commands are the most useful. For a list of supported SQL statements, see  
Appendix B (page 133).  
Example of Running an SQL Statement With -q or -sql  
Use -qor -sqlwith the CREATE SCHEMA statement to create a schema when launching the  
Neoview Script interface:  
•
On Windows, in the Command Prompt window, enter:  
cd hpnvs-installation-directory\nvscript\bin  
hpnvs.cmd -q "create schema persnl"  
•
On Linux or UNIX, in the terminal window, enter:  
cd hpnvs-installation-directory/nvscript/bin  
./hpnvs.sh -q "create schema persnl"  
After you enter the SQL statement, the Neoview Script interface launches, prompts you to log  
in by default (if you did not specify -h, -u, -p, and -dsnon the command line), runs the SQL  
statement, and then returns to the command prompt:  
Host Name/IP Address: sys0101.mylab.mycorp.net:18650  
User Name: dba1  
Password:  
DataSource Name [Admin_Load_DataSource]:  
--- SQL operation complete.  
C:\install\nvscript\bin>_  
Example of Running a Neoview Script Interface Command With -q or -sql  
Use -qor -sqlwith the PRUN command to run multiple script files simultaneously from the  
command line:  
•
On Windows, in the Command Prompt window, enter:  
cd hpnvs-installation-directory\nvscript\bin  
hpnvs.cmd -q "prun"  
•
On Linux or UNIX, in the terminal window, enter:  
cd hpnvs-installation-directory/nvscript/bin  
./hpnvs.sh -q "prun"  
After you enter the Neoview Script interface command, the Neoview Script interface launches,  
prompts you to log in by default (if you did not specify -h, -u, -p, and -dsnon the command  
line), and runs the command. The parallel run (PRUN) operation prompts you to enter settings  
and then executes the script files. At the end of the PRUN operation, the Neoview Script interface  
returns to the command prompt. For more information about the PRUN operation, see “PRUN  
Command” (page 95).  
Running a Script File When Launching Neoview Script  
To run a script file when launching Neoview Script, use the -sor -scriptcommand-line  
parameter.  
NOTE: You cannot specify this parameter at the same time as the -qor -sqlparameter.  
After you launch the Neoview Script interface with -sor -script, Neoview Script executes  
the script file. The Neoview Script interface remains open until you enter the EXIT, QUIT, or  
48  
Launching the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
DISCONNECT command. To quit the interface immediately after executing a script file, include  
the EXIT, QUIT, or DISCONNECT command at the end of the script file.  
Example of a Script File  
You can create a script file that contains SET commands that customize a session when you  
launch Neoview Script:  
For more information, see “Creating a Script File” (page 67).  
Example of Running a Script File With -s or -script  
•
On Windows, in the Command Prompt window, enter:  
cd hpnvs-installation-directory\nvscript\bin  
hpnvs.cmd -s settings.txt  
Specify the full path of the script file if it is outside the directory of hpnvs.cmd.  
•
On Linux or UNIX, in the terminal window, enter:  
cd hpnvs-installation-directory/nvscript/bin  
./hpnvs.sh -s settings.txt  
Specify the full path of the script file if it is outside the directory of hpnvs.sh.  
The Neoview Script interface launches, prompts you to log in by default (if you did not specify  
-h, -u, -p, and -dsnon the command line), and runs the commands in the script file:  
Host Name/IP Address: sys0101.mylab.mycorp.net:18650  
User Name: dba1  
Password:  
DataSource Name [Admin_Load_DataSource]:  
Welcome to the HP Neoview Script Interface 2.1  
(c) Copyright 2006, 2007 Hewlett-Packard Development Company, LP.  
Connected to DataSource: Admin_Load_DataSource  
SQL>SET IDLETIMEOUT 0  
SQL>SET SQLPROMPT *  
*SET TIME ON  
14:14:57 *SET TIMING ON  
2:14:57 PM *SET SQLTERMINATOR .  
2:14:57 PM *  
Launching Neoview Script Without Connecting to the Database  
To start a Neoview Script session without connecting to the Neoview platform, use the  
-noconnectoption.  
Logging In to the Database Platform  
49  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Example of Launching Neoview Script File With -noconnect  
•
On Windows, in the Command Prompt window, enter:  
cd hpnvs-installation-directory\nvscript\bin  
hpnvs.cmd -noconnect  
•
On Linux or UNIX, in the terminal window, enter:  
cd hpnvs-installation-directory/nvscript/bin  
./hpnvs.sh -noconnect  
Exiting the Neoview Script Interface  
To exit the Neoview Script interface, enter one of these commands at a prompt:  
•
•
EXIT  
QUIT  
For example:  
SQL>quit  
These commands are not case-sensitive and do not require a terminator before you press Enter.  
After you enter one of these commands, the Neoview Script interface immediately quits running  
and disappears from the screen.  
50  
Launching the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
4 Running Commands Interactively in the Neoview Script  
Interface  
After launching the Neoview Script interface, you can run SQL statements and Neoview Script  
interface commands in the interface.  
•
•
•
•
“Neoview Script Interface” (page 51)  
“Using Neoview Script Interface Commands” (page 52)  
“Running SQL Statements” (page 59)  
“Logging Output” (page 63)  
Neoview Script Interface  
•
•
•
•
“Product Banner” (page 51)  
“Interface Prompts” (page 51)  
“Breaking the Command Line” (page 51)  
“Case Sensitivity” (page 52)  
Product Banner  
After you launch Neoview Script and connect to the database platform, the product banner  
appears in the Neoview Script interface. The product banner displays the version of Neoview  
Script and the data source to which you are connected:  
Interface Prompts  
During a session, Neoview Script prompts you to enter SQL statements and Neoview Script  
interface commands:  
SQL>  
+>  
Standard prompt in SQL mode. You can change the  
standard prompt, SQL>, to something else by using the  
SET SQLPROMPT command. For more information, see  
the “Customizing the Standard Prompt” (page 53).  
Continuation prompt. Continue the SQL statement from  
the previous line. Use the SQL terminator (a semicolon by  
default) to terminate an SQL statement. For more  
information, see “Setting and Showing the SQL  
Terminator” (page 54). Note: Neoview Script interface  
commands must be entered on one line and do not require  
an SQL terminator.  
Breaking the Command Line  
You cannot break a Neoview Script interface command over multiple lines. Each Neoview Script  
interface command must be entered on one line. If you accidentally break a Neoview Script  
interface command across more than one line, enter the SQL terminator and then reenter the  
command on one line.  
Neoview Script Interface  
51  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                         
You can continue any SQL statement over multiple lines, breaking that statement at any point  
except within a word, a numeric literal, or a multicharacter operator (for example, <=). To break  
a string literal in a DML statement, use a concatenation operator (||). For more information, see  
the concatenation operator in the Neoview SQL Reference Manual.  
To terminate an SQL statement that spans multiple lines, use the SQL terminator for the session.  
You can also include several SQL statements on the same command line provided that each one  
is terminated by the SQL terminator. For more information, see “Setting and Showing the SQL  
Terminator” (page 54).  
Case Sensitivity  
In the Neoview Script interface, you can enter SQL statements and Neoview Script interface  
commands in uppercase, lowercase, or mixed-case characters. All parts of statements and  
commands are case-insensitive except for parts that you enclose in single-quotes (') or  
double-quotes (").  
Using Neoview Script Interface Commands  
The Neoview Script interface commands allow you to customize the Neoview Script interface  
(for example, by using SET commands) or return information about the interface settings or  
database objects (for example, by using SHOW commands):  
•
•
•
•
•
•
•
•
•
•
•
•
“Showing the Session Attributes” (page 52)  
“Setting and Showing the Idle Timeout Value for the Session” (page 53)  
“Customizing the Standard Prompt” (page 53)  
“Setting and Showing the SQL Terminator” (page 54)  
“Displaying the Elapsed Time” (page 54)  
“Setting and Showing the Current Schema” (page 55)  
“Limiting the Result Set of a Query” (page 55)  
“Showing Information About SQL Database Objects” (page 55)  
“Displaying Executed Commands” (page 58)  
“Editing and Reexecuting a Command” (page 58)  
“Clearing the Interface Window” (page 58)  
“Obtaining Help” (page 58)  
For more information about the Neoview Script interface commands, see Appendix A (page 79).  
NOTE: Each Neoview Script interface command must be entered on one line. If you accidentally  
break a Neoview Script interface command across more than one line, enter the SQL terminator  
and then reenter the command on one line.  
Showing the Session Attributes  
To display the attributes and settings of the current Neoview Script session, use the ENV, SHOW  
SESSION, or SESSION command. For example, this SESSION command displays the session  
attributes:  
SQL>session  
COLSEP  
" "  
DATASOURCE  
HISTOPT  
TDM_Default_DataSource  
ALL  
IDLETIMEOUT  
LIST COUNT  
LOG  
30 min(s)  
0 [All Rows]  
OFF  
LOOK AND FEEL BTEQ  
MARKUP  
MODE  
RAW  
SQL  
PROMPT  
SQL>  
52  
Running Commands Interactively in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
SCHEMA  
SERVER  
USR  
neo0101.acme.com:18650  
SQLTERMINATOR ;  
TIME  
OFF  
TIMING  
USER  
OFF  
role.dba  
SQL>  
For more information, see the “ENV Command” (page 85) or “SHOW SESSION Command”  
(page 122).  
Setting and Showing the Idle Timeout Value for the Session  
The idle timeout value of a session determines when the session expires after a period of inactivity.  
To set the idle timeout value of a session, enter the SET IDLETIMEOUT command. For example,  
this SET IDLETIMEOUT 0 command sets the idle timeout to an infinite amount of time so that  
the session never expires:  
SQL>set idletimeout 0  
SQL>  
To show the idle timeout value that is in effect for the session, enter the SHOW IDLETIMEOUT  
command. For example, this SHOW IDLETIMEOUT command displays an idle timeout of zero  
minutes, which means that the session never expires:  
SQL>show idletimeout  
IDLETIMEOUT 0 min(s) [Never Expires]  
SQL>  
For more information, see the “SET IDLETIMEOUT Command” (page 103) and the “SHOW  
IDLETIMEOUT Command” (page 114).  
Customizing the Standard Prompt  
To change the standard prompt in the Neoview Script interface, use one or both of these  
commands:  
•
•
“SET PROMPT Command” (page 109)  
“SET TIME Command” (page 53)  
SET PROMPT Command  
The SET PROMPT command changes the default prompt to a specified character or string. For  
example, this SET PROMPT command changes the prompt to the operating mode (SQL) and  
ENTER>:  
SQL>set prompt "%MODE ENTER>"  
SQL ENTER>  
For more information, see the “SET PROMPT Command” (page 109).  
SET TIME Command  
The SET TIME ON command causes the current time of the client workstation to be displayed  
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:  
Using Neoview Script Interface Commands  
53  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
20:32:26 SQL ENTER>set time off  
SQL ENTER>  
For more information, see the “SET TIME Command” (page 112).  
Setting and Showing the SQL Terminator  
The SQL terminator symbolizes the end of an SQL statement. By default, the SQL terminator is  
a semicolon (;).  
To change the SQL terminator, enter the SET SQLTERMINATOR command. For example, this  
SET TERMINATOR command sets the SQL terminator to a period (.):  
SQL>set sqlterminator .  
SQL>insert into sales.custlist  
+>(select * from invent.supplier  
+>where suppnum=8).  
--- 1 row(s) inserted.  
SQL>  
To show the SQL terminator that is in effect for the session, enter the SHOW SQLTERMINATOR  
command. For example, this SHOW TERMINATOR command displays SQLTERMINATOR .,  
where the period (.) is the SQL terminator for the session:  
SQL>show sqlterminator  
SQLTERMINATOR .  
SQL>  
For more information, see the “SET SQLTERMINATOR Command” (page 112) and the “SHOW  
SQLTERMINATOR Command” (page 124).  
Displaying the Elapsed Time  
By default, Neoview Script does not display the elapsed time of an SQL statement after the  
statement executes. To display the elapsed time after each SQL statement executes, enter the SET  
TIMING ON command:  
SQL>set timing on  
SQL>select suppname, street, city, state, postcode  
+>from invent.supplier  
+>where suppnum=3;  
SUPPNAME  
STREET  
CITY  
STATE  
POSTCODE  
----------------- -------------------- -------------- ------------ ----------  
HIGH DENSITY INC 7600 EMERSON  
--- 1 row(s) selected.  
Elapsed :00:00:00.111  
SQL>  
NEW YORK  
NEW YORK  
10230  
To prevent the elapsed time from being displayed after each SQL statement executes, enter the  
SET TIMING OFF command:  
SQL>set timing off  
SQL>/  
SUPPNAME  
STREET  
CITY  
STATE  
POSTCODE  
----------------- -------------------- -------------- ------------ ----------  
HIGH DENSITY INC 7600 EMERSON  
--- 1 row(s) selected.  
NEW YORK  
NEW YORK  
10230  
54  
Running Commands Interactively in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
SQL>  
For more information, see the “SET TIMING Command” (page 113).  
Setting and Showing the Current Schema  
By default, the schema of the session is USR. The SQL statement, SET SCHEMA, allows you to  
set the schema for the Neoview Script session. For example, this SET SCHEMA statement 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.  
SQL>  
The schema that you specify with SET SCHEMA remains in effect until the end of the session or  
until you execute another SET SCHEMA statement.  
If you execute this statement in a script file, it affects not only the SQL statements in the script  
file but all subsequent SQL statements that are run in the current session. If you set the schema  
in a script file, reset the default schema for the session at the end of the script file.  
For more information about the SET SCHEMA statement, see the Neoview SQL Reference Manual.  
The SHOW SCHEMA command displays the current schema for the session. For example, this  
SHOW SCHEMA command displays SCHEMA PERSNL, where PERSNL is the name of the current  
schema for the session:  
SQL>show schema  
SCHEMA PERSNL  
SQL>  
For more information, see the “SHOW SCHEMA Command” (page 120).  
Limiting the Result Set of a Query  
To set the maximum number of rows to be returned by SELECT statements that are executed in  
the session, enter the SET LIST_COUNT command. For example, this SET LIST_COUNT command  
limits the result set of queries to 20 rows:  
SQL>set list_count 20  
To show the limit that is in effect for the session, enter the SHOW LIST_COUNT command. For  
example, this SHOW LIST_COUNT command shows that the number of rows returned by  
SELECT statements is unlimited:  
SQL>show list_count  
LISTCOUNT 0 [All Rows]  
For more information, see the “SET LIST_COUNT Command” (page 106) and the “SHOW  
LIST_COUNT Command” (page 115).  
Showing Information About SQL Database Objects  
•
•
•
“Showing the Schemas” (page 56)  
“Showing the Tables in a Schema” (page 56)  
“Showing the Dependent Objects of a Table” (page 56)  
Using Neoview Script Interface Commands  
55  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
•
•
“Showing the Views in a Schema” (page 57)  
“Showing the Synonyms in a Schema” (page 57)  
Showing the Schemas  
The SHOW SCHEMAS command displays the schemas that exist in the default catalog:  
SQL>show schemas  
SCHEMA NAMES  
-----------------------------------------------------------------------------  
DBA001  
DBA082  
DBMGR  
DBSCRIPT_SALES  
DEMOSCH1  
DEV060525  
HMGR  
HPNVS_SAMPLE  
ODBC_INVENT  
ODBC_SCHEMA  
PUBLIC_ACCESS_SCHEMA  
ROLEUSER  
DEFINITION_SCHEMA_VERSION_1200 DEMOSCH  
DEMOSCH2  
DS_SCH  
HPNVS  
HPNVS_SAMPLE  
ODBC_PERSNL  
ODBC_TEST  
ROLEDBA  
DEMO_SCH  
D_SALES  
HPNVSSCH  
INVENT  
ODBC_SALES  
PERSNL  
ROLEMGR  
SCH  
SALES  
SERVICES  
T4JDBC_SCHEMA  
TEST1  
USR  
SQL>  
For more information, see the “SHOW SCHEMAS Command” (page 120).  
Showing the Tables in a Schema  
The SHOW TABLES command displays the tables that exist in the current schema. For example,  
this SHOW TABLES command displays all the tables in the current schema, PERSNL:  
SQL>show schema  
SCHEMA PERSNL  
SQL>show tables  
TABLE NAMES  
----------------------------------------------------------------  
DEPT  
EMPLOYEE JOB  
PROJECT  
SQL>  
For more information, see the “SHOW TABLES Command” (page 127).  
Showing the Dependent Objects of a Table  
The SHOW TABLE command displays information about the indexes, materialized views, or  
synonyms of a specified table. For example, this SHOW TABLE command with the INDEXES  
option displays information about each index of the EMPLOYEE table:  
SQL>show table persnl.employee, indexes  
COLUMN NAME  
ORDER INDEX TYPE UNIQUE CARDINALITY POSITION  
------------------------------- ----- ---------- ------ ----------- --------  
Index 1 :EMPLOYEE  
-----------------  
EMPNUM  
ASC Other  
ASC Other  
Yes  
No  
0
0
1
1
Index 2 :XEMPDEPT  
-----------------  
DEPTNUM  
Index 3 :XEMPNAME  
-----------------  
LAST_NAME  
ASC Other  
ASC Other  
No  
No  
0
0
1
2
FIRST_NAME  
56  
Running Commands Interactively in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
SQL>  
For more information, see the “SHOW TABLE Command” (page 125).  
Showing the Views in a Schema  
The SHOW VIEWS command displays the views that exist in the current schema. For example,  
this SHOW VIEWS command displays all the views in the current schema, INVENT:  
SQL>set schema invent;  
--- SQL operation complete.  
SQL>show schema  
SCHEMA INVENT  
SQL>show views  
VIEW NAMES  
----------------------------------------------------------------  
VIEW207 VIEW207N VIEWCS  
VIEWCUST  
SQL>  
For more information, see the “SHOW VIEWS Command” (page 129).  
The SHOW MVS command displays the materialized views that exist in the current schema. For  
example, this SHOW MVS command displays all the materialized views in the current schema,  
PERSNL:  
SQL>set schema persnl;  
--- SQL operation complete.  
SQL>show schema  
SCHEMA PERSNL  
SQL>show mvs;  
MATERIALIZED VIEW NAMES  
-------------------------------------------------------------  
mvemp1 mvemp2 mvemp3 mvjobdesc  
SQL>  
For more information, see the “SHOW MVS Command” (page 117).  
Showing the Synonyms in a Schema  
The SHOW SYNONYMS command displays the synonyms that exist in the current schema. For  
example, this SHOW SYNONYMS command displays all the synonyms in the current schema,  
SALES:  
SQL>set schema sales;  
--- SQL operation complete.  
SQL>show schema  
SCHEMA SALES  
SQL>show synonyms  
SYNONYM NAMES  
-------------------------------------------------------------  
CUST DTLS ORDR PRTS  
SQL>  
Using Neoview Script Interface Commands  
57  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
For more information, see the “SHOW SYNONYMS Command” (page 124).  
Displaying Executed Commands  
To display commands that were recently executed in the Neoview Script session, enter the  
HISTORY command. The HISTORY command associates each command with a number that  
you can use to reexecute or edit the command with the FC command. See “Editing and  
Reexecuting a Command” (page 58).  
For example, this HISTORY command displays a maximum of 100 commands that were entered  
in the session:  
SQL>history  
1>  
2>  
3>  
set idletimeout 0  
set schema persnl;  
select * from project;  
SQL>  
To save the session history in a user-specified file, enter the SAVEHIST command. For example,  
this SAVEHIST command saves the session history in a file named history.txtin the local  
directory where you are running Neoview Script:  
SQL>savehist history.txt  
For more information, see the “HISTORY Command” (page 90) and the “SAVEHIST Command”  
(page 101).  
Editing and Reexecuting a Command  
To edit and reexecute a command in the history buffer of a Neoview Script session, enter the FC  
command. To display the commands in the history buffer, use the HISTORY command. See  
“Displaying Executed Commands” (page 58).  
For example, this FC command and its delete (D) editing command correct a SELECT statement  
that was entered incorrectly:  
SQL>fc  
SQL>selecct * from employee;  
....  
d
SQL>select * from employee;  
....  
Pressing Enter executes the corrected SELECT statement.  
For more information, see the “FC Command” (page 87).  
Clearing the Interface Window  
After entering commands in the Neoview Script interface, you can clear the interface window  
by using the CLEAR command. For example, this CLEAR command clears the interface window  
so that only the prompt appears at the top of the window:  
SQL>clear  
For more information, see the “CLEAR Command” (page 83).  
Obtaining Help  
To display help text for an interface command that is supported in the current operating mode  
of Neoview Script, enter the HELP command. For example, this HELP command displays syntax  
and examples of the FC command:  
SQL>help fc  
For more information, see the “HELP Command” (page 90).  
58  
Running Commands Interactively in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Running SQL Statements  
In the Neoview Script interface, you can run SQL statements interactively. For a list of SQL  
statements that you can run interactively, see Appendix B (page 133).  
This subsection shows examples of:  
•
•
•
“Executing an SQL Statement” (page 59)  
“Repeating an SQL Statement” (page 59)  
“Preparing and Executing SQL Statements” (page 60)  
To run SQL statements from script files in the Neoview Script interface, see Chapter 5 (page 67).  
Executing an SQL Statement  
For example, you can query the EMPLOYEE table and return an employee’s salary by executing  
this SELECT statement in the Neoview Script interface:  
SQL>select salary  
+>from persnl.employee  
+>where jobcode=100;  
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.  
SQL>  
If the SQL statement executes successfully, Neoview Script returns a message indicating that the  
SQL operation was successful, followed by the standard prompt. If a problem occurs during the  
execution of the SQL statement, Neoview Script returns an error message. For information about  
error messages, see the Neoview Messages Manual.  
Repeating an SQL Statement  
To run a previously executed SQL statement, use the /, RUN, or REPEAT command.  
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.  
Running SQL Statements  
59  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
SQL>  
For more information, see the “/ Command” (page 82), “RUN Command” (page 100), or “REPEAT  
Command” (page 98).  
Preparing and Executing SQL Statements  
You can prepare, or compile, an SQL statement by using the PREPARE statement and later  
execute the prepared SQL statement by using the EXECUTE statement.  
•
•
•
•
•
“Preparing an SQL Statement” (page 60)  
“Setting Parameters” (page 61)  
“Displaying the Parameters of the Session” (page 61)  
“Resetting the Parameters” (page 61)  
“Executing a Prepared SQL Statement” (page 62)  
Preparing an SQL Statement  
Use the PREPARE statement to compile an SQL statement for later execution with the EXECUTE  
statement. You can also use the PREPARE statement to check the syntax of an SQL statement  
without executing the statement. For example, this PREPARE statement compiles a SELECT  
statement named empsaland detects a syntax error:  
SQL>prepare empsal from  
+>select salary from employee  
+>where jobcode = 100;  
*** ERROR[4082] Table, view or stored procedure NEO.INVENT.EMPLOYEE does not exist or is inaccessible.  
*** ERROR[8822] The statement was not prepared.  
SQL>  
You can then correct the syntax of the SQL statement and prepare it again:  
SQL>prepare empsal from  
+>select salary from persnl.employee  
+>where jobcode = 100;  
--- SQL command prepared.  
To specify a parameter to be supplied later, either in a SET PARAM statement or in the USING  
clause of 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, this prepared SELECT statement specifies unnamed parameters for salary and job  
code:  
SQL>prepare findemp from  
+>select * from persnl.employee  
+>where salary > ? and jobcode = ?;  
--- SQL command prepared.  
This PREPARE statement prepares another SELECT statement named empcom, which has one  
named parameter, ?dn, for the department number, which appears twice in the statement:  
SQL>prepare empcom from  
+>select first_name, last_name, deptnum  
+>from persnl.employee  
+>where deptnum <> ?dn and salary <=  
+>(select avg(salary)  
+>from persnl.employee  
+>where deptnum = ?dn);  
--- SQL command prepared.  
For the syntax of the PREPARE statement, see the Neoview SQL Reference Manual.  
60  
Running Commands Interactively in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Setting Parameters  
In a Neoview session, you can set a parameter of an SQL statement (either prepared or not) by  
using the SET PARAM command.  
NOTE: The parameter name is case-sensitive. If you specify it in lowercase in the SET PARAM  
command, you must specify it in lowercase in other statements, such as DML statements or  
EXECUTE.  
For example, this SET PARAM command sets a value for the parameter named ?sal, which  
you can apply to one of the unnamed parameters in the prepared findempstatement or to a  
named parameter with an identical name in an SQL statement:  
SQL>set param ?sal 40000.00  
This SELECT statement uses salas a named parameter:  
SQL>select last_name  
+>from persnl.employee  
+>where salary = ?sal;  
This SET PARAM command sets a value for the parameter named dn, which you can apply to  
the named parameter, ?dn, in the prepared empcomstatement or to a named parameter with an  
identical name in an SQL statement:  
SQL>set param ?dn 1500  
For the syntax of the SET PARAM command, see the “SET PARAM Command” (page 107).  
Displaying the Parameters of the Session  
To determine what parameters you have set in the current session, use the SHOW PARAM  
command. For example, this SHOW PARAM command displays the recent SET PARAM settings:  
SQL>show param  
dn 1500  
sal 40000.00  
SQL>  
For the syntax of the SHOW PARAM command, see the “SHOW PARAM Command” (page 118).  
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  
SQL>  
Entering the RESET PARAM command without specifying a parameter name clears all parameter  
settings in the session. For example:  
SQL>reset param  
SQL>show param  
SQL>  
To use the parameters that you had set before, you must reenter them in the session:  
SQL>set param ?dn 1500  
SQL>set param ?sal 80000.00  
SQL>show param  
Running SQL Statements  
61  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
dn 1500  
sal 80000.00  
SQL>  
For the syntax of the RESET PARAM command, see the “RESET PARAM Command” (page 99).  
Executing a Prepared SQL Statement  
To execute a prepared SQL statement, use the EXECUTE statement.  
For example, this EXECUTE statement executes the prepared empsalstatement, which does  
not have any parameters:  
SQL>execute empsal;  
SALARY  
----------  
137000.10  
90000.00  
75000.00  
138000.40  
56000.00  
136000.00  
80000.00  
70000.00  
175500.00  
90000.00  
118000.00  
--- 11 row(s) selected.  
SQL>  
This EXECUTE statement executes the prepared empcomstatement, which has one named  
parameter, ?dn, which was set by SET PARAM for the department number:  
SQL>execute empcom;  
FIRST_NAME  
LAST_NAME  
DEPTNUM  
--------------- -------------------- -------  
ALAN  
DAVID  
PETE  
TERRY  
TERRY  
WELLINGTON  
CHOU  
CONRAD  
CLARK  
FISHER  
FRENCHMAN  
HELMSTED  
JONES  
HUGHES  
LANCASTER  
BONNY  
WINN  
KING  
FOSTER  
JOSEF  
ALBERT  
BARTON  
SEDLEMEYER  
TAYLOR  
CLARK  
HERMAN  
STRICKER  
SCHNABL  
WALKER  
3000  
2000  
3100  
3500  
4000  
9000  
3200  
4000  
4000  
4000  
3200  
4000  
4000  
2000  
2500  
3300  
4000  
3300  
1000  
3300  
3100  
1000  
3000  
3100  
3200  
3000  
JOHN  
MANFRED  
DINAH  
DAVE  
GEORGE  
KARL  
JOHN  
JOHN  
WALTER  
MARLENE  
BILL  
MIRIAM  
GINNY  
MARIA  
HERB  
RICHARD  
XAVIER  
DONALD  
LARRY  
JIM  
GEORGE  
OTTO  
TIM  
62  
Running Commands Interactively in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
TED  
PETER  
MARK  
HEIDI  
ROCKY  
SUE  
MARTIN  
HERBERT  
JESSICA  
MCDONALD  
SMITH  
FOLEY  
WEIGL  
LEWIS  
CRAMER  
SCHAEFFER  
KARAJAN  
CRINER  
2000  
3300  
4000  
3200  
2000  
1000  
3200  
3200  
3500  
--- 35 row(s) selected.  
SQL>  
This EXECUTE statement executes the prepared findempstatement, which has two unnamed  
parameters: ?sal, which was set by SET PARAM for the salary, and a parameter that was not  
set in advance for the job code:  
SQL>execute findemp using ?sal, 100;  
EMPNUM FIRST_NAME  
LAST_NAME  
DEPTNUM JOBCODE SALARY  
------ --------------- -------------- ------- ------- --------  
213 ROBERT  
23 JERRY  
1 ROGER  
29 JANE  
32 THOMAS  
43 PAUL  
WHITE  
HOWARD  
GREEN  
RAYMOND  
RUDLOFF  
WINTER  
MCKAY  
1500  
1000  
9000  
3000  
2000  
3100  
4000  
100 90000.00  
100 137000.10  
100 175500.00  
100 136000.00  
100 138000.40  
100 90000.00  
100 118000.00  
65 RACHEL  
--- 7 row(s) selected.  
SQL>  
For the syntax of the EXECUTE statement, see the Neoview SQL Reference Manual.  
Logging Output  
To log a Neoview Script session, use the SPOOL or LOG command. The SPOOL and LOG  
commands record into a log file the commands that you enter in the Neoview Script interface  
and the output of those commands.  
•
•
•
“Starting the Logging Process” (page 63)  
“Stopping the Logging Process” (page 64)  
“Viewing the Contents of a Log File” (page 64)  
Starting the Logging Process  
To start logging, enter one of these commands:  
SPOOL ON or LOG ON  
SPOOL log-fileor LOG log-file  
•
•
For more information, see the “LOG Command” (page 91) and the “SPOOL Command” (page 130).  
SPOOL ON or LOG ON Command  
The SPOOL ON or LOG ON command logs information about a session in the sqlspool.lst  
file, which Neoview Script stores in the Neoview Script bindirectory:  
•
On Windows:  
hpnvs-installation-directory\nvscript\bin\sqlspool.lst  
Logging Output  
63  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files. For more information, see Table 2-1 (page 34).  
•
On Linux or UNIX:  
hpnvs-installation-directory/nvscript/bin/sqlspool.lst  
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files. For more information, see Table 2-1 (page 34).  
For example, this SPOOL ON command starts logging the session in the sqlspool.lstfile:  
SQL>spool on  
SPOOL log-fileor LOG log-fileCommand  
The SPOOL log-fileand LOG log-filecommands record information about a session in  
a log file that you specify. If you specify a directory for the log file, the directory must exist as  
specified. Otherwise, an error occurs when you try to run the SPOOL or LOG command. If you  
do not specify a directory for the log file, Neoview Script uses the Neoview Script bindirectory.  
For example, this SPOOL log-filecommand starts logging the session in the  
persnl_updates.logfile in the C:\logdirectory:  
SQL>spool C:\log\persnl_updates.log  
Using the CLEAR Option  
The CLEAR option clears the contents of an existing log file before logging new information to  
the file. If you omit CLEAR, Neoview Script appends new information to existing information  
in the log file.  
For example, this SPOOL log-fileCLEAR command clears existing information from the  
specified log file and starts logging the session in the log file:  
SQL>spool C:\log\persnl_updates.log clear  
Logging Concurrent Neoview Script Sessions  
If you plan to run two or more Neoview Script sessions concurrently on the same workstation,  
use the SPOOL log-fileor LOG log-filecommand 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 each session.  
Stopping the Logging Process  
To stop logging, enter one of these commands:  
•
•
SPOOL OFF  
LOG OFF  
For example, this SPOOL OFF command stops logging in a Neoview Script session:  
SQL>spool off  
Viewing the Contents of a Log File  
The log file is an ASCII text file that contains all the lines in the Neoview Script interface from  
the time you start logging to the time you stop logging. The logged lines include prompts, entered  
commands, output from commands, and diagnostic messages.  
For example, this log file contains information from when you started logging to when you  
stopped logging:  
64  
Running Commands Interactively in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                     
For information about error messages that might appear in the log file, see the Neoview Messages  
Manual.  
Logging Output  
65  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
66  
Download from Www.Somanuals.com. All Manuals Search And Download.  
5 Running Scripts in the Neoview Script Interface  
In the Neoview Script interface, you can run script files.  
•
•
•
•
“Creating a Script File” (page 67)  
“Running a Script File” (page 68)  
“Logging Output” (page 69)  
“Running Scripts in Parallel” (page 69)  
Creating a Script File  
A script file that you run in the Neoview Script interface must be an ASCII text file that contains  
only these elements:  
•
•
•
•
“Supported SQL Statements in Script Files” (page 67)  
“Permitted Neoview Script Interface Commands in Script Files” (page 67)  
“Comments” (page 67)  
“Section Headers” (page 67)  
For an example, see “Example of a Script File” (page 68).  
NOTE: You cannot use shell commands in a script file that you run in the Neoview Script  
interface. To create shell scripts that run Neoview Script, see Chapter 6 (page 71).  
Supported SQL Statements in Script Files  
See Appendix B (page 133).  
Permitted Neoview Script Interface Commands in Script Files  
Most Neoview Script interface commands are supported in script files except for a few disallowed  
interface commands. For a list of interface commands, see Appendix A (page 79).  
Disallowed Interface Commands in Script Files  
•
FC  
Starting in Neoview Release 2.0, you can use @ and OBEY commands in script files.  
Comments  
You can include comments anywhere in a script file. SQL also supports comments. Comments  
are useful for documenting the functionality of the script file and for debugging. When debugging,  
use comments to disable specific statements or commands without removing them from the  
script file.  
To denote a comment in a script file, use two hyphens before the comment:  
-- comment  
The end of the line marks the end of the comment.  
Section Headers  
To create sections of commands within a script file, put a section header at the beginning of each  
section:  
?SECTION section-name  
The section-namecannot begin with a number or an underscore. Each section name in a script  
file should be unique because Neoview Script executes the first section that it finds that matches  
Creating a Script File  
67  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
the section name in the @ or OBEY command. For more information, see the“@ Command”  
(page 81) or the “OBEY Command” (page 93).  
Example of a Script File  
This script file creates tables in the inventory schema:  
Running a Script File  
To run a script file in the Neoview Script interface, use the @ or OBEY command. The @ and  
OBEY commands run one script file at a time in the Neoview Script interface. To run a script file  
when launching Neoview Script, see “Running a Script File When Launching Neoview Script”  
(page 48).  
For example, this @ command runs a script file, sch_invent.sql, that creates tables in the  
inventory schema:  
@C:\ddl_scripts\sch_invent.sql  
68  
Running Scripts in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
NOTE: If the script file is outside the directory of the hpnvs.cmdor hpnvs.shfile (by default,  
the Neoview Script bindirectory), you must specify the full path of the script file in the @ or  
OBEY command. For the Neoview Script bindirectory, see Table 2-1 (page 34).  
SQL>@C:\ddl_scripts\sch_invent.sql  
SQL>-- CREATE SCHEMA  
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.supplier (  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
+>  
suppnum  
,suppname  
,street  
NUMERIC (4) UNSIGNED  
NO DEFAULT  
NOT NULL  
CHARACTER (18)  
NO DEFAULT  
NOT NULL  
CHARACTER (22)  
NO DEFAULT  
NOT NULL  
CHARACTER (14)  
NO DEFAULT  
NOT NULL  
CHARACTER (12)  
NO DEFAULT  
NOT NULL  
CHARACTER (10)  
NO DEFAULT  
NOT NULL  
,city  
,state  
,postcode  
,PRIMARY KEY  
(suppnum)  
);  
--- SQL operation complete.  
For more information about the @ and OBEY commands, see the “@ Command” (page 81) and  
the “OBEY Command” (page 93).  
Logging Output  
To log output of a Neoview Script session while running one script file at a time, use the SPOOL  
or LOG command. When you run an OBEY or @ command, Neoview Script displays each  
command in the script file, the output for each command, and diagnostic messages in the Neoview  
Script interface. The SPOOL or LOG command captures this output as it appears in the Neoview  
Script interface and logs it in a log file.  
For more information, see “Logging Output” (page 63).  
Running Scripts in Parallel  
In the Neoview Script interface, the @ and OBEY commands allow you to run only one script  
file at a time. However, the PRUN command allows you to run multiple script files simultaneously.  
Logging Output  
69  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
NOTE: Starting with the 2.1 release, the PRUN command can be run in non-interactive mode.  
The PRUN command now allows options to be specified on the command line, which enables  
PRUN to be run in script and/or obey files.  
The PRUN command is most useful for running sets of data definition language (DDL) statements  
simultaneously, which speeds up the process of creating large databases. Put all dependent or  
related DDL statements in the same script file.  
For more information on running scripts in parallel using the PRUN command, see the “PRUN  
Command” (page 95).  
70  
Running Scripts in the Neoview Script Interface  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
6 Running Neoview Script From Perl or Python  
You can execute an SQL statement in Perl or Python by invoking the Neoview Script Perl or  
Python wrapper script. To use the Perl or Python wrapper script, see:  
•
•
•
•
“Setting the Login Environment Variables” (page 71)  
“Perl and Python Wrapper Scripts” (page 74)  
“Launching Neoview Script From the Perl or Python Command Line” (page 74)  
“Launching Neoview Script From a Perl or Python Program” (page 76)  
These instructions assume that you installed the Neoview Script product. For more information,  
see Chapter 2 (page 23).  
NOTE: Neoview Script provides a beta version of enhanced support for Perl and Python  
programs. This functionality enables multiple SQL statements to run in one database connection  
from a Perl or Python program. For more information, see the README in the Neoview Script  
samplesdirectory.  
Setting the Login Environment Variables  
Before launching Neoview Script from Perl or Python, set these login environment variables:  
Environment Variable  
Description  
HPNVS_SERVER=host-name[:port-number]  
HPNVS_SERVER=IP-address[:port-number]  
Specifies the host name or IP address of the database  
platform to which you want the client to connect. The  
host-nameshould include the domain name of the  
database platform if it is different from the domain of the  
client workstation. If you do not specify a port number,  
Neoview Script uses the default port number, which is  
18650.  
HPNVS_USER=user-name  
Specifies the user name to log in to the database platform.  
HPNVS_PASSWORD=password  
Specifies the password of the user to log in to the database  
platform.  
HPNVS_DATASOURCE=data-source-name  
Specifies the name of a data source.  
If you do not set these environment variables, Neoview Script prompts you to enter the host  
name, user name, and password each time you invoke Neoview Script on the Perl or Python  
command line. Invoking Neoview Script from within a Perl or Python program requires you to  
set these login environment variables.  
To set the login environment variables, see the instructions for the operating system of the client  
workstation:  
•
•
“Setting the Login Environment Variables on Windows” (page 71)  
“Setting the Login Environment Variables on Linux or UNIX” (page 73)  
Setting the Login Environment Variables on Windows  
You can set the login environment variables for the session at command prompts, or you can set  
the login environment variables for the system or user by including them in the System Properties.  
Setting Login Environment Variables on the Command Line  
At each command prompt, enter one of these commands:  
set HPNVS_SERVER=host-name:port-number  
set HPNVS_USER=user-name  
Setting the Login Environment Variables  
71  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
set HPNVS_PASSWORD=password  
set HPNVS_DATASOURCE=data-source-name  
Setting Login Environment Variables in the System Properties  
1. Right-click the My Computer icon on your desktop, and then select Properties:  
2. In the System Properties dialog box, click the Advanced tab.  
3. Click the Environment Variables button:  
72  
Running Neoview Script From Perl or Python  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
4. In the Environment Variables dialog box, click New under System or User variables,  
whichever you prefer.  
5. In the New User Variable dialog box, type the name of the login environment variable for  
the Variable Name and the required value for the Variable Value, and then click OK:  
6. Verify that the environment variable appears under System or User variables.  
7. Repeat Step 4 to Step 6 for each login environment variable.  
8. After adding all four login environment variables, click OK in the Environment Variables  
and System Properties dialog boxes to accept the changes.  
Setting the Login Environment Variables on Linux or UNIX  
You can set the login environment variables for the session at command prompts, or you can set  
the login environment variables for each user by including the variables in the user profile on a  
Linux or UNIX client workstation.  
Setting Login Environment Variables on the Command Line  
At each command prompt in any shell except the C shell, enter one of these commands:  
Setting the Login Environment Variables  
73  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
export HPNVS_SERVER=host-name:port-number  
export HPNVS_USER=user-name  
export HPNVS_PASSWORD=password  
export HPNVS_DATASOURCE=data-source-name  
At each command prompt in the C shell, enter one of these commands:  
setenv HPNVS_SERVER=host-name:port-number  
setenv HPNVS_USER=user-name  
setenv HPNVS_PASSWORD=password  
setenv HPNVS_DATASOURCE=data-source-name  
Setting Login Environment Variables in the User Profile  
To set the login environment variables in the user profile:  
1. Open the user profile (.profileor .bash_profilefor the Bash shell) in the /home  
directory. For example:  
vi .profile  
2. Add these exportcommands (or setenvcommands for the C shell) to the user profile.  
For example:  
export HPNVS_SERVER=host-name:port-number  
export HPNVS_USER=user-name  
export HPNVS_PASSWORD=password  
export HPNVS_DATASOURCE=data-source-name  
3. To activate the changes, either log out and log in again or execute the user profile. For  
example:  
. .profile  
Perl and Python Wrapper Scripts  
The Perl or Python wrapper script enables you to invoke Neoview Script from Perl or Python to  
execute an SQL statement. The Perl wrapper script is hpnvs.pl, and the Python wrapper script  
is hpnvs.py. By default, these wrapper scripts are located in the Neoview Script bindirectory:  
•
On Windows:  
hpnvs-installation-directory\nvscript\bin  
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files. For more information, see Table 2-1 (page 34).  
•
On Linux or UNIX:  
hpnvs-installation-directory/nvscript/bin  
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files. For more information, see Table 2-1 (page 34).  
To use the Perl and Python wrapper scripts, see:  
•
•
“Launching Neoview Script From the Perl or Python Command Line” (page 74)  
“Launching Neoview Script From a Perl or Python Program” (page 76)  
Launching Neoview Script From the Perl or Python Command Line  
You can run an SQL statement by invoking the Neoview Script Perl or Python wrapper script  
on the Perl or Python command line:  
74  
Running Neoview Script From Perl or Python  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
You can pass only one SQL statement at a time on the Perl or Python command line. The SQL  
statement must:  
•
•
•
Be enclosed in double quotes (") without the SQL terminator (;)  
Contain fully qualified database object names (for example, neo.schema-name.obj-name)  
Contain the syntax of one of the supported SQL statements. See Appendix B (page 133).  
See “Perl and Python Commands on Windows” (page 75) and “Perl and Python Commands on  
Linux or UNIX” (page 75).  
Perl and Python Commands on Windows  
In these examples, hpnvs-installation-directoryis the directory where you installed  
the Neoview Script software files. For more information, see Table 2-1 (page 34).  
•
On the Perl command line, enter:  
cd hpnvs-installation-directory\nvscript\bin  
perl hpnvs.pl "sql-statement-string"  
For example:  
>cd install\nvscript\bin  
>perl hpnvs.pl "POPULATE INDEX neo.persnl.xempname  
>ON neo.persnl.employee"  
•
On the Python command line, enter:  
cd hpnvs-installation-directory\nvscript\bin  
python hpnvs.py "sql-statement-string"  
For example:  
>cd install\nvscript\bin  
>python hpnvs.py "SELECT * FROM neo.persnl.employee"  
The command returns this output:  
EMPNUM FIRST_NAME  
LAST_NAME  
DEPTNUM JOBCODE SALARY  
------ --------------- -------------- ------- ------- --------  
1 ROGER  
23 JERRY  
29 JANE  
GREEN  
9000  
1000  
3000  
2000  
100 175500.00  
100 137000.10  
100 136000.00  
100 138000.40  
HOWARD  
RAYMOND  
RUDLOFF  
32 THOMAS  
...  
--- 61 row(s) selected.  
Perl and Python Commands on Linux or UNIX  
In these examples, hpnvs-installation-directoryis the directory where you installed  
the Neoview Script software files. For more information, see Table 2-1 (page 34).  
•
On the Perl command line, enter:  
cd hpnvs-installation-directory/nvscript/bin  
perl hpnvs.pl "sql-statement-string"  
Launching Neoview Script From the Perl or Python Command Line  
75  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
For example:  
>cd /usr/local/hp/nvscript/bin  
>perl hpnvs.pl "POPULATE INDEX neo.persnl.xempname  
>ON neo.persnl.employee"  
•
On the Python command line, enter:  
cd hpnvs-installation-directory/nvscript/bin  
python hpnvs.py "sql-statement-string"  
For example:  
>cd /usr/local/hp/nvscript/bin  
>python hpnvs.py "SELECT * FROM neo.persnl.employee"  
The command returns this output:  
EMPNUM FIRST_NAME  
LAST_NAME  
DEPTNUM JOBCODE SALARY  
------ --------------- -------------- ------- ------- --------  
1 ROGER  
23 JERRY  
29 JANE  
GREEN  
9000  
1000  
3000  
2000  
100 175500.00  
100 137000.10  
100 136000.00  
100 138000.40  
HOWARD  
RAYMOND  
RUDLOFF  
32 THOMAS  
...  
--- 61 row(s) selected.  
Launching Neoview Script From a Perl or Python Program  
You can execute an SQL statement by invoking the Neoview Script Perl or Python wrapper script  
in a Perl or Python program. You can pass only one SQL statement at a time in a perlor python  
command. To execute an SQL statement in a Perl or Python program, follow these instructions:  
•
•
•
“Setting the Login Environment Variables” (page 76)  
“Using SQL Statements in a Perl or Python Program” (page 76)  
“Running the Perl or Python Program” (page 77)  
Setting the Login Environment Variables  
To invoke the Perl or Python wrapper script in a Perl or Python program, you must set the login  
environment variables. For more information, see “Setting the Login Environment Variables”  
(page 71).  
Using SQL Statements in a Perl or Python Program  
In a Perl or Python program, each SQL statement that you invoke with the Perl or Python wrapper  
script must:  
•
•
•
Be enclosed in double quotes (") without the SQL terminator (;)  
Contain fully qualified database object names (for example, neo.schema-name.obj-name)  
Contain the syntax of one of the supported SQL statements. See Appendix B (page 133).  
For examples, see “Example of a Perl Program (example.pl)” (page 76) and “Example of a Python  
Program (example.py)” (page 77).  
Example of a Perl Program (example.pl)  
#########################################################################  
# Example Perl program that maintains a database using hpnvs.pl  
#
#########################################################################  
#----------------------------------------------------------------------------  
$reorgtable="REORG TABLE neo.persnl.employee";  
$updatestats="UPDATE STATISTICS FOR TABLE neo.persnl.employee ".  
"ON EVERY COLUMN";  
$selecttable="SELECT COUNT(*) FROM neo.persnl.employee";  
print "\n";  
76  
Running Neoview Script From Perl or Python  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
#-----Reorganize the table --------------------------------------------------  
$status=`perl /usr/local/hp/nvscript/bin/hpnvs.pl "$reorgtable"`;  
print "Reorg status :".$status;  
print "\n";  
#----------Update the statistics of the table--------------------------------  
$status=`perl /usr/local/hp/nvscript/bin/hpnvs.pl "$updatestats"`;  
print "Update statistics status :".$status;  
print "\n";  
#--------------Fetch results-------------------------------------------------  
@resultrows=`perl /usr/local/hp/nvscript/bin/hpnvs.pl "$selecttable"`;  
#-------------Display the results--------------------------------------------  
foreach $rowvalue (@resultrows)  
{
print $rowvalue;  
}
Example of a Python Program (example.py)  
import os  
import sys  
import string  
if __name__ == '__main__':  
#Define SQL statements  
reorgtable="REORG TABLE neo.persnl.employee";  
updatestats="UPDATE STATISTICS FOR TABLE neo.persnl.employee "  
updatestats=updatestats + "ON EVERY COLUMN";  
selecttable="SELECT COUNT(*) FROM neo.persnl.employee";  
#Contruct a list of SQL statements to be executed  
stmnt = [reorgtable,updatestats,selecttable]  
print "\n";  
for stmntstr in stmnt:  
cin, cout ,cerr = os.popen3('python /usr/local/hp/nvscript/bin/hpnvs.py "'+stmntstr+'"')  
while 1:  
text = cout.read()  
if text:  
print text  
else:  
break  
while 1:  
text = cerr.read()  
if text:  
print text  
else:  
break  
cin.close()  
cout.close()  
Running the Perl or Python Program  
Before running the Perl or Python program, make sure that you included the absolute path of  
the Perl or Python wrapper script (hpnvs.plor hpnvs.py) in the program file:  
•
On Windows:  
hpnvs-installation-directory\nvscript\bin\hpnvs.pl  
or  
hpnvs-installation-directory\nvscript\bin\hpnvs.py  
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files. For more information, see Table 2-1 (page 34).  
•
On Linux or UNIX:  
hpnvs-installation-directory/nvscript/bin/hpnvs.pl  
or  
hpnvs-installation-directory/nvscript/bin/hpnvs.py  
Launching Neoview Script From a Perl or Python Program  
77  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
hpnvs-installation-directoryis the directory where you installed the Neoview  
Script software files. For more information, see Table 2-1 (page 34).  
To run a Perl program, enter the perlcommand at a command prompt, as this example shows:  
>perl example.pl  
To run a Python program, enter the pythoncommand at a command prompt, as this example  
shows:  
>python example.py  
78  
Running Neoview Script From Perl or Python  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
A Neoview Script Interface Commands  
Neoview Script supports these commands in the Neoview Script interface or in script files that  
you run in the Neoview Script interface. For a list of Neoview Script interface commands that  
are available only to HP support, see the Neoview Database Support Guide.  
Command  
Description  
Syntax  
@
Runs the SQL statements and  
Neoview Script interface commands  
contained in a specified script file.  
See the “@ Command” (page 81).  
/
Runs the previously executed SQL  
statement.  
See the “/ Command” (page 82).  
CLEAR  
Clears the command console so that See the “CLEAR Command” (page 83).  
only the prompt appears at the top of  
the screen.  
CONNECT  
Creates a new connection to the  
See the “CONNECT Command”  
Neoview platform from a current or (page 83).  
existing Neoview Script session.  
DISCONNECT  
Terminates the connection to the  
Neoview platform.  
See the “DISCONNECT Command”  
(page 84).  
ENV  
EXIT  
FC  
Displays attributes of the current  
Neoview Script session.  
See the “ENV Command” (page 85).  
Disconnects from and exits the  
Neoview Script interface.  
See the “EXIT Command” (page 86).  
See the “FC Command” (page 87).  
Edits and reexecutes a previous  
command. This command is restricted  
to the Neoview Script interface and is  
disallowed in script files.  
HELP  
Displays help text for the interface  
commands that are supported in the  
current operating mode.  
See the “HELP Command” (page 90).  
HISTORY  
LOG  
Displays recently executed  
commands.  
See the “HISTORY Command”  
(page 90).  
Logs commands and output from the See the “LOG Command” (page 91).  
Neoview Script interface to a log file.  
MODE  
Determines the operating mode of the See the “MODE Command” (page 92).  
current session to be either SQL for  
database commands or CS for  
connectivity service commands.  
OBEY  
Runs the SQL statements and  
Neoview Script interface commands  
contained in a specified script file.  
See the “OBEY Command” (page 93).  
PRUN  
QUIT  
Runs script files in parallel.  
See the “PRUN Command” (page 95).  
See the “QUIT Command” (page 97).  
Disconnects from and exits the  
Neoview Script interface.  
RECONNECT  
Creates a new connection to the  
Neoview platform using the login  
credentials of the last successful  
connection.  
See the “RECONNECT Command”.  
REPEAT  
Reexecutes a command.  
See the “REPEAT Command”  
(page 98).  
RESET PARAM  
Clears all parameter values or a  
specified parameter value in the  
current session.  
See the “RESET PARAM Command”  
(page 99).  
79  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Command  
Description  
Syntax  
RUN  
Runs the previously executed SQL  
statement.  
See the “RUN Command” (page 100).  
SAVEHIST  
SESSION  
Saves the session history in a  
user-specified file.  
See the “SAVEHIST Command”  
(page 101).  
Displays attributes of the current  
Neoview Script session.  
See the “SHOW SESSION Command”  
(page 122).  
SET COLSEP  
Sets the column separator and allows See the “SET COLSEP Command”  
you to control the formatting of the (page 101).  
result displayed for SQL queries.  
SET HISTOPT  
Sets the history option and controls See the “SET HISTOPT Command”  
how commands are added to the  
history buffer.  
(page 102).  
SET IDLETIMEOUT  
SET LIST_COUNT  
Sets the idle timeout value for the  
current session.  
See the “SET IDLETIMEOUT  
Command” (page 103).  
Sets the maximum number of rows to See the “SET LIST_COUNT Command”  
be returned by SELECT statements (page 106).  
that are executed after this command.  
SET MARKUP  
Sets the markup format and controls See the“SET MARKUP Command”  
how results are displayed by Neoview (page 104).  
Script.  
SET PARAM  
SET PROMPT  
Sets a parameter value in the current See the “SET PARAM Command”  
session.  
(page 107).  
Sets the prompt of the current session See the “SET PROMPT Command”  
to a specified string or to a session  
variable.  
(page 109).  
SET SQLPROMPT  
SET SQLTERMINATOR  
SET TIME  
Sets the SQL prompt of the current See the “SET SQLPROMPT Command”  
session to a specified string. The  
default is SQL.  
(page 110).  
Sets the SQL statement terminator of See the “SET SQLTERMINATOR  
the current session to a specified  
string. The default is a semicolon (;).  
Command” (page 112).  
Causes the local time of the client  
See the “SET TIME Command”  
workstation to be displayed as part of (page 112).  
the interface prompt.  
SET TIMING  
Causes the elapsed time to be  
displayed after each SQL statement (page 113).  
executes.  
See the“SET TIMING Command”  
SHOW COLSEP  
SHOW HISTOPT  
Displays the value of the column  
separator for the current Neoview  
Script session.  
See the “SHOW COLSEP Command”.  
Displays the value that has been set See the “SHOW HISTOPT Command”  
for the history option of the current (page 114).  
setting.  
SHOW IDLETIMEOUT  
SHOW LIST_COUNT  
Displays the idle timeout value of the See the “SHOW IDLETIMEOUT  
current session.  
Command” (page 114).  
Displays the maximum number of  
rows to be returned by SELECT  
statements in the current session.  
See the “SHOW LIST_COUNT  
Command” (page 115).  
SHOW MARKUP  
SHOW MODE  
Displays the value that has been set See the “SHOW MARKUP Command”  
for the markup option for the current (page 115).  
Neoview Script session.  
Displays the operating mode of the See the “SHOW MODE Command”  
current session.  
(page 116).  
80  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Command  
Description  
Syntax  
SHOW MVGROUPS  
Displays all or a set of the  
materialized view groups in the  
current schema of the Neoview Script  
session.  
See the “SHOW MVGROUPS  
Command” (page 116).  
SHOW MVS  
Displays all or a set of the  
materialized views in the current  
schema of the Neoview Script session.  
See the “SHOW MVS Command”  
(page 117).  
SHOW PARAM  
Displays the parameters that are set See the “SHOW PARAM Command”  
in the current session. (page 118).  
SHOW PREPARED  
SHOW SCHEMA  
SHOW SCHEMAS  
Displays the prepared statements in See the “SHOW PREPARED  
the current Neoview Script session. Command” (page 119).  
Displays the current schema of the  
Neoview Script session.  
See the “SHOW SCHEMA Command”  
(page 120).  
Displays all or a set of the schemas  
See the “SHOW SCHEMAS Command”  
that exist in the default catalog of the (page 120).  
current session.  
SHOW SESSION  
Displays attributes of the current  
Neoview Script session.  
See the “SHOW SESSION Command”  
(page 122).  
SHOW SQLPROMPT  
SHOW SQLTERMINATOR  
SHOW SYNONYMS  
Displays the value of the SQL prompt See the “SHOW SQLPROMPT  
for the current session.  
Command” (page 123).  
Displays the SQL statement  
terminator of the current session.  
See the “SHOW SQLTERMINATOR  
Command” (page 124).  
Displays all or a set of the synonyms See the “SHOW SYNONYMS  
in the current schema of the Neoview Command” (page 124).  
Script session.  
SHOW TABLE  
SHOW TABLES  
Displays information about the  
dependent objects (indexes,  
materialized views, or synonyms) of  
a specified table.  
See the “SHOW TABLE Command”  
(page 125).  
Displays all or a set of the tables that See the “SHOW TABLES Command”  
exist in the current schema of the  
Neoview Script session.  
(page 127).  
SHOW TIME  
Displays the setting for the local time See the “SHOW TIME Command”  
in the SQL prompt. (page 128).  
SHOW TIMING  
SHOW VIEWS  
Displays the setting for the elapsed See the “SHOW TIMING Command”  
time. (page 129).  
Displays all or a set of the views that See the “SHOW VIEWS Command”  
exist in the current schema of the  
Neoview Script session.  
(page 129).  
SPOOL  
Logs commands and output from the See the “SPOOL Command” (page 130).  
Neoview Script interface to a log file.  
VERSION  
Displays the build versions of  
See the “VERSION Command”  
Neoview Script and the JDBC Type 4 (page 131).  
Driver.  
@ Command  
The @ command executes the SQL statements and Neoview Script interface commands contained  
in a specified script file.  
Syntax  
@script-file [ (section-name )]  
@ Command  
81  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
script-file  
is the name of an ASCII text file that contains SQL statements, Neoview  
Script interface commands, and comments. If the script file exists outside  
the local directory where you launch Neoview Script (by default, the  
Neoview Script bindirectory), specify the full directory path of the script  
file.  
is the name of a section within the script-fileto execute. If you specify  
section-name, the @ command executes the commands between the  
header line for the specified section and the header line for the next section  
(or the end of the script file). If you omit section-name, the @ command  
executes the entire script file. For more information, see “Section Headers”  
(page 67).  
(section-name)  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
•
Space is disallowed between the @ sign and the first character of the file name.  
You can execute this command in a script file.  
You can specify only one script file at a time using the @ command. To run multiple script  
files in parallel, see “Running Scripts in Parallel” (page 69).  
Examples  
•
This @ command runs the script file from the local directory (the same directory where you  
are running Neoview Script):  
SQL>@ddl.sql  
•
•
This @ command runs the script file in the specified directory on a Windows workstation:  
SQL>@c:\my_files\ddl.sql  
This @ command runs the script file in the specified directory on a Linux or UNIX  
workstation:  
SQL>@./my_files/ddl.sql  
/ Command  
The / command executes the previously executed SQL statement. This command does not repeat  
a Neoview Script interface command.  
Syntax  
/
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Example  
This / command executes the previously executed SELECT statement:  
SQL>select count(*) from persnl.employee;  
(EXPR)  
--------------------  
62  
--- 1 row(s) selected.  
82  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
SQL>/  
(EXPR)  
--------------------  
62  
--- 1 row(s) selected.  
SQL>  
CLEAR Command  
The CLEAR command clears the interface window so that only the prompt appears at the top  
of the window. CLEAR does not clear the log file or reset the settings of the session.  
Syntax  
CLEAR  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Example  
This CLEAR command clears the interface window:  
SQL>clear  
After the CLEAR command executes, the interface window appears with only the prompt  
showing:  
SQL>  
CONNECT Command  
The CONNECT command creates a new connection to the Neoview platform from the current  
or existing Neoview Script session.  
Syntax  
CONNECT [username [/password][@hostname][,dsnName]]  
username specifies the user name to log in to the database platform. If the user name is not  
specified, Neoview Script prompts for the user name.  
password specifies the password of the user to log in to the database platform. If the password  
is not specified, Neoview Script prompts for the password.  
hostname specifies the host name or IP address of the database platform to which you want  
the client to connect. If the hostname is not specified, the value is automatically  
used from the current Neoview Script session. If Neoview Script was invoked with  
the -noconnectlaunch parameter, you are prompted for a hostnamevalue.  
dsnName  
specifies the name of a data source. If the dsnNameis not specified, the value is  
automatically used from the current Neoview Script session. If Neoview Script  
was invoked with the -noconnectlaunch parameter, you are prompted for a  
dsnNamevalue.  
Considerations  
In the Neoview Script interface, you must enter the command on one line.  
CLEAR Command  
83  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
If Neoview Script was invoked with the -noconnectlaunch parameter, Neoview Script prompts  
you for the values.  
Currently, none of the commands work with the -noconnectoption.  
Examples  
These commands create a new connection to the Neoview platform from the current or existing  
Neoview Script interface:  
SQL>connect  
User Name: super.services  
Password:  
Connected to DataSource TDM_Default_DataSource.  
SQL>connect super.services/password  
Connected to DataSource TDM_Default_DataSource.  
SQL>connect super.services/password@host0101  
Connected to DataSource TDM_Default_DataSource.  
SQL>connect super.services,NVSCRIPT  
Password:  
Connected to DataSource NVSCRIPT.  
DISCONNECT Command  
The DISCONNECT command terminates the connection from the Neoview platform, not from  
the Neoview Script interface.  
Syntax  
DISCONNECT [IF ERRORCODE{=|<|>|<=|>=|<>}error-code]  
error-code  
is an integer that represents an error condition of the previously executed  
command. If the previously executed command returns this error code, the  
Neoview Script interface disconnects and exits.  
Commands that execute successfully in the Neoview Script interface have an  
error code of zero (0). Interface commands that do not perform SQL operations  
and that fail to execute have an error code of -1. A failed SQL operation has a  
specific SQL error code associated with the error condition. For more information  
about SQL error messages, see the Neoview Messages Manual.  
Considerations  
In the Neoview Script interface, you must enter the command on one line.  
Examples  
This command terminates the connection to the Neoview platform. You can connect to the  
Neoview platform by using the CONNECT and RECONNECT commands:  
SQL>disconnect  
Session Disconnected. Please connect to the database by using connect/reconnect command.  
84  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
ENV Command  
ENV displays attributes of the current Neoview Script session. You can also use the SESSION  
and SHOW SESSION commands to perform the same function.  
Syntax  
ENV  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
ENV displays these attributes:  
•
COLSEP  
Current column separator, which is used to control how query results are displayed.  
For more information, see “SET COLSEP Command” (page 101).  
DATASOURCE  
HISTOPT  
Name of the data source that you entered when logging in to the database platform.  
For more information, see “Logging In to the Database Platform” (page 45).  
Current history options, which controls how the commands are added to the  
history buffer. For more information, see “SET HISTOPT Command” (page 102).  
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 Idle Timeout Value for the Session”  
(page 53) and “SET IDLETIMEOUT Command” (page 103).  
LIST COUNT  
LOG  
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 106).  
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 63)  
and “LOG Command” (page 91) or “SPOOL Command” (page 130).  
LOOK AND FEEL  
Current look and feel of the Neoview Script interface. This property affects the  
formatting of status messages. For more information, see “Setting the Look and  
Feel of the Neoview Script Interface” (page 35).  
MARKUP  
MODE  
Current markup option selected for the session. The default option is RAW. For  
more information, see “SET MARKUP Command” (page 104).  
Current operating mode of the session. The default mode is SQL. For more  
information, see “MODE Command” (page 92).  
PROMPT  
Current prompt for the session. In SQL mode, the default is SQL>. In CS mode,  
the default is CS#. For more information, see “Customizing the Standard Prompt”  
(page 53) and “SET PROMPT Command” (page 109).  
SCHEMA  
SERVER  
Current schema. The default is USR. For more information, see “Setting and  
Showing the Current Schema” (page 55).  
Host name and port number that you entered when logging in to the database  
platform. For more information, see “Logging In to the Database Platform”  
(page 45).  
SQLTERMINATOR  
TIME  
Current SQL statement terminator. The default is a semicolon (;). For more  
information, see “Setting and Showing the SQL Terminator” (page 54) and “SHOW  
SQLTERMINATOR Command” (page 124).  
Current setting (on or off) of the local time as part of the prompt. When this  
command is set to on, military time is displayed. By default, the local time is off.  
For more information, see “Customizing the Standard Prompt” (page 53) and  
“SET TIME Command” (page 112).  
ENV Command  
85  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
TIMING  
USER  
Current setting (on or off) of the elapsed time. By default, the elapsed time is off.  
For more information, see “Displaying the Elapsed Time” (page 54) and “SET  
TIMING Command” (page 113).  
User name that you entered when logging in to the database platform. For more  
information, see “Logging In to the Database Platform” (page 45).  
Examples  
•
This ENV command displays the attributes of the current session:  
SQL>env  
COLSEP  
" "  
DATASOURCE  
HISTOPT  
TDM_Default_DataSource  
ALL  
IDLETIMEOUT  
LIST COUNT  
LOG  
30 min(s)  
0 [All Rows]  
OFF  
LOOK AND FEEL BTEQ  
MARKUP  
MODE  
RAW  
SQL  
PROMPT  
SCHEMA  
SERVER  
SQL>  
USR  
neo0101.acme.com:18650  
SQLTERMINATOR ;  
TIME  
OFF  
TIMING  
USER  
OFF  
role.dbaSQL>  
•
This ENV command shows the effect of setting various session attributes:  
4:16:43 PM >env  
COLSEP  
" "  
DATASOURCE  
HISTOPT  
TDM_Default_DataSource  
ALL  
IDLETIMEOUT  
LIST COUNT  
LOG  
0 min(s) [Never Expires]  
0 [All Rows]  
c:\mydir\examples.log  
LOOK AND FEEL BTEQ  
MARKUP  
MODE  
RAW  
SQL  
PROMPT  
SCHEMA  
SERVER  
4:16:49 PM >  
PERSNL  
sys0101.mylab.mycorp.net:18650  
SQLTERMINATOR .  
TIME  
ON  
TIMING  
USER  
ON  
dba1  
4:16:49 PM >  
EXIT Command  
The EXIT command disconnects from and exits the Neoview Script interface.  
Syntax  
EXIT [IF ERRORCODE{=|<|>|<=|>=|<>}error-code]  
86  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
error-code  
is an integer that represents an error condition of the previously executed  
command. If the previously executed command returns this error code, the  
Neoview Script interface disconnects and exits.  
Commands that execute successfully in the Neoview Script interface have an  
error code of zero (0). Interface commands that do not perform SQL operations  
and that fail to execute have an error code of -1. A failed SQL operation has a  
specific SQL error code associated with the error condition. For more information  
about SQL error messages, see the Neoview Messages Manual.  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Examples  
•
This command disconnects from and exits the Neoview Script interface, which disappears  
from the screen:  
SQL>exit  
•
In a script file, the conditional exit command causes the script file to quit running and  
disconnect from and exit the Neoview Script interface when the previously run command  
returns error code 4082:  
log c:\errorCode.log  
select * from employee;  
exit if errorcode=4082  
log off  
These results are logged when error code 4082 occurs:  
SQL>select * from employee;  
*** ERROR[4082] Table, view or stored procedure NEO.USR.EMPLOYEE  
does not exist or is inaccessible.  
*** ERROR[8822] The statement was not prepared.  
SQL>exit if errorcode=4082  
FC Command  
The FC command allows you to edit and reissue a command in the history buffer of a Neoview  
Script session. You can display the commands in the history buffer by using the HISTORY  
command. For information about the history buffer, see the “HISTORY Command” (page 90).  
Syntax  
FC [text | [-]number]  
text  
is the beginning text of a command in the history buffer. Case is not significant  
in matching the text to a command.  
is either a positive integer that is the ordinal number of a command in the history  
buffer or a negative integer that indicates the position of a command relative to  
the most recent command.  
[-]number  
Without text or number, FC retrieves the most recent command.  
FC Command  
87  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Considerations  
•
•
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
You cannot execute this command in a script file. You can execute this command only at a  
command prompt.  
As each line of the command is displayed, you can modify the line by entering these editing  
commands (in uppercase or lowercase letters) on the line below the displayed command  
line:  
D
Deletes the character immediately above the letter D.  
Repeat to delete more characters.  
Icharacters  
Rcharacters  
Inserts characters in front of the character immediately  
above the letter I.  
Replaces existing characters one-for-one with characters,  
beginning with the character immediately above the  
letter R.  
characters  
Replaces existing characters one-for-one with characters,  
beginning with the first character immediately above  
characters. charactersmust begin with a nonblank  
character.  
To specify more than one editing command on a line, separate the editing commands with  
a double slash (//). The end of a line terminates an editing command or a set of editing  
commands.  
After you edit a line of the command, Neoview Script displays the line again and allows  
you to edit it again. Press Enter without specifying editing commands to stop editing the  
line. If that line is the last line of the command, pressing Enter executes the command.  
To terminate a command without saving changes to the command, use the double slash (//),  
and then press Enter.  
Examples  
•
Reexecute the most recent command that begins with SH:  
SQL>fc sh  
SQL>show schema  
....  
Pressing Enter executes the SHOW SCHEMA command and displays the current schema,  
PERSNL:  
SQL>fc sh  
SQL>show schema  
....  
SCHEMA PERSNL  
SQL>  
•
Correct an SQL statement that you entered incorrectly by using the delete (D) editing  
command:  
SQL>selecct * from persnl.employee;  
*** ERROR[15001] A syntax error occurred at or before:  
selecct * from persnl.employee;  
^
*** ERROR[8822] The statement was not prepared.  
SQL>fc  
SQL>selecct * from persnl.employee;  
....  
d
88  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
SQL>select * from persnl.employee;  
....  
Pressing Enter executes the corrected SELECT statement.  
•
Correct an SQL statement that you entered incorrectly by using more than one editing  
command:  
SQL>selt * fromm persnl.employee;  
*** ERROR[15001] A syntax error occurred at or before:  
selt * fromm persnl.employee;  
^
*** ERROR[8822] The statement was not prepared.  
SQL>fc  
SQL>selt * fromm persnl.employee;  
.... iec// d  
SQL>select * from persnl.employee;  
....  
Pressing Enter executes the corrected SELECT statement.  
•
Modify a previously executed statement by replacing a value in the WHERE clause with  
another value:  
SQL>select first_name, last_name  
+>from persnl.employee  
+>where jobcode=111;  
--- 0 row(s) selected.  
SQL>fc  
SQL>select first_name, last_name  
....  
SQL>from persnl.employee  
....  
SQL>where jobcode=111;  
450  
....  
SQL>where jobcode=450;  
....  
Pressing Enter lists the first and last names of all of the employees whose job code is 450.  
•
Modify a previously executed statement by replacing a column name in the select list with  
another column name:  
SQL>select first_name, last_name  
+>from persnl.employee  
+>where jobcode=450;  
FIRST_NAME  
LAST_NAME  
--------------- --------------------  
MANFRED  
WALTER  
JOHN  
CONRAD  
LANCASTER  
JONES  
KARL  
THOMAS  
HELMSTED  
SPINNER  
--- 5 row(s) selected.  
SQL>fc  
SQL>select first_name, last_name  
....  
SQL>select  
....  
R empnum,  
empnum, last_name  
SQL>from persnl.employee  
....  
FC Command  
89  
Download from Www.Somanuals.com. All Manuals Search And Download.  
SQL>where jobcode=450;  
....  
Pressing Enter lists the employee number and last names of all employees whose job code  
is 450:  
EMPNUM LAST_NAME  
------ --------------------  
180 CONRAD  
215 LANCASTER  
216 JONES  
225 HELMSTED  
232 SPINNER  
--- 5 row(s) selected.  
SQL>  
HELP Command  
The HELP command displays help text for the interface commands that are supported in the  
current operating mode.  
Syntax  
HELP [command-name]  
command-name  
is the name of an interface command that is supported in the current  
operating mode. If you do not specify a command, Neoview Script returns  
a list of all commands that are supported in the current mode. If you specify  
SET, Neoview Script returns a list of all SET commands that are supported  
in the current mode. If you specify SHOW, Neoview Script returns a list of  
all SHOW commands that are supported in the current mode.  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Examples  
•
This HELP command lists all the commands that are supported in SQL mode:  
SQL>help  
•
•
•
This HELP command lists all the SET commands that are supported in SQL mode:  
SQL>help set  
This HELP command shows help text for SET IDLETIMEOUT:  
SQL>help set idletimeout  
This HELP command lists all the SHOW commands that are supported in CS mode:  
CS#help show  
HISTORY Command  
The HISTORY command displays recently executed commands, identifying each command by  
a number that you can use to reexecute or edit the command.  
90  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Syntax  
HISTORY [number]  
number is the number of commands to display. The default number is 10. The maximum  
number is 100.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can use the FC command to edit and reexecute a command in the history buffer, or use  
the REPEAT command to reexecute a command without modifying it. See the “FC Command”  
(page 87) or the “REPEAT Command” (page 98).  
Example  
Display the three most recent commands and use FC to redisplay one:  
SQL>history 3  
14>  
15>  
16>  
set schema sales;  
show tables  
show views  
SQL>fc 14  
SQL>set schema sales  
....  
Now you can use the edit capabilities of FC to modify and execute a different SET SCHEMA  
statement.  
LOG Command  
The LOG command logs the entered commands and their output from the Neoview Script  
interface to a log file.  
Syntax  
LOG { ON [CLEAR] | log-file [CLEAR] | OFF }  
ON  
starts the logging process and records information in the sqlspool.lst  
file in the Neoview Script bindirectory.  
ON CLEAR  
log-file  
instructs Neoview Script to clear the contents of the sqlspool.lstfile  
before logging new information to the file.  
is the name of a log file into which Neoview Script records the entered  
commands and their output. If you want the log file to exist outside the  
local directory where you launch Neoview Script (by default, the Neoview  
Script bindirectory), specify the full directory path of the log file. The  
log file does not need to exist, but the specified directory must exist before  
you execute the LOG command.  
log-fileCLEAR  
instructs Neoview Script to clear the contents of the specified log-file  
before logging new information to the file.  
OFF  
stops the logging process.  
LOG Command  
91  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
Use a unique name for each log file to avoid writing information from different Neoview  
Script sessions into the same log file.  
Examples  
•
This command starts the logging process and records information to the sqlspool.lst  
file in the Neoview Script bindirectory:  
SQL>log on  
•
This command starts the logging process and appends new information to an existing log  
file, persnl_updates.log, in the local directory (the same directory where you are running  
Neoview Script):  
SQL>log persnl_updates.log  
•
•
•
•
This command starts the logging process and appends new information to a log file,  
sales_updates.log, in the specified directory on a Windows workstation:  
SQL>log c:\log_files\sales_updates.log  
This command starts the logging process and appends new information to a log file,  
sales_updates.log, in the specified directory on a Linux or UNIX workstation:  
SQL>log ./log_files/sales_updates.log  
This command starts the logging process and clears existing information from the log file  
before logging new information to the file:  
SQL>log persnl_ddl.log clear  
This command stops the logging process:  
SQL>log off  
For more information, see “Logging Output” (page 63).  
MODE Command  
The MODE command determines the operating mode of the current session to be either SQL for  
database commands or CS for connectivity service commands. The default mode for Neoview  
Script sessions is SQL.  
Syntax  
MODE { SQL | CS }  
SQL specifies SQL mode and supports the use of all SQL statements and Neoview Script  
interface commands. The connectivity service commands are disallowed in SQL mode.  
CS  
specifies connectivity service (CS) mode and supports the use of connectivity service  
commands. For more information, see Appendix C (page 135).  
CS mode also supports these Neoview Script interface commands:  
•
•
•
•
•
•
•
•
@ and OBEY  
CLEAR  
CONNECT, RECONNECT, DISCONNECT, EXIT, and QUIT  
ENV, SESSION, and SHOW SESSION  
FC and REPEAT  
HELP  
HISTORY and SAVEHIST  
LOG and SPOOL  
92  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
•
•
•
•
•
•
•
•
•
MODE and SHOW MODE  
SET COLSEP and SHOW COLSEP  
SET HISTOPT and SHOW HISTOPT  
SET IDLETIMEOUT and SHOW IDLETIMEOUT  
SET MARKUP and SHOW MARKUP  
SET PROMPT  
SET TIME and SHOW TIME  
SET TIMING and SHOW TIMING  
VERSION  
All other interface commands are disallowed in CS mode.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You cannot execute the MODE command or any connectivity service commands in PRUN  
script files. However, you can execute the MODE command in OBEY or @ script files.  
Examples  
•
This command changes the Neoview Script session to CS mode operation:  
SQL>mode cs  
CS#  
For more information, see Appendix C (page 135).  
•
This command returns the Neoview Script session to SQL mode operation:  
CS#mode sql  
SQL>  
OBEY Command  
The OBEY command executes the SQL statements and Neoview Script interface commands  
contained in a specified script file.  
Syntax  
OBEY script-file [ (section-name) ]  
script-file  
is the name of an ASCII text file that contains SQL statements, Neoview  
Script interface commands, and comments. If the script file exists outside  
the local directory where you launch Neoview Script (by default, the  
Neoview Script bindirectory), specify the full directory path of the script  
file.  
(section-name)  
is the name of a section within the script-fileto execute. If you specify  
section-name, the OBEY command executes the commands between  
the header line for the specified section and the header line for the next  
section (or the end of the script file). If you omit section-name, the  
OBEY command executes the entire script file. For more information, see  
“Section Headers” (page 67).  
OBEY Command  
93  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
•
Put a space between OBEY and the first character of the file name.  
You can execute this command in a script file.  
You can specify only one script file at a time using the OBEY command. To run multiple  
script files in parallel, see “Running Scripts in Parallel” (page 69).  
Examples  
•
This OBEY command runs the script file from the local directory (the same directory where  
you are running Neoview Script):  
SQL>obey ddl.sql  
•
•
This OBEY command runs the script file in the specified directory on Windows.  
SQL>obey c:\my_files\ddl.sql  
This OBEY command runs the script file in the specified directory on a Linux or UNIX  
workstation:  
SQL>obey ./my_files/ddl.sql  
•
This sample file contains sections to be used in conjunction with the OBEY command:  
?section droptable  
DROP TABLE COURSE  
?section create  
CREATE TABLE COURSE  
(
CNO  
VARCHAR(3)  
NOT NULL,  
NOT NULL,  
NOT NULL,  
CNAME VARCHAR(22)  
CDESCP VARCHAR(25)  
CRED  
INT,  
CLABFEE NUMERIC(5,2),  
CDEPT VARCHAR(4)  
primary key (cno)  
) ;  
NOT NULL,  
?section insert  
INSERT INTO COURSE VALUES  
('C11', 'INTRO TO CS','FOR ROOKIES',3, 100, 'CIS');  
INSERT INTO COURSE VALUES  
('C22', 'DATA STRUCTURES','VERY USEFUL',3, 50, 'CIS');  
INSERT INTO COURSE VALUES  
('C33', 'DISCRETE MATHEMATICS',  
'ABSOLUTELY NECESSARY',3, 0,'CIS');  
?section select  
SELECT * FROM course;  
?section delete  
purgedata course;  
To run only the commands in section create, execute the following :  
SQL>obey C:\Scripts\course.sql (create)  
SQL>?section create  
SQL>CREATE TABLE COURSE  
+>(  
94  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
+> CNO  
+> CNAME VARCHAR(22)  
+> CDESCP VARCHAR(25)  
VARCHAR(3)  
NOT NULL,  
NOT NULL,  
NOT NULL,  
+> CRED  
INT,  
+> CLABFEE NUMERIC(5,2),  
+> CDEPT VARCHAR(4)  
+> primary key (cno)  
+>) ;  
NOT NULL,  
--- SQL Operation complete.  
To run only the commands in the insert section, execute the following :  
SQL>obey C:\Scripts\course.sql (insert)  
SQL>?section insert  
SQL>INSERT INTO COURSE VALUES  
+> ('C11', 'INTRO TO CS','FOR ROOKIES',3, 100, 'CIS');  
--- 1 row(s) inserted.  
SQL>INSERT INTO COURSE VALUES  
+>  
('C22', 'DATA STRUCTURES','VERY USEFUL',3, 50, 'CIS');  
--- 1 row(s) inserted.  
SQL>INSERT INTO COURSE VALUES  
+>  
('C33', 'DISCRETE MATHEMATICS',  
'ABSOLUTELY NECESSARY',3, 0, 'CIS');  
--- 1 row(s) inserted.  
PRUN Command  
The PRUN command runs script files in parallel.  
Syntax  
PRUN [-d | -defaults] | PRUN [-sd | -scriptsdir directoryName]  
[-e | -extension extension]  
[-ld | -logsdir logDirectory]  
[-o | -overwrite {y | n}]  
[-c | -connections num]  
scriptsdir  
In this directory, PRUN processes every file with the specified extension. If  
you do not specify a directory or if you specify an invalid directory, an error  
message occurs and you are prompted to reenter the directory. Note: Verify  
that this directory contains valid script files.  
extension  
logsdir  
The default is .sql.  
In this directory, PRUN creates a log file for each script file by appending the  
.logextension to the name of the script file. If you do not specify a log file  
directory, PRUN places the log files in the same directory as the script files.  
Note: PRUN puts the prun.err.logsummary file in the errorsubdirectory.  
If you specify (y), PRUN overwrites the contents of existing log files. By default,  
PRUN keep the original information in the log files and appends new  
information at the end of each file.  
overwrite  
connections  
Enter a number for the maximum number of connections for the data sources.  
The data source should support this number of connections.  
PRUN Command  
95  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
If the PRUN command is executed without any arguments, Neoview Script prompts for the  
PRUN arguments. If one or more options are specified, the PRUN command runs without  
prompting for more input. In the non-interactive mode, if any options are not specified then  
the default value of is used.  
•
The -d optionor -defaultscannot be specified with any other option.  
Example  
•
To use PRUN, enter the PRUN command in the Neoview Script interface:  
SQL>prun  
Enter * as input to stop the current prun session  
--------------------------------------------------  
Enter the scripts directory  
Enter the script file extension[sql]  
:
:
c:\ddl_scripts  
Enter the logs directory[scripts dir] :  
Overwrite the log files (y/n)[n]?  
Enter the number of connections(2-248)[2]:  
c:\log  
y
3
:
After you enter the number of connections, PRUN starts to process the script files and  
displays this status:  
Status: In Progress.......  
After executing all the script files, PRUN returns a summary of the operation:  
_____________________________________________  
PARALLELRUN(PRUN) SUMMARY  
_____________________________________________  
Total files present ........................3  
Total files processed ......................3  
Total sqls processed ......................40  
Total errors ...............................4  
Total warnings .............................0  
Total successes ...........................36  
Total connections ..........................5  
Total connection failures...................0  
Please verify the error log file c:\log\error\prun.err.log  
SQL>  
•
This PRUN command initiates a parallel run operation with the -doption:  
SQL>prun -d  
SQL> prun -scriptsdir ./prun/sql –e sql –ld ./prun/logs –o y –connections 5  
PRUN options are -scriptsdir  
-logsdir  
c:/_nvs/prun  
c:/_nvs/prun/logs  
-extension  
-overwrite  
sql  
y
-connections  
5
Status: Complete  
_____________________________________________  
PARALLELRUN(PRUN)SUMMARY  
_____________________________________________  
Total files present ......................99  
Total files processed ....................99  
Total sqls processed ....................198  
Total errors ..............................0  
Total warnings ............................0  
Total warnings ............................0  
96  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
Total connections .........................5  
Total connection failures..................0  
You can execute this command only in SQL mode.  
•
•
PRUN can be started in non-interactive mode using the –q parameter, thus requiring no  
input:  
hpnvs.cmd -h arc0101.caclab.cac.cpqcorp.net -dsn  
TDM_Default_DataSource -u super.services -p host1  
-q "prun –sd c:/_nvs/prun -o y -c 3"  
PRUN can be started in non-interactive mode from an obey file:  
SQL>obey startPrun.txt  
SQL>prun -sd c:/_nvs/prun -ld c:/_nvs/prun/logs -e sql -o y -c 5  
PRUN options are -scriptsdir  
-logsdir  
c:/_nvs/prun  
c:/_nvs/prun/logs  
-extension  
-overwrite  
-connections  
sql  
yes  
5
Status: Complete  
For a summary of all errors and warnings that occurred during the PRUN operation, go to the  
errorsubdirectory in the same directory as the log files (for example, C:\log\error) and  
open the prun.err.logsummary file.  
For details about the errors that occurred during the execution of a script file, open each individual  
log file (<script-file.sql>.log)  
QUIT Command  
The QUIT command disconnects from and exits the Neoview Script interface.  
Syntax  
QUIT [IF ERRORCODE{=|<|>|<=|>=|<>}error-code]  
error-code  
is an integer that represents an error condition of the previously executed  
command. If the previously executed command returns this error code, the  
Neoview Script interface disconnects and exits.  
Commands that execute successfully in the Neoview Script interface have an  
error code of zero (0). Interface commands that do not perform SQL operations  
and that fail to execute have an error code of -1. A failed SQL operation has a  
specific SQL error code associated with the error condition. For more information  
about SQL error messages, see the Neoview Messages Manual.  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Examples  
•
This command disconnects from and exits the Neoview Script interface, which disappears  
from the screen:  
SQL>quit  
•
In a script file, the conditional exit command causes the script file to quit running and  
disconnect from and exit the Neoview Script interface when the previously run command  
returns error code 4082:  
QUIT Command  
97  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
log c:\errorCode.log  
select * from employee;  
quit if errorcode=4082  
log off  
These results are logged when error code 4082 occurs:  
SQL>select * from employee;  
*** ERROR[4082] Table, view or stored procedure NEO.USR.EMPLOYEE  
does not exist or is inaccessible.  
*** ERROR[8822] The statement was not prepared.  
SQL>quit if errorcode=4082  
RECONNECT Command  
The RECONNECT command creates a new connection to the Neoview platform using the login  
credentials of the last successful connection.  
Syntax  
RECONNECT  
Considerations  
The host name or IP address and port number, credentials (user name and password) and the  
datasource names values are used from information previously entered. This is the information  
specified at launch or when the last CONNECT command was executed.  
If Neoview Script was invoked with the -noconnectlaunch parameter, Neoview Script prompts  
you for the values.  
Examples  
This command creates a new connection to the Neoview platform using the login credentials of  
the last successful connection:  
SQL>reconnect  
Connected to DataSource TDM_Default_DataSource  
REPEAT Command  
The REPEAT command reexecutes a previous command.  
Syntax  
REPEAT [ text | [-]number ]  
text  
specifies the text of the most recently executed command. The command must  
have been executed beginning with text, but textneed be only as many  
characters as necessary to identify the command. Neoview Script ignores leading  
blanks.  
[-]number  
is an integer that identifies a command in the history buffer. If number is negative,  
it indicates the position of the command in the history buffer relative to the current  
command; if number is positive, it is the ordinal number of a command in the  
history buffer.  
The HISTORY command displays the commands or statements in the history  
buffer. See the “HISTORY Command” (page 90).  
98  
Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
To reexecute the immediately preceding command, enter REPEAT without specifying a  
number. If you enter more than one command on a line, the REPEAT command reexecutes  
only the last command on the line.  
•
When a command is selected for repeat, and the SQL terminator value has changed since  
the execution of that command, Neoview script replaces the SQL terminator in the command  
with the current SQL terminator value and executes the command.  
Examples  
•
Display the previously executed commands and reexecute the second to the last command:  
SQL>history  
1>  
2>  
3>  
4>  
5>  
6>  
7>  
8>  
set idletimeout 0  
log on  
set schema persnl;  
select * from employee;  
show tables  
select * from dept;  
show views  
select * from emplist;  
SQL>  
SQL>repeat -2  
show views  
VIEW NAMES  
-------------------------------------------------------------  
EMPLIST MGRLIST  
SQL>  
•
•
Reexecute the fifth command in the history buffer:  
SQL>repeat 5  
show tables  
TABLE NAMES  
-------------------------------------------------------------  
DEPT  
EMPLOYEE JOB  
PROJECT  
SQL>  
Reexecute the SHOW TABLES command:  
SQL>repeat show  
show tables  
TABLE NAMES  
-------------------------------------------------------------  
DEPT  
SQL>  
EMPLOYEE JOB  
PROJECT  
RESET PARAM Command  
The RESET PARAM command clears all parameter values or a specified parameter value in the  
current session.  
RESET PARAM Command  
99  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
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-namecan be preceded by a question mark (?), such as  
?param-name.  
If you do not specify a parameter name, all of the parameter values in the current  
session are cleared.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
To clear several parameter values but not all, you must use a separate RESET PARAM  
command for each parameter.  
Example  
This RESET PARAM command clears the setting of the ?sal(salary) parameter, and the SET  
PARAM command resets it to a new value:  
SQL>reset param ?sal  
SQL>set param ?sal 80000.00  
For more information, see “Resetting the Parameters” (page 61).  
RUN Command  
The RUN command executes the previously executed SQL statement. This command does not  
repeat a Neoview Script interface command.  
Syntax  
RUN  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Example  
This RUN command executes the previously executed SELECT statement:  
SQL>select count(*) from persnl.employee;  
(EXPR)  
--------------------  
62  
--- 1 row(s) selected.  
SQL>run  
(EXPR)  
100 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
--------------------  
62  
--- 1 row(s) selected.  
SQL>  
SAVEHIST Command  
The SAVEHIST command saves the session history in a user-specified file. The session history  
consists of a list of the commands that were executed in the Neoview Script session before the  
SAVEHIST command.  
Syntax  
SAVEHIST file-name [CLEAR]  
file-name is the name of a file into which Neoview Script stores the session history. If you  
want the history file to exist outside the local directory where you launch Neoview  
Script (by default, the Neoview Script bindirectory), specify the full directory  
path of the history file. The specified directory must exist before you execute the  
SAVEHIST command.  
CLEAR  
instructs Neoview Script to clear the contents of the specified file before adding  
the session history to the file.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
If the specified file already exists, Neoview Script appends newer session-history information  
to the file.  
Examples  
•
This command clears the contents of an existing file named history.txt in the local directory  
(the same directory where you are running Neoview Script) and saves the session history  
in the file:  
SQL>savehist history.txt clear  
SQL>  
•
•
This command saves the session history in a file named hist.txt in the specified directory on  
a Windows workstation:  
SQL>savehist c:\log_files\hist.txt  
SQL>  
This command saves the session history in a file named hist.txt in the specified directory on  
a Linux or UNIX workstation:  
CS#savehist ./log_files/hist.txt  
CS#  
For more information, see “Displaying Executed Commands” (page 58).  
SET COLSEP Command  
The SET COLSEP command sets the column separator and allows you to control the formatting  
of the result displayed for SQL queries. The SET COLSEP command specifies a delimiter value  
SAVEHIST Command 101  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
to use for separating columns in each row of the results. The default delimiter is “ ”(white  
space).  
Syntax  
SET COLSEP [separator]  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The SET COLSEP  
command can be executed only in SQL mode.  
The SET COLSEP command has no effect if the markup is set to HTML, XML, or CSV.  
Examples  
•
This SET COLSEP command specifies the separator as a “|”(pipe):  
SQL>set colsep |  
SQL>show colsep  
COLSEP "|"  
SQL>select * from employee;  
EMPNUM|EMPNAME  
|REGNUM|BRANCHNUM|JOB  
------|--------------|------|---------|--------  
1|ROGER GREEN |  
23|JERRY HOWARD |  
29|JACK RAYMOND |  
32|THOMAS RUDLOFF|  
39|KLAUS SAFFERT |  
99|  
2|  
1|  
5|  
5|  
1|MANAGER  
1|MANAGER  
1|MANAGER  
3|MANAGER  
2|MANAGER  
--- 5 row(s) selected.  
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  
In the Neoview Script interface, you must enter the command on one line.  
Examples  
This SET HISTOPT command shows only the obey commands added to the history buffer.  
SQL> show histopt  
HISTOPT DEFAULT [No expansion of script files]  
SQL> obey e:\scripts\nobey\insert2.sql  
SQL> ?section insert  
SQL> set schema neo.sch;  
102 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
--- SQL operation complete.  
SQL> INSERT INTO COURSE1 VALUES  
+> ('C11', 'INTRO TO CS','FOR ROOKIES',3, 100,'CIS');  
--- 1 row(s) inserted.  
SQL> INSERT INTO COURSE1 VALUES  
+>  
('C55', 'COMPUTER ARCH.','VON NEUMANN''S MACH.',3, 100, 'CIS');  
--- 1 row(s) inserted.  
SQL> history;  
1>  
2>  
show histopt  
obey e:\scripts\nobey\insert2.sql  
This SET HISTOPT command shows all the commands added to the history buffer.  
SQL> set histopt all  
SQL> obey e:\scripts\nobey\insert2.sql  
?section insert  
SQL> set schema neo.sch;  
--- SQL operation complete.  
SQL>  
+>  
INSERT INTO COURSE1 VALUES  
('C11','INTRO TO CS','FOR ROOKIES',3, 100, 'CIS');  
---1 row(s) inserted.  
SQL> INSERT INTO COURSE1 VALUES  
+> ('C55','COMPUTER ARCH.','VON NEUMANN''S MACH.',3,100,'CIS');  
---1 row(s) inserted.  
SQL> history;  
1>  
2>  
3>  
4>  
5>  
6>  
show histopt  
obey e:\scripts\nobey\insert2.sql  
history;  
set histopt all  
set schema neo.sch;  
INSERT INTO COURSE1 VALUES  
('C11','INTRO TO CS','FOR ROOKIES',3, 100, 'CIS');  
INSERT INTO COURSE1 VALUES  
('C55','COMPUTER ARCH.','VON NEUMANN''S MACH.',3,100,'CIS');  
7>  
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. The  
default is 30 minutes.  
Syntax  
SET IDLETIMEOUT value  
value is an integer representing the idle timeout value in minutes. Zero represents an infinite  
amount of time, meaning that the session never expires.  
SET IDLETIMEOUT Command 103  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
If you execute this command in a script file, it affects the session in which the script file runs.  
You can specify this command in PRUN script files. However, running this command from  
a PRUN script file does not affect the idle timeout value for the current session.  
•
To reset the default timeout value, enter this command:  
SET IDLETIMEOUT 30  
Examples  
•
This command sets the idle timeout value to four hours:  
SQL>set idletimeout 240  
•
•
This command sets the idle timeout value to an infinite amount of time so that the session  
never expires:  
SQL>set idletimeout 0  
To reset the idle timeout to the default, enter this command:  
SQL>set idletimeout 30  
SQL>  
For more information, see “Setting and Showing the Idle Timeout Value for the Session” (page 53).  
SET MARKUP Command  
The SET MARKUP command sets the markup format and controls how results are displayed by  
Neoview Script.  
Syntax  
SET MARKUP [RAW|HTML|XML|CSV]  
The supported options enable results to be displayed in XML, HTML, and CSV (Comma Separated  
Values) format. The default format is RAW.  
Considerations  
In the Neoview Script interface, you must enter the command on one line.  
Examples  
•
This SET MARKUP command specifies results be displayed in HTML:  
SQL>set markup html  
SQL>select c.custnum, c.custnum, ordernum, order_date  
+>from customer c, orders o where c.custnum=o.custnum;  
<TABLE>  
<!--select c.custnum, c.custname,ordernum,order_date  
from customer c, orders o where c.custnum=o.custnum;-->  
<tr>  
<th>CUSTNUM</th>  
<th>CUSTNAME</th>  
<th>ORDERNUM</th>  
<th>ORDER_DATE</th>  
</tr>  
<tr>  
<td>143</td>  
104 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
<td>STEVENS SUPPLY</td>  
<td>700510</td>  
<td>2003-06-01</td>  
</tr>  
<tr>  
<td>3333</td>  
<td>NATIONAL UTILITIES</td>  
<td>600480</td>  
<td>2003-05-12</td>  
</tr>  
<tr>  
<td>7777</td>  
<td>SLEEP WELL HOTELS</td>  
<td>100250</td>  
<td>2003-01-23</td>  
</tr>  
<!-- *** Query completed. 3 rows found, 4 columns returned.-->  
<!-- *** Total elapsed time was 2 second(s).-->  
</TABLE>  
SQL>select c.custnum, c.custname,ordernum,order_date,  
+>from customer c, orders o where c.custnum=o.custnum;  
<TABLE>  
<!-- select c.custnum, c.custname,ordernum,order_date,  
from customer c, orders o where c.custnum=o.custnum;-->  
<tr>  
<th>Error Id</th>  
<th>Error Code</th>  
<th>Error Message</th>  
<tr>  
<td>1</td>  
<td>4082</td>  
<td>Object NEO.NVS.CUSTOMER does not exist or is inaccessible.</td>  
</tr>  
<tr>  
<td>2</td>  
<td>8822</td>  
<td>The statement was not prepared.</td>  
</tr>  
</TABLE>  
•
This SET MARKUP command specifies results be displayed in CSV:  
SQL>set markup CSV  
SQL>select c.custnum, c.custnum, ordernum, order_date  
+>from customer c,orders o where c.custnum=o.custnum;  
143,STEVENS SUPPLY  
,700510,2003-06-01  
3333,NATIONAL UTILITIES,600480,2003-05-12  
7777,SLEEPWELL HOTELS ,100250,2003-01-23  
324,PREMIER INSURANCE ,500450,2003-04-20  
926,METALL-AG.  
,200300,2003-02-06  
123,BROWN MEDICAL CO ,200490,2003-03-19  
123,BROWN MEDICAL CO ,300380,2003-03-19  
543,FRESNO STATE BANK ,300350,2003-03-03  
5635,ROYAL CHEMICALS ,101220,2003-07-21  
21,CENTRAL UNIVERSITY,200320,2003-02-17  
1234,DATASPEED  
,100210,2003-04-10  
3210,BESTFOOD MARKETS ,800660,2003-10-09  
•
This SET MARKUP command specifies results be displayed in XML:  
SQL>set markup xml  
<?xml version="1.0"?>  
SET MARKUP Command 105  
Download from Www.Somanuals.com. All Manuals Search And Download.  
<Results>  
<Query>  
<![CDATA[select * from author;]]>  
</Query>  
<rowid="1">  
<AUTHORID>91111</AUTHORID>  
<AUTHORNAME>Bjarne Stroustrup</AUTHORNAME>  
</row>  
<rowid="2">  
<AUTHORID>444444</AUTHORID>  
<AUTHORNAME>John Steinbeck</AUTHORNAME>  
</row>  
<rowid="3">  
<AUTHORID>2323423</AUTHORID>  
<AUTHORNAME>Irwin Shaw</AUTHORNAME>  
</row>  
<rowid="4">  
<AUTHORID>93333</AUTHORID>  
<AUTHORNAME>Martin Fowler</AUTHORNAME>  
</row>  
<rowid="5">  
<AUTHORID>92222</AUTHORID>  
<AUTHORNAME>Grady Booch</AUTHORNAME>  
</row>  
<rowid="6">  
<AUTHORID>84758345</AUTHORID>  
<AUTHORNAME>Judy Blume</AUTHORNAME>  
</row>  
<rowid="7">  
<AUTHORID>89832473</AUTHORID>  
<AUTHORNAME>Barbara Kingsolver</AUTHORNAME>  
</row>  
<Status> <![CDATA[*** Query completed. 7 rows found.  
2 columns returned. *** Total elasped time was 1 second(s).]]></Status>  
</Results>  
SET LIST_COUNT Command  
The SET LIST_COUNT command sets the maximum number of rows to be returned by SELECT  
statements that are executed after this command. The default is zero, which means that all rows  
are returned.  
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 executed after this command. Zero means  
that all rows of data are returned.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
To reset the number of displayed rows, enter this command:  
SET LIST_COUNT 0  
106 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Examples  
•
This SET LIST_COUNT command specifies that the number of rows to be displayed by  
SELECT statements is five:  
SQL>set list_count 5  
SQL>select empnum, first_name, last_name  
from persnl.employee  
order by empnum;  
EMPNUM FIRST_NAME  
LAST_NAME  
------ --------------- --------------------  
1 ROGER  
23 JERRY  
29 JANE  
32 THOMAS  
39 KLAUS  
GREEN  
HOWARD  
RAYMOND  
RUDLOFF  
SAFFERT  
--- 5 row(s) selected. LIST_COUNT was reached.  
SQL>  
•
This SET LIST_COUNT command resets the number of displayed rows to all rows:  
SQL>set list_count 0  
SQL>select empnum, first_name, last_name  
+>from persnl.employee  
+>order by empnum;  
EMPNUM FIRST_NAME  
------ ---------------  
1 ROGER  
LAST_NAME  
--------------------  
GREEN  
23 JERRY  
HOWARD  
29 JANE  
RAYMOND  
32 THOMAS  
39 KLAUS  
RUDLOFF  
SAFFERT  
43 PAUL  
WINTER  
65 RACHEL  
...  
MCKAY  
995 Walt  
Farley  
--- 62 row(s) selected.  
SQL>  
SET PARAM Command  
The SET PARAM command associates a parameter name with a parameter value in the current  
session. The parameter name and value are associated with one of these parameter types:  
•
•
Named parameter (represented by ?param-name) in a DML statement or in a prepared  
SQL statement  
Unnamed parameter (represented by ?) in a prepared SQL statement only  
A prepared statement is one that you SQL compile by using the PREPARE statement. For more  
information about PREPARE, see the Neoview SQL Reference Manual.  
After running SET PARAM commands in the session:  
•
•
You can specify named parameters (?param-name) in a DML statement.  
You can execute a prepared statement with named parameters by using the EXECUTE  
statement without a USING clause.  
•
You can execute a prepared statement with unnamed parameters by using the EXECUTE  
statement with a USING clause that contains literal values and/or a list of the named  
parameters set by SET PARAM.  
SET PARAM Command 107  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
The EXECUTE statement substitutes parameter values for the parameters in the prepared  
statement. For more information about EXECUTE, see the Neoview SQL Reference Manual.  
Syntax  
SET PARAM param-name param-value  
param-name  
is the name of the parameter for which a value is specified. Parameter names  
are case-sensitive. For example, the parameter ?pn is not equivalent to the  
parameter ?PN. param-namecan be preceded by a question mark (?), such  
as ?param-name.  
is a numeric or character literal that specifies the value for the parameter. If  
you do not specify a value, Neoview Script returns an error.  
param-value  
If param-value is a character literal and the target column type is a character  
string, you do not have to enclose the value in single quotation marks. Its data  
type is determined from the data type of the column to which the literal is  
assigned. Character strings specified as parameter values are always  
case-sensitive even if they are not enclosed in quotation marks.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
Use separate SET PARAM commands to name and assign values to each unique parameter  
in a prepared SQL statement before running the EXECUTE statement.  
•
Parameter names are case-sensitive. If you specify a parameter name in lowercase in the  
SET PARAM command, you must specify it in lowercase in other statements, such as DML  
statements or EXECUTE.  
•
The name of a named parameter (?param-name) in a DML statement must be identical to  
the parameter name (param-name) that you specify in a SET PARAM command.  
Examples  
•
This command sets a value for the ?sal(salary) parameter:  
SQL>set param ?sal 40000.00  
•
•
This command sets a character string value, GREEN, for the ?lastnameparameter:  
SQL>set param ?lastname GREEN  
These commands set values for named parameters in a subsequent SELECT statement:  
SQL>set param ?sal 80000.00  
SQL>set param ?job 100  
SQL>select * from persnl.employee  
where salary = ?sal  
and jobcode = ?job;  
EMPNUM FIRST_NAME  
LAST_NAME  
DEPTNUM JOBCODE SALARY  
------ --------------- -------------------- ------- ------- ----------  
72 GLENN  
--- 1 row(s) selected.  
SQL>  
THOMAS  
3300  
100 80000.00  
108 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
NOTE: The names of the named parameters, ?saland ?job, in the SELECT statement  
are identical to the parameter names, saland job, in the SET PARAM command.  
For more information, see “Setting Parameters” (page 61).  
SET PROMPT Command  
The SET PROMPT command sets the prompt of the current session to a specified string and/or  
to these session variables: %USER, %MODE, %SERVER, %SCHEMA, or %DATASOURCE. In  
SQL mode, the default prompt is SQL>. In CS mode, the default prompt is CS#.  
Syntax  
SET PROMPT [string] [%USER] [%MODE] [%SERVER]  
[%SCHEMA] [%DATASOURCE]  
string  
is a string value to be displayed as the prompt. The string may contain any  
characters. Spaces are allowed if you enclose the string in double quotes. If  
you do not enclose the string in double quotes, the prompt is displayed in  
uppercase.  
%USER  
displays the session user name as the prompt.  
%MODE  
%SERVER  
%SCHEMA  
displays the operating mode of the session as the prompt.  
displays the session host name and port number as the prompt.  
displays the session schema as the prompt.  
%DATASOURCE displays the session data source as the prompt.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
Unlike SET SQLPROMPT, you can execute this command in other modes.  
To reset the default prompt, enter this command:  
SET PROMPT  
Examples  
•
This SET PROMPT command sets the SQL prompt to ENTER>:  
SQL>set prompt Enter>  
ENTER>  
•
This SET PROMPT command sets the CS prompt to #:  
ENTER>mode cs  
CS#set prompt #  
#
•
•
To reset the CS prompt to the default, enter this SET PROMPT command:  
#set prompt  
CS#  
To reset the SQL prompt to the default, enter this SET PROMPT command:  
CS#mode sql  
ENTER>set prompt  
SET PROMPT Command 109  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
SQL>  
•
•
•
•
•
•
This command displays the session user name for the prompt:  
SQL>set prompt %user>  
dba1>  
This command displays the operating mode of the session for the prompt:  
SQL>set prompt %mode:  
SQL:  
This command displays the session host name and port number for the prompt:  
SQL>set prompt %server>  
sys0101.mylab.mycorp.net:18650>  
This command displays the session schema for the prompt:  
SQL>set prompt "Schema %schema:"  
Schema USR:  
This command displays the session data source for the prompt:  
SQL>set prompt "%datasource SQL>"  
TDM_Default_DataSource SQL>  
This command displays multiple session variables:  
SQL>set prompt %USER@%SCHEMA>  
super.super@USR>  
SQL> set prompt %SERVER@DATASOURCE>  
nvs0101:23000@TDM_Default_DataSource>  
SQL>set prompt ”%schema NVSCRIPT> ”  
NVSCHEMA NVSCRIPT>  
For more information, see “Customizing the Standard Prompt” (page 53).  
SET SQLPROMPT Command  
The SET SQLPROMPT command sets the SQL prompt of the current session to a specified string.  
The default is SQL>.  
Syntax  
SET SQLPROMPT [string] [%USER] [%MODE] [%SERVER]  
[%SCHEMA] [%DATASOURCE]  
string  
is a string value to be displayed as the SQL prompt. The string may contain  
any characters. Spaces are allowed if you enclose the string in double quotes.  
If you do not enclose the string in double quotes, the prompt is displayed in  
uppercase.  
%USER  
displays the session user name as the prompt.  
%MODE  
%SERVER  
%SCHEMA  
displays the operating mode of the session as the prompt.  
displays the session host name and port number as the prompt.  
displays the session schema as the prompt.  
110 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
%DATASOURCE displays the session data source as the prompt.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
You can execute this command only in SQL mode.  
To reset the default SQL prompt, enter this command:  
SET SQLPROMPT  
•
•
Examples  
•
This command sets the SQL prompt to ENTER>:  
SQL>set sqlprompt Enter>  
ENTER>  
•
•
•
•
•
•
•
To reset the SQL prompt to the default, enter this command:  
ENTER>set sqlprompt  
SQL>  
This command displays the session user name for the prompt:  
SQL>set sqlprompt %user>  
dba1>  
This command displays the operating mode of the session for the prompt:  
SQL>set sqlprompt %mode:  
SQL:  
This command displays the session host name and port number for the prompt:  
SQL>set sqlprompt %server>  
sys0101.mylab.mycorp.net:18650>  
This command displays the session schema for the prompt:  
SQL>set sqlprompt "Schema %schema:"  
Schema USR:  
This command displays the session data source for the prompt:  
SQL>set sqlprompt "%datasource SQL>"  
TDM_Default_DataSource SQL>  
This command displays multiple session variables:  
SQL>set sqlprompt %USER@%SCHEMA>  
super.super@USR>  
nvs0101:23000@TDM_Default_DataSource>  
SQL>set sqlprompt ”%schema NVSCRIPT> ”  
NVSCHEMA NVSCRIPT>  
For more information, see “Customizing the Standard Prompt” (page 53).  
SET SQLPROMPT Command 111  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
SET SQLTERMINATOR Command  
The SET SQLTERMINATOR command sets the SQL statement terminator of the current 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.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
If you execute this command in a script file, it affects not only the SQL statements in the  
script file but all subsequent SQL statements that are run in the current session. If you set  
the SQL terminator in a script file, reset the default terminator at the end of the script file.  
•
To reset the default SQL terminator (;), enter this command:  
SET SQLTERMINATOR ;  
Examples  
•
This command sets the SQL terminator to a period (.):  
SQL>set sqlterminator .  
•
This command sets the SQL terminator to a word, go:  
SQL>set sqlterminator go  
This query ends with the new terminator, go:  
SQL>select * from persnl.employee go  
•
To reset the SQL terminator to the default, enter this command:  
SQL>set sqlterminator ;  
For more information, see “Setting and Showing the SQL Terminator” (page 54).  
SET TIME Command  
The SET TIME command causes the local time of the client workstation to be displayed as part  
of the interface prompt. By default, the local time is not displayed in the interface prompt.  
Syntax  
SET TIME { ON[12H] | OFF }  
ON specifies that the local time be displayed as part of the prompt.  
OFF specifies that the local time not be displayed as part of the prompt. OFF is the default.  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
112 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
Starting with the R2.1 release, the default is a 24–hour military style display. The additional  
argument of 12h allows the time to be displayed in a 12–hour AM/PM style.  
Examples  
•
This command causes the local time to be displayed in the SQL prompt:  
SQL>set time on  
14:17:17 SQL>  
•
•
This command causes the local time to be displayed in 12–hour AM/PM style in the SQL  
prompt:  
SQL>set time on 12h  
2:17:17 PM SQL>  
This command turns off the local time in the SQL prompt:  
2:17:17 PM SQL>set time off  
SQL>  
For more information, see “Customizing the Standard Prompt” (page 53).  
SET TIMING Command  
The SET TIMING command causes the elapsed time to be displayed after each SQL statement  
executes. This command does not cause the elapsed time of Neoview Script interface commands  
to be displayed. By default, the elapsed time is off.  
Syntax  
SET TIMING { ON | OFF }  
ON specifies the elapsed time be displayed after each SQL statement executes. For a list of  
these statements, see Appendix B (page 133).  
OFF specifies that the elapsed time not be displayed after each SQL statement executes. OFF  
is the default.  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Examples  
•
This command displays the elapsed time of SQL statements:  
SQL>set timing on  
•
This command turns off the elapsed time:  
SQL>set timing off  
For more information, see “Displaying the Elapsed Time” (page 54).  
SHOW COLSEP Command  
The SHOW COLSEP command displays the value of the column separator for the current Neoview  
Script session.  
SET TIMING Command 113  
Download from Www.Somanuals.com. All Manuals Search And Download.  
               
Syntax  
SHOW COLSEP  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Examples  
•
This SHOW COLSEP command displays the column separator.  
SQL> show colsep  
COLSEP " "  
SQL> set colsep *  
SQL> show colsep  
COLSEP "*"  
SHOW HISTOPT Command  
The SHOW HISTOPT command displays the value that has been set for the history option.  
Syntax  
SHOW HISTOPT  
Considerations  
In the Neoview Script interface, you must enter the command on one line.  
Examples  
This command displays 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 Neoview  
Script session. The idle timeout value of a session determines when the session expires after a  
period of inactivity. The default is 30 minutes.  
Syntax  
SHOW IDLETIMEOUT  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
114 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                       
Examples  
•
This command shows that the idle timeout value of the session is 30 minutes, which is the  
default:  
SQL>show idletimeout  
IDLETIMEOUT 30 min(s)  
•
•
This command shows that the idle timeout value of the session is four hours:  
SQL>show idletimeout  
IDLETIMEOUT 240 min(s)  
This command shows that the idle timeout value is an infinite amount of time, meaning that  
the session never expires:  
SQL>show idletimeout  
IDLETIMEOUT 0 min(s) [Never Expires]  
For more information, see “Setting and Showing the Idle Timeout Value for the Session” (page 53).  
SHOW LIST_COUNT Command  
The SHOW LIST_COUNT command displays the maximum number of rows to be returned by  
SELECT statements in the current Neoview Script session. The default is zero, which means that  
all rows are returned.  
Syntax  
SHOW LIST_COUNT  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Examples  
•
This SHOW LIST_COUNT command shows that SELECT statements return all rows in the  
current session:  
SQL>show list_count  
LISTCOUNT 0 [All Rows]  
•
This SHOW LIST_COUNT command shows that the maximum number of rows to be  
displayed by SELECT statements in the session is five:  
SQL>set list_count 5  
SQL>show list_count  
LISTCOUNT 5  
SHOW MARKUP Command  
The SHOW MARKUP command displays the value set for the markup option.  
Syntax  
SHOW MARKUP  
Considerations  
In the Neoview Script interface, you must enter the command on one line.  
SHOW LIST_COUNT Command 115  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Examples  
This command displays the value set for the markup option:  
SQL>show markup  
MARKUP RAW  
SHOW MODE Command  
The SHOW MODE command displays the operating mode of the current Neoview Script session.  
The default is SQL.  
Syntax  
SHOW MODE  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Example  
This command shows that the mode of the current session is CS:  
>show mode  
MODE CS  
For more information, see “MODE Command” (page 92).  
SHOW MVGROUPS Command  
The SHOW MVGROUPS command displays all or a set of the materialized view groups in the  
current schema of the Neoview Script session.  
Syntax  
SHOW MVGROUPS [wild-card-pattern]  
wild-card-pattern  
is a character string used to search for and display materialized view  
groups with names that match the character string.  
wild-card-patternmatches an uppercase string unless you  
enclose it within double quotes. To look for similar values, specify  
only part of the characters of wild-card-patterncombined 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 PARTICULARbut not smartor  
Hearts. "%art%"matches smartand  
Heartsbut not SMART, ARTIFICIAL,  
or PARTICULAR.  
_
Use an underscore to indicate any single  
character. For example, boo_matches  
BOOKand BOOTbut not BOOor BOOTS.  
"boo_"matches bookand bootbut not  
booor boots.  
116 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                   
Considerations  
•
•
•
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
If you do not specify a wild-card pattern in a SHOW MVGROUPS command, Neoview  
Script displays all the materialized view groups that exist in the current schema.  
If you specify a wild-card pattern in a SHOW MVGROUPS command, Neoview Script  
displays only the materialized view group names that match the wild-card pattern.  
You can execute this command only in SQL mode.  
Examples  
•
This command shows all the materialized view groups in the current schema, PERSNL:  
SQL>show mvgroups  
MATERIALIZED VIEW GROUP NAMES  
-------------------------------------------------------------  
MVGROUP1 MVGROUP2 EMPLOYEEINFO  
SQL>  
•
•
This command shows all the materialized view groups in the current schema, PERSNL, that  
have “GROUP” in their names:  
SQL>show mvgroups %group%  
MATERIALIZED VIEW GROUP NAMES  
-------------------------------------------------------------  
MVGROUP1 MVGROUP2  
SQL>  
This command shows all the materialized view groups in the current schema, SALES, that  
are named “PART” followed by one character:  
SQL>show mvgroups "PART_"  
MATERIALIZED VIEW GROUP NAMES  
-------------------------------------------------------------  
PART1 PART2 PARTS  
SQL>  
SHOW MVS Command  
The SHOW MVS command displays all or a set of the materialized views in the current schema  
of the Neoview Script session.  
Syntax  
SHOW MVS [wild-card-pattern]  
wild-card-pattern  
is a character string used to search for and display materialized views  
with names that match the character string. wild-card-pattern  
matches an uppercase string unless you enclose it within double  
SHOW MVS Command 117  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
quotes. To look for similar values, specify only part of the characters  
of wild-card-patterncombined 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 PARTICULARbut not smartor  
Hearts. "%art%"matches smartand  
Heartsbut not SMART, ARTIFICIAL,  
or PARTICULAR.  
_
Use an underscore to indicate any single  
character. For example, boo_matches  
BOOKand BOOTbut not BOOor BOOTS.  
"boo_"matches bookand bootbut not  
booor boots.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
If you do not specify a wild-card pattern in a SHOW MVS command, Neoview Script displays  
all the materialized views that exist in the current schema.  
•
If you specify a wild-card pattern in a SHOW MVS command, Neoview Script displays only  
the materialized view names that match the wild-card pattern.  
Examples  
•
This command shows all the materialized views in the current schema, PERSNL:  
SQL>show mvs;  
MATERIALIZED VIEW NAMES  
-------------------------------------------------------------  
mvemp1 mvemp2 mvemp3 mvjobdesc  
SQL>  
•
•
This command shows all the materialized views in the current schema, PERSNL, that have  
“EMP” in their names:  
SQL>show mvs %emp%;  
MATERIALIZED VIEW NAMES  
-------------------------------------------------------------  
MVEMP1 MVEMP2 MVEMP3  
SQL>  
This command shows all the materialized views in the current schema, SALES, that are  
named “ORDER” followed by one character:  
SQL>show mvs "ORDER_"  
MATERIALIZED VIEW NAMES  
-------------------------------------------------------------  
ORDER1 ORDER2 ORDERS  
SQL>  
SHOW PARAM Command  
The SHOW PARAM command displays the parameters that are set in the current Neoview Script  
session.  
118 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Syntax  
SHOW PARAM  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Example  
•
This command shows all the schemas that exist in the default catalog of the current session:  
SQL>show schemas  
SCHEMA NAMES  
------------------------------------------------------------------------  
DBA001  
DBA082  
DBMGR  
DBSCRIPT_SALES  
DEMOSCH1  
DEV060525  
HMGR  
HPNVS_SAMPLE  
ODBC_INVENT  
ODBC_SCHEMA  
PUBLIC_ACCESS_SCHEMA  
ROLEUSER  
DEFINITION_SCHEMA_VERSION_1200 DEMOSCH  
DEMOSCH2  
DS_SCH  
HPNVS  
HPNVS_SAMPLE  
ODBC_PERSNL  
ODBC_TEST  
ROLEDBA  
DEMO_SCH  
D_SALES  
HPNVSSCH  
INVENT  
ODBC_SALES  
PERSNL  
ROLEMGR  
SCH  
SALES  
SERVICES  
T4JDBC_SCHEMA  
TEST1  
USR  
SQL>  
•
•
This command shows that parameters that are set for the current session:  
SQL>show param  
lastname GREEN  
dn 1500  
sal 40000.00  
This command shows that when no parameters exist, the SHOW PARAM command displays  
an error message:  
SQL>show param  
No parameters found.  
For more information, see “Displaying the Parameters of the Session” (page 61).  
SHOW PREPARED Command  
The SHOW PREPARED command displays the prepared statements in the current Neoview  
Script 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  
In the Neoview Script interface, you must enter the command on one line. The SHOW PREPARED  
command can be executed only in SQL mode.  
SHOW PREPARED Command 119  
Download from Www.Somanuals.com. All Manuals Search And Download.  
             
Examples  
•
This SHOW PREPARED command shows all the prepared statements, by default:  
SQL>show prepared  
S1  
select * from t1  
S2  
select * from student  
T1  
select * from test123  
SQL> show prepared s%  
S1  
select * from t1  
S2  
select * from student  
SQL> show prepared t%  
T1  
select * from test123  
SHOW SCHEMA Command  
The SHOW SCHEMA command displays the current schema of the Neoview Script session.  
Syntax  
SHOW SCHEMA  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Example  
This 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 55).  
SHOW SCHEMAS Command  
The SHOW SCHEMAS command displays all or a set of the schemas that exist in the default  
catalog of the current Neoview Script session.  
Syntax  
SHOW SCHEMAS [wild-card-pattern]  
120 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                 
wild-card-pattern  
is a character string used to search for and display schemas with  
names that match the character string. wild-card-patternmatches  
an uppercase string unless you enclose it within double quotes. To  
look for similar values, specify only part of the characters of  
wild-card-patterncombined 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 PARTICULARbut not smartor  
Hearts. "%art%"matches smartand  
Heartsbut not SMART, ARTIFICIAL,  
or PARTICULAR.  
_
Use an underscore to indicate any single  
character. For example, boo_matches  
BOOKand BOOTbut not BOOor BOOTS.  
"boo_"matches bookand bootbut not  
booor boots.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
If you do not specify a wild-card pattern in a SHOW SCHEMAS command, Neoview Script  
displays all the schemas that exist in the default catalog.  
•
If you specify a wild-card pattern in a SHOW SCHEMAS command, Neoview Script displays  
only the schema names that match the wild-card pattern.  
Examples  
•
This command shows all the schemas that exist in the default catalog of the current session:  
SQL>show schemas  
SCHEMA NAMES  
------------------------------------------------------------------------  
DBA001  
DBA082  
DBMGR  
DBSCRIPT_SALES  
DEMOSCH1  
DEV060525  
HMGR  
HPNVS_SAMPLE  
ODBC_INVENT  
ODBC_SCHEMA  
PUBLIC_ACCESS_SCHEMA  
ROLEUSER  
DEFINITION_SCHEMA_VERSION_1200 DEMOSCH  
DEMOSCH2  
DS_SCH  
HPNVS  
HPNVS_SAMPLE  
ODBC_PERSNL  
ODBC_TEST  
ROLEDBA  
DEMO_SCH  
D_SALES  
HPNVSSCH  
INVENT  
ODBC_SALES  
PERSNL  
ROLEMGR  
SCH  
SALES  
SERVICES  
T4JDBC_SCHEMA  
TEST1  
USR  
SQL>  
•
This command shows the schemas in the default catalog that have “SALES” in their names:  
SQL>show schemas %sales%  
SCHEMA NAMES  
------------------------------------------------------------------------  
DBSCRIPT_SALES  
SALES  
D_SALES  
ODBC_SALES  
SQL>  
For more information, see “Showing the Schemas” (page 56).  
SHOW SCHEMAS Command 121  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
SHOW SESSION Command  
SHOW SESSION or SESSION displays attributes of the current Neoview Script session. You can  
also use the ENV command to perform the same function.  
Syntax  
[SHOW] SESSION  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
SHOW SESSION or SESSION displays these attributes:  
COLSEP  
Current column separator, which is used to control how query results are  
presented. For more information, see “SET COLSEP Command” (page 101).  
DATASOURCE  
HISTOPT  
Name of the data source that you entered when logging in to the database platform.  
For more information, see “Logging In to the Database Platform” (page 45).  
Current history options, which controls how the commands are added to the  
history buffer. For more information, see “SET HISTOPT Command” (page 102).  
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 Idle Timeout Value for the Session”  
(page 53) and “SET IDLETIMEOUT Command” (page 103).  
LIST COUNT  
LOG  
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 106).  
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 63)  
and “LOG Command” (page 91) or “SPOOL Command” (page 130).  
LOOK AND FEEL  
Current look and feel of the Neoview Script interface. This property affects the  
formatting of status messages. For more information, see “Setting the Look and  
Feel of the Neoview Script Interface” (page 35).  
MARKUP  
MODE  
Current markup option selected for the session. The default option is RAW. For  
more information, see “SET MARKUP Command” (page 104).  
Current operating mode of the session. The default mode is SQL. For more  
information, see “MODE Command” (page 92).  
PROMPT  
Current prompt for the session. In SQL mode, the default is SQL>. In CS mode,  
the default is CS#. For more information, see “Customizing the Standard Prompt”  
(page 53) and “SET PROMPT Command” (page 109).  
SCHEMA  
SERVER  
Current schema. The default is USR. For more information, see “Setting and  
Showing the Current Schema” (page 55).  
Host name and port number that you entered when logging in to the database  
platform. For more information, see “Logging In to the Database Platform”  
(page 45).  
SQLTERMINATOR  
TIME  
Current SQL statement terminator. The default is a semicolon (;). For more  
information, see “Setting and Showing the SQL Terminator” (page 54) and “SHOW  
SQLTERMINATOR Command” (page 124).  
Current setting (on or off) of the local time as part of the prompt. By default, the  
local time is off. For more information, see “Customizing the Standard Prompt”  
(page 53) and “SET TIME Command” (page 112).  
122 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
TIMING  
USER  
Current setting (on or off) of the elapsed time. By default, the elapsed time is off.  
For more information, see “Displaying the Elapsed Time” (page 54) and “SET  
TIMING Command” (page 113).  
User name that you entered when logging in to the database platform. For more  
information, see “Logging In to the Database Platform” (page 45).  
Examples  
•
This SHOW SESSION command displays the attributes of the current session:  
SQL>show session  
COLSEP  
","  
DATASOURCE  
HISTOPT  
TDM_Default_DataSource  
ALL  
IDLETIMEOUT  
LIST COUNT  
LOG  
30 min(s)  
0 [All Rows]  
OFF  
LOOK AND FEEL BTEQ  
MARKUP  
MODE  
XML  
SQL  
PROMPT  
SCHEMA  
SERVER  
SQL>  
USR  
neo0101.acme.com:18650  
SQLTERMINATOR ;  
TIME  
OFF  
TIMING  
USER  
OFF  
role.dba  
•
This SESSION command shows the effect of setting various session attributes:  
SQL>session  
COLSEP  
" "  
DATASOURCE  
HISTOPT  
TDM_Default_DataSource  
ALL  
IDLETIMEOUT  
LIST COUNT  
LOG  
30 min(s)  
0 [All Rows]  
OFF  
LOOK AND FEEL BTEQ  
MARKUP  
MODE  
RAW  
SQL  
PROMPT  
SCHEMA  
SERVER  
SQL >  
USR  
neo0101.acme.com:18650  
SQLTERMINATOR ;  
TIME  
OFF  
TIMING  
USER  
OFF  
role.dba  
SHOW SQLPROMPT Command  
The SHOW SQLPROMPT command displays the value of the SQL prompt for the current Neoview  
Script session.  
Syntax  
SHOW SQLPROMPT  
SHOW SQLPROMPT Command 123  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Example  
This command shows that the SQL prompt for the current session is SQL>:  
SQL>show sqlprompt  
SQLPROMPT SQL>  
SHOW SQLTERMINATOR Command  
The SHOW SQLTERMINATOR command displays the SQL statement terminator of the current  
Neoview Script session.  
Syntax  
SHOW SQLTERMINATOR  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Example  
This 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 54).  
SHOW SYNONYMS Command  
The SHOW SYNONYMS command displays all or a set of the synonyms in the current schema  
of the Neoview Script session.  
Syntax  
SHOW SYNONYMS [wild-card-pattern]  
wild-card-pattern  
is a character string used to search for and display synonyms with  
names that match the character string. wild-card-patternmatches  
an uppercase string unless you enclose it within double quotes. To  
124 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                     
look for similar values, specify only part of the characters of  
wild-card-patterncombined 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 PARTICULARbut not smartor  
Hearts. "%art%"matches smartand  
Heartsbut not SMART, ARTIFICIAL,  
or PARTICULAR.  
_
Use an underscore to indicate any single  
character. For example, boo_matches  
BOOKand BOOTbut not BOOor BOOTS.  
"boo_"matches bookand bootbut not  
booor boots.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
If you do not specify a wild-card pattern in a SHOW SYNONYMS command, Neoview  
Script displays all the synonyms that exist in the current schema.  
•
If you specify a wild-card pattern in a SHOW SYNONYMS command, Neoview Script  
displays only the synonym names that match the wild-card pattern.  
Examples  
•
This command shows all the synonyms in the current schema, SALES:  
SQL>show synonyms  
SYNONYM NAMES  
-------------------------------------------------------------  
CUST DTLS ORDR PRTS  
SQL>  
•
•
This command shows all the synonyms in the current schema, SALES, that have “S” at the  
end of their names:  
SQL>show synonyms %s  
SYNONYM NAMES  
-------------------------------------------------------------  
DTLS PRTS  
SQL>  
This command shows all the synonyms in the current schema, SALES, that are named “PRT”  
followed by one character:  
SQL>show synonyms "PRT_"  
SYNONYM NAMES  
-------------------------------------------------------------  
PRTS  
SQL>  
SHOW TABLE Command  
The SHOW TABLE command displays information about the indexes, materialized views, or  
synonyms of a specified table or materialized view.  
SHOW TABLE Command 125  
Download from Www.Somanuals.com. All Manuals Search And Download.  
       
Syntax  
SHOW TABLE {table-name | materialized-view-name}, { INDEXES | MVS | SYNONYMS |ALL}  
table-name is:  
[schema-name.]table-name  
table-name  
specifies the name of a table. If you do not fully qualify the  
table-name, Neoview Script uses the current schema.  
materialized-view-name  
specifies the name of a materialized view. If you do not fully  
qualify the materialized-view-name, Neoview Script  
uses the current schema.  
INDEXES  
displays information about the indexes associated with the  
specified table or materialized view. The displayed  
information about each index includes:  
• Column name  
• Order  
Name of each column in the index  
Storage and retrieval order, either  
ascending or descending, for rows  
in the index  
• Index type  
• Uniqueness  
Type of index (clustered, hashed, or  
other)  
Whether the column or set of  
columns that comprise the index do  
not contain more than one  
occurrence of the same value or set  
of values  
• Cardinality  
• Position  
Number of unique values in the  
index  
Position of the column within the  
index  
For more information about indexes, see the Neoview SQL  
Reference Manual.  
MVS  
displays a list of the materialized views associated with the  
specified table or materialized view.  
ALL  
displays information about indexes, materialized views, and  
synonyms for a specified table or materialized view.  
SYNONYMS  
displays a list of the synonyms associated with the specified  
table or materialized view.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
You can execute this command only in SQL mode.  
Examples  
•
This command shows information about three indexes of the EMPLOYEE table:  
SQL>show table persnl.employee, indexes  
COLUMN NAME  
ORDER INDEX TYPE UNIQUE CARDINALITY POSITION  
------------------- ----- ---------- ------ ----------- --------  
Index 1 :EMPLOYEE  
-----------------  
EMPNUM  
ASC Other  
Yes  
0
1
126 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
Index 2 :XEMPDEPT  
-----------------  
DEPTNUM  
ASC Other  
No  
0
1
Index 3 :XEMPNAME1  
-----------------  
LAST_NAME  
ASC Other  
ASC Other  
No  
No  
0
0
1
2
FIRST_NAME  
SQL>  
•
•
•
This command shows information about the materialized views of the CUSTOMERS table:  
SQL>show table customers, mvs  
MATERIALIZED VIEW NAME  
----------------------  
MYSCH.MV_CUST  
SQL>  
This command shows information about the synonyms of the CHANNELS table:  
SQL>show table channels, synonyms  
SYNONYM NAME  
---------------  
MYSCH.BANDS  
SQL>  
This command shows all information of the EMP table:  
SQL>show table employee, all  
INDEXES  
------------------- ----- ---------- ------ ----------- --------  
COLUMN NAME  
ORDER INDEX TYPE UNIQUE CARDINALITY POSITION  
------------------- ----- ---------- ------ ----------- --------  
Index 1 :EMPLOYEE  
-----------------  
EMPNUM  
ASC Other  
ASC Other  
Yes  
No  
0
0
1
1
Index 2 :EMPLOYE0  
-----------------  
DEPTNUM  
Index 3 :EMPLOYE1  
-----------------  
REQNUM  
ASC Other  
ASC Other  
No  
No  
0
0
1
2
BRANKNUM  
No synonyms present for object, SCH.EMPLOYEE  
No materialized views present for object, SCH.EMPLOYEE  
For more information, see “Showing the Dependent Objects of a Table” (page 56).  
SHOW TABLES Command  
The SHOW TABLES command displays all or a set of the tables that exist in the current schema  
of the Neoview Script session.  
Syntax  
SHOW TABLES [wild-card-pattern]  
SHOW TABLES Command 127  
Download from Www.Somanuals.com. All Manuals Search And Download.  
     
wild-card-pattern  
is a character string used to search for and display tables with names  
that match the character string. wild-card-patternmatches an  
uppercase string unless you enclose it within double quotes. To look  
for similar values, specify only part of the characters of  
wild-card-patterncombined 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 PARTICULARbut not smartor  
Hearts. "%art%"matches smartand  
Heartsbut not SMART, ARTIFICIAL,  
or PARTICULAR.  
_
Use an underscore to indicate any single  
character. For example, boo_matches  
BOOKand BOOTbut not BOOor BOOTS.  
"boo_"matches bookand bootbut not  
booor boots.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
If you do not specify a wild-card pattern in a SHOW TABLES command, Neoview Script  
displays all the tables that exist in the current schema.  
•
If you specify a wild-card pattern in a SHOW TABLES command, Neoview Script displays  
only the table names that match the wild-card pattern.  
Examples  
•
This command shows all the tables in the current schema, PERSNL:  
SQL>show schema  
SCHEMA PERSNL  
SQL>show tables  
TABLE NAMES  
-------------------------------------------------------------  
DEPT  
EMPLOYEE JOB  
PROJECT  
SQL>  
•
This command shows the tables in the current schema, INVENT, that have “PART” at the  
beginning of their names:  
SQL>show tables part%  
TABLE NAMES  
-------------------------------------------------------------  
PARTLOC PARTSUPP  
SQL>  
For more information, see “Showing the Tables in a Schema” (page 56).  
SHOW TIME Command  
The SHOW TIME command displays whether the setting for the local time in the interface prompt  
is ON or OFF.  
128 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Syntax  
SHOW TIME  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Example  
This command shows that the setting for the local time in the SQL prompt is OFF:  
SQL>show time  
TIME OFF  
SHOW TIMING Command  
The SHOW TIMING command displays whether the setting for the elapsed time is ON or OFF.  
Syntax  
SHOW TIMING  
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Example  
This command shows that the setting for the elapsed time is OFF:  
SQL>show timing  
TIMING OFF  
SHOW VIEWS Command  
The SHOW VIEWS command displays all or a set of the views that exist in the current schema  
of the Neoview Script session.  
Syntax  
SHOW VIEWS [wild-card-pattern]  
wild-card-pattern  
is a character string used to search for and display views with names  
that match the character string. wild-card-patternmatches an  
uppercase string unless you enclose it within double quotes. To look  
SHOW TIMING Command 129  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                       
for similar values, specify only part of the characters of  
wild-card-patterncombined 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 PARTICULARbut not smartor  
Hearts. "%art%"matches smartand  
Heartsbut not SMART, ARTIFICIAL,  
or PARTICULAR.  
_
Use an underscore to indicate any single  
character. For example, boo_matches  
BOOKand BOOTbut not BOOor BOOTS.  
"boo_"matches bookand bootbut not  
booor boots.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
•
You can execute this command only in SQL mode.  
If you do not specify a wild-card pattern in a SHOW VIEWS command, Neoview Script  
displays all the views (not materialized views) that exist in the current schema.  
•
If you specify a wild-card pattern in a SHOW VIEWS command, Neoview Script displays  
only the view names that match the wild-card pattern.  
Examples  
•
This command shows all the views that exist in the current schema, SALES:  
SQL>show schema  
SCHEMA INVENT  
SQL>show views  
VIEW NAMES  
-------------------------------------------------------------  
VIEW207 VIEW207N VIEWCS  
VIEWCUST  
SQL>  
•
This command shows the views in the current schema, INVENT, that have “VIEW” at the  
beginning of their names:  
SQL>show views view%  
VIEW NAMES  
-------------------------------------------------------------  
VIEW207 VIEW207N VIEWCS  
SQL>  
VIEWCUST  
For more information, see “Showing the Views in a Schema” (page 57).  
SPOOL Command  
The SPOOL command logs the entered commands and their output from the Neoview Script  
interface to a log file.  
Syntax  
SPOOL { ON [CLEAR] | log-file [CLEAR] | OFF }  
130 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
ON  
starts the logging process and records information in the sqlspool.lst  
file in the Neoview Script bindirectory.  
ON CLEAR  
log-file  
instructs Neoview Script to clear the contents of the sqlspool.lstfile  
before logging new information to the file.  
is the name of a log file into which Neoview Script records the entered  
commands and their output. If you want the log file to exist outside the  
local directory where you launch Neoview Script (by default, the Neoview  
Script bindirectory), specify the full directory path of the log file. The  
log file does not need to exist, but the specified directory must exist before  
you execute the SPOOL command.  
log-fileCLEAR  
instructs Neoview Script to clear the contents of the specified log-file  
before logging new information to the file.  
OFF  
stops the logging process.  
Considerations  
•
In the Neoview Script interface, you must enter the command on one line. The command  
does not require an SQL terminator.  
•
Use a unique name for each log file to avoid writing information from different Neoview  
Script sessions into the same log file.  
Examples  
•
This command starts the logging process and records information to the sqlspool.lst  
file in the Neoview Script bindirectory:  
SQL>spool on  
•
This command starts the logging process and appends new information to an existing log  
file, persnl_updates.log, in the local directory (the same directory where you are running  
Neoview Script):  
SQL>spool persnl_updates.log  
•
•
•
•
This command starts the logging process and appends new information to a log file,  
sales_updates.log, in the specified directory on a Windows workstation:  
SQL>spool c:\log_files\sales_updates.log  
This command starts the logging process and appends new information to a log file,  
sales_updates.log, in the specified directory on a Linux or UNIX workstation:  
SQL>spool ./log_files/sales_updates.log  
This command starts the logging process and clears existing information from the log file  
before logging new information to the file:  
SQL>spool persnl_ddl.log clear  
This command stops the logging process:  
SQL>spool off  
For more information, see “Logging Output” (page 63).  
VERSION Command  
The VERSION command displays the build versions of Neoview Script and the JDBC Type 4  
Driver.  
Syntax  
VERSION  
VERSION Command 131  
Download from Www.Somanuals.com. All Manuals Search And Download.  
         
Considerations  
In the Neoview Script interface, you must enter the command on one line. The command does  
not require an SQL terminator.  
Example  
This command shows build versions of Neoview Script and the JDBC Type 4 Driver:  
SQL>version  
Neoview Script Build Version  
: T0774_N24_AAC(R2.1)_11MAY07_HP_hpnvs_2007_04_12  
JDBC Type 4 Driver Build Version : T1249_N24_AAK(R2.1)_11MAY07_HP_JDBCT4_2007_04_05  
SQL>  
For more information, see “Verifying the Installed Version of Neoview Script” (page 35).  
132 Neoview Script Interface Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
   
B Supported SQL Statements  
Neoview Script supports these SQL statements, SQL utilities, and other SQL-related commands.  
For more information about these statements, see the Neoview SQL Reference Manual. For a list of  
statements that are available only to HP support, see the Neoview Database Support Guide.  
SQL Statement  
Description  
ALTER MVGROUP  
Adds or removes a materialized view to or from a  
materialized view group.  
ALTER SYNONYM  
ALTER TABLE  
ALTER TRIGGER  
ALTER VIEW  
Alters the synonym of a specified table.  
Adds a column to a table or renames a table.  
Enables or disables triggers, individually or by SQL table.  
Renames a view.  
BEGIN WORK  
Starts a transaction.  
COMMIT WORK  
Commits changes made during a transaction and ends the  
transaction.  
CREATE INDEX  
Creates an index on a table.  
Creates a materialized view.  
CREATE MATERIALIZED VIEW  
CREATE MVGROUP  
Creates a logical collection of materialized views, such as  
materialized views that are defined on a common table or  
that share the same refresh frequency rate.  
CREATE SCHEMA  
CREATE SYNONYM  
Creates a schema.  
Creates a synonym for a table so that queries can refer to  
the synonym instead of the actual table name.  
CREATE TABLE  
Creates a table.  
CREATE TRIGGER  
Creates a trigger on an SQL table. A trigger is a mechanism  
that enables a database system to perform certain actions  
automatically when specified events occur.  
CREATE VIEW  
Creates a view.  
CREATE VOLATILE INDEX  
CREATE VOLATILE TABLE  
DELETE  
Creates a volatile index.  
Creates a volatile table.  
Deletes a row or rows from a table or an updateable view.  
Deletes an index.  
DROP INDEX  
DROP MATERIALIZED VIEW  
DROP MVGROUP  
DROP SCHEMA  
Deletes a materialized view.  
Deletes a materialized view group.  
Deletes a schema.  
DROP SYNONYM  
DROP TABLE  
Deletes a synonym.  
Deletes a table and any indexes, constraints, and inactive  
locks on the table.  
DROP TRIGGER  
DROP VIEW  
Deletes a trigger on an SQL table.  
Deletes a view.  
DROP VOLATILE INDEX  
DROP VOLATILE TABLE  
EXECUTE  
Deletes a volatile index.  
Deletes a volatile table.  
Executes an SQL statement previously compiled by a  
PREPARE statement.  
GRANT  
Grants access privileges for a table or view to specified  
users.  
133  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                                                       
SQL Statement  
INSERT  
Description  
Inserts rows of data into a table or view.  
LOCK TABLE  
Locks the specified table (or underlying tables of a view)  
and its associated indexes for the duration of the active  
transaction.  
MAINTAIN  
Performs one or more table maintenance tasks, such as  
REORG, UPDATE STATISTICS, and REFRESH, on a  
specified database object.  
POPULATE INDEX  
PREPARE  
Loads a specified index with data from a specified table.  
Compiles an SQL statement for later use with the  
EXECUTE statement.  
PURGEDATA  
REORG  
Deletes all data from a table and its related indexes.  
Reorganizes data in a table or index and compacts space  
needed for rows by removing unused space.  
REVOKE  
Revokes access privileges for a table or view from specified  
users.  
ROLLBACK WORK  
Undoes all modifications to database objects during the  
current transaction, releases all locks on database objects  
held by the transaction, and ends the transaction.  
SELECT  
Retrieves data from tables, views, derived tables  
determined by the evaluation of query expressions, or  
joined tables.  
SET SCHEMA  
Sets the schema name for unqualified object names for the  
current session.  
SET TABLE TIMEOUT  
SET TRANSACTION  
UPDATE  
Sets a dynamic timeout value for a lock timeout or a stream  
timeout in the environment of the current session.  
Sets attributes, such as isolation level and access mode,  
for the next transaction.  
Updates data in a row or rows of a table or updateable  
view.  
UPDATE STATISTICS  
Updates histogram statistics for one or more groups of  
columns in a table.  
134 Supported SQL Statements  
Download from Www.Somanuals.com. All Manuals Search And Download.  
                             
C Connectivity Service Commands  
Neoview Script supports connectivity service commands in the Neoview Script interface in  
connectivity service (CS) mode. You can execute connectivity service commands interactively  
or in script files that you run in CS mode. For information about changing to CS mode, see the  
“MODE Command” (page 92).  
Any user can execute the “INFO DS Command” (page 135). Other connectivity service commands  
are available only to HP support. For information about those commands, see the Neoview Database  
Support Guide.  
For more information about managing client data sources and connectivity, see the Neoview  
Database Administrator’s Guide.  
INFO DS Command  
This command displays the attributes for the specified data source.  
Syntax  
INFO DS ds-name;  
ds-name is the name of the data source to be displayed and cannot be the asterisk (*) wild  
card. ds-nameis case-sensitive.  
Considerations  
•
•
None of the servers or the EVARs are shown in this display.  
The wild card (*) is not supported for the data source name, and the data source name is  
case-sensitive.  
Example  
This command displays information about the data source QueryDataSource:  
CS#info ds QueryDataSource;  
DsName...................................QueryDataSource  
MaxSrvrCnt.............................................1  
AvailSrvrCnt...........................................1  
InitSrvrCnt............................................1  
SrvrIdleTimeout........................................1  
ConnIdleTimeout........................................1  
LastUpdated...................2006-08-02 14:39:19.977046  
StartMode............................. ...........MANUAL  
ProcessPriority.....................Same as Assoc Server  
CpuList....................................Not Available  
ConnInfoStat.........................................OFF  
SessionInfoStat......................................OFF  
SQLStmtStat..........................................OFF  
SQLPrepareStat.......................................OFF  
SQLExecuteStat.......................................OFF  
SQLExecDirectStat....................................OFF  
SQLFetchStat.........................................OFF  
Terms used in the INFO DS reports are:  
DsName  
Name of the data source this report is about.  
MaxSrvrCnt  
Upper limit of operational servers for this service on this  
data source  
INFO DS Command 135  
Download from Www.Somanuals.com. All Manuals Search And Download.  
           
AvailSrvrCnt  
Available servers for this service on this data source  
(registered minus connected servers)  
InitSrvrCnt  
Number of idle servers to start when data source starts  
SrvrIdleTimeout  
Number of minutes a server waits in the available state  
before stopping itself  
ConnIdleTimeout  
LastUpdated  
StartMode  
Number of minutes a client server connection remains  
idle before the server terminates  
Date and time of the last update of the component's state,  
in client's local time.  
How the servers for this data source were started:  
MANUAL or AUTOMATIC.  
ProcessPriority  
CpuList  
The priority assigned to the process for this data source.  
List of CPUs that the service can start the servers on  
(round-robin)  
ConnInfoStat  
Connection information statistics gathered when a  
connection is established  
SessionInfoStat  
SQLStmtStat  
Session information statistics gathered when a session is  
terminated  
SQL statement statistics gathered when a PREPARE  
statement is received  
SQLPrepareStat  
SQLExecuteStat  
SQLExecDirectStat  
SQLFetchStat  
SQL prepare statistics gathered when a PREPARE  
statement is received  
SQL execute statistics gathered when an EXECUTE  
statement is received  
SQL execute direct statistics gathered when an  
EXECUTEDIRECT statement is received  
SQL fetch statistics when calling a statement  
136 Connectivity Service Commands  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Index  
Symbols  
D
-DhpnvsLF property, 35  
-dsn parameter, 46  
-h parameter, 46  
Data definition language (DDL) statements, running  
simultaneously, 70  
Data source connection, 51  
Database platform, logging in to, 45  
Database, creating, 70  
-host parameter, 46  
-no connect parameter, 47  
-noconnect  
Default schema, 55  
examples of, 50  
-p parameter, 46  
DISCONNECT command, 84  
Documents, related information, 17  
Download site, 28  
-password parameter, 46  
-q parameter  
description of, 47  
E
examples of, 48  
Editing commands, FC, 88  
Elapsed time, displaying, 54  
ENV command, syntax of, 85  
Environment variables  
_JAVA_OPTIONS, 35, 37  
HPNVS_DATASOURCE, 71  
HPNVS_PASSWORD, 71  
HPNVS_SERVER, 71  
HPNVS_USER, 71  
-s parameter  
description of, 47  
examples of, 49  
-script parameter, 47  
-sql parameter, 47  
-u parameter, 46  
-user parameter, 46  
/ command  
example of, 59  
PATH, 24, 44  
syntax of, 82  
Error messages, 59, 65  
EXECUTE statement  
description of, 133  
@ command  
example of, 68  
syntax of, 81  
examples of, 62  
_JAVA_OPTIONS environment variable  
setting at a command-line prompt, 37  
setting in the user profile, 39  
setting in Windows System Properties, 37  
EXIT command, 86  
F
FC command, 87  
A
H
Admin_Load_DataSource, 46  
HELP command, syntax of, 90  
HISTORY command, 90  
Host name, 45  
B
bin directory, 34  
hpnvs.bat, creating a shortcut to, 41  
hpnvs.cmd, location of, 34  
hpnvs.jar, location of, 34  
hpnvs.pl  
C
Case sensitivity, 52  
CLEAR command, syntax of, 83  
CLEAR option, 64  
description of, 74  
location of, 34  
Command line, breaking, 51  
Comments, 67  
hpnvs.py  
description of, 74  
location of, 34  
Conditional exit, 87, 97  
CONNECT command, syntax of, 83  
Continuation prompt, 51  
CREATE SCHEMA statement  
description of, 133  
hpnvs.sh  
location of, 34  
setting the path of, 44  
HPNVS_DATASOURCE environment variable, 71  
HPNVS_PASSWORD environment variable, 71  
HPNVS_SERVER environment variable, 71  
HPNVS_USER environment variable, 71  
example of, 48, 68  
CREATE TABLE statement  
description of, 133  
example of, 68  
CS mode, 92  
I
Idle timeout value, 53  
Indexes, showing all indexes of a table, 56  
137  
Download from Www.Somanuals.com. All Manuals Search And Download.  
 
INFO DS command, 135  
INSERT statement  
N
Neoview JDBC Type 4 Driver  
See JDBC driver, 26  
description of, 134  
example of, 54  
Installation procedures  
Neoview Script  
description of, 21  
installation directory, 34  
installing, 27  
launching from a Perl or Python command line, 74  
launching from a Perl or Python program, 76  
Perl wrapper script, 74  
Python wrapper script, 74  
software files, 34  
testing the launch of, 39  
version of, 51  
downloading the Neoview Script installer file, 27  
testing the launch of Neoview Script, 39  
Installer file, Neoview Script, 27  
Interface command (see Neoview Script interface  
command)  
IP address, 45  
J
JDBC driver  
installation, 26  
Neoview Script installer file, downloading, 27  
Neoview Script interface, 49  
case sensitivity, 52  
verifying the version, 26  
JDBC Type 4 driver (see JDBC driver)  
description of, 51  
L
exiting, quitting, or disconnecting, 50  
launching and running a command, 47  
launching and running a script file, 48  
launching on Linux or UNIX, 44  
launching on Windows, 41  
product banner, 51  
Launch files, location of, 34  
Launch parameters  
descriptions of, 46  
presetting on Linux or UNIX, 45  
presetting on Windows, 43  
lib directory, 34  
prompts, 51  
Linux launch file, location of, 34  
LOG command, 91  
Neoview Script interface command  
breaking across lines, 51  
editing, 87  
Log files  
Neoview Script session, 64  
PRUN operation, 95  
list of supported commands, 79  
repeating, 98  
running when launching Neoview Script, 48  
using in a script file, 67  
Logging in  
default method, 45  
using login parameters, 47  
Logging output  
Neoview Script JAR file, location of, 34  
Neoview Script session  
concurrent sessions, 64  
script file execution, 69  
starting, 63  
stopping, 64  
viewing a log file, 64  
logging output, 63  
setting the idle timeout value, 53  
Neoview SQL look and feel, 36  
nvscript directory, 34  
Login environment variables  
description of, 71  
setting in the user profile, 74  
setting in Windows System Properties, 72  
setting on a Linux or UNIX command line, 73  
setting on a Windows command line, 71  
Login parameters  
O
OBEY command, 68, 93  
P
Parameters, SQL  
displaying, 61  
resetting, 61  
presetting on Linux or UNIX, 45  
presetting on Windows, 43  
specifying on the command line, 47  
Look and feel  
setting, 61  
PATH environment variable, 26, 44  
Perl command line  
invoking Neoview Script, 74  
running an SQL statement, 75  
Perl program  
setting a look-and-feel type, 36  
supported types, 36  
including SQL statements, 76  
launching Neoview Script, 76  
running, 78  
M
Materialized views  
showing all materialized views in a schema, 57  
wild-card search, 117  
MODE command, 92  
Perl wrapper script  
description of, 74  
location of, 34  
POPULATE INDEX utility  
138 Index  
Download from Www.Somanuals.com. All Manuals Search And Download.  
description of, 134  
examples of, 75, 76  
Port number, default, 45  
PREPARE statement  
description of, 134  
examples of, 60  
SET commands, in a script file, 49  
SET HISTOPTcommand, syntax of, 102  
SET IDLETIMEOUT command  
example of, 53  
syntax of, 103  
SET LIST_COUNT command, syntax of, 106  
SET MARKUP command, syntax of, 104  
SET PARAM command  
examples of, 61  
Product banner, 51  
Prompts  
continuation, 51  
standard, 51  
syntax of, 107  
PRUN  
SET PROMPT command  
example of, 53  
syntax, 95  
Python command line  
invoking Neoview Script, 74  
running an SQL statement, 75, 76  
Python program  
syntax of, 109  
SET SCHEMA statement  
description of, 134  
example of, 55, 68  
including SQL statements, 76  
launching Neoview Script, 76  
running, 78  
SET SQLPROMPT command, syntax of, 110  
SET SQLTERMINATOR command  
example of, 54  
Python wrapper script  
description of, 74  
location of, 34  
syntax of, 112  
SET TIME command  
examples of, 53  
syntax of, 112  
Q
SET TIMING command  
examples of, 54  
QUIT command, 97  
syntax of, 113  
R
SHOW COLSEP command, syntax of, 113  
SHOW HISTOPT command, 114  
SHOW IDLETIMEOUT command  
example of, 53  
RECONNECT command, syntax of, 98  
REORG command  
description of, 134  
example of, 76  
syntax of, 114  
REPEAT command, 98  
RESET PARAM command  
examples of, 61  
SHOW LIST_COUNT command, syntax of, 115  
SHOW MARKUP command, 115  
SHOW MODE command, syntax of, 116  
SHOW MVGROUPS command, syntax of, 116  
SHOW MVS command  
example of, 57  
syntax of, 99  
RUN command, syntax of, 100  
S
syntax of, 117  
Sample script files, 34  
SAVEHIST command, syntax of, 101  
Schema  
SHOW PARAM command  
example of, 61  
syntax of, 118  
setting the current schema, 55  
showing all schemas in the default catalog, 56  
showing the current schema, 55  
wild-card search, 121  
SHOW PREPARED command, syntax of, 119  
SHOW SCHEMA command  
example of, 55  
syntax of, 120  
Script file  
SHOW SCHEMAS command  
example of, 56  
comments, 67  
creating, 67  
syntax of, 120  
example of, 68  
SHOW SESSION command, syntax of, 122  
SHOW SQLPROMPT command, 123  
SHOW SQLTERMINATOR command, 124  
SHOW SYNONYMS command  
example of, 57  
running multiple files in parallel, 69  
running one file at a time, 68  
running when launching Neoview Script, 48  
SELECT statement  
description of, 134  
syntax of, 124  
example of, 59, 75  
SHOW TABLE command  
example of, 56  
Session  
See Neoview Script session, 53  
SESSION command, syntax of, 122  
SET COLSEP command, syntax of, 101  
syntax of, 125  
SHOW TABLES command  
example of, 56  
139  
Download from Www.Somanuals.com. All Manuals Search And Download.  
syntax of, 127  
REORG command, 134  
REVOKE statement, 134  
ROLLBACK WORK statement, 134  
SELECT statement, 134  
SET SCHEMA, 134  
SHOW TIME command, 128  
SHOW TIMING command, 129  
SHOW VIEWS command  
example of, 57  
syntax of, 129  
SET TABLE TIMEOUT statement, 134  
SET TRANSACTION statement, 134  
UPDATE statement, 134  
UPDATE STATISTICS statement, 134  
SQL terminator  
SPOOL command  
examples of, 64  
syntax of, 130  
Spooling (see Logging output)  
SQL mode, 92  
setting, 54  
SQL parameters  
showing, 54  
displaying, 61  
SQL utilities, 133  
resetting, 61  
SQLPlus look and feel, 36  
Standard prompt  
setting, 61  
SQL statement  
customizing, 53  
description of, 51  
breaking across lines, 52  
displaying the elapsed time, 54  
editing, 87  
displaying the current time, 53  
Synonyms  
preparing and executing, 60  
repeating, 59, 98  
showing all synonyms in a schema, 57  
wild-card search, 124  
running in a Perl or Python program, 76  
running in the Neoview Script interface, 59  
running on a Perl or Python command line, 75  
running when launching Neoview Script, 48  
terminating, 52  
T
Tables  
showing all tables in a schema, 56  
wild-card search, 128  
TDM_Default_DataSource, 46  
Teradata look and feel, 36  
Timeout, idle session, 53  
Transaction, example of, 64  
Type 4 driver  
SQL statements, supported in Neoview Script  
ALTER MVGROUP statement, 133  
ALTER SYNONYM statement, 133  
ALTER TABLE statement, 133  
ALTER TRIGGER statement, 133  
ALTER VIEW statement, 133  
BEGIN WORK statement, 133  
COMMIT WORK statement, 133  
CREATE INDEX statement, 133  
CREATE MATERIALIZED VIEW statement, 133  
CREATE MVGROUP statement, 133  
CREATE SCHEMA, 133  
See JDBC driver, 26  
U
UNIX launch file, location of, 34  
UPDATE STATISTICS statement  
description of, 134  
example of, 76  
CREATE SYNONYM statement, 133  
CREATE TABLE, 133  
CREATE TRIGGER statement, 133  
CREATE VIEW statement, 133  
DELETE statement, 133  
User profile  
setting _JAVA_OPTIONS, 39  
setting login environment variables, 74  
setting the PATH, 26, 44  
Utilities, 133  
DROP INDEX statement, 133  
DROP MATERIALIZED VIEW statement, 133  
DROP MVGROUP statement, 133  
DROP SCHEMA statement, 133  
DROP SYNONYM statement, 133  
DROP TABLE statement, 133  
DROP TRIGGER statement, 133  
DROP VIEW statement, 133  
EXECUTE statement, 133  
GRANT statement, 133  
V
VERSION command, syntax of, 131  
Views  
showing all views in a schema, 57  
wild-card search, 129  
W
Wild-card characters, 116  
Wild-card search  
materialized views, 117  
schemas, 121  
INSERT statement, 134  
LOCK TABLE statement, 134  
MAINTAIN command, 134  
POPULATE INDEX utility, 134  
PREPARE statement, 134  
PURGEDATA utility, 134  
synonyms, 124  
tables, 128  
views, 129  
Windows launch file, location of, 34  
140 Index  
Download from Www.Somanuals.com. All Manuals Search And Download.  
141  
Download from Www.Somanuals.com. All Manuals Search And Download.  
Download from Www.Somanuals.com. All Manuals Search And Download.  

Graco Car Seat ISPC001BA User Manual
Graco Car Seat PM 1373AD User Manual
Greenheck Fan Fan SQ BSQ User Manual
GSW Water Heater Signature Series Electric User Manual
Harbor Freight Tools Clock 94738 User Manual
Hasbro Video Game Console 7 832 User Manual
HP Hewlett Packard Laptop 443562 001 User Manual
Huffy Fitness Equipment P N 21147703 User Manual
Hypertec Mouse 260Euro User Manual
Hypertec Mouse Z10288ZHY User Manual