Communicator e3000 MPE/iX Release 7.0 Express 1 (Software Release C.70.01) (30216-90328)

136 Chapter6
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.20 contains enhancements that were
requested by customers thru the SIGIMAGE User's Group. These enhancements are
• Progress Reporting Feature,
• the VERBOSE and TERSE Commands,
• the expanded SHOW command,
• 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.
Progress Reporting Feature
QUERY/iX has been enhanced to perform Progress Reporting during long database
retrievals. In a FIND, SUBSET, or MULTIFIND command that takes longer than a set
time interval, if VERBOSE messages have been enabled, a message will be displayed upon
each timeout reporting the progress QUERY/iX has made in processing the command. The
messages look like:
aaa ENTRIES AFTER bbb RECORDS OUT OF ccc IN STEP ddd OF eee
Example 6-1. Entries
15 ENTRIES AFTER 12345 RECORDS OUT OF 76000 IN STEP 1 of 3
295 ENTRIES AFTER 54321 RECORDS OUT OF 76000 IN STEP 1 OF 3
123 ENTRIES AFTER 234 RECORDS OUT OF 345 IN STEP 2 OF 3
0 ENTRIES AFTER 12 RECORDS OUT OF 576 IN STEP 3 OF 3
The default time interval for the progress messages is thirty (30) seconds. This may be
changed by an MPE command :SETVAR HP_QUERY_PROGRESS_INTERVAL nnnn
(even while in QUERY/iX) where nnnn is the integer number of seconds from 1 to 65000.
A zero value will revert to the default interval of 30 seconds. Negative values are reserved
for testing and will cause VERBOSE mode to be ENABLED and a report message
generated every -nth occurrence of checks for a timeout.
For most messages, the maximum records to be accessed (value ccc above) are reported as
the dataset capacity. For some retrievals where the capacity is unknown, the maximum of
2147483647 will be reported. This may occur on Third-Party Indexing packages or Btree
databases. For MULTIFIND commands, there may be multiple steps and is some cases
the maximum records will be reported as the sum of previously found records. The step