FUP Messages
File Utility Program (FUP) Reference Manual—523323-014
3-2
Cause. An ALTFILE option specified an SQL object as an alternate-key file.
Effect. The operation terminates.
Recovery. Retry the command by specifying a valid alternate-key file.
Cause. An attempt to create or alter a file failed because an alternate-key file that had
no corresponding alternate key was specified.
Effect. The CREATE or ALTER command fails.
Recovery. Retry the command after correcting the ALTKEY or ALTFILE definition.
Cause. An attempt to create or alter a file failed because the length of the alternate
key (which was added to the offset of the alternate key) exceeded the record length
specified for the file.
Effect. The CREATE or ALTER command fails.
Recovery. Retry the command after correcting the ALTKEY or ALTKEY definition.
Cause. An attempt to create or alter a file failed. An alternate key was specified for a
file, but an alternate-key file was not specified for the alternate key.
Effect. The CREATE or ALTER command fails.
Recovery. Retry the command after correcting the ALTKEY or ALTFILE definition.
Cause. When entering the CREATE or ALTER command, you either omitted the
KEYLEN parameter from an ALTKEY specification or specified zero for KEYLEN.
Effect. The CREATE or ALTER command fails.
Recovery. Retry the command after correcting the KEYLEN parameter.
Cause. The ASSUMEID attribute of a file failed to transfer during a duplicate operation
while using the SAVEALL option to a remote node.
ALTERNATE KEY FILE CANNOT BE AN SQL OBJECT
AN ALTERNATE KEY FILE HAS NO CORRESPONDING ALTERNATE KEY
AN ALTERNATE KEY GOES BEYOND THE END OF THE RECORD
AN ALTERNATE KEY HAS NO CORRESPONDING ALTERNATE KEY FILE
AN ALTERNATE KEY HAS THE INVALID LENGTH OF 0
ASSUMEID NOT PRESERVED AT DESTINATION
To Next Page
Loading...
Need help?
General