C PAK/UNPAK Messages
This section describes the error messages that can arise when you use PAK or UNPAK. In addition
to their own messages, PAK and UNPAK can display any BACKUP or RESTORE messages during
their processing.
num files created
Cause. The -split option was used, and PAK created num files.
Effect. None.
Recovery. Informational message; no corrective action is necessary.
'after' command too long
Cause. The length of the parameter to the -after option is larger than 255.
Effect. The program stops with completion code 2. No archive is created.
Recovery. Use a shorter command and try again.
Archive does not exist
Cause. The archive file given in the UNPAK command does not exist.
Effect. The program stops with completion code 2. No files are extracted.
Recovery. Correct the command and try again.
Archive file is too small - specify a larger extent
Cause. PAK reaches the maximum file size while writing to the archive.
Effect. The program stops with completion code 2. The created archive file is purged.
Recovery. Resubmit the command with larger extent size (-ext option), larger maxextents (-max),
or multifile option (-split) or reduce the number or size of files to be compressed.
Archive version: num
Cause. UNPAK has read the header of an archive file and reports the version of the file. The
supported version numbers are 1 and 2.
Effect. The program continues.
Recovery. None. This is not an error if the version is 1 or 2.
BACKUP issued a READ or WRITEREAD
Cause. The BACKUP process issued an unexpected READ operation BACKUP should only write
data to the PAK process.
Effect. The program abends. A saveabend file is possibly created. The archive is created but is
probably invalid.
Recovery. This is an internal error. Report it to your service provider.
Comment string too long: string
271
To Next Page
Loading...
Need help?
General