Cause: Command line option for the data splitting utility is not valid. Valid options are:
Action: Given for each reason code:
Cause: The utility cannot read the configuration file "<config-file>".
Action: Please ensure the configuration file exists and is readable.
Cause: The utility cannot open the log file "<log-file>" for writing or appending.
Action: Please ensure the log file exists and is writable.
Cause: The utility cannot read the input data file "<input-data-file>".
Action: Please ensure the input data file exists and is readable.
Cause: The utility cannot read the input partitioning map file "<in-map-file>".
Action: Please ensure the input partitioning map file exists and is readable.
Cause: The utility cannot open the output partitioning map file "<out-map-file>" for writing.
Action: Please ensure the output partitioning map file is writable.
Cause: The utility cannot open the distribution file "<dist-file>" for writing.
Action: Please ensure the distribution file is writable.
Cause: The utility cannot open the output data file "<out-data-file>" for writing.
Action: Please ensure the output data file is writable.
Cause: There is a syntax error in the specification of a keyword and its argument.
Action: A keyword and its argument must be delimited by an '=' sign.
Cause: There is an undefined keyword in the configuration file.
Action: Valid keywords (case insensitive) are:
Cause: The column delimiter (CDELIMITER) specified in the configuration file is not valid.
Action: Make sure the column delimiter (CDELIMITER) is a single byte character.
Cause: The string delimiter (SDELIMITER) specified in the configuration file is not valid.
Action: The string delimiter (SDELIMITER) cannot be a period.
Cause: The value for run type (RUNTYPE) specified in the configuration file is not valid.
Action: Valid run type (RUNTYPE) can be either PARTITION or ANALYZE (case insensitive).
Cause: The value for message level (MSG_LEVEL) specified in the configuration file is not valid.
Action: Valid message level (MSG_LEVEL) can be either CHECK or NOCHECK (case insensitive).
Cause: The value for check level (CHECK_LEVEL) specified in the configuration file is not valid.
Action: Valid check level (CHECK_LEVEL) can be either CHECK or NOCHECK (case insensitive).
Cause: The value for record length (RECLEN) "<reclen>" specified in the configuration file is not valid.
Action: The record length (RECLEN) must be between 1 and 32767.
Cause: The node specification (NODES) in the configuration file is not valid.
Action: Given for each reason code:
Cause: The output node specification (OUTPUTNODES) in the configuration file is not valid.
Action: Given for each reason code:
Cause: The output type (OUTPUTTYPE) in the configuration file is not valid.
Action: Valid output types (OUTPUTTYPE) are W (write) or S (stdin), case insensitive.
Cause: The number of partitioning keys defined cannot exceed the maximum limit: 256.
Action: Remove one or more partitioning keys defined in the configuration file.
Cause: A partitioning key specification (PARTITION) in the configuration file is not valid. Valid format:
PARTITION=<key name>,<position>,<offset>,
<len>,<nullable>,<datatype>
If a delimited-data file, <position> must be defined; otherwise, <offset> and <len> must be defined.
Action: Given for each reason code:
Cause: The log file specification (LOGFILE) in the configuration file is not valid.
Action: The log file specification (LOGFILE) must be in one of the following two formats:
Cause: The trace specification (TRACE) in the configuration file is not valid.
Action: The trace specification (TRACE) must be a positive integer between 0 and 65536 (exclusive).
Cause: The node list specification is not valid.
Action: One and only one of the two parameters: NODES and MAPFILI (input partition map) must be specified in the configuration file.
Cause: If run type is ANALYZE, a filename for the output partition map must be defined.
Action: Specify a filename for the output partition map.
Cause: At least one partitioning key must be defined.
Action: Specify one or more partitioning keys.
Cause: For non-delimited data, starting position for a key must be less than the record length.
Action: Make sure starting position for a key is less than the record length.
Cause: Output node list must be a subset of the node list, which is derived from NODES or the input partition map file.
Action: Make sure all output nodes are defined in the node list.
Cause: There is at least one error in the input partition map file.
Action: The input partition map must contain no less than 4096 data entries, and each data entry must be a number between 0 and 999.
Cause: An I/O error occurred while writing the header to an output data file.
Action: Check your operating system documentation for file I/O errors and ensure that there is sufficient space on the output device.
Cause: An I/O error occurred while reading from input data file.
Action: Check your operating system documentation for file I/O errors.
Cause: Binary data is not permitted on the host versions of this utility program.
Action: Check your input data file.
Cause: The run type (RUNTYPE) must be defined as either PARTITION or ANALYZE.
Action: Please specify run type (RUNTYPE) in the configuration file.
Cause: The specification for parameter 32KLIMIT in the configuration file is not valid.
Action: Parameter 32KLIMIT can be either YES or NO, case insensitive.
Cause: The record "<rec-no>" of the input data is discarded because it contains nothing but spaces.
Action: Check record "<rec-no>" in the input data file.
Cause: Partitioning key fields contain invalid data.
Action: Check the input data file at line "<line>".
Cause: An I/O error occurred while writing a record to the output data file for node "<out-node>".
Action: Check your operating system documentation for file I/O errors and ensure that there is sufficient space on the output device.
Cause: Expected writing length (RECLEN) does not match the actual writing length.
Action: Adjust record length value defined in the configuration file.
Cause: If a binary numerical input data file, the record length has to be defined.
Action: Please specify the record length in your configuration file.
Cause: Float data type is only supported when the file type is BIN (binary).
Action: Make sure data types and the type of input data file match.
Cause: The file type specification (FILETYPE) in the configuration file is not valid.
Action: Valid values for the file type parameter are as follows:
All the values are case insensitive.
Cause: In a binary input data file, the length of a partition key with decimal data type must conform to the equation: LENGTH=(PRECISION+2)/2 (integer division), because it is a packed decimal.
Action: Match the length of a decimal-typed partition key with its precision if the input data file is a binary data file.
Cause: In a binary input data file, the length of a partition key with integer, small integer, float, and double data type must be a predefined constant, i.e. 4 for integer, 2 for small integer, 4 for float, and 8 for double.
Action: Check partition key definitions in the configuration file.
Cause: The maximum length for a file name is 80 bytes.
Action: Check the configuration file.
Cause: The NEWLINE flag must be either YES or NO, and if not given, it is NO.
Action: Check the specification of NEWLINE flag in the configuration file.
Cause: If a fixed-length positional ASC file or a binary numerical data file, each record has to be exactly the same length as the value of the RECLEN parameter in the configuration file.
Action: Make sure the input data file is complete.
Cause: For a positional ASC input data file or a delimited data file with parameter 32KLIMIT on, the maximum record length can not exceed the 32k (bytes) limit.
Action: Check your input data file and make sure the record length is less than 32k bytes.
Cause: For a positional ASC input data file or a binary numerical data file, each record has to be long enough to hold all partitioning keys.
Action: Check the record length of your input data file.
Cause: If a record is greater than 32k bytes long in a delimited data file, all partitioning keys of each record have to be within the first 32k bytes of the record.
Action: Check record "<rec-no>" in the input data file.
Cause: The maximum length of a line in the configuration file must be less than 255 bytes.
Action: Check your configuration file and make sure all lines are less than 255 bytes.
Cause: If new line checking is required for a fixed length ASC data file (NEWLINE parameter is YES and RECLEN parameter is not zero), the actual length of each record has to match the expected record.
Action: Check record "<rec-no>" in the input data file.
Cause: The codepage specification is not valid. It must be a positive integer.
Action: Correct the codepage specification in the configuration file.
Cause: The program failed to get the country code and codepage of its environment.
Action: Check with your database system adminstrator.
Cause: The database does not support codepage conversion between those two codepages.
Action: Please ensure your data is in a convertible codepage.
Cause: Valid format of decimal data is SQL_PACKEDDECIMAL_FORMAT, SQL_CHARSTRING_FORMAT, or SQL_IMPLIEDDECIMAL_FORMAT, mutually exclusive.
Action: Verify the format of your decimal data, correct the format value, and resubmit the command.
Cause: Specify either the table name or the nodegroup name, but not both.
Action: Check your command line options.
Cause: The utility needs to know where the database manager is installed, then it can find its bind file.
Action: Make sure your database manager is properly installed.
Cause: The table "<tbl-name>" cannot be located in sysibm.systables.
Action: Make sure the table exists in the database.
Cause: The nodegroup "<nodegroup>" cannot be located in sysibm.sysnodegroupdef.
Action: Make sure the nodegroup exists in the database.
Cause: The utility cannot open the output partition map file for writing. It will write the output to stdout.
Action: Check your file access permissions.
Cause: The size of the partition map is not correct. Data is corrupted in the database.
Action: Contact the Database Administrator to resolve the problem.
Cause: There is an invalid command line option.
Action: Make sure to specify the correct command line options.