FUP Messages
File Utility Program (FUP) Reference Manual—523323-014
3-30
Recovery. Determine why the tape mount request was rejected, resolve the problem,
and retry the command. For the corrective action for file-system error 194, see the
Guardian Procedure Errors and Messages Manual.
Cause. The key-file-number parameter to LOADALTFILE was undefined for the
specified primary file.
Effect. The command fails.
Recovery. Execute a FUP INFO with the DETAIL option to see what the alternate-key
files are for a given file. Use LOADALTFILE only for existing alternate-key files.
Cause. A specified string was too long.
Effect. The command fails.
Recovery. Retry the command after correcting the string length.
Cause. Too many objects were specified for the attempted command. For example,
more than 10 file sets were specified in a file-set list for FUP, or too many key tags
were specified for the BUILDKEYRECORDS command.
Effect. The command fails.
Recovery. Retry the command with an acceptable number of specified objects.
Cause. Too many (more than 1000) volumes were specified for the system.
Effect. Only the first 1000 volumes are sorted by name. The remaining volumes are
printed in hardware device number order.
Recovery. Retry the command with 1000 or fewer volumes specified.
Cause. During execution of the COPY, LOAD, or LOADALTFILE command, the input
records were truncated.
Effect. The command proceeds; this is only a warning.
THERE IS NO SUCH ALTERNATE FILE
TOO LONG
TOO MANY
TOO MANY ENTRIES TO SORT, REST ARE UNSORTED
TRUNCATION OCCURRING
To Next Page
Loading...
Need help?
General