198
219
A comma-separated list of files to exclude when extracting files.
199
220
If multiple files are specified, the list should be included in
227
Valid keywords (exactly one must be specified) are:
229
| NEW_VERSION Create a new version of an existing file.
230
| OVERWRITE Overwrite the same version of an existing file.
231
| (But only if the archive member name includes a
233
| NOEXTRACT Do not extract. An existing file is not affected.
236
When UnZip would extract an archive member, but the destination file
237
already exists, UnZip will, by default, ask the user what to do.
238
/EXISTING lets the user specify on the command line what to do in this
239
situation, eliminating the interactive question(s).
241
NOEXTRACT will always stop UnZip from extracting an archive member if
242
the destination file already exists.
244
If an archive member name does not include a VMS version number, or if
245
UnZip is run with /NOVERSION (the default, causing it to ignore version
246
numbers), then either NEW_VERSION or OVERWRITE will cause UnZip to
247
create a new version of the existing file.
249
If an archive member name does include a VMS version number, and if
250
UnZip is run with /VERSION, then NEW_VERSION will cause UnZip to create
251
a new version of the existing file, and OVERWRITE will cause UnZip to
252
overwrite the existing file which has the version specified by the
249
301
Convert filenames from all-uppercase operating systems to lowercase. This
250
302
option has no effect under VMS.
310
Causes UnZip to convert archived file names to ODS2-compatible file
311
names (substituting "_" for any invalid characters), regardless of the
312
type of the destination file system.
314
The default is to use ODS5-compatible file names when the destination
315
file system is ODS5, and to convert the names to ODS2-compatible names
316
when the destination file system is ODS2.
318
Beginning in UnZip 6.0, ODS2-compatible names are explicitly set to
258
The qualifier /OVERWRITE forces overwriting of existing files when extracting.
259
The negation /NOOVERWRITE results in never overwriting an existing file.
260
The default action is to prompt for desired action when about to
261
overwrite an existing file.
263
For VMS, "overwriting" results in the creation of a new version of the file,
264
unless version numbers are stored in the archive and /VERSION is specified.
329
/OVERWRITE is equivalent to /EXISTING = NEW_VERSION.
331
/NOOVERWRITE is equivalent to /EXISTING = NOEXTRACT.
302
Restore file owner and protection settings.
365
/RESTORE[=(KEYWORD, ...)]
367
Selects restoration options for some meta-data.
368
The optional keywords recognized are:
370
| OWNER_PROT Restore file owner and ACL protection settings.
371
| NOOWNER_PROT Do not restore file owner and ACL protection settings.
372
| NODATE Do not restore any timestamps.
373
| DATE=ALL Restore timestamps for all extracted entries, files
375
| DATE=FILES Restore timestamps for extracted files. (default)
378
By default, VMS UnZip restores the original date-time attributes for files,
379
but not for directories. This agrees with the behavior of VMS BACKUP
380
(and UnZip versions before 5.52 where the capability to restore directory
381
timestamps was added).
383
For compatibility with UnZip versions before 6.0 (5.53), the following
384
obsolete short forms are still accepted:
386
| Obsolete form: Modern form:
387
| /RESTORE /RESTORE = OWNER_PROT
388
| /NORESTORE /RESTORE = NOOWNER_PROT
384
473
VMS on-line help ported from UNZIP.TXT by Hunter Goatley.
389
On VMS, UnZip's UNIX style exit values are mapped into proper
392
| 1 (success) normal exit,
393
| (0x7fff0000 + 16*UnZip_errnum) -W- warnings
394
| (0x7fff0002 + 16*UnZip_errnum) -E- normal errors
395
| (0x7fff0004 + 16*UnZip_errnum) -F- fatal errors
398
The UnZip error level (or exit code) approximates the exit
399
codes defined by PKWARE and takes on the following values:
401
| VMS UnZip Type of error
403
| - 0 normal; no errors or warnings detected.
405
| W 1 one or more warning errors were encountered,
406
| but processing completed successfully any-
407
| way. This includes zipfiles where one or
408
| more files was skipped due to unsupported
409
| compression method or encryption with an
412
| E 2 a generic error in the zipfile format was
413
| detected. Processing may have completed
414
| successfully anyway; some broken zipfiles
415
| created by other archivers have simple work-
418
| F 3 a severe error in the zipfile format was
419
| detected. Processing probably failed imme-
422
| F 4 unzip was unable to allocate memory for one
423
| or more buffers during program initializa-
426
| F 5 unzip was unable to allocate memory or
427
| unable to obtain a tty to read the decryp-
430
| F 6 unzip was unable to allocate memory during
431
| decompression to disk.
433
| F 7 unzip was unable to allocate memory during
434
| in-memory decompression.
436
| F 8 [currently not used]
438
| E 9 the specified zipfiles were not found.
440
| E 10 invalid options were specified on the com-
443
| E 11 no matching files were found.
445
| F 50 the disk is (or was) full during extraction.
447
| F 51 the end of the ZIP archive was encountered
450
| E 80 the user aborted unzip prematurely with con-
451
| trol-C (or similar)
453
| E 81 no files were found due to unsupported com-
454
| pression methods or unsupported decryption.
455
| (If even one additional file is successfully
456
| processed, however, the exit status is 1.)
458
| E 82 no files were found due to bad decryption
459
| password(s). This is also the exit status
460
| if no files were found due to a combination
461
| of unsupported compression and bad pass-
462
| words. As in the previous case, however, a
463
| single successful file will result in an
464
| exit status of 1 instead.)
467
In addition, there is a compilation option to expand upon this behavior:
468
An executable compiled with the option RETURN_CODES defined displays
469
a human-readable explanation of what the error status means.
478
On VMS, UnZip's UNIX-style exit values are mapped into VMS-style status
479
codes with facility code 1954 = %x7A2, and with the inhibit-message
480
(%x10000000) and facility-specific (%x00008000) bits set:
482
| %x17A28001 normal exit
483
| %x17A28000 + 16*UnZip_error_code warnings
484
| %x17A28002 + 16*UnZip_error_code normal errors
485
| %x17A28004 + 16*UnZip_error_code fatal errors
488
Note that multiplying the UNIX-style UnZip error code by 16 places it
489
conveniently in the hexadecimal representation of the VMS exit code,
490
"__" in %x17A28__s, where "s" is the severity code. For example, a
491
missing archive might cause UnZip error code 9, which would be
492
transformed into the VMS exit status %X17A28092.
494
The UnZip VMS exit codes include severity values which approximate those
495
defined by PKWARE, as shown in the following table:
498
| severity code Error description
499
| ----------+---------+----------------------------------------------
500
| Success 0 Normal. No errors or warnings detected.
501
| Warning 1 One or more warnings were encountered, but
502
| processing completed successfully anyway.
503
| This includes archives where one or more
504
| (but not all) files were skipped because of
505
| unsupported compress or encrypt methods, or
507
| Error 2 Error in the archive format. Processing may
508
| have completed successfully anyway. Some
509
| defects in archives (made by other programs)
510
| can be repaired transparently.
511
| Fatal 3 Severe error in the archive format. Process-
512
| ing probably failed immediately.
513
| Fatal 4 Memory allocation failed in program initial-
515
| Fatal 5 Memory allocation failed in password pro-
517
| Fatal 6 Memory allocation failed while decompressing
519
| Fatal 7 Memory allocation failed while decompressing
521
| Fatal 8 Memory allocation failed (reserved for
523
| Error 9 Specified archive files were not found.
524
| Error 10 Invalid command-line options or parameters.
525
| Error 11 No files matched selection criteria.
526
| Fatal 50 Disk full.
527
| Fatal 51 Unexpected end-of-file while reading the
529
| Error 80 User interrupt (Ctrl/C).
530
| Error 81 No files were processed, because of unsup-
531
| ported compress or encrypt methods.
532
| Error 82 No files were processed, because of bad
534
| Fatal 83 Large-file archive could not be processed by
535
| this small-file program.
488
555
| -z display only the archive comment
491
| -a auto-extract only text files in standard VMS text file format
558
| -a extract text files in standard VMS text file format
492
559
| -aa extract all files as text
493
| -b auto-extract only binary files in VMS fixed 512 bytes records
494
| -bb extract all files as binary VMS fixed 512 byte record files
560
| -b auto-extract only binary files in fixed 512-byte record format
561
| -bb extract all files as binary in fixed 512-byte record format
495
562
| -j junk paths (don't recreate archive's directory structure)
496
| -n never overwrite existing files; don't prompt
497
| -o OK to overwrite files without prompting
563
| -n never overwrite or make a new version of an existing file
564
| -o always make a new version (-oo: overwrite orig) existing file
498
565
| -q perform operations quietly (-qq => even quieter)
499
566
| -C match filenames case-insensitively
500
| -L convert filenames to lowercase if created on MSDOS, VMS, etc.
501
| -P<pwd> supply decryption password on the command line (insecure!)
502
| -M page output through built-in "more" function
567
| -D do not restore any timestamps (--D restore them even for dirs)
568
| -L convert filenames to lowercase if created under DOS, VMS, etc.
569
| -M feed screen output through built-in "more" pager
570
| -P<password> supply decryption password on the cmd line (insecure!)
571
| -S use Stream_LF record format to extract text files (with -a[a])
503
572
| -V retain (VMS) file version numbers
504
| -X restore owner/protection info (may require privileges)
505
| -: allow "../" path components that traverse across extract dir root
573
| -X restore owner/ACL protection info (may require privileges)
574
| -Y treat ".nnn" suffix as version number ("a.b.3" -> "a.b;3")
575
| -: allow "../" path components to traverse across top extract dir
576
| -2 force creation of ODS2-compatible file names
508
Note that uppercase options such as -C, -L, -M, -P, -T, -V, -X and -Z
509
must be specified in quotes. For example:
579
Note that uppercase options such as -C, -D, -L, -M, -P, -S, -T, -V, -X, -Y,
580
and -Z must be specified in quotes (unless SET PROC/PARSE=EXTEND is set).
512
584
| $ unzip "-VX" -a zipfile