Messages 001 - 2000
EDA001 THE NAME OF THE FILE OR THE WORD 'FILE' IS MISSING
The request statement is missing the word FILE, or data field names were encountered before the file's identity was provided.
EDA002 A WORD IS NOT RECOGNIZED:
A word which is not a reserved word begins a phrase. A reserved word may have been misspelled or there is a syntax error. Reserved words are IF, BY, AND, etc.
EDA003 THE FIELDNAME IS NOT RECOGNIZED:
A word which is assumed to be the name of a data field does not appear on the list of names or aliases for the file. Check the spelling of the field name.
EDA004 THE OPTION ON THE VERB OBJECT IS NOT RECOGNIZED:
The prefix in front of the field name is not valid. Valid options include: MAX., MIN., AVE., ASQ., FST., LST., PCT., RPCT., TOT., SUM., CNT., ALL., SEG., ST., and CT.
EDA005 THE NUMBER OF VERB OBJECTS EXCEEDS THE MAXIMUM
Up to 256 fields may be used in a single report request. This total does not include sort fields (for example, BY and ACROSS fields).
EDA006 THE FORMAT OF THE TEST VALUE IS INCONSISTENT WITH FIELD FORMAT:
The value supplied as a literal in an IF or WHERE test must match the format type of the field being tested. For example, an integer field may not be tested against a nonnumeric character string.
EDA007 THE REQUEST STATEMENT DOES NOT CONTAIN A VERB
The request statement does not contain a verb, and the heading, if any, does not contain a reference to any data fields implying a verb.
EDA008 THE NUMBER OF IN-GROUPS-OF/IN-RANGES-OF FIELDS EXCEEDS 5
The number of sort fields grouped into ranges exceeds five.
EDA009 INCOMPLETE REQUEST STATEMENT
The request statement is terminated with an END, RUN, semicolon (;), or end-of-file before the request is complete.
EDA010 THE NUMBER OF SORT FIELDS EXCEEDS THE MAXIMUM:
For a single TABLE or GRAPH request, there is a limit of 32 BY or ACROSS fields.
EDA011 THE TEST RELATION IS NOT RECOGNIZED:
The test relation in an IF or WHERE phrase is not a valid type of test condition, such as IS, FROM, TO, EQ, NE, GE, GT, LE, LT, etc.
EDA012 THE WORD 'FILE' OR THE FILENAME APPEARS TWICE
The word FILE appears more than once in the request statement. A file has already been identified and a second file name is not allowed.
EDA013 THE 'ON FIELDNAME' FIELD IS NOT A SORT FIELD:
The ON phrase requires that the field named also be used in a BY phrase as a sort break.
EDA014 THE NUMBER OF ACROSS SORT FIELDS EXCEEDS THE MAXIMUM
There is a limit of 5 ACROSS phrases in a request statement.
EDA015 THE TEST VALUE IS LONGER THAN THE FIELD FORMAT LENGTH:
An IF or WHERE test compares an alphanumeric field against a value which is longer than the field format. Or, a text field may have been used in an FML 'FOR' phrase, which is not supported. Or, a literal longer than 15 digits was used to test a short packed field.
EDA016 THE TRUNCATED FIELDNAME IS NOT UNIQUE:
The short form used to identify a data field is not unique, and could apply to another field. Use additional letters, or the full field name or alias, to make it unique.
EDA017 THE NUMBER OF TEST CONDITIONS EXCEEDS THE MAXIMUM
The total length of the literal test values in the IF phrases exceeds the maximum capacity for storing the literal data. For FOCUS databases, the limit is 32767 literals; for other files, the limit is about 3000 characters.
EDA018 THE OPTION IN THE 'ON' PHRASE IS INVALID:
An action named after the field in the ON phrase is not one of the valid options such as SKIP-LINE, SUB-TOTAL, or SUMMARIZE.
EDA019 THERE ARE TOO MANY VERBS IN THE REQUEST
There is a limit of 16 verbs (for example, PRINT, SUM, etc.) in a single report request.
EDA020 THE SETS OF SORT PHRASES ARE INCONSISTENT
In a request statement with more than one verb, the sort fields for each verb must include the sort fields of the previous verb before any additional sort fields. For example, SUM A BY B SUM D BY C is invalid, whereas SUM A BY B SUM D BY B BY C is correct.
EDA021 THE MAXIMUM HEADING/FOOTING SIZE HAS BEEN EXCEEDED
The free text supplied for the heading and/or footing exceeds the allowed maximum. Try eliminating trailing blanks within double quotes from the heading and footing text.
EDA022 THE MAXIMUM SPACE FOR COLUMN TITLES HAS BEEN EXCEEDED
Each displayed data field may have from 1 to 5 lines as a column title. The total area allotted for column titles has been exceeded.
EDA023 'BY' FIELDS FROM PREVIOUS VERB ARE MISSING
Multiple verbs are present, and one verb statement does not have all of the sort control fields of the previous statement. For example, the following is an error: SUM A BY B BY C SUM D BY B. The second phrase should contain BY B BY C as the first BYs in the sentence.
EDA024 LIST OR PRINT MUST BE THE LAST VERB IN A MULTI-VERB REQUEST
The verbs LIST and PRINT can only be used as the last (or only) verb in a report request. For example, the correct form is: SUM A BY B LIST D BY B.
EDA025 THE 'IN-GROUPS-OF' VALUE IS NOT NUMERIC:
The test literal for the IN-GROUPS-OF test is not a valid number.
EDA026 THE REPORT IS NO LONGER AVAILABLE
The last report is no longer available for use by a command such as RETYPE, HOLD, OR SAVE. Reissue the report request. RETYPE is not available after TABLEF, and OFFLINE from within Hot Screen is not available.
EDA027 YOU CANNOT USE 'IN-GROUPS-OF' ON A NON-NUMERIC FIELD:
The data field does not have a numeric format, so it cannot be grouped into ranges.
EDA028 INCLUDES OR EXCLUDES TEST CANNOT BE USED ON AN EXTERNAL FILE
The test conditions INCLUDES and EXCLUDES can only be applied to FOCUS files where the order of occurrence of record segments can be controlled.
EDA029 ALL SORT KEYS ARE NOT IN A SINGLE TOP-TO-BOTTOM SEGMENT PATH
A report request cannot contain sort fields from multiple paths in the database. The resulting report would incorrectly reflect the relationships between the data fields. Fields with DST prefix in PRINT are changed into BY fields.
EDA030 ALL VERB OBJECTS MUST BE IN THE SAME PATH AS THEIR SORT FIELDS
A verb object is being sorted by a field on a different path in the database. A multi-verb request where each set of verb objects has its own sort fields may be appropriate, or an alternate view can be used. Fields with DST prefix in PRINT are changed into BY fields.
EDA031 THE MAXIMUM NUMBER OF 'ACROSS' VALUES HAS BEEN EXCEEDED
Up to 64 distinct values may be retrieved for an ACROSS field when using GRAPH.
EDA032 RECTYPE FIELD IS MISSING FROM MULTI-RECORD FILE DESCRIPTION:
In an external (non-FOCUS) file description, one of the record segments is missing a required identification field named RECTYPE.
EDA033 THE FIELD IN THE TOTAL TEST MUST ALSO BE VERB OBJECT:
The test condition for IF TOTAL or WHERE TOTAL does not refer to a data field which is being accumulated. It must refer to a verb object field which is used in the request statement.
EDA034 THE PRINT LINE EXCEEDS THE MAXIMUM LINE WIDTH. WIDTH IS:
The number of characters in the print line exceeds the maximum page width and therefore cannot be displayed. Compression to one space between columns has been tried in an effort to fit the report on the page. Use SET PANEL to break up the report.
EDA035 ERROR IN THE FORMAT OF THE COMPUTED FIELD DEFINITION:
The format of the computed field given after the name is not valid. Check that the field name does not contain a slash (/).
EDA036 NO DATA FOUND FOR THE FOCUS FILE NAMED:
Data cannot be located for the FOCUS file. A USE command may be needed.
EDA037 THE REQUEST IS INCOMPATIBLE WITH TABLEF
Some report options are not compatible with the way TABLEF retrieves and prints without sorting. For example, ACROSS and FOR cannot be used in a TABLEF request.
EDA038 THE EXTERNAL FILE DOES NOT CONTAIN ANY TEST LITERALS:
The option IF field EQ (ddname) cannot find any values in the file to use as tests.
EDA039 THE OPTION AFTER 'ON TABLE' IS NOT RECOGNIZED:
The word after TABLE in the phrase ON TABLE is not a valid option. Valid options include HOLD, SUBFOOT, SUMMARIZE, etc.
EDA040 THE FIELD NAMED IN THE SUB-TOTAL MUST BE A VERB OBJECT:
In a list of field names following a SUB-TOTAL request, one of the names must be a verb object field which is retrieved for display.
EDA041 THE DATA FIELD REFERENCED IS NOT PART OF THE REQUEST:
An option is requested when the value changes for a field that has not yet been mentioned in the request.
EDA042 THE SUBTOTAL OPTION MUST APPLY TO VERB OBJECTS:
An option, such as SUBTOTAL, is requested on a field which is not a verb object.
EDA043 THE HOLD OPTION AFTER THE MATCH IS NOT RECOGNIZED:
The relation in the MATCH process is not a valid one, such as OLD-OR-NEW, NEW-NOT-OLD, etc.
EDA044 THIS OPERATION IS NOT ALLOWED IN MATCH COMMAND:
Some request options such as BY HIGHEST n and COMPUTE are not permitted in a MATCH FILE request.
EDA045 THE FIELDNAME USED IN A VIEW IS NOT INDEXED:
The form MODIFY FILE filename.fieldname requires that the field name be an indexed field.
EDA046 THE FIELDNAME USED IN A VIEW IS NOT IN A REAL SEGMENT:
The form FILE filename.fieldname requires that the view of the file be from the vantage point of a real data field, not a cross-referenced field.
EDA047 THE USER DOES NOT HAVE SUFFICIENT ACCESS RIGHTS TO THE FILE:
The user must have a password that provides the appropriate access level before the file can be referenced. Issue the PASS or SET PASS command and provide a suitable password.
EDA048 DBA ERROR. INVALID ACCESS PARAMETER:
In the DBA section of the Master File Description, there is an invalid type of access entered in the ACCESS= parameter.
EDA049 DBA ERROR. INVALID RESTRICT PARAMETER:
In the DBA section of the Master File Description, there is an invalid word after RESTRICT=.
EDA050 DBA ERROR. RESTRICTED SEGMENT NAME NOT RECOGNIZED:
In the DBA section of the Master File Description, the name of a segment is not recognized. Check the list of segment names.
EDA051 DBA ERROR. RESTRICTED FIELDNAME NOT RECOGNIZED:
In the DBA section of the Master File Description, a field name is not valid. Check the list of field names and aliases in the file.
EDA052 THE USER DOES NOT HAVE ACCESS TO THE FIELD:
The password provided does not allow access to the field mentioned. Provide an appropriate password using the SET PASS or the PASS command.
EDA053 DBA ERROR. INVALID ATTRIBUTE IN MASTER FILE:
In the DBA section of the Master File Description, an attribute such as ACCESS or RESTRICT is not recognized.
EDA054 THE FILE IS PROTECTED BY A DIFFERENT DATA ADMINISTRATOR:
The DBA password in the Master File Description does not match the password in the FOCUS file. The RESTRICT command may be needed to change the DBA password. This error may also occur when a FOCUS file is referenced as if it were a FOCUS database.
EDA055 DBA ERROR. VALUE EXPRESSION PROVIDED WITHOUT RESTRICT=VALUE:
In the DBA section of the Master File Description, the VALUE= parameter has been specified without also specifying the RESTRICT= parameter. The RESTRICT= keyword may have been misspelled.
EDA056 THE USER'S ACCESS RIGHTS DO NOT ALLOW INCLUDE OR DELETE
The user's password does not have sufficient access rights to add or delete segment instances.
EDA057 'ROW-TOTAL' IS INCOMPATIBLE WITH 'OVER'
The two options were not compatible in early releases of FOCUS.
EDA058 DBA ERROR. SEGMENT NAME IS NOT RECOGNIZED IN 'NAME=':
The segment where a value restriction is to be applied is not recognized. Check the list of segment names.
EDA059 DBA ERROR. TOO MANY 'SAME' OPTIONS FOR USER
The use of the RESTRICT=SAME option in the DBA section of the Master File Description may be looping from one name to another. Only four consecutive references to the same user are allowed.
EDA060 INCLUDES/EXCLUDES TESTS NOT ALLOWED FOR UNIQUE SEGMENTS:
A UNIQUE segment can have only one instance. Therefore INCLUDES or EXCLUDES tests are not logical. Use an EQ or NE test instead.
EDA061 'WITH FIELDNAME' IN DEFINE LIES ON DIFFERENT PATH:
A DEFINE cannot specify that the computation is to be performed with a field name that does not lie on the same path as the fields referenced in the expression.
EDA062 A CONSTANT REQUIRES A REAL FIELD ON THE LEFT SIDE. USE 'WITH':
A constant is calculated but no real fields are specified. Use the form: 'fieldname WITH realfield = expression;'. The real field indicates the point at which the expression is evaluated during the retrieval.
EDA063 WARNING. MATCH FIELDS HAVE SAME NAME BUT DIFFERENT FORMATS:
The BY fields in two MATCH statements have different formats. Disjoint matching will occur because no matching values will be found.
EDA064 ERROR IN THE ASSOCIATION OF NEW FIELD WITH DATABASE FIELD
The field named after WITH and the expression are incompatible. The WITH option is generally used with constants.
EDA065 THE PRINT LINE EXCEEDS 4 PANELS. THE TOTAL LENGTH IS:
The maximum number of panels has been exceeded. Increase the panel length to reduce number of panels using the SET PANEL command.
EDA066 MAXIMUM NUMBER OF PLOT POINTS EXCEEDED FOR SCATTER DIAGRAM
There are too many points to plot on a scatter diagram. The limit is approximately 1000 points.
EDA067 THE MAXIMUM NUMBER OF SUBTOTAL VALUES EXCEEDED
The number of individual fields to subtotal, including heading and footing verb objects, multiplied by the number of totaling levels exceeds 1024.
EDA068 WARNING. DEFAULT TICS ARE BEING USED FOR:
EDA069 NUMBER OF POINTS ON HAXIS EXCEEDS THE CHARACTERS ON HAXIS:
The length of the horizontal axis is too small for the number of retrieval points.
EDA070 ACROSS IS INCOMPATIBLE WITH THE REQUEST
ACROSS is not compatible with some request options such as MATCH FILE or HOLD FORMAT FOCUS. Change the ACROSS to BY. ACROSS also requires a SUM/PRINT verb if there are any data references in the heading.
EDA071 INVALID WORD OR NO WORD BEFORE = SIGN IN LET COMMAND:
The left hand side is missing in a LET assignment statement.
EDA072 INVALID TERMINAL TYPE IN THE SET COMMAND
See the User's Manual for a complete list of valid values. The default is IBM3270.
EDA073 A 'LET' WORD IS UNDEFINED AND CANNOT BE CLEARED:
The LET CLEAR xxxx command names a word for which no LET has been issued.
EDA074 A 'LET' WORD IS DEFINED BY DBA AND CANNOT BE CLEARED:
The command LET CLEAR xxxx will not clear a word specified by DBA.
EDA075 INSUFFICIENT MEMORY IS AVAILABLE FOR LETS
More memory is needed for the LET statements. Increase memory or use the LET CLEAR command to release some space.
EDA076 A 'LET' WORD IS DEFINED BY THE DBA AND CANNOT BE REDEFINED:
A word assigned in a LET cannot be the same as one defined by the DBA.
EDA077 WARNING. RECURSION IN LET WILL CAUSE AN INFINITE LOOP:
The LET assignment has the same word on both the left-hand side and on the right-hand side. Use LET CLEAR to remove this LET.
EDA078 OVERFLOW DURING LET SUBSTITUTION. INPUT WORD AND LINE IGNORED:
The succession of LET substitutions results in a line too long to process. Use the # character to break up the line.
EDA079 WARNING. INVALID VARIABLE SUBSTITUTION IN LET STATEMENT:
There is an error in the use of the <> or <n> substitution in the statement. Use the LET ECHO facility to test the expression.
EDA080 WORD OR SYNTAX IN 'FOR' PHRASE (FML OPTION) NOT RECOGNIZED:
An option in the FOR phrase is invalid. Valid options include RECAP, DATA, etc.
EDA081 THE USER PROGRAM NEEDED TO READ THE DATA CANNOT BE FOUND:
The SUFFIX=program in the Master File Description cannot find the program specified to read the data. Check USERLIB on MVS, or GLOBAL TXTLIB on CMS.
EDA082 INCOMPLETE OR INCORRECT FOCUS FILE NAME IN 'USE' COMMAND:
The file name may be too long; it cannot exceed 8 characters. On CMS, the file type and file mode may be missing.
EDA083 THE 'ON' CONDITION FIELD IS NOT IN THE REQUEST STATEMENT:
The field name after the word ON is a valid field, but has not been mentioned in the request.
EDA084 THE SECOND VALUE OF RANGE CANNOT BE LESS THAN THE FIRST VALUE:
The form 'FROM value1 TO value2' is used, but the second value is smaller than the first value.
EDA085 WARNING. CROSS-REFERENCED DATA FILE IS NOT AVAILABLE:
A field which is on a cross-referenced segment is required for the request, but the cross-referenced file cannot be located. Default values will be provided for the missing cross-referenced fields. A USE command may be needed for the cross-referenced file.
EDA086 TOO MANY HORIZONTAL PLOT POINTS ON A HISTOGRAM
The histogram requires a larger horizontal axis in order to fit the individual bars. Try increasing the value of HAXIS or switching to a bar chart.
EDA087 THE HORIZONTAL AXIS IS TOO SMALL TO FIT GRAPH
The horizontal axis of the graph is too small to fit the number of plot points. Try increasing the value of HAXIS.
EDA088 THE VERTICAL AXIS IS TOO SMALL TO FIT GRAPH
The vertical axis of the graph is too small to provide a reasonable fit for the number of points needed. Try increasing the value of VAXIS.
EDA089 THE FOOTING OR HEADING OPTION NOT RECOGNIZED:
The word after HEADING or FOOTING is not a valid option, such as CENTER or BOTTOM.
EDA090 UNRECOGNIZED FML LABEL IN FREE TEXT:
The substituted value is not a recognized label on one of the prior lines of the FML request.
EDA091 THE FML LABEL IS ALREADY DEFINED:
A tag value may not reuse a label.
EDA092 THE FML LABEL HAS AN INVALID NAME:
The label contains invalid characters or exceeds 66 characters in length.
EDA093 MAXIMUM NUMBER OF LABELS EXCEEDED IN FML
The maximum number of labels depends on the amount of memory available. Try increasing memory.
EDA094 MAXIMUM NUMBER OF TAG VALUES EXCEEDED IN FML
The maximum number of tag values depends upon the amount of memory available. Try increasing memory.
EDA095 WARNING. PREVIOUS USE OF THIS OPTION IS OVERRIDDEN:
Certain control options, such as SKIP-LINE, can only appear once in a request. The second use is accepted but the first use is ignored.
EDA096 WARNING. NO TEXT SUPPLIED BELOW SUBHEAD OR SUBFOOT
Text is missing under a subheading or subfoot control statement. Supply text, or remove the control statement.
EDA097 DBA ERROR. USER NAMED AFTER 'RESTRICT=SAME' NOT FOUND
The user named by the NAME= parameter cannot be found in the Master File Description.
EDA098 LIMIT FOR TOTAL LENGTH OF ALL VERB OBJECTS EXCEEDED
In addition to the actual length of the fields, a control variable exists for every verb object; some exist for the whole report. Concatenating fields can lower the number of control variables thus allowing a large report to fit.
EDA099 SECURITY ERROR. CALL YOUR SYSTEM ADMINISTRATOR
EDA100 UNRECOVERABLE MODIFY PARSING ERROR
A subcommand other than CASE, or a global subcommand, may not follow an ENDCASE subcommand. Other causes should be reported to your FOCUS representative.
EDA101 ERROR IN DEFINE IN MASTER FILE:
While parsing the Master File Description an error in a DEFINE was detected. This may be due to an error in a computational statement, incorrectly placed delimiters, or an irresolvable reference.
EDA102 DEFINE IN MASTER NOT ENDED PROPERLY. ; OR $ MAY BE MISSING
The terminators for DEFINEs in the Master File Description are a semicolon and then a dollar sign, in that order. These delimiters must occur once for each defined field.
EDA103 DEFINE IN MASTER TOO LONG. ; OR $ MAY BE MISSING
A DEFINE of more than 8000 bytes was detected. It is possible that the cause was a missing terminator of semicolon or dollar sign. The maximum length of a Master File DEFINE is 8000 bytes.
EDA104 DEFINE IN MASTER REFERS TO A FIELD OUTSIDE ITS SCOPE:
The defined field refers to a field which is not in the same segment as the DEFINE (for FIELDNAME=OLD), or to a field that is not in this Master File (for FIELDNAME=NEW).
EDA105 INSUFFICIENT NUMBER OF BINS FOR DEFINES IN THE MASTER:
Set the number of bins higher (if necessary, increase memory) to open this Master File Description. DEFINEs in the Master File require increased bin size while reading the Master File.
EDA106 MAXIMUM NUMBER OF BY FIELDS WITH 'BY HIGHEST' EXCEEDED:
Sorting 'BY HIGHEST n' or 'BY LOWEST n' can be used with up to 5 BY fields.
EDA107 THE NUMBER OF RECAP FIELDS EXCEEDS 7
There is a limit of 7 RECAP fields allowed in the 'ON fieldname RECAP/COMPUTE' phrase.
EDA108 NUMBER OF ANALYSE VARIABLES EXCEEDS 64
The statistical analysis subsystem cannot handle more than 64 variables.
EDA109 INSUFFICIENT MEMORY FOR FACTOR ANALYSIS
The statistical operation requested requires more memory storage. Increase memory or reduce the number of variables.
EDA110 INVALID STATSET MODE:
The ANALYSE option STATSET does not have the parameter requested.
EDA111 SET VALUE MISSING IN ANALYSE
The value after the STATSET parameter is missing. A valid value must be provided.
EDA112 THE VALUE MUST BE NUMERIC:
The value in response to the ANALYSE prompt or STATSET parameter must be numeric.
EDA113 AN ILLEGAL RESPONSE HAS BEEN ENTERED:
The response to the ANALYSE prompt is not recognized. Type EXPLAIN in the ANALYSE mode if assistance is needed.
EDA114 AN INDEPENDENT VARIABLE IS ALSO A DEPENDENT VARIABLE:
A regression cannot use the same variable as both independent and dependent variables.
EDA115 THE NUMBER ENTERED EXCEEDS THE NUMBER OF VARIABLES:
The numeric identifier for a variable provided in response to the ANALYSE prompt exceeds the number of variables in the file being analyzed.
EDA116 BYPASSING TO NEXT STATISTICAL OPERATION OR TO QUIT
Sequential processing of ANALYSE commands cannot be continued because of parameter errors. The stacked commands are ignored until the next valid statistical operation is encountered.
EDA117 VALID RESPONSES ARE ON OR OFF
There are only two valid responses to this prompt: ON or OFF.
EDA118 THE DEPENDENT VARIABLE DOES NOT EXIST:
The dependent variable provided in response to the ANALYSE prompt is not specified in the Master File Description for the data. Only real data fields found in the file, not defined fields, may be used.
EDA119 THE INDEPENDENT VARIABLE DOES NOT EXIST:
The independent variable provided in response to the ANALYSE prompt is not specified in the Master File Description for the data. Only real data fields found in the file may be used, not defined fields.
EDA120 THE VALUE ENTERED IS INCONSISTENT WITH THE FILE DESCRIPTION:
The value supplied does not match the format in the file description. For example, the format is numeric but the value supplied is not. Or, the format is a date field, but the input value is not a recognized date.
EDA121 INVALID LEVEL ENCOUNTERED IN DATA FOR FACTOR:
Only numeric fields are allowed in factor analysis.
EDA122 THE NUMBER OF LEVELS IS NOT CONSISTENT FOR FACTOR:
The factor analysis subsystem has detected an input setup error.
EDA123 NUMBER OF FACTORS EXCEEDS 6:
The statistical process of factor analysis cannot exceed 6 factors.
EDA124 NON-NUMERIC DATA IN FILE
There is nonnumeric data for a variable which must be numeric.
This observation must be eliminated from the ANALYSE statistical process.
EDA125 RECAP CALCULATIONS MISSING
The word RECAP is not followed by a calculation. Either the RECAP should be removed, or a calculation should be provided.
EDA126 NUMBER OF DATA VALUES MUST EQUAL OR EXCEED FACTOR LEVELS
In ANALYSE, the factor analysis procedure FACTO requires at least the same number of fields as levels of factors.
EDA127 LITERAL TEST VALUE FOR GROUP IS INCORRECT:
A screening phrase against a group field has inconsistent values based on the contents of the fields in the group. The size of one or more sections is either incorrect or not numeric.
EDA128 WARNING. LIMIT USES 'EQ' OR 'LE' TEST CONDITION ONLY:
The RECORDLIMIT and READLIMIT phrases test with EQ or LE only. In either case, retrieval will stop when the specified number of records have been retrieved. If another type of test is used, it is transformed into an EQ type test.
EDA129 A REFERENCED DATA FILE IS NOT AVAILABLE:
A field which is mentioned in the request is in a cross-referenced file which is not available. Default values will be substituted for the cross-referenced data field.
EDA130 RANGE SPECIFICATION OUT OF ORDER:
The crosstab range specification is not in proper order.
EDA131 A NUMERIC VALUE OR 'BOT' IS REQUIRED:
EDA132 A NUMERIC VALUE OR 'TOP' IS REQUIRED:
EDA133 WARNING. ANALYSE FILE LOST, HAD SAME NAME AS HOLD FILE
The prior HOLD file is overwritten. Use new names with the EQFILE option.
EDA134 RE-READING DATA UNDER NEW SELECTION CRITERIA IS INHIBITED
EDA135 INSUFFICIENT MEMORY FOR SORTING DATA
EDA136 INSUFFICIENT MEMORY FOR COMPILING TABLE
EDA137 MISSING UPPER BOUND
EDA138 MAXIMUM NUMBER OF RANGES OR VALUES EXCEEDED
EDA139 WARNING. NO RANGES SPECIFIED FOR THIS VARIABLE
EDA140 'BY' OR 'AND' MISSING WHERE EXPECTED
EDA141 FIELDNAME MISSING WHERE EXPECTED
EDA142 THE TRUNCATED OPTION NAME IS NOT UNIQUE:
EDA143 NO DATA FOUND IN FILE:
EDA144 WARNING. TESTING IN INDEPENDENT SETS OF DATA:
The request contains a test on one path and retrieves data from another independent path. Records on the independent path will be retrieved regardless of whether the condition is satisfied on the tested path. Setting MULTIPATH=COMPOUND will alter this behavior.
EDA145 THE POSITION NUMBER AFTER THE WORD 'IN' IS INVALID:
The request option of IN is not followed by a valid number.
EDA146 THE REQUEST STATEMENT DOES NOT REFERENCE ANY DATA:
No data is requested in the statement.
EDA147 FML PICKUP DATA IS MISSING THE TERMINATOR OF '$':
The FML option of data PICKUP requires a terminator at the end of the data.
EDA148 ERROR IN USE OF 'IS MISSING'
The use of the IS MISSING option is incorrect.
EDA149 RESERVED FOR USE ON ANOTHER PLATFORM
EDA150 DYNAMIC ALLOCATION SYNTAX ERROR:
Attempt to dynamically allocate a file has failed.
EDA151 DYNAMIC ALLOCATION FAILED:
EDA152 DYNAMIC ALLOCATION ERROR
EDA153 VERB OBJECTS TIMES RETRIEVED COLUMNS EXCEEDS MAXIMUM:
The combination of ACROSS and the number of verb objects will produce more than the maximum number of output columns allowed in the report. Reduce the number of verb objects . See the documentation for further details.
EDA154 THE 'TO' FILE IN THE JOIN DOESN'T HAVE A SEGMENT DEFINITION:
The Master File Description of the second file (the TO file) does not contain the matching field provided in the JOIN. Possibly the TO field is on a segment whose attributes are not provided in the Master File Description.
EDA155 DBA ERROR. THE PROGRAM REQUESTED CANNOT BE FOUND
The RESTRICT attribute specifies PROGRAM, but the program used with the NAME attribute cannot be found. Or, VALUE=returncode may be incorrect.
EDA156 DBA ERROR. MORE THAN ONE DBA IS NAMED IN THE MASTER FILE
Only one DBA password can be specified in the Master File Description.
EDA157 DATA FOR THIS VARIABLE IS OUTSIDE THE CURRENT SUBSET:
A SUBSET command is in effect whose first data point is at a time-index beyond the last data point of the variable named.
EDA158 NO HELP INFORMATION AVAILABLE ON:
There is no additional information available on the subject requested in the HELP query.
EDA159 3279 GRAPHICS CANNOT BE PRODUCED. THE GDDM CODE IS MISSING
The IBM program product GDDM has not been link-edited into the FOCUS module. See your installation coordinator.
EDA160 THE OPTION AFTER THE WORD 'FORMAT' IS INVALID:
For a complete list of formats, see the User's Manual. Some of the supported format options include: ALPHA, BINARY, CALC, DB2, DIF, FOCUS, GRAPH, IFPS, LOTUS, SQL, SQLDBC, SYLK, TERADATA, WP.
EDA161 IFPS. TAG LENGTH EXCEEDS 8 CHARACTERS:
The field values used to create tag fields must result in a length of 8 or fewer characters. Use the FOCUS EDIT function to reduce the size if possible.
EDA162 IFPS. THE LENGTH OF THE NAME EXCEEDS 247 CHARACTERS:
The length of the name of the variable on the left hand side must be less than 247 characters (IFPS limit).
EDA163 IFPS. DUPLICATE LINES MAY RESULT WITH THIS REQUEST:
The verb PRINT may retrieve two or more lines with the same left hand side variable name. This is a problem for IFPS because the model will only use one of the duplicate names.
EDA164 IFPS. THE TAG FIELD FOR IFPS FILES MUST BE AN ALPHA DATA FIELD:
EDA165 THE FORMAT SPECIFIED CANNOT BE USED WITH THE TABLEF COMMAND
The TABLEF command cannot generate a HOLD file for certain formats. You must use the TABLE command for the following HOLD formats: CALC, DIF, GRAPH, IFPS, LOTUS, SYLK.
EDA166 WRONG FILEDEF, ALLOCATE, OR DYNAM FOR A SPECIAL FORMAT SAVE FILE
All of the DCB parameters (LRECL, BLKSIZE, and RECFM) should be specified, or you should omit the DCB specification. If specified, the DCB parameters must be compatible with the format requested.
EDA167 IMS/DC USER IS NOT AUTHORIZED FOR 'DYNAM' COMMAND
The User Profile Table does not specify DYNAM as a valid command for this user ID. Ask your coordinator about the NONIMSIO parameter.
EDA168 THE 'WITHIN' FIELD IS NOT ALSO A 'BY' OR 'ACROSS' FIELD:
The field name after the WITHIN option must also be mentioned in the request statement as either a BY field or as an ACROSS field. For example, SUM PCT UNITS WITHIN MONTH BY PRODUCT BY MONTH
EDA169 THE FIELD ATTRIBUTE 'MISSING' IS NOT EITHER ON OR OFF:
The value of the Master File Description attribute called MISSING or NA (for not available) must be either ON or OFF.
EDA170 FIELD WITH 'MISSING ON' REDEFINES FIELD WITH 'MISSING OFF':
In a MODIFY procedure, the COMPUTE subcommand creates a computed field with the SOME/ALL DATA PRESENT specification, but this field redefines a real FOCUS database field which does not have the MISSING=ON attribute.
EDA171 TYPE OF MISSING CALCULATION IS NOT SPECIFIED ON LEFT SIDE:
A computed field created through the DEFINE command, the COMPUTE subcommand of the MODIFY command, is assigned the value MISSING, but its definition does not specify NEEDS SOME DATA or NEEDS ALL DATA.
EDA172 THE FILE SPECIFIED AS THE 'FROM' FILE IN XFER CANNOT BE FOUND:
EDA173 WARNING. REPORT MAY NOT REFLECT DATA STRUCTURE. SEE FIELD:
The verb objects of this request lie along several hierarchical paths, and one or more verb objects are in more than one path. Convert the offending verb object into a BY field. This diagnostic can only occur with PRINT or LIST verbs.
EDA174 INVALID USE OF FOCEXEC WITH -CRTFORM:
Under IMS/DC, FOCEXECS with -CRTFORM should be invoked using the PROMPT command. The PROMPT command may not be used within a FOCEXEC. "g"
EDA175 -TYPE AND -PROMPT NOT SUPPORTED IN THIS ENVIRONMENT:
The -TYPE and -PROMPT commands are not supported within the IMS/DC environment.
EDA176 WARNING. CRTFORM * SEGMENT MENTIONED HAS NO KEYS
The statement 'CRTFORM * SEG n KEYS' or 'MATCH * SEG n KEYS' is used for a segment that has no keys. Check the Master File Description against the FOCEXEC.
EDA177 INVALID DATE CONSTANT:
The constant in the calculation is not a valid date. Enter a valid date.
EDA178 THE ADDITION OF TWO OR MORE DATE FIELDS IS INVALID
Only the addition of constants which will be assigned to a date field is allowed.
EDA179 REENTRANCY ERROR. ROUTINE OUT OF SYNCH:
The reentrant and non-reentrant object decks of the subroutine have different compilation dates. This is an internal error that should be reported to your FOCUS representative.
EDA180 HOLDINDEX IS OUT OF RANGE DURING HOLD OR GETHOLD:
The variable HOLDINDEX is greater than HOLDCOUNT or is less than or equal to 0. Remember that HOLD resets HOLDCOUNT to the value of HOLDINDEX, and then increases HOLDINDEX.
EDA181 REPETITION FACTOR IS INVALID:
The value following the REPEAT statement must be between 0 and 32767, or an asterisk (*).
EDA182 NO MORE MEMORY IS AVAILABLE FOR HOLDING RECORDS
No room is left to create more record instances. Increase your run-time storage or set BINS lower.
EDA183 MAXIMUM NUMBER OF FIELD NAMES EXCEEDED IN HOLD LIST:
Only 64 fields may be held in all of the HOLD lists.
EDA184 NO MORE HOLD LISTS ARE AVAILABLE
A maximum of eight hold pockets may be used.
EDA185 REPEAT LOOP PARSING ERROR:
Either there is no room for repeat cases to be stored, or an ENDREPEAT was encountered without a corresponding REPEAT, or there is no body of code to repeat. Repeat loops cannot be nested.
EDA186 THE INDEX TO HOLD LIST IS INVALID IN CRTFORM:
Either the index value is greater than 32767 or less than 0, or there is no hold instance corresponding to that index.
EDA187 PERFORMS NESTED TOO DEEPLY
PERFORM cases are nested too deeply for the available memory. You may have recursively invoked a PERFORM statement. Try increasing available storage.
EDA188 'CASE AT START' OR 'CASE AT END' CANNOT BE THE FIRST CASE
CASE AT START and CASE AT END cannot be created without an existing TOP case.
EDA189 INTERNAL INCOMPATIBILITY IN PRE-LOADED MODIFY:
Fatal error in pre-loaded MODIFY. Contact your FOCUS representative.
EDA190 THE FILE HAS NOT BEEN LOADED
The UNLOAD command has been issued for a file which has not been loaded previously.
EDA191 AN INCORRECT TYPE OF FILE HAS BEEN SPECIFIED
An incorrect type of file has been specified in the LOAD command. The file should be MASTER, FOCEXEC, FOCCOMP, or MODIFY, or it can be omitted.
EDA192 TRANSACTION LOGGING AREA OVERFLOW. MODIFY TERMINATING
PROMPT and FREEFORM make a list of all transaction values in order to allow them to be logged. FOCUS saves the transactions until it re-executes the first PROMPT in the procedure. In this case, the area where the saving is done has overflowed.
EDA193 DBA ERROR. LOAD PASSWORD IS DIFFERENT FROM RUN TIME PASSWORD
Current password differs from the one that was active when the LOAD command was issued. Reload the file or restore the original password.
EDA194 UMF ERROR. 'AS' IS REQUIRED FOR FIND ON EXTERNAL FILES:
FIND on external files requires the full form of the FIND command, including the AS keyword, to identify the name of the field in the target file.
EDA195 UMF ERROR. DBFIELD IS WRONG OR NOT DIFFERENT FROM FIELDNAME:
FIND on external files requires the full form of the FIND command. The FIELDNAME and DBFIELD must be different for external files.
EDA196 UMF ERROR. DBFIELD IN FIND IS INVALID:
The DBFIELD specified in the FIND command does not exist in the target file.
EDA197 USE LOCAL IS ALLOWED ONLY FOR FILES WITH FILEMODE NUMBER 6
The LOCAL option of the USE command can only be specified on CMS for files with a file mode number of 6 (for example, a file mode of A6). This designates the file to CMS as an "update-in-place" file. You can use the CMS RENAME command to change the file mode number.
EDA198 FATAL ERROR IN DATABASE I/O. FOCUS TERMINATING %1
A severe error was encountered in reading from or writing to a FOCUS database. FOCUS was unable to recover from this error, and will return to the host environment.
EDA199 'WITH' AND 'AND' COMBINATION IS INVALID IN JOIN:
The JOIN based on a DEFINE field cannot use the AND phrase in the definition of the FROM field. If field concatenation is desired, the concatenation operator should be used in the FROM field computational expression itself.
EDA200 INTERRUPT. DATA EXCEPTION
This error is generally caused by either bad data or an incorrect ACTUAL field format in the Master File Description of an external file (often a packed field). More than ten of these errors in one request may result in an exit from FOCUS.
EDA201 INTERRUPT. DIVISION BY ZERO
An attempt to perform an arithmetic operation with non-arithmetic data has occurred. Error cause is indeterminate and possibly due to input of binary data which bypasses the normal character checking operation.
EDA202 INTERRUPT. FLOATING VALUE OVERFLOW
An attempt to perform an arithmetic operation with non-arithmetic data has occurred. Error cause is indeterminate and possibly due to input of binary data which bypasses the normal character checking operation.
EDA203 INTERRUPT. FLOATING VALUE UNDERFLOW
An attempt to perform an arithmetic operation with non-arithmetic data has occurred. Error cause is indeterminate and possibly due to input of binary data which bypasses the normal character checking operation.
EDA204 TOO MANY INTERRUPTS. RUN TERMINATED
Errors FOC201, FOC202 and/or FOC203 have occurred more than ten times and the run is terminated.
EDA205 THE DESCRIPTION CANNOT BE FOUND FOR FILE NAMED:
No data description can be found for the file requested. Check the Master File Descriptions allocated or available, or the spelling of the file name. If you are in Screen Painter, type IGNore to continue, or any other input to return to TED.
EDA206 INSUFFICIENT MEMORY IS AVAILABLE FOR PROGRAM/CACHE
The amount of main storage is insufficient for loading the program, or a request for a user written program has been issued during execution and there is insufficient space for it, or there is not enough storage for cache creation. Define larger storage and retry the procedure.
EDA207 ERROR IN THE FORMAT DEFINITION OF FIELD:
The format of a data field in the Master File Description is not a recognized type or length, or has invalid edit options.
EDA208 REENTRANCY ERROR. MODULE DOES NOT CONTAIN CSECT:
The reentrant object of the program has not been explicitly included into a module when it was created. Contact your FOCUS representative.
EDA209 THE DATA VALUE EXCEEDS ITS LENGTH SPECIFICATION:
In comma delimited data, the number of characters supplied for the field exceeds the number allowed by the FORMAT.
EDA210 THE DATA VALUE HAS A FORMAT ERROR:
An alphabetic character has been found where all numerical digits are required.
EDA211 THE PARENT SEGMENT NAME IS NOT FOUND IN THE MASTER:
The name used for a PARENT has not been encountered in the Master File Description. Check for a spelling error.
EDA212 THE FILE DESCRIPTION CONTAINS AN ERROR:
An error has been encountered in the Master File Description, making it unusable. Another diagnostic message is usually printed with this one.
EDA213 THE RECORD CONTAINS A FIELDNAME WHICH IS NOT RECOGNIZED:
In comma delimited data, the field name is not recognized. Check the spelling or look for special characters.
EDA214 MORE THAN 64 SEGMENTS OR 189 SEGMENTS+INDEXES DESCRIBED:
A Structure can only contain a total of 64 segments or a total sum of 189 segments, indexes, and text fields in any combination.
EDA215 THE FIRST SEGMENT IS SPECIFIED WITH A NON-BLANK PARENT:
The first segment in the Master File Description is the "root"; it cannot have a parent. Specify 'PARENT=' for the root segment, or omit the 'PARENT=' parameter.
EDA216 THE TERMINATOR OF '$' MISSING FROM THE END OF THE RECORD
A record submitted in free format is missing a final terminator.
EDA217 THE SEGMENT NAME IS A DUPLICATE AND NOT THE SAME AS PREVIOUS:
A segment with the same name has been encountered in the Master File Description. Segment names must be unique within a file.
EDA218 THE STRUCTURE HAS TOO MANY LEVELS:
The maximum number of levels in a structure is 64.
EDA219 ERROR WRITING PAGE N OF FILE:
A disk writing error has occurred while attempting to write page 'n' of the named file. Backup the data file, erase it, reload it onto the disk and retry the procedure. Also check to see that the disk is attached with 'WRITE' privileges.
EDA220 ERROR READING PAGE N OF FILE:
A disk reading error has occurred while attempting to read page 'n' of the named file. Check the number of blocks associated with the physical file. The cause of the error is the last number, which can be looked up in the CMS or MVS error message book.
EDA221 A HOLD FILE DOES NOT CURRENTLY EXIST
A query about the fields in the HOLD file indicates that no HOLD file is currently active.
EDA222 THE WORD 'FILE' IS MISSING
There is a syntax error. The word FILE is required.
EDA223 NON-NUMERIC CHARACTER HAS BEEN FOUND IN A COMPUTATIONAL FIELD:
A numeric field was given a nonnumeric character.
EDA224 SYNTAX ERROR:
There is a syntax error serious enough to halt interpretation.
EDA225 THE ALPHANUMERIC FIELD HAS TOO MANY CHARACTERS:
The attribute for the FORMAT of the field is too small to accommodate the number of characters submitted.
EDA226 FILEDEF OR ALLOC MISSING FOR EXTERNAL FILE:
It is necessary to provide a FILEDEF on CMS or DDcard/ALLOC on MVS/TSO so that the data may be located.
EDA227 THE FOCEXEC PROCEDURE CANNOT BE FOUND: %1
The stored procedure named cannot be located or is not valid for execution.
EDA228 FORMAT ERROR:
The data values do not match the FORMAT attribute (for example, characters in a numeric field).
EDA229 ERROR READING EXTERNAL DATA FILE:
An error occurred while reading the external data file. Check the FILEDEF (on CMS) and ALLOC (on TSO), including any DCB supplied or other elements related to the definition of the external file.
EDA230 MISSING ENDING QUOTE MARK:
A beginning quotation mark is not paired with a closing quotation mark.
EDA231 SEGTYPE ATTRIBUTE IS NOT VALID:
The attribute for SEGTYPE has an invalid value. Check the MASTER file description. Valid attributes include S, Sn, SHn, U, KU, DKU, KM, DKM, KL.
EDA232 ERROR ENCOUNTERED ALLOCATING HOLD FILE:
Possibly an attempt to create a FOCUS file, which is already allocated to a file that does not have an LRECL and a block size of 4096 bytes.
EDA233 TOO MANY FIELDS ARE INDEXED. THE LAST ONE IS:
The number of indexed fields plus the number of segments exceeds 189. Check the attribute FIELDTYPE= on each field to verify that only the required indices are present (have FIELDTYPE=I).
EDA234 FIELDNAME USED AS A KEY IS NOT FOUND IN THE PATH TO THE SEGMENT:
The field named as the cross-reference key has not been encountered in the file description before the point where it is used as a cross-reference, hence the field name is undefined at this point.
EDA235 DESCRIPTION ERROR. SEGMENT WITH REAL DATA NOT FOUND FOR:
The segment to be retrieved via a cross-reference is not in the cross-reference file, or in the set of files in the dictionary. Check the spelling.
EDA236 LINKED FILE DOES NOT HAVE A MATCHING KEY FIELD OR SEGMENT:
The referencing and cross-referenced file do not have the field named as the CRKEY in common. The CRKEY must be the field name or alias of the referencing field and the field name of the cross- referenced field.
EDA237 LINKED AND REAL FIELD HAVE DIFFERENT FORMATS:
The common CRKEY has a different FORMAT in the cross-referenced file and the referencing file.
EDA238 LINKED FIELD IS NOT INDEXED:
The cross-referenced field in the cross-referenced file does not have FIELDTYPE=I. Or, if the segment has been re-described in the referencing file, the FIELDTYPE=I attribute is missing.
EDA239 FORMAT DEFINITION IN ERROR. INTERNAL FIELD:
The format attribute is invalid. Check the attributes for the field.
EDA240 INDEX FIELD OR SEGMENT IS NOT FOUND IN THE CROSS-REF FILE:
The cross-referenced file does not contain the named segment or index.
EDA241 NO NAME PROVIDED FOR CROSS-REFERENCE FILE:
The name of the cross-referenced file is missing. Provide the name of the file in which the segment is described with the CRFILE parameter in the Master File Description.
EDA242 CANNOT FIND THE CROSS REFERENCE FILE NAMED:
The Master File Description for a named cross-referenced file cannot be located. Check the spelling.
EDA243 TOO MANY DEFINED FIELDS
EDA244 EXPRESSION CANNOT BE INTERPRETED. BREAK UP INTO SECTIONS:
The size of the computational expression is too large to be handled in a single expression. Divide it into separate expressions.
EDA245 COMPUTATIONAL BRANCHING ALONG MORE THAN ONE DATA PATH
A conditional or unconditional branching statement was defined, and the entire set of temporary defined fields for the file does not follow along a single top-to-bottom data path.
EDA246 COMPUTATIONAL STATEMENT REFERS TO MORE THAN ONE DATA PATH
All data fields referenced by a computational expression must occur in a single top-to-bottom data path.
EDA247 STORED BRANCHING STATEMENTS ARE NOT ALLOWED
EDA248 INCORRECT EVALUATION SEGMENT FOR STORED DEFINED FIELD
EDA249 UNDEFINED LABEL:
EDA250 DUPLICATE LABEL:
EDA251 COMPUTATION STATEMENT NOT RECOGNIZED. RETYPE ENTIRE LINE
EDA252 COMPUTATIONAL EXPRESSION NOT RECOGNIZED:
A label must be 12 characters or less, and must not include blanks or special characters.
EDA253 INVALID FORMAT SPECIFICATION ON LEFT HAND SIDE:
The format after the new field name is invalid. Check the spelling, and check for the special characters period (.) and slash (/) in the field name.
EDA254 TEMPORARY FIELD REDEFINED WITH A CHANGED FORMAT:
The same field name is used with 2 temporarily defined expressions, with different formats on the left-hand side. The second instance should either omit the format specification or repeat it exactly as before. (A temporarily defined field may redefine an actual field.)
EDA255 COMPUTATIONAL ELEMENT IS TOO LONG:
The expression contains a number represented by more than 33 characters or more than 31 digits. This exceeds the maximum size of a computational number.
EDA256 STRING OF DIGITS TOO LONG:
The expression contains a number represented by more than 33 characters or more than 31 digits. This exceeds the maximum size of a computational number.
EDA257 MISSING QUOTE MARKS:
An open quote mark is not followed by a close quote mark within 256 characters (including blanks).
EDA258 FIELDNAME OR COMPUTATIONAL ELEMENT NOT RECOGNIZED:
An element in a computational expression is not recognized. It may be a mistyped field name or function.
EDA259 FIELDNAME EXCEEDS ITS MAXIMUM SIZE:
The maximum size of a field name or alias is 66 characters. Reduce the size of the name.
EDA260 AN OPERATION IS MISSING AN ARGUMENT
An arithmetic or logical operation is missing an argument. Possibly two operations have been written in succession without a semicolon (;) separating them.
EDA261 EXPRESSION IS INCOMPLETE BECAUSE AN OPERATION IS MISSING
An arithmetic or logical operation is missing. Possibly two operations have been written in succession without a semicolon (;) separating them.
EDA262 UNBALANCED PARENTHESES
The right and left parentheses in the expression are not balanced. Check that the number of opening parentheses is the same as the number of closing parentheses.
EDA263 EXTERNAL FUNCTION OR LOAD MODULE NOT FOUND:
An external function referred to in the expression could not be located within the accessible virtual disks, possibly a misspelled FOCUS function or a failure to issue a 'GLOBAL TXTLIB' for the library containing the SORT program for the REBUILD INDEX function.
EDA264 FUNCTION HAS AN INCORRECT NUMBER OF ARGUMENTS:
A FOCUS function was specified with too many or too few arguments.
EDA265 AN OPERATION OR A RELATION IS NOT RECOGNIZED:
An unidentified type of error is present in the statement, possibly a spelling or typing error.
EDA266 IF .. THEN .. ELSE .. SYNTAX ERROR
Missing or extra IF, THEN, or ELSE clauses, or possibly a missing semicolon (;).
EDA267 THE LAST ARGUMENT IN AN EXTERNAL FUNCTION IS INVALID
The last argument passed to a user function must be the name of the variable to receive the result, or must be a valid format. For example, NAME/I4=MYFUN(P1,P2,NAME); or NAME/I4=MYFUN(P1,P2,'I4');
EDA268 THE FIELD NAME IS NOT REFERENCED IN THE REQUEST STATEMENT:
A field in a COMPUTE calculation is not also mentioned as a verb object in the request statement.
EDA269 EQUALITY SCREENING TESTS MUST BE PROVIDED IN AN INDEXED VIEW
When an indexed view is used, for example, filename.fieldname, then one or more equality screening tests for the indexed field must be provided.
EDA270 SYNTAX ERROR IN DECODE ELSE CLAUSE
The ELSE clause in the decode is incorrect; it is not followed by a single decode element and a left parenthesis.
EDA271 ODD NUMBER OF DECODE LIST ELEMENTS
The decode list (including the ELSE clause) must have paired code/decode elements. Check the number of elements. For example, DECODE field (A 1 B 1 C 1 ELSE 0), not DECODE field (A 1 B 1 C ELSE 0).
EDA272 FORMAT ERROR IN DECODE OR FILE ELEMENT:
A code element does not conform to the format of the DECODE field; a decode element does not conform to the format of the field on the left-hand side of the expression; or a file element is improperly quoted in a DECODE or IN FILE expression.
EDA273 SYNTAX ERROR IN DECODE
Missing parentheses around the decode list or the list elements are not separated by blanks or commas.
EDA274 FROM/TO UNAVAILABLE IN COMPUTATIONS. USE LE AND GE
The DEFINE or COMPUTE syntax uses 'GE' for greater than or equal rather than 'FROM', and 'LE' for less than or equal rather than 'TO'.
EDA275 FOCUS FUNCTION HAS INCORRECT NUMBER OF ARGUMENTS:
The DEFINE or COMPUTE expression is using a built-in function and the number of argument parameters is not the correct number needed for the particular function.
EDA276 THE FIRST ARGUMENT OF 'EDIT' MUST BE A FIELDNAME
The EDIT function must identify the field to be edited as its first argument. It cannot be a numeric value. (Use quotation marks if necessary).
EDA277 GROUP FIELDS AND CHARACTER MASKS MUST BE ALPHANUMERIC
Group fields must be in the Master File Description as type alpha. The argument to EDIT or LIKE must be a quoted alphanumeric mask. Including '/' as the second argument of a relational comparison to a group field transforms it into a mask, and the same rules apply.
EDA278 THE LAST ARGUMENT IN AN EXTERNAL FUNCTION IS INVALID
The last argument passed to a user function must be the name of the variable to receive the result, or must be a valid format. For example, NAME/I4=MYFUN(P1,P2,NAME); or NAME/I4=MYFUN(P1,P2,'I4');
EDA279 NUMERIC ARGUMENTS IN PLACE WHERE ALPHA ARE CALLED FOR
The syntax requires an alphanumeric value where a numeric value was supplied. Quotation marks may be missing from the literal.
EDA280 COMPARISON BETWEEN COMPUTATIONAL AND ALPHA VALUES IS NOT ALLOWED
There is a mismatch in data types: one is a number and the other is an alphanumeric value. Quotation marks may be missing around a literal or a nonnumeric character may have been entered by mistake.
EDA281 ALPHA ARGUMENTS IN PLACE WHERE NUMERIC ARE CALLED FOR
An alphanumeric field is being used in a computation or being compared to a computational number.
EDA282 RESULT OF EXPRESSION IS NOT COMPATIBLE WITH THE FORMAT OF FIELD:
The left-hand side of the expression has a different format from that yielded by the right-hand side of the expression. Alpha fields may have the wrong length or a format may be needed after the field name.
EDA283 IMPROPER USE OF 'GOTO'
The 'GOTO' is incorrect in the context of the expression.
EDA284 PARENTHESIZE 'AND' AND 'OR' FOR CLEARER MEANING:
The expression is ambiguous because of the placing of the 'AND' and 'OR' connectors. Add parentheses to make the meaning clearer.
EDA285 SUBSTITUTED LINE IN FOCEXEC TRUNCATED:
A line in the Dialogue Manager procedure has been truncated because after substitution the line exceeds the limit of 80 characters.
EDA286 THE VARIABLE NAME EXCEEDS 12 CHARACTERS IN FOCEXEC:
A substitutional variable name must be 12 or characters or less.
EDA287 THE NUMBER OF FOCEXEC VARIABLES EXCEEDS THE MAXIMUM:
The maximum number of amper variables in a FOCEXEC procedure has been exceeded. The default limit is 512 variables (of which 25 or so are reserved by FOCUS). Break up the procedure or try to reuse variables.
EDA288 TOTAL LENGTH OF FOCEXEC VARIABLES EXCEEDS MAXIMUM:
The total length of all amper variable values in a FOCEXEC procedure exceeds the limit. The default limit is 32,768 bytes. Break up the procedure or try to reuse variables.
EDA289 MISSING OR MISPLACED QUOTE IN REPLY, RETYPE COMPLETE REPLY
The reply to a prompt has a misplaced quote, so its length cannot be determined. Retype the line.
EDA290 EQUAL SIGN MUST BE QUOTED IN A PROMPT REPLY, RETYPE COMPLETE REPLY
A special character such as an equal sign must be enclosed in single quotes if it is part of the text, for example, 'AB=BA'.
EDA291 THE VALUE IN THE PROMPT REPLY EXCEEDS THE MAXIMUM LENGTH:
The reply to the prompt for the particular value has too many characters. The maximum length is shown for the message.
EDA292 THE VALUE IN PROMPT REPLY IS NON-NUMERIC:
The prompt reply expects a numeric response for the value being requested.
EDA293 MISSING OR MISPLACED QUOTE IN THE FOCEXEC ARGUMENT LINE:
The values in the FOCEXEC line cannot be correctly interpreted because a quote is missing and one is therefore unbalanced.
EDA294 SYNTAX ERROR IN THE FOCEXEC ARGUMENT LINE:
The variables supplied in the FOCEXEC line cannot be properly identified. The use of the form 'name=value' may be needed.
EDA295 A VALUE IS MISSING FOR:
A value for the Dialogue Manager variable named has not been supplied. It is needed in order to properly expand a line.
EDA296 THE INTERPRETED FOCEXEC EXCEEDS MAXIMUM NUMBER OF LINES
When a '-RUN' control is used in the Dialogue Manager, the variables in the current procedure are saved and any other FOCEXEC procedures called for are then executed. The combined length of the saved and new procedure exceeds the space available to store it.
EDA297 THE NUMBER OF FILES EXCEEDS MAXIMUM:
The number of files provided in the FOCUS 'USE' command exceeds the current maximum allowed (usually 253). If the file has dynamically loaded sections (LOCATION or CRFILE), these must also be counted. However, files mentioned in a USE...LOCAL statement are not counted.
EDA298 TED CANNOT EXECUTE PROPERLY
One possibility to check is that FOCEXEC was not allocated, and TED was invoked without file specification. In such a case there is no 'last executed procedure' to edit.
EDA299 UNRECOGNIZED FORMAT OF AMPER VARIABLE IN -READ:
The Dialogue Manager subcommand -READ is asked to read a variable whose format (or length) is unknown.
EDA300 MISPLACED QUOTE IN DATA REPLY. DISREGARDED:
The reply to a Dialogue Manager prompt contains an open quote, but no close quote.
EDA301 DATA CONTAINING EQUAL SIGNS OR COMMAS MUST BE QUOTED:
Prompted values can be supplied in advance of actual prompting by identifying then with a 'name=value' syntax. Hence, if a single response has an equal sign or comma as part of its value, enclose it in quotes so it won't be confused with advance data.
EDA302 ERROR WRITING FOCEXEC TEMPORARY FILE
An I/O error occurred while attempting to write the FOCSTACK temporary work file. Erase all copies of such a file and try again.
EDA303 CONTROL LINE NOT RECOGNIZED IN FOCEXEC:
The subcommand in the Dialogue Manager starts with a dash and appears to be a control line, but is not correct. Check the list of valid commands.
EDA304 LABEL INCORRECTLY SPECIFIED:
A GOTO statement does not refer to a valid label name. The label may contain a special character, or the hyphen has been used incorrectly. For instance, -GOTO MYLAB .... -MYLAB is correct, but -GOTO -MYLAB .... -MYLAB is wrong because it contains an extra hyphen.
EDA305 SPECIFIED LABEL NOT FOUND:
A GOTO statement cannot find the label to branch to. The label may contain a special character, or the hyphen has been used incorrectly. For instance, -GOTO -MYLAB has been used rather than -GOTO MYLAB. Another cause is a nonzero return code from a HOLD VIA user program.
EDA306 DESCRIPTION ERROR. MASTER FILE ATTRIBUTE NOT RECOGNIZED:
The attribute used in a Master File Description is not recognized.
EDA307 TOO MANY DATA FIELDS IN THE LINE:
A FREEFORM limited transaction has too many comma separators, hence refers to too many data values. The transaction is rejected as an error.
EDA308 THE ASSIGNED FIELD IS NOT MENTIONED IN THE TRANSACTION:
A field on a FREEFORM limited transaction is not on the list specified in the FREEFORM statement. The transaction is rejected as an error.
EDA309 THE TRANSACTION IS INCOMPLETE:
A terminator has been encountered on a transaction before all of the fields on the FREEFORM list have been processed. The transaction is rejected as an error.
EDA310 PART OF REJECTED TRANSACTION:
A prior transaction has been rejected, and until a terminator has been encountered, other lines are considered part of the rejected one.
EDA311 ERROR FROM PRIOR TRANSACTION STILL ACTIVE. CANNOT PICKUP YET:
A previous transaction had an error in the referenced data field for which a new value has not yet been substituted.
EDA312 NO FIELD IS SPECIFIED ON THE LEFT HAND SIDE OF THE ASSIGNMENT:
There is a syntax error because an equal sign has been encountered with no variable name before it.
EDA313 THE -PROMPT STATEMENT DOES NOT SPECIFY AN &VARIABLE:
A -PROMPT subcommand line does not contain a variable name beginning with an '&' for which a value is to be supplied.
EDA314 SYNTAX ERROR IN DYNAM COMMAND
EDA315 INVALID VALUE ASSIGNED TO SYSTEM VARIABLE:
The system variable named is not assigned a valid value.
EDA316 THE -IF CONTROL STATEMENT BRANCHES TO AN INVALID LABEL:
The branching statement does not name a valid label as the point to branch to. Possibly the label exceeds 12 characters, or contains an unacceptable special character.
EDA317 MAXIMUM NUMBER OF POSITIONAL VARIABLES EXCEEDED:
The maximum number of numeric positional variables in the Dialogue Manager has been attained.
EDA318 A FIELD FORMAT IS NOT ALLOWED IN -SET:
In a -SET control statement, the variable on the left-hand side of the equal sign cannot be assigned a format. The format in the Dialogue Manager is implied from the data which is provided. 10110(FOC319) WARNING. THE FIELD IS INDEXED AFTER THE FILE WAS CREATED: A field has been given the attribute FIELDTYPE=I after data was entered. Use the INDEX option of the REBUILD command to actually construct an index for the field and remove the warning message.
EDA320 INVALID DIALOGUE MANAGER QUERY:
The option after the -? is not recognized. 11110(FOC321) WARNING. SEGMENT POSITION HAS BEEN CHANGED AFTER FILE CREATION: The Master File Description of the file has been changed after data was entered. The REORG option of REBUILD may be needed to actually construct the data as the file description specifies.
EDA322 FILE DESCRIPTION CHANGED AFTER DATA ENTERED (FILE/SEGMENT
The Master File Description has been changed after data was entered into the file and no longer describes the data. Data fields may have been added or deleted from the segment named. Restore the original MASTER file and REBUILD/REORG the file. 12010(FOC323) WARNING. THE SEGMENT NAME HAS BEEN CHANGED AFTER FILE CREATION: The name of a segment was changed after data was entered into the file.
EDA324 THE PARAMETER TO BE SET IS NOT RECOGNIZED:
In the SET command, the left-hand side of an assignment is not one of the valid parameters that can be used.
EDA325 ERROR WRITING FILE NAMED:
An error was encountered while writing the file. If an error code appears after the ddname, it may be interpreted as follows: 31--error in GETMAIN; 32--I/O error; 72--error in OPEN.
EDA326 MORE MEMORY IS NEEDED TO FORMAT THE REPORT OR SAVE FILE:
Additional memory is needed in order to complete the processing. If possible, the report will be printed line by line instead of in full screen mode. Set memory larger and repeat.
EDA327 DATA EXCEPTION. PACKED DECIMAL VALUE IMPROPER. INTERRUPT
A packed decimal value has an incorrect format and is not a valid packed decimal number.
FOC328 THE FIELD NAMED IN A MODIFY FILE 'VIEW' IS NOT INDEXED:
The form filename.fieldname is used in a MODIFY but the field name does not have the attribute of FIELDTYPE=I.
EDA329 EXPECTED CONTINUATION OF TSO COMMAND NOT FOUND
The TSO command expects further information.
EDA330 SYNTAX ERROR IN ? TSO COMMAND
Check the syntax of ? TSO or ? TSO ddname.
EDA331 ERROR IN TSO COMMAND
There is a nonzero code from the TSO command issued from within FOCUS. A parameter may be missing, or the command or a data set cannot be found. 'nnnn' is the decimal value returncode.
EDA332 RESERVED FOR USE ON ANOTHER PLATFORM
EDA333 INVALID DATASET NAME: %1
Either an installation-dependent program is checking data set names for conformance with standards, in which case you should inquire with the FOCUS coordinator, or a ddname was used when a data set name is required (non-full-screen TED). 01110(FOC334) WARNING. FIELDNAMES MISSING FROM UPDATE SUBCOMMAND: In a MODIFY statement the ON MATCH UPDATE line has no list of field names to be updated.
EDA335 SEGNAME IN FILE DESCRIPTION NOT FOUND IN DATA:
The cross-reference segment cannot be located in the cross-reference file. Check the CRSEGNAME spelling.
EDA336 THE SUM OF ALL FIELD LENGTHS EXCEEDS MAXIMUM.
The sum of the lengths of all fields in a structure exceeds the limit. The default limit is 32,768 bytes. Reduce the number and size of the fields in the file, or eliminate JOINs and cross-references if possible.
EDA337 THE SEGMENT POINTER AREA LIMIT HAS BEEN EXCEEDED:
An important internal table has a problem. Notify your FOCUS representative.
EDA338 MORE MEMORY IS NEEDED TO OPEN THIS MASTER FILE:
When more than 256 data fields occur in a file, memory is dynamically acquired but was not available. Try increasing the region size.
EDA339 DIALOGUE MANAGER -READ FAILED: CHECK FILEDEF OR ALLOCATION FOR:
The data file to be read cannot be located.
EDA340 DIALOGUE MANAGER -WRITE FILE NOT ALLOCATED OR FILEDEF'ED:
The data file to be written has not been described to the operating system.
EDA341 FML LABEL SYNTAX ERROR:
The FML label violates a naming convention, such as having too many characters, or first character is a digit not a letter.
EDA342 FML TEST VALUES FIRST COLUMN IS GREATER THAN LAST COLUMN:
The FROM-TO range in an FML tag line has a smaller second value than the first value.
EDA343 FML COLUMN INCREMENT VALUE IS INVALID:
The specification of a column in an FML RECAP line is not an integer, or the name is not recognized.
EDA344 FML NEW LABEL DEFINITION IS INCOMPATIBLE WITH OLD:
The FML line is reusing a label, but the supplied format on the RECAP is incompatible with the format of the first usage. Change one or both formats.
EDA345 FML MODEL HAS AN UNRESOLVED LABEL:
A label mentioned in an FML RECAP line has not been found in the model. Check for a spelling error, or for a non-unique truncation.
EDA346 DESCRIPTION ERROR. GROUP SPANS FIELDS ON DIFFERENT SEGMENTS:
The fields spanned by a GROUP must all be in the same segment. Check the length of the GROUP.
EDA347 DESCRIPTION ERROR. GROUP SPAN SPLITS A FIELD IN THE MIDDLE:
A GROUP length must cover its set of consecutive fields exactly. Its length must equal the sum of their lengths.
EDA348 ERROR WRITING HOLD FILE DESCRIPTION TO HOLD MASTER
An I/O error has prevented the HOLD MASTER from being written. Check to see that adequate file space is available.
EDA349 OUTPUT FILE NOT ALLOCATED:
Some TSO files must be allocated prior to usage.
EDA350 ERROR WRITING OUTPUT FILE:
An I/O type error prevented the file named from being written.
EDA351 INPUT FILE NOT ALLOCATED:
All TSO files must be allocated prior to use.
EDA352 ERROR READING INPUT FILE:
An I/O type error occurred while reading a file. Check the DCB parameters.
EDA353 COPY COMMAND. READ ERROR
The FROM file cannot be used.
EDA354 COPY COMMAND. WRITE ERROR
The TO file cannot be written. Check its allocation.
EDA355 COPY COMMAND. SYNTAX ERROR
The syntax of the command contains an error.
EDA356 COPY COMMAND. NO FILENAME OR INCORRECT FILENAME
The syntax of the command is missing one of the files FROM or TO.
EDA357 COPY COMMAND. INCORRECT DCB OR DISP PARAMETER
The description of one of the FROM or TO files contains an error in the JCL.
EDA358 ERROR ISSUING FILEDEF COMMAND FOR:
An error in the FILEDEF has been encountered. (CMS only.)
EDA359 OCCURS FIELD IS NOT IN THE PARENT OR GRAND-PARENT SEGMENT:
The Master File attribute of OCCURS refers to a field which is not in the path of the segment. It cannot serve as an occurrence counter.
EDA360 INVALID FIXED OCCURS VALUE:
The valid values for the Master File attribute of OCCURS range from 1 to 4095.
EDA361 POSITION FIELD IS NOT IN THE PARENT SEGMENT:
The Master File attribute of POSITION remaps a parent segment only. The field at the remap start must therefore be in the parent.
EDA362 LASTFIELD NOT IN OWN SEGMENT:
The Master File attribute of LASTFIELD must be in the parent segment which is being remapped.
EDA363 THE OCCURS KEYWORD IS NOT PERMITTED IN FOCUS FILES. SEGMENT:
The Master File attribute of OCCURS is not supported for FOCUS files.
EDA364 MAXIMUM NUMBER OF 'JOINS' EXCEEDED. CLEAR SOME AND RE-ENTER:
The number of separate JOIN commands exceeds the current limit of 16.
EDA365 THE PAGE NUMBER IS BEYOND THE END OF THE OF FILE:
The ? FILE file name command has encountered a page which exceeds the known size of the physical data set.
EDA366 THE PAGE NUMBER EXCEEDS THE MAXIMUM RECORDED FOR THIS SEGMENT:
In counting physical segment instances with ? FILE file name the following page is longer than any recorded for this segment.
EDA367 THE PAGE USED BY THE SEGMENT NOT RECORDED AS OWNED BY SEGMENT:
A page has been retrieved in ? FILE file name which does not belong to the segment. The file is damaged.
EDA368 AN INVALID PAGE NUMBER HAS BEEN ENCOUNTERED FOR THIS SEGMENT
The physical segment page control has encountered an invalid page. The file is damaged.
EDA369 ADDITIONAL PAGES ARE RECORDED FOR THIS SEGMENT:
The number of physical pages retrieved to count segment instances in the ? FILE file name is smaller than it appears it should be. The physical file integrity is suspect.
EDA370 THE FIELDNAME USED IN JOIN CANNOT BE FOUND IN THE FILE:
The key field in a JOIN is not found in the MASTER file description.
EDA371 THE JOIN IS ALREADY ON THE LIST OF ACTIVE JOINS:
A duplicate JOIN has been issued. If it is intended, then use a different 'AS' label for each.
EDA372 'QUIT' IS NOT A VALID REPLY:
The option of replying QUIT to a Dialogue Manager prompt has been turned off.
EDA373 DYNAMIC ALLOCATION FAILED %1%2%3
Return code means: 2 - Unavailable System Resource, 3 - Invalid Parameter List, 4 - Environmental Error, 7 - System Routine Error. For further information, see MVS/XA SPL:System Macros & Facilities, Vol.1,p.1-262, or OS/VS2 Job Management, Supervisor and TSO, p.80
EDA374 DIALOGUE MGR VARIABLE IS NOT SPECIFIED BEFORE USE IN -READ:
The option -READ requires information about the variables being read, for example, their length.
EDA375 MAXIMUM FIELDS IN SINGLE 'JOIN' EXPRESSION EXCEEDS 4:
The number of fields connected by the word 'AND' cannot exceed four (for example, JOIN F1 AND F2...TO...).
EDA376 SYNTAX ERROR OR MISSING ELEMENT IN THE JOIN/COMBINE COMMAND:
A required word is missing or perhaps misspelled. See the section on 'JOIN' for the required format (for example, JOIN field IN file TO field IN file AS name).
EDA377 JOIN IS NOT SUPPORTED BETWEEN THESE FILE TYPES:
The 'FROM' file and 'TO' file have file types for which the current level of 'JOIN' cannot be used. The MASTER description attribute of SUFFIX is used to determine the file type.
EDA378 RECORD LENGTH LESS THAN THE SEGMENT LENGTH FOR FILE:
An external file has an ALLOC or FILEDEF smaller than the MASTER description for the file or segment in question in the file.
EDA379 THE FOCUS REQUEST DOES NOT REFERENCE ANY REAL FIELDS
The request statement does not have any fields in it, or contains only constants. The security option of 'NOPRINT' will ignore protected fields; if only these are present no report is possible.
EDA380 CANNOT JOIN TO 'FROM' FILE WITH MORE THAN ONE SEGMENT
'FROM' file in an external join cannot consist of more than one segment.
EDA381 MORE THAN ONE SEGMENT REFERENCED IN FIRST FILE IN JOIN
The fields to be combined (field AND field..) are on different external file segments, and cannot be assembled for use as a key to other external files (the 'TO' file).
EDA382 WRONG SEGMENT FROM INTERFACE FOR FIRST FILE IN JOIN
EDA383 UNIQUE JOIN MAY NOT BE APPLIED TO A 'TO' FILE WITH DUPLICATES
If the 'TO' field has duplicates, the JOIN command must specify each field name in file.
EDA384 THE 'FROM' FIELD IN THE JOIN IS NOT SORTED:
When a JOIN is used between two sequential files, both must be in the same sort order.
EDA385 THE 'TO' FIELD IN THE JOIN IS NOT SORTED
The 'TO' field must be in sorted order, or indexed. When a JOIN is used between sequential files, both must be in the same sort order.
EDA386 RETRIEVAL ERROR READING 'TO' FILE
EDA387 FILE DEFINITION ERROR. A SEGMENT HAS NO DATA FIELDS:
The Master File Description has a segment for which no fields have been provided. Check the description for an extra line.
EDA388 FATAL ERROR IN REMOTE EXTERNAL DATA BASE ACCESS:
External Data Base Access Module reports a fatal error in the distributed environment.
EDA389 FOCUS DATABASE PAGE INTEGRITY VIOLATION DETECTED IN:
A severe database integrity error was detected. FOCUS was unable to recover from this error and will return to the host environment. 00110(FOC390) WARNING. POSSIBLE CORRUPTION OF FOCUS ENVIRONMENT The CMS maximum number of LOADLIBs that can be GLOBALed has been exceeded. A minimal set necessary for FOCUS to function has been reinstated. All others have been lost.
EDA391 INVALID VERSION. HLI PROGRAM CANNOT BE EXECUTED. RERUN GENHLI
Version level of HLI program must match the version level of the FOCUS they are running with.
EDA392 TEXT FIELD DATA DOES NOT END WITH %$
TEXT FIELD data in a transaction file should always end with %$.
EDA393 CENTRAL SU ERROR (805:
EDA394 CENTRAL SU ERROR (806:
EDA395 CANNOT WRITE TO A FILE WHOSE 'USE' COMMAND REQUESTS 'READ'
If a file is specified as 'READ' in a USE command, a MODIFY procedure may not attempt to INCLUDE, UPDATE or DELETE data.
EDA396 MASTER ATTRIBUTE REPEATED. TERMINATOR (,$ MISSING?:
Check your Master File Description for syntax errors.
EDA397 LENGTH OF FIELDS ON FOCUS FILE SEGMENT EXCEEDS 4000 BYTES:
The sum of the field lengths on a segment exceeds maximum. Break the segment into two using a unique segment, or reduce the size or number of fields.
EDA398 DYNAM COMMAND REJECTED, INAPPROPRIATE DDNAME: %1%2%3
1) The allocation can't be changed; (FREE, CONCAT, ALLOC REUSE): file is common for all MSO users (global) or has PERM attribute.
2) The file has a HIPERFOCUS attribute (CONCAT). 3) Requested HIPERFOCUS attribute can't be assigned, DDNAME exception (ALLOC).
EDA399 MORE THAN ONE SEGMENT CANNOT BE USED IN A FIX TO FOCUS JOIN
When FIX to FOCUS join is in effect only fields from one FOCUS segment may be referenced.
EDA401 THE MODIFY SUBCOMMAND IS NOT RECOGNIZED:
The subcommand issued in a MODIFY procedure is not recognized. Check the list of subcommands.
EDA402 UNRECOGNIZED WORD:
The parser of a MODIFY subcommand does not recognize a word. Check the syntax and spelling of the subcommand.
EDA403 THE TRANSACTION DATA FILE CANNOT BE LOCATED:
The name of the file containing the transactions is provided on the DATA ON ddname subcommand. FOCUS cannot locate the file if it is missing the FILEDEF (CMS), ALLOCATE, DYNAM, or DD statement (MVS).
EDA404 INCOMPLETE MODIFY PROCEDURE
The MODIFY procedure was not executed due to an error in the procedure, or it was terminated by a QUIT command or a premature END statement.
EDA405 TRANSACTION REJECTED. DUPLICATE
The MATCH conditions for transaction number n all match corresponding database records. The option ON MATCH REJECT is in effect (explicitly or by default), and the transaction is rejected.
EDA406 THE FIELDNAME IS NOT RECOGNIZED:
The name of the data field is not on the list of fields for this file. Check the spelling or the list of field names and aliases for the file.
EDA407 THE TRUNCATED FIELDNAME IS NOT UNIQUE:
The short form used to identify a data field is not unique and could apply to another field in the file. Use additional letters, or the full field name or alias, to make it unique.
EDA408 AN INCORRECT OPTION IS SPECIFIED AFTER 'ON':
The action after the word ON is not valid. Specify a valid action such as MATCH, NOMATCH, NEXT, NONEXT, INVALID.
EDA409 AN 'ON MATCH' SUBCOMMAND CONFLICTS WITH A PRIOR SUBCOMMAND:
The subcommand conflicts with a previous one. They are mutually exclusive. For instance, ON MATCH DELETE conflicts with ON MATCH UPDATE.
EDA410 THE ACTION AFTER 'ON MATCH' IS INVALID:
The action following ON MATCH is not valid. Choose a valid action such as DELETE, REJECT, COMPUTE, CONTINUE, VALIDATE, FIXFORM, FREEFORM, PROMPT, CRTFORM, TYPE, GOTO, IF, PERFORM.
EDA411 THE ACTION AFTER 'ON NOMATCH' IS INVALID:
The action following ON NOMATCH is not valid. Choose a correct action such as INCLUDE, REJECT, COMPUTE, VALIDATE, FIXFORM, FREEFORM, PROMPT, CRTFORM, TYPE, GOTO, PERFORM, IF.
EDA412 THE FIELD NAMED IS NOT A DEFINED VALIDITY TEST:
A name is used in a VALIDATE subcommand without an accompanying expression or prior definition in a COMPUTE.
EDA413 NULL TRANSACTION AND/OR DUPLICATE TRANSACTION
Two transactions are the same and the option ON MATCH REJECT is in effect explicitly or by default, or insufficient data appears on the transaction.
EDA414 NO DATA WAS SUPPLIED FOR AN INCLUDE ACTION
The transaction does not contain data for descendent segments, although the procedure explicitly requires them.
EDA415 TRANSACTION REJECTED. NOMATCH
Transaction number n does not match corresponding database fields as specified by the MATCH subcommand. The name of the segment (SEGNAME) on which NOMATCH occurred is displayed for reference, followed by the full transaction record.
EDA416 MORE VALUES SUPPLIED THAN FIELDS IN THE MASTER FILE DESCRIPTION
Freeform data, in which commas delimit each value, contain too many commas. Or, a field is identified by its order number in the Master File Description, which exceeds the number of fields in the file.
EDA417 ADDITIONAL MEMORY IS NEEDED FOR RECORD WORK SPACE
Before transaction processing starts, work space is obtained. If this is not adequate, then more memory is needed. Try increasing the amount of memory available.
EDA418 THE DISK CONTAINING THE FOCUS FILE IS NOT WRITABLE
The FOCUS file cannot be modified because the disk in which it resides is not writable. Issue a USE...READ command if MODIFY is being used but the file is not to be updated.
EDA419 FIXFORM SUBCOMMAND ELEMENT OR FIELDNAME NOT RECOGNIZED:
An element on the FIXFORM subcommand, such as the number of characters to process, cannot be identified.
EDA420 THE FIELD NAMED DOES NOT HAVE A COMPUTED EXPRESSION:
EDA421 TRANSACTION REJECTED. INVALID:
Transaction number n failed the validate test for it. The name of the test is displayed, followed by the COMPUTE transaction.
EDA422 THE FOCUS FILE IS NOT ON A WRITABLE DISK. CANNOT MODIFY:
The FOCUS file cannot be modified, as it does not reside on a disk that can be written to. Issue a USE...READ command if MODIFY is being used but the file is not to be updated.
EDA423 AN ERROR OCCURRED WRITING THE LOG FILE NAMED:
An input/output error has occurred while writing a transaction to a log file. The LRECL (length) parameter may not be large enough on the FILEDEF (CMS), ALLOCATE, DYNAM, or DD statement (MVS). It must be large enough to write a full logical transaction.
EDA424 THE TYPE OF LOG RECORD IS NOT RECOGNIZED:
The activity to log is not allowed. Choose a valid option such as NOMATCH, INVALID, DUPL, TRANS, ACCEPT, or FORMAT.
EDA425 A SYNTAX ERROR OCCURRED ON THE LOG SUBCOMMAND:
A word is not recognized in the LOG subcommand.
EDA426 THE LOG FILE MUST HAVE A FILEDEF OR ALLOCATION ISSUED:
Prior to the MODIFY procedure, the log file must have a FILEDEF (CMS), ALLOCATE, DYNAM, or DD statement (MVS).
EDA427 LOG MESSAGES MUST BE EITHER ON OR OFF:
The syntax in the LOG subcommand mentions messages but is not either MSG ON or MSG OFF.
EDA428 THE FORMAT OF THE DATA VALUE IS INCORRECT:
On a FREEFORM transaction (comma delimited) a field value either exceeds the length specified for it, or a numeric field is given a nonnumeric character.
EDA429 NESTED GROUPS ARE NOT ALLOWED ON A FIXFORM STATEMENT
The FIXFORM subcommand specifies repeating groups of fields which are enclosed in parentheses. Within one set of parentheses, another set has been detected, which is not permitted.
EDA430 TRANSACTION REJECTED. DUPLICATE UNIQUE SEGMENT:
For a segment with SEGTYPE=U (unique), an attempt has been made to include more than one segment on this chain. The transaction is treated as a duplicate and rejected. It is logged on the DUPLLOG file if one has been specified.
EDA431 TOO MANY MATCHES ON NON-KEY FIELDS
There is a limit of approximately 150 MATCHes on non-key fields within a single MODIFY. Possibly the MODIFY does not specify an explicit MATCH, and the file contains blank SEGTYPEs, which requires that all fields on the segment must be matched.
EDA432 CANNOT MATCH ON, UPDATE, OR REPOSITION A TEMPORARY FIELD:
The list of fields to match on the MATCH subcommand must all exist in the data file. They cannot be computed fields unless they have the same name as real fields.
EDA433 A START OR STOP SUBCOMMAND REQUIRES AN INTEGER:
The value following a START or STOP subcommand must be a positive integer.
EDA434 THE PROCEDURE CONTAINS CONFLICTING SUBCOMMANDS
The MODIFY procedure contains instructions which cannot be used together, such as FIXFORM and FREEFORM.
EDA435 THE MATCH CONDITIONS ARE MISSING. SUPPLY THEM FIRST
An ON MATCH or ON NOMATCH subcommand precedes any match condition. A line may have been left out of the procedure or inserted at the wrong point.
EDA436 THE SOURCE OF DATA IS MISSING. THERE IS NO DATA COMMAND
The subcommand DATA must be present in the procedure to identify the source of the transactions or the start of the data entry.
EDA437 THE FORMAT USED WITH FIXFORM IS INCOMPATIBLE WITH THE DATA FORMAT
The type and/or length specifications on a FIXFORM element is not compatible with its format attribute. For example, the error occurs if a FIXFORM has COST/P4, and COST is described as D8.2 in the Master File Description.
EDA438 YOU CANNOT SCAN A NON-FOCUS FILE
Only Master File Descriptions containing the attribute SUFFIX=FOC are considered FOCUS files.
EDA439 WARNING. A MATCH CONDITION HAS BEEN ASSUMED FOR:
Some segment keys are not mentioned in the MODIFY procedure, but the segment must be retrieved to process the transaction. Add any necessary MATCH statements and check that all segment keys are mentioned.
EDA440 CHECK CONDITIONS MUST BE EITHER ON OR OFF
The MODIFY subcommand CHECK has the options ON or OFF, or a positive integer.
EDA441 WARNING. THE FILE EXISTS ALREADY. CREATE WILL WRITE OVER IT
The use of the CREATE command destroys an existing file as if it were erased. Type END, QUIT, N or NO to stop the CREATE process and avoid the erasure. Any other response allows the CREATE to continue.
EDA442 ERROR CREATING THE NEW FILE:
An error was encountered during the CREATE command. Possibly more disk space is needed.
EDA443 YOU CANNOT DELETE OR INCLUDE ON AN INDEXED VIEW SEGMENT:
A MODIFY on a file view, using the command 'MODIFY FILE filename.fieldname', cannot delete or include instances of the segment containing the field specified in the indexed view.
EDA444 THE SAME RECORD CANNOT BE DELETED TWICE IN ROW. DUPLICATE:
Two transactions are attempting to delete the same record. The rejected transaction is considered a duplicate.
EDA445 WARNING. THE LAST MODIFY DID NOT COMPLETE NORMALLY
The last MODIFY or SCAN did not end with a normal end of transaction stream, or stop. The contents of the file should be checked. To clear the message enter 'CHECK FILE file name CLEAR'.
EDA446 THE FOCUS FILE SIZE IS LESS THAN THE PHYSICAL FILE SIZE
The effect of a MODIFY procedure that did not complete normally is seen in a lack of correspondence between the FOCUS logical file size and the blocks allocated to the file.
EDA447 THE FOCUS FILE SIZE IS LARGER THAN THE PHYSICAL FILE SIZE
Some of the blocks assigned to the FOCUS files are missing. Read errors are possible.
EDA448 PREMATURE END OF FILE ON FOCUS FILE. MODIFY NOT COMPLETED
A prior delete procedure did not complete normally and there is a problem in reading the FOCUS file. Try to use the REBUILD command to reconstruct the file.
EDA449 THE LOOKUP OR FIND FIELD IS NOT INDEXED (FIELDTYPE=I):
The field named in FIND (field IN file) or used for a LOOKUP is not indexed in the file named.
EDA450 THE FILE FOR THE FIND OR LOOKUP FIELD CANNOT BE FOUND:
The file named in FIND(field IN file) or used for a LOOKUP cannot be located. A USE command may be needed.
EDA451 DEFINED FIELDS SHOULD NOT BE USED IN MODIFY. USE 'COMPUTE':
The use of defined fields in MODIFY is not allowed. Use the COMPUTE command in MODIFY instead.
EDA452 THE MAXIMUM SPACE FOR PROMPT OR TYPE TEXT HAS BEEN EXCEEDED:
Either the user-supplied text after 'PROMPT fieldname' exceeds 4000 characters, or the combined length of the text and fields in all TYPE statements exceeds the limit of about 32000 characters.
EDA453 FIXFORM LINES MUST BE CONTIGUOUS. UNABLE TO CONTINUE
The FIXFORM subcommands in a single case must follow one after the other. Processing commands cannot be interspersed.
EDA454 ERROR ENCOUNTERED WHILE DELETING. PRIOR MODIFY MAY HAVE FAILED
This error may indicate that a prior MODIFY did not complete normally. The REBUILD utility should be used.
EDA455 RESERVED FOR USE ON ANOTHER PLATFORM
EDA456 THE LENGTH OF THE CRTFORM LINE EXCEEDS THE LOGICAL WIDTH:
The CRTFORM has a maximum number of characters on a line. This is 2 less than the logical width given by the CRTFORM WIDTH parameter. When no width is specified, a width of 78 OR 130 is assumed depending on the terminal. An ending quotation mark may be missing.
EDA457 CRTFORM EXCEEDS 20 LINES
The CRT being used with FIDEL has a default of 20 lines, leaving 4 lines at the bottom of the 24 line screen.
EDA458 WARNING. THE FILE IS NOT AVAILABLE FOR MODIFYING:
The file specified is not a type suitable for MODIFY. It may be a file accessed with a read-only FOCUS interface.
EDA459 VALIDATE IS MISSING FOR AN 'ON VALID' OR 'ON INVALID' STATEMENT:
The TYPE or GOTO option is requested after a validation, but the VALIDATE does not precede the option.
EDA460 UNRECOGNIZED OPTION AFTER 'TYPE':
The option which follows the word TYPE is not one of the recognized options. Choose a valid option such as "message", AT START, AT END or ON ddname.
EDA461 MODIFY PROCEDURE OVERFLOW
This is a rare condition that requires the procedure to be reduced in size. Contact your FOCUS representative.
EDA462 AN OVERFLOW CONDITION HAS BEEN DETECTED IN MODIFY SIZE
The number of steps in the MODIFY procedure has exceeded some bounds and cannot be executed. This message should rarely occur, if ever. If it does occur, reduce the procedure size.
EDA463 FOCUS FILE CANNOT BE MODIFIED BECAUSE IT HAS NOT BEEN CREATED:
Use the CREATE FILE command to create a FOCUS file before modifying the database.
EDA464 RESERVED FOR USE ON ANOTHER PLATFORM
EDA465 WARNING. THE FILE IS NOT ON A WRITABLE DISK
The disk or directory must be attached with WRITE privileges. The file cannot be modified.
EDA466 WARNING. VALIDATE OR COMPUTE FOLLOWS UPDATE, INCLUDE OR DELETE
Generally actions are taken before the database is changed, although in some cases it would be appropriate for actions to be taken afterward. If this is not intended, then move the VALIDATE or COMPUTE subcommand before the action subcommand.
EDA467 WARNING. REJECT OCCURS BEFORE ACTION. ACTION IGNORED ON:
The subcommand ON MATCH REJECT or ON NOMATCH REJECT occurs before an action such as ON MATCH COMPUTE or ON NOMATCH COMPUTE. The COMPUTE will be ignored.
EDA468 THE FILE IS CURRENTLY IN USE. RETRY LATER:
The FOCUS file is currently being updated by another user, and is not available in read-write mode. At the end of usage it will become available.
EDA469 WARNING. A FIELD ON A CROSS REFERENCED SEGMENT IS MENTIONED:
The MODIFY procedure is using a field in a cross-referenced file. While this is permitted, it is often done in error and is flagged for the user.
EDA470 NESTING OF CASES IS NOT PERMITTED. END THE PREVIOUS CASE FIRST
A new case has been started before the word ENDCASE for the current case. Separate the cases.
EDA471 THE CASE NAME EXCEEDS 12 CHARACTERS:
Case names may be from 1 to 12 characters long.
EDA472 'ENDCASE' ENCOUNTERED WITHOUT A PRIOR 'CASE' STATEMENT
The signal for the end of the case, the word ENDCASE, was encountered before the name of case was supplied. A line is missing or out of place.
EDA473 THE REFERENCED CASE IS NOT DEFINED:
A 'GOTO casename' expression specified a name not in this procedure. There may be a typing error or a missing casename.
EDA474 THE NUMBER OF CRTFORM STATEMENTS EXCEEDS 255
A single MODIFY may have up to 255 separate CRTFORM statements. Try to combine some screens into larger continuous forms.
EDA475 THE CRTFORM IS NULL. THE CRTFORM WAS NOT SPECIFIED:
No lines enclosed in double quotation marks have been supplied after a CRTFORM. Check for a misplaced line.
EDA476 RESERVED FOR USE ON ANOTHER PLATFORM
EDA477 THE SPOT MARKER OVERWRITES PART OF THE LINE:
The spot marker positions text or data over some text or data which already occupies that spot. Every data field must be preceded by at least one space.
EDA478 THE USE OF REPEATING GROUPS IS INVALID FOR CRTFORM
The same field names repeat on a form in a pattern which is either ambiguous or in a MATCH or NOMATCH position where it cannot be combined with other parts of the data record.
EDA479 REPEATING GROUPS ARE NOT PERMITTED AFTER A MATCH
The same field names repeat at a position where they cannot be processed. Try to make the entire case repeat.
EDA480 A KEY FIELD CANNOT BE UPDATED USING MODIFY:
A field that is used as a sequence key cannot be named in an ON MATCH UPDATE list. Use the FSCAN or SCAN command REPLACE KEY.
EDA481 THE LOOKUP FIELD IS NOT ON A CROSS REFERENCED SEGMENT:
The field named in the LOOKUP statement cannot be found. Check the spelling.
EDA482 A MEMBER IS NOT SPECIFIED FOR THE PARTITIONED DATASET
A command used the ddname for a PDS; it must identify the particular member.
EDA483 CONCATENATED PARTITIONED DATASETS MUST HAVE A MEMBER NAME
Two or more PDS files are concatenated. The member name must be supplied in order to determine to which PDS it belongs.
EDA484 CONCATENATED SEQUENTIAL DATASETS. UNABLE TO FIND DATASET
The DSORG is PS (physical sequential) and more than one name is associated with a given ddname. The system cannot determine which data set you requested.
EDA485 THE FOLLOWING DATASETS ARE CONCATENATED UNDER DDNAME
List all data sets associated with the specified ddname.
EDA486 A NEW FILE WAS DYNAMICALLY ALLOCATED
A new temporary file has been created and will remain intact until the end of the session.
EDA487 A MEMBER WAS SPECIFIED WITH A NON-PDS FILE
The file is physical sequential but you specified a member name.
EDA488 THE DATASET IS IN THE CATALOG:
The data set described is both allocated and in the system catalog.
EDA489 THE DATASET IS IN THE CATALOG BUT NOT ON VOLUME INDICATED:
A temporary data set is in the catalog but not on the disk. Delete the catalog entry, then reallocate the data set.
EDA490 THE DATASET IS NOT IN THE CATALOG:
The data set is not in any system catalog, and is not allocated.
EDA491 THE SIZE REQUESTED IN CRTFORM EXCEEDS THE TRUE SCREEN SIZE
The CRTFORM WIDTH or HEIGHT statement requires that the physical terminal equal or exceed the dimensions requested. When FOCUS cannot determine the physical size of the terminal, an 80 by 24 screen is assumed. Use SET TRMSW and SET TRMSD if necessary.
EDA492 UNRECOVERABLE FOCUS INDEX ERROR. ERROR CODE:
A fatal error has occurred during the FOCUS database index processing. The file integrity is questionable.
EDA493 NO ACCESSIBLE FIELDS ARE MENTIONED IN THE REQUEST
All the fields mentioned are protected with ACCESS=NOPRINT. No display fields are present in this request.
EDA494 FOCUS INSTALLATION ERROR
A FOCUS installation option was incorrectly installed, or an attempt was made to execute an unlicensed copy of FOCUS in VM/PC. Contact your FOCUS representative or your company FOCUS coordinator.
EDA495 ERROR IN COMPILATION OF MODIFY NAMED:
This message should be accompanied by at least one other message. Try the solution suggested; if recompilation fails, then call your FOCUS representative.
EDA496 ERROR IN EXECUTION OF COMPILED MODIFY NAMED:
FOCUS is unable to run the MODIFY procedure. Recompile the procedure and retry.
EDA497 INTERNAL INCOMPATIBILITY IN COMPILED MODIFY. CODE:
This message should be accompanied by at least one other message. Try the solution suggested; if recompilation fails, then call your FOCUS representative.
EDA498 COMPILE AND RUN TIME MASTER FILES ARE DIFFERENT. RUN TERMINATED:
At the time the RUN command is issued, the Master File Description is checked to see if it has changed from when the COMPILE command was issued. If it has changed, the procedure must be recompiled.
EDA499 SEGMENT NUMBER USED IN 'CRTFORM *' OR 'MATCH *' NOT FOUND:
The file has no segment n which is specified by 'CRTFORM * SEG n' or 'MATCH * SEG n'. Check the FOCEXEC procedure against the Master File Description.
EDA500 SU. THE COMMAND IS NOT RECOGNIZED:
An invalid HLI command was issued. For example, NXT rather than the NEX command. (HLI status code 760)
EDA501 SU. THE COMMAND SYNTAX IS INCORRECT:
Too few arguments have been provided in the HLI command. (HLI status code 761)
EDA502 SU. THE FILE IS NOT OPEN:
The command cannot be executed because the file has not yet been opened. Possibly no OPN command has been issued. (HLI status code 762)
EDA503 SU. MORE MEMORY IS NEEDED ON THE CENTRAL DATABASE MACHINE:
The sink machine requires more virtual storage to operate. Restart the sink machine with more memory. (HLI status code 763)
EDA504 SU. THE MASTER FILE DESCRIPTION CANNOT BE LOCATED:
The requested Master File Description cannot be found by the sink machine. (HLI status code 764)
EDA505 SU. THE DESCRIPTION OF THE DATA CANNOT BE FOUND:
The requested Master File Description cannot be found by the sink machine. (HLI status code 765)
EDA506 SU. NO DATA WAS FOUND FOR THE FILE:
No data was found in the specified file. The file must first be initialized by the CREATE command, even if no data is entered. (HLI status code 766)
EDA507 SU. AN ERROR WAS FOUND IN THE MASTER FILE DESCRIPTION:
An error was encountered in the Master File Description on the sink machine. (HLI status code 767)
EDA508 SU. THE HLI CALL CONTAINS AN INVALID PARAMETER:
An invalid parameter was encountered in an HLI call received by the sink machine (for example, NTEST is less than zero). (HLI status code 768)
EDA509 SU. A FIELDNAME IS NOT FOUND IN THE MASTER FILE DESCRIPTION:
A field name mentioned on a SHO command does not exist in the Master File Description. Check the spelling or the structure of the NAMES array passed into the SHO command. (HLI status code 769)
EDA510 SU. THE FILE IS NOT OPEN. CLOSE IGNORED:
The file specified in the CLO command is not open. The CLO command has been ignored. (HLI status code 770)
EDA511 SU. A SEGMENT NAME IS NOT RECOGNIZED:
The segment specified as a TARGET or an ANCHOR segment is not found in the Master File Description. (HLI status code 771)
EDA512 SU. THE OPTION IS NOT SUPPORTED:
The HLI command passed to the sink is recognized but is not yet supported. (HLI status code 772)
EDA513 SU. NO CURRENT POSITION IS ACTIVE IN THE FILE:
No current position has been established from which to execute the command. (HLI status code 773)
EDA514 SU. THE TEST RELATION IS NOT RECOGNIZED:
An invalid test relation was passed to the sink machine. Possibly the number of tests was specified incorrectly. Valid test conditions are LT, LE, GT, GE, EQ, NE, CO, and OM. (HLI status code 774)
EDA515 SU. IMPROPER USE OF A VIRTUAL SEGMENT:
An attempt was made to change or improperly use a cross-referenced segment. (HLI status code 775)
EDA516 SU. ERROR ON INCLUDE. THE UNIQUE INSTANCE ALREADY EXISTS:
(HLI status code 776)
EDA517 SU. ACCESS DENIED BY EXTERNAL SECURITY SYSTEM:
The external security system such as ACF2, RACF, or TOP SECRET has determined that you do not have access rights to a file controlled by a sink machine.
EDA518 SU. NO PATH EXISTS FROM THE ANCHOR TO THE TARGET SEGMENT:
The ANCHOR and TARGET segments specified do not lie on the same path in the file. (HLI status code 778)
EDA519 SU. THE INDEXED FIELD DOES NOT HAVE FIELDTYPE=I:
An error has occurred in the use of an indexed field, or a field named in an NXD command is not indexed. (HLI status code 779)
EDA520 SU. NO VALUE WAS SUPPLIED FOR AN INDEXED LOOKUP:
(HLI status code 780)
EDA521 SU. NO CURRENT PARENT ESTABLISHED FOR CROSS-REFERENCED RETRIEVAL:
No parent position has been established for the retrieval of a cross-referenced segment. The key for the linked segment is not active, so no retrieval can be performed. (HLI status code 781)
EDA522 SU. THE PASSWORD DOES NOT PROVIDE FILE ACCESS RIGHTS:
Check the password provided in the FCB. (HLI status code 782)
EDA523 SU. THE PASSWORD DOES NOT ALLOW THIS ACTIVITY:
The command issued is not allowed with the current password. Check the password provided in the FCB. (HLI status code 783)
EDA524 SU. ATTEMPT TO INCLUDE A DUPLICATE SEGMENT:
The segment instance identified by the key values is already in the database. The database has not been changed. This is analogous to FOCURRENT=1 in MODIFY/SU. (HLI status code 784)
EDA525 SU. A RANDOMLY A OBTAINED SEGMENT CANNOT BE DELETED:
Segment instances obtained with NXK or NXD may not be deleted. (HLI status code 785)
EDA526 SU. THE CURRENT POSITION HAS BEEN LOST:
The attempt to change, delete or include an instance has not been performed, because the instance was deleted by another user. In the case of include, the parent instance was deleted by another user. Analogous to FOCURRENT=2 in MODIFY/SU. (HLI status code 786)
EDA527 SU. THE FCB IS STILL OPEN AND CANNOT BE REUSED:
An OPN command was issued for an FCB which was already open. Before reusing the FCB, it must be closed. (HLI status code 787)
EDA528 SU. TOO MANY USERS/FCBS ARE OPEN ON THE CENTRAL DATABASE MACHINE:
Too many connections are open on the central database machine (limit 512) or too many FCBs are open (limit 4096). (HLI status code 788)
EDA529 SU. THE CURRENT RECORD HAS BEEN CHANGED BY ANOTHER USER:
The attempt to change the instance has not been performed because another user has already changed the record. This is analogous to FOCURRENT=3 in MODIFY/SU. (HLI status code 789)
EDA530 SU. THE NUMBER OF FIELDS IN THE FILE EXCEEDS 1500:
SU cannot be used with more than 1500 fields in a FOCUS file, including cross-references. (HLI status code 790)
EDA531 SU. ALL FILES IN COMBINE DO NOT HAVE SAME CENTRAL MACHINE:
The FOCUS USE command must designate that all of the files used in COMBINE have the same sink machine. Either they must all be controlled by the same sink or they must all be local files. (HLI status code 791)
EDA532 THE LENGTHS OF THE FIELDS IN THIS CRTFORM CANNOT BE DETERMINED
A Master File Description is not active, there are some computed fields, or there are Dialogue Manager fields. To continue, type IGN(ore) and provide the lengths explicitly, or type ?F file name to activate the appropriate Master File Description.
EDA533 AN INVALID ACCEPT ATTRIBUTE WAS SPECIFIED FOR:
The ACCEPT attribute has an invalid format or contains an invalid relation or invalid data.
EDA534 THE DATA VALUE IS NOT AMONG THE ACCEPTABLE VALUES FOR:
Data is not within the range of values specified by the ACCEPT attribute.
EDA535 MORE MEMORY IS NEEDED TO EXECUTE THE REQUEST:
The amount of main storage is insufficient for executing the specified command. Define larger storage and re-execute the command.
EDA536 ON NEXT UPDATE IS NOT VALID IN SU ON BOTTOM SEGMENT WHEN BLOCKING
An attempt was made to update a segment after retrieval in block mode was issued. In SU you must either turn off block retrieval to do the ON NEXT UPDATE or do a match before the update.
EDA537 ERROR FREEING MEMORY ALLOCATED FOR BLOCK RETRIEVAL IN SU
An internal programming error occurred. Please report this problem, and save the procedure that you were running at the time, to be submitted with the report.
EDA538 SU. CENTRAL AND LOCAL USERS HAVE DIFFERENT MASTER DESCRIPTIONS:
The Master File Description read by the central database machine is not the same as the one used by the source or local machine. (HLI status code 798)
EDA539 ON NEXT DELETE IS NOT VALID ON BOTTOM SEGMENT IN SU WHEN BLOCKING
An attempt was made to do an ON NEXT DELETE while block retrieval was in effect in SU mode. You must do an ON MATCH DELETE or turn blocking off.
EDA540 SU. ENVIRONMENT PROBLEM OCCURRED IN THE CENTRAL DATABASE MACHINE:
The central database machine has terminated because of a fatal error. (HLI status code 800)
EDA541 SU. CENTRAL DATABASE MACHINE ERROR:
A communication error has occurred on the central database machine. (HLI status code 801)
EDA542 SU. COMMUNICATION IS NOT AVAILABLE TO CENTRAL DATABASE MACHINE:
The central database machine has not been started or the wrong name has been used for the central database machine. (HLI status code 802)
EDA543 SU. ERROR COMMUNICATING WITH CENTRAL DATABASE MACHINE:
(HLI status code 803)
EDA544 SU. COMMUNICATION NO LONGER AVAILABLE TO CENTRAL DATABASE MACHINE
The central database machine is not active. Check to see if it has been terminated, and restart it. (HLI status code 804)
EDA545 SU. UNRECOVERABLE CENTRAL DATABASE MACHINE ERROR
(HLI status code 805)
EDA546 SU. UNRECOVERABLE CENTRAL DATABASE MACHINE ERROR
(HLI status code 806)
EDA547 SU. TOO MANY SINK MACHINES AT ONCE
There is a limit of 64 sink machines that can be accessed simultaneously by one user. Please restructure your USE commands.
EDA548 INVALID VERSION. RUN CANNOT BE EXECUTED. RECOMPILE
Compiled MODIFY procedures must be run at the same version level as they were compiled. This is an internal restriction and may or may not be related to the release level.
EDA549 INVALID. A SIMULTANEOUS USER HAS JUST INPUT THIS SEGMENT:
Another FOCUS user has input a segment with the same keys as you. Re-retrieve the data and try again, or alter your MODIFY case logic to check the value of FOCURRENT and automatically retry.
EDA550 INVALID. A SIMULTANEOUS USER HAS JUST CHANGED THIS SEGMENT:
Another FOCUS user has changed some data in this segment before you. Re-retrieve the data and try again, or alter your MODIFY case logic to check the value of FOCURRENT and automatically retry.
EDA551 INVALID. A SIMULTANEOUS USER HAS JUST DELETED THIS SEGMENT:
Another FOCUS user has just deleted the segment you are trying to update or include. Re-retrieve the data and try again, or alter your MODIFY case logic to check the value of FOCURRENT and automatically retry.
EDA552 ERROR IN AUTOMATIC MODIFY GENERATION:
A problem has been detected while generating a MODIFY procedure. Try to increase your virtual storage, or check to see whether the interface to this file is supported by ModifyTalk. If the problem persists, contact your FOCUS representative.
EDA553 A COMPUTATIONAL EXPRESSION IS TOO LARGE
A computational expression in a DEFINE, COMPUTE or -SET command is too large (the limit is approximately 32K for the parsed version). Split the computation up into two expressions, or issue the command SET COMPUTE=OLD and retry.
EDA554 A FIELD AND ITS NAME ARE TOO LONG FOR FIDEL SCREENS:
The total of this field length and name exceeds the width of the FIDEL screen. The field is ignored, and ModifyTalk generation will proceed without it.
EDA555 RESERVED FOR USE ON ANOTHER PLATFORM
EDA556 INSUFFICIENT MEMORY AVAILABLE TO PERFORM IMPORT TRANSLATION
When attempting to allocate dynamic memory for internal tables, the memory allocation routine failed to allocate the space needed. LET or Dialogue Manager variables may be consuming a large amount of memory. Exit out of FOCUS and try the procedure again.
EDA557 SYNTAX ERROR WHEN PARSING IMPORT COMMAND LINE:
A syntax error occurs when a field length is too long or a keyword name is not recognized. Check the spelling of the command parameters.
EDA558 THE FILENAME OF THE IMPORT FILE IS NOT SPECIFIED
The IMPORT command requires that a file name be included in the list of parameters when parameters are specified on the command line. For example, IMPORT FILE=filename,MASTER=MAS,SUFFIX=FOC, TRANSLATMAS=Y.
EDA559 NO DATA WAS FOUND IN THE IMPORT MASTER FILE DESCRIPTION:
The Master File Description was not found or the file was empty. Be sure the Master File Description is in the current directory or is accessible through the FOC$DIR search path.
EDA560 RESERVED FOR USE ON ANOTHER PLATFORM
EDA561 RESERVED FOR USE ON ANOTHER PLATFORM
EDA562 AN ERROR OCCURRED WRITING THE NEW MASTER FILE DESCRIPTION:
While translating the EBCDIC Master File Description to ASCII an error occurred when attempting to write out the new records. The EBCDIC version of the Master File has been renamed with a new extension of .OMA. Rename the master file back to .MAS to continue.
EDA563 RESERVED FOR USE ON ANOTHER PLATFORM
EDA564 THE DATABASE HAS ALREADY BEEN TRANSLATED:
An attempt was made to translate an already translated database. The existing database was not translated a second time; this would destroy data in the database.
EDA565 THE TAPE DRIVE HAS NOT BEEN ALLOCATED:
The tape drive must be allocated and mounted before entering FOCUS. Finish the FOCUS session and allocate the tape drive; then mount the tape that the database is on.
EDA566 THE EXTERNAL DATABASE IS INVALID:
The file did not contain correct database information for translation. Perhaps the file was incorrectly named when it was moved between systems. Check the file on the other system before moving it to be sure of the validity of the database.
EDA567 RESERVED FOR USE ON ANOTHER PLATFORM
EDA568 RESERVED FOR USE ON ANOTHER PLATFORM
EDA569 RESERVED FOR USE ON ANOTHER PLATFORM
EDA570 RESERVED FOR USE ON ANOTHER PLATFORM
EDA571 THE WINDOW SUBCOMMAND IS NOT RECOGNIZED:
An invalid WINDOW subcommand was entered, or the subcommand was omitted. Select a valid option such as ACTIVE, NEXT, SCROLL, SET, ZOOM, MOVE, SIZE, HELP, CLEAR, ON, OFF, ROUTE, COMPILE, RECALL, OPEN or CLOSE.
EDA572 THE OPTION ON THE WINDOW COMMAND IS NOT RECOGNIZED:
An invalid option or window name has been entered for a particular WINDOW subcommand. Check the syntax of the subcommand.
EDA573 THE WINDOW COMMAND IS MISSING AN OPTION
An option is missing for a particular WINDOW subcommand. Check the syntax of the subcommand.
EDA574 AN INVALID NUMERIC VALUE WAS SUPPLIED ON THE WINDOW COMMAND
A nonnumeric value was entered where a numeric value was expected.
EDA575 A WINDOW SUBCOMMAND IS VALID ONLY IN THE WINDOW ENVIRONMENT
A WINDOW subcommand, which is not valid when the window environment is off, was entered. The WINDOW ON command will activate the window environment, after which any WINDOW subcommand can be issued.
EDA576 THE WINDOW NAME IS INVALID:
The window name supplied in the WINDOW command is not a valid window name.
EDA577 THE NUMERIC VALUE IN THE WINDOW COMMAND MUST BE POSITIVE
A negative number was entered in the WINDOW command when a positive number was required. Check the syntax of the subcommand.
EDA578 THE WINDOW COMMAND CONTAINS A NON-UNIQUE TRUNCATION:
The WINDOW command recognizes truncations of its options, but only when the truncation describes only one possible option. Use the full name of the WINDOW command option or window name.
EDA579 INTERNAL INCOMPATIBILITY IN WINDOWS
A problem was detected in the environment windows. On CMS, possibly the file TOEWIN ERRORS could not be found. On TSO, possibly the ERRORS ddname was not allocated or was allocated to the wrong data set.
EDA580 TOO MANY SUBHEAD AND/OR SUBFOOT EXPRESSIONS
The expression 'ON fieldname SUBHEAD/SUBFOOT' can be used up to 9 times in a single TABLE request.
EDA581 SQL LEXICAL ERROR. PLEASE RETYPE THE LINE
The lexical analyzer discovered an error. Check your input.
EDA582 SQL SYNTAX ERROR. PLEASE RETYPE THE LINE
The parser discovered an error. Check your input.
EDA583 THE SQL VERB WAS NOT IMPLEMENTED
An update verb such as DELETE, UPDATE or INSERT is not permitted. The FOCUS SQL Translator is designed for data retrieval only.
EDA584 THE SELECT LIST CONTAINS AN INVALID COMBINATION OF ITEMS
The SELECT list contains a combination of ordinary columns and functions without a GROUP BY clause which included those columns. A SELECT list which does not have a matching GROUP list can include either ordinary columns or functions, but not both.
EDA585 'GROUP BY' OR 'ORDER BY' LIST DOES NOT AGREE WITH SELECT LIST
One or more columns specified in the GROUP BY or ORDER BY list does not appear in the SELECT list.
EDA586 JOIN CONDITIONS OTHER THAN EQUAL ARE NOT SUPPORTED
The FOCUS SQL Translator supports only equijoin.
EDA587 THE SQL SELECT PREDICATE WAS NOT IMPLEMENTED
The particular predicate you used cannot be translated.
EDA588 WHERE AND SUBORDINATE CLAUSES CANNOT CONTAIN FUNCTIONS
Function calls like MIN(fieldname) cannot appear in the WHERE predicate, or in any part of a subordinate ('IN' delimited) clause.
EDA589 WILD CARD SPECIFICATION WAS NOT IMPLEMENTED
Expressions such as "%X___" are not permitted.
EDA590 QUALIFIED COMPARISON WAS NOT IMPLEMENTED
EDA591 NO MEMORY IS AVAILABLE TO COMPLETE YOUR REQUEST
Increase the amount of memory and restart.
EDA592 NAMING RESTRICTION: (X.Y <RELOP> Z.Y IN JOIN IS FORBIDDEN
Such a request might cause the translator to produce an expression like "SIZE GT SIZE," thus it is not allowed.
EDA593 FOCUS OUTPUT CANNOT BE PRODUCED FOR THIS REQUEST
Either an implementation restriction or a complex error, which is context dependent, was detected. This may not be a syntax error, but an error that was discovered during the translation phase.
EDA594 ERROR IN ECHO SPECIFICATIONS, DEFAULT VALUES WILL BE USED
EDA595 THE FILE SPECIFIED IS NOT ALLOCATED
EDA596 FUNCTIONS CANNOT BE NESTED
Expressions of the form 'func1(func2(expression)...)' are not allowed in SQL. Please rewrite the expression to comply with this rule.
EDA597 THERE IS A MISMATCH BETWEEN THE VIEW AND THE SELECT
Check the view definition; the number of columns in the view may be different from the number of columns in the resulting TABLE request.
EDA598 THE COLUMN LISTS IN THE UNION QUERIES ARE NOT THE SAME LENGTH
The column lists in the two UNIONED queries should be the same length.
EDA599 THE ORDER LIST IN THE UNION CONTAINS COLUMN NAMES
The order list in the union you requested contains one or more column names. The order list should contain only numeric column designators.
EDA600 RESERVED FOR USE ON ANOTHER PLATFORM
EDA601 THE TED COMMAND IS UNKNOWN
EDA602 THE COMMAND IS NOT ACTIVE UNDER HELP
Help information may not be changed.
EDA603 ERROR IN CMS. RETURN CODE:
On CMS, if the return code is -2, the command is not valid from within FOCUS, which invokes the command from CMS SUBSET mode. On TSO, this message indicates that the command returned a nonzero error code.
EDA604 ONE OR MORE PARAMETERS IS MISSING
EDA605 A PARAMETER OR COMMAND IS INVALID
EDA606 TOO MANY PARAMETERS WERE PROVIDED
EDA607 HELP IS NOT AVAILABLE
EDA608 HELP IS NOT AVAILABLE IN INPUT MODE
EDA609 THE TARGET LINE WAS NOT FOUND
The line specified as the target in the command line was not found.
EDA610 NO LINES WERE CHANGED
No lines were found containing the string to change.
EDA611 ONE OR MORE OCCURRENCES WAS CHANGED
The specified number of occurrences has been changed.
EDA612 THE CHANGE COMMAND WAS ABORTED
An error has occurred while processing the CHANGE command. Some of the matching lines may have been changed.
EDA613 A PREFIX SUBCOMMAND CONFLICT OCCURRED
The commands placed in the prefix area conflict. For example, F(ollowing) and P(revious).
EDA614 NOT EXECUTED. THE TARGET LINE IS WITHIN THE LINES TO COPY OR MOVE
When moving or copying a block of lines, the point at which the block is to be placed may not be within the block itself.
EDA615 INSUFFICIENT MEMORY EXISTS TO STORE SOME/ALL LINES
There is not enough room in the stack to store further lines. Not all of the requested lines have been stored.
EDA616 ONLY ONE PUT COMMAND MAY BE ENTERED
The PUT commands were not processed.
EDA617 LINES WERE NOT DELETED
Since lines could not be stored, they have not been deleted.
EDA618 INSUFFICIENT MEMORY EXISTS TO COPY ALL LINES
The file is too large to copy all lines. Try copying fewer lines or FILE the changes and begin the edit again.
EDA619 THE FILE WAS NOT FOUND:
The file specified in the GET command could not be located. Correct the file name and retry.
EDA620 THERE ARE NO LINES TO GET
There are no lines in the stack. Check the PUT command issued.
EDA621 LINE LENGTH EXCEEDED. TRUNCATED AT 160 OR RECORD LENGTH
The maximum line length supported by TED is 160 characters. All characters beyond 160 or past the record length have been truncated.
EDA622 AN ATTEMPT WAS MADE TO MOVE PAST THE RECORD LENGTH
The line length is limited to 160 characters or the record length.
EDA623 THE LENGTH LIMIT WAS EXCEEDED. THE LINE MAY BE TRUNCATED
The combined length would exceed the limit of 160 characters or the record length. The second line is truncated.
EDA624 THE CURSOR IS NOT POSITIONED ON A VALID DATA AREA
The SPLIT or JOIN command cannot be processed.
EDA625 THE SAME FILEID CANNOT BE USED TWICE
The attempted change to the fileid would result in ambiguity.
EDA626 NOTE. DEFAULT ASSIGNMENT IS ASSUMED
No operand is specified for the parameter. The default is 'U' for case setting, and 'ON' for scale setting.
EDA627 THERE ARE NO LINES TO RECOVER
EDA628 THE COMMAND CANNOT BE USED WITH MULTIPLE FILES
The command may not be issued with multiple screens active, or in some cases when multiple files are being edited.
EDA629 THE FILETYPE OR DDNAME IS NOT FOCEXEC
The RUN command can only be issued for a file with file type or ddname of FOCEXEC.
EDA630 THE FOCUS FILENAME WAS NOT SUPPLIED WITH ?F
The ?F command requires the FOCUS file name to be supplied.
EDA631 OPERATION INCOMPLETE. INSUFFICIENT MEMORY TO INSERT LINES
The operation attempted has terminated prematurely due to a lack of memory. Check the file being edited to see how far the operation had proceeded. Obtain more memory.
EDA632 THERE ARE ALREADY FOUR WINDOWS ON THE SCREEN
TED allows a maximum of four windows.
EDA633 THE REQUESTED SCREEN SIZE IS TOO SMALL
EDA634 MULTIPLE SCREEN QUITS CANNOT BE PROCESSED
Only one QUIT/QQUIT/FILE/FFILE can be processed at one time.
EDA635 THE FILE HAS BEEN CHANGED. USE QQUIT TO QUIT ANYWAY
The QUIT subcommand may not be used if the file has been altered. Use the FILE command to save the changed version or the QQUIT command to abandon the changes.
EDA636 AN INTERNAL TED ERROR OCCURRED. SAVE THE FILE(S NOW
An error has occurred within TED. Save all files being edited and reenter TED.
EDA637 THERE IS INSUFFICIENT MEMORY TO SATISFY THE REQUEST
Not enough memory is available to continue editing this file. Save the file, obtain more memory and reenter TED/Screen Painter.
EDA638 AN INVALID FREEMAIN OCCURRED
An internal error has been detected. If the error persists, contact your FOCUS representative.
EDA639 SOME COMMANDS WERE NOT EXECUTED
A command separator cannot be used after a command that changes the window layout, such as SPH and QQ of the last file in a window.
EDA640 THIS SCREEN CANNOT BE CLOSED. FILE OR QUIT ANOTHER FIRST
Because of the screen layout, the screen cannot merge with any one of the other screens. File or quit another so that rectangles can be formed at quitting. For further assistance, please contact your FOCUS representative.
EDA641 THE COMMAND IS NOT AVAILABLE IN THIS INSTALLATION
Your installation has disabled the usage of this command. Contact your system programmer or your FOCUS representative for more details.
EDA642 THE FOCUS FUNCTION REQUESTED IS NOT LICENSED
Contact your FOCUS representative to obtain one.
EDA643 A NEGATIVE NUMBER MAY NOT BE RAISED TO A POWER
Exponentiation of negative numbers is not supported and will return the value zero. For example -3**2 will result in zero.
EDA644 THE FILE ALREADY EXISTS. USE FFILE/SSAVE/PPUT/PPUTD
An attempt to write over an existing file has occurred. Please verify and issue the appropriate command.
EDA645 AN ERROR OCCURRED WHILE READING THE FILE
An error has occurred while trying to read the file specified. This error will be followed by another error explaining the condition.
EDA646 AN ERROR OCCURRED WHILE WRITING THE FILE
An error has occurred while trying to write the file specified. This error will be followed by another error explaining the condition.
EDA647 A SYSTEM I/O ERROR OCCURRED
Please contact your FOCUS representative and specify the system return code that appears in the error line.
EDA648 INVALID FILEID
File name, file type or file mode contain invalid characters.
EDA649 THERE IS INSUFFICIENT MEMORY FOR FILE MANAGEMENT
The operating system could not allocate enough memory to handle the file I/O. Obtain more memory and reenter TED.
EDA650 THE DISK IS NOT ACCESSED
EDA651 THE FILE CANNOT BE CLOSED
EDA652 AN ATTEMPT WAS MADE TO WRITE TO A READ-ONLY DISK
EDA653 DISK IS FULL OR PROBLEM IN DATASET/DIRECTORY
Write the file on another disk, or clear some space and file again. For TSO users, either the PDS directory is full, the data set is out of allocated space, or there is an I/O error. In the latter case, this message will be preceded by a system message.
EDA654 THE DISK IS NOT ACCESSED OR IS READ-ONLY
EDA655 The record length exceeds 160. Use IEDIT for wide files.
TED allows for a maximum of 160 characters. Use IEDIT to edit files with lrecl greater than 160. Format: IEDIT fn.
EDA656 THE DATASET ORGANIZATION IS INCOMPATIBLE WITH THE ONE SPECIFIED
A member name may have been specified for a sequential data set, or no member name was supplied for a partitioned data set.
EDA657 THE DATASET NAME IS INVALID
Allowed options are ddname, or dsname with an assumed prefix or a fully qualified dsname.
EDA658 THE FILE CANNOT BE READ USING TED
Either the file is a variable length record, or there is a record containing hex nulls.
EDA659 AN ERROR OCCURRED IN DYNAMIC ALLOCATION OR OPEN
EDA660 THE DDNAME SPECIFIED IS NOT ALLOCATED
EDA661 THE DATASET OR MEMBER IS IN USE
Another user is currently editing this data set or member with TED or a system editor. Try again later.
EDA662 THE NEW DATASET NAME CANNOT BE USED
The new name refers to a data set with a different logical record length (LRECL) from the one currently being edited. The file may not be saved under the new name requested.
EDA663 NOSPLIT MAY NOT BE USED WITH FML
A request cannot contain both the word FOR and the NOSPLIT option.
EDA664 THERE ARE NO FIELDS TO EDIT. FSCAN TERMINATED
There are no fields in the database that can be displayed for editing. Reasons why fields cannot be displayed include DBA security restrictions, fields of length greater than 63, and children of segments whose keys cannot be displayed.
EDA665 A FATAL FSCAN ERROR OCCURRED. FSCAN TERMINATED:
An internal FOCUS database error was detected. FSCAN attempted to recover and to terminate normally. In the attempt, some changes to the file may have been lost. Use ? FILE to check the status of the file.
EDA666 AN EXTERNAL FILE INTERFACE ERROR OCCURRED. FSCAN TERMINATED
A fatal internal error was discovered while attempting to use FSCAN on a non-FOCUS file. Check the Master File Description and the Access File Description.
EDA667 AN ERROR READING OR WRITING THE FILE OCCURRED. FSCAN TERMINATED
An error was encountered in reading from or writing to an internal FSCAN work file. Insufficient memory is one possible cause.
EDA668 COMBINED STRUCTURE CAN BE USED ONLY WITH MODIFY AND CHECK
EDA669 FSCAN CANNOT BE USED WITH AN ALTERNATE VIEW
The syntax FSCAN FILE filename.fieldname is not allowed. Use FSCAN on the file without the alternate view.
EDA670 COMMAND NOT ALLOWED FROM WITHIN FOCUS:
A invalid CMS command was issued. Certain CMS commands cannot be issued from within FOCUS, since they may destroy the environment.
EDA671 UNKNOWN CMS COMMAND:
The command entered was not recognized as a valid command by CMS. If the command is a CP command, it must be preceded by the words CMS CP (for example, CMS CP QUERY TIME instead of CMS QUERY TIME). If the command is an EXEC, it must be preceded by the words CMS EXEC.
EDA672 FSCAN CANNOT BE USED WITH NON-FOCUS FILES. FSCAN TERMINATED
FSCAN is only available for files with SUFFIX=FOC.
EDA673 DBA RESTRICTIONS DO NOT ALLOW FSCAN ON THIS FILE
FSCAN cannot be used because of DBA security restrictions. You can set a different password with the SET PASS or PASS command.
EDA674 A CHILD SCREEN OVERFLOW OCCURRED IN FSCAN FOR SEGMENT:
There is not enough room on the screen to list all the children for a particular segment. FSCAN cannot proceed. Use the SHOW option of the FSCAN command to limit the segments being displayed.
EDA675 THERE IS NO ROOM FOR THE SCREEN IN FSCAN FOR SEGMENT:
An internal error in the screen generation for FSCAN has occurred. Possibly the file has too many fields and/or segments. Use the SHOW option of the FSCAN command to limit the fields and segments being displayed.
EDA676 PANEL OVERFLOW OCCURRED IN FSCAN FOR SEGMENT:
More than 99 panels were needed to fit all the fields for the given segment. Use the SHOW option of the FSCAN command to limit the number of fields being displayed for this segment.
EDA677 THE SCREEN SIZE IS INSUFFICIENT TO RUN FSCAN
To run FSCAN, you must have a minimum of 24 lines on your terminal screen. Use the ? TERM command to check the screen size.
EDA678 GROUP FIELDS MAY NOT BE SHOWN IN FSCAN:
FSCAN cannot display GROUP fields in FOCUS files.
EDA679 THE PATH TO THE FIELD CANNOT BE SHOWN:
While a field selected with the SHOW option of the FSCAN command can be displayed, the key fields lying on the path from the root segment to the selected field cannot be shown. As a result, the selected field cannot be displayed.
EDA680 THE ROOT SEGMENT OF THE DATABASE CONTAINS DUPLICATE KEY VALUES
For FSCAN to maintain the integrity of the database, there can be no duplicate keys in the database.
EDA681 THE KEYS ON THE ROOT SEGMENT ARE TOO LONG TO BE EDITED
For FSCAN to maintain the integrity of the database, there is a limit of approximately 200 bytes of data for the key fields on a given segment.
EDA682 A FATAL FOCUS ERROR OCCURRED. FSCAN TERMINATED
While running FSCAN, a serious FOCUS error was detected that requires FSCAN be terminated. A probable cause is insufficient memory.
EDA683 TOO MANY DATABASES ARE IN USE. FOCUS SESSION TERMINATED
FOCUS has a default limit of 253 databases that can be in use at one time. One database USE entry is created for each file mentioned a USE command and one for each FOCUS or XMI file accessed. A file has been opened that exceeds the limit.
EDA684 FULL SCREEN TERMINAL REQUIRED FOR COMMAND:
A terminal with full screen capability is required to run the command.
EDA685 THE ROOT SEGMENT OF DATABASE CONTAINS KEY(S) WITH INVALID DATA
Key fields that contain leading single quotation marks cannot be edited by FSCAN.
EDA686 THE FIELDNAME CONTAINS AN INVALID CHARACTER AND CANNOT BE SHOWN
Field names that contain the following characters cannot be shown in FSCAN: semicolon, single quote, double quote, left or right parentheses, period, blank, and ampersand.
EDA687 TEXT FIELDS CANNOT BE PRINTED WITH OVER
A text field cannot be printed using over. As a workaround you might use HEADING, FOOTING, SUBHEAD, or SUBFOOT.
EDA688 A FOCEXEC CANNOT BE 'RUN' WHEN USING TED INSIDE FOCCALC
EDA689 AN ERROR OCCURRED WHILE LOADING SCREEN PAINTER
An attempt to activate the Screen Painter has failed.
EDA690 NO 'CRTFORM' LINE WAS FOUND
An attempt to invoke the Screen Painter was made, but no line in the FOCEXEC after the current line contains the word CRTFORM.
EDA691 THE LENGTH EXCEEDS LOGICAL WIDTH. LINE
EDA692 AN UNKNOWN SCREEN PAINTER OR SET COMMAND WAS ISSUED
The command issued or the SET parameter specified is not recognized.
EDA693 THE FIELD LENGTH IS INVALID
EDA694 AN INVALID BOX REGION OR CURSOR POSITION IS DEFINED
An invalid box region is caused by one of the following:
1. The cursor position is outside the valid screen area.
2. The box defined intersects a field.
3. The positions chosen do not define an existing box (for deletion)
EDA695 YOU HAVE EXCEEDED THE LIMIT FOR THIS OPERATION
Either the 300 field limit per screen has been exceeded or the limit of the number of boxes has been exceeded.
EDA696 FATAL CRTFORM ERROR: LINE SKIP CANNOT CREATE A NEW SCREEN
The line skip operator (</) must not have characters following it if the skip is also used to create a new screen. You may either use the Screen Painter to reformat the CRTFORM or move the characters or fields to the next line.
EDA697 NO MASTER FILES WERE FOUND FOR TALK PRODUCTS
Master File Descriptions must be available in order to generate FOCUS requests with TableTalk, ModifyTalk and PlotTalk.
EDA698 NO TABLETALK SAVED SESSION FILES WERE FOUND
Saved TableTalk sessions are kept in files with a TTEDIT file type (CMS) or in the TTEDIT PDS (TSO). You can create a TTEDIT file or member by selecting the menu option to save a TableTalk session after creating a TableTalk request.
EDA699 THE TABLETALK SAVED SESSION WAS NOT FOUND:
No TableTalk saved session file by that name could be found. Check the spelling, or try TABLETALK EDIT with no file name to get a list of saved session files.
EDA700 THE MAXIMUM NUMBER OF TEXT FIELDS IN MODIFY WAS EXCEEDED
The maximum number of text fields in a single MODIFY procedure is 95.
EDA701 A TEXT FIELD CANNOT BE USED AS A SEGMENT SORT KEY
EDA702 THE OPTION SPECIFIED IS NOT AVAILABLE WITH TEXT FIELDS:
The following options are not yet supported with text fields: CRTFORM, TYPE, FSCAN, WHERE, HOLD FORMAT LOTUS, CALC, ISPF, and DIF. Text fields are not currently supported in most non-FOCUS files.
EDA703 PLEASE SUPPLY THE END-OF-TEXT MARK
Data for the text field is entered via TED, and the text does not end with the end-of-text mark (%$). TED tried to insert the end-of-text mark, but failed.
EDA704 THE FIELD CANNOT BE MODIFIED USING TED:
The MODIFY option TED is allowed only with text fields.
EDA705 THERE HAS BEEN AN INVALID USE OF A TEXT FIELD IN FIXFORM:
When using text fields in a FIXFORM subcommand, placing the text fields at the end of the list of fields is required.
EDA706 A TEXT FIELD CANNOT BE INDEXED:
EDA707 THE MAXIMUM NUMBER OF TEXT AND INDEX FIELDS WAS EXCEEDED.
The total number of text field locations and indexed fields allowed in a single FOCUS database structure is 63.
EDA708 A TEXT FIELD CANNOT BE USED AS A SORT FIELD:
Text fields can only be used as verb objects in a report. A text field cannot be used as a BY field.
EDA709 INVALID POSITION OF THE TEXT FIELD DURING SAVE OR HOLD
When creating SAVE or HOLD files, a text field may only be followed by another text field. If a text field is used in the ACROSS set, there may not be any non-text fields in that set.
EDA710 FOCUS VERSION DOES NOT ALLOW TED OPTION ON TEXT FIELDS
Data for text fields can be entered via TED only in CMS CP/A version of FOCUS or TSO XA version.
EDA711 RESERVED FOR USE ON ANOTHER PLATFORM
EDA712 RESERVED FOR USE ON ANOTHER PLATFORM
EDA713 RESERVED FOR USE ON ANOTHER PLATFORM
EDA714 RESERVED FOR USE ON ANOTHER PLATFORM
EDA715 RESERVED FOR USE ON ANOTHER PLATFORM
EDA716 RESERVED FOR USE ON ANOTHER PLATFORM
EDA717 RESERVED FOR USE ON ANOTHER PLATFORM
EDA718 RESERVED FOR USE ON ANOTHER PLATFORM
EDA719 RESERVED FOR USE ON ANOTHER PLATFORM
EDA720 THE NUMBER OF INDEXES ADDED AFTER FILE CREATION EXCEEDS 7:
A limit of 7 additional indexes may be added after the file is created using REBUILD INDEX. To correct the problem, the file can be completely rebuilt using REBUILD DUMP and REBUILD LOAD.
EDA721 AN ERROR OCCURRED WHILE READING THE WINDOW SOURCE FILE:
The file is missing or cannot be opened for input, or an I/O error was encountered when reading a record. On MVS, check the allocation of the TRF ddname.
EDA722 AN ERROR OCCURRED WHILE WRITING THE WINDOW OUTPUT FILE:
The file cannot be opened for output, or an error was encountered while writing a record. On MVS, check the allocation of the FMU ddname.
EDA723 SYNTAX ERROR IN WINDOW:
An error was encountered in processing the window source file. Possibly a syntax error was discovered in parsing the window file. On MVS, check the allocation of the TRF ddname.
EDA724 CACHE MUST HAVE AT LEAST TWO PAGES
A SET CACHE command was issued with a negative number of pages, or with only one page. The cache status prevailing before this SET CACHE command remains unchanged.
EDA725 THE HLI PROFILE CONTAINS AN ERROR
Only certain SET commands may be issued in the HLI profile. Either a non-SET line was found, or an invalid SET command was issued. Check the file PROFILE HLI on CMS or member HLIPROF of the FOCEXEC data set on MVS. The erroneous line was ignored.
EDA726 THE OPTION IS NOT SUPPORTED WITH COMMIT/SU:
COMMIT/SU does not support the use of an alternate file view.
EDA727 CREATE MUST BE FOLLOWED BY INSERT
CREATE TABLE is only supported in the FOCUS SQL Translator when immediately followed by one or more INSERT INTO statements.
EDA728 INSERT MUST BE PRECEDED BY CREATE
INSERT INTO is only supported in the FOCUS SQL Translator when immediately preceded by a CREATE TABLE statement.
EDA729 THE TABLE NAME USED IN CREATE AND INSERT MUST BE THE SAME
EDA730 A NEGATIVE VALUE FOR PANEL IS ILLEGAL, PANEL IS SET TO '0'
The PANEL setting should be positive, or zero to set it off.
EDA731 THE DEFINE-BASED JOIN IS IMPROPERLY DEFINED:
The specified field name is not in the path of the define-based join.
EDA732 COMPUTED FIELDS CAN ONLY BE REFERENCED IN A WHERE TOTAL
The boolean expression in the WHERE clause includes a reference to a computed field. Since WHERE expressions are evaluated before retrieval and computed fields are evaluated after retrieval, this can only be achieved using WHERE TOTAL.
EDA733 AGGREGATION FUNCTIONS CAN BE USED ONLY IN A WHERE TOTAL
The boolean expression in the WHERE clause includes a reference to an aggregation function. Since WHERE expressions are evaluated before retrieval and computed fields are evaluated after retrieval, this can only be achieved using WHERE TOTAL.
EDA734 AN UNRECOVERABLE ERROR OCCURRED IN ACE:
A fatal internal error has occurred within ACE. Possibly a problem exists with the central ACE sink machine.
EDA735 THE APPLICATION WAS NOT FOUND IN THE ACE APPLICATION DIRECTORY:
You have asked to run an application which is not registered in the ACE application directory. You can obtain a list of registered applications with the ACE MENU command.
EDA736 ACE APPLICATIONS ARE NESTED TOO DEEPLY
An ACE application can issue an ACE RUN command for another application, but you can only nest applications this way to a depth of eight.
EDA737 ACCESS IS DENIED BY ACE SECURITY
The user does not have sufficient access rights to use this ACE application or file. Check with the owner of the application or file.
EDA738 THE ACE FILENAME IS NOT UNIQUE. AN APPLICATION MUST BE SPECIFIED:
You cannot omit the application name in the ACE SETUP FILE command if more than one database exists for that name. Supply the name in the ACE SETUP command. For example, to set up the employee file for the application payroll, issue ACE SETUP FILE PAYROLL:EMPLOYEE.
EDA739 THE DATABASE IS NOT FOUND IN THE ACE APPLICATION DIRECTORY:
An ACE SETUP FILE command was issued for a database which is not registered in the ACE application directory. To see a list of databases, issue the ACE MENU DBS command.
EDA740 AN INVALID OPTION WAS SPECIFIED IN THE ACE COMMAND:
A subcommand or option to the ACE command was not recognized. Please check the syntax for the function you want to use and try again.
EDA741 AN OPTION IS MISSING IN THE ACE COMMAND:
A subcommand, option, application identifier, or file identifier was not found in the ACE command where it was expected. Please check the syntax for the function you want and try again.
EDA742 AN INVALID ACE SECURITY RULE WAS FOUND:
A syntax error was discovered while processing the specified ACE security rule set. Possibly a semicolon was omitted from the end of one of the rules. Security access is denied to the requested entity. Check with the owner of the entity.
EDA743 THE ACE CENTRALLY STORED FILE OR RULE WAS NOT FOUND:
On ACE EXPORT or TED, the named file did not exist in the Central Storage Filesystem. On parsing or execution of an ACE rule, the rule was not found. Check the file identifier and try again.
EDA744 ACE SETUP FAILED
This message appears in many circumstances. ACE SETUP can link minidisks, allocate data sets, issue USEs, etc. Any one or more of these operations may have failed in the ACE SETUP, generating this message. Look at preceding errors for more information.
EDA745 THE FILE WAS NOT FOUND ON DISK FOR THE ACE OPERATION:
On an ACE IMPORT or ACE RULECHK, the disk file was not found. Please check the file identifier and try your request again.
EDA746 AN ATTEMPT WAS MADE TO RUN A NON-RUNNABLE ACE APPLICATION:
No ACE PROLOG exists for the named application. Therefore it cannot be run. Check the name of the application you wanted to run and try again. Otherwise, you may add a prolog to the application so you can run it.
EDA747 THE FILENAME CANNOT BE FOUND IN AN 'ACE USE' COMMAND:
You have tried to ACE CLEAR a file name which has never been ACE USEd or which has been already ACE CLEARed.
EDA748 THE RESTRICT ACE RULE IS ON A COMBINED FILE
The RESTRICT ACE rule is permitted only on single files, not on COMBINEd files. Each file of the COMBINE should be restricted separately.
EDA749 AN INVALID ACE ALLOC OR ACE FREE WAS ISSUED:
Either an ACE ALLOCation did not succeed, or an ACE FREE was attempted for a not yet allocated file. Check the parameters in your ACE logical database description and try again.
EDA750 RESERVED FOR USE ON ANOTHER PLATFORM
EDA751 RESERVED FOR USE ON ANOTHER PLATFORM
EDA752 RESERVED FOR USE ON ANOTHER PLATFORM
EDA753 RESERVED FOR USE ON ANOTHER PLATFORM
EDA754 RESERVED FOR USE ON ANOTHER PLATFORM
EDA755 RESERVED FOR USE ON ANOTHER PLATFORM
EDA756 RESERVED FOR USE ON ANOTHER PLATFORM
EDA757 WARNING. YOU REQUESTED PRINT * OR COUNT * FOR A MULTIPATH FILE
The PRINT * and COUNT * commands cause the leftmost path in a file to be referenced. If the file has more than one path, data which is not part of the leftmost path is not printed or counted.
EDA758 NO FILE INTEGRITY IS AVAILABLE. MODIFY TERMINATED
The COMMIT/ROLLBACK feature of MODIFY requires Absolute File Integrity in order to run.
EDA759 A FATAL ERROR OCCURRED DURING COMMIT. MODIFY TERMINATED
A fatal error was encountered while applying the COMMIT to the database.
EDA760 A FATAL ERROR OCCURRED DURING ROLLBACK. MODIFY TERMINATED
A fatal error was encountered while attempting to ROLLBACK the database.
EDA761 FOCSORT CANNOT BE INITIALIZED. MODIFY TERMINATED
In order to run a MODIFY with the COMMIT/ROLLBACK feature, FOCSORT must be used. Check to see if FOCSORT was allocated properly.
EDA762 THE 'WHEN' CLAUSE CAN APPEAR ONCE FOR EACH 'ON' OPTION
The WHEN clause can be used only after 'ON field option', and only once for each option. For screening records, use the WHERE clause.
EDA763 WARNING. PRINT * WILL DISPLAY A MAXIMUM OF 256 FIELDS
The verb phrase 'PRINT *' was coded in a TABLE request for a file which contains more than 256 fields. The report will display only the first 256 fields encountered.
EDA764 WINDOW PAINTER CANNOT BE EXECUTED FROM THIS ENVIRONMENT
The Window Painter cannot be executed while running another FOCUS command, such as MODIFY or TABLE. Complete the first command with a QUIT or an END before attempting to start the Window Painter.
EDA765 WARNING. LOGICAL RECORD LENGTH EXCEEDED. THE LINE WAS TRUNCATED
The maximum line length allowed for the HOLD file was exceeded. Therefore the line was truncated.
EDA766 UNABLE TO ESTABLISH SINK POSITION. ROLLBACK FORCED
A position from which to match on the sink could not be established. Any further database actions are meaningless. Therefore, a ROLLBACK is forced.
EDA767 UNABLE TO ESTABLISH NEW COMMIT USER ON THE SINK
There is no more room on the sink for another COMMIT user. As a result, the user is terminated.
EDA768 THERE IS A DUPLICATE FIELD OR ALIAS NAME IN HOLD FORMAT SQL
No duplication of field or alias names is allowed when holding an SQL table. As a result, nothing is held.
EDA769 SU. FUNCTION DISABLED: COMMIT
COMMIT functionality on the sink machine has been disabled. Contact your sink machine administrator.
EDA770 FROM AND TO MUST APPEAR IN PROPER SEQUENCE
'FROM value TO value' clauses must appear as specified. 'FROM' must appear first, and a 'TO' must follow each 'FROM'.
EDA771 TOE MUST REMAIN ACTIVE DURING AN MSO/FOCUS SESSION
The WINDOW OFF command is not allowed when FOCUS is running under MSO.
EDA772 THE FILE TO BE CLEARED FROM THE 'USE' TABLE WAS NOT FOUND
The file specified on the CLEAR option was never ADDed or REPLACED by a previous USE command.
EDA773 THE 'CLEAR' OPTION MUST BE USED ONLY IN 'USE REPLACE'
To clear only selected files from USE table, use the option CLEAR in the USE REPLACE request for each selected file.
EDA774 THE WORD 'IN' MUST APPEAR IN A VALID CLAUSE
The following clauses must adhere strictly to the specified syntax: 'field IN FILE filename' and 'field IN (x,y,z)'.
EDA775 INCLUDES/EXCLUDES SYNTAX MUST BE IN SIMPLE WHERE CLAUSES
WHERE clauses with the INCLUDES or EXCLUDES keywords cannot be joined to other relational operators with the words AND or OR. Try breaking the complex clause into separate parts.
EDA776 MASKED GROUP FIELD TESTS MUST BE IN SIMPLE WHERE CLAUSES
WHERE clauses which refer to group fields with the slash character (/) cannot be used in conjunction with AND or OR. Try breaking the complex clause into separate parts. WHERE TOTAL clauses also may not make use of the slash separator.
EDA777 OPTION FOR 'ON' PHRASE IS NOT SUPPORTED WITH 'WHEN' CLAUSE
Valid options are PAGE-BREAK, RECAP, RECOMPUTE, REPAGE, SKIP-LINE, SUBFOOT, SUBTOTAL, SUB-TOTAL, SUBHEAD, SUMMARIZE and UNDER-LINE.
EDA778 WARNING. BYPANELING HAS BEEN DISABLED
For this TABLE request only, BYPANEL has been set to OFF. It is not possible to establish column location for this report.
EDA779 USER TRIED TO ADD MORE THAN 5 ACE SINKS
No more than five ACE sinks may be added to the hard-coded list at runtime. If you need to add more sinks to the official list, see your system administrator.
EDA780 NO FILES ARE CENTRALLY STORED FOR THE APPLICATION:
ACE was unable to find any centrally stored files owned by this application. It may be a non-runnable application. An application needs at least an ACE Prologue to be runnable.
EDA781 RESERVED FOR USE ON ANOTHER PLATFORM
EDA782 WARNING. BYPANELING DISABLED - GRAPH
For this TABLE request only, BYPANEL has been set to OFF. It is not possible to use BY paneling with GRAPH.
EDA783 WARNING. BYPANELING DISABLED - FOLD-LINE
For this TABLE request only, BYPANEL has been set to OFF. It is not possible to use BY paneling with FOLD-LINE.
EDA784 WARNING. BYPANELING DISABLED - 'IN' REQUEST
For this TABLE request only, BYPANEL has been set to OFF. It is not possible to use BY paneling with IN requests.
EDA785 WARNING. BYPANELING DISABLED - REPORT UNDERFLOW
For this TABLE request only, BYPANEL has been set to OFF. The report width is less than the specified panel-size.
EDA786 WARNING. BYPANELING DISABLED - REQUEST TOO LARGE
For this TABLE request only, BYPANEL has been set to OFF. The number of BY fields requested exceeds the actual number.
EDA787 WARNING. BYPANELING DISABLED - REPORT OVERFLOW
For this TABLE request only, BYPANEL has been set to OFF. The selected BY fields are too big to fit on a single panel.
EDA788 WARNING. THE FIELD TO BE INDEXED IS NOT IN THE HOLD FILE:
The requested field to be indexed is not found in the HOLD file. The field is not indexed.
EDA789 UNABLE TO READ THE DECODE OR 'IN' FILE
The DECODE or IN file (such as WHERE CAR IN XYZ) may have been allocated as a temporary file with no DCB parameters, and is handled by a nonstandard access method such as HiperFOCUS.
EDA790 WARNING. COLUMN SPLITTING WILL OCCUR WITH THIS REPORT
For this TABLE request only, BYPANEL has been set to OFF. It is not possible to establish column location for this report.
EDA791 WARNING. COLUMN SCROLLING HAS BEEN DISABLED
For this TABLE request only, COLUMNS has been set to OFF. It is not possible to establish column location for this report.
EDA792 A FATAL ERROR OCCURRED IN COLUMN TABLE ALLOCATION
This is an internal error. If the error recurs, contact your FOCUS representative.
EDA793 THERE IS NO LICENSE FOR THIS FEATURE:
EDA794 THE SPECIFIED PARAMETER CANNOT BE TEMPORARILY SET:
The specified parameters are not allowed during a TABLE request using ON TABLE SET. If you wish to set these parameters, an explicit SET statement should be issued before the TABLE request. (Consult documentation for valid parameters for ON TABLE SET.)
EDA795 THE ACE ENTITY CANNOT BE STORED IN PRODUCTION
You have tried to FILE in TED a PRODUCTION entity, or IMPORT such an entity. Use FACET to transfer entities to PRODUCTION.
EDA796 DATASET ALLOCATION CANCELLED BY DYNAM USER EXIT
A site-written exit has rejected the allocation of the data set specified in the DYNAM command; request terminated. Contact the site administrator.
EDA797 ALLOCATION TERMINATED, UNABLE TO LOAD DYNAM USER EXIT
A site-written DYNAM allocation exit has been defined but cannot be loaded. Access verification is not available, DYNAM terminates all allocations. Contact the site administrator.
EDA798 THE FOCUS DATABASE EXCEEDS THE MAXIMUM NUMBER OF PAGES:
An attempt has been made to access page number 262,144 in the FOCUS database file. A single FOCUS File can have a maximum of 262,143 (256K-1) pages. Use of LOCATION files for some segments can alleviate this situation.
EDA799 THE TABLE REQUEST CANNOT BE PERFORMED AGAINST THE EXTERNAL FILE
The number of database fields referenced in the TABLE request against the external file exceeds available space.
EDA800 THE TABLEF HEADING OR FOOTING LINE IS TOO LONG
TABLEF encountered an unexpectedly long heading or footing line and was unable to re-initialize. Try using a shorter heading or footing, or use TABLE.
EDA801 ERROR DELETING APPLICATION TABLE
There has been an operating system memory management problem. Try to run the operation again. If it still fails, call your FOCUS representative.
EDA802 ACE TED ERROR:
There has been an error in invoking TED on an ACE file. Check on the existence of the file, under the correct file ID, in the proper environment, and try the request again.
EDA803 INVALID FOCUS COMMAND IN ACE ENABLE/DISABLE:
One of the FOCUS commands on the list may be mistyped, or you may be trying to disable the ACE or EXEC commands, which are not allowed.
EDA804 FOCUS COMMAND IS DISABLED IN ACE SUBSET:
To use this command you must be out of ACE SUBSET. To exit ACE SUBSET, type ACE RETURN.
EDA805 ACE DISABLE/ENABLE IS NOT ALLOWED IN ACE SUBSET
To exit ACE SUBSET, type ACE RETURN.
EDA806 UNEXPECTED END CONDITION ENCOUNTERED WHEN PARSING CONSULT
One of the following was encountered in the middle of parsing a CONSULT verb phrase: END, QUIT, RUN.
EDA807 KNOWLEDGEBASE NAME HAS MORE THAN 8 CHARACTERS:
Knowledgebase names may only contain up to 8 alphanumeric characters.
EDA808 MISSING KNOWLEDGEBASE NAME OR INVALID DELIMITER FOLLOWING NAME
When parsing the CONSULT verb phrase, the required knowledgebase name was not found; or an invalid delimiter was detected following the knowledgebase name.
EDA809 MISSING 'FOR' KEYWORD OR INVALID DELIMITER FOLLOWING KEYWORD
When parsing the CONSULT verb phrase, the keyword FOR following the knowledgebase name was not found; or an invalid delimiter was detected following the keyword FOR.
EDA810 VARIABLE FOLLOWING 'AND', 'FOR', OR 'USING' NOT TO BE FOUND
When parsing the CONSULT verb phrase, a variable name following the AND, FOR, or the USING keyword was not found.
EDA811 INVALID VARIABLE NAME OR DELIMITER FOLLOWING VARIABLE NAME
When parsing the CONSULT verb phrase, an invalid variable name or a delimiter following the variable name was detected.
EDA812 INSUFFICIENT MEMORY TO PROCESS THE CONSULT VERB
The operation attempted has terminated prematurely due to a lack of main memory. Obtain more memory.
EDA813 INVALID FORMAT OR DELIMITER FOLLOWING THE FORMAT FOUND
When parsing the CONSULT verb phrase, an invalid format or delimiter following the format was detected.
EDA814 UNDEFINED FACT NAME IN CONSULT VERB PHRASE:
Variables whose values are being passed to the knowledgebase system must be predefined before the CONSULT verb phrase.
EDA815 INTERNAL SYSTEM ERROR WHEN PARSING THE CONSULT VERB
An internal system error has developed when parsing the CONSULT verb phrase. This can only happen when the FOCUS program currently in memory has been corrupted. Exit FOCUS and try again.
EDA816 MISSING ARGUMENT FOLLOWING THE 'AS' OR 'IN' PHRASE
When parsing the CONSULT verb phrase, the argument following the AS or IN phrase was not to be found.
EDA817 'AS', 'IN', OR 'NOPRINT' ALLOWED ONLY IN TABLE CONTEXT
When parsing the CONSULT verb phrase, the AS, IN, or NOPRINT keyword was not encountered in a TABLE context.
EDA818 MISSING OR INVALID ARGUMENT FOLLOWING THE AS KEYWORD
When parsing the CONSULT verb phrase, the argument following the AS keyword is missing or invalid.
EDA819 MISSING OR INVALID VALUE FOLLOWING THE IN KEYWORD
When parsing the CONSULT verb phrase, the value following the IN keyword is missing or invalid.
EDA820 UNEXPECTED END OF FILE ENCOUNTERED WHEN PARSING CONSULT
An unexpected end of file condition was encountered in the middle of parsing a CONSULT verb phrase in Dialogue Manager.
EDA821 INVALID CONTINUATION LINE ENCOUNTERED WHEN PARSING CONSULT
An invalid continuation line was encountered while in the middle of parsing a CONSULT verb phrase in Dialogue Manager.
EDA822 SPECIFIED FORMAT CONFLICTS WITH DEFINED FORMAT:
The format of the goal variable specified in the CONSULT verb phrase conflicts with the format currently defined for this variable.
EDA823 THE NUMBER OF GOAL AND FACT VARIABLES EXCEEDS 50
The number of goal variables and fact variables in a CONSULT verb phrase should not exceed the currently set MAXIMUM of 50.
EDA824 INVALID USAGE OF WILDCARDS IN ACE IMPORT OR EXPORT:
Only certain pattern types are recognized by ACE IMPORT and ACE EXPORT. Consult your ACE user's manual for proper usage. Alternatively, the FROM or TO phrase and the ACE storage file identifier may be mismatched. Check the command and try again.
EDA825 DDNAME MUST BE ALLOCATED TO SEQUENTIAL DATASET, NOT PDS
The ddname specified in the command must be allocated to a sequential data set. If it is allocated to a partitioned data set, it will destroy that data set's directory of members.
EDA826 PROBLEM ALLOCATING DDNAME TO CONCATENATED DATASET:
A previous allocation not using the 'SHR' option may currently be active.
EDA827 ENQUEUE OF FILE IN CONCATENATED DATASET FAILED:
The specified file is currently enqueued by another user.
EDA828 OPEN OF FILE IN CONCATENATED DATASET FAILED:
The specified file has not been opened for writing.
EDA829 UNABLE TO ALLOCATE FILE:
The named file may not exist or may be in use by another job.
EDA830 ERROR OPENING FILE:
See the IBM Messages and Codes manuals for IEC messages that might appear on the system log.
EDA831 MEMBER NAMED DOES NOT EXIST:
File name may be wrong or misspelled, or the file may be missing.
EDA832 DYNAMIC ALLOCATION FAILED FOR FILE:
This error might appear when trying to deallocate the file.
EDA833 ERROR READING FILE:
Check for conflicting file parameters such as record length, block size, blocking factors, etc. Record length must be 80.
EDA834 SECURITY FAILED - LAST JOB PROCESSED:
An installation may use a customized TSO Security Routine. In this case, SECURITY failed a job in the data-stream being processed. See the System Administrator. Prompting is not supported.
EDA835 SECURITY FAILED - LAST JOB PROCESSED:
An installation may use a customized TSO Security Routine. In this case, SECURITY failed a job in the data-stream being processed. See the System Administrator. Prompting is not supported.
EDA836 SECURITY MODULE FAILURE - LAST JOB PROCESSED:
TSO module IKJEFF10 is unable to continue. A code 16 was received. Report this error to the System Administrator and/or the System Programming staff.
EDA837 JOB %1(%2 SUBMITTED
EDA838 %1 JOBS SUBMITTED
EDA839 HOLD FILE DESTINATION MISSING AFTER ON TABLE HOLD AT
Correct syntax: ON TABLE HOLD AT CLIENT or ON TABLE HOLD AT SERVER. CLIENT or SERVER not specified after AT. AT phrase ignored.
EDA840 HERMES ENTITY NAME NOT YET SUPPORTED. AT IGNORED
Correct syntax: ON TABLE HOLD AT CLIENT or ON TABLE HOLD AT SERVER or ON TABLE HOLD AT hermes_entity_name. Hermes entity name not yet supported. AT phrase ignored.
EDA841 ERROR IN REFERENCING A DEFINED FIELD:
Only the first 256 DEFINE fields can be referenced by another DEFINE field.
EDA842 A NULL LITERAL IS DETECTED IN THE CURRENT LINE
FOCUS does not support null literals. Remove the double apostrophe from the statement.
EDA843 RESTRICT NOT ALLOWED ON FILE WITHOUT DBA:
The RESTRICT command can only be used for restricting, or clearing ACE rules, or for setting the DBA into the FOCUS file.
EDA844 UNCORRECTABLE SYNTAX ERROR:
A syntax error was detected within the current line. Retype the entire line.
EDA845 WHERE TOTAL IS INCOMPATIBLE WITH THE REQUEST.
WHERE TOTAL is not compatible with MATCH FILE. Change the WHERE to an IF.
EDA846 INVALID ACE SETUP PARAMETER SET:
ACE SETUPs are batches of comma-delimited parameters describing separate components created by FACET. A user may have attempted unsuccessfully to change these parameter sets manually. Have the owner of the SETUP recreate it with FACET.
EDA847 WARNING... FOCUS INTERNAL CSA ERROR
FOCUS results are unpredictable. Contact your FOCUS representative.
EDA848 REQUEST NOT ACCEPTED. ABOVE SMARTMODE THRESHOLD
The SmartMode governor determined that your TABLE request would exceed the cost threshold for this database, and canceled the TABLE request.
EDA849 SMARTMODE ESTIMATES THE COST OF THIS QUERY TO EXCEED: %1
The SmartMode governor determined that your TABLE request will exceed the specified the cost threshold for this database.
EDA850 SMARTMODE COST CANNOT BE DETERMINED. REQUEST NOT ACCEPTED
The cost of the TABLE request could not be determined by SmartMode. The DBA instructed SmartMode to cancel all requests for which a cost could not be determined.
EDA851 ERROR IN DEFINING FIELDNAME:
Format K is not supported with USAGE or FORMAT.
EDA852 ACE SECURITY VIOLATION: ACCESS CONTROL FILE MISSING
EDA853 ACE SECURITY VIOLATION: ERROR IN ACCESS CONTROL FILE
EDA854 ACE SECURITY VIOLATION: INSUFFICIENT QUALIFICATION
ACE is expecting more qualifiers for the SQL table. The number of qualifiers specified in ACESECUR ERRORS for SQL/DS does not match the actual number supplied by SQL. Either number mentioned above needs to be adjusted, or info in Access Files needs to be expanded.
EDA855 UNABLE TO LOCATE DATASET
Most likely, the data set is not cataloged. For details, check shown LOCATE (#026) or DYNALLOC (#099) svc return and reason codes.
EDA856 UNABLE TO DELETE
Unusual condition encountered while deleting data set or PDS member. For details, check shown SCRATCH (#029) or STOW (#021) svc return code.
EDA857 UNABLE TO UNCATALOG
Unusual condition encountered while removing reference to data set name from catalog. For details, check shown CATALOG (#026) svc return code.
EDA858 UNABLE TO ALLOCATE
Unusual condition encountered during dynamic allocation of data set. For details, check shown DYNALLOC (#099) svc return and reason codes.
EDA859 UNABLE TO FIND
Most likely, data set or PDS member does not exist. For COPY members, no members are processed. For DELETE and RENAME, all preceding members are processed. For details, check shown svc number (#) and its return and reason codes.
EDA860 FOLLOWING DATASET IS IN USE BY
Specified data set is already allocated to another job or user and its USAGE attribute is incompatible with request. Command terminated.
EDA861 INVALID DATASET ORGANIZATION OF
Non-PDS specified where PDS is expected, or vice versa, or unmovable data set specified as input for copy operation.
EDA862 UNABLE TO OPEN
The error shown is one of the following: abend condition and reason codes (S); svc number and its return and reason codes (#); program return code (R): 08 -insufficient memory, 0C -APPEND option is incompatible with RECFM=FBS.
EDA863 UNABLE TO CLOSE
The error shown is either abend condition and reason codes (S), or svc number and its return and reason codes (#).
EDA864 UNABLE TO DEALLOCATE
Unusual condition encountered during dynamic deallocation of data set. For details, check shown DYNALLOC (#099) svc return and reason codes.
EDA865 UNABLE TO RENAME
Unusual condition encountered while renaming data set or PDS member. For details, check shown SCRATCH (#029) or STOW (#021) svc return code.
EDA866 UNABLE TO REPLACE
New PDS member already exists and REPLACE option is not specified. For COPY members, no members are processed; for DELETE and RENAME, all preceding members are processed.
EDA867 UNABLE TO CATALOG DATASET
Unusual condition encountered while cataloging data set. For details, check shown CATALOG (#026) svc return code.
EDA868 UNABLE TO COMPRESS DATASET
IEBCOPY was unable to compress the data set and we could not obtain IEBCOPY's error message. The error shown is IEBCOPY's return code. Common reasons include lack of APF authorization (required by IEBCOPY), or use of APFAUTH=INTERNAL in the MSO or the server.
EDA869 IEBCOPY FAILED:
Unsuccessful invocation of IEBCOPY. This message is followed by IEBCOPY's error message or data set name and abend code.
EDA870 UNABLE TO COPY
This includes: user data in member's directory entry contains note field(s TTRN (R0114 or R0214), RECFM=U (R0314), LRECL=X specified (R0010) - not supported; insufficient memory (R0008); error during execution of IEBCOPY and unable to get IEBCOPY's error message.
EDA871 INAPPROPRIATE OR MISSING MEMBER SPECIFICATION(S)
The inappropriate specification is either a member name (old or new), a replace option found where it is not expected (for example, for non-PDS), or a replace option not found where it is expected (for example, new member name for copying member into same PDS). Note: allocation with member name is treated as sequential file.
EDA872 INCOMPATIBLE KEY LENGTHS
This includes: input data set does not have keys, but the output does; both input and output data sets have keys but also have different BLKSIZE or LRECL or RECFM; or input and output key lengths are different and option KEYMOD not specified.
EDA873 OUTPUT ERROR IN
The error shown is one of the following: abend condition and reason codes (S); one flags and two sense bytes describing an error (O); STOW svc (#021) return and reason codes; indication of error writing capacity record for DSORG=DA data set (R0008).
EDA874 INPUT ERROR IN
The error shown is one of the following: abend condition and reason codes (S); or one flag and two sense bytes describing an error (I).
EDA875 TOO LONG INPUT RECORD IN
An input record was found which was longer than the output LRECL, but TRUNCATE option was not specified.
EDA876 COMMAND REJECTED, DATASET IS ALLOCATED TO DDNAME
RENAME/DELETE: free the data set and repeat the command. Other command: either free the data set, or reallocate it as non-SHR to change the shared usage to exclusive (the command does not do this implicitly to prevent locking of the data set).
EDA877 REQUESTED HIPERFOCUS OPTION IS NOT ACTIVE
Allocation with HIPERFOCUS attribute can't be completed: the option is not installed.
EDA878 UNABLE TO ASSIGN REQUESTED HIPERFOCUS ATTRIBUTE
Allocation terminated, most likely, due to temporary lack of resources or inappropriate requester (MSO console or computer operator).
EDA879 %1 WAS RETURN CODE FROM CALLCICS COMMAND
This is an informational reply to the CALLCICS command. It will appear if the application CICS program did not or could not generate a reply. The return code values are documented in the API/SQL Reference Manual.
EDA880 DYNAMIC ALLOCATION ERROR: %1%2%3
The text is the system message for a dynamic allocation error, extracted by IEFDB476. See MVS Authorized Assembler Services Guide.
EDA881 FOLLOWING DDNAME IS NOT AVAILABLE:
Specified DDNAME cannot be allocated, it is already in use.
EDA882 THE NUMBER OF BY FIELDS ON MODIFY SORTHOLD EXCEEDS THE MAXIMUM
For the SORTHOLD subcommand of MODIFY, there is a limit of 8 BY fields.
EDA883 WARNING. DEVICE DOES NOT SUPPORT SAVE FORMAT GRAPH
SAVE FORMAT GRAPH is intended for some devices in order to be used for replotting. In the case of IBM terminals, this option is ignored and the graph is directed to the terminal.
EDA884 CRTFORM TRANSACTION AREA OVERFLOW:
No room is left to create more CRTFORMs.
EDA885 THIS ENVIRONMENT DOES NOT SUPPORT THE USE OF TSO COMMANDS
Some environments, such as CICS, ROSCOE/ETSO, and MSO, do not allow TSO commands to be issued from within FOCUS. If you are executing under TSO, the copy of FOCUS in use may have been installed for one of these other environments.
EDA886 RESERVED FOR USE ON ANOTHER PLATFORM
EDA887 THE DDNAME CANNOT BE USED IN THIS CONTEXT:
The ddname mentioned is probably SYSPRINT, which cannot be used as a LOG file or TYPE file, since it conflicts with regular FOCUS terminal output. Use a different ddname.
EDA888 HOLD FORMAT FOCUS CANNOT BE FOLLOWED BY 'RUN'
HOLD FORMAT FOCUS cannot be followed by the TABLE subcommand RUN in the same TABLE request. (This is not to be confused with the Dialogue Manager -RUN command which may separate TABLE requests.
EDA889 - EDA895 RESERVED FOR USE ON ANOTHER PLATFORM
EDA896 READ OPTION REQUIRED ON USE STATEMENT WITH AS AND ON OPTIONS
Must specify the READ option on a USE statement when using the AS and ON options.
EDA897 HIPERFOCUS USAGE DENIED
The user does not have sufficient access rights to use this option. A rule governing access to HiperFOCUS has failed. Check your installation.
EDA898 HIPERFOCUS USAGE DENIED: RULE ENGINE MASTER MISSING
Rule MFD used for evaluating HIPERULE RULE is missing. Check your installation.
EDA899 INVALID HIPERRULE
A syntax error was discovered while processing rules governing HiperFOCUS usage. Possibly a semicolon was omitted from the end of one of the rules. Access is denied.
EDA900 FOCEXEC LIBRARY %1 EXCEEDS LRECL LIMIT OF %2 (DDNAME=%3)
Maximum record length of a FOCEXEC library cannot exceed the value shown in the message. All libraries within the ddname cannot be accessed.
EDA901 A %1 BYTE LINE IS TOO LONG TO BE WRITTEN TO %2 LIBRARY
Length error: the line cannot be written to the library because its length exceeds the library LRECL. The library must be allocated with an LRECL not less than the length of the line being written.
EDA902 THE %1 LIBRARY %2 MUST HAVE LERCL=80, RECFM=FB (DDNAME=%3)
The dataset has incorrect DCB parameters. All libraries within the ddname cannot be accessed.
EDA903 INVALID %1 LIBRARY CONCATENATION (DDNAME=%22 DSN=%3)
The dataset mentioned in the message is a BPDSE with recfm=V, but it belongs to the concatenated DD where the first dataset has recfm=F. This combination is not allowed. All libraries within the ddname cannot be accessed.
EDA904 - EDA906 RESERVED FOR USE ON ANOTHER PLATFORM
EDA907 ALLOCATION REJECTED, NO SPACE IN MSO DD-TABLE
Overflow of internal MSO DD-table: "local" for MSO user, "global" for MSO console or computer operator. The table space may be obtained by unallocating file(s).
EDA908 ERROR SETTING PASSWORD
An error in setting the password occurred. It could be that the password exceeded 8 characters; or a user has attempted to view the password using the & variable.
EDA909 CRITICAL ERROR IN EXTERNAL SORT. RETURN CODE IS:
A critical return code was issued by the external sort package. Refer to the relevant SORT manual for an explanation.
EDA910 INVALID OR DISABLED KEYWORD %1%2%3
EDA911 INVALID OR MISSING VALUE FOR KEYWORD %1%2%3
EDA912 CONCATENATION FAILED: INVALID NUMBER OF FILES
Total number of files to concatenate must be greater then 1 and less then 17.
EDA913 UNABLE TO FIND DDNAME
EDA914 WARNING: CANNOT FIND HOLDSTAT MASTER OR ERRORS:
The user requested a HOLDSTAT file which cannot be found. If a specific master was requested, it could not be opened at run time. If HOLDSTAT was set ON, see your FOCUS administrator. HOLDSTAT ERRORS should always be available as a default.
EDA915 ERROR GRAPH AND PRINT WITH NO BY/ACROSS, USE LIST INSTEAD
EDA916 CANNOT ACCESS ACE FILE. IT IS LOCKED BY USER:
When an ACE file is changed in TEST, it is registered as locked by that user. Until the file is transferred to PROD, or explicitly unlocked, only that user may make further changes to it. Get the specified user to unlock the file.
EDA917 NUMBER OF FIELDS IN SINGLE JOIN EXPRESSION EXCEEDS 20:
The number of fields connected by the word AND cannot exceed 20. (for example, JOIN F1 AND F2...TO...).
EDA918 ERROR MATCH WITH NO BY PHRASE
For MATCH to work correctly each individual request should have at least one BY phrase associated with a key field.
EDA919 WARNING: SAMPLE SIZE IS INSUFFICIENT FOR THIS ANALYSIS
For accurate statistical measurement, the sample size should be large enough for meaningful results. (for example, DECILES require at least 10 instances or observations of data; QUARTILES require at least 4).
EDA920 EDASORT HAS REACHED ITS PAGE LIMIT
A severe error was encountered in writing to EDASORT EDATEMP. FOCUS will not be able to recover from this error, and will return to the host environment.
EDA921 CRITICAL ERROR IN HIPERFOCUS/EDA. CODE: %1
A severe error was encountered in HiperFOCUS/EDA. It was impossible to recover from this error. Return to the host environment is executed.
EDA922 PROCESSOR DOES NOT SUPPORT MVPG. HIPERFILE/CACHE DISABLED
This processor does not support the move page command or hiper-spaces. HIPERFILE and HIPERCACHE functions are disabled. You may continue with FOCUS.
EDA923 NO FOCUS FILE WAS FOUND UNDER THE NAME:
For a data set to be a FOCUS file, it must have the following structure (RECFM=F|FB; LRECL=4096; BLKSIZE=4096; DSORG=PS).
EDA924 INVALID DATA SET NAME:
A valid data set name should have one or more qualifiers separated by periods. Each qualifier is 1-8 characters. The first character must be alphanumeric, $, # or @, while any other character can be alphanumeric, $, #, @, - or char (HEX'1C').
EDA925 TEXT FIELD/MULTI-VERB REQUESTS ARE NOT SUPPORTED THIS WAY
FOCUS only supports multi-verb requests with text fields if: a) the text field is in the last verb set, or b) the verb set which contains the text field is using BY, and all other subsequent verb sets are SUM requests with the same key set.
EDA926 INCORRECT FORMAT ON RETYPE WITH FIELD REDEFINITION:
When redefining a field on a RETYPE, the field must be specified as field name/format where the field type is the same as the original and the format is valid for that field type.
EDA927 UNKNOWN RECORD LENGTH OF FILE, DDNAME:
An EDAEXEC contains a TABLE request with ACROSS and an IF condition which is not satisfied. Record length of file to SAVE to is unknown. Data set is not created.
EDA928 INVALID CHANGE IN FIELD FORMAT:
In REBUILD you are not allowed to change the field format; you may only change the format width (for example, A10 to A16).
EDA929 CRITICAL ERROR IN HIPERFOCUS. EXTERNAL SECURITY ABEND
A severe error was encountered in HiperFOCUS. The user external security exit returned rc=16. Call system programmer.
EDA930 AN ASTERISK (* CANNOT BE USED WITH ENCRYPT OR DECRYPT
In CMS, specify the file name, file type, and file mode of the file to be encrypted or decrypted. The file type defaults to MASTER, and the file mode defaults to the A disk if not specified. In MVS, the member name and ddname must be specified. The ddname defaults to MASTER.
EDA931 OPTION MAY BE SET ONLY WITH HIPERFOCUS
EDA932 OPTION MAY BE SET ON OR OFF
EDA933 INCORRECT NUMBER OF LINES HAS BEEN SPECIFIED
The next token after -LINES is not an integer number or is out of range 1-500.
The number of lines specified after -LINES is greater than the actual number of lines in the "EX -LINES" command.
EDA934 INCORRECT LENGTH OF U- OR A-VARIABLE
The length specified is not numeric or is out of range 1-32000.
Length of U-var. is greater than the remainder of the command line, or a non-blank character is found between U-var. and the next comma.
Specified length of A-var. is less than the value after = sign.
EDA935 INCORRECT LENGTH OF &-VARIABLE HAS BEEN SPECIFIED
Variable length greater than 255 is allowed only in "EX -LINES..." instruction.
EDA936 THIS FIELD CANNOT BE REFORMATTED BY USING RETYPE:
In order to reformat a field using RETYPE, it must be numeric. A packed field must retain the same number of decimal places, and its width must not cross the 16-digit barrier, either up or down: either P8->P20 or P20->P8 is illegal. Reformat by reDEFINEing.
EDA937 FIELD BASE TYPE CANNOT BE ALTERED IN RETYPE REDEFINITION:
The base type (D, I, ...) of the field in the field redefinition must be the same as the original field.
EDA938 DYNAM COPYDD ERROR. FILE WAS NOT COPIED
EDA939 ACTUAL NOT SPECIFIED FOR FIELD:
All fields in non-FOCUS files must have ACTUAL explicitly specified.
EDA940 MACHINE ARCHITECTURE MODE IS NOT XC. HIPERFILE/CACHE DISABLED.
Hiperfile and hipercache require a XC mode virtual machine in CMS and OS VS/2 in MVS. For hiperfile/cache in CMS, issue: CP SET MACHINE XC and re-IPL CMS.
EDA941 WARNING. ACCESS LIMITED BY PASSWORD
All fields are not available due to limited access.
EDA942 COPY/COMPRESS FAILED, IEBCOPY REQUIRES APF AUTHORIZATION
DYNAM is unable to invoke IEBCOPY because it requires APF authorization (or abend S172 occurs). For DYNAM COPY, this may happen only if the whole PDS is to be copied, or a selected member's directory entry contains TTRN data.
EDA943 JOB CANCELED BY SUBMIT, REASON CODE %1
This message appears as a comment in job output if MSGLEVEL permits. Reasons: 0- external request (for example, source error); 2- error writing in INTRDR; 3- user exit's request or error; 4- error in "DLM=" operand (termination on this error may be suppressed).
EDA944 SUBMIT TERMINATED DUE TO USER EXIT, REASON CODE
Reasons: 0- supervisor state requirement not suppressed but SUBMIT runs unauthorized; 4- unable to load exit (IKJEFF10); 8- unable to issue exit's message; 12- unable to issue exit's prompt; 16- exit requested the termination; other- invalid exit's return code.
EDA945 SUBMIT TERMINATED DUE TO IN-STREAM DATA SET ERROR
Most likely, 'DLM=' operand is invalid. There is the possibility the system starts to execute JCL statements from the in-stream data set. The message (and action may be suppressed by zapping SUBMIT options.
EDA946 MORE THAN 16 INCONSISTENT MATCH SORT SETS.
A consistent match sort set is a set of sort keys that has all or part of the earliest key set in the whole MATCH request while reserving the order of the keys, and can not exceed the last consistent key set if an inconsistent key set occurs at anytime.
EDA947 CONFLICTING SPECIFICATION OF %1%2%3
Either the named parameter is specified more than once, or it is mutually exclusive with another parameter.
EDA948 INVALID OR MISSING SPECIFICATION OF %1%2%3
Either the named parameter has incorrect value, or it is required but not specified.
EDA949 THE NUMBER OF SORT FIELDS EXCEEDS THE MAXIMUM:
A total of 32+number of common BY fields-number of PRINT (LIST) verbs-number of no BY verbs BY phrases can be used in a MATCH request at one time. Common BY fields are any subsequence of the largest consistent MATCH sort key set.
EDA950 INVALID REFORMAT OPTION WITH COUNT OR CNT. :
When using a COUNT verb or the prefix CNT. with verb object(s), REFORMATTING is allowed only with I FORMAT.
EDA951 LARGE FOCUS DATABASE IS NOT SUPPORTED IN THIS RELEASE OF FOCUS
In FOCUS Release 7.0, an FOCUS database can exceed 65536 pages. A large FOCUS database created in Release 7.0 cannot be accessed from a previous release.
EDA952 NO MATCH IS FOUND FOR THE FIELD OF MAIN REQUEST:
Can't find match for one or more field(s).
EDA953 INVALID STRUCTURE IN SUBREQUEST:
Only "if" and "where" clauses are allowed in the subrequest.
EDA954 UNIVERSAL CONCATENATION DOES NOT SUPPORT:
EDA955 THE FIELD DOESN'T HAVE A UNIQUE FLDNAM, OR ALIAS:
The field specified exists more than once in the logical database structure. It is possible that a JOIN is in effect and both files have the same field name and alias.
EDA956 THE ASNAME IS NOT UNIQUE:
EDA957 FORMAT MISMATCH FOR THE FIELD:
The format of the field doesn't match the corresponding field format in the main request.
EDA958 ATTEMPT TO USE ONLINE COMMAND IN BATCH MODE FAILED
In batch mode, online commands like CRTFORM or -CRTFORM cannot be performed.
EDA959 NO FILENAME SPECIFIED FOR TED.
You have typed TED without specifying a file name or previously executing an EDAEXEC.
EDA960 WARNING. QUALIFIED FIELDNAME IS NOT PERMITTED:
A qualified field name may not be used on the left-hand side of a COMPUTE or DEFINE. Use the REDEFINES option to specify a field that will redefine or recompute a qualified field name.
EDA961 INVALID DATE INPUT IN REBUILD TIME:
EDA962 FILE IS NOT WRITABLE:
EDA963 ONLY SET COMMANDS ALLOWED IN FOCUS EDAPARM FILE:
EDA964 THIS SET OPTION ONLY ALLOWED IN FOCUS EDAPARM FILE:
EDA965 VALID VALUES ARE SORTLIB=VMSORT/SYNCSORT/DFSORT/SITEDEFINED
Specify SORTLIB for one of the known sort packages. Each site may specify an unknown sort package using the SITEDEFINED parm. Refer to Installation guide for nonstandard sorts.
EDA966 MASTER FILE OF THIS FOCUS FILE IS NOT FOUND
EDA967 DATA SET NOT ALLOCATED/BAD ALLOCATION
TSO IEDIT: error happened while allocating the data set to be edited. Check data set name, ddname, DYNAMNBR parameter in logon procedure.
EDA968 INVALID MEMBER NAME
TSO IEDIT: Syntax error in member name operand.
EDA969 INVALID DDNAME
TSO IEDIT: Syntax error in ddname operand.
EDA970 EXTERNAL INDEX SYNTAX ERROR: CONFLICTING OPTIONS
External index syntax does not support following USE command options: NEW, READ, ON, LOCAL, AS master ON userid READ.
EDA971 EXTERNAL INDEX SYNTAX ERROR: ILLEGAL DDNAME
Key word WITH must be followed by a valid DDNAME, whose length is greater than 0 and less than or equal to 8 characters.
EDA972 EXTERNAL INDEX ERROR: MORE THAN 8 INDICES IN USE
There can be a maximum of 8 external indices in USE.
EDA973 EXTERNAL INDEX INVALID CONFIGURATION:
Not all components used to build concatenated external index are in use at this time, or the USE directory contains the extra components. It is not safe to use this index.
EDA974 EXTERNAL INDEX ERROR: INVALID TARGET SEGMENT
The target segment for the external index is invalid. Real database fields cannot have a target segment different from the location segment.
EDA975 EXTERNAL INTERNAL ERROR: %1
EDA976 EXTERNAL INDEX EXPIRED:
One of the component databases was updated after the index was generated. It is not safe to use the index under these conditions.
EDA977 EXTERNAL INDEXES CANNOT BE CREATED FOR NON-FOCUS FILES
External indexes may only be created for files with SUFFIX=EDA.
EDA978 LRECL EXCEEDS THE MAXIMUM OF 1024 FOR DECODE
The input file for decode exceeds the maximum LRECL of 1024.
EDA979 WARNING: FOLD-LINE OPTION IS IGNORED WITH ACROSS
The FOLD-LINE option cannot be executed with ACROSS in a TABLE request unless it is used with BY objects.
EDA980 INVALID RECFM OR LRECL ON FILEDEF FOR IMPORT DATABASE:
To IMPORT a database, you must first issue a FILEDEF for the database file, with a LRECL of 4096 and a RECFM of F. Check the FILEDEF command.
EDA981 SEVERE ISPF ERROR: %1 %2
TSO IEDIT: Severe ISPF error occurred; IEDIT cannot proceed. Refer to ISPF documentation for more information about specific ISPF error messages.
EDA983 Failure with external sort; SORTLIB was set to %1
FOCUS or EDA has experienced a problem relating to an external sort, and the session will soon terminate; SET option SORTLIB has the value shown. (This message always appears together with another message that describes the reason for the failure.)
EDA984 DFSORT needs DDname SYSOUT to display messages
FOCUS or EDA invoked DFSORT; DFSORT tried to display a message to DDname SYSOUT, but found no such DDname. Supply a DD statement for SYSOUT and retry. (This should happen only when the bvalue of SORTLIB is MVSMSGDF and only on MVS or MVS/OE...see EDA983
EDA985 DD %1, SPILL DD: %2; ERROR WHILE %3, CODE %4
An error occurred during the read/write operation for spilled hiperfile. The code explanation is the same as for EDA198 message.
EDA986 %1
This is a standard MVS system I/O error message. The format is similar to IEC020I message.
EDA987 INVALID DATA SET
TSO IEDIT: "ddname (member)" specified but file is sequential; or DD is allocated and the file does not exist; or the file is PDS, but the member name is not specified.
EDA988 NO FILE SPECIFIED BUT CURRENT EDAEXEC NOT KNOWN
TSO IEDIT: You entered the TSO IEDIT command without operands, but there is no last executed EDAexec. Reenter the TSO IEDIT command and specify the file to be edited.
EDA989 ERROR DURING FREEING OF FILE
TSO IEDIT: An error occurred while freeing the data set just edited.
EDA990 ISPF NOT FOUND, TSO IEDIT CANNOT PROCEED
TSO IEDIT: You issued the "TSO IEDIT" command, but there is no ISPF program in your environment.
EDA991 SYNTAX ERROR IN COMMAND
TSO IEDIT: Syntax error in command; probably the string specified is too long.
EDA992 INVALID RECORD LENGTH
TSO IEDIT: Record length is greater than 160, or both lrecl and blksize are 0. (You may have tried to "iedit" an empty or preempted record from a previously run Hiperfile).
EDA993 UNIVERSAL CONCATENATION IS NOT SUPPORTED FOR TABLEF
EDA994 EXTERNAL INDEX ERROR: MORE THAN %1 COMPONENTS
There is a limit to the number of partitions that may be indexed.
EDA995 ERROR. EXTERNAL INDEX DUPLICATE COMPONENT: %1
The same component database is used twice.
EDA996 EXTERNAL INDEX ERROR: INDEX DATABASE NOT IN USE
Add option in an external index build requires that the existing index database be placed in use before the rebuild process.
EDA997 EMGFILE DDNAME NOT ALLOCATED
The setting EMGSRV=FILE was attempted, but there was no allocation for the DDNAME "EMGFILE." The setting is ignored.
EDA998 EMGFILE CANNOT BE OPENED FOR WRITE
The setting EMGSRV=FILE was attempted, and the DDNAME "EMGFILE" was allocated, but it could not be opened for write. The setting is ignored.
EDA999 ERROR. EXTERNAL INDEX COMPONENT REUSED: %1
An attempt is made to add data to an external index from a database that was previously used as a component.
EDA1000 INVALID USE OF CROSS REFERENCE FIELD: %1
Cross-reference fields may only be used as an external index if they are associated with a real database field. An external index cannot be associated with a cross-reference field.
EDA1001 ACCESS NOT SUPPORTED. CHECK SUFFIX IN THE MASTER %1%2%3%4
The ACCESS method for the file is not supported by FOCUS. The SUFFIX parameter in the Master File Description must specify VSAM, ISAM, FIX, COM, or XFOC.
EDA1002 LASTFLD IS NOT A VALID FOCUS FIELD NAME %1%2%3%4
LASTFLD is a reserved word in FOCUS.
EDA1003 OCCURS VALUE NOT A FOCUS FIELDNAME OR VALID CONSTANT %1%2%3%4
The OCCURS value specified for the repeating group in the Master File Description is not a valid number, or the field name identified does not exist.
EDA1004 POSTNFLD NOT A VALID FOCUS FIELDNAME %1%2%3%4
POSTNFLD is a FOCUS reserved word.
EDA1005 POSTNFLD NOT IN PARENT SEGMENT %1%2%3%4
EDA1006 THE DDNAME REQUESTED IS NOT ALLOCATED OR DLBL'ED %1%2%3%4
The VSAM file or Alternate Index specified by the Master File Description has not been allocated.
EDA1007 RECTYPE CANNOT EXCEED 12 CHARACTERS %1%2%3%4
The ACTUAL length for a RECTYPE field cannot exceed 12 bytes.
EDA1008 RECTYPE FIELD NOT SPECIFIED FOR SEGMENT %1%2%3%4
More than one segment is described for the file and no RECTYPE field was defined to identify the different record layouts.
EDA1009 DIFFERENT RECTYPE FORMATS %1%2%3%4
All RECTYPE fields described in the Master File Description must have the same ACTUAL and USAGE formats.
EDA1010 DIFFERENT RECTYPE POSITIONS %1%2%3%4
All RECTYPE fields described in the Master File Description must start at the same relative position within the record.
EDA1011 DIFFERENT RECTYPE LENGTHS %1%2%3%4
All RECTYPE fields described in the Master File Description must have the same USAGE and ACTUAL formats and lengths.
EDA1012 KEYFIELD NOT A VALID FOCUS FIELD NAME %1%2%3%4
The field identified as the key to the file does not have a valid FOCUS field name.
EDA1013 KEYFIELD USAGE AND ACTUAL FORMATS NOT THE SAME %1%2%3%4
The ACTUAL and USAGE format types for the KEY field must be the same. If the SUFFIX is ISAM or VSAM, the KEY must be described as a GROUP field with alpha formats.
EDA1014 KEYFIELD ACTUAL LENGTH EXCEEDS USAGE LENGTH %1%2%3%4
The ACTUAL length of the KEY field cannot exceed the USAGE length.
EDA1015 KEYFIELD NOT IN ACCESSED PARENT SEGMENT %1%2%3%4
EDA1016 INVALID KEY DESCRIPTION IN MASTER FILE - %1%2%3%4
EDA1017 ORDER OR MAPVALUE SHOULD BE THE LAST FIELD IN SEG = %1%2%3%4
EDA1018 PARENT OF GIVEN SEGMENT SHOULD BE MAPFIELD TYPE - %1%2%3%4
EDA1019 OCCURS=FIELDNAME USAGE FORMAT HAS TO BE I4 %1%2%3%4
EDA1020 OCCURS WITH POSITION HAVE NONE POSITION CHILD %1%2%3%4
If a segment has a POSITION attribute then all its descendants must be positional as well.
EDA1021 KEY SHOULD BE A GROUP %1%2%3%4
EDA1022 INVALID DUMMY KEY DESCRIPTION IN MASTER FILE - %1%2%3%4
EDA1023 INVALID SEGMENT NUMBER FOR OPERATION %1%2%3%4
The message may be received during SQL STATIC compile if the compiled MODIFY procedure exceeds certain internal static interface limitations. Such procedures can only by executed dynamically or compiled and run without the STATIC option.
EDA1024 INVALID OCCURS FIELD VALUE %1%2%3%4
The value of an OCCURS field must be less than or equal to 4096.
EDA1025 RESERVED FOR FOCSAM %1%2%3%4
EDA1026 OCCURS ACCESS NOT VALID FOR ROOT SEGMENT %1%2%3%4
The root or first segment cannot be an occurs segment.
EDA1027 FIXED OCCURS SEGMENT FOLLOWS VARIABLE OCCURS SEGMENT %1%2%3%4
A fixed occurs segment cannot be described following a varying occurs segment. If used, the fixed occurs segment must be described as the first child segment chain.
EDA1028 THIS TYPE OF RECURSIVE JOIN IN NOT SUPPORTED %1%2%3%4
EDA1029 THE ROOT SEGMENT CANNOT BE AN OCCURS SEGMENT %1%2%3%4
The root or first segment in the file cannot be an occurs segment.
EDA1030 FIRST SEGMENT IN THE MASTER FILE MUST HAVE NAME 'ROOT' %1%2%3%4
The first segment in a VSAM or ISAM Master File Description must have the segment name ROOT.
EDA1031 VSAM KEYS MUST BE IN THE SAME POSITIONS IN ALL SEGMENTS %1%2%3%4
All group fields with ALIAS=KEY identify the VSAM record key. They must start at the same relative position in every segment of the Master File Description.
EDA1032 RECTYPE LENGTH MUST BE LESS THAN OR EQUAL TO 12 BYTES %1%2%3%4
The ACTUAL length of a RECTYPE field cannot exceed 12 bytes.
EDA1033 RECTYPES MUST HAVE THE SAME LENGTH IN ALL SEGMENTS %1%2%3%4
All RECTYPE fields described in the Master File Description must have the same ACTUAL format and length.
EDA1034 RECTYPES MUST BE IN THE SAME RELATIVE POSITION IN ALL SEGMENTS
All RECTYPE fields described in Master File Description must start at the same relative position within the record.
EDA1035 MULTI-PATH FILE NON-OCCURS SEGMENTS MUST HAVE RECTYPE FIELDS
If the Master File Description contains more than one segment, then each segment without an OCCURS attribute must have a RECTYPE field.
EDA1036 THE FILE MUST HAVE AT LEAST ONE NON-OCCURS SEGMENT %1%2%3%4
The Master File Description must contain at least one segment without an OCCURS attribute.
EDA1037 MULTI-PATH FILE MUST HAVE RECTYPE FIELDS %1%2%3%4
A file that contains more than one non-occurring segment type MUST define a RECTYPE field in each segment to identify the record layout.
EDA1038 LENGTH OF THE KEY MAY NOT EXCEED 80 BYTES %1%2%3%4
A key field cannot exceed 80 bytes in length.
EDA1039 JOIN 'TO' SEGMENT NOT REFERENCED %1%2%3%4
The TABLE request must reference at least one field in the cross-reference segment.
EDA1040 JOIN 'TO' FIELD IS NOT IN THE BEGINNING OF THE KEY %1%2%3%4
An error occurred when joining the file allocated to the specified ddname. The field name identified was used in a JOIN command and is not a key field; alternate index or its initial subset.
EDA1041 INVALID FORMAT COMBINATION OF 'FROM' AND 'TO' FIELDS %1%2%3%4
The USAGE format of the FROM fie1d used in the JOIN command must be the same as the ACTUAL format of the TO field.
EDA1042 LENGTHS OF 'FROM' AND 'TO' FIELDS MUST BE EQUAL %1%2%3%4
If the file has SUFFIX=FIX, the USAGE length of the FROM field and the ACTUAL length of the TO field used in a JOIN must be the same.
EDA1043 INVALID COMBINATION OF 'TO' FIELD FORMATS %1%2%3%4
The USAGE and ACTUAL formats of the TO field used in the JOIN must be the same.
EDA1044 INVALID COMBINATION OF THE FIELD LENGTHS IN JOIN %1%2%3%4
EDA1045 UNIQUE JOIN MUST BE DONE TO FULL PRIMARY KEY %1%2%3%4
A one-to-one unique JOIN must be done to the full primary key. If a partial key is used, JOIN TO ALL syntax must be invoked.
EDA1046 INAPPROPRIATE USE OF ALL OPTION IN JOIN COMMAND %1%2%3%4
The full key of alternate index was used as the TO field in the JOIN command.
EDA1047 ERROR IN ENTRY SEGMENT RETRIEVAL %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS Message with additional information.
EDA1048 ERROR IN REPOSITIONING %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS Message with additional information.
EDA1049 ERROR IN READING NEXT RECORD %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information.
EDA1050 ERROR IN DIRECT RETRIEVAL OF INVERTED SEGMENT %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information.
EDA1051 ERROR IN SEQUENTIAL RETRIEVAL OF INVERTED SEGMENT %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information.
EDA1052 ERROR IN INITIAL POSITIONING %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information.
EDA1053 KEY LENGTH OF CHILD SEGMENT MUST BE LONGER THAN THAT OF PARENT
The key length of a child segment must be greater than the key length of its parent for RECTYPE processing.
EDA1054 KEY LENGTH OF CHILD SEGMENT MUST BE LONGER THAN THAT OF PARENT
The key length of the parent of inverted segment is less than or equal to the key length of the segment itself.
EDA1055 ADDITIONAL MEMORY IS NEEDED FOR RECORD WORK SPACE %1%2%3%4
You do not have enough virtual memory for the VSAM read/write interface. Increase your region or virtual machine size.
EDA1056 THE DYNAMIC ROOT OF A JOIN MAY NOT BE AN OCCURS SEGMENT %1%2%3%4
The FROM field in a JOIN command cannot belong to an occurs clause.
EDA1057 MORE THAN ONE PRIMARY KEY IS DEFINED IN A SINGLE SEGMENT %1%2%3%4
There is more than one GROUP field with ALIAS=KEY in one of the segments of the Master File Description.
EDA1058 READ NEXT ERROR %1%2%3%4
EDA1059 VSAM ENTRY-SEQUENCED OR FIXED FILES CANNOT BE INVERTED %1%2%3%4
A file view or JOIN which results in a file inversion cannot be used for FIX or VSAM/ESDS files.
EDA1060 RECTYPE MAY NOT BE IN THE LEFT PORTION OF THE KEY %1%2%3%4
The RECTYPE field cannot be the first part of the key field in a multi-segment hierarchical file.
EDA1061 ENTRY SEGMENT RETRIEVAL ERROR %1%2%3%4
EDA1062 OCCURS=VARIABLE SEGMENT MAY NOT HAVE OCCURS PARENT/TWIN %1%2%3%4
An OCCURS=VARIABLE segment must be described as the right most segment for that level in the structure. It can have twins to the left. The OCCURS=VARIABLE segment MUST have a non-occurs segment for its parent.
EDA1063 ERROR IN SEQUENTIAL RETRIEVAL OF DUPLICATES %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information.
EDA1064 ERROR IN DIRECT RETRIEVAL OF DUPLICATES %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information.
EDA1065 PROGRAM ERROR %1%2%3%4
Contact your iWay representative.
EDA1066 VSAM OPEN ERROR %1%2%3%4
An error occurred while trying to open the VSAM file specified. Possible causes are: JCL error; catalog not allocated; wrong data set name; file was not properly closed by another application; or file is being updated by another system.
EDA1067 VSAM RETRIEVAL ERROR %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information. Refer to the appropriate system manual and make corrections as needed.
EDA1068 ERROR IN SEQUENTIAL RETRIEVAL %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information. Refer to the appropriate system manual and make corrections as needed.
EDA1069 ERROR IN DIRECT RETRIEVAL %1%2%3%4
This message is displayed after an I/O error occurs. It is preceded by another FOCUS message with additional information. Refer to the appropriate system manual and make corrections as needed.
EDA1070 VALUE FOR JOIN 'FROM' FIELD OUT OF SEQUENCE. RETRIEVAL ENDED
The FROM field used in a JOIN command must be sorted in ascending sequence within the file if it is joined to a FIX, COM or VSAM/ESDS file.
EDA1071 VALUE FOR JOIN 'TO' FIELD OUT OF SEQUENCE. RETRIEVAL ENDED
The TO field used in a JOIN command must be sorted in ascending sequence if the TO file is a FIX, COM or VSAM/ESDS file.
EDA1072 DUPLICATES IN JOIN 'FROM' FIELD %1%2%3%4
Duplicates in the FROM field are not allowed if the JOIN is to a FIX, COM or VSAM/ESDS file and the 'TO' file has more than one non-occurs segment.
EDA1073 JOIN 'FROM' AND 'TO' FIELDS MUST HAVE EQUAL LENGTHS %1%2%3%4
EDA1074 INVALID SUFFIX %1%2%3%4
The SUFFIX parameter in the Master File Description must be FIX, COM, VSAM or ISAM.
EDA1075 INVALID USE OF ALL OPTION IN JOIN COMMAND %1%2%3%4
EDA1076 - EDA1078 ORPHAN SEGMENT IN FILE %1%2%3%4
EDA1079 RECTYPES MUST HAVE THE SAME USAGE AND ACTUAL FORMATS %1%2%3%4
The USAGE and ACTUAL formats of all RECTYPE fields must be the same. Alpha, integer, and packed formats are supported.
EDA1080 RECTYPE ALIAS VALUE AND ACTUAL FORMAT ARE INCONSISTENT %1%2%3%4
The RECTYPE field has a numeric ACTUAL format but the value of the ALIAS is not numeric.
EDA1081 LOGICAL ERROR READING VSAM FILE %1%2%3%4
A possible JCL or Master File Description error has occurred. 072 (hex '48') File with described keys is allocated to an ESDS cluster. 200 (hex 'C8') File without described keys is allocated to a path or KSDS cluster instead of an ESDS cluster.
EDA1082 PHYSICAL ERROR READING VSAM FILE %1%2%3%4
A low-level I/O error occurred while reading the VSAM file. Refer to the appropriate system manual and make corrections as needed.
EDA1083 THE RECORD LENGTH IS LARGER THAN THE MAXIMUM SPECIFIED %1%2%3%4
The actual record length shown in hex is larger than the buffer allocated by the FOCSAM interface. Use SET MAXRECL= to increase the default buffer size. Otherwise, the segment occurrence you are trying to insert will cause the file to exceed its VSAM defined length.
EDA1084 ONLY ONE RETRIEVAL PATH IS AVAILABLE FOR ALTERNATE INDEX VIEW
If a VSAM file is accessed via an alternate index, all fields referenced in the request must be in the segment of OCCURS descendents of the segment whose index is used.
EDA1085 DUMMY RECTYPE SEGMENT MUST BE THE ROOT SEGMENT ONLY %1%2%3%4
If a DUMMY segment is used, it must always be the root segment in the Master File Description.
EDA1086 DUMMY RECTYPE SEGMENT MUST HAVE ONE FIELD %1%2%3%4
The DUMMY segment must have only one field. The FIELDNAME and ALIAS must be blank. This field cannot be referred to in any way.
EDA1087 FILE MUST HAVE PROPERLY DESCRIBED KEYS %1%2%3%4
The key in an ISAM or VSAM file must always be described as a GROUP field with ALIAS=KEY.
EDA1088 OCCURS COUNTER NOT IN ROOT PATH FOR SEGMENT %1%2%3%4
The field referred to in the OCCURS = field name parameter must be in the parent or a higher level ancestor of the OCCURS segment.
EDA1089 XMI EXTENSION GENCB ACB ERROR %1%2%3%4
An internal VSAM error has occurred. Refer to a VSAM manual for the specified code.
EDA1090 XMI EXTENSION GENCB RPL ERROR %1%2%3%4
An internal VSAM error has occurred. Refer to a VSAM manual for the specified code.
EDA1091 RECTYPE FIELD LENGTH MUST BE 12 CHARACTERS OR LESS %1%2%3%4
The ACTUAL format of any RECTYPE field used in the Master File Description must be less than or equal to 12 characters in length.
EDA1092 ERROR TRANSLATING RECTYPE GIVEN IN MASTER TO INTERNAL FORMAT
An error occurred while converting the RECTYPE field from its ACTUAL to USAGE format. Change to formats to A, I, or P.
EDA1093 RECTYPE FORMAT MUST BE A, I, OR P %1%2%3%4
The ACTUAL and USAGE formats of a RECTYPE field must be alpha, integer or packed. Change the description and try to report again.
EDA1094 CHILDREN HAVE NON-MATCHING RECTYPE FIELD LENGTHS %1%2%3%4
The ACTUAL format of the RECTYPE field must be the same length in each reference belonging to the same parent.
EDA1095 CHILDREN HAVE NON-MATCHING RECTYPE FIELD FORMATS %1%2%3%4
The RECTYPE field must have the same ACTUAL format in each reference within the file.
EDA1096 RECTYPE SEGMENT MUST HAVE NON-RECTYPE, NON-OCCURS PARENT %1%2%3%4
A segment which contains a RECTYPE field must be the descendent of a non-RECTYPE segment. In addition, it cannot be the descendant of a segment that specifies OCCURS= as a segment attribute.
EDA1097 THERE IS MORE THAN ONE RECTYPE FIELD IN A SINGLE FORMAT %1%2%3%4
Only one RECTYPE field can be defined in a segment.
EDA1098 ACTUAL FORMAT OF AN OCCURS COUNTER FIELD MUST BE 12 %1%2%3%4
EDA1099 ACTUAL FORMAT OF AN ORDER FIELD MUST BE 14 %1%2%3%4
The ORDER field is a reserved word used as an ALIAS to identify position in an array. The ACTUAL format of the ORDER field must be I4. Correct the Master File Description.
EDA1100 OCCURS=VARIABLE HAS A MISNAMED OR MISPLACED COUNT FIELD %1%2%3%4
EDA1101 THIS INTERFACE DOES NOT SUPPORT THE GLOBAL JOIN %1%2%3%4
The JOIN command does not support the external files you are attempting to join together.
EDA1102 ONLY JOIN 'TO' SEGMENT MAY BE REFERENCED IN FOCUS FILE %1%2%3%4
When joining to a FOCUS database, you can only reference fields in the segment to which you joined. This applies up to FOCUS Release 5.5.
EDA1103 FOCUS SEGMENT CANNOT BE THE ROOT IN A GLOBAL JOIN %1%2%3%4
A FOCUS database cannot be the 'FROMI' file in a JOIN command. This applies up to FOCUS Release 5.0.4.
EDA1104 GATEWAY USERID IS NOT RUNNING OR IS INOPERABLE %1%2%3%4
You are attempting to use an XMI interface and the GATEWAY userid is not running or is inoperable. Contact your FOCUS coordinator.
EDA1105 ERROR SENDING XMI MESSAGE %1%2%3%4
An error occurred sending a message from the XMI target job. Contact your systems department.
EDA1106 ERROR RECEIVING XMI MESSAGE %1%2%3%4
An error occurred receiving a message from the XMI target job. Contact your systems department.
EDA1107 XMI EXTENSION JOB HAS NO ALLOCATION FOR FILE %1%2%3%4
The XMI target job running under either VSE or MVS does not have an allocation statement for the file in your request.
EDA1108 XMI EXTENSION JOB ATTEMPTS TO ALLOCATE NON-EXISTING FILE %1%2%3%4
The XMI target job running under either VSE or MVS allocates a nonexisting file. Check the data set name and resubmit.
EDA1109 DATA IS NOT PRESENT FOR FOCUS FILE %1%2%3%4
No data exists for the specified FOCUS database.
EDA1110 ATTEMPT TO DELETE,UPDATE OR INCLUDE NON-WRITABLE SEGMENT %1%2%3%4
EDA1111 PARENT WAS NOT RETRIEVED OR INCLUDED %1%2%3%4
A MATCH logic error has occurred. There was an attempt to retrieve a record without mentioning the intervening segment.
EDA1112 CONTROL COMMAND EXCEEDS THE MAXIMUM LENGTH %1%2%3%4
Internal programming error.
EDA1113 INVALID CONTROL COMMAND %1%2%3%4
Internal programming error.
EDA1114 FORMAT ERROR IN VSAM COMMAND %1%2%3%4
Internal programming error.
EDA1115 PARENT WASN'T RETRIEVED OR INCLUDED %1%2%3%4
An error occurred while updating the file. An attempt was made to modify a child segment without matching or including the parent segment first.
EDA1116 INVALID COUNTER FIELD %1%2%3%4
The field specified in the OCCURS attribute is invalid. Check the Master File Description for correct spelling and field format.
EDA1117 MISSING KEYFIELD OR OCCURS ATTRIBUTE %1%2%3%4
The Master File Description is in error. Either the VSAM key has been omitted, or there is a segment which is missing an OCCURS attribute.
EDA1118 DIFFERENT ALT KEYS REFERENCED WITH THE SAME ALT VIEW %1%2%3%4
More than one alternate index was specified in the request.
EDA1119 RESERVED FOR VSAM %1%2%3%4
EDA1120 FORMAT CONVERSION ERROR FIELD/SEGMENT %1%2%3%4
An error occurred attempting to convert the specified field from its ACTUAL to USAGE format. The ACTUAL format is described incorrectly. Check the Master File Description.
EDA1121 ATTEMPT WAS MADE TO INCLUDE A DUPLICATE KEY
An attempt was made to INCLUDE a duplicate key value into the VSAM file. The transaction has been rejected.
EDA1122 DIRECT WRITE ERROR %1%2%3%4
An error occurred while attempting to update a VSAM file. Look up the return code in the appropriate VSAM messages and codes manual and make corrections as needed.
EDA1123 SEQUENTIAL WRITE ERROR %1%2%3%4
An error occurred while attempting to update a VSAM file. Look up the return code in the appropriate VSAM messages and codes manual and make corrections as needed.
EDA1124 NO DASD SPACE AVAILABLE %1%2%3%4
An out of space condition occurred while attempting to update a VSAM file. Contact your system programmer.
EDA1125 UPDATE OF VSAM KEY OR OCCURS COUNTER FIELD NOT ALLOWED %1%2%3%4
An attempt was made to UPDATE a VSAM key field, which is prohibited. You must delete and re-add the record to accomplish this. 2) An attempt was made to UPDATE an OCCURS counter field, which is prohibited. FOCUS updates automatically.
EDA1126 ATTEMPT TO INCLUDE THIS RECORD WILL EXCEED MAXIMUM RECORDSIZE
You are trying to insert a segment occurrence that causes the file to exceed its VSAM defined length.
EDA1127 SEGTYPE MUST BE SO FOR UMF %1%2%3%4
The Master File Description must have SEGTYPE=SO when using the VSAM read/write interface.
EDA1128 INCLUDE OR DELETE INVALID FOR OCCURS=N SEGMENTS. USE UPDATE
You cannot INCLUDE or DELETE any OCCURS=N segment. You can only UPDATE these segments.
EDA1129 VSAM ERROR %1%2%3%4
This message is always used in conjunction with another messages. Its primary purpose is to display the VSAM error code that has been generated. See the appropriate VSAM messages and codes manual.
EDA1130 FORMAT CONVERSION ERROR FIELD/KEY %1%2%3%4
An error occurred attempting to convert the specified field from its ACTUAL to USAGE format. Either the ACTUAL format is described incorrectly or the data may be invalid. Check the MFD.
EDA1131 INVALID FIELDNAME %1 FOR %2. %3 LN %4
A record in a multi-segment AFD contains a KEYFLD reference to a field that does not exist in its parent segment, or IXFLD/FKEY reference a field that does not exist in the segment. Check the corresponding Master File Description and enter the correct reference in the Access File Description.
EDA1132 INSUFFICIENT STORAGE. %1.%2 %3 LN %4
EDA1133 INTERNAL ERROR IN DATA CONVERSION ROUTINES %1%2%3%4
EDA1134 RECORD TOO LONG OR INCOMPLETE %1.%2 %3 LN %4
An AFD record was too large to fit into the parser buffer. Since the AFD parser allows reasonable amounts of temporary storage for buffering, the most probable reasons are either a missed logical record ending ($) or large blank gaps within the record.
EDA1135 INVALID KEYWORD %1.%2 %3 LN %4
The keyword has not been found in the parsing table, so it is not a documented Access File keyword for this type of interface. Check the spelling of the keyword and make sure the correct delimiters are used. Make necessary corrections.
EDA1136 TOO LONG VALUE %1 FOR %2. %3 LN %4
The token that follows the keyword is too long for that keyword. For example, the SEGNAME keyword value cannot exceed 66 characters.
EDA1137 DUPLICATE KEYWORDS %1.%2 %3 LN %4
Two identical keywords were found within the same Access File Description record. One of the probable reasons could be an omitted $ delimiter between AFD records.
EDA1138 RECORD DOES NOT START WITH A KEYWORD '%1'.%2 %3 LN %4
An Access File Description record must start with a keyword like: SEGNAME = name. This keyword determines the type of the AFD record. Positional values may be used for subsequent parameters though the use of keywords is strongly recommended.
EDA1139 NO VALUE SPECIFIED FOR KEYWORD %1.%2 %3 LN %4
A syntax error found in an Access File Description. No value (even an empty one) was specified for a keyword (like KEYS=WRITE=.). The message supplies the keyword and AFD line number where the error is encountered.
EDA1140 MISUSE OF QUOTATION MARKS IN KEYWORD %1 VALUE %2. %3 LN %4
A keyword value in quotation marks was found syntactically incorrect; the closing quotation mark was not found in the proper place. Non-duplicated embedded quotation marks are the most probable reason for this.
EDA1141 NO DEFAULT KEYWORD FOR VALUE %1.%2 %3 LN %4
A positional value in an Access File Description record could not be associated with any default keyword. Avoid coding positional parameters in AFD. AFD records should be pairs of tokens and values (keyword = value), and should be terminated with a $.
EDA1142 KEYWORD %1 INVALID IN THE CONTEXT.%2 %3 LN %4
A keyword in an Access File Description record is not supposed to be used in this particular type of record. The first keyword of an AFD record determines its type. Then, for instance, the FIELD keyword is invalid in a record beginning with "SEGNAME = ... ".
EDA1143 PRIVATE ACCESS SUBROUTINES ERROR %1%2 %3 LN %4
EDA1144 KEYWORD %1 IS MISSING %2 %3 LN %4
Keyword is required but not specified. For example, a segment description in the AFD is missing the KEYFLD/IXFLD/PKEY/FKEY/REFERENCE parameter. A segment description in an AFD must have matching definitions for KEYFLD/IXFLD and PKEY/FKEY/REFERENCE groups of parameters.
EDA1145 PARSE FAIL FOR %1=%2. %3 LN %4
Cannot parse value for KEYFLD/IXFLD/PKEY/FKEY.
EDA1146 %1 AND %2 HAVE UNEQUAL NUMBER OF COMPONENTS. %3 LN %4
The KEYFLD/IXFLD or PKEY/FKEY references for a table in a multi-table Access File Description do not contain the same number of component columns. Check the corresponding Master File Description and enter the correct references.
EDA1147 NTTRACE ERROR %1%2%3%4
EDA1148 FROM AND TO ARE DIFFERENT SIZED GROUPS %1%2%3%4
EDA1149 INVALID LENGTH ALIGNMENT FOR FROM/TO FIELDS IN A JOIN %1%2%3%4
EDA1150 ZCOMP DECOMPRESS ERROR %1%2%3%4
EDA1151 MORE BUFFER SPACE FOR ZCOMP1 - SET MAXLRECL %1%2%3%4
EDA1152 - EDA1154 reserved for zcomp exit error %1%2%3%4
EDA1155 RECORD > 8K IS SENT THROUGH XMI; SOME DATA MAY BE LOST %1%2%3%4
Truncation might have occurred and some data could be lost.
EDA1156 XMI MEMORY ERRROR %1%2%3%4
EDA1157 XMI LOAD ERROR %1%2%3%4
EDA1158 XMI SINK ALLOCATION ERROR %1%2%3%4
EDA1159 XMI IOPEN ERROR %1%2%3%4
EDA1160 XMI IENQUE ERROR %1%2%3%4
EDA1161 XMI IPUT ERROR %1%2%3%4
EDA1162 XMI IGET ERROR %1%2%3%4
EDA1163 XMI IDEQUE ERROR %1%2%3%
EDA1164 XMI ICLOSE ERROR %1%2%3%4
EDA1165 NOT ENOUGH VIRTUAL MEMORY %1%2%3%4
EDA1166 CREATE FUNCTION NOT AVAILABLE FOR THIS ENGINE %1%2%3%4
EDA1167 SET OPTION NOT SPECIFIED %1%2%3%4
EDA1168 INVALID SET OPTION %1%2%3%4
EDA1169 STATIC COMPILATION. SUFFIX IS NOT SUPPORTED %1%2%3%4
EDA1170 XMI INTERNAL ACB ALLOCATION ERROR %1%2%3%4
EDA1171 XMI REMOTE ACB ALLOCATION ERROR %1%2%3%4
EDA1172 XMI INTERNAL RPL ALLOCATION ERROR %1%2%3%4
EDA1173 XMI REMOTE RPL ALLOCATION ERROR %1%2%3%4
EDA1174 REMOTE HLI ERROR %1%2%3%4
EDA1175 NO REFERENCE TO FIELD DATA %1%2%3%4
EDA1176 MAILBOX ALLOCATION ERROR %1%2%3%4
EDA1177 SET OPTIONS - %1%2%3%4
EDA1178 %1%2%3%4
This used only for additional PRV messages.
EDA1179 MODULE IS MISSING - CHECK ACCESS FILE %1%2%3%4
EDA1180 %1%2%3%4
This is for trace query.
EDA1181 No remote session is currently available. Try later. %1%2%3%4
EDA1182 C-ISAM error: %1%2%3%4
EDA1183 SUFFIX %2 IS SUPPORTED IN REMOTE MODE ONLY %3%4
EDA1184 COBOL FD file syntax error %1%2%3%4
EDA1185 MEMORY ALLOCATION FAILED %1%2%3%4
EDA1186 ERROR WRITING MASTER FILE DESCRIPTION %1%2%3%4
EDA1187 ERROR WRITING ACCESS FILE DESCRIPTION %1%2%3%4
EDA1188 SYNONYM %1 ALREADY EXISTS; Use DROP SYNONYM to delete it %1%2%3%4
EDA1189 Invalid or incomplete CREATE SYNONYM command syntax %1%2%3%4
EDA1190 Missing file %1%2%3%4
EDA1191 COBOL FD file not found %1%2%3%4
EDA1192 Remote session is wrong numbered %1%2%3%4
EDA1193 Cobol FD file location syntax error %1%2%3%4
EDA1194 Cobol FD file location missing parameter %1%2%3%4
EDA1195 ACUCOBOL activator file *.vlc not found %1%2%3%4
EDA1201 ERROR LOADING MODULE %1%2%3%4
Interface module could not be loaded by QMFSS.
EDA1202 DBMS INITIALIZATION FAILED FOR SUFFIX %1%2%3%4
EDA1203 DBMS TERMINATION FAILED FOR SUFFIX %1%2%3%4
EDA1204 INVALID COMMAND CODE %1%2%3%4
EDA1205 DBMS CONTROL FAILED FOR SUFFIX %1%2%3%4
EDA1206 MEMORY ALLOCATION ERROR %1%2%3%4
EDA1207 INVALID MESSAGE RECEIVED BY QMFSST %1%2%3%4
EDA1208 INVALID COMMAND RECEIVED BY QMFSST %1%2%3%4
EDA1209 - EDA1211 RESERVED FOR QMFSS %1%2%3%4
EDA1212 INVALID USE OF FORMAT KEYWORD IN CREATE SYNONYM
FORMAT keyword in CREATE SYNONYM command may be used only with DBMS FIX and MODEL.
EDA1213 LOAD MODULE %1 FAILED.%2%3%4
Can not load module.
EDA1214 RESERVED FOR QMFSS %1%2%3%4
EDA1215 KEYWORD %1 HAS INVALID VALUE %2. %3 LN %4
Named parameter has incorrect value. For example, the KEYS attribute value must be a non-negative integer which does not exceed the number of fields in the segment. 0 should be specified only if the table has no primary key.
EDA1216 - EDA1220 RESERVED FOR QMFSS %1%2%3%4
EDA1221 ERROR IN FMI SET COMMAND %1%2%3%4
EDA1222 %1%2%3%4
Used for a general FMI message
EDA1223 FMI ERROR %1%2%3%4
EDA1224 FMI OPTION VALUE %1%2%3%4
EDA1225 - EDA1240 RESERVED FOR FMI %1%2%3%4
EDA1241 RETRIEVAL OPTIMIZATION FOR FIX 1 SEGMENT FILES IS %1%2%3%4
EDA1242 Mismatch in lengths between MFD and LRECL for the file %1%2%3%4
Calculated length of data from the Master File Description is not equal to the real file record length.
EDA1243 - EDA1245 %1%2%3%4
EDA1246 JDE Business Unit Security %1%2%3%4
EDA1247 JDE Search Type Security %1%2%3%4
EDA1248 JDE Column Security
EDA1249 JDE Business Unit Sec. for PA
EDA1250 RETRIEVAL KILLED %1%2%3%4
EDA1251 QUIT MANAGER: QUIT INITIATED FOR TSCOMID/SCB %1%2%3%4
EDA1252 QUIT MANAGER: TSCOMID NOT FOUND %1%2%3%4
EDA1253 QUIT MANAGER: SCB NOT CURRENT %1%2%3%4
EDA1254 QUIT MANAGER: SHARED MEMORY NOT CONFIGURED %1%2%3%4
EDA1255 INVALID CNS COMMAND %1%2%3%4
EDA1256 CNS: PROCESS TABLE IS NOT ACCESSIBLE %1%2%3%4
The EDASHARE is set, but PTH Manager is either not started or not responding. Start or recycle PTH Manager.
EDA1257 CNS: THE SERVER IS BEING SHUTDOWN %1%2%3%4
EDA1258 - EDA1270 RESERVED FOR QUIT MANAGER %1%2%3%
EDA1270 REQUEST KILLED DUE TO HEAVY QUIT %1%2%3%4
EDA1271 DFIX: RECORD %1. FIELD %2 IS TRUNCATED. ORIGINAL LEN = %3
EDA1272 DFIX: INCORRECT MFD ALIAS VALUE FOR NUMERIC DELIMITER
EDA1273 MQSERIES: INCORRECT VALUE FOR MSGID/CORID %1%2
EDA1274 MQSERIES: INCORRECT MFD ALIAS VALUE FOR TIMEOUT %1%2
EDA1275 MQSERIES: OPEN ERROR OR FILE IS NOT ALLOCATED %1%2%3%4
The MQSeries file specified by the Master File Description has not been allocated by the MQDEF command (rc=5040). An error appeared during MQOPEN. See Return Code in MQSeries Manual.
EDA1276 MQSERIES: READ ERROR FOR REQUESTED FILE %1%2%3%4
Error appeared during MQREAD. See Return Code in MQSeries Manual.
EDA1277 MQSERIES: INTERNAL PROBLEM - CONTEXT WAS NOT CREATED %1%2
The module NTMQ/NTMQP was not loaded. There was a memory problem in the allocation of the MQS Context/Main Control Block.
EDA1278 MQSERIES: ERROR DURING "NTMQ" MODULE LOADING %1%2%3%4
EDA1279 MQSERIES: ERROR IN PROCESSING %1%2%3%4
EDA1280 MQSERIES: WRITE ERROR FOR MASTER FILE %1%2%3%4
EDA1281 MQSERIES: MASTER FILE ALREADY EXISTS %1%2%3%4
EDA1282 MQSERIES: INCORRECT INPUT CODEPAGE %1%2%3%4
EDA1283 MQSERIES: LOOKUP ERROR FOR REQUESTED FILE %1%2%3%4
EDA1284 MQSERIES: WRITE ERROR FOR REQUESTED FILE %1%2%3%4
Error appeared during MQPUT. See Return Code in MQSeries Manual.
EDA1285 - EDA1290 %1%2%3%4
EDA1291 RECORDS AFFECTED DURING CURRENT REQUEST %1%2%3%4
Some VSAM records were updated, deleted, or inserted during the current VSAM session.
EDA1292 - EDA1300 %1%2%3%4
EDA1301 RMS TIME OUT ERROR. %1%2%3%4
EDA1302 RMS DEADLOCK SITUATION. %1%2%3%4
EDA1303 RMS RECORD NOT FOUND. %1%2%3%4
EDA1304 RMS GENERAL DELETE MESSAGE. %1%2%3%4
EDA1305 RMS DUPLICATE RECORD. RECORD NOT PROCESSED. %1%2%3%4
EDA1306 RMS INVALID RECORD SIZE, RECORD NOT PROCESSED. %1%2%3%4
EDA1307 RMS GENERAL INSERT MESSAGE. %1%2%3%4
EDA1308 RMS GENERAL UPDATE MESSAGE. %1%2%3%4
EDA1309 RMS FILE IS IN READONLY MODE. CANT MODIFY FILE %1%2%3%4
EDA1310 RMS NO CHANGES ON KEY AS FILE IS DECLARED %1%2%3%4
EDA1311 RMS ACCESS FILE IS NOT FOUND %1%2%3%4
EDA1312 FAILED TO OPEN RMS ACCESS FILE %1%2%3%4
EDA1313 FAILED TO CONNECT RMS ACCESS FILE %1%2%3%4
EDA1314 FAILED TO READ RMS ACCESS FILE %1%2%3%4
EDA1315 INVALID VALUE SPECIFIED IN ACCESS KEYWORD %1%2%3%4
EDA1316 INVALID VALUE SPECIFIED IN LOCKMODE KEYWORD %1%2%3%4
EDA1317 INVALID KEYWORD SPECIFIED IN RMS ACCESS FILE %1%2%3%4
EDA1318 PROTECTED/EXCLUSIVE NO ACCESS IN WRITE %1%2%3%4
EDA1319 OPEN RMS FILE ERROR %1%2%3%4
EDA1320 RMS STATS%1%2%3%4
EDA1321 RMS ERROR%1%2%3%4
EDA1322 RMS SKIP%1%2%3%4
EDA1323 INVALID VALUE SPECIFIED IN STATMODE KEYWORD %1%2%3%4
EDA1324 RMS KEEP%1%2%3%4
EDA1325 RMS ABORT%1%2%3%4
EDA1326 RMS RESERVED %1%2%3%4
EDA1327 RMS RESERVED %1%2%3%4
EDA1328 RMS CRSYN %1%2%3%4
EDA1329 - EDA1331 %1%2%3%4
EDA1332 CREATE SYNONYM %1%2 ERROR %3%4
EDA1333 Cobol FD Error card %1%2 (or above)
EDA1334 Card Content %1%2
EDA1336 THE SUM OF ALL FIELD LENGTHS EXCEEDS MAXIMUM. %1%2%3%4
The sum of the lengths of all fields in a structure exceeds the limit. The default limit is 32,767 bytes. Reduce the number and actual size of the fields in the file, or eliminate JOINs and cross-references if possible.
EDA1337 %1%2%3%4
EDA1338 ORACLE APPS Responsibility ID: %1%2%3%4
EDA1339 LAWSON DBMS suffix %1%2%3%4
EDA1340 LAWSON default Product Line: %1%2%3%4
EDA1341 Error in writing seq. file %1%2%3%4
EDA1342 Error in processing GENERATE command %1%2%3%4
EDA1343 Error in processing LOAD command %1%2%3%4
EDA1344 PeopleSoft EnterpriseOne Row Level Security Scope: %1%2%3%4
EDA1345 INITIAL SETTING FOR PASSREC OPTION IS: %1%2%3%4
EDA1346 %1%2%3%4
This message is reserved for GNTINT in case of 1 segment FIX files. It indicates the record number and position in this record when data conversion interruption occurs.
EDA1347 COMMAND IS TOO LONG %1%2%3%4
EDA1348 PARTIAL REPORT PRINTING OPTION IS: %1%2%3%4
EDA1349 FIELDTYPE=I REQUIRED FOR JOIN TO FIELD. CHECK TARGET MFD %1%2%3%4
EDA1350 ERROR IN SETTING INTERFACES ENVIRONMENT COMMAND. %1%2%3%4
EDA1351 ACCESS FILE NOT FOUND %1%2%3%4
At least one segment reference in the Master File Description did not have a corresponding reference in the Access File Description. If applicable, the cross-referenced Access File Description will be searched, and additional messages will be displayed as appropriate.
EDA1352 NESTED TRANSACTIONS CURRENTLY NOT SUPPORTED %1%2%3%4
An error condition occurred due to an attempt to enter a DBC BEGIN TRANSACTION statement when a previous one was not closed by an END TRANSACTION statement. This type of processing is currently not supported for the RDBMS being accessed. Restructure the FOCUS procedure as necessary.
EDA1353 ERROR READING/PARSING ACCESS FILE %1%2%3%4
An error occurred while attempting to read/parse an Access File Description. This message usually indicates a serious system-level problem. On-site system support personnel should be contacted.
EDA1354 ACCESS FILE RECORD ABSENT, WRONG OR INCOMPLETE FOR SEGMENT %1%2
No Access File Description record can be found for a segment record in the Master File Description, or the record length and/or format of the Access File Description are incorrect. Verify the allocation of the Access File Description and its contents.
EDA1355 NOT ENOUGH BASE REGISTERS FOR STATIC MODULE %1%2%3%4
An error condition was encountered while attempting to compile a FOCUS MODIFY procedure with the static SQL option, due to the fact that the procedure being compiled exceeded resource limitations. Consult the Interface User's Manual for formulas to determine eligibility for static SQL.
EDA1356 NO TABLE NAME FOR THE SEGMENT IN THE ACCESS FILE %1%2%3%4
The TABLENAME attribute in the Access File Description was either omitted or is syntactically incorrect. Check the Access File Description being referenced.
EDA1357 NOT ENOUGH VIRTUAL MEMORY %1%2%3%4
A system error occurred due to an attempt to run a procedure in an address space of insufficient size. Increase the region or virtual machine size, and execute the procedure again.
EDA1358 ERROR LOADING STATIC SQL LOAD MODULE. CHECK STUBLIB ALLOCATION
No static SQL load module could be located for the FOCEXEC being run. Check to be sure that the DDNAME of STUBLIB has been allocated to the proper data set.
EDA1359 TOO MANY FIELDS FOR SEGMENT %1%2%3%4
An error condition was encountered while attempting to compile a FOCUS MODIFY procedure with the static SQL option, due to the fact that the number of fields in the segment specified exceeded resource limitations. Consult the Interface User's Manual for formulas concerning limitations. A Join between two segments represented in this message is unsupported for suffix SQLSAP.
EDA1361 STATIC COMPILATION. ERROR(S OCCURRED %1%2%3%4
An error condition was encountered while attempting to compile a FOCUS MODIFY procedure with the static SQL option. This message is usually accompanied by additional error messages which supply more specific information.
EDA1362 COLUMN %1 TRUNCATED
Maximum character field length has been exceeded. This field has therefore been truncated.
EDA1363 THIS SUFFIX DOES NOT SUPPORT REQUESTED SETTING %1%2%3%4
EDA1364 ROWS AFFECTED BY PASSTHRU COMMAND %1%2%3%4
EDA1365 ROLLBACK ERROR %1%2%3%4
An RDBMS error condition was encountered while attempting to rollback changes to the database. This usually indicates that some required disks or libraries have not been properly accessed. Check to be sure that the RDBMS environment has been set up correctly.
EDA1366 SQL STATEMENT NOT GENERATED %1%2%3%4
SQL statement was not generated by the interface for one of the following reasons: there was not enough memory in the region to build the statement in; or the length of the statement would exceed 32K, which is the interface limit.
EDA1367 WRITE INTERFACE IS NOT INSTALLED. OPERATION NOT PERFORMED % %2
When the interface was installed at this site, it was given read-only access to the RDBMS system. No operations requiring INSERT, UPDATE, or DELETE may be executed through the interface. This configuration can be changed by systems personnel at the site, if appropriate to do so.
EDA1368 IMMEDIATE SQL NOT EXECUTED - INHIBITED BY INSTALLATION OPTION
When the interface was installed at this site, support for passing native SQL commands through the interface to the RDBMS was disabled. This configuration can be changed by systems personnel at the site, if appropriate to do so.
EDA1369 STATIC LOAD MODULE AND FOCCOMP OUT OF SYNCH %1%2%3%4
When a FOCEXEC which was compiled using the static SQL option was run, the timestamps for the FOCCOMP and its corresponding static SQL load module did not match. Check current FOCCOMP and STUBLIB allocations, and recompile the FOCEXEC with the static SQL option activated if necessary.
EDA1370 BINARY FIELDS NOT SUPPORTED (FIELD %1 IGNORED
Interface does not support BINARY fields.
EDA1371 VIEW NOT FOUND %1%2%3%4
A Direct SQL Passthru command (such as SQL PURGE) was issued. This command referred to a FOCUS view that had not been previously created using the SQL PREPARE command, or had been previously PURGEd.
EDA1372 ACCESS MODULE AND LOAD MODULE ARE OUT OF SYNCH %1%2%3%4
When a FOCEXEC which was compiled using the static SQL option was run, the timestamps for the SQL database access module and its corresponding load module did not match. Check current FOCCOMP and STUBLIB allocations, and recompile the FOCEXEC with the static SQL option activated if necessary.
EDA1373 STATIC COMPILATION. CANNOT ALLOCATE FILE TO OVERRIDE DDNAME %1%2
An error condition was encountered while compiling a FOCUS MODIFY procedure with the static SQL option, caused by an attempt to allocate a file for dynamic compilation or linking. If the message does not contain the exact data set name, a failure to allocate a temporary data set has been detected.
EDA1374 STATIC COMPILATION. KEYS=0 NOT SUPPORTED SEGMENT %1%2%3%4
A segment with the attribute KEYS=0 was referenced in a MODIFY procedure being compiled with the static SQL option. To use static SQL, all tables referenced in the MODIFY procedure must have KEYS=1 or greater.
EDA1375 STATIC COMPILATION. CANNOT GET DSNAME FOR DDNAME %1%2%3%4
An error condition was encountered while compiling a FOCUS MODIFY procedure with the static SQL option, caused by an attempt to determine the name of the data set allocated as ASMSQL and/or DBRMLIB. Check file allocations, and correct if necessary.
EDA1376 DUPLICATE SEGMENT NAMES IN ACCESS FILE %1%2%3%4
Segment names must be unique within each corresponding Master and Access File Description. Duplicates are not permitted. Check both the Master and Access File Description(s) being referenced, and make the appropriate corrections.
EDA1377 UPDATE OR DELETE FOR KEYS=0 NOT SUPPORTED FOR SUFFIX %1%2%3%4
An error occurred during execution of a MODIFY procedure during an attempt to issue an UPDATE or DELETE for a table that does not have a unique key, because the RDBMS (specified by the file suffix) does not support the syntactic construction "WHERE CURRENT OF cursor_name."
EDA1378 STATIC COMPILATION. CANNOT FREE FILE FOR DDNAME %1%2%3%4
An error condition was encountered while attempting to compile a FOCUS MODIFY procedure with the static SQL option, caused by an attempt to free a file that was not previously allocated to the DDNAME being referenced. Check file allocations, and correct if necessary.
EDA1379 MAXIMUM STORED PROCEDURE PARAMETERS - %1%2%3%4
Maximum number of parameters allowed for Oracle stored procedure.
EDA1380 STORED PROCEDURE CAN'T BE SUPPORTED - %1%2%3%4
Oracle stored procedure can't be supported by interface for the specified reason.
EDA1381 JOIN FIELDS MUST HAVE IDENTICAL actual and usage DATATYPES %1%2
Field pairs participating in joins must be of identical types. Namely, usage type of host field must be same as its actual type and same as the usage and actual types of the cross-reference field.
EDA1382 UNSUPPORTED DATATYPE FOUND, COLUMN %1 IGNORED
EDA1383 UNSUPPORTED DATETIME FORMAT FOR FIELD %1%2%3%4
The given SQL interface doesn't support DATETIME format indicated in MFD description for the field.
EDA1384 LONG FIELD NAME IN ACCESS FILE IS NOT PRESENT IN MASTER %1%2%3%4
A long field name declaration in the Access File Description contains a FIELD= keyword value that does not match any field name in the corresponding segment in the Master File Description. Check the spelling and order of field description records in the MFD and AFD.
EDA1385 UNCOMPARABLE FORMATS FOR DATETIME JOIN FIELDS %1%2%3%4
DATETIME field pairs participating in joins must consist of the same DATETIME components. (For example, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, MILLISECOND, MICROSECOND.)
EDA1386 THE EXPLAIN TEXT IS AS FOLLOWS:
A DDNAME of XPLTRACE was not allocated. Therefore, the Explain Text will be written out to the terminal. In such a case, this message will precede the Explain Text.
EDA1387 FIELD NEEDS AN ALIAS IN MASTER FILE OR ACCESS FILE %1%2%3%4
A field reference in either a Master or Access File Description is missing its corresponding ALIAS reference to the actual RDBMS column name. Check the RDBMS system catalogs to determine the column name, and make the appropriate corrections to the Master or Access File Description.
EDA1388 TYPE MISMATCH FOR JOIN ON DATETIME FIELD %1%2%3%4
One of two fields in join pair is DATETIME, while the other is not. This is not supported by SQL interfaces.
EDA1389 STATIC SQL IS NOT SUPPORTED IN PRESENSE OF DATETIME FIELDS
EDA1390 ACTUAL LENGTH FOR FORMAT D MUST BE 8 %1%2%3%4
Columns defined in the RDBMS as REAL or FLOAT and having an ACTUAL format of D in the Master File Description must have an ACTUAL length of 8. Check the RDBMS catalogs and make the appropriate corrections to the Master File Description.
EDA1391 ACTUAL FORMAT Z IS INVALID FOR SQL FILES. USE FORMAT A %1%2%3%4
The FOCUS ACTUAL format of Z does not correspond to any RDBMS data type and is not allowed. Refer to the ACTUAL Format Conversion Chart in the appropriate Interface User's Manual for the correct ACTUAL format.
EDA1392 STATIC COMPILATION. DD MISSING %1%2%3%4
During the compilation of a MODIFY procedure with the static SQL option, at least one of the required DDNAMES was missing. Check the allocations for DDNAMES ASMSQL, DBRMLIB, DB2LOAD, STUBLIB, SQLERR1, SQLERR2, SQLERR3, and FOCCOMP, and make the appropriate corrections.
EDA1393 STATIC COMPILATION. CANNOT ALLOCATE PDS MEMBER FOR DDNAME %1%2%
An error condition was encountered while compiling a FOCUS MODIFY procedure with the static SQL option, caused by an attempt to allocate a member in a data set that does not have partitioned organization or has no space for a new directory element or member. Reallocate or compress the data set.
EDA1394 CONNECT FAILURE %1%2%3%4
An error condition occurred while attempting to attach to the RDBMS. An error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1395 OPEN FAILURE %1%2%3%4
An error condition occurred while attempting to allocate a thread to the RDBMS. An additional error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1396 CLOSE FAILURE %1%2%3%4
An error condition occurred while attempting to deallocate a thread to the RDBMS. An additional error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1397 DISCONNECT FAILURE %1%2%3%4
An error condition occurred while attempting to detach from the RDBMS. An error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1398 CONNECT FAILED. DO DISCONNECT FIRST %1%2%3%4
An error condition occurred while attempting to attach to the RDBMS, due to an attachment already in effect. Either allocate a thread using the current connection, or disconnect from the RDBMS and then attempt connection again.
EDA1399 SQL PUT ERROR. %1%2%3%4
An error condition occurred during an INCLUDE operation in SQL LOADONLY mode. This can result in unexpected results during the data load process. The FOCERROR variable should be tested after every INCLUDE in this mode, and any non-zero return code should be made to trigger an SQL ROLLBACK.
EDA1400 SQLCODE IS %1 (HEX: %2 %3%4
This message indicates an error at execution of an SQL operation. It contains the SQL return code returned by the RDBMS and is usually accompanied by appropriate FOCUS error messages. For additional information about SQL return codes, refer to the RDBMS manual.
EDA1401 %1
Used as an alternative to 1400. Its syntax is: DBMS#ErrorCode#DBMS specific information. For example, DB2#-204#52004#CAR
EDA1402 KEYFLD AND IXFLD KEYWORDS MISSING FOR SEGMENT %1%2%3%4
A segment reference in a multi-table Access File Description is missing the required KEYFLD and IXFLD attributes, which should exist in all segments except the top segment. Check the Master File Description and make the appropriate corrections to the Access File Description.
EDA1403 SEGTYPE=S0 OR U IS REQUIRED FOR SQL UPDATE %1%2%3%4
Segments in Master File Descriptions which describe RDBMS tables must have a SEGTYPE attribute of S0 or U (S0 is required for the root segment). Check the Master File Description and make the appropriate corrections.
EDA1404 LOADONLY MODE IS INVALID IN PRESENCE OF UPDATE OR DELETE %1%2%3%4
An attempt was made to issue the SQL SET LOADONLY command from within a MODIFY procedure that contains UPDATEs or DELETEs. LOADONLY Mode is only valid for ON NOMATCH INCLUDE operations, as it disables the SQL SELECT logic necessary for any other MATCH commands to be effective.
EDA1405 SQL PREPARE ERROR. %1%2%3%4
An error condition occurred while attempting to prepare a cursor in the RDBMS. An additional error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1406 SQL OPEN CURSOR ERROR. %1%2%3%4
An error condition occurred while attempting to open a cursor in the RDBMS. An additional error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1407 SQL FETCH CURSOR ERROR. %1%2%3%4
An error condition occurred while attempting to fetch data through a cursor in the RDBMS. An additional error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1408 SQL CLOSE CURSOR ERROR. %1%2%3%4
An error condition occurred while attempting to close a cursor in the RDBMS. An additional error message specifying the appropriate RDBMS error code will usually accompany this message. Consult the appropriate RDBMS error message reference for proper corrective measures.
EDA1409 SQL TABLE NOT FOUND. (FOR TABLE: CHECK SEGNAME AND TABLE %1%2
An RDBMS table referenced in a procedure could not be located in the database. Make sure the correct database is being accessed, and check the SEGNAME and TABLENAME attributes in the Access File Description. Also, consider the RDBMS default object-naming rules.
EDA1410 SQL COLUMN NOT FOUND. (FOR TABLE: CHECK ALIAS NAMES %1%2%3%4
An RDBMS column referenced in a procedure could not be located in the database. Make sure the correct database is being accessed, and check the FIELDNAME and ALIAS attributes in the Master File Description (and the Access File Description, if appropriate).
EDA1411 SQL/DS SYSTEM IS NOT ACTIVE %1%2%3%4
The SQL/DS database being accessed was found to be inactive during the execution of a procedure. Contact the appropriate on-site SQL/DS RDBMS support personnel.
EDA1412 RUN SQLINIT EXEC TO SPECIFY THE DATABASE NAME %1%2%3%4
An attempt was made to execute a procedure which accesses an SQL/DS database without first running the IBM SQLINIT program to identify the database to be utilized during subsequent procedures. Run the SQLINIT program to specify the database.
EDA1413 USER HAS INSUFFICIENT AUTHORITY FOR REQUESTED OPERATION %1%2%3%4
An RDBMS operation was attempted for which the user has not been granted sufficient authority, or the RDBMS object named in the operation does not exist. Contact the appropriate on-site RDBMS support personnel.
EDA1414 EXECUTE IMMEDIATE ERROR. %1%2%3%4
An RDBMS error condition was encountered during the execution of an SQL statement. This message is usually accompanied by additional error messages which supply more specific information.
EDA1415 COMMIT WORK ERROR. %1%2%3%4
An RDBMS error condition was encountered while attempting to commit changes to the database. This message is usually accompanied by additional error messages which supply more specific information.
EDA1416 EXECUTE ERROR %1%2%3%4
An RDBMS error condition was encountered during the execution of an SQL statement. This message is usually accompanied by additional error messages which supply more specific information.
EDA1417 INSERT WOULD CREATE DUPLICATES FOR UNIQUE INDEX. NO ACTION TAKEN
An attempt was made to INSERT a row of data into an RDBMS table that would have resulted in duplicate key values in the table for columns that were indexed with an RDBMS unique index. This resulted in an RDBMS error condition, and no rows were inserted into the table.
EDA1418 ACTUAL/USAGE TYPE MISMATCH FOR DATETIME FIELD %1%2%3%4
EDA1419 USER DOES NOT HAVE CONNECT AUTHORITY %1%2%3%4
The current userid, or the SQL userid specified in an explicit SQL CONNECT command, does not currently have authority to connect to the RDBMS. Contact the appropriate on-site RDBMS support personnel.
EDA1420 OPTIMIZATION OF ALL=ON AS LEFT JOIN - %1%2%3%4 2%3%4
EDA1421 TABLE EXISTS ALREADY. DROP IT OR USE ANOTHER TABLENAME %1%2%3%4
An attempt was made to create an RDBMS table that already exists in the database. Check to see that the correct database is being utilized. If necessary, drop the currently existing table, or create the new table with a different name. Correct the AFD if the message was issued in response to CREATE FILE.
EDA1422 NO PRIVATE DBSPACE IN WHICH TO CREATE THE TABLE %1%2%3%4
The RDBMS has no default private DBSPACE for the currently connected user. Either explicitly identify the DBSPACE which should contain the newly created table, or connect as an RDBMS user who has a default DBSPACE set up.
EDA1423 DBC CHARACTER SET NAME - %1%2%3%4
EDA1424 ISOLATION LEVEL FOR DB2 TABLE INTERFACE IS %1%2%3%4
EDA1425 OVERFLOW, ZERODIVIDE OR CONVERSION ERROR ON ITEM # %1%2%3%4
The message refers to an answer set item (SQLDA element) for which the indicator value was set to (-2) by the RDBMS, by its positional number and SQLDA name (if supplied). A potential solution is to enlarge the range of acceptable values by changing MFD for the corresponding field.
EDA1426 DATA ELEMENT VALUE TOO BIG FOR SEGMENT/FIELD %1%2%3%4
An error occurred when converting a data item for the field in the segment with the names given in the message. Data could not be converted without truncation from the USAGE to the ACTUAL format for INSERT or UPDATE operation. FOCERROR is posted to 1426.
EDA1427 SAP/R3 CLIENT%1 -: %2%3%4
This is one line of the system response to the interface's settings query: SQL <suffix>? This setting is the current SAP/R3 client, which will be used for connection to the SAP/R3 server for the next FOCUS request. This setting may be changed using the SET SQLSAP CLIENT command.
EDA1428 DEFINED FIELDS ARE NOT SUITABLE FOR SQLSAP JOIN - %1%2%3%4
Using defined fields for a join between two files is currently unsupported for suffix SQLSAP.
EDA1429 SAP/R3 REQUEST EXECUTION MODE IS - : %1%2%3%4
This is one line of the system response to the interface's settings query: SQL <suffix>? This setting is the current SAP/R3 request execution mode, which will be used for the next FOCUS request. This setting may be changed using the SET SQLSAP EXECUTIONMODE command.
EDA1430 SAP/R3 DYNAMIC REQUEST MODE IS - : %1%2%3%4
This is one line of the system response to the interface's settings query: SQL <suffix>? This setting is the current SAP/R3 system number (sysnr), which will be used for connection to the SAP/R3 server for the next FOCUS request. This setting may be changed using the SET SQLSAP DYNAMICMODE cmd.
EDA1431 SAP/R3 SYSTEM IS - %1%2%3%4
This is one line of the system response to the interface's settings query: SQL <suffix>? This setting is the current SAP/R3 system number (sysnr), which will be used for connection to the SAP/R3 server for the next FOCUS request. This setting may be changed using the SET SQLSAP USER command.
EDA1432 MISSING PACKED FIELD MUST HAVE ACTUAL LENGTH 8 OR MORE %1%2
An RDBMS column defined as DECIMAL, and which allows null values, must have an ACTUAL format of P8 through P16 in the Master File Description. It should also have the MISSING attribute set to ON. Check the Master File Description and make the appropriate corrections.
EDA1433 MISSING FIELD IN INTEGER FORMAT MUST HAVE ACTUAL FORMAT I4 %1%2
An RDBMS column that allows null values and is defined as SMALLINT or INTEGER must have an ACTUAL format of I4 in the Master File Description. It should also have the MISSING attribute set to ON. Check the Master File Description, and make the appropriate corrections.
EDA1434 THE VALUE FOR 'KEYS' KEYWORD IS INVALID %1%2%3%4
The value assigned to the KEYS attribute in an Access File Description must be a nonnegative integer which does not exceed the number of fields in the segment. 0 should be specified only if the table has no primary key.
EDA1435 ROLLBACK OCCURRED DUE TO AN INTERNAL SYSTEM DEADLOCK %1%2%3%4
A forced RDBMS ROLLBACK occurred during a procedure due to a system deadlock condition in the RDBMS. Contact the appropriate on-site RDBMS support personnel.
EDA1436 ROLLBACK OCCURRED DUE TO EXCESSIVE SYSTEM-WIDE DEADLOCKS %1%2%3%4
A forced RDBMS ROLLBACK occurred during a procedure due to an excessive number of user-related deadlocks in the RDBMS. Contact the appropriate on-site RDBMS support personnel.
EDA1437 ROLLBACK OCCURRED DUE TO EXCESSIVE LOCKS HELD FOR THIS LUW %1%2
A forced RDBMS ROLLBACK occurred during a procedure due to an excessive number of locks being held by the current Logical Unit of Work generated by the procedure. Enhance the procedure to COMMIT WORK more frequently if possible. Contact on-site RDBMS support personnel if the problem persists.
EDA1438 CURRENT DATABASE NAME - %1%2%3%4
This is the current database we are connected to in the DB2/6000 environment.
EDA1439 CURRENT USER ID - %1%2%3%4
This is the current user name under which we are connected to the current database in the DB2/6000 environment.
EDA1440 CURRENT SQL INTERFACE SETTINGS ARE : %1%2%3%4
This is the first line of the system response to the interface's SQL ? query. Following this line will be a list of system defaults and current settings for the RDBMS environment.
EDA1441 WRITE FUNCTIONALITY IS - %1%2%3%4
This setting shows the functionality the interface was installed with. If the setting is ON, the interface was installed to allow INCLUDE, UPDATE and DELETE operations through the FOCUS MODIFY facility. If the setting is OFF, only TABLE and MODIFY with browse functionality are permitted.
EDA1442 CALL ATTACH FACILITY IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. If the setting is ON, the interface was installed with the Call Attach Facility (CAF), which allows dynamic DB2 environmental control. If the setting is OFF, the interface was installed with TSO Attach.
EDA1443 RUN ON OPTION IS - %1%2%3%4
EDA1444 AUTOCLOSE OPTION IS - %1%2%3%4
The message shows the currently established strategy of DB2 thread manipulation. The thread is automatically closed at the end of the FOCUS session if the setting is ON FIN, at the end of TABLE or MODIFY if the setting is ON COMMAND, or whenever COMMIT WORK is issued if the setting is ON COMMIT.
EDA1445 OPTIMIZATION OPTION IS - %1%2%3%4
This is the optimization strategy for multi-segment TABLE requests. Setting OFF prohibits any attempts to create a united SQL statement for all segments (for example, SQL tables) utilizing RDBMS join, sort and aggregation capabilities. See interface documentation for description of other settings.
EDA1446 DEFAULT DBSPACE IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. This setting is the name of the SQL/DS DBSPACE or DB2 database where the RDBMS places tables created by FOCUS CREATE FILE or HOLD FORMAT SQL commands. The SQL SET DBSPACE command may be used to alter this setting.
EDA1447 SSID FOR CALL ATTACH IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. This setting is the name of the DB2 subsystem that will be accessed with the next FOCUS request or native SQL command. If the Call Attach Facility is installed, use the SQL DB2 SET SSID command to alter this setting.
EDA1448 ACTIVE PLAN FOR CALL ATTACH IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. This setting is the name of the DB2 application plan that is attached to the currently open thread. If no thread is currently allocated, this setting will be blank.
EDA1449 CURRENT SQLID IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. This setting is the name of the SQL id currently in use for purposes of DB2 authorization. Use the SQL DB2 SET CURRENT SQLID command to alter this setting.
EDA1450 CURRENT %1 INTERFACE SETTINGS ARE :
This is the first line of the system response to the interface's SQL? query. Following this line will be a list of system defaults and current settings for the RDBMS environment.
EDA1451 CURSOR ALLOCATION ERROR - REINSTALL INTERFACE, INCREASE NCRS
An attempt was made by an application to allocate more concurrent RDBMS cursors than the maximum that was specified during the interface installation process. To increase the maximum setting, the interface must be reinstalled with an increased NCRS value (to a maximum of 99).
EDA1452 STATEMENT ALLOCATION ERROR - REINSTALL INTERFACE,INCREASE NSTMTS
An attempt was made by an application to allocate more concurrent RDBMS statements than the maximum that was specified during the interface installation process. To increase the maximum setting, the interface must be reinstalled with an increased NSTMTS value (to a maximum of 99).
EDA1453 DEFAULT INDEX SPACE PARAMETERS - %1%2%3%4 1%2%3%4
EDA1454 BIND OPTIONS FOR STATIC COMPILATION - %1%2%3%4
EDA1455 CAF: INACTIVE DB2 SSID %1%2%3%4
During an attempt to allocate a thread to DB2, the most recently specified subsystem name was found to be inactive. Contact the appropriate on-site DB2 support personnel.
EDA1456 CAF: SPECIFIED DB2 SSID NOT FOUND %1%2%3%4
During an attempt to allocate a thread to DB2, the most recently specified subsystem name could not be located. Determine the correct subsystem name, and use the SQL DB2 SET SSID command to change the current setting. If a nonexistent subsystem is the default, the interface should be reinstalled.
EDA1457 CAF: NOT AUTHORIZED TO CONNECT TO THIS DB2 SSID %1%2%3%4
During an attempt to allocate a thread to DB2, the CURRENT SQLID was found to have no authority in the most recently specified DB2 subsystem. Change the CURRENT SQLID or subsystem setting (or both), or request authority for the CURRENT SQLID and subsystem from on-site DB2 personnel.
EDA1458 CAF: PLAN NOT FOUND OR USER NOT AUTHORIZED %1%2%3%4
During an attempt to allocate a thread to DB2, either the most recently specified plan could not be found, or the CURRENT SQLID has not been granted EXECUTE authority for it. Change the CURRENT SQLID or plan setting (or both), or request authority from on-site DB2 support personnel.
EDA1459 USER SET PLAN FOR CALL ATTACH IS - %1%2%3%4
This is one line of the system response to the interface's SQL ? query. This setting is the name of the DB2 application plan that was specified by the most recent SQL DB2 SET PLAN command issued, if the Call Attach Facility is installed.
EDA1460 INSTALLATION DEFAULT PLAN IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. This setting is the name of the DB2 application plan that was specified as the default during the interface installation process. This plan will be in effect unless the SQL DB2 SET PLAN command is issued (CAF only).
EDA1461 CURRENT DBC/SQL SETTINGS ARE: %1%2%3%4
This is the first line of the system response to the interface's SQLDBC? query. Following this line will be a list of system defaults and current settings for the RDBMS environment.
EDA1462 DYNAMIC ALLOCATION ERROR CODE / INFO CODE %1%2%3%4
During compilation of a FOCEXEC with the static SQL option, the system was unable to dynamically allocate a data set necessary for one of the stages of processing the generated static SQL program. Consult the SVC99 RETURN CODES section of IBM SYSTEMS PROGRAMMING LIBRARY: SYSTEM MACROS AND FACILITIES.
EDA1463 DBC/1012 CONNECTION - %1%2%3%4
This is one line of the system response to the interface's SQLDBC? query. If the setting is ON, then a connection to the DBC/1012 computer is currently in effect. If the setting is OFF, there is no current connection. The SQLDBC SET AUTOCLOSE command is used to change connection duration.
EDA1464 FULL KEY MATCH RETURNED MORE THAN 1 ROW. CHECK KEYS= IN AFD
During the run of a static MODIFY procedure, a full key MATCH against an SQL table returned multiple rows. This means that the KEYS parameter in the Access File Description for the table does not identify a unique key. Make appropriate corrections to the KEYS attribute.
EDA1465 DBC COLNAME OPTION IS - %1%2%3%4
This is a line of the system response to the TERADATA interface's SQLDBC? query. This setting determines whether column names or column titles from the colinfo parcel are used at describe time. If the value is NAME, names are used whenever present; otherwise titles are used. TITLE is the default.
EDA1466 JOINTYPE - %1%2%3%4
The algorithm used to compute a Cross-Platform JOIN. The default is NESTEDLOOP for the SQL interfaces Files; however, it may be set to SORTMERGE.
EDA1467 PARTITION - %1%2%3%4
This is one line of the system response to the interface's SQLDBC? query. This setting is the name of the Teradata language partition currently in use by the interface.
EDA1468 TERADATA DIRECTOR PROGRAM (TDP) - %1%2%3%4
This is one line of the system response to the interface's SQLDBC? query. This setting is the name of the Teradata Director Program that will be used to access the DBC/1012 for the next FOCUS request or native SQL command. This setting may be changed using the SQLDBC SET DBCLOGON command.
EDA1469 DBC/1012 USER ID - %1%2%3%4
This is one line of the system response to the interface's SQLDBC? query. This setting is the Teradata userid that will be used to access the DBC/1012 for the next FOCUS request or native SQL command. This setting may be changed using the SQLDBC SET DBCLOGON command.
EDA1470 TYPE CONVERSION FAILED FOR STATEMENT %1%2%3%4
An attempt was made to execute a statement that was prepared and bound with parameterized SQL, using data that cannot be converted to the data type(s) specified when the statement was bound.
EDA1471 INTERNAL ERROR IN PHYSICAL LEVEL INTERFACE %1%2%3%4
An inconsistency in the interface internal control blocks has been encountered. This condition may be caused by a user error. Please contact your iWay support representative for assistance in resolving this condition.
EDA1472 STATIC SQL PROGRAM CREATED SUCCESSFULLY %1%2%3%4
This is the first of the responses issued during the compilation of a FOCUS MODIFY procedure with STATIC option set to ON. This message signifies that a static SQL program has been generated and is ready for preprocessing by the RDBMS software.
EDA1473 STATIC SQL PROGRAM PREPROCESSED. RETURN CODE IS %1%2%3%4
This is the response issued following the preprocessing of a static SQL program created by the compilation of a FOCUS MODIFY procedure with the static SQL option set to ON. A successful completion will be signified by a return code of less than or equal to 4.
EDA1474 STATIC SQL PROGRAM ASSEMBLED. RETURN CODE IS %1%2%3%4
This is the response issued following the assembly of a static SQL program created by the compilation of a FOCUS MODIFY procedure with the static SQL option set to ON and preprocessed by DB2. A successful completion will be signified by a return code of 0.
EDA1475 DEFAULT SERVER IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. This setting is the name of the default server. The SQL EDA SET SERVER command may be used to alter this setting.
EDA1476 STATIC SQL PROGRAM LINKED. RETURN CODE IS %1%2%3%4
This is the response issued following the linkage editing of a static SQL program created by the compilation of a FOCUS MODIFY procedure with the STATIC option set to ON, preprocessed by DB2 and assembled. A successful completion will be signified by a return code of 0.
EDA1477 UNEXPECTED BEGIN SESSION OR END SESSION %1%2%3%4
An attempt was made to issue an improper sequence of parameterized SQL commands. The proper sequence is as follows: BEGIN SESSION, PREPARE, BIND, EXECUTE, ..., END SESSION.
EDA1478 PLAN CANNOT BE BOUND IN BATCH MODE. USE TSO TMP %1%2%3%4
An attempt was made to BIND an application plan in batch mode. Because the DSN command processor cannot be invoked in batch, the SET STATIC option must be set to NOBIND if static SQL processing is desired, and any plans resulting from COMPILE commands must be bound separately, in online mode.
EDA1479 ERROR CONNECTING TO SQL DATABASE %1%2%3%4
An error condition occurred during an attempt to connect to the RDBMS. This message is usually accompanied by additional error messages which supply more specific information.
EDA1480 INTERNAL ERROR: STATEMENT NOT FOUND IN SQL LOAD MODULE %1%2%3%4
An error occurs when SQL load module does not correspond to FOCCOMP with the same time stamp. This usually means corrupted data. Recompile the modify request and try again.
EDA1481 SET PLAN INSIDE NESTED PROCEDURE IS INVALID, IGNORED %1%2%3%4
An attempt was made to issue the SQL DB2 SET PLAN command inside a nested FOCUS procedure. Since only a single plan may be in effect at any one time, this operation is not supported. Restructure the FOCUS procedure as necessary.
EDA1482 NESTED PROCEDURE DEFAULT PLAN IGNORED, USING CURRENT %1%2%3%4
A static SQL procedure loaded as a nested FOCUS procedure has a different DB2 plan than the calling procedure. Since switching plans (CAF Close followed by CAF Open) cannot be performed when a procedure is nested, an attempt will be made to continue under the current plan.
EDA1483 DBTFOC MODULE IS NOT LINKED OR CLI TXTLIB IS UNAVAILABLE %1%2%3%4
During an attempt to access the Teradata interface, the loaded DBTFOC module did not have DBC CLI routines linked into it. Check to see that the Teradata interface was installed successfully, as well as current allocation of FOCUS and Teradata libraries or minidisks.
EDA1484 SQL ERROR MESSAGE TYPE IS - %1%2%3%4
This setting shows the type of error message handling currently in effect. The setting is either FOCUS (no DBMS error messages are issued), or DBMS (both FOCUS and DBMS messages are issued). The default setting can be changed at run time by issuing the SQL DB2 SET ERRORTYPE command.
EDA1485 SQL ERRORRUN OPTION IS - %1%2%3%4
The setting determines the RDBMS error handling type in a MODIFY procedure. With ERRORRUN OFF, the procedure is terminated when an error is encountered unless it is of "transaction" type. With ERRORRUN ON, the procedure always continues and any error handling must be performed by the procedure itself.
EDA1486 SET SSID INSIDE NESTED PROCEDURE IS INVALID, IGNORED %1%2%3%4
An attempt was made to issue the SQL DB2 SET SSID command inside a nested FOCUS procedure. Since only a single subsystem may be in effect at any one time, this operation is not supported. Restructure the FOCUS procedure as necessary.
EDA1487 SQL SYNTAX ERROR %1%2%3%4
An error was encountered during parsing of a Direct SQL Passthru command such as SQL PREPARE, SQL BIND, SQL EXECUTE, SQL PURGE etc. Check and correct the sequence and/or spelling of tokens and delimiters comprising the command entered, using its description in the SQL interface manual.
EDA1488 SQL INTERFACE HAS NOT BEEN INSTALLED OR COULD NOT BE INSTALLED
One of the interface modules cannot be loaded into memory or does not have proper DBMS software components linked into it or the DBMS environment has not been properly set up. The installation procedure must be executed prior to using the interface. Consult the appropriate installation manual.
EDA1489 LOCAL SQL INTERFACE IS NOT AVAILABLE %1%2%3%4
An error condition occurred during an attempt to use the interface with the Cross Machine Interface (XMI) facility, due to the unavailability of the local machine portion of the SQL interface. Check the files currently linked or allocated, and make appropriate corrections.
EDA1490 INVALID SQL SUFFIX. UNSUPPORTED SQL DIALECT %1%2%3%4
The SUFFIX attribute in a Master File Description was specified as something other than SQLDS, SQLDBC, or SQLORA etc. These are the only supported interface dialects. Check the Master File Description and make appropriate corrections.
EDA1491 FETCH BUFFERING FACTOR - %1%2%3%4
The setting controls the block size used for fetching data from Oracle tables. The default setting is 20. The greater the factor, the greater the interface performance in terms of CPU usage; however, increasing this factor increases operating memory requirements.
EDA1492 XMI SQL ERROR %1%2%3%4
An error condition occurred during an attempt to access the XMI Gateway to either DB2 or SQL/DS. This message is usually accompanied by additional error messages which supply more specific information.
EDA1493 XMI ERROR. GATEWAY IS DOWN OR INOPERABLE %1%2%3%4
An error condition occurred during an attempt to access the XMI Gateway to either SQL/DS or DB2. The XMI Gateway is either down or is in an inoperable state. Contact the appropriate on-site support personnel.
EDA1494 REFERENTIAL INTEGRITY VIOLATION %1%2%3%4
An attempt was made to perform an operation that would cause a violation of one or more referential integrity constraints specified in the RDBMS. This violation will not terminate a MODIFY procedure. Contact on-site RDBMS support personnel for specific referential integrity constraints.
EDA1495 EXECUTION ENDED DUE TO RESOURCE LIMIT VIOLATION %1%2%3%4
The RDBMS optimizer calculated a cost estimate for an SQL query generated by a FOCUS request or entered in native SQL that is higher than the maximum cost allowed by the RDBMS governor. This condition resulted in the termination of the request. Any query results should be ignored.
EDA1496 AUTODISCONNECT OPTION IS - %1%2%3%4
This is one line of the system response to the interface's SQL ? query. If the setting is ON FIN (the default), the connection lasts for the entire FOCUS session. Optional settings are ON COMMIT and ON COMMAND, which can be invoked by issuing the SQL SET AUTODISCONNECT command.
EDA1497 SQL EXPLAIN OPTION IS - %1%2%3%4
This setting shows whether EXPLAIN processing will be invoked for subsequent report requests. If the setting is ON, an EXPLAIN will be performed for any subsequent requests, followed by an execution of the request itself. If it is OFF, then only the request itself will be executed.
EDA1498 CURRENT USERID IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. This setting is the name of the user id currently in use for authorization. Use the SQL EDA SET USER command to alter this setting.
EDA1499 AUTOCOMMIT OPTION IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. If the setting is ON COMMAND (the default), an SQL COMMIT WORK will occur at the end of every procedure. Optional settings are ON CRTFORM and ON FIN, which can be made by issuing the SQL SET AUTOCOMMIT command.
EDA1501 CURRENT ORACLE INTERFACE SETTINGS ARE: %1%2%3%4
This is the first line of the system response to the interface's SQLORA ? query. Following this line will be a list of system defaults and current settings for the RDBMS environment.
EDA1502 USERID AND PASSWORD ARE - %1%2%3%4
This is one line of the system response to the interface's settings query: SQL <suffix>?. This setting is the userid and password (not displayed); it will be used for connection to RDBMS for the next FOCUS request or native SQL command. The setting may be changed using the SET USER command.
EDA1503 SQL STATIC OPTION IS - %1%2%3%4
This is one line of the system response to the interface's SQL? query. If the setting is ON, compiling a FOCEXEC will generate static SQL code to be used when the compiled FOCEXEC is RUN. If the setting is OFF, running the compiled FOCEXEC will generate dynamic SQL at run time.
EDA1504 SET SSID IS INVALID UNDER MSO, IGNORED %1%2%3%4
Due to a system limitation of one active subsystem per address space, only the address space that was active when MSO was initiated may be used. As a result, a SQL DB2 SET SSID command in a procedure was ignored.
EDA1505 BIND ERROR %1%2%3%4
The interface detected a misuse of the parameterized SQL commands PREPARE, BIND, and/or EXECUTE. This message will usually be accompanied by additional messages containing more specific information.
EDA1506 NUMBERS OF LITERALS AND PARAMETER MARKERS DO NOT MATCH %1%2%3%4
An error condition occurred which was caused by the issuance of a parameterized SQL EXECUTE command that contained a different number of literals than the number of parameter markers referenced in the corresponding previous parameterized SQL PREPARE command.
EDA1507 NUMBERS OF LITERALS AND TYPES SPECIFIED IN BIND DO NOT MATCH %1%2
An error condition occurred which was caused by the issuance of a parameterized SQL EXECUTE command that contained a different number of literals than the number of data items referenced in the corresponding previous parameterized SQL BIND command.
EDA1508 STATIC SQL MODULE NEEDS TO BE RECOMPILED %1%2%3%4
An error condition occurred which was caused by an attempt to use a static SQL module called by a FOCEXEC which was compiled under an earlier release of FOCUS. This FOCEXEC must be recompiled under the release of FOCUS currently running.
EDA1509 SETTING LOGON PARAMETERS INSIDE NESTED PROCEDURE IS INVALID %1%2
An error condition occurred during the execution of a MAINTAIN procedure which invoked another procedure that sets Oracle USER and PASSWORD parameters. This is prohibited in a nested procedure.
EDA1510 MAINTAIN: NO SEGMENT POSITION ESTABLISHED PRIOR TO NEXT %1%2%3%4
EDA1511 MAINTAIN: SQL INTERNAL ERROR %1%2%3%4
EDA1512 SQL PASSTHRU INTERNAL ERROR %1%2%3%4
EDA1513 SQL PASSTHRU - DATATYPE NOT SUPPORTED FOR EDA %1%2%3%4
EDA1514 SQL PASSTHRU - STATEMENT IS ALREADY IN USE %1%2%3%4
This condition will occur if a Direct SQL Passthru statement is PREPAREd for one RDBMS, and the same name is subsequently used to PREPARE a statement for another RDBMS while the first name is still in effect.
EDA1515 WRONG SQL ENGINE TAG SPECIFIED %1%2%3%4
EDA1516 UNRECOGNIZED SET COMMAND %1%2%3%4
EDA1517 UNRECOGNIZED COMMAND %1%2%3%4
EDA1518 INVALID SYNTAX FOR COMMAND %1%2%3%4
EDA1519 SERVER INTERNAL ERROR: %1%2%3%4
EDA1520 SQL CURRENT OWNER ID IS - %1%2%3%4
This value is attached to all unqualified SQL table references issued by the interface, for example, SELECT, INSERT, CREATE. This value will not affect Direct SQL Passthru.
EDA1521 UNKNOWN SERVER: %1
EDA1522 %1%2%3%4
Messages from CALLPGM procedures.
EDA1523 Bad syntax in CREATE TABLE. %1%2%3%4
CALLPGM
EDA1524 Data comes before description ( CREATE TABLE %1%2%3%4
CALLPGM
EDA1525 A message inside an answerset %1%2%3%4
CALLPGM
EDA1526 STATIC TABLE REQUEST DOESN'T CORRESPOND TO SQL LOAD MODULE
EDA1527 COMMAND FLUSHED WHILE COMPILING STATIC TABLE %1%2%3%4
EDA1528 (CREATE SYNONYM Unable to write in file: %1%2%3%4
DQODSC couldn't write to disc for DROP/CREATE SYNONYM.
EDA1529 STATIC TABLE: cannot find FOCEXEC specified %1%2%3%4
EDA1530 DIRECT SQL DATASTORE %1%2%3%4
EDA1531 INSERT BUFFERING FACTOR - %1%2%3%4
The setting controls the block size used for inserting data into Oracle tables. The default setting is 20. The greater the factor, the greater the interface performance in terms of CPU usage; however, increasing this factor increases operating memory requirements.
EDA1532 NUMERIC VALUE EXPECTED %1%2%3%4
EDA1533 Wrong value for SET EXORDER %1%2%3%4
EDA1534 Wrong EX command %1%2%3%4
EDA1535 SQLENGINE is not set for 3GL ODBC %1%2%3%4
EDA1536 OWNERID is not set for 3GL ODBC %1%2%3%4
EDA1537 3GL procedure doesn't exist: %1%2%3%4
EDA1538 4GL procedure doesn't exist: %1%2%3%4
EDA1539 STATIC TABLE: SCREENING DATA OUT OF RANGE %1%2%3%4
EDA1540 STATIC SQL IS NOT SUPPORTED FOR THIS INTERFACE %1%2%3%4
EDA1541 %1%2%3%4
Tracing to the client.
EDA1542 %1%2%3%4
ODBCPROC in SPG (stored procedures gateway).
EDA1543 SYNONYM NAME IS INVALID OR LONGER THAN 64 CHARACTERS.
The synonym name is incorrect. Some of the possible reasons are that the name is in appname/filename format but APP mode is disabled; or that the maximum length of a synonym (64 bytes) is exceeded. The message is usually preceded by other error messages.
EDA1544 Syntax error: %1
EDA1545 AFD '%1' wasn't erased - DROP SYNONYM failed
EDA1546 MFD '%1' wasn't erased - DROP SYNONYM failed
EDA1547 Neither MFD nor AFD exists for synonym '%1'
EDA1548 ITC Request to Interface Function %1 Execution Error
EDA1549 %1 %2 setting forsed on engine SUFFIX=%3
EDA1550 AFD '%1' couldn't be overwritten by CREATE SYNONYM
EDA1551 QUERY NUMBER TO BE USED FOR EXPLAIN - %1%2%3%4
This setting shows the arbitrary number assigned to the subsequent SQL queries being analyzed with the FOCUS/RDBMS EXPLAIN option. This number may be changed by issuing SQL SET EXPLAIN ON with the query number after the ON parameter.
EDA1552 INTERFACE DEFAULT DATE TYPE - %1%2%3%4
This setting shows the default date that the interface will supply for MODIFY procedures on fields with an ACTUAL attribute of DATE. If the setting is NEW, the default is 1900-12-31. If it is OLD, the default is 1901-01-01. Issue the SQL SET DEFDATE command to change this setting.
EDA1553 STATIC SQL: NOTHING TO COMPILE IN THIS FOCEXEC %1%2%3%4
EDA1554 MFD '%1' couldn't be overwritten by CREATE SYNONYM
EDA1555 Invalid statement for MODEL option: %1%2%3%4
CREATE SYNONYM
EDA1556 Wrong output mode for EXECUTE %1%2%3%4
EDA1557 Extra tokens found for SQL Translator after SQL
EDA1558 Wrong command sequence: %1%2%3%4
Comes from DQPARSE
EDA1559 Wrong BLOB/CLOB field or it's already fetched: %1%2%3%4
Comes from DQPARSE
EDA1560 %1: WRITING ERROR
EDA1561 %1: ERROR IN PARAMETERS LIST
EDA1562 %1: FILE %2 NOT FOUND
EDA1563 %1: %2 COULDN'T BE OVERWRITTEN
EDA1564 ERROR IN DB2 CUBE VIEWS METADATA
This error message is produced when an attempt to read metadata information about a cube from DB2 CUBE VIEWS via db2info.md_message resulted in an error. This message is accompanied with DB2 error message describing the details of error.
EDA1565 Syntax error: SYNONYM command for '%1' doesn't have a proper END.
EDA1566 REFRESH SYNONYM: '%1'. SYNONYM COULD NOT EXCEED 8 CHAR.
EDA1567 CREATE SYNONYM: DATASOURCE '%1' IS NOT UNIQUE.
EDA1568 DATASOURCE %1 FOR SYNONYM IS NOT FOUND
EDA1569 SYSTEM COMMANDS DISABLED. CAN NOT EXECUTE %1
EDA1570 DIRECT PASSTHRU DISABLED ON THIS SERVER.
EDA1571 MISUSE OF QUOTES IN A LITERAL FOR %1%2%3%4
EDA1572 STATIC SQL/DB2 plan used.
Indicates that STATIC SQL/DB2, prepared by command COMPILE and bound, is now in use.
EDA1573 REFERENTIAL INTEGRITY VIOLATION - PARENT KEY NOT FOUND
A WRITE operation attempted to place a value in a foreign key of the object table; however, this value was not equal to the value of the primary key of some row of the parent table. This violation causes the MODIFY or MAINTAIN transaction to be rejected, but the procedure continues.
EDA1574 reserved for ibm sql: db2/sqlds %1%2%3%4
EDA1575 AUTODISCONNECT ON END OF COMMAND NOT PERFORMED FOR INTERFACE %1
Autodisconnect on the end of a command (such as TABLE, MODIFY, MAINTAIN or immediate END SESSION etc.) could not be performed because of an uncommitted Logical Unit of Work or unallocated cursor or statement.
EDA1576 INSTHOME %1%2%3%4
EDA1577 DB2INSTANCE %1%2%3%4
EDA1578 SAP/R3 INTERFACE LDB ACCESS CONFLICTS WITH %1%2%3%4
EDA1579 SAP/R3 INTERFACE RUN IN BATCH MODE CONFLICTS WITH %1%2%3%4
EDA1580 SAP/R3 USE SAPGUI MODE IS - : %1%2%3%4
EDA1581 - EDA1583 reserved for ibm sql: db2/sqlds %1%2%3%4
EDA1584 ERROR IN SET COMMAND FOR SAP/R3 INTERFACE %1%2%3%4
EDA1585 SAP/R3 INTERFACE BAPI ACCESS CONFLICTS WITH %1%2%3%4
EDA1586 SAP/R3 INTERFACE QUERY ACCESS CONFLICTS WITH %1%2%3%4
EDA1587 NO SELECTION SPECIFIED FOR SAP/R3 QUERY ACCESS
There is no WHERE/IF condition specified for "VARIANT" and READLIMIT is equal to zero.
EDA1588 WARNING: MORE THAN ONE AGGEREGATOR DEFINED FOR MEASURE %1%2%3%4
This is a limitation on the current implementation of the DB2 CUBE VIEWS interface. More than one aggregation function was defined directly or indirectly for a MEASURE element. No field for this measure was generated in MFD.
EDA1589 NON-UNIQUE OBJECT %1 OF TYPE %2
This is a limitation of the current implementation of the DB2 CUBE VIEWS interface. More than one object of the indicated type and name were defined within a corresponding scope. No synonym can be generated for the cube.
EDA1590 INCOMPLETE RECORD FOR ACCESS FILE %1
Access file for CUBE IEW interface must contain all of the CONNECTION=, CUBENAME= and SCHEMA= attributes attached to the top segment. Run CREATE SYNONYM.
EDA1591 WARNING: CUBE HIERARCHY %1 REFERENCES RECURSIVE HIERARCHY
Recursive hierarchies are not supported in the current release of DB2 CUBE VIEWS Interface. No segment for that hierarchy was generated in MFD.
EDA1592 MEASURE FIELD %1 HAS A MULTIPLE PARAMETER AGGREGATOR
DB2 CUBE VIEWs Interface allows using measure fields with multiparameter aggregators (such as CORRELATION etc.) only as aggregation objects such as WRITE. They cannot be referenced in a WHERE or BY clause.
EDA1593 NON-SQLIZABLE IF/WHERE CONDITION
Table request contains IF and/or WHERE condition which cannot be passed to SQL. Current version of DB2 CUBE VIEWS Interface doesn't support such requests.
EDA1594 UNSUPPORTED TYPE OF JOIN
Current version of DB2 CUBE VIEW Interface doesn't support ALL=ON or ALL=PASS settings or ALL.field constructs. Recursive hierarchies are not supported in the current release of DB2 CUBE VIEWS Interface. No segment for that hierarchy was generated in MFD.
EDA1595 DYNAMIC JOIN CANNOT BE USED DB2 CUBE VIEWS
Interface doesn't support dynamic joins.
EDA1596 MFD CONTAINS NO HIERARCHIES
Corrupted MFD for DB2 CUBE VIEW. Run CREATE SYNONYM.
EDA1597 FIELD REFERENCED BY "WITHIN=" KWD NOT FOUND %1
Corrupted MFD for DB2 CUBE VIEW. Run CREATE SYNONYM.
EDA1598 EACH "WITHIN" KEYWORD MUST REFERENCE A DIFFERENT FIELD %1
Corrupted MFD for DB2 CUBE VIEW. Run CREATE SYNONYM.
EDA1599 CYCLICAL HIERARCHY %1
Corrupted MFD for DB2 CUBE VIEW. Run CREATE SYNONYM.
EDA1600 MORE THAN ONE HIERARCHY WITH THE SAME NAME %1
Corrupted MFD for DB2 CUBE VIEW. Run CREATE SYNONYM.
EDA1601 INTERNAL ERROR IN EJB INTERFACE %1%2%3%4
EDA1602 ERROR CONNECTING TO JAVA SERVER %1%2%3%4
EDA1603 FAILED TO SEND DATA TO JAVA SERVER, NODE : %1%2%3%4
EDA1604 FAILED TO RECEIVE DATA FROM JAVA SERVER, NODE : %1%2%3%4
EDA1605 FAILED TO START JAVA CLASS : %1%2%3%4
EDA1606 FAILED TO SEND COMMAND TO JAVA SERVER : %1%2%3%4
EDA1607 FAILED TO GET RESPONSE FROM JAVA SERVER FFOR COMMAND : %1%2%3%4
EDA1608 SYNONYM %1 ALREADY EXISTS; USE DROP SYNONYM TO DELETE IT
EDA1609 I/O ERROR WRITING MASTER FILE %1
EDA1610 - EDA1624 reserved for EJB %1%2%3%4
EDA1625 SYNONYM %1 RESERVED FOR SYSTEM USE
EDA1626 UNDECLARED SERVER %1 REFERENCED FOR EJB INTERFACE
Servername in ACX file attribute SERVER= or in CREATE SYNONYM command AT or in SET DEFAULT_CONNECTION has not been declared by SET USER command or in CFG file.
EDA1627 INVALID SYSTEM FILE %1 FOR EJB INTERFACE
EDA1628 - EDA 1629 reserved for EJB %1%2%3%4
EDA1630 ERROR IN THE QUERY:
EDA1631 MORE THAN ONE IF/WHERE TEST FOR FIELD %1
EDA1632 NO IF/WHERE TESTS SPECIFIED FOR KEY PARAMETERS
EDA1633 KEY PARAMETERS NOT COVERED WITH IFS OR JOINS
EDA1634 INVALID FOREIGN KEY VALUE FOR PARAMETER %1, ONLY NULL IS ALLOWED
EDA1635 EJB INVOKE STATEMENT NOT GENERATED
EJB statement was not generated by the interface for one of the following reasons: not enough memory in the region to build the statement in, or the length of the statement would exceed 32K (the interface limit).
EDA1636 reserved for EJB %1%2%3%4
EDA1637 EJB OPENC CATALOG ERROR %1%2%3%4
EDA1638 EJB READING CATALOG DATA ERROR %1%2%3%4
EDA1639 EJB CLOSE CATALOG ERROR
EDA1640 EJB INVOKE ERROR %1%2%3%4
EDA1641 - EDA1642 reserved for EJB %1%2%3%4
EDA1643 EJB READING DATA ERROR %1%2%3%4
EDA1644 EJB CLOSE ERROR %1%2%3%4
EDA1564 - EDA1646 reserved for EJB %1%2%3%4
EDA1647 UNCOMPARABLE ACTUAL/USAGE FORMATS FOR DATETIME FIELD %1%2%%3%4
EDA1648 INVALID FORMAT FOR DATETIME FIELD %1%2%3%4
EDA1649 OPERATION INTERRUPTED DUE TO HEAVY QUIT %1%2%3%4
EDA1650 RETRIEVAL KILLED DUE TO HEAVY QUIT %1%2%3%4
EDA1651 INTERNAL ERROR IN ORACLE INTERFACE %1%2%3%4
EDA1652 CHARACTER TYPE FOR INSERT OR UPDATE - %1%2%3%4
The message reflects the results of the last SET ORACHAR VAR/FIX command. VAR means that outgoing character data will be described at bind time as VARCHAR2 Oracle data type. As a result, trailing blanks will be truncated when stored into the Oracle table. FIX prevents that truncation.
EDA1653 CONVERSION STYLE FOR ORACLE NUMBERS - %1%2%3%4
The message shows the results of the oranumber setting that determines which standard SQL types are used for mapping Oracle NUMBER type of different precision and scale. DECIMAL implies using DECIMAL type where possible, COMP implies upwardly compatible behavior.
EDA1654 ORACLE HOME - %1%2%3%4
EDA1655 ORACLE SID - %1%2%3%4
EDA1656 DEFAULT SERVER NAME - %1%2%3%4
EDA1657 USER NAME ON DEFAULT SERVER - %1%2%3%4
EDA1658 TIMEOUT FACTOR FOR RUNAWAY COMMANDS - %1%2%3%4
EDA1659 LOGIN TIMEOUT - %1%2%3%4
EDA1660 HOST NAME - %1%2%3%4
EDA1661 DATABASE NAME - %1%2%3%4
EDA1662 HOME - %1%2%3%4
EDA1663 INVALID VALUES IN SET CONVERSION COMMAND FOR %1 INTERFACE
EDA1664 ORACLE NODE - %1%2%3%4
EDA1665 UNSUPPORTED DATA TYPE IN ORACLE INTERFACE %1%2%3%4
The ORACLE CLI interface does not support some new data types, like CLOB/BLOB. To access these data types, switch to the Oracle OCI interface.
EDA1665 - EDA1670 reserved for oracle %1%2%3%4
EDA1671 SET SERVER %1 COMMAND FOR %2 INTERFACE OUT OF SEQUENCE
Before using a SET SERVER command, the corresponding server with its logon attributes (for example, user and password) must be declared by a SET USER command.
EDA1672 SYNTAX ERROR IN SET USER CONNECTION ATTRIBUTES FOR %1 INTERFACE
See documentation for the proper syntax of SET CONNECTION_ATTRIBUTES command for this interface.
EDA1673 MISPLACED SERVER ATTRIBUTE SETTINGS FOR %1 INTERFACE
The SET USER, SET SERVER, or SET PASSWORD command is issued against a previously declared server when there is an active Logical Unit of Work (LUW). Execute COMMIT/ROLLBACK to finish the LUW, and then reissue the command.
EDA1674 MISPLACED HOST OR HOME SPECIFICATION FOR %1 INTERFACE
Attempt to change the HOME setting while there are open connections.
EDA1675 OUT OF SEQUENCE SERVER REFERENCE FOR %1 INTERFACE
At least one server with its logon attributes (for example, user and password) must be declared by a SET USER command before issuing a SET PASSWORD or SQL command.
EDA1676 UNRECOGNIZED SET COMMAND FOR %1 INTERFACE
EDA1677 UNDECLARED SERVER "%1" REFERENCED FOR %2 INTERFACE
SERVER= attribute in an access file, or AT servername in a CREATE SYNONYM command, references a server that has not been previously declared by a SET USER command.
EDA 1678 USER ID AND PASSWORD UNAVAILABLE FOR PASSING THRU FOR %1
The SET CONNECTION _ATTRIBUTES command that has been entered specifies PASSWORD PASSTHRU mode. However, iWay user credentials are unavailable for passing to the DBMS engine.
EDA1679 SERVER %1, USER ID %2, STATUS %3
One or more of these messages list all the servers "declared" by SET USER command(s). STATUS ACTIVE means that there is either an uncommitted Logical Unit of Work or at least one cursor or command open or prepared on the connection associated with this server.
EDA1680 SERVERS DECLARED FOR %1 INTERFACE:
EDA1681 reserved for oracle %1%2%3%4
EDA1682 MISMATCHING CUBE METADATA INFORMATION
Metadata information stored in MFD doesn't correspond to current information obtained from DBW CUBE VIEW catalogs. Run CREATE SYNONYM to update the MFD.
EDA1683 reserved for oracle %1%2%3%4
EDA1684 USE OF PRINT OR LIST IS NOT ALLOWED IN THIS CONTEXT
The DB2 CUBE VIEWS Interface supports PRINT/LIST only in reports that print or list dimension information such as dimension attributes.
EDA1685 STORED PROCEDURE DOESN'T EXIST OR PARAMETERS DO NOT MATCH
Attempt to run with parameters non-existing stored procedure or retrieve the value of a stored procedure parameter which is input-only.
EDA1686 CANNOT READ STORED PROCEDURE OUTPUT PARAMETERS FOR THIS DBMS
EDA1687 CANNOT RUN REPORT WITH MORE THAN ONE VERB SET
The DB2 CUBE VIEWS Interface supports only single verb set reports (except for reports on dimension attributed). One of the cases of multiple verb set reports is the Financial Modeling Language (FML).
EDA1688 AN EXPRESSION CANNOT BE CONVERTED TO SQL: %1
When processing reports that reference cube measures the DB2 CUBE VIEWs Interface has to create a fully aggregated SQL SELECT statement. Pressure of non-SQLizable expressions prevents the report from being processed.
EDA1689 INCORRECT DEFINE %1 REFERENCING A MEASURE
Only simple redefines (p.e. those that just change the format) are supported by DB2 CUBE VIEWS Interfacde as objects of aggregatoin operators if they reference a cube measure.
EDA1690 CANNOT WRITE FROM MEASURE %1 WITH MULTIPLE AGGREGATORS
DB2 CUBE VIEWS Interface currently does not support using measures with different aggregators on different dimensions as aggregation objects.
EDA1691 REPORT WITH NO MEASURE REFERENCES MORE THAN ONE DIMENSION
Currently, a report that references attributes of more than one dimension, must also reference at least one on the cube measures.
EDA1692 SAP/R3 INTERFACE UNSUPPORETED IF CONDITION FOR BAPI INPUT PARMS%2%3%4
The only supported IF condition is EQ with single test value.
EDA1693 BAPI INPUT PARAMETER CAN NOT BE REFERENCED IN VERB OR KEYS %1%2
Input Parameters for the special BAPI for LDB Dynamic execution can not be referenced in verbs or keys.
EDA1694 WARNING: SAP/R3 INTERFACE STATIC MODE IGNORED FOR %1%2%3%4
The current setting DYNAMIC=OFF will be ignored and ABAP/4.
EDA1698 TERADATA PASSWORD EXPIRED FOR DATASOURCE %1, USER %2%3%4
EDA1699 SYNTAX ERROR IN SET NEWPASSWORD COMMAND FOR %1 INTERFACE
See documentation for the proper syntax of SET NEWPASSWORD command for this interface.
EDA1700 CANNOT FIND REFERENCED DATA SOURCE %1 FOR %2 INTERFACE
The last command referenced a data source not previously identified by a SET USER or SET CONNECTION_ATTRIBUTES command.
EDA1701 CURRENT ODBC INTERFACE SETTINGS ARE : %1%2%3%4
EDA1702 ODBC SOURCE IS - %1%2%3%4
EDA1703 ODBC USER IS - %1%2%3%4
EDA1704 ODBC TIMEOUT IS - %1%2%3%4
EDA1705 ODBC SQL_ANSI_TO_OEM - %1%2%3%4
EDA1706 ODBC CONCUR IS - %1%2%3%4
EDA1707 ODBC ISOLATION IS - %1%2%3%4
EDA1708 %1%2%3%4
This contains information returned by SQLGetInfo() call.
EDA1709 NCHAR OPTION IS - %1%2%3%4
This message specifies whether single-byte character set (SBCS) or double-byte character set (DBCS) mode is being used.
EDA1710 EXTENDED SECURITY IS - %1%2%3%4
The message shows whether the extended security feature of the EDA API has been turned on. This feature is defined by the EDASET variable EDA_VAR_EXTENDSEC.
EDA1711 ODBC AUTODISCONNECT OPTION IS - %1%2%3%4
EDA1712 ODBC COLNAME IS - %1%2%3%4
EDA1713 ODBC UPPER IS - %1%2%3%4
EDA1715 MACRO MODE IS - %1%2
EDA1714 RDBMS ENVIRONMENT NOT PROPERLY INITIALIZED
The RDBMS API could not be initialized, possibly due to an erroneous value in an environment variable.
EDA1717 INVALID VALUE %1 FOR SET OPTION %2
The value specified for the given SET option is invalid. Please specify a valid value.
EDA1721 WARNING: COULD NOT SET ISOLATION LEVEL FOR %1%2
An active Logical Unit of Work exists for the given data source, therefore could not set isolation level. Please make sure that all LUWs are closed on all active connections and retry to setting the isolation level.
EDA1722 WARNING: COULD NOT SET TRANSACTION MODE FOR %1%2
EDA1723 TRANSACTION MODE IS - %1%2
EDA1724 - EDA1750 reserved for supra sql %1%2%3%4
EDA1726 JDBC SOURCE IS - %1%2%3%4
EDA1727 JDBC USER IS - %1%2%3%4
EDA1728 JDBC ISOLATION IS - %1%2%3%4
EDA1729 JDBC AUTODISCONNECT OPTION IS - %1%2%3%4
EDA1742 CREATE SYNONYM: "FOREIGNKEYS" INVALID FOR NON CURRENT DATABASE %1%2%3%4
Create Multisegment Synonym based on FK/PK Info for Informix can be done only for the current connected database.
EDA1743 CREATE SYNONYM: "FOREIGNKEYS" IS UNSUPPORTED FOR ENGINE %1
Create Multisegment Synonym based on FK/PK Info is unsupported for the given SQL engine.
EDA1744 CREATE SYNONYM: "FOREIGNKEYS" REQUIRES SCHEMA NAME
Create Multisegment Synonym based on FK/PK Info requires schema name to be specified either within Object Name or Schema Parameters.
EDA1745 CREATE SYNONYM: "FOREIGNKEYS" IS UNSUPPORTED FOR BASIC SYNONYM
Create Multisegment Synonym based on FK/PK Info is unsupported in BASIC SYNONYM mode.
EDA1746 JCL for deferred BIND execution generated in dataset %1%2%3%4
EDA1747 ERROR ALLOCATING DATASET %1%2%3%4
EDA1748 ERROR OPENING DATASET %1%2%3%4
EDA1749 ERROR WRITING TO DATASET %1%2%3%4
EDA1750 ERROR CLOSING DATASET %1%2%3%4
EDA1751 INFORMIXDIR %1%2%3%4
EDA1752 INFORMIXSERVER %1%2%3%4
EDA1753 SYBASE %1%2%3%4
EDA1754 DSQUERY %1%2%3%4
EDA1755 CURSORS TYPE IS - %1%2
EDA1756 CURRENT IDMS DICTIONARY IS - %1%2%3%4
EDA1757 CURRENT SCHEMA IS - %1%2%3%4
EDA1758 CURRENT ISOLATION LEVEL IS - %1%2%3%4
EDA1759 UNIFY SEPARATOR - %1%2%3%4
EDA1760 READ ONLY CLAUSE OPTION - %1%2%3%4
EDA1763 IF-THEN-ELSE OPTIMIZATION IS -%1%2%3%4
EDA1777 INFORMIX ANSI DB %1%2%3%4
EDA1801 %1
EDA1802 FATAL PARSE ERROR. LOOP DETECTED:
EDA1803 FATAL PARSE ERROR. INSUFFICIENT MEMORY.
EDA1804 FATAL PARSE ERROR. HASH VECTOR ERROR.
EDA1805 FATAL PARSE ERROR. SYMBOL TOO LONG FOR INTERNAL BUFFER.
EDA1806 FATAL PARSE ERROR. FROM GETLINE:
EDA1807 FATAL PARSE ERROR. FROM SETEOL:
EDA1808 FATAL PARSE ERROR. FILE NOT FOUND:
EDA1809 FATAL PARSE ERROR. BAD FUNCTION POINTER:
EDA1810 EXTERNAL SORT NOT FOUND:
Under VM, FOCUS or EDA tried to locate the external sort but could not do so. Verify that any TXTLIBs required for the sort product are available. See also "Solutions for a EDA909--Critical Error in External Sort"--using "Knowledge Base Search" on support.ibi.com.
EDA1811 FATAL PARSE ERROR. ISS OVERFLOW.
EDA1812 FATAL PARSE ERROR. PST OVERFLOW.
EDA1813 FATAL PARSE ERROR. ERR OVERFLOW.
EDA1814 FATAL PARSE ERROR. AST OVERFLOW:
EDA1815 FATAL PARSE ERROR. OUT OF CORE FOR AST:
EDA1816 FATAL PARSE ERROR. SYM OVERFLOW:
EDA1817 FATAL PARSE ERROR. OUT OF CORE FOR SYM:
EDA1818 FATAL PARSE ERROR. TSS BUFFER POINTERS EXHAUSTED.
EDA1819 FATAL PARSE ERROR. TSS OVERFLOW. SYMBOL LARGER THAN BUFFER
EDA1820 %1 COULD NOT BE LOADED
The module indicated (usually XSBEG), which FOCUS or EDA uses to invoke external sort, cult not be loaded. Confirm that FOCUS/EDA was generated properly and that library containing this module is available.
EDA1821 THE FOLLOWING ARE VALID TOKENS:
EDA1822 WARNING. INVALID SYMBOL:
A symbol in the Master File is not recognized. Please consult the documentation for a description of all valid Master File attributes.
EDA1823 ERROR. ILLEGAL SYMBOL:
EDA1824 DELETING THE FOLLOWING SYMBOL:
EDA1825 INSERTING NEW SYMBOL BEFORE OLD SYMBOL:
EDA1826 REPLACING OLD SYMBOL WITH NEW SYMBOL:
EDA1827 NOTE: REST OF LINE IGNORED.
EDA1828 NOTE: YOU MAY RETYPE THE ERRONEOUS PART OF THE LINE.
EDA1829 WARNING. FIELDNAME IS NOT UNIQUE WITHIN A SEGMENT:
Two fields in a segment have the same field name and alias. To avoid this warning message, rename the name or alias in the Master File.
EDA1830 NAME OF INDEX FIELD OR TEXT FIELD EXCEEDS 12 CHARACTERS:
For FOCUS, the file field name of an index field or text field is restricted to 12 characters. You must change your Master File.
EDA1831 TAGNAME OR FILENAME IS DUPLICATED IN THIS JOIN/COMBINE:
TAG name cannot be the name of some other file in this join (except the file name it is tagged to). TAG names must be unique within a JOIN or COMBINE. Only one TAG name is permitted per host file.
EDA1832 TAG AND PREFIX CANNOT BE USED TOGETHER IN COMBINE
EDA1833 NAME OF SEGMENT IN FOCUS FILE EXCEEDS 8 CHARACTERS:
For FOCUS files, the segment name is restricted to 8 characters. You have to change your Master File.
EDA1834 INVALID LANGUAGE VALUE SPECIFIED
LANGUAGE parameter should be set with language code or language name. Issue '? LANG' or 'HELP LANG' commands to refer to a list of valid language codes, names and their abbreviations.
EDA1835 VALID VALUES ARE SHIFT = ON, OFF, LEFT, YES OR NO
If SHIFT=OFF(default), padding characters belong on shift-codes location. If SHIFT=ON, no padding characters are used. If SHIFT= LEFT, padding characters are located at the end of the field. You can see shift-codes themselves by using SHIFT=YES.
EDA1836 INVALID TERM VALUE SPECIFIED
For more information, issue '? LANG' or 'HELP LANG' commands to see a list of valid language codes, names and their abbreviations.
EDA1837 DUPLICATE INDEXED FIELDNAMES ARE NOT ALLOWED:
No two fields with the same field name can be indexed within the same Master File. Rename one field or make only one indexed.
EDA1838 SMARTMODE UNAVAILABLE TO COLLECT FOR DATABASE: %1
The databases required for SmartMode collection are unavailable at this time. Contact your DBA.
EDA1839 DO YOU WISH TO CONTINUE THIS QUERY? (RESPOND Y OR N)>
The SmartMode governor determined that your TABLE request will be expensive. Respond with Y to continue with the request. All other responses will cancel the request.
EDA1840 THIS HIPERFOCUS OPTION IS LOCKED BY THE INSTALLATION
EDA1841 FORMAT ERROR. INVALID K FORMAT VALUE:
K Format should start with SO and end with SI. The data filled with all blanks can be converted to K Format. SBCS trailer blanks also are convertible to DBCS trailer blanks. K Format is treated as the GRAPHIC field of DB2.
EDA1842 ERROR IN THE K FORMAT DEFINITION OF FIELD:
The number of characters of FORMAT=Amm corresponding to ACTUAL=Knn should be calculated with the following formula:mm = nn x 2 + (the length of shift code) x 2.
EDA1843 WARNING.. SMARTMODE COST CANNOT BE DETERMINED.
The cost of the TABLE request could not be determined by SmartMode; however, the DBA instructed SmartMode to run all requests for which a cost could not be determined.
EDA1844 WARNING.. SMARTMODE UNAVAILABLE - INFORM DBA.
The database table required for the SmartMode subsystem is not available. SmartMode is be unable to process requests. Please inform your System Administrator.
EDA1845 WARNING.. SMARTMODE KNB UNAVAILABLE - INFORM DBA.
The knowledgebase that SmartMode governor needs for estimation is not available. SmartMode will be unable to govern this query. Please inform your System Administrator.
EDA1846 %1
SmartMode custom message. Please contact your database or system administrator for the specific explanation.
EDA1847 DECIMAL OVERFLOW EXCEPTION
An attempt to perform a decimal arithmetic operation has occurred, and has surpassed the hardware magnitude limit. The cause of the error is indeterminate; it may be due to input of binary data that bypasses the normal character checking operation.
EDA1848 DECIMAL DIVIDE EXCEPTION
An attempt to perform a decimal division has occurred, and has diverged from the requirements of such division. The cause of the error is indeterminate; it may be due to input of binary data that bypasses the normal character checking operation.
EDA1849 Database :%1: is currently in use. Maintain Terminated.
EDA1850 MISMATCH IN NUMBER OF FILES IN COMPONENT OF CONCATENATION
There must be either exactly one cross-referenced file, or one cross-referenced file per host file throughout the concatenated structure.
EDA1851 DUPLICATE DASH REPEAT LABEL
Each label can be referenced in a single dash repeat statement.
EDA1852 OPTION ASQ. NOT ALLOWED FOR PACKED FIELDS:
Squaring a packed field may often exceed hardware limitations. Therefore, the ASQ option may not be applied to packed fields.
EDA1853 CNT/SUM/AVE.DST CAN ONLY BE USED WITH AGGREGATION VERBS
EDA1854 THE DST OPERATOR IS ONLY SUPPORTED IN TABLE REQUESTS
EDA1855 DISTINCT FIELDS MUST PRECEDE THE NONDISTINCT ONES
EDA1856 ONLY ONE DISTINCT FIELD IS ALLOWED IN AGGREGATION
EDA1857 WARNING: NO MATCHING FOR FIELD OF SUBREQUEST:
EDA1858 MULTI-LINE/EMBEDDED LET'S NOT SUPPORTED IN AUTOINDEX
EDA1859 MULTI-LINE/EMBEDDED LET'S NOT SUPPORTED WITH "MORE"
EDA1860 THE NUMBER OF DISPLAY PATH IS DIFFERENT BETWEEN REQUESTS
EDA1861 MULTI-PATH PRINT IS NOT SUPPORTED IN UNIVERSAL CONCAT
EDA1862 REFORMAT DST.FIELD IS NOT SUPPORTED WITH PRINT
In order to PRINT distinct values of a field, FOCUS changes the field into a BY field. FOCUS does not allow a BY field to be reformatted. Hence, DST.FIELD in PRINT is not supported.
EDA1863 MASTER FILE USED IN COMBINE HAS NO SEGMENT:
The Master File has no SEGMENT specified. This is not allowed in a MODIFY when MASTER=OLD. To do this, set MASTER=NEW.
EDA1864 THE DST OPERATOR IS NOT SUPPORTED WITH ACROSS/FOR/NOSPLIT
EDA1865 ERROR: WHERE CLAUSE IN USE COMMAND YIELDS EMPTY SET
Conditions specified for the fields in the WHERE clause of a USE command are contradictory, for example: USE car1 focus a AS car WHERE seats = 5 AND seats FROM 7 TO 10.
EDA1866 WARNING. ONE DBCS CHARACTER MAY BE TRUNCATED:
The number of characters of FORMAT=Amm corresponding to ACTUAL=Knn is less two bytes according to the following formula: mm = nn x 2 + 2. This normally happens in HOLD files.
EDA1867 DST OPERATOR MUST BE AT THE LOWEST LEVEL OF AGGREGATION
EDA1868 LOCATION IS NOT SPECIFIED FOR THE FLD WITH MD_EXTERNAL: %1
The LOCATION attribute is mandatory for all fields defined with INDEX MD_EXTERNAL.
EDA1869 ERROR: SECTION CAN'T PRECEDE CLASS SPECIFICATION
A SECTION specification cannot appear before a CLASS specification that the SECTION is a part of.
EDA1870 LOCATION IS ALLOWED ONLY ON TEXT FLDS OR INDEXED FLDS: %1
The LOCATION attribute can only be used with TEXT fields (FORMAT=TXnnn) or with fields that have an INDEX specified.
EDA1871 ERROR: CLASS CAN'T HAVE SECTION AS A PARENT: %1
It is not permitted to specify a PARENT attribute of a CLASS using the name of a SECTION as a value. SECTIONs cannot have child attributes.
EDA1872 THE DST OPERATOR IS NOT SUPPORTED WITH TEXT FIELDS
Since the DST field is changed into a BY field during retrieval and TEXT fields cannot be used as BY fields, the DST operator cannot be used with TEXT fields.
EDA1873 JOINED MASTER FILE IS NOT FOUND: %1
In FUSION, embedded JOINs are allowed as well as external ones. This message occurs when an embedded JOIN refers to a Master File Description that cannot be found.
EDA1874 ERROR: CURRENT & ORIGINAL SCHEMAS CAN'T BE RECONCILED
In the AS clause of the USE command, users cannot specify current and original Master File Description names. The original logical schema can not be mapped to the current one.
EDA1875 LOCATION IS NOT SPECIFIED FOR THE FIELD WITH DATASET: %1
DATASET specification on a field level requires a LOCATION to associate physical data with a logical name.
EDA1876 LOCATION IS NOT SPECIFIED FOR THE SEGMENT WITH DATASET: %1
DATASET specification on a segment/class level requires LOCATION to associate physical data with a logical name.
EDA1877 LOCATION WITH DATASET; INCONSISTENT DATASET VALUE FOR: %1
Multiple segments in a structure can specify the same LOCATION name. These LOCATION attributes cannot point to multiple DATASET values. This also applies to cross-referenced segments pointing to the same cross-referenced file.
EDA1878 JOIN_TO FIELD IS NOT FULLY QUALIFIED: %1
Embedded JOIN in FUSION requires at least one qualifier before a join_to field name. This qualifier is interpreted as a file name. USAGE: JOIN_TO FileName. <ClassName> FieldName
EDA1879 ERROR: UNSUPPORTED INDEX TYPE FOR DEFINED FIELD
The index specified for DEFINEd field must be EXTERNAL or MD_EXTERNAL. In both cases, INDEX specification should be accompanied by a LOCATION.
EDA1880 NOT FULLY QUALIFIED INDEX SPECIFICATION FOR DEFINED FIELD
LOCATION becomes a mandatory attribute for a DEFINEd field if an INDEX is specified for this DEFINE.
EDA1881 LOCATION IN DEFINE FIELD IS INCONSISTENT WITH PREV SPEC
Index LOCATION in DEFINEd field should be consistent with all previous references to this name.
EDA1882 ERROR: REDEFINITION OF AN ATTRIBUTE IN DEFINE STATEMENT
All attributes in DEFINE statements are allowed to be specified only once for the given DEFINED name.
EDA1883 USE WHERE: PARSE OF WHERE CLAUSE FAILED FOR %1
Current USE command aborted. No new USEs were added.
EDA1884 ACTUAL FIELDTYPE MUST MATCH USAGE : %1
For BLOB/CLOB field types, the USAGE and ACTUAL attributes must match.
EDA1885 WARNING: MODIFY USES CENTURY INFO. WILL NOT RUN BELOW 7.0.6
The user has set Year 2000 information that relates to fields in this MODIFY, and should be aware that MODIFYs compiled with such information will not run in versions of FOCUS prior to 7.0.6.
EDA1886 ERROR: %1 FOCCOMP NEEDS CENTURY INFO. PLEASE RECOMPILE.
The user is using the Project 2000 feature, which affects some fields in the named compiled MODIFY. To prevent entry of inconsistent data, we require that the user recompile their MODIFY.
EDA1887 CENTURY: NEED BOTH DFC AND YRT ON LEFT SIDE OF EXPRESSION
If one wants to use century specification on the left hand side of an expression, a) both must be given, b) they must immediately follow the format, and c) they must be in the order DFC then YRT.
EDA1888 INVALID MASTER NAME %1
The name of the master is invalid. Check the length and characters used.
EDA1889 UNABLE TO ISSUE FOCDEF FOR FILE %1
A system FOCDEF could not be set. Check for a valid path name and/or file name.
EDA1890 DATASET FORMAT INVALID %1
Data sets are operating system dependent file names. Check the format of the file name.
EDA1891 HLI SERVER NAME INVALID %1
Check the name of the ID for the HLI server.
EDA1892 FILE NOT FOUND : %1
Check the name and make sure that the file exists in the correct location.
EDA1893 FILE TABLE SYSTEM ERROR
EDA1894 INVALID LOCATION NAME %1 FOR MASTER %2
Check the Location name.
EDA1895 BLOB/CLOB FIELDS ARE NOT SUPPORTED IN TABLE REQUEST
BLOB/CLOB fields cannot be used in a TABLE request
EDA1896 (WARNING ONLY) YEAR 2000 ATTRIBUTES NOT SUPPORTED
EDA1897 FATAL ERROR DURING POOLED TABLES RETRIEVAL. FOCUS TERMINATING.
An error was encountered in a report during Pooled Tables retrieval. FOCUS cannot recover from this error and will return to the host environment.
EDA1898 REUSABLE (BUT NON-REENTRANT) SORT MODULE NOT SUPPORTED
The module SORT is marked REUS but not RENT. This is incompatible with certain FOCUS environments that use simultaneous execution of SORT. SyncSort Early Warning Notice EW5140-0 shows how to replace module SORT with a copy that is not marked REUS.
EDA1899 LOAD OF %1 (EXTERNAL-SORT MODULE) UNDER %2 FAILED
FOCUS/EDA ws unable to bring the external-sort module into memory. If under FM, LOAD failed. If under MVS or MVS/OE, LINK failed. Make the libraries containing the external sort available and retry.
EDA1900 NOT ENOUGH MEMORY FOR EXTERNAL SORT
In preparation for an external sort, available memory was queried. Not enough memory is available for an external sort. Increase memory and execute the request again.
EDA1901 RECORD LENGTH %2 FOR FILE %1 EXCEEDS 32K
EDA1902 ERROR ALLOCATING FILE: %1 REASON: %2
EDA1903 ERROR ESTABLISHING DCB PARAMETERS FOR FILE: %1 REASON: %2
EDA1904 ERROR OPENING FILE: %1 REASON: %2
EDA1905 ERROR WRITING TO FILE: %1 REASON: %2
EDA1906 ERROR READING FROM FILE: %1 REASON: %2
EDA1907 MEMORY ALLOCATION FAILURE IN %1
EDA1908 NAME OF DIMENSION EXCEEDS 66 CHARACTERS: %1
EDA1909 MAXIMUM NUMBER OF WITHIN STATEMENTS IS 300
EDA1910 UNABLE TO LOAD %1
EDA1911 CURRENCY IN FILE DESCRIPTION NOT FOUND IN DATA
EDA1912 ERROR IN PARSING CURRENCY STATEMENT
EDA1913 PARSER ERROR: INVALID TOKEN %1
The ENCRYPT keyword takes either ON or OFF as a value.
EDA1914 PARSER ERROR: INVALID TOKEN %1
The MISSING keyword takes either ON or OFF as a value.
EDA1915 PARSER ERROR: MDI NAME %1 CONFLICTS WITH DDNAME
An MDI may not share its name with any DDNAME. This includes MASTER FILE NAMEs, JOINed MASTER FILE NAMEs, CLASS LOCATIONs, and INDEX LOCATIONs.
EDA1916 WARNING: DUPLICATE CURRENCY IN FILE %1. FIRST OCCURRENCE TAKEN.
EDA1917 CURRENCY PARSER ERROR: FEATURE NOT SUPPORTED
2nd parameter must be a constant field if the 1st parameter is a non-currency field type.
EDA1918 LINK_TO FIELD IS NOT A VALID CLASSNAME: %1
The LINK_TO clause of a JOIN in FUSION allows an optional Class name after the File name. USAGE: LINK_TO FileName <. ClassName >
EDA1919 ERROR: TEXT FIELD REQUESTED FROM A CONCATENATED DB:
Fields of TEXT format cannot be retrieved from a concatenated FOCUS database.
EDA1920 UNABLE TO ALLOCATE FILE %1 AS %2
System could not allocate the file. Check spelling and file access permissions and try again.
EDA1921 ERROR PARSING DATASET IN MASTER %1: %2
Error occurred while analyzing value of DATASET. Check the master for spelling errors.
EDA1922 FOCUS DATASET INTERNAL ERROR: %1
A serious problem occurred processing FOCUS DATASET.
EDA1923 WARNING: USE COMMAND OVERRIDES DATASET VALUE IN %1
Data set value in master has been overridden by the USE command.
EDA1924 WARNING: ALLOCATION OF %1 OVERRIDES DATASET VALUE IN %1
Data set value in master has been overridden by user's allocation of the ddname.
EDA1925 DATASET ERROR: PHYSICAL NAME SPECIFIED WITH ON CLAUSE
A ddname instead of the physical file name should be used in DATASET when the ON <sinkname> clause is present.
EDA1926 INVALID USE OF KEYSET
The KEYSET keyword may only be used on a top segment that has keys.
EDA1927 REBUILD/OLDCIPHER INTERNAL ERROR: %1
Rebuild encountered an internal error.
EDA1928 REBUILD/OLDCIPHER PARSING ERROR: FILE %1
Rebuild processor failed to parse master file. Check the name and try again.
EDA1929 REBUILD/OLDCIPHER: INVALID DBA PASSWORD FOR FILE %1
You must set valid DBA password before rebuilding a DBA-protected FOCUS/FUSION database.
EDA1930 OBSOLETE CIPHER DETECTED IN FILE:
DBA-protected FOCUS/FUSION file uses obsolete cipher. Use REBUILD/OLDCIPHER command to rebuild the file.
EDA1931 LENGTH OF INDEXED ALPHA FIELD EXCEEDS 256 CHARACTERS:
For FOCUS, file length of indexed alpha field is restricted to 256 characters.
EDA1932 ERROR PARSING MASTER FILE: %1
RESTRICT command failed to parse master file. Check the name and try again.
EDA1933 RESTRICT SYNTAX ERROR: %1
RESTRICT command must be followed by a list of masters to be processed. Each Master must appear on a separate line. The list is terminated by END keyword.
EDA1934 CANNOT RESTRICT NON-FOCUS DATABASE %1
RESTRICT command can be applied to FOCUS/FUSION databases only.
EDA1935 MASTER NAME MUST BE SPECIFIED TO RESTRICT A FUSION DB %1
Physical names for RESTRICT command can be used for FOCUS databases only, and only on CMS. To restrict a FUSION database, specify its master name.
EDA1936 ERROR: PARTITION %1 IS NOT WRITABLE
Make sure that all files that constitute a database to be RESTRICTed are writable (including LOCATION segments).
EDA1937 ERROR: PARTITION %1 IS PROTECTED BY DIFFERENT DBA
You do not have sufficient rights to RESTRICT the database, because it is protected by a different database administrator. Set the correct password and try again.
EDA1938 ERROR: PARTITION %1 NOT FOUND
FOCUS/FUSION can not find the physical partition.
EDA1939 RESTRICT INTERNAL ERROR: %1
RESTRICT command encountered an internal error.
EDA1940 DEFINE FUNCTION name not 1-8 characters: %1
The name given for a DEFINE FUNCTION (the character string following "DEFINE FUNCTION") contains more than eight characters or is null.
EDA1941 DEFINE FUNCTION %1 CLEAR--illegal delimiter
In a "DEFINE FUNCTION dfname CLEAR" command, the character string dfname contains a forward slash, an open or close parenthesis, or a comma; this is not supported.
EDA1942 DEFINE FUNCTION not found: %1
In a "DEFINE FUNCTION dfname CLEAR" command, the syntax is proper but dfname does not exist, so it cannot be CLEARed.
EDA1943 DEFINE FUNCTION needs close paren to delimit params: %1
A DEFINE FUNCTION definition must contain a list of parameters delimited by a close parenthesis. The DEFINE FUNCTION parser encountered END or a similar termination without finding a close parenthesis.
EDA1944 No open paren after DEFINE FUNCTION format: %1
A format may be specified for a DEFINE FUNCTION immediately after the DEFINE FUNCTION name (and a forward slash) and before the open parenthesis enclosing the parameter list. The forward slash is coded, but the next delimiter is not an open parenthesis.
EDA1945 DEFINE FUNCTION format not 1-8 characters: %1
A format may be specified for a DEFINE FUNCTION immediately after the DEFINE FUNCTION name (and a forward slash) and before the open parenthesis enclosing the parameter list. The length of the format specification must be from one to eight characters.
EDA1946 Name of DEFINE FUNCTION not delimited by "/" or "(": %1
The delimiter for the DEFINE FUNCTION name must be a forward slash (if a format specification follows) or an open parenthesis (if there is no format specification). The actual delimiter is neither of these.
EDA1947 DEFINE FUNCTION parameter name not delimited by "/": %1
A format specification must follow each parameter for a DEFINE FUNCTION, and the delimiter that separates the name from the format specification must be a forward slash. The actual delimiter is not a forward slash.
EDA1948 DEFINE FUNCTION parameter name not 1-12 characters: %1
The name of each parameter for a DEFINE FUNCTION must contain from one to twelve characters. Either the parameter name shown is null or it contains more than twelve characters.
EDA1949 DEFINE FUNCTION parameter format not delimited by "," or ")": %1
A format specification must follow each parameter for a DEFINE FUNCTION, and the delimiter that marks the end of the specification must be a comma (if there are additional parameters) or a close parenthesis (if this is the last parameter).
EDA1950 DEFINE FUNCTION parameter format not 1-8 characters: %1
A format specification must follow each parameter for a DEFINE FUNCTION, and it must contain from one to eight characters. Either the actual specification contains more than eight characters or it is null.
EDA1951 Invalid DEFINE FUNCTION parameter format: %1
The format specification given for the parameter shown for a DEFINE FUNCTION is not recognized.
EDA1952 DEFINE FUNCTION %1 is void
At least one computational statement must appear between the parameter list for DEFINE FUNCTION and "END", but the actual DEFINE FUNCTION has no computational statements.
EDA1953 DEFINE FUNCTION name %1 not equal to final assignment name %2
The name immediately following "DEFINE FUNCTION" must match the name on the left-hand side of the final computational statement given for the DEFINE FUNCTION, but it does not match.
EDA1954 DEFINE FUNCTION format %1 not equal to final assignment format %2
The (optional) format specified before the parameters for a DEFINE FUNCTION must match the format on the left-hand side of the final computational statement given for the DEFINE FUNCTION, but it does not match.
EDA1955 DEFINE FUNCTION %1 entered recursively
A DEFINE FUNCTION was invoked, but before returning it was invoked again; this is not supported. Note that the invalid recursive usage may have been indirect: DF1 invokes DF2, which invokes DF3, ... ,which invokes DF1.
EDA1956 DEFINE FUNCTION %1 used after CLEAR or reDEFINE
A DEFINE FUNCTION dfname was invoked, but it no longer exists. A "DEFINE FUNCTION dfname" command was processed subsequently (with or without CLEAR), thereby invalidating any references to the original version of dfname.
EDA1957 Warning--DEFINE FUNCTION %1 superseded; could result in EDA1956
A successful DEFINE FUNCTION dfname has replaced the prior dfname. Trying to use a DEFINE FILE (or another DEFINE FUNCTION) that refers to the prior version of dfname will result in EDA1956. Such a DEFINE FILE/FUNCTION could be reissued, which would direct it to use the new version of dfname.
EDA1958 DEFINE FUNCTION %1 takes %2 parameter(s), but # supplied = %3
DEFINE FUNCTION dfn requires Nexp input parameters, but Nsupp were supplied. dfn, Nexp, and Nsupp are displayed within the message text.
EDA1959 NOSPLIT option is not supported in this request
NOSPLIT and BY TOTAL cannot be used in the same request.
EDA1960 Physical File %1 does not match FDT for the USE list.
EDA1961 MQDEF ERROR: error in operands
An operands in the MQDEF command are missing or too long.
EDA1962 MQDEF ERROR: MQDEF name is opened now
The MQDEF command tried to free the MQDEF name that is currently open.
EDA1963 MQDEF ERROR: MQDEF name is already taken
The MQDEF name is already taken, and has used another Queue Manager and/or Queue names.
EDA1964 MQDEF ERROR: memory problems
EDA1965 MQDEF ERROR: internal problem - context does not exist
EDA1966 %1 %2
Check to see that the access file exists.
EDA1968 ACCESS FILE INFORMATION IN MASTER %1 WILL NOT BE CONSIDERED
ACCESS FILE for FOCUS files will not be honored if you are running a command that will alter the FOCUS database (e.g. MODIFY, ...). An explicit allocation or USE is needed.
EDA1969 WARNING: USE/ALLOCATION FOR DDNAME %1 OVERRIDES
FOCUS MFD uses the access file to specify physical partitions. However, the same DDNAME is found in the USE directory or it was explicitly allocated. Access file was disregarded.
EDA1970 MQDEF ERROR: internal problem - context was not created
The module NTMQ/NTMQP was not loaded.
EDA1971 COMPILED DEFINES NOT SUPPORTED ON CURRENT PLATFORM
The Compiled Defines feature is only available in UNIX and NT environments. Future releases may include support for other platforms.
EDA1972 SYNTAX ERROR IN MASTER %1: DATASET WITH ACCESSFILE
The ACCESSFILE attribute in FOCUS MFD cannot be combined with the DATASET attribute. Fix the master file and issue CHECK FILE to ensure that it contains no errors.
EDA1973 ATTEMP TO OVERWRITE EXISTING FILE
EDA1974 WARNING: ACROSS HIGHEST/LOWEST CANNOT PROCESS LIMIT
EDA1975 COMPILED DEFINES SYSTEM ERROR: %1
There was an error in the Compiled Defines Subsystem. Restart the system and try the query again.
EDA1976 COMPILED DEFINES: UNABLE TO LOCATE/USE TEMP DIRECTORY
The system was unable to locate and/or use the temporary directory. Specify the temporary directory in the appropriate manner (see manual), and try the query again.
EDA1977 COMPILED DEFINES: GENCPGM SCRIPT NOT OPERATIONAL
The Compiled Define feature utilizes the gencpgm script for the purpose of compiling and linking. The script has been modified since the original install.
EDA1978 COMPILED DEFINES: UNABLE TO FIND THE C COMPILER
Compiled Defines utilize the C compiler to create the compiled Define. Please modify the GEMCPGM script to use the compiler on this system.
EDA1979 COMPILED DEFINES: UNABLE TO LOCATE GENCPGM SCRIPT
The GENCPGM script was originally installed along with the other executables in the HOME directory of the product. The system is unable to locate the HOME directory.
EDA1980 COMPILED DEFINES: FEATURE NOT APPLICABLE.
This feature is not applicable for the current TABLE request. This could be because the feature contains no DEFINEs, or the DEFINEs utilizing functionality are currently unsupported by the feature.
EDA1981 SYNTAX ERROR IN MASTER %1: CAN'T FIND "FILE=" KEYWORD.
Neither "FILE="nor "FILENAME=" keyword was found in the MASTER file.
EDA1982 UNABLE TO FIND LONGNAME %1
EDA1983 CAN'T ENCRYPT MASTER/FOCEXEC : %1
EDA1984 AUTODATE FORMAT NOT ALLOWED ON THE LHS OF AN EXPRESSION
Left hand side of a COMPUTE or DEFINE expression can not use AUTODATE format. Use HDS format instead.
EDA1985 AUTODATE FIELDS CANNOT BE USED AS A SEGMENT SORT KEY:
EDA1986 AUTODATE FIELDS ARE ONLY SUPPORTED IN FOCUS/FUSION FILES:
EDA1987 WARNING: ATTEMPT TO MODIFY AN AUTODATE FIELD %1
MODIFY request tried to update an AUTODATE field explicitly. The user-supplied field value has been ignored. See FOCUS/FUSION documentation for more detail on using AUTODATE fields.
EDA1988 lw_del could not find struct for filename %1--internal error
Internal error deteted by rlcsa--contact IBI technical support. A CSA block exists but no s_recdes_save structure exists for that filename.
EDA1989 MASTER or PASS has changed since last DEFINE for filename %1
Since the previous DEFINE for the file indicated, either the MASTER definition for that file or a SET PASS value used by DBA for that MASTER was changed. Neither is supported; reissue all DEFINEs after any change to a MASTER or a relevant SET PASS value. EDA1991 may also appear.
EDA1990 Missing s_recdes_save struct for filename %1 intenral error
This is an internal error. A CSA block exists but no s_recdes_save strtucture exists for that fileneme. Contact IBI technical support. Detected by setpl1.
EDA1991 REDEFINE plus changed MASTER forces DEFINE CLEAR for filename %1
The master file definition of the file indicated was changed (see prior message EDA1989) and a REDEFINE of a filed would have
EDA1992 PARSER ERROR: "XDEFAULT" not supported for SUFFIX=%1:
"XDEFAULT" attribute supported only for MFD with SUFFIX=XFOCUS.
EDA1993 DDs %1(%2) and %3(%4) both use DNS %5
The same dataset is allocated to two different DD statements, and at least one of those is opened for output; although this is not supported, command processing continues. The character between parentheses is "I" for input and "U" or "O" foot output.
EDA1994 %1 %2:
An interrupt occurred in S390 (mainframe) compiled define code. Offset is the hex offset of the abending instruction from the top of the compiled code for the segment.
EDA1995 CREATE SYNONYM: "LOADPROC" currently not supported:
"LOADPROC" mcan be used with limited number of SUFFIX/DBMS.
EDA1996 DATASET VALUE MUST BE A FULLY-QUALIFIED NAME: %1
DATASET value in MFD should unambigiously identify the physical file. It can not generally be a "relative" file name. The only case when DATASET value may look like a partially-qualified name is APP-style name (APP environment must be enabled).
EDA1997 INVALID APP FILENAME: %1
APP-style file name must be of the form <APPNAME>/<FILENAME>. Slash symbol must appear once (and only once) within the APP filename. Also, it should not be the first symbol.
EDA1998 CONFLICTING DATASET SPECIFICATIONS FOR %1
When DATASET file or segment level is used to specify sink machine as a data source (<filename> ON <sinkname> syntax) the file name must match the MFD name for file-level datasets, and LOCATION name for segment-level datasets.
EDA1999 INCORRECT 'ON' FILE NAME IN DATASET FOR %1 (2%)
When DATASET file or segment level is used to specify sink machine as a data source (<filename> ON <sinkname> syntax) the file name must match the MFD name for file-level datasets, and LOCATION name for segment-level datasets.
EDA2000 BY TOTAL not supported in MATCH requests
BY TOTAL is not supported by MATCH. It is supported by TABLE, TABLEF, GRAPH, and PLOT.