![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This message gives you instructions on how to confirm.The message is one of the following:
• LOCAL VARIABLE "%" cannot be CALLEDRemove the misuse of the local variable or parameter in question.This message indicates that the named object does not exist.You are unable to delete or save the specified rule due to locking or security.
• If due to security, contact your Database Administrator if there is a need for you to be able to read or modify this rule. The Database Administrator can decide if you should be given this authority.Notifies the user that not all promotion rights have been OBTAINED, RELEASED, or TRANSFERRED.Read the message log to find out the reasons.This message is used by the Object Service Broker program that produces the Information Log.Study the TIBCO Object Service Broker Information Log.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.% at exception handler "%" statement # % statement #This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.% at exception handler "% %" statement # % statement #This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.This message is used by the Object Service Broker program that produces the Information Log.Study the Object Service Broker Information Log.You are trying to define the screen table with invalid values for "Last Col/Row" or for "Empty Occs". You need to modify the values so that they are logically correct.Modify the value at the cursor position based on the message.The argument VALUE of the ROUND tool cannot be converted to a binary 4.You specified an invalid date for the date range to be purged.% does not have permissions to purge the AuditlogYou attempted to purge the audit log contents but you did not have the permissions to do so.The DIFFDEFN utility has failed due to an error which cannot be circumvented by the user. When trying to compare definitions, a corrupted definition or unexpected security restriction, or invalid table or data reference error was encountered.No action required although the problem should be reported.This message is used by the TIBCO Object Service Broke program that produces the Information Log.Study the Object Service Broker Information Log.No field can be an ACROSS BY field and SORT BY field at the same time.Remove the field name from the ACROSS BY or SORT BY section.% field "%" does not follow the sequence of % field(s)The BREAK BY fields must be given in the same order as the SORT BY fields. Furthermore, any field that you want to BREAK BY, you must also SORT BY.Change the order of the BREAK BY fields to match the order of the SORT BY fields, or vice versa.An error occurred during the processing of the parameters for a table. The complete message describes the nature of the error.% inside area occupied by %; modify last row/colYou are trying to define two screen tables, but the Origin Row in one screen table is in conflict with the Last Row in another screen table.Modify the value for Origin Row or Last Row in one of the screen tables.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 was generated.Date specification has to be in the format YYMMDD,HHMMSS.% is invalid. Field must exist in table definitionThe value indicated in the message is invalid. It must be defined as a field in the table definition.Enter a value that is a field in the definition.This is a warning that you have entered a blank in the Break Event field of the Breakevent control area.Specify a valid break event, press <Enter>, or press another key.Ask your System Administrator to check the default libraries.The operation specified is not supported between the specified combinations of semantic type and syntax.Verify that the operation is valid. See the Processing manual for more information about operations.You tried to do an arithmetic operation that involved a null value.Verify that null values do not appear in arithmetic expressions.You have specified either a RULE but no LIBRARY or a SCREEN which has presentation-environment-specific definition components but no PRESENTATION ENVIRONMENT. This information is required to fully identify the object you wish to compare.For a RULE, specify which LIBRARY the rule is to be found in. For a SCREEN specify the PRESENTATION ENVIRONMENT which should be used in the comparison.Based on the width of the screen and the screen table image, the indicated part of the screen table may be overlapped.Check the screen table's attributes to see if the screen table needs to be repositioned or modified.% segment number "%" is invalid - it must be numericYou have entered an invalid segment number.You can either press <ENTER> for 0 or enter a number for the segment which you want new table(s) to be stored in.
• Allocation of file % failed. RC=%, ERRCODE=%, INFOCODE=%
• File % is a partitioned data set but a member name was not specified
• File % is a sequential data set but a member name was specified
• The gateway is unable to allocate or open an external sequential or partitioned data set.
• The data set is the wrong type - either partitioned or sequential.
• Parameters have been specified for a non-partitioned data set.
• There is insufficient below-the-line storage available for the DCB.
• Too many Import/Export files are currently open.
• Verify that the external data set exists and contains valid data.
• Verify that parameters have not been specified for a non-partitioned data set.
• Consider accessing Import/Export tables at a separate transaction level so that DCB storage may be released at transaction end and therefore be available for reuse.
• Increase the maximum number of open files allowed by changing the Execution Environment parameter SESSIONFILEMAX.You specified a user exit routine, but did not specify the amount of working storage required by the routine.When using an exit routine, ensure that you specify a value from 1 to 32767 for the EXIT STORAGE field in the table definition.The indicated item has the indicated value, which exceeds the indicated maximum.Reduce the value to less than the indicated maximum.The indicated item has the indicated value, but it must be changed to the second indicated value.The value indicated for the given item is above the indicated range. For example, if you change the length of a variable length character field from 22 to 300, you see a message similar to this:Example Length of field LNAME = 300, is above the range 22 : 254Reduce the value so that it falls within the range given.The value indicated for the given item is below the indicated range. For example, if you change the length of a variable length character field from 127 to 90, you see a message similar to this:Example Length of field ADDRESS = 90, is below the range 127 : 254Raise the value so that it falls within the range given.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |