| CRN 0438 | DISPLAY-RELATION |
| CRN 0439 | ABORT-DISPLAY-RELATION |
| CRN 0497 | DISPLAY-DISK-RELATION |
| CRN 0498 | ABORT-DISPLAY-DISKREL |
DATABASE ADMINISTRATION
(A)....................... (B).................
(C)...........................(D).(E)
-------------------------------------------------------------------------
INPUT:
REL = (1)....... (2).. = (3)..
LDEV = (4).
STARTTUP = (5)....
ENDTUP = (6)...
QUALIFY: (7)
(8).............................................................
OUTPUT: (9)
LCEID = (10). NA = (11).
REL = (12)...... RID = (13).
(14)
DLSID = (15).
DBCS-ERROR = (16)........................... (17)
IO-ERROR = (18).........................................
DBCS-WARNING = (19)........................... (20) (21)
ERROR = (22).........................................
ERROR NO = (23)
PAR =
PAR NO = (25)
ARG NO = (26)
(27).
RELATION-TYPE = (28)................
(29)......................
(30)......................
(31)...................... PARTS: (32)
(33)......................
(34)......................
(35)......................
(36)......................
LIST OF DOMAINS FOR RELATION (37)......
=========================================
CONSEC I DOMAIN I OFFSET I DOMAIN I ACCESS I VIRTUAL
NUMBER I NAME I I SIZE I METHOD I DOMAIN
--------I------------I--------I--------I----------I----------(38)
(39). I (40)...... I (41). I (42). I (43).... I (44)......
(45)
CONTENTS OF RELATION (46)...... ((47)..........
==============================================================
TUPLE I CONTENTS I DOMAIN
NBR I I NUMBER
------I-------------------------------------------------I-------(48)
(49). I (50)........................................... I (51)-(52)
REPORT REFERENCE NUMBER = 0377
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | command name | |
| (B) | main execution result | |
| (C) | result part type | |
| (D) | result part number | |
| (E) | continuation indicator | |
| (1) | name of the relation | |
| (2) | lceid or na or dlsid (inputparameter | |
| (3) | ce-id | |
| (4) | logical device (disk), (inputparameter) | |
| (5) | first displayed tuple | |
| (6) | last displayed tuple | |
| (7) | ||
| (8) | qualification | |
| (9) | ||
| (10) | logical control element identification | |
| (11) | physical control element identification | |
| (12) | name of the relation | |
| (13) | relation identification | |
| (14) | ||
| (15) | data-load-segment identification | |
| (16) | dbcs-error | |
| (17) | dbcs-error number | |
| (18) | i/o-error | |
| (19) | dbcs-warning | |
| (20) | dbcs-warning number | |
| (21) | lceid for same warnings | |
| (22) | error-report, see evaluation | |
| (23) | parameter, which was specified wrong | |
| (25) | number of the parameter, which was specified wrong | |
| (26) | number of the argument, which was specified wrong | |
| (27) | additional userinformation | |
| (28) | relationtype | LOCAL REAL: The relation is
physically stored in the CE. LOCAL REDEFINED: The relation is a subset of domains of one local real relation. LOCAL MULTITARGETTED: The relation is a composition of domains of more than one real relation (located in one CE), which are joined together (over one domain). LOCAL PROCEDURAL: The relation is a composition of domains of local real relation(s) where the domain-join is hardcoded (to have the fastest access). GLOBAL: The relation is in another CE. DISK ONLY: The relation is not resident in any memory but only kept on disk and temporarily loaded in a reserved area in any CE. ERROR INDICATION: The relation is not populated in the CE. |
| (29) | relation-information | DISTR. HEADER NOT LOCAL: There is
no distribution-control-relation for the displayed relation in the CE. DISTR. HEADER LOCAL: The distribution-control-relation for the displayed relation is local in the CE. |
| (30) | relation-information | REPLICATED: The relation is
mapped on several CEs with master-slave relationship. |
| (31) | relation-information | IMPLICIT DISTRIBUTED: The
relation is split into several parts, whereby each part is kept in the same CE and the size is less than 64 kbyte. |
| (32) | if implicit-distributed: number of parts | |
| (33) | relation-information | DISTRIBUTION PART LOCALLY: The
relation is split into several parts, whereby each part is kept in a different CE. |
| (34) | relation-information | SLAVE COPY: The relation in the
CE is just used for reading. Updates are routed to the master copy. MASTER COPY: Updates are performed in the CE and than the slave copies will be synchronized. |
| (35) | relation-information | OFFLINE REPLICATION: The relation
is replicated without master-slave relationship. |
| (36) | relation-information | DUPLEX: The relation may be
accessed in both CEs of a pair and is always to be synchronized to the mate. SIMPLEX: The relation is only to be accessed in the specified CE and has not to be synchronized to the mate. CROSS OVER: The relation is divided into 2 parts, which belong to 2 CEs. |
| (37) | name of the relation | |
| (38) | ||
| (39) | consecutive number | |
| (40) | name of the domain | |
| (41) | offset in tuple | |
| (42) | size of the domain (in bytes) | |
| (43) | access method | SEQUENT: The tuples are not
sorted. INDEXED: The tuples are sorted according to an index, which is not physically stored. B SEARCH: The tuples are sorted according to the values of the first domain. B MIXED: The tuples are sorted according to the values of the first two or three domains. The domainmodes are different. B CONCAT: The tuples are sorted according to the values of the first two or three domains. The domainmodes are equal. |
| (44) | yes, in case of a virtual domain | YES: The value of the domain is
equal for all tuples and is stored only once. |
| (45) | ||
| (46) | name of the relation | |
| (47) | primary- or secondary-area | The secondary-area includes
tuples, which could not be stored directly in the primary-area of a sorted relation. |
| (48) | ||
| (49) | tuple-number | |
| (50) | value of the tuple | A gap in a tuple is indicated
with $$. |
| (51) | first displayed domain | |
| (52) | last displayed domain |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (22) | ACCESS TO A PROCEDURAL RELATION IS NOT ALLOWED . . | A | ||
| (22) | ACCESS TO R-DOMDCR FAILED . . . . . . . . . . . . | D | ||
| (22) | ACCESS TO R-GDIR-V4 FAILED . . . . . . . . . . . . | D | ||
| (22) | ACCESS TO R-LCE-SWCD FAILED . . . . . . . . . . . | D | ||
| (22) | ACCESS TO R-LCEPCE-C FAILED . . . . . . . . . . . | D | ||
| (22) | ACCESS TO R-RELDCR FAILED . . . . . . . . . . . . | D | ||
| (22) | ACCESS TO RELATION FAILED . . . . . . . . . . . . | D | ||
| (22) | ARGUMENT IS MISSING . . . . . . . . . . . . . . . | B | ||
| (22) | COUNT TO R-LDIR-V4 FAILED . . . . . . . . . . . . | D | ||
| (22) | DISC-ACCESS TO DISKONLY RELATION IS NOT ALLOWED . | A | ||
| (22) | DISKACCESS TO MULTITARGET RELATION NOT ALLOWED . . | A | ||
| (22) | DLSID FOR SPECIFIED NA NOT FOUND . . . . . . . . . | D | ||
| (22) | DLSID IS NOT AVAILABLE . . . . . . . . . . . . . . | B | ||
| (22) | ENDTUP < STARTTUP . . . . . . . . . . . . . . . . | B | ||
| (22) | ERRORINDICATION IN R-GDIR-V4 . . . . . . . . . . . | A | ||
| (22) | LCEID FOR SPECIFIED DLSID IN R-LCEPCE-C NOT FOUND | D | ||
| (22) | LCEID IS NOT AVAILABLE . . . . . . . . . . . . . . | B | ||
| (22) | NA IS NOT AVAILABLE . . . . . . . . . . . . . . . | B | ||
| (22) | PARAMETER ENDTUP = 0 . . . . . . . . . . . . . . . | B | ||
| (22) | PARAMETER STARTTUP = 0 . . . . . . . . . . . . . . | B | ||
| (22) | RELATION NOT FOUND . . . . . . . . . . . . . . . . | A | ||
| (22) | RELATION NOT FOUND IN R_GDIR_V4 . . . . . . . . . | D | ||
| (22) | RELATION NOT FOUND IN SPECIFIED CE . . . . . . . . | B | ||
| (22) | WRONG DOMAINNAME IN QUALIFICATION . . . . . . . . | B | ||
| (22) | WRONG DOMAINVALUE IN QUALIFICATION . . . . . . . . | B | ||
| (22) | WRONG OPERATOR IN QUALIFICATION . . . . . . . . . | B | ||
| Action | Meaning |
|---|---|
| A | Check the input data. If necessary, correct the input data and re-enter the command. |
| B | Correct the input data and re-enter the command. |
| D | Take care of the error-report, re-enter the command eventually and if necessary, call the system specialist. |