Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Using Messages Without Identifiers : Messages beginning with: B

Messages beginning with: B
Back out request % cancelled
Promotion
You canceled a request to back out a promotion.
No action required.
Backed up %
Promotion
The specified number of objects were backed up before the change was applied to the system.
No action required.
Backed up all information for % tables
Promotion
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.
No action required.
Backed up data only for % tables or table instances
Promotion
The Promotion utility has backed up the specified number of tables or table instances so as to allow subsequent backout of the change.
No action required.
BACKING UP OLD OBJECTS
Promotion
The Promotion tool backs up old objects before deleting them so that they can be restored if the promotion is backed out.
No action required.
Backout canceled
Promotion
You canceled the backout process. The status of the change request did not change.
No action required.
Backup file contains % page files - segment '%' contains % page files
Offline Utilities
The 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 '%'
Offline Utilities
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.
Backup source file is larger than target
Offline Utilities
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.
Bad value length in parameter string
Interpreter
Internal error. The message log contains a more detailed error message.
Do the following:
1.
2.
Contact TIBCO Support with the log and a description of the actions performed before the message was displayed.
Bad value length in selection string
Interpreter
Internal error. The message log contains a more detailed error message.
Do the following:
1.
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 ONLINE
S6BTLADM - SEGMENT/DASD
You 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 time
External Gateway Logon
The 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 SQL
Static SQL for DB2 Gateway
A batch job has been submitted to generate the requested Static SQL.
No action required.
Batch request not found on queue %; key = %
Batch Submission Tool
A batch request was not found on the indicated queue as expected.
Contact TIBCO Support.
Batch request saved
Batch Submission Tool
Batch request information was saved.
No action required.
Begin to print definition for object "%" type "%"
Print Definition
You are trying to print an object and an object, which is defined by the object you specified, is now printing.
No action required.
Binary field decimal not allowed (must be 0)
Screen Definer
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.
Binary field length must be less than 12
Screen Definer
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 information
Screen Definer
Your 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.
Blank commands are not allowed
DEFINE_OBJLIST Tool
You did not specify any letters to use to invoke the command.
Specify a letter to denote the command.
Both DBID and FILE NO. must be entered
Adabas Definer
Required field DBID and/or FILE number are missing.
Specify ADABAS Database ID and FILE number.
Both from and to tokens are %; no change necessary
CHANGERULE tool
You 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.
Both LAST ROW and LAST COL must be '0'
Screen Definer
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-null
Table Definer
Invalid 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 specified
Screen Definer
You 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.
Enter both a field name and a screen table name.
Bottom of Window
General
You pressed <PF8> until you reached the bottom of the displayable information. No more information exists below the screen you are viewing.
No action required.
Break event established at %
Debugger Utility
You have specified a break event using either the primary command area or the break event control area. This provides feedback.
No action required.
Break event information for "%" cannot be restored.
Debugger Utility
The Debugger uses a child transaction to restore break event information. This failed. Possible cause: Attempting to nest too many transactions
Verify that your application is not nesting transactions too deeply.
Break event information saved for "%"
Debugger Utility
You have used <PF4> to save the current Break event information. This provides feedback.
No action required.
Break event removed at %
Debugger Utility
You have used the OFF primary command (or <PF22>) to remove a specific break event. This provides feedback.
No action required.
Break number # is missing in the report fields of controlling report table "%"
Report Server
The Report Server detected an internal error regarding breaks without controlling break tables.
Contact TIBCO Support.
Browse & Search may NOT be specified when Action="C"
Security
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.
Browse mode must be "Y" or "N"
Batch Submission Tool
The browse mode flag can be either Y or N. N means that the mode is update.
Specify a Y or N value.
BROWSE must be Y or N
DEFINE_OBJLIST Tool
You did not specify a value for the BROWSE field.
Specify a value (Y or N) for the BROWSE field.
BROWSE must be Y or N
Menu Definer
When ACTION is N, the BROWSE field requires a value to determine the mode in which the rule executes. The choices are:
Enter Y or N in the BROWSE field.
Buffer conversion error for subview "%"
TAM
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=#
Interpreter
Internal error. The message log contains a more detailed error message.
Do the following:
1.
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=#
Interpreter
Internal error. The message log contains a more detailed error message.
Do the following:
1.
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 small
Builtin Routines
The 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 DETECTED
S6BTLADM - PAGE DISPLAY
An error occurred retrieving the requested buffer from the Data Object Broker.
If this error persists contact TIBCO support.
BUFFER STATISTICS RETRIEVAL ERROR
S6BTLADM - BUFFER POOL
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
Copyright © TIBCO Software Inc. All Rights Reserved