HP 3000 Manuals HP 3000 Manuals
HP IMAGE/SQL: with TurboIMAGE/XL and Query Enhancements
by Bharati V. Desai
Commercial Systems Division
What is HP IMAGE/SQL?
HP IMAGE/SQL is the next generation version of TurboIMAGE/XL. It is an
enhanced combination of TurboIMAGE/XL and what was formerly known as
ALLBASE/Turbo CONNECT (ATC). HP IMAGE/SQL provides relational access to
your TurboIMAGE/XL data using the industry-standard Structured Query
Language (SQL) and now includes both read and write capability using ANSI
standard functionality. ATC provided only read capability.
Closely tuned to the architecture of Hewlett-Packard computers, HP
IMAGE/SQL gives you flexibility in designing and using new SQL database
applications on a small or large scale. At the same time, you can
continue to use your existing TurboIMAGE/XL applications without any
noticeable differences. You do not have to convert, recompile, or make
changes to your existing applications. Your TurboIMAGE/XL database can
now be accessed simultaneously by SQL applications as well as by your
existing TurboIMAGE/XL applications. If you want, you can continue to
enhance your existing TurboIMAGE/XL applications or even develop new
ones.
HP IMAGE/SQL includes the client/server components HP ALLBASE/PC API and
ALLBASE/NET. PC client applications using industry-standard SQL can
therefore use HP IMAGE/SQL to access TurboIMAGE/XL data on an HP 3000
host system. With the increased usage of PCs and rapid adoption of
client/server technology, HP IMAGE/SQL extends the availability of your
TurboIMAGE/XL data to report writers, 4GLs, and other applications
running on a PC network.
To summarize, you benefit in the following ways:
* By leveraging your investment.
Your existing investment in TurboIMAGE/XL is preserved while you
take advantage of relational technology.
* By accessing new tools not previously available to TurboIMAGE/XL
users.
The purchasable SQL client/server tools allow you to view data
from TurboIMAGE/XL, ALLBASE/SQL, or third-party databases.
* By benefiting from productivity gains.
SQL uses a common interface to access TurboIMAGE/XL, ALLBASE/SQL,
and third-party SQL databases. Productivity improves when you can
use the same interface to access different types of databases.
Components of HP IMAGE/SQL
HP IMAGE/SQL includes TurboIMAGE/XL, certain components of ALLBASE/SQL,
and a database administration tool called IMAGESQL (formerly known as
ATCUTIL) that links them together. The components of HP IMAGE/SQL are:
TurboIMAGE/XL A set of programs and procedures to create and
maintain TurboIMAGE/XL databases.
ALLBASE/SQL ALLBASE/SQL components such as Interactive Structured
Query Language (ISQL), SQLUtil, SQLGEN, and
preprocessors to provide relational access to
TurboIMAGE/XL databases.
ISQL lets you enter SQL statements at the keyboard
and observe query results, messages, and other
information on a video display. ISQL is the main
tool for HP IMAGE/SQL programmers and database
administrators to create and modify DBEnvironments,
load and unload data, and enter SQL queries.
SQLUtil is a database administrator's tool for
maintaining relational database environments.
SQLGEN is a database administrator's tool that
generates the commands to recreate all or part of the
existing database environment. These commands can
later be used to recreate the database environment.
Preprocessors are tools to convert C, COBOL, FORTRAN,
or Pascal source programs containing SQL statements
into source code that can be compiled.
HP ALLBASE/SQL PC Software that provides access to ALLBASE/SQL and
API TurboIMAGE/XL databases residing on HP-PA RISC
database servers from a Microsoft window-based PC.
You need to use one of several available PC
client/server or decision support tools to build your
application or query.
ALLBASE/NET Works with HP ALLBASE/SQL PC API to connect users
with databases residing on an HP 3000 server.
IMAGESQL A database administrator's tool, formerly known as
ATCUTIL, to manage TurboIMAGE/XL databases in a
relational access environment.
Information Access A component of the Hewlett-Packard Information Access
Server SQL/iX and is the HP 3000-based data server.
How Do You Get HP IMAGE/SQL?
HP IMAGE/SQL is available to TurboIMAGE/XL customers through the HP
IMAGE/SQL upgrade program. You must have TurboIMAGE/XL on your support
contract to get HP IMAGE/SQL. If you purchase a new HP-PA RISC computer
system, you will automatically get HP IMAGE/SQL.
The HP IMAGE/SQL upgrade program is a special limited time offering to
provide the HP IMAGE/SQL upgrade to customers through their support
contract. It is formally offered until every customer has had an
opportunity to renew his/her contract for HP IMAGE/SQL. This program is
the result of extensive customer requests through SIGIMAGE user groups
and responses to a worldwide Interex customer survey, which indicated
that 80 percent of Hewlett-Packard support customers would prefer to buy
an HP IMAGE/SQL upgrade product through a support price increase. User
level support price increases were established and modified based on
customer responses and sensitivity to proposed price increases.
A letter was sent to all existing support customers from Hewlett-Packard
and the Interex user group explaining the addition of HP IMAGE/SQL
upgrade support to every support agreement at quote renewal time.
At your support renewal time, you will receive a quote reflecting the HP
IMAGE/SQL upgrade and the addition of support at the MPE/iX user level.
You have an option to accept or decline the offer.
Monthly support price increases are based on MPE/iX user levels. You may
choose to lower your MPE/iX user level license to more accurately reflect
current operating environments. This provides a lower HP IMAGE/SQL
upgrade support price.
You can receive HP IMAGE/SQL prior to your normal support contract
renewal or if you currently don't have TurboIMAGE/XL on your system. For
more information, call your sales representative or sales office in the
region.
Additional Information.
HP IMAGE/SQL can be automatically installed using HP AUTOINST.
The manuals included with HP IMAGE/SQL are:
* HP IMAGE/SQL Administration Guide (36385-90001)
* Getting Started With HP IMAGE/SQL (36385-90008)
* HP PC API User's Guide for ALLBASE/SQL and IMAGE/SQL (36216-90104)
TurboIMAGE/XL Enhancements
MPE/iX Release 5.0 includes significant enhancements to TurboIMAGE/XL,
which now constitutes a major component of HP IMAGE/SQL. A majority of
these enhancements have been requested by TurboIMAGE/XL users.
TurboIMAGE/XL version C.05.00 or later includes the following
enhancements:
* Dynamic Detail Data Set Expansion
* Dynamic Intrinsic Rollback
* Placement of Entries in DBPUT
* Transient Broken Chains
Dynamic Detail Data Set Expansion.
Dynamic detail data set expansion is one of the most frequently requested
enhancements for TurboIMAGE/XL. It allows a detail data set to be
expanded dynamically (up to a new maximum capacity specified in the root
file) during DBPUT when the detail data set space is exhausted. Unlike
before, your application will not terminate as often with the "Data Set
Full" error message when you use this new feature. However, to use this
enhancement, you must let TurboIMAGE/XL know of certain required
information such as the set's maximum capacity , initial capacity, and
the increment to be applied every time the capacity is exhausted. At
present, you can accomplish this by using any of the following methods:
1. When defining new databases, use the DBSCHEMA CAPACITY definition
statement to specify the new parameters. The syntax is as
follows:
C[APACITY]: maxcap [(blockfac)] [,initcap [,increment]];
The increment can either be the number of entries or the
percentage of the initial capacity by which the detail data set is
to be expanded each time its current allocation is exhausted. If
a percentage is used, the percent sign (%) must follow the
incremental amount. The data set capacity expansion information
is included in the DBSCHEMA summary table when using the $CONTROL
TABLE command.
2. For existing databases, use DBChange Plus or other third-party
tools such as ADAGER, DBGENERAL, or FLEXIBASE to specify the
expansion parameters.
For more information about DBChange Plus, refer to the article
"DBChange Plus Enhancements" in this Communicator.
To facilitate the dynamic detail data set expansion enhancement, DBUTIL
and some of the TurboIMAGE/XL intrinsics are enhanced as follows:
* DBUTIL
DBUTIL now offers a new SHOW CAPACITY command and an enhanced SHOW
database ALL command. The SHOW CAPACITY command displays capacity
related information for all sets, master as well as detail, and
whether or not the dynamic expansion feature is specified for a
set. The SHOW database ALL command now includes information on
whether or not the database uses this new feature and information
on the number of detail sets specified for the feature.
* DBINFO
DBINFO now offers one additional mode, 205, to allow users to
obtain information on dynamic data set capacity expansion
programmatically. The new mode 205 is an extension of mode 202 to
include dynamic capacity expansion information, such as maximum
capacity, initial capacity, incremental number of entries,
incremental percent and the dynamic capacity expansion flag (0 for
off and 1 for on) for the data set. Mode 205 can be used for a
master or detail data set.
* DBPUT
When a detail set reaches end of the current allocation and the
dynamic capacity expansion is specified, TurboIMAGE/XL attempts to
expand the data set by the incremental amount. If the expansion
is successful, the new record is added to the database. If not
successful, an error message is displayed.
* DBERROR and DBEXPLAIN
DBERROR and DBEXPLAIN are enhanced to give new error messages
pertaining to the new dynamic expansion feature.
* Dynamic Intrinsic Rollback
This enhancement is an extension of the existing dynamic rollback
(DBX) feature that was first released in MPE/iX Release 3.0. The
feature introduced three new intrinsics: DBXBEGIN, DBXEND, and
DBXUNDO. In brief, DBXBEGIN is used to start a dynamic
transaction, DBXEND is used to end it, and DBXUNDO is used within
the dynamic transaction to dynamically rollback the entire
transaction. An example of a dynamic transaction depicting
current functionality is as follows:
DBLOCK
DBXBEGIN
DBINFO
IF Error then Handle'Error
DBFIND
IF Error then Handle'Error
DBGET
IF Error then Handle'Error
DBUPDATE
IF Error then DBXUNDO'And'Leave'DBX
DBPUT
IF Error then DBXUNDO'And'Leave'DBX
DBGET
IF Error then Handle'Error
DBDELETE
IF Error then DBXUNDO'And'Leave'DBX
DBPUT
IF Error then DBXUNDO'And'Leave'DBX
DBXEND
DBUNLOCK
As shown in the above example, if any modify intrinsic (DBPUT, DBDELETE,
DBUPDATE) fails within a dynamic transaction, the entire dynamic
transaction must be rolled back; that is, all modify intrinsics completed
so far in that transaction must be undone. The user is restricted to use
DBXUNDO to rollback the entire transaction and the only intrinsics
allowed subsequently within that transaction are DBXUNDO, DBERROR, or
DBEXPLAIN.
Currently, TurboIMAGE/iX allows the entire dynamic transaction to
complete successfully only when it does not encounter any of the
following:
* Failure of a modify intrinsic (DBPUT, DBDELETE, DBUPDATE).
* Use of DBUNLOCK inside a dynamic transaction when DBUNLOCK is
preceded by a modify intrinsic within this dynamic transaction.
In other words, DBUNLOCK is permitted if the database is not
updated after the onset of the dynamic transaction.
* Use of DBCLOSE modes 1 and 2 inside a dynamic transaction.
* Program abort during an active dynamic transaction.
* System abort during an active dynamic transaction.
* Unexpected errors encountered by XM.
* Stalled transaction. This generally occurs when an application
has an extremely large dynamic transaction causing it to exhaust
its limit of XM log file space. The limit of 1MB, 2MB, and 4MB
varies depending on the MPE/iX release.
All conditions other than the above simply return appropriate errors, as
intrinsics outside a dynamic transaction would do, and do not enforce
using DBXUNDO. The fate of the dynamic transaction rests more or less
with the application designer.
As requested, Hewlett-Packard now offers more flexibility and control to
the application designer in deciding the fate of the dynamic transaction
when a modify intrinsic fails, when DBCLOSE mode 2 is used, or when
DBUNLOCK is used. This enhancement, Dynamic Intrinsic Rollback, is also
known as Local Rollback. It signifies that unlike before, only the
failed modify intrinsic is rolled back automatically by TurboIMAGE/XL;
therefore, you will not have to use DBXUNDO. With the new feature, you
now have the following options when a modify intrinsic, DBCLOSE mode 2,
or DBUNLOCK fails within the dynamic transaction:
* Use DBXEND to end the dynamic transaction.
* Continue with the remainder of the dynamic transaction (keep in
mind, the failed intrinsic did not complete).
* Use DBXUNDO as before to rollback the entire dynamic transaction.
There have been no changes to the externals of any intrinsic. The failed
intrinsics will return the same error codes as before. You must verify
success or failure of the intrinsic and take the appropriate action.
There are still some exceptions that will trigger an abort of the entire
dynamic transaction. They are:
1. DBCLOSE mode 1 inside a DBX
2. Stalled transaction
3. Unexpected errors encountered by Transaction Management (XM)
4. Program abort
5. System abort
This enhancement is done in conjunction with the XM enhancements in
MPE/iX Release 5.0. Hence, your system must be upgraded to MPE/iX
Release 5.0 to use this extended feature. If you use TurboIMAGE/XL
version C.05.00 or later on any MPE/iX releases prior to 5.0, the dynamic
transaction feature will continue to work as before.
Placement of Entries in DBPUT.
As requested by many TurboIMAGE/XL users, DBPUT is now enhanced to give
you more control on where the new entry is to be placed first, either at
a free spot indicated by the delete chain head, as currently done, or to
place it at the high-water mark.
At present, DBPUT first checks the delete chain head, and if it is empty,
DBPUT places the new entry at the high-water mark. This enhancement
allows you to reverse the sequence by giving you the option to place the
entry at the high-water mark first. Then, after the high-water mark
reaches the file limit, DBPUT will start using the delete chain head.
To facilitate this new feature, DBUTIL introduces a new option HWMPUT for
its ENABLE and DISABLE commands. When HWMPUT is enabled, DBPUT uses the
high-water mark first. The syntax is as follows:
ENABLE database FOR HWMPUT
DISABLE database FOR HWMPUT
To programmatically control this, DBCONTROL now offers two new modes, 9
and 10, to enable and disable this feature respectively, for the process
only. If HWMPUT is enabled using DBUTIL, all processes will take
advantage of this new feature. By default, HWMPUT remains disabled and
DBPUT places the new entry using the delete chain head.
There are two circumstances to be aware of when using this feature:
1. If HWMPUT is enabled, DBPUT will not inform you when DBPUT has
reached the end of file and has started using the delete chain
head.
2. When using DBRECOV to recover the database, DBRECOV uses the
current settings indicated by the root file. If you toggle the
high-water mark setting (HWMPUT) after storing the database for
roll-forward recovery and then have a long log cycle before
performing the recovery, DBRECOV will not be aware of the previous
HWMPUT setting(s) and may abort with a table overflow error.
Transient Broken Chains.
When you are performing chained reads without locking, TurboIMAGE/XL now
reduces the probability of condition word 18, which is a Broken Chain
error message.
There are cases when you may still get a condition word 18, such as when
the current record in the chain is deleted or placed in another chain by
another process performing updates.
Additional Information.
TurboIMAGE/XL, along with HP IMAGE/SQL, can be automatically installed
using HP AUTOINST. For more information on TurboIMAGE/XL enhancements,
refer to the Fifth Edition of TurboIMAGE/XL Database Management System
Reference Manual (30391-90001).
Query
QUERY provides a simple method of accessing TurboIMAGE databases without
programming effort. To keep pace with recent TurboIMAGE/XL enhancements,
QUERY version D.02.25 now includes the following enhancements:
* Third-party indexing enhancement
* New entry point, NOCI
Third-party Indexing Enhancement.
In MPE/iX Release 4.0, TurboIMAGE/XL introduced the third-party indexing
(TPI) enhancement. TPI is a seamless interface to the indexing products
of Dynamic Information Systems Corporation (DISC) and Bradmark
Technologies, Inc. Their products, OMNIDEX and SUPERDEX, respectively,
offer generic and keyword search capabilities through the standard
interface in TurboIMAGE/XL. You must have one of the above products
installed on your system to use the TPI enhancement.
QUERY version D.02.25 is enhanced to offer generic key and single or
multiple key searches using the standard TPI interface.
The external changes are made to the retrieval commands (FIND [ALL],
MULTIFIND [ALL], FIND CHAIN, JOIN, and SUBSET) and the FORM, SHOW, and
VERSION commands.
For the retrieval commands, QUERY now accepts a TPI item name anywhere a
TurboIMAGE item name can be specified.
The FORM command now includes TPI information, if any, for a data set.
In addition, the FORM command offers a new option, INDEXES, to obtain
third-party key information.
The SHOW command now provides a new INDEX option to identify the
third-party product configured for the database.
The VERSION command now includes information about the TPI products
installed on the system as shown below:
>version
QUERY D.03.00
TURBOIMAGE overall VUF:
HP30391C.05.05 TurboIMAGE/XL
TURBOIMAGE PROCEDURES:
.
.
.
TURBOIMAGE PROGRAMS FILES:
.
.
TURBOIMAGE REFERENCE MANUAL:
Edition 5 June 1994 30391C.05.00
THIRD PARTY INDEXING:
OMNIDEX Version: 3.00.87
SUPERDEX Version: 4.0
When no TPI product is installed on the system, the line "THIRD PARTY
INDEXING:" is not displayed.
For information on the syntax, use the HELP command.
New Entry Point NOCI.
You can now use the QUERY version D.02.25 and disable execution of MPE
commands within QUERY by using the new entry point, NOCI. For example:
RUN QUERY.PUB.SYS,NOCI
When using this new entry point, subsequent use of any MPE/iX command
from QUERY (with the exception of the
EOD command) will result in an INVALID COMMAND error. The EOD command
continues to be recognized as End-Of-File.