File Utility Programming (FUP) Reference Manual

FUP Messages
File Utility Program (FUP) Reference Manual—523323-015
3-3
Effect. The ASSUMEID attribute is not preserved.
Recovery. Use the ALTER command to change the attribute. You might have to use
remote logon.
Cause. An attempt was made in DUP rename-options to rename a nonexistent
alternate file. The source file does not have the specified alternate-key file.
Effect. This is only a warning. Command execution proceeds, but the alternate-key file
is not created.
Recovery. Check that the rename-options are those intended, and specify valid
alternate-key file names.
Cause. An attempt was made in DUP rename-options to rename a nonexistent
secondary partition volume. The source file does not have the specified partition.
Effect. This is only a warning. Command execution proceeds.
Recovery. Check that the values for rename-options are those intended, and
specify valid partition file names. Retry the DUP operation if information was lost.
Cause. The ALTKEY or the ALTFILE specifications for a CREATE or ALTER
command were not correct. This situation can also occur if an existing file had invalid
alternate-key parameters and an attempt was made to load one of its alternate-key
files using LOADALTFILE.
Effect. The command fails.
Recovery. Reenter the command (if it is CREATE or ALTER) after correcting the
alternate-key parameters. For a LOADALTFILE command, alter the existing file to
contain valid alternate-key parameters.
Cause. An attempt to load or copy a file failed because the length of a block was
either 0 or 1 byte. 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.
ATTEMPT TO RENAME A NONEXISTENT ALTFILE
ATTEMPT TO RENAME A NONEXISTENT PARTITION
BAD ALT KEY PARAMETERS
BAD BLOCK LENGTH FOR VARIABLE RECORD LENGTH BLOCKING