Communicator e3000 MPE/iX Release 7.0 (C.70.00) (30216-90312)

80 Chapter5
Technical Articles
QUERY/iX Enhancements Respond to User Requests
QUERY/iX Enhancements Respond to
User Requests
By James Overman
Enterprise Support Services Organization R&D
The newest release of QUERY/iX HP32216D.03.17 (and later) contains enhancements that
were requested by customers through the SIGIMAGE User's Group. These enhancements
are the support of the Expanded TurboIMAGE Limits and the Find-by-Record-Number
option.
In addition, QUERY/iX has been changed to allow the runtime PARM=%777 option that
invokes Business Basic Floating Decimal datatype on the Native Mode version of QUERY.
TurboIMAGE Expanded Limits
The support of the TurboIMAGE Limit Expansion allows for the increased number of
datasets from 199 to 240, the increased number of data items from 1023 to 1200, and the
increase in paths into a master dataset from 16 to 64. QUERY/iX will utilize the new
limits on systems with the TurboIMAGE version HP30391C.09.00 and later. If the new
DBUTIL option flag of OLDINFOLIMITS is enabled for a database, QUERY/iX will
function normally as it uses the new DBCONTROL Mode 20 to inform TurboIMAGE that
QUERY code supports the new expanded limits.
FIND by Record Number
The long requested Find-by-Record-Number enhancement has been implemented. This
new format of the FIND command permits the retrieval of a specific record in a dataset.
The form of the new feature is:
FIND [DATA BASE NAME:] DATA SET NAME.#RECORD NUMBER
The record number is preceded by a "#" and is the record offset into the dataset that is to
be retrieved. The record number may be a decimal number (the default) or an octal value
indicated by a "%" after the "#", or a hexadecimal value indicated by a "$".
For example, to read the fifteenth record in the dataset INVOICES, one could use any of
the following commands:
FIND INVOICES.#15
FIND INVOICES.#%17
FIND INVOICES.#$f
After a record is retrieved, all of the usual QUERY commands may be used on the record.
If the record number requested does not exist, QUERY will return a "NO ENTRY" or
"DIRECTED END OF FILE" followed by "0 ENTRIES QUALIFIED."