HP QUERY User manual

QUERY/V
Reference Manual
HP 3000 MPE/iX Computer Systems
ABCDE
HP Part No. 30000-90042
Printed in U.S.A. OCT 98
E1098

The information contained in this do cument is sub ject to change without notice.
HEWLETT-PACKARD MAKES NO WARRANTY OF ANY KIND WITH REGARD
TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. Hewlett-Packard shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance or use of this material.
Hewlett-Packard assumes no responsibilit y for the use or reliability of its software on
equipment that is not furnished by Hewlett-Packard.
This do cument contains proprietary information which is protected by copyright. All rights
are reserved. No part of this do cumentmay b e photo copied, repro duced or translated to
another language without the prior written consent of Hewlett-Packard Company.
c
 Copyright 1976, 1978, 1979, 1981, 1985-87,1998 HEWLETT-PACKARD COMPANY

PRINTING HISTORY
New editions are complete revisions of the man
ual. Up date packages, which are issued
between editions, contain additional and replacement pages to b e merged in
to the manual by
the customer. The dates on the title page c
hange only when a new edition or a new update
is published. No information is incorporated in
to a reprinting unless it appears as a prior
update; the edition do es not c
hange when an update is incorp orated.
The software code printed alongside the data indicates the v
ersion level of the softw
are
pro duct at the time the man
ual or up date w
as issued. Many pro duct updates and xes
do not require manual changes and, conversely, manual corrections may b e done without
accompanying pro duct changes. Therefore, do not expect a one-to-one corresp ondence
between product updates and man
ual updates.
First Edition Jun 1976 32216A.00.00
Update 1 Apr 1978 32216A.03.05
Update 2 May 1979 32216A.04.01
Update 2 Incorporated May 1979 32216A.04.01
Second Edition Nov 1981 32216B.00.00
Third Edition Dec 1985 32216C.00.00
Update 1 Apr 1986 32216C.00.00
Update 1 Incorporated May 1986 32216C.00.00
Fourth Edition May 1987 32216C.00.08
Update Oct 1998 Converted to SGML format
PREFACE
This manual describes QUERY/V, the Hewlett-Packard Data Base Inquiry Facility which
is designed to run under the control of the HP 3000 Multiprogramming Executive (MPE)
Operating System. QUERY/V enables you to access data in IMAGE data bases without
writing a computer program.
In order to use QUERY, you should know enough ab out the MPE Operating System to start
a job or op erate in session mo de. It is recommended that you read an introductory b o ok to
the HP 3000 systems if you are not an exp erienced MPE user. Knowledge of EDIT/3000 is
useful for some QUERY techniques but is not required to op erate QUERY.
This manual documents QUERYversions B.01.01 and later. Information on Native Language
Support (NLS) and the IMAGE data types I4, J4, and K2 has b een added to this edition.
NLS is supported on QUERYversions B.01.00 and later, and the IMAGE data types I4, J4,
and K2 are supported on QUERYversions C.00.00 and later. Information which is sp ecic to
a particular version of QUERY (B.01.01 or later) is noted throughout this manual.
This manual is arranged in three sections and seven app endices. Section 1 introduces QUERY
terminology, briey describ es IMAGE data bases, and discusses other imp ortant general
IMAGE, QUERY, and MPE concepts. Section 2 illustrates op erating QUERY in session
or job mo de and discusses the functions of QUERY and the commands which are used
iii

to p erform them. Appendix A con
tains all QUERY messages. Appendix B lists helpful
information on numeric limits of QUERY commands and discusses the les used b
y QUERY
during execution. Appendix C describ es three w
ays to access a data base on a remote HP
3000. Appendix D discusses Native Language Supp ort. Appendix E discusses self-describing
les. App endix F discusses user-dened pro cedures and giv
es examples in programming
languages. Appendix G lists the ASCII c
haracter set.
In addition to this manual, you may need to consult the following man
uals:
TurboIMAGE/XL Database Management System Reference Manual *
IMAGE/SQL Adminstration Guide *
MPE/iX Commands Reference Manual
Using NS3000/iX Network Services
Native Language Programmer's Guide
Throughout this manual, no distinction is made bet
ween TurboIMAGE/XL and
IMAGE/SQL. These manuals are both referenced as the
IMAGE Reference Manual .
The QUERY pro duct is now referred to as QUERY/V. In previous editions of this manual,
the QUERY pro duct was called QUERY/3000. This edition of the QUERY/V Reference
Manual do cuments the C.00.08 version of QUERY.
iv

Contents
1. INTRODUCING QUERY/V
STRUCTURE OF THE DATA BASE . . . . . . . . . . . . . . . . . . 1-2
Fully-Qualied Data Item Names . . . . . . . . . . . . . . . . . . . 1-3
Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Data Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Literals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Comp ound Data Items . . . . . . . . . . . . . . . . . . . . . . . 1-6
Data Set Relations . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Sample Data Base . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
MODES OF ACCESS . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Logging and Mo de Selection . . . . . . . . . . . . . . . . . . . . . 1-11
PASSWORDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
QUERY CHARACTER SET . . . . . . . . . . . . . . . . . . . . . . 1-11
MPE FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
2. USING QUERY/V
USING QUERY IN SESSION MODE . . . . . . . . . . . . . . . . . . 2-1
Running QUERY.. . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Accessing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Using the Break Key . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Using Control Y . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Exiting QUERY . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
USING QUERY IN JOB MODE . . . . . . . . . . . . . . . . . . . . 2-3
Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
QUERY COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . 2-5
IDENTIFYING THE QUERY ENVIRONMENT . . . . . . . . . . . . . 2-8
LOCATING DATA . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
MODIFYING DATA . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
REPORTING DATA . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
USING PROCEDURES IN A PROC-FILE . . . . . . . . . . . . . . . . 2-12
USING QUERY COMMANDS FROM AN XEQ FILE . . . . . . . . . . 2-13
3. QUERY/V COMMANDS
ALTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
ASSIGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
CLOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
COMMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
CREATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
CREATE SPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
DATA-BASE= . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
DATA-SETS= . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
DBLIST= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Contents-1

DEFINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
DESTROY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
DISPLAY LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
FIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
FIND ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
FIND CHAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
FIND pro cedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
FORM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48
HELP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
JOIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
JOIN pro cedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
LANGUAGE= . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
LISTREDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
MODE= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
MULTIDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
MULTIFIND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
MULTIFIND ALL . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
MULTIFIND pro cedure . . . . . . . . . . . . . . . . . . . . . . . . 3-84
OUTPUT= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
PASSWORD= . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88
PROC-FILE = . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90
REDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92
RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
RENAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96
REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
REPORT ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130
REPORT pro cedure . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134
SAVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136
SETLOCKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137
SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138
SUBSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139
SUBSET pro cedure . . . . . . . . . . . . . . . . . . . . . . . . . . 3-142
TRANSBEGIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143
TRANSEND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-144
TRANSMEMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-145
UNDO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-146
UPDATE ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-147
UPDATE DELETE . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151
UPDATE REPLACE . . . . . . . . . . . . . . . . . . . . . . . . . 3-153
UPDATE procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 3-157
VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-159
XEQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-160
Contents-2

A. QUERY/V MESSAGES
B. QUERY/3000 SPECIFICATIONS
LIMITS USED BY QUERY . . . . . . . . . . . . . . . . . . . . . . B-1
FILES USED BY QUERY. . . . . . . . . . . . . . . . . . . . . . . B-3
C. ACCESSING A REMOTE DATA BASE
METHOD 1: QUERY ON REMOTE SYSTEM . . . . . . . . . . . . . C-1
METHOD 2: QUERY ON LOCAL SYSTEM . . . . . . . . . . . . . . C-2
METHOD 3: USING A DATA-BASE-ACCESS FILE . . . . . . . . . . . C-4
D. NATIVE LANGUAGE SUPPORT
EFFECTS OF NLS ON QUER
Y . . . . . . . . . . . . . . . . . . . . D-2
E. SELF-DESCRIBING FILES
FILE DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
USER LABELS . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Global Information Label F
ormat . . . . . . . . . . . . . . . . . . . E-2
Item Description Lab el Format . . . . . . . . . . . . . . . . . . . . E-2
ITEM NAMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
F. USER-DEFINED PROCEDURES
Pro cedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-1
Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-5
MPROC Pro cedure . . . . . . . . . . . . . . . . . . . . . . . . . F-5
SPL - MPROC Pro cedure . . . . . . . . . . . . . . . . . . . . . . F-6
COBOL - MPROC Pro cedure . . . . . . . . . . . . . . . . . . . . F-8
COBOL Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . F-10
PASCAL - MPROC Pro cedure . . . . . . . . . . . . . . . . . . . . F-10
PASCAL Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . F-13
Additional Comments . . . . . . . . . . . . . . . . . . . . . . . . F-14
FORTRAN - MPROC Pro cedure . . . . . . . . . . . . . . . . . . . F-14
QPROC Pro cedure . . . . . . . . . . . . . . . . . . . . . . . . . F-16
SPL - QPROC Pro cedure . . . . . . . . . . . . . . . . . . . . . . F-16
COBOL - QPROC Pro cedure . . . . . . . . . . . . . . . . . . . . F-21
G. ASCII CHARACTER SET
Contents-3

Figures
1-1. ORDERS Data Base Structure . . . . . . . . . . . . . . . . . . . . 1-7
1-2. Sample Entry Values . . . . . . . . . . . . . . . . . . . . . . . . 1-7
1-3. IMAGE/QUERYEnvironments . . . . . . . . . . . . . . . . . . . . 1-10
2-1. Job Mo de Operation . . . . . . . . . . . . . . . . . . . . . . . . 2-4
3-1. FORM ITEMS Output . . . . . . . . . . . . . . . . . . . . . . . 3-49
3-2. FORM PATHS Output . . . . . . . . . . . . . . . . . . . . . . . 3-50
3-3. FORM SETS Output . . . . . . . . . . . . . . . . . . . . . . . . 3-50
3-4. FORM data item name Output . . . . . . . . . . . . . . . . . . . . 3-51
3-5. FORM data set name Output . . . . . . . . . . . . . . . . . . . . 3-51
3-6. FORM Output . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
3-7. General Rep ort Format . . . . . . . . . . . . . . . . . . . . . . . 3-100
3-8. Sample Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-101
3-9. Sample Output Using Numeric Edit Masks . . . . . . . . . . . . . . . 3-109
3-10. REPORT Pro cedure Named SHIPMNTS . . . . . . . . . . . . . . . 3-135
3-11. Billing Report From an XEQ File . . . . . . . . . . . . . . . . . . . 3-162
C-1. Using Metho d 1 . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
C-2. Using Metho d 2 . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
C-3. Using Metho d 3 . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Contents-4

Tables
1-1. Data Item Types and Values . . . . . . . . . . . . . . . . . . . . . 1-5
2-1. Command Categories and Functions . . . . . . . . . . . . . . . . . . 2-6
2-2. Pro cedure Commands . . . . . . . . . . . . . . . . . . . . . . . . 2-12
2-3. Commands Used to Dene Pro cedures . . . . . . . . . . . . . . . . . 2-13
3-1. FIND Command Relational Operators . . . . . . . . . . . . . . . . . 3-33
3-2. MATCHING Pattern Operators . . . . . . . . . . . . . . . . . . . 3-40
3-3. LIST Command Relational Operators . . . . . . . . . . . . . . . . . 3-68
3-4. Field Widths of Data Item T
ypes . . . . . . . . . . . . . . . . . . . 3-69
3-5. REPORT Statements . . . . . . . . . . . . . . . . . . . . . . . . 3-98
3-6. REPORT StatementParameters . . . . . . . . . . . . . . . . . . . 3-98
3-7. Numeric Edit Mask Characters . . . . . . . . . . . . . . . . . . . . 3-108
3-8. Numeric Edit Mask Combinations . . . . . . . . . . . . . . . . . . . 3-109
3-9. REPORT ALL Options . . . . . . . . . . . . . . . . . . . . . . . 3-131
3-10. Overpunch Characters . . . . . . . . . . . . . . . . . . . . . . . . 3-131
3-11. Output of P and Z Type Values . . . . . . . . . . . . . . . . . . . 3-132
3-12. Retrieval Command Relational Op erators . . . . . . . . . . . . . . . 3-140
B-1. General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B-2. JOIN Command . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B-3. LIST Command . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B-4. PROC-FILE Command . . . . . . . . . . . . . . . . . . . . . . . B-1
B-5. REPORT Command . . . . . . . . . . . . . . . . . . . . . . . . B-2
B-6. Retrieval Command (FIND, MULTIFIND, SUBSET) . . . . . . . . . . B-2
B-7. SAVE Command . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
B-8. TRANSMEMO Command . . . . . . . . . . . . . . . . . . . . . . B-2
B-9. Up dating Command (UPDATE ADD and UPDATE REPLACE) . . . . . B-3
B-10. Files Equated by the User . . . . . . . . . . . . . . . . . . . . . . B-3
B-11. Files Not Equated by the User (Temp orary Files) . . . . . . . . . . . . B-3
B-12. Files Created by the User and/or Sp ecied to be Built b
y QUERY . . . . B-4
B-13. Unnamed Scratch Files (Temp orary Files) . . . . . . . . . . . . . . . B-4
D-1. Commands for Language-Dep endent Information . . . . . . . . . . . . D-2
Contents-5

1
INTRODUCING QUERY/V
QUERY/V provides a simple metho d of accessing IMA
GE data bases without programming
eort. You can use QUERY to do the following:
enter data
mo dify or delete data v
alues
retrieve data which meets selection criteria
report on the data retriev
ed
You perform these op erations b
yentering simple commands consisting of English k
eywords
such as FIND and REPORT. You can request information about the function, format, and
parameters of QUERY commands with the HELP command. All of the QUER
Y commands
are discussed in Section 3.
You only need to know the relationships of the data base elements and not the structure of
the disc les. You can request information ab out the structure of the data bases with the
FORM command. QUERY nds the data and p erforms the operations in resp onse to y
our
commands using the data base, data set, and data item names y
ou sp ecify.
QUERY can b e used either in session (in
teractive) mo de or job (batch) mode. If you are
using QUERYinteractively at a terminal, QUERY prompts you for commands, issues error
messages when an error o ccurs, and prin
ts other information of interest to you. You can
operate QUERY in job mo de as an MPE job from an input device. In job mo de, an
y error
messages are printed on the $STDLIST device which is usually a line printer.
QUERY adheres to all of the IMAGE security provisions described in the IMAGE Reference
Manual .You must enter a valid password for the data base you want to use. This password
determines which information you can access in the data base.
QUERY report formatting capabilities enable you to design reports with header and column
lab els, page numb ers, and group lab els. In addition, y
ou can sort entries through multiple
elds, as well as total, average, or count columns of numeric data values.
A sequence of commands can b e stored in a le and executed at any time byentering the
XEQ command as part of a session or a job. A frequently used or complex command can be
stored as an individual pro cedure in a le referred to as a Pro c-le. The pro cedure name can
then be used in place of the command parameters.
If your lo cal HP 3000 and a remote HP 3000 have Distributed Systems (DS/3000) capability,
you can use QUERY to access IMAGE data bases residing on the remote computer and
retrieve information to b e used on the lo cal system. Three metho ds of accessing a remote data
base are describ ed in Appendix C.
QUERY allows you to write your own user-dened pro cedures in any programming language
which enable a report to p erform a sp ecialized function not provided by QUERY. Refer to
INTRODUCING QUERY/V 1-1

Appendix F for further discussion. All of the tasks except user-dened rep ort pro cedures can
be accomplished without programming.
If you are developing programs which access IMAGE data bases through the IMA
GE library
pro cedures, QUERY makes an excellent debugging aid. You can alter the data base con
tent
using your program and then use QUER
Y to examine the data and determine the results of
your programmed changes.
STRUCTURE OF THE DATA BASE
It is not necessary to understand all the IMA
GE features in order to use QUER
Y. However,
it is imp ortant to ha
ve a general idea of data base structure and kno
w the denitions of some
IMAGE terms which will be used in this man
ual.
Each item of information in a data base is referenced b
ya data item name. The name
asso ciates the information with c
haracteristics which describe it:
the type of information (n
umeric, alphanumeric, etc.)
its relation to other data in the data base
the passwords required to read and/or write the information
The data base designer organizes data items into data sets for the purpose of accessing them
as a group. For example, an employee data set could contain the items EMPID, F-NAME,
L-NAME, SOCSEC#, and SALARY. A credit union data set could contain EMPID,
AMOUNT, TRANSCODE, and so forth. Each data set is referenced bya data set name.
Each time you enter a new employee's record into the data base, you can supply a value for
each data item. This group of values is stored as a single data entry in the data set. For
example:
F-NAME SALLY
L-NAME MERTON
SOCSEC# 527-58-6492
SALARY 18000.02
QUERY allows you to lo cate particular entries whichhavevalues you specify.You can then
change the values or print them in a report. You can also add or delete an entire entry if your
password gives you the capability to write to each item in the data set.
You can use the FORM command to display the names of each data set to whichyou have
access and the names of the data items in those sets. Only the items to whic
hyou haveat
least read access are listed.
1-2 INTRODUCING QUERY/V

Fully-Qualified Data Item Names
If you are referring to a data item whic
h appears in more than one data set and/or data base,
you must specify which data set and data base to access. A particular data item can app ear
in more than one data set within a giv
en data base, and a particular data item can app ear in
more than one data base. Y
ou can sp ecify the data item in three w
ays:
by sp ecifying the data set through the D
ATA-SET= command and the data base through
the DBLIST= command.
by sp ecifying the data set through the DEFINE command (D
ATA-SETS= prompt) or
through the MULTIDB command (DATA-SETS= prompt).
by qualifying the data item name.
A fully-qualied data item name has the following form:
data base name:data set name.data item name
For example:
BADGE# is the name of a data item in the data set named LABOR whic
h is in a data
base named IRONCO. If BADGE# is also the name of a data item in a data set named
EMPLOYEE, which is also in the IRONCO data base, its fully-qualied name would be
IRONCO:EMPLOYEE.BADGE#.
Data Types
The data base designer denes each data item as a particular type, depending on what kind of
information is to b e stored in the item. A data item ma
y b e one of several types of integers,
real or oating-p ointnumbers, or ASCI I character information.
The FORM command can display the data typ e for each item. When using QUERY, you will
usually be unconcerned with the specic data type with the following exceptions:
when supplying values for an item, either to enter new information or to lo cate sp ecic
entries, you maywant to know the acceptable range of values for a numeric type item.
when creating rep orts you should be aware of the item types in order to format the rep ort
properly.
when using the QUERY registers while printing a rep ort, it is helpful to knowhow
calculations aect the register values.
Detailed information ab out each of these situations is given with the appropriate command in
Section 3. Table 1-1 contains a summary of the data item typ es and the range of acceptable
values for each.
INTRODUCING QUERY/V 1-3

Data Values
If you use QUERYtoenter a value for a data item of t
ype P (packed decimal), you should
be a
ware of the way QUERY handles the sign of the v
alue. A dierent co de is used for the
sign of a value entered with a plus sign than for a v
alue entered without a sign. Ho
wever,
when QUERY retrieves unsigned and p ositiv e t
ype P data items with the same v
alue, they are
considered to b e equiv
alent. For example, +2 and 2 are equiv
alent. Data items with values
+0, 0, and -0 are also equiv
alent.
Literals
When sp ecifying the v
alue of a particular data item, y
ou must sometimes surround the v
alue
with quotation marks. This t
ype of value is called a literal. A c
haracter or string literal
contains alphanumeric characters. For example:
"TANYA OAKLEY" "ZXR=93458273" "3215"
Character literals containing numeric values of the types listed under In
teger or Real in
Table 1-1 are called, more sp ecically
,numeric literals. For example:
"5468" "+408E-15" "-16.73892"
Rules for using quotation marks are described with the commands whic
h allow or require their
use.
1-4 INTRODUCING QUERY/V

Table 1-1. Data Item Types and V
alues
TYPE MINIMUM MAXIMUM
INTEGER
I1 -32768 +32767
I2 -2,147,483,648 +2,147,483,647
I4 +9,223,372,036,845,775,808 +9,223,372,036,854,775,807
J1 -9999 +9999
J2 -999999999 [phone]
J4 -999999999999999999 +999999999999999999
K1 0 +65535
K2 0 +4,294,967,295
Z n * -( n digit number) +( n digit number)
P n * -( n -1 digit number)'' +( n -1 digit number)''
REAL
R2 -1.157920 x 10
77
-0.863617 x 10
-77
+0.863617 x 10
-77
+1.157920 x 10
77
Largest accurate absolute integer
is 8,388,607 . (QUERY rounds to
6 digits when printing R2 values.)
R4 -1.157920892373161 x 10
77
-0.8636168555094445 x 10
-77
+0.8636168555094445 x 10
-77
+1.157920892373161 x 10
77
Largest accurate absolute integer
is 36,028,797,018,963,967 .
(QUERY rounds to 16 digits when
printing R4 values.)
CHARACTER
U n ** 1 ASCII character
(lower case not allowed)
n ASCII characters (lower case
not allowed)
X n ** 1 ASCII character'' n ASCII characters
Notes on Table 1-1.
* n cannot exceed 255 and must be even for type Z and evenly divisible by 4 for type P n .
QUERY rep orts print at most 20 digits for type Z and 19 digits for typ e P data values.
** n cannot exceed 255. QUERY rep orts print at most 136 characters for type U and X data
values.
INTRODUCING QUERY/V 1-5

Compound Data Items
IMAGE allows the data base designer to sp ecify comp ound data items. A compound data
item is one that occurs more than once in the same data en
try. Each occurrence of the data
item is called a sub-item. Eac
h sub-item can haveavalue, and QUERY can lo cate and update
any or all sub-items. If y
ou update only the rst sub-item, QUER
Y preserves the existing
values of all other sub-items.
Data Set Relations
There are three types of IMA
GE data sets: manual master, automatic master, and detail.
Master data sets are related to detail data set through sp ecic items called searc
h (or key)
items. The FORM command identies the data set type and searc
h items.
The data base designer can sp ecify one or more sort items. These items are also iden
tied
by the FORM command. As a QUER
Y user, it is not necessary to understand the function
of sort items. If y
ou want to know more ab out data set relations and sort items, refer to the
IMAGE Reference Manual description of the data base structure.
Sample Data Base
Figure 1-1 and Figure 1-2 illustrate a sample data base named ORDERS. The data base is
used in many examples in this manual. It contains six data sets. The four master data sets
are shown in the center column and the detail data sets on the sides.
CUSTOMER contains information ab out each customer.
SUP-MASTER contains information ab out each supplier.
PRODUCT contains information ab out each pro duct.
DATE-MASTER is an index of dates and can be used to retriev
e information by date from
the SALES or INVENTORY data sets.
SALES contains credit and purchase information.
INVENTORY contains pro duct supply information.
Both gures show a single entry for each data set. Figure 1-1 contains the data item names,
and Figure 1-2 contains a sample of the values in one entry. The arrows in both gures
illustrate the relationship of the data sets through search items.
1-6 INTRODUCING QUERY/V

Figure 1-1. ORDERS Data Base Structure
Figure 1-2. Sample Entry Values
INTRODUCING QUERY/V 1-7

Note: This data base is not mean
t to b e a practical application but rather is designed to
illustrate as many IMAGE/QUERY features as possible.
MODES OF ACCESS
Each person using QUER
Y to access a data base m
ust specify one of the 8 modes of access.
The following table lists the capabilities y
ou will have in each mode.
MODE CAPABILITIES
1 Find (read), replace, add, delete en
tries (QUERY requests IMAGE
dynamically lo ck and unlo ck the data base when accessing it)
2 Find and replace en
tries
3* or 4 Find, replace, add, and delete en
tries
5 Find entries (QUERYlocks and unlocks)
6, 7*, or 8 Find entries
* Mo des 3 and 7 giveyou exclusive access to the data base. All other mo des allow others to
share the data base.
A data base can only b e shared in certain situations or en
vironments. The mo de you
specify must b e acceptable for the environment already established by other IMAGE and
QUERY users (if any) when you open the data base. Here is a summary of the acceptable
environments:
multiple mode 1 and mo de 5 users
multiple mode 6 and mo de 2 users
multiple mode 6 users and one mo de 4 user
multiple mode 6 and mo de 8 users
one mo de 3 user
one mo de 7 user
Subsets of these environments are also allowed. For example, there may b e all mo de 6 users or
all mo de 8 users. There may also be one mo de 1 user or all mo de 5 users and so forth.
If a mo de 3 or mo de 7 user is currently accessing the data base that you want to access, you
must wait until that user either terminates their IMAGE or QUERY session or accesses a
dierent data base. This is true any time you try to access a data base with a mo de whichis
incompatible with other users accessing the same data base. Changing your mo de of access
may enable you to access the data base.
When deciding which mode to use, you should consider the following:
If you merely want to nd information and examine or rep ort on it, you should open the
data base with a nd (read-only) mo de, thus allowing other users as much capabilit y as
possible. The following table gives the result of using each read-only mo de.
1-8 INTRODUCING QUERY/V

MODE RESULT
5 The data base is lo c
ked for some op erations and ma
y slow the rate of
activity somewhat. If mo de 1 or mo de 5 users are already accessing the
data base, you must use mo de 5.
6 Mo de 2 users can replace en
tries, and one mo de 4 user can replace,
add, or delete; or mo de 8 users can read en
tries.
7 You have exclusive access to the data base.
8 No other users can replace, add, or delete en
tries.
An imp ortant adv
antage of using mo des 5 through 8 is that the data base is is opened for
reading only. As a result, y
ou are more likely to gain access to the data base b
yavoiding
restrictions due to the MPE accoun
t structure. Also, the les are not mark
ed for inclusion
in the MPE system bac
kup tap es (SYSDUMP) since they are not altered in an
yway. This
saves time when the daily system bac
kup pro cedure is executed.
If you want to nd information and replace data in existing en
tries but do not need to add
or delete anyentries (and do not wantanyone else to add or delete entries), you should open
the data base with mo de 2.
If you want to p erform all the op erations, including adding and deleting en
tries, you should
open with mo de 1, 3, or 4. The follo
wing table gives the result of using each of these mo des.
MODE RESULT
1 QUERYlocks and unlo cks the data base while p erforming operations.
Other users are able to add and delete en
tries. (The previous
comments for mo de 5 apply here also.)
3 You have exclusive access to the data base.
4 You have exclusive abilityto change the data base but mo de 6 users
are able to read while you makechanges.
Figure 1-3 illustrates acceptable IMAGE/QUERYenvironments. Users at terminals can
operate IMAGE or QUERY simultaneously. A single user indicates that only one user ma
y
specify that mo de. Two users indicates that multiple users may specify that mo de. Terminals
indicate the mo des which are incompatible with the currentenvironment. The capability of
each user is abbreviated as follows: F = nd, R = replace, A = add, D = delete.
INTRODUCING QUERY/V 1-9

Figure 1-3. IMAGE/QUERY Environments
1-10 INTRODUCING QUERY/V