Messages 2501 - 2700
EDA2501 DUPLICATE LDBNAME IN ACCESS FILE %1%2%3%4
The Logical Data Base Name (LDBNAME=) must be specified in one Access File Description for the JOIN structure.
EDA2502 NO LDBNAME FOR LDB IN ACCESS FILE %1%2%3%4
The Logical Data Base Name was omitted in LDBNAME attribute in the Access File Description or is syntactically incorrect. Check the Access File Description being referenced.
EDA2503 UNEXPECTED KEYWORD %1 IN ACCESS FILE %2% / %3
Warning. Referenced keyword should not be specified and is not valid in this type of Access File Description. The keyword is ignored.
EDA2504 UNIQUE JOIN TO SQL FILE WHERE NOT ALL SEGMENTS ARE UNIQUE
EDA2505 A SEGMENT IN THE STRUCTURE IS NON-KEYED: %1%2%3%4
This message is included in the FSTRACE3 output when the RDBMS-managed native join logic could not be invoked, due to the existence of a non-keyed segment located above the bottom active segment in the join structure being accessed. The join logic will be processed by FOCUS.
EDA2506 INTERFACE-MANAGED NATIVE JOIN SELECTED FOR THE FOLLOWING REASON:
This is the first line of the Interface FSTRACE3 output that is generated when the RDBMS JOIN optimization has been set to ON or FOCUS, and is able to correct any segment multiplication. Screening conditions, and a sort by all KEY fields, are passed. Aggregation cannot be passed.
EDA2507 %1%2%3%4
EDA2508 WARNING: NON-PASSABLE WHERE BASED JOIN CONDITION %1%2%3%4
EDA2509 RDBMS-MANAGED JOIN SELECTED BUT RESULTS MAY BE INACCURATE
This is the first line of the Interface FSTRACE3 output that is generated when RDBMS JOIN optimization has been set to SQL. This indicates that the report that will be generated may be different than if FOCUS had processed each file separately.
EDA2510 FOCUS-MANAGED JOIN SELECTED FOR FOLLOWING REASON(S): %1%2%3%4
This is the first line of the Interface FSTRACE3 output that is generated when RDBMS JOIN optimization has been disabled. This indicates that a separate SQL SELECT statement will be generated for each table in the report request, and FOCUS will process the JOIN internally.
EDA2511 DISABLED BY USER %1%2%3%4
Optimization was disabled due to the previous issuance of an SQL SET OPTIMIZATION OFF command. If SQL optimization is desired, it may be reactivated by issuing the SQL SET OPTIMIZATION command with a different setting.
EDA2512 NON-SQL SEGMENT IN MULTI-PATH REQUEST %1%2%3%4
Optimization was disabled due to the presence of segment(s) of different suffix while the tables in SQL part not sharing a common retrieval path in the JOINed structure. Such requests must be processed by FOCUS logic. To view the retrieval path, issue CHECK FILE filename PICTURE RETRIEVE.
EDA2513 OUTER JOIN (ALL=ON or ALL=PASS) CANNOT BE PASSED %1%2%3%4
Optimization was disabled due to the previous issuance of a SET ALL = ON or ALL = PASS command while the given SQL engine doesn't support a proper type of OUTER JOIN. For instance, SET ALL=ON is passable to DB2 (v.4 and up) and ORACLE, while SET ALL=PASS can be passed to SYBASE and Informix.
EDA2514 NON-CONTIGUOUS SQL SUBTREE %1%2%3%4
Optimization was disabled due to the fact that the list of active segments of the given suffix generate a non-contiguous hierarchy in the JOINed structure. FOCUS must process the JOIN request against the answer sets returned by each file.
EDA2515 NON-ELIGIBLE EXPRESSION IN DEFINE OR WHERE BASED JOIN
Optimization was disabled due to the use of a DEFINE-based JOIN or WHERE-based JOIN on an expression that cannot be passed to SQL.
EDA2516 MULTIPLICATIVE EFFECT WOULD ENSUE %1%2%3%4
Optimization was disabled due to the use of SUM or COUNT on a segment level in the structure where duplicate rows could be generated in an RDBMS-performed JOIN, causing inaccurate aggregation results to be displayed in the report. SQL SET OPTIMIZATION FOCUS or ON invokes this processing.
EDA2517 FST. OR LST. WHERE SORT FIELDS DO NOT COVER KEY %1%2%3%4
Optimization was disabled due to the use FST. or LST. operators on or below a non-unique segment defined as KEYS=0. FOCUS must perform the sort on this answer set, according to the BY fields in the report request unless SET OPTIMIZATION SQL is issued.
EDA2518 NO FUNCTION OR REFTABLE SPECIFIED IN ACCESS FILE %1 / %2
Both Function Name and Reference Table were omitted from the Access File Description or are syntactically incorrect. Check the Access File Description being referenced.
EDA2519 THE JOINED SEGMENTS RESIDE IN MORE THAN ONE NODE OR SUBSYSTEM
Optimization was disabled due to segment references to multiple RDBMS subsystem locations. For this reason, no single RDBMS subsystem can perform the JOIN. It must therefore be processed by FOCUS logic.
EDA2520 COUNT IN SUBHEAD, SUBFOOT, HEADING, OR FOOTING %1%2%3%4
Optimization was disabled due to the existence of a COUNT verb in a heading or footing specification.
EDA2521 MULIT-PATH REQUEST IN MULTIPATH=SIMPLE mode %1%2%3%4
Optimization was disabled due to the tables not sharing a common retrieval path in the JOINed structure. Optimization of such requests is possible only in MULTIPATH=COMPOUND mode. To view the retrieval path, issue a CHECK FILE filename PICTURE RETRIEVE command.
EDA2522 AN OCCURS SEGMENT PRESENT IN HIERARCHY %1%2%3%4
Optimization was disabled due to the existence of an OCCURS type segment in the JOINed structure. Since the OCCURS structure is specific to FOCUS, FOCUS must perform the processing separately on the answer set from the OCCURS segment.
EDA2523 MULTIPLICATIVE EFFECT MAY CAUSE DUPLICATED LINES IN REPORT
A FOCUS procedure was executed which contained a PRINT or LIST verb on a segment level in the structure where duplicate rows could be generated, causing duplicated lines to be displayed in the report. The effect of this condition will vary depending on the setting of SQL SET OPTIMIZATION.
EDA2524 JOIN TO A UNIQUE SEGMENT DOES NOT COVER ITS PRIMARY KEY
A FOCUS procedure was executed on a unique JOIN structure that did not specify all the field components in the primary key of the cross-referenced file. The effect of this condition will vary depending on the setting of SQL SET OPTIMIZATION.
EDA2525 FOREIGN KEY IS NOT A SUPERSET OF PRIMARY KEY FOR SEGMENT: %1%2
This message is used to enumerate the segments that caused the issuance of an EDA2524 message during a FOCUS procedure on a unique JOIN structure. The effect of this condition will vary depending on the setting of SQL SET OPTIMIZATION.
EDA2526 WARNING: NO JOIN CONDITION SPECIFIED FOR SEGMENT %1%2%3%4
EDA2527 ERRORS IN PARENT SEGMENT %1 FOR SEGMENT %2 in ACCESS FILE %3
One of the SEGTYPE/FUNCTION/TABLE Parameters in the Access File Description is omitted or has an incorrect value. Check the Access File Description being referenced.
EDA2528 KEYWORD %1 IS MISSING IN ACCESS FILE %2 / %3
A referenced keyword is missing from the Access File Description.
EDA2529 SYSTEM IS NOT UNIQUE IN ACCESS FILE %1%2%3%4
All SYSTEM names (SYSTEM=) must have the same value in all Access Files for the JOIN structure.
EDA2530 DUPLICATE QUERY NAME IN ACCESS FILE %1%2%3%4
The SAP/R3 Query Name (QUERY=) must be specified only once in Access File Description.
EDA2531 NO QUERY NAME FOR SAP QUERY IN ACCESS FILE %1%2%3%4
The SAP R/3 Query Name was omitted in the QUERY attribute in the Access File Description, or is syntactically incorrect. Check the Access File Description.
EDA2532 DUPLICATE USERGROUP IN ACCESS FILE %1%2%3%4
The USERGROUP must be specified only once in the Access File Description for the SAP R/3 query.
EDA2533 NO USERGROUP FOR SAP QUERY IN ACCESS FILE %1%2%3%4
The USERGROUP must be specified in USERGROUP attributes in the Access File Description for the SAP R/3 query. The value was omitted, or is syntactically incorrect. Check the Access File Description.
EDA2534 BOTH LDB AND SAP QUERY SPECIFIED IN ACCES FILE %1%2%3%4
LDB Access and SAP/R3 Query Access are mutually exclusive.
EDA2535 NON-SQL SEGMENT IN HIERARCHY (BAPI/LDB/QUERY PRESENT) %1%2%3%4
Optimization was disabled due to use of BAPI or LDB or QUERY files in the JOINed structure. Optimization may only occur when all the files in a request are Open/SQL. FOCUS must process the JOIN request against the answer sets returned by each file.
EDA2536 NON-TRANSPARENT Open/SQL SEGMENT IN HIERARCHY %1%2%3%4
Optimization was disabled due to use of non-transparent Open/SQL files in the JOINed structure. Optimization may only occur when all the files in a request are Transparent Open/SQL. FOCUS must process the JOIN request against the answer sets returned by each file.
EDA2537 UNSUPPORTED OPTIMIZATION/JOIN TYPE %1%2%3%4
SAP R/3 native interface currently supports only SAL_OPTIMIZE_SQL optimization/join type.
EDA2538 - EDA 2550 %1%2%3%4
EDA2551 PRESENCE OF FST. OR LST. IN MULTI-PATH REQUEST %1%2%3%4
Optimization was disabled due to the presence of FST. or LST. verbs in the multi-segment TABLE request, with the tables not sharing a common retrieval path in the JOINed structure. To view the retrieval path, issue a CHECK FILE filename PICTURE RETRIEVE command.
EDA2552 INTERNAL ERROR IN SQL SHARED MODULE %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.
EDA2553 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1387. Used to be: (EDA2553) FIELD NEEDS AN ALIAS IN MASTER OR ACCESS FILE %1%2%3%4
EDA2554 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1388. Used to be: (EDA2554) INTEGER FIELDS MUST HAVE ACTUAL FORMAT OF I1, I2, OR I4 %1%2%3%4
EDA2555 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1389. Used to be: (EDA2555) ACTUAL FORMAT F IS INVALID FOR SQL, USE FORMAT D %1%2%3%4
EDA2556 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1390. Used to be: (EDA2556) ACTUAL LENGTH MUST BE 4 FOR FORMAT F AND 8 FOR FORMAT D %1%2%3%4
EDA2557 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1391. Used to be: (EDA2557) ACTUAL FORMAT Z IS INVALID FOR SQL, USE FORMAT A %1%2%3%4
EDA2558 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1432. Used to be: (EDA2558) MISSING FIELD IN PACKED FORMAT MUST HAVE ACTUAL FORMAT P8%1%2%3%4
EDA2559 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1433. Used to be: (EDA2559) MISSING FIELD IN INT. FORMAT MUST HAVE ACTUAL FORMAT I4 %1%2%3%4
EDA2560 %1%2%3%4
Comment: Free slot. Moved to focsql errors: foc1434. Used to be: (EDA2560) INVALID VALUE GIVEN FOR 'KEYS' KEYWORD %1%2%3%4
EDA2561 NUMBER OF CROSS-REFERENCED SQL TABLES EXCEEDS DBMS LIMITS %1%2
Optimization was disabled due to the JOINed structure containing a higher number of segments than the maximum that the RDBMS can process in an SQL join. Consult the appropriate RDBMS manual to determine the maximum number allowed.
EDA2562 %1%2%3%4
Comment: Available slot. Used to be: (EDA2562) CROSS-REFERENCED FIELDS MUST HAVE IDENTICAL DATA TYPES %1%2%3%4
EDA2563 %1%2%3%4
Comment: Available slot. Used to be: (EDA2563) KEYFIELD MUST HAVE IDENTICAL USAGE AND ACTUAL FORMATS %1%2%3%4
EDA2564 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1353. Used to be: (EDA2564) I/O ERROR READING ACCESS FILE %1%2%3%4
EDA2565 %1%2%3%4
Comment: Available slot. Moved to focsql errors: foc1354. Used to be: (EDA2565)ACCESS FILE RECORD ABSENT, WRONG / INCOMPLETE FOR SEGMENT %1%2%3%4
EDA2566 %1%2%3%4
Comment: Free slot. Moved to focsql errors: foc1356. Used to be: (EDA2566) NO TABLE NAME FOR THE SEGMENT IN THE ACCESS FILE %1%2%3%4
EDA2567 %1%2%3%4
Comment: Free slot. Moved to focsql errors: foc1351. Used to be: (EDA2567) ACCESS FILE NOT FOUND %1%2%3%4
EDA2568 %1%2%3%4
EDA2569 %1%2%3%4
EDA2570 %1%2%3%4
Comment: Free slot. Moved to focsql errors: foc1362. Used to be: (EDA2570) 'KEYFLD' KEYWORD IS MISSING FOR SEGMENT %1%2%3%4
EDA2571 %1%2%3%4
Comment: Free slot. Moved to focsql errors: foc1363. Used to be: (EDA2571) 'IXFLD' KEYWORD IS MISSING FOR SEGMENT %1%2%3%4
EDA2572 %1%2%3%4
EDA2573 %1%2%3%4
Comment: Available slot. Used to be: (EDA2573) SQL FILE MUST HAVE A KEY %1%2%3%4
EDA2574 %1%2%3%4
Comment: Free slot. Moved to focsql errors: foc1384. Used to be: (EDA2574) LONG FIELD NAME IN ACCESS FILE IS NOT PRESENT IN MASTER %1%2%3%4
EDA2575 %1%2%3%4
Comment: Available slot. Used to be:(EDA2575) DBC/1012 MESSAGE: %1%2%3%4
EDA2576 %1%2%3%4
Comment: Free slot. Moved to focsql errors: foc1402. Used to be: (EDA2576) 'KEYFLD' AND/OR 'IXFLD' KEYWORD MISSING FOR SEGMENT %1%2%3%4
EDA2577 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1137. Used to be: (EDA2577) DUPLICATE KEYWORDS IN ACCESS FILE RECORD %1%2%3%4
EDA2578 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1138. Used to be: (EDA2578) RECORD DOES NOT START WITH A KEYWORD %1%2%3%4
EDA2579 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1139. Used to be: (EDA2579) NO VALUE SPECIFIED FOR KEYWORD %1%2%3%4
EDA2580 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1135. Used to be: (EDA2580) INVALID KEYWORD IN ACCESS FILE %1%2%3%4
EDA2581 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1141. Used to be: (EDA2581) NO KEYWORD FOR ACCESS FILE VALUE %1%2%3%4
EDA2582 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1136. Used to be: (EDA2582) KEYWORD VALUE EXCEEDS MAXIMUM LENGTH %1%2%3%4
EDA2583 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1131. Used to be: (EDA2583) IXFLD VALUE IS NOT A FOCUS FIELDNAME OR ALIAS %1%2%3%4
EDA2584 %1%2%3%4
Comment: Free slot. Moved to focsam errors: foc1366. Used to be: (EDA2584)KEYFIELD & INDEXFIELD HAVE UNEQUAL NUMBER OF COMPONENTS %1%2%3%4
EDA2585 - EDA 2588 %1%2%3%4
EDA2589 AGGREGATION DONE BUT MAY PRODUCE INCONSISTENT RESULTS %1%2%3%4
This is the first line of the Interface FSTRACE3 output that is generated when RDBMS aggregation has been performed, but may produce different results than FOCUS would have if optimization had been disabled and FOCUS had managed the JOINs and aggregation. Examine report results carefully.
EDA2590 AGGREGATION NOT DONE FOR THE FOLLOWING REASON: %1%2%3%4
This is the first line of the Interface FSTRACE3 output that is generated when RDBMS aggregation has been disabled. This message indicates that FOCUS will handle all aggregation processing for this query. A FOCUS message indicating the reason for this decision will accompany this message.
EDA2591 AVE ON ALPHA, DATE OR DATETIME CANNOT BE AGGREGATED
Aggregation was disabled due to the use of an AVE. operator on an alpha, date or datetime field. These FOCUS operations do not have counterparts in the RDBMS, therefore FOCUS must perform this processing on the answer set.
EDA2592 RDBMS-MANAGED JOIN HAS BEEN DISABLED %1%2%3%4
RDBMS aggregation was disabled as a result of optimization (RDBMS join processing) being disabled. This message will be preceded by additional messages regarding the reason optimization was disabled.
EDA2593 AGGREGATION OF AVERAGE CANNOT BE PASSED TO SQL %1%2%3%4
Aggregation of AVE verb can be passed only on the widest set of BY and /or ACROSS keys.
EDA2594 AGGREGATION IS NOT APPLICABLE TO THE VERB USED %1%2%3%4
Aggregation was not performed because a verb such as PRINT or LIST was the only one used in the request, and aggregation is not applicable to these verbs.
EDA2595 ONLY ADD, SUM, CNT, AVE, MIN, AND MAX PREFIXES CAN BE AGGREGATED
Aggregation was disabled due to the use of verbs other than WRITE, ADD, SUM, and COUNT; or operators other than AVE., CNT., MIN., and MAX. in a request.
EDA2596 ONE OR MORE EXPRESSION(S) CAN NOT BE TRANSLATED TO SQL %1%2%3%4
Aggregation was disabled due to the use of logic specific to FOCUS, which cannot be directly translated to the RDBMS, and therefore must be executed by FOCUS.
EDA2597 USE OF DEFINE FIELD THAT CANNOT BE AGGREGATED %1%2%3%4
Aggregation was disabled due to the use of a FOCUS DEFINE field that did not meet the conditions for the passing of aggregation specified in the Interface User's Manual.
EDA2599 NON-SQL SEGMENT IN HIERARCHY (OTHER INTERFACE PRESENT) %1%2%3%4
Aggregation was disabled due to use of several files with different suffixes in the JOINed structure. Aggregation may only occur when all the suffixes in a request are the same. FOCUS must process the JOIN request against the answer sets returned by each file.
EDA2600 'MISSING=ON' OPTION IS NOT APPLICABLE TO COUNTED FIELDS %1%2%3%4
Aggregation was disabled due to the use of the FOCUS verb COUNT on fields specified as MISSING=ON in the Master File Description. The RDBMS would count rows with null values in these fields, so this answer set must be processed by FOCUS logic.
EDA2601 AGGREGATION CANNOT BE DONE FOR DATE FIELDS %1%2%3%4
Aggregation was disabled due to the use of an aggregation verb on a field with data type DATE. Since the RDBMS will not perform aggregation on a DATE field, this answer set must be processed by FOCUS logic.
EDA2602 AGGREGATION OF AVERAGE CANNOT BE PASSED TO SQL %1%2%3%4
Aggregation of AVE verb can be passed only on the widest set of BY and/or ACROSS keys.
EDA2603 IDENTICAL USAGE AND ACTUAL DATA TYPES REQUIRED FOR AVERAGE %1%2%3
Aggregation was disabled due the use of the AVE. operator on a field that does not have identical data types in its USAGE and ACTUAL attributes. If the attributes are compatible according to FOCUS, then FOCUS will perform the required processing; otherwise, a FOCUS error condition will result.
EDA2604 MORE THAN ONE DISTINCT AGGREGATED VERB IN THE REQUEST
EDA2605 ACTUAL MUST BE COMPATIBLE WITH USAGE FORMAT FOR P-TYPE FIELDS
Aggregation was disabled due to the use of a field with an ACTUAL data type of P and a different USAGE data type. If the data types are compatible according to FOCUS, then FOCUS will perform the required processing; otherwise, a FOCUS error condition will result.
EDA2606 ACTUAL MUST BE COMPATIBLE WITH USAGE FORMAT FOR D-TYPE FIELDS
Aggregation was disabled due to the use of a field with an ACTUAL data type of D and a different USAGE data type. If the data types are compatible according to FOCUS, then FOCUS will perform the required processing; otherwise, a FOCUS error condition will result.
EDA2608 ONLY COUNT CAN BE AGGREGATED FOR CONSTANT DEFINES
Aggregation was disabled due to the use of an aggregation verb other than COUNT (or an operator other than CNT.) on a field that was created by the use of DEFINE, and assigned a constant value, either numeric or alphanumeric.
EDA2609 CANNOT AGGREGATE BY NON-SQLIZABLE SORT KEY %1%2%3%4
EDA2610 CANNOT AGGREGATE BY CONSTANT SORT KEY %1%2%3%4
EDA2611 OVERFLOW MAY OCCUR WHEN SUMMING AN I4 FIELD WITH USAGE D OR P
An RDBMS field with an ACTUAL format of I4 can have a precision as high as 10. Using a FOCUS SUM verb on an I4 field with a USAGE format of D or P will cause an overflow condition if the USAGE format length is not specified as large enough to hold the summation.
EDA2612 OVERFLOW MAY OCCUR WHEN SUMMING AN I2 FIELD WITH USAGE I, D OR P
An RDBMS field with an ACTUAL format of I2 can have a precision as high as 5. Using a FOCUS SUM verb on an I2 field with a USAGE format of I, D or P will cause an overflow condition if the USAGE format length is not specified as large enough to hold the summation.
EDA2613 AVERAGE ON NON-MISSING FIELDS MAY RETURN INCONSISTENT RESULTS IF
Comment: no references to the message found down to 60.
EDA2614 DEFINED FIELD IN FORMAT PACKED CANNOT BE AGGREGATED
Aggregation was disabled due to the use of a defined field in packed format, and the conversion into packed format is not supported by the interface.
EDA2615 AGGREGATION OF DISTINCT VALUES NOT SUPPORTED BY ENGINE
The SQL engine does not provide for aggregation of distinct values. In other words, constructs like COUNT(DISTINCT column) and/or SUM(DISTINCT column) are not available.
EDA2616 - EDA2619 %1%2%3%4
EDA2620 AGGREGATION IS NOT SUPPORTED BY SQL DIALECT4
This version of SAP/R3 Open/SQL dialect does not support aggregation.
EDA2621 OUTPUT ERROR DURING TRACE %1%2%3%4
EDA2622 OPTIMIZATION OF HOLD FORMAT SAME_DB CANNOT BE DONE:
EDA2623 HOLD FORMAT SAME_DB CANNOT BE PERFORMED:
EDA2624 RCBMS DOES NOT IMPLEMENT TEMPORARY TABLES OF THIS TYPE: %1
EDA2625 SOURCE AND TARGET RESIDE ON DIFFERENT CONNECTIONS
EDA2626 "ACCROSS" IS PRESENT IN THE REQUEST
EDA2627 MULTIPLE VERB/KEY SETS IN THE REQUEST
EDA2628 INCOMPATIBLE WITH FML
EDA2629 REQUEST IS IMPOSSIBLE TO CONVERT TO SQL (SEE SQLAGGR TRACE)
EDA2630 AN IF- OR WHERE-TOTAL CONDITION CANNOT BE CONVERTED TO SQL
EDA2631 READLIMIT RESTRICTION CANOT BE PASSED TO SQL
EDA2632 PRINT DISTINCT COMBINED WITH 'BY'