FUP Messages
File Utility Program (FUP) Reference Manual—523323-014
3-6
Recovery. Informational message; no corrective action is needed.
Cause. A check was made of some internal structures.
Effect. The command might not finish.
Recovery. This message should never appear. If it does, contact your service
provider.
Cause. A logical style DEFINE name was specified for a DEFINE class, such as class
SPOOL or class TAPE, that does not exist.
Effect. The command fails.
Recovery. Specify a correct name and retry the command.
Cause. When an attempt was made to use FUP ALTER filename, NO AUDIT, FUP
encountered a “file is bad” error (CRASHOPEN flag is on). filename was partitioned.
Effect. The command is not executed.
Recovery. Reissue the FUP ALTER command for each partition.
Cause. A file-system error occurred while you tried a CREATE command with 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. A file name was entered with the volume name specified and the subvolume
name unspecified. In later RVUs, you are required to specify the subvolume name
when you specify the volume name in a command.
Effect. Processing continues.
CONSISTENCY CHECK
COULD NOT FIND DEFINE.
CRASH OPEN FLAG ON. MUST ALTER PARTITIONS INDIVIDUALLY (I.E.
PARTONLY)
filename : CREATE ERR : nnn
filename: DEFAULTED SUBVOLUME WILL NOT BE SUPPORTED IN THE
FUTURE
To Next Page
Loading...
Need help?
General