8.1 List of Definition Check Information

Messages that involve definition check errors provide definition check information, which is output in the following format. The bold portion is the definition check information.

KFSPxxxxx-x [Code:attribute:definition type:definition name:I/O type:check target] message-text

The following describes the content that is output as part of the definition check information.

ItemDescriptionContent that is output
CodeA code that identifies the definition check item.A code number is output.
AttributeThis indicates the check type of the particular check.One of the following is output.
W: Warning
E: Error
I: Information
Definition typeThis indicates the name of the tag that is the subject of the check.A definition tag name, such as InprocessGroupDefinition or InputAdaptorDefinition, is output.
Definition nameIndicates the name (name attribute) specified in the definition that is the subject of the particular check. When there is no name specification in the target definition type, however, the value specified for name for the high-order definition is shown.The value specified as the name attribute of each definition is output.
I/O typeIndicates whether the definition that is the subject of the check is for an input adaptor or an output adaptor.One of the following is output.
INPUT: For input adaptors.
OUTPUT: For output adaptors.
*****: Not applicable
Check targetIndicates the tag name or attribute name where the error was found. Attribute names are shown in the format tag@attribute.One of the following values is output.
For a tag name: file, stream or the like.
For an attribute: stream@name, records@recordsType or the like.

Check this information and the causes given for the specific codes in the following table, and then take corrective action for errors.

Table 8-1 Causes for the output of the definition check information codes

CodeCause
010-001The count for in-process group definitions under the adaptor structure definitions exceeds the maximum (1).
010-002The count for RMI group definitions under the adaptor structure definitions exceeds the maximum (1).
010-003A name is not unique among the in-process group definitions and RMI group definitions under the adaptor structure definitions.
010-004A name is not unique among the in-process group definitions and RMI group definitions under the adaptor structure definitions.
030-001An adaptor name is not unique among the relevant in-process group definitions.
030-002An adaptor name is not unique among the relevant in-process group definitions.
040-001An adaptor name is not unique among the relevant RMI group definitions.
040-002An adaptor name is not unique among the relevant RMI group definitions.
050-002The count for record extraction definitions under the input adaptor definitions exceeds the maximum (2).
050-003The count for filter definitions under the input adaptor definitions exceeds the maximum (4).
050-005The count for format conversion definitions under the input adaptor definitions exceeds the maximum (1).
060-002The count for filter definitions under the output adaptor definitions exceeds the maximum (4).
060-004The count for format conversion definitions under the output adaptor definitions exceeds the maximum (1).
091-002A file name was found among the file names specified as input file names whose character string length is less than the minimum value (one single-byte character).
Another possibility is that a file name was found among the file names specified as input file names whose character string length is greater than the maximum value (60 single-byte characters).
091-003In serial number specification for input file names, the number of digits in the numeric string of the lower limit value is not less than or equal to the number of digits in the numeric string of the upper limit value.
091-004In serial number specification for input file names, the numeric value of the numeric string of the lower limit value is not less than or equal to the numeric value of the numeric string of the upper limit value.
091-006Serial numbers are being specified as input file names, and a file name was specified more than once.
091-008A period was specified at the start or end of a file name specified as an input file name.
091-009The serial number specification format when input file names are specified as serial numbers is invalid.
091-010The character string length specified for an input file path name is less than the minimum value (one single-byte character).
Another possibility is that the character string length specified for an input file path name is greater than the maximum value (160 single-byte characters).
091-011The status is one of the following.
  • WRAP_AROUND was specified for input@compositionType and BATCH was specified for input@readType.
  • input@readType is REAL_TIME and input@readOrder is DEFINED.
  • ANTI_WRAP_AROUND is specified for input@compositionType and MODIFIED for input@readOrder.
091-013input@readOrder is MODIFIED, and the same file name is specified more than once for file@name.
092-001The specified value for packet data size area offset has made the packet data size area exceed the packet header area.
092-002The total of the packet data size area length and the timestamp area length exceeds the packet header area.
092-003The specified value for timestamp area offset has made the timestamp area exceed the packet header area.
092-004The packet data size area duplicates the timestamp area.
092-008A field name that cannot be used in the specified record type has been specified.
101-003The character string length specified for a prefix name is less than the minimum value (one single-byte character).
Another possibility is that the character string length specified for a prefix is greater than the maximum value (60 single-byte characters).
101-004The character string length specified for an extension is less than the minimum value (one single-byte character).
Another possibility is that the character string length specified for an extension is greater than the maximum value (four single-byte characters).
101-005The character string length specified for an output file path name is less than the minimum value (one single-byte character).
Another possibility is that the character string length specified for an output file path name is greater than the maximum value (160 single-byte characters).
101-006The output of the callback defined immediately before this is not an I/O format record.
102-003The processing function definition corresponding to a processing function name was not found.
102-004The value at the position of the specified field exceeds the field count.
102-005The specified time field number exceeds the field count.
102-006No record name equivalent to the record of the specified record name was found.
102-007The record name equivalent to the record of the specified record name was deleted prior to this callback.
102-008The output of the callback defined immediately before is not a common format record.
111-002The record name is not unique among the record definitions under the record group definitions.
111-003The format type is text, and no record structure is specified.
111-005The format type is text, and not all the field names (($_field-name) format) that constitute the record in question have been specified.
111-006The format type is text, and a field name other than the field names that constitute the record in question has been specified.
111-007The format type is text, and the order in which the field names are specified differs from the definition order.
111-008The format type is text, and a field name has been defined more than once.
111-009The field definition count exceeds the maximum value (3,000).
111-010The field name is not unique among the field definitions under the applicable record definitions.
111-011The format type is text, and the regular expression specified in the pattern is invalid.
111-012The format type is text, and the status is the following.
  • If the I/O type is INPUT
    The data type is not STRING.
    Another possibility is that a pattern has been specified.
  • If the I/O type is OUTPUT
    A pattern has been specified.
111-013The specified value for the type of I/O does not match the adaptor definition type in which its own format conversion definition exists.
111-014The record specified by the record name was not found.
111-015The field specified by the field name is not in the target record.
111-016The data type specified in field@type differs from the data type of the field specified in field@name.
111-017The record specified in the record name was defined in the previous callback but has not been input.
111-018The value of format@timestampformat is not 2, and @year or @month has been specified. Another possibility is that @year or @month has been specified by the output adaptor.
111-019The value of record@timestampformat is not 2, and @year or @month has been specified. Another possibility is that @year or @month has been specified by the output adaptor.
111-020The output of the callback defined immediately before is not an I/O format record.
111-021The output of the callback defined immediately before is not a common format record.
112-001The stream definition count exceeds the maximum value (1,024).
112-002A query group name and stream name combination is not unique among the stream definitions under the stream group definitions.
112-003The column definition count exceeds the maximum value (3,000).
112-004A column name is not unique among the column definitions under the stream definitions.
112-005The mapping group definitions count exceeds the maximum value (1,024).
112-006The mapping definitions count exceeds the maximum value (3,000).
112-007A conversion target path expression is not unique among the mapping definitions under the mapping group definitions.
112-008A query group name and conversion target name combination is not unique among the mapping group definitions under the mapping intermediate definitions. Note that this does not apply to INPUT (record to record).
112-009A conversion target name is not unique among the mapping group definitions under the mapping intermediate definitions. Note that this does not apply to INPUT (record to stream).
112-011For record to stream, the mapping definitions are under the input adaptor definitions and the stream group definition under the mapping target definitions is not specified.
112-012For stream to record, the mapping definitions are under the output adaptor definition and the stream group definition under the mapping source definitions is not specified.
112-013The specified value for the type of I/O does not match the adaptor definition type in which its own mapping definition exists.
112-014The query group name does not match the query group name of the stream definition. Another possibility is that the conversion target name (stream name) does not match the stream name of the stream definitions. Note that this does not apply to INPUT (record to record).
112-015The query group name does not match the query group name of the stream definition. Another possibility is that the conversion source name (stream name) does not match the stream name of the stream definitions. Note that this does not apply to OUTPUT (record to record).
112-018The status is one of the following.
  • For INPUT (record to stream), there is no column name that matches the specified value under the stream definition that matches the conversion target name (query group name and stream name).
  • For INPUT (record to record), there is no field name that matches the specified value under the record definition that matches the conversion target name (record name).
  • For OUTPUT (record to record), there is no field name that matches the specified value under the record definition that matches the conversion target name (record name).
112-019The status is one of the following.
  • For INPUT (record to stream), the number of mapping definitions does not match the number of column definitions under the stream definition that matches the conversion target name (query group name and stream name).
  • For INPUT (record to record), the number of mapping definitions does not match the number of field definitions under the record definition that matches the conversion target name (record name).
  • For OUTPUT (record to record), the number of mapping definitions does not match the number of field definitions under the record definition that matches the conversion target name (record name).
112-020The status is one of the following.
  • For INPUT (record to stream), if a constant was specified as the conversion source path expression, the data type of the column definition in which the conversion target path expression and column name match does not match the type of the constant.
  • For INPUT (record to record), if a constant was specified as the conversion source path expression, the data type of the field definition in which the conversion target path expression and field name match does not match the type of the constant.
  • For OUTPUT (record to record), if a constant was specified as the conversion source path expression, the data type of the field definition in which the conversion target path expression and field name match does not match the type of the constant.
112-021The specified record name was used more than once within a single adaptor. Note that this does not apply to INPUT (record to stream) or OUTPUT (stream to record).
112-022A function that requires argument1 was used, and argument1 was not specified.
112-023The field specified in argument1 was not found.
112-024The type of the field specified in argument1 was invalid.
112-025A function that requires argument2 was used, and argument2 was not specified.
112-026The regular expression specified in map@argument2 is invalid (when regexsubstring is specified in map@function).
112-027The argument specified in map@argument2 does not include parentheses (( )) (when regexsubstring is specified in map@function).
112-028The type of the field specified in argument2 is invalid (when subTime is specified in map@function).
112-032The data type specified in field@type differs from the data type of the field specified in field@name. Note that this does not apply to INPUT (record to stream) or OUTPUT (stream to record).
112-033The record specified by the conversion source name was not found. Note that this does not apply to OUTPUT (stream to record).
112-034The field specified by the conversion path name is not in the target record. Note that this does not apply to OUTPUT (stream to record).
112-036Both map@source and map@function are defined.
112-037The record specified by the conversion source name was defined in the previous callback but was not input. Note that this does not apply to OUTPUT (stream to record).
112-038Neither map@source nor map@function is defined.
112-039For INPUT (record to record) and OUTPUT (record to record), mappings@querygroup has been specified.
112-040For INPUT (record to stream) and OUTPUT (stream to record), mappings@querygroup has not been specified.
112-041getTupleTime has been specified in map@function and map@argument1, or map@argument2 has been specified.
112-042The mapping definition is under the input adaptor definition, and a stream group definition under the mapping source definitions has been specified.
112-043The data type specified by column@type differs from the data type specified by the column@type of the column definition that corresponds to map@source. Note that this does not apply to INPUT (record to record).
112-044map@source has been specified, and map@argument1 or map@argument2 has been specified.
112-045The output of the callback defined immediately before this is not a common format record. (This does not apply to OUTPUT (stream to record).)
112-046The output of the callback defined immediately before this is not a stream. (This covers OUTPUT (stream to record).)
112-047The record definition count exceeds the maximum value (1,024).
112-048The field definition count exceeds the maximum value (3,000).
112-049The mapping definition is a stream group definition under the mapping target definitions. Another possibility is that both the stream group definition under the mapping source definition and the record group definition have been specified.
112-050For INPUT (record to stream) mapping and OUTPUT (stream to record) mapping, map@function has been specified.
112-051For OUTPUT (stream to record), the column name specified in the conversion source path expression is not in the conversion source definition.
112-052For INPUT/OUTPUT (record to record), the record name is not unique among the record definitions under the record group definitions.
112-053For INPUT/OUTPUT (record to record), the field name is not unique among the field definitions under the record definitions.
112-054The field specified in argument2 was not found (when subTime is specified in map@function).
112-055The record specified by the conversion target name was not found. Note that this does not apply to INPUT (record to stream) or OUTPUT (stream to record).
112-056getTupleTime has been specified in map@function.
113-001The record specified by the name of the record to be filtered was not found.
113-002The field specified by the field name is not among the fields of the target record.
113-003The field specified by field@source is character data, and something other than eq or ne has been specified.
113-004The field specified by the field name is numeric data and the condition value is character data.
113-005The regular expression of the condition value is invalid.
113-007The data type of the field specified by the field name is not STRING, BYTE, SHORT, INTEGER, or LONG.
113-008The record condition name duplicates another record condition name.
113-009The record specified by the name of the record to be filtered was deleted prior to this callback.
113-010The output of the callback defined immediately before this is not a common format record.
113-011The type of field@source is BYTE, INTEGER, SHORT or LONG, and the condition value is outside the range for the LONG type.
114-001The field specified by the time field name is not among the fields of the target record.
114-002The record specified by the record name was not found.
114-003The field specified by the field name is not among the fields of the target record.
114-004The field specified by field@source is STRING type, but something other than eq or ne has been specified.
114-005The record specified by the name of the record to be extracted was not found.
114-006The record specified by the name of the record to be extracted was not found.
114-007The field specified by the field name is not among the fields of the target record.
114-008The field specified by the field name is not among the fields of the target record.
114-009The record name specified by the retrieved record name is not unique.
114-010The record specified by the name of the record to be extracted was not found.
114-011A record extraction callback is defined in an output adaptor.
114-013A name of a record to be extracted has been specified more than once in a single record extraction callback.
114-014The type of the field specified in the time field is not TIMESTAMP.
114-015Among all the target tags in the same targets tag, the target@sourceL to be checked is the same as the record name specified by another target@sourceL or target@sourceR. However, the combination of target@sourceL and target@sourceR, to be checked in 114-022, is not covered by this check.
114-016The type of the field specified by the field name is not STRING, BYTE, SHORT, INTEGER, or LONG.
114-017The type of field@source is STRING, and the regular expression of the condition value is invalid.
114-018The record name specified by the timeout record name is not unique within the adaptor.
114-019The type of the field specified by field@source is BYTE, SHORT, INTEGER or LONG, and the condition value specified by field@value is not an integer value.
114-020A extraction condition name has been specified more than once in a single record extraction callback.
114-021The record specified by the record name has not been input.
114-022In the second or subsequent inter-record condition, the name of the record to be extracted differs from the name of the record to be extracted that was specified in the target@sourceR immediately before.
114-023The type of field@source is BYTE, INTEGER, SHORT or LONG, and the condition value is outside the range for the LONG type.
114-024The output of the callback defined immediately before this is not a common format record.
114-025extractions@timeout is ON, but the timeoutrecord tag has been omitted.
114-026The field count total of the records to be extracted specified in select@source of extractrecord exceeds the maximum value (2,999).
114-030The total character count of the names of records to be extracted and the field names of records to be extracted has exceeded 99.
114-031Among all the target tags in the same targets tag, the target@sourceL to be checked is the same as the record name specified by another target@sourceL or target@sourceR. However, the combination of target@sourceL and target@sourceR, to be checked in 114-022, is not covered by this check.
114-032No name of a record to be extracted has been specified in any of the extraction conditions.
114-033A record name for extraction has been specified more than once in select@source of extractrecord.
114-034In the second and subsequent target tags, the field name of the record to be extracted, specified by fieldcondition@sourceR under the target tag immediately before this, has not been specified in fieldcondition@sourceL under the target tag.
120-001The count of input stream information definitions at the transmission target exceeds the maximum value (1,024).
120-002A query group name and stream name combination is not unique among the input stream information items under the transmission CB definitions.
120-003The output of the callback defined immediately before this is not a stream.
130-001The count of output stream information definitions at the reception source exceeds the maximum value (1,024).
130-002A query group name and stream name combination is not unique among the output stream information items under the reception CB definitions.