![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You have supplied screen table names for the Session Menu you are defining; however, the name is not unique. Each of these names will be used for a different screen table of the screen for this menu.You must provide unique names for each of the screen tables.A table must have either its DEFN and/or DATA set to Y.Either one group or a number of group fields may be selectedYou selected both group and group fields. This selection is invalid.Select either a group or a collection of group fields.EITHER THE POOL NAME WAS NOT SUPPLIED OR IT IS INVALIDYou have requested processing of a pool. You have failed to enter a valid pool name for the processing to continue.Correct the pool name and retry your request.A SELECT command did not find any occurrences that satisfied it.The EMS function failed with the reason code listed.Keep any logs and dumps produced for this failure and report this error to TIBCO Support.The routine name supplied is not supported by either the S6BCALL or the S6BFUNCTION shareable tool.The routine name coded as argument of the shareable tool S6BCALL or S6BFUNCTION could not be converted to a valid variable length string.EMS initialization failed: Return code #, Reason code #The initialization failed for an external TIBCO supplied API. It will be disabled for the life of the Execution Environment.A return code of 4 with a reason code 4 indicates a failure to load the EMS interface code S6BDRPSX. Check the installation of EMS support. A return code of 8 with a return code of 0 indicates that TASKPOSIXNUM is set to 0. Set TASKPOSIXNUM to 1 and retry. For any other values contact TIBCO Support.TIBCO EMS is not supported in this Execution Environment.Modify the EMS API parameters TASKPOSIXNUM and THREADPOSIXNUM or the EMS API parameter EMSWIRECODEPAGE as required.EMS prior initialization attempt failed: Return code #, Reason code #See the explanation for message: EMS initialization failed: Return code #, Reason code #See the action for message: EMS initialization failed: Return code #, Reason code #The field reference in @SCHEDULEMODEL is incorrect. It should be of the form T.F where T is the table name and F is the field name. This check is reporting an incorrect token for ".".Specify "." between the table name and field name for the field reference.Encountered "%" when expecting a constant, identifier or "("The token was encountered when a constant value, an identifier, or a left parenthesis was expected.Check the Processing manual for the correct syntax, or cancel the changes.Encountered "%" when expecting a field nameThe field reference in @SCHEDULEMODEL is incorrect. It should be of the form T.F where T is the table name and F is the field name. This check is reporting that the field name is incorrect.Specify the correct field name for the field reference.Encountered "%" when expecting a field nameYou did not provide a valid field name in an indirect reference of the form: table.fieldCheck the Processing manual for the correct syntax and valid field names.Encountered "%" when expecting a field referenceYou did not provide a valid field reference in one of the following places:
• In the WHERE clause of a FORALL statementPossibly, you did not provide a valid parameter reference in one of the following places:
• In the WHERE clause of an INSERT statement
• In the WHERE clause of a REPLACE statement.Check the Processing manual for the correct syntax and valid field or parameter references.Encountered "%" when expecting a local variable nameYou did not provide a valid local variable name after the keyword LOCAL.Check the Processing manual for the correct syntax and valid local variable names.Encountered "%" when expecting a parameter nameYou did not provide a valid parameter name in brackets after the rule name in the rule header.Check the Processing manual for the correct syntax and valid parameter names.Encountered "%" when expecting a relational operator
• one of the following relational operators was expected =, <, <=, >, >=, ^= (in the condition section of a rule)
• one of the relational operators or LIKE was expected (in a WHERE clause).Check the Processing manual for the correct syntax, or cancel the changes.You did not provide a valid rule name in one of the following places:
• In a rule invocation statement (CALL, EXECUTE, TRANSFERCALL, SCHEDULE).Check the Processing manual for the correct syntax and valid rule names.Encountered "%" when expecting a table nameThe field reference in @SCHEDULEMODEL is incorrect. It should be of the form T.F where T is the table name and F is the field name. This check is reporting an incorrect table name.Change the table name in the field reference.Encountered "%" when expecting a table referenceYou did not provide a valid table reference in one of the following statements:
•
•
•
•
•
• Check the Processing manual for the correct syntax and valid table references.Encountered "%" when expecting an empty stringThe field reference in @SCHEDULEMODEL is incorrect. It should be of the form T.F where T is the table name and F is the field name. This check has found extra tokens after T.F.Remove the extra token in the field reference.Encountered "%" when expecting an exception nameYou did not provide a valid exception name in one of the following places:Check the Processing manual for the correct syntax and valid exception names.Encountered "%" when expecting an identifierThere is a syntax error in your rule. The token was encountered when an identifier was expected.Check the Processing manual for the proper syntax, or cancel the changes.This message is used by the Object Service Broker program that produces the Object Service Broker Information Log. It signals the end of the list of the last 16 rules called before the error occurred.You called the @READDSN tool, but the last record has already been read.Supply a handler for exception ENDFILE.You scrolled to the bottom of the selection list and were informed of the total number of rows in your selection.This message is used by the Object Service Broker program that produces the Object Service Broker Information Log. It signals the end of the list of tables accessed when the error occurred.This message is used by the Object Service Broker program that produces the Object Service Broker Information Log. It signals the end of the list of rules called before the error occurred.An error has caused a FORALL statement to be ignored; therefore, there are too many END statements.Usually, the FORALL statement needs to be corrected.An EXPAND FLD operation was requested, and the expanded field definition screen is currently displayed.If desired, enter or change the expanded field definition for the displayed field and press <PF3>; otherwise, press <PF10>.Enter "S" for system, "I" for installation, or "L" for localYou specified an invalid search path code on the batch submission screen.Enter a FIELD name to perform report function ONIf a report function has been selected as the derived field definition value, the OF FIELD field must be filled in.Enter the name of the field or fields on which to perform the report function. Consult the Object Service Broker documentation for further information.In order to describe result set cursors the stored procedure must return a result setEnter at least 1 field or Only enter completed location parm for minimal defnThe current type of table requires that you specify at least one field unless this is a minimal definition.Specify a field for the table, or if this is a minimal definition, define only the Location parameter including the name of the remote node. See the Managing Data manual for more information about defining fields and minimal definitions.Enter DB2 creator or press <PF4> for selectionThe DB2 CREATOR field must be filled in.Enter the DB2 creator of a DB2 source table or press <PF4> for a list of tables in the DB2 database.Enter DB2 table name or press <PF4> for selectionThe DB2 TABLE field must be filled in to associate this MetaStor DB2 table definition with a DB2 table.Enter the DB2 source table or press <PF4> for a list of tables in the DB2 database. If the DB2 CREATOR field is filled in, <PF4> will show you a list of the tables created by the specified DB2 Creator.Enter field of "%" to which "%" of "%" is to be relatedThe field name of the table that you want to relate to is missing.Enter M204 file/group name or press <PF4> for selectionThe first step in defining a 204 table is to specify the Model 204 file or group name.Enter the file or group name, or press <PF4> to select one.You have chosen to have prompting for this item.If a menu manager is named in the column entitled MENU_MANAGER or PROMPT RULE, enter the name of a menu. If an object manager is named in that column, enter a table name.Enter name of the rule to be saved in library %You specified that you wanted to save the rule that generates this report, but you neglected to provide a name for the rule.Enter a rule name or reset the SAVE RULE flag to N.Enter required field at the cursor positionYou have forgotten to insert some important information when comparing two objects.Insert the missing information at the position located by the cursor.You specified the indicated field or parameter of the indicated table, but did not relate it to any other table.Enter the name of a preceding table and field or parameter to relate to.ENTERKEY requested before Screen "%" displayedA rule has called the ENTERKEY tool before the screen specified has been displayed.Display the screen before calling the ENTERKEY tool.Entries must be positioned either to the right (R) or left (L)The menu manager can present the input areas to the right or left of the title.Entry in @SYSTEM_TABLES not insertedThis message is always preceded by message 10 which says that a report table does not have an entry in TABLES. As a result, no entry will be inserted to @SYSTEM_TABLES. This implies that the report table will not be recognized as an object on the target system.Redefine the report table and promote it in another change request.Entry level rule to execute % cannot have argumentsThe selected entry-level rule to execute cannot require any arguments to be passed to it.You have toggled the value of the ENT field for the specified rule. This field indicates whether a rule is an entry rule or not. If you wish to change the value, use the T line command to toggle it back.You typed an entry that exceeds the length accepted by the field.Environment ID % not allowed to purge audit logThe user ID that you used to log on to the external environment is not allowed to purge the Object Service Broker audit log because it does not appear in the secparm data set with a Y in the required column.Contact your system administrator to determine if your environment logon user ID should be allowed to purge the Object Service Broker audit log.Environment ID % not allowed to specify file for audit logThe ID that you used to log on to the external environment was disallowed to specify the archive file for the backup audit log data.Contact your system administrator to determine if your environment ID should be allowed to specify the archive file for the Object Service Broker audit log data.Errors were found in Object Service Broker statements.Correct or remove the erroneous statements.If rules are to be executed at the time of promotion, one rule must be an entry-level rule.Contact the application developer to resolve the problem.Before all occurrences of a parameterized table can be promoted, a PRM table must exist.ERROR: *** Object "%" to be backed up does not exist ***The Promotion system tried to take a backup of the specified object before promoting it, but the object does not exist.Find out what happened to the object, e.g., who deleted it.ERROR: *** Selected object "%" does not exist ***Cannot find the object specified which was selected for promotion.Make sure that you have the correct name for the object.ERROR: *** Table % used by promotion system; CANNOT apply ***The specified table is used by the promotion system and must be applied specially. Customers should not see this message because they should not be modifying Object Service Broker system tables.Detected an error or errors when updating @SYSTEM_PARMSETS.Read the message log to determine which table causes the failure and act accordingly.An overflow occurred during the initialization of TED. A value that was passed in for a parameter is too long for the table definition.Error # was detected by system; meaning:%The operating system used on the portable platform returned a value other than zero for an internal function; meaning shows the text that corresponds to this value as it was defined by the vendor of the system.Inform your local systems support person for corrective action.This is a general VSAM access error. The variables, from left to right, are as follows:ERROR *** Execution of rule to execute % failed ***The rule to execute specified with the promotion failed to execute. A dump follows in the log.Correct and execute the rule separately, or back out the change and resubmit the promotion with the corrected rule.You have entered a primary command which contains unmatched quotes.Correct the quotes in your primary command.ERROR - Overlap or fit problem for fields and/or headingsThe definition of two or more fields in the definition area or the Paint Screen overlap.All changes are erased. Redo any required changes, and ensure that the definitions do not overlap.Error - Probably bad selection. LIKE <number> not supportedThe specified selection contains an error. A common error is to use LIKE with a number.This line specifies that a rule is to be called. Prompting is only supported for rules that are executed.Remove the prompting or change the invocation from call to execute.You attempted to purge the audit log contents but you were disallowed for the given reasons.A security logging error has occurred. In the traceback log, this message will be preceded by a message describing the exact error.Review the traceback log for a prior error message. Take appropriate steps based on this prior message.You attempted to specify the given file as the archive file but you were disallowed for the given reasons.The rule is attempting to insert a numerical value into the field of a screen table. The specific reason for the conversion error is given in the message.If the value is too big, make the screen table field larger so that it can hold the value.The derived field rule has returned a value which cannot be converted to the attributes of the derived field.
• Rewrite the rule so that it returns a value matching the attributes of the derived field.
• Change the attributes of the derived field so that the field matches the return value of the derived field rule.An error occurred during the conversion of a numeric value.Check that the size of the field is large enough to hold the value.The parameter value does not match the attributes of the parameter in the table definition.
• Change the attributes of the parameter in the table definition to match the existing parameter value.
• Use a parameter value which matches the attribute of the parameter definition.A value in a selection cannot be converted to the attributes of the target field, (e.g., alphanumeric to numeric).Use a value which matches the attributes of the target field in the selection clause or the stored selection.Error detected during definition build; PRINT abortedIn the Screen Definer, you issued the PRINT command; however, a system error in the internal tables prevented the printing.
• Error detected in %. Conversion of % % to % % not allowedInternal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Error detected in system dump routine; "%" is not a valid event type; dump of rule error terminatedThis message is used by the program that produces the Object Service Broker Information Log; it indicates an internal error.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Error detected in system dump routine; dump of rule error terminatedInternal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Error detected in the definition of the parameters for routine "%"Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.ERROR DETECTED WHEN ATTEMPTING TO ISSUE CANCEL USERWhen attempting to send the CANCEL USER request to the Data Object Broker, an error was detected.Review the job log for possible additional messages which may help identify the cause of the error. Retry your request. Contact TIBCO Support if the problem persists.ERROR DETECTED WHEN ATTEMPTING TO ISSUE TRACEID/NOTRACEWhen attempting to issue the change in tracing request an error was detected.Review the joblog to determine if there are addition messages which may help identify the cause of the problem. Retry your request. Contact TIBCO Support if the problem persists.Error detected when loading the definition of report "%"A table access error occurred when the report server loaded the definition of the named report.The Promotion utility detected an error when processing the specified object during application of the change request.See log for the cause of the error. You may reapply the change after you have corrected the error.ERROR DETECTED WHEN PROCESSING RESPONSEWhen validating the values you set for the monitor processing an undetermined error was detected.Retry your request. If the problem persists contact TIBCO Support.Error during default value conversion for "%.%"The default value for a subview field cannot be converted to the target attributes.Change the attributes to an allowable type, syntax, length, and number of decimals.The attributes for the primary key for the subview table cannot be different from those of the source table primary key.Change the primary key attributes of the subview table to match the attributes of the source table primary key.The system sort was unable to continue.Review the message log. You may also want to review the amount of DASD space available for sorting, and increase it to accommodate the largest volume of data to be sorted. Refer to your Installation and Operations manual for DASD allocation.Error encountered in Server TYPE "%" Server ID "%"A request was sent to a gateway of the indicated type, and an error occurred while processing the request.The specified HELP rule failed to execute successfully.If this rule has been modified, refer to the traceback. If it has not been modified, contact TIBCO Support.If user prompting was defined for the field, you can leave the cursor on this field and press <PF1> to see a list of values allowed for the field. Contact TIBCO Support.Error in % table name for assignment-by-name; %At evaluation time, an indirect reference was not evaluated to a valid table name.Study the second part of the message that gives details about the invalid name.Error in arithmetic expression; "%" system condition detectedWhile evaluating an arithmetic expression, a system condition was raised, but not handled.Verify the arithmetic expression. You may need to supply a handler.ERROR IN COMMIT/ABORT CONFIRMATION RESPONSE, RETRYThe internal processing of the utility detected an unexpected condition when processing a confirmation response.Retry your request. If the problem persists contact the support center.Error in definition of % table "%" at field "%"The type, syntax, length, or # of decimals specified are not valid for this table.Verify the field attributes against the external file layout.Error in definition of report "%": report field "%" of report table "%" has an invalid SORT-BY numberAn error exists in the control fields of the report.Error in definition of report "%": report field "%" of report table "%" has an invalid SUMMARY-BY numberAn error exists in the control fields of the report.Error in definition of report "%"; controlling report table "%" has no report fieldsThe body report table for the named report has no report fields.Use the Report Definer to correct the definition of the report.Error in definition of report "%"; more than one report table bodyThe named report has more than one body report table.Use the Report Definer to correct the definition of the report.Error in definition of report "%"; report field "%" of report table "%" cannot be both an ACROSS-BY and SORT-BY fieldA report field of the body report table was used as a SORT-BY and an ACROSS-BY field.Use the Report Definer to remove the report field from the list of SORT fields. An implicit SORT is performed for ACROSS-BY fields.Error in definition of report "%"; report field "%" of report table "%" has an invalid ACROSS-BY numberThe ACROSS-BY numbers either do not start at 1 or are not consecutive.Use the Report Definer to identify and correct the problem.Error in definition of report "%"; report field "%" of report table "%" has an invalid break numberA break member was either negative or not consecutive for the body report table of a report.Correct the error in the definition of the report by using the Report Definer.Error in definition of report "%"; report has no report tablesThe definition of the named report is incomplete because it has no report tables.Use the Report Definer to add report tables to the definition of the report.The dictionary occurrences may have been modified outside of the Table Definer.
• A field of the calculation (CLC) table (that is not a primary key or a COUNT field) is not a field of the source table.
• A field of the CLC table (that is not a COUNT field) does not have the same syntax or length as the source field.
• The primary key for the CLC table is not of syntax B and length 4.Determine the error in the field definition and redefine the field accordingly.The evaluation of an indirect table or field reference is found to be a value that cannot be a name.Verify that the rule argument or field of a table that is used to resolve the indirect reference is a name.Error in menu - Objectlist or Menu for this item does not existThe menu was defined to prompt or display another menu for this item. The required objectlist or menu does not exist.A menu item requires the call or execution of a rule, but does not have the name of the rule.Error in option; % encountered when expecting %An invalid token appears in the options for the HLIPREPROCESSOR tool.Error in queue name for asynchronous event "%"; %The expression evaluated to determine the queue in a SCHEDULE TO statement has not yielded a value that can be a name.Modify the expression that determines the queue.Correct the quoted string to be one of the supported formats of quoted strings: Plain string, Unicode string, hexadecimal string or raw data string.An error occurred converting the data in the specified columns of the specified record of the Import file.Ensure that the definition of the external data is correct. Also ensure that the external data itself is valid.Error in SCHEDULE statement; queue "%" is undefinedThe queue specified in a SCHEDULE statement is unknown to the scheduler.Error in source table "%"; unable to construct object screenThe definition of the table containing the list has an error that prevents the display of the list.ERROR OCCURRED WHEN DUMP REQUEST ISSUEDWhen attempting to send your dump request to the Data Object Broker, an error was detected.Review the joblog to determine if there where associated messages that may help identify the cause of the problem. Retry your request. If the problem persists contact TIBCO Support.ERROR OCCURRED WHEN PROCESSING LOCK OWNER RETRIEVALWhen attempting to retrieve the list of owners of a particular table, the Lock Manager encountered an error.Retry the request, if the error recurs contact TIBCO Support.Error occurred while closing file used to schedule rule, error code %An internal error occurred while closing the file descriptor used to write the schedule model instance to a disk file.Error occurred while closing stream used to schedule rule, error code %An internal error occurred while closing the buffered I/O stream used to write the schedule model instance to a disk file.Error occurred while unlinking temporary file used to schedule rule, error code %An internal error occurred while attempting to unlink a temporary disk file used to hold an instance of a schedule model.Ensure that the directory specified by the TEMPUNIT parameter has permissions that allow for the deletion of files.Error occurred while waiting for process used to schedule rule, error code %An internal error occurred while waiting for termination of the at(1) command that is used to schedule a batch job.An error occurred while attempting to update the Bind flag for the specified object.Review the reasons for the failures and resolve if you require the objects to be unbound then run @PROMBINDOBJS and re-run @PROMUNBINDOBJS.An error occurred reading the system color definitions from the indicated table.Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.ERROR RETRIEVING CURRENT LOG, REQUEST REJECTEDWhen attempting to process your request to retrieve the last 400 operator messages an error was detected.Review the joblog to determine if there are additional message which may help identify the cause of the problem. Retry your request. If the problem persists contact the support center.
2. Contact TIBCO Support or the System Administrator with the log and a description of what actions were being performed when this message was generated.
2. Contact TIBCO Support or the System Administrator with the log and a description of what actions were being performed when this message was generated.One of the following could have occurred:
• The screen definition has been modified outside of the Screen Definer.Use the Screen Definer to redefine the screen. If the problem persists, contact TIBCO Support.Error retrieving security parm access info for table "%"
2. Contact TIBCO Support with the log and a description of what actions were being performed when this message was generated.One of the following could have occurred:
• The table definition has been modified outside of the Table Definer.Use the Table Definer to redefine the table. If the problem persists, press <PF2> and print the log, then contact TIBCO Support or the Database Administrator with the log and a description of what actions were being performed when this message was generated.Errors: % Warnings: %. Change #% backed outThe errors and warnings given result from the change request number specified that was backed out.Consult the Promotions manual if you received errors or warnings that you want to resolve.This message gives the number of error messages and warnings that occurred in one phase for the objects that were unloaded. It is joined to a message listing the number of objects unloaded:Example Unloaded % Tables, % Screens, % Rules, % ReportsIf you received errors or warnings, consult the Promotions manual.This message gives the number of errors and warnings that occurred when the objects were being backed up. This message is followed by:Example Backed up % Tables, % Screens, % Rules, % ReportsThis message gives the number of errors that occurred during Phase 1 of apply processing. In this phase, the change request instructions are validated to ensure that the disposition of objects are correct (e.g., new, modified, deleted or deleted occurrences).If you have errors, consult the Promotions manual.ERRORS DETECTED ON HIGHLIGHTED INPUT FIELDS, CORRECT AND RETRYThe highlighted values on the screen are either invalid, present when not supported, or missing when required.Correct the indicated values and retry your update request.You entered an event access that is not defined.Specify a valid event access. To review a list of valid event accesses, press <PF1>.Event rule '%' must have TYPE = 'T' to have ACCESS = 'G'Only T (Trigger) type event is allowed for access type of G (General).Specify valid ACCESS value for type of event rule.Event type "%" is not allowed for % table typeYou entered an event type that is not defined.Specify a valid event type. To review a list of valid event types, press <PF1>.An exception was raised by a SIGNAL statement.Determine whether an exception handler is needed.Exception handler ON "%" is already defined in this ruleA syntax error is in the rule; an exception handler is defined twice.Excess parameter value "%" encounteredYou selected a table but typed in more parameter values than there are parameters for the table.
2. Contact TIBCO Support or the System Administrator with the log and a description of what actions were being performed when this message was generated.The user exit routine produced an invalid return code.Examine the user exit routine to determine why it produced an invalid return code.You tried to execute Phase 2 before Phase 1.Execute Phase 1 first by using the APPLY_PHASE1 rule.You tried to execute Phase 3 before Phase 2.Execute Phase 2 by using the rule APPLY_PHASE2.You have selected the specified rule for execution. When the change request is promoted, this rule will be executed. If you do not wish this to happen, use the C line command to remove it from the request.The Promotion facility is executing the rule that was designated to be executed at promotion time.No more sessions will be accepted, as the Data Object Broker limit has been reached.If required, change the Data Object Broker parameter limiting the number of Execution Environments the Data Object Broker will support, and restart the Data Object Broker. Then resubmit the session when the Data Object Broker is ready.Execution Environment Startup CompletedStart Execution Environment was successful.Execution of rule "%" (specified using "RULE" keyword) FAILEDWhen you attempted to log on, you specified the "RULE" CLIST parameter. In this case, once the rule has executed, your session is terminated. There is a problem with the rule and as a result, its execution failed.Log on to the workbench and debug the rule. If you cannot logon to the workbench, contact your System Administrator.The specified rule invoked through an EXECUTE statement has failed.Press <PF2> for the Information log for details about the failure.The rules called are nested too deeply for the current setting of the Execution Environment parameter EXECSTACKSIZE.
• Verify that this error message is not caused by an infinite loop. If it is, correct the rules to eliminate the loop.
• Increase the size of the EXECSTACKSIZE parameter.
• If possible, replace recursion with iteration.Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Executor detected a bad data value; possible error in table data storeInternal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Internal error that may indicate a problem with the Rule Editor. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.An access statement does not name enough parameters for a table.EXPECTED COMMIT/ABORT CONFIRMATION NOT RECEIVEDWhen you were prompted to confirm your manual indoubt transaction resolution your failed to press the required confirmation key. Your resolution request has been abandoned.Expecting parameter for % in unparameterized table "%"A non-parameterized table was encountered in an object type that should only have parameterized tables. The definition of that object type may be corrupted.Exponent overflow on an exponential operationThe result of an exponential operation exceeds some predefined maximum. Currently, this maximum is approximately 10E75.Verify the expression to ensure that the maximum possible value does not exceed the predefined maximum.Exponent underflow on an exponential operationThe result of an exponential operation is smaller than some predefined minimum (approximately 2E-78).Verify the expression to ensure that the minimum possible value does not fall below the predefined minimum.An open export file cannot be closed.The specified table is not defined as an export table.External attributes of a key field must have DECIMAL set to '0'Invalid external decimal for ADABAS key fields.Specify external decimal of 0 for ADABAS key fields.Invalid ADABAS external field name. A matching field name cannot be found in the ADABAS file definition.External Gateway TYPE "%" Server ID "%" unavailable or request abortedThe gateway of the indicated type was not started or it failed.
1. Verify that the gateway and the Object Service Broker Data Object Broker are started and available.
2. Verify that the server3d is correct in the table definition.For IMS Gateways, the RESPONSEMODE parameter should be set to ASYNC for online gateways and SYNC for gateways running in batch mode. If this problem persists, contact TIBCO Support.External length must be % for external syntax "%"The external length is incompatible with the external syntax.Specify a value for the external length within the range indicated by the message. Examine the external syntax to evaluate the correctness of the syntax/length combination.External routine library error - cannot load routine "%"A module corresponding to the specified external routine was not loaded successfully.Verify that the required module is in the external routine library.External Server TYPE "%" Server ID "%" unavailable or request abortedThe Gateway ID specified in the message in not availableChange the SERVERID to an available ID or start a new gatewayThe external syntax indicated in the message is invalid.Enter valid external syntax. Press <PF1> for list.Invalid external syntax for ADABAS key fields.Specify external syntax of B for ADABAS key fields.Extra input found beyond end of rule statementMore characters appear in the Object Service Broker statement after the semicolon or colon.Correct the Object Service Broker statement by removing the extra characters or by removing the semicolon or colon.A parameter found in a DEFINE TABLE or an access statement does not exist in the definition of the table.Correct the DEFINE TABLE or the access statement.The message is to confirm your request to cancel the ADABAS extract.Extract and backup file names must be differentYou are attempting to apply a source or target promotion but the names of the extract and backup files are the same.The extract process you started has completed. The status of the change request is now X.The ADABAS definition for the DBID and File No has been deleted.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |