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.
Item | Description | Content that is output |
---|---|---|
Code | A code that identifies the definition check item. | A code number is output. |
Attribute | This indicates the check type of the particular check. | One of the following is output. W: Warning E: Error I: Information |
Definition type | This 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 name | Indicates 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 type | Indicates 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 target | Indicates 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
Code | Cause |
---|---|
010-001 | The count for in-process group definitions under the adaptor structure definitions exceeds the maximum (1). |
010-002 | The count for RMI group definitions under the adaptor structure definitions exceeds the maximum (1). |
010-003 | A name is not unique among the in-process group definitions and RMI group definitions under the adaptor structure definitions. |
010-004 | A name is not unique among the in-process group definitions and RMI group definitions under the adaptor structure definitions. |
030-001 | An adaptor name is not unique among the relevant in-process group definitions. |
030-002 | An adaptor name is not unique among the relevant in-process group definitions. |
040-001 | An adaptor name is not unique among the relevant RMI group definitions. |
040-002 | An adaptor name is not unique among the relevant RMI group definitions. |
050-002 | The count for record extraction definitions under the input adaptor definitions exceeds the maximum (2). |
050-003 | The count for filter definitions under the input adaptor definitions exceeds the maximum (4). |
050-005 | The count for format conversion definitions under the input adaptor definitions exceeds the maximum (1). |
060-002 | The count for filter definitions under the output adaptor definitions exceeds the maximum (4). |
060-004 | The count for format conversion definitions under the output adaptor definitions exceeds the maximum (1). |
091-002 | A 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-003 | In 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-004 | In 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-006 | Serial numbers are being specified as input file names, and a file name was specified more than once. |
091-008 | A period was specified at the start or end of a file name specified as an input file name. |
091-009 | The serial number specification format when input file names are specified as serial numbers is invalid. |
091-010 | The 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-011 | The status is one of the following.
|
091-013 | input@readOrder is MODIFIED, and the same file name is specified more than once for file@name. |
092-001 | The specified value for packet data size area offset has made the packet data size area exceed the packet header area. |
092-002 | The total of the packet data size area length and the timestamp area length exceeds the packet header area. |
092-003 | The specified value for timestamp area offset has made the timestamp area exceed the packet header area. |
092-004 | The packet data size area duplicates the timestamp area. |
092-008 | A field name that cannot be used in the specified record type has been specified. |
101-003 | The 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-004 | The 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-005 | The 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-006 | The output of the callback defined immediately before this is not an I/O format record. |
102-003 | The processing function definition corresponding to a processing function name was not found. |
102-004 | The value at the position of the specified field exceeds the field count. |
102-005 | The specified time field number exceeds the field count. |
102-006 | No record name equivalent to the record of the specified record name was found. |
102-007 | The record name equivalent to the record of the specified record name was deleted prior to this callback. |
102-008 | The output of the callback defined immediately before is not a common format record. |
111-002 | The record name is not unique among the record definitions under the record group definitions. |
111-003 | The format type is text, and no record structure is specified. |
111-005 | The format type is text, and not all the field names (($_field-name) format) that constitute the record in question have been specified. |
111-006 | The format type is text, and a field name other than the field names that constitute the record in question has been specified. |
111-007 | The format type is text, and the order in which the field names are specified differs from the definition order. |
111-008 | The format type is text, and a field name has been defined more than once. |
111-009 | The field definition count exceeds the maximum value (3,000). |
111-010 | The field name is not unique among the field definitions under the applicable record definitions. |
111-011 | The format type is text, and the regular expression specified in the pattern is invalid. |
111-012 | The format type is text, and the status is the following.
|
111-013 | The specified value for the type of I/O does not match the adaptor definition type in which its own format conversion definition exists. |
111-014 | The record specified by the record name was not found. |
111-015 | The field specified by the field name is not in the target record. |
111-016 | The data type specified in field@type differs from the data type of the field specified in field@name. |
111-017 | The record specified in the record name was defined in the previous callback but has not been input. |
111-018 | The 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-019 | The 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-020 | The output of the callback defined immediately before is not an I/O format record. |
111-021 | The output of the callback defined immediately before is not a common format record. |
112-001 | The stream definition count exceeds the maximum value (1,024). |
112-002 | A query group name and stream name combination is not unique among the stream definitions under the stream group definitions. |
112-003 | The column definition count exceeds the maximum value (3,000). |
112-004 | A column name is not unique among the column definitions under the stream definitions. |
112-005 | The mapping group definitions count exceeds the maximum value (1,024). |
112-006 | The mapping definitions count exceeds the maximum value (3,000). |
112-007 | A conversion target path expression is not unique among the mapping definitions under the mapping group definitions. |
112-008 | A 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-009 | A 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-011 | For 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-012 | For 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-013 | The specified value for the type of I/O does not match the adaptor definition type in which its own mapping definition exists. |
112-014 | The 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-015 | The 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-018 | The status is one of the following.
|
112-019 | The status is one of the following.
|
112-020 | The status is one of the following.
|
112-021 | The 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-022 | A function that requires argument1 was used, and argument1 was not specified. |
112-023 | The field specified in argument1 was not found. |
112-024 | The type of the field specified in argument1 was invalid. |
112-025 | A function that requires argument2 was used, and argument2 was not specified. |
112-026 | The regular expression specified in map@argument2 is invalid (when regexsubstring is specified in map@function). |
112-027 | The argument specified in map@argument2 does not include parentheses (( )) (when regexsubstring is specified in map@function). |
112-028 | The type of the field specified in argument2 is invalid (when subTime is specified in map@function). |
112-032 | The 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-033 | The record specified by the conversion source name was not found. Note that this does not apply to OUTPUT (stream to record). |
112-034 | The 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-036 | Both map@source and map@function are defined. |
112-037 | The 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-038 | Neither map@source nor map@function is defined. |
112-039 | For INPUT (record to record) and OUTPUT (record to record), mappings@querygroup has been specified. |
112-040 | For INPUT (record to stream) and OUTPUT (stream to record), mappings@querygroup has not been specified. |
112-041 | getTupleTime has been specified in map@function and map@argument1, or map@argument2 has been specified. |
112-042 | The mapping definition is under the input adaptor definition, and a stream group definition under the mapping source definitions has been specified. |
112-043 | The 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-044 | map@source has been specified, and map@argument1 or map@argument2 has been specified. |
112-045 | The output of the callback defined immediately before this is not a common format record. (This does not apply to OUTPUT (stream to record).) |
112-046 | The output of the callback defined immediately before this is not a stream. (This covers OUTPUT (stream to record).) |
112-047 | The record definition count exceeds the maximum value (1,024). |
112-048 | The field definition count exceeds the maximum value (3,000). |
112-049 | The 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-050 | For INPUT (record to stream) mapping and OUTPUT (stream to record) mapping, map@function has been specified. |
112-051 | For OUTPUT (stream to record), the column name specified in the conversion source path expression is not in the conversion source definition. |
112-052 | For INPUT/OUTPUT (record to record), the record name is not unique among the record definitions under the record group definitions. |
112-053 | For INPUT/OUTPUT (record to record), the field name is not unique among the field definitions under the record definitions. |
112-054 | The field specified in argument2 was not found (when subTime is specified in map@function). |
112-055 | The 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-056 | getTupleTime has been specified in map@function. |
113-001 | The record specified by the name of the record to be filtered was not found. |
113-002 | The field specified by the field name is not among the fields of the target record. |
113-003 | The field specified by field@source is character data, and something other than eq or ne has been specified. |
113-004 | The field specified by the field name is numeric data and the condition value is character data. |
113-005 | The regular expression of the condition value is invalid. |
113-007 | The data type of the field specified by the field name is not STRING, BYTE, SHORT, INTEGER, or LONG. |
113-008 | The record condition name duplicates another record condition name. |
113-009 | The record specified by the name of the record to be filtered was deleted prior to this callback. |
113-010 | The output of the callback defined immediately before this is not a common format record. |
113-011 | The type of field@source is BYTE, INTEGER, SHORT or LONG, and the condition value is outside the range for the LONG type. |
114-001 | The field specified by the time field name is not among the fields of the target record. |
114-002 | The record specified by the record name was not found. |
114-003 | The field specified by the field name is not among the fields of the target record. |
114-004 | The field specified by field@source is STRING type, but something other than eq or ne has been specified. |
114-005 | The record specified by the name of the record to be extracted was not found. |
114-006 | The record specified by the name of the record to be extracted was not found. |
114-007 | The field specified by the field name is not among the fields of the target record. |
114-008 | The field specified by the field name is not among the fields of the target record. |
114-009 | The record name specified by the retrieved record name is not unique. |
114-010 | The record specified by the name of the record to be extracted was not found. |
114-011 | A record extraction callback is defined in an output adaptor. |
114-013 | A name of a record to be extracted has been specified more than once in a single record extraction callback. |
114-014 | The type of the field specified in the time field is not TIMESTAMP. |
114-015 | Among 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-016 | The type of the field specified by the field name is not STRING, BYTE, SHORT, INTEGER, or LONG. |
114-017 | The type of field@source is STRING, and the regular expression of the condition value is invalid. |
114-018 | The record name specified by the timeout record name is not unique within the adaptor. |
114-019 | The 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-020 | A extraction condition name has been specified more than once in a single record extraction callback. |
114-021 | The record specified by the record name has not been input. |
114-022 | In 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-023 | The type of field@source is BYTE, INTEGER, SHORT or LONG, and the condition value is outside the range for the LONG type. |
114-024 | The output of the callback defined immediately before this is not a common format record. |
114-025 | extractions@timeout is ON, but the timeoutrecord tag has been omitted. |
114-026 | The field count total of the records to be extracted specified in select@source of extractrecord exceeds the maximum value (2,999). |
114-030 | The total character count of the names of records to be extracted and the field names of records to be extracted has exceeded 99. |
114-031 | Among 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-032 | No name of a record to be extracted has been specified in any of the extraction conditions. |
114-033 | A record name for extraction has been specified more than once in select@source of extractrecord. |
114-034 | In 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-001 | The count of input stream information definitions at the transmission target exceeds the maximum value (1,024). |
120-002 | A query group name and stream name combination is not unique among the input stream information items under the transmission CB definitions. |
120-003 | The output of the callback defined immediately before this is not a stream. |
130-001 | The count of output stream information definitions at the reception source exceeds the maximum value (1,024). |
130-002 | A query group name and stream name combination is not unique among the output stream information items under the reception CB definitions. |