FUP Messages
File Utility Program (FUP) Reference Manual—523323-014
3-4
Recovery. Variable-length blocks must contain at least two bytes at the beginning of
the block.
Cause. An error occurred in the program logic.
Effect. FUP ends abnormally.
Recovery. Call your service provider and describe the circumstances under which the
error occurred.
Cause. The PART specification for CREATE or ALTER was wrong. For example, all
partition numbers must be sequential, starting from 1. When this message appears
after FUP LOAD... PARTOF..., it indicates that FUP found the file that should have
been the primary file, but it was not a partitioned file, or it was not the primary partition
for the destination.
Effect. The command fails.
Recovery. In the first case, retry the command after specifying all partitions up to the
maximum partition number. In the second case, correct either the destination file name
or the PARTOF volume name.
Cause. An attempt to load or copy a file failed because the record length specified for
a variable-length record was not valid. For example, the record length was a negative
number. This error can occur if the file to be loaded or copied was filled without
specifying the VAROUT option of the COPY command. Alternatively, data in the file
might have been corrupted.
Effect. The COPY or LOAD command fails.
Recovery. Retry the command after specifying the VAROUT option.
Cause. Unique and nonunique alternate keys cannot reside in the same alternate-key
file.
Effect. The CREATE or ALTER command fails.
Recovery. Retry the command after changing the alternate-key file.
Cause. An audited file was the object of a CHECKSUM command.
BAD CASE NUMBER
BAD PARTITION PARAMETERS
BAD VARIABLE RECORD LENGTH
CANNOT MIX UNIQUE AND NON-UNIQUE KEYS WITHIN AN ALTERNATE KEY
FILE
CAN'T CHECKSUM AUDITED FILES
To Next Page
Loading...
Need help?
General