![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
You canceled a request to back out a promotion.The specified number of objects were backed up before the change was applied to the system.The Promotion utility has backed up both definition and data of the specified number of tables so as to allow subsequent backout of the change.Backed up data only for % tables or table instancesThe Promotion utility has backed up the specified number of tables or table instances so as to allow subsequent backout of the change.The Promotion tool backs up old objects before deleting them so that they can be restored if the promotion is backed out.You canceled the backout process. The status of the change request did not change.Backup file contains % page files - segment '%' contains % page filesThe backup file contains a different number of page files than the segment.Correct the ACBS parameter of the DBDEF for the segment and/or ensure that all files for the segment have been correctly defined and initialized.Backup file contains too many pages for segment '%'The backup file has more pages than the segment is capable of handling.Run a verify (-v) on the backup file to determine the number of pages in the segment. Reformat the segment to allow for the number of pages in the backup file.The target of a restore operation is not large enough to contain all of the pages in the backup set. The utility is terminated.Redefine the target segment with enough space to contain the backup set and rerun the utility.Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.Internal error. The message log contains a more detailed error message.
2. Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.BASE SEGMENT (0) CANNOT BE MODIFIED ONLINEYou have requested modifications to the base segment (0). This segment contains the MetaStor and cannot be modified while the Data Object Broker is running.To make changes to the base segment refer to the appropriate documents. Recycle the Data Object Broker to invoke those changes.Batch connections are not accepted at this timeThe Data Object Broker is not available for batch at this time.Resubmit the session when the environment is ready.Batch job submitted for: % time: % to generate Static SQLA batch job has been submitted to generate the requested Static SQL.A batch request was not found on the indicated queue as expected.You are trying to print an object and an object, which is defined by the object you specified, is now printing.You have defined a field to have a SYN of B but also defined it to have decimal places. This definition is not valid.Change the SYN to a syntax which allows for decimal places, or change the field definition to have 0 decimal places.You have defined a field to have a SYN of binary but given it a LEN greater than 12.Enter a valid value no greater than 12 to LEN, or change the syntax.Binding failed: Press <PF2> for more informationYour request to bind the indicated screen failed.If the failure was due to locking, try again later. If the failure was due to security, contact your Security Administrator.You did not specify any letters to use to invoke the command.Both DBID and FILE NO. must be enteredRequired field DBID and/or FILE number are missing.Both from and to tokens are %; no change necessaryYou have entered the same thing in both the FROM and TO columns.Enter the token you wish to have changed in the FROM column and the token you want to replace it in the TO column.This message indicates that one of LAST COL or LAST ROW is "0" or empty but the other is not. "0", or empty, is the default value for these fields. If you modified one of these fields, you should also modify the other to have them properly specified.Set both fields to be "0" or empty, or set them to some specified values based on your requirements.Both REFERENCE and SOURCENAME must be either null or non-nullInvalid REFERENCE and/or SOURCENAME values. For MEM table type, the fields REFERENCE and SOURCENAME are used together optionally to provide chaining. They should both be specified or else left blank.Specify valid MetaStor names for both REFERENCE and SOURCENAME, or leave both fields as blanks.Both the field name & the screen table name must be specifiedYou have entered either a field name, or a screen table name, to the SCROLL FIELD ENTRY or DEFAULT CURSOR POSITION specification.If you are going to use these specifications you must enter both a field name and a screen table name.You pressed <PF8> until you reached the bottom of the displayable information. No more information exists below the screen you are viewing.You have specified a break event using either the primary command area or the break event control area. This provides feedback.Break event information for "%" cannot be restored.The Debugger uses a child transaction to restore break event information. This failed. Possible cause: Attempting to nest too many transactionsVerify that your application is not nesting transactions too deeply.You have used <PF4> to save the current Break event information. This provides feedback.You have used the OFF primary command (or <PF22>) to remove a specific break event. This provides feedback.Break number # is missing in the report fields of controlling report table "%"The Report Server detected an internal error regarding breaks without controlling break tables.Browse & Search may NOT be specified when Action="C"In the User Profile, you specified the startup rule to run. Since you specified C (CALL) as the method for initiating the rule, you cannot specify the Browse and Search Path. These parameters are inherited from the parent transaction Session Manager (if there is a session menu), or from the logon transaction (if there is no session menu).If the Browse and Search attributes must be different from those used by the Session Manager (i.e., Y and S respectively), specify E (EXECUTE) or T (TRANSFERCALL) in the ACTION field. If you specify E, the rule is a child transaction. If you specify T, the Session Manager TRANSFERCALLs to the startup rule.NOTE: if you specify T, the session ends after the startup rule has run because the Session Manager has ended, transferring control to the rule. This kind of functionality is better achieved by NOT using a Session Menu, but simply specifying the rule to run at logon, the Browse mode, and the Search Path.The browse mode flag can be either Y or N. N means that the mode is update.You did not specify a value for the BROWSE field.When ACTION is N, the BROWSE field requires a value to determine the mode in which the rule executes. The choices are:The attributes defined for the source field cannot be converted to the attributes defined for the subview field.Match the definition of the attributes of the subview field with the attributes defined for the source field.Buffer position argument beyond end of buffer - position=#,buflen=#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.Buffer position argument is less than 1 - position=#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.Buffer provided to Catalog Search Interface was too smallThe buffer is provided by the $LISTDSN built-in routine to the Catalog Search Interface (CSI). It is large enough for 120 Generation Data Sets (GDS) in a given Generation Data Group (GDG). A GDG with all of its associated GDS is seen by CSI as one record.Change the filter key to reduce the number of GDSs to no more than 120.BUFFER RETRIEVAL ERROR DETECTEDAn error occurred retrieving the requested buffer from the Data Object Broker.If this error persists contact TIBCO support.When attempting to retrieve the data to build the buffer statistics screen an error was detected.Review the job logs for possible additional messages to identify the cause of the problem. Retry the request. If the problem persists contact TIBCO Support.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |