Neoview Command Interface (NCI) Guide (R2.5)

2 Installing and Configuring NCI

• “Installing NCI” (page 25)

• “Setting the Look and Feel of NCI” (page 25)

• “Testing the Launch of NCI” (page 29)

Installing NCI

To install NCI, follow the procedures in the README for the HP Neoview Command Interface (NCI).

Setting the Look and Feel of NCI

To determine the look and feel of NCI, set the -DhpnciLF property 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 execute

in NCI. Each look-and-feel type accepts all the SQL statements, commands, and syntax that NCI

currently supports.

Supported Look-and-Feel Types

Currently, NCI 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 Command Interface 2.5

Connected to DataSource: TDM_Default_DataSource

SQL>create view persnl.salarylist

+>as select salary from persnl.employee;

--- SQL operation complete.

SQL>

To display the SQL status messages in SQLPlus look and feel, the -DhpnciLF property value

is set to SQLPlus. The SQLPlus look and feel appears as shown below:

Picked up _JAVA_OPTIONS: -DhpnciLF=SQLPlus

Welcome to the HP Neoview Command Interface 2.5

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 Oracle is supported for backward compatibility.

The -DhpnciLF property value for setting the Teradata look and feel is BTEQ. Setting this

property results in a Teradata personality for the status messages logged for all SQL operations

within NCI. The Teradata look and feel appears as shown below:

Picked up_JAVA_OPTIONS: -DhpnciLF=BTEQ

LP. Connected to DataSource: TDM_Default_DataSource

SQL>set schema sch;

Installing NCI 25