Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Using Messages With Identifiers : TR: TDS

TR: TDS
S6BTR001E
Invalid field syntax for secondary index
TDS
Secondary index cannot be defined and built on fields with syntax W and F.
Do not use SIXBUILD on fields with syntax W or F.
S6BTR002E
CTABLE too large to return for table
TDS
The table definition is too large to be processed. Possible reasons are:
The Data Object Broker parameter CTABLESIZE is too small
Increase the Data Object Broker parameter CTABLESIZE from 8 to 16 to double the CTABLE size to 16 KB. The Data Object Broker must be shut down and restarted with the new parameter.
S6BTR003E
Cannot derive PRM table from non-TDS table
TDS
The source of a parameter (PRM) table must be a TDS table.
Do not define a PRM table on a non-TDS source.
S6BTR004E
On-line SIXBUILD disallowed for large table
TDS
Online use of SIXBUILD is restricted by the size of the table, for performance and operation reasons.
Use S6BBRSIX to build a secondary index when the table has more than 3000 data pages.
S6BTR005E
Field name not found in table
TDS
The input field name is not one of the defined fields for the table.
Verify the field name and repeat the operation.
S6BTR006E
Secondary index not found in
TDS
The secondary index was not built, but was expected.
Call SIXBUILD (online) or S6BBRSIX (offline) to build the secondary index and repeat the operation.
S6BTR007E
Secondary index already exists in
TDS
You tried to build a secondary index when it already exists.
No action is required.
S6BTR008E
Secondary key length > 127 in
TDS
You used SIXBUILD (to build a secondary index) on a field whose length is greater than maximum allowed.
Do not use SIXBUILD on a field with a length greater than 127.
S6BTR009E
Invalid table type (not TDS) for table
TDS
Certain database operations, such as SIXBUILD and CLRTAB, are applicable only to TDS tables.
Do not use SIXDELETE or CLRTAB on non-native tables (i.e., tables other than TDS tables). Do not use SIXBUILD on non-TDS tables.
S6BTR010E
Field name must not be the primary key in
TDS
You tried to build an index (SIXBUILD) or delete an index (SIXDELETE) on a primary key.
Do not use SIXBUILD or SIXDELETE on a primary key field.
S6BTR011E
Too many fields defined for a composite key
TDS
The maximum number of fields allowed in a composite key is 16.
Reduce the number of fields in the composite key.
S6BTR013E
TABLES occurrence not found for table
TDS
The requested table has not been defined yet.
Use the Table Definer to define the table.
S6BTR014E
No fields defined for table
TDS
No occurrence for the table is in the FIELDS table, but an occurrence exists in the TABLES table.
Use the Table Definer to define fields for the table.
S6BTR015E
Source tablename required in definition for table
TDS
The name of a source table was not provided when required.
Provide the appropriate source name.
S6BTR017E
Table row exceeds maximum size for table
TDS
The calculated row length (based on the sum of field lengths) exceeds 4051 bytes.
Reduce the field lengths or the number of fields.
S6BTR018E
Invalid field number found for a field of table
TDS
The field number must be an integer greater than 0.
Edit the occurrences of the FIELDS table to ensure that all NUMBER values are greater than 0 and consecutive.
S6BTR019E
Invalid sort direction in ordering of table
TDS
Stored ordering must either be A (for ascending) or D (for descending).
Edit the occurrences of the ORDERING table for this table to ensure that the order is A or D.
S6BTR021E
Key field not field number 1 in table
TDS
For TDS tables, the primary key field must be the first field.
Edit the occurrence for the table in the FIELDS table to ensure that the field where NUMBER=1 is the primary key.
S6BTR022E
Key must be defined as BINARY 4 for IDGEN table
TDS
The only type of key supported for an IDgen table is one with binary syntax (B) and a length of 4.
Use the Table Definer to either set IDgen=N or define the primary key correctly.
S6BTR023E
Definition too large to process for table
TDS
The table definition is too large to be processed. Possible reasons are:
The Data Object Broker parameter CTABLESIZE is too small
Increase the Data Object Broker parameter CTABLESIZE from 8 to 16 to double the CTABLE size to 16 KB. The Data Object Broker must be shut down and restarted with the new parameter.
S6BTR024E
Severe error occurred building CTABLE for table
TDS
Internal system error.
Contact TIBCO Support.
S6BTR025E
Length must be 1 for LOGICAL attribute for
TDS
For a field with a semantic type of logical (L), its LENGTH must be 1.
Either change the field type or field length to avoid error.
S6BTR027E
Length of 2 or 4 required with BINARY syntax for
TDS
For a field with binary syntax (B), only lengths of 2 and 4 are currently supported.
Change the field length accordingly.
S6BTR028E
Zero DECIMAL required with type/syntax specified for
TDS
Unless a field is defined with packed decimal syntax (P), the DECIMAL field must be 0.
Either make SYNTAX=P or set DECIMAL=0 for the indicated field.
S6BTR029E
Non-positive length specified for
TDS
The length of a field must be greater than 0.
Change the field length to a valid integer.
S6BTR030E
Length of 4/8/16 required with FLOAT syntax for
TDS
For a field of floating point syntax (F), only three places of precision are supported.
Change the field length to 4, 8, or 16.
S6BTR031E
Invalid type/syntax combination for
TDS
The combination of semantic type and syntax is not supported.
Refer to the Managing Data manual for the permitted syntaxes for each semantic type.
S6BTR032E
Invalid syntax for
TDS
The syntax for the indicated field is not permitted for its semantic type.
Refer to the Managing Data manual for the permitted syntaxes for each semantic type.
S6BTR033E
Invalid semantic type for
TDS
The semantic type for the indicated field is not permitted for its syntax.
Refer to the Managing Data manual for the permitted syntaxes for each semantic type.
S6BTR034E
No definition found for virtual Screen
TDS
The screen name is not found in the table SCREENS.
Contact TIBCO Support.
S6BTR035E
No screen tables found for virtual Screen
TDS
The screen has no corresponding screen table.
Use the Screen Painter to define at least one screen table.
S6BTR036E
No screen fields defined for screen table
TDS
Every screen table must have at least one field.
Use the Screen Table Painter to create at least one field for the named screen table.
S6BTR037E
No CTABLE found for screen table
TDS
An error was encountered in building a CTABLE for the screen table while building a CTABLE for the screen.
Check that all the field definitions for the indicated screen table are correct or contact TIBCO Support.
S6BTR038E
No CTABLE field entry found for screen field
TDS
No screen field is defined for the indicated screen table.
Use the Screen Table Painter to define at least one field for the screen table.
S6BTR039E
Screen CTABLE too large for virtual Screen
TDS
Too many screen fields or too many screen tables are defined for the screen.
Change the Data Object Broker parameter XTABLESIZE from 16 KB (the default size) to an appropriate value, or reduce the number of screen tables and screen fields.
S6BTR040E
No definition found for reference table
TDS
The reference table name provided in the REFERENCE field of the FIELDS table does not exist.
Set the REFERENCE field to null or provide a valid table name.
S6BTR041E
Invalid table type for reference table
TDS
The reference table named in the REFERENCE field of the FIELDS table cannot be a screen table or an export table.
Set the REFERENCE field to null or provide a valid table name.
S6BTR042E
Error occurred building key code for table
TDS
Internal system error.
Contact TIBCO Support.
S6BTR045E
Multiple key fields are not contiguous for table
TDS
Composite primary key must be defined over contiguous fields.
Redefine the table using Table Definer. Rearrange the order of defined fields such that the primary key fields are contiguous.
S6BTR050E
Window ctable build error encountered in definition table
TDS
An inconsistency has been detected in the definition table. For example, the table instance for the window may be empty, or a graphical object mapping a screen field (given by @DATAMAPPING) may not exist in the window. This could have resulted from editing the definition table without knowing the dependencies involved.
For a nonexistent graphical object as an occurrence in @DATAMAPPING, either add the graphical object through the Window Builder or remove the occurrence from @DATAMAPPING. Contact TIBCO Support.
S6BTR053E
Dictionary table not defined
TDS
The requested table is not in @IDMSTABLES.
Redefine the external table for CA-IDMS data.
S6BTR054E
No IDMSTABLES definition found for table
TDS
No occurrence was found in the table @IDMSTABLES for the requested IDM table.
Delete the table definition for the given table (by using the Table Editor) and redefine the table with the CA-IDMS manager system.
S6BTR055E
Error encountered retrieving IDMSACCESS
TDS
The IDMSACCESS page retrieved is not a data page.
Contact TIBCO Support.
S6BTR056E
Subschema definition not found
TDS
The subschema definition for the given table does not exist in TIBCO(r) Object Service Broker.
Load the subschema definition with the CA-IDMS manager system.
S6BTR057E
Record name not found in table IDMSRECORDS
TDS
The requested record was not found in the subschema definition.
Use the CA-IDMS manager system to reload the subschema.
S6BTR058E
No IDMSFIELDS table found for table name
TDS
No fields were found for the given table.
Delete and redefine the CA-IDMS table definition.
S6BTR059E
No IDMSFIELDS entry found for field name
TDS
FIELDS(tablename) and @IDMSFIELDS(tablename) do not match.
Delete and redefine the CA-IDMS table definition.
S6BTR060E
No IDMSELEMENTS table found for record name
TDS
The requested field was not found in the subschema definition.
Reload the subschema definition.
S6BTR061E
No IDMSELEMENTS entry found for element name
TDS
The requested element name was not found in the @IDMSELEMENTS table for the given subschema and record.
Reload the subschema definition.
S6BTR063E
Error encountered retrieving IDMSINDEXES
TDS
The page retrieved was not a data page.
Contact TIBCO Support.
S6BTR064E
CTABLE for IDMS data too large for table
TDS
The IDM table definition has exceeded the maximum allowed.
Increase the XTABLESIZE= parameter in the Data Object Broker startup.
S6BTR074E
No definition found for report
TDS
No definition could be found for the indicated report.
Check that you have specified the correct report name.
S6BTR075E
No report tables defined for report
TDS
No component report tables exist for the indicated report.
Use the Report Definer to define the report tables you want to include in the indicated report.
S6BTR076E
No report fields defined for report table
TDS
There are no report fields defined for the indicated report table.
Define some report fields for the indicated report table, or remove the report table name from the report definition.
S6BTR077E
No CTABLE found for report table
TDS
The table definition for the indicated report table cannot be found.
Define the required report table.
S6BTR079E
Report CTABLE too large for virtual report
TDS
If the Data Object Broker parameters CTABLESIZE and XTABLESIZE are both set to 31, the definition of the indicated report is too complex. In other words, there are too many report tables, report fields, or literals for this report.
Ensure the Data Object Broker Parameters CTABLESIZE AND XTABLESIZE are set to 31. If the problem still occurs, decrease the number of report fields and literals for this report.
S6BTR082E
Unicode Field length must be even
TDS
The length of a Unicode field cannot be an odd number.
Correct the definition of the Unicode field.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved