|
|
|
Table of Contents
- USING QUERY IN SESSION MODE
- Running QUERY
- Accessing Data
- Using the Break Key
- Using Control Y
- Exiting QUERY
- USING QUERY IN JOB MODE
- Discussion
- QUERY COMMANDS
- IDENTIFYING THE QUERY ENVIRONMENT
- LOCATING DATA
- MODIFYING DATA
- REPORTING DATA
- USING PROCEDURES IN A PROC-FILE
- USING QUERY COMMANDS FROM AN XEQ FILE
QUERY can be run in either session mode (interactive) or job
mode (batch). In session mode, QUERY issues command prompts, error
messages, and other messages of general interest to you. The manner
in which QUERY proceeds depends upon your responses to QUERY messages
and prompts. In job mode, QUERY reads commands and other input from
a job file and prints messages on the $STDLIST device.
Before accessing data in either session or job mode, you must
define the QUERY environment. After you define the environment,
you use QUERY to enter, replace, delete, retrieve, and report data
in the data base(s).
You can save a frequently used command as a named procedure
or a sequence of commands as an XEQ file. Procedures and XEQ files
allow you to execute commands repeatedly without re-entering the
commands. These features can be used in either session or job mode.
Note: In this manual, examples are shown in uppercase letters.
When using QUERY, you may use either upper or lowercase letters.
Passwords must be entered exactly as defined by the data base administrator.
The QUERY/iX product provides three executable programs that
implement the functionality as described in this manual. The first,
and most likely the one which users should run, is QUERY.PUB.SYS.
This program is always the latest standard release of the QUERY/iX
product. On releases prior to MPE/iX 6.0, this program was the
Compatibility Mode version of QUERY/iX. As of the MPE/iX 6.0 release,
QUERY.PUB.SYS is a Native Mode version which provides better performance
over the Compatibility Mode version, which is now found at QUERYCM.PUB.SYS.
QUERY.PUB.SYS no longer needs to be ALLOCATE'd for improved access
but users may want to ALLOCATE QUERYCM.PUB.SYS instead. The program
QUERYNM.PUB.SYS is generally the same as QUERY.PUB.SYS and is provided
for backward compatibility for those users who were using that version
rather than the older QUERY.PUB.SYS. Note that QUERY and QUERYNM
may diverge in features in the future and so users should employ QUERY.PUB.SYS
as the preferred program.
Generally, the QUERYCM program provides the same functionality
as QUERY but with some lower limits for internal tables. One exception
is that only the Compatibility Mode version may be run with a PARM=%777
to invoke a Business Basic Floating Decimal override, which treats
K1 and K2 datatypes as Floating Decimal datatypes. Otherwise, any
command, script, procedure, or report that runs with QUERYCM should
also run with QUERY (or QUERYNM) but the reverse may not be true
if the larger table sizes of the Native Mode versions are required.
|
Complete PDF