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


Using Messages Without Identifiers : Messages beginning with: K

Messages beginning with: K
Key field % in source table missing from table definition
Table Definer
The indicated key field from the source table is not found in the Subview table definition.
Define the indicated field as key field in your Subview table definition.
Key field cannot have default value
Table Definer
A primary key cannot have a default value.
Remove the default value specification for the primary key field.
Key field not number 1 in dynamically created table %
TAM
The field identified by @DOFTABLES.KEY equal to "P" is not the first field.
Set the first Primary Key field to be the first field.
Key field representing the records' ISN must have a length of '4'
Adabas Definer
Invalid external length for key field representing the ADABAS ISN#.
Specify special external length of 4 for key field representing the ISN#.
Key field representing the records' relative number must have a length of '2'
Adabas Definer
Length of key fields (other than the first key representing the ADABAS ISN#) should be 2.
Specify a length of 2 for the key representing the records' relative occurrence.
Key fields not contiguous in dynamically created table %
TAM
A compound primary key must be composed of an initial, contiguous set of fields.
Ensure that all primary key fields in @DOFFIELDS are grouped at the beginning.
Key for dynamically created IDGEN table % must be IDENTIFIER BINARY 4
TAM
The primary key of the table you are dynamically creating is not of semantic type IDENTIFIER, syntax BINARY, and length 4.
Set the type, syntax, and length to IDENTIFIER BINARY 4.
Key length > 127; cannot be selected as key
Table Definer
You cannot choose a field that is longer than 127 bytes to be a primary key.
Use another line command so that the field is not a primary key for the MetaStor IMS table.
Key length for table "%" does not match key length of VSAM % "%"
TAM
The length of the key for the Object Service Broker definition of the indicated table is not equal to the length of the actual key in the KSDS data set. The variables in the message, from left to right, are as follows:
1.
2.
3.
Change the definition of the Object Service Broker table so that the key length equals the VSAM record key length.
Key offset for table "%" does not match key offset of VSAM % "%"
TAM
The offset of the key in the table definition does not match the actual key offset of the VSAM file. The variables, from left to right, are as follows:
1.
2.
Ensure that the table definition for the indicated table matches the characteristics of the actual VSAM file.
Keyfield for % M204 table must have % % % attributes
Table Definer
The Keyfield must have the specified attributes
Specify the attributes as requested
Keys must be together and at the front of the definition
Adabas Definer
The ordering of your key fields is invalid.
Define keys to be consecutive and at the front of the table definition.
Keytype of % must be consistent with source table
Table Definer
The keytype of the indicated field does not match that of the source table.
Change keytype to contain the same value as in source table.
Keyword(s) longer than 20 characters ignored - see message log
Keyword Manager
This object has one or more keywords of more than 20 characters. These keywords will not be indexed. The objects and their keywords are listed in the message log.
Press <PF2> to see a list of objects whose keywords must be shortened.

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