FUP Messages
File Utility Program (FUP) Reference Manual—523323-014
3-22
Cause. A DUP operation that did not specify PARTONLY was attempted on a
partitioned file, and one of the partitions is an SQL object.
Effect. None of the file is duplicated. The DUP operation continues executing on the
next file in the file set.
Recovery. If you intended to specify another type of file, retry the command after
correcting the file specification.
Cause. When you created or altered a file with a nonunique alternate key, the
combined length of the primary key, the alternate key, and the 2-byte key specifier
exceeded the 255-byte total allowed. Or when you created or altered a file with a
unique alternate key, the combined length of the alternate key and the 2-byte key
specifier exceeded the allowed 255-byte total.
Effect. The command fails.
Recovery. Retry the command, specifying values within the specified byte limits.
Cause. A RELOAD, STATUS, or SUSPEND command attempted to create a reload
server, but the server could not be created.
Effect. The command fails.
Recovery. Ask the system manager to install ORSERV on $SYSTEM.SYSTEM. If this
does not correct the problem, an internal error exists. In this case, contact your service
provider.
Cause. A file-system error occurred while the system tried to purge the indicated file.
Effect. The command fails.
Recovery. For corrective action for the file-system error number indicated by nnn, see
the Guardian Procedure Errors and Messages Manual.
Cause. FUP cannot access the file specified in a qualified file set.
Effect. A file-system error (error number could be 0) is generated.
PRIMARY KEY TOO LONG FOR AN ALTERNATE KEY FILE
PROCESS CREATION ERROR TRYING TO CREATE SERVER: %error
filename : PURGE ERR : nnn
QUALIFIED FILESET ERROR
To Next Page
Loading...
Need help?
General