![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
T = TITLE rows/cols H = HEADING rows F = FINAL colsThe code T or H can be used to designate a row as a title or heading row. For Across reports only, the code T or F can be used to designate a column as a title or final column.Enter or change all title or heading rows by entering the correct code on the command line for the row. For Across reports only, enter or change all title or final columns by entering the correct code on the line bar at the desired column.TABLE.* expected on both sides of an assign-by-name statementAn invalid assignment-by-name statement was detected.Check the Processing manual for the syntax of an assignment-by-name statement.Table "%", field "%" has no source field in source table "%"Cannot find the field in the source table that corresponds to the given field.Use a different source field for the given field, and make the appropriate changes in the definition of the given table.Table "%", parameter "%" has no source parameter in "%" source tableCannot find the field in the source table that corresponds to the given parameter.Use a different source field for the given parameter, and make the appropriate change in the definition of the given table.Table "%" and its fields excluded - selection removedThe source data table and its fields have been excluded. Since some of its fields are referenced in the selection criteria, the selection criteria were also removed.The source data table and its fields have been excluded at your request.Some types of tables may only be browsed, for example tables of type PRM. You have attempted to edit one of these types of tables.Table "%" cannot be referred to more than onceYou referred to a particular table more than once while specifying table permissions for an object set definition. Since the table is not parameterized, the entry refers to the whole table and thus only one entry is allowed.NOTE: You can refer to a parameterized table more than once, but you must specify either the instance involved for each entry, or refer to the whole table.Remove duplicate entries from the list by replacing the table name with blanks, nulls, or another table name.Table "%" contains data; cannot change type from "%" to "%"Because the specified table contains data on the target system but the source table type does not match the target type, the apply process cannot proceed as requested.If the target type is TDS: 1) Unaccept the change and return it to the developer on the source system. 2) The developer should roll back the change request and make the table compatible with the target system. 3) Submit a change to delete the data from the table. 4) Submit a change to modify the table type. If the target type is SES or EES, either restart the session or EE to clear the table, or explicitly clear the table before re-applying the change.The contents of the source table have been copied into the destination table.No bound data occurred for the table in the fixed storage; therefore, the data could not be found and used.Table "%" does not exist or has no location parmIn order to remotely apply a change that involves table data, the table in question must have a location parameter.Ask your Promotion Administrator to unaccept your change by selecting U, then roll it back and add a location parameter to the specified table and submit your change again.Formatting of a table buffer by $FORMATROW failed. The table is not defined or $FORMATROW was called before the access to the table in the transaction.The indicated data table does not exist. A data table must be created before you can use it to generate a report.You specified the indicated source data table more than once.Remove one of the duplicate source data tables from the input area.Table "%" has invalid or non-existent source table "%"Check the definition of the table and see if it uses a valid source table.Internal error. The definition of the table has been altered.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Use only the Table Definer to modify table definitions.This message confirms that the indicated table is empty.The table specified in the COPY command is not a MetaStor IMS table. You cannot copy the definitions of other types of tables into a MetaStor IMS table.You can execute the COPY command again, and provide a valid MetaStor IMS table as the source table.You requested the PARMS function for a non-parameterized table in the table permissions screen of an object set definition.The application is attempting to INSERT into a report table that is neither a body nor a fixed report table. Either the wrong report name was specified, or the name of the report table was misspelled.Use the Report Definer to determine and specify the correct name.You have tried to list (or set) a field of an undefined table.Table "%" is not one of the data tables in the preceding rowsYou can only relate a source data table to another source table that precedes it.The indicated table is not related to any other source data tables. Each table (except the first one) must be related to another source data table.Relate a field of the indicated table to a preceding data table.A table access was attempted on a table which is not defined.Verify the spelling of the table name or define the table.Specify the table type indicated in the message.An invalid table type was entered. Table type must be the same as the one indicated in the message.Table "%" needs % data parameter(s) and % location parameterYou tried to edit or browse another table using the EDIT or BROWSE command but you specified the wrong number of parameters.The specified table was previously bound but no longer exists.A table that you specified for indirect calls does not exist.Check the table name and existence of the specified table.The rule has attempted to insert, delete or replace an occurrence from a screen table. This screen table has been specified with the wrong screen as its parameter.
• Specify a screen which already contains the desired screen table as the parameter to the screen table in the rule.
• Using the Screen Table Painter, add the desired screen table to the screen.Table "%" not printed because a PRM table was not foundYou are trying to print an object and a table which stores part of the object's definition. A PRM table for that table is required.Define a PRM table for that table and try the operation again.You are trying to print an object and a table which stores part of the object's definition is not printed.Read the message log and find out the reason why the table is not printed.You cannot use the indicated type of table as a source data table for generating a report.Choose any type of table except one of the following:You requested a REPLACE or DELETE operation, but the VSAM data set is not open for update. The variables, from left to right, are as follows:Ensure that the table definition for this table specifies Y in the UPDATE field and N in the LOAD field.You are trying to print an object and a table which stores part of the object's definition is printed.The specified table was printed as a result of the PRINT command.The message indicates how many parameters the table has been defined with. You have attempted to supply a different number of parameters.
• Do not specify any parameters so that you can have the Table Browser/Editor prompt for them.The number of parameters you supplied in the selection string for the indicated table does not match the actual number of parameters for the table.Check the parameter list from the table definition and change the selection string accordingly.To run GEN_SYS_TBLS, you must provide a table name for the system to create a table. If a table with the specified name already exists, this message appears.Table % cannot be moved due to minimal table definitionMOVTAB failed. Requested table to be moved is a minimal table definition. Segment# of the table is not changed.No action required. Refer to the Shareable Tools manual for more information on MOVTAB.Some or all occurrences of the specified table have been deleted as requested.Table % does not exist or is of type "OBJ" or "EXP"Rule object code (OBJ) and export (EXP) tables are not printed.Check the name of the table; define the table if it is not defined.The specified field is not a field of the table.The indicated table does not have a field with the indicated name.The indicated table does not have a parameter with the indicated name.Table % has a SIX that is incompatible with the backup; delete SIX before BackoutOne of the secondary index fields of this table does not exist in the backup file.Remove the secondary index before proceeding with the Backout.Table % has already been defined under Serverid %The specified defined table has already been mapped to another Serverid under the same external DBMS.You entered the table name more than once in the selection screen. You cannot unload a table more than once.Table % has more than 4 parameters; No occurrences unloadedA table cannot have more than four parameters. No occurrences are unloaded.No primary key exists in the table you are loading.Check the definition of the table and designate a primary key.A definition has already been generated for the indicated table.Put the DECLARE TABLE command before any other commands, such as DECLARE CURSOR, which cause the definition to appear automatically.You specified an empty source text table with the COPY command.You can only load occurrences of a TDS-type table.TED was called with an input table that does not have the fields required to hold text.Call TED with a table that meets the specifications for text. Refer to the Shareable Tools manual for information about defining the table.The requested table cannot be found in the system. This message appears in the user log.Ensure that a table by that name exists and unload the table again.The indicated table is not defined in this program.Define the table either by using DEFINE TABLE or by declaring a cursor on the table.The indicated table is not defined in the Object Service Broker database, or was not defined in a DEFINE TABLE statement.Make sure the DEFINE TABLE statement specifies a table that is already defined to Object Service Broker.Your request to move the table to the specified segment was successful.The table used for the matching field does not previously appear in the join.Add the table to the join. If it is already in the join, try changing the order of the tables in the join.The request to clear the indicated table is canceled.Table % not supported in % since field % has syntax F 16A field of the table has syntax F (floating point) length 16, which is not supported in COBOL.Change the definition of the table or use another table.Table % of % cannot be included in a promotion requestThis table cannot be promoted through the promotion system because:
• The table contains data that is specific to the system, such as valid userids or borrowing rights.
• The table contains data that is shared by systems, such as @SCHEDULEMODEL.The first % is OCCURRENCES or DEFINITION. The second % is the table name.If you want to promote the table anyway, contact TIBCO Support.Table % or % may not exist or be a screen and screen tableGEN_TED was called with parameters that are not the names of a screen and a screen table.A table was specified with the incorrect number of parameters.You entered the incorrect number of parameters for a table.The indicated table requires the given number of parameters to be specified explicitly.Put the required parameter specification right after the table name.Either your request to reset the bind on the table was successful, or you attempted to bind something other than the table definition or data.If your request was successful, no action is required. If you attempted to bind something other than the table definition or data, try again and specify either the definition or data.This message is used by the Object Service Broker program that produces the Object Service Broker Information Log.Inform the user that the specified table has been deleted.You are trying to delete a table but the table does not exist.Table @PROMUNBOUNDOBJS contains data; run @PROMBINDOBJSObjects have been unbound with the @PROMUNBINDOBJS tool and have not all been successfully rebound using the @PROMBINDOBJS tool.Run the @PROMBINDOBJS tool to restore the bind information before attempting to unbind objects again.Table access error detected when loading the definition of table "%"Internal error. The definition of the table has been altered.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Use only the Table Definer to modify table definitions.This message generally introduces more specific messages that describe the error encountered.Read the messages that follow in the Information Log.Table contains data; modifications are restrictedThe specified table contains data. Modifications of the table definition are restricted to the unprotected fields. Note that the length of the fields can only be increased, not decreased.Table definer for % type tbl not availableThe Table Definer tool cannot be used for the table type specified in the particular presentation environment.Press <PF1> for a listing of table types accessible from the Table Definer.Table definition at location "%" has "%" which are incompatible with definition at this locationA distributed transaction encountered a table definition at the named location which was incompatible with the definition at this location. Definitions do not have to be identical on both systems, but PARMS, FIELDS, ORDERING, SELECTION, and CODEPAGE must match.Determine which definition item is incompatible and use the Table Definer to correct it.Table definition at this location has no LOCATION parm; % can not be accessed remotelyA distributed transaction encountered a table definition that did not have a location parameter at the remote Object Service Broker system. A table without a location parameter cannot be accessed remotely.Use the Table Definer on the remote system to add an appropriate location parameter. Note that this may not be an error; the remote system's administrator may have chosen to make a table accessible from that system only, by not defining a location parameter.Changes to the table definition were canceled at your request when you pressed <PF12> to cancel.Table definition could not be bound from location "%"A table's definition implied that it was to be obtained from another location. However, the definition was invalid or the message failed. In either case, subsequent message log text will specify the reason.Preceding messages will identify the error in the definition or the distributed message.Formatting of a table buffer by $FORMATROW failed. The table does not have an i-th field. The format string does not match the definition of the table.The EES table definition does not contian the correct defintions for mandatory fields @@UPDATE_COUNT and @@REF_COUNT.Table definition was not bound from this locationA local transaction attempted to use an incompatible definition which was previously obtained from another location. Prior messages will have detailed the incompatibility.Revise one or both table definitions using the Table Definer.Table is not of type TDS; No occurrences unloadedOnly occurrences of a TDS table can be unloaded.Check the type of the table that you want to unload.No table name has more than 16 characters.Table name can only be given for table access exceptionsOnly table access exceptions (such as GETFAIL, INSERTFAIL, etc.) may have an associated table name. For example ON GETFAIL TABLE is permissible, but ON CONVERSION TABLE and ON MY_EXCEPTION TABLE are not.You did not enter the table name when using either the Table Browser/Editor, or the Single Occurrence Editor.The definition of the table is not printed because of an integrity error.
1. Try printing the table definition again later. If it still does not work, try printing another table definition.
2. Report the results to the System Administrator. The Administrator can check your security clearance and the integrity of the database.
3. If the problem is not resolved, contact TIBCO Support.Table or table instance for BIND table "%" exceeds system instance bind limitThe total occurrence for a bound table has exceeded the system limit. This message appears in the system log to provide more information about bound table storage when there is a transaction failure.Table parameter "%" has not been specifiedThe indicated table parameter was not specified.Table parameter cannot be repeated in the WHERE clauseA table parameter appears both inside parentheses after the table name and in the WHERE clause.Correct the access statement so that the parameter is specified only once.You changed the table type. You may see a different screen which displays the attributes of the new type of table.The table type code must be N for regular DB2 table definitions or P for stored procedure definitions. After saving a stored procedure definition you can create result sets table by pressing PF9. The table type code for these tables are tagged with an R.More than one table name appears in this command.Only one table is supported; therefore, all table names must be the same.The two tables named for comparison are the same.Tables permissions for object set will be committed on SAVEYou saved changes to tables permissions for an object set definition. These changes are committed if the object set definition is saved, or ignored if the object set definition is canceled.Tables whose segment number was not preservedThe definition of the loaded table has been changed so it is on a different segment than before.Title for the tally showing the number of each type of object loaded.TAM selection string not found in the constants tableThe message log will contain a more detailed error message.
2. Contact TIBCO Support with the log and a description of what actions were being performed when this message was generated.The chosen action has been completed.You pressed <PF12> to cancel some processing.The DB2 table is defined incorrectly. An entry in the Object Service Broker table FIELDS is missing.The reported field holds data with a length that differs from its definition. The definition of the length of this field was changed after data was entered.Correct the field length in the table definition to match the data occurrence length.TDS LOCK LIST SCREEN DISPLAY ERROR DETECTEDWhen attempting to display the list of logical locks an undetermined error was detected.Retry your request. If the problem persists contact TIBCO Support.TDS LOCK RETRIEVAL ERROR DETECTEDAn error was detected when attempting to issue the logical TDS lock request to the Data Object Broker.Review the job log to determine if there were additional messages which may help identify the cause of the problem. Retry your request. If the problem persists contact TIBCO Support.A TDS error has occurred or a table's definition has been corrupted.A TDS occurrence that contains more fields than are defined was retrieved.If fields were deleted from the definition, replace them. If this is not the case, contact TIBCO Support.You tried to load only the occurrences of a table, but the table is not defined in the target system.Define the table and load the occurrences, or load both the table definition and occurrences.TDS UPDATE INTENT LIST RETRIEVAL ERRORWhen attempting to send your request to retrieve the pending update list to the Data Object Broker, an error was detected.Review the joblog to determine if there are additional messages which may help identify the cause of the problem. Retry your request. If the problem persists contact TIBCO Support.Terminal I/O error during DISPLAY processingAn I/O error occurred while attempting to write to or read from a terminal as a result of a call to ETDISP.Contact the installation's hardware support.Terminal I/O error during DISPLAY processingA terminal I/O error occurred during the Object Service Broker DISPLAY operation.Notify the installation's hardware support.The text specified has been saved as a result of pressing <PF3>.The unformatted text has been printed as a result of pressing <PF13>.An ORDERED or WHERE clause contains too many terms.You specified an invalid LIBRARY for a rule object.Specify a valid identifier to allow the operation to be completed.You specified information about an object that is invalid.One of the following required fields was not specified in the field definition:
•
•
• Supply a value for the indicated attribute.The accumulator for report function "%" overflowedAn accumulator for the computation of a report function overflowed when the report function was evaluated.Validate whether or not the Of-Field values of the report function are within reasonable ranges. If the validation does not solve the problem, use the syntax FLOAT for the Of-Field.The command "%" failed. Data segment is unavailable.The indicated request failed due to the data segment being offline.Bring the data segment online before proceeding with the request.THE CURRENT SCHEDULE NAME IS EITHER INVALID OR NOT SUPPLIEDA schedule name or target was entered on the input which contains invalid characters or identifies a schedule that does not exist.The cursor must be on a table to be deleted from the joinThe cursor was not placed on any table when <PF22> was pressed.Put the cursor on the table to be excluded from the join, and press <PF22> again.The Data Object Broker is not accepting any logons at this timeThe Data Object Broker is not ready to accept new connections.Check on the status of the Data Object Broker and resubmit the session when the environment is ready.The Data Object Broker is quiescing, no new logons allowedThe Data Object Broker is in the process of normal termination.Resubmit the session when the Data Object Broker is available.The DB2 catalog definition is not available. Metastor definition shownThe DB2 Gateway for the Server ID specified is not available. The current Metastor definition is displayed. See documentation for instructions on setting up a local side catalog.Start a DB2 Gateway with the desired Server ID.The defined table has % parms; The table loaded has %The number of parameters in the source table is not the same as the number in the target table.Check the definition of both the source and target tables to ensure that the definitions of the parameters are the same.The definition of file "%" in group "%" has been changedThe definition of the indicated file on the Model 204 system did not match the one in the MetaStor. This is caused by a change in the Model 204 file definition on the Model 204 system.The definition of table "%" (Server "%") has been changedThe definition of the indicated table in the MetaStor does not match the one in the DB2 system which corresponds to the indicated gateway. This is caused by a change in the DB2 table definition on the DB2 system.The field % must be marked as a primary keyYou have not marked one of the CA-Datacom key fields as a Primary Key for the Object Service Broker table. All the CA-Datacom key fields must appear in the Object Service Broker DAT Table Definition key, either as simple fields or as group fields, but not both.You must mark the indicated field as a primary key or include the CA-Datacom key data another way.THE GROUP INPUT (group) FOR DETAIL DISPLAY IS NOT DEFINED, RETRYYou keyed an invalid group name into the input group field and requested a detail display; the group does not exist in the Data Object Broker repository.To add the group press <PF5>; if attempting to display an existing group rekey the group name or identify it by cursor position.THE GROUP MUST BE IDENTIFIED IN ORDER TO DISPLAY RESOURCE DETAILSYou have requested the display of the details for a specific resource but the system could not determine which resource you wished to review.Key in the group name on the input field or identify the group via cursor position and retry your request.THE GROUP MUST BE IDENTIFIED TO ISSUE A STOP, PLEASE INPUT OR SELECT GROUPYou have requested the issue of a stop for all paths within a specific group but the system is not able to identify the group you wish to stop.Either type the desired group name in the input field or position the cursor on the desired group and retry your request.The indicated file or group does not exist in the MetaStor.
• Import the required file or group into the MetaStor before defining the table.The maximum number of allowed selections is %You are only allowed to select up to the indicated number of entries."Blank out" some selections so that the total number of selections does not exceed the indicated maximum.The indicated name appears more than once for the object type shown.The name "%" is too long; maximum is % charactersA name entered on the Search screen has exceeded the given number of characters.The name % is invalid for a dynamically created tableThe table name specified in @DOFTABLES.NAME is already in use by an Object Service Broker system table.The NEW owner must be different than the CURRENT ownerIn the Transfer Ownership screen, you specified that the new owner is the same as the current owner, meaning that no transfer is to take place.Either cancel the Transfer Ownership function, or supply a new owner that is different from the current owner. A list of new owners is available to select from by using the appropriate function key.The number of OCCURS/READ must be in the range 1 - 100The number you specified for field OCCURS/READ is out of range.Specify a number for field OCCURS/READ that is greater than or equal to 1 and less than or equal to 100.The number of OCCURS/READ to be read in each ADABAS call must be specifiedField OCCURS/READ requires a value. This field specifies the number of occurs of a periodic group or multiple value field to be accessed in each call to ADABAS.Specify the number of occurs of a periodic group or multiple value field to be accessed. It is suggested that this value be set to the average number of occurs for this periodic group or multiple field so that in 90% of reads all occurs are read by one call to ADABAS.The number of primary keys cannot exceed 16The number of primary keys that you have specified in your MetaStor table definition exceeds the maximum number of 16 primary keys.The object does not exist in a location or library.Reenter object or location (destination location, library, or environment).You are trying to delete an object from list 1 and the object is deleted.You have specified a nonexistent object.The specified object name is not a valid name.The operating system denied (S0C4) access to memory for MAP table %During a read or write to an area of main storage by a MAP table, the operating system detected an invalid storage address, and terminated the access with a 0C4 abend. Object Service Broker recovers from this situation and raises the DATAREFERENCE exception. A partial data transfer may have occurred, and consistency is not guaranteed.Investigate why the address being accessed is invalid. It may be necessary to register the storage area to be accessed using the @MAP tool.You are trying to do one of the following operations: OBTAIN all rights, RELEASE all rights, and TRANSFER all rights. The operation fails.Refer to the reason given in the error message and correct the problem.The table @PRINTDEFAULTS is empty. This table is used to store the default parameters of printing, e.g., page length, page width, etc.Update the default parameters table and try the operation again.The report is too big to fit in the message logYou attempted to print a report to the message log but the report with the current date range was too large to fit into the message log.Try sending the report to either the printer or a file. To see the part of the report that was sent to the message log press <PF2> twice.THE REQUEST TO STOP ALL RESOURCES OF TYPE = type HAS BEEN ISSUEDYour confirmed stop request has been issued to the Data Object Broker.The result of an exponential was an imaginary numberAn exponential number had to be evaluated with floating-point arithmetic. If the base number is negative, the result is assumed to be an imaginary number.The rule Debugger must be set up before using %The same PF key cannot be assigned to different functionsIn the Screen Definer, you assigned the same PF key to more than one standard function.Change the assignments so that each PF key is assigned to only one standard function.THE SCHEDULE HAS BEEN UPDATED SUCCESSFULLYThis message is to acknowledge that the updates have been applied to the repository as your requested.The source definition for a literal must be enclosed in quotesThe text that defines the source for a literal report field must be enclosed in single quotation marks.Enter single quotation marks around the text you have entered as the source for this literal.The specified rule name is the same as a system routine: name "%"You have tried to give a rule the same name as a system routine (which is not written with rules).THE STOP SERVER REQUEST HAS BEEN ISSUEDThis message acknowledges that the stop server request has been issued to the Data Object Broker.The sum of primary key LENGTHS cannot exceed 127The sum of the primary key lengths that you have specified exceeds the maximum allowed of 127.You must respecify the primary key field(s) so that the sum of their lengths do not exceed 127.The total of all TITLE and HEADING rows must not exceed %The total number of title and heading rows defined for a report table exceeds the maximum given in the message.Change the specified title/heading rows so that their sum does not exceed the maximum.The defined MetaStor semantic type and syntax are not compatible.See the Managing Data manual for the possible combinations of field syntax and semantic types.The version parameter is required for objects of type '%'You are trying to delete an object but the version of that object is not specified.Enter the version of the specified object and retry the operation again.There are % host variables but cursor has % fieldsThis query specifies the given number of host variables, but the cursor declaration specifies a different number of fields.Make the query and cursor declaration agree on the number of host variables and fields.THERE ARE CURRENTLY NO RESOURCE GROUPS DEFINED UNDER TYPE typeWhen the system was attempting to retrieve the groups under the specified type, there were no groups available.Redisplay the Type List screen (PF4) and try your request again.This command names more fields than it gives values.This command provides more values than fields.You have selected an object type for which you do not have any objects with promotion rights.THERE ARE NO ACTIVE PATHS TO BE DISPLAYED, REQUEST IGNOREDFrom the Resource Detail screen you pressed <Enter> to display the active path list; at present there are no paths active.THERE ARE NO ACTIVE SESSIONS FROM REGION =You have requested the active sessions which have been grouped under the identified region name. There are currently no connections to report.There are no ENABLED object sets which include this objectYou requested to view Enabled Object Sets from an object permissions list to see if any enabled object set includes this object.You requested the FIELDS function to see the list of CA-Datacom fields in the CA-Datacom table you specified in the previous context. There are no fields in the extraction tables.Call your database administrator to determine why the extraction information shows the presence of the CA-Datacom table but not its fields.You requested a list of Groups, but there are no Groups to list.There are NO instances currently selectedIn INSTANCE SELECT you have requested to unselect any currently selected instance; however, there are no currently selected instances.You requested a list of libraries, but none exist. You may have made your request from the main menu "Manage Object Permissions" section by pressing the OPTIONS function key when your cursor was on the OBJECT field.There are NO object sets enabled for group "%"You requested the OBJECTSETS function in the Manage Group screen, which lists object sets enabled for the group. There are no enabled object sets that include the group on the enable list.You have requested a list of existing object sets. There are no object sets defined.You requested a list of reports, either in the main menu through OPTIONS, or while specifying reports in an object set definition. However, there are no reports to list.You requested a list of screens, but there are no screens to list.There are no SECURITY ADMINISTRATORS to LISTYou requested a list of Security Administrators, but there are no Security Administrators to list.You requested a list of users, but there are no users to list.You have pressed <PF17> to paste a field but there are no contents being held to be pasted.Before issuing a PASTE command, copy a line or cut a field.There is no cross-reference information availableYou requested a list of screens referencing a screen table, but no cross-reference material is available.You have requested to specify data instances for the table named on the cursor row; however, there is no data in the table to unload.There is no data in the Audit Log for the current date rangeYou attempted to purge the audit log contents but you specified a date range which started and ended before the earliest date recorded in the audit log.Check the date range to be purged and try again.The audit log does not contain any data and therefore the utility has nothing to display.At this time the accesslog only contains entries for the current date. There is no data that can be purged.There is no occurrence in (identifying) table "%" for %You have specified an object which has a corrupted definition. There is no occurrence for that object in the identifying table (table which has object names as key values.You cannot perform the requested operation on the corrupted object. See your database administrator for further assistance.There is no such field as "%" in screen table "%"You have referenced a field that does not exist in the screen table named.Check your screen table definition and reference an existing field, or add the desired field in your definition.You have requested to Manage Permissions for, or Specify Permissions for an object set, in the Main Menu of the Security Manager. The object set named does not exist.You must enter the name of an existing object set or press <PF2> to obtain a list of existing object sets for selection.You have pressed <PF19> to load and given a non-existent table name on the prompting screen.You referred to a non-existent userid when you requested to view a userid profile.You can request a list of users and select from this list, or correct the entry.You referred to a non-existent member when specifying a permissions list or default list.No action is required unless you have to remove the entry.When ACTION is M, the OBJ LIST OR MENU field requires the name of the menu to display.When ACTION is N or C, the RULE field requires the name of a rule to execute or call.There must be an object list for promptingYou have set the PROMPT to O, so the object list to be displayed must be named in OBJ LIST OR MENU.There must be at least 1 distribution point and 1 count fieldYou did not specify a distribution point or a count field for the CLC table. A distribution point must be a field of the source table, and a count field must have semantic type count (C), binary syntax (B), a length of 4, Src C, and Source Name COUNT.Specify one distribution point and one count field.You want to compare two lists of objects to see if they are different. The result is, they are different.The highlighted command does not have a description.Type in the description text for the command.The highlighted command does not have a rule associated with it.Specify the rule to be executed when the command is invoked.<PF13> was pressed and the formatted text was printed.You have entered a negative value into a field requiring a positive value.This field is used only for SCREENS and RULESYou have specified a LIBRARY or ENVIRONMENT identifier for an object when the object does not require this information to identify it.You have included information which does not pertain to the type of object you are specifying.Remove the information or change the object type.You have entered a nonnumeric value into a field requiring a numeric value.You have entered a non-positive value (i.e., 0, -1) into a field requiring a positive value.The type of the object is not one of the valid ones.This line will call or execute a rule; enter its nameA title exists for this item, but a rule does not.DEFINE_MENU was executed with the name of a special session manager entry point that does not correspond to one of the menu types supported by DEFINE_MENU.Change the menu name to an undefined name or to a menu whose type is supported by DEFINE_MENU.THIS SCREEN ONLY SUPPORTS STOP BY TYPE, GROUP MUST NOT BE SPECIFIEDYou entered a stop request after keying in both the type and group. The Type List screen does not support stop server request for a specific group.If you wish to stop all gateways/servers within the type clear the group field and retry the request. If you wish to stop only the gateways/servers in the specified group then proceed to the Group List screen and issue the Stop from there.This SecAdmin requires a CLEARANCE of at least %Based upon users who are assigned as subjects of the SecAdmin whose user profile is being viewed, the clearance assigned to this Security Administrator must be raised. This ensures that the Security Administrator's clearance is higher than or equal to any of the SecAdmin's subjects.The Security Administrator's clearance must be set to the clearance indicated in this message, or higher.This subschema exists; will be overwritten upon confirmationThe subschema that you are about to load is already defined in Object Service Broker. The current definition will be replaced by the new data from the import files shown on the screen.Press <PF21> to confirm that you want to load the subschema or press any other key if you do not want to load it.This table has an instance that is referred to more than onceThe instance for this table, specified by the parameters, occurs more than once.The userid being used to run the tool is not a Level 7 id.TITLE/FINAL cols & body will not fit within defined page widthThe title columns, final columns, and all body report fields must fit within the page width.Change the page width to accommodate all the fields.TITLE/HEADING/FINAL rows/cols must be 0 or a positive numberTitle and heading rows can only be a positive number or zero. Negative title or heading rows are not valid.Change the indicated title or heading row to a valid value.TITLE COLS must be consecutive, starting from column 1Title columns can only be marked consecutively and the first title column must be in column 1.Correct the T line commands to be consecutive and start with column 1.TITLE COLUMNs for break table "%" not the same as TITLE COLUMNs for body table "%"The number of title columns for break tables and body tables must be the same.Use the Report Definer to correct the report definition.Title report tables can only have skip before and after TABLEA Title report table can have skip before and after table spacing attributes only. Therefore, a user who enters values for the other spacing attributes is prompted and the values are reset to null. Users are encouraged to use the format screen by pressing <PF4> where a Title report table has only the appropriate attributes shown.A report field is defined partly in title columns and partly out of title columns.Move the report field or title columns to correct the problem.Titles must be consecutive - followed by consecutive headingsOnly consecutive title rows can be marked, and consecutive heading rows can follow them. Headings cannot precede titles.Correct the T and H markers specified to agree with the restrictions given above.TO ASSOCIATE A SCHEDULE THE TARGET RESOURCE TYPE-GROUP MUST BE SPECIFIEDYou pressed PF5 to associated the displayed schedule to a specific Resource Detail entry but you did not identify the Resource ahead of time.Key in the target type and group in the input fields provided and try your request again.TO COPY A SCHEDULE SPECIFY THE NEW SCHEDULE NAME IN THE TARGET INPUT FIELDYou have pressed PF4 to copy the schedule currently displayed but have not identified the new name of the schedule.Key in the new schedule name as instructed and press PF4 again.To DELETE Menu "%", you must DEFINE_MENU("%")You have changed the MENU NAME and then requested to DELETE. If a menu of this new name does not exist, there is nothing to delete. If a menu of this new name does exist, then you may not delete it from here.If the menu does not exist, there is no need to delete it. To delete the (existing) menu you specified on entry to this tool, change the Menu Name back to this name and then request delete. To delete the (existing) menu you refer to in the changed Menu Name field, CANCEL this Menu Definition and then request DEFINE_MENU specifying the name of the menu you wish to delete as an argument.To INSERT, select occurrence then use CLEAR command in SOEYou tried to use the I line command in the Table Browser where this line command is not valid.To insert an occurrence, follow the directions in the message.To promote table % occurrence, promote the definition as wellTable occurrences for a new table cannot be promoted on their own.The indicated field must be supplied in order to unload the indicated object.To use LIST TABLES function, you must fill in the UNITYou requested a list of tables while specifying tables permissions on the object set definition screen, but you did not specify the unit.Specify the unit to use the list tables function; it narrows the search.The token specified for a FIND or CHANGE command was not found.Make sure that you have specified the token correctly.Break the string into more parts and use the concatenation symbol (||) to join them.There are too MANY, or too FEW, END statements in the rule.Add or delete the appropriate number of END statements.Too many % fields to fit in report definitionControl fields and selection criteria specified are required for a report function to produce a derived field. One or both of the following has occurred:
• You specified too many SORT BY or ACROSS BY fields for a summary report, or too many BREAK BY fields for a detail report.
• The selection criteria, specified on the Selection screen, is too long.
• Reduce the number of SORT BY or ACROSS BY fields if the SUMMARY flag is on, or reduce the number of BREAK BY fields if the SUMMARY flag is off.
• Press the SELECT function key to display the Selection screen, and shorten the criteria by removing unnecessary blanks or parentheses, or by replacing "AND" and "OR" with "&" and "|" respectively.There are more than 600 colors defined in the indicated table.Either delete some color definitions that are no longer needed, or contact TIBCO Support to increase the limit.You have reached the maximum number of conditions allowed in a rule.Try to separate a single rule into two or more rules.You have reached the maximum number of conditions allowed in a rule.Try to separate the single rule into two or more rules.Too many destinations specified for Move/CopyOnly one line command, A (After) or B (Before) is allowed for each M (Move) or C (Copy).Too many exception handlers; maximum 32A rule may have at most 32 exception handlers. This includes not only the explicit exception handlers, but also any UNTIL statements within the actions.If possible, delete some of the exception handlers or UNTIL loops. If not, split the rule.Too many key fields in dynamically created table %The number of fields in a composite primary key is too large.Reduce the number of fields in the composite primary key to 16 or fewer.Too many levels of event rules; at most 5 event levels may be nestedEvent rules can be nested, but only to five levels; you have exceeded that depth.Too many local variables in rule programYou created too many local variables in one transaction, or the variables use up too much storage. This message may indicate an infinite loop or a recursion that is too deep.Verify that the recursion does not get out of control.At this point in the list, the number of nested lists has not left enough room for the last one to be indented.Too many non-derived fields in Definition Area; max is %The maximum number of fields has been exceeded in the Definition Area.Decrease the number of fields specified until you have the indicated maximum or less.The maximum number of open files permitted for a user has been reached. No more files can be opened.Call your system administrator for help if you need more files opened at the same time.Too many parm values to show; All occurrences unloadedThe number of occurrences of a parameterized table is too great to fit into the screen table. UNLOAD bypasses the selection of parameter values and unloads all occurrences from the table.TOO MANY PEER NODES ACCESSED DURING PROCESSING, REQUEST REJECTEDWhen you select remote nodes from the node list screen security data is retained for function validation. The retained data is stored in a table which has a limited number of entries. The current request to process a new node has exhausted the node security table.Exit and reenter the Administrator utility to clear the table.The message log will contain a more detailed error message.
2. Contact TIBCO Support with the log and a description of what actions were being performed when this message was generated.Too many report tables; # is the maximum that can be used by a transactionThe number of tables of type RPT used by an application exceeded the maximum allowed. These are report tables into which a rule can INSERT occurrences.Reduce the number of reports used by the application.Too many reports used by transaction; maximum number possible is #The number of distinct reports used by an application exceeded the maximum allowed. Note that a report can be run an indefinite number of times, and this is a limit on report definitions.Too many Screens used in this transactionThe number of distinct screens used by an application exceeds the maximum allowed.Too many table names for FORALLA routine; maximum number is 16The FORALLA routine has a total of 16 tables currently active. It has just been called referencing another table name, but there is a limit of 16 active tables.Call routine FORALLE to indicate FORALL processing is finished for at least one of the tables that are currently active.Too much output for Message Log from %; excess discardedThe message log overflowed. The overflow was discarded.To get all the output, direct it to hard copy or a data set.Scrolling had reached the top of your selection list of audit log occurrences.You pressed <PF7> until you reached the top of the displayable information. No more information exists above the screen that you are viewing.When invoking an external sort to perform an ordering function the total length of the order fields and internal suffixes has exceeded 4080 bytesModify the rules/table definitions such that the total length of order fields is less than 4081.Total number of Sort/Break/Across fields is %, maximum is %The indicated total number of control fields has exceeded the indicated maximum.Reduce the number of control fields to the indicated maximum or less.The total length of all sort fields for this report has exceeded 4080 bytesAlter the report definition to reduce the sort criteria field lengths to less than 4081 bytes.The indicated report width has exceeded the limit.Reduce the width of the report as follows:
• Shorten the labels or display masks if they are longer than the actual data.
•
• Remove some function-field pairs from the SUMMARY PRINT section of the Function screen if it is a summary but not an across report.This message is used by the Object Service Broker program that produces the Object Service Broker Information Log. It signals the beginning of a list of rules that were called before the error occurred, starting with the most recent.This 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.Transaction being debugged has reached % break eventThe session is not able to create a transaction.Check the session log for more information.TRANSFER OWNERSHIP function CANCELLEDYou returned to the main menu after canceling the TRANSFER OWNERSHIP function. The objects chosen in the function are not transferred.Translation object not found or invalid locale.codepage combination for %The Locale and Codepage are valid values but the combination of the two is not.Specify a valid locale.codepage combination.An error occurred when the rule was detranslated to examine it for the given token.Try to edit the rule and save it. If a similar error occurs, contact TIBCO Support.The message log will contain a more detailed error message.
2. Contact TIBCO Support with the log and a description of what actions were being performed when this message was generated.TSO & BATCH user IDs differ; password provided is invalidYou submitted an offline job that has a userid that differs from the TSO user ID. A password was provided as required, but the password was not the correct one for the userid used. Since password prompting is not possible in this case (logon in batch), the logon failed.Resubmit the batch job with the correct password or use the same userid as the TSO user ID for the offline job.The subview table definition contains two fields with the same source name.Change one of the source field names to a different source field in the subview table definition.Two keys must be specified for REPEAT TYPE 'PE'For an ADABAS table definition with repeat type of GRP, exactly two primary keys must be supplied.Supply two primary keys for the table definition.Two or three keys must be specified for REPEAT TYPE 'MU'An ADABAS table definition with repeat type of MU must have either two or three primary keys.Define the correct number of keys for the table definition.Type and syntax combination is invalid for ";" argumentThe argument does not satisfy the type/syntax requirements for the specified shareable tool.Ensure that the value used for the argument has a syntax and type combination that is valid for the specified shareable tool.The semantic type and syntax are an invalid combination.Change either the semantic type or the syntax to make an acceptable pair. Refer to the Processing manual for valid semantic and syntax combinations.Type and syntax require Decimal = 0 for % % of dynamically created table %Decimal must be zero for the combination of semantic type and syntax you specified.Consult the Managing Data manual for information about valid combinations of Type, Syntax, and Decimal.The table definition or the processed program was probably modified since the last pass through the preprocessor.Type error detected in conversion of argument # of % 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.Type in 'S' to select an optional action then press <Enter>The optional selection list is selected by typing S; you can also press <PF4> to access the TABLE screen directly.You must enter the TYPE of event. Valid values for TYPE include V for validation, and T for trigger.Enter T for trigger or V for validation for TYPE, or press <PF1> for selection.Type mismatch for table "%"; source is "%" but target is "%"Because the table type for the specified table does not match on the source and target systems, the apply process cannot proceed as requested.
• include the definition change with this change request
• or if the definition change is in another change request, ensure that change is applied prior to the change to the data.If the target type is correct, return the change to the developer to have the source type fixed.The semantic data types of the fields that you want to relate are incompatible.Choose another field or modify the semantic type of the field definition through the Table Definer.Type of rule "%" cannot be both "V"alidation and "T"riggerYou used the indicated rule for both validation and trigger. A validation rule must be a logical function, whereas a trigger cannot be a function.Change the event type according to the type of the rule.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |