SQL/MX Quick Start (H06.04+, J06.03+)

Welcome to MXCI and the Sample Database

HP NonStop SQL/MX Quick Start—540438-001

1-5

DEPT Table

Dept/Num Dept/Name Mgr Rpt/Dept Location

-------- --------- --- -------- -------------

1000 FINANCE 23 9000 CHICAGO

1500 PERSONNEL 213 1000 CHICAGO

2000 INVENTORY 32 9000 LOS ANGELES

2500 SHIPPING 234 2000 PHOENIX

3000 MARKETING 29 9000 NEW YORK

3100 CANADA SALES 43 3000 TORONTO

3200 GERMNY SALES 39 3000 FRANKFURT

3300 ENGLND SALES 72 3000 LONDON

3500 ASIA SALES 111 3000 HONG KONG

4000 RESEARCH 65 9000 NEW YORK

4100 PLANNING 87 4000 NEW YORK

9000 CORPORATE 1 9000 CHICAGO

For more information about the tables in the sample database, see the SQL/MX

Reference Manual.

Installing the setmxdb Script

The OSS installation script, setmxdb, creates and populates the sample database and

is provided as a pax file, T0517PAX, in the temporary OSS installation subvolume

$SYSTEM.ZOSSUTL. The pax file is a multifile archive file that is created by the pax

utility on UNIX-compatible systems. For OSS, pax files provide the form by which

product files are distributed for installation.

If OSS has been installed and the Manage OSS files option has been selected,

DSM/SCM automatically extracts the setmxdb script from the pax file and installs it in

the /usr/tandem/sqlmx/bin directory.

If the files are not present in this directory, DSM/SCM might not be configured to

extract the files automatically. In this case, you must extract the files manually:

1. At the TACL prompt, change to the $SYSTEM.ZOSSUTL subvolume:

volume $system.zossutl

2. Use the copyoss command to extract the files:

run copyoss t0517pax

3. In OSS, verify that the setmxdb and readme files were extracted to the

/usr/tandem/sqlmx/bin directory.

Note. To install the SQL/MX Release 2.x setmxdb script, you must have a license for the use

of SQL/MX DDL statements. To acquire the license, you must purchase product T0394. If you

did not purchase T0394 and you try to install setmxdb, an error message informs you that the

system is not licensed. If the system is not licensed, see Using a SQL/MX Release 1.8

setmxdb Script in a SQL/MX Release 2.x Environment on page 1-9.