![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
Identifier "%" exceeds maximum length of % charsThe identifier specified exceeds the present limit of 16 characters.Reduce the number of characters in the identifier.IDgen % must be Type I, Syntax B, Length 4You specified Y for the IDgen field, and therefore you are defining a TDS or IMP table with an IDgen key. If you are also defining a parameter for the IMP table, it must be an IDgen parameter. IDgen keys or parameters must be defined with a semantic type of I, a syntax of B, and a length of 4.Specify the key or parameter attributes accordingly.The table you have just defined has passed all the edits.The indicated subschema definition is no longer defined in Object Service Broker because you confirmed your request to delete it.The deletion of a subschema definition failed.Check the message log for more information. If the cause cannot be determined and resolved, contact TIBCO Support.If flag is 'N', fields must be defined in the same order as in ADABASField ordering is invalid. For Repeat Type of GRP and MU/Special field in Grp of N, the selected fields must be defined in exactly the same order as in ADABAS.Reorder the fields to match ADABAS file definition.The promotion rights for the specified object are held by another user.Check who is holding the rights for the specified object and ask that the rights be released.Ill formed name for % % of dynamically created table %The name you specified for the indicated Field or Parameter does not meet the criteria for a valid Object Service Broker name.Consult the Processing manual for information about the criteria a name must meet.The Image Area contains a new field in the indicated row which was created by typing it into the Image Area. This is not allowed.Import of IMS database definitions cancelledThe IMS database import was canceled by not confirming with <PF22>.Forward the message log to TIBCO Support.Import table "%" could not be repositioned to start of data setYou have entered a DBGCOM containing an ill-formed string literal.Verify that the quotes delimiting, as well as those inside, the string literal are balanced.You have mismatched opening and closing quotes in your input.Insert the closing quote, or delete the opening quote, as appropriate.The string indicated is not surrounded by an appropriate number of quotation marks.The IMS database(s) was (were) imported into Object Service Broker.The IMS Gateway has not been started, or it has failed.Confirm that the IMS Gateway and the Object Service Broker Data Object Broker are started and available. If this problem persists, contact TIBCO Support.IMS offset cannot exceed segment length %When defining a subdivided field, you must keep the offset value within the segment length.Calculate the segment length by adding the offset and length of the last field. Correct the highlighted offset value.The database definitions will be imported into Object Service Broker.In/out argument # of % routine "%" is not a local variable or a field of a tableSome routines, such as TOKEN, modify their arguments. The argument must be a local variable or a field of a table for the routine to be able to modify it.You have requested to copy an object set and its children. However, the object set references an object which requires additional information to identify.Your application has reached a break event you specified. This provides feedback.INBOUND RESOURCE DETAIL ENTRY NOT DEFINED FOR PATH FROM node-nameYou request the display of the Inbound Peer connection on the Resource Detail screen, the identified inbound Peer does not exist.Select a different node name or add the inbound Peer Detail entry by pressing PF5 Add on the Resource Type List screen.INCLUDE statement has appeared alreadyAt least one $ INCLUDE HURON statement has already appeared.Including object set "%" results in a circular referenceYou cannot include the indicated object set because to do so would result in a circular reference of object sets. The simplest example of a circular reference is to have object set A contain object set B, and object set B contain object set A.Remove the indicated object set from the list of object sets in the current object set.Incompatible STARTUP PATH for STARTUP RULE; rule "%" not runThe Startup Rule cannot be found through the Search Path specified in the User Profile. For example, if the startup rule is in the local library, and the search path specifies searching the installation and system libraries, the rule cannot be found. The rule and search path combination is validated in the profile when specified, but events that take place after the information is specified can cause the specification to become invalid.You can EXECUTE the startup rule if you still want to run the rule.If you want the rule to run at the next logon, change the SEARCH field or the STARTUP RULE field in the User Profile.Incomplete fields information - check Print/Control Fields screenAn error or errors were detected in the specified screen.Incomplete function information - check Report Functions screenAn error or errors were detected in the specified screen.Incomplete relationship information - check Relate Tables screenAn error or errors were detected in the specified screen.Incomplete selection information - check Selection Criteria screenAn error or errors were detected in the specified screen.Incorrect % in definition of % "%" of 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.When the specified rule was invoked, the number of arguments supplied did not match the number of arguments defined for the rule.Verify that the rule is correctly defined and invoked.You must either supply all the arguments expected by a rule or none (you will be prompted if arguments are required).Verify the number of arguments supplied.Incorrect number of arguments for shareable tool ";"The number of arguments supplied to the shareable tool is not correct for the function being invoked.Correct the argument list for the shareable tool.Incorrect value specified; must be in the range % to %Correct the input. The message gives you the valid range.Index field must be either be defined as 'K'ey or 'P'arameterInvalid line command entered. IMS Index field must be either defined as a MetaStor key or as a data parameter.Enter line command K or P to define IMS Index as key or parameter respectively.Index field must be selected as 'K', or 'P' before viewing subfieldsVIEW failed. The desired base index field must be selected prior to viewing the sub index fields.Choose the desired base index field as Key (K) or Parameter (P). Press <PF6> to view the sub index fields.Indexing of library "%" completed; Press PF2 for LogsYou asked to have a library indexed. This is done. You can see the Logs by pressing <PF2>.An inappropriate indirect reference to a table or rule has been made.Check the Processing manual to see where indirect references are valid.INDOUBT TRANSACTION RETRIEVAL FAILEDWhen attempting to issue the indoubt transaction retrieval request to the Data Object Broker, an error with the transmission 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 the support center.Infinite loop suspected, handler for exception "%" was executed more than once for rule call ("%" was exception signalled)The statements comprising the handler for a given exception were executed and caused the same exception to be raised.Restructure the exception handler so that it does not raise the same exception.When loading a table, you can only use the following option codes:There is a syntax error in your rule. The input token was found; the other token was expected.Check the Processing manual for the proper syntax, or cancel the changes.The ADDRESS and ENDADDRESS arguments to $GETSTRING are such that the input string or length cannot be read.Verify that ADDRESS and ENDADDRESS are correct and that the string in storage is not corrupt.INSERT access to this object was denied. If the object is a parameterized table, the value of the first parameter for this table instance is indicated.Ask someone who has CONTROL access to the object to provide INSERT access.The user has inserted data into the given table with the specified parameter.INSERT failed: table "%" has max ## rows allowedNo more occurrences can be inserted.The screen table has reached its allowed maximum number of occurrences.
• Using the Screen Table Painter, increase the number of occurrences allowed for the screen table.
• Delete another occurrence before attempting this insertion.INSERT failed for table "%" - row already existsThe maximum number of occurrences allowed for this screen table is one. The rule has tried to insert more than this maximum.Using the Screen Table Painter, check why the screen table was specified to have only one occurrence. Increase this number if possible.Insert not generated, table % missing DB2 NOTNULL fieldsAttempt to generate Static SQL for a DB2 INSERT failed because a DB2 field defined as NOT NULL is not part of the MetaStor DB2 table definition. An attempt to do this insert would fail in DB2.Select all fields marked NOT NULL as part of the MetaStor DB2 table definition or redefine the DB2 table in DB2 to remove the NOT NULL restriction.An error occurred inserting the specified row into @PROMUNBOUNDOBJS and the @PROMUNBINDOBJS tool terminated.Resolve the error specified and run @PROMBINDOBJS before re-running @PROMUNBINDOBJS.When inserting table occurrences, LOAD encountered an error that may be caused by duplicate primary key entries.Delete the duplicate occurrences in the target system and load the object again.The selected fields are not inserted because you did not place the cursor in an area where fields can be inserted.If you still want to select the previous set of fields, press the RECALL function key and then place the cursor in a valid area (PRINT, SORT, BREAK, or ACROSS) before you press ENTER.If you want to select a different set of fields, type an alphanumeric (0-9, A-Z) next to the field names, then place the cursor in a valid area (PRINT, SORT, BREAK, or ACROSS) before you press ENTER.Insertion of selected functions and fields cancelledThe selected function-field pairs are not inserted because you did not place the cursor in an area where the pairs can be inserted.If you want to select the previous function-field pairs, press the RECALL function key and then place the cursor in the summary/break area before you press <ENTER>.If you want to select a different set of function-field pairs, for each pair, type the same alphanumeric (0-9, A-Z) next to the function name and the field name, then place the cursor in the summary/break area before you press <ENTER>.INSTANCE SELECT function is for PARAMETERIZED TABLES onlyIn the UNLOAD first context, you have requested the INSTANCE SELECT function for a table entry where the table is not parameterized.Position the cursor on a parameterized table entry to use the INSTANCE SELECT function. The #PARMS column of the object list display will indicate which tables are parameterized.You had requested to specify which data instances of a parameterized table to unload via the INSTANCE SELECT function. However you requested to CANCEL the changes you made to the specification. The state of the selection list before you requested INSTANCES select will be used to determine which instances to unload.You can request the INSTANCE SELECT function again to double check which instances will get unloaded should you complete the unload request (as opposed to canceling it).INSTANCES function is for TABLES with STORED DATA onlyYou have requested to specify which instances for a table to unload, however the table on the same row as the cursor is not a table which has stored data in it (e.g., it is a TEM, SCR, RPT table).You cannot unload data from a nonpermanent table. Recheck the name.The maximum amount of storage available for an Object Service Broker user to run transactions has been exceeded.Ensure your application does not use an excessive amount of storage. Possible sources of problems may be:
• Inserting a large number of occurrences into a temporary table or screen tableAn Object Service Broker system administrator can limit the maximum amount of storage available to an Object Service Broker user. Refer to the Parameters manual for information about the TRANMEMMAX Execution Environment parameter.In the Screen Table Painter, you requested adding a field in a location where the space is insufficient to add a field.You can do any of the following to gain sufficient space to add a field:You have pressed <PF17> but there is no room to paste the field.Paste the field elsewhere, or move the other fields to allow the field to be pasted where first indicated.You pressed <PF17> but there is insufficient room, as the pasted field would overlap the physical boundaries of the terminal screen.Insufficient security clearance to % change#%You did not have sufficient security clearance to perform the specified action against the specified change.Ask your Security Administrator or Promotion Administrator for the required security clearance.Insufficient security clearance to % defn of % %You did not have sufficient security clearance to perform the specified action against the definition of the specified object.Ask your Security Administrator or the owner of the object for the required security clearance. Then apply the change again.Insufficient security clearance to % occs of table %You did not have sufficient security clearance to perform the specified action against the occurrences of the specified table.Ask your Security Administrator or the owner of the object for the required security clearance. Then apply the change again.You do not have security clearance to access the specified object.Ask your security administrator for the required security clearance.You did not have sufficient security clearance to create the specified table.Ask your Security Administrator or the owner of the base table for the required security clearance. Then apply the change again.Insufficient security clearance to run this utilityThis utility can be run by a selected group of users only and you are not a member of that group.Contact your DBA to include you in the group which can run this utility.Insufficient space for COPY: <PF3>/COPY PARTIAL or <PF12>/CANCELIn the Screen Table Painter, you wanted to load a whole table; however, the screen table does not have sufficient space.Insufficient space to return all remote log messagesDuring a distributed data access, a condition occurred at the remote node that caused error or informational messages to be written to the system log on the remote system. When the system attempted to transfer these messages back to the local system log, there was not enough space in the peer-to-peer message buffer to contain all of them. The usual reason for a large remote log is the failure of a remote trigger rule and the dumping of its local variables, active tables, and so on. As well, log information shares the buffer with any table occurrences being returned, so a number of successful operations within a FORALL, followed by a failure may not leave room for all the messages.Investigate the reason for the failure on the remote system. It may be necessary to reproduce the problem by accessing the remote table from a rule on the remote system, and examining the log on that system.Insufficient storage for DISPLAY & TRANSFERCALLNot enough session storage is available to contain the definition and data for the current screen.Decrease the amount of storage required by either simplifying the definition of the screen or having fewer occurrences in the component screen tables.Integrity Failure: Cannot order join cursor %Join cursors reference many tables. To sort outcome, one would need to create a storage table on the fly. The preprocessor cannot create one.Define a table to store outcomes, declare a cursor for the table by specifying order clause, and use this cursor to retrieve an ordered selection.Join type cursors cannot update tables referenced in the join.Use some other ways to update the tables referenced in the join.The promotion rights on the current table cannot be determined, probably as a result of locking. Therefore, the specified operation, which requires changes to the table, cannot be performed.The table cannot be printed because an INTEGRITYFAIL exception was raised.COMMIT operations for certain external tables cannot be followed by any other table or transaction operator in the same transaction. Refer to the appropriate Object Service Broker documentation for the rules governing each external table type.ROLLBACK operations for certain external table types cannot be followed by any other table or transaction operator in the same transaction. Refer to the appropriate Object Service Broker documentation for the rules governing each external table type.Remove any request for an intermediate ROLLBACK.This is a first-level message for an internal editor error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of what actions were being performed when this message appeared.Internal error; contact the Customer Support CenterThe Table Editor has an unexpected error situation.Internal error in $LISTDSN - IGGCSI00 parmlist errorThis is an internal error in the $LISTDSN built-in routine.Internal error in $LISTDSN - IGGCSI00 parmlist pointer was zeroThis is an internal error in the $LISTDSN built-in routine.Internal error obtaining definition for table "%"The program for the table definition retrieval is illegally called.Internal occurrence length error for table "%"The occurrence length in variable length format is longer than the dictionary record length in fixed length format.Change all the field lengths in the definition of the table, and ensure that the total field length matches the occurrence length.One of the parameters on the connect of the gateway/server session was found to be in error.Check that libraries of compatible versions were used, and that the parameters you provided were correct.Internal report server error: attempting to read a file that is not open for INPUT processingThe Report Server detected an inconsistent server action.Internal report server error: attempting to write to a file that is not open for OUTPUT processingThe Report Server detected an inconsistent server action.Internal report server error: Invalid sequence of report blocks when printing report "%"The Report Server detected an invalid state while producing a report page.Internal report server error: Invalid source opcode for a report field. Report table is "%"The Report Server detected an error in the data structures that describe a report.Internal report server error: Invalid source opcode for report field "%" of report table "%"An internal Report Server error was detected while the server was evaluating a derived report field.Internal report server error: recursion stack overflowAn error was detected during the building of the definition of a report.Internal report server error: report function accumulator has an invalid syntaxAn error was detected in the data structure of the Report Server.Internal report server error: report function value for derived field "%" of "%" was not foundAccess to a computed report function failed during report page formatting.This row or col is invalid. It should be positive rather than negative.Page Occ and Page Across values must be numeric or an asterisk ("*"). A number indicates the number of occurrences or across repetitions to allow per page. An asterisk indicates that as many occurrences or across repetitions as will fit on a page are to be allowed.An invalid row or column was specified.Invalid "Attribute Name" in $SETRPTATTRIBUTEThe second parameter of $SETRPTATTRIBUTE is not one of:
•
• OCCLIMIT (Limit occurrences used to generate report)
•
•
• EJECT (Control page eject if more than 1 report in transaction)
• PAGENUMBER (Set new starting page number).Correct second parameter to match one of the listed values.Invalid %; must be between 0 and 255 (inclusive)A Security Administrator specified an invalid TDS segment number. Valid numbers are in the range 0 to 255, but the number of segments being used are installation dependent.Invalid access to table "%". Null parm "%" not allowedThe user tried to access a table with a null parameter value.Invalid access to table "%": duplicate reference in parameters list and WHERE clauseFor the same request, a parameter specified in a WHERE clause is also specified in the table reference.Remove the parameter reference in either the WHERE clause or the table reference.Invalid access type for table "%" of VSAM % "%"The specification in the TYPE field of the table definition is not one of the following VSAM access types:
•
•
• The variables in the message, from left to right, are as follows:Change the TYPE value in the table definition to one of the allowed values.The action must be one of IS or IR for an object definition, or one of IS, IR, MI, or MR for table data.The action specified is not supported. The following line commands are supported:Change the line command to G or R, or remove the action.Invalid address specified in call to %. ADDRESS must be less than or equal to ENDADDRESSThe ENDADDRESS argument to $GETSTRING or $SETSTRING is the address just past valid storage and is used to protect against reading or writing to invalid storage. The ADDRESS argument is the storage address where you will read or write the next string, and so it must have a value less than or equal to ENDADDRESS.Correct ADDRESS and/or ENDADDRESS so that they refer to the same block of storage and ADDRESS is less than or equal to ENDADDRESS.Argument # of the $SETTITLE tool cannot take the value zero (0).One of the following arguments does not meet specifications:Invalid attribute "%" for "$SETATTRIBUTE"You specified an invalid attribute as a parameter to the $SETATTRIBUTE tool. Valid values are:Change the utility call to specify one of the valid values.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 internal Report Server error was detected in the definition of a report function.The category is the reason for the change request. Valid categories are listed in the Help.Invalid CLASSIFICATION "%"; must be 1..7You have specified an invalid classification for the object whose Access Control List you are updating.You must specify the classification to be a number between 1 and 7.You specified an invalid color for the utility $SETCOLOUR. Valid colors are those defined in the table @COLOURS.Change the invalid color to one that is present in the table @COLOURS.The color code for the indicated field is not one of the valid codes defined in the table @COLOURS.Change the value of @SCREENFIELDS.FOREGROUND or @SCREENFIELDS.BACKGROUND to a valid color code.Invalid color type "%" for "$SETCOLOUR"You specified an invalid color type for the utility $SETCOLOUR. Valid types are F (foreground) and B (background).Invalid column specified for COPY/APPEND resultsThe column indicated as the target position for the results of a COPY/APPEND command cannot contain the copied fields and headings without causing an overlap condition, or exceeding the maximum report width.
• Reposition the cursor to a row and column that will not cause a copied field to overlap existing report fields or exceed the maximum report width.
• Use the keyword NONAMES after the APPEND command to indicate that no headings are to be copied.The column number that you gave as an argument to the SETCURSOR_POS tool does not fall within the number.Change the column number to fall within the range of columns in the specified screen field. The range begins with 1 and extends to the length of the field.Invalid combination of arguments for ";": OFFSET "#" + LENGTH "#" > LENGTH(STRING) "#"Adjust the arguments so as to satisfy the stated constraint.Invalid combination of screen/table/field specified for "%"Either the screen, screen table, or screen field name has not been specified for the indicated utility.Make sure that the screen, screen table, and screen field names are specified in the utility call.Invalid command: "%"; Use "P"-parameter "K"-key "S"-selectThe indicated command is invalid. Use one of the following line commands:Change the line command to a valid command.The indicated command is invalid; you can use only S to select fields.Change the invalid command to S if you want to select that field; otherwise, remove the invalid command.You have entered an invalid command.Enter a valid command. If necessary press <PF1> to see a list of the commands.An invalid primary command was entered.The indicated parameter value is an invalid constant.You specified an invalid current group in the user profile screen.You can use the MEMBERSHIPS function to determine valid current groups, or change the CURRENT GROUP field to null so that you are not operating out of any group.INVALID CURSOR POSITION FOR COMMAND SELECTIONThe Administrator processing was unable to determine which operator request you wished to invoke.Reposition the cursor using the tab key and try your request again.Invalid D/C indicator "%" - must be "D"ebit, "C"redit, or "_"The specified indicator is invalid. It must be one of the following:Change the D/C indicator to a valid character.You specified an invalid data set name in the Rule Printer utility.Invalid data value in syntax W field - DBCS delimiters are not pairedThe DBCS delimiters are not paired.Supply missing DBCS delimiter. Alternatively, remove unpaired one.Invalid data value in syntax W field - odd number of bytes between DBCS delimitersThe value in the syntax W field yields an odd number of bytes between the DBCS delimiters.Verify the number of bytes between the DBCS delimiters.Invalid data value in Unicode field - Length field incorrectEither the length value for a Unicode field is not even or the length is two and the first two bytes contain the first half of a surrogate pair.The IMS database name that you entered is not defined or loaded into the MetaStor.Press <PF4> for a list of valid IMS database names and select one from the list.You specified a date value that does not conform to the expected date format.Change your date value to the indicated expected format and try again.The indicated date display mask is invalid.Correct the date display mask. You can refer to the Reporting manual for a description of valid date display masks.The format you have used for the .date command is unsuitable for the tool $TRXDATE.Refer to $CREATE_DATE in the Shareable Tools manual for the correct syntax to be used with this rule.Invalid date in GO TO date specificationYou have specified a date which you wish to go to in the Appointment Book; however, there is no such date.Change the date to a valid data and press <Enter> again.The field in error is supposed to be a pure double-byte character set (DBCS) field, where each character is represented by 2 bytes.Correct the field so that it contains an even number of bytes, representing a DBCS string.The specified text contains an invalid DBCS subfield. A DBCS subfield represents a string of DBCS characters within a mixed string. Each DBCS character is represented by 2 bytes so the length of the DBCS subfield must be a multiple of 2.Correct the DBCS subfield (the data between the "Shift Out" and "Shift In" characters) so that it contains an even number of bytes.A string contains one of the characters SO or SI (Shift Out or Shift In) without the other. DBCS subfields must start with an SO and end with an SI.Add a "Shift Out" or "Shift In" character so that all DBCS subfields in the string are valid.The DDname that you provided is not a valid Object Service Broker identifier.Enter a valid Object Service Broker identifier. See the Object Service Broker Documentation for more information about Object Service Broker identifiers.You did not enter a positive number in the MetaStor decimal field to indicate a decimal length.Enter a positive integer value in the decimal field.You referred to an invalid default security group in the User Profile screen.You can use the MEMBERSHIPS function to determine valid default security groups for the profile.Invalid derived defn request:"%" is not defined as DERIVEDA derived field definition was requested for a non-derived field.Position the cursor on a derived field before requesting derived field definition.An invalid display mask has been specified for the indicated screen field.Correct the display mask specification using the Screen Definer and Screen Table Painter.INVALID DUMP IDENTIFICATION ITEM SPECIFIEDThe item number you input to request a diagnostic dump is invalid.Invalid encoding "%" specified in call to %. Use ASCII, UTF-8, UTF-16BE, UTF-16LE, UTF-32BE, or UTF-32LEThe ENCODING argument for $GETSTRING or $SETSTRING does not have one of the supported values.Action parameter for $SETSESSIONEND is not a valid action to be performed when the user's session ends. Valid actions are START, XTCL, FORMAT, SWITCH, RETCODE, RC, and ABEND.Change the call to $SETSESSIONEND to pass a valid session end action.Invalid exception name for a SIGNAL statementInternal 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.You must enter a positive integer for the field length.Check the field name that you specified and try the procedure again.Invalid field number found in dynamically created table %@DOFFIELDS.NUMBER does not correspond to the field's position in the table.Set @DOFFIELDS.NUMBER to correspond to the occurrence number in @DOFTABLES.FIELDS.The indicated field is not a valid field of the indicated table.Check the table definition and specify a valid field name.Invalid field specified for COPY/APPEND of report table "%"A copy of a table.field has been requested, but the field specification is invalid.Specifying only a table in a COPY or an APPEND operation will display a prompt list of all available fields on the table. The required field can then be selected.Invalid field syntax for ORDERING - field "%.%"The indicated field is syntax F (floating point), which is invalid for ordering a screen table.Either change the syntax of the screen field or do not try to order occurrences based on the indicated field.The filter key supplied for the $LISTDSN is not allowed.Check the Shareable Tools manual for valid formats.Invalid footnote definition in screen table "%" within Screen "%"
1. The footnote text exceeds the number of rows specified for the occurrence.
2. Correct the screen definition by using the Screen Table Painter.INVALID FUNCTION KEY HIT, OR FUNCTION RESTRICTEDThe function key you pressed is either invalid for this screen or provides access to a function for which you do not have security clearance.Verify you pressed the key you intended, contact your security administrator to arrange the appropriate external security. Refer to the Security manual for further details.You assigned an invalid hexadecimal number to a Unicode or raw data field of an occurrence.Assign a valid hexadecimal number to the field.The table you selected from the list is not an IDMS table. The table type was changed by nonstandard methods.Try to find out why the table type was changed. If it should not have been changed, edit the TABLES table and change the table type back to IDM. You can then use the Table Definer to see if the table definition was also changed, and change it back, if necessary.The value in the IMS length field is not a positive value.Enter a positive integer value that does not exceed the length of the current segment.The IMS offset field has a negative or null value.Enter a positive value in the offset field, but ensure that the offset value does not exceed the length of the segment.The evaluation of an indirect reference to a field did not yield a name.Verify that indirect references to fields resolve to names.The evaluation of an indirect reference did not produce a name.Verify the expression for the indirect reference.The evaluation of an indirect reference to a table has not yielded a name.Verify that indirect references to tables resolve to names.Invalid input: % is not a text table nor a valid parameterTED was executed with an input argument that is neither the name of a text table nor a parameter of @TEXT.You have pressed a PF key that is not defined.Invalid key type "%" - must be "P"rimaryThe indicated key type is invalid. It must be either P (primary key) or S (secondary key). Since the Table Definer does not create secondary indexes, you can specify only P.
• Remove the invalid key type and build a secondary index by using the SIXBUILD tool. See the Shareable Tools manual for more information.Invalid LENGTH and/or COL specified - max report width is %The maximum width that a report field can be defined is indicated.Ensure that each report field does not extend beyond the maximum width.Invalid length specification; must be either F or VYou have specified an invalid length specification for the input file.Specify whether the input file is fixed (F) or variable (V) length.Invalid length specified; must be in the range 1 to 3915You specified an incorrect field length.Correct the input. The field length must be in the range of 1 to 254 bytes.You tried to define a Library, but the name you provided is not a valid library identifier (e.g., the identifier has internal blanks, starts with a number or an invalid character, etc.).Specify a library name that is up to 8 characters in length, has no internal blanks and no invalid characters.You specified an invalid value for the record limit.You entered an invalid line command.Enter a valid line command. Press <PF1> for a list of valid line commands.Invalid line command: Only D-Delete line command is allowedYou have specified an invalid line command to be operated on the location parameter.Specify only the D line command to delete the location parameter.The specified character is an invalid line command.Remove the line command or change it to a valid command. You can get a list of valid line commands by pressing <PF1> for Help.You entered a character that is not a command in the line command position.Remove or correct the invalid character. Press <PF1> for a list of valid line commands.The line command you entered is not valid on this screen. Valid line commands are listed at the bottom of the screen.Invalid line specification: % - a number is requiredYou issued the script command .tm or .bm to specify the number of lines for the top or bottom margin but you did not specify a valid number.Specify a valid number for the top or bottom margin lines.Informs you that the location is invalid.You have specified a location which does not exist.Remove or correct the location specification.You assigned an invalid logical value to a logical field of an occurrence.Assign a valid logical value (Y or N) to the indicated field.You assigned an invalid logical value to a logical field of an occurrence.Assign a valid logical value (Y or N) to that field.You have not entered either Y or N into the SCROLL prompt in the screen table definition.This is an internal error in the screen server.
2. Contact TIBCO Support with the log and an exact description of what actions were being performed when this message was generated.You typed over the month name with an invalid month name.The indicated name is not a valid Object Service Broker object name.Change the name so it is valid. A valid name is any character string up to 16 characters beginning with a letter (A-Z) or a special character ($ or #), and continuing with more letters, special characters, digits (0-9), or underscores (_).The grammar definition of % is invalid as it contains a transition to a non-existent state.If the grammar was supplied with Object Service Broker, contact TIBCO Support.If the grammar is user-defined, examine the grammar and either add the state or remove the attempted transition to that state.An invalid numeric constant has been detected (possibly one too large to represent).Check the Processing manual to determine the form of valid numeric constants.You assigned an invalid value, such as a string, to a numeric field of an occurrence.You assigned an invalid value, such as a string, to a numeric field of an occurrence.Invalid number of copies %: must be from 1 to 255In the User Profile screen, you specified an invalid number of copies for the print parameters; the number must be in the range 1 to 255.Invalid number of parameters supplied for table "%"The number of parameters supplied for a table access does not match the number of parameters defined for the table.Check the table definition for the parameters and based on this information correct the number of parameters that you are supplying.Invalid number of parameters supplied for table "%"The parameters specified in a table request (INSERT, GET, REPLACE, DELETE, or FORALL), and/or in an accompanying WHERE clause, are different from the parameters in the definition of the table.Make sure that all parameters in the table definition are specified in a table request, and/or the parameter names in the accompanying WHERE clause are specified correctly.Invalid object code in detranslator rule "%" at offset %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.You entered a line command that is not listed at the bottom of the screen.You have specified a break event using either the primary command area or the break event control area. You may have misspelled the name of the object qualifying the break event to be set.Invalid OBJECT_TYPE % - use PF1 key to select valid typesThe KEYWORDSEARCH tool has been called with an invalid value for the argument object_type.This argument indicates which type of object to search for, and must be one of the following single characters:
• Check the valid selection syntax in the calling rule (see the traceback). Also check for a valid stored selection in the definition of the specified table. If this is correct, push <PF2> and print the log, then contact TIBCO Support, or the Database Administrator, with the log and a description of what actions where being performed when this message was generated.Invalid opcode in selection string for access on table "%"Invalid operation code found during security checkingUnexpected condition detected during clearance checking.Print the message log if possible. Log off and log on before continuing. Contact TIBCO Support.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.During a FORALL, a non-existent field was specified for ordering.
2. Add the field to the table on which the ordered FORALL is to be done.You specified an invalid OTMA function request to the $OTMA built-in routine. Valid function requests are: OPEN, ALLO, SEND, FREE and CLOS.If the function shown in the message text is OPEN, this indicates that you already have an IMS OTMA connection open. Only one connection is allowed per session.Correct the error and retry. Refer to the sample rules in the Shareable Tools manual.If the function in error is OPEN, close the current connection before opening another one.While processing a backup file, the utility has encountered an invalid page. Additional messages will indicate the exact nature of the problem.Refer to accompanying messages for additional instructions.Invalid parameter: % - must be "#", "t", or bullet charactersThe list command requires a parameter of: #, T, or the characters that are assigned to be bullets.Invalid parameter: % - must not be negativeA negative number has been given as a parameter.Numeric parameters must be non-negative, whole numbers.Change the parameter number to a positive, whole number.The indicated name is not a parameter for the indicated table.Check the table definition for the correct parameter names, and change the selection string accordingly.Invalid parameter or field in selection string for access on table "%"A parameter or field specified in a table access statement is not a parameter or field of the indicated table. The table definition or the processed program was probably modified since the last pass through the preprocessor.Verify the parameter and field names, and preprocess the program again.The indicated parameter value is invalid and an explanation is provided.Modify the selection string accordingly by assigning a valid value to the indicated parameter.Invalid parameter value; bad source data for parameter %You specified an invalid value for the indicated parameter. For example, specifying a string value for a numeric parameter is invalid.Try again using a valid value for the indicated parameter.Invalid parameter value; source number too large for parameter %You specified a value that cannot be represented by the syntax defined for the indicated numeric parameter.Try again using a value within the range of the syntax. See the Managing Data manual for a description of valid values.Invalid parameter value; source number too small for parameter %You specified a value that cannot be represented by the syntax defined for the indicated numeric parameter.Try again using a value within the range of the syntax. See the Managing Data manual for a description of valid values.Invalid parameter value; source string too long for parameter %You have specified a string value which is too long for the indicated parameter.Try again using a shorter string value for the indicated parameter.Invalid PF key assignment: must be 0 (disabled), or 1..23In the Screen Definer, you assigned a standard function to an invalid PF key. Valid PF key values are in the range 1 to 23 and 0.If you want to disable the standard function, assign 0 to the PF key. If you do not want to disable the function, assign a value based on:
• How many function keys are available in the destination screen
•
1. After an INSERT or REPLACE to a VSAM table with multiple record types, the length of the record about to be written to the VSAM file does not match the physical record size of the file. This error can occur for RRDS and ESDS type VSAM tables, which must have all physical records the same length.
2. When accessing a VSAM KSDS base cluster with an attached alternate index, the alternate index RECORDSIZE is not big enough to add another duplicate base key occurrence in the current alternate index record.Depending on the cause of the problem, do one of the following:
1. Either alter the parent or child VSAM table definitions, or else change the number of INSERTs or DELETEs of child records such that the total record size matches the physical record size.
2. Rebuild the alternate index specifying a larger RECORDSIZE.Invalid presentation environment for this objectThe environment of your system does not support the presentation of this type of object.Use a system that supports the presentation of this type of object.You entered an invalid primary command.The primary key selection cannot be rationalized.You have specified an invalid print class for your output setting. A valid print class must be an alphanumeric character A-Z or 0-9.You have specified an invalid print class for your profile. A valid print class must be an alphanumeric character A-Z or 0-9.You specified an invalid print destination for your print parameters in your user profile.INVALID PROFILE SELECTION ENTRY NUMBER SUPPLIEDThe item number you specified in the input field is invalid.Select one of the values listed on the screen and retry your request.The CROSSREFSEARCH tool was called with the parameter QUERYKIND set to an invalid value.This parameter indicates the type of search to conduct, and must be one of the following strings:
•
•
•
•
• Enter a valid Object Service Broker identifier. See the Processing manual for more information about Object Service Broker identifiers.You accessed the indicated dictionary table by using an invalid method. The dictionary table is one of the following:
• If the indicated dictionary table is $$SYSTABLES, you cannot access this table.
• If you want to access the $$SYSPARMS or $$SYSFIELDS tables, use an unqualified FORALL statement.This is an Object Service Broker internal error. The Screen Server has been called with an invalid request code.
2. Contact TIBCO Support with the log and an exact description of what actions were being performed when this message appeared.You are trying to perform one of the following operations: OBTAIN all rights, RELEASE all rights, or TRANSFER all rights on an object. However, the type of the promotion rights (DEFN, DATA, etc.) that you have specified for that object is invalid or does not match with the type of rights available for the object.Check the promotion type of the specified object and try again.Invalid row/col for screen table "%" within Screen "%"The screen table has been specified to start at a position outside the bounds that the Screen Server can handle.Using the Screen Table Painter, check the start rows and columns for the screen table. If any unreasonable values exist, such as row = 600 or column = -350, change these values and try the rule again.An invalid row or column was entered in the definition area. Row and column values must be numeric and greater than zero.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.Invalid ROW for COPY/APPEND; copy requires 3 rows; exceeds %The copy of a field and its headings requires 3 rows.
• Position the cursor to a row that has 2 rows available below it for the copy results, and press <ENTER>.
• Use the NONAMES keyword with the COPY or APPEND command so that the headings are not copied. In this case, you need only 1 row.The rule name that you provided is not a valid Object Service Broker identifier.Enter a valid Object Service Broker identifier. See the Processing manual if you want to know more about Object Service Broker identifiers.Invalid scope for report function "%" of report field "%" in report table "%"The scope of the report function was not one of REPORT, RUNNING, or PAGE.Use the Report Definer to correct the derived report field.An invalid Scope value was specified for the @PROMUNBINDOBJS tool.Specify a valid Scope value of SYSTEM, INSTALLATION or ALL.You specified an invalid value for the scroll amount.Press <PF1> for a list of valid scroll amount values. Try again with a valid value.You entered an invalid amount in the scroll field. The invalid scroll amount was replaced with a P (Page).If you do not want to scroll by pages, enter another valid scroll amount. They are:
• You entered an invalid scroll amount for vertical scrolling. Valid scroll amounts are:
• Enter a valid scroll amount and press <PF7> or <PF8>.You specified an invalid value for the scroll amount.Press <PF1> to invoke field-level help to display a list of valid scroll values. Try again with a valid scroll value.You specified an invalid value as parameter SEGMENT# to one of the following tools: $GETENVCOMMAREA, $SETENVCOMMAREA.You put an invalid selection character beside an object in the Transfer Ownership screen. Valid selection characters for this screen are blank, null, and S.If you do not want to select the object, type over the invalid character with a blank, or remove it (i.e., becomes NULL). If you want to select the object, replace it with an S.Invalid selection string during FORALL on table "%"The requested or stored selection is syntactically invalid.Verify that the stored selection was not modified outside of the Table Definer. If modified, redefine the table again.Invalid selection string for report field "%" of report table "%"A syntax error was detected in the selection string for a report function.Using the Report Definer, review the selection string for report functions that were used in the source of the derived report field.A syntax error was detected in the selection string for the body report table.Using the Report Definer, review the selection string for a body report table with syntax errors.Invalid selection term using parameter "%" in % selection for table "%"In an input selection string the selection term/clause using a table parameter must be of the format:Example TableParm "=" valueIn a stored selection a selection term using a table parameter or source-table parameter can have one of the following formats:Example SourceTableParm "=" valueExample SourceTableField RelationalOperator TableParmReplace the selection clause with one of the valid formats.Unable to list ADABAS COLUMNS for selection.Specify the ADABAS Database ID (DBID) and FILE No for COLUMN selection.You did not enter a valid MetaStor semantic type in the MetaStor TYPE field.Consult the Managing Data manual for information about valid MetaStor semantic types.Invalid semantic type for OF-FIELD "%" of report function "%"; see report field "%" of report table "%"The semantic type of the indicated OF-Field is not valid for the indicated report function.Either change the semantic type of the OF-Field or use a different report function for the derived field.The type of gateway/server you will be running as must be supplied.Supply the gateway/server type in the parameters before starting the gateway/server.The value for $SETSESSIONEND action is invalid. For actions of START, XTCL, FORMAT, and SWITCH the value must be a string of a maximum length of 8. For actions of RETCODE, RC, and ABEND the value must be an integer.Change the call to $SETSESSIONEND to pass a suitable value for the action specified.Invalid session menu % in user profile; STANDARD is usedYour user profile names a menu that is not a logon menu or does not exist.The set name you specified on the VERIFY ACCESS PATH screen is incorrect or invalid.Correct the set name; you can find valid set names by returning to the SELECT RECORDS screen, and using the ? line command to list all valid set names.Invalid setup: % - Default setup has been assumedA non-existent setup name has been given in the setup command.Invalid sort direction in ordering of dynamically created table %You specified a sort direction other than blank, "A", or "D".Invalid sort order for report field "%" of report table "%"The sort order in the control information of the report is invalid.Use the Report Definer to correct the sort order. Sort orders can be either A (ascending) or D (descending).Invalid source: "%"; specify either "DATABASE" or "ARCHIVE"You invoked the BATCH_UNLD_CARDS tool, and specified an invalid source as the input parameter to this utility.Specify either "DATABASE" if you want to unload from the MetaStor, or "ARCHIVE" if you want to unload from an archive backup file.Invalid source: valid values for location parameter SRC are: %You have assigned a value other than those allowed for the SOURCE attribute of a location parameter.Specify the correct value as the SOURCE attribute value.Invalid source for report field "%" of report table "%"The source of a derived report field contains a syntax error.Use the Report Definer to correct the report field.Invalid string: % - "on" or "off" is requiredThe command requires a parameter which must have the value of ON or OFF.Invalid string: % - "on" or "off" or a number is requiredA correct parameter value was not supplied.The command requires either the parameter ON or OFF, or a number.The command requires a parameter in the form of a number, and the number was not supplied.
2. Contact TIBCO Support with the log, and a description of what actions were being performed when this message was generated.The indicated parameter has invalid syntax; only B (binary), P (packed decimal), and C (fixed character) are allowed.Change the syntax of the indicated parameter to a B, P, or C.Change the syntax to a valid value. See the Processing manual for valid syntaxes.The mentioned field is improperly defined.Use the Table Definer to assign a valid TBCO Object Service Broker syntax to the field.You entered an invalid syntax in the MetaStor SYN field.Enter a valid syntax. See the Managing Data manual for a list of valid syntax codes.Invalid syntax for % % of dynamically created table %The syntax you specified for the indicated Field or Parameter is not supported for the specified semantic type.Consult the Managing Data manual for information about valid MetaStor syntaxes.Invalid syntax found in dynamically created table %An internal conversion of the contents of @DOFEXTFIELDS encountered an invalid syntax. This should never occur in the course of normal operation.Invalid syntax specified; press <PF1> for list of valid syntaxesCorrect the input. Valid values are given in the message. Press <PF1> for Help to find a detailed explanation of each syntax value.A screen routine (e.g., $SETATTRIBUTE) has been passed a non-existent screen table or field parameter for the Screen parameter provided.Use the correct combination of screen, screen table and field parameters.The source table must be one of: TDS, TEM, SCR, IMS, or EXP.Make sure that the table type used is one of the allowed values.Invalid table type for reference table "%" on table "%"The table that you reference cannot be of type SCR, EXP, or RPT.External sort is unable to find the directory name supplied in the Workfile parameter.Supply the SORTUNIT parameter with a valid directory name. For more detail, refer to the Parameters manual.In the User Profile, you have specified an invalid TIMEZONE. The TIMEZONE is really an OFFSET from the system time. So, if you are say, 3 hours ahead of the system time, then the TIMEZONE setting should be 3. If you are 3 hours behind system time, then set TIMEZONE to -3 and so on. Note that your RESTRICTED HOURS are according to SYSTEM TIME.Set the TIMEZONE according to the difference between your local time and the time in which the system operates.Invalid token "%" in selection string for report field "%" of report table "%"A syntax error was detected in the selection string for a report function.Using the Report Definer, look for the syntax error near to the token listed and correct the error.Invalid token "%" in selection string for report table "%"A syntax error was detected in the selection string for the body report table.Using the Report Definer, look for the syntax error near to the token listed and correct the error.Invalid token "%" in source of report field "%" of report table "%"A syntax error exists in the source of a derived report field.Use the Report Definer to fix the syntax error in the report field.Invalid type/syntax combination for % % of dynamically created table %The combination of semantic type and syntax you specified for the indicated Field or Parameter is not supported.Consult the Managing Data manual for information about MetaStor semantic type and syntaxes.The type and syntax specified for a report field within the definition area cannot be used together.Consult the Object Service Broker documentation for the correct type and syntax combinations.You have defined a field with an invalid TYPE/SYNTAX combination.Refer to the Text-based Presentation manual for valid values, and correct your definition.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.The semantic type specified is invalid.Change the type to one of the valid values. See the Processing manual for valid semantic types.Invalid type for % % of dynamically created table %The type you specified for the indicated Field or Parameter is not recognized.Consult the Managing Data manual for information about valid MetaStor semantic types.The FROM and TO fields must have non-negative integers with the value of the TO field greater than the FROM field.Invalid use of $PAGE_NUMBER for report field ";" of report table ";"The specified field references the report function $PAGE_NUMBER either directly or indirectly, and is also a break, sort, summary, or across field. Since the page number in a report is dependent on the break fields in the report, the break fields cannot be dependent on the page number or we would have a circular definition.Change the report definition so that there are no circular dependencies.The userid or IDPREFIX that was supplied was not valid, or not unique in this environment.Ensure that your userid is valid, and that only one gateway/server run with the supplied IDPREFIX.The userid that you specified has embedded blank or special characters, such as quotation marks or parentheses, which do not make it a valid single token.Make the necessary correction to the userid value and try again.Invalid userid; % starts with an illegal characterThe userid that you specified has an invalid starting character. A userid must start with either an alphabetic character, $, # or @.Make necessary correction to the userid value and try again.You specified a userid which has either less than 3 characters or more than 8 characters.Make necessary correction to the userid value and try again.The indicated value is invalid for the indicated field.Invalid value for % parameter; ensure type-compatibleWhile specifying an instance of a table, you entered a value for a parameter of the table that is incompatible with the defined type and syntax of the parameter. For example, if you enter B5 for a DATE type parameter, you will see this message.Remove the offending value and replace it with a valid one.
• This message applies to arguments OPTION_NAME and OPTION_VALUE of the $BATCHOPT tool. You cannot assign the latter value to the former.If the error was caused by the $BATCHOPT tool, supply a valid value. If not, contact TIBCO Support.A value in the selection cannot be used in the selection.Correct the value. This may require that a date be expressed in the format used on the screen, YYYY-MM-DD.Invalid version; enter V2.2, V2.3 or leave blankThe DB2 version number entered did not match the allowed values of V2.2 or V2.3.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |