1 – ABORT
008D82FA ABORT: <text>
Explanation:
DEC DATATRIEVE has processed an ABORT statement and, as a result,
has terminated the statement, procedure, or command file that was
being executed. The text supplied as part of the ABORT statement
is displayed. You include ABORT in a statement, procedure, or
command file to prevent DEC DATATRIEVE from continuing under
certain conditions. For example, you may want to terminate a
STORE statement if invalid data is entered or stop a report
procedure if information is missing.
User Action:
Reexecute the statement, procedure, or command file, avoiding the
conditions that caused the ABORT statement to be processed.
2 – ADTAKBOVF
008D874A Maximum key count for ADT exceeded.
Explanation:
ADT allows a maximum of only 10 keys (one primary and nine
alternate keys).
User Action:
If you need more than ten keys for the file, you must define the
file using the DEFINE FILE command in DEC DATATRIEVE, instead of
using ADT.
3 – ADTANBOVF
008D8752 Maximum field count for ADT exceeded.
Explanation:
ADT allows a maximum of 197 field names for a single record
definition for a domain.
User Action:
If you need more than 197 fields for the record, you must use
the DEFINE commands in DEC DATATRIEVE to define the domain, the
record, and the file, instead of using ADT.
4 – ADTEXIT
008D875A ADT exited by user request.
Explanation:
You entered CTRL/Z in response to an ADT question. The ADT
session is terminated; no definitions are stored in the data
dictionary.
User Action:
If you still want the data definitions you began, repeat the ADT
session.
5 – ASSERROR
008D939A Assignment abandoned due to error.
Explanation:
An error occurred during the processing of an assignment
statement. The variable or field may have been given a wrong
value.
User Action:
Correct the condition indicated by the error message.
6 – ASSVIRFLD
008D8392 Cannot assign to a virtual field.
Explanation:
A STORE or MODIFY statement tried to assign a value to a COMPUTED
BY field.
User Action:
Reenter the STORE or MODIFY statement without the assignment to a
COMPUTED BY field.
7 – BADCONSIST
008D93D2 It is illegal to have CONSISTENCY and CONCURRENCY for
the same database.
Explanation:
You cannot specify both CONSISTENCY and CONCURRENCY for the same
database.
User Action:
Specify either CONSISTENCY or CONCURRENCY, not both.
8 – BADDATEOP
008D8B12 Cannot multiply or divide dates.
Explanation:
You tried to use multiplication or division operations with date
fields or date variables.
User Action:
Change the expression so that you are not multiplying or dividing
dates.
9 – BADDFPTER
008D80D2 Invalid TERMINAL specification for DEFINEP command.
Explanation:
The DEFINEP command contains an invalid TERMINAL specification.
User Action:
Reenter the DEFINEP command. The following are valid terminal
specifications:
o TERMINAL = TTnn (where TTnn is the terminal number)
o TERMINAL = LOCAL (all users hard-wired to the local system)
o TERMINAL = NONLOCAL (all users not hard-wired to local system)
o TERMINAL = BATCH (all batch processes)
o TERMINAL = NETWORK (all users accessing DEC DATATRIEVE from
remote nodes)
10 – BADEDIT
008D9462 Error encountered when entering editor.
Explanation:
DEC DATATRIEVE encountered a problem while trying to invoke the
editor. For example, this error message might occur if you have
insufficient privilege for the editor to open a journal file and
you then attempt to edit again without correcting the privilege
problem.
User Action:
Exit DEC DATATRIEVE, correct the error, and reenter DEC
DATATRIEVE.
11 – BADELEMENTID
008D9912 Unable to process dictionary element.
Explanation:
DEC DATATRIEVE is not able to access the element selected in the
DEC DATATRIEVE Dictionary Navigator display.
User Action:
Check the element's ACL protection to make sure you have the
appropriate privileges to access it. If you do have the proper
privileges, then check with your system or dictionary manager.
12 – BADFETCH
008D95B2 Unable to fetch an object from the window interface DRM
database.
Explanation:
DEC DATATRIEVE was not able to fetch an object defined in the
VAX_DATATRIEVE.UID, the DECwindows Motif object definition file
used by DEC DATATRIEVE. This file is located in DTR$LIBRARY.
User Action:
Your DEC DATATRIEVE session will continue, but you should exit
from DEC DATATRIEVE and notify your system manager. Make sure the
VAX_DATATRIEVE.UID file supplied by the installation and located
in SYS$COMMON:[DTR] has not been modified.
13 – BADFLDCTX
008D8AB2 Invalid context for field "<field-name>".
Explanation:
You used a context variable improperly; DEC DATATRIEVE cannot
resolve the context.
User Action:
Correct the context variable so DEC DATATRIEVE can resolve
the context. The DEC DATATRIEVE User's Guide explains context
resolution in detail.
14 – BADGUICHA
008D8FC2 Invalid channel number for Guide Mode.
Explanation:
You tried to call Guide Mode from your program without assigning
a number to the input/output channel.
User Action:
Assign a channel number to DAB$W_TT_CHANNEL. The simplest way to
do this is to call the DEC DATATRIEVE Terminal Server immediately
after initializing the DEC DATATRIEVE Call Interface: CALL
DTR$DTR (DAB, DTR$M_OPT_CMD)
15 – BADGUITT
008D8FCA Invalid terminal type for Guide Mode.
Explanation:
You can enter Guide Mode only if your terminal is a VT-terminal
or is compatible with VT-terminals.
User Action:
If you wish to use Guide Mode, you must use a VT- or VT-
compatible terminal. If you are using a VT-terminal, then enter
the following command from DCL level: $ SET TERMINAL/INQUIRE
16 – BADHANDLE
008D80F2 Invalid DDMF handle.
Explanation:
The DAB you passed to a callable DEC DATATRIEVE program is
invalid.
User Action:
Check that your program is passing the correct DAB. If you see
this error in interactive DEC DATATRIEVE, please submit an SPR if
you are eligible.
17 – BADKEYBRD
008D948A Invalid keyboard ID.
Explanation:
DEC DATATRIEVE encountered a problem when trying to set up the
keyboard ID for terminal input.
User Action:
If you are eligible, submit a Software Performance Report (SPR).
18 – BADKEYTBL
008D9482 Invalid key table ID.
Explanation:
DEC DATATRIEVE encountered a problem when trying to set up the
key table for terminal input.
User Action:
If you are eligible, submit a Software Performance Report (SPR).
19 – BADLENRED
008D816A Bad length for REDEFINES field "<field-name>".
Explanation:
The REDEFINES field cannot describe an area larger than the area
of the field it is redefining.
User Action:
Reenter the DEFINE RECORD command but describe an area for the
REDEFINES field that is equal to or smaller than the area of the
field you are redefining.
20 – BADNUMARG
008D80FA Invalid number of arguments to DDMF.
Explanation:
Your program passes the wrong number of arguments to a callable
DEC DATATRIEVE routine.
User Action:
Check the call format in the DEC DATATRIEVE Guide to Programming
and Customizing to find how many arguments the routine requires
and correct your program accordingly.
21 – BADNUMBER
008D8202 Bad number: "<number>".
Explanation:
A nonnumeric character has been found.
User Action:
Replace the nonnumeric character by a numeric character.
22 – BADPORTOP
008D8B6A It is invalid to MODIFY, ERASE or FIND a port.
Explanation:
You tried to FIND, ERASE, or MODIFY through a port from
interactive DEC DATATRIEVE. Ports can be accessed only through
callable DEC DATATRIEVE.
User Action:
Make your FIND, ERASE, or MODIFY refer to a domain that points
to a record to which the port refers, or access the port through
callable DEC DATATRIEVE.
23 – BADQUOSTR
008D8F02 Expected closing quote, encountered "***END_OF_LINE***".
Explanation:
You began a line of text with a quotation mark but did not
include a closing quotation mark before the end of the line.
User Action:
Insert a closing quotation mark at the end of the text you want
to quote.
24 – BADRECSIZ
008D8258 Bad record size. Defined: <number> File: <number>
Explanation:
The size of the record in the data file must agree with the
specification in the record definition.
User Action:
If you have edited the record definition so that the record size
(in bytes) has changed, you must restructure the domain. The DEC
DATATRIEVE User's Guide explains this procedure in detail. If
you are trying to create a DEC DATATRIEVE domain to access an
existing data file, you must correct the record definition so
that the size you specify in the definition matches the size of
the record in the file.
25 – BADSORLEN
008D8EF2 You tried to sort by too large a value or too many
values. (Total size: <number>)
Explanation:
The total size of the sort keys you specified and the internal
sort information used by DEC DATATRIEVE was greater than 255
characters long.
User Action:
If you specified a very large field, you should sort on just the
first part of it. You can do this in two ways:
o Redefine the record so the entire field is a group field and
the first part of the record is an elementary field that can
be sorted on.
o Use the function FN$STR_EXTRACT to extract the first part of
the field.
26 – BADSOURCE
008D999A Object <...> is not a valid DEC DATATRIEVE source.
Explanation:
You attempted to ready a CDD$DATABASE object that refers to a
Oracle CODASYL DBMS database. This is not a valid DEC DATATRIEVE
source.
User Action:
You must use the DEC DATATRIEVE DEFINE DATABASE command to
specify which subschema of the Oracle CODASYL DBMS database is
to be used. Once the DEC DATATRIEVE database has been defined,
you can ready the database directly or you can define domains
using the DEC DATATRIEVE database.
27 – BADSTRDES
008D89BA Invalid string descriptor.
Explanation:
The token type your program passes to the callable DEC DATATRIEVE
routine, DTR$GET_STRING, is not a valid token type.
User Action:
Correct your program to use a valid token type. The DEC
DATATRIEVE Guide to Programming and Customizing lists valid
token types. If you see this error in interactive DEC DATATRIEVE,
please submit an SPR, if you are eligible.
28 – BADUDKCTX
008D8C8A Invalid parsing context specified for User Defined
Keyword.
Explanation:
Your program passed an invalid User Defined Keyword (UDK) type
when creating a user-defined keyword. The DEC DATATRIEVE Guide to
Programming and Customizing lists valid UDK types.
User Action:
Correct your program to use a valid UDK type.
29 – BADUDKIDX
008D8C92 Invalid index specified for User Defined Keyword.
Explanation:
Your program passed an invalid UDK index when creating a user-
defined keyword. UDK indexes must be between 1 and 32767.
User Action:
Correct your program to use a valid UDK index.
30 – BADUIC
008D80DA Invalid UIC specified.
Explanation:
You specified an incorrect UIC in the DEFINEP command.
User Action:
Reenter the DEFINEP command. The UIC must be of the form [m,n],
where m is the group number and n is the user number. An asterisk
(*) can be used in place of either n (all users in a group) or in
place of m and n (all users).
31 – BLKTOOBIG
008D8024 Maximum block size exceeded; statement aborted.
Explanation:
Memory could not be allocated to perform the attempted operation.
User Action:
Simplfy the operation you are performing. For example, if an
extremely complex RSE is causing the error, try to simplify the
RSE by reorganizing it or by eliminating redundant clauses.
32 – CANRDYDOM
008D8AA2 Source cannot be readied at this access mode unless a
COMMIT, ROLLBACK, or FINISH is issued.
Explanation:
You readied and accessed a Oracle CODASYL DBMS domain or Oracle
CODASYL DBMS database. You then attempted to ready, under a more
restrictive access mode, another domain or database that referred
to records in the same Oracle CODASYL DBMS realm:
o A second Oracle CODASYL DBMS domain that referred to another
record in the same realm as the first domain
o The same database using a different record in the same realm
User Action:
Issue a COMMIT, ROLLBACK, or FINISH command. Ready the domain or
database under the desired access mode.
33 – CANRDYSRC
008D0585 Source cannot be readied unless a COMMIT, ROLLBACK, or
FINISH is issued.
Explanation:
You attempted to reready a modified database before entering a
COMMIT, ROLLBACK, or FINISH command.
User Action:
You can have only one outstanding transaction at a time. Execute
a COMMIT, ROLLBACK, or FINISH command, then enter the READY
command again.
34 – CDAERROR
008D9A33 Aborting report execution due to CDA toolkit error.
Explanation:
DEC DATATRIEVE internal error.
User Action:
Contact you System Manager.
35 – CDANOTINST
008D9A22 Aborting report execution-cannot access CDA image.
Explanation:
While executing a CDA report, DEC DATATRIEVE has attempted to
access the CDA shareable image and has not succeeded.
User Action:
Contact the System Manager to verify that CDA is properly
installed.
36 – CDDCORRUPT
008D9472 A Oracle CDD/Repository stream cannot be started. Exit
and reinvoke DEC DATATRIEVE!
Explanation:
Oracle CDD/Repository error
User Action:
Exit and reinvoke DEC DATATRIEVE before attempting to access the
Oracle CDD/Repository.
37 – CDDNOTFOUND
008D9812 Element <...> cannot be found in the dictionary.
Explanation:
DEC DATATRIEVE could not find the specified object in either the
CDO or the DMU dictionary.
User Action:
Be sure that the path name of the specified object is listed
correctly.
38 – CDONOTFOUND
008D981A Element <...> is not in the CDO dictionary.
Explanation:
DEC DATATRIEVE could not find the specified object in the CDO
dictionary.
User Action:
Be sure that the path name of the specified object is listed
correctly.
39 – CDONOTRANS
008D9A52 Unable to build DEC DATATRIEVE source text from this CDO
definition.
Explanation:
DEC DATATRIEVE could not access the CDO definition.
User Action:
Check your CDO definition.
40 – CHAOPTINV
008D888A The "CHANGE" option is invalid on the primary key of a
file.
Explanation:
The CHANGE option determines whether or not you can modify the
content of the associated key field. It cannot be used with
primary keys.
User Action:
Reenter the DEFINE FILE command but without specifying CHANGE for
the primary key.
41 – CLANOTPER
008D8472 <...> clause is not permitted on a variable declaration.
Explanation:
You cannot use an OCCURS or REDEFINES clause when defining a
variable.
User Action:
Reenter the DECLARE statement but without the OCCURS or REDEFINES
clause.
42 – CLIPFAIL
008D970A Failure to access DECwindows Motif clipboard.
Explanation:
You cannot access the DEC DATATRIEVE DECwindows Motif clipboard
during a CUT, COPY, or PASTE operation for a reason other than
the keyboard being locked. The operation cannot be completed, but
DEC DATATRIEVE continues to be usable.
User Action:
You should contact your system manager to make sure that the
DECwindows Motif interface is running properly. If the interface
is working properly, submit an SPR if you are elegible.
43 – CLIPLOCKED
008D971A The DECwindows Motif clipboard is locked, please try
again later.
Explanation:
The DECwindows Motif clipboard was locked by another user when
DEC DATATRIEVE attempted to access it during a CUT, COPY or PASTE
operation. The operation cannot be completed.
User Action:
You should repeat the operation when the keyborad is not locked.
44 – CLIPNODATA
008D9722 No data is currently contained on the DECwindows Motif
clipboard.
Explanation:
You attempted a DEC DATATRIEVE DECwindows Motif interface PASTE
operation to retrieve data from the clipboard when the DATA did
not exist on the clipboard.
User Action:
You should place data on the clipboard by a CUT or COPY operation
and then repeat the PASTE operation.
45 – CLIPTRUNCATE
008D9712 DECwindows Motif clipboard data truncated.
Explanation:
Data being transferred from the clipboard during a DECwindows
Motif interface PASTE operation has been truncated. The operation
cannot be completed, but DEC DATATRIEVE continues to function.
User Action:
If you are elegible to do so, you should submit an SPR.
46 – CNVNUMDAT
008D83C2 Can't convert number to a date string.
Explanation:
An invalid number was assigned to a date field.
User Action:
Enter a correct date in the field.
47 – COLTOOBIG
008D9A62 Too many records for this collection.
Explanation:
The user tried to create a collection with more records than
allowed.
User Action:
Refer to the restriction for the number of records in a
collection created by the statement FIND, in DEC DATATRIEVE
reference documentation.
48 – COMFILNES
008D8EC2 Command file nesting limit exceeded.
Explanation:
You are permitted to nest indirect command files only eight deep.
User Action:
Either include some of one command file in another or use
procedures.
49 – COMPOVF
008D8222 Computation overflow.
Explanation:
You entered an integer too large to fit in a longword. This
can happen in the Report Writer with SET LINES_PAGE and in
collections.
User Action:
Enter a smaller number.
50 – CONTPREQ
008D8972 All "P"s must be contiguous in PICTURE or EDIT string.
Explanation:
P picture string characters must not be separated by other
picture string characters.
User Action:
Reenter the field or variable definition. To specify a decimal
scaling position, place one or more P characters together either
at the right or the left of the picture string.
51 – CSERROR
008D95BA Window interface compound string conversion error.
Explanation:
DEC DATATRIEVE encountered an error while converting a compound
string used by the DECwindows Motif interface.
User Action:
Your DEC DATATRIEVE session will continue, but you should exit
from DEC DATATRIEVE and notify your system manager.
52 – CURRFAIL
008D8E3A Record from source <...> failed to set up currency for
set connection.
Explanation:
A statement you issued attempted to use a record from the Oracle
CODASYL DBMS domain or Oracle CODASYL DBMS record named in
the message to establish currency for a set. The record was
not a member of the set and the statement failed to establish
currency. This message can be generated by CONNECT, DISCONNECT,
and RECONNECT statements, as well as the STORE statement.
User Action:
Set up a record stream containing only records that are members
of some occurrence of the set. You can do this with an ANY clause
in the record selection expression. For example:
FOR PARTS WITH ANY EMPLOYEES OWNER OF RESPONSIBLE_FOR
DISCONNECT A FROM RESPONSIBLE_FOR
53 – DFBADRECCNT
008D99E2 The number of DEC DATATRIEVE records does not match the
number of records in the form record list.
Explanation:
The number of records specified in a SEND or RECEIVE clause does
not match the number of records expected by the form.
User Action:
Check how many records are requested or returned by the form
record/record list and the WITH_FORM statement used to send
/receive records or the FORM IS clause in domain definition.
54 – DFBADRECLEN
008D9A5A The length of the DEC DATATRIEVE record and the form
record do not match.
Explanation:
The length of the DEC DATATRIEVE data record to be sent/received
to/from a form and the length of the corresponding form record
are different. This corresponds to the DECforms error FORMS$_
BADRECLEN.
User Action:
Check the definition of the DEC DATATRIEVE data record and of the
corresponding form record.
55 – DFDBLATTEMPT
008D99F3 Both DECforms and DEC FMS/ VAX TDMS are unable to access
the specified form.
Explanation:
To manage a form connected to a domain, DEC DATATRIEVE tried
first with DECforms but DECforms was unable to use it; then
DEC DATATRIEVE tried with DEC FMS/ VAX TDMS because the DEC
DATATRIEVE image was linked with DEC FMS/ VAX TDMS code but
DEC FMS/ VAX TDMS too was unable to use the form file. It is an
informational message which is followed by the detailed messages
from DECforms and DEC FMS/ VAX TDMS.
User Action:
Check the file used as form file or library.
56 – DFLOADFORM
008D99BA Failure attempting to load a DECforms form.
Explanation:
DEC DATATRIEVE called DECforms to enable a session and the
operation failed. This error corresponds to DECforms error
FORMS$_LOADFORM. An example: a DEC FMS form library was used
instead of a DECforms form file.
User Action:
Check the DECforms file used in the operation.
57 – DFNOLAYOUT
008D99C2 No layouts in the DECforms form conform to this terminal
type, language, and display size.
Explanation:
DEC DATATRIEVE called DECforms to enable a session and the
operation failed, because no layouts in the DECforms form conform
to type, language, and display size of the current terminal. This
error corresponds to DECforms error FORMS$_NOLAYOUT.
User Action:
Check the DECforms form used in the operation.
58 – DFNOLICENSE
008D99CA DECforms form manager is present, but no DECforms
software license is active.
Explanation:
DEC DATATRIEVE tried to call DECforms but failed because no
DECforms software license is active. This error corresponds to
DECforms error FORMS$_NOLICENSE.
User Action:
Add software license for DECforms.
59 – DFOPENFORM
008D99D2 Error opening DECforms form file !AD .
Explanation:
DEC DATATRIEVE called DECforms to enable a session but failed
because DECforms did not succeeded in opening the specified form
file. This error corresponds to DECforms error FORMS$_OPENFORM.
User Action:
Check the name of the file used in the operation or the form file
itself.
60 – DFREADFORM
008D99DA Error reading DECforms form file !AD .
Explanation:
DEC DATATRIEVE called DECforms to enable a session but failed.
This error corresponds to DECforms error FORMS$_READFORM.
User Action:
Check the form file used in the operation.
61 – DFNORECORD
008D99EA A form record specified in the operation is unknown in
the DECforms form.
Explanation:
DEC DATATRIEVE tried to send or receive data from a record that
is not in the form. This error corresponds to DECforms error
FORMS$_NORECORD.
User Action:
Check the name of the form record specified in the WITH_FORM
statement or the top field name of the domain connected to the
form.
62 – DFNOTNOW
008D99FA A DECforms form cannot be used now.
Explanation:
Not in use
User Action:
None
63 – DICELTUSE
008D818A Dictionary element "<path-name>" already in use.
Explanation:
You cannot define a new dictionary element if another element
with the same path name is already in Oracle CDD/Repository.
User Action:
Rename the element before entering it in the data dictionary, or
delete the old dictionary object before entering a new version of
that object.
64 – DICNOTRED
008D0586 Dictionaries may not be redefined.
Explanation:
The Oracle CDD/Repository path name you specified in a REDEFINE
command is the name of a dictionary. Dictionaries may not be
redefined.
User Action:
Reenter the REDEFINE command and give the name of a dictionary
object that can be redefined.
65 – DICNOTUND
008D81A2 Dictionary element not understood.
Explanation:
The Oracle CDD/Repository definition you are using was created
with CDDL and contains elements that DEC DATATRIEVE cannot
translate. These elements refer to data types and storage formats
that DEC DATATRIEVE does not support.
User Action:
None. If DEC DATATRIEVE does not support a data type in an
existing file, you cannot use DEC DATATRIEVE to access that data.
66 – DIFFNODE
008D988A Node name in remote domain anchor <...> does not match
name in node specification <...>.
Explanation:
The node name given in the anchor of the domain path name of a
remote domain definition does not match the node name in the node
specification of that definition. This node name inconsistency is
illustrated in the following example:
DTR> REDEFINE DOMAIN REM_DOM USING
DFN> MYNODE::SYS$ROOT:[DEBRUN.DIC]YACHTS AT
DFN> URNODE"SYSTEM PASSWORD" RELATIONSHIPS;
Node name in remote domain anchor "MYNODE",
does not match name in node specification,
"URNODE".
User Action:
Remove the node name from the anchor of the remote domain path
name or change the node name to match the name in the node
specification section of the DEFINE DOMAIN command
67 – DIGNUMPIC
<008D839A Too many digits in numeric picture or edit string.
Explanation:
You declared a numeric variable and used a PICTURE clause or
EDIT_STRING more than 31 characters long, or you used an EDIT_
STRING that contained more than 31 characters to print a numeric
variable with a PRINT statement.
User Action:
Declare the PICTURE clause or EDIT_STRING with 31 or fewer
characters, or do not use more than 31 characters in the
EDIT_STRING when you print a numeric variable with the PRINT
statement.
68 – DMUFROMFLD
008D994A DMU record <...> may not be referenced in FROM field.
Explanation:
Only records defined in a CDO format dictionary can be referenced
by a FROM clause in a DEC DATATRIEVE record definition.
User Action:
Convert the record to CDO format.
69 – DROPOPT
008D9428 Keyword OPTIMIZE removed from definition of record
"<...>".
Explanation:
Optimization has failed. The record will be defined but not
optimized. DEC DATATRIEVE removes the keyword OPTIMIZE from the
record definition.
User Action:
If a message concerning insufficient virtual memory preceded this
message, then free up memory space by using the FINISH command to
end access to other readied domains, relations, or Oracle CODASYL
DBMS records. Edit the record definition and replace the OPTIMIZE
qualifier.
70 – DROPUSING
008D99B0 FORM IS...USING cannot be applied to DMU domains. The
USING clause has been removed from domain "!AD".
Explanation:
The clause USING added to the FORM IS clause in domain
definitions (to specify an exchange record to be used while
moving data to and from a form), can be used only with domains
defined in CDO, because only the CDO protocols allow for this
clause.
User Action:
Put the domain definition in a CDO dictionary or remove the USING
clause.
71 – DTR$_CDONOTRANS
008D9A52 Unable to build DEC DATATRIEVE source text from this CDO
definition.
Explanation:
The error may happen while doing an EXTRACT, EDIT or SHOW on a
record defined by the Dictionary Operator (CDO) utility. DEC
DATATRIEVE tries to interpret the CDO definition to build a
DEC DATATRIEVE source text. Numeric constants contained in CDO
expressions such as INITIAL_VALUE and COMPUTED_BY need to be
converted to text format to be displayed: if the conversion
fails, DEC DATATRIEVE displays this message and returns to the
prompt.
User Action:
CDO record definitions which cannot be properly converted to
DEC DATATRIEVE source text should be managed by means of the CDO
utility.
72 – DTYPEUNS
008D9A6A <data-type> is not supported on this platform.
Explanation:
The user has attempted to define a field in a record using a data
type that is not supported by the hardware or operating system
on which DEC DATATRIEVE is running. At present, S_FLOATING and
T_FLOATING data types are not allowed on an OpenVMS VAX system,
while the H_FLOATING data type is not allowed on an OpenVMS Alpha
system.
User Action:
Use an alternative data type supported by the platform you are
using.
73 – DUPCLASPE
008D811A Duplicate clause specified: "<clause>".
Explanation:
The clause specified in the message cannot appear more than once
in the statement or field definition.
User Action:
Edit the statement or definition and delete the duplicate clause.
74 – DUPUSACLA
008D89CA Duplicate USAGE clause specified: "<clause>".
Explanation:
Only one USAGE clause is permitted in a field or variable
definition.
User Action:
Reenter the field or variable definition using only one USAGE
clause.
75 – EXCCMPSTK
008D94D2 Exceeded compiler stack level at level <number>.
Explanation:
This error is generated if you exceed the internal limit of
64 compiler levels for a compound DEC DATATRIEVE statement. A
compiler level is needed for certain constructs like FOR loops,
WHILE loops, and REPEAT counts. The level is also incremented for
each source in a record selection expression.
User Action:
You may need to restructure your query or even your application
so that DEC DATATRIEVE does not need to process so many levels
in a single statement. For example, if this error occurred as
a result of nested FOR loops, you may need to change these to
appropriate FIND statements.
76 – ELSEREQ
008D8BDA An ELSE clause is required for IF and CASE values.
Explanation:
Conditional value expressions require ELSE clauses.
User Action:
Formulate the value expression again, including an ELSE clause
for any IF or CHOICE value expression.
77 – ELTNOTDIC
008D8192 Element "<...>" not found in dictionary.
Explanation:
The path name specified in the SHOW or READY command does not
resolve to an element in the data dictionary.
User Action:
Reenter the command with a different path name. You might use
a SHOW ALL command to see what is in data dictionary at your
current directory.
78 – ELTNOTDTR
008D819A Element <name> is not a DEC DATATRIEVE object.
Explanation:
You attempted to execute a command such as DELETE or EXTRACT
on a dictionary object that is not a DEC DATATRIEVE one. DEC
DATATRIEVE objects are: domains, records, databases, tables,
procedures and plots.
User Action:
Use the repository utilities to manage the object.
79 – ERROR
008D80BA Statement abandoned due to error.
Explanation:
DEC DATATRIEVE generates this general error message after any
statement or command that fails. It follows a more descriptive
error message.
User Action:
Refer to the more detailed error message.
80 – EXPINVPIC
008D896A Exponential edit string is invalid for PICTURE clause.
Explanation:
You cannot use E as a picture string character. Use E only as an
edit string character.
User Action:
Reenter the field or variable definition with an appropriate
PICTURE or USAGE clause.
81 – EXTBADPARAM
008D9442 Argument list cannot contain both the object path name
and the object type.
Explanation:
You cannot specify both the object path name and the object type
in the argument list of a single EDIT or EXTRACT command. Object
types include DOMAINS, PLOTS, RECORDS, PROCEDURES, or TABLES.
User Action:
Reenter the EDIT or EXTRACT command, but do not specify an object
path name and an object type in the same argument list.
82 – FDLBADSIZ
008D94CA Incompatible record size. Defined: <number> FDL File:
<number>.
Explanation:
The size of the record in the FDL file must agree with the
specification in the record definition.
User Action:
Decide what the correct record length should be and edit either
the record definition or the FDL file so that the record lengths
match.
83 – FDLERROR
008D94B2 Error using FDL file "<file-name>".
Explanation:
FDL encountered an error in the use of the specified FDL file.
The error was not related to a specific statement number. This
could include errors such as Internal logic error detected or
Insufficient virtual memory.
User Action:
At DCL level, issue a CREATE/FDL command which specifies the
FDL file referred to in the error message. This should give more
information about the nature of the error. If the error does not
occur at DCL level, then submit a Software Performance Report
(SPR) if you are eligible.
84 – FDLOPEN
008D94C2 Error opening FDL file "<file-name>".
Explanation:
DEC DATATRIEVE could not open the specified FDL file. Reasons
for this might include misspelling the FDL file name, disk, or
directory; access problems; or improper OpenVMS file protection.
User Action:
Check to see that the name of the file has been spelled
correctly, that the specified disk or directory exists, and that
the OpenVMS file protection is appropriate.
85 – FDLSTMNT
008D94BA Error using FDL file "<file-name>"; statement <number>.
Explanation:
FDL has detected an error in the specified file at the indicated
statement number.
User Action:
Check the indicated statement number for syntax errors or for any
ambiguous or undefined FDL keywords. If necessary, you may want
to issue a CREATE/FDL at DCL level to get more detailed error
information from FDL.
86 – FILNOTFND
008D8A4A File not found - "<...>".
Explanation:
DEC DATATRIEVE cannot locate the data file associated with
the domain. This error most commonly occurs when the domain
definition does not include device and directory information
for the file and the default OpenVMS directory does not contain
the file.
User Action:
Use a SHOW domain-name command to see how the file is specified
in the domain definition. If the information is incomplete
or inaccurate, edit the domain definition to correct the file
specification.
87 – FILNOTRED
008D0587 Files may not be redefined.
Explanation:
The Oracle CDD/Repository path name you specified in a REDEFINE
command belongs to a file; files may not be redefined.
User Action:
Reenter the REDEFINE command, giving the name of a dictionary
object that can be redefined.
88 – FLDNOTOCC
008D812A Field "<field-name>" not found for OCCURS DEPENDING ON.
Explanation:
The field named in an OCCURS DEPENDING ON clause must be a field
previously defined in the record definition.
User Action:
Reenter the DEFINE RECORD command, making sure that the field
specified in the OCCURS DEPENDING ON clause is a field in the
same record.
89 – FLDNOTRED
008D8122 Field "<field-name>" not found for REDEFINES.
Explanation:
The field to be redefined must appear in the record definition
before its REDEFINES field.
User Action:
Reenter the DEFINE RECORD command, checking that the REDEFINES
clause names a field that has already been defined.
90 – FLDSELFREF
008D8B82 Field "<field-name>" contains a self-reference and
cannot be evaluated.
Explanation:
Field or variable definitions cannot have clauses that contain a
self-reference. For example, you cannot use a COMPUTED BY clause
that includes a value expression containing the name of the field
or variable that is being defined.
User Action:
Reenter the definition but eliminate any recursive or self-
referring expressions in definition clauses.
91 – FMSITT
008D8F32 Invalid terminal type for forms.
Explanation:
You are using an DEC FMS forms application from a type of
terminal that DEC FMS does not support, such as a hardcopy
terminal.
User Action:
Use a terminal that DEC FMS supports, such as a VT100-series
terminal.
92 – FMTNEEDON
008D9A3A Execution of a report in !AS format requires an ON
clause specifying the file name.
Explanation:
You did not supply an ON clause specifying the file name.
User Action:
Reissue the command.
93 – FUNCAPTIVE
008D94FA Function cannot be executed from a captive account.
Explanation:
You tried to issue a function call to either FN$SPAWN or FN$DCL
from within a captive account. These function calls are not
allowed from within captive accounts.
User Action:
See the people in charge of DEC DATATRIEVE on your system. They
can consult the DEC DATATRIEVE Release Notes for version 5.0 or
later for further information.
94 – GIVNAMUSE
008D8B7A Given name "<...>" is already used by source <...>.
Explanation:
You tried to ready a record source as an alias, but the alias
name you chose is already being used by another readied source.
User Action:
Execute the READY command using a different alias, or finish the
source that is using the name you wish to use.
95 – ILLOPERVIEW
008D9992 Illegal operation for relational view source <...>.
Explanation:
An operation that requires a relational database key, such as
an operation referring to a collection or to a MODIFY or DELETE
statement, can not be executed because the source is a relational
view that is not based on physical records in the database. Such
views include the following:
o Views defined using the SQL/Services interface to Oracle Rdb
that include GROUP BY or UNION clauses
o Views defined using either the Relational Database Operator
(RDO) or SQL/Services that include functions like SUM
User Action:
To avoid error messages, you should not perform these statements
when you are referring to a relational view that is not based on
a physical record source.
96 – ILLPICSTR
008D814A Illegal PICTURE or EDIT string character: "<...>".
Explanation:
The character specified in the message is either an invalid
character for a PICTURE or EDIT_STRING clause, or it is a valid
character that has been used incorrectly.
User Action:
Edit the field definition and correct the picture or edit string.
97 – ILLSEGEDIT
008D947A Segmented string field <field-name> must have a T (text)
edit string.
Explanation:
Segmented string fields in relational database sources must use T
(text) edit strings.
User Action:
Reenter the statement specifying a "T" (text) edit string.
98 – ILLSEGOPR
008D9392 Statement is illegal for segmented string field <field-
name>.
Explanation:
Your statement violated one of the following restrictions that
apply to segmented string fields:
o Do not assign values of fields or declared variables to a
segmented string field.
o Do not retrieve or store segmented string fields from remote
domains.
o Do not use segmented string fields with forms, plots, or with
the DISPLAY statement.
o Do not use the following operators or clauses in an RSE that
refers to segmented string fields:
- Relational operators, including CONTAINING, ANY, STARTING
WITH, and MISSING
- Boolean operators: AND, OR, NOT, BUT
- SORTED BY clause
- REDUCED TO clause
- CROSS clause
User Action:
Rewrite your statement to comply with the restrictions.
99 – INFBADCOD
008D82DA Bad information code.
Explanation:
Your program passed an invalid information code in a call to
DTR$INFO.
User Action:
Correct the information code your program passes.
100 – INFBADID
008D82D2 Bad object id.
Explanation:
Your program passed a null object identification code to
DTR$LOOKUP or DTR$INFO.
User Action:
Correct the object identification code your program passes.
101 – INFBADIDX
008D9502 Information index is out of range.
Explanation:
The index parameter on a call to DTR$INFO was either less than 1
or greater than the number of elements in the object as specified
by the object-id parameter.
User Action:
Make sure that the index parameter is within the correct range
for the object being queried.
102 – INFNOTFOU
008D82EA Object not found.
Explanation:
DEC DATATRIEVE could not find the object you specified in a call
to DTR$LOOKUP.
User Action:
Check that you specified the object correctly.
103 – INPLINTRU
008D8CC2 Input line too long - truncated to 255 characters.
Explanation:
An input line cannot exceed 255 characters.
User Action:
Reenter the line with a legal number of characters. To enter
more than 255 characters in a string, you can declare several
variables and assign values to them. Then use a concatenation
expression to specify the desired string.
104 – INVACLATT
008D980A Invalid ACL attribute found for <...>.
Explanation:
DEC DATATRIEVE attempted to read a CDO dictionary entity that has
an invalid ACL protection attribute.
User Action:
Determine the source of the problem by using the CDO utility's
SHOW PROTECTION command. If the CDO utility can successfully
complete this command, then report this problem to the person
responsible for DEC DATATRIEVE on your system. If you are
eligible, submit an SPR. If the CDO utility cannot complete the
command, report this problem to the person responsible for Oracle
CDD/Repository.
105 – INVCOLPAG
008D86EA Invalid number of columns for Set Columns_Page.
Explanation:
The maximum value for the SET COLUMNS_PAGE command is 255.
User Action:
Reenter SET COLUMNS_PAGE, assigning a value that is not greater
than 255.
106 – INVDIRPROT
008D9882 Invalid ACL found for directory <...>.
Explanation:
The specified CDO dictionary directory has an invalid protection
ACL.
User Action:
Determine the source of the problem by using the CDO utility's
SHOW PROTECTION command. If the CDO utility can successfully
complete this command, then report the initial problem to the
person responsible for DEC DATATRIEVE on your system. If you are
eligible, submit an SPR. If the CDO utility cannot complete the
command, report this problem to the person responsible for Oracle
CDD/Repository.
107 – INVEDITOR
008D9402 <...> is not a valid editor within DEC DATATRIEVE.
Explanation:
You have assigned the logical name DTR$EDIT to an editor not
currently supported by DEC DATATRIEVE.
User Action:
Redefine the logical name DTR$EDIT.
From within DEC DATATRIEVE, use the FN$CREATE_LOG function to
redefine the logical name.
At the DCL level, use the DEFINE or ASSIGN command to redefine
the logical name. Do not use the FN$SPAWN function (creating a
subprocess) to get to the DCL level in this instance. Commands
issued from the subprocess will not take effect in the original
process.
108 – INVNODSPC
008D8C2A Invalid Node Specification.
Explanation:
The node specification has an invalid syntax.
User Action:
Reenter the statement or command with a valid node specification.
109 – INVOPTION
008D957A An invalid option has been specified for the DECwindows
Motif terminal handler DTR$WINDOWS call.
Explanation:
One of the following invalid options was passed to call
DTR$WINDOWS:
o DTR$M_OPT_BANNER
o DTR$M_OPT_KEYDEFS
o DTR$M_OPT_REMOVE_CTLC
User Action:
Repeat the DTR$WINDOWS call without the invalid option(s).
110 – INVWDTHRANGE
008D9A8A WIDTH value of <number> not in range for <PORTRAIT
/LANDSCAPE> paper orientation.
Explanation:
The number specified in the WIDTH clause is not in the range
allowed by the SET PAPER_ORIENTATION statement (80 columns for
portrait orientation and 132 columns for landscape orientation).
User Action:
Change the value of the WIDTH clause to a number in the range of
the chosen paper orientation.
111 – IRRELESET
008D83FA Domain <domain-name> is not related to set <set-name>.
Explanation:
Your Oracle CODASYL DBMS domain implies a set to which it is not
related.
User Action:
Use the SHOW SETS command to identify the sets in which the
Oracle CODASYL DBMS domain participates.
112 – KEYUNDEF
008D837A Key "<...>" is not defined in domain "<domain-name>".
Explanation:
The key specified in the DEFINE FILE command must be a field in
the record.
User Action:
Reenter the DEFINE FILE command, specifying one of the record
fields, either elementary or group, as a key field.
113 – LINTOOLON
008D8172 Command line exceeds 255 characters.
Explanation:
DEC DATATRIEVE input lines cannot exceed 255 characters.
User Action:
Correct the error by entering an input line with a legal number
of characters.
114 – MAXEXTEXC
008D952A Maximum size for extract or edit buffer exceeded.
Explanation:
A request for a particular portion of the extract or edit command
exceeded the 256-byte size of the buffer for that operation.
Typically, this means that a field definition clause for a record
is too large.
User Action:
If this record definition was not created by DEC DATATRIEVE, you
must do one of the following:
o Define the record through DEC DATATRIEVE before you edit it
o Edit the record definition in the original definition facility
115 – MAXLINEXC
008D86AA Maximum line count exceeded - report terminated.
Explanation:
The report length is greater than the line limit specified.
User Action:
Edit the report specification, increasing the value for SET MAX_
LINES.
116 – MAXPAGEXC
008D86DA Maximum report pages exceeded - report terminated.
Explanation:
The report length is greater than the page limit specified.
User Action:
Edit the report specification, increasing the value for SET MAX_
PAGES.
117 – MAXSCRLIN
008D9512 Maximum lines for scrolling region exceeded.
Explanation:
The maximum number of lines allowed within a scrolled region has
been exceeded. This error might occur when using scroll regions
in the DEC DATATRIEVE screen manager from commands such as the
HELP *... command.
User Action:
Request less information in scroll region.
118 – MISNOTFLD
008D842A Object of MISSING operator must be a field.
Explanation:
The MISSING operator refers to something other than a field, for
example, WITH "PRICE" NOT MISSING.
User Action:
Make sure the MISSING clause refers to a field in the domain you
are using.
119 – MISPICUSA
008D8162 Missing PICTURE or USAGE clause in previous line.
Explanation:
An elementary field or variable definition must contain one of
the following clauses: PICTURE, COMPUTED BY, or USAGE. With some
USAGE clauses, you must also specify a PICTURE clause to define
the length of the field.
User Action:
Reenter the DECLARE or DEFINE RECORD command, including the
required clauses in the field or variable definition.
120 – MISSETCTX
008D830A Set "<set-name>" is undefined or used out of context.
Explanation:
Your DEC DATATRIEVE record selection expression invalidly
referred to an existing set.
User Action:
To use a record selection expression containing a set name, you
must:
o Establish a single record context in the database by
specifying a set occurrence in one of the domains that make up
the set. Use a FOR statement or the FIND and SELECT statements
to specify a single owner or member record and establish the
context.
o Make sure the domain name you specify before the OWNER or
MEMBER clause is correct for that set. Use the SHOW SETS
command to see which domain, collection, or list in the set
is the owner and which is the member. You must use the OWNER
clause after the owner and the MEMBER clause after the member.
You can use either the MEMBER or OWNER clause with the WITHIN
clause.
121 – MISSUBPAR
008D8282 Missing substitution parameter in command string.
Explanation:
The command string you passed in callable DEC DATATRIEVE did not
contain a necessary !CMD or !VAL substitution parameter.
User Action:
Supply the missing parameter.
122 – MODACCREQ
008D8242 Modify access is required for "<...>".
Explanation:
You cannot modify records unless the record source is readied for
MODIFY or WRITE access.
User Action:
Reready the source for modify access, and then enter the MODIFY
statement to modify a record.
123 – MULOCCDEP
008D8132 Multiple OCCURS DEPENDING ON clauses are not allowed.
Explanation:
You cannot have more than one variable-length list in a record.
User Action:
Reenter the record definition using only one OCCURS DEPENDING
clause. A record can have an OCCURS DEPENDING clause and an
OCCURS clause, specifying a variable-length and a fixed-length
list.
124 – NAMTOOLONG
008D8B32 Field name cannot be longer than 31 characters.
Explanation:
The maximum length of a DEC DATATRIEVE field name is 31
characters.
User Action:
Reenter the DEFINE RECORD command with a shorter field name.
125 – NESTFDI
008D8C22 You cannot nest DISPLAY_FORM statements within DISPLAY_
FORM.
Explanation:
You included a DISPLAY_FORM statement inside another DISPLAY_FORM
statement.
User Action:
Rewrite the statement to eliminate the illegal nesting.
126 – NEWPINBOT
008D86B2 NEW-PAGE and NEW-SECTION are illegal in AT BOTTOM OF
PAGE print list.
Explanation:
NEW_PAGE and NEW_SECTION are illegal elements in AT TOP or AT
BOTTOM OF PAGE.
User Action:
Revise the report specification, and remove NEW_PAGE or NEW_
SECTION from the AT TOP or AT BOTTOM OF PAGE statement.
127 – NOALIAS
008D0583 You cannot READY a database with an alias.
Explanation:
You tried to ready an entire relational or Oracle CODASYL DBMS
database using an alias name. Only specific relations or records
may have aliases.
User Action:
Reenter the READY command with no alias or with the alias on the
relation or record name only.
128 – NOCODTRAN
008D940A Table must include a code/translation pair.
Explanation:
You defined a domain table but did not include the name of a code
field and its corresponding translation field.
User Action:
Edit or redefine the table definition to include the required
code field and translation field.
129 – NOCOLDROP
008D847A No collection with selected record for DROP.
Explanation:
You cannot drop a record if there is no established collection
with a selected record or if the selected record has already been
dropped.
User Action:
Form a collection with a FIND statement and use a SELECT
statement to select a record. Then use the DROP statement to
drop the selected record from the collection.
130 – NOCOLPRO
008D8BBA No collection for project.
Explanation:
The REDUCE statement operates only on an established collection.
User Action:
Form a collection with a FIND statement and then use a REDUCE
statement to obtain the unique values for the fields you specify.
131 – NOCOLSEL
008D834A No collection for select.
Explanation:
You must form a collection before you can select a record.
User Action:
Form a collection with a FIND statement and then use the SELECT
statement to select a record.
132 – NOCOLSOR
008D8352 No collection for sort.
Explanation:
You can use the SORT statement only with an established
collection.
User Action:
Use the SORTED BY clause in an RSE to order records not contained
in an established collection. For example: PRINT EMPLOYEES SORTED
BY LAST_NAME.
You can also use the SORTED BY clause in the RSE of the FIND
statement to order records when a collection is being created. In
addition, you can use a SORT statement to reorder records after
the collection is created.
133 – NOCOMFILE
008D8CDA Expected indirect command file name, encountered end of
line.
Explanation:
DEC DATATRIEVE expected the name of an indirect command file
at the point where the error occurred but you ended the line
instead.
User Action:
Reenter the line, adding the name of the indirect command file
you want to execute.
134 – NOCOMMAND
008D9573 DEC DATATRIEVE is not ready to process a command or
statement
Explanation:
You entered a DEC DATATRIEVE command or statement while the
DECwindows Motif interface was processing a previous command
or statement.
User Action:
Enter the command or statement again when DEC DATATRIEVE has
finished processing the command or statement.
Menu names on the menu bar are gray if DEC DATATRIEVE is not
ready to process a command or statement. When menu names are
black, DEC DATATRIEVE is ready to process a new command or
statement.
135 – NOCOMP6
008D82AA COMP-6 data type is not implemented.
Explanation:
The COMP-6 data type is not supported by DEC DATATRIEVE.
User Action:
Reenter the record or variable definition, specifying an
available data type in the USAGE clause.
136 – NOCONTEXT
008D81F2 "<...>" is undefined or used out of context.
Explanation:
A name is "undefined" if spelled incorrectly or if it does
not exist in any of the definitions DEC DATATRIEVE uses to
process your statement. A name is "used out of context" when
DEC DATATRIEVE cannot use it to determine which records or fields
you want to access.
User Action:
Check to make sure the name specified is valid. If it is, make
corrections to your statement so that DEC DATATRIEVE can link,
for example, a field to the correct record source or a list item
to the correct list (OCCURS field).
If the name used out of context is in an Assignment statement,
make sure it is on the correct side of the equal sign.
If the name used out of context is a list field (or any of its
items), you might have to add to your statement certain clauses
that enable DEC DATATRIEVE to access lists correctly.
137 – NOCTXCON
008D89A2 No context found for "<...>".
Explanation:
There is no subschema for the Oracle CODASYL DBMS domain you
tried to access.
User Action:
Redefine your Oracle CODASYL DBMS database using a valid
subschema and enter the READY command again.
138 – NOCURCOL
008D8342 A current collection has not been established.
Explanation:
You must have a current collection in order to use the SHOW
CURRENT command or PRINT ALL statement.
User Action:
Form a collection with a FIND statement. The format of the FIND
statement is FIND rse.
139 – NODATA
008D8FBA Field "<...>" from view cannot be used as a value.
Explanation:
Your statement tried to access data using the name of the field
in the OCCURS clause of the definition of the view domain. You
must use one of the names associated with the FROM clause to
access data. For example, suppose your view domain is defined:
DOMAIN PARTS_PUBLIC OF PART_S USING
01 PART_T OCCURS FOR PART_S WITH PART_SUPPORT = "FS".
03 PART_ID FROM PART_S.
03 PART_DESC FROM PART_S.
03 PART_PRICE FROM PART_S.
;
The statement PRINT PART_T OF PARTS_PUBLIC will generate the
NODATA error.
User Action:
Reenter the statement, giving the name of a valid field.
140 – NODBMS
008D89AA The Oracle CODASYL DBMS interface is not included in
this image.
Explanation:
You tried to access a Oracle CODASYL DBMS domain using DEC
DATATRIEVE, but Oracle CODASYL DBMS is not on the system you
are using.
User Action:
Use a version of DEC DATATRIEVE that has a Oracle CODASYL DBMS
interface or reinstall DEC DATATRIEVE with Oracle CODASYL DBMS.
141 – NODECTERM
008D97D2 Unable to create DECterm window-execute
DTR$LIBRARY:REMOTE_DECTERM.COM.
Explanation:
DEC DATATRIEVE was not able to create a DECterm window to perform
the operation you requested. This might happen if you are working
with DEC DATATRIEVE in a DECwindows Motif environment and the
DECW$DISPLAY logical is defined to direct output to another node.
User Action:
Invoke DEC DATATRIEVE from a DECwindows Motif terminal and be
sure that the DECW$DISPLAY logical is defined to point to the
node from which you are invoking DEC DATATRIEVE. If DECW$DISPLAY
logical is already defined to point to the node from which DEC
DATATRIEVE is invoked, then report the problem to your system
manager.
You might also try invoking DEC DATATRIEVE in line mode by
assigning a value of true to the DEC DATATRIEVE logical
DTR$NOWINDOWS. This will let you use the following utilities in
line mode: ADT, Guide Mode, DEC DATATRIEVE help, or plots. When
you invoke these utilities in a DECwindows Motif environment, DEC
DATATRIEVE spawns a DECterm window. When you invoke them in line
mode, DEC DATATRIEVE does not involve DECterm.
You might also try invoking the following command procedure at
the DCL level. This allows for the display of a DECterm window on
a remote node.
$ @DTR$LIBRARY:REMOTE_DECTERM.COM node-name
In this command, node-name represents the name of the remote work
station on which the DECterm display is to appear.
See the DEC DATATRIEVE User's Guide for more information on using
DEC DATATRIEVE with DECwindows Motif.
142 – NODISCO
008D8C3A CONNECT, DISCONNECT, and RECONNECT do not work on remote
domains.
Explanation:
You tried to connect, disconnect, or reconnect a local domain
(Oracle CODASYL DBMS record) to a set which is owned by a remote
domain.
User Action:
Reenter the statement, making sure both domains are local or both
are remote.
143 – NOERACRO
008D8AF2 Can't ERASE from a CROSS.
Explanation:
The RSE of an ERASE statement cannot contain a CROSS clause.
User Action:
Reenter the ERASE statement without a CROSS clause.
144 – NOERALIS
008D8AEA Can't ERASE from an OCCURS list.
Explanation:
You cannot use the ERASE statement to change or remove fields
from a list in a hierarchical record.
User Action:
Use the ERASE statement to remove data records from a file, not
to remove fields or list items from a list.
145 – NOERASEQ
008D8AD2 Can't ERASE from a sequential file (domain <domain-
name>).
Explanation:
You cannot erase a record from a sequential file.
User Action:
Either leave the file as it is, or define a new indexed file from
which you can erase records. To define an indexed file, use the
DEFINE FILE command, specifying a key field. Then transfer the
data with a Restructure statement.
146 – NOEXCHANGE
008D9A1A An EXCHANGE record is needed to perform this operation.
Explanation:
For some records (view records for instance), an exchange record
is needed to restructure data to/form a form record.
User Action:
Use an exchange record.
147 – NOEXTRACT
008D8B42 That record contains things that can't be expressed in
the DEC DATATRIEVE language.
Explanation:
You tried to extract a record from the data dictionary that
contains a data type DEC DATATRIEVE does not support.
User Action:
Redefine the field to use a data type that DEC DATATRIEVE
understands.
148 – NOFLDS
008D0581 No field information available.
Explanation:
The relation contains no field definitions.
User Action:
Use the utility supplied by the relational database product you
are using to define relational fields.
149 – NOFMI
008D8F0A There is no forms package available.
Explanation:
You tried to access a domain that uses a form, but the DEC
DATATRIEVE installation you are using was installed without a
forms package.
User Action:
Reinstall DEC DATATRIEVE with a forms package.
150 – NOFORMAT
008D9A02 Unable to load exchange record definition.
Explanation:
DEC DATATRIEVE tried to get the definition of an exchange record,
from the dictionary but it didn't find or failed during the
operation.
User Action:
Check the pathname of the exchange record or its definition.
151 – NOFORMFLD
008D8FDA Field does not exist on form.
Explanation:
The domain you are accessing uses a form. You tried to access a
field that was not defined in the form.
User Action:
Reenter the statement with a valid field name or recreate the
form to define the field you want to access.
152 – NOFTREE
008D9A12 Unable to build the Field Tree.
Explanation:
User Action:
153 – NOGOCDO
008D954A A DEC DATATRIEVE <...> cannot be stored in a CDO
directory.
Explanation:
The CDO format dictionary does not support certain DEC DATATRIEVE
object types. These types include tables, procedures, plots, and
DEC DATATRIEVE databases.
User Action:
Define the object in a DMU format dictionary.
154 – NOGODMU
008D96F2 Definition contains attributes that cannot be stored in
DMU dictionary.
Explanation:
The object being defined contains attributes that cannot be
stored in the DMU format dictionary. Such an object might be a
record that contains a CDO field-level definition included in a
FROM clause or a domain that refers to a CDD$DATABASE object.
User Action:
Define the object in a CDO dictionary.
155 – NOGROPRMT
008D86E2 Illegal assignment to a group data item.
Explanation:
When you assign a value from one group field to another, both
group fields must have at least one elementary field with the
same field name or query name.
User Action:
Reenter the STORE USING or MODIFY USING statement, using a
legal assignment to a group field or to its component elementary
fields.
156 – NOLISTKEY
008D8EFA Field "<field-name>" is part of an OCCURS list, so it
cannot be used as a key.
Explanation:
The field you specified for a key field in DEFINE FILE is part
of an OCCURS list. That means that either the field itself has
an OCCURS clause in its definition or a group field that contains
the field has an OCCURS clause. Since the field you specified
will occur multiple times in the same record, it cannot be a key.
User Action:
If you want to specify a key somewhere within the OCCURS group,
you must REDEFINE the entire OCCURS group and specify one of the
redefine fields as the key.
157 – NOLOGFILE
008D8CEA Expected log file name, encountered end of line.
Explanation:
You must specify a file with the OPEN command.
User Action:
Reenter the OPEN command and include a file specification. The
format of the OPEN command is: OPEN file-spec.
158 – NONAVIGATOR
008D991A Unable to invoke the dictionary navigator.
Explanation:
DEC DATATRIEVE is not able to invoke the DEC DATATRIEVE
Dictionary Navigator window.
User Action:
Contact your system manager to make sure that DEC DATATRIEVE is
properly set up to run on your workstation.
159 – NOPGETPUT
008D8CCA Storing and retrieving from ports is not allowed in
interactive DEC DATATRIEVE.
Explanation:
You tried to store data in or receive data from a port in
interactive DEC DATATRIEVE.
User Action:
Use callable DEC DATATRIEVE if you must access a port.
160 – NOPROJFLD
008D8BB2 You can't have a project list that doesn't reference any
fields.
Explanation:
You tried to reduce to a constant (REDUCE YACHTS TO $10,000, for
example). The reduce key must be a variable or a field in the
record referred to in the REDUCE statement.
User Action:
Reenter the statement, giving a global variable or field in the
record as the reduce key.
161 – NOREMANY
008D8ADA Remote ANY expressions are not supported.
Explanation:
You cannot use the relational operator ANY through the remote
interface.
User Action:
Rewrite the RSE so that it does not include the operator ANY.
162 – NOREMEXP
008D8AFA Remote expression is not supported.
Explanation:
The expression you used is not supported through the remote
interface.
User Action:
Enter a legal expression.
163 – NOSELECTION
008D9702 No current selection exists.
Explanation:
You attempted to perform a DEC DATATRIEVE DECwindows Motif
interface COPY or CUT operation; however, no text was selected
from the output window or from a dialog box text field.
User Action:
Select text from the DEC DATATRIEVE output window or from a DEC
DATATRIEVE dialog box and repeat the operation.
164 – NOSELECTMEM
008D96FA Unable to allocate memory for CUT or COPY or PASTE
selection.
Explanation:
Virtual memory cannot be allocated for a DEC DATATRIEVE
DECwindows Motif interface CUT, COPY, or PASTE operation.
The operation will not take place but you can still use the
DECwindows Motif interface.
User Action:
Try again when more virtual memory is available. If this problem
persists, contact your system manager to determine why there is
insufficient memory.
165 – NOSMG
008D9582 The DEC DATATRIEVE SMG keyboard is not active.
Explanation:
When the DECwindows Motif interface is active, the DTR$DTR call
is not valid.
This call is valid only when the SMG keyboard interface is
active.
User Action:
You must make the call DTR$FINISH_WINDOWS to exit the DECwindows
Motif interface. You can then make the DTR$DTR call to enable the
SMG interface. Once the SMG interface is active, you can make the
remaining calls.
166 – NOSTOREL
008D8ACA Can't STORE into a relative file (domain <domain-name>).
Explanation:
You tried to store a record into a relative file. DEC DATATRIEVE
allows you to retrieve data from a relative file but not to store
in it.
User Action:
Store into the file through a program written in a language that
supports relative files.
167 – NOTDBNAM
008D8982 "<...>" is not a database name.
Explanation:
You referred to a database whose domain definition uses the same
name for the domain path name, the record path name, and the
database path name. These three names must all be unique.
User Action:
Redefine the domain using different names for the domain, record,
and database.
168 – NOTDOMAIN
008D81E2 "<...>" is not a readied source, collection, or list.
Explanation:
The source for a DEC DATATRIEVE collection must be a readied
domain, relation, or Oracle CODASYL DBMS record; a collection; or
a list.
User Action:
Check that you have spelled all names correctly. Ready the
appropriate source, if necessary, and reenter the statement.
169 – NOTDOMNAM
008D81C2 "<...>" is not a domain name.
Explanation:
DEC DATATRIEVE expected a domain name at the point the error
occurred. The name specified is the name of another type of
dictionary object; for example, it might be the name of a record
or table in the current dictionary.
User Action:
Check the list of available domain names for the specified name.
Type SHOW DOMAINS to see the list of domains in your current
dictionary. Reenter the statement or command using a domain name.
170 – NOTELEST
008D9A92 <Non-elementary field xxx cannot be used in a
statistical function.>
Explanation:
A non-elementary field (e.g. a group field) is used with a
statistical function.
User Action:
Check to be sure that the field is an elementary field.
171 – NOTFLDNAM
008D97DA <...> is not a field name.
Explanation:
The name specified is not the name of a field object. The error
may occur when a name other than a defined field name is given as
the argument of a FROM FIELD clause in a record definition.
User Action:
Check to be sure that the field definition exists and that you
have used the field's correct path name.
172 – NOTINFDI
008D8C1A GET_FORM and PUT_FORM are allowed only in DISPLAY_FORM
statements.
Explanation:
You tried to use a GET_FORM or PUT_FORM outside of a DISPLAY_FORM
statement.
User Action:
Reenter the statement using the correct syntax.
173 – NOTMEMSET
008D83EA Domain <...> is not a member of set <...>.
Explanation:
You specified a record type in a STORE or CONNECT statement that
is not a member of the named set.
User Action:
If you specify CURRENCY in STORE statements, make sure the record
type is a member of the set. In CONNECT statements, make sure the
record type to be connected is a member of the set. Use the SHOW
SETS command to see the owner type and member type of each set.
174 – NOTPLTNAM
008D81DA "<...>" is not a plot name.
Explanation:
DEC DATATRIEVE expected a plot name at the point where the error
occurred. The specified name belongs to a dictionary object other
than a plot.
User Action:
Check the specified name against the list of available plot
names. Type SHOW PLOTS to see the list of plots in your current
dictionary. Reenter the statement or command using a plot name.
175 – NOTPRCNAM
008D81CA "<...>" is not a procedure name.
Explanation:
DEC DATATRIEVE expected a procedure name at the point where the
error occurred. The specified name belongs to a dictionary object
other than a procedure.
User Action:
Check the name specified against the list of available procedure
names. Type SHOW PROCEDURES to see a list of procedures in your
current dictionary. Reenter the statement or command using a
procedure name.
176 – NOTRDYDOM
008D81AA "<...>" is not a readied source.
Explanation:
You tried to store into or show fields for a record source that
has not been readied, or you specified an invalid domain name.
User Action:
Check that you have spelled the source name correctly.
If you have not readied the source you want to access, use the
READY command to do so, and then reenter your statement. The SHOW
READY command tells you what sources you have readied.
177 – NOTRECNAM
008D81BA "<...>" is not a record name.
Explanation:
The statement or command requires a record name at the point
where the error occurred. The name specified is not a record name
but rather belongs to a dictionary object other than a record.
User Action:
Check the specified name against the list of available record
names. Type SHOW RECORDS to see the list of record names in your
current dictionary. Reenter the statement or command using a
record name.
178 – NOTRELNAM
008D0589 "<...>" is not a valid relation name for database
"<...>".
Explanation:
The name you entered does not exist in the relational database
you are using.
User Action:
Enter the READY command with a valid relation name. To find out
what relations exist in your database, invoke the relational
utility and use the SHOW RELATIONS command.
179 – NOTRGREC
008D83BA No target record for <...>.
Explanation:
You must specify a target record with an ERASE or MODIFY
statement.
User Action:
Use a FOR loop or a SELECT statement to designate a target record
for the ERASE or MODIFY statement.
180 – NOTSET
008D8302 "<...>" is not a set.
Explanation:
The name you specified in the WITHIN, MEMBER, or OWNER clause is
not a set name.
User Action:
Use a SHOW SETS command to identify valid set names.
181 – NOTSYNONYM
008D8E82 "<...>" is not the name of a synonym.
Explanation:
The name you specified in a RELEASE SYNONYM command is not a
synonym.
User Action:
Enter the correct name with the RELEASE SYNONYM command. You
can use the SHOW SYNONYM command to see the synonyms you have
defined.
182 – NOTTABNAM
008D81D2 "<...>" is not a table name.
Explanation:
The statement or command requires a table name at the point where
the error occurred. The name specified is not a table name but
belongs to a dictionary object other than a table.
User Action:
Check the specified name against the list of available table
names. Type SHOW TABLES to see the list of table names in your
current dictionary. Reenter the statement or command using a
table name.
183 – NOTVALPRI
008D846A "<...>" is not a valid privilege code.
Explanation:
You can assign privileges only by using one or more of the
following privilege codes in the DEFINEP command: CDEFGHMPRSUWX.
User Action:
Reenter the DEFINEP command, using one or more of the privilege
codes in the GRANT, DENY, or BANISH clauses.
184 – NOUDKS
008D8CD2 User Defined Keywords are not allowed in interactive DEC
DATATRIEVE.
Explanation:
You can use User Defined Keywords only through the call
interface.
User Action:
Do not use User Defined Keywords in interactive DEC DATATRIEVE.
185 – NOVALFROM
008D83B2 Value not found from record or table.
Explanation:
The table that verifies the value that you entered does not
contain the value you have specified. The table must contain
the value you want to enter.
User Action:
Check the value you have entered to be sure that it is accurate.
If it is not, reenter a correct value. To see what values are
included in the table, do one of the following:
o For dictionary tables, use a SHOW table-path-name command.
o For domain tables, use a PRINT domain statement for the domain
associated with the table.
If the value you entered is accurate, you might want to add to
the list of table values (in a dictionary table definition),
update the records in the source domain (for a domain table), or
add an ELSE clause to the table definition (in the definition of
either type of table).
186 – NOVIEWSTO
008D8A92 Illegal STORE into a view.
Explanation:
You cannot store data into a view domain.
User Action:
If you want a physical file corresponding to the view domain,
define another domain with a record definition and a physical
file. Then use the view domain as a source for storing data in
the new domain. Use a statement of the following form:
FOR view-domain STORE domain USING assignment-statement
187 – NOWINDOWS
008D956A The DEC DATATRIEVE window interface is not active.
Explanation:
This error is generated in one of two ways:
o One of the following calls was made while the DECwindows Motif
interface is inactive:
- DTR$FINISH_WINDOWS
- DTR$WINDOW_MSG
- DTR$WINDOW_OUTPUT
o DECwindows Motif cannot be initialized when the DTR$WINDOWS
call is made. This is indicated when a DTR$_NOWINDOWS status
is returned to the caller.
User Action:
Take one of the following actions:
o If the error was generated because the user made a call to
DTR$FINISH_WINDOWS, DTR$WINDOW_MSG, or DTR$WINDOW_OUTPUT
prior to activating the DECwindows Motif interface, then
make a DTR$FINISH call followed by a DTR$WINDOWS call. The
DTR$WINDOWS call initializes the DECwindows Motif terminal
handler. The call DTR$FINISH_WINDOWS ends a DEC DATATRIEVE
session with DECwindows Motif.
o If the error was generated because the DECwindows Motif
interface could not be initialized, report the situation to
your system manager.
188 – NOWITHF
008D9A0A It is not possible to use the WITH_FORM statement when a
SET NO FORM is active.
Explanation:
The user tried to use a WITH_FORM statement when the use of forms
is disabled.
User Action:
Enable the use of forms or avoid using DECforms.
189 – NO_DFPID
008D80C2 One of PW, UIC, USER, or TERMINAL must be specified.
Explanation:
You entered a DEFINEP command but did not specify any user
identification criteria.
User Action:
Reenter the command, specifying a password, user identification
code (for example, [100,100]), a username, or terminal
specification (for example, TTE1:).
190 – NO_DFPPRI
008D80CA One of GRANT, DENY, or BANISH must be specified.
Explanation:
You entered a DEFINEP command but did not specify any privileges.
You must include at least one privilege for at least one of the
privilege specifications.
User Action:
Reenter the command with a privilege list in at least one of the
clauses GRANT, DENY, or BANISH.
191 – NULPRILIS
008D81FA Null print list.
Explanation:
Unless you are working with a collection, you must specify what
you want to display in the PRINT statement.
User Action:
Specify an RSE in the PRINT statement or establish a collection.
192 – OBJTOOBIG
008D8382 Print object is too large for line width.
Explanation:
The print object is longer than the COLUMNS_PAGE setting.
User Action:
Enter a SET COLUMNS_PAGE statement and assign it a value that is
greater than the character length of the print object.
193 – OCCDEPOCC
008D8B8A An OCCURS DEPENDING ON is not allowed within an OCCURS
list.
Explanation:
You cannot include a variable-length list within a fixed-length
list.
User Action:
Reformulate the field definitions to specify a different list
structure. It is permissible to include a fixed-length list
within a variable-length list.
194 – OCCNOTLAS
008D813A Only fields with higher level numbers are allowed after
an OCCURS DEPENDING ON.
Explanation:
No other field definition can follow the last elementary field in
the group field containing the OCCURS DEPENDING ON clause.
User Action:
Reenter the DEFINE RECORD command, making sure that the OCCURS
DEPENDING ON group field and its elementary fields are the last
fields specified in the record definition.
195 – OCCOUTRAN
008D8142 OCCURS DEPENDING ON count out of range.
Explanation:
The list cannot contain the number of items specified. The range
of values allowed in this list is determined by the OCCURS clause
in the list field definition.
User Action:
Reenter a value within the range allowed for the list by the
record definition or edit the record definition and restructure
the domain so that the list field can contain more items.
196 – OCCREQFRO
008D8ABA OCCURS clause requires at least one FROM field at a
lower level.
Explanation:
The view domain definition must contain at least one FROM clause.
User Action:
Reenter the DEFINE DOMAIN command, specifying at least one field
with a FROM clause.
197 – OLDPLOT
008D8E52 The plot <plot-name> is stored in an incompatible
format. You must extract and redefine it.
Explanation:
The plot is stored in an incompatible format.
User Action:
Extract and redefine the plot.
198 – ONEEPERM
008D897A Only one "E" permitted in PICTURE or EDIT string.
Explanation:
Use only one E in an edit string to separate the two parts of
floating-point or scientific notation.
User Action:
Reenter the field or variable definition. Place one E in the edit
string, separating the mantissa and the exponent edit string.
199 – OUTRANCOL
008D835A Record number out of range for collection.
Explanation:
The record number referred to by the SELECT statement exceeds the
number of records in the collection.
User Action:
Reenter the SELECT statement with a different value expression or
other argument.
200 – PASTELENGTH
008D972A Item to be pasted is too large for text field.
Explanation:
The material that you are trying to paste from the DECwindows
Motif clipboard to a text entry field is too large to fit in the
text entry field area.
User Action:
Paste the material to the scrollable area of the DEC DATATRIEVE
main application window. Select a portion of the material that
will fit into the text field area and copy that to the clipboard.
Then, paste the shorter material into the text entry field area.
201 – PATNOTDIR
008D824A Path node "<...>" is not a directory.
Explanation:
You used the SET DICTIONARY for an object that is not a
dictionary.
User Action:
Specify a dictionary name in the command. Use the SHOW
DICTIONARIES command to see the dictionaries available to you.
202 – PICUSAMAT
008D8152 PICTURE and USAGE clauses do not match in previous line.
Explanation:
The PICTURE clause is incompatible with the specified USAGE
clause. Both these clauses specify the internal storage format
of a data item. Most USAGE clauses define numeric data and
the PICTURE clause, when needed, must also specify numeric
characters.
User Action:
Correct the field definition so that the PICTURE string
characters are appropriate for the USAGE clause. If you
mistakenly used a PICTURE clause to format the data, replace
the PICTURE clause with an EDIT_STRING clause.
203 – PLOBADARG
008D8442 Too many parameters for plot definition.
Explanation:
Your plot statement includes too many field names.
User Action:
Reenter the plot statement with the correct number of fields.
204 – PLOENTMIS
008D843A Plot entry point is not defined.
Explanation:
The plot you tried to use is corrupt; it does not contain a valid
entry point.
User Action:
If the plot is from DIGITAL, submit an SPR, if you are eligible.
If the plot is user defined, redefine the plot with the correct
entry point information.
205 – PLOHDRLNG
008D941A A title for a plot cannot exceed 49 characters.
Explanation:
The title line you entered for the plot was longer than 49
characters. The PLOT TITLE statement centers one to three lines
of a title above the base plot. Each line of the title must be 49
characters or less.
User Action:
Reenter the PLOT TITLE statement and reduce the number of
characters in each line to 49 or less.
206 – PLOIDXRAN
008D845A Plot index out of range. Vector: <...>, index: "<...>"
Explanation:
The plot index is out of range.
User Action:
When you see this error in interactive DEC DATATRIEVE, please
submit an SPR if you are eligible.
207 – PLOLOCRAN
008D8462 Plot location fn out of range. Fn: <text>, value:
<number>
Explanation:
The plot cannot handle all of the data. The coordinates cannot be
plotted on the screen.
User Action:
Make sure the record stream specified contains records.
208 – PLOTOOBIG
008D945A Maximum plot size exceeded.
Explanation:
The internal data structures needed to produce this plot exceeded
the DEC DATATRIEVE limits.
User Action:
Reduce the number of records used for this plot.
209 – PRIVVIOL
008D80E2 Privilege violation-access denied.
Explanation:
You do not have sufficient privileges for the operation you
attempted to perform.
User Action:
Use the SHOW PRIVILEGES command to see your privileges. Use
the DEFINEP command to grant yourself additional privileges.
Check with your system manager if you cannot grant yourself the
necessary privileges.
210 – PROTNOTSUPP
008D9822 Use CDO to define protection for element <...>.
Explanation:
The element for which you are attempting to define, display,
or delete protection is not a domain, record, or dictionary
directory.
User Action:
You must use the CDO utility to define, display, or delete the
ACLs for this object.
211 – PURELMSEM
008D92FA You cannot purge a specific version of object "<...>".
Explanation:
The PURGE command deletes all but the highest versions of
dictionary objects. Therefore, you cannot specify version numbers
in an object path name.
User Action:
Do not include version numbers within an object path name when
using the PURGE command. To delete specific versions, use the
DELETE command.
212 – PURKEEPBAD
008D92E2 The KEEP value for PURGE must be greater than zero.
Explanation:
When you use the KEEP argument of the PURGE command, you cannot
specify a value less than or equal to zero.
User Action:
Make sure you specify a number greater than zero for the KEEP
argument of the PURGE command.
213 – RDBCOMPOUND
008D92C2 Compound statements referencing relational fields may
not contain COMMITs.
Explanation:
You used a COMMIT statement within a compound statement. The
compound statement contained a record selection expression that
referred to a relation or relational field. DEC DATATRIEVE does
not allow this.
User Action:
Make sure compound statements that refer to relations or
relational fields do not contain COMMIT statements.
214 – RDBNOREL
008D932A Database "<...>" cannot be readied since it contains no
relations.
Explanation:
You cannot ready a relational database that does not have any
relations defined for it.
User Action:
Define relations for the relational database.
215 – RDBREQSYNC
008D92CA Statement aborted by relational database due to an
invalid request for data.
Explanation:
An invalid data request has been sent from DEC DATATRIEVE to the
relational database system.
User Action:
Please submit an SPR if you are eligible.
216 – RDSNOTACT
008D82B2 Remote DDMF server could not be activated.
Explanation:
You tried to access a remote domain, but DEC DATATRIEVE was not
able to start the DDMF server on the remote system.
User Action:
The problem is on the remote node.
217 – RDSTERMIN
008D82BA Remote DDMF server terminated unexpectedly.
Explanation:
The DDMF server on the remote node was unexpectedly terminated.
User Action:
Find the cause of termination on the remote node.
218 – RDYNOTOPT
008D9420 Use of optimization for record "<...>" failed.
Processing will continue.
Explanation:
Use of optimization to define the file or to ready the domain,
relation, or Oracle CODASYL DBMS record has failed. The command
is processed, but the process takes longer because optimization
is not used.
User Action:
None.
219 – RECERSD
008D83CA You can not use a field from a record that has been
erased.
Explanation:
You tried to retrieve information from a record you erased.
User Action:
Use the STORE command to store a new record, or select an
existing record.
220 – RECEXCMAX
008D92D2 Record size exceeds maximum.
Explanation:
You created a record longer than 65,535 bytes. Records longer
than 65,535 bytes are illegal.
User Action:
Make sure the record definitions you create are shorter than
65,535 bytes. To avoid such long records, use care when defining
records with multiple OCCURS clauses.
221 – RECNOTCUR
008D9430 Record "<...>" uses old record format. Processing will
continue, but for optimization you must redefine record.
Explanation:
A record that is defined using the OPTIMIZE qualifier under a
previous version of DEC DATATRIEVE is not compatible with the
current version of DEC DATATRIEVE. The process will continue;
however, optimization is not used.
User Action:
To update the record so that formats are compatible, you must
redefine the record in one of two ways:
o Edit the record without making any changes.
o Extract the record using the full dictionary or relative path
name; make no changes to the definition; then execute the
resulting command file.
222 – RECNOTOPT
008D9410 Record will be defined, but will not be optimized.
Explanation:
Optimization of the record failed. The record will be defined,
but it will not be optimized. DEC DATATRIEVE removes the word
OPTIMIZE from the record definition.
User Action:
If a message concerning insufficient virtual memory preceded this
message, then free up memory space by using the FINISH command to
end access to other readied domains, relations, or Oracle CODASYL
DBMS records. Edit the record again and replace the OPTIMIZE
qualifier.
223 – RECPREDRO
008D8482 Record has been dropped from the collection.
Explanation:
You selected a record, dropped it, then tried to access it again.
User Action:
Find the collection again.
224 – RELINK
008D9522 Please relink your DEC DATATRIEVE image or reinstall DEC
DATATRIEVE.
Explanation:
The DTR image was linked under a OpenVMS V4 system and is being
run from a OpenVMS V5 system.
User Action:
Please relink your DEC DATATRIEVE image or reinstall DEC
DATATRIEVE.
225 – REMCROSS
008D9212 CROSS can only be used on domains with the same node
specifications.
Explanation:
You tried to cross a remote domain with a local domain. This is
not allowed.
User Action:
Reenter the statement, making sure all domains are local or all
are remote.
226 – REMNOCROSS
008D921A This remote node does not support CROSS.
Explanation:
The system on which you attempted to perform a CROSS operation
does not support the CROSS clause.
User Action:
If you wish to perform the cross, transfer the data to a system
which has a DEC DATATRIEVE that supports the CROSS clause.
227 – REMSELBOO
008D8FAA SELECT with a boolean is not supported for remote
collections.
Explanation:
This is a restriction.
User Action:
Do not use the SELECT statement with Boolean expressions on
remote collections.
228 – REMSYNERR
008D82F2 DDMF remote synchronization error.
Explanation:
While you were accessing a remote domain, DEC DATATRIEVE
encountered a software inconsistency.
User Action:
See the person responsible for DEC DATATRIEVE on the remote
system.
229 – REPNOTFIT
008D869A Print object(s) too long to fit on report line.
Explanation:
The print object is longer than the Report Writer COLUMNS_PAGE
specification.
User Action:
Reenter the report specification and use a larger value in the
SET COLUMNS_PAGE statement.
230 – REQDICMIS
008D8232 Required dictionary attribute <...> missing.
Explanation:
A Oracle CDD/Repository object did not have the attributes DEC
DATATRIEVE expected. Either it is the wrong type of object for
the operation attempted (for example, a Oracle CODASYL DBMS
record used in a DEC DATATRIEVE domain) or the object did not
get stored in the data dictionary correctly.
User Action:
Check that you are using the correct type of dictionary object
for the operation. If so, and the object was stored correctly
in the data dictionary, you may have encountered an error in
the software. If you are eligible, submit a Software Performance
Report.
231 – RERDYFAIL
008D82A2 Re-ready failed. Domain automatically finished.
Explanation:
You tried to ready domain based on a RMS file again, but RMS
returned an error. DEC DATATRIEVE automatically finished the
domain at the old access mode.
User Action:
Try reentering the READY command. If the error continues, see
your system manager.
232 – RMSCHG
008D8EE2 You cannot modify the value of an RMS key field that
does not allow changes.
Explanation:
Some RMS key fields are defined so that once a value is stored in
the field it cannot be changed.
User Action:
Since you cannot change the value of the field, the only way to
have a record with that change is to erase the old record and
store a new one. It is better to store before you erase the old
record. If you made the change accidentally at a *.prompt, then
retype the query and press TAB and RETURN at that prompt. You can
find out which fields are keys by entering a SHOW FIELDS command.
233 – RMSDUP
008D8EEA You cannot store a duplicate value in an RMS key field
that doesn't allow duplicates.
Explanation:
Some fields that areRMS keys are defined so that it is not
possible to have two records with the same value stored in that
field.
User Action:
If you made a mistake in entering data at a *.prompt, then retype
the query and enter the proper data. You can find out which
fields are keys by entering a SHOW FIELDS command.
234 – RPODUPAT
008D844A Duplicate control break specified for <...>.
Explanation:
You specified more than one control break for a single control
group.
User Action:
Include only one control break for each group.
235 – RPOEXCPRI
008D841A Excessive PRINT statements for REPORT.
Explanation:
You can only include one PRINT statement in a report
specification.
User Action:
Eliminate one of the PRINT statements or combine the two into
one. You may include one or more AT statements in addition to the
PRINT statement.
236 – RPOFMTRJT
008D8422 REPORT formatting clause out of context.
Explanation:
The NEW_SECTION, REPORT_HEADER, or COLUMN_HEADER clause in a
report is entered in the wrong place.
User Action:
Enter the clauses in the right order.
237 – SELBADBOO
008D8B22 Unable to select a record that satisfies the Boolean.
Explanation:
There is no record in the collection that meets the conditions
set forth in the Boolean expression.
User Action:
If you still require a selected record, either change the
composition of the source collection or change the Boolean
expression within the RSE.
238 – SELNOTFND
008D8362 Selected record not found.
Explanation:
You selected a record from a collection, erased it, then tried
to select it again. (A READY command generates this message if
during a reready of a domain another user readies the domain and
erases your selected record.)
User Action:
None. The record has been erased.
239 – SELRECREQ
008D83DA No selected record in collection.
Explanation:
There is no record in the collection that meets the condition of
your record selection expression.
User Action:
If you still require a selected record, either change the
composition of the source collection or change the record
selection expression.
240 – SETNOTUSE
008D8B62 Set "<set-name>" can not be used - either an owner or a
member source is not ready.
Explanation:
The statement you entered referred to a set for which not all
necessary Oracle CODASYL DBMS domains or records are readied.
User Action:
Ready the missing sources and reenter the statement.
241 – SORTOPEN
008D8B4A Error creating the work files for the sort.
Explanation:
The SORT statement could not open its work files. This usually
means you have exceeded your quota for open files or run out of
disk space.
User Action:
Check your quotas for open files and disk space and have these
quotas enlarged if necessary.
242 – SYNTAX
008D8112 Expected <...>, encountered "<...>".
Explanation:
You have made a syntax error.
User Action:
See help for the statement, command, clause, or expression that
you used. Correct the syntax error and enter the command or
statement again.
243 – SYNTAX_ERR
Syntax error at or near "!AD" .
Explanation:
A general syntax error has been discovered which cannot be
considered in the general schema of Expected X, Encountered Y.
User Action:
Check the syntax of command/statement.
244 – TOOMANDIG
008D815A Too many digits in numeric string (max is 18).
Explanation:
A numeric PICTURE clause cannot specify more than 31 digits (PIC
9(31)). When an item is defined as USAGE COMP, the associated
PICTURE clause cannot specify more than 18 digits (PIC9(18)).
User Action:
Correct the PICTURE clause for the field so that the number of
digits specified is no larger than the maximum number allowed for
that field.
245 – TOOMNYFLD
008D8B72 Maximum number of fields exceeded.
Explanation:
In the report writer, you have specified too many fields for the
number of columns specified.
User Action:
Reduce the number of fields.
246 – TXTNOTFND
008D826A Source text for <...> not found in dictionary.
Explanation:
You tried to show a dictionary object such as a record or
procedure but there was no text in the data dictionary.
User Action:
See your system manager for help.
247 – UNSCONV
008D8212 Unsupported data conversion.
Explanation:
Your definition uses an unsupported data type.
User Action:
Redefine the field or variable to use a data type that DEC
DATATRIEVE supports. See the DEC DATATRIEVE Reference Manual
for a list of valid data types.
248 – UNTERQUO
008D817A Unterminated quoted string.
Explanation:
You entered an alphanumeric literal string without including the
terminating quotation mark.
User Action:
Reenter the statement and add the missing quotation mark.
249 – UNWIND
008D821A Execution terminated by operator.
Explanation:
You entered a CTRL/C to terminate your command or statement.
User Action:
None. DEC DATATRIEVE will handle all the cleanup. If you are
storing or modifying records, data may be lost.
250 – USESLOEXH
008D8102 DDMF user slots are exhausted - cannot initialize
another DEC DATATRIEVE stream.
Explanation:
In callable DEC DATATRIEVE, your program has used all five slots
available for DAB information.
User Action:
Call DTR$FINISH to free slots.
251 – VALIDERR
008D838A Validation error for field <field-name>.
Explanation:
The value assignment for a field or variable does not meet the
Boolean test in the VALID IF clause of the definition.
User Action:
Check the definition to see which values are allowed. Then
reenter the Assignment statement using an acceptable value.
252 – VIEDOMUND
008D8492 Domain <domain-name> was not included in domain list for
view.
Explanation:
The view you tried to ready references a domain that DEC
DATATRIEVE cannot find.
User Action:
Define a domain for the view or redefine the view to reference
an existing domain, then reready the view. You can use the SHOW
DOMAINS commands to see what existing domains are available.
253 – VIEFIEUND
008D848A Field <field-name> cannot be found in domain <domain-
name>.
Explanation:
The view you tried to ready contains a field that does not exist
in the domain the view references.
User Action:
Redefine the view to specify only those fields that are contained
in the domain.
254 – WRIACCREQ
008D823A Write access is required for "<...>".
Explanation:
You cannot store or erase records unless the record source is
readied for WRITE access.
User Action:
Reready the source for write access and enter the STORE or ERASE
statement.
255 – WRODOMTYP
008D8372 "<...>" is not a domain based on a RMS file.
Explanation:
You tried to define a file, but the domain you specified is not a
domain based on a RMS file.
User Action:
Reenter the definition with a valid domain name.
256 – WRONGSTALL
008D810A Wrong call for current stallpoint.
Explanation:
Your program calls the wrong callable DEC DATATRIEVE routine for
the stallpoint. For example, DTR$GET_STRING can be called only
when the stallpoint is DTR$K_STL_UDK.
User Action:
Make sure you are at the correct stallpoint for this call. If you
see this error in interactive DEC DATATRIEVE, please submit an
SPR if you are eligible.