372
SecureZIP ® for z/OS ® Messages and Codes Guide SZZM-V10R0013 PKWARE Inc.
SecureZIP® for z/OS®
Messages and Codes Guide
SZZM-V10R0013
PKWARE Inc.
ii
PKWARE, Inc. 648 N Plankinton Avenue, Suite 220 Milwaukee, WI 53203 Main office: 888-4PKWARE (888-475-9273) Sales: 937-847-2374 (888-4PKWARE / 888-475-9273) Sales - E-Mail: [email protected] Support: 937-847-2687 Support - http://www.pkware.com/business_and_developers/support Fax: 414-289-9789 Web Site: http://www.pkware.com 10.0 Edition (2007) SecureZIP for z/OS, PKZIP for z/OS, SecureZIP for i5/OS®, PKZIP for i5/OS, SecureZIP for UNIX, and SecureZIP for Windows are just a few of the members of the PKZIP family. PKWARE Inc. would like to thank all the individuals and companies—including our customers, resellers, distributors, and technology partners—who have helped make PKZIP the industry standard for trusted ZIP solutions. PKZIP enables our customers to efficiently and securely transmit and store information across systems of all sizes, ranging from desktops to mainframes. This edition applies to the following PKWARE Inc. licensed programs: PKZIP for z/OS (Version 10, Release 0, 2007) SecureZIP for z/OS (Version 10, Release 0, 2007) SecureZIP Partner for z/OS (Version 10, Release 0, 2007) PKZIP and SecureZIP are registered trademarks of PKWARE Inc. z/OS, i5/OS, zSeries, and iSeries are registered trademarks of IBM Corporation. Other product names mentioned in this manual may be trademarks or registered trademarks of their respective companies and are hereby acknowledged. Any reference to licensed programs or other material, belonging to any company, is not intended to state or imply that such programs or material are available or may be used. The copyright in this work is owned by PKWARE Inc., and the document is issued in confidence for the purpose only for which it is supplied. It must not be reproduced in whole or in part or used for tendering purposes except under an agreement or with the consent in writing of PKWARE Inc., and then only on condition that this notice is included in any such reproduction. No information as to the contents or subject matter of this document or any part thereof either directly or indirectly arising there from shall be given or communicated in any manner whatsoever to a third party being an individual firm or company or any employee thereof without the prior consent in writing of PKWARE Inc. Copyright © 1989 - 2007 PKWARE Inc. All rights reserved.
iii
Contents
PREFACE............................................................................................................. 1
About this Manual.......................................................................................................1
Conventions Used in this Manual .............................................................................1
Related Publications ..................................................................................................2
Related IBM Publications...........................................................................................2
Related Information on the Internet..........................................................................3
User Help and Contact Information ..........................................................................4
Release Notes .............................................................................................................4
CHAPTER 1. SECUREZIP MESSAGES.............................................................. 5
Message Format .........................................................................................................5
Message Definitions...................................................................................................6
IEC – IKJ IBM System-Related Messages ................................................................7
ZPAM - Archive Manager Messages.......................................................................10
ZPAP – Application Programming Interface Messages........................................79
ZPCA - Certificate Administration Messages ........................................................92
ZPCE - Compression Engine Messages...............................................................125
ZPCM - Configuration Manager Messages...........................................................126
ZPCO - Compression Manager Messages ...........................................................182
ZPCS - Common Service Messages .....................................................................190
ZPDA - Dynamic Allocation Messages .................................................................194
ZPEN – Encryption Processing Messages...........................................................203
ZPEX - Extract Manager Messages.......................................................................275
ZPFM - File Manager Messages ............................................................................299
ZPGE - General Messages .....................................................................................324
ZPIS – ISPF User Interface Messages ..................................................................327
ZPLI - License Manager Messages .......................................................................328
ZPMT - Main Task Messages .................................................................................334
ZPTM - Task Manager Messages ..........................................................................342
iv
ZPTR - Trace Recording Messages ......................................................................344
CHAPTER 2. USER ABEND CODES.............................................................. 345
Code Definitions .....................................................................................................345
U1999 .......................................................................................................................345
CHAPTER 3. INTERNAL PROCESSING CODES........................................... 346
General ....................................................................................................................346
EvtAuth Errors ........................................................................................................346
PKCAuth Errors ......................................................................................................346
EvtHash Errors........................................................................................................347
EvtCrypt Errors .......................................................................................................347
EvtCrypt ICSF Integration Codes..........................................................................348
EvtCertE Errors.......................................................................................................349
CertKeys Errors ......................................................................................................349
GetCertFls Errors....................................................................................................349
EvtCertE Decryption Errors...................................................................................350
EvtCertE Signing Errors.........................................................................................350
PartnerLink SecureZIP Partner Errors..................................................................351
Certificate Store VSAM Error Codes.....................................................................352
Certificate Scan Utility (PKSCANCRT) Messages ...............................................353
HFS Error Codes ($HFSCODE)..............................................................................355
CHAPTER 4. UTILITY PROGRAM MESSAGES............................................. 357
PKCS - Certificate Store Utility Messages ...........................................................357
INDEX............................................................................................................... 361
1
Preface
This manual covers messages for SecureZIP for z/OS and SecureZIP Partner for z/OS.
SecureZIP for z/OS provides powerful, easy-to-use data compression and data protection on the mainframe. SecureZIP for z/OS protects data with digital signatures and several encryption choices. Both trusted RSA BSAFE encryption or IBM ICSF are offered, either password- or certificate-based, and with key lengths of up to 256 bits. SecureZIP for z/OS uses the widely-adopted ZIP format and creates files that can be accessed on all major platforms throughout the enterprise.
The SecureZIP Partner for z/OS application is a special version of SecureZIP for z/OS, provided to partner participants in the PKWARE PartnerLink program. SecureZIP Partner offers most of the commands and options of the full SecureZIP for z/OS but works only with archives created by (or for) a PartnerLink sponsor. A PartnerLink sponsor organization gives SecureZIP Partner to partner organizations that may not have SecureZIP for z/OS to enable sponsor and partner to securely exchange files.
About this Manual
This manual provides information to help a system administrator install and use SecureZIP for z/OS in an operational environment on supported IBM releases of z/OS. It is assumed that anyone using this manual has a good understanding of JCL and data set processing.
Conventions Used in this Manual
Throughout this manual, the following conventions are used:
SecureZIPz (bold-italicized) is used as a shorthand to refer to SecureZIP for z/OS.
The terms ZIP and UNZIP are used to refer to the respective overall processes of operating on an archive.
The term PKZIP is often used generically to refer to any of the underlying executable programs that process archives in PKZIP for z/OS and SecureZIP for z/OS. These include programs PKZIP and SECZIP, to ZIP archives, and programs PKUNZIP and SECUNZIP, to UNZIP them. PKZIP is also more narrowly used to refer to either the PKZIP or SECZIP program, and PKUNZIP is often used to refer to either the PKUNZIP or SECUNZIP program.
The use of the Courier font indicates text that may be found in job control language (JCL), parameter controls, or printed output.
The use of italics in a command line indicates a value that must be substituted by the user, for example, a data set name. Italics are also used in body text to quote command names and so forth or to indicate the title of a manual or other publication.
2
The use of <angle brackets> in a command definition indicates a mandatory parameter.
The use of [square brackets] in a command definition indicates an optional parameter.
A vertical bar (|) in a command definition is used to separate mutually exclusive parameter options or modifiers.
Related Publications
SecureZIPz product manuals include:
SecureZIP for z/OS User’s Guide - Provides detailed information on the product set in the z/OS operating environment. Provides a general introduction to data compression and an overview of how to use SecureZIPz control cards, and parameters. Provides security extension information.
SecureZIP for z/OS Messages and Codes Guide - Provides information on the messages and codes that are displayed on the consoles, printed outputs, and associated terminals.
SecureZIP for z/OS System Administrator’s Guide - Provides detailed information to assist the system administrator to install and manage SecureZIPz in an operational environment. Topics include:
o System planning and administration
o Installation, licensing and configuration
o Verifying the installation
o Security administration overview (SecureZIP)
o Certificate store management (SecureZIP)
Related IBM Publications
IBM Manuals relating to the SecureZIPz product include:
System Codes - Documents the completion codes issued by the operating system when it terminates a task or an address space. Describes the wait state codes placed in the program status word (PSW) when the system begins a wait state. Describes the causes of loops.
System Messages - Documents the messages issued by the z/OS operating system. The descriptions explain why the component issued the message, give the actions of the operating system, and suggest responses by the applications programmer, system programmer, and/or operator.
JES2 Messages - Documents the messages issued by the JES2 subsystem. The descriptions explain why the component issued the message, give the actions of the operating system, and suggest responses by the applications programmer, system programmer, and/or operator.
JCL User's Guide - Describes the job control tasks needed to enter jobs into the operating system, control the system's processing of jobs, and request the resources needed to run jobs. To perform the tasks, programmers code job control statements. The user's guide assists in deciding how to perform job control tasks.
3
JCL Reference - Describes the job control tasks needed to enter jobs into the operating system, control the system's processing of jobs, and request the resources needed to run jobs. To perform the tasks, programmers code job control statements. The reference guide; is designed to be used while coding the statements.
Access Methods Services - Documents the functions that are available with Virtual Storage Access Method (VSAM) and describes the IDCAMS commands that can be issued to control VSAM datasets.
DFSMS Using Data Sets – Reference materials regarding z/OS file systems and their usage.
DFSMS Macro Instructions for Data Sets – Reference material regarding I/O handling and diagnostics.
ICSF Application Programmers Guide – Describes how to use the callable services provided by the Integrated Cryptographic Service facility.
ICSF Administrators Guide – Describes how to manage cryptographic keys by using the z/OS Integrated Cryptographic Service facility.
ICSF Overview – Contains overview and planning information for the z/OS Integrated Cryptographic Service facility.
ISPF bookshelf – Reference materials regarding run-time environments supporting, and used by SecureZIPz.
Language Environment bookshelf – Reference materials regarding run-time environments supporting, and used by SecureZIPz.
TSO/E Command Reference - Documents the functions of the TRANSMIT and RECEIVE Command Facility used for the distribution and allocation of SecureZIPz installation libraries.
TSO/E REXX Reference – Reference materials regarding run-time environments supporting, and used by SecureZIPz.
z/OS XL C/C++ bookshelf – Reference materials regarding run-time environments supporting, and used by SecureZIPz.
z/OS Unix System Services User’s Guide – Provides information that is fundamental to working with UNIX File Systems (also known as the hierarchical file system).
MVS/QuickRef (Chicago-Soft, Ltd.) - Includes both messages and command reference material for SecureZIPz.
Related Information on the Internet
PKWARE, Inc.
www.pkware.com
FTP site
Product manuals - ftp://bigiron.pkware.com/pub/manuals/zOS
Product downloads - ftp://bigiron.pkware.com/pub/products
o SecureZIP for z/OS - ftp://bigiron.pkware.com/pub/products/securezip/zOS
4
o PartnerLink: SecureZIP Partner - ftp://bigiron.pkware.com/pub/products/partnerlink/zOS
National Institutes of Standards
Computer Security Resource Center - http://csrc.ncsl.nist.gov
Information on the AES development - http://csrc.nist.gov/encryption/aes/
Information on Key Management - http://csrc.nist.gov/CryptoToolkit/tkkeymgmt.html
RSA BSAFE® Content Library – http://www.rsasecurity.com/content_library.asp
User Help and Contact Information
For licensing, contact Sales at 937-847-2374 (888-4PKWARE / 888-475-9273) or email [email protected].
For technical assistance, contact the Technical Support at 937-847-2687 or visit the Support Web site at http://www.pkware.com/business_and_developers/support.
Release Notes
Release 10 – Message ZPGE001T was renamed to ZPGE001I
5
Chapter 1. SecureZIP Messages
Note: The message format refers to the program generically as PKZIP/SECZIP or PKUNZIP/SECUNZIP.
This chapter gives details about the standard messages produced by PKZIP/SECZIP and PKUNZIP/SECUNZIP. All the messages detailed in this section are written to SYSPRINT, SYSLST, or to the console, depending on the operating system and its configuration.
The first four positions of the message number consist of a prefix and sub-prefix that identify the program and program module generating the message. Some messages can be generated from a number of points in the program logic and thus a single message number (nnn - the numeric identifier) may be prefixed by more than one program and program module identifier.
Message Format
The format of the messages produced by both PKZIP/SECZIP and PKUNZIP/SECUNZIP is as follows:
ZPbbnnns <= Text => <= Variables =>
ZP is the standard prefix for all PKZIP/SECZIP and PKUNZIP/SECUNZIP messages.
bb indicates which component originated the message. Possible values for these sub-components include:
AM Archive Manager - processes the input and output archives. Also schedules compression tasks.
AP Application Program Interface management.
CA Certificate Administration
CE Compression Engine - performs data compression.
CM Configuration Manager - read and parses control statements and determines eligible files to compress.
CO Compression Manager - reads input files for compression and handles staged data from the compression engine.
CS Common Service - a variety of system services.
DA Dynamic Allocation - manages dynamic allocation routines.
EN Encryption Processing – messages relating to encryption and certificates
EX Extract Manager - manages UNZIP files and calls decompression.
FM File Manager - various I/O and data management services.
6
GE General Processing.
IS ISPF Dialog
LI License Manager - licensing functions.
MT Main Task - SECZIP and SECUNZIP mainlines.
TM Task Manager - Sub-task management.
TR Trace Recording -
nnn is the message number.
s is the severity. In most cases, the return code shown in parenthesis will be associated with the level of message The possible values are:
C Continuation line E Error (8 or higher) I Informational (no effect on RC)
T Trace
W Warning (4)
Text information specific to the message number and those conditions causing the message to be displayed.
Variables values inserted into the message that are unique to the processing conditions occurring at that time. Three types of variable data may be displayed in the formats:
+44+C+ represents 44 Characters (for example, DSNAME).
+4+D+ represents 4 Decimal digits. (for example, byte count).
+8+H+ represents 8 Hexadecimal digits (for example, storage address).
Message Definitions
The messages produced by PKZIP/SECZIP and PKUNZIP/SECUNZIP are described in the following sections, listed in order by message number.
System-Related 7
IEC – IKJ IBM System-Related Messages
IEC214I
IEC214I 614-10,IGG0201W,jobname,stepname,ddname Explanation: Information relating to networked file services (NFS). An abnormal termination of file access through an NFS mount point may be detected when the remote server is unable to complete a request, or terminates the file connector unexpectedly. This may be induced by insufficient permissions on the remote system or a break in the connection for the mount point with the NFS server. System Response: Processing for the related file is terminated. User Response: Work with the networking administration team responsible for the associated mount point (and its target NFS server) to ensure that access authorized. Invoking module: Operating System
IEF238D
*nn IEF238D jobname - REPLY DEVICE NAME OR 'CANCEL'. Explanation: An attempt was made to create or access a data set on a volume that is not mounted. The operator is prompted to either supply the device address of the volume, or CANCEL the request. System Response: If the operator replies CANCEL, then the request is terminated. Subsequent processing depends on the type of file (Archive or Output data set) being processed, and processing options requested. User Response: Determine the source of the volume serial being used and correct the commands or JCL involved. See Also: //SYSPRINT DD output Related messages: IEF244I, IEF877E, IEF238D Volume information was provided by one of the following: 1. Extended attributes from the original file when the Archive was created. 2. The Defaults module being used (ACZDFLT) Ref: Installation Guide 3. Command input (EXEC parms, //PARMLIB DD and //SYSIN DD
System-Related 8
Supply an accessible volume serial or SMS STORCLASS through the appropriate ARCHIVE_xxx or OUTFILE_xxx command Note: By using -SHOW_SETTINGS as the last command in the //SYSIN DD command stream, a determination can be made as to the source of the volume serial. If the volume does not show under the associated volume-list for either the Archive or Output file, then the Volume serial came from either the EXEC parm or the internal file attributes in the Archive. Invoking module: Operating System
IEF244I
IEF244I jobname stepname - UNABLE TO ALLOCATE 1 UNIT(S) Explanation: See IEF238D System Response: See IEF238D User Response: See IEF238D Invoking module: Operating System
IEF877E
IEF877E jobname NEEDS 1 UNIT(S) FOR VIEW ddname FOR VOLUME volser OFFLINE 0318-032F 0332 0334-033F 0355-03BE 0A80-0 : OFFLINE, NOT ACCESSIBLE Explanation: See IEF238D System Response: See IEF238D User Response: See IEF238D Invoking module: Operating System
IGD17271I
IGD17271I ALLOCATION HAS BEEN ALLOWED TO PROCEED FOR DATA SET ... ALTHOUGH VOLUME COUNT REQUIREMENTS COULD NOT BE MET
System-Related 9
Explanation: An allocation request (for either work space or a dynamically created ZIP Archive) was performed with the maximum number of volumes supported (31). This is an informational message from the operating environment and can be ignored. System Response: Processing Continues User Response: None Invoking module: Operating System
IKJ56228I
IKJ56228I DATA SET +44+C+ NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED Explanation: When a dataset is being searched for dynamically, this message is put out by the dynamic allocation service of the operating system. System Response: The message is informational, and PKZIP/SecureZIP will take appropriate action according to the work being performed (e.g. create a new output file if the requested DSN could not be found). User Response: The command -SUPPRESS_DYNALLOC_MSGS may be used to suppress this message. However, when error conditions are encountered, use of this command may mask the reason behind it. Invoking module: Operating System
Archive Manager 10
ZPAM - Archive Manager Messages
ZPAM000I
ZPAM000I +121+C+ Explanation: A general purpose informational message for Archive Management. System Response: None User Response: Review surrounding messages and JOB log for additional information. Invoking module: <ACAMGR>
ZPAM000W
ZPAM000W +121+C+ Explanation: A general purpose warning message for Archive Management. System Response: None User Response: See detail information under Explanation. Invoking module: <ACAMGR>
ZPAM001C
ZPAM001C ... +100+C+ Explanation: A continuation line from -VIEWDETAIL showing the filename (in internal archive format). Ref: ZPAM001I System Response: None User Response: None Invoking module: <ACAMVIEW>
Archive Manager 11
ZPAM001I
ZPAM001I Filename: +100+C+ Explanation: A display line from -VIEWDETAIL showing the filename from the archive. This name has been translated with the translate table specified by -TRANSLATE_TABLE_FILEINFO System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM002I
ZPAM002I File type: +6+C+ +17+C+ Explanation: A display line from -VIEWDETAIL showing the data type of the file being listed. +6+C+ will have one of the following values: "TEXT" - File data was translated (possible ASCII). "BINARY" - File data was not translated. +17+C+ may have the following values: "SAVED_LRECL (RDW)" -SAVE_LRECL was used during ZIP processing. Each record is prefixed by an RDW containing the length. System Response: None User Response: When performing -EXTRACT, -USE_SAVED_LRECL should be specified. Invoking module: <ACAMVIEW>
ZPAM003I
ZPAM003I Date/Time: +11+C+ +8+C+ Explanation: A display line from -VIEWDETAIL showing the date and conditionally the time (if available) from the ZIP Archive. The date and time are displayed "as is" without timezone conversion (or daylight savings time adjustment).
Archive Manager 12
If created by PKZIP for z/OS or SecureZIP for z/OS, this date/time combination is governed by -ARCHIVE_TIMESTAMP. Other platforms typically use the local system time to set this value. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM004I
ZPAM004I Compression Method: +20+C+ Explanation: A display line from -VIEWDETAIL showing the method of compression used during ZIP processing. +20+C+ may have one of the following values" "DEFLATE" - Created by PKZIP 2.04g compatible products (PKZIP and SecureZIP MVS use this method by default). "IMPLODE" - Created by pre-2.0 PKZIP compatible products "STORED" - Data has not been compressed "REDUCED" - An early method pre-2.0 PKZIP. "UNRECOGNIZED" Note: -COMPRESSION_LEVEL can be used in PKZIP and SecureZIP for z/OS to control this value during ZIP processing. A value of STORE will result in "STORE". All others will result in "DEFLATE". System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM005I
ZPAM005I Compressed Size: +8+D+ Explanation: A display line from -VIEWDETAIL showing the resulting number of bytes after processing the data. This count does not include the Archive directory
Archive Manager 13
information. Note: When the Data Type is "TEXT", record delimiters are added to the records before processing. It is possible that a STORED file byte count can be larger than the original file's byte count. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM006I
ZPAM006I Uncompressed Size: +8+D+ Explanation: A display line from -VIEWDETAIL showing the resulting byte-count of the data before processing by the compression engine. Note: When the Data Type is "TEXT", record delimiters are added to the records before processing. The byte count can be larger than the number of data bytes in an EBCDIC data set. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM007C
ZPAM007C XTAPE VSeq/BLK/Pos: +8+D+ /+8+D+/ +8+H+ Explanation: A conditionally displayed VIEWDETAIL report line showing Enhanced Tape positioning information of the file in the archive. The information is used during UNZIP processing to locate the file within the archive. VSeq - Volume sequence number (relative to 1) BLK - The block ID (decimal) returned by NOTE Pos - The relative position (Hex offset relative to 0) within the block System Response: None User Response: None
Archive Manager 14
ZPAM007I
ZPAM007I 32-bit CRC: +8+H+ LHDR Offset: +16+C Explanation: A display line from -VIEWDETAIL showing the resulting CYCLICAL-REDUNDANCY-CHECK computed by the compression Routine and the offset (in decimal) to the local header. System Response: The CRC value will be used during -TEST and -EXTRACT processing to validate the integrity of the data. User Response: None Invoking module: <ACAMVIEW>
ZPAM008I
ZPAM008I Created by: +10+C+ +4+C+ {PKZIP 2.x Compatible} Explanation: A display line from -VIEWDETAIL showing the product and release level detected as the creating ZIP product. The values for product include: "PKZIP " (a general PKZIP product) "PKZIP for MVS " A product of PKWARE "PKZIP for OS400" A product of PKWARE "PKZIP for i5/OS" A product of PKWARE "SecureZIP for i5/OS" A product of PKWARE "PKZIP for z/OS" A product of PKWARE "SecureZIP for z/OS" A product of PKWARE The values for release reflect the "PKZIP" release saved in the archive directory. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM009I
ZPAM009I Needed to extract: +20+C+ Explanation: A display line from -VIEWDETAIL describing the Zip File Format specification level required to extract this file. This value does not represent the Product Release number. See the User's Guide for more information regarding the .ZIP File Format Specification and the corresponding
Archive Manager 15
product release numbers required to support individual features. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM010I
ZPAM010I Encryption: +40+C Explanation: A display line from -VIEWDETAIL indicating whether encryption was used on the file. -PASSWORD during ZIP processing controls whether this flag is set in the Archive directory for the file. The algorithm and mode of encryption are displayed. Standard ======== SecureZIP for z/OS provides backward compatibility with PKZIP-compatible programs using older 96-bit encryption. This method can only be used with Password-based encryption. Advanced Encryption: AES and BSAFE(R) ======================================= SecureZIP for z/OS provides a licensed set of algorithms that can be specified with the -ENCRYPTION METHOD command, supplying up to 256-bit encryption with various algorithms. SecureZIP offers the ability to protect files with a PASSWORD, Certificate-based RECIPIENTs, or a combination of both. Password-based+encryption requires that both the sending and receiving parties know the same password to generate the correct internal key for the encryption algorithm. Certificate-based+encryption allows the exchange of encrypted data without the exposure of also exchanging or retaining a password. This form of encryption uses a Public-key digital certificate when created and its corresponding Private-key certificate by the recipient. Digital certificates may be identified and selected by naming information (such as "Common Name" or and email address). Combination-key encryption specifies one or more recipients who do not require a password, as well as a
Archive Manager 16
password for access without having the Private-key certificate available. Either the Private-key certificate, or the password may be used for extraction. System Response: None User Response: During -EXTRACT or -TEST processing, the correct case-sensitive password must be provided. Invoking module: <ACAMVIEW>
ZPAM011C
ZPAM011C ... +80+C+ Explanation: A continuation line for ZPAM011I System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM011I
ZPAM011I Comment: +80+C+ Explanation: A display line from -VIEWxxxCOMMENT showing a saved comment for the Zip related Zip file. This comment may have been placed in the Archive directory entry by another PKZIP-compatible product. See also: ZPAM012I regarding a Zip Archive comment. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM012C
ZPAM012C ... +80+C+ Explanation: A display line from -VIEWxxx showing a saved ARCHIVE comment. (A continuation of ZPAM012I) System Response: None
Archive Manager 17
User Response: -ARCHIVE_COMMENT allows a PKZIP/SecureZIP for z/OS user to specify an Archive comment. Invoking module: <ACAMVIEW>
ZPAM012I
ZPAM012I ... +80+C+ Explanation: A display line from -VIEWxxx showing a saved ARCHIVE comment. (This is a comment that is stored for the entire Archive, as opposed to an individual file in the Archive). See also: ZPAM011I regarding a Zip File comment. System Response: None User Response: -ARCHIVE_COMMENT allows a PKZIP/SecureZIP for z/OS user to specify an Archive comment. Invoking module: <ACAMVIEW>
ZPAM013I
ZPAM013I ******************************************** Explanation: A -VIEWDETAIL report separator. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM014I
ZPAM014I +8+D+ file(s) are in the input Archive. Explanation: -VIEW information. System Response: None User Response: None Invoking module: <ACAMVIEW>
Archive Manager 18
ZPAM015I
ZPAM015I Length Method Size Ratio Date Time CRC-32 Name Explanation: -VIEW header line. LENGTH - UNCOMPRESSED size (see ZPAM006I) METHOD - Compression Method (see ZPAM004I) SIZE - Reflects COMPRESSED size (see ZPAM005I) RATIO - Data compression ratio DATE/TIME (as stored in Archive, see ZPAM003I) CRC-32 - Integrity check value. (see ZPAM007I) Name - Zip file name. (see ZPAM001I) System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM016I
ZPAM016I ------------ ------------ ------------ ----- ---------- ----- Explanation: -VIEW header separator line. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM017C
ZPAM017C +121+C+ Explanation: -VIEW data line continuation. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM017I
ZPAM017I +121+C+ Explanation: -VIEW data line. See ZPAM015I for column header info.
Archive Manager 19
System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM018I
ZPAM018I ------------ ------------ ----- Explanation: -VIEW trailer System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM019I
ZPAM019I +45+C+ Explanation: -VIEW summary line with counts and overall percentage. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM020I
ZPAM020I Length Method Size Ratio Date Time Name Explanation: -VIEWBRIEF header line. See ZPAM015I header descriptions. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM021I
ZPAM021I ------------ ------------ ------------ ----- ---------- -----
Archive Manager 20
Explanation: -VIEW separator line. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM030I
ZPAM030I Output Archive opened: +80+C+ Explanation: During ZIP processing, the indicated output Archive was successfully opened. System Response: None User Response: None Invoking module: <ACAMGR> Invoking module: <ACAMVIEW>
ZPAM031I
ZPAM031I ZIPFORMAT=zzzz UNIT=uuuu BLKSIZE=bbbbb Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued for an opened archive to indicate some of the archive characteristics. zzzz - Represents the ARCHIVE_ZIPFORMAT that was identified for the archive. "XTAPE*IGNR" indicates that an enhanced tape format was identified but will not be processed with enhanced tape positioning features. This may be present when STAGE_TAPE_ON_DISK=Y is active, or the archive has been moved from its original tape location. System Response: None User Response: None Invoking module: <ACAMGR>
Archive Manager 21
ZPAM032I
ZPAM032I File already in Archive: +80+C+ Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued for each ZIP file request that was already in the Archive and could not be added. Associated Message: ZPAM092E Nothing to do! System Response: Processing continues with other selection files. User Response: None Invoking module: <ACAMGR>
ZPAM033I
ZPAM033I Self-extracting archive detected: +80+C+ Explanation: While reading the input Archive, a Preamble was detected that matches a known self-extracting program. +8+C+ - Designates the matched self-extractor. SF2AIX IBM AIX Version 4.0 and above SF2HP HP/UX Version 9.0 and above SF2LNX2I LINUX Kernel 2.x for Intel SF2SUN Sun Solaris 2.3 (SunOS 53) and above SF2WIN Microsoft Windows (95 and above) SF6AIX IBM AIX Version 4.3 and above SFXAIX is an alias for this value. SF6HP HP/UX Version 10.20 and above SFXHP is an alias for this value. SF6LNX2I LINUX running the 2.4 or later kernel on x86 with glibc-2.2.4 SFXLNX2I is an alias for this value. SF6SUN Sun Solaris 2.6 and above SFXSUN is an alias for this value. SFAWINC Microsoft Windows command line (Windows 98, ME, NT 4.0, 2000, XP) SFXWIN is an alias for this value. SFAWING Microsoft Windows GUI (same as SFAWINC) See also: User's Guide -INCLUDE_SFX for a detailed list of supported platforms and release levels of extractors. +80+C+ A self-extraction release level display. System Response: None User Response: None
Archive Manager 22
Invoking module: <ACAMGR>
ZPAM034T
ZPAM034T ARCHIN FMCB created: +8+H+ for +80+C+ Explanation: Problem analysis. When the input Archive file is determined, a File Management Control Block is built to describe it. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM035E
ZPAM035E ARCHOUT Archive DCB information missing/mismatch in DD +8+C+ Explanation: An abend 013-34 was detected on the open of the output archive. System Response: The execution is aborted. User Response: -See the JOBLOG messages for IEC141I. -Reference IBM z/OS MVS System Messages manual. -Correct the DCB specifications relating to the output Archive. Invoking module: <ACAMGR>
ZPAM036E
ZPAM036E //+8+C+ Open Failure for archive. Check joblog for additional Explanation: The open for the output Archive dataset failed. System Response: The execution is aborted. User Response: Check the JOBLOG for operating system messages relating to the open failure. Invoking module: <ACAMGR>
ZPAM037E
ZPAM037E -STAGE_TAPE_ON_DISK could not be performed. DYNALLOC DARC=+4+C+
Archive Manager 23
Explanation: An attempt was made to copy the input Archive to a temporary disk file before processing. The allocation of the file failed. System Response: The copy of the file is terminated. Processing continues with the original input Archive. A minimal return code of 4 will be generated for the step. User Response: -Determine the reason for the allocation failure. -For information about dynamic allocation reason codes, see the IBM z/OS MVS Programming: Authorized Assembler Services Guide. -Check the SYSPRINT messages for other dynamic allocation error messages (ZPDA....). Invoking module: <ACAMGR>
ZPAM038E
ZPAM038E -STAGE_TAPE_ON_DISK could not be performed. I/O error during Explanation: An attempt was made to copy the input Archive to a temporary disk file before processing. The write to the file failed. System Response: The copy of the file is terminated. Processing continues with the original input Archive. A minimal return code of 4 will be generated for the step. User Response: -Determine the reason for the write failure. -Check the JOBLOG for operating system messages relating to the file (e.g. x37 abends due to insufficient space). -Specify modified -TEMPxxxx commands as appropriate or use the //ARCHTEMP DD statement to provide allocation information for the temporary Archive dataset. Invoking module: <ACAMGR>
ZPAM039I
ZPAM039I -STAGE_TAPE_ON_DISK copy to //ARCHTEMP completed. Explanation: A request was made to copy the input Archive to a temporary disk file before processing, or dynamically invoked for 3400-tape processing to improve performance. The copy of the file was successful.
Archive Manager 24
System Response: Input Archive operations will continue with the disk-copy of the Archive. User Response: None. Invoking module: <ACAMGR>
ZPAM040C
ZPAM040C +54+C+ Explanation: A continuation of ZPAM040E indicating the name of the PATH involved. System Response: See ZPAM040E User Response: See ZPAM040E Invoking module: <ACAMGR> <ACCMGR>
ZPAM040E
ZPAM040E HFS archive could not be opened. Reason=+8+D+ Explanation: The ZIP archive could not be opened for the reason indicated by +8+D+ as follows: '2981' An unsupported HFS file type was found to be defined for the archive file. For example, the PATH specified a directory or FIFO Special File (which is not supported for an input Archive) instead of a regular file. System Response: Processing of the archive will be terminated. User Response: Correct the specification of the archive to a supported type. Invoking module: <ACAMGR> <ACCMGR>
ZPAM041E
ZPAM041E Unsupported ARCHIVE_ZIPFORMAT: +80+C+ Explanation: An unsupported archive format was detected for the reason shown:
Archive Manager 25
"Streamed/XTAPE sequential mode" The archive is being accessed in sequential mode (either on disk with ARCHIVE_FASTSEEK=N, or non-LBI tape) and the archive was found to be in Streamed format. An archive in this format may be accessed on disk if ARCHIVE_FASTSEEK is enabled, or with Enhanced Tape Processing (XTAPE) on an eligible device. Note: Streamed format makes use of trailers known as "Data Descriptors" to identify file data lengths instead of Local Header lengths. Sequential mode processing is dependent on the local header length information to index through the archive. System Response: Processing of the archive will be terminated. User Response: For "Streamed/XTAPE sequential mode": - If the archive resides on disk, ensure that ARCHIVE_FASTSEEK=Y is enabled and that the archive data set attributes are appropriate (RECFM=U or FB). - If the archive resides on a device supporting Enhanced Tape Processing, use a suitably licensed product to access the archive. - If the archive resides on a tape device and Enhanced Tape Processing is not available, use STAGE_TAPE_ON_DISK=Y with ARCHIVE_FASTSEEK=Y. Invoking module: <ACAMGR>
ZPAM045W
ZPAM045W The +8+C+ self-extraction program will not support ZIP64 Features. Explanation: Archive Manager process warning. ZIP64 features were activated while creating a a Self-extracting Archive. The self-extraction program listed does not support one of the possible extensions that ZIP64 provides: 'More than 65,535 files' 'File size > 4 gigabytes 'Archive size > 4 gigabytes System Response: The self-extracting Archive is created. RC=4 is set. The resulting Archive can be processed by PKZIP products that support ZIP64 features. Note: PKWARE Windows and UNIX products at the 4.5 release level or higher are required for ZIP64. User Response: If the use of the self-extraction program is required, keep the Archive contents within its processing limits.
Archive Manager 26
Invoking module: <ACAMGR>
ZPAM046E
ZPAM046E ZIP64 processing activation for: +40+C+ Explanation: Archive Manager process information. While writing the output Archive, it was detected that the ZIP64 feature of ZIP file format processing was required for one of the following reasons: 'More than 65,535 Files' 'File size > 4 gig' 'Archive size > 4 gig' Some target systems may not be able to handle the ZIP64 extensions. This may be due to the release of the UNZIP software or file system capabilities of the target system. System Response: Processing is halted and RC=8 is set in accordance with the SIGNAL_ZIP64 command setting or licensed features. User Response: If desired, the message severity and RC can be changed with the SIGNAL_ZIP64 command. Valid values are: 0, 4, 8. Note: SIGNAL_ZIP64 is only available for use with an appropriately licensed product (having ZIP64 feature code). Invoking module: <ACAMGR>
ZPAM046I
ZPAM046I ZIP64 processing activation for: +40+C+ Explanation: Archive Manager process information. While writing the output Archive, it was detected that the ZIP64 feature of ZIP file format processing was required for one of the following reasons: 'More than 65,535 Files' 'File size > 4 gig' 'Archive size > 4 gig' Some target systems may not be able to handle the ZIP64 extensions. This may be due to the release of the UNZIP software or file system capabilities of the target system. System Response: Processing continues. RC=0 is set in accordance with the SIGNAL_ZIP64 command setting. User Response: If desired, the message severity and RC can be changed with the SIGNAL_ZIP64 command. Valid values are: 0, 4, 8.
Archive Manager 27
Invoking module: <ACAMGR>
ZPAM046W
ZPAM046W ZIP64 processing activation for: +40+C+ Explanation: Archive Manager process information. While writing the output Archive, it was detected that the ZIP64 feature of ZIP file format processing was required for one of the following reasons: 'More than 65,535 Files' 'File size > 4 gig' 'Archive size > 4 gig' Some target systems may not be able to handle the ZIP64 extensions. This may be due to the release of the UNZIP software or file system capabilities of the target system. System Response: Processing continues. RC=4 is set in accordance with the SIGNAL_ZIP64 command setting. User Response: If desired, the message severity and RC can be changed with the SIGNAL_ZIP64 command. Valid values are: 0, 4, 8. Invoking module: <ACAMGR>
ZPAM050I
ZPAM050I GZIP Header: +8+H++8+H++4+H+ Explanation: This message is not currently in use. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM051I
ZPAM051I UTF-8 encoded archive filename(s) detected Explanation: This message reason may be issued during two phases of processing: 1. During input archive directory processing, this message reason will be issued at the first
Archive Manager 28
occurrence of a UTF-8 encoded filename. 2. During VIEWDETAIL reporting, the message will occur just prior to each ZPAM000I Filename message that is encoded with UTF8. The archive was found to have filenames encoded in UTF-8 format. Filename viewing, selection and transformation to an acceptable z/OS data set name may require special handling. Depending on the TRANSLATE_TABLE_FILEINFO table being used, some UTF-8 encoding bytes may cause unexpected results during VIEW, output display, file selection or filename transformation processing. The translation table value associated with TRANSLATE_TABLE_FILEINFO(EBC@UTF8) may be used to perform a simple byte-for-byte translation of the UTF-8 encoded filename into an EBCDIC display format. As distributed, this translate table uses the C'@' character to replace unrecognized characters. This permits VIEW and File Selection operations using typical keyboard characters. Note: If complex handling of input archive file names is required, FILENAME_API logic may be necessary. Note: The use of TRANSLATE_TABLE_FILEINFO also has an effect on -PASSWORD, archive file comment display, and ARCHIVE_COMMENT processing. System Response: None User Response: See detail information under Explanation. Invoking module: <ACAMGR>
ZPAM060T
ZPAM060T Work Directive: +80+C+ Explanation: An internal trace entry showing a work request being posted to the Archive Manager. System Response: None User Response: None Invoking module: <ACAMGR>
Archive Manager 29
ZPAM070T
ZPAM070T Processing FILE_SELECT_QUEUE {+52+C+} Explanation: An internal trace entry showing a dataset being processed. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM071T
ZPAM071T Processing OLD_FILE_QUEUE {+52+C+} Explanation: An internal trace entry showing a dataset being processed. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM080I
ZPAM080I Passed MVS Dataset Name has no matching -ZIPPED_DSN table entry Explanation: During ZIP processing, the filename conversion routine detected a mismatch in looking up filename comparisons via the -ZIPPED_DSN command. System Response: Continued processing will be attempted with the name information provided in the archive. Minimal name translation will be provided. User Response: Review the -ZIPPED_DSN (or equivalent alias command) to ensure that a match will occur with the ZIP files contained in the archive. Invoking module: <ACAMGR>
ZPAM081I
ZPAM081I Passed MVS DSN format is invalid: {+54+C+} Explanation: During ZIP processing, the filename conversion routine detected a miscoded DSNAME format.
Archive Manager 30
System Response: Continued processing will be attempted, although error conditions arising from a failed name translation may terminate processing for the associated file. See also: ZPAM081W User Response: Review the -ZIPPED_DSN (or equivalent alias command) to ensure that a match will occur with the ZIP files contained in the archive. Invoking module: <ACAMNIA>
ZPAM081W
ZPAM081W Problem in generating -EXTRACT name {+54+C+} Explanation: During UNZIP processing, a problem was detected in the routines that convert the ZIP filename to an name that is valid for the operating system. System Response: Processing of the current file is stopped. Processing of the entire run is governed by the value set in -ON_FILE_ACCESS_ERROR. User Response: Review the utility output messages for an indication of the filename translation problem. Invoking module: <ACAMGR>
ZPAM082W
ZPAM082W Invalid -ZIPPED_DSN statement given: {+80+C+} Explanation: During ZIP processing, the filename conversion routine detected a miscoded format in the command. System Response: Continued processing will be attempted, although error conditions arising from a failed name translation may terminate processing for the associated file. User Response: Review the -ZIPPED_DSN (or equivalent alias command) to ensure that it is correctly coded. Invoking module: <ACAMNIA>
ZPAM083I
ZPAM083I Passed -ZIPPED_DSN Archive Name invalid: {+80+C+} Explanation: During ZIP processing, the filename conversion routine
Archive Manager 31
detected a miscoded command. System Response: Continued processing will be attempted, although error conditions arising from a failed name translation may terminate processing for the associated file. User Response: Review the -ZIPPED_DSN (or equivalent alias command) to ensure that the Archive Name parameter of the command is of the proper format. Invoking module: <ACAMGR>
ZPAM084I
ZPAM084I Passed DSN PDS Name is greater then 8 characters: {+54+C+} Explanation: A partitioned member name must be less than 8 characters. System Response: None User Response: Correct the member name. Invoking module: <ACAMGR>
ZPAM085W
ZPAM085W EXTRACT bypassed. {+80+C+} Explanation: Under a variety of conditions, the processing of a file may be bypassed. System Response: None User Response: Examine the reason for the bypass. Invoking module: <ACAMGR>
ZPAM086W
ZPAM086W EXTRACT attempt of input archive to itself. Explanation: A request was made to perform -EXTRACT of a ZIP file that would result in the input Archive itself being overwritten. System Response: Bypass the requested file. User Response: Ensure that the target file is not the active input Archive.
Archive Manager 32
Invoking module: <ACAMGR>
ZPAM087C
ZPAM087C File not extracted: +54+C+ Explanation: This is the target filename that was bypassed. (see ZPAM087W) System Response: Info only. User Response: see ZPAM087W Invoking module: <ACAMGR>
ZPAM087W
ZPAM087W SAFETYEX filtered out EXTRACT {+80+C+} Explanation: The installation-tailorable -EXTRACT "safety" table has an entry that prevented the target file from being written to. System Response: Bypass the requested file. User Response: Contact the installation-support staff representative at your installation for information regarding the table entries. If the entry is desired to be removed, edit the SAFETYEX source and re-assemble the table into the product load library. Otherwise, EXTRACT the file to a temporary work location and copy the data to the target with another utility. Invoking module: <ACAMGR>
ZPAM088E
ZPAM088E TEMPFILE Allocation error FMCB: +8+H+ +54+C+ Explanation: Archive Manager processing error indication. Allocation of the TEMPFILE spill dataset failed. System Response: None User Response: Examine other SYSPRINT and JOBLOG messages for an indication of the reason for the failure. If necessary, use -TRACE_DYNALLOC(I) to obtain system IKJ (DYNALLOC) messages.
Archive Manager 33
Ensure that the TEMP_... specifications are correct for VOLUME, SPACE and SMS controls so that the file can be allocated. Note: If -MULTI_THREAD_LIMIT(1) is specified, then //TEMPFILE DD may be specified in the JCL to provide the spill storage space. DCB=(DSORG=PS,RECFM=U,LRECL=27998,BLKSIZE=27998) Unpredictable results will occur if -MULTI_THREAD_LIMIT is greater than 1 and //TEMPFILE is used. Invoking module: <ACAMGR>
ZPAM089E
ZPAM089E TEMPFILE Open/Read/Write error FMCB: +8+H+ +54+C+ Explanation: Archive Manager processing error indication. I/O to the TEMPFILE spill dataset failed. System Response: None User Response: Examine other SYSPRINT and JOBLOG messages for an indication of the reason for the failure. If necessary, use -TRACE_DYNALLOC(I) to obtain system IKJ (DYNALLOC) messages. Ensure that the TEMP_... specifications are correct for VOLUME, SPACE and SMS controls so that the file can be allocated. Note: If -MULTI_THREAD_LIMIT(1) is specified, then //TEMPFILE DD may be specified in the JCL to provide the spill storage space. DCB=(DSORG=PS,RECFM=U,LRECL=27998,BLKSIZE=27998) Unpredictable results will occur if -MULTI_THREAD_LIMIT is greater than 1 and //TEMPFILE is used. Invoking module: <ACAMGR>
ZPAM091W
ZPAM091W Nothing to do! File selection did not match any files in Archive. Explanation: No files were selected from the Archive for processing.
Archive Manager 34
1. This can be the result of the requested file selection specification not matching any of the ZIP files in the selected Archive. 2. Although files may have been matched in the Archive, they were filtered out or bypassed for other reasons. System Response: Processing terminates. User Response: 1. Check the SYSPRINT messages for reasons of files being bypassed. 2. Use -VIEW to ensure that the Archive has the expected files on it. 3. Check the spelling of the file selection statements. 4. Ensure that no extra non-command characters are in the command lines. (File names may be imbedded in the same line as commands, so imbedded comments are treated as data set names for selection). Invoking module: <ACAMGR>
ZPAM092E
ZPAM092E Nothing to do! Explanation: During ZIP processing, the requested action (along with files specified for processing) did not result in any files being identified for processing. 1. For a -ACTION(DELETE) the requested ZIP files were not found on the Archive. 2. For -ACTION(ADD/UPDATE/FRESHEN) the requested files were either not found, or were bypassed for processing. System Response: Processing terminates. The input Archive (if any) remains unchanged.
RC=8 is the default associated with this condition
User Response: 1. Check the SYSPRINT messages for reasons of files being bypassed. 2. Use -LOGGING_LEVEL(VERBOSE) to obtain ZPAM032I messages associated with files already in the the archive (which will not be re-added). 3. Use -VIEW to ensure that the Archive has the expected files on it (DELETE/FRESHEN/UPDATE). 4. Check the system catalog to ensure that the intended files are available. 5. Check the spelling of the file selection statements.
Archive Manager 35
6. -PKSUPPRC(ZPEX092E) may be coded to suppress the return code normally set by this condition. (The message will still be displayed). Invoking module: <ACAMGR>
ZPAM093W
ZPAM093W No files match selection. Initializing/Copying to ARCHIVE OUTFILE(ddname) Explanation: See also: ZPAM091W When a ZIP operation results in no files being selected for processing AND the input archive is specified via -ARCHIVE_INFILE, an implicit copy operation of the Archive will be performed. System Response: An attempt will be made to copy the input Archive to the output Archive. RC=4 is the default associated with this condition User Response: See also: ZPAM091W -PKSUPPRC(ZPAM093W) may be coded to suppress the return code normally set by this condition. (The message will still be displayed). Invoking module: <ACAMGR>
ZPAM094E
ZPAM094E ZIP64 Archive updating requires an appropriate license. Explanation: The ZIP Archive structure was found to require "ZIP64" Large File Support during a ZIP processing request. This function requires an additional license feature in order to update the archive. System Response: Processing is terminated. User Response: Contact PKWARE Customer Service for additional information regarding the Large File Support option. Invoking module: <ACAMGR>
ZPAM095E
ZPAM095E The ZIP64 Large File Support license is required to exceed
Archive Manager 36
65,535 files. Explanation: The ZIP Archive structure was found to require "ZIP64" Large File Support during a ZIP processing request. This function requires an additional license feature in order to update the archive. System Response: Processing continues with the files that fit into the Archive. Additional files are bypassed. User Response: Contact PKWARE Customer Service for additional information regarding the Large File Support option. By specifying -LOGGING_LEVEL(VERBOSE), additional informational messages will be issued to indicate which files are bypassed. Invoking module: <ACAMGR>
ZPAM096E
ZPAM096E The total amount of space required for extended attributes exceeds 64K. Explanation: The ZIP Archive directory entries maintain extended meta-data associated with each file for allocation, SecureZIP recipients and digital signatures. The total space required to hold the requested file information exceeded the allowable limit of 64K. System Response: Processing is terminated. User Response: If the related allocation information (e.g. space, DCB, RECFM) is not needed to restore the dataset to its original form on a z/OS system, then specify -SAVE_FILE_ATTRIBUTES=NONE. SecureZIP users may consider reducing the total number of RECIPIENTs being requested. (-VERBOSE during a ZIP run may assist with identifying all of the digital certificates found). Each additional recipient requires 20 bytes in the ZIP Archive extended area. SecureZIP users may consider reducing the number of digital signers being requested. A variable amount of signing information (hundreds of bytes) per signatory is required. Invoking module: <ACAMGR>
Archive Manager 37
ZPAM097I
ZPAM097I HFS/FIFO is about to be opened for processing: +54+C+ Explanation: During ZIP processing, the output archive was detected to be a FIFO Special File (named PIPE). The OPEN will only complete for this type of file when a partner process also opens the file for output. System Response: Attempt to OPEN the specified FIFO Special File. Note: The OPEN will WAIT indefinitely until a partner process opens the file for output, a system WAIT time limit is exceeded, or the process is cancelled. User Response: -Ensure that a partnering process performs an OPEN for OUTPUT to the named PIPE file. Invoking module: <ACAMGR>
ZPAM098E
ZPAM098E FIFO pipe defined for ARCHOUT has unacceptable File Format: +4+C+ Explanation: The FIFO Special file specified for use for archive output processing was found to have a File Format definition that can interfere with the archive stream. The File Format attribute must either be undeclared or 'binary'. System Response: The archive will not be opened. A minimum return code of 8 will be established for the ZIP run. User Response: Provide an acceptable named pipe for use. Invoking module: <ACCMGR>
ZPAM100I
ZPAM100I Archive Manager Task {+3+D+} TCB: +8+H+ Started. Explanation: This message will be issued upon the startup of the Archive Manager sub-task. System Response: None User Response: None
Archive Manager 38
Invoking module: <ACAMGR>
ZPAM101I
ZPAM101I Archive Manager Task {+3+D+} TCB: +8+H+ shutdown begun. Explanation: This message may be issued when the shutdown of the Archive Manager sub-task is begun. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM109I
ZPAM109I Archive Manager Task {+3+D+} TCB: +8+H+ shutdown complete. Explanation: This message may be issued when the Archive Manager shutdown process is complete. This will not occur until all compression and extraction sub-tasks have shutdown. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM111E
ZPAM111E ACTIVITY_LOG write error: +80+C+ Explanation: The ACTIVITY_LOG data set updates could not be completed. System Response: Return code=8 will be set. Processing continues. User Response: Verify that the ACTIVITY_LOG data set is defined, available for output and has sufficient space. Invoking module: <ACAMGR>
ZPAM140I
ZPAM140I FILES: ADDED EXCLUDED BYPASSED IN ERROR ZPAM140I 1 0 0 0
Archive Manager 39
Explanation: At the end of PKZIP and PKUNZIP processing, a set of summary lines will be issued regarding the run. Column headings will vary with the type of processing performed. The primary metrics shown in the column headings are associated with the ACTION request for the run. A complex ACTION such as UPDATE may result in primary processes of both ADDED and FRESHENED. In addition, secondary process headings such as COPIED may be required to reflect files copies from an input archive to the target output archive. The fields EXCLUDED, BYPASSED and ERROR provide feedback on files that were not processed. - Files are generally excluded based on -EXCLUDE command(s). - Files are generally bypassed when processing criteria are not met. Examples include: 1. A ZIP cataloged file search was requested that identified a partitioned data set, but SELECT_FROM_PDS(_NO_) was specified. 2. ZIP file selection requests that generate no matches. 3. HFS files determined to have insufficient PATHMODE permissions to be processed. - Files processing errors will typically be accompanied by explicit error messages. System Response: None User Response: None required. Reference the User's Guide for ACTION for a better understanding of ZIP and UNZIP processing. Invoking module: <ACAMGR>
ZPAM150E
ZPAM150E GZIP processing will not update an existing archive. Explanation: When -GZIP is specified, a new Archive must be created. An existing ZIP Archive cannot be updated with -GZIP. System Response: Processing terminates. User Response: Specify a new filename for the Archive, or update
Archive Manager 40
it with standard ZIP Archive format. Invoking module: <ACAMGR>
ZPAM151E
ZPAM151E Input Archive in GZIP format cannot be updated. Explanation: When -GZIP is specified, a new Archive must be created. Updating an existing GZIP Archive is not supported. System Response: None User Response: Specify a new filename for the Archive. Invoking module: <ACAMGR>
ZPAM152I
ZPAM152I Compressed size: X"+8+H++8+H+", Uncompressed size: X"+8+H++8+H+" Explanation: When a GZIP -ADD function is completed, this message is issued to display the compression results. Byte counts are displayed in Hexadecimal due to the large file sizes possible (> 4 Gig) System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM162I
ZPAM162I Self-extracting stub {+8+C+} inserted. +80+C+ Explanation: The -INCLUDE_SFX command was used to insert a Preamble in the Archive that is a self-extracting program for a target platform. +8+C+ - Designates the program module name. SF2AIX IBM AIX Version 4.0 and above SF2HP HP/UX Version 9.0 and above SF2LNX2I LINUX Kernel 2.x for Intel SF2SUN Sun Solaris 2.3 (SunOS 53) and above SF2WIN Microsoft Windows (95 and above) SF6AIX IBM AIX Version 4.3 and above
Archive Manager 41
SFXAIX is an alias for this value. SF6HP HP/UX Version 10.20 and above SFXHP is an alias for this value. SF6LNX2I LINUX running the 2.4 or later kernel on x86 with glibc-2.2.4 SFXLNX2I is an alias for this value. SF6SUN Sun Solaris 2.6 and above SFXSUN is an alias for this value. SFAWINC Microsoft Windows command line (Windows 98, ME, NT 4.0, 2000, XP) SFXWIN is an alias for this value. SFAWING Microsoft Windows GUI (same as SFAWINC) +80+C+ A self-extraction release level display. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM163E
ZPAM163E Self-extracting stub {+8+C+} could not be found. Explanation: The -INCLUDE_SFX command was used to insert a Preamble in the Archive as a self-extracting program, but the specified member could not be found in the load library. +8+C+ - Designates the load module name that is missing. Supplied self-extraction programs are: SF2AIX IBM AIX Version 4.0 and above SF2HP HP/UX Version 9.0 and above SF2LNX2I LINUX Kernel 2.x for Intel SF2SUN Sun Solaris 2.3 (SunOS 53) and above SF2WIN Microsoft Windows (95 and above) SF6AIX IBM AIX Version 4.3 and above SFXAIX is an alias for this value. SF6HP HP/UX Version 10.20 and above SFXHP is an alias for this value. SF6LNX2I LINUX running the 2.4 or later kernel on x86 with glibc-2.2.4 SFXLNX2I is an alias for this value. SF6SUN Sun Solaris 2.6 and above SFXSUN is an alias for this value. SFAWINC Microsoft Windows command line (Windows 98, ME, NT 4.0, 2000, XP) SFXWIN is an alias for this value. SFAWING Microsoft Windows GUI (same as SFAWINC) System Response: A return code = 8 is set for the execution. User Response: Correct the name. Invoking module: <ACAMGR>
Archive Manager 42
ZPAM180C
ZPAM180C {+110+C+} Explanation: Continuation for message ZPAM180I System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM180I
ZPAM180I UNIX Dataset Name has no matching -UNZIPPED_DSN entries. Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message can be issued if the Archive file being processed did not match any of the UNZIPPED_DSN specifications (if any). System Response: The system continues to translate the filename with according to rules that do not include UNZIPPED_DSN values. Note: This message is issued with -LOGGING_LEVEL=VERBOSE User Response: Ensure the desired name was built and provide an appropriate UNZIPPED_DSN command if necessary. Invoking module: <ACAMGR>
ZPAM181C
ZPAM181C {+110+C+} Explanation: Continuation of ZPAM181E System Response: see ZPAM181E User Response: see ZPAM181E Invoking module: <ACAMGR>
ZPAM181E
ZPAM181E ZIPPED_DSN(parm1,...) is invalid: {+82+C+}
Archive Manager 43
Explanation: During UNZIP processing the ZIP Filename was being translated to operating-system format and specifications from UNZIPPED_DSN were being examined to map a new name. An invalid first parameter was detected (shown +82+C+). System Response: Translation of the current file name stops. User Response: Correct the coding of the UNZIPPED_DSN command. Invoking module: <ACAMHLQ>
ZPAM182E
ZPAM182E Invalid -UNZIPPED_DSN statement given: {+80+C+} Explanation: A syntax error was detected in the specified command. System Response: Translation of the current file name stops. User Response: Correct the coding of the UNZIPPED_DSN command. Invoking module: <ACAMGR>
ZPAM183E
ZPAM183E -UNZIPPED_DSN(..., parm2) Name is invalid: {+54+C+} Explanation: During UNZIP processing the ZIP Filename was being translated to operating-system format and specifications from UNZIPPED_DSN were being examined to map a new name. An invalid second parameter was detected (shown +54+C+). System Response: Translation of the current file name stops. User Response: Correct the coding of the UNZIPPED_DSN command. Invoking module: <ACAMGR>
ZPAM184E
ZPAM184E Inconsistency in command requests Explanation: During UNZIP processing the ZIP Filename was being translated to operating-system format and specifications from UNZIPPED_DSN were being examined to map a new name. The utility detected that the requested UNZIPPED_DSN specification would result in an illogical DSNAME being
Archive Manager 44
built. For example, in z/OS a PDS name without a member would result. System Response: Translation of the current file name stops. User Response: Correct the coding of the UNZIPPED_DSN command. Invoking module: <ACAMGR>
ZPAM185E
ZPAM185E Low level UNIX qualifier too long for PDS member name Explanation: During UNZIP processing the ZIP Filename was being translated to operating-system format and specifications from UNZIPPED_DSN were being examined to map a new name. The utility detected that the requested UNZIPPED_DSN specification would result in an illogical DSNAME being built from the source file name. System Response: Translation of the current file name stops. User Response: Correct the coding of the UNZIPPED_DSN command. Invoking module: <ACAMGR>
ZPAM191I
ZPAM191I +121+C+ generic_message Explanation: This informational message may be issued to provide additional explanation regarding a condition. Note: This message is issued with -LOGGING_LEVEL=VERBOSE Sample Info: 'GENERATED MVS DSN LEVEL TOO LONG' for -UNZIPPED_DSN DIRECTING SORT SYSPRINT TO //PKSPRINT’ System Response: None. User Response: Check the return code and other messages surrounding this message. Invoking module: <ACAMGR>
ZPAM193W
ZPAM193W Archive alias(es) found and not restored. RC=+8+H+
Archive Manager 45
Explanation: During an UPDATE operation, when the archive was being renamed, the old archive is deleted. Any aliases defined for the old archive name are also deleted. System Response: None User Response: Use IDCAMS DEFINE ALIAS to restore each alias listed in the associated IDC0550I messages Invoking module: <ACCSAMSP>
ZPAM201E
ZPAM201E Load of Data Translate table {+8+C+} Failed. +8+H+-+8+H+ Explanation: The Load Module as indicated in +8+C+ could not be loaded. The -TRANSLATE_TABLE_DATA controls which load module is to be loaded. {+8+C+} is the module name. +8+H+-+8+H+ is the abend-reason for the failure. System Response: Processing terminates. User Response: Ensure that the correct translate table as specified by -TRANSLATE_TABLE_DATA is accessible (e.g. STEPLIB). Contact the person responsible for installation to ensure that the translate table is available on the system. Invoking module: <ACAMGR>
ZPAM202E
ZPAM202E Load of File Translate table {+8+C+} Failed. +8+H+-+8+H+ Explanation: The Load Module as indicated in +8+C+ could not be loaded. The -TRANSLATE_TABLE_FILEINFO controls which load module is to be loaded. This table is required to translate the ZIP Filename(s). {+8+C+} is the module name. +8+H+-+8+H+ is the abend-reason for the failure. System Response: Processing terminates. User Response: Ensure that the correct translate table as specified by -TRANSLATE_TABLE_FILEINFO is accessible (e.g. STEPLIB). Contact the person responsible for installation to ensure that the translate table is available on the system.
Archive Manager 46
Invoking module: <ACAMGR>
ZPAM203E
ZPAM203E Load of SAFETYEX module failed. +8+H+-+8+H+ Explanation: The Load Module table that protects system datasets could not be loaded. +8+H+-+8+H+ is the abend-reason for the failure. System Response: All files are assumed to be protected. User Response: The product administrator should ensure that the SAFETYEX module is linked into the execution library. Invoking module: <ACAMGR>
ZPAM204E
ZPAM204E Load of LATIN1 Translate table Failed. +8+H+-+8+H+ Explanation: The Load Module LATIN1 could not be loaded. This translate table is required for GZIP processing. +8+H+-+8+H+ is the abend-reason for the failure. System Response: Processing terminates. User Response: Ensure that LATIN1 is in the execution load library. Invoking module: <ACAMGR>
ZPAM212T
ZPAM212T ZIP header extended field {+4+H+} +40+C+ Explanation: This is a Technical Support tracing message that assists in debugging extended information about a ZIP file within an Archive. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM251I
ZPAM251I Bypassing File +54+C+ Explanation: Multiple files were requested that would resolve to the
Archive Manager 47
same Zip Filename. Only the first file will be placed into the Archive. All others will be ignored. Note: This message is issued with -LOGGING_LEVEL=VERBOSE System Response: Bypass the file and continue with additional requests. User Response: Ensure that when selecting multiple files (or members) and using the -NOPATH or -ZIPPED_DSN commands that duplications will not result in the output archive. Invoking module: <ACAMGR>
ZPAM252C
ZPAM252C ... +100+C+ Explanation: Continuation of ZPAM252I System Response: See related message. User Response: See related message. Invoking module: <ACAMGR>
ZPAM252I
ZPAM252I +9+C+ File +100+C+ Explanation: The file +100+C+ is not being processed for output. +9+C+ gives an indication of the reason why. "DELETED" - The file is being logically deleted. "DUPLICATE" - This is a duplicate filename with another file being processed. "NOPASSWRD" - An encrypted file was encountered, but no password was provided for the run. "NOENCRLIC" - Strong encryption was set for the specified file, but PKZIP is not licensed for Strong Encryption. "-EXCLUDED" - The filename matched one of the –EXCLUDE command specifications. The file is bypassed. "NOZ64LICA" - The -ADD request would result in more than 65,535 files in the Archive. This feature is separately licensed. Note: This message is issued with -LOGGING_LEVEL=VERBOSE (Some conditions may issue it unconditionally) System Response: The file is not processed to the output Archive. RC = 4 is set for NOPASSWRD RC = 8 is set for NOENCRLIC
Archive Manager 48
User Response: For "NOPASSWD", supply the correct -PASSWORD value. For "NOENCRLIC", contact PKWARE support for ENCRYPTION licensing options. Invoking module: <ACAMGR>
ZPAM253I
ZPAM253I +9+C+ File +54+C+ Explanation: ZIP processing has completed for the file specified by +54+C+. The type of action completed (e.g. ADD/FRESHEN) is shown in +9+C. "-EXCLUDED" A file match was encountered with the -EXCLUDE command(s) and the file was bypassed. See additional information messages relating to the ZIP completion (ZPAM254I and ZPAM255I). Note: This message is issued with -LOGGING_LEVEL=VERBOSE System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM254I
ZPAM254I as +100+C+ Explanation: ZIP processing has completed for the file specified in message ZPAM253I. This message reflects the name generated inside the archive. Note: The name shown here is an EBCDIC translation of the name actually stored in the Archive, since file information is stored in an ASCII format for cross-platform compatibility. (see -TRANSLATE_TABLE_FILEINFO command) System Response: None User Response: None Note: Commands that can affect the generation of this name include: PATH/NOPATH, ZIPPED_DSN, ZIPPED_DSN_SEPARATOR Invoking module: <ACAMGR>
Archive Manager 49
ZPAM255I
ZPAM255I (+8+C+ +2+C+%/+2+C+%) +90+C+ Explanation: ZIP processing has completed for the file specified in message ZPAM253I. This message reflects the type of compression used (STORED/DEFLATE) and the percentage of data compression achieved. "DATA SIZE" reflects the total data input size to the compression and encryption engines, including record control information. "ZIP SIZE" reflects the resulting size after compression and encryption. Two percentages of data compression are computed. The first number reflects the data compression engine results alone (total bytes input and output to the engine) The second number takes into account additional record control information added (e.g. CRLF for text or RDW for BINARY) or characters stripped (-STRIP_CHAR) before the data is fed to the compression engine. This number may more closely represent compression relative to the actual input file. The percentages only represent data compression levels. They do not take into account Archive space overhead associated with the file. For example: Local and Central directory, extended file attributes (-SAVE_FILE_ATTRIBUTES), filenames, and comments (-ARCHIVE_COMMENT). Note: When -SIMULATE is active, the compression engine is bypassed, and percentages will read "0%/ 0%". +90+C+ - A conditional display of the encryption method being used, along with the uncompressed and compressed size. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM256W
ZPAM256W +9+C+ request failed for +54+C+
Archive Manager 50
Explanation: ZIP processing failed for the file specified by +54+C+. The type of action completed (e.g. ADD/FRESHEN) is shown in +9+C. See additional messages relating to the ZIP process prior to ZPAM256W System Response: Processing continues depending on the values set for ON_FILE_ACCESS_ERROR and ON_FILE_IO_ERROR and the type of error encountered. User Response: See additional messages relating to the ZIP process prior to ZPAM256W to assist in resolving the problem. Set ON_FILE_ACCESS_ERROR and ON_FILE_IO_ERROR to TOLERATE or IGNORE if you desire other datasets to be processed. Invoking module: <ACAMGR>
ZPAM257E
ZPAM257E +9+C+ request failed for +54+C+ Explanation: ZIP processing failed for the file specified by +54+C+. The type of action attempted is shown in +9+C+. System Response: Processing is terminated if the archive build process cannot be completed. User Response: See additional messages relating to the ZIP process prior to ZPAM257E (or in the JOB log) to assist in determine the root cause of the problem. Invoking module: <ACAMGR>
ZPAM290I
ZPAM290I ARCHIVE Create/Update aborted due to errors. Explanation: Errors occurred during ZIP update processing and the command controls (such as ON_FILE_IO_ERROR) designated that processing should be terminated. System Response: Processing stops and the original Archive is retained. User Response: Review the preceding error messages to determine the problem condition. Invoking module: <ACAMGR>
Archive Manager 51
ZPAM291I
ZPAM291I ARCHIVE Rename {+54+C+} Explanation: When a ZIP process specifies a -ARCHIVE_DSN that already exists, a new temporary Archive is written until end of processing. When the temporary Archive has been built successfully, the old input Archive of the same name is deleted, and the new temporary Archive is renamed to the original DSNAME. +54+C+ represents the temporary name being renamed. See also: ZPAM292I System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM292I
ZPAM292I to {+54+C+} Explanation: When a ZIP process specifies a -ARCHIVE_DSN that already exists, a new temporary Archive is written until end of processing. When the temporary Archive has been built successfully, the old input Archive of the same name is deleted, and the new temporary Archive is renamed to the original DSNAME. +54+C+ represents the target (or original) DSN. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM293I
ZPAM293I Removing temporary ARCHIVE {+54+C+} Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued to indicate that ZIP processing is deleting the current output archive. +54+C+ represents the name of the archive data set (or HFS archive filename). This event normally occurs when the creation of a new
Archive Manager 52
archive cannot be completed. System Response: None User Response: See other related processing messages. Invoking module: <ACAMGR>
ZPAM301I
ZPAM301I File Type: +80+C+ Explanation: -VIEWDETAIL was requested. This detail line shows information regarding the File Type. MVS Data Sets: An indication of data set structure for the original file such as: NONVSAM (sequential) PDS or PDSE VSAM UNIX File Systems: UNIX files carry format information that is separate and unique from MVS Data Sets. Ref. "IBM z/OS UNIX System Services User's Guide" 'Regular_File' 'Directory' 'Symbolic_Link' 'Block_Special' 'Character_Special' 'FIFO/PIPE' 'Local_Socket' 'MVS_executable_EXEC' 'MVS_executable_DATA' 'MVS_executable_MEL ' 'Native_Object ' '*subtype N/A*' - Attributes were not saved in the archive directory entry for the file. For selected platforms, UNIX-type file system information will be displayed in braces. Note: SAVE_FILE_ATTRIBUTES=BOTH or CENTRAL must be specified during a ZIP run for TAG information to be retained in the archive directory entry. Sample: {- untagged T=off rwxrwxr-x 00000000} Fields: ....tag info..... permission tagstat. <...tag info ...> Tag information associated with the file. The format
Archive Manager 53
of this section will be similar to the USS "ls -T" or "chtag -p" commands. See "IBM z/OS UNIX System Services Command Reference" <permission> Permissions are shown in three groups of 3. The first group of 3 describes owner permissions; the second describes group permissions; the third describes "other" "world") permissions. Within each triplet, the permissions are positionally displayed in the following order. r Permission to read the file w Permission to write on the file x Permission to execute the file - No permission for this processing mode <tagstat> If present, the hexadecimal representation of platform-dependent External File Attributes will also be displayed as {nnnnnnnn}. For programming information, reference the "ZIP File Format Specification" APPNOTE document from PKWARE, as well as IBM z/OS programming structures st_tag and ft_ccsid. z/OS-HFS and OS/400-IFS define the low order 3 octets as the file permissions in the order of User/Group/Other. For example, if {000001FD}, then the breakdown of 01FD: = 0001 1111 1101 = xxx111 111 101 = 775 = rwx rwx r-x System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM302I
ZPAM302I File PDS Directory Blocks: +10+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the number of PDS directory blocks that had been allocated for the file (only if DSORG=PO). System Response: None User Response: None
Archive Manager 54
Invoking module: <ACAMVIEW>
ZPAM303I
ZPAM303I File Record Format: +40+C+ Explanation: -VIEWDETAIL was requested. When SAVE_FILE_ATTRIBUTES=CENTRAL is active for a ZIP run, format information associated with the file will be retained and available for reporting. For NONVSAM DSNAME data sets, the value reflects the DCB RECFM field (e.g. FB = Fixed Block) Record and Block size values correspond to system requirements for the RECFM of the data set. For Hierarchical File System PATH files, two values are presented with a blank separator. Example: ZPAM303I File Record Format: NL V The first is the HFS File Format definition from the input HFS PATH. The second value presents a pseudo-RECFM value to reflect the mode of processing used during ZIP. HFS File Format for regular files BINARY - Declared binary CR - Carriage Return CRLF - Carriage Return/Line Feed CRNL - Carriage Return/New Line LF - Line Feed LFCR - Line Feed/Carriage Return NL - New line See also DD PATH FILEDATA= keyword UNDECLARED - not set HFS pseudo-RECFM F - TEXT or SAVE_LRECL=Y ZIP processing was requested against an HFS file designated to use FILEDATA=TEXT (or implied File Format "nl") record mode processing. During ZIP processing, all records were found to be of equal length. The record size reflected in message ZPAM307I is the size of the data portion of records processed, not including record delimiter(s). V - TEXT or SAVE_LRECL=Y ZIP processing was requested against an HFS file designated to use FILEDATA=TEXT (or implied File Format "nl") record mode processing. During ZIP processing, records
Archive Manager 55
found to be of different lengths. The record size reflected in message ZPAM307I is the size of the data portion of records processed plus 4 bytes, not including record delimiter(s). The extra 4 bytes simulates an RDW length found in NONVSAM RECFM=V data sets to assist in the defintion of a maximum possible record size (constrained by RECFM=V limitations). U - The ZIP processing and HFS File Format options selected caused stream mode input operations to be performed against the HFS file. HFS pseudo LRECL (ZPAM307I) information: - 32760 typically reflects the default access method processing value, not a reported record size. HFS pseudo LRECL (ZPAM307I) Notes: - For pseudo RECFM=F and RECFM=V processing, the use of - The size reported in ZPAM307I is for reference purposes. It may represent a composite of multiple values, not only that of application data. - The record size may be influenced by the use of ZOSFILE_RECORD_DELIMITER, which would add a corresponding number of bytes to each record. - HFS File Format characters are not accounted for. - File format information is used to declare EBCDIC IBM-1047 record delimiters. System Response: None User Response: See also: IBM DFSMS Using Datasets "Record Format" See also: z/OS USS Command Reference for chtag Invoking module: <ACAMVIEW>
ZPAM304I
ZPAM304I File Allocation Type: +80+C+ Explanation: -VIEWDETAIL was requested. This detail line shows space allocation used for the file (e.g. CYK, TRK). System Response: None User Response: None Invoking module: <ACAMVIEW>
Archive Manager 56
ZPAM305I
ZPAM305I File Primary Space Allocated: +80+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the Primary Space for the File. System Response: None User Response: See also: ZPAM304I Invoking module: <ACAMVIEW>
ZPAM306I
ZPAM306I File Secondary Space Allocated: +80+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the Secondary Space for the File. System Response: None User Response: See also: ZPAM304I and ZPAM305I Invoking module: <ACAMVIEW>
ZPAM307I
ZPAM307I File Record Size: +80+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the LRECL of the file. See message ZPAM303I for detailed information relating to the value presented. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM308I
ZPAM308I File Block Size: +80+C+ Explanation: -VIEWDETAIL was requested. This detail line shows
Archive Manager 57
the BLKSIZE for the File. See message ZPAM303I for detailed information relating to the value presented. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM309C
ZPAM309C ... +100+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the volumes used for the File. Up to 31 volumes can be specified, so message ZPAM309C (continuation) may follow. System Response: None User Response: See also: ZPAM309I Invoking module: <ACAMGR>
ZPAM309I
ZPAM309I File Volume(s) Used: +80+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the volumes used for the file. Up to 31 volumes can be specified, so message ZPAM309C (continuation) may follow. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM310I
ZPAM310I File Creation Date: +12+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the date stored in the Archive for the related file. If available from the source-system at ZIP time, the Date/Time information is obtained from the
Archive Manager 58
associated file system. - NONVSAM DSN VTOC - PDS member ISPF Statistics - VSAM Catalog Cluster entry - z/OS UNIX directory entry (UTC) System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM311I
ZPAM311I File Referenced|Modified Date: +22+C+ Explanation: -VIEWDETAIL was requested. This detail line shows the date stored in the Archive for the related file. If available from the source-system at ZIP time, the Date/Time information is obtained from the associated file system. - NONVSAM DSN VTOC - PDS member ISPF Statistics - VSAM Catalog Cluster entry - z/OS UNIX directory entry (UTC) Note: This information may not have been available in the operating environment if SMS was not in control of the file at ZIP time. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM312C
ZPAM312C +80+C+ Explanation: When a PDS or PDSE member containing ISPF statistics is viewed, the directory information will be formatted for display. This message acts as a continuation of ZPAM312I. -SIZE -CREATED-- ------CHANGED------ ---ID-- -INIT VV.MM 18590 2004/07/16 2004/07/30 11:56:25 MAS 17918 01.10 System Response: None User Response: For additional information regarding PDS directory
Archive Manager 59
information, reference IBM DFSMS Using Datasets "Processing the PDS Directory". Invoking module: <ACAMGR>
ZPAM312I
ZPAM312I File PDS Extended Directory Information: +10+C+ Explanation: -VIEWDETAIL was requested. This detail line shows PDS directory information that is dependent on the type of PDS or PDSE being processed. The information displayed is in HEX dump format as presented by the operating system according to the specific member type. Different formats are used by IBM for ISPF statistics and Load modules. System Response: None User Response: For additional information regarding PDS directory information, reference IBM DFSMS Using Datasets "Processing the PDS Directory". Invoking module: <ACAMGR>
ZPAM313I
ZPAM313I PDS member TTRKZC: +12+C+ Explanation: -VIEWDETAIL was requested. This detail line shows PDS directory control information relating to the member. This information is used during EXTRACT processing to reconstruct member data. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM314I
ZPAM314I Member Alias: +8+C+ Explanation: -VIEWDETAIL was requested. This detail line shows that a member alias was defined for a PDS member and that
Archive Manager 60
-PROCESS_ALIAS(Y) was specified. When -PROCESS_ALIAS(Y) is specified during EXTRACT processing, the member ALIAS entries will be re-built for the associated member. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPAM316E
ZPAM316E Delete failed for: +44+C+ Explanation: An existing archive was to be replaced as a result of the functions requested. An old archive had to be deleted prior to renaming the temporary archive file. The old archive could not be deleted, usually because it was in use at the time of processing by another user. System Response: Messages ZPAM291T and ZPAM292T proceed this message and identify the dataset and members involved. User Response: Manually delete the old archive and rename the temporary archive to the name desired. Invoking module: <ACAMGR>
ZPAM317E
ZPAM317E Rename failed for: +44+C+ Explanation: An existing archive was to be replaced as a result of the functions requested. The old archive had been deleted and the temporary archive needed to be renamed. The old archive could not be renamed, usually because it was in use at the time of processing by another user. System Response: Messages ZPAM291T and ZPAM292T proceed this message and identify the dataset and members involved. User Response: Delete the old archive if it exists and rename the temporary archive to the name desired. Invoking module: <ACAMGR>
Archive Manager 61
ZPAM318I
ZPAM318I +8+D+ recipient(s) were designated: Explanation: The file had been encrypted using digital certificates with a designated list of target recipients. System Response: View processing will attempt to list the recipients. The digital certificates associated with the recipient(s) must be accessible from the system which is performing the view request. User Response: None. Invoking module: <ACAMVIEW>
ZPAM319I
ZPAM319I SMS Data|Management|Storage Class: +121+C+ Explanation: The saved attributes for the file being viewed indicate that the designated SMS class information was retained. System Response: During EXTRACT processing, UNZIP will attempt to use the designated SMS class in the allocation of a new dynamically allocated output data set. This information has no effect on existing output data sets, or output data sets allocated in JCL through -OUTFILE_DD. User Response: These values may be overridden during UNZIP processing by specifying the appropriate -OUTFILE_DATACLASS, -OUTFILE_MGMTCLASS or -OUTFILE_STORCLASS commands. Invoking module: <ACAMVIEW>
ZPAM320I
ZPAM320I +8+D+ recipient(s) were designated: Explanation: When certificate-based encryption has been used for files, VIEWDETAIL will provide a count of the number of RECIPIENT descriptors that were targeted. Each descriptor represents a unique Private-key digital certificate that can be used to decrypt the file. The number of individuals or organizations represented may be less than the number presented if different certificates were included for the same party. System Response: If SecureZIP is being used, an attempt will be made to
Archive Manager 62
display the individual parties represented by the certificate descriptors via a Local Certificate Store lookup. (Messages ZPAM321I, ZPAM322I, ZPAM323I & ZPAM324I) Individual recipient listings will not be made if the certificate descriptor cannot be resolved via the Local Certificate Store database. User Response: None required. Invoking module: <ACAMVIEW> SecureZIP
ZPAM321I
ZPAM321I Cert Name: +100+C+ Explanation: The file had been encrypted or signed using digital certificates. SecureZIP will attempt to look up the identity of each certificate and display pertinent information. Encryption Recipients: ---------------------- Each recipient is represented in the ZIP Archive by a digital hash of the associated digital certificate's Public Key. SecureZIP attempts to perform a lookup of the hash in the Local Certificate Store index. +100+C+ - The first 100 characters of the Common Name stored in the Local Certificate Store is displayed. Message ZPAM318I shows the total number of unique recipient certificates that were found. Signatory Certificates: ----------------------- Each signatory is represented in the ZIP Archive by a copy of the public-key certificate information. Certificate Authority chain certificate information associated with each signing certificate is also held within this store. +100+C+ - The first 100 characters of the Common Name stored in the Archive Certificate Store is displayed for each certificate. Message ZPAM329I shows the total number of unique signature certificates that were found. System Response: If the Local Certificate Store index for the Public Key hash cannot be opened, or if the hash value cannot be located, then this message will be bypassed.
Archive Manager 63
User Response: None required. Note that the Common Name may not be sufficient to clearly identify which digital certificate is associated with the recipient. Multiple certificates can be issued to an individual or organization with the same Common Name, but different email addresses, expiration dates, or purpose. The Public Key hash will be unique for each one. Invoking module: <ACAMVIEW> SecureZIP
ZPAM322I
ZPAM322I Public Key Hash: +40+C+ Explanation: The file had been encrypted using digital certificates with a designated list of target recipients. SecureZIP will attempt to look up the identity of each recipient and display pertinent information. Each recipient is represented in the ZIP Archive by a digital hash of the associated digital certificate's Public Key. SecureZIP attempts to perform a lookup of the hash in the Local Certificate Store index. If the lookup is successful, message ZPAM321I will be issued with the associated Common Name (as represented in the database). +40+C+ - The hexadecimal representation of the Public Key hash. This is the lookup key in the Local Certificate Store index. System Response: None User Response: None required. See also ZPAM321I Invoking module: <ACAMVIEW> SecureZIP
ZPAM323I
ZPAM323I Email: [email protected] Explanation: The file had been encrypted using digital certificates with a designated list of target recipients. SecureZIP will attempt to look up the identity of each recipient and display pertinent information. Each recipient is represented in the ZIP Archive by a digital hash of the associated digital certificate's
Archive Manager 64
Public Key. SecureZIP attempts to perform a lookup of the hash in the Local Certificate Store index. +100+C+ - The first 100 characters of the Email Address stored in the Local Certificate Store is displayed. System Response: If the Local Certificate Store index for the Public Key hash cannot be opened, or if the hash value cannot be located, then this message will be bypassed. User Response: None required. Note that the Email Address may not be sufficient to clearly identify which digital certificate is associated with the recipient. Multiple certificates can be issued to an individual or organization with the same Email Address, Common Name, expiration date, or purpose. The Public Key hash will be unique for each one. Invoking module: <ACAMVIEW> SecureZIP
ZPAM324I
ZPAM324I Cert: +100+C+ Explanation: - System Response: None User Response: None Invoking module: <ACAMVIEW> ZPAM324I Cert: +100+C+ Explanation: The file had been encrypted using digital certificates with a designated list of target recipients. SecureZIP will attempt to look up the identity of each recipient and display pertinent information. Each recipient is represented in the ZIP Archive by a digital hash of the associated digital certificate's Public Key. SecureZIP attempts to perform a lookup of the hash in the Local Certificate Store index. If the lookup is successful, message ZPAM324I will be issued with the associated location of the Certificate (as represented in the database). System Response: None User Response: None required. See also ZPAM321I
Archive Manager 65
Invoking module: <ACAMVIEW> SecureZIP
ZPAM325I
ZPAM325I Valid: +100+C+ Explanation: Digital certificates were used for encryption (-RECIPIENT used for encryption mode). SecureZIP will attempt to look up the identity of each recipient and display pertinent information. When digital certificates are issued by a Certificate Authority, an intended range of valid dates for use are frequently published within the certificate. This message reports the data range encoded within the specified certificate. System Response: None User Response: None required. See also ZPAM321I Invoking module: <ACAMGR> SecureZIP
ZPAM326I
ZPAM326I Issuer: +100+C+ Explanation: Digital certificates were used for encryption (-RECIPIENT used for encryption mode). SecureZIP will attempt to look up the identity of each recipient and display pertinent information. When digital certificates are issued by a Certificate Authority, a declaration of the issuing Certificate Authority is published within the certificate. This message reports the Issuer information encoded within the specified certificate. System Response: None User Response: None required. See also ZPAM321I Invoking module: <ACAMGR> SecureZIP
ZPAM329I
ZPAM329I +8+D+ Signature Certificates were saved in the archive:
Archive Manager 66
Explanation: When File or Archive signing is performed, a set of digital certificates are saved in the archive for use in authentication on a receiving system. Each descriptor represents a unique Private-key digital certificate that was used to sign files or the archive. System Response: If SecureZIP is being used, an attempt will be made to display the individual parties represented by the certificate descriptors. (Messages ZPAM321I, ZPAM322I, ZPAM323I & ZPAM324I) User Response: None required. Invoking module: <ACAMGR> SecureZIP
ZPAM331I
ZPAM331I VSAM Cluster +80+C+ Explanation: A display line from -VIEWDETAIL showing various VSAM CLUSTER-level file attributes. ZPAM331I VSAM Cluster Type: NUMBERED ZPAM331I VSAM Cluster Catalog Name: CATALOG.TSO.USERCAT ZPAM331I VSAM Cluster Erase: ERASE ZPAM331I VSAM Cluster Format: NUMBERED ZPAM331I VSAM Cluster Free CI Space %: 33 ZPAM331I VSAM Cluster Free CA Space %: 10 ZPAM331I VSAM Cluster Key Length: 4 ZPAM331I VSAM Cluster Key Position: 0 ZPAM331I VSAM Cluster Ordered: UNORDERED ZPAM331I VSAM Cluster Avg. Record Size: 80 ZPAM331I VSAM Cluster Max. Record Size: 100 ZPAM331I VSAM Cluster Recovery/Speed: RECOVERY ZPAM331I VSAM Cluster Spanned: NONSPANNED System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM332C
ZPAM332C ... +100+C+ Explanation: This line is a continuation of ZPAM332I when more than one line is needed (e.g. many volumes in a volume list). System Response: None User Response: None
Archive Manager 67
Invoking module: <ACAMVIEW>
ZPAM332I
ZPAM332I VSAM Data +80+C+ Explanation: A display line from -VIEWDETAIL showing various VSAM DATA-level file attributes. ZPAM332I VSAM Data Name: TEST.RRDS.DATA ZPAM332I VSAM Data Type Space: CYL ZPAM332I VSAM Data Primary Space: 5 ZPAM332I VSAM Data Secondary Space: 2 ZPAM332I VSAM Data Buffer Space: 24576 ZPAM332I VSAM Data CI Size: 8192 ZPAM332I VSAM Data Reuse: REUSE ZPAM332I VSAM Data Share Options: 1,3 System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM333I
ZPAM333I VSAM Index +80+C+ Explanation: A display line from -VIEWDETAIL showing various VSAM INDEX-level file attributes. ZPAM333I VSAM Index Name: MAS01.TEST.RRDS.INDEX ZPAM333I VSAM Index Type Space: TRK ZPAM333I VSAM Index Primary Space: 6 ZPAM333I VSAM Index Secondary Space: 3 ZPAM333I VSAM Index CI Size: 8192 ZPAM333I VSAM Index Reuse: REUSE ZPAM333I VSAM Index Share Options: 1,3 ZPAM333I VSAM Index Volume: TSO001 System Response: None User Response: None Invoking module: <ACAMGR>
Archive Manager 68
ZPAM390W
ZPAM390W No files matched View selection. Explanation: -VIEW was requested with a file selection list, but none of the files in the Archive match, OR, the Zip Archive is empty. System Response: None User Response: None Invoking module: <ACAMRPT>
ZPAM400E
ZPAM400E Error in VIEW processing +32+C+ Explanation: A -VIEW action was requested, but processing could not be completed for the request. This error is typically associated with an attempt to invoke system SORT for the report. If the SORTIN SORTOUT work files cannot be opened, or the system SORT fails for any reason, this message will be issue. System Response: The -VIEW report is not created. User Response: Look for other messages in the JOBLOG or SYSPRINT for a reason leading up to the failure. Invoking module: <ACAMRPT>
ZPAM560I
ZPAM560I ARCHIVE FASTSEEK processing is disabled. Explanation: The ARCHIVE_FASTSEEK feature was deactivated for this execution for one of the following reasons: 1. The Archive was not on Disk 2. The product is not licensed for Large File Support 3. The DCB attributes of the Archive do not allow for FASTSEEK processing. 1. RECFM=V or VB. 2. RECFM=U and LRECL<>0 and LRECL<>BLKSIZE 4. The data set organization of the Archive does not allow for FASTSEEK processing. System Response: None User Response: None
Archive Manager 69
Invoking module: <ACAMGR>
ZPAM561I
ZPAM561I ARCHIVE FASTSEEK processing is being bypassed (Code +2+H+) Explanation: When LOGGING_LEVEL=VERBOSE is specified, this informational message is issued. The code value specifies one of the reasons for the switch to sequential processing of the Archive. 1. ARCHIVE_FASTSEEK=N was specified 2. See ZPAM560I 8. An I/O error or other inability to successfully perform direct I/O processing occurred. System Response: Switch to sequential mode and continue processing. User Response: None Invoking module: <ACAMGR>
ZPAM562I
ZPAM562I XTAPE Processing: _status_ unit/read volume/read fileseq/read Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued for an opened ARCHIVE_ZIPFORMAT=XTAPE archive. unit/read - original archive write unit / current unit The unit device (e.g. 3590-1) that was used to write the archive, and the current unit being used to read it. Note: The reading unit must support the native write unit positioning information for enhanced tape processing to operate. The UNIT values need not match as long as the reading UNIT supports the original positioning information. volume/read - original archive volume / current volume The first volume(e.g. 3590-1) that was used when the archive was written, and the first archive volume being read. Note: The archive must be in the original position on the tape volume(s) for enhanced tape processing to operate. fileseq/read - original file number/ current file number The file sequence number of the first volume that was used to write the archive on, and the identified media information for the current archive being read. Note: The archive must be in the original media location for enhanced tape processing to
Archive Manager 70
successfully operate. status values MATCH The read characteristic matches the saved archive information. MISMATCH The input characteristic does not match the saved archive information. This may adversely affect processing. DIF-UNIT The input characteristic does not match the saved archive information. This is not likely to adversely affect processing. *STAGED* STAGE_TAPE_ON_DISK is active. Enhanced tape operations are suspended to permit disk processing of the staged archive. System Response: Processing dependent (see explanations above) User Response Processing dependent (see explanations above) Invoking module: <ACAMGR>
ZPAM700I
ZPAM700I Archive was digitally signed by +30+C+ Explanation: A Digital signature has been detected for the Archive. When -AUTHCHK(ARCHIVE) processing is requested, the Digital Signature is parsed and the signing party is displayed. Otherwise, {UNDETERMINED SIGNER} is displayed. The appearance of a name in this message does not imply a successful authentication of the digital signature. Refer to message ZPEN035I. System Response: None User Response: None required When running under a PartnerLink license, a valid SPONSOR_AUTH specification for the associated signatory must be provided for the signing party to be identified and displayed. A configured list of all installed Sponsor Packages may be provided to determine the source of an archive. Invoking module: <ACAMGR>
Archive Manager 71
ZPAM701E
ZPAM701E Archive has been digitally signed and cannot be updated Explanation: The ARCHIVE contains a digital signature and cannot be updated in place. System Response: None User Response: ARCHIVE can be updated using the ARCHINDD and ARCHOUTDD parameters to create a new archive copying the old archive into the new while performing the update. However the digital signature will not be propagated. Invoking module: <ACAMGR>
ZPAM702I
ZPAM702I File was digitally signed by +60+C+ Explanation: A Digital signature has been detected for the file. When processing options allow, the Digital Signature is parsed and the signing party is displayed. Otherwise, {UNDETERMINED SIGNER} is displayed.
If available, signatory certificate information is shown with various fields separated by semi-colons ";" Fields may include: Common name Email address Certificate Serial Number
System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM706W
ZPAM706W Input archive was digitally signed; removed from output archive. Explanation: When creating an updated Archive from a previously signed Archive (using ARCHIVE_OUTFILE), the digital signature in the input archive is no longer valid and will be removed. System Response: None User Response: None required.
Archive Manager 72
Invoking module: <ACAMGR>
ZPAM710I
ZPAM710I Archive Directory is Compressed +2+C+%s Explanation: The Archive Central Directory was compressed to save space. This feature exists with ZIP File Format Specification 6.2 (which is supported by PKZIP and SecureZIP release 8.0 and above). System Response: None User Response: None required. Invoking module: <ACAMGR>
ZPAM711I
ZPAM711I Archive Directory is Encrypted +40+C+ Explanation: The Archive Central Directory was encrypted with the FILENAME_ENCRYPTION feature. The Encryption Algorithm and Mode are displayed as part of the message. Licensing for the above is as follows for releases 8.0 and higher: - Decrypt Mode of Password is supported by any version of PKZIP or SecureZIP - Creation of Encrypt Mode Password Only is supported by SecureZIP or PKZIP with the Enhanced Encrypt/Decrypt Module - Encryption Mode of Recipients is supported only by SecureZIP System Response: None User Response: None required. Invoking module: <ACAMGR>
ZPAM712I
ZPAM712I Archive Directory Encryption Recipients Explanation: SecureZIP Filename Encryption was used to create the input archive with specified recipients. Digital
Archive Manager 73
certificates are used to identify each recipient. The following messages report the intended recipients for the archive. System Response: None User Response: None required Invoking module: <ACAMGR> SecureZIP
ZPAM713I
ZPAM713I Archive Directory requires a product supporting +20+C+ Explanation: The Archive Central Directory has extended features requiring advanced processing capability. The value shown in +20+C+ indicates the .ZIP Format Specification level required to process the archive. This value does not represent the Product Release number. See the User's Guide for more information regarding the .ZIP File Format Specification and the corresponding product release numbers required to support individual features. System Response: None User Response: None required. Invoking module: <ACAMGR>
ZPAM800I
ZPAM800I +80+C+ Explanation: "Archive in GZIP Format" is displayed with this message during a -VIEW request and a GZIP header was detected for the Archive. System Response: None User Response: None Invoking module: <ACAMVIEW>
Archive Manager 74
ZPAM900T
ZPAM900T +121+C+ Explanation: This is a generalized trace message for the Archive Manager component of PKZIP/PKUNZIP and will contain program-dependent information for PKWARE Product Support. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAM901E
ZPAM901E +121+C+ Explanation: This is a generalized error message for the Archive Manager component of PKZIP/PKUNZIP and will contain program-dependent information for PKWARE Product Support. "COPY EXIT (BAD HEADER)" While copying files from the input archive to the output archive, unexpected data was found in the input archive. This condition may arise if the user has inappropriately used the same file for both the ARCHINDD and ARCHOUTDD archive designations, such that the input archive file was overlaid by output archive information before the remainder of the input archive could be processed. System Response: Failure of the active process User Response: Corrective action is likely to be required. Review the job setup associated with the error condition. Invoking module: <ACAMGR>
ZPAM910I
ZPAM910I Non-Standard Archive detected. Attempting to fix offsets. Explanation: While processing the input Archive, the Archive Manager determined that directory offsets were not consistent with ZIP Archive standards. This can occur if non-ZIP data had been prefixed to an Archive (including a self-extraction program preamble). System Response: Processing continues and the Archive Manager will attempt to adjust for the invalid offsets found in the directory.
Archive Manager 75
User Response: Determine whether the specified archive should be valid. Note: All standard Archives begin with either x'504B0304' or x'504B0506'. Invoking module: <ACAMGR>
ZPAM911E
ZPAM911E The designated input Archive is not a valid ZIP Archive. Explanation: The Archive Manager opened the specified input Archive file, but determined that the file is not an Archive. - A standard ZIP Archive will always start with X'504B' - A GZIP Archive will start with X'1F8B' - When a signature authentication check fails, the archive will be treated as "not valid" System Response: Processing is terminated. User Response: Determine whether the specified archive should be valid. Invoking module: <ACAMGR>
ZPAM912E
ZPAM912E An error occurred attempting to locate the beginning of the Central Directory. Explanation: The Archive Manager opened the specified input Archive file, but was unable to locate the Central Directory at the end of the file. This can occur if the Archive has been truncated during a data transmission from one system to another. Note: The Central Directory begins with either X'504B0102' or X'504B0506' (when the Archive is empty). System Response: Processing is terminated. User Response: Determine whether the file has been truncated. Invoking module: <ACAMGR>
Archive Manager 76
ZPAM913E
ZPAM913E An error occurred attempting to process the Central Directory. Explanation: The Archive Manager opened the specified input Archive file and located the Central Directory, but could not process it to completion. This can occur if the Archive has been truncated during a data transmission from one system to another. Note: The Central Directory begins with either X'504B0102' or X'504B0506' (when the Archive is empty). This message may also be issued if other special features for the Central Directory are in effect. This may include FILENAME_ENCRYPTION or Authentication. System Response: Processing is terminated. User Response: Review the output for other related messages. Determine whether the file has been truncated. Invoking module: <ACAMGR>
ZPAM914E
ZPAM914E An error occurred attempting to locate a Local Directory entry. Explanation: The Archive Manager was reading through the input Archive by using offsets and lengths according to other directory entries. A Local Directory Header was expected at a specific offset in the file, but the eye-catcher was not present there. Note: The Local Directory begins with X'504B0304' System Response: Processing is terminated. User Response: Determine whether the file has been truncated. Invoking module: <ACAMGR>
ZPAM915E
ZPAM915E Central Directory signature mismatch. Explanation: The Archive Manager opened the specified input Archive file, located the Central Directory and began reading through the entries. Each entry should begin with
Archive Manager 77
the documented eye-catcher, but the data did not match. This can occur if the Archive has been truncated during a data transmission from one system to another. Note: The Central Directory begins with either X'504B0102' or X'504B0506' (when the Archive is empty). System Response: Processing is terminated. User Response: Determine whether the file has been truncated or appended. Invoking module: <ACAMGR>
ZPAM916E
ZPAM916E Archive build failed: +80+C+ Explanation: A problem was encountered while writing the output archive in the processing phase shown. 'Central Directory Construction Error' Although file processing appeared to be successful, the creation of the archive Central Directory could not be completed. System Response: Processing is terminated. User Response: Review additional messages for an apparent reason. Invoking module: <ACAMGR>
ZPAM931W
ZPAM931W An invalid extended attribute was detected. Some attributes are ignored. Explanation: While processing the Archive Directory information, descriptive file information (e.g. space allocation) was being parsed. (ZIP had been run with -SAVE_FILE_ATTRIBUTES(Y)). During EXTRACT processing, this information can be used (-USE_FILE_ATTRIBUTES(Y)) to re-allocate the file. One or more extended attributes were not recognized, or of an unsupported format to be used. System Response: The reading of extended file attributes for the specified file may be incomplete. Processing continues with known values. User Response: If an EXTRACT was performed and PKUNZIP dynamically
Archive Manager 78
allocated the file for output, verify that the file attributes are acceptable. If not, re-run with OUTFILE_xxx commands to set the attributes correctly, or pre-allocate the file. Run -VIEWDETAILS to assess which attributes are correct or missing. Invoking module: <ACAMGR>
ZPAM950E
ZPAM950E Insufficient Virtual Storage to handle the file request. Explanation: Archive Manager processing error detected. While processing the Archive, insufficient Virtual Storage was available to hold work areas. System Response: Processing is terminated. User Response: Specify a larger REGION/PARTITION size. - OR - Use -MEMORY_MODEL=MEDIUM Invoking module: <ACAMGR>
ZPAM999E
ZPAM999E INVALID INTERNAL DIRECTIVE: +80+C+ Explanation: An internal program error was detected. System Response: Processing is terminated. User Response: Please contact the Product Services Division at 1-937-847-2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACAMGR>
API 79
ZPAP – Application Programming Interface Messages
ZPAP001E
ZPAP001E Anchor Getmain Failed - API Disabled Explanation: The API Interface Failed to Initialize System Response: User API processing is disabled User Response: Increase the region size and rerun. If you continue to receive this error message contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
ZPAP002E
ZPAP002E API LE Failed to Load Explanation: The Language Environment would not load. System Response: User API processing is disabled User Response: The Language Environment did not start. If you continue to receive this error message contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
ZPAP003E
ZPAP003E API LE Failed to Initialize Explanation: The Language Environment would not initialize. System Response: User API processing is disabled User Response: The Language Environment did not start. If you continue
API 80
to receive this error message contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
ZPAP004E
ZPAP004E API IRXEXEC FAILED RC=+8+H+ +8+D+(DEC) Explanation: The Language Environment would not run the user API. System Response: User API processing is disabled User Response: The Language Environment returned an unacceptable condition code attempting to load the user API. If you continue to receive this error message contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
ZPAP005E
ZPAP005E Filename Module +8+C+ Failed to Load Explanation: The User API module could not be found. System Response: Filename User API processing is disabled User Response: Place the User API module in a STEPLIB, JOBLIB, or system linklist library and restart. If you continue to receive this error message contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
API 81
ZPAP006E
ZPAP006E Data Transformation Module +8+C+ Failed to Load Explanation: The User API module could not be found. System Response: Data Transformation User API processing is disabled User Response: Place the User API module in a STEPLIB, JOBLIB, or system linklist library and restart. If you continue to receive this error message contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
ZPAP007E
ZPAP007E API LE Failed to Terminate Explanation: The Language Environment would not terminate. System Response: User API processing is disabled User Response: The Language Environment did not end. If you continue to receive this error message contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
ZPAP008E
ZPAP008E Filename Module +8+C+ is an unsupported language +5+C+ Explanation: The User API module language specified is not supported. System Response: Processing is terminated. User Response: Specify the correct language and rerun. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support.
API 82
Invoking module: <ACTMAPI>
ZPAP009E
ZPAP009E Data Transformation Module +8+C+ is an unsupported language +5+C+ Explanation: The User API module language specified is not supported. System Response: Processing is terminated. User Response: Specify the correct language and rerun. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMAPI>
ZPAP010I
ZPAP010I Filename Module +8+C+ Loaded Explanation: The name of the user API Filename module. System Response: Informational message issued once per run User Response: none Invoking module: <ACTMAPI>
ZPAP011I
ZPAP011I Data Transformation Module +8+C+ Loaded Explanation: The name of the user API Data Transformation module. System Response: Informational message issued once per run User Response: none Invoking module: <ACTMAPI>
API 83
ZPAP020E
ZPAP020E Filename Module +8+C+ Abort RC=+8+H+ +8+D+(DEC) Explanation: The user Filename API issued a return code > 4 System Response: Discontinue processing and end the run User Response: none Invoking module: <ACTMAPI>
ZPAP021E
ZPAP021E Data Transformation Module +8+C+ Abort RC=+8+H+ +8+D+(DEC) Explanation: The user Data Transformation API issued a return code > 4 System Response: Discontinue processing and end the run User Response: none Invoking module: <ACTMAPI>
ZPAP050E
ZPAP050E Filename Module +8+C+ ABEND at Address=+8+H+ Cond Code=+2+H+ Explanation: The user Filename API has abended with a program exception. at Address is the next instruction address and Cond Code is the condition code for the program exception For Example: ZPAP050E Filename Module FNEXIT ABEND at Address=80052B70 Cond Code=01 System Response: If the -FILENAME_API_ERROR indicator is IGNORE processing continues. If the indicator is ABEND a SYSABEND dump will be produced. If the indicator is STOPRUN processing will cease. User Response: Correct the abending code and rerun. Invoking module: <ACTMAPI>
API 84
ZPAP051E
ZPAP051E DataTransformationModule +8+C+ ABEND at Address=+8+H+ Cond Code=+2+H+ Explanation: The user DataTran API has abended with a program exception. at Address is the next instruction address and Cond Code is the condition code for the program exception For Example: ZPAP051E DataTransformationModule DTEXIT ABEND at Address=80052B70 Cond Code=01 System Response: If the -Data Transformation_API_ERROR indicator is IGNORE processing continues If the indicator is ABEND a SYSABEND dump will be produced. If the indicator is STOPRUN processing will cease. User Response: Correct the abending code and rerun. Invoking module: <ACTMAPI>
ZPAP090E
ZPAP090E Registers at entry to Abend Explanation: The user API has abended with a program exception. System Response: The next four messages will contain the register at entry to abend. User Response: Correct the abending code and rerun. Invoking module: <ACTMAPI>
ZPAP091E
ZPAP091E +8+C+ +8+H+ +8+H+ +8+H+ +8+H+ Explanation: The user API has abended with a program exception. System Response: The next four messages will contain the register at entry to abend.
API 85
User Response: Correct the abending code and rerun. Invoking module: <ACTMAPI>
ZPAP100I
ZPAP100I <+8+C+> Filename Manipulation Result: RC=+8+D+ Name=+54+C+ Explanation: This message is displayed immediately after a call to the file name user API when any API trace indicators are set on. The message contains the name of the API, the return code of the call and the results of the file name manipulation. System Response: None User Response: None Invoking module: <ACAMGR>
ZPAP101E
ZPAP101E <+8+C+> Filename Manipulation Length > 54 (+8+D+) Name=+60+C+ Explanation: The Filename Manipulation user API returned a file name greater than 54 Characters. The file is bypassed. The message contains the name of the user API, new file name length and the new file name. System Response: The file is bypassed from extraction. User Response: Review and correct file user API code. Invoking module: <ACAMGR>
ZPAP102E
ZPAP102E <+8+C+> Filename Manipulation Length = 0 Name=+60+C+ Explanation: The Filename Manipulation user API returned a file name of zero length. The message contains the name of the user API and the name of the new file name. System Response: The file is bypassed from extraction.
API 86
User Response: Review and correct file user API code. Invoking module: <ACAMGR>
ZPAP200I
ZPAP200I +121+C+ Explanation: This message is informational. Reasons for message invocation: DATA_TRANS_API_TRACE is set to '3' or greater. Contents: Transformed record. System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPAP201E
ZPAP201E Record Transformation Failure: RC=+8+H+ Explanation: The Record Transformation user API or the API interface returned code greater than 4. System Response: The ZIP run is terminated, Archive is not created or updated. User Response: Please review previous messages. Invoking module: <ACCOMAIN>
ZPAP202E
ZPAP202E Record Transformation Invalid Record Length=+8+D+ Explanation: The Record Transformation user API returned an invalid record length. The record length is either zero or greater than 32760. System Response: The ZIP run is terminated, Archive is not created or updated. User Response: Review and correct Data user API code. Invoking module: <ACCOMAIN>
API 87
ZPAP203E
ZPAP203E API Control: Call error - RC=+8+H+ Explanation: The API service routine detected an invalid return condition. For example, an undefined return code was returned for the type of API User Routine that was invoked. System Response: An error condition will be percolated to the ZIP/UNZIP processing phase currently in control. Processing of the file will be terminated. User Response: Review and correct the User Routine. Invoking module: <ACCOMAIN>
ZPAP204W
ZPAP204W API Control: User exit signal received to skip file {+12+C+} Explanation: The API service routine received an indication from the User Routine that the file is to be skipped. RC=6 was retuned by the User Routine during the processing phase indicated by {+12+C+}. System Response: Bypass the inclusion of the file in processing. User Response: None Invoking module: <ACTMAPI>
ZPAP210I
ZPAP210I User Exit Feedback {+8+H+} for +54+C+ Explanation: This message is informational and is controlled by the installation-supplied DATA_TRANS_API User Routine. The User Routine may choose to place a non-zero value into the APIP2_USER_FDBK field, which triggers this message to be issued on its behalf upon return. For additional information regarding USER feedback areas: INSTLIB(COBMAPIU) - COBOL copybook INSTLIB(DCTMAPIU) - Assembler DSECT INSTLIB2(DCTMAPIU) - C Structure System Response: None
API 88
User Response: None Invoking module: <ACTMAPI>
ZPAP211I
ZPAP211I +121+C+ Explanation: This message is informational and is controlled by the installation-supplied DATA_TRANS_API User Routine. The User Routine may choose to place message text into the APIP2_USER_MESSAGE field, which triggers this message to be issued on its behalf upon return. For additional information regarding USER feedback areas: INSTLIB(COBMAPIU) - COBOL copybook INSTLIB(DCTMAPIU) - Assembler DSECT INSTLIB2(DCTMAPIU) - C Structure System Response: None User Response: None Invoking module: <ACTMAPI>
ZPAP290E
ZPAP290E +121+C+ Explanation: Review message text. System Response: The ZIP run is terminated, Archive is not created or updated. User Response: Review and correct Data user API code. Invoking module: <ACCOMAIN>
ZPAP406E
ZPAP406E PARM 2 VL BIT OFF Explanation: The parameter list passed to a PKZIP entry point is invalid. This message is issued as a WTO, with ROUTCDE=11 System Response: The ZIP module returns RC=32.
API 89
User Response: Change the calling program code to insure that: 1. if a BATCH call, the high-order bit of the first parameter list address is set to 1. 2. if an API call, the high-order bit of the second parameter list address is set to 1. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go online at http://www.pkware.com/business_and_developers/support Invoking module: <ACZMAIN>
ZPAP407E
ZPAP407E APIB ADDR INVALID Explanation: The parameter list passed to a PKZIP entry point is invalid. The address of the APIB interface block points to unaccessable storage. This message is issued as a WTO, with ROUTCDE=11 System Response: The ZIP module returns RC=32. User Response: Change the calling program code to insure that a valid address is passed. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go online at http://www.pkware.com/business_and_developers/support Invoking module: <ACZMAIN>
ZPAP408E
ZPAP408E APIB STG PROTECTED Explanation: The parameter list passed to a PKZIP entry point is invalid. The address of the APIB interface block points to write-protected storage. This message is issued as a WTO, with ROUTCDE=11 System Response: The ZIP module returns RC=32. User Response: Change the calling program code to insure that a valid address is passed. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go online at http://www.pkware.com/business_and_developers/support Invoking module: <ACZMAIN>
API 90
ZPAP409E
ZPAP409E APIB EYECATCHER NOT PKB Explanation: The parameter list passed to a PKZIP entry point is invalid. The second parameter either points to the wrong storage area, or the API interface control was not initialized. This message is issued as a WTO, with ROUTCDE=11 System Response: The ZIP module returns RC=32. User Response: Change the calling program code to insure that the address of an initialized API control interface is passed as the second parameter. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go online at http://www.pkware.com/business_and_developers/support Invoking module: <ACZMAIN>
ZPAP498E
ZPAP498E APIB Caller TERMINATE received before FINALIZE-REQUEST. Explanation: During an API call sequence, before a FINALIZE-REQUEST was completed, the calling application requested a TERMINATE action. System Response: ZIP processing is terminated, and APIB_RTRN_PK_RC is set to a minimum of 8. If an archive was being created or updated to a file or data set, an attempt will be made to delete it. User Response: Examine the call sequence, as well as the ZIP message output to determine the cause leading up to this condition to determine whether the application caller intended to TERMINATE without a FINALIZE-REQUEST. Invoking module: <AMAPIB>
ZPAP499E
ZPAP499E APIB Unexpected TERMINATE encountered Explanation: During an API call sequence, before a FINALIZE-REQUEST was completed, either the calling application attempted
API 91
a TERMINATE action, or ZIP processing was prematurely ended due to a processing error. System Response: ZIP processing is terminated, and APIB_RTRN_PK_RC is set to a minimum of 8. If an archive was being created or updated to a file or data set, an attempt will be made to delete it. User Response: Examine the call sequence, as well as the ZIP message output to determine the cause leading up to this error. Invoking module: <AMAPIB>
ZPAP900I
ZPAP900I NO API REQUIRED Explanation: When LOGGING_LEVEL=VERBOSE is specified, this message will be issued to indicate that no FILENAME_API or DATA_TRANS_API functions were requested. System Response: None User Response: None Invoking module: <ACTMAPI>
Certificate Administration 92
ZPCA - Certificate Administration Messages
See also “PKCS - Certificate Store Utility Messages” in Chapter 4.
ZPCA801E
ZPCA801E Invalid parameter value for Preferred Certificate Store. Value = %s. Explanation: The PKCAADMN utility expects one of the following value for the Preferred Certificate Store parameter: CA - Certificate Authority Store RT - Root Store CR - Certificate Revocation List Store BG - Best Guess (PKCAADMN attempts to select the store based on the input certificate constraints.) %s Shows the value that the PKCAADMN utility received for the Preferred Certificate Store parameter. System Response: The PKCAADMN utility will be unable to proceed without a properly specified Preferred Certificate Store parameter. Program execution will terminate. User Response: Determine the origin of the incorrect value and change to one of the correct input values listed above. Invoking module: <PKCAADMN>
ZPCA802E
ZPCA802E Invalid parameter value for Action. Value = %s. Explanation: The PKCAADMN utility expects one of the following value for the Action parameter: A - Add certificate to a store D - Delete a certificate from a store V - Verify the integrity of a store S - Short list of a store's contents L - Long list of a store's contents I - Initialize a certificate store B - Browse a certificate file's contents %s Shows the value that the PKCAADMN utility received for the Action parameter. System Response: The PKCAADMN utility will be unable to proceed without a properly specified Action parameter. Program execution will terminate.
Certificate Administration 93
User Response: Determine the origin of the incorrect value and change to one of the correct input values listed above. Invoking module: <PKCAADMN>
ZPCA803E
ZPCA803E Invalid parameter value for Certificate File Type. Value = %s. Explanation: The PKCAADMN utility expects one of the following value for the Certificate File Type parameter: CER - .cer Certificate File (also called a PEM file) P7B - PKCS #7 Certificate File CRL - .crl Certificate Revocation List File %s Shows the value that the PKCAADMN utility received for the Certificate File Type parameter. System Response: The PKCAADMN utility will be unable to proceed without a properly specified Certificate File Type parameter. Program execution will terminate. User Response: Determine the origin of the incorrect value and change to one of the correct input values listed above. Invoking module: <PKCAADMN>
ZPCA804E
ZPCA804E Certificate service module failed to initialize. <SecureZIP Only> Explanation: The PKCAADMN relies on the certificate service modules to
process certificate files and stores. Without the proper execution of these modules, the PKCAADMN cannot function. If initialization cannot be completed, the PKCAADMN program cannot continue. System Response: The PKCAADMN utility will be unable to proceed without proper initialization. Program execution will terminate. User Response: Contact PKWARE Technical Support to determine the origin of the failure. Invoking module: <PKCAADMN>
Certificate Administration 94
ZPCA805E
ZPCA805E Open certificate store failed. Store '%s1' type incompatible with certificate '%s2' type. Explanation: When performing an add to store operation, the PKCAADMN utility requires that the type of the certificate match the type of the store that the certificate is being added to. In the case of the CA store, this means the certificate must have the certificate authority constraint.* For the root store, the certificate must be self signed. %s1 Shows the value that the PKCAADMN utility received for the certificate store. %s2 Shows the value that the PKCAADMN utility received the certificate file. System Response: The PKCAADMN utility will be unable to proceed with the add command without the certificate store type and the certificate file type matching. Program execution will terminate. User Response: Determine the origin of the type mismatch and change the certificate store and/or certificate file values so that the certificate and store types match and reattempt the add command. Invoking module: <PKCAADMN>
ZPCA806E
ZPCA806E The certificate store '%s' was not opened. Explanation: While attempting to open the certificate store file, the PKCAADMN program was unable to open the file. %s Shows the value that the PKCAADMN utility received for the certificate store. System Response: The PKCAADMN utility will be unable to proceed with the command without a valid certificate store being specified. Program execution will terminate. User Response: Verify that the correct file name was passed to PKCAADMN for the certificate store name and re-attempt the command. Invoking module: <PKCAADMN>
Certificate Administration 95
ZPCA807E
ZPCA807E Memory allocation error. Explanation: The PKCAADMN program was unable to allocate storage space. System Response: The PKCAADMN utility will be unable to proceed without the ability to allocate memory for storage. Program execution will terminate. User Response: Contact PKWARE Technical Support to determine the origin of the memory allocation error. Invoking module: <PKCAADMN>
ZPCA808E
ZPCA808E Failed to read from certificate store '%s'. Explanation: The PKCAADMN program was unable to read from the specified certificate store file. %s Shows the value that the PKCAADMN utility received for the certificate store. System Response: The PKCAADMN utility was able to open the specified certificate store file. However, the program was unable read from the file. Program execution will terminate. User Response: Verify that the file is indeed a valid certificate store file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA809E
ZPCA809E Failed to read the entire file '%s'. Expected %d1, read %d2. Explanation: The PKCAADMN program was unable to read all of the data from the specified certificate store file. %s Shows the value that the PKCAADMN utility received for the certificate store. %d1 Shows the expected data size to be read from the certificate store file. %d2 Shows the actual data size read from the certificate store file. System Response: The PKCAADMN utility was able to open the specified
Certificate Administration 96
certificate store file and read from it successfully. However, the program was unable to read all the expected data from the file. Program execution will terminate. User Response: Verify that the file is indeed a valid certificate store file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA810E
ZPCA810E Failed to build certificate store '%s'. Explanation: The PKCAADMN program was unable take the data from the file and form a certificate store in memory. %s Shows the value that the PKCAADMN utility received for the certificate store. System Response: The PKCAADMN utility was able to open the specified certificate store file and read all the data from it successfully. However, the program was unable to use the data from the file to form a valid certificate data structure in memory. Program execution will terminate. User Response: Verify that the file is indeed a valid certificate store file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA811E
ZPCA811E PKCAADMN failed to open '%s'. CW Error = 0x%X. Explanation: The PKCAADMN program was unable to take the data from the certificate file and form a certificate data object in memory. %s Shows the file name of the certificate file that the PKCAADMN utility was working with when the failure occurred. %X Shows the hexadecimal value of the internal certificate service module's return code upon failure to process the certificate file. This internal value will assist technical support to help resolve the issue for non obvious errors. Possible follow on messages: * : <File contents could not be resolved for certificates> : <File could not be found or physically opened> : <PKCS12 File may have incorrect Password>
Certificate Administration 97
: Cannot continue. Unable to open PKCS7 certificate file : Cannot continue. Unable to open PKCS12 certificate file : Cannot continue. Unable to open CER certificate file System Response: The PKCAADMN utility was able to open the specified certificate file and read all the data from it successfully. However, the program was unable to use the data from the file to form a valid certificate data structure in memory. Program execution will terminate. User Response: Verify that the file is indeed a valid certificate file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA812E
ZPCA812E PKCAADMN failed to add '%s'. CW Error = 0x%X. <SecureZIP Only> Explanation: The PKCAADMN program was unable to add the specified certificate file to the certificate store. %s Shows the value that the PKCAADMN utility received for the certificate file. %X Shows the hexadecimal value the certificate service module returned. System Response: The PKCAADMN utility was able to open the specified certificate file and process the data. However, the utility failed to add to certificate to the store. Program execution will terminate. User Response: Verify that the file is indeed a valid certificate file and attempt the command again. If PKWARE technical support is contacted for assistance, provide the following: 1. The full text of this message. 2. The DCB attributes of the input file. 3. The expected format of the input file, for example: > Public key only certificate > PKCS#12 private key certificate package > P7B Invoking module: <PKCAADMN>
ZPCA813E
ZPCA813E Failure attempting to free certificate context. CW Error = 0x%X.
Certificate Administration 98
<SecureZIP Only> Explanation: The PKCAADMN program was unable to release the system resources allocated by the certificate service modules during program execution. %X Shows the hexadecimal value the service module returned upon failure to free the certificate context. System Response: The PKCAADMN utility was unable to release the system resources allocated by the certificate service modules during program execution. This is indicative of an internal program error. Program execution will terminate. User Response: Contact PKWARE Technical Support to determine the resolution of the program error. Invoking module: <PKCAADMN>
ZPCA814E
ZPCA814E Cannot continue. Unable to close root store. Explanation: The PKCAADMN program was unable to close the root store. The program allocates system resources associated with the root store and was unable to free those resources after use. System Response: The PKCAADMN utility was unable return the root store resources back to the operating system after use. The program cannot recover from this state and the program execution will terminate. User Response: It is possible that the certificate store is corrupt in some way. Verify that the root store is valid. If the root store proves valid, contact PKWARE Technical Support to determine the source of the failure. Invoking module: <PKCAADMN>
ZPCA815E
ZPCA815E Cannot continue. Unable to close CA store. Explanation: The PKCAADMN program was unable to close the CA store. The program allocates system resources associated with the CA store and was unable to free those resources after use. System Response: The PKCAADMN utility was unable return the CA store resources back to the operating system after use. The program cannot recover from this state and the program execution will terminate.
Certificate Administration 99
User Response: It is possible that the certificate store is corrupt in some way. Verify that the CA store is valid. If the CA store proves valid, contact PKWARE Technical Support to determine the source of the failure. Invoking module: <PKCAADMN>
ZPCA816E
ZPCA816E Cannot continue. Unable to save certificate store. Explanation: The PKCAADMN program was unable to save the certificate store. The program write the certificate store back to disk to complete the operation and was unable to do so. System Response: The PKCAADMN utility was unable write the certificate store back to disk. The program cannot recover from this state and the program execution will terminate. User Response: It is possible that the certificate store is corrupt in some way. Verify that the certificate store is valid. If the store proves valid, verify that the utility has write access to the disk in question and reattempt the operation.* Invoking module: <PKCAADMN>
ZPCA817E
ZPCA817E Failed to write to certificate store '%s'. Explanation: The PKCAADMN program was unable to write to the specified certificate store file. %s Shows the value that the PKCAADMN utility received for the certificate store. System Response: The PKCAADMN utility was able to open the specified certificate store file. However, the program was unable write to the file. Program execution will terminate. User Response: Verify that the file is indeed a valid certificate store file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA818E
ZPCA818E Failed to write the entire file '%s'. Expected %d1, wrote %d2.
Certificate Administration 100
Explanation: The PKCAADMN program was unable to write all of the data to the specified certificate store file. %s Shows the value that the PKCAADMN utility received for the certificate store. %d1 Shows the expected data size to be written to the certificate store file. %d2 Shows the actual data size written to the certificate store file. System Response: The PKCAADMN utility was able to open the specified certificate store file and wrote to it successfully. However, the program was unable to write all the expected data to the file. Program execution will terminate. User Response: Verify that the file is indeed a valid certificate store file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA819E
ZPCA819E Cannot continue. Nothing found to save to the certificate store. Explanation: The PKCAADMN program found nothing to write to the specified certificate store file. System Response: The PKCAADMN utility was able to open the specified certificate store file but found nothing to write. This is an unrecoverable program state and the program execution will terminate. User Response: Verify that the file is indeed a valid certificate store file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA820E
ZPCA820E Cannot continue. Unable to close the certificate store. Explanation: The PKCAADMN program was unable to close the certificate store. The program allocates system resources associated with the certificate store and was unable to free those resources after use. System Response: The PKCAADMN utility was unable return the root store resources back to the operating system after use. The program cannot recover from this state and the program
Certificate Administration 101
execution will terminate. User Response: It is possible that the certificate store is corrupt in some way. Verify that the root store is valid. If the root store proves valid, contact PKWARE Technical Support to determine the source of the failure. Invoking module: <PKCAADMN>
ZPCA821E
ZPCA821E Cannot continue. Unable to close certificate revocation list store. Explanation: The PKCAADMN program was unable to close the certificate revocation list store. The program allocates system resources associated with the certificate revocation list store and was unable to free those resources after use. System Response: The PKCAADMN utility was unable return the certificate revocation list store resources back to the operating system after use. The program cannot recover from this state and the program execution will terminate. User Response: It is possible that the certificate store is corrupt in some way. Verify that the certificate revocation list store is valid. If the certificate revocation list store proves valid, contact PKWARE Technical Support to determine the source of the failure. Invoking module: <PKCAADMN>
ZPCA822E
ZPCA822E Cannot continue. Unhandled certificate file type. Explanation: The PKCAADMN utility received a certificate file type that the program does not know how to process. System Response: The PKCAADMN utility will be unable to proceed without a properly specified certificate file type parameter. Program execution will terminate. User Response: This is an error internal to the program. Contact PKWARE Technical Support to resolve this issue. Invoking module: <PKCAADMN>
Certificate Administration 102
ZPCA823E
ZPCA823E Cannot continue. Unable to retrieve certificate name from the store. Explanation: The PKCAADMN utility must match the certificate name specified for deletion with the certificate name found in the certificate store. The program was unable to read the certificate name from the certificate store. System Response: The PKCAADMN utility will be unable to proceed without properly reading the certificate name from the store. Program execution will terminate. User Response: The certificate store in question may be invalid. Verify the integrity of the certificate store and try the command again. Invoking module: <PKCAADMN>
ZPCA824E
ZPCA824E Cannot continue. Delete certificate failed. Explanation: The PKCAADMN utility was unable to delete the certificate from the certificate store. System Response: The PKCAADMN utility will be unable to proceed past this point in the deletion process and program execution will terminate. User Response: This is an error internal to the program. The program was able to identify the certificate to be deleted in the certificate store but the deletion failed. Contact PKWARE Technical Support to resolve this issue. Invoking module: <PKCAADMN>
ZPCA825E
ZPCA825E Delete certificate failed. Match was not found in the specified store. Explanation: The PKCAADMN utility must match the certificate specified in the input parameters with a certificate in the specified certificate store in order to perform the deletion process. This match failed. System Response: The PKCAADMN utility will be unable to proceed without properly matching the certificate specified for deletion with an entry in the certificate store. Program execution
Certificate Administration 103
will terminate. User Response: The certificate store in question may not contain the specified certificate. Verify the certificate store contents and try the command again. Invoking module: <PKCAADMN>
ZPCA826E
ZPCA826E Serial number must be in hexadecimal notation. Explanation: The PKCAADMN utility must match the certificate serial number to an entry in the certificate store. The provided serial number was not in proper hexadecimal notation. System Response: The PKCAADMN utility will be unable to proceed without properly matching the certificate specified for deletion with an entry in the certificate store. Program execution will terminate. User Response: The serial number may have been improperly entered in the PKCAADMN utility. Verify the serial number parameter and try the command again. Invoking module: <PKCAADMN>
ZPCA827E
ZPCA827E Certificate store verification failed. Explanation: The PKCAADMN utility was unable to verify the specified certificate store. System Response: The PKCAADMN utility failed to verify the store for a specific reason. Look to the previous errors associated with this error in the listing to determine the exact cause of the verify command failure. User Response: Investigate the previous errors in the listing to determine the root cause of the verify failure. Invoking module: <PKCAADMN>
ZPCA828E
ZPCA828E Must specify root, CA or CRL store to initialize. Explanation: The PKCAADMN utility was to continue with the certificate
Certificate Administration 104
store initialization due to an invalid store type. System Response: The PKCAADMN utility will be unable to proceed past this point in the initialization process and program execution will terminate. User Response: This is an error internal to the program. Contact PKWARE Technical Support to resolve this issue. Invoking module: <PKCAADMN>
ZPCA829E
ZPCA829E Certificate store initialization failed. Explanation: The PKCAADMN utility was unable to initialize the specified certificate store. System Response: The PKCAADMN utility failed to initialize the store for a specific reason. Look to the previous errors associated with this error in the listing to determine the exact cause of the initialization command failure. User Response: Investigate the previous errors in the listing to determine the root cause of the initialization failure. Invoking module: <PKCAADMN>
ZPCA830E
ZPCA830E The end entity file '%s' was not opened. Explanation: The PKCAADMN program was unable to open the specified end entity output file. %s Shows the value that the PKCAADMN utility received for the output file. System Response: The PKCAADMN utility was unable to open the specified end entity output file. The program cannot recover from this situation and the program execution will terminate. User Response: Verify that the file name is indeed a valid and attempt the command again. Invoking module: <PKCAADMN>
Certificate Administration 105
ZPCA831E
ZPCA831E Could not retrieve certificate property from store. Explanation: The PKCAADMN utility must retrieve certificate properties from the certificate store and could not. System Response: The PKCAADMN utility will be unable to proceed past this point in the end entity output process and program execution will terminate. User Response: This is an error internal to the program. Contact PKWARE Technical Support to resolve this issue. Invoking module: <PKCAADMN>
ZPCA832E
ZPCA832E Cannot continue. Unable to make CRL from file '%s'. Explanation: The PKCAADMN utility must create a certificate revocation list data structure from the input file but was unable to. %s Shows the value that the PKCAADMN utility received for the certificate revocation list. System Response: The PKCAADMN utility will be unable to proceed past this point in the certificate revocation list add process and program execution will terminate. User Response: It is possible that the input file is not a valid certificate revocation list file. Verify the input file and attempt the command again. Invoking module: <PKCAADMN>
ZPCA833W
ZPCA833W Cannot verify CRL issuer '%s' with CA Store. Trying Root Store. Explanation: The PKCAADMN utility must verify the certificate revocation list data issuer to be sure the revocation list is valid. The program was unable to find the CRL issuer in the CA store. %s The issuer name for the certificate revocation list in question. System Response: The PKCAADMN utility will also look in the root store for the issuer before abandoning the CRL add process.
Certificate Administration 106
User Response: The utility will also check the root store for the CRL issuer. This is only a warning message and will not hinder the CRL add process unless the CRL issuer is not found in the root store either. Invoking module: <PKCAADMN>
ZPCA834W
ZPCA834W Cannot verify CRL issuer with root store. Explanation: The PKCAADMN utility must verify the certificate revocation list data issuer to be sure the revocation list is valid. The program was unable to find the CRL issuer in the root store. System Response: The PKCAADMN utility will also look in the CA store for the issuer before abandoning the CRL add process. User Response: The utility will also check the CA store for the CRL issuer. This is only a warning message and will not hinder the CRL add process unless the CRL issuer is not found in the CA store either. Invoking module: <PKCAADMN>
ZPCA835E
ZPCA835E Cannot continue. Unable to verify CRL issuer. Explanation: The PKCAADMN utility must verify the certificate revocation list data issuer to be sure the revocation list is valid. The program was unable to find the CRL issuer in the root store or the CA store. System Response: The PKCAADMN utility has checked both the root and the CA stores for the CRL issuer and was unsuccessful. The program cannot continue with the CRL add without verifying the issuer and the program execution will terminate. User Response: Verify the contents of the root and/or CA stores to be sure that the issuer for the CRL in question is present in one of the stores and attempt the command again. Invoking module: <PKCAADMN>
ZPCA836E
ZPCA836E Cannot continue. Unable to add CRL to store.
Certificate Administration 107
Explanation: The PKCAADMN utility was unable to add the CRL file to the certificate revocation list store. System Response: The PKCAADMN utility cannot continue the add process past this point and the program execution will terminate. User Response: Verify the certificate revocation list store is valid and attempt the command again. Invoking module: <PKCAADMN>
ZPCA837E
ZPCA837E Failure attempting to free CRL context. CW Error = 0x%X. Explanation: The PKCAADMN program was unable to release the system resources allocated by the certificate service modules during program execution. %X Shows the hexadecimal value the service module returned upon failure to free the CRL context. System Response: The PKCAADMN utility was unable to release the system resources allocated by the certificate service modules during program execution. This is indicative of an internal program error. Program execution will terminate. User Response: Contact PKWARE Technical Support to determine the resolution of the program error. Invoking module: <PKCAADMN>
ZPCA838E
ZPCA838E Cannot continue. Unable to get information from CRL. Explanation: The PKCAADMN program was unable to retrieve information from the certificate revocation list data structure. System Response: The PKCAADMN utility was unable to retrieve information from the certificate revocation list data structure. This is indicative of an internal program error. Program execution will terminate. User Response: Contact PKWARE Technical Support to determine the resolution of the program error. Invoking module: <PKCAADMN>
Certificate Administration 108
ZPCA839E
ZPCA839E Cannot continue. Unable to get name from CRL. Explanation: The PKCAADMN program was unable to retrieve the CRL name from the certificate revocation list data structure. System Response: The PKCAADMN utility was unable to retrieve the CRL name from the certificate revocation list data structure. This is indicative of an internal program error. Program execution will terminate. User Response: Contact PKWARE Technical Support to determine the resolution of the program error. Invoking module: <PKCAADMN>
ZPCA840E
ZPCA840E Delete CRL failed. Match was not found in the CA or Root store. Explanation: The PKCAADMN program was unable to find the CRL issuer in the CA or root stores. The CRL delete is unable to proceed in this situation. System Response: The PKCAADMN utility was unable to retrieve the CRL issuer from the root or CA stores. The program cannot recover from this situation and the program execution will terminate. User Response: Verify the contents of the CA and/or root stores and attempt the command again. Invoking module: <PKCAADMN>
ZPCA841E
ZPCA841E Delete CRL failed. Unable to find the CRL in the store. Explanation: The PKCAADMN program was unable to find the specified CRL in the certificate revocation list store. The CRL delete command is unable to proceed in this situation. System Response: The PKCAADMN utility was unable to find the CRL in the certificate revocation list store. The program cannot recover from this situation and the program execution will terminate. User Response: Verify the contents of the certificate revocation list store and attempt the command again.
Certificate Administration 109
Invoking module: <PKCAADMN>
ZPCA842E
ZPCA842E Delete CRL failed. Unable to remove the CRL from the store. Explanation: The PKCAADMN program was unable to delete the specified CRL entry from the certificate revocation list store. System Response: This error is indicative of an internal program error. The program execution will terminate. User Response: Contact PKWARE Technical Support to determine the resolution of the program error. Invoking module: <PKCAADMN>
ZPCA843E
ZPCA843E The store file '%s' was empty. Please try a valid certificate store. Explanation: The PKCAADMN program was passed the name of an empty file in place of a certificate store. %s Shows the value that the PKCAADMN utility received for the certificate store. System Response: The PKCAADMN utility is unable to proceed without properly specified certificate stores. The program cannot recover from this situation and the program execution will terminate. User Response: Verify the certificate store file names and attempt the command again. Invoking module: <PKCAADMN>
ZPCA844E
ZPCA844E Certificate type could not be determined. Explanation: The PKCAADMN program was unable to determine the type of the certificate to be add. System Response: The PKCAADMN utility is unable to proceed without properly the type of the certificate being added as this type determines which store the certificate should be placed in. The program cannot recover from this situation and
Certificate Administration 110
the program execution will terminate. User Response: Verify the origin of the input file and be sure it is a valid certificate file and try the command again. Invoking module: <PKCAADMN>
ZPCA845E
ZPCA845E Invalid type specified for '%s' for Browse. Only CER and P7B types are valid. Explanation: The PKCAADMN program was unable to browse a file of the specified file type. %s Shows the value that the PKCAADMN utility received for the certificate file. System Response: The PKCAADMN utility was able to browse the specified certificate file type. Program execution will terminate. User Response: Verify the type of the certificate file in question and attempt the command again. Invoking module: <PKCAADMN>
ZPCA846W
ZPCA846W Simulation Requested. Nothing will be saved to the store. Explanation: The PKCAADMN utility has been given a simulate add command via the flag settings. Due to the simulation, nothing was saved to the certificate store. System Response: The PKCAADMN utility successfully ran the add command to completion, however nothing was saved to the certificate store. This is expected behavior for the simulated add command and this message is presented only as a reminder. User Response: If a simulate add was requested, no user action is required. However, if a simulation was not desired, change the flags so that a simulation will not occur and attempt the command again. Invoking module: <PKCAADMN>
ZPCA847W
ZPCA847W Simulation Requested. The end entity was not saved.
Certificate Administration 111
Explanation: The PKCAADMN utility has been given a simulate add command via the flag settings. Due to the simulation, the end entity was not saved to the output file. System Response: The PKCAADMN utility successfully ran the add command to completion, however nothing was saved to the output file. This is expected behavior for the simulated add command and this message is presented only as a reminder. User Response: If a simulate add was requested, no user action is required. However, if a simulation was not desired, change the flags so that a simulation will not occur and attempt the command again. Invoking module: <PKCAADMN>
ZPCA848W
ZPCA848W End entity not saved as file was not specified. Explanation: The PKCAADMN utility could not save the end entity to disk as no output file was specified in the input parameters to the PKCAADMN program. System Response: The PKCAADMN utility successfully ran the add command to completion, however nothing was saved as the output file was not specified. User Response: If this was the desired command, no user action is required. However, if the end entity output was needed, change the input parameters so that a valid output file is specified and attempt the command again. Invoking module: <PKCAADMN>
ZPCA849E
ZPCA849E Cannot continue. Unable to determine certificate store count. Explanation: The PKCAADMN utility was not able to determine the number of certificates in the certificate store. System Response: The PKCAADMN utility successfully opened the certificate store but was unable to get a count of the number of certificates in that store. The program can not continue if this situation occurs. User Response: This error could be indicative of an invalid store. Run a validate command against the store in question to determine that it is not corrupt. If the validate command is successful, this could be indicative of an internal
Certificate Administration 112
program error. In this case, contact PKWARE Technical Support to resolve this problem. Invoking module: <PKCAADMN>
ZPCA850E
ZPCA850E Cannot continue. Unable to determine certificate file count. Explanation: The PKCAADMN utility was not able to determine the number of certificates in the specified input file. System Response: The PKCAADMN utility successfully opened the input file but was unable to get a count of the number of certificates in that file. The program can not continue if this situation occurs. User Response: This error could be indicative of an invalid input file. Verify the source of the input file in question to determine that it is not corrupt. If necessary, export and/or transfer the input file to the system again to ensure file integrity. If this fails to resolve the problem with the file, contact PKWARE Technical Support to resolve this problem. Invoking module: <PKCAADMN>
ZPCA851E
ZPCA851E Cannot continue. Unable to determine CRL store count. Explanation: The PKCAADMN utility was not able to determine the number of certificate revocation list entries in the CRL store. System Response: The PKCAADMN utility successfully opened the CRL store but unable to get a count of the number of certificate revocation list entries in that store. The program can not continue if this situation occurs. User Response: This error could be indicative of an invalid store. Run a validate command against the store in question to determine that it is not corrupt. If the validate command is successful, this could be indicative of an internal program error. In this case, contact PKWARE Technical Support to resolve this problem. Invoking module: <PKCAADMN>
Certificate Administration 113
ZPCA852E
ZPCA852E Cannot continue. Unable to determine CRL file count. Explanation: The PKCAADMN utility was not able to determine the number of certificate revocation list entries were contained in the specified input file. System Response: The PKCAADMN utility successfully opened the input file but was unable to get a count of the number of certificate revocation list entries in that file. The program can not continue if this situation occurs. User Response: This error could be indicative of an invalid input file. Verify the source of the input file in question to determine that it is not corrupt. If necessary, export and/or transfer the input file to the system again to ensure file integrity. If this fails to resolve the problem with the file, contact PKWARE Technical Support to resolve this problem. Invoking module: <PKCAADMN>
ZPCA853E
ZPCA853E Add operation was not completed due to newer CRL entry in the CRL store. Explanation: The PKCAADMN utility was unable to complete the Add command due to the fact that there was a newer copy of the input certificate revocation list already in the CRL store. System Response: The PKCAADMN utility will not permit an older certificate revocation list to overwrite a newer one already present in the CRL store. The program will terminate in this case. User Response: This error could be indicative of an invalid input file. Verify the source of the input file in question to determine that it is not corrupt. If necessary, export and/or transfer the input file to the system again to ensure the newest available certificate revocation list is being added to the CRL store. Invoking module: <PKCAADMN>
ZPCA854E
ZPCA854E Add operation was not completed due to newer certificate entry in the store.
Certificate Administration 114
Explanation: The PKCAADMN utility was unable to complete the Add command due to the fact that there was a newer copy of the input certificate already in the certificate store. System Response: The PKCAADMN utility will not permit an older certificate to overwrite a newer one already present in the certificate store. The program will terminate in this case. User Response: This error could be indicative of an invalid input file. Verify the source of the input file in question to determine that it is not corrupt. If necessary, export and/or transfer the input file to the system again to ensure the newest available certificate is being added to the certificate store. Invoking module: <PKCAADMN>
ZPCA900I
ZPCA900I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSVFY>
ZPCA901E
ZPCA901E Certificate Verification Errors Explanation: A call to PKCAADMN for Verification of a store was not successful. The data preceding this message will identify the type of error. System Response: Processing continues User Response: Review the preceding messages to determine a cause of action. Invoking module: <PKCSVFY>
Certificate Administration 115
ZPCA910I
ZPCA910I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSCRLA>
ZPCA911E
ZPCA911E Exclusive control can not be obtained for the CRL store Explanation: Another user is administering the Cert Store System Response: Process stopped User Response: Rerun at a later time Invoking module: <PKCSCRLA>
ZPCA912E
ZPCA912E Could not process the CRL store for add Explanation: PKCAADMN could not update the CRL store System Response: Process stopped User Response: See preceding messages for additional information Invoking module: <PKCSCRLA>
ZPCA913E
ZPCA913E Could not process the CRL store for add Explanation: PKCAADMN could not update the CRL store System Response: Process stopped User Response: See preceding messages for additional information Invoking module: <PKCSCRLA>
Certificate Administration 116
ZPCA914W
ZPCA914W Certificate Revocation List warning messagesº Explanation: A call to PKCAADMN for addition of a CRL return with a warning message. The data preceding this message will identify the type of error. System Response: Process continues User Response: Review the preceding messages to determine a cause of action. Invoking module: <PKCSCRLA>
ZPCA915E
ZPCA915E Exclusive control can not be obtained for the CRL store Explanation: Another user is administering the Cert Store System Response: Process stopped User Response: Update the CRL store at a later time. Invoking module: <PKCSCRLA>
ZPCA916E
ZPCA916E Exclusive control can not be obtained for the CRL store Explanation: Another user is administering the Cert Store System Response: Process stopped User Response: Update the CRL store at a later time. Invoking module: <PKCSCRLA>
ZPCA917E
ZPCA917E The source input file is invalid Explanation: The CRL input dataset is not valid System Response: Process stopped
Certificate Administration 117
User Response: Specify the correct input dataset Invoking module: <PKCSCRLA>
ZPCA920I
ZPCA920I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSCRLL>
ZPCA921E
ZPCA921E List Completed with errors Explanation: List of a CRL file failed. System Response: Processing continues User Response: Review the preceding messages to determine the type of error. Invoking module: <PKCSCRLL>
ZPCA930I
ZPCA930I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSDCR>
ZPCA931E
ZPCA931E Certificate Delete Failed
Certificate Administration 118
Explanation: A call to PKCAADMN for deletion of a CA or Root was not successful. The data preceding this message will identify the type of error. System Response: Process stopped User Response: Review the preceding messages to determine a course of action. Invoking module: <PKCSDCR>
ZPCA932E
ZPCA932E Certificate Delete Failed Explanation: A call to PKCAADMN for deletion of a CA or Root was not successful. The data preceding this message will identify the type of error. System Response: Process stopped User Response: Review the preceding messages to determine a course of action. Invoking module: <PKCSDCR>
ZPCA933W
ZPCA933W Certificate Delete warning messages Explanation: A call to PKCAADMN for deletion of a CA or Root return with a warning message. The data preceding this message will identify the type of error. System Response: Process continues User Response: Review the preceding messages to determine a course of action. Invoking module: <PKCSDCR>
ZPCA934E
ZPCA934E Exclusive control can not be obtained for the P7B store
Certificate Administration 119
Explanation: Another user is administering the Cert Store System Response: Process stopped User Response: Delete the CA or Root certificates at a later time Invoking module: <PKCSDCR>
ZPCA940I
ZPCA940I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSEXTR>
ZPCA941E
ZPCA941E Extract Completed with errors Explanation: Extract processing of a store input failed. System Response: Processing continues User Response: Review the preceding messages to determine the type of error. Invoking module: <PKCSEXTR>
ZPCA942E
ZPCA942E Extract can not allocate the P7B store Explanation: Extract processing of a store output failed. System Response: Process stopped User Response: Respecify the output stores Invoking module: <PKCSEXTR>
Certificate Administration 120
ZPCA943E
ZPCA943E Extract stopped by user Explanation: Extract processing of a store input was stopped by request System Response: Process stopped User Response: None Invoking module: <PKCSEXTR>
ZPCA950I
ZPCA950I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSINIT>
ZPCA951E
ZPCA951E Init Failed for: P7B store dataset Explanation: Init could not process the output P7B store System Response: Process halted User Response: Review the preceding messages to determine the type of error. Invoking module: <PKCSINIT>
ZPCA952W
ZPCA952W Init Warning issued for: P7B store dataset Explanation: PKCAADMN issued a warning message for this store System Response: Process completed User Response: Review the preceding messages to determine the type of error.
Certificate Administration 121
Invoking module: <PKCSINIT>
ZPCA953E
ZPCA953E Exclusive control can not be obtained for the P7B store Explanation: Another user is administering the Cert Store System Response: Process stopped User Response: Initialize the P7B store at a later time. Invoking module: <PKCSINIT>
ZPCA954E
ZPCA954E Can not allocate the P7B store Explanation: The P7B store can not be allocated. System Response: Process stopped User Response: Verify the correct dataset name Invoking module: <PKCSINIT>
ZPCA955E
ZPCA955E Overwrite existing dataset denied by user Explanation: The P7B store can not be used as output System Response: Process stopped User Response: Select a different dataset name Invoking module: <PKCSINIT>
ZPCA960I
ZPCA960I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None
Certificate Administration 122
User Response: None Invoking module: <PKCSLIST>
ZPCA961E
ZPCA961E List Completed with errors Explanation: List of a CA or Root certificate failed. System Response: Processing continues User Response: Review the preceding messages to determine the type of error. Invoking module: <PKCSLIST>
ZPCA970I
ZPCA970I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSENDE>
ZPCA971E
ZPCA971E End Entity Processing Completed with errors Explanation: End Entity processing of a store failed. System Response: Process stopped User Response: Review the preceding messages to determine the type of error. Invoking module: <PKCSENDE>
ZPCA972E
ZPCA972E End Entity Processing Completed with errors
Certificate Administration 123
Explanation: Can not allocate the P7B store System Response: Process stopped User Response: Verify the dataset entered is the correct dataset to use as output Invoking module: <PKCSENDE>
ZPCA973E
ZPCA973E End Entity Processing Completed with errors Explanation: The process was stopped by the user System Response: Process stopped User Response: Specify a dataset acceptable to use as output. Invoking module: <PKCSENDE>
ZPCA978I
ZPCA978I Member "member" created Explanation: The extraction of an End Entity was successful System Response: The certificate was placed in the member indicated User Response: NONE Invoking module: <PKCSENDE>
ZPCA980I
ZPCA980I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSTRAN>
Certificate Administration 124
ZPCA981E
ZPCA981E Translate Completed with errors Explanation: Attempting to translate an EBCDIC BASE64 encoded certificate to ASCII was not successful. System Response: Processing continues User Response: Verify that this is an EBCDIC encoded certificate with the source of the certificate. Invoking module: <PKCSTRAN>
ZPCA990I
ZPCA990I Certificate Store General Information Explanation: This message will contain banner and general information for Certificate Store processing. System Response: None User Response: None Invoking module: <PKCSSIM>
ZPCA991E
ZPCA991E Add simulation was not successful Explanation: Simulation add of a CA or Root certificate failed. System Response: Processing continues User Response: Review the preceding messages to determine the type of error. Invoking module: <PKCSSIM>
Compression Engine 125
ZPCE - Compression Engine Messages
ZPCE060T
ZPCE060T Work Directive: +80+C+ Explanation: This is a technical-support trace message from the compression engine. System Response: None User Response: None Invoking module: <ACCOZIP>
ZPCE201I
ZPCE201I Memory Shortage, medium memory model selected Explanation: The compression engine detected that a virtual storage threshold was reached and switched from "Large" to "Medium". System Response: An attempt is made to continue processing with smaller buffers. User Response: Specify a larger REGION size. Invoking module: <ACCOZIP>
ZPCE204E
ZPCE204E Internal PUTQ failure, Short on Storage Explanation: An internal error was detected trying write to an output storage queue. Short on Storage condition. System Response: Zip process terminated. User Response: Specify a larger REGION size. Invoking module: <ACCOZIP>
Configuration Manager 126
ZPCM - Configuration Manager Messages
ZPCM000I
ZPCM000I Simulation Mode has been selected for action +8+C+ Explanation: The specified action was requested to be performed in simulation mode (via the -SIMULATE command). Various I/O activity and compression/decompression activities will be bypassed for actions including ADD, FRESHEN, UPDATE and EXTRACT. Other actions will operate normally. -SIMULATE is useful when attempting to see what filenames will be selected for processing, and to what target names they will be extracted with various command options (e.g. -NOPATH, -ZIPPED_DSN, etc). System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM001E
ZPCM001E Invalid ACZDFLT value PARMLIB_DSNAME_ZIP{+54+C+} Explanation: The Configuration Manager was reading the active defaults module and detected that the dataset name specified does not conform to MVS dataset naming conventions. Note: If the execution has specified a defaults module other than ACZDFLT (via -DM EXEC PARM), then that module should be examined. System Response: The execution is terminated. User Response: The product installer should correct the value before another execution is attempted, or a different defaults module should be specified. Invoking module: <ACCMGR>
ZPCM002E
ZPCM002E //PARMLIB DATASET NOT FOUND: {+54+C+}
Configuration Manager 127
Explanation: The DSNAME specified in the defaults module could not be found. This file is dynamically allocated when the //PARMLIB (or //CONFIG) statement is not provided at execution time. System Response: Initialization is terminated. User Response: The product installer should correct the value before another execution is attempted, or a different defaults module should be specified. The user may also specify a //PARMLIB DD statement as an override. Invoking module: <ACCMGR>
ZPCM003E
ZPCM003E Command line exceeds 256 characters Explanation: The total number of continued command lines exceeds the programmed limit of 256 characters. An individual control statement consists of a control segment which is constructed from multiple input lines with continuation characters (with suffixed blanks having been removed), and is delimited by either record end, or ";" if multiple commands per line are specified. System Response: Initialization is terminated. User Response: Reduce the number of continuation lines in the command. Invoking module: <ACCMGR>
ZPCM004E
ZPCM004E An unrecognized command was found in +8+C+ Explanation: The command specified in the DD statement or EXEC parm was not found in the valid commands table. System Response: Initialization is terminated. The invalid command is listed in the line following ZPCM004E. User Response: Check the spelling of the command. Invoking module: <ACCMGR>
Configuration Manager 128
ZPCM005E
ZPCM005E An invalid value was specified for +40+C+ Explanation: Each command has a valid set of value formats. This command was not of the proper format. Some common formats are: NUMERIC - Numeric digits only (although in some cases nnnK and nnnM are allowed for Kilobyte and Megabyte support). YESNO - The value must be "Y" or "N". DSNAME - A valid MVS data set name. CHARACTER- Any character values (up to a specified length) LIST - Only specific string values may be specified. System Response: Initialization is terminated User Response: Specify a correct value. Invoking module: <ACCMGR>
ZPCM006E
ZPCM006E Syntax error: +40+C+ Reason(+2+H+) Explanation: Configuration Manager could not properly parse the designated command for the reason specified. Note: A text reason is provided in +40+C+ for the user. The Hex Reason code may be ignored unless technical support requests it. System Response: Initialization is terminated User Response: Code an appropriate value with the control statement. Invoking module: <ACCMGR>
ZPCM007E
ZPCM007E SYSIN expected for DD=+8+C+, but //+8+C+ DD is not allocated Explanation: The installation defaults module specified that input commands should be read from the DD shown, but the execution did not provide that JCL statement. System Response: Initialization is terminated User Response: Either provide the specified DD JCL statement or use -NOSYSIN in the EXEC PARM.
Configuration Manager 129
Invoking module: <ACCMGR>
ZPCM008E
ZPCM008E PARMLIB file is in use and maximum wait time was exceeded. Explanation: The installation defaults module specified a "PARMLIB" dataset to read control cards from (before //SYSIN), but the dataset was held under exclusive control by another job or user. The defaults module values for PARMLIB_FILE_WAIT_TIMER and PARMLIB_FILE_WAIT_MAX govern how long retries will be attempted before the limit is reached. System Response: Initialization is terminated User Response: Determine who has the dataset to have it freed, then re-run the job. Invoking module: <ACCMGR>
ZPCM009E
ZPCM009E Error (+2+H+) processing +80+C+ Explanation: The command could not be processed successfully. Reason Code 08 - A comma was expected, but a blank was found, or the end of the command field was found instead. 09 - An inconsistent use of the command with the mode of execution was found. (e.g. A ZIPPED_DSN command was found while running PKUNZIP instead of UNZIPPED_DSN). 0A - The z/OS MVS data set name portion of the command has a length of either 0 or > 54. 0B - UNZIPPED_DSN (and its synonyms) is only valid for PKUNZIP processing. 0D - ZIPPED_DSN (and its synonyms) is only valid for PKZIP processing. 0E - ZIPPED_DSN translation specification error. System Response: Initialization is terminated User Response: Correct the commands or program selection. Invoking module: <ACCMGR>
Configuration Manager 130
ZPCM010E
ZPCM010E Member not accessible in dataset: +54+C+ Explanation: The input PDS member could not be read. System Response: If the error is for the PARMLIB file, processing continues If the error is for //SYSIN, processing terminates. User Response: Determine the correct member name and ensure that it is not in use by another job or user in the system. Note: You may provide a //PARMLIB DD DUMMY statement to eliminate the error message and the RC=4 completion code. Invoking module: <ACCMGR>
ZPCM010I
ZPCM010I Processing input file: +8+C+ +54+C+ Explanation: The configuration manager is reading commands. This message is issued when LOGGING_LEVEL(VERBOSE) is specified. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM011I
ZPCM011I Processing EXEC PARM parameters Explanation: The Configuration Manager finished reading the PARMLIB and SYSIN commands and is now processing EXEC PARM commands (if any). This message is issued when LOGGING_LEVEL(VERBOSE) is specified. System Response: None User Response: None Invoking module: <ACCMGR>
Configuration Manager 131
ZPCM012T
ZPCM012T Working on entry: +80+C+ Explanation: An internal trace record showing which command table entry is being processed. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM013T
ZPCM013T Setting entry value: +80+C+ Explanation: An internal trace record showing which command table entry is being processed and that the value is being set. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM014T
ZPCM014T Scanning command table - Pass +1+C+ Explanation: An internal trace record showing which command table entry is being processed. The command table is being scanned for either a real command match or an alias. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
Configuration Manager 132
ZPCM015I
ZPCM015I Relating alias {+40+C+} to truename Explanation: An alias name was used for a command and it is being translated internally to the real command name. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM016I
ZPCM016I Alias replaced with +50+C+ Explanation: The requested command (an alias command) was substituted with the real command value shown. This line is only issued when LOGGING_LEVEL(VERBOSE) is specified. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM017I
ZPCM017I A total of +8+D+ ADD/UPDATE candidate data sets were identified. Explanation: Configuration Manager processing information. During ZIP processing, files are identified for possible addition to the ZIP archive. These data sets will be examined for possible inclusion of processing. This count does not include individual members yet to be identified for partitioned data sets or PDSE Libraries. This line is only issued with LOGGING_LEVEL(VERBOSE). System Response: None User Response: None Invoking module: <ACCMGR>
Configuration Manager 133
ZPCM018E
ZPCM018E Relative GDG requests cannot be processed. Use -INFILE with JCL. Explanation: Relative GDG data set requests are only supported through -INFILE(ddname) with appropriate JCL DD statements. See also: -GDGALL_SUPPORT System Response: The file selection is skipped. Processing continues based on -ON_FILE_ACCESS_ERROR. User Response: Change the control card(s) to use -INFILE or -GDGALL_SUPPORT. Invoking module: <ACCMGR>
ZPCM019E
ZPCM019E -ACTION=+20+C+ is not valid for PGM=+8+C+. Switch programs or Action.
Explanation: The Action shown was requested, but is not valid with the specified program (PKZIP or PKUNZIP).
System Response: Processing is terminated. User Response: Change to the correct program for the action needed. Invoking module: <ACCMGR>
ZPCM020C
ZPCM020C SHOW_SETTINGS Completed Explanation: Configuration Manager processing information. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM020I
ZPCM020I SHOW_SETTINGS Display: (Using defaults module <+8+C+>) Explanation: Configuration Manager processing information. System Response: None
Configuration Manager 134
User Response: None Invoking module: <ACCMGR>
ZPCM021I
ZPCM021I Encryption Configuration Section Explanation: Configuration Manager processing information. The reports that follow contain collective information available a the time the report request is made regarding pertinent security settings. The report shows the currently merged configuration based on the defaults module, included command streams, in-line commands and the EXEC PARM commands. See also: ZPCM022I, ZPCM022C System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM021C
ZPCM021C -------------------------------- Explanation: Continuation message marking further information for ZPCM021I
System Response:
User Response:
Invoking module: <ACCMGR>
ZPCM022C
ZPCM022C Method: _algorithm_ (See -ENCRYPTION_METHOD) Password: Active|Inactive Recipient: Active|Inactive Master Recipient: None|Active|Dormant _default_master_recipient_information Explanation: Configuration Manager processing information. Method: During ZIP processing, the specified ENCRYPTION_METHOD
Configuration Manager 135
algorithm is employed when either -PASSWORD or -RECIPIENT settings have a value. One of the BSAFE encryption methods must be specified if recipients are desired (with or without a password). Password: If a PASSWORD value is provided, this field will indicate "Active". Recipient: If one or more RECIPIENTs are specified, this field will indicate "Active" Master Recipient: When this configuration setting specifies a recipient value when a BSAFE Encryption Method is activated (via PASSWORD or RECIPIENT) for ZIP processing, the specified Master Recipient will be automatically included as a recipient for the file. This value would commonly be set within the installation defaults module, included via the -DDNAME_PARMLIB command stream, or read in through an -INCLUDE_CMD statement. A corporate Private Key Digital Certificate would be specified that could be used regardless of other individuals listed in the RECIPIENT command(s). _default_master_recipient_information_ lists the first 80 characters of the specified setting. See also: ZPCM022C, ZPCM021I System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM022I
ZPCM022I Encryption: Active|Inactive Explanation: Configuration Manager processing information (ZIP) Encryption is activated through the use of the -PASSWORD and -RECIPIENT commands. If a value is present for either setting, whether through commands or default settings, then encryption will be attempted in accordance with other settings (e.g. -ENCRYPTION_METHOD). See also: ZPCM022C, ZPCM021I System Response: None User Response: None
Configuration Manager 136
Invoking module: <ACCMGR>
ZPCM023C
ZPCM023C (continuation line) {CSPUB=n;1;...} {CSPRVT=n;1;...} {CSCA=n;1;...} {CSROOT=n;1;...} {LDAP=n;_ip_address_;port;...} Explanation: ZPCM023C is a continuation line for ZPCM023I. User Response: See ZPCM023I
ZPCM023I
ZPCM023I Digital Certificate Store Configuration ZPCM023C (continuation line) {CSPUB=n;1;...} {CSPRVT=n;1;...} {CSCA=n;1;...} {CSROOT=n;1;...} {LDAP=n;_ip_address_;port;...} Explanation: Configuration Manager processing information. Recipient-based Encryption, Signing and Authentication require that digital certificates be used. This report displays the various specifications that are in effect for locating public-key and private-key certificates, as well as certificate processing controls. terms: CSPUB: Certificate Store for individual Public-key X.509 certificates on the local system. CSPRVT: Certificate Store for individual Private-key X.509 certificates on the local system. CSCA: Certificate Store for Certificate Authority Public-key X.509 certificates on the local system. Used to validate the certificate TRUST chain. CSROOT: Certificate Store for the Trusted Root Public-key X.509 certificates on the local system. Used to validate the certificate TRUST chain. LDAP: Certificate Store for individual Public-key X.509 certificates accessible via a TCPIP network for RECIPIENT based encryption.
Configuration Manager 137
CSPUB_DBX_...: A suite of database index components used to resolve DB: format lookups for RECIPIENT and AUTHCHK commands. AUTHENTICATE: The certificate validation policy settings to be used with signature verification (AUTHCHK). VAL_DECRYPT: The certificate validation policy settings to be used with RECIPIENT decryption. VAL_ENCRYPT: The certificate validation policy settings to be used with RECIPIENT encryption. VAL_SIGN: The certificate validation policy settings to be used with SIGN_FILES and SIGN_ARCHIVE. SPONSOR_AUTH: When a SecureZIP Partner license is in effect, Certificate Store for one or more Public-key X.509 certificates on the local system to be used with Archive Authentication. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM024C
ZPCM024C Req'd Public Recipient CN=Joe Smith ZPCM024C FILE FOUNDREQUIRED* ZPCM024C FILE CERT_OPEN_FAILUREREQUIRED* Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, a summary of -RECIPIENT requests will be logged. The type of digital certificate (public or private), the source (ldap or local file) and the status of whether the digital certificate was located will be listed. An indication of CERT_OPEN_FAILURE means that although the x.509 certificate file was located, it could not be successfully opened for the intended action. For example, if a private-key certificate was being accessed, but insufficient authority was given (either by the system security facility, or an incorrect case-sensitive password was provided), then the file will not be opened for processing. An indication of "UNUSABLE" means that the certificate validation policy in force at the time of the request deemed the certificate to be inappropriate for use for the intended action. See: -{VALSIGN..} -{VALENCRYPT...} -{AUTHENTICATE...}
Configuration Manager 138
System Response: None User Response: This information is useful in determining whether the expected recipient certificates could be located. If a private-key certificate is flagged CERT_OPEN_FAILURE, ensure that the correct password (case-sensitive) was specified in the associated -RECIPIENT specification. If a private-key certificate is flagged UNUSABLE, refer to messages ZPEN057W and ZPEN057C for additional details. Invoking module: <ACCMGR>
ZPCM024I
ZPCM024I Digital Certificate Request List Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, a summary of -RECIPIENT requests will be logged. Details will be listed for each recipient request with ZPCM024C. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM025C
ZPCM025C +118+C+ Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, detailed information from within the digital certificates found from -RECIPIENT requests will be listed. The information includes Common Name and Email address (if one is defined within the certificate). System Response: None User Response: This information is useful in determining whether the expected recipient certificates could be located. Invoking module: <ACCMGR>
Configuration Manager 139
ZPCM025I
ZPCM025I +8+D+ Digital Certificates Found: +30+C+ Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, a list of Digital Certificates found for the following request types will be provided. - ENCRYPTION RECIPIENTS - ARCHIVE SIGNER - FILE SIGNERS Information from within the certificates themselves will be provided in message ZPCM025C. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM027I
ZPCM027I Including commands from +54+C+ Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued to indicate that the command records associated with a -INCLUDE_CMD are being read from the specified source. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM028I
ZPCM028I Command(s) generated from +80+C+ Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued to indicate that the command or condition specified by +80+C+ caused an additional command to be generated in support of the processing request. Some conditions include: - A SecureZIP_CONFIG setting requested that additional commands be included from another source. An implicit -INCLUDE_CMD command was generated to read in the requested settings.
Configuration Manager 140
- "DEFAULT -RECIPIENT=" indicates that a defaults module entry for RECIPIENT was found, and a -RECIPIENT command was generated for processing. - "MASTER_RECIPIENT" indicates that a SecureZIP default MASTER_RECIPIENT was specified, so a -RECIPIENT command was generated for processing. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM030T
ZPCM030T IDCAMS TRACE: +8+C+ RC=+8+D+ Explanation: A call was made to IDCAMS for a basic function (+8+C+) such as LISTCAT with the return code indicated. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCSAMS>
ZPCM031I
ZPCM031I {+8+D+} files were found by the above request Explanation: Configuration Manager processing information. Catalog Management reported the number of datasets shown for the file filter specified. Each file filter request (e.g. SYS1.**) results in a separate call to catalog services. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
Configuration Manager 141
ZPCM032W
ZPCM032W Cataloged file request not found: +54+C+ Explanation: Configuration Manager processing information. The file filter supplied for ZIP processing did not result in any matches with the system catalog. System Response: The requested file/mask is ignored and processing continues. | RC = 4 is set. User Response: Verify that the correct dataset name or filter was specified. | -PKSUPPRC(ZPCM032W) may be specified to suppress | the return code for this event. Invoking module: <ACCMGR>
ZPCM033I
ZPCM033I Bypassed duplicate file select; +44+C+ Explanation: Configuration Manager processing information. A ZIP file request had multiple data set filter requests that resolved to the same file (dataset or member). System Response: Only the first occurrence of the file found will result in a ZIP for that item. Others will be bypassed. User Response: None Invoking module: <ACCMGR>
ZPCM034T
ZPCM034T File Candidate FMCB created: +8+H+ for +44+C+ Explanation: Configuration Manager processing internal trace. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR> <ACCSAMSP>
Configuration Manager 142
ZPCM035E
ZPCM035E Invalid internal parameter list. Explanation: Configuration Manager processing information. A call was made to catalog management, but an invalid PLIST was passed. System Response: Processing is terminated. User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACCSAMS>
ZPCM036T
ZPCM036T Device type +8+C+ = {+4+C+} {+6+C+} for +44+C+ Explanation: Configuration Manager processing trace record. Either a DD statement was provided or an input file filter located a cataloged dataset. A device table lookup was performed and the specified device type information was returned. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR> <ACCSAMSP>
ZPCM037W
ZPCM037W Device type +8+C+ unknown for dataset: +44+C+ Explanation: See also: ZPCM036T The device type shown could not be resolved. System Response: Access to the dataset is stopped. User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACCMGR> <ACCSAMSP>
Configuration Manager 143
ZPCM038I
ZPCM038I ALIAS match. Performing catalog lookup for: +44+C+ Explanation: -ALIAS_NAME_SUPPORT(Y) was specified and a cataloged alias was identified from the ZIP request. The TRUE catalog name will be resolved and used in the ZIP process. System Response: None User Response: None Invoking module: <ACCSAMSP>
ZPCM039I
ZPCM039I GDGALL request match for: +44+C+ Explanation: -GDGALL_SUPPORT(Y) was specified and a generation was located for ZIP processing. System Response: Processing for the individual generation continues. User Response: None Invoking module: <ACCMGR>
ZPCM040E
ZPCM040E Specified INFILE(+8+C+) is not allocated. Explanation: The specified DD statement is not in the JCL for the step (or allocated to the TSO session). System Response: Processing for the file is terminated. User Response: Correct the job allocations or -INFILE statement. Invoking module: <ACCMGR>
ZPCM041T
ZPCM041T //+8+C+ DD DSN=+44+C+ {+8+C+} Explanation: Configuration Manager processing information. The specified INFILE DD statement was resolved to the specified data set name. This line is only issued when Configuration Manager
Configuration Manager 144
tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM042W
ZPCM042W INFILE(+8+C+) had a catalog access error for +44+C+ Explanation: Configuration Manager processing information. An INFILE control card specified a DD statement for a cataloged dataset, but the catalog information request failed. System Response: Processing is terminated for the file. User Response: None Invoking module: <ACCMGR>
ZPCM043E
ZPCM043E INFILE(+8+C+) syntax error - MEMBER LENGTH > 8. Explanation: Configuration Manager processing error detected. A PDS or PDSE member name must be 1 - 8 characters. System Response: Processing is terminated for the file request. User Response: Correct the file name. Invoking module: <ACCMGR>
ZPCM044T
ZPCM044T FMCB Updated at +8+H+ for +44+C+ Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCSAMSP>
Configuration Manager 145
ZPCM045W
ZPCM045W The +8+C+ self-extraction program will not support Strong Encryption. Explanation: Configuration Manager command verification warning. Strong Encryption was selected for files while creating a Self-extracting Archive. The self-extraction program listed does not support Strong Encryption. System Response: The Archive is created. RC=4 is set . The Self Extractor is not added to the archive. The resulting Archive can be processed by PKZIP products that are at the 5.1 level or higher. User Response: If Strong Encryption is required, use a PKZIP product on the target system that supports it. Use Standard Encryption if the Self-extraction program is required for operation. Invoking module: <ACCMGR>
ZPCM046E
ZPCM046E Syntax error in RECIPIENT: +80+C+ Explanation: Configuration Manager command syntax error. SecureZip RECIPIENT processing could not be completed with the specified RECIPIENT information. The following reasons may be listed: "Unrecognized certificate locator type" - The first parameter designates the valid search type to be used when locating the digital certificate for an intended recipient. Values such as EM=, CN=, DD:, DSN: are expected. System Response: Processing is terminated. User Response: Correct the RECIPIENT information. Invoking module: <ACCMGR>
ZPCM047I
ZPCM047I This Edition is not licensed to create self extracting archives. Explanation: The creation of self-extracting archives is a licensed
Configuration Manager 146
feature. System Response: The request will be bypassed and a non-self extracting archive will be written. User Response: None Invoking module: <ACCMGR>
ZPCM048I
ZPCM048I OUTFILE_DSNTYPE(HFS) triggered by -CWD or -PATH_EDIT command(s). Explanation: During an EXTRACT, commands associated with an HFS target file system were entered, but no command for OUTFILE_DSNTYPE was provided. When -LOGGING_LEVEL(VERBOSE) is specified, this message is issued. System Response: The use of CWD or PATH_EDIT triggers OUTFILE_DSNTYPE=HFS. User Response: If a target file system other than HFS is desired, either remove the trigger commands from the input stream, or provide an explicit OUTFILE_DSNTYPE command. Invoking module: <ACCMGR>
ZPCM050W
ZPCM050W File is in use by another job/user: +44+C+ Explanation: Configuration Manager processing information. The file is being held by another job or user in the system. System Response: Processing for the file is bypassed. User Response: None Invoking module: <ACCMGR>
ZPCM051W
ZPCM051W No member selection requests matched in +44+C+ Explanation: Configuration Manager processing information. Although the associated dataset could be located, no members exist in the file to match the member
Configuration Manager 147
name selection criteria. System Response: None User Response: Verify that the desired members exist in the dataset. Invoking module: <ACCMGR>
ZPCM052I
ZPCM052I Recalling file to obtain attributes: +44+C+ Explanation: Configuration Manager processing information. ZIP processing identified a requested dataset that is migrated. Because RECALL_TO_ZIP(Y) is specified, the dataset is being recalled. See also: ZPCM053W Note: The recall is done early in the process to determine whether the dataset is partitioned. This information is necessary to assess each prospective Archive filename and match against any files already existing in the Archive. ADD, FRESHEN & UPDATE are all affected by the the existence of a file within the Archive. System Response: None User Response: If migrated datasets are not desired for ZIP processing, specify RECALL_TO_ZIP(N). Invoking module: <ACCMGR>
ZPCM053W
ZPCM053W RECALL_TO_ZIP(N) bypassing file: +44+C+ Explanation: ZIP processing can optionally skip Migrated datasets (i.e. migrated with DFSMS/DFHSM). See also: ZPCM052I System Response: Message issued only if LOGGING_LEVEL(VERBOSE) is specified. The file will be bypassed for ZIP processing. User Response: None Invoking module: <ACCMGR>
Configuration Manager 148
ZPCM055W
ZPCM055W Bypassing HFS file: +90+C+ Explanation: The file PATH shown was not processed. System Response: Processing of the z/OS UNIX Filesystem object is bypassed. User Response: Ensure that the file object is of a supported file type, such as a "regular file". Invoking module: <ACCMGR>
ZPCM056W
ZPCM056W Insufficient +7+C+ (+5+C+) authority: +54+C+ Explanation: The PATH object has insufficient PATHMODE permissions for the operation being attempted. System Response: Processing of the z/OS UNIX Filesystem object is terminated. User Response: Ensure that the file object has sufficient permissions defined for the process, or change the process owner executing the job to one that has sufficient authority. Invoking module: <ACCMGR>
ZPCM057E
ZPCM057E Insufficient PATHOPTS access defined for +16+C+ Explanation: When reading from an HFS PATH (file), PATHOPTS must specify either ORDONLY or ORDWR. When writing to an HFS PATH (file), PATHOPTS must specify either OWRONLY or ORDWR. +16+C+ indicates the type of command DD reference that was coded without an adequate PATHOPTS value in the corresponding DD statement. Common abends resulting from an incorrect PATHOPTS setting for HFS output files include: S013-C0 S614-10 (possibly followed by sub-task abend S30A) System Response: Command processing is terminated.
Configuration Manager 149
User Response: Supply an appropriate PATHOPTS value in the DD statement. Invoking module: <ACCMGR>
ZPCM058W
ZPCM058W The +8+C+ self-extraction program will not support FileName Encryption. Explanation: Configuration Manager command verification warning. File Name Encryption was specified for files while creating a Self-extracting Archive. The self-extraction program listed does not support File Name Encryption. System Response: The Archive is created. RC=4 is set. The Self Extractor is not added to the archive. The resulting Archive can be processed by PKZIP products that are at the 5.1 level or higher. User Response: If Strong Encryption is required, use a PKWARE product on the target system that supports it. - OR - Specify FILENAME_ENCRYPTION=N Use Standard Encryption if the Self-extraction program is required for operation. Invoking module: <ACCMGR>
ZPCM060T
ZPCM060T Work Directive: +80+C+ Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM061T
ZPCM061T +8+D+K allocated to +8+D+ elements on the Arch Mgr. Prelim
Configuration Manager 150
Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM062T
ZPCM062T +8+D+K allocated to +8+D+ elements on the Arch Mgr. Request Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM063T
ZPCM063T +8+D+K allocated to +8+D+ elements on the Arch Mgr. Add Queue Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM064T
ZPCM064T <SUBFMCB1> Processing {+80+C+} Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None
Configuration Manager 151
Invoking module: <ACCMGR>
ZPCM065T
ZPCM065T Phase1 input parm processing complete. Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM069E
ZPCM069E Error (+2+H+) processing +80+C+ Explanation: Configuration Manager processing error for -INFILE. Error Code: 8 Syntax error C Syntax error (name too long) 10 See ZPCM040E or ZPCM057E message 14 Short on storage 16 Possible DD definition problem 18 Member processing error 63 Unsupported DSORG 69 Member-name or GDG generation level problem. System Response: Processing for the dataset is terminated. RC=4 is set when ON_FILE_ACCESS_ERROR=TOLERATE is set, otherwise RC=8. User Response: Attempt to determine the cause of the error. Reference associated ZPCM040E message, if available Invoking module: <ACCMGR>
ZPCM070T
ZPCM070T Sending to FILE_SELECT_QUEUE {+80+C+} Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on.
Configuration Manager 152
System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM071E
ZPCM071E An input Archive must be specified with VIEW/UPDATE/REFRESH/DELETE Explanation: Configuration Manager processing error detected. One of the -ACTIONs was specified, but no input Archive was provided. System Response: Processing is terminated. User Response: Provide -ARCHIVE or -ARCHIVE_INFILE for the requested action, or change the request. Invoking module: <ACCMGR>
ZPCM072E
ZPCM072E An output Archive must be specified with ADD/UPDATE/REFRESH/DELETE Explanation: Configuration Manager processing error detected. One of the -ACTIONs was specified, but no output Archive was provided. System Response: Processing is terminated. User Response: Provide either -ARCHIVE or -ARCHIVE_OUTFILE. Invoking module: <ACCMGR>
ZPCM073E
ZPCM073E A conflict was detected with -ARCHIVE_DSN and ARCHIVE_INFILE/ARCHIVE_OUTFILE Reason Code=+2+H+ Explanation: Configuration Manager processing error detected. An invalid combination of the commands shown was encountered. -ARCHIVE_DSN cannot be specified with -ARCHIVE_INFILE or -ARCHIVE_OUTFILE. Reason Code 1 -ARCHIVE_DSN & -ARCHIVE_INFILE were both specified. 2 -ARCHIVE_DSN & -ARCHIVE_OUTFILE were both specified. 3 -ARCHIVE_DSN was specified, but the DDNAME that
Configuration Manager 153
would be used to dynamically allocate the dataset is already in the JCL (ARCHIVE_INFILE) 4 -ARCHIVE_DSN was specified, but the DDNAME that would be used to dynamically allocate the dataset is already in the JCL (e.g. ARCHIVE_OUTFILE=ARCHOUT) System Response: Processing is terminated. User Response: Correct the JCL and/or control cards. Invoking module: <ACCMGR>
ZPCM074E
ZPCM074E Input Archive not found: {+54+C+} Explanation: Configuration Manager processing error detected. The specified Archive could not be located on the system. System Response: Processing is terminated. User Response: Check the spelling and catalog status of the Archive. (If cataloged, ensure that it is on the volume shown). Invoking module: <ACCMGR>
ZPCM075E
ZPCM075E -Archive supports tape for -VIEW or -ADD for a new Archive. Use Use -ARCHIVE_INFILE/ARCHIVE_OUTFILE. Explanation: When a tape Archive is to be UPDATED/FRESHENED, use DD statements to access the tape volumes. System Response: Processing is terminated. User Response: Use -ARCHIVE_INFILE/ARCHIVE_OUTFILE in place of -ARCHIVE_DSNAME and re-submit the job. Invoking module: <ACCMGR>
ZPCM076E
ZPCM076E -Archive DSN is in use by another job. {+54+C+} Explanation: Configuration Manager processing error detected. The Archive could not be allocated.
Configuration Manager 154
System Response: Processing is terminated. User Response: Free the dataset from the owning job/user and re-submit. Invoking module: <ACCMGR>
ZPCM077E
ZPCM077E -Archive DSN could not be allocated. {+54+C+} Explanation: Configuration Manager processing information. The Archive could not be allocated. System Response: None User Response: See the associated dynamic allocation return code. Invoking module: <ACCMGR>
ZPCM078E
ZPCM078E -Archive specified PDS without a valid member {+54+C+} Explanation: Configuration Manager processing information. An ARCHIVE PDS/PDSE was specified, but no member was provided, or a -FRESHEN was requested and the specified member does not exist. System Response: Processing is terminated. User Response: Specify which member is desired as the Archive. If performing an action that requires an existing Archive, ensure that the member exists. Invoking module: <ACCMGR>
ZPCM079E
ZPCM079E An input Archive may not be specified for ZIPFORMAT(XTAPE) processing. Explanation: ARCHIVE_ZIPFORMAT Enhanced Tape format is supported only for new archive creation. System Response: Processing is terminated. User Response: Remove the ARCHIVE_INFILE specification Invoking module: <ACCMGR>
Configuration Manager 155
ZPCM088E
ZPCM088E TEMPFILE Allocation error FMCB: +8+H+ +54+C+ Explanation: Configuration Manager processing error indication. Allocation of the TEMPFILE spill dataset failed. System Response: None User Response: Examine other SYSPRINT and JOBLOG messages for an indication of the reason for the failure. If necessary, use -TRACE_DYNALLOC(I) to obtain system IKJ (DYNALLOC) messages. Ensure that the TEMP_... specifications are correct for VOLUME, SPACE and SMS controls so that the file can be allocated. Invoking module: <ACCMGR>
ZPCM089E
ZPCM089E TEMPFILE Open/Read/Write error FMCB: +8+H+ +54+C+ Explanation: Configuration Manager processing error indication. I/O to the TEMPFILE spill dataset failed. System Response: None User Response: Examine other SYSPRINT and JOBLOG messages for an indication of the reason for the failure. If necessary, use -TRACE_DYNALLOC(I) to obtain system IKJ (DYNALLOC) messages. Ensure that the TEMP_... specifications are correct for VOLUME, SPACE and SMS controls so that the file can be allocated. Note: If -MULTI_THREAD_LIMIT(1) is specified, then //TEMPFILE DD may be specified in the JCL to provide the spill storage space. DCB=(DSORG=PS,RECFM=U,LRECL=27998,BLKSIZE=27998) Unpredictable results will occur if -MULTI_THREAD_LIMIT is greater than 1 and //TEMPFILE is used. Invoking module: <ACCMGR>
Configuration Manager 156
ZPCM090E
ZPCM090E Error processing CertStore Configuration command. Reason=+8+D+ Explanation: Configuration Manager processing error indication. The Certificate Store Configuration command could not be processed. The Reason codes are as follows: 1 - The combined parameter set exceeds the internal buffer size. 2 - Syntax error: End brace "}" missing 3 - Syntax error: Unrecognized command keyword System Response: Processing is terminated. User Response: Correct the parameter set. Invoking module: <ACCMGR>
ZPCM100I
ZPCM100I Configuration Manager Shutdown. Posting Main Task: +8+C+ Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued upon the startup of the Configuration manager sub-task. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM101W
ZPCM101W Command is locked in ACZDFLT - RC=4 Explanation: The system administrator has locked this command. System Response: The command is ignored, and the return code is set to 4. User Response: Either remove the command, or contact your system administrator to unlock the command. -PKSUPPRC(ZPCM101W) may be coded to suppress the return code associated with this condition. Invoking module: <ACCMGR>
Configuration Manager 157
ZPCM102E
ZPCM102E Input and output archives reference the same file. RC=8 Explanation: The input and output archive definitions reference the same file. Archives cannot be updated 'inplace', as writing the output would overlay the input. System Response: The ZIP run is terminated with return code 8. User Response: If using -ARCHIVE_DSN and -ARCHINDD, -ARCHIVE_DSN must specify a different data set. If using -ARCHINDD and -ARCHOUTDD, -ARCHOUT_DD must specify a different data set. To update an archive without generating a new file, use -ARCHIVE_DSN only. Invoking module: <ACCMGR>
ZPCM132W
ZPCM132W HFS file request not found: +80+C+ Explanation: A ZIP request for z/OS UNIX files was made, but no files could be located by the specified filename mask. System Response: The file will not be processed. User Response: None Invoking module: <ACCMGR>
ZPCM133I
ZPCM133I +9+C+ File +54+C+ Explanation: This message indicates that a file was to be excluded from processing based on run-time settings. System Response: The file will not be processed. User Response: None Invoking module: <ACCMGR>
ZPCM193W
ZPCM193W TT3686 ALERT! ICSF HCR7730 REQUIRES MAINTENANCE FOR AES128 HARDWARE CRYPTOGRAPHY
Configuration Manager 158
Explanation: During initialization for FACILITY_ENCRYPTDATA a system maintenance check determined that ICSF requires maintenance to operating properly with AES128 hardware-based encryption. IBM has identified PTF UA22474 as being required for ICSF AES128. Other key lengths or algorithms do not introduce the error condition. However, other cryptographic service jobs concurrently running other CPACF-enable algorithms (e.g. DES/3DES) may be affected adversely. APAR OA13766 "When running multiple CSNBSYE or CSNBSYD jobs simultaneously on a z9 and using the AES128 rule, you could experience Data loss" System Response: The request will be processed with a warning. RC = 4 is set. Warning: Erroneous encrypted data streams may be generated for individual files in the archive. This can result in errors when attempting to extract the file from the archive. In addition, other cryptographic processes concurrently running in the system can be adversely affected. A verification run with -ACTION(TEST) can be performed to validate the archive data. User Response: 1. Contact your systems programming staff to apply maintenance before using AES128 with IBMHARDWARE. 2. If AES128 is required, avoid using ICSF until maintenance is applied and activated on the system. -FACILITY_ENCRYPTDATA(SECUREZIP) to avoid using 3. Use another algorithm untill ICSF maintenance is applied. (Such as 3DES, AES192 or AES256). Invoking module: <ACCMGR>
ZPCM199I
ZPCM199I Patch Report: Developer fixes included in the current release. Explanation: -ACTION(PATCH_REPORT) will generate this message and a display DUMP of the PATCHID module. Some fixes are supplied in a "patch" format prior to being released in a fully integrated form (either an SMP/E PTF or full library distribution). When a patch is distributed, a modification to the PATCHID module will also accompany it. This patch tracking mechanism
Configuration Manager 159
may be helpful to the PKZIP support staff in performing problem analysis. Note: Not all product modifications are tracked in the PATCHID module. Version/Release information, along with the product generation date is the primary basis for tracking changes to the product. The format of this report may change. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM201T
ZPCM201T <ACCMGR> <SUBFMCB1> Routine Entry. Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM202T
ZPCM202T <ACCMGR> <SUBFMCB2> Routine Entry. Explanation: Configuration Manager processing trace record. This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM203E
ZPCM203E Load of File Translate table {+8+C+} Failed. Explanation: The Load Module as indicated in +8+C+ could not be loaded.
The -TRANSLATE_TABLE_FILEINFO controls which load module
Configuration Manager 160
is to be loaded. This table is required to translate the ZIP Filename(s).
System Response: Processing terminates. User Response: Ensure that the correct translate table as specified
by -TRANSLATE_TABLE_FILEINFO is accessible (e.g. STEPLIB). Contact the person responsible for installation to ensure that the translate table is available on the system.
Invoking module: <ACCMGR>
ZPCM250C
(See ZPCM250I)
ZPCM250I
ZPCM250I Directory/File Search Selection:<%path/files> ZPCM250C %options Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued to reflect requests made to find z/OS UNIX directories and files that meed the %path/files criteria. The second line displays the other selection options that are in effect for the request. For example: "Wild Card Search", "Recursive" or "Non-Recursive", "Ignore Case Sensitivity" or "Case Sensitive" System Response: None. User Response: None. Invoking module: <PKHFSAPI>
ZPCM251E
ZPCM251E Invalid OS Environment - Application fails to support HFS file system. Explanation: While trying to request the User Id information an error code EMVSINITIAL was returned. This indicates a process initialization error or USS not available.
Configuration Manager 161
Ref. getpwuid() System operating parameters may prevent this message from being issued. Instead, the task may be terminated with a SEC6 abend. If RACF is active as the security server, message ICH408I "OMVS SEGMENT NOT DEFINED" will be issued in the job log. Other related Language Environment and UNIX System Services messages may also be issued: "CEE0374C CONDITION=CEE3250C TOKEN=... WHILE RUNNING PROGRAM BPXINLPA " System Response: Processing will be terminated. User Response: Ensure that the user associated with the job has a valid OMVS segment defined. Invoking module: <PKHFSAPI>
ZPCM252I
ZPCM252I Search Found(%nbr files) Bypassed(%nbr bypass) In Error(%nbr in error) RC=%return code Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued to reflect requests made to find z/OS UNIX directories and files. This message summarizes the results. %nbr files - The number of files that met the selection criteria. %nbr bypass - The number of files or directories that were by passed due to permissions or unsupported file types. %nbr in error - The number IO errors that occurred. This might be due to invalid links. See Job Log for more information. %return code - The return code from search request. System Response: None. User Response: None. Invoking module: <PKHFSAPI>
Configuration Manager 162
ZPCM253I
ZPCM253I Selection process [%level] exceeded Maximum Search Depth Level of [%max level] <[%current path]>. Explanation: A request was made to find directories/files with recursion. While searching, the request exceeded the maximum depth of directories that are supported. [%level] - The current depth level of the [%current path] [%max level] - The system's maximum level. Default is 0 or no maximum. [%current path] - The current path that is at the depth level [%level]. System Response: Search Depth stopped at maximum which is [%current path], and search continue at current level. User Response: None. Invoking module: <PKHFSAPI>
ZPCM254E
ZPCM254E Memory request failure RQ(request nbr) (request size) Explanation: Program PKHFSAPI encountered an error when attempting a malloc(). (request nbr) internal request number. (request size) is the number of bytes requested. System Response: Active process request will be terminated. Note: HFS API returns rc=12 to internal calling programs. User Response: Review region size and increase size. If the error continues, contact PKWARE, Inc. with joblog. Invoking module: <PKHFSAPI>
ZPCM255C
(See ZPCM255E)
Configuration Manager 163
ZPCM255E
ZPCM255E File is not a Regular File. [%file type]<%File Name>. ZPCM255C File is treated as Not Found. Explanation: A informational request was made for <%File Name> and it was found, but is not a regular type file. File is treated as if not found. [%file type] - is the file type that was discovered. "Directory", "Symbolic Link", "External Link", or "Mode" if invalid. System Response: None. User Response: Re-Try request with a valid file name. Invoking module: <PKHFSAPI>
ZPCM256E
ZPCM256E An error occurred while reading directory data - errorcode=%errno RC=%returncode. Explanation: A request was made to find directories/files, and while searching the directories and IO error occurred with the directory data. This could occur if someone is changing the contents of the current directory. [%errno] - Error number returned by the readdir_r() function. [%returncode] - results readdir_r() function. System Response: Increment Error Count. Note: HFS API returns rc=8 to internal calling programs. User Response: Re-Try request and if same results occurs, contact PKWARE Technical Support and provide the Return and Reason code information with job log Invoking module: <PKHFSAPI>
Configuration Manager 164
ZPCM257E
ZPCM257E Could not open directory for browse:%reason <%path>. Explanation: A request was made to find directories/files and while searching the directories, an error occurred when opening a directory for searching. Search will continue with next directory. [%reason] - "Insufficient Permissions" or error no returned from opendir() function. [%path ] - directory that could not be browsed. System Response: Increment Error Count. Note: HFS API returns rc=8 to internal calling programs. User Response: Review the [%path ] for authority. If [%path ] looks ok, then contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI>
ZPCM258W
ZPCM258W Selected Directory/File Cannot be Validated. File <%path/file name> will be bypassed. Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued to reflect requests made to find z/OS UNIX Expl directories and files. While searching, an error occurred attempting to gather information for [%path/file name]. This message will occur when when File Error Continue Flag is turned on, otherwise message ZPCM259E is issued. The file will be bypassed and searching will continue. [%path/file name] - path and file name that could be validate with stat() function. System Response: Increment Bypass Count. Note: HFS API returns rc=2 to internal calling programs. User Response: Review the [%path/file name] for validity. If [%path/file name] looks ok, then contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI>
Configuration Manager 165
ZPCM259E
ZPCM259E Selected Directory/File Cannot be Validated. File <%path/file name>. Explanation: A request was made to find directories/files and while searching, an error occurred when trying gather information on [%path/file name]. This message will occur when when File Error Continue Flag is turned off, otherwise message ZPCM258W is issued. The file will be bypassed and searching will stop. [%path/file name] - path and file name that could be validate with stat() function. System Response: Increment Error Count. Note: HFS API returns rc=8 to internal calling programs. User Response: Review the [%path/file name] for validity. If [%path/file name] looks ok, then contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI>
ZPCM260W
ZPCM260W Directory %attribs Permission denied (%IDType): <%path> Explanation: The directory %path is being evaluated and if current user does not have the correct permission to continue with the request. This message indicates that the permission [%attribs] based on [%IDType] is not sufficient to continue. The directory request will be bypassed. [%attribs] - Type permissions required such as: Read, Write, or Execute. [%IDType] - The type used to determine permissions: Owner, Group or Other. [%path] - path that is being evaluated. System Response: Increment Bypass Count. Note: HFS API returns rc=4 to internal calling programs. User Response: Review the [%path] for permissions. Invoking module: <PKHFSAPI>
Configuration Manager 166
ZPCM261E
ZPCM261E File Status Failure occurred in %requester(%error no): <%path/file> Explanation: During an HFS API request, an unexpected failure occurred with a stat() function call for %path/file. [%path/file] - Full path /file that failed request. [%requester] - Internal place holder where call was issued. [%error no] - Internal error number reason for failure. System Response: The file or directory will be treated as 'not found' and processing will continue with other requests. User Response: See other messages that explain return code and actions. Contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI>
ZPCM262E
ZPCM262E Selected Directory does not exist:<%path> Explanation: A informational request is being made for a file in the directory <%path>, but that directory does not exist. [%path] - Full path that is being evaluated. System Response: Increment Error Count. Note: HFS API returns rc=8 to internal calling programs. User Response: Review the [%path] to determine whether it exists. If the requested %path is a symbolic link, verify that the target path (and intermediate links) are defined and mounted. Verify that other processes do not actively remove and redefine the directory. Invoking module: <PKHFSAPI>
Configuration Manager 167
ZPCM263E
ZPCM263E Passed Working Directory does not start with / nor ~/: <%path/file> Explanation: During an HFS API request, the CWD (Current Working Directory) must be fully qualified by starting with a /, or it must start with ~/ (Users home directory). This should not occurred, but may be a result of an internal error. System Response: Request-dependent. See related messages. Note: HFS API returns rc=12 to internal calling programs. Reason Code: 2979 User Response: Contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI>
ZPCM265E
ZPCM265E Get %uidnbr UID information failed. Error(%error nbr) Explanation: During an HFS API request while trying to retrieve information for the User ID Number %uidnbr, an error occurred. HFS API request fails immediately. [%uidnbr] - User ID (UID) number. See UNIX System Services. [%error nbr] - Error number returned from getpwuid() function. If UNIX system is correct this should not occur. System Response: Request-dependent. See surrounding messages. Note: HFS API returns rc=12 to internal calling programs. Reason Code: 2985 User Response: Contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI>
Configuration Manager 168
ZPCM266W
ZPCM266W Selected PATH/File name exceeds 255 bytes. File will be bypassed. <%path/file name> Explanation: A request was made to find directories/files and while searching, a path/file was found where the full path name exceeds the 255 character restriction for allocation. [%path/file name] - The full path and file name that that exceeds 255 bytes. Note: System allocation via JCL PATH or DYNALLOC PATH limits accessibility to a fully qualified absolute path/file name to 255 characters. System Response: Increment Bypass Count. Note: HFS API returns rc=2 to internal calling programs. User Response: Rename the full path and file name to be less than 255 bytes. Invoking module: <PKHFSAPI>
ZPCM267E
ZPCM267E Some Directories cannot be created: <%mkdir path> Explanation: A request was made to inquire about the paths and file name with the "Create Paths Option" on. If any node in the full path does not exist, a mkdir() function call will be performed. While attempting to create one or more directories, an error occurred resulting in an incomplete path. [%mkdir path] - The path of the directory that is trying to be created. The lowest level directory is the one that could not be created. This condition can be raised when insufficient permissions are available in the previous directory level into which the target mkdir() directory is to be created. System Response: Request-dependent. See surrounding messages. Note: HFS API returns rc=12 to internal calling programs. User Response: Review all previous messages in the jog log to help diagnose the failure.
Configuration Manager 169
Invoking module: <PKHFSAPI>
ZPCM268I
ZPCM268I Directory Created:<%path name> Explanation: A request was made to inquire about the paths and file name with the "Create Paths Option" on. If any node in the full path does not exist, a mkdir() function call will be performed. This message informs that the path was created in this run. %path name - The Full path name that was just created. When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued. System Response: None. User Response: None. Invoking module: <PKHFSIOU>
ZPCM269W
ZPCM269W Insufficient (RACF) Permissions:<%path name> Explanation: A informational request is being made for directory <%path>, but the user does not have RACF permissions to the directory. [%path name] - Full path that is being evaluated. System Response: Increment Bypass Count for ZIP data file search requests. Note: HFS API returns rc=4 to internal calling programs. If this is for a new file allocation, the request is terminated. Note: HFS API returns rc=8 to internal calling programs. User Response: Review following message to evaluate system response. Contact your System's Administrator for HFS file Authorizations.
Configuration Manager 170
Invoking module: <PKHFSAPI>
ZPCM270E
ZPCM270E Remote File System Connection has Timed Out:<%path name> Explanation: An HFS request is being made to a directory <%path name> that is defined as a remote file system. While servicing the request, the remote system has exceeded the Timeout limit. [%path name] - Full path that is being processed. ZPCM270W may be issued in lieu of this message if run-time settings permit toleration of file access errors. System Response: Increment Error Count. Note: HFS API returns rc=8 to internal calling programs. User Response: Review the remote file system connections. Invoking module: <PKHFSAPI>
ZPCM270W
ZPCM270W Remote File System Connection has Timed Out:<%path name> Explanation: An HFS request is being made to a directory <%path name> that is defined as a remote file system. And while trying to service the request, the remotes system has exceeded the Timeout limit. [%path name] - Full path that is being processed. Message ZPCM270E will be issued in lieu of this message when run-time settings specify that file access errors should terminate processing. System Response: Increment Bypass Count. Note: HFS API returns rc=2 to internal calling programs. User Response: Review all messages to determined if there will be any missing items from the request. Review the remote file system connections.
Configuration Manager 171
Invoking module: <PKHFSAPI>
ZPCM271W
ZPCM271W Symbolic Filtered <%path/file name> Explanation: An HFS request is being made to a directory <%path name> that is defined as a symbolic link and the symbolic filter ON to validate with lstat(). [%path/file name] - Full path that is being processed. Note: Only valid when running in Symbolic Mode which is internally defined. System Response: Increment Bypass Count. Note: HFS API returns rc=2 to internal calling programs. User Response: none. Invoking module: <PKHFSAPI>
ZPCM272E
ZPCM272E <%path/file name> No permission for file attribute changes: <%changes> Explanation: An HFS request is being made to change the attributes to <%path/file name>, but has failed due to lack of permission to make the changes. [%path/file name] - Full path that is being processed. [%changes ] - List of attributes to change. i.e. Mode Change, Owner Change, File Format Change, and/or File Tag Change. System Response: Request-dependent. See surrounding messages. Note: HFS API returns rc=8 to internal calling programs. Reason Code 2978. User Response: See your System's Administrator for authority. Invoking module: <PKHFSAPI> <PKHFSIOU>
Configuration Manager 172
ZPCM273C
(See ZPCM273E)
ZPCM273E
ZPCM273E <%path/file name> Invalid file attribute change requested: ZPCM273C <%changes> Explanation: An HFS request is being made to change the attributes to <%path/file name>, but one of the attributes combinations caused the __chattr() function to fail. [%path/file name] - Full path that is being processed. [%changes ] - List of attributes to change. i.e. Mode Change, Owner Change, File Format Change, and/or File Tag Change. System Response: Request-dependent. See surrounding messages. Note: HFS API returns rc=8 to internal calling programs. Reason Code 2978. User Response: See your System's Administrator for authority and review changes requested. Invoking module: <PKHFSAPI> <PKHFSIOU>
ZPCM274I
ZPCM274I PKERRS summary cmd(%func) err<%errornbr-%errdecp> <%path/file> Explanation: During an HFS API request an error was receive on a function This message is used with verbose to provide more information to help analyze the condition. [%func] - Function which received error. [%path/file] - path/file involved in error. [%errornbr] - Error number returned from function. [%errdecp] - Error description for %errornbr. System Response: None. User Response: Review job log and previous errors for more information.
Configuration Manager 173
Invoking module: <PKHFSAPI>
ZPCM275I
ZPCM275I User Name<%usrname> UID(%uidnbr) GID(%gidnbr) Dir<%homedir> Shell<%unixshell> Explanation: An HFS API request was issued with the Show Setting Option ON. The following information for the run-time user is shown: [%usrname] - UNIX User name (system USERID) [%uidnbr] - User ID number. [%gidnbr] - Group ID number. [%homedir] - User Home directory. [%unixshell] - Initial user program. System Response: None. User Response: None. Invoking module: <PKHFSAPI>
ZPCM276C
(See ZPCM276I)
ZPCM276I
ZPCM276I The following is the list of %nbr supplementary groups: ZPCM276C %seq %groupname (%gidnbr) Explanation: An HFS API request was issued with the Show Setting Option ON. Information Only message about current user. [%nbr] - The number of groups that the user is associated with. [%seq] - Sequence number of group/line number. [%gidnbr] - Group ID number. [%groupname]- Group external name. System Response: None.
Configuration Manager 174
User Response: None. Invoking module: <PKHFSAPI>
ZPCM277I
ZPCM277I Current umask settings %hexmask Octal(%octmask) attr<%attr> Explanation: An HFS API request was issued with the Show Setting Option ON. Information Only message about current umask settings. [%hexmask] - The hexadecimal mode setting of bits that will be masked. [%octmask] - The Octal mode setting of bits that will be masked. [%attr] - external representation of what is being masked. For Example a standard system setting is Octal 022 to mask out the write permission for Group and Other. This would be represented in the message as: "Current umask settings 0x0012 Octal(022) attr<----w--w->" System Response: None. User Response: None. Invoking module: <PKHFSAPI>
ZPCM278I
ZPCM278I Override umask settings %hexmask Octal(%octmask) attr<%attr> Explanation: An HFS API request was issued with the Show Setting Option ON and there was an envirnoment override for umask using the key word _EDC_UMASK_DFLT. Information Only message about current umask changes. [%hexmask] - The hexadecimal mode setting of bits that will be masked. [%octmask] - The Octal mode setting of bits that will be masked. [%attr] - external representation of what is being masked. For Example a standard system setting is Octal 022 to
Configuration Manager 175
mask out the write permission for Group and Other. This would be represented in the message as: "Override umask settings 0x0012 Octal(022) attr<----w--w->" System Response: None. User Response: None. Invoking module: <PKHFSAPI>
ZPCM281E
ZPCM281E Cannot find ZIP64 End Central Signature Offset=%offset, Len=%rtnlen Explanation: A request was made to access the End Central Directory of an archive. While positioning in the archive a ZIP64 End Central Locator record was found with the offset of [%offset] to the ECREC. The End Central Signature could not be located at that offset. [%offset] - offset to ZIP64 End Central Signature [%rtnlen] - Maximum length return on file read request System Response: HFS API returns 8 to calling programs. No pointer to End Central Directory User Response: Verify that the file is an actual and valid archive. Invoking module: <PKHFSAPI><PKHFSGCD>
ZPCM282E
ZPCM282E Found ZIP64 End Central Signature but Invalid. Len(ecs=%ecslen fnd=%rtnlen) Explanation: A request was made to access the End Central Directory of an archive. The End Central Signature record has a length of %ecslen in the record but the read request could only return %rtnlen bytes. [%ecslen] - Length found in the End Central Signature [%rtnlen] - Maximum length return on file read request System Response: HFS API returns 8 to calling programs. No pointer to End Central Directory User Response: Verify that the file is an actual and valid archive.
Configuration Manager 176
Invoking module: <PKHFSAPI><PKHFSGCD>
ZPCM283E
ZPCM283E Central Directory NOT found at Offset=%offset. Len(fnd=%rtnlen) Explanation: A request was made access the End Central Directory of an archive. It was determined that the Central Directory should start at offset [%offset]. At that offset there is no Central Directory signature. [%offset] - offset to start of Central Directory [%rtnlen] - Maximum length return on file read request System Response: HFS API returns 8 to calling programs. No pointer to End Central Directory User Response: Verify that the file is an actual and valid archive. Invoking module: <PKHFSAPI><PKHFSGCD>
ZPCM284E
ZPCM284E Could not position to Central Directory at Offset=%offset. Explanation: A request was made access the End Central Directory of an archive. The API could not get the [%offset] in the archive. This could be file access problem or an invalid archive file. This error should not occur at this point in the accessing process. [%offset] - offset to start of Central Directory System Response: HFS API returns 8 to calling programs. No pointer to End Central Directory User Response: Verify that the file is an actual and valid archive. Contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI><PKHFSGCD>
Configuration Manager 177
ZPCM285E
ZPCM285E Could not find or position to archive offset=%offset. Explanation: A request was made access the End Central Directory of an archive. While trying to position to an HFS archive Central Directory, the file buffer IO routine could position to the %offset position in the file. This error should no occur. This may be an internal error. [%offset] - offset to ZIP64 End Central Signature System Response: HFS API returns 8 to calling programs. No pointer to End Central Directory User Response: Verify that the file is an actual and valid archive. Contact PKWARE Technical Support and provide the Return and Reason code information along with the job log. Invoking module: <PKHFSAPI><PKHFSGCD>
ZPCM286E
ZPCM286E End Central Record was NOT Found. Explanation: An attempt was made to access the End Central Directory record found at the end of an archive. After positioning to the end of the archive, the ZIP End Central Record could not be located. The most likely occurrence of this error is that the archive file is incomplete. System Response: HFS API returns 8 to calling programs. No pointer to End Central Directory User Response: Verify that the file is an actual and valid archive. The ZIP End Central Record has a signature of x'504B0506'. Invoking module: <PKHFSAPI><PKHFSGCD>
ZPCM290I
ZPCM290I HFS Open:Blocksize(%blsz) fm_status<%st> Opt<%opt> file<%flnm> RC=%rc
Configuration Manager 178
Explanation: An HFS OI request was issued to open an HFS File. This message displays the status info used to open the file name %flnm. [%blsz] - The Maximum blocksize used for HFS IO processing. [%st] - An Internal FMCB Status Byte. Used to diagnose allocations of File. [%opt] - Open Options used to open the HFS File. If type=record then file is in NL Text mode, otherwise it will be processed in stream mode. [%flnm] - The full path and file name that was opened. [%rc] - Internal return code for the open API. Should be 0. System Response: None. User Response: None. Invoking module: <PKHFSIOR>
ZPCM291I
ZPCM291I HFS Close Statistics:File Nbr IOs=%ios Bytes=%byts, Max Record Len=%recln Explanation: An HFS OI request was issued to close an HFS File. This message displays the statistics that were occurred while processing current HFS file. [%IOs] - The number of Reads or Writes that occurred. [%byts] - The total number of bytes that were read or written. [%recln] - The maximum record length read or written on the HFS File. System Response: None. User Response: None. Invoking module: <PKHFSIOR>
Configuration Manager 179
ZPCM292E
ZPCM292E HFS Open (%io) Error:File<%flnm> Opt<%opt> error(%errno) Explanation: An HFS OI request was issued to open an HFS File and the open encountered a failure. See ZPFM112I for more details. [%io] - Type of Open. "Input" or "Output" [%flnm] - The full path and file name that was being opened. [%opt] - Open Options used to open the HFS File. If type=record then file is in NL Text mode, otherwise it will be processed in stream mode. [%errno]- Internal return code errno define reason code. Message ZPFM112I will be issued which will describe in text the reason. System Response: Processing for the specified file is terminated. User Response: Check SYSPRINT and the JOBLOG for other error indications. Invoking module: <PKHFSIOR>
ZPCM900I
ZPCM900I +121+C+ Explanation: A processing-dependent informational message. "Candidate DSN/Members thus far." Issued in conjunction with ZPCM950E to indicate how far setup has proceeded with locating files for subsequent processing. System Response: No action based on this message. User Response: See related error or warning messages. Invoking module: <ACCMGR>
ZPCM900T
ZPCM900T +121+C+ Explanation: Configuration Manager processing trace record.
Configuration Manager 180
This line is only issued when Configuration Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCMGR>
ZPCM901E
ZPCM901E -INCLUDE_CMD did not reference a PDS or PDSE. Explanation: Configuration Manager processing error detected. -INCLUDE_CMD supports PDS and PDS/E members. (This does not include OEM subsystems) System Response: Processing is terminated. User Response: Remove the -INCLUDE_CMD command referencing the subsystem, or use a PDS/PDSE for PARMLIB. Invoking module: <ACCMGR>
ZPCM902E
ZPCM902E -INCLUDE_CMD member could not be +12+C+: +54+C+ Explanation: Configuration Manager processing error detected. -INCLUDE_CMD supports PDS and PDS/E members. The requested member could not be processed. +12+C+ specifies a reason as follows: FOUND - The member could not be located ALLOCATED - A DYNALLOC failure occurred. OPENED - OPEN failed. PROCESSED - An I/O error occurred reading the member System Response: Processing is terminated. User Response: Check the DARC if the DYNALLOC request failed. Verify that the correct data set member exists. Check the JOB log for OPEN error reasons. Invoking module: <ACCMGR>
ZPCM950E
ZPCM950E Insufficient Virtual Storage to handle the file request.
Configuration Manager 181
Explanation: Configuration Manager processing error detected. While performing setup for file processing there was insufficient virtual storage to continue processing the request. Message ZPCM900I will be issued to indicate the number of files that have been selected to this point in the processing. This number can be helpful in determining an adjustment to be performed (see User Response below). Message ZPGE001I will be issued to indicate the amount of virtual storage remaining at the point of failure. System Response: Processing is terminated. User Response: One of more of the following actions may be taken. 1. Specify a larger REGION size 2. If MEMORY_MODEL=LARGE was used, specify MEDIUM 3. Reduce the number of data sets/member requests. 4. Be more specific regarding the data set/member requests rather than using generic filters which may identify unnecessary files for processing. If an identification of which files have been identified thus far is required, use the command -TRACE_CMGR=1 and review message ZPCM070T. Invoking module: <ACCMGR>
Compression Manager 182
ZPCO - Compression Manager Messages
ZPCO060T
ZPCO060T Work Directive: +80+C+ Explanation: Compression Manager processing trace record. This line is only issued when Compression Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPCO070T
ZPCO070T CACHEMEMORY limit reached - FMCB: +8+H+ +54+C+ Explanation: Compression Manager processing trace record. This line is only issued when Compression Manager tracing is turned on. System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPCO071I
ZPCO071I CACHE SHORTAGE +8+C+ - Limit=+8+D+K Current=+8+D+K Queues{IN=+8+D+K PROCESS=+8+D+K ARC=+8+D+K} Explanation: Compression Manager detected a change in virtual storage usage. "CACHE SHORTAGE DETECTED" The amount of virtual storage currently allocated for holding input, transient ZIP data and queued buffers for the output archive has exceeded the DATA_STORAGE threshhold. This is commonly a temporary condition, caused by a pending tape mount for the output archive, whereby the queued output buffers accumulate. "CACHE SHORTAGE RELIEVED"
Compression Manager 183
The temporary virtual storage shortage is no longer in effect. Limit=+8+D+K A decimal value of the number of kilobytes of virtual storage that is being used as the threshhold for monitoring. The -DATA_STORAGE setting is used to govern this value, and may be dynamically modified to fit processing requirements. Current=+8+D+K A decimal value of the number of kilobytes of virtual storage currently allocated. Queues{IN=+8+D+K PROCESS=+8+D+K ARC=+8+D+K} A breakdown of the internal storage queues that comprise the currently allocated virtual storage value. IN - The current inbound buffer queue PROCESS - The current set of buffers currently being processed. ARC - The current set of buffers queued to be written to the archive. System Response: For "DETECTED", the ZIP process will wait for the storage shortage to be relieved before reading any additional data for processing. User Response: When the ARC queue size appears to be the cause of the shortage, no action is required. A very large DATA_STORAGE setting will permit more data to be processed by ZIP compression/encryption and held in virtual storage, thereby reducing some elapsed time. However, the large setting will place a greater demand on system paging resources (Local Aux storage). Invoking module: <ACCOMAIN>
ZPCO080E
ZPCO080E TEMPFILE Allocation error FMCB: +8+H+ +54+C+ Explanation: Compression Manager processing error indication. During Compression processing with PKZIP, the compressed data is kept in virtual storage until the DATA_STORAGE limit is exceeded. (This is dynamically computed and varies from run to run based on the multi-tasking level, the number of files processed and the timing of I/O in the job). Once, the DATA_STORAGE limit is exceeded, then the compressed data is spilled into a temporary file. This file is dynamically allocated by PKZIP by using the -TEMP_... commands.
Compression Manager 184
Allocation of the TEMPFILE spill dataset failed. System Response: None User Response: Examine other SYSPRINT and JOBLOG messages for an indication of the reason for the failure. If necessary, use -TRACE_DYNALLOC(I) to obtain system IKJ (DYNALLOC) messages. Ensure that the TEMP_... specifications are correct for VOLUME, SPACE and SMS controls so that the file can be allocated. Note: If -MULTI_THREAD_LIMIT(1) is specified, then //TEMPFILE DD may be specified in the JCL to provide the spill storage space. DCB=(DSORG=PS,RECFM=U,LRECL=27998,BLKSIZE=27998) Unpredictable results will occur if -MULTI_THREAD_LIMIT is greater than 1 and //TEMPFILE is used. Invoking module: <ACCOMAIN>
ZPCO081E
ZPCO081E Translate table +8+C+ could not be loaded. Explanation: Compression Manager processing error detected. Text translation was going to be done for the file data, but the translate table specified by TRANSLATE_TABLE_DATA could not be loaded. System Response: ZIP processing for the file is terminated. User Response: Verify that the specified translate table module is in the JOBLIB/STEPLIB for the job. Invoking module: <ACCOMAIN>
ZPCO082E
ZPCO082E Text/Binary detection table +8+C+ could not be loaded. Explanation: Compression Manager processing information. -DATA_TYPE(DETECT) had been specified, so the Compression Manager attempted to determine whether the data is binary or text. The load module table specified by -DATATYPE_DETECT_TABLE could not be loaded. System Response: Processing for the file is terminated.
Compression Manager 185
User Response: Determine the correct table to be loaded. Invoking module: <ACCOMAIN>
ZPCO083W
ZPCO083W File in use by another job: +54+C+ Explanation: During ZIP processing, the file listed was found to be allocated to another job or user. System Response: Continued processing depends on the value set for ON_FILE_ACCESS_ERROR. User Response: -Identify the job or user who has the file allocated and free it before running the ZIP request. -Use ON_FILE_ACCESS_ERROR(TOLERATE) to bypass the error and continue with other files. -Remove this file from the ZIP request. Invoking module: <ACCOMAIN>
ZPCO084W
ZPCO084W TEMPFILE I/O error FMCB: +8+H+ +54+C+ Explanation: Compression Manager processing error indication. During Compression processing with PKZIP, the compressed data is kept in virtual storage until the DATA_STORAGE limit is exceeded. (This is dynamically computed and varies from run to run based on the multi-tasking level, the number of files processed and the timing of I/O in the job). Once, the DATA_STORAGE limit is exceeded, then the compressed data is spilled into a temporary file. This file is dynamically allocated by PKZIP by using the -TEMP_... commands. An output operation to the TEMPFILE spill dataset failed. System Response: Processing of the active file is terminated. User Response: Examine other SYSPRINT and JOBLOG messages for an indication of the reason for the failure. A likely problem scenario is insufficient space being allocated to the TEMPFILE.
Compression Manager 186
Ensure that the TEMP_... specifications are correct for VOLUME, SPACE and SMS controls so that the file can be allocated. Note: If -MULTI_THREAD_LIMIT(1) is specified, then //TEMPFILE DD may be specified in the JCL to provide the spill storage space. DCB=(DSORG=PS,RECFM=U,LRECL=27998,BLKSIZE=27998) Unpredictable results will occur if -MULTI_THREAD_LIMIT is greater than 1 and //TEMPFILE is used. Invoking module: <ACCOMAIN>
ZPCO085E
ZPCO085E Input file > 4-gigabyte limit for a standard Archive. GZIP may be used. Explanation: Compression Manager processing error detected. | Unless licensed for Large File Support, a standard ZIP Archive has a 4-gigabyte limitation for input file size. This is because a 4-byte unsigned fields in the Archive directory is used to hold file size information. While accessing the input file for processing, the Compression Manager detected a 4-gigabyte overflow. | Large File Support expands the size variables to 64-bits | allowing > 4 gigabytes of data to be compressed. System Response: Processing for the file is terminated. User Response: -GZIP may be used to create a Zip file with a dataset that exceeds 4-gigabytes. Be aware that a GZIP output file is limited to 1 input file. Invoking module: <ACCOMAIN>
ZPCO095I
ZPCO095I HFS/FIFO is about to be opened for processing: +54+C+ Explanation: During ZIP processing, the file about to be opened was detected to be a FIFO Special File (named PIPE). The OPEN will only complete for this type of file when a partner process also opens the file for output. System Response: Attempt to OPEN the specified FIFO Special File. Note: The OPEN will WAIT indefinitely until a partner process opens the file for output, a system
Compression Manager 187
WAIT time limit is exceeded, or the process is cancelled. User Response: -Ensure that a partnering process performs an OPEN for OUTPUT to the named PIPE file. Invoking module: <ACCOMAIN>
ZPCO100I
ZPCO100I Compression Task {+3+D+} TCB: +8+H+ Started. Explanation: When -TRACE_GENERAL=1 is specified, this message will be issued upon the startup of a Compression manager sub-task. Note: In z/OS, more than one instance of this task (and message) may be generated. The number of compression tasks is controlled by -MULTI_THREAD_LIMIT System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPCO101I
ZPCO101I Compression Task {+3+D+} TCB: +8+H+ shutdown begun. Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued upon the shutdown of each Compression manager sub-task. System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPCO109I
ZPCO109I Compression Task {+3+D+} TCB: +8+H+ shutdown complete. Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued upon the shutdown of each Compression manager sub-task.
Compression Manager 188
System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPCO110I
ZPCO110I Exceeded Binary threshold (+3+C+%). +50+C+ Explanation: Compression Manager processing information. -DATA_TYPE(DETECT) had been specified, so the Compression Manager attempted to determine whether the data is binary or text. The number of binary bytes for the sample taken exceeds that allowed by TEXT_PERCENT. See also: -DATATYPE_DETECT_DEPTH -DATATYPE_TEXT_PERCENT -DATATYPE_DETECT_TABLE System Response: The file is treated as BINARY. User Response: None Invoking module: <ACCOMAIN>
ZPCO111I
ZPCO111I +10+C+ Records processed for +54+C+. Explanation: Compression Manager processing information. When LOGGING_LEVEL=VERBOSE is specified, this message will be issued on a periodic basis as a progress bar for ZIP processing. This is useful for long running jobs with very large files. System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPCO900T
ZPCO900T +121+C+ Explanation: Compression Manager processing trace record. This line is only issued when Compression Manager
Compression Manager 189
tracing is turned on. System Response: None User Response: None Invoking module: <ACCOMAIN>
ZPCO999E
ZPCO999E INVALID INTERNAL DIRECTIVE: +80+C+ Explanation: Compression Manager processing error detected. System Response: None User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACCOMAIN>
Common Service 190
ZPCS - Common Service Messages
ZPCS010W
ZPCS010W Define Cluster requires either VOLUMES or STORCLASS. Explanation: Access Method Services requires that volume control information be provided for a DEFINE CLUSTER. When a data set is under DFSMS control, then ARCHIVE_STORCLASS can be used. Otherwise, ARCHIVE_VOLUMES should be specified. System Response: In cases when ARCHIVE_STORCLASS has been specified, but the data set is not DFSMS managed, then Access Method Services will issue IDC3506I indicating that a volume specification is required. User Response: Provide the appropriate volume information. Invoking module: <ACCSAMS>
ZPCS100T
ZPCS100T CCSERV1 Started: MTVT=%p TMCB=%p TCB=%p Explanation: Some processing requests require a C Service subtask to perform the necessary operations. When -TRACE_CSERV >= 1, this message is issued by the C Service task when it initializes. This information may be used by PKWARE support when performing problem analysis. System Response: Processing continues. User Response: No action required. Invoking module: <CCSERV1>
ZPCS121E
ZPCS121E fetch CSBSAUTH/PKiAUTH FAILED Explanation: Digital Signature processing requires that module CSBSAUTH be loaded by the C Service task. The module could not be loaded.
Common Service 191
System Response: Processing for the function is terminated. User Response: Check the job log for associated system errors to determine the reason for the load failure. (For example, an Abend 106-C indicates that the region size must be increased). Invoking module: <CCSERV1>
ZPCS200I
ZPCS200I Opening %s1 (%s2) Explanation: SecureZIP is attempting to access the Local Certificate Store database to resolve a recipient specification or View detail information. %s1 Indicates which of the following database access points is being opened: Path Type Default VSAM Path ====================== ======================= - Common Name DB Index PKZIP.CERTSTOR.PATHCN - Email Address DB Index PKZIP.CERTSTOR.PATHEM - Public Key DB Index PKZIP.CERTSTOR.PATHPUBK %s2 Shows the VSAM path being used for the open in accordance with the active Certificate Store profile. System Response: Processing continues. User Response: No action is necessary unless an open error follows. (See ZPCS201W, ZPCS202W, ZPCS203W) Invoking module: <CCSERV1>
ZPCS201W
ZPCS201W fopen(%s) for Common Name Index failed. Explanation: SecureZIP could not access the Local Certificate Store database to resolve a recipient specification or View detail information. %s Shows the VSAM path being used for the open in accordance with the active Certificate Store profile. Preceding message ZPCS200I shows which path type was being attempted. System Response: The functions requiring information will be bypassed.
Common Service 192
User Response: -Determine whether the path type specified in ZPCS200I was configured correctly. -Ensure that the correct Local Certificate Store profile is being used. Invoking module: <CCSERV1>
ZPCS202W
ZPCS202W fopen(%s) for Email Index failed. Explanation: SecureZIP could not access the Local Certificate Store database to resolve a recipient specification or View detail information. %s Shows the VSAM path being used for the open in accordance with the active Certificate Store profile. Preceding message ZPCS200I shows which path type was being attempted. System Response: The functions requiring information will be bypassed. User Response: -Determine whether the path type specified in ZPCS200I was configured correctly. -Ensure that the correct Local Certificate Store profile is being used. Invoking module: <CCSERV1>
ZPCS203W
ZPCS203W fopen(%s) for Public Key Hash Index failed. Explanation: SecureZIP could not access the Local Certificate Store database to resolve a recipient specification or View detail information. %s Shows the VSAM path being used for the open in accordance with the active Certificate Store profile. Preceding message ZPCS200I shows which path type was being attempted. System Response: The functions requiring information will be bypassed. When requesting an Archive View, the information about each recipient cannot be shown. User Response: -Determine whether the path type specified in ZPCS200I
Common Service 193
was configured correctly. -Ensure that the correct Local Certificate Store profile is being used. Invoking module: <CCSERV1>
ZPCS211I
ZPCS211I DB: %s key not found. Explanation: SecureZIP could not locate an entry in the Local Certificate Store database. %s Shows the type of key being used in the lookup attempt. "Common Name" - As requested in RECIPIENT command "Email Addr." - As requested in RECIPIENT command "Public Key " - Used during VIEW processing to correlate the certificate public key (as held in the Archive) to an installed certificate in the local Certificate Store. System Response: Processing dependent User Response: -Ensure that the correct Local Certificate Store profile is being used. User -Ensure that all available certificates for intended recipients are installed in the Local Certificate Store. Invoking module: <CSCERTDB>
ZPCS212I
ZPCS212I DB: Suspended certificate bypassed: %s Explanation: SecureZIP found that a Certificate Store Administrator has marked this certificate as "Suspended". %s Shows the physical path of the associated certificate. System Response: The certificate is not included in the request. User Response: -If the certificate is required for processing, contact the Certificate Store Administrator to have the User certificate unsuspended. Invoking module: <CSCERTDB>
Dynamic Allocation 194
ZPDA - Dynamic Allocation Messages
ZPDA000I
ZPDA000I +121+C+ Explanation: The DYNALLOC service routine (SVC99) was invoked to perform a dynamic allocate/unallocate for a data set, DD, or HFS PATH. An intpretation of the SVC99 parameters is displayed when the appropriate level of TRACE_DYNALLOC is set. The parameters displayed are specific to the type of data set, DD or file being accessed. The following table lists the SVC99 Text Unit values and their associated interpretation for this message. Ref. IBM z/OS MVS Authorized Assembler Services Guide; "SVC 99 Paramter List Verb Codes and Text Units" 0001 - DDNAME 0002 - DSNAME 0003 - MEMBER 0004 - DISP_STATUS X'01'- OLD X'02'- MOD X'04'- NEW X'08'- SHR 0005 - DISP_NORMAL X'01'- UNCATLG X'02'- CATLG X'04'- DELETE X'08'- KEEP 0006 - DISP_ABNORMAL 0007 - SPACE_TYPE=TRK 0008 - SPACE_TYPE=CYL 0009 - SPACE_TYPE=BLK 000A - SPACE_PRIMARY 000B - SPACE_SECONDARY 000C - SPACE_DIRBLKS 000D - SPACE_RLSE=Y 000E - INFO_ALCFMT 0010 - VOLUMES 0013 - MAXVOL 0015 - UNIT 0024 - SYSOUT 001C - FREE=CLOSE 0024 - DD DUMMY 0030 - BLKSIZE 003C - DSORG 0042 - LRECL
Dynamic Allocation 195
0049 - RECFM 0055 - DDNAME_RETURN 0056 - DSNAME_RETURN 8004 - SMS_STORCLASS 8005 - SMS_MGMTCLASS 8006 - SMS_DATACLASS 8012 - PDSE/LIBRARY 8017 - HFS_PATHNAME Specify absolute PATH 8018 - HFS_PATHOPTS Binary PATHOPTS flags: (SET) X'00000100' OSYNC X'00000080' OCREAT X'00000040' OEXCL X'00000020' ONOCTTY X'00000010' OTRUNC X'00000008' OAPPEND X'00000004' ONONBLOCK X'00000003' ORDWR X'00000002' ORDONLY X'00000001' OWRONLY 8019 - HFS_PATHMODE Four-byte HEX integers: (SET) X'00000800' SISUID X'00000400' SISGID X'00000100' SIRUSR X'00000080' SIWUSR X'00000040' SIXUSR X'000001C0' SIRWXU X'00000020' SIRGRP X'00000010' SIWGRP X'00000008' SIXGRP X'00000038' SIRWXG X'00000004' SIROTH X'00000002' SIWOTH X'00000001' SIXOTH X'00000007' SIRWXO 801A - HFS_NORMDISP X'04'-DELETE, X'08'-KEEP 801B - HFS_ABDISP X'04'-DELETE, X'08'-KEEP 801D - HFS_FILEDATA Org. of a Hierarchical File X'80' - binary undelimited X'40' - Text EBCDIC x'15' delim C003 - INFO_CNTL (Request info) C004 - INFO_STORCLASS (Request info) C005 - INFO_MGMTCLASS (Request info) C006 - INFO_DATACLASS (Request info) C00B - INFO_VSAMRECORG (Request info) C00C - INFO_VSAMKEYOFF (Request info) C00D - INFO_COPYDD (Request info) C00F - INFO_COPYMDL (Request info) C010 - INFO_AVGRECU (Request info) C012 - INFO_DSTYPE (Request info) C017 - GET HFSPATH (Request info) C018 - HFS_PATHOPTS (Request info) C019 - HFS_PATHMODE (Request info) C01A - HFS_DISP (Request info) C01B - HFS_ABDISP (Request info) C01D - HFS_ORG (Request info)
Dynamic Allocation 196
System Response: None User Response: None Invoking module: <AMFMDALC>
ZPDA001E
ZPDA001E Dynamic Allocation error (+4+H+) for {+54+C+} S99ERSN=(+8+D+) Explanation: The DYNALLOC service routine (SVC99) was invoked to perform a dynamic allocate/unallocate for a data set or DD. The request could not be satisfied by the system, and the DARC was returned from SVC 99 (+4+H+). {+54+C+} - The data set name involved. {+8+D+} - The SVC 99 Error Reason; particularly of importance for SMS errors having DARC values in the range of 9700 - 97FF. For more information on MVS Dynamic Allocation, see IBM z/OS MVS Programming: Authorized Assembler Services Guide. DARC codes may also be looked up on ISPF under the Help Index section "D1 - DAIR Return Codes". DARC 9700: Severe storage management subsystem (SMS) IDAX error. The above error is commonly issued when one or more SMS Class specifications (Data, Management, Storage) conflict with the active SMS environment. For example, this can occur when a file under SMS control is Zipped, and later EXTRACTED to an environment with a different or altered SMS environment. Additional system allocation error information is issued to the JOBLOG in the form of IGDxxxxxx messages. "IGD01014I DATA SET ALLOCATION REQUEST FAILED..." "SPECIFIED DATACLAS yyyyyyy DOES NOT EXIST" Review the details following the IGD01014I message and use SMS-control commands (e.g. -OUTFILE_STORCLASS) to redirect the allocation of the file. System Response: Depends on the function requested. Some common DARC codes encountered by PKZIP are: 1708 - File not found on the system. 0210 - File in use by another job/user. User Response: Evaluate the processing being performed. It may be appropriate to encounter 1708 if a new file is being
Dynamic Allocation 197
created. PKZIP will then attempt to allocate a new file (or Archive). -TRACE_DYNALLOC(0) to avoid seeing extraneous DYNALLOC error messages. Invoking module: <AMFMDALC>
ZPDA001I
ZPDA001I DARC: +70+C+ Explanation: The DYNALLOC service routine (SVC99) was invoked to perform a dynamic allocate/unallocate for a data set, DD, or HFS PATH. The request could not be satisfied by the system, and the Dynamic Allocation Return Code (DARC) was returned from SVC 99. This message provides a textual interpretation of the DAIR Return Code (as provided in IBM documentation) For more information on MVS Dynamic Allocation, see IBM z/OS MVS Programming: Authorized Assembler Services Guide. DARC codes may also be looked up on ISPF under the Help Index section "D1 - DAIR Return Codes". System Response: None User Response: None Invoking module: <AMFMDALC>
ZPDA003E
ZPDA003E Invalid DSNAME provided for DYNALLOC {+54+C+} Explanation: Dynamic Allocation was attempted for the data set, but the name does not conform to MVS standards. System Response: Processing for the specified file is terminated. User Response: Try to determine why the invalid DSNAME is being passed. Invoking module: <AMFMDALC>
Dynamic Allocation 198
ZPDA004E
ZPDA004E DSNAME not found: {+54+C+} Explanation: Dynamic Allocation could not locate the specified data set on the system. System Response: Processing for the specified file is terminated. User Response: Ensure that the file is accessible on the system. Invoking module: <AMFMDALC>
ZPDA005E
ZPDA005E Text Unit in error: {+22+C+} Explanation: A dynamic allocation was attempted, but some information that was provided (either through control cards, Archive attributes, or defaults) was incorrect. (This could be something like an invalid DDNAME of blanks). For more information about DYNALLOC (SVC 99) and "Text Units", refer to IBM publication for z/OS MVS Authorized Assembler Services Guide in the chapter entitled "SVC 99 Parameter list Verb Codes and Text Units" System Response: The DYNALLOC request failed. Processing may be terminated. User Response: Attempt to determine which element is incorrect and provide a correct command (or default via the defaults module) to complete the necessary "Text Unit" for the dynamic allocation. Another option is to pre-allocate a new file before the execution. Invoking module: <AMFMDALC>
ZPDA011E
ZPDA011E Unallocation error (+4+H+) for {+8+C+} Explanation: A FREE attempt for the specified DDname +8+C+ failed for the reason shown in DAIR RC +4+H+ For more information on MVS Dynamic Allocation, see IBM z/OS MVS Programming: Authorized Assembler Services Guide.
Dynamic Allocation 199
DARC codes may also be looked up on ISPF under the Help Index section "D1 - DAIR Return Codes". System Response: Continue processing. User Response: Try to determine the reason for the failure. Invoking module: <AMFMDALC>
ZPDA020T
ZPDA020T Allocation entered for DD{+8+C+} DSN{+54+C+} Explanation: Dynamic Allocation processing trace record. This line is only issued when Dynamic Allocation tracing is turned on. System Response: None User Response: None Invoking module: <AMFMDALC>
ZPDA021T
ZPDA021T Membername parsed {+8+C+} Len=+4+H+ Explanation: Dynamic Allocation processing trace record. This line is only issued when Dynamic Allocation tracing is turned on. System Response: None User Response: None Invoking module: <AMFMDALC>
ZPDA022T
ZPDA022T Unallocate entered for DD{+8+C+} Explanation: Dynamic Allocation processing trace record. This line is only issued when Dynamic Allocation tracing is turned on. System Response: None User Response: None
Dynamic Allocation 200
Invoking module: <AMFMDALC>
ZPDA023T
ZPDA023T Unallocate leaving for DD{+8+C+} Explanation: Dynamic Allocation processing trace record. This line is only issued when Dynamic Allocation tracing is turned on. System Response: None User Response: None Invoking module: <AMFMDALC>
ZPDA029T
ZPDA020T Allocation leaving for DD{+8+C+} DSN{+54+C+} Explanation: Dynamic Allocation processing trace record. This line is only issued when Dynamic Allocation tracing is turned on. System Response: None User Response: None Invoking module: <AMFMDALC>
ZPDA091T
ZPDA091T PLIST: DD=+8+C+ DISP=+3+C DSN=+44+C+ Explanation: Dynamic Allocation processing trace record. This line is only issued when Dynamic Allocation tracing is turned on. System Response: None User Response: None Invoking module: <AMFMDALC>
ZPDA101I
ZPDA101I WTO : ZPDA101I WAITING ON DATASET +44+C+
Dynamic Allocation 201
Explanation: PKZIP/PKUNZIP is waiting for the specified dataset
to be available, this message is informational. PKZIP will wait for the dataset to be available for the time specified in FILE_BUSY_WAITTIME. If the time expires, the job step is terminated.
System Response: None User Response: Free dataset specified. Invoking module: <AMFMDALC>
ZPDA102I
ZPDA102I WTO : ZPDA102I WAITING ON DEVICE FOR DATASET +44+C+ Explanation: PKZIP/PKUNZIP is waiting for a device (usually a
tape mount) to be available for the specified dataset, this message is informational. PKZIP will wait for the dataset to be available for the time specified in FILE_BUSY_WAITTIME. If the time expires, the job step is terminated.
System Response: None User Response: Mount the tape - enable device. Invoking module: <AMFMDALC>
ZPDA111I
ZPDA111I SMS DARC(97xx) detected. Reason= {+8+D+} Explanation: The DYNALLOC service routine (SVC99) was invoked to
perform a dynamic allocate/unallocate for a data set. The request could not be satisfied due to an exception condition within the SMS runtime environment. {+8+D+} - S99ERSN code in decimal. For more information on MVS Dynamic Allocation, see IBM z/OS MVS Programming: Authorized Assembler
Services Guide. Copyright IBM Corp. 1988, 2000 +------------------------------------------------------------------+ | SMS Reason Code (S99ERSN): A fullword field that contains the | | SMS reason code explaining the failure. The system returns a | | reason code in this field only when an error code beginning with | | X'97xx' is returned in the S99ERROR field of the request block. | | |
Dynamic Allocation 202
| IGD messages accompany the SMS reason code depending on the | | allocation message processing options in the S99EOPTS field of | | the request block. (See "Processing Options (S99EOPTS).") The | | SMS reason code also corresponds to an IGD system message that | | further describes the error. For example, if the reason code is | | X'4379' (decimal 17273), the IGD message that contains the | | decimal equivalent, IGD17273I, describes the error. See OS/390 | | MVS System Messages, Vol 5 (IGD-IZP) for descriptions of IGD | | messages. | +------------------------------------------------------------------+
System Response: Depends on the function and S99ERSN encountered. 9700/1014 - One of the SMS Class specifications
is incorrect. The EXTRACT routine will attempt retries for the dataset in the following sequence: A. ACZDFLT and command class values. B. No SMS Class specifications.
Other - No special action.
User Response: Evaluate the processing being performed. Review the extended attributes for the file (if any) along with the ACZDFLTS and command settings (-SHOW_SETTINGS) to determine the file allocation controls being requested. -TRACE_DYNALLOC(0) to avoid seeing extraneous DYNALLOC error messages.
-TRACE_DYNALLOC(4) will display SVC 99 Text Unit parameters being passed to the system for allocation requests.
Invoking module: <AMFMDALC>
Encryption 203
ZPEN – Encryption Processing Messages
ZPEN001I
ZPEN001I Protected with +40+C+ Explanation: Encryption Service processing information.
A password was used to protect the file during ZIP processing. The encryption type indicated was used.
System Response: None User Response: See also: -ENCRYPTION_METHOD command. Invoking module: <ACAMGR>
ZPEN002W
ZPEN002W Algorithm not supported by this release: +40+C+ Explanation: Encryption Service processing information.
A password was used to protect the file during ZIP processing. An ENCRYPTION_METHOD was used that is not supported on this release.
System Response: The file is skipped. User Response: See also: -ENCRYPTION_METHOD command. -PKSUPPRC(ZPEN002W) may be specified to suppress the return code for this event. Invoking module: <ACAMGR>
ZPEN003W
ZPEN003W Switching to STANDARD encryption. Explanation: Encryption Service processing information.
A request was made for strong encryption, but either the license did not allow it, or -GZIP was specified. The -GZIP encryption extension does not support "strong encryption".
System Response: The file is encrypted with standard encryption. User Response: See also: -ENCRYPTION_METHOD command. Invoking module: <ACCMGR>
Encryption 204
ZPEN005I
ZPEN005I No password was provided. Encrypted files will be bypassed. Explanation: During file selection, a file was found to have been
password-protected. However, no password was provided for the PKUNZIP request.
System Response: The file is not processed. RC = 4 is set for the run.
User Response: Supply the correct -PASSWORD value. Invoking module: <ACAMGR>
ZPEN006E
ZPEN006E Strongly-encrypted AES file length mismatch - not module 16. Explanation: During file selection, a file was found to have been
password-protected with the AES algorithm. By definition, AES is a block-cipher requiring 16-byte blocks. The compressed-length of the file must be a multiple of 16 bytes.
System Response: The file is not processed. RC = 8 is set for the run.
User Response: Contact the vendor who created the AES file in the Archive.
Invoking module: <ACAMGR>
ZPEN007E
ZPEN007E A BSAFE Encryption_Method is required to support Recipients. Explanation: After all default and command settings were merged, it was determined that an ENCRYPTION_METHOD was specified that does not support RECIPIENTs. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Correct either the ENCRYPTION_METHOD or RECIPIENT settings. Invoking module: <ACCMGR>
Encryption 205
ZPEN008E
ZPEN008E The number of recipients requested could not be processed. Explanation: Too many recipient requests were found to fit into the file archive. Virtual Storage and/or Archive restrictions apply. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Refine -RECIPIENT requests. Invoking module: <ACCMGR>
ZPEN009E
ZPEN009E Recipient Processing Error: +80+C+ Explanation: An error was encountered while attempting to process a SecureZIP RECIPIENT digital certificate request. Reason: +80+C+ ZERO-LENGTH PASSWORD The RECIPIENT or MASTER_RECIPIENT syntax indicated that a private-key certificate should be used, but the PASSWORD= value is zero length. DD: LENGTH ERROR The format for specifying a DD name is DD:ddname, where "ddname" is an allocated DD in the jobstep. FILE: LENGTH ERROR A filename specifying an MVS data set may be a maximum of 44 characters for a sequential file, or 54 characters for a PDS. UNSUPPORTED CERT. STORE The Certificate Store type as specified in the RECIPIENT command was not recognized. Valid values are: DB: FILE: LDAP: (public recipient only) DSN: DA: Appropriate search criteria must immediately follow the type. For example: DB:CN=Joe Smith FILE://'PKZIP.JOE.SMITH.CER' DA:'PKZIP.JOE.SMIT.CER' LDAP:[email protected] “SecureZIP Partner (Write mode) SETUP: No Valid Recipients” A valid Sponsor RECIPIENT command must be available for encryption. System Response: Processing is terminated.
Encryption 206
RC = 12 is set for the run. User Response: Correct the -RECIPIENT or Certificate Store configuration Invoking module: <ACCMGR>
ZPEN010I
ZPEN010I Encryption not selected for this run. Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued when -ENCRYPTION_METHOD=N is specified. System Response: Processing continues. User Response: None Invoking module: <ACCMGR>
ZPEN011W
ZPEN011W Switching FILENAME_ENCRYPTION off; inadequate ENCRYPTION_METHOD Explanation: When requesting FILENAME_ENCRYPTION during a ZIP run, one of the strong encryption_method algorithms must also be specified. System Response: Processing continues with a minimum RC=4. User Response: Specify an ENCRYPTION_METHOD that uses a minimum strength of 128-bits. Invoking module: <ACCMGR>
ZPEN013I
ZPEN013I Switching ENCRYPTION_METHOD=STANDARD to minimal AES128 for RECIPIENT(S). Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued under the following condition(s): - A RECIPIENT was supplied for encryption, but a strong ENCRYPTION_METHOD was not specified. System Response: A minimal default level of AES128 will be set in an attempt to complete the RECIPIENT processing. User Response: If a different algorithm is desired, or to eliminate this
Encryption 207
message, specify one of the strong ENCRYPTION_METHOD values. If STANDARD encryption is required, then the RECIPIENT requests must be removed. Invoking module: <ACCMGR>
ZPEN014I
ZPEN014I Decryption RECIPIENTs without a private-key certificate password will not be used. Explanation: A RECIPIENT was supplied for decryption that did not contain a valid PASSWORD= sub-parameter. Note that this subparameter of the RECIPIENT command is different than the -PASSWORD command used for password encryption. System Response: The RECIPIENT(s) not containing a password will be bypassed when attempting to decrypt files. A decryption attempt without a matching private-key recipient or valid password will fail. User Response: Supply a PASSWORD subparameter or remove the -RECIPIENT command from the command stream. Invoking module: <ACCMGR>
ZPEN015I
ZPEN015I No PASSWORD or RECIPIENTS were provided. Encrypted files will be bypassed. Explanation: During file selection, a file was found to have been strongly encrypted. However, insufficient decryption information was provided to continue with the UNZIP process for the file. Note: Only SecureZIP for z/OS supports recipient-based decryption. PKZIP for z/OS with the Enhanced Encrypt/Decrypt module supports password-based decryption for AES, 3DES and RC4. System Response: The file is not processed. RC = 4 is set for the run. User Response: Supply a -PASSWORD or -RECIPIENT specification. Invoking module: <ACAMGR>
Encryption 208
ZPEN016W
ZPEN016W This edition of the product is not licensed to access strongly encrypted files. File bypassed. Explanation: Either PKZIP Enterprise Edition or SecureZIP are required to decrypt strongly-encrypted files. This includes the use of FILENAME_ENCRYPTION for the Archive directory. System Response: The object file/directory will be skipped. User Response: PKSUPPRC=ZPEN016W may be used to suppress the return code. However, processing will still be bypassed for the strongly* encrypted file/directory. Invoking module: <ACAMGR>
ZPEN017E
ZPEN017E Insufficient authority to open secured Archive. +40+C+ Explanation: The Archive appears to have an encrypted Central Directory. The directory could not be accessed for the reason specified below. "ENHANCED DECRYPT REQUIRED" The Central Directory was encrypted with a password. This feature requires an appropriate PKZIP/SecureZIP edition to access this archive. "SECUREZIP REQUIRED" The Central Directory was encrypted with digital certificates, but not a password. SecureZIP is required to access this mode of encryption. "NO RECIPIENTS PROVIDED" The Central Directory was encrypted with digital certificates, but not a password. SecureZIP needs access to a matching private-key certificate to access this archive. "NO PASSWORD PROVIDED" The Central Directory was encrypted with a password. When SecureZIP Partner (Write mode) is running, an invalid ZIP-update attempt may have been made against an input archive having FILENAME ENCRYPTION. "PASSWORD OR MATCHING RECIPIENT REQUIRED" When the archive was secured, the user specified that either a private-key recipient, or a password may be used to decrypt the file. Either a matching SecureZIP private-key certificate or the password must be specified. Note: Only SecureZIP for z/OS supports recipient-based
Encryption 209
decryption. PKZIP for z/OS with the Enhanced Encrypt/Decrypt module supports password-based decryption for AES, 3DES and RC4. "UNRECOGNIZED CENTRAL DIRECTORY ENCODING" The data found at the start of the Central Directory does not match the known encoding schemes for this release. It is possible that the Central Directory has been encrypted or compressed with a technique not recognized by this version of the software. "ENCRYPTED/COMPRESSED C.D. UNSUPPORTED" Filename Encryption and Compressed Central Directory features are not supported by this release of SecureZIP. "UNRECOGNIZED/UNSUPPORTED ENCRYPT MODE" While attempting to locate the start of an encrypted and/or compressed archive Central Directory, a validation of the decryption information failed. The Central Directory will not be able to be extracted for processing. System Response: The open of the archive is terminated. User Response: See reason codes above. Invoking module: <ACAMGR>
ZPEN018W
ZPEN018W FILENAME_ENCRYPTION has been disabled for the Archive update. Explanation: The input archive for updating was detected to have encrypted files. PKZIP will not allow a new archive to be created which may contain files that cannot be accessed with the new encryption parameters. System Response: FILENAME_ENCRYPTION is turned off for the remainder of the ZIP process. Newly added or updated files will be created with the specified encryption parameters. Files copied from the input Archive will retain their original encryption state (and will be accessed with their associated password or recipient attributes). User Response: If an FNE archive is desired, all previously encrypted files should be removed from the archive before attempting an update process to the archive. Optionally, all file data should be extracted and a fresh Archive created. Invoking module: <ACAMGR>
Encryption 210
ZPEN019W
ZPEN019W INCLUDE_SFX has been disabled for FILENAME_ENCRYPTION processing. Explanation: The self-extractors do not have support for filename encryption. System Response: The Self-extractor request will be ignored and FILENAME_ENCRYPTION will continue. User Response: Turn off the request for INCLUDE_SFX and obtain an appropriate PKZIP or SecureZIP product for the target platform to handle the filename-encrypted archive. Invoking module: <ACCMGR>
ZPEN020W
ZPEN020W FILENAME_ENCRYPTION has been deactivated in the output archive. Explanation: While creating a new output archive from an input archive that had FILENAME_ENCRYPTION turned on, it was determined that the default settings for ZIP processing specified FILENAME_ENCRYPTION=N. This results in an implicit conversion to a less secure archive. System Response: Processing continues with a minimum RC=4. User Response: -PKSUPPRC(ZPEN020W) may be coded to suppress the return code = 4 that is associated with this message. If the warning message is not desired, include the command -FILENAME_ENCRYPTION=N to specifically state that the conversion to a nonFNE archive is desired. Otherwise, use -FILENAME_ENCRYPTION=Y to retain the FNE state in the new archive. Invoking module: <ACCMGR>
ZPEN021I
ZPEN021I Recipients are not valid for GZIP processing and will be ignored. Explanation: -RECIPIENT processing is only valid for the ZIP archive format. When GZIP=Y is specified, all specifications for recipients will be ignored. System Response: Processing continues. User Response: None.
Encryption 211
Invoking module: <ACCMGR>
ZPEN022C
ZPEN022C +121+C+ Explanation: If the STATUS= field is non-zero, use it to refer to CRYPTOSR for additional information. System Response: No action. User Response: See also: ZPEN105E Invoking module: <ACAMGR> See also: HELP(CRYPTOSR)
ZPEN022I
ZPEN022I +121+C+ Explanation: If the STATUS= field is non-zero, use it to refer to CRYPTOSR for additional information. System Response: No action. User Response: See also: ZPEN105E Invoking module: <ACAMGR> See also: HELP(CRYPTOSR)
ZPEN023I
ZPEN023I Recipients are not valid for PKZIP processing and will be ignored. Explanation: -RECIPIENT processing is only valid for SecureZIP or PKUNZIP processing. -RECIPIENT requests will be ignored for PKZIP (ZIP) Processing. System Response: Processing continues. User Response: None. Invoking module: <ACCMGR>
Encryption 212
ZPEN025I
ZPEN025I Switching to ENCRYPTION_METHOD=3DES to match FIPSMODE requirement. Explanation: "Effective May 19, 2005: Federal Agencies may continue to use DES as a NIST recommended Approved security function in a FIPS Approved mode of operation in FIPS 140-1 or FIPS 140-2 validated cryptographic modules for a period of 2 years (until May 19, 2007)." Compliance for ENCRYPTION_METHOD=DES has expired. http://csrc.nist.gov/groups/STM/common_documents/DESTranPlan.pdf System Response: ENCRYPTION_METHOD=3DES is substituted to meet FIPSMODE requirements. User Response: If necessary, have the security administrator provide grant access to resources needed to operate with 3DES. Alternatively, change the settings for FIPSMODE or ENCRYPTION_METHOD to meet operational security policies. Invoking module: <ACCMGR>
ZPEN029E
ZPEN029E Certificate setup for Signing/Authentication was unsuccessful. Explanation: While accessing certificates for Signing or AUTHCHK processing, an unacceptable configuration or certificate state was encountered. Typical conditions include: - A SIGN_ARCHIVE request could not be set up because the identifying certificate file could not be accessed, opened (with the correct password), or did not pass the certificate validation policy defined by -{VALSIGN=...} - No usable certificates could be found for the action requested. System Response: Processing is terminated. User Response: Examine other messages to determine the cause. Various configuration settings (such as specifying that certificates are required) govern whether processing can continue. If the process had run successfully on a previous day, check to see if the requested certificate has expired.
Encryption 213
Invoking module: <ACEXMAIN>
ZPEN030I
ZPEN030I Signers are not valid for +8+C+ processing and will be ignored. Explanation: Signing is supported for SecureZIP processing because it requires Digital Certificate support. PKZIP for z/OS does not support certificates The GZIP standard does not support certificate-based processing. System Response: Processing continues. User Response: None. Invoking module: <ACCMGR>
ZPEN031E
ZPEN031E A request to authenticate could not be completed. Status = RC Error Text Explanation: The -AUTHCHK command encountered an error. The Status contains a return code (8 or 12). The Error Text is an explanatory string describing the problem. NO LICENSE Authentication is not licensed. INVALID AUTHCHK TYPE The AUTHCHK type is not ALL, ARCHIVE, or FILES MULITPLE AUTHCHK(ARCHIVE) Only one AUTHCHK(ARCHIVE... or AUTHCHK(ALL... is permitted. ZPEN009E ISSUED An error associated with certificates was encountered. Reference the previous ZPEN009E error message. System Response: The request is terminated. User Response: Correct the -AUTHCHK( ) requests, or the problem with the associated certificate. Invoking module: <ACCMGR>
Encryption 214
ZPEN032E
ZPEN032E A request to sign could not be completed. Status = +8+D+ +12+C+ Explanation: An error occurred operation was requested. System Response: The signing request cannot be fulfilled, and the ZIP process is terminated. User Response: Check the status information code for additional information relating to the failure of the associated SIGN_FILES or SIGN_ARCHIVE command. Invoking module: <ACCMGR>
ZPEN032I
ZPEN032I A request to sign could not be completed. +30+C+ Explanation: The signing request could not logically be performed. "Cannot sign empty Archive" - An empty archive does not have sufficient structure to hold a directory signature. There are no central directory records to perform a signing hash against. System Response: Processing continues User Response: None required Invoking module: <ACAMGR>
ZPEN034E
ZPEN034E Signing requires a password for a private-key certificate Explanation: Because a signing operation was requested, a private-key digital certificate is required along with its associated password. System Response: The signing request cannot be fulfilled, and the ZIP process is terminated. User Response: Supply a PASSWORD subparameter or remove the related SIGN_FILES or SIGN_ARCHIVE command. Invoking module: <ACCMGR>
Encryption 215
ZPEN035E
ZPEN035E Archive Directory Authentication Failed. Explanation: An Archive Directory AUTHCHK request did not pass. A more specific message will be included to describe the type of check that failed. System Response: Processing continues SecureZIP Partner will stop processing when an input archive cannot be authenticated from a configured Sponsor. An acceptable SPONSOR_AUTH configuration setting must be included in the run for the associated input archive. User Response: Review additional messages to determine the reason for the failed authorization check. Review the authentication policy settings specified with -{AUTHENTICATE=...} to determine whether the desired level of checking is being performed. It is possible to override the RC=6 produced by SECUNZIP processing due to this condition by specifying -PKSUPPRC(ZPEN035E) in the run. Invoking module: <ACAMGR>
ZPEN035I
ZPEN035I Archive Directory Authentication Succeeded Explanation: An Archive Directory AUTHCHK request was completed in accordance with the -{AUTHENTICATE} policy settings. System Response: Processing continues User Response: None required. Invoking module: <ACAMGR>
ZPEN036W
ZPEN036W Archive Directory tampering detected Explanation: The Archive Central Directory signature verification did not match the directory information. This indicates that the signature should not be used to trust the content of the archive.
Encryption 216
System Response: Processing will continue in accordance with ZPEN035E User Response: Review additional messages to determine the reason for the failed authorization check. Invoking module: <ACAMGR>
ZPEN037C
ZPEN037C +121+C+ Explanation: When ZPEN037W is issued to declare that an Archive Signature Authentication Check Failed, this message is issued to provide detailed information regarding the certificate. Information that may be included: Common Name internal to the certificate Email address (if available) internal to the certificate Serial Number of the certificate Reason(s) the certificate may have failed System Response: See ZPEN037W User Response: Review additional messages to determine the reason for the failed authorization check. Invoking module: <ACAMGR>
ZPEN037W
ZPEN037W Archive Signature Authentication Check Failed xxxx-xxxx-xxxx Explanation: The Authorization check of the Central Directory signature failed. The feedback status for 3 levels of authentication are represented in the message as follows: CCxx-AAxx-RRxx Where: CC - The individual certificate status AA - The intermediate Certificate Authority status RR - The ROOT Certificate Authority status The first byte contains flag settings for failed status. A failure in the CA or Root levels will cause the individual "not trust" flag x'10' to be set. FBST_CHK_NOSTORE x'FF' for CA and Root: Store not found FBST_CHK_NOQUALFY x'80' BIT 0 for secure Certificate not qualified FBST_CHK_EXPIRED x'40' BIT 1 Cert has expired
Encryption 217
FBST_CHK_REVOKED x'20' BIT 2 Cert has been revoked FBST_CHK_NOTRUST x'10' BIT 3 Cert is not trusted FBST_CHK_NOCERT x'08' BIT 4 Cert Could not be found FBST_CHK_NOVERIFY x'04' BIT 5 Signature was NOT verified System Response: Processing will continue in accordance with ZPEN035E User Response: Review additional messages to determine the reason for the failed authorization check. Invoking module: <ACAMGR>
ZPEN038E
ZPEN038E The number of Signers requested could not be processed. Explanation: Too many Signing requests were made for one of the following reasons: 1. More than one -SIGN_ARCHIVE request was made. 2. More than 100 -SIGN_FILES requests were made. 3. There is insufficient room in the Archive extended attributes section to hold the Certificate Store associated with the signers. 4. There is insufficient virtual storage allocated to the job to allow the completion of the requests. 5. The product is not licensed to support this feature. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Refine -SIGN_ARCHIVE/-SIGN_FILES command requests. Invoking module: <ACCMGR>
ZPEN039E
ZPEN039E Archive Authentication check unsuccessful - +30+C+ Signatory Info. not Found No Matching Archive Signer Explanation: An AUTHCHK request for the Archive Directory could not be completed for the reason shown. "Signatory Info. not Found" Either the Archive Directory is not signed, or the signature could not be located for processing due to some other error (such as Filename_Encryption being enabled, but there is insufficient authority to open the directory for processing). "No Matching Archive Signer"
Encryption 218
One of the following is true: - A Required certificate was specified for the AUTHCHK, but the directory was signed by another certificate This will be accompanied by ZPEN105E Error = 3451 - None of the listed certificates specified for the AUTHCHK matched the signatory. This will be accompanied by ZPEN105E Error = 3447 System Response: Processing continues as conditions allow An authentication failure RC=6 will be set. User Response: Determine whether AUTHCHK(ARCHIVE) is appropriate. -PKSUPPRC(ZPEN039E) may be specified to suppress the return code associated with this condition. Invoking module: <ACEXMAIN>
ZPEN040W
ZPEN040W AUTHCHK Signatory Certificate was not found Explanation: A request to authenticate based on a specific certificate could not be made because the certificate was not found. System Response: Processing continues. RC=4 is set. - If no other specific certificates are specified and located, then a generic AUTHCHK for the type (Archive or File) will be performed. - If other FILE certificates were specified and found, then the list of satisfied certificates will be used to perform the authentication check. User Response: Review the AUTHCHK command to ensure that the correct certificate name is specified, and that it matches its certificate store definition (public or private). Invoking module: <ACCMGR>
ZPEN041I
ZPEN041I File authentication is being bypassed: +30+C+ Explanation: The -AUTHCHK(FILES) command is inconsistent with other processing options. The AUTHCHK request will be ignored. * EXTRACT_PREVIEW Processing In order to validate a signature, the complete file must be extracted. The preview command may prevent the entire file from being available.
Encryption 219
System Response: Processing continues. User Response: None required. Invoking module: <ACCMGR>
ZPEN045E
ZPEN045E File Authentication Failed. Explanation: An AUTHCHK request for files did not pass. A more specific message will be included to describe the type of check that failed. System Response: Processing continues. User Response: Review additional messages to determine the reason for the failed authorization check. Review the authentication policy settings specified with -{AUTHENTICATE=...} to determine whether the desired level of checking is being performed. Invoking module: <ACEXMAIN>
ZPEN045I
ZPEN045I File Authentication Passed. Explanation: An AUTHCHK request for files was successful for the file being tested/extracted. See the subsequent ZPEX001I or ZPEX002I for the related file name. System Response: None. User Response: None required. Invoking module: <ACEXMAIN>
ZPEN047C
ZPEN047C +121+C+ Explanation: When ZPEN047W is issued to declare that a File Signature Authentication Check Failed, this message is issued to provide detailed information regarding the
Encryption 220
certificate. Information that may be included: Common Name internal to the certificate Email address (if available) internal to the certificate Serial Number of the certificate Reason(s) the certificate may have failed System Response: See ZPEN047W User Response: Review additional messages to determine the reason for the failed authorization check. Invoking module: <ACEXMAIN>
ZPEN047W
ZPEN047W File Signature Authentication Check Failed xxxx-xxxx-xxxx Explanation: The Authorization check for the Extracted/Tested file's signature failed. The error code information will be interpreted in additional messages. See also: ZPEN037W for details regarding the status bytes displayed in this message. System Response: Processing will continue in accordance with ZPEN045E User Response: Review additional messages to determine the reason for the failed authorization check. Invoking module: <ACEXMAIN>
ZPEN049E
ZPEN049E File Authentication check unsuccessful - +30+C+ File was not signed No Matching File Signer Explanation: One of the following is true: - A Required certificate was specified for the AUTHCHK, but the file was signed by another certificate. This will be accompanied by ZPEN105E Error = 3451 - None of the listed certificates specified for the AUTHCHK matched the signatories found for the file. This will be accompanied by ZPEN105E Error = 3447 System Response: Processing continues. An authentication failure RC=6 will be set. User Response: Review the status of the files in the archive to determine whether AUTHCHK(FILES) is appropriate.
Encryption 221
-PKSUPPRC(ZPEN049E) may be specified to suppress the return code associated with this condition. Invoking module: <ACEXMAIN>
ZPEN050E
ZPEN050E FIPSMODE=+20+C+ requirements are not met. Explanation: Settings for FIPSMODE specify that cryptographic facility requirements be enforced for file processing. For ZIP processing of ADD, FRESHEN, or UPDATE files, one of the following requirements has not been satisfied. 1. Either Password or Recipient-based encryption was not requested. In accordance with the specified FIPSMODE setting, files are required to be encrypted. 2. An algorithm was specified that does not meet the criteria of the required FIPSMODE. (Ref. -ENCRYPTION_METHOD) 3. A FIPS-validated cryptographic module is not available to process the specified encryption algorithm. (Ref. -FACILITY_ENCRYPTDATA) For UNZIP processing of files, one of the following requirements has not been satisfied. 1. The file was determined to not be encrypted. 2. The file was determined to be encrypted, but with an algorithm that is not FIPS compliant. System Response: The request is terminated. 1. The ZIP run will be halted. 2. UNZIP processing for the file will be bypassed and flagged as a file in error. Message ZPEN202E with Status=3318 may accompany this condition to indicate that a FIPS-validated cryptographic module is not available on the system for the algorithm requested. User Response: See -FIPSMODE processing requirements. 1. Correct the process settings to satisfy the FIPSMODE specification (ZIP processing only). 2. Change the FIPSMODE specification to permit processing to continue without requiring FIPS enforcement. Invoking module: <ACCMGR, ACAMGR>
Encryption 222
ZPEN050W
ZPEN050W FIPSMODE=+20+C+ requirements will not be met Explanation: Settings for FIPSMODE specify that cryptographic facility requirements be enforced for file processing. For UNZIP processing of files, one of the following requirements has not been satisfied for one or more files. 1. A file encrypted with DES was being extracted with a FIPSMODE setting requiring 140-x compliance. Compliance for ENCRYPTION_METHOD=DES has expired. "Effective May 19, 2005: Federal Agencies may continue to use DES as a NIST recommended Approved security function in a FIPS Approved mode of operation in FIPS 140-1 or FIPS 140-2 validated cryptographic modules for a period of 2 years (until May 19, 2007)." http://csrc.nist.gov/groups/STM/common_documents/DESTranPlan.pdf System Response: The request is allowed to continue with RC=4 User Response: -PKSUPPRC(ZPEN050W) may be specified to suppress the return code. If FIPS 140 compliance is required, contact the provider of the archive and notify them that a current FIPS 140 compliant algorithm/key strength is required. Invoking module: <ACEXMAIN>
ZPEN057C
ZPEN057C +121+C+ Explanation: When ZPEN057W is issued to declare a certificate as having failed validation, this message is issued to provide detailed information regarding the certificate. Information that may be included: Common Name internal to the certificate Email address (if available) internal to the certificate Serial Number of the certificate Reason(s) the certificate may have failed System Response: See ZPEN057W User Response: Review additional messages to determine the reason for the failed authorization check.
Encryption 223
Invoking module: <ACCMGR>
ZPEN057I
ZPEN057I Certificate Validation Passed Explanation: The Validation check for a requested certificate passed. System Response: Processing will attempt to continue for the requested certificate-based action with the listed certificate. User Response: None Invoking module: <ACCMGR>
ZPEN057W
ZPEN057W Certificate Validation Failed +4+H+-+4+H+-+4+H+ Explanation: The Validation check for a requested certificate failed. The feedback status for 3 levels of authentication are represented in the message as follows: CCxx-AAxx-RRxx Where: CC - The individual certificate status AA - The intermediate Certificate Authority status RR - The ROOT Certificate Authority status The first byte contains flag settings for failed status. A failure in the CA or Root levels will cause the individual "not trust" flag x'10' to be set. FBST_CHK_NOSTORE x'FF' for CA and Root: Store not found FBST_CHK_NOQUALFY x'80' BIT 0 for secure Certificate not qualified FBST_CHK_EXPIRED x'40' BIT 1 Cert has expired FBST_CHK_REVOKED x'20' BIT 2 Cert has been revoked FBST_CHK_NOTRUST x'10' BIT 3 Cert is not trusted FBST_CHK_NOCERT x'08' BIT 4 Cert Could not be found FBST_CHK_NOVERIFY x'04' BIT 5 Signature was NOT verified System Response: This message signifies that the listed certificate was not included for processing. If this certificate was specified as "Required", or if no other certificates qualify for use in the requested
Encryption 224
action, then processing will be terminated. User Response: Review additional messages to determine the reason for the failed authorization check. Review the policy set by the SecureZIP Administrator for the action being performed. See: -{VALSIGN..} -{VALENCRYPT...} -{AUTHENTICATE...} -PKSUPPRC(ZPEN057W) may be coded to suppress the return code = 4 that is associated with this message. Invoking module: <ACCMGR>
ZPEN100E
ZPEN100E Certificate-Based functions require a minimum operating system Explanation: RSA BSAFE Cert-C (R) is used to handle digital certificate operations. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Remove the -RECIPIENT settings or execute on a system capable of utilizing BSAFE Cert-C. Invoking module: <ACCMGR>
ZPEN101E
ZPEN101E L/E Pre-initialization failed for +30+C+. RC=+8+H+ Explanation: Encryption Service processing failure. Some PKZIP operations require Language Environment runtime support through the CEEPIPI service. The initialization call to CEEPIPI which loads necessary PKZIP service routines failed. Ref: IBM Language Environment Programming Guide "Using PreInitialization Services" +30+C+ - Indicates the type of processing in control. "BSAFE SUPPORT IN <ACCOMAIN>" <ACCOMAIN> is responsible for controlling compression services, data translation, data encryption and file signatures. Some components of data encryption and file signing require Language Environment support for BSAFE service routines.
Encryption 225
+8+H+ - The return code from CEEPIPI initialization. System Response: The requested function is terminated. User Response: See additional messages to determine which feature(s) could not be performed. Invoking module: <ACCOMAIN>
ZPEN102E
ZPEN102E +20+C+ error encountered. Errno=+8+D+ Reason=+8+D+ Explanation: A cryptographic service request encountered an error. System Response: The requested function is terminated. User Response: Lookup the Errno/Reason code information to determine whether a configuration or environmental condition caused the error. See also: HELP(CRYPTOSR) Contact PKWARE Technical Support and provide the Errno and Reason code information when assistance is required. Invoking module: <ACCOMAIN>
ZPEN103E
ZPEN103E Crypto Service Environment initialization failed. Explanation: Encryption Service processing failure. The initialization call to CEEPIPI which loads the needed cryptographic service module failed. System Response: The requested function is terminated. User Response: Contact PKWARE Technical Support. Invoking module: <ACCOMAIN>
ZPEN104E
ZPEN104E BSAFE(R) CertC Service is unavailable to process certificates Explanation: Digital Certificate retrieval could not be performed
Encryption 226
because the C Service task required to handle the request was not successfully initialized. System Response: The requested function is terminated. User Response: See additional messages to determine the cause of the failure. Invoking module: <ACCMGR>
ZPEN105E
ZPEN105E BSAFE(R) Certificate request error=+8+D+ +32+C+ Explanation: BSAFE(R) Cryptographic Service requests resulting in non-zero return codes (internally) will result in this message being displayed. System Response: Processing associated with the failure in certificate access will be terminated. User Response: See additional messages to determine the cause of the failure. Note that a variety of error conditions can be caused by insufficient REGION begin available for Language Environment HEAP processing. Abends such as 106, 80A and 878 are clear indications that a larger REGION size is required to handle the number of digital certificates associated with the RECIPIENT requests. Additional information may be obtained by setting LOGGING_LEVEL=VERBOSE. (See also ZPEN022I) See also: HELP(CRYPTOSR) SecureZIP Partner: request error= 3350 kPKErr_kPLnoAuthFL Processing will be stopped when an input archive cannot be authenticated from a configured Sponsor. An acceptable SPONSOR_AUTH configuration setting must be included in the run for the associated input archive. Invoking module: <ACAMGR> <ACCMGR> <ACEXMAIN>
ZPEN109T
ZPEN109T Crypto Service request code=+8+D+ +32+C+ Explanation: Cryptographic Service requests resulting in
Encryption 227
non-zero return codes (internally) will result in this message being displayed when -LOGGING_LEVEL(VERBOSE) is specified. This message is considered to be informational and does not directly govern subsequent processing. Some common processing codes and their explanations are: "code=3319 kPKErr_NoActFacility" means that an active cryptographic facility could not be located for the algorithm required in accordance with the FACILITY specifications. Example: FACILITY ENCRYPTDATA specified only IBMHARDWARE for AES decryption on a system that does not have AES hardware acceleration. Example: FIPSMODE specified a constraint for a FIPS-validated facility to be used, but an algorithm was specified for encryption (or found for decryption) that could not handled by the facility. "code=3599 kPKErr_PassWordInvalid" will be displayed when the incorrect password is supplied. However, if the file can also be decrypted with a private-key certificate (recipient), then a retry attempt may be made to decrypt. "code=3594 kPKErr_BSISetKeyInf" may be issued when no password is provided for a "password or recipient" encrypted file. This simply indicates that no password was supplied and that an attempt to locate a recipient private-key certificate will be made. System Response: Processing continues based on the options and conditions encountered. User Response: See additional messages to determine whether a resulting failure has occurred. See also: HELP(CRYPTOSR) Invoking module: <ACEXMAIN>
ZPEN110I
ZPEN110I Locating Digital Certificates ... Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message is issued during the initialization phase that attempts to locate and retrieve digital certificates associated with recipient-based encryption. (SecureZIP only). This message provides run-time "state" information.
Encryption 228
This can be useful if a job appears to be in a wait state due to LDAP network requests that take a long period of time. System Response: Processing continues through a sub-task that accesses digital certificates within local files, the Local Certificate Store, or networked LDAPs. User Response: If a long wait occurs after this message is issued, 1. Review the joblog for additional messages associated local file certificates or the Local Certificate Store. 2. Determine if resource contention exists for the job (console command D GRS,C) 3. Review LDAP configuration settings along with the corresponding LDAP Server parameters (time-out values). 4. Assess whether LDAP-based RECIPIENT requests may result in long searches in the LDAP Server. 5. Use the "LDAP Certificate Store Configuration" panels within "SecureZIP Certificate Store Administration" to determine whether the LDAP Server(s) are responding properly to the search criteria specified in the run. Invoking module: <ACCMGR>
ZPEN121E
ZPEN121E Special Archive Directory processing could not be completed Reason=+8+D+ Explanation: The Archive Central Directory required special processing that could not be completed. This is commonly encountered when Filename Encryption or Archive Central Directory Signing is used. Reason Code 1 - An attempt was made to allocate a temporary work file to process the special Archive Central Directory, but the allocation failed. 2 - The OPEN failed for a temporary work file. 3 - OUTPUT error on the temporary work file. 4 - INPUT error while copying the input ARCHIN data. 5 - Internal error 6 - Internal error 7 - Likely decryption failure Invalid Password or incorrect private-key certificate 8 - Unrecognized ZIP File format record An extension to the ZIP File format was encountered
Encryption 229
that this release does not support. 9 - The requested processing for Filename Encryption with inbound certificate-based recipients requires a license for the Advanced Security Module. System Response: Terminate processing of the Archive. User Response: Check for additional messages to determine the cause. Invoking module: <ACAMGR>
ZPEN202E
ZPEN202E Crypto Setup Error: Type=n R15=+8+H+ Status=n Explanation: During initialization, a system query was attempted to determine the types of cryptographic services available for use. Type=n reflects the type of setup query performed 1 - Encrypt/Decrypt 2 - Hash (Digital Signature/Authentication) R15=+8+H+ Indicates the basic assessment return code. 80000010 - A problem occurred when attempting to fetch and execute the cryptographic assessment module PKCRYMTX. 00000008 - A logical setup error was detected. See Status=n for more information. Status=n Reflects specific information about a logical setup error. 3327 - Configuration error, such as an unrecognized FACILITY parameter. 3318 - There are no FIPS-validated cryptographic components available for use. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Action is dependent on the error code(s) encountered. Invoking module: <ACCMGR>
ZPEN203E
ZPEN203E Cryptographic initialization error Explanation: During startup, an attempt was made to establish which
Encryption 230
cryptographic facilities are available for use. A condition was encountered that would not permit processing to continue. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Review the preceding messages to determine the reason for the failure. Invoking module: <ACCMGR>
ZPEN204E
ZPEN204E No viable cryptographic facility exists for +20+C+ +20+C+ Explanation: An operational request involving cryptographic services could not be completed in accordance with the associated facility specifications. Information is provided in the message to assist in identifying which cryptographic operation could not be completed. ENCRYPTION_METHOD named-method The named-method was to be used to perform symmetric encryption or decryption processing. - Encryption can be performed during ZIP processing. - Decryption can be performed during UNZIP processing, and can also be invoked for an input archive that had FILENAME ENCRYPTION enabled. SIGN_HASHALG named_method The named-method was to be used in support of digital signature operations. - SIGN ARCHIVE - SIGN FILES - AUTHCHK System Response: The requested operation is terminated. User Response: Review the following configuration items to determine why a viable cryptographic facility could not be selected for use. - The state of ICSF and associated facilities at the time of the failure. Operational disruptions for ICSF or the hardware facilities can cause an interruption in the callable services. 1. Whether ICSF is executing on the run-time system at the appropriate level. 2. Whether hardware cryptographic services are available on the system for the specified method. - For ENCRYPTION_METHOD, also see:
Encryption 231
- FACILITY_ENCRYPTDATA settings - FIPSMODE setting - For SIGN_ALGID, also see: - FACILITY_HASH settings Invoking module: <ACCMGR>
ZPEN205I
ZPEN205I Cryptographic facility {+15+C+} is selected for +20+C+ +20+C+ Explanation: An operational request involving cryptographic services identified an appropriate cryptographic facility for use. A facility identified with FACILITY_ENCRYPTDATA or FACILITY_HASH is listed. In addition, the associated cryptographic operation type and specific method are shown. ENCRYPTION_METHOD named-method The named-method was to be used to perform symmetric encryption or decryption processing. - Encryption can be performed during ZIP processing. - Decryption can be performed during UNZIP processing, and can also be invoked for an input archive that had FILENAME ENCRYPTION enabled. SIGN_HASHALG named_method The named-method was to be used in support of digital signature operations. - SIGN ARCHIVE - SIGN FILES - AUTHCHK System Response: The requested operation continues. User Response: None required. -SHOW_SETTINGS may be used to review the configuration in effect. For ENCRYPTION_METHOD, also see: - FACILITY_ENCRYPTDATA settings For SIGN_ALGID, also see: - FACILITY_HASH settings Invoking module: <ACCMGR>
Encryption 232
ZPEN300I
ZPEN300I OSname<oooo> OS Ver(vv) Rel(rr) Mod(mm) HWclass<cccccccc> Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. The operating system level and hardware platform govern which cryptographic facilities may be available for use. Classification of hardware. S/390 Pre-zArchitecture, possibly with G5/G6 Z/X00 zArchitecture z800/z900, possibly with CCF Z/X90 zArchitecture z890/z990, with CPACF Z9 zArchitecture z9-109 or equivalen, with CPACF System Response: The requested operation continues. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN301E
ZPEN301E-AMUTCQRY Error Occurred: Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. An attempt was made to determine the what cryptographic facilities are available through ICSF, but required ICSF and/or hardware facilities are not operative. Additional messages follow with more detailed information. System Response: ICSF-based Crytpographic service requests associated with IBMHARDWARE and IBMSOFTWARE facility requests may fail. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run.
Encryption 233
The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN302I
ZPEN302I The CCVT is not built by ICSF. Explanation: The Cryptographic Communications Vector Table is the major control block used in the operating system to govern ICSF service requests. It appears that ICSF has not been started in the operating environment. See also: ZPEN301E System Response: None User Response: Start an appropriately configured (and release) of ICSF if ICSF-based facilities are required for SecureZIP processing. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN303I
ZPEN303I Either ICSF is not up, or it is up in PCF mode. Explanation: It appears that ICSF is not currently running, or an older PCF service is running. See also: ZPEN301E System Response: None. User Response: Start an appropriately configured (and release) of
Encryption 234
ICSF if ICSF-based facilities are required for SecureZIP processing. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN304I
ZPEN304I There are no valid cryptographic units ACTIVE. Explanation: Although ICSF is operating, there are no active hardware cryptographic components in the system. Although one or more may show as ONLINE, they are not usable by ICSF due to configuration settings. See also: ZPEN301E System Response: None. User Response: Ensure that ICSF has been configured properly, and that the Master Key has been properly set for the cryptographic environment. Use the ICSF "COPROCESSOR MGMT" dialog to verify that one or more coprocessor facilities are ACTIVE before proceeding with SecureZIP use of ICSF facilities. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN305E
ZPEN305E-Unknown ICSF Error Code: +2+H+
Encryption 235
Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. An attempt was made to determine the what cryptographic facilities are available through ICSF, but required ICSF and/or hardware facilities are not operative. An unexpected error value was encountered. System Response: Unpredictable results. User Response: Report the error code and surrounding message information to PKWARE Technical Support. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN306I
ZPEN306I State Exception Found <State=%02X/Exception=%02X> Explanation: The Cryptographic Communications Vector Table is the major control block used in the operating system to govern ICSF service requests. When ICSF environmental conditions are determined to be inappropriate to ICSF operations through SecureZIP this message may be issued. State Flags: x'80' - An error has been detected (See Exception Flags) x'40' - ICSF is active in the system x'20' - The ICSF level supports CSFIQF x'10' - z/Architecture hardware is present x'08' - CPACF Crypto Assist Hardware is present x'04' - CSNBSYE/CSNBSYD API services are available Exception Flags: x'80' - The CCVT has never been initialized by ICSF x'40' - ICSF is not up in an appropriate mode x'20' - There are no hardware crypto devices available Sample State/Exception codes: State=80/Exception=80 - ICSF was never started. No other info is available (no CCVT) State=B4/Exception=40 - ICSF is in the process of starting but has not completed initialization. State=B4/Exception=60 - ICSF has been shut down.
Encryption 236
See also: ZPEN301E System Response: None User Response: Evaluate other messages surrounding the Exception. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN307I
ZPEN307I ICSF is [not] Active/CCVTACT Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. ICSF (which is required for IBMHARDWARE and IBMSOFTWARE cryptographic facility use) is active in the system. System Response: Request-dependent User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN308I
ZPEN308I ICSF is [not] at a proper level for CSFIQF Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. ICSF (which is required for IBMHARDWARE and IBMSOFTWARE
Encryption 237
cryptographic facility use) is at a release level that supports the ICSF Query Facility CSFIQF. This is necessary to determine whether more advanced cryptographic services (such as Hardware-based AES) are available for use. System Response: The requested operation continues. Note: If ICSF is not at a sufficient level to support the Query Facility, then some advanced system cryptographic services may not be available for use. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN309I
ZPEN309I z/Architecture Hardware Available %s Explanation: The Cryptographic Communications Vector Table is the major control block used in the operating system to govern ICSF service requests. The hardware classification is also shown. - CCF (Cryptographic Coprocessor Feature) may be available with Z/X00 or S/390 systems. - CPACF (CP Assist for Cryptographic Functions) may be active on Z/X90 or Z9 systems See also: ZPEN300I System Response: None User Response: None -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
Encryption 238
ZPEN310I
ZPEN310I CP Assist For Crytographic Functions Available Explanation: The Cryptographic Communications Vector Table is the major control block used in the operating system to govern ICSF service requests. CPACF hardware acceleration is available for select service requests. System Response: None User Response: None -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN313I
ZPEN313I CSNBSYE (AES) System capable with ICSF when available. Explanation: ICSF AES symmetric data encryption can be performed on this system if the IBM Hardware Cryptographic feature is enabled. The CSNBSYE API will be used to access the IBMSOFTWARE or IBMHARDWARE facility depending on the system hardware available. System Response: None. User Response: Ensure that ICSF has been configured properly, and that the harware cryptographic environment is active. Use the ICSF "COPROCESSOR MGMT" dialog to verify that one or more coprocessor facilities are ACTIVE before proceeding with SecureZIP use of ICSF facilities. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration
Encryption 239
Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN314I
ZPEN314I AES Software Only Available [system_classification] Explanation: Some systems (hardware) do not support hardware-based AES processing. ICSF will provide CSNBSYE API software emulation. Classification of hardware. S/390 Pre-zArchitecture, possibly with G5/G6 Z/X00 zArchitecture z800/z900, possibly with CCF Z/X90 zArchitecture z890/z990, with CPACF Z9 zArchitecture z9-109 or equivalen, with CPACF System Response: None. User Response: None. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN315I
ZPEN315I AES Hardware Available -cccccccc Explanation: A request was made to report on the available cryptographic facilities for the current operating environment with ICSF Query Service for ICSFSTAT. The status returned indicated that the AES encryption is available to run on the hardware. cccccccc Classification of hardware. S/390 Pre-zArchitecture, possibly with G5/G6 Z/X00 zArchitecture z800/z900, possibly with CCF Z/X90 zArchitecture z890/z990, with CPACF Z9 zArchitecture z9-109 or equivalent, with CPACF
Encryption 240
System Response: The requested operation continues. Note: If ICSF is not at a sufficient level to support the Query Facility, then some advanced system cryptographic services may not be available for use. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYMTX>
ZPEN316W
ZPEN316W Review DCicsf-SYE Conflict #[type] [ICSF_AES_lvl} Explanation: A request was made to report on the available cryptographic facilities for the current operating environment and the results returned from the ICSF Query Service for ICSFSTAT conflicted with the environment state settings. The environment state indicates that AES is available but the ICSFSTAT AES level indicates a different AES level. Message ZPEN313I would have been issued prior to this message. [type] is the environment type and the [ICSF_AES_lvl} is the ICSFSTAT AES level. System Response: The requested operation will try to continue but could result with an API error. User Response: This message should never be occur. Contact PKWARE, Inc. with associated documentation. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYMTX>
Encryption 241
ZPEN317W
ZPEN317W CSFIQF Invalid CPACF Byte [c] (Should be 0, 1 or 2) Explanation: A request was made to report on the available cryptographic facilities for the current operating and the results returned from the ICSF Query Service for ICSFSTAT CPACF availability. CPACF availability code was invalid and must be a 0, 1 or a 2. [c] is the returned code. System Response: The requested operation continues and assumes a code of 2 or DES/TDES enabled. User Response: This message should never be occur. Contact PKWARE, Inc. with appropriate documentation. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYMTX>
ZPEN318W
ZPEN318W CSFIQF Invalid AES Byte [c] (Should be 0, 1 or 2) Explanation: A request was made to report on the available cryptographic facilities for the current operating and the results returned from the ICSF Query Service for ICSFSTAT AES availability. "AES availability for clear keys" code was invalid and must be a 0, 1 or a 2. [c] is the returned code. System Response: The requested operation continues and assumes a code of 2 or AES hardware available. User Response: This message should never be occur. Contact PKWARE, Inc. with appropriate documentation. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog.
Encryption 242
For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYMTX>
ZPEN320I
ZPEN320I Crypto Facilities HW SW SecureZIP Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. A list of supported cryptographic algorithms follows indicating which API facilities are available for use by SecureZIP. See also: ZPEN321I The cryptographic API facilities are categorized into one of the following groups: HW - IBM Cryptographic Hardware SW - IBM Cryptographic Software SecureZIP - Software algorithms System Response: The requested operation continues. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN321I
ZPEN321I [crypto_algorithm] [hw_API] [sw_API] [SecureZIP_API] Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. A separate report line is listed for each algorithm to indicate which (if any) API is available for use by SecureZIP before dynamic evaluation. A subsequent check of each algorithm will be performed based on run-time options and environmental characteristics. See also: ZPEN320I, ZPEN342I
Encryption 243
[crypto_algorithm] The [crypto_algorithm] name will also identify the use type for the algorithm. Symmetric Data Encryption algorithms: 96 Bit Encryption AES 128 Encryption AES 192 Encryption AES 256 Encryption 3DES Encryption DES Encryption RC4 Encryption Data Integrity and Digital Signature algorithms: CRC32 Hashing SHA1 Hashing MD5 Hashing SHA256 Hashing SHA384 Hashing SHA512 Hashing [hw_API] [sw_API] The IBM Cryptographic facilities are accessed through one if the following ICSF APIs (hardware and software). ENC- CSNBENC/CSNBDEC Encipher/Decipher SYE- CSNBSYE/CSNBSYD Symmetric Key Encrypt/Decrypt OWH- CSNBOWH One way hash RNG- CSNBRNG Random Number Generation [SecureZIP_API] SecureZIP provides software algorithms using one of the following services. BSAFE-RSA BSAFE CryptoC PKW -PKWARE internal routine "------" indicates that no service facility could be identified under the API service category for the algorithm. System Response: The requested operation continues. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
Encryption 244
ZPEN322I
ZPEN322I [Facility Category] Seq: IBMHW(x) IBMSW(x) PKW(x) Explanation: As part of the CryptoAPI report (see also ZPEN320I), the specified FACILITY sequence is displayed. [x] - The preferred facility order of choice. 0 - Not included in the FACILITY list 1 - First selection if available for use 2 - Second selection if available for use 3 - Third selection if available for use See also: ZPEN340I, ZPEN341I, ZPEN342I [Facility Category] Encryptdata Algorithms associated with symmetric data encryption. HASH (Signature) Algorithms associated with hashing. Uses include digital signature creation and authentication. RandomData Algorithms associated with creating random data for encryption extensions (such as Cipher Block Chaining) System Response: The order of preference is used to select a viable CryptoAPI. User Response: See: FACILITY_ENCRYPTDATA, FACILITY_HASH, FACILITY_RANDOM -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN324E
ZPEN324E ICSF is not available. Either ICSF was not started, or ICSF has started, but does not have access to any cryptographic units. Your request cannot be processed. Explanation: A request to ICSF Query Service was made and returned a return code 12 with reason 0.
Encryption 245
System Response: IBM Hardware/Software API's will be assumed not available and will return a condition code of 12. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes" in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <PKCRYMTX>
ZPEN325E
ZPEN325E The CKDS or PKDS management service you called is not available because it has been disallowed by the ICSF User Control Functions panel. Explanation: A request to ICSF Query Service was made and returned a return code 12 with reason 4. System Response: IBM Hardware/Software APIs will be assumed not available and will return a condition code of 12. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes" in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <PKCRYMTX>
ZPEN326E
ZPEN326E The service or algorithm is not available on current hardware. Your request cannot be processed.
Encryption 246
Explanation: A request to ICSF Query Service was made and returned a return code 12 with reason 8. System Response: IBM Hardware/Software APIs will be assumed not available and will return a condition code of 12. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A ICSF and TSS Return and Reason Codes" in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <PKCRYMTX>
ZPEN327E
ZPEN327E An ICSF PKA service could not be performed because ICSF is being terminated. Any of the PKA services can issue this. Explanation: A request to ICSF Query Service was made and returned a return code 12 with reason 50. System Response: IBM Hardware/Software API's will be assumed not available and will return a condition code of 12. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A ICSF and TSS Return and Reason Codes" in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <PKCRYMTX>
ZPEN328E
ZPEN328E Service could not be performed because the required PCICC or
Encryption 247
PCIXCC/CEX2C was not active. Explanation: While generating random numbers using the CSNBRNG API, an error was encountered. The return code 12 and and the reason code was 11060 indicating the required PCICC or PCIXCC/CEX2C hardware was not active. System Response: The requested function is terminated. User Response: If the service required a specific PCICC or PCIXCC/CEX2C, verify that the value specified is correct. Reissue the request when the required PCICC or PCIXCC/CEX2C is available. Review log for more details. Invoking module: <EVTCRYPT> <PKCRYMTX>
ZPEN329E
ZPEN329E The call to the service could not be processed because ICSF found something seriously wrong in its environment or a processing error occurred in the PCICC or PCIXCC/CEX2C. Explanation: A request to ICSF Query Service was made and returned a return code greater than 12. System Response: IBM Hardware/Software API's will be assumed not available and will return a condition code of 12. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes" in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <PKCRYMTX>
ZPEN330E
ZPEN330E QueryIBMStatus -AMUTCQRY Error was found [return code] Explanation: A request to the operating system environment was made with AMUTCQRY function, and while examining the returned
Encryption 248
contents, a failure occurred. [return code] is the code returned. System Response: The requested operation fails to be able to determine the correct availability of encryption available in the OS environment. Note: If ICSF is not at a sufficient level to support the Query Facility, then some advanced system cryptographic services may not be available for use. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYMTX>
ZPEN331I
ZPEN331I ICSF is not Available for [type] - AMUTCQRY status([status]) Explanation: A request to the operating system environment was made to check the status of ICSF for API [type]. AMUTCQRY return a status of [status code] which indicated that the ICSF is not available. [type] "Encryptdata " "Hash (Signature)" "Randomdata " System Response: The requested operation fails to be able to determine the correct availability of encryption available in the OS environment. Note: If ICSF is not at a sufficient level to support the Query Facility, then some advanced system cryptographic services may not be available for use. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog.
Encryption 249
For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYMTX>
ZPEN332E
ZPEN332E Invalid QueryIBMerror error ([reason code]). Explanation: A request to ICSF Query Service was made and returned an unexpected return code. The [reason code] is the hex value.* System Response: IBM Hardware/Software APIs will be assumed not available and will return a condition code of 12. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A ICSF and TSS Return and Reason Codes" in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <PKCRYMTX>
ZPEN333E
ZPEN333E CtlMatrx HW_ParseConfig failure. Explanation: A request to analyze the cryptographic facilities was issued but the facility configuration parameters were incorrect. If this occurs, an internal error has occurred. System Response: Cryptography options will not take place followed by a return of of 12. User Response: Contact PKWARE, Inc. with Job Log. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration
Encryption 250
Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYMTX>
ZPEN335I
ZPEN335I CSRSI Error (return code) Reason Explanation: The PKCRYUTL basic system query to profile the hardware base failed. System Response: None User Response: For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN336I
ZPEN336I CSRSI Query IBM Type(cpu_type) Mod(model) S/N(serial_number) Explanation: The PKCRYUTL utility program performed a basic system query to profile the hardware base. System Response: None User Response: For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN337I
ZPEN337I Assuming Hardware Class (S/390 ) Explanation: Hardware class S/390 is assumed if hardware query fails. Message ZPEN335I will preceed this message. System Response: None User Response: For more information, see the SecureZIP Administrator Guide*
Encryption 251
Invoking module: <PKCRYMTX>
ZPEN340I
ZPEN340I /--------[Facility_Category] Matrix ([type_code]) --------/ Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. A separate report is listed for each category of cryptographic service. All associated algorithms are included in the report along with resulting selection results. See also: ZPEN341I, ZPEN342I for report line details. [Facility_Category] Encryptdata Algorithms associated with symmetric data encryption. HASH (Signature) Algorithms associated with hashing. Uses include digital signature creation and authentication. System Response: If no facilities are available for a given algorithm, subsequent service request will fail. If one or more facilities are available for a given algorithm, then the preferred order specified by the associated FACILITY setting will govern which facility will be used for all subsequent service requests. User Response: If a cryptographic request fails for an algorithm, adjust the associated FACILITY setting to choose a category associated with "-NoFacil-". -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
Encryption 252
ZPEN341C
ZPEN341C Status-IBMHW([APIstate]) IBMSW([APIstate]) PKW([APIstate]) Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. A separate report line is listed for each algorithm to indicate which (if any) API is available for use by SecureZIP after dynamic evaluation. Each algorithm is validated against requested FACILITY settings, licensing and facilities reported by ICSF. See also: ZPEN341I, ZPEN321I [APIstate] The state of each facility type is reported for the algorithm reported in the preceeding ZPEN341I message. State definitions are as follows: -NotCap- The facility category is not capable of servicing this algorithm, and is therefore not available for use. -NoAPI- No API could be identified as being available for use in the current run-time environment. -NoFacil- This facility was not listed in the associated FACILITY setting, and is not available for use. -NoLic- The product does not have the appropriate SecureZIP feature license code enabled to make use of this facility category. -NotSup- This algorithm is not supported under the current release of SecureZIP. BSAFE BSAFE(r) CryptoC routines included with the SecureZIP product has been identified as being viable for use. ENC/DEC For the system platform being executed on, the ICSF CSNBENC(encipher) and CSNBDEC(decipher) API calls were identified as viable for use. SYE/SYD For the system platform being executed on, the ICSF CSNBSYE(symmetric key encipher) and CSNBSYD(symmetric
Encryption 253
key decipher) API calls were identified as viable for use. PKW A PKWARE proprietary routine was identified as viable for use. OWH For the system platform being executed on, the ICSF CSNBOWH(One Way Hash) API call was identified as viable for use. System Response: If no facilities are available for a given algorithm, subsequent service request will fail. If one or more facilities are available for a given algorithm, then the preferred order specified by the associated FACILITY setting will govern which facility will be used for all subsequent service requests. User Response: If a cryptographic request fails for an algorithm, adjust the associated FACILITY setting to choose a category associated with "-NoFacil-". -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN341I
ZPEN341I [alg_id]([algorithm_name]) Select ([code]) [Facility Category] Explanation: A request was made to report on the available cryptographic facilities for the current operating environment. A separate report line is listed for each algorithm to indicate which (if any) API is selected for use by SecureZIP after dynamic evaluation. Each algorithm is validated against requested FACILITY settings, licensing and facilities reported by ICSF. See also: ZPEN342I has detailed information to interpret the [code] for each facility category.
Encryption 254
[Facility Category] The final facility chosen is shown. NONE FOUND No viable facility could be identified for use. This algorithm cannot be serviced with the current configuration. IBM Hardware The CryptoAPI identified in ZPEN321I (HW) will be used IBM Software The CryptoAPI identified in ZPEN321I (SW) will be used SecureZIP The CryptoAPI identified in ZPEN321I (PKW) will be used System Response: If no facilities are available for a given algorithm, subsequent service request will fail. If one or more facilities are available for a given algorithm, then the preferred order specified by the associated FACILITY setting will govern which facility will be used for all subsequent service requests. User Response: If a cryptographic request fails for an algorithm, adjust the associated FACILITY setting to choose a category associated with "-NoFacil-". -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN342C
ZPEN342C +121+C+ Explanation: The continuation messages for ZPEN342I provide details regarding the types of keys that may be available for processing, and whether they are FIPS 140 compliant. Note: Secure key operations performed in a FIPS 140
validated cryptographic coprocessor are considered to be FIPS 140 compliant.
Encryption 255
"AES is [NOT] available. 3DES is [NOT] available." This message reflects the general algorithms that are available for use in ICSF. Minimally, Clear Key operations may be used. See additional clarification messages below to determine whether Secure Key (FIPS 140) operations are available for specific algorithms.
"Secure Key Encryption not supported."
This message indicates that there are no hardware facilities available for use to perform Secure Key operations. Therefore, FIPS 140 processing is not available for any algorithm.
"<alg1> <alg2> ... <algN> supports Secure Key Encryption."
This message lists the specific algorithms (and key lengths) for which Secure Key (FIPS 140) operations may performed in the active operating environment.
(e) - Compliance has Expired.
"Effective May 19, 2005: Federal Agencies may continue to use DES as a NIST recommended Approved security function in a FIPS Approved mode of operation in FIPS 140-1 or FIPS 140-2 validated cryptographic modules for a period of 2 years (until May 19, 2007)."
http://csrc.nist.gov/groups/STM/common_documents/DESTranPlan.pdf
System Response: None required. User Response: None required. Invoking module: <PKCRYMTX>
ZPEN342I
ZPEN342I Facility [is NOT] Found to be FIPS [type] Compliant Explanation: A request was made to report on the available cryptographic facilities for the current operating environment with ICSF Query Service for STATEXPT. The query verified that the coprocessor is active and available for processing. The status returned indicated that the encryption algorithm is available to run in [type] mode. [type] 140-1 or 140-2. See the SecureZIP Administrator Guide for details. See also: ZPEN342C for details regarding Secure Key operations. See also: ZPEN314I and ZPEN315I regarding Clear Key operations. Note: Secure key operations performed in a FIPS 140
Encryption 256
validated cryptographic coprocessor are considered to be FIPS 140 compliant. SecureZIP for z/OS v9.0 may be said to be running in FIPS mode and FIPS 140-1 Compliant when the following conditions are satisfied: 1. The program is running on an IBM eServer System z800 or z900 with a CMOS Cryptographic Coprocessor Facility (CCF). This cryptographic module is FIPS 140-1 validated under certificate number 118. 2. When the program is encrypting data, one of the following options is specified: FACILITY_ENCRYPTDATA(IBMHARDWARE) ENCRYPTION_METHOD(DES) or ENCRYPTION_METHOD(3DES) SecureZIP for z/OS SE and EE v10.0 may be said to be running in FIPS mode and FIPS 140-2 Compliant when the following conditions are satisfied: 3DES 1. The program is running on an IBM eServer System z890 or z990 with a PCIX cryptographic coprocessor (PCIXCC) or a System z890, z990, z9, or z10 with a Crypto Express2 Coprocessor (CEX2C). Both of these cryptographic modules are FIPS 140-2 validated under certificate number 524 and 661. 2. When the program is encrypting data, one of the following options is specified: -FACILITY_ENCRYPTDATA(IBMHARDWARE) -ENCRYPTION_METHOD(3DES) AES 1. The program is running on an IBM system qualified for use with AES secure key operations. Components requiring qualification include: a. Crypto Express2 Coprocessor (with appropriate MCL) b. System z hardware c. ICSF at a minimum release of HCR7751 d. Configured system AES master key 2. When the program is encrypting data, one of the following options is specified: -FACILITY_ENCRYPTDATA(IBMHARDWARE) -ENCRYPTION_METHOD(AES128|AES192|AES256) System Response: None required. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog.
Encryption 257
See -FIPSMODE processing requirements. Invoking module: <PKCRYMTX>
ZPEN343E
ZPEN343E Environment NOT FIPS [type] Compliant with Required Options Explanation: A request was made to run in FIPS [type] Mode, but the operating environment does not support the level with current available cypto coprocessors. [type] 140-1 or 140-2. See the SecureZIP Administrator Guide for detials. System Response: The request is terminated. 1. The ZIP run will be halted. 2. UNZIP processing for the file will be bypassed and flagged as a file in error. 3. PKCRYUTL will have a return code of 8 and will be halted. User Response: See -FIPSMODE processing requirements. 1. Correct the process settings to satisfy the FIPSMODE specification (ZIP processing only). 2. Change the FIPSMODE specification to permit processing to continue without requiring FIPS enforcement. For more information, see the SecureZIP Administrator Guide and or message ZPEN342I for more details on FIPS Mode. Invoking module: <PKCRYMTX>
ZPEN343I
ZPEN343I Environment NOT FIPS [type] Compliant with Required Options Explanation: A request was made to run in FIPS [type] Mode, but the operating environment does not support the level with current available cypto coprocessors. [type] 140-1 or 140-2. See the SecureZIP Administrator Guide for detials. System Response: The request is terminated. 1. The ZIP run will be halted. 2. UNZIP processing for the file will be bypassed and flagged as a file in error. 3. PKCRYUTL will have a return code of 8 and will be halted. User Response: See -FIPSMODE processing requirements.
Encryption 258
1. Correct the process settings to satisfy the FIPSMODE specification (ZIP processing only). 2. Change the FIPSMODE specification to permit processing to continue without requiring FIPS enforcement. For more information, see the SecureZIP Administrator Guide and or message ZPEN342I for more details on FIPS Mode. Invoking module: <PKCRYMTX>
ZPEN344I
ZPEN344I Environment DES or 3DES not available on hardware. Explanation: A request was made to report on the available cryptographic facilities for the current operating environment with ICSF Query Service for STATEXPT. The query verified that the coprocessor is active, available for processing and that DES and 3DES are & available for encryption/decryption. System Response: None required. User Response: None required. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. The PKCRYUTL program may be run independently, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog. For more information, see the SecureZIP Administrator Guide and or message ZPEN342I for more details on FIPS Mode. Invoking module: <PKCRYMTX>
ZPEN350I
ZPEN350I PKCRYUTL 1.x Cryptographic API Review Utility Copyright (C) 1989-2007 PKWARE, Inc. All rights reserved. Program and Output used by permission only. PKWARE, Inc. Explanation: The PKCRYUTL utility program is used to evaluate which cryptographic facilities are available for use in the current operating environment. System Response: None User Response: For more information, see the SecureZIP Administrator Guide
Encryption 259
Invoking module: <PKCRYMTX>
ZPEN351I
ZPEN351I PKCRYUTL Unregistered copy expires mm/dd/yyyy Explanation: The PKCRYUTL utility program is used by permission of PKWARE, Inc. System Response: None User Response: For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN359I
ZPEN359I No Active [Crypto/Hash] Algorithm for [algorithm_name] ([alg_id]) Explanation: A request was made to encrypt, decrypt or hash data, but the algorithm requested was not available with current cryptographic facilities settings. System Response: If no facilities are available for a given algorithm, subsequent service request will fail. Message ZPEN359C Reverting to SecureZIP Facility will follow to indicate SecureZIP's APIs will be used. User Response: Review the FACILITY settings in comparison to the algorithm being used. -SHOW_SETTINGS may be used to produce the associated report within a SecureZIP run. For more information, see the SecureZIP Administrator Guide* Invoking module: <EVTCRYPT> <EVTHASH>
ZPEN360E
ZPEN360E Hash Generate #d failed:Return Code=4d,Reason Code=4d Explanation: While generating a hash, the Hash CSNBOWH API encountered an error. The return code and the reason code should
Encryption 260
describe the problem encountered and action to take. The error occurred in process step #d. System Response: The requested function is terminated. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes"* in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <EVTHASH>
ZPEN361I
ZPEN361I [type] Matrix ([type code]) Explanation: Is displayed as a heading for each algorithm tested when running PKCRYUTL with Test selected along with the report for detail test results is selected. Example:ZPEN361I Encryptdata Matrix (01) [type] [type code] Encryptdata 01 Hash (Signature) 02 Randomdata 03 System Response: None. User Response: None. Invoking module: <PKCRYUTL>
ZPEN362I
ZPEN362I ([intl AlgId])[Alg Desc] Select ([intl ctlmask])[facility] Explanation: Is displayed as a heading for each algorithm tested when running PKCRYUTL with Test selected along with the report for detail test results is selected. Example:(660E)AES 128 Encryption Select (20)IBM Software [intl AlgId] An internal algorithm id used for indexing [Alg Desc] 'Encryptdata', 'Hash (Signature)', or 'Randomdata'.
Encryption 261
[intl ctlmask] An internal mask byte for matrix control [facility] Which facility being tested: 'IBM Hardware', 'IBM Software' or 'SecureZIP'. System Response: None. User Response: None. Invoking module: <PKCRYUTL>
ZPEN364E
ZPEN364E Need at least 3 parms argc=[nbr of arg] Explanation: A request was made for PKCRYUTL with less than 3 (three) parameters. [nbr of arg] is the number of actual parameters being passed. System Response: Program will fail. User Response: Review all parameters being passed. With supplied JCL and ISPF procedures this should not occur. Invoking module: <PKCRYUTL>
ZPEN365E
ZPEN365E Memory request failure ([request size]) Explanation: Program PKCRYUTL encountered an error when attempting a malloc(). [request size] is the number of bytes requested.* System Response: PKCRYUTL program will fail. User Response: Review region size and try to increase size. If the error continues, contact PKWARE, Inc. with joblog. Invoking module: <PKCRYUTL>
ZPEN368I
ZPEN368I Will not test matrix<->
Encryption 262
Explanation: The "text matrix" parameter (Parm 3) passed to PKCRYUTL indicated that no test should be performed. System Response: None User Response: For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN370I
ZPEN370I *************Start of Testing********************** *************Nbr of Bytes=[nbr bytes]************** *************Nbr of MEG=[nbr of Meg]*************** Explanation: Is displayed as a heading for when PKCRYUTL starts its testing mode. [nbr bytes] The actual byte count that will be tested. [nbr of Meg] The number of megabytes that [nbr bytes] represents. System Response: None User Response: None Invoking module: <PKCRYUTL>
ZPEN373E
ZPEN373E Quiting due to Error ([reason code]) ([mtx status]) Explanation: A failure occurred in PKCRYMTX module with [reason code] and [mtx status]. PKCRYUTL will end abnormally. System Response: PKCRYUTL will fail and return condition code 12. User Response: Review all previous messages issued and joblog to determine why PKCRYUTL failed. Invoking module: <PKCRYUTL>
Encryption 263
ZPEN374I
ZPEN374I Completing with Return Code=[rtn code] Error Code=[error code]---- Explanation: PKCRYUTL is completing and the final return code and the major error code that occurred during the run will be displayed. System Response: None. User Response: If the [rtn code] or [error code] are both not zero (0), then review all previous messages for more detail why PKCRYUTL did not run successfully. Invoking module: <PKCRYUTL>
ZPEN375I
ZPEN375I [algorithm] [process] for [facility] Test CPU [cpu seconds] sec. Explanation: A request was made to test each algorithm and to show detail test result report. After each test this message shows the number CPU seconds per test. Example: AES 128 Encryption for SecureZIP Test CPU 0.166581 sec. [process] " Decrypt/Compare" are for the decryption and the compare process. i.e. AES 128 Encryption Decrypt/Compare for SecureZIP Test CPU 0.173777 sec System Response: None. User Response: None. Invoking module: <PKCRYUTL>
ZPEN377E
ZPEN377E [Alg Desc] for [facility] Test Failed rc=[return_code] Explanation: A request was made to test each algorithm. While testing an unexpected error occurred with [return_code]. [Alg Desc] Description of Algorithm that failed. [facility] Which facility being tested: 'IBM Hardware', 'IBM Software' or 'SecureZIP'. System Response: PKCRYUTL will fail for the tested Algorithm.
Encryption 264
User Response: Review all previous messages issued to help determine why PKCRYUTL may have failed. If test continues to fail contact PKWARE Inc. with detail joblog and output. Invoking module: <PKCRYUTL>
ZPEN378I
ZPEN378I Testing with [nbr of bytes] Bytes Active Explanation: The PKCRYUTL parameter to test each algorithm was submitted with [nbr of bytes] to test. System Response: None. User Response: None. Invoking module: <PKCRYUTL>
ZPEN379I
ZPEN379I Decryption/Compare Results Active Explanation: The PKCRYUTL parameter to test each encryption algorithm and the Decryption/Compare parameter were submitted. System Response: None. User Response: None. Invoking module: <PKCRYUTL>
ZPEN380E
ZPEN380E Decryption/Compare Failed Explanation: The PKCRYUTL parameter to test each encryption algorithm and to with the Decryption/Compare was entered. While running the Decryption/Compare process, a failure occurred and did not complete. System Response: PKCRYUTL will return condition code 12.
Encryption 265
User Response: Review joblog and output for PKCRYUTL for other errors. If test continues to fail contact PKWARE Inc. with detail joblog and output. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYUTL>
ZPEN381I
ZPEN381I [Alg Desc] for [facility] Not Tested Explanation: A request was made to test all algorithms. Some algorithms are not supported for testing with PKCRYUTL such as "96 Bit Encryption for SecureZIP". This message is informational only to indicate algorithm was not tested. [Alg Desc] Description of Algorithm that failed. [facility] Which facility being tested: 'IBM Hardware', 'IBM Software' or 'SecureZIP'. System Response: None. User Response: None. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYUTL>
ZPEN382W
ZPEN382W Test being restricted to 10M with Compare Explanation: The PKCRYUTL parameter to test each encryption algorithm and the parameter to compare the decrypted data to the original test data was submitted. The number of bytes to test exceeded the 10Meg Maximum for compare process. System Response: The number of bytes to test is revised to 10Meg and the process continues. User Response: None.
Encryption 266
Invoking module: <PKCRYUTL>
ZPEN383I
ZPEN383I Crypto Facilities HW SW SecureZIP Explanation: A request was made to produce a timing report for supported cryptographic facilities in the current operating environment. A list of supported cryptographic algorithms follows indicating which API facilities are available for use by SecureZIP. A list of supported cryptographic algorithms follows showing timing test values for each. A preceding header line will indicate whether this report is for raw TCB CPU time, or a computed throughput rate in megabytes per CP Second. See also: ZPEN384I System Response: None User Response: None The PKCRYUTL program is run, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog to produce this report. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN384I
ZPEN384I [crypto_algorithm] [hw_API] [sw_API] [SecureZIP_API] Explanation: A request was made to produce a timing report for supported cryptographic facilities in the current operating environment. A value will be listed for each facility category associated with the correlated facility API listed in ZPEN321I. An "*" following a timing value indicates that the corresponding API will be selected based on the facility preference list shown in ZPEN322I. A preceding header line will indicate whether this report
Encryption 267
is for raw TCB CPU time, or a computed throughput rate in megabytes per CP Second. See also: ZPEN383I, ZPEN321I, ZPEN322I Note: The "96 bit encryption" algorithm will not have timings run. The SecureZIP(PKW) facility API will always be selected for use when ENCRYPTION_METHOD(STANDARD) is specified. System Response: None User Response: None The PKCRYUTL program is run, either in batch, or through the SecureZIP Administration Cryptographic Utilities dialog to produce this report. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCRYMTX>
ZPEN385I
ZPEN385I Testing Completed Total CPU Seconds([CPU seconds]) Elapsed Seconds([elapsed seconds]) Explanation: A request was made to test each algorithm. This message is issued to indicate all testing has completed and shows the total CPU seconds used and the total elapse seconds since testing began. Example: -Testing Completed Total CPU Seconds(5.718) Elapsed Seconds(0.200) System Response: None. User Response: None. Invoking module: <PKCRYUTL>
ZPEN392E
ZPEN392E Testing Failed at byte [offset] of [nbr_of_bytes] bytes Explanation: A request was made to test encryption and compare the decrypted results to the original test data. While comparing the decrypted results to the original test data, a difference was found at [offset] byte.
Encryption 268
System Response: PKCRYUTL will continue with testing and will return a condition code 12. User Response: Review joblog and output for PKCRYUTL for other errors. If test continues to fail contact PKWARE Inc. with detail joblog and output. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYUTL>
ZPEN393E
ZPEN393E Testing Failed with byte count difference Explanation: A request was made to test encryption and to compare the decrypted results to the original test data. While comparing the decrypted results to the original test data, the number of bytes for the results did not match the number of bytes of the original test data. System Response: Message ZPEN394I will be issued and PKCRYUTL will continue with other testing. PKCRYUTL will return condition code 12. User Response: Review joblog and output for PKCRYUTL for other errors. If test continues to fail contact PKWARE Inc. with detail joblog and output. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYUTL>
ZPEN394I
ZPEN394I Test Bytes In=[in byte count], Bytes from Decrypt=[in byte count] Explanation: A request was made to test encryption and to compare the decrypted results to the original test data. While comparing the decrypted results to the original test data, the number of bytes did not match. This message will follow the message ZPEN393E.
Encryption 269
System Response: PKCRYUTL will continue with testing and will return a condition code 12. User Response: Review joblog and output for previous PKCRYUTL errors. If test continues to fail contact PKWARE Inc. with detail joblog and output. For more information, see the SecureZIP Administrator Guide Invoking module: <PKCRYUTL>
ZPEN399I
ZPEN399I facility_category Matrix (type_code) Matrix Dump Heading Explanation: An internal control array is displayed to assist PKWARE Technical Support System Response: None User Response: None Invoking module: <PKCRYMTX>
ZPEN403E
ZPEN403E CSNBCKM Import Failed:Return Code=4d,Reason Code=4d Explanation: While initializing the decryption/encryption process, the importing of the session key failed using the CSNBCKM API. The return code and the reason code should describe the problem encountered and action to take. System Response: The requested function is terminated. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes"* in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details.
Encryption 270
Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <EVTCRYPT>
ZPEN404E
ZPEN404E "API-name" Encipher step n Failed:Return Code=4d,Reason Code=4d Explanation: While performing encryption, the encipher API encountered an error. The return code and the reason code should describe the problem encountered and action to take. System Response: The requested function is terminated. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes"* in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <EVTCRYPT>
ZPEN405E
ZPEN405E "API-name" Decipher step n Failed:Return Code=4d,Reason Code=4d Explanation: While performing decryption, the decipher API encountered an error. The return code and the reason code should describe the problem encountered and action to take. System Response: The requested function is terminated. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes"* in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required.
Encryption 271
Invoking module: <EVTCRYPT>
ZPEN406E
ZPEN406E CSNBRNG Random Generator Failed:Return Code=4d,Reason Code=4d Explanation: While generating random numbers using the CSNBRNG API, an error was encountered. The return code and the reason code should describe the problem encountered and action to take. System Response: The requested function is terminated. User Response: Lookup the Return/Reason code information to determine whether a configuration or environmental condition caused the error. Reference "Appendix A.ICSF and TSS Return and Reason Codes"* in IBM Document SA22-7522 "z/OS ICSF Application Programmer's Guide for details. Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <EVTCRYPT>
ZPEN407W
ZPEN407W Invalid API Method(%d) Algo(%04X) Explanation: While initializing the decryption/encryption process, the API Selection Method for the algorithm was invalid. There is no valid decryption/encryption facility specified. System Response: The requested function is terminated. User Response: Contact PKWARE Technical Support and provide the Return and Reason code information when assistance is required. Invoking module: <EVTCRYPT>
ZPEN411E
ZPEN411E [%type] File could not be opened:<%path/file> (%errdecp).
Encryption 272
Explanation: While trying to process a PartnerLink certificate request an error occurred in opening the [%path/file] file. [%type] - Type of certificate package type in error. "PartnerLink Recipient" or "PartnerLink Authenticator" [%path/file] - The full file name that could not be opened. [%errdecp] - Error description. "File Not Found" or "Reason Code=%status/%errornbr" where %status is an internal status code and %errornbr is IO error code number. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Review job log and previous errors for more information. Verify that the appropriate file exists and that it is valid. Correct job or environment and re-run. Invoking module: <CSBSCRTE>
ZPEN412E
ZPEN412E [%type] File had IO error during read:<%path/file> (%errdecp). Explanation: While trying to process a PartnerLink certificate request an error occurred while reading the [%path/file] file. [%type] - Type of certificate package type in error. "PartnerLink Recipient" or "PartnerLink Authenticator" [%path/file] - The full file name that could not be read. [%errdecp] - Error description. "Reason Code=%status/%errornbr" where %status is an internal status code and %errornbr is IO error code number. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Review job log and previous errors for more information. Verify that the appropriate file exists and that it is valid. Correct job or environment and re-run.
Encryption 273
Invoking module: <CSBSCRTE>
ZPEN413E
ZPEN413E [%store] Store could not be opened:<%path/file> (%errdecp). Explanation: While trying to process a certificate request an error occurred in opening the [%path/file] file. [%store] - Store type in error. "CA", "ROOT", or "CRL" [%path/file] - The full file name of the store that could not be opened. [%errdecp] - Error description. "File Not Found" or "Reason Code=%status/%errornbr" where %status is an internal status code and %errornbr is IO error code number. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Review job log and previous errors for more information. Verify that the appropriate file exists and that it is valid. Correct job or environment and re-run. Invoking module: <CSBSCRTE>
ZPEN414E
ZPEN414E [%store] Store had IO error during read:<%path/file> (%errdecp). Explanation: While trying to process a certificate request an error occurred in reading the [%path/file] store file. [%store] - Store type in error. "CA", "ROOT", or "CRL" [%path/file] - The full file name of the store that could not be read. [%errdecp] - Error description. "Reason Code=%status/%errornbr"
Encryption 274
where %status is an internal status code and %errornbr is IO error code number. System Response: Processing is terminated. RC = 12 is set for the run. User Response: Review job log and previous errors for more information. Verify that the appropriate file exists and that it is valid. Correct job or environment and re-run. Invoking module: <CSBSCRTE>
Extract Manager 275
ZPEX - Extract Manager Messages
ZPEX000I
ZPEX000I +121+C Explanation: Extract Manager processing information. Various string messages listed below, with a separate explanation for each string. ZPEX000I ATTEMPT TO OVERWRITE UNMOVABLE DATA SET: data.set.name Invoking module: <ACEXMAIN> See also: ZPFM000I Occurs when an unmovable data set is targeted dynamic allocation, and -OVERWITE=Y is specified. Occurs when an unmovable data set is targeted by -OUTDD= command, and -OVERWITE=Y is specified. PKZIP cannot reliably overwrite unmovable files. See also: ZPFM000I System Response: If the target is an -OUTDD=ddname, no files are extracted, the return code is set to 12. If the target was allocated dynamically, the file is bypassed, and the return code is set to 4. User Response: If the file must be restored, delete the original data set, and re-allocate it, and rerun the job. PKZIP will extract the file, but the unmovable attribute will NOT be set, and if the data set was a Checkpointed, data set, the checkpoint indicator is NOT set.
ZPEX001C
ZPEX001C ... +100+C+ Explanation: Extract Manager processing information. Continuation of ZPEX001I is turned on. System Response: None User Response: None Invoking module: <ACEXMAIN>
Extract Manager 276
ZPEX001I
ZPEX001I tested okay +100+C+ Explanation: Extract Manager processing information. -ACTION(TEST) was requested, and the file shown "tested" correctly. System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX001W
ZPEX001W +12+C+ +100+C+ Explanation: Extract Manager processing warning. A problem was encountered during the EXTRACT process. Reasons may include: "RDW > 32K" A record length was encountered that was too large to process, and the output file was not defined for spanning. "PASSWORD ERR"- Check case sensitivity for password. "CRC Error "- The data integrity check failed. "DATA Error "- The data integrity check failed. "Inflate ERR "- The compressed data stream was found to have invalid compression codes. System Response: Processing for the file is terminated. User Response: Try to determine the reason for the failure. If attempting to process a GZIP and "CRC Error" is encountered, an incorrect data set format (e.g. RECFM=F/FB) could be the cause. You can use -GZIPCRC_IGNORE=Y to bypass the failure and permit the data to be extracted. When a password error is indicated with the following conditions both true, refer to information regarding fix TT3057. 1. The password value is > 95 characters. 2. The archive file was created with PKZIP for zSeries or SecureZIP for zSeries without TT3057 previously applied.
Extract Manager 277
Invoking module: <ACEXMAIN>
ZPEX002C
ZPEX002C ... +100+C+ Explanation: Extract Manager processing information. Continuation for ZPEX002I System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX002I
ZPEX002I +100+C+ Explanation: When UNZIP processing is complete, (successfully, or in error), the file name +100+C+ will be listed. See also ZPEX002C System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX003I
ZPEX003I Extracted to +54+C+ Explanation: Extract Manager processing information. Upon a successful EXTRACT (or SIMULATE) of a file, this message reports the destination file name. System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX004I
ZPEX004I Archive Central Directory extracted for processing.
Extract Manager 278
Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message is issued to indicate that a special form of the Archive Central Directory was encountered (compressed and/or encrypted). The Central Directory was decrypted and/or decompressed to a temporary file for parsing. System Response: Processing continues User Response: None Invoking module: <ACEXMAIN>
ZPEX010E
ZPEX010E Extract failed. Explanation: Extract Manager processing error detected. The request to process a file from a ZIP archive could not be completed. System Response: Processing for the file was terminated. Message ZPEX002I will accompany this message to indicate which file could not be processed. User Response: Check the SYSPRINT and LOG messages for indications of the failure reason. Invoking module: <ACEXMAIN>
ZPEX011E
ZPEX011E Error opening Archive +44+C+ for +50+C+ Explanation: Extract Manager processing error detected. The input Archive could not be re-opened to extract file +50+C+. System Response: Processing for the file +50+C+ is terminated. User Response: Check the SYSPRINT and LOG messages for indications of the failure reason. Invoking module: <ACEXMAIN>
ZPEX012E
ZPEX012E Error allocating new output file +54+C+ Explanation: Extract Manager processing error detected.
Extract Manager 279
The dynamic creation of the output file failed. System Response: Processing of the file is terminated. User Response: Check SYSPRINT and the JOBLOG for other messages that may indicate the reason for the failure. Invoking module: <ACEXMAIN>
ZPEX013I
ZPEX013I Record(s) wrapping. Rec#/Len: +output_record+ +total_len+ Explanation: Extract Manager processing information. While Extracting the data, record(s) were found, whose length exceeded that of the output file. The option requesting that long record length wrapping was found to be on. (See also: ZPEX013W) +output_record+ The message is issued for the first portion of the record being written with respect to the output file. This will assist the user in locating the wrapped record in the extracted file. For the first instance of a long record being wrapped, it also corresponds to the logical record number coming from the extracted file. However, subsequent events will no longer match the original record number based on the number of previous wrapping output records counted. +total_len+ The represents the total length of the record to be wrapped. The number of output wrapping records can be determined from the total record length and the output files LRECL. System Response: The long record is wrapped to 1 or more additional output records depending upon the output file record length. By default, only the first occurrence of record truncation will cause ZPEX013I to be issued. This is an informational message and does not set a return code. User Response: If wrapping is not desired, specify an LRECL large enough to contain the greatest record length. It may be helpful to use variable length records for the output data set along with a very large LRECL. -LOGGING_LEVEL(VERBOSE) may be used
Extract Manager 280
to see every occurrence of record truncation. Invoking module: <ACEXMAIN>
ZPEX013W
ZPEX013W Record(s) being truncated to LRECL=+8+D+. Record# +8+D+ is +4+D+ bytes. Explanation: Extract Manager processing warning. While Extracting the data, record(s) were found, whose length exceeded that of the output file. System Response: Processing of the file continues, but some data has been truncated. | RC=4 is the default associated with this condition | By default, only the first occurrence of record truncation will cause ZPEX013W to be issued. User Response: Specify an LRECL large enough to contain the greatest record length. | -PKSUPPRC(ZPEX013W) may be coded to suppress the return code normally set by this condition. (The message will still be displayed). | If not suppressed, -LOGGING_LEVEL(VERBOSE) may be used to see every occurrence of record truncation. Invoking module: <ACEXMAIN>
ZPEX014W
ZPEX014W Encrypted file skipped. Password not provided or not valid. Explanation: Extract Manager processing warning. A file was identified for processing, but the -PASSWORD value (if provided) was not correct for decrypting the file. A password may only be used for decryption when password-based encryption was used to ZIP the file. SecureZIP for z/OS and other PKWARE products also support recipient-based encryption through the use of digital certificates. Note: If multiple files are being processed, this may be a valid condition if different passwords were specified during various ZIP runs.
Extract Manager 281
System Response: The file is bypassed, but other files will be processed. User Response: Specify the correct password for this file, or ignore the message. When a password error is indicated with the following conditions both true, refer to information regarding fix TT3057. 1. The password value is > 95 characters. 2. The archive file was created with PKZIP for zSeries or SecureZIP for zSeries without TT3057 previously applied. Invoking module: <ACEXMAIN>
ZPEX015I
ZPEX015I Retrying allocation without specified/inherent VOLUME information. Explanation: Extract Manager processing information. During the EXTRACT process of creating an output file, Dynamic Allocation detected that the combination of the unit and volser (from defaults, commands, inherent saved attributes in the Archive and system management routines) were incompatible. System Response: PKZIP will discard the VOLSER information and retry the allocation with the unit information available. User Response: If additional information regarding the allocation request is needed, perform a VIEWDETAIL for the file and match with the command values (with a SHOW_SETTINGS command in the UNZIP run). -LOGGING_LEVEL=VERBOSE can be used to display Dynamic Allocation specifications during the EXTRACT process to see the Volume and Unit information being requested. Invoking module: <ACEXMAIN>
ZPEX016W
ZPEX016W Encrypted file skipped. No valid password or recipient certificate provided. Explanation: Extract Manager processing warning. A file was identified for processing, but the -PASSWORD value (if provided) was not correct for decrypting the file, and there were no matching private-key recipient certificates (SecureZIP feature only) provided.
Extract Manager 282
Note: If multiple files are being processed, this may be a valid condition if different passwords were specified during various ZIP runs. System Response: The file is bypassed, but other files will be processed. User Response: Specify the correct password for this file, or provide a matching private-key recipient if appropriate. When a password error is indicated with the following conditions both true, refer to information regarding fix TT3057. 1. The password value is > 95 characters. 2. The archive file was created with PKZIP for zSeries or SecureZIP for zSeries without TT3057 previously applied. Invoking module: <ACEXMAIN>
ZPEX017W
ZPEX017W Encrypted file skipped. One of the following is required: +40+C+ "A VALID PASSWORD" "A MATCHING RECIPIENT" "A VALID PASSWORD OR MATCHING RECIPIENT" "A VALID -FACILITY_ENCRYPTDATA" Explanation: Extract Manager processing warning. An encrypted file was encountered, but insufficient information was provided to decrypt it. Different decryption settings may be required depending on the options used to encrypt it. "A VALID PASSWORD" When PKZIP was used to create the file, only a password was used to secure the file data. "A MATCHING RECIPIENT" When PKZIP was used to create the file, only recipient(s) (public key encryption) was specified. This means that a valid SecureZIP private-key certificate must be provided to decrypt the file. "A VALID PASSWORD OR MATCHING RECIPIENT" When PKZIP was used to create the file, the user specified that either a private-key recipient, or a password may be used to decrypt the file. Either a matching SecureZIP private-key certificate or the password may be specified. Note: Only SecureZIP for z/OS supports recipient-based
Extract Manager 283
decryption. PKZIP for z/OS with the Enhanced Encrypt/Decrypt module supports password-based decryption for AES, 3DES and RC4. "A VALID -FACILITY_ENCRYPTDATA" An algorithm encountered did not have an enabled cryptographic facility available to perform the decryption operation. System Response: The file is bypassed, but other files will be processed. User Response: Specify the correct password for this file, or provide a matching private-key recipient if appropriate. For -FACILITY_ENCRYPTDATA, use VERBOSE and/or -SHOW_SETTINGS to obtain more detailed information about the configuration settings being used. When a password error is indicated with the following conditions both true, refer to information regarding fix TT3057. 1. The password value is > 95 characters. 2. The archive file was created with PKZIP for zSeries or SecureZIP for zSeries without TT3057 previously applied. Invoking module: <ACEXMAIN>
ZPEX018W
ZPEX018W UNMOVABLE file overwrite attempt bypassed: +44+C+ Explanation: In order to maintain data integrity, data sets on the system having the UNMOVABLE attribute turned on in the VTOC may not be overwritten. System Response: The file is bypassed. User Response: If the data set must be restored, it should be deleted and re-allocated without the UNMOVABLE attribute. Invoking module: <AMEXMAIN>
ZPEX060T
ZPEX060T Work Directive: +80+C+ Explanation: Extract Manager processing information. This line is only issued when EXTRACT tracing is turned on.
Extract Manager 284
System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX061I
ZPEX061I ARCHIVE_FASTSEEK (DISK) processing is being bypassed (Code +2+H+) Explanation: When LOGGING_LEVEL=VERBOSE is specified, this informational message is issued. The code value specifies one of the reasons for the switch to sequential processing of the Archive. 1. BSAM OPEN failed 2. SEEK TO EXTENT END FAILED 3. SEEK TO FILE POSITION FAILED System Response: Switch to sequential mode and continue processing if possible. Otherwise, terminate the file extract. User Response: Review the JOBLOG for any system reason codes associated with the input archive. Invoking module: <ACEXMAIN>
ZPEX062I
ZPEX062I ARCHIVE_FASTSEEK (TAPE) processing is enabled. Explanation: When LOGGING_LEVEL=VERBOSE is specified, this informational message is issued. EXTRACT processing recognized that the input archive contains high-speed NOTE/POINT XTAPE information. System Response: Continue processing using high speed tape features. User Response: None Invoking module: <ACEXMAIN>
ZPEX070T
ZPEX070T ?CACHEMEMORY limit reached - FMCB: +8+H+ +54+C+ Explanation: Extract Manager processing trace record. This line is only issued when EXTRACT tracing is turned on.
Extract Manager 285
System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX071E
ZPEX071E OUTFILE Open failed. Check joblog for additional information. Explanation: Extract Manager processing error detected. System Response: None User Response: Check the SYSPRINT and JOBLOG messages for error reasons. Invoking module: <ACEXMAIN>
ZPEX072W
ZPEX072W OUTFILE_OVERWRITE(N) excluded overwrite of {+54+C+} Explanation: Extract Manager processing warning. When an EXTRACT request is made, and the target file already exists, -OUTFILE_OVERWRITE(Y) must be specified to write over the old file. System Response: Processing of the current file is bypassed. User Response: Use OUTFILE_OVERWRITE as needed. Invoking module: <ACEXMAIN>
ZPEX073W
ZPEX073W INSERT_MEMBER(N) disallowed creation of {+54+C+} Explanation: Extract Manager processing warning. When an EXTRACT request is made, and the target PDS/PDSE already exists, -INSERT_MEMBER(Y) must be specified to create a new member. System Response: Processing of the current file is bypassed. User Response: Use INSERT_MEMBER(Y) as needed. Invoking module: <ACEXMAIN>
Extract Manager 286
ZPEX074E
ZPEX074E Allocation to PDS was denied. {+44+C+} Explanation: Extract Manager processing error detected. During EXTRACT processing, an attempt was made to open the PDS/PDSE directory to determine if the target member(s) already exist. The open failed for the dataset. System Response: Processing for the PDS/PDSE is terminated. User Response: Evaluate other SYSPRINT/JOBLOG messages to determine the OPEN failure reason. Invoking module: <ACEXMAIN>
ZPEX075W
ZPEX075W Program objects are not supported for PDSE Extract. Data saved "as is". Explanation: Extract Manager processing error detected. During EXTRACT processing, an attempt was made to UNZIP a load module to a PDSE (Library). The original source load module was likely a PDS Load Library. System Response: The data records are saved in the PDSE, but "Program Object" information is likely to be incomplete. User Response: EXTRACT the Load Modules to a PDS Load Library. Invoking module: <ACEXMAIN>
ZPEX076W
ZPEX076W Extract bypassed for member +8+C+ -- in use. Explanation: Extract Manager processing error detected. An attempt to restore a member of a PDS could not be satisfied because the member was being used. System Response: Processing for the member is bypassed. User Response: Reprocess the member when the member or dataset is no longer in user. Invoking module: <ACEXMAIN>
Extract Manager 287
ZPEX077E
ZPEX077E OUTFILE Cluster could not be defined. {+44+C+} Explanation: Extract Manager processing error. During EXTRACT processing, an attempt was made to perform a DEFINE CLUSTER for the target output file, but it failed. System Response: Processing for the file is terminated. User Response: Check the SYSPRINT output for Access Method Services messages that would describe the reason for the failure. Invoking module: <ACEXMAIN>
ZPEX078E
ZPEX078E OUTFILE Cluster could not be allocated. {+44+C+} Explanation: Extract Manager processing error detected. A VSAM cluster was identified for output, but a dynamic allocation for the cluster failed. See also ZPDAxxx messages for DYNALLOC error reasons. System Response: Processing for the file is terminated. User Response: Check for other messages describing the allocation failure Invoking module: <ACEXMAIN>
ZPEX079E
ZPEX079E PDS specified without a member name. Explanation: Extract Manager processing error detected. A PDS was requested for output, but either no member name was specified or an attempt was made to alter the dataset organization of an existing dataset by specifying OUTFILE_DSNTYPE. System Response: Processing for the file is terminated. User Response: Specify a member name and verify no conflicting OUTFILE_DSNTYPE specifications have been made. Invoking module: <ACEXMAIN>
Extract Manager 288
ZPEX080W
ZPEX080W Duplicate concurrent target file detected. Bypassing {+54+C+} Explanation: Extract Manager processing warning. When an EXTRACT request is made, and the target file is already being processed by another extraction task in the same job, this message may be issued to avoid conflicts in processing. This condition can result when PATH=N is specified, causing only the filename portion of the entire PATH to be used, or when PATH_EDIT results in multiple files resolving to the same destination file name. Detection of this condition is timing dependent. It can only occur when multi-tasking is requested (with MULTI_THREAD_LIMIT > 1). System Response: Selection of the duplicate file is bypassed. Subsequent files may be found to be processed when the target file is no longer active. User Response: Run MULTI_THREAD_LIMIT=1 if it is desirable to extract multiple files to the same target file. Otherwise, respecify the selection and naming of files so that each extracts to a unique target location within a single invocation of extract processing. Invoking module: <ACAMGR>
ZPEX081E
ZPEX081E Invalid record length detected (> 32k) +8+H+ Explanation: A BINARY file with saved LRECL information was being extracted. While the records were being processed, a record with a length > 32k was detected. System Response: Processing on the current file stops. The output file will be closed and the data written up to the point of failure will be intact. Warning: ONLY A PARTIAL FILE WILL BE AVAILABLE. User Response: Take necessary action to remove the output file and obtain a copy of the ZIP Archive with record lengths less than 32K. Invoking module: <ACEXMAIN>
Extract Manager 289
ZPEX082E
ZPEX082E Text/Binary detection table +8+C+ could not be loaded. Explanation: Extract Manager processing information. -DATA_TYPE(DETECT) had been specified, so the Extract Manager attempted to determine whether the data is binary or text. The load module table specified by -DATATYPE_DETECT_TABLE could not be loaded. System Response: Processing for the file is terminated. User Response: Determine the correct table to be loaded. Invoking module: <ACEXMAIN>
ZPEX083I
ZPEX083I DATA_TYPE(DETECTX) switching file to -TEXT Explanation: Extract Manager processing information. Issued only with -LOGGING_LEVEL=Verbose. A file was identified without the TEXT attribute turned on in the Archive Directory entry. However, PKZIP identified the data as being predominantly ASCII-based text and dynamically switched to TEXT mode. See -DATA_TYPE(DETECTX). System Response: Processing for the file continues with text processing. User Response: No action is required if the text data is processed as desired. However, if the actual binary representation of the data is desired, then use -DATA_TYPE(BINARY). Invoking module: <ACEXMAIN>
ZPEX084E
ZPEX084E Unknown/unsupported compression method +2+H+ +44+C+. Explanation: Compression method for the selected archive member is either not known or not supported. System Response: The member is bypassed and the next member is processed User Response: Check the compression method and the file bypassed which appears immediately following the message text
Extract Manager 290
Invoking module: <ACEXMAIN>
ZPEX090E
ZPEX090E HFS processing error: HFSAPI STATUS=+2+D+ REASON=+2+D+ action_desc Explanation: While attempting an extract operation to a Unix file, an error condition was raised for the "action_desc" listed in the message. A general STATUS code and a conditional feedback REASON are provided. This message is commonly issued when HFS PATH permissions are insufficient for the dynamic creation of a directory or allocation of the target file. System Response: Processing may either continue or be terminated for the file in progress depending on the setting for -ON_FILE_ACCESS_ERROR. User Response: Check for additional messages, both in SYSPRINT, as well as in the joblog to determine the reason for the failure. See also: $HFSCODE for Status and Reason codes ZPFM081I Invoking module: <ACEXMAIN>
ZPEX092C
ZPEX092C Processing info - UNZIP: +6+C+ +6+C+ +8+C+ / HFS: +6+C+ Format(+2+C+:+2+C+) +7+C+ / DATA_TYPE=+15+C+ Explanation: When -LOGGING_LEVEL=VERBOSE is specified, this message will be issued as a continuation to ZPEX092W. The purpose of the message is to report on several factors that can influence resulting record delimiter processing during an extract process to an HFS file. The message is divided into the following sections: 1. UNZIP data mode 2. HFS File Format controls 3. -DATA_TYPE control value UNZIP data mode =============== This section reflects how data is handled as it is 'read' from the ZIP archive file. Field-1 +6+C+ - Read processing mode of ZIP file. 'RECORD' - Reading as either delimited records, or
Extract Manager 291
processing with SAVE_LRECL length values. 'STREAM' - Reading as a stream of data without record length analysis. See also: -DATA_TYPE and ZIP file mode. Field-2 +6+C+ - ZIP file mode declarations '*TEXT*' - Explicitly declared as "Text" by ZIP processing in the archive. '*ZDW*' - Explicitly declared as SAVE_LRECL=Y by ZIP processing in the archive. '~TEXT' - Data detection determined the data to be within specified limits for either ASCII or EBCDIC text data. -DATA_TYPE(DETECTX) is required for this value to be set. '------' - Undeclared by ZIP and undetected by UNZIP. Field-3 +8+C+ - ZOSFILE_RECORD_DELIMITER value (hex). 'xx' - For example, '15' is the hex representation of E-NL (EBCDIC Newline). '--' - Not active. 1. Not valid for use in STREAM mode. 2. Deactivated because HFS File Format has taken control. 3. Unspecified by the user. HFS File Format =============== This section reflects some aspects of external HFS File Format controls that may influence record delimiters being written to an HFS file target. Field-1 +6+C+ - Write processing mode in effect by HFS. 'RECORD' - Writing in record-mode, usually associated with File Format 'nl (JCL FILEDATA=TEXT). 'STREAM' - Writing as a stream of data without record delimiters being applied by the file system handler. Field-2 +2+C+:+2+C+ info.st_filefmt indicator enumerated by st_filefmt 00 UNDECLARED - not set 01 BINARY - Declared binary 02 NL - New line 03 CR - Carriage Return 04 LF - Line Feed 05 CRLF - Carriage Return/Line Feed 06 LFCR - Line Feed/Carriage Return 07 CRNL - Carriage Return/New Line If not influenced by RESTORE_HFS_TAGINFO, part 1 will reflect the original File Format for an existing file targeted for OVERWRITE=Y processing. The second part of the field (after the ":" indicates the final File Format derived for processing. This may be influenced by:
Extract Manager 292
1. JCL DD FILEDATA=BINARY|TEXT 2. For an existing file to be overridden, the original File Format of the target file. 3. For a dyamically allocated target file (not via OUTFILE_DD), a specific -HFS_FILEFORMAT processing specification. 4. RESTORE_HFS_TAGINFO, which references information from the ZIP archive SAVE_FILE_ATTRIBUTES values (if any). Field-3 +7+C+ - A reflection of HFS_FILEDATA control. value - See -HFS_FILEDATA 'JCL-DD' - The target file is controlled via DD. If FILEDATA=TEXT or FILEDATA=BIANRY are specified in the JCL, these values will override any other specifications. '-' - No value was provided for the command. Defaults or RESTORE_HFS_TAGINFO will influence the resulting File Format. DATA_TYPE ========= This command setting governs how UNZIP data mode will be determined. 'BINARY' - An explicit BINARY mode of operation was requested. Even when the ZIP file mode declaration was for *TEXT*, the data will be treated in a stream mode. 'TEXT' - An explicit TEXT record-mode was requested. An attempt will be made to perform delimiter scanning on the ZIP file. '*ZDW' - No DATA_TYPE override request was made and the ZIP file mode was declared to use SAVE_LRECL=Y. '*TEXT' No DATA_TYPE override request was made and the ZIP file mode was declared to use TEXT records. '~DETECTX=' DATA_TYPE(DETECTX) was requested. The results were found to be: ASCII - The detection limits identified the file data to be ASCII Text delimited records. EBCDIC - The detection limits identified the file data to be EBCDIC Text delimited records. BINARY - The detection limits did not match either ASCII or EBCDIC. Stream-mode processing will be selected. Note: DATA_TYPE(DETECTX) is not recommended when HFS File Data settings may result in record mode operations and UNZIP processing operations may result in BINARY stream-mode operations. This combination would result in the file system I/O handler adding a record delimiter at the end of each buffer written (commonly 32760 bytes). System Response: See ZPEX092W and ZPEX093I.
Extract Manager 293
User Response: See ZPEX092W and ZPEX093I. Invoking module: <ACEXMAIN>
ZPEX092W
ZPEX092W +12+C+ HFS Delimiter(s) detected - verify setup Explanation: A condition was detected in which the HFS FILEDATA File Format control may conflict with the intended UNZIP settings for the file. The specific condition will be declared in the +12+C+ text of the message as follows: "BINARY ZIP &" ============== UNZIP Extract processing is operating in a BINARY stream-mode while writing to an HFS file defined to have an 'nl' File Format. If the file is being accessed in FILEDATA=TEXT processing mode, then newline characters will be added to the end of each buffer written. "Dual ZIP &" ============== UNZIP Extract settings specify that record delimiters from ZOSFILE_RECORD_DELIMITER be added to each record. In addition, UNZIP processing detected that the target file has a File Format that instructs the system to place a record delimiter after each record written for output. "Mixed ZIP &" ============== UNZIP Extract settings specify that record delimiters from ZOSFILE_RECORD_DELIMITER be added to each record. In addition, UNZIP processing detected that the target file has a File Format declaration that may conflict with the ZOSFILE_RECORD_DELIMTER value. System Response: Unpredictable results may occur. - If the value declared in the HFS File Format for an existing file, (or a restored value from RESTORE_HFS_TAGINFO) does not match the value written by ZOSFILE_RECORD_DELIMITER, then subsequent processes expecting the HFS File Format value may not operate correctly. - When Dual ZIP & HFS delimiters are detected for record-mode processing, message ZPEX093I will also be issued to indicate that HFS File Format processing will be honored and the application of ZOSFILE_RECORD_DELIMITER will be bypassed. User Response: Evaluate the state of the File Format attribute for the
Extract Manager 294
HFS file and coordinate the settings for HFS_FILEDATA and ZOSFILE_RECORD_DELIMITER accordingly. If the results are as desired, the return code for this message may be suppressed with -PKSUPPRC(ZPEX092W). Use -LOGGING_LEVEL=VERBOSE to cause message ZPEX092C to be issued, as well as -SHOW_SETTINGS as the last command in the input stream to show what settings are in effect. When explicit use of the HFS File Format is desired, one use -ZOSFILE_RECORD_DELIMITER() so that UNZIP does not attempt to add its own record delimiter. When use of the ZOSFILE_RECORD_DELIMITER is desired, one of the following techniques may be used to ignore the HFS File at 1. -HFS_FILEDATA() causes UNZIP to open the output file in binary stream mode for dynamically allocated PATH files. 2. OUTFILE_DD FILEDATA=BINARY in the respective DD for the path causes UNZIP to open the output file in binary stream mode. 3. For a pre-existing target file, use an external utility to reset the HFS File Format before invoking UNZIP. For "BINARY ZIP &", if a pure binary stream is desired from UNZIP, specify -HFS_FILEDATA() for dynamically allocated output processing, or FILEDATA=BINARY for JCL OUTFILE_DD PATH target files. Invoking module: <ACEXMAIN>
ZPEX093I
ZPEX093I Bypassing ZOSFILE_RECORD_DELIMITER in lieu of HFS File Format "nl" processing. Explanation: The new-line "nl" character was specified by both ZOSFILE_RECORD_DELIMITER=E-NL and the attributes of the HFS file. See also ZPEX092W. System Response: UNZIP processing will bypass the application of ZOSFILE_RECORD_DELIMITER=E-NL and permit the HFS File Format aspect of the file system apply the record delimiter. User Response: Evaluate the state of the File Format attribute for the HFS file and coordinate the settings for HFS_FILEDATA and ZOSFILE_RECORD_DELIMITER accordingly.
Extract Manager 295
If the results are as desired, the return code for ZPEX092W may be suppressed with -PKSUPPRC(ZPEX092W). Invoking module: <ACEXMAIN>
ZPEX095I
ZPEX095I HFS/FIFO is about to be opened for processing: +54+C+ Explanation: During UNZIP processing, the file about to be opened was detected to be a FIFO Special File (named PIPE). The OPEN will only complete for this type of file when a partner process also opens the file for output. System Response: Attempt to OPEN the specified FIFO Special File. Note: The OPEN will WAIT indefinitely until a partner process opens the file for output, a system WAIT time limit is exceeded, or the process is cancelled. User Response: -Ensure that a partnering process performs an OPEN for INPUT for the named PIPE file. Invoking module: <ACCOMAIN>
ZPEX100I
ZPEX100I Extract Task {+3+D+} TCB: +8+H+ Started. Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued upon the startup of an Extract Manager sub-task. Note: In Z/OS, more than one instance of this task (and message) may be generated. The number of extraction tasks is controlled by -MULTI_THREAD_LIMIT System Response: None User Response: None Invoking module: <ACEXMAIN>
Extract Manager 296
ZPEX101I
ZPEX101I Extract Task {+3+D+} TCB: +8+H+ shutdown begun. Explanation: When -LOGGING_LEVEL(VERBOSE) is specified, this message will be issued upon the shutdown of each Extraction manager sub-task. System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX109I
ZPEX109I Extract Task {+3+D+} TCB: +8+H+ shutdown complete. Explanation: Extract Manager processing information. The EXTRACT sub-task has shut down. This line is only issued when LOGGING_LEVEL(VERBOSE) is specified. System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX111I
ZPEX111I +10+C+ Records processed for +54+C+. Explanation: Extract Manager processing information. When LOGGING_LEVEL=VERBOSE is specified, this message will be issued on a periodic basis as a progress bar for UNZIP processing. This is useful for long running jobs with very large files. System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX193W
ZPEX193W Unrecognized extended attribute +2+H+ for o/p file type, sequential assumed.
Extract Manager 297
Explanation: An unrecognized extended attribute was found for the file type while extracting a file. System Response: The file type is assumed sequential and processing continues. User Response: If PKZIP created the archive, PKWARE should be contacted. Invoking module: <ACEXMAIN>
ZPEX200I
ZPEX200I Compressed size: X"+8+H++8+H+", Uncompressed size: Explanation: Extract Manager processing information. When GZIP files are processed, the file size can exceed 4 gigabytes. This message is displayed to show the byte sizes (in HEX) of the associated file. System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX900T
ZPEX900T +121+C+ Explanation: Extract Manager processing trace record. This line is only issued when EXTRACT tracing is turned on. System Response: None User Response: None Invoking module: <ACEXMAIN>
ZPEX999E
ZPEX999E INVALID INTERNAL DIRECTIVE: +80+C+ Explanation: Extract Manager processing error detected. An internal logic error was detected. System Response: Processing is terminated for the current file.
Extract Manager 298
User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACEXMAIN>
File Manager 299
ZPFM - File Manager Messages
ZPFM000I
ZPFM000I +121+C Explanation: File Manager processing information. Various string messages listed below, with a separate explanation for each string. ZPFM000I UNMOVABLE CKPT DATA SET PROCESSED: data.set.name Invoking module: <AMFMOBTN> See also: ZPEX000I Occurs only when -PROC_OPT5=Y was set to specifically request that Checkpointed/Unmovable data sets are to be processed. PKZIP will not normally process unmovable data sets, but when the -PROC_OPT5=Y is issued, it will copy files that are marked as Checkpointed/Unmovable. Extracting these files to their original location requires special handling described in ZPEX000I.
ZPFM001E
ZPFM001E +121+C Explanation: An I/O error occured. The standard IBM SYNAD message text is displayed as a problem analysis aid. An additional message describing the action taken is also displayed. System Response: None User Response: Check for other messages following this one, and take the appropriate action. Invoking module: <ACFMBSAM>
ZPFM011W
ZPFM011W OBTAIN failed (rc=+8+D+) for +44+C+ Vol(+8+C+) Explanation: The File Manager was attempting to gather information about a non-VSAM DISK dataset but could not get the VTOC
File Manager 300
information. This can happen if a dataset is cataloged to a volume, but the dataset does not actually exist. For more information about CAMLST OBTAIN, see IBM manual: DFSMS/MVS DFSMSdfp Advanced Services - Reading DSCBs from the VTOC Using OBTAIN & Return Codes from OBTAIN (Reading by Data Set Name) +--------------+--------------------------------------------------------+ › 0(X'00') › Successful completion of OBTAIN routine. | +--------------+--------------------------------------------------------+ › 4(X'04') › The required volume was not mounted. | +--------------+--------------------------------------------------------+ › 8(X'08') › The format-1 DSCB was not found in the VTOC of the | › › specified volume. | +--------------+--------------------------------------------------------+ › 12(X'0C') › A permanent I/O error was encountered, or an invalid | › › format-1 DSCB was found when processing the specified | › › volume, or an unexpected error return code was received| › › from CVAF (common VTOC access facility). | +--------------+--------------------------------------------------------+ › 16(X'10') › Invalid work area pointer. | +-----------------------------------------------------------------------+ User Response: Check the return code. Invoking module: <ACFMGR>
ZPFM012W
ZPFM012W File type {+16+C+} unsupported: +44+C+ Explanation: A dataset was determined to be unsupported by PKZIP. Examples of these types of files are: "UNMOVABLE" "ISAM" System Response: The file is bypassed. User Response: UNMOVABLE Checkpoint data sets can be accepted for ZIP processing by using -ZIP_UNMOVABLE_CHKPT=Y Invoking module: <AMFMOBTN>
ZPFM013I
ZPFM013I File type {+16+C+} accepted: +44+C+ Explanation: A special data set condition arose that requires explicit settings to process. "UNMOVABLE_CHKPT" - ZIP_UNMOVABLE_CHKPT=Y was specified for the ZIP run. The data set is
File Manager 301
added to the archive as a normal file. System Response: The file is processed. User Response: None Invoking module: <AMFMOBTN>
ZPFM014W
ZPFM014W Unmovable Dataset overwrite attempt bypassed: +44+C+ Explanation: In order to maintain data integrity, data sets on the system having the UNMOVABLE attribute turned on in the VTOC may not be overwritten. System Response: The file is bypassed. User Response: If the data set must be restored, it should be deleted and re-allocated without the UNMOVABLE attribute. Invoking module: <AMFMOBTN>
ZPFM015W
ZPFM015W BLKSIZE=+7+D+ IS NOT VALID FOR ZIPFORMAT +10+C+ C+ Explanation: -ARCHIVE_BLKSIZE exceeds the maximum (32760) for the specified -ZIPFORMAT. System Response: -ARCHIVE_BLKSIZE is reduced to 27998, and processing continues with RC=4. User Response: If the archive should be written to a Large Block Interface tape, rerun the job with the correct -ZIPFORMAT specified. If the archive should be not be written to an LBI tape, the archive that was written is correct. Update the -ARCHIVE_BLKSIZE specification for later executions to avoid receiving this message. Invoking module: <ACFMBSAM,ACFMGR>
ZPFM019I
ZPFM019I OBTAIN info: Alloc=+2+H+ Filetype=+2+H+ RECFM=+2+H+ Explanation: This message is issued when certain traces are set as active. It is informational and describes the VTOC information found for a non-VSAM disk file.
File Manager 302
Programming info: Alloc is FM_ALLOCATION Filetype is FM_FILETYPE RECFM is FM_RECFM System Response: None User Response: None Invoking module: <AMFMOBTN>
ZPFM030E
ZPFM030E <AMFMPDSD> Error: +80+C+ Explanation: The routine responsible for reading a PDS or PDS/E directory encountered an error. This can occur if the system disallows access to the dataset. Some possible reasons for the failure include: Insufficient Virtual Storage (GETMAIN failure) (an excessively large ZIP run was being performed) Error opening the PDS/PDSE System Response: Processing for the file is terminated. User Response: Check for additional messages in the SYSPRINT or JOBLOG. Invoking module: <AMFMPDSD>
ZPFM031T
ZPFM031T <AMFMPDSD> +8+H+ +8+C+ +8+H+ +8+C+ Explanation: File Manager processing trace record. This line is only issued when FMGR tracing is turned on. This information is useful to Technical Support in assessing member name filtering. System Response: None User Response: None Invoking module: <AMFMPDSD>
File Manager 303
ZPFM032T
ZPFM032T DSNMATCH MEMBER FILTER: +8+C+ DIRECTORY AT +8+H+ = +8+C+ Explanation: File Manager processing trace record. This line is only issued when FMGR tracing is turned on. System Response: None User Response: None Invoking module: <AMFMPDSD>
ZPFM033T
ZPFM033T Empty PDS found for DD: +8+C+ Explanation: File Manager processing trace record. This line is only issued when FMGR tracing is turned on. System Response: None User Response: None Invoking module: <AMFMPDSD>
ZPFM034T
ZPFM034T <AMFMPDSD> DSNMATCH MEMBER RC=+8+D+ Explanation: File Manager processing trace record. This line is only issued when FMGR tracing is turned on. System Response: None User Response: None Invoking module: <AMFMPDSD>
ZPFM040I
ZPFM040I Alias entry +8+C+ built for member +8+C+ Explanation: An alias was created for the identified member as a result of -PROCESS_ALIAS(Y) being specified for EXTRACT processing. This message will occur for each
File Manager 304
ALIAS constructed as a result of the EXTRACT request. This line is only issued with LOGGING_LEVEL(VERBOSE). System Response: None User Response: None Invoking module: <CCFMBPAM>
ZPFM041E
ZPFM041E <AMFMSTOW> +8+C+ Open Failed for operation on member +8+C+ Explanation: File Manager was attempting to make a modification to a PDS or PDS/E member, but the OPEN for the directory failed. For more information on STOW, reference IBM manual: DFSMS/MVS Macro Instructions for Data Sets - STOW--Update Partitioned Data Set Directory (BPAM) System Response: Processing for the data set terminates. User Response: Check SYSPRINT and the JOBLOG for other messages that may indicate the reason for the failed OPEN. Invoking module: <AMFMSTOW>
ZPFM042E
ZPFM042E <AMFMSTOW> PDS +8+C+ failure for member +8+C+ on DD +8+C+ STOW Explanation: File Manager was attempting to make a modification to a PDS or PDS/E member, but the STOW action +8+C+ failed. STOW actions may include: ADD, DEL, CHG or REName. An example of a failure might be that an ADD was requested but the PDS had no more directory space. For more information on STOW, reference IBM manual: DFSMS/MVS Macro Instructions for Data Sets - STOW--Update Partitioned Data Set Directory (BPAM) System Response: Processing for the data set terminates. User Response: Check SYSPRINT and the JOBLOG for other messages that may indicate the reason for the failed OPEN. Invoking module: <AMFMSTOW>
File Manager 305
ZPFM050I
ZPFM050I File Information about {+44+C+} Explanation: File Manager processing information. This line is only issued when FMGR tracing is turned on. Related messages: ZPFM050I FILE INFORMATION ABOUT {+44+C+} ZPFM051I VOLSER: +4+C+ BASIC DEVICE: +4+C+ UNIT: +6+C+ ZPFM052I DSORG: +4+C+ RECFM: +10+C+ ZPFM053I LRECL: +6+D+ BLKSIZE: +6+D+ ZPFM054I STORCLASS: +8+C+ MGMTCLASS: +8+C+ DATACLASS: + System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM051I
ZPFM051I VOLSER: +6+C+ BASIC DEVICE: +4+C+ UNIT: +6+C+ FLAGS: +8+H+ Explanation: File Manager processing information. This line is only issued when FMGR tracing is turned on. Related messages: ZPFM050I FILE INFORMATION ABOUT {+44+C+} ZPFM051I VOLSER: +4+C+ BASIC DEVICE: +4+C+ UNIT: +6+C+ ZPFM052I DSORG: +4+C+ RECFM: +10+C+ ZPFM053I LRECL: +6+D+ BLKSIZE: +6+D+ ZPFM054I STORCLASS: +8+C+ MGMTCLASS: +8+C+ DATACLASS: + System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM052I
ZPFM052I DSORG: +4+C+ RECFM: +10+C+ Explanation: File Manager processing information. This line is only issued when FMGR tracing is turned on.
File Manager 306
Related messages: ZPFM050I FILE INFORMATION ABOUT {+44+C+} ZPFM051I VOLSER: +4+C+ BASIC DEVICE: +4+C+ UNIT: +6+C+ ZPFM052I DSORG: +4+C+ RECFM: +10+C+ ZPFM053I LRECL: +6+D+ BLKSIZE: +6+D+ ZPFM054I STORCLASS: +8+C+ MGMTCLASS: +8+C+ DATACLASS: + System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM053I
ZPFM053I LRECL: +6+D+ BLKSIZE: +6+D+ Explanation: File Manager processing information. This line is only issued when FMGR tracing is turned on. Related messages: ZPFM050I FILE INFORMATION ABOUT {+44+C+} ZPFM051I VOLSER: +4+C+ BASIC DEVICE: +4+C+ UNIT: +6+C+ ZPFM052I DSORG: +4+C+ RECFM: +10+C+ ZPFM053I LRECL: +6+D+ BLKSIZE: +6+D+ ZPFM054I STORCLASS: +8+C+ MGMTCLASS: +8+C+ DATACLASS: + System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM054I
ZPFM054I STORCLASS: +8+C+ MGMTCLASS: +8+C+ DATACLASS: +8+C+ Explanation: File Manager processing information. This line is only issued when FMGR tracing is turned on. Related messages: ZPFM050I FILE INFORMATION ABOUT {+44+C+} ZPFM051I VOLSER: +4+C+ BASIC DEVICE: +4+C+ UNIT: +6+C+ ZPFM052I DSORG: +4+C+ RECFM: +10+C+ ZPFM053I LRECL: +6+D+ BLKSIZE: +6+D+ ZPFM054I STORCLASS: +8+C+ MGMTCLASS: +8+C+ DATACLASS: +
File Manager 307
System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM061I
ZPFM061I +15+C+ +18+C+ +15+C+ +12+C+ Explanation: File Manager processing information for VSAM. This line is only issued when FMGR tracing is turned on. Field information: P1=FM_VSAM_KEYS P2=FM_VSAM_RECSIZE 6+C+ P3=FM_VSAM_DATA_BUFSPACE P4=FM_VSAM_DATA_CISIZE System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM062I
ZPFM062I +10+C+ +8+C+ +8+C+ +8+C+ +8+C+ Explanation: File Manager processing information for VSAM. This line is only issued when FMGR tracing is turned on. Field information: P1=FM_VSAM_FORMAT P2=FM_VSAM_RECOV_SPEED 6+C+ P3=FM_VSAM_UNIQUE P4=FM_VSAM_ERASE P5=FM_VSAM_DATA_SHROPTNS System Response: None User Response: None Invoking module: <ACCMGR>
File Manager 308
ZPFM063I
ZPFM063I +10+C+ +7+C+ +5+C+ +9+C+ +7+C+ +10+C+ Explanation: File Manager processing information for VSAM. This line is only issued when FMGR tracing is turned on. Field information: P1=FM_VSAM_WRITECHK P2=FM_VSAM_IMBED P3=FM_VSAM_REPLICATE P4=FM_VSAM_ORDERED P5=FM_VSAM_DATA_REUSE P6=FM_VSAM_SPANNED System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM064I
ZPFM064I +13+C+ +22+C+ Explanation: File Manager processing information for VSAM. This line is only issued when FMGR tracing is turned on. Field information: P1=FM_VSAM_FREE_SPACE_DEF P2=FM_VSAM_DATA_SPACE_DEF 6+C+ System Response: None User Response: None Invoking module: <ACCMGR>
ZPFM071E
ZPFM071E VSAM OPEN Error +8+H+ for File(+8+C+) DA(+44+C+) Explanation: File Manager attempted to open the specified VSAM Cluster, but the OPEN failed. +8+H+ is the ACB Error reason as defined in the IBM manual DFSMS/MVS Macro Instructions for Data Sets -
File Manager 309
VSAM Macro Return and Reason Codes - OPEN Return and Reason Codes System Response: Processing for the file is terminated. User Response: Determine the reason for the failed open from the provided reason code. Invoking module: <ACFMGR>
ZPFM072E
ZPFM072E VSAM I/O ERROR: File is not Open DA(+44+C+) Explanation: File Manager attempted to read a record from the Cluster, but the file had not opened properly. System Response: Processing for the file is terminated. User Response: Check SYSPRINT and the JOBLOG for associated OPEN errors. Invoking module: <ACFMGR>
ZPFM073E
ZPFM073E FILE GET ERROR: +8+C+ +44+C+ VSAM FDBK=+8+H+ ARG=+8+H+ Explanation: File Manager attempted to read the specified VSAM Cluster, but the request failed. +8+C+ = DDNAME +44+C+= Cluster name FDBK and ARG are displays from: SHOWCB RPL=(Rx),FIELDS=(FDBK,ARG) FDBK=+8+H+ is the RPL Error reason as defined in the IBM manual DFSMS/MVS Macro Instructions for Data Sets - VSAM Macro Return and Reason Codes - Record Management Return and Reason Codes ARG=+8+H+ is the argument field from the VSAM RPL System Response: Processing for the file is terminated. User Response: Determine the reason for the failed read from the provided reason code. Invoking module: <ACFMGR>
File Manager 310
ZPFM074E
ZPFM074E FILE PUT ERROR: +8+C+ +44+C+ VSAM FDBK=+8+H+ ARG=+8+H+ Explanation: File Manager attempted to write to the specified VSAM Cluster, but the request failed. +8+C+ = DDNAME +44+C+= Cluster name FDBK and ARG are displays from: SHOWCB RPL=(Rx),FIELDS=(FDBK,ARG) FDBK=+8+H+ is the RPL Error reason as defined in the IBM manual DFSMS/MVS Macro Instructions for Data Sets - VSAM Macro Return and Reason Codes - Record Management Return and Reason Codes ARG=+8+H+ is the argument field from the VSAM RPL System Response: Processing for the file is terminated. User Response: Determine the reason for the failed write from the provided reason code. Invoking module: <ACFMGR>
ZPFM075E
ZPFM075E Unsupported VSAM filetype: +8+C+ +44+C+ Explanation: File Manager detected a VSAM file organization that is not supported by PKZIP. Supported Cluster types are: ZIP Archive: ESDS (NONINDEXED) Files: ESDS (NONINDEXED) KSDS (INDEXED) RRDS (NUMBERED) System Response: Processing for the file is terminated. User Response: None Invoking module: <ACFMGR>
ZPFM076E
ZPFM076E VSAM CLOSE Error on File (+8+C+) DA(+44+C+) Explanation: The specified file could not be closed properly.
File Manager 311
System Response: None User Response: Check SYSPRINT and the JOBLOG for other messages that may indicate the reason for the close failure. Perform a LISTCAT ENTRY(cluster name) to assess the health of the file. Invoking module: <ACFMGR>
ZPFM077W
ZPFM077W VSAM CLOSE Error on File (+8+C+) DA(+44+C+) Explanation: The specified file could not be closed properly. The CLOSE associated with this message occurs when File Manager was writing sequentially to an output KSDS during UNZIP processing. An out-of-sequence key was detected and the File Manager was in the process switching to "direct" insert mode (a CLOSE/Re-OPEN is required to perform this function). System Response: Processing for the file is terminated. User Response: Check SYSPRINT and the JOBLOG for other messages that may indicate the reason for the close failure. UNZIP the data to a non-KSDS file and check the record sequence, and/or sort the data before loading to a KSDS. Perform a LISTCAT ENTRY(cluster name) to assess the health of the file. Invoking module: <ACFMGR>
ZPFM078I
ZPFM078I Switching KSDS from SEQ to DIR on File (+8+C+) DA(+44+C+) Explanation: File Manager processing information for VSAM. File Manager was writing sequentially to an output KSDS during UNZIP processing. An out-of-sequence key was detected and the File Manager was in the process switching to "direct" insert mode (a CLOSE/Re-OPEN is required to perform this function). System Response: Processing continues in "direct" insert mode. Note: Performance may be degraded, record placement may be changed and file sizing may not be as expected due to changes in VSAM operating
File Manager 312
characteristics. User Response: UNZIP the data to a non-KSDS file and check the record sequence, and/or sort the data before loading to a KSDS. Perform a LISTCAT ENTRY(cluster name) to assess the health of the file. Invoking module: <ACFMGR>
ZPFM080E
ZPFM080E <ACFMBSAM> FSEEK BSP Error: RC=+8+H+ FDBK=+8+H+ Explanation: File Manager processing error for FASTSEEK. An I/O error occurred while performing ARCHIVE_FASTSEEK System Response: FASTSEEK processing is terminated and sequential mode is invoked to complete the function. User Response: Refer to ZPFM080I for detailed Backspace feedback info. Invoking module: <ACFMGR>
ZPFM080I
ZPFM080I +80+C+ Explanation: Detailed information regarding a FASTSEEK failure. Associated message: ZPFM080E System Response: FASTSEEK processing is terminated and sequential mode is invoked to complete the function. User Response: None. Invoking module: <ACFMGR>
ZPFM081I
ZPFM081I +120+C+ Explanation: File Manager feedback information for HFS processing. When an abnormal condition is encountered for a Unix File System request, descriptive feedback information will be displayed in this message. Process-specific messages will also be issued around
File Manager 313
this message with Status and Reason code information relating to the condition. See also: $HFSCODE for Status and Reason codes System Response: None User Response: See related error or warning messages relating to the processing request. Invoking module: <PKHFSAPI,ACCMGR,ACAMGR,ACEXMAIN>
ZPFM100T
ZPFM100T <ACFMGR> Entry: +8+C+ +8+C+ +44+C+ {+8+C+} +8+H+ Explanation: File Manager processing trace record. This line is only issued when FMGR tracing is turned on. P1=FM_ACTION (file access request) P2=FM_DDNAME P3=FM_DSNAME P4=FM_MEMBER P5=plist_address System Response: None User Response: None Invoking module: <ACFMGR>
ZPFM101T
ZPFM101T File Opened +8+C+ +54+C+ Explanation: File Manager processing information for VSAM. This line is only issued when FMGR tracing is turned on. +8+C+ - DDNAME +54+C+ - DSNAME System Response: None User Response: None Invoking module: <ACFMGR>
File Manager 314
ZPFM102E
ZPFM102E File Open Error: +8+C+ +54+C+ Explanation: An open for either a VSAM or NONVSAM file failed. +8+C+ - DDNAME +54+C+ - DSNAME System Response: Processing for the specified file is terminated. User Response: Check SYSPRINT and the JOBLOG for other error indications. Invoking module: <ACFMGR>
ZPFM103E
ZPFM103E PENDING FIFO Special file OPEN is being terminated due to caller request. Explanation: When processing a FIFO Special File (named pipe), ZIP processing determined that the outstanding OPEN will not be satisfied. A likely cause is that the APIB caller has requested a TERMINATE action without completing an OPEN for the other 'side' of the pipe file. System Response: The OPEN that is pending on the FIFO Special File will be abnormally terminated. User Response: Review the information to determine the reason for the application to fail opening its side of the pipe. Invoking module: <ACCOMAIN> <ACEXMAIN> <ACAMGR>
ZPFM104I
ZPFM104I PENDING FIFO Special file awaiting application partner OPEN (1 minute polling check). Explanation: APIB Call Mode processing has issued an OPEN for a FIFO Special File and is awaiting the application to complete it's OPEN for its side of the pipe. File Management detected that an APIB Call Mode request for a FIFO Special File remained in PENDING status for a significant period of time. A partner application is expected to complete an OPEN request for the other 'side' of the FIFO Special File.
File Manager 315
This message may be issued if an application requests WAIT-UNTIL-PENDING but delays its OPEN of the FIFO pipe for more than one minute. System Response: The PENDING state will be replaced by an ACTIVE state when the application completes the required OPEN. A polling check (spaced at approximately 1 minute) will be done while the file is in PENDING state. User Response: Check application processing logs to determine why an OPEN has not completed for the FIFO Special File. Invoking module: <ACCOMAIN> <ACEXMAIN> <ACAMGR>
ZPFM111E
ZPFM111E File Get Error: +8+C+ +44+C+ {+8+C+} Explanation: File Manager encountered a NONVSAM read error. +8+C+ - DDNAME +54+C+ - DSNAME {+8+C+}- conditional member name System Response: Processing for the specified file is terminated. User Response: Check SYSPRINT and the JOBLOG for other error indications. Invoking module: <ACFMGR>
ZPFM112I
ZPFM112I SYNAD Info: +80+C+ Explanation: When a NONVSAM error occurs, the system returns additional error information in a buffer. One or more lines may be displayed in accordance with the system information returned to the SYNADAF handler. +80+C+ System-supplied error info. See also: ZPFM111E, ZPFM121E For more information about SYNAD routines and the format of information returned, see IBM manual(s): DFSMS/MVS Macro Instructions for Data Sets SYNADAF--Perform SYNAD Analysis Function Message Buffer Format
File Manager 316
DFSMS/MVS Using Data Sets - SYNAD Synchronous Error Routine Exit Typical order of fields for line 1 JOB name, Step name, Device number, Device type, DD name, Operation, Error Description Typical order of fields for line 2 (conditionally written) Concatenation Number, TTR Token of member (PDSE only), Relative Record number or RBN (PDSE/HFS or extended fmt), SMS Return Code, SMS Reason code, SMS Diagnostic code Note: "OMVS" for Device number may be used to indicate an HFS file. Note: The SMS Return/Reason code information provided by the operating system regarding a condition may be different depending upon the Filesystem type used for the associated mount point. For example, an 'out of space' WRITE ERROR may present reason code 0008001C for an HFS mount point, but 000C0010 for a zFS mount point. An OMVS PUT, WRITE ERROR can be encountered with a QSAM SYNAD error SMS code 0008001C (or 000C0010) under the following conditions: - The associated HFS mount point is full. An OMVS PUT, WRITE ERROR can be encountered with a QSAM SYNAD error SMS code 00080010 under the following conditions: - For a FIFO Special File (named pipe), the affiliated application closed the file prematurely. System Response: None User Response: Review the information to determine the reason for the failure. Invoking module: <ACFMGR>
ZPFM113E
ZPFM113E File Get Error lrecl > 32k: +8+C+ +44+C+ {+8+C+} Explanation: File Manager encountered a Spanned record in which the sum of the data portion of it's segments exceed 32768. +8+C+ - DDNAME +54+C+ - DSNAME {+8+C+}- conditional member name System Response: Processing for the specified file is terminated.
File Manager 317
User Response: Check SYSPRINT and the JOBLOG for other error indications. Invoking module: <ACFMGR>
ZPFM121E
ZPFM121E File Put Error (+8+H+): +8+C+ +54+C+ Explanation: File Manager encountered a NONVSAM PUT error. +8+C+ - DDNAME +54+C+ - DSNAME {+8+C+}- conditional member name See also ZPFM112I Example: (EEB37004): SYS00005 SYS01120.T113425.RA000.MASQZIP.R0100246 The above message was issued for a Temporary work file that ran out of space (B37 in positions 3 - 5). In this case, the -TEMP_... commands should be used to provide more space when allocating temporary work space during a ZIP function for large files. System Response: Processing for the specified file is terminated. User Response: Check SYSPRINT and the JOBLOG for other error indications. Use the appropriate -TEMP_.. , -OUTFILE_... or -ARCHIVE_.. commands to adjust dynamically allocated output files. Adjust JCL space allocation specifications for the target file referenced via JCL. Invoking module: <ACFMGR>
ZPFM700I
ZPFM700I - +9+C mode archive being created - BLKSIZE=+7+D Explanation: Message presented in VERBOSE mode only. Informational msg for an archive being created on tape, and Large Block Interface (LBI) is in effect. System Response: None User Response: None Invoking module: <ACFMBSAM>
File Manager 318
ZPFM701I
ZPFM701I - LBI mode archive being read - BLKSIZE=+7+D Explanation: Message presented in VERBOSE mode only. Informational msg for an archive being read from tape, and Large Block Interface (LBI) is in effect. System Response: None User Response: None Invoking module: <ACFMBSAM>
ZPFM702I
ZPFM702I - Device reports non-LBI, BLKSIZE set to +6+D Explanation: Informational msg for an archive being written to tape. The user requesed LBI mode, but the device does not support it. System Response: The archive is written in non-LBI mode at the BLKSIZE specified in the message. User Response: If LBI mode is required, direct the output archive to a device that supports the LBI interface. Invoking module: <ACFMBSAM>
ZPFM703I
ZPFM703I - LBI BLKSIZE NOT RESOLVED, USING +6+D Explanation: The BLKSIZE and BLKSZLIM parameters were not resolved from any source, and the device did not return an Optimum or Max BLKSZLIM. System Response: The archive is written in non-LBI mode at the BLKSIZE specified in the message. User Response: If LBI mode is required, specify the BLKSZLIM parameter in the JCL, or the -ARCHIVE_BLKSIZE= command in the SYSIN stream. Invoking module: <ACFMBSAM>
File Manager 319
ZPFM704I
ZPFM704I - Specified BLKSIZE (+7+D) exceeds device maximum, using device optimum (+7+D) Explanation: The resolved BLKSIZE for the archive exceeds the device maximum block size. System Response: The archive is written using the device's reported optimum block size. User Response: Modify the source for the BLKSIZE to be less than or equal to the device's maximum. Sources include: PKZIP command stream JCL SMS Storage Class definition SYS1.PARMLIB definition Invoking module: <ACFMBSAM>
ZPFM705I
ZPFM705I ARCHIVE_BLKSIZE=+8+C+ is invalid, using DYNAMIC Explanation: The resolved BLKSIZE for the archive exceeds the device maximum block size. System Response: The archive is written using the device's reported optimum block size. User Response: Modify the source for the BLKSIZE to be less than or equal to the device's maximum. Sources include: PKZIP command stream JCL SMS Storage Class definition SYS1.PARMLIB definition Invoking module: <ACFMBSAM>
ZPFM706I
ZPFM706I +9+C+ ARCHIVE WRITE STATS: SIZE=+20+C+ BLOCKS=+20+C+ Explanation: Informational message issued with -VERBOSE only. System Response: None User Response: None
File Manager 320
Invoking module: <ACFMBSAM>
ZPFM707I
ZPFM707I +9+C+ ARCHIVE READ STATS: BLOCKS=+20+C+ Explanation: Informational message issued with -VERBOSE only. System Response: None User Response: None Invoking module: <ACFMBSAM>
ZPFM708I
ZPFM708I +9+C+ TAPE ARCHIVE Explanation: Informational message issued with -VERBOSE only. During a long-running tape I/O operation, a status message is displayed, allowing the user or operator to determine why the job appears to be in a wait state. Inserted text: REWINDING Rewinding to beginning of file CLOSING Triggers a rewind SEEKING Long seek to a position on the tape. Not issued for XTAPE seeks. PosTo EOT Forward spacing to end of file on the tape System Response: None User Response: None Invoking module: <ACFMBSAM>
ZPFM711I
ZPFM711I TAPE MOUNT REQUESTED FOR VOLSER +6+C Explanation: Informational message issued with -VERBOSE only. During a long-running tape I/O operation, a status message is displayed, allowing the user or operator to determine why the job appears to be in a wait state. This message indicates that the archive is being positioned to another tape, and that an outstanding tape mount is active for the job.
File Manager 321
System Response: None User Response: None Invoking module: <ACFMBSAM>
ZPFM712W
ZPFM712W NOT ALL TAPES USED ZPFM712C USED : +6+C+ ZPFM712C UNUSED: +6+C+ Explanation: While creating a LBI or XTAPE archive, the user specified a specific set of tape volume serials in the JCL. The ZIP process did not use all of the tapes. If JCL specifies DISP=(,CATLG), the archive is cataloged on all tapes in the JCL, regardless of whether they were actually used. This can cause extra tape mounts when the archive is used as input to a PKUNZIP run, as PKUNZIP will always mount he last tape in the volume list during the search for the CENTRAL DIRECTORY. If multiple volumes were not used, they will be mounted in reverse order until the CENTRAL DIRECTORY is found. ZPFM712W is followed by a set of ZPFM712C messages that provide a map of the used and unused volumes. This message results in RC=4 from the ZIP process. System Response: None User Response: If the archive is being cataloged, recatalog is with only the volumes listed as "USED". If the volume is not being cataloged, make note of the actual list of volumes used, and place only those volumes in the VOL=() JCL parameter in any subsequent UNZIP job. Invoking module: <ACFMBSAM>
ZPFM713E
ZPFM713E TAPE DSN MISMATCH ON VOLUME +6+C+ Explanation: This message occurs when reading a multi-volume tape archive, and an ABEND occurs during an End of Volume exit. The message will be accompanied by an IEC149I 813-04 message in the job log. No recovery is possible, and the UNZIP run ends.
File Manager 322
System Response: None User Response: If an archive tape has not been overwritten, either modify the job's JCL or the system catalog to specify the correct list of volumes. If an archive tape has been overwritten, recreate the archive. Invoking module: <ACFMBSAM>
ZPFM713I
ZPFM713I TAPE DSN MISMATCH ON VOLUME +6+C+ - ATTEMPTING RECOVERY Explanation: This message occurs when reading a multi-volume tape archive, and the volume listed: 1. Was not written to during the ZIP process (see ZPFM712W) 2. Has been overwritten It will be accompanied by an IEC149I 813-04 message in the job log. The UNZIP process attempts to recover by successively mounting each previous archive volume. This process may produce additional ZPFM713I messages. In case 1, recovery will be successful when the last volume that contains data is mounted. In case 2, recovery will not be successful, and an error message indicating that the archive is invalid will be issued. System Response: None User Response: If an archive tape has not been overwritten, either modify the job's JCL or the system catalog to specify the correct list of volumes. If an archive tape has been overwritten, recreate the archive. Invoking module: <ACFMBSAM>
ZPFM714E
ZPFM714E ABEND +3+C+ ON DDNAME +8+C+ DURING +8+C+ OPERATION. RC=8 Explanation: This message occurs when reading or writing a tape, and an IOS ABEND occurs.
File Manager 323
It will be accompanied by an IEC149I xxx-xx message in the job log. The BSAM module signals the error by returning a return code 8. System Response: The ZIP or UNZIP will terminate. User Response: Check the job log for a corresponding IEC message, and take the recommended action for that message. Invoking module: <ACFMBSAM>
ZPFM900T
ZPFM900T +121+C+ Explanation: File Manager processing trace record. This line is only issued when FMGR tracing is turned on. System Response: None User Response: None Invoking module: <ACFMGR>
ZPFM999E
ZPFM999E Invalid FMGR Action: {+8+C+} Explanation: An internal file request error was encountered. System Response: Unpredictable User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACFMGR>
General 324
ZPGE - General Messages
ZPGE001I
ZPGE001I +16+C+ STORAGE QUERY: 24BIT=+8+D+K 31BIT=+8+D+K CACHE=+8+D+K Explanation: Main Task initialization startup. During initialization, PKZIP attempts to determine the total amount of virtual storage available for processing. This value is used along with the -DATA_STORAGE and -MEMORY_MODEL commands to control the amount of virtual storage assigned for various processes. The "Storage Query" values for 24-bit and 31-bit storage are determined by performing a transient variable-length GETMAIN request, and assessing the value(s) returned by the system. The storage obtained is immediately returned to the system following the query GETMAIN. The amounts actually reported by the query are limited to the least of the REGION= JCL parms and the operating system limits set by the system programmer(s) for the installation. An attempt made to increase the amount of virtual storage beyond installation limits will result in lower query and caching values than reflected by the JCL REGION or DATA_STORAGE requests. As of release 5.0.9, the maximum amount of virtual storage requested by the storage query for 31-bit storage is controlled by the REGION= according to the table below. The intent of this technique is to assist users in the control of 31-bit virtual storage acquired by PKZIP. +----------------------+ | JOBSTEP Maximum | | REGION= 31-bit | | Query | | ======== ========= | | 0M 32M | | | | 1 - 16M 64M | | | | > 16M REGION= | +----------------------+ System Response: None User Response: None Invoking module: <ACZMAIN>
General 325
ZPGE002I
ZPGE002I Jobname: +8+C+ Stepname: +8+C+ StepPGM: +8+C+ Callmode: +8+C+ Explanation: Main Task initialization startup. During initialization, the current run-time environment is reported for reference. System Response: None User Response: None Invoking module: <ACZINIT1>
ZPGE111E
ZPGE111E Required log file not accessible: +44+C+ Explanation: The ACTIVITY_LOG data set is required for processing. System Response: Processing is terminated. User Response: Verify that the ACTIVITY_LOG data set is defined and available for output. Invoking module: <ACUTALOG>
ZPGE112I
ZPGE112I ACTIVITY_LOG file is in use and maximum wait time was exceeded. Explanation: Another job or user appears to have exclusive control of the ACTIVITY_LOG data set. The defaults module values for PARMLIB_FILE_WAIT_TIMER and PARMLIB_FILE_WAIT_MAX govern how long retries will be attempted before the limit is reached. System Response: See ZPGE111E User Response: Determine who has the dataset to have it freed, then re-run the job. Invoking module: <ACUTALOG>
General 326
ZPGE113E
ZPGE113E L/E Pre-initialization failed for <+8+C+> RC=+8+H+ Explanation: Language Environment processing failure. Some PKZIP operations require Language Environment runtime support through the CEEPIPI service. The initialization call to CEEPIPI which loads necessary PKZIP service routines failed. Ref: IBM Language Environment Programming Guide "Using PreInitialization Services" +8+C+ - The module requesting CEEPIPI initialization. +8+H+ - The return code from CEEPIPI initialization. System Response: The requested function is terminated. User Response: See additional messages to determine which modules were involved with the initialization request. Invoking module: <ACCOZIPC>
ZPIDCAMS
ZPIDCAMS +121+C+ Explanation: An invocation of IDCAMS was performed and its processing messages are included in the ZIP SYSPRINT file. Reference IBM z/OS Messages manuals for detailed information regarding these messages. System Response: Processing Continues User Response: None Invoking module: <ACCSAMS> z/OS Operating Environment
ISPF User Interface 327
ZPIS – ISPF User Interface Messages
ZPIS001I
ZPIS001I (Internal Message) Explanation: This message is built completely in module ACAMVIEW for the purpose of passing detail file information whenever the ACTION(VIEWISPF) is requested. This is only used for the VIEW function of the ISPF panels. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPIS002I
ZPIS002I (Internal Message) Explanation: This message is built completely in module ACAMVIEW for the purpose of passing detail file information whenever the ACTION(VIEWISPF) is requested. This is only used for the VIEW function of the ISPF panels. System Response: None User Response: None Invoking module: <ACAMVIEW>
ZPIS003I
ZPIS003I (Internal Message) Explanation: This message is built completely in module ACAMVIEW for the purpose of passing detail file information whenever the ACTION(VIEWISPF) is requested. This is only used for the VIEW function of the ISPF panels. System Response: None User Response: None Invoking module: <ACAMVIEW>
License Manager 328
ZPLI - License Manager Messages
ZPLI001I
ZPLI001I +120+C+ Explanation: Informational startup messages produced from each execution of the program. The information includes: - Product name - Release and maintenance level - Execution processor information - Operating system execution level System Response: None User Response: None Invoking module: <ACUTLIC>
ZPLI200I
ZPLI200I +120+C+ Explanation: Informational messages about the product license System Response: None User Response: None Invoking module: <RMUBLIC,RMUDLIC,RMURLIC,RMUSLIC>
ZPLI210I
ZPLI210I +120+C+ Explanation: Informational messages about the Customer environment System Response: None User Response: None Invoking module: <RMUBLIC>
License Manager 329
ZPLI220I
ZPLI220I +120+C+ Explanation: Informational messages about a DEMO license System Response: None User Response: None Invoking module: <RMUDLIC>
ZPLI230E
ZPLI230E +120+C+ Explanation: Control card input used to build the License is invalid System Response: License dataset will not be created User Response: Verify that the characters in the first three fields are correct. If correct, contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <RMUBLIC>
ZPLI230I
ZPLI230I +120+C+ Explanation: Control card input to the license build process System Response: None User Response: None Invoking module: <RMUBLIC>
ZPLI235E
ZPLI235E +120+C+ Explanation: No license control statements found. System Response: The license dataset will not be updated. User Response: Place the license control statements in the LICENSE
License Manager 330
member of the INSTLIB dataset and rerun the job. Invoking module: <RMUBLIC>
ZPLI235I
ZPLI235I +120+C+ Explanation: Informational messages produced from a successful build of the license dataset System Response: None User Response: None Invoking module: <RMUBLIC>
ZPLI240E
ZPLI240E +120+C+ Explanation: The license dataset could not be written. The license dataset is in error. System Response: The license dataset will not be updated. User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <RMUBLIC,RMUDLIC,RMURLIC>
ZPLI250E
ZPLI250E +120+C+ Explanation: The PARM field is invalid. Please use DEMO, UPDATE, REPORT or SHOWSYS. System Response: License dataset will not be updated. User Response: Correct the PARM and resubmit. Invoking module: <RMUBLIC>
ZPLI299E
ZPLI299E +100+C+
License Manager 331
Explanation: The License dataset is not valid for this release. System Response: The report will contain invalid information. User Response: Verify the name of the License dataset. Verify that the License dataset matches the product and release version. Invoking module: <RMURLIC>
ZPLI901E
ZPLI901E +120+C+ Explanation: Product Licensing Error System Response: Only the VIEW feature will function User Response: Rerun LICUPDAT with the correct input. If you continue to receive this error message, contact PKWARE immediately. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACUTLIC>
ZPLI901W
ZPLI901W +120+C+ Explanation: Product Licensing Warning System Response: Product features available for use. User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACUTLIC>
ZPLI902E
ZPLI902E +120+C+ Explanation: Feature Licensing Error You do not have an active license for the listed feature.
License Manager 332
System Response: Functions associated with the feature will not function to their fullest extent. Some features may permit limited functionality (such as viewing the contents of an archive). User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go online at http://www.pkware.com/business_and_developers/support An optional feature of the product can be licensed separately. Below is a list of separately licensable features PKZIP: "GZIP" This feature provides support for GNU Zip. It is a different standard for handling compressed file data in archive "ISPF" This feature provides support for the TSO/ISPF User Interface "Command Line Interface" A subset of the product features can be invoked from the ZIP and UNZIP REXX EXECs. These commands are intended to approximate the PKZIP and UNZIP DOS-based with similar command syntax. "Self Extraction Creator" Create a self-extracting archive by prefixing the archive with a self-extraction program appropriate to a target system. SecureZIP: "Advanced Encryption" Provides public/private key PKI certificate-based encryption and digital signing. Please note: SecureZIP base is always licensed for password processing. "Directory Integration" Enables access to certificates residing on an LDAP server. "ICSF Integration" Enables use of IBM ICSF services for cryptography. "XTAPE-Enhanced Tape Processing"
License Manager 333
Enables Enhanced Tape Processing, including Large Block Interface and ARCHIVE_ZIPFORMAT(XTAPE) single-stage processing. Invoking module: <ACUTLIC>
ZPLI902W
ZPLI902W +120+C+ Explanation: Feature Licensing Warning System Response: Features available for use. User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACUTLIC>
Main Task 334
ZPMT - Main Task Messages
ZPMT002I
ZPMT002I PKZIP processing complete. RC=+8+H+ +8+D+(Dec) Explanation: Main Task informational message. System Response: None User Response: None Invoking module: <ACZMAIN>
ZPMT003E
ZPMT003E ACZMAIN may not be called directly. Use PKZIP or PKUNZIP. Explanation: PKZIP and PKUNZIP are packaged together under one program. However, the correct call sequence (PKZIP or PKUNZIP) must be called for the product to work correctly. System Response: Processing terminates. User Response: Change the call (or JCL) to run the proper program. Invoking module: <ACZMAIN>
ZPMT011W
ZPMT011W INVALID INTERNAL DIRECTIVE: +80+C+ Explanation: An internal logic error was detected. System Response: Unpredictable User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACZMAIN>
ZPMT020I
ZPMT020I DISPLAY STATUS
Main Task 335
Explanation: Reserved for future use. System Response: None User Response: None Invoking module: <ACZMAIN>
ZPMT060T
ZPMT060T Work Directive: +80+C+ Explanation: Main Task processing trace record. This line is only issued when general tracing is turned on. System Response: None User Response: None Invoking module: <ACZMAIN>
ZPMT101I
ZPMT101I PartnerLink: +80+C+ Explanation: Main Task processing trace record. Various processing status messages may be issued as shown below. "{PARTNERLINK=ON} set for certificate processing." SecureZIP Partner processing characteristics will be in effect for digital certificate processing. "GZIP ignored" "INCLUDE_SFX ignored" "PASSWORD ignored: "MASTER_RECIPIENT ignored" SecureZIP Partner does not support the specified request. "Set minimum encrypt method=AES128" ENCRYPTION_METHOD= was not set to the minimum level required for a SecureZIP Partner encryption ZIP run. The published default of AES128 was set. System Response: None User Response: None Invoking module: <ACCMGR>
Main Task 336
ZPMT901E
ZPMT901E Initialization error at label: +8+C+ Explanation: An error occurred during base initialization. This can be caused by an insufficient run-time Region size, by inappropriate <ACZDFLT> parameters or incorrect installation of the PKZIP Load Library. System Response: See supplemental information below User Response: Review the information provided to determine whether an installation problem has occurred. If so, contact your local support staff to correct the problem. Otherwise,* contact PKWARE Technical Support. For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go on-line at http://www.pkware.com/business_and_developers/support. Invoking module: <ACZINIT1> Supplemental Information: LABEL: The label indicates where the failure occurred in <ACZINIT1>. values are as follows: GETMTVT: The 24-bit main task vector table GETMAIN failed. Programmer response: 1) Check the JOBLOG for other system messages. 2) Increase the region size. System response: 1) Terminate initialization. LOADDFLT: The defaults module <ACZDFLT> could not be loaded. Programmer response: 1) Check the JOBLOG for other system messages, such as s806 or s106 abend conditions. 2) Ensure that <ACZDFLT> is available in the execution environment (STEPLIB, JOBLIB, ispf-ispllib, lnklst, etc.) System response: 1) Terminate initialization. COPYDFLT: The defaults module <ACZDFLT> length does not match the compiled version of <ACZINIT1>. Programmer response: 1) Verify that the release levels of <ACZINIT1>
Main Task 337
and <ACZDFLT> match (by browsing the modules). 2) Re-generate <ACZDFLT> with the maclib which matches the release level of <ACZINIT1>. System response: 1) Terminate initialization. LOADQMGR: Module <ACUTQMGR> could not be loaded. This module Is required for execution. Programmer response: 1) Check the JOBLOG for other system messages, such as s806 or s106 abend conditions. 2) Ensure that <ACUTQMGR> is available in the execution environment (STEPLIB, JOBLIB, ISPF-ISPLLIB, LNKLST, etc.) System response: 1) Terminate initialization. LOADAMS: Module <IDCAMS> could not be loaded. this module Is required for execution. (system module). Programmer response: 1) Check the JOBLOG for other system messages, such as s806 or s106 abend conditions. 2) Ensure that <IDCAMS> is available in the execution environment (STEPLIB, JOBLIB, ispf-ispllib, lnklst, etc.) System response: 1) Terminate initialization. LOADUJRL: Module <ACUTJRNL> could not be loaded. this module Is required for execution. (system module). Programmer response: 1) Check the JOBLOG for other system messages, such as s806 or s106 abend conditions. 2) Ensure that <acutjrnl> is available in the execution environment (STEPLIB, JOBLIB, ispf-ispllib, lnklst, etc.) System response: 1) Terminate initialization. LOADQSYN: Module <acutqsyn> could not be loaded. this module Is required for execution. (system module). Programmer response: 1) Check the JOBLOG for other system messages, such as s806 or s106 abend conditions. 2) Ensure that <acutqsyn> is available in the execution environment (STEPLIB, JOBLIB, ispf-ispllib, lnklst, etc.) System response:
Main Task 338
1) Terminate initialization. OPENTMCB: The task manager "task control block queue" could not Be initialized. Programmer response: 1) Check the JOBLOG for other system messages. 2) increase the region size. System response: 1) Terminate initialization. OPENTMWQ: One of the two task manager work queues could not OPENTMWN Be opened. OPENMTWQ OPENMTWN Programmer response: 1) Report this problem to PKZIP support. System response: 1) Terminate initialization. MAKEJRNL: An attempt to create the journal subtask control Block (tmcb) failed. Programmer response: 1) Report this problem to PKZIP support. System response: 1) Terminate initialization. ATTCHJNL: An attempt to signal the task manager to attach The journal subtask failed. Programmer response: 1) Report this problem to PKZIP support. System response: 1) Terminate initialization. GETTRACE: The 31-bit trace table could not be obtained. Programmer response: 1) Check the JOBLOG for other system messages. 2) Reduce the trace_table_size parameter value in <ACZDFLT> generation. 3) Increase the region size. System response: 1) Terminate initialization. Note: Before terminating execution, <ACZINIT1> attempts to reduce the size of the trace table to 64k.
Main Task 339
ZPMT902E
ZPMT902E INITIALIZATION ERROR - DEFAULTS MODULE mmmmmmmm COMPILED mm/dd/yyhh.mm HAS A VERSION MISMATCH. Explanation: During initialization, defaults module "mmmmmmmm" was loaded and a validation was performed to ensure that the format of the module matches the current release of the software. The module appears to have been compiled by a different release of PKZIP/SecureZIP and needs to be re-assembled. See also: ZPMT903I System Response: Processing is terminated. User Response: Reference the PKZIP/SecureZIP installation materials for instructions on how to tailor the supplied defaults module ACZDFLT. Locate the source used to generate module "mmmmmmmm" and re-assemble it to the correct load library. Invoking module: <ACZINIT1>
ZPMT903I
ZPMT903I THE MODULE WAS LAST ASSEMBLED AT VERSION vvvvvvvv AND MUST BE RE-ASSEMBLED TO RUN WITH VERSION nnnnnnnn. Explanation: During initialization, defaults module "mmmmmmmm" was loaded and a validation was performed to ensure that the format of the module matches the current release of the software. The module appears to have been compiled by a different release of PKZIP/SecureZIP and needs to be re-assembled. See also: ZPMT902E System Response: Processing is terminated. User Response: Reference the PKZIP/SecureZIP installation materials for instructions on how to tailor the supplied defaults module ACZDFLT. Locate the source used to generate module "mmmmmmmm" and re-assemble it to the correct load library. Invoking module: <ACZINIT1>
ZPMT904E
ZPMT904E COULD NOT LOAD DEFAULTS MODULE: +8+C+ Explanation: An error occurred during base initialization.
Main Task 340
A -DM defaults module specification was provided, but the module name shown could not be loaded. This is message is issued in lieu of an Abend S806. System Response: Processing is terminated. User Response: Review the load module name passed in the parameter stream. Verify that the load module is available in the run-time libraries. Invoking module: <ACZINIT1>
ZPMT993W
ZPMT993W +21+C+ failed: S/xxx-rc in program mmmmmmmm - task terminated with RC=cc Explanation: An unexpected task termination was detected. The task manager determined that the abend was not critical. See also: ZPMT994E System Response: Processing for the respective function is terminated. Continued processing will be attempted. User Response: Review the abend information to assess whether this is a critical error. Invoking module: <ACTMGR>
ZPMT994E
ZPMT994E +21+C+ failed: S/xxx-rc in program mmmmmmmm - task terminated with RC=cc Explanation: An unexpected task termination was detected. +21+C+ - Type of task that terminated. Archive Manager Manages archive I/O operations and file scheduling. Configuration Manager Manages settings, command inputs and setup. IDCAMS IBM Access Method Services Journal SYSPRINT message handling C Program Services Digital Certificate processing Extraction UNZIP file handler
Main Task 341
Compression ZIP file handler Unidentified S/xxx-rc - The abend/reason code for the task SA03 - An abend encountered when a higher level task fails to wait for a subtask to complete prior to terminating itself. This is not normally caused by the task reflected in the message. Common causes include: 1. When PKZIP/PKUNZIP is called from an application program, the application failed to wait for PKZIP to complete its processing. 2. When APIB Call Mode is used by an application, it neglected to perform a TERMINATE request. mmmmmmmm - The module found to be in error RC=cc - The internal return code reflected for the condition of the task. This is not the final PKZIP/PKUNZIP Condition code. System Response: Processing for the respective function is terminated. An orderly shutdown is attempted. User Response: Review the abend information to assess whether this is a critical error. Invoking module: <ACTMGR>
ZPMT999E
ZPMT999E Please contact the PKWARE Product Services Division at 1-937-847-2687 for Assistance. Explanation: An error was encountered that may require technical support to evaluate. System Response: None User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACZMAIN>
Task Manager 342
ZPTM - Task Manager Messages
ZPTM001I
ZPTM001I SUBTASK (+3+D+) EP: +8+C+ ATTACHED - TCB: +8+H+ TMCB: +8+H+ Explanation: Task Manager processing information. This line is only issued when general tracing is turned on. Sub-tasking is performed for various components of PKZIP to improve over-all throughput. Each subtask is assigned a number (+3+D+). System Response: None User Response: None Invoking module: <ACTMGR>
ZPTM002I
ZPTM002I SUBTASK (+3+D+) EP: +8+C+ Ended - TCB: +8+H+ Comp: +8+H+ Explanation: Task Manager processing information. This line is only issued when general tracing is turned on. See also ZPTM001I System Response: None User Response: None Invoking module: <ACTMGR>
ZPTM003E
ZPTM003E ATTACH TASK (+3+D) FAILED FOR LMOD: <+8+C+> Explanation: A subtask attach was attempted for the specified module, but a failure was encountered. Abend 806 - Module not found. Abend 106 - Possible region limitation or corrupt module. System Response: None
Task Manager 343
User Response: Check the JOBLOG for abend codes that may indicate the reason for the failure. Invoking module: <ACTMGR>
ZPTM998E
ZPTM998E TASK AT ADDRESS +8+C+ COULD NOT BE LOCATED BY <ACTMETXR> Explanation: Internal Logic error detected. System Response: Unpredictable User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMGR>
ZPTM999E
ZPTM999E INVALID INTERNAL DIRECTIVE: +20+C+ Explanation: Internal logic error detected. System Response: Unpredictable User Response: For Technical Support assistance, please contact the Product Services Division at 937.847.2687, or go to http://www.pkware.com/business_and_developers/support. Invoking module: <ACTMGR>
Trace Recording 344
ZPTR - Trace Recording Messages
ZPTR000I
ZPTR000I +120+C+ Explanation: Trace record. This line is only issued when general tracing is turned on. System Response: None User Response: None Invoking module: <ACUTRACE>
User Abend Codes 345
Chapter 2. User Abend Codes
SecureZIPz should normally terminate with a condition code (not an abend) . This includes situations where a system abend is intercepted by SecureZIPz and reported in the JOBLOG, as well as a non-zero condition code being reported in the job step. (For example, this can happen when invalid DCB information is supplied for an output file and a S001 Abend is detected for the file open).
There are also unique situations for which SecureZIPz determines a dump is appropriate and a user abend is requested. These abend codes (of the form Unnnn) should be reported to product support.
In all cases of abends, detailed information is provided in the JOBLOG:
IEF450I jobname stepname ABEND=S000 Unnnn Reason=xxxxxxxx
where:
jobname is the job name associated with this execution of SecureZIPz.
stepname is the step name associated with this execution of SecureZIPz.
nnnn is the user abend code.
xxxxxxxx is the reason code associated with this abend (typically the return code from the failing system function).
Code Definitions
The abend codes produced by the PKZIP/SECZIP and PKUNZIP/SECUNZIP programs are described in the following section, listed in order by the user abend code.
U1999
Explanation Program Working storage is detected as being inadequate for the module being invoked.
System Response Processing will be stopped for the sub-process involved.
User Response Please contact the Product Support Division at 1-937-847-2687 for assistance. Be prepared to provide the information in the JOBLOG. Retain the JOB output, execution JCL, and dump, if available.
Internal Processing Codes 346
Chapter 3. Internal Processing Codes
This chapter provides a reference for processing codes displayed by other messages.
General
kPKErr_BadParams 3998
kPKErr_MemoryFailure 3997
kPKErr_BufferTooSmall 3996
kPKErr_InvalidAction 3995 Invalid action was requested should not happen
kPKZError_BufferTooSmall 3994
kPKZError_NoMsgFnd 3993 Message not in EvtMsg tables
kPKZError_Warning 3992 A warning issued examine MainErrs structure
kPKErr_MVSMemoryLimit 3991 Avail 31 memory less than MVSMIN_AVAIL_31_K
EvtAuth Errors
kPKErr_NotSigned 3899 Validation not verified
kPKErr_NoEF15_record 3898 No input sign records available
kPKErr_NoZipStoreRec 3897 No Zip Store 0x14
kPKErr_InvalidStatus 3896 No status settings
PKCAuth Errors
kPKErr_NoIssuerData 3799
kPKErr_NoSerialData 3798
kPKErr_NoHashData 3796
kPKErr_CTXAquireFailed 3795
Internal Processing Codes 347
EvtHash Errors
kPKErr_NoHashHandle 3699 No hash handle in BSAFE calls
kPKErr_FailCrtHashObj 3698 Create object failed in create hash
kPKErr_InvalidHashAlgo 3697 Invalid Algorithm for create hash
kPKErr_InvalidHashCrtParm 3696 Unsupported parm create hash
kPKErr_NoHashDigestCrtHash 3695 No hash digest create hash
kPKErr_NotEnoughMemory 3694 Not enough memory
kPKErr_FailedFinalData 3693 Final failed with bad data
kPKErr_FailedCSNBOWH 3692 CSNBOWH Failed
EvtCrypt Errors
kPKErr_PassWordInvalid 3599 Password is invalid i.e.invalid pad bytes
kPKErr_InvalidCryAlgo 3598 Algorithm not in SetAlgoItem function
kPKErr_BSIcrtAlgObj 3597 Failed Initialize B_CreateAlgorithmObject
kPKErr_BSISetAlgInf 3596 Failed Initialize B_SetAlgorithmInfo
kPKErr_BSIcrtKeyObj 3595 Failed Initialize B_CreateKeyObject
kPKErr_BSISetKeyInf 3594 Failed Initialize B_SetKeyInfo "546 weak key"
kPKErr_BSIEncryptIn 3593 Failed Initialize B_EncryptInit
kPKErr_BSIEncryptUp 3592 Failed Data B_EncryptUpdate
kPKErr_BSIEncryptFnl 3591 Failed Final B_EncryptFinal
kPKErr_BSIDecryptIn 3590 Failed Initialize B_DecryptInit
kPKErr_BSIDecryptUp 3589 Failed Data B_DecryptUpdate
kPKErr_BSIDecryptFnl 3588 Failed Final B_DecryptFinal
kPKErr_EvtCryInvalidAction 3587 Invalid action was requested(unexpected)
kPKErr_WZFailMAC 3586 Reserved
Internal Processing Codes 348
kPKErr_HWIcrtAlgObj 3585 Failure returned from Initial_IBM_Objects
kPKErr_HWISetKeyInf 3584 Failed Initial_IBM_Objects
kPKErr_HWIcrtKeyObj 3583 Failed import clear key
KErr_HWIEncryptFnl 3581 Failed Final Call Rtn_ENC_Func/Rtn_SYE_Func
kPKErr_HWIEBlockSize 3580 Failed Data len not multiple of block Rtn
kPKErr_HWOutLen 3579 Output Len is smaller than required
kPKErr_HWDECFinal 3578 Decrypt input not allowed on final call
kPKErr_ICSFNotAvail 3577 12/0 ICSF is not available or started
kPKErr_CSFNoSrvce 3576 12/8 The service or algorithm is not available
kPKErr_CSFENCFail 3575 Either CSNBENC or CSNBDEC failed
kPKErr_CSFSYEFail 3574 Either CSNBSYE or CSNBSYD failed
kPKErr_HWIDecryptUp 3573 Failed Data Rtn_DEC_Func/Rtn_SYD_Func
kPKErr_HWIDecryptFnl 3572 Failed Final Rtn_DEC_Func/Rtn_SYD_Func
kPKErr_RandInvParm 3571 PK_PRNG encountered invalid parameters
kPKErr_RNGFailed 3570 PK_PRNG CSNBRNG returned > 4 return code
EvtCrypt ICSF Integration Codes
kPKErr_HW_InvalidMtrx 3330 Invalid Matrix code was passed to build
kPKErr_HWBadParams 3329 Invalid Parameters passed to CtlMatrx
kPKErr_HWPInvParse 3328 Parsing Error #1 in config parsing
kPKErr_HWConfigFail 3327 The config parsing found invalid configs
kPKErr_HWPCntExceed 3326 More than 3 Facilities were passed
kPKErr_HWPInvalidTxCfg 3325 Error occurred in parsing for type
kPKErr_HWPMissingTxCfg 3324 No FACILITY was found
kPKErr_HWMemoryFailure 3323 Error occurred allocating memory
kPKErr_HWPInvalType 3322 Parsing Error #2 in config parsing
kPKErr_HWAMUTCQRYFail 3321 Either AMUTCQRY failed or it passed back error
kPKErr_HWCSFIQFFail 3320 CSFIQF failed when tried
kPKErr_NoActFacility 3319 No Active Facility available for algorithm
kPKErr_FIPSFailure 3318 No FIPS validated facility was available
Internal Processing Codes 349
EvtCertE Errors
kPKErr_kINVSNoTxStore 3499 No Stores passed
kPKErr_kINVSInvalidTxStore 3498 Invalid Stored passed
kPKErr_kINVSInvParse 3497 Invalid Store Parse-no proper end char
kPKErr_kINVInvStoreType 3496 The store type is invalid
kPKErr_kINVInvLDAPParce 3495 LDAP has invalid parse fields
kPKErr_kINVStoreCntExceed 3494 More than 1 store or 3 LDAPS
kPKErr_kINVSMissingTxStore 3493
kPKErr_kINVSMissingMSK 3492 Combo requested by no password or MSK supplied
kPKErr_NoRecipients_Fnd 3491 No Recipients selected
CertKeys Errors
kPKErr_kCERTPinitalz 3490 PK_E_INITIALIZE
kPKErr_kCERTPInvalidParm 3489 PK_E_INVALID_PARAM
kPKErr_kCERTExportKey 3488 PK_E_CRYPT_EXPORT_KEY
kPKErr_kCERTPCryptErr 3487 PK_E_CRYPT
kPKErr_kCERTPImportKey 3486 PK_E_CRYPT_IMPORT_KEY
kPKErr_kCERTPCreateKey 3485 PK_E_CRYPT_CREATE_KEY
kPKErr_kCERTPProvErr 3484 PK_E_CRYPT_IMPORT_KEY
GetCertFls Errors
kPKErr_kCRTFLreaderror 3483 Problem reading store Cert
kPKErr_kCRTFLinvalidType 3482 PKINVALID_TYPE
kPKErr_kCRTFLSizeError 3481 Size of Cert not consistent
kPKErr_kCRTFLOpenCert 3480 Could not translate Cert File
kPKErr_kCRTFLNoFileFnd 3479 File not found (IO 3025 )
kPKErr_kCRTFLRecpREQ 3478 Recipient Required but failed
kPKErr_kCRTFLINVEncAlgo 3477 Invalid Encryption Algorithm Passed
kPKErr_kCRTFLCryRandFail 3476 pkCryptGenRandom Failed
kPKErr_kCRTFLLDAPOpenFail 3475 LDAP Failed to Open
Internal Processing Codes 350
EvtCertE Decryption Errors
kPKErr_kCRTLINVcontrol 3474 Decrypt Action with invalid Control code
kPKErr_kCRTLNoRecpListIn 3473 No recipient List data
kPKErr_kCRTLRecpNoPW 3472 Recipient must have password for private
kPKErr_kCRTLbsPrvKeyErr 3471 Error in build BSAFE Key Obj
kPKErr_kCRTLnoHashMatch 3470 No Recip hash macth stored hash table
kPKErr_kCRTLInvalidRLData 3469 Recip List Data Invalid i.e. Simple Blob
kPKErr_kCRTLInvImportParms 3468 Invalid Import Keys/parms
kPKErr_kCRTLRDStoreFile 3467 Error Reading Store Type2Cert
kPKErr_RLBufferTooSmall 3466 Supplied bRecipients_List area too small
kPKErr_kCRTFLTOTMaxCnt 3465 Selected exceeded TOTAL_MAX_CERTS 3,275
kPKErr_kCRTFLTotalMaxCnt 3464 Number of Certs returned > dwMax_nbr_certs
kPKErr_kCRTFLEndOfDB 3463 End of DB search (only on >2nd pass)
kPKErr_kCRTLNoPrvtStore 3462 No Private keys found for Decryption
kPKErr_kCERTPSavStore 3461 CertKeyC pkCertSaveStore error
kPKErr_kCERTPInvStore 3460 CertKeyC passed invalid store id
kPKErr_kCERTPSavSSize 3459 CertKeyC Store Size allowed is too small
kPKErr_kCERTLSNoStore 3458 CertList No store supplied
kPKErr_kCERTLSOpenStore 3457 CertList supplied store could not be opened CW2
kPKErr_kCERTLSNoCertsFnd 3456 CertList Failed to get any cert's from store
EvtCertE Signing Errors
kPKErr_kSignHErr 3455 Signing Hash failed
kPKErr_kSignInvalidParm 3454 Invalid function parms
kPKErr_kSignInvalidHash 3453 Invalid hash for signing
kPKErr_kAuthFailed 3452 One or More Signers failed-see FDBK details
kPKErr_kAuthReqFailed 3451 One or More Input Req'd Signers were not foun d
kPKErr_kAuthNoFeedBack 3450 No Feedback area provided for Getsigner names
kPKErr_kSignArchMaxed 3449 More than 1 archive signer submitted
kPKErr_kINVSConfigMissing 3448 No store config supplied for initial
kPKErr_kAuthNoAuthFail 3447 >= 1 Input Opt Signers but no auth took place
kPKErr_kCertFailedFlts 3446 >=1 Certificate failed filters-see FDBK
kPKErr_kSysStoreFailure 3445 Could not open CA, Root or CRL store
Internal Processing Codes 351
PartnerLink SecureZIP Partner Errors
kPKErr_kPLnoAuthFL 3350 No SPONSOR_AUTH specified
kPKErr_kPLStoreFailure 3349 Could not Open PL physical file
kPKErr_kPLAuthFail 3348 Auth signature from archive not partner
kPKErr_kPLAuthStoreErr 3347 Internal Signature was not valid
kPKErr_kPLEncyptFail 3346 Reserved
kPKErr_kPLEncryptStoreErr 3345 Internal Signature was not valid
kPKErr_kPLMultiRecips 3344 More than one PL Recipient
kPKErr_kPLNotPackage 3343 Auth not PL Package
Internal Processing Codes 352
Certificate Store VSAM Error Codes
The following codes are provided as a problem determination reference for DBX update processing.
0001 Invalid argument passed
0002 Open Failed
0003 Close Failed
0004 End of File
0005 File is already open
0006 Unable to access an internal variable
0007 REXX record variable could not be accessed or was undefined
0008 Duplicate record
0010 Unable to save VSAM error data
0011 Unable to set return message text
0012 ACB was not available to perform CLOSE request
0014 ACB was not available to perform I/O request
0015 Unable to obtain max record length for this file
0016 Record not found, or FULL KEY not specified
0017 Cannot determine length of record
0018 Unable to modify RPL for "UPDate"
0019 Function Failed
0020 Unable to update RECORD variable
0021 File is not open for INPUT
0022 File is not open for OUTPUT
0023 Unable to switch to DIR processing
0024 READGENERIC only allowed for KSDS
0025 Non-numeric key specified for an RRDS
0026 This function is not allowed for an ESDS
0027 Unable to set RXVSAM_RRN#
0028 A zero length (omitted) key is only allowed for an ESDS
0088 READPREV attempted without a previous STARTBWD
0092 REWRITE or DELETE attempted without a previous READ
0108 Record length = 0, > max, < key length (KSDS)
Internal Processing Codes 353
Certificate Scan Utility (PKSCANCRT) Messages
While scanning an X.509 file for digital certificate information, various processing messages may be issued. The following codes are provided to help determine problems.
001E “--No path entered in call…”
An incorrect input was supplied
002I “File to be PKCS7 Type”
A generic PKCS#7 X.509 file is to be parsed.
003I “File to be Auth PKCS7 Type”
A SecureZIP Partner (Read mode) authentication list of signatories is to be processed
004I “File to be Recip PKCS7 Type”
A SecureZIP Partner (Write mode) list of recipients is to be processed
005I The data set or DD name being used as input for processing
006E --Cannot open Output file
007I “Private Cert will be processed”
A PKCS#12 file containing private keys is to be processed (a password is required to access the contents)
008I Details regarding the entity being processed:
(nnnn) – File size information required for buffers
Type=1 – Process a directory
Type=2 – Process a sequential file
009E “--Password Invalid”
The PKCS#12 access password is not correct
010E “Type 2 PKCS#7 Contains Multiples Failed”
An attempt other than Information List was made to process a PKCS#7 to extract certificate information. This function is only supported for CER and PFX X.509 files.
011E “--Cert PW Required or file is Invalid”
A password was not supplied for a PKCS#12 file, or an invalid file was supplied for public-key or private-key processing.
012E “--Cert File Open Failed”
The supplied file does not appear to be a valid X.509 file for Public-keys.
013E Directory processing failure
014E “Get1File Cannot Find File”
Data set is not found or accessible
015E “--Get1File Open Error for File”
016E “Get1File #2 Input File is 0 length”
Empty file
017E Reserved
018E Reserved
019E FileScan file NOT Found
020E Cannot open Parm file
Internal Processing Codes 354
021I “Validate Sponsor Authentication Signed Message”
The input file is to have its authenticity verified as a SecureZIP Partner (Read mode) authorized Sponsor signatory list.
022I “Validate Sponsor Recipient Signed Message”
The input file is to have its authenticity verified as a SecureZIP Partner (Write mode) recipient list.
023E “ValidateSignedPKCS7 Invalid Type code”
An invalid call type was passed (must be R, A, 7)
024E “ValidateSignedPKCS7”:
"Virtual Storage Exceeded"
Insufficient virtual storage was available for the user process executing the request.
025E “ValidateSignedPKCS7”:
"Failed Exceeded Maximum Certificate"
The Sponsor Package was built with too many recipients (> 3,275) to be processed.
026E “ValidateSignedPKCS7”:
"Signer of the PKCS#7 data is not the allowed signer"
An unauthorized PKCS#7 Sponsor file was identified.
027E “ValidateSignedPKCS7”:
"The PKCS#7 data is not signed, or the signature is invalid"
An unauthorized PKCS#7 Sponsor file was identified.
028E “ValidateSignedPKCS7”:
"The PKCS#7 Container Could not be opened"
An invalid PKCS#7 Sponsor file was identified. (or other errors preventing the open occurred)
029E “ValidateSignedPKCS7”:
ValidateSignedPKCS7 Failed to Open
An internal error was encountered attempting to process the Sponsor File.
030I
031I
032I
“PL EndEntity Store”
“PL CA Store”
“PL Root Store”
Report Headers
Internal Processing Codes 355
033E
“No Certificates in PKCS#7” End Entity”
The package file must contain at least one "End Entity" certificate.
034W
035W “No Certificates in PKCS#7” CA/Root”
One or more supplied End Entity certificates did not have their associated Certificate Authority chain included.
- For SecureZIP Partner (Read mode) AUTHCHK operations, AUTHENTICATE=TRUST and AUTHENTICATE=REVOKE certificate validation checking will require that a CA and Root P7 be installed independently to the local certificate store.
- For SecureZIP Partner (Write mode) RECIPIENT operations, VALENCRYPT=TRUST and VALENCRYPT=REVOKE certificate validation checking will require that a CA and Root P7 be installed independently to the local certificate store.
036E “ValidateSignedPKCS7 Failed”
An unexpected error occurred with an invalid package file
HFS Error Codes ($HFSCODE)
The following error codes are provided to help determine problems pertaining to HFS (UNIX file system) processing.
Both general Status errors and associated Reason (Feedback) codes are listed.
2934 Call to HFS Close Error Encountered
2935 Call to HFS Open Error Encountered
2936 Call to HFS IO Write Error Encountered
2937 Call to HFS IO Read Error Encountered
2938 Call to HFS IO had invalid parameters passed
2939 Read received EOF
2940 HFS Processor Unknown Error
2944 Archive was found to be empty.
2945 Archive structure problem occurred: Reason Code(&cd). &cd code refers to message ZPCM28&cdE. See message for more on the reason.
2946 File I/O Failure occurred in archive process
2947 File Open Failure occurred in archive process
2948 Archive process buffer Failure occurred
2949 Get zip archive API has invalid parameters
2950 More CD data available from archive.
2966 Directory/File is Symbolic Link and failed filter.
2967 A request to a remote file system had a connection time condition.
2968 Write Permission not available.
2969 Directory failed to be created. - mkdir() failed.
2970 Directory not found
Internal Processing Codes 356
2971 Directory open() failed
2972 Rename File failed
2973 Remove Link failed
2974 Invalid unalloc DD or file
2975 unalloc failed
2976 dynalloc() failed
2977 Internal FMCB invalid
2978 Invalid starting directory
2979 Invalid CWD
2980 PostNewName() failed
2981 File not valid
2982 File not found
2983 Invalid characters in name
2984 stat() or open() failed
2985 getcwd() failed
2986 File match failed
2987 Cannot remove parent dir.
2988 Insufficient Virt Storage
2989 Internal Select Parm error
2990 Internal Action Parm error
2994 Internal Buffer too small
2995 Internal Message error
2996 Internal Parm error
1026 Write or Create permissions were denied.
1. Execute permission was not available to examine one of the directories in the PATH.
2. Write permission was not granted to create a new directory or file to complete the absolute PATH (and filename).
Utility Program Messages 357
Chapter 4. Utility Program Messages
This chapter provides information associated with specialized utilities.
PKCS - Certificate Store Utility Messages
See also “ZPCA - Certificate Administration Messages” in Chapter 1.
PKCS023
PKCS023 Certificate Administration Generic Messages Explanation: While adding certificates (public or private) to the local store, messages will appear with the PKCS023 message number. While most messages are informational type messages, at times there are error messages reporting a failure while trying to add a certificate to the local certificate stores. System Response: See supplemental error messages below User Response: Review the information provided to determine whether an environment problem has occurred or a file issues has occurred. If the problem continues, contact your local support staff to correct the problem. Otherwise, contact PKWARE Technical Support. For more information, see the SecureZIP Administrator Guide* Invoking module: <PKCS023> Supplemental Error Message: 1: 'Duplicate "certstor_dsn" already stored' The Certificate Store Dataset Name Member (certstor_dsn) already exist in the local public or private store. Response: Choose another member name to store the certificate or remove current member. Re-try request. 2: 'Call to scan routine failed rc=&x' The inputted certificate failed to be scanned successfully for certificate contents. Review previous messages for more details for the failure. It may be an invalid certificate type or require a password if it is
Utility Program Messages 358
a private certificate package. 3: The certificate does not declare itself to be an End- Entity. If the inputted file is an Intermediate CA or Root Certificate Authority certificate type, then you should return to the previous panel to direct the certificate into the correct Store Type. Note: Some certificates are issued without an End-Entity indicator. Press ENTER to install. PF3 or 'CANCEL' to abort and review certificate details. 4: 'Add request cancelled by user' A previous message was issued that required a response of PF3 to CANCEL or ENTER to accept. This message indicates that the PF3 key was pressed and add was cancelled. 5: "Some current Security Policy settings did not pass." "PF3 or 'CANCEL' to abort the add, or 'ENTER' to continue." The addition of a certificate file was found to be either not trusted or has been revoked while the Security Policy indicates they must be trusted or not revoked. To continue press the ENTER key. 6: 'CSPUB_DBX - t: &vsamdb_dsn' The Certificate Store public database is trying to be updated with the contents of the inputted certificate, but a failure has occurred. Review all previous messages to determine why the file failure has occurred. 7: 'CERTDBV DSN=&vsamdb_dsn' 'Allocation of CERTDBV failed rc=&x' While trying to allocate the Certificate Database &vsamdb_dsn for updating, an allocation error occurred. More details on the failure will follow this message. 8: 'Cert. added to data base "&file"' The certificate was successfully added to the database &file. 9: 'Certificate not added' 'Duplicate key found - &key' An attempt to add a certificate was unsuccessful because the public key hash for the certificate already existed in the Certificate Database. 10: 'CERTDBV add failed &rc' While adding a certificate to the Certificate Database, a failure occurred with reason code &rc. See "Certificate Store VSAM Error Codes" in the message guide for more details about the failure.
Utility Program Messages 359
11: 'CERTDBV open failed &rc' While Opening the Certificate Database, failure occurred with reason code &rc. See "Certificate Store VSAM Error Codes" in the message guide for more details about the failure. 12: 'Certificate copy to &certstor failed &rc' While coping the inputted certificate file &certstor to the local public/private store file, a failure occurred with reason code &rc. See previous messages for more details on why the failure occurred. 13: 'ALLOC &file failed' While attempting to copy the inputted file to its local store file, a dataset allocation failure occurred for the &file. The messages following this message will provide more details for the failure. 14: 'repro failed &rc' While copying the inputted file to its store file, an error occurred. Review all previous messages for more details. 15: 'free fail frfile &rc or free fail tofile &rc' The freeing of the inputted file (frfile) or the store file (tofile) failed with the reason code &rc. 16: 'setup fail &rc' PKCS023 module failed during setup initialization with reason code &rc. Review previous message for more details of the failure. 17: 'lminit fail &rc' PKCS023 module failed during setup initialization while doing a LMINIT with reason code &rc for the public/private store. Review previous message(s) for more details. 18: 'lmopen fail &rc' PKCS023 module failed during setup initialization while doing a LMOPEN with reason code &rc for the public/private store. Review previous message(s) for more details.
PKCS0231
---Begin new PKCS0231 CA and Root Store Administration Generic Messages Explanation: While administrating the CA and/or Root stores, messages will appear with the PKCS0231 message number. While most messages are informational in nature, under some conditions, error messages report a failure or warning while trying to add
Utility Program Messages 360
a certificate to the CA/Root stores. Along with the PKCS0231 messages, messages that start with ZPCA8 may appear with more details on a failure. System Response: See supplemental error messages below User Response: Review the information provided to determine whether an environment problem has occurred or a file issue has occurred. If the problem continues, contact your local support staff to correct the problem. Otherwise, contact PKWARE Technical Support. For more information, see the SecureZIP Administrator's Guide. Invoking module: <PKCS0231> Supplemental Error Message: 1: "Add Certificate Failed for: &srcfile_dsn" "See the preceding messages for the reason" "Add Certificate Failed" While trying to import certificates(s) to the CA or Root store, an error occurred that prevented the certificate(s) from being added to the store. The reason and details of the failure are shown in previous messages that begin with the prefix ZPCA8. 2: "Add Certificate Warning for: &srcfile_dsn" "See the preceding messages for the reason" "Add Certificate Warning" While importing certificates(s) to the CA or Root store, a condition occurred that warns about the certificate(s) that were added to the store. The details of the warnings are shown in previous messages that begin with the prefix ZPCA8. 3: "&srcfile_dsn invalid - re-specify" The Input Certificate File name &srcfile_dsn is invalid or cannot be found. Verify and correct the file name and re-run. 4: "Processing &file" This informational message displays the current file being processed. There will be a message for the Input Certificate File, the CA Store File, and the Root Store File. 5: "Extract Failed for: &bkupdsn" "Can not allocate the P7B store" A backup copy was requested prior to the import process, but the backup dataset name &bkupdsn specified could not be created due a file allocation error. 6: "Could not make a backup copy of the store &storbkpi" A backup copy was requested prior to the import process, but the store copy process failed. Review previous
Utility Program Messages 361
messages. 7: "Could not lock down the CSCRL store for add &cscrl" The administration program was trying get exclusive control of the CRL store and it failed because the store is in use by another user/session. Try again later when the CRL store is free. 8: "Could not copy the CSCRL store for add &cscrl" The admin program was trying to make a temporary copy of the CRL store when a failure occurred. Review previous messages in the log for more details. 9: "Add stopped by user" A backup copy was requested prior to the certificate import process using an existing backup dataset. A warning message "Overwrite existing Backup" was issued with an option to overwrite the dataset or to end the backup process. If PF3 was keyed to cancel the overwrite, then this message is issued to indicate that no additions took place to the CA or Root store.
Index
Certificate scan utility, 354 Code Definitions, 346 HFS (UNIX file system), 356 IEC214I, 7 IEF238D, 7 IEF244I, 8 IEF877E, 8 IGD17271I, 8 IKJ56228I, 9 PKCS023, 358 PKCS0231, 360 PKSCANCRT, 354 U1999, 346 User Abend Codes, 346 ZPAM000I, 10 ZPAM000W, 10 ZPAM001C, 10 ZPAM001I, 11 ZPAM002I, 11 ZPAM003I, 11 ZPAM004I, 12 ZPAM005I, 12 ZPAM006I, 13 ZPAM007C, 13 ZPAM007I, 14
ZPAM008I, 14 ZPAM009I, 14 ZPAM010I, 15 ZPAM011C, 16 ZPAM011I, 16 ZPAM012C, 16 ZPAM012I, 17 ZPAM013I, 17 ZPAM015I, 17, 18 ZPAM016I, 18 ZPAM017C, 18 ZPAM017I, 18 ZPAM018I, 19 ZPAM019I, 19 ZPAM020I, 19 ZPAM021I, 19 ZPAM030I, 20 ZPAM031I, 20 ZPAM032I, 21 ZPAM033I, 21 ZPAM034T, 22 ZPAM035E, 22 ZPAM036E, 22 ZPAM037E, 22 ZPAM038E, 23
Index 362
ZPAM039I, 23 ZPAM040C, 24 ZPAM040E, 24 ZPAM041E, 24 ZPAM045W, 25 ZPAM046E, 26 ZPAM046I, 26 ZPAM046W, 27 ZPAM050I, 27 ZPAM051I, 27 ZPAM060T, 28 ZPAM070T, 29 ZPAM071T, 29 ZPAM080I, 29 ZPAM081I, 29 ZPAM081W, 30 ZPAM082W, 30 ZPAM083I, 30 ZPAM084I, 31 ZPAM085W, 31 ZPAM086W, 31 ZPAM087C, 32 ZPAM087W, 32 ZPAM088E, 32 ZPAM089E, 33 ZPAM091W, 33 ZPAM092E, 34 ZPAM093W, 35 ZPAM094E, 35 ZPAM095E, 35 ZPAM096E, 36 ZPAM097I, 37 ZPAM098E, 37 ZPAM100I, 37 ZPAM101I, 38 ZPAM109I, 38 ZPAM111E, 38 ZPAM140I, 38 ZPAM150E, 39 ZPAM151E, 40 ZPAM152I, 40 ZPAM162I, 40 ZPAM163E, 41 ZPAM180C, 42 ZPAM180I, 42 ZPAM181C, 42 ZPAM181E, 42 ZPAM182E, 43 ZPAM183E, 43 ZPAM184E, 43 ZPAM185E, 44 ZPAM191I, 44 ZPAM193W, 44 ZPAM201E, 45 ZPAM202E, 45, 46 ZPAM204E, 46 ZPAM212T, 46 ZPAM251I, 46 ZPAM252C, 47 ZPAM252I, 47 ZPAM253I, 48 ZPAM254I, 48
ZPAM255I, 49 ZPAM256W, 49 ZPAM257E, 50 ZPAM290I, 50 ZPAM291I, 51 ZPAM292I, 51 ZPAM293I, 51 ZPAM301I, 52 ZPAM302I, 53 ZPAM303I, 54 ZPAM304I, 55 ZPAM305I, 56 ZPAM306I, 56 ZPAM307I, 56 ZPAM308I, 56 ZPAM309C, 57 ZPAM309I, 57 ZPAM310I, 57 ZPAM311I, 58 ZPAM312C, 58 ZPAM312I, 59 ZPAM313I, 59 ZPAM314I, 59 ZPAM316E, 60 ZPAM317E, 60 ZPAM318I, 61 ZPAM319I, 61 ZPAM320I, 61 ZPAM321I, 62 ZPAM322I, 63 ZPAM323I, 63 ZPAM324I, 64 ZPAM325I, 65 ZPAM326I, 65 ZPAM329I, 65 ZPAM331I, 66 ZPAM332C, 66 ZPAM332I, 67 ZPAM333I, 67 ZPAM390W, 68 ZPAM400E, 68 ZPAM560I, 68 ZPAM561I, 69 ZPAM562I, 69 ZPAM700I, 70 ZPAM701E, 71 ZPAM702I, 71 ZPAM706W, 71 ZPAM710I, 72 ZPAM711I, 72 ZPAM712I, 72 ZPAM713I, 73 ZPAM800I, 73 ZPAM900T, 74 ZPAM901E, 74 ZPAM911E, 74, 75 ZPAM912E, 75 ZPAM913E, 76 ZPAM914E, 76 ZPAM915E, 76 ZPAM916E, 77 ZPAM931W, 77
Index 363
ZPAM950E, 78 ZPAM999E, 78 ZPAP - Application Programming Interface Messages,
79 ZPAP001E, 79 ZPAP002E, 79 ZPAP003E, 79 ZPAP004E, 80 ZPAP005E, 80 ZPAP006E, 81 ZPAP007E, 81 ZPAP008E, 81 ZPAP009E, 82 ZPAP010I, 82 ZPAP011I, 82 ZPAP020E, 83 ZPAP021E, 83 ZPAP050E, 83 ZPAP051E, 84 ZPAP090E, 84 ZPAP091E, 84 ZPAP100I, 85 ZPAP101E, 85 ZPAP102E, 85 ZPAP200I, 86 ZPAP201E, 86 ZPAP202E, 86 ZPAP203E, 87 ZPAP204W, 87 ZPAP210I, 87 ZPAP211I, 88 ZPAP290E, 88 ZPAP406E, 88 ZPAP407E, 89 ZPAP408E, 89 ZPAP409E, 90 ZPAP498E, 90 ZPAP499E, 90 ZPAP900I, 91 ZPCA - Certificate Administration Messages, 92 ZPCA801E, 92 ZPCA802E, 92 ZPCA803E, 93 ZPCA804E, 93 ZPCA805E, 94 ZPCA806E, 94 ZPCA807E, 95 ZPCA808E, 95 ZPCA809E, 95 ZPCA810E, 96 ZPCA811E, 96 ZPCA812E, 97 ZPCA813E, 97 ZPCA814E, 98 ZPCA815E, 98 ZPCA816E, 99 ZPCA817E, 99 ZPCA818E, 99 ZPCA819E, 100 ZPCA820E, 100 ZPCA821E, 101 ZPCA822E, 101
ZPCA823E, 102 ZPCA824E, 102 ZPCA825E, 102 ZPCA826E, 103 ZPCA827E, 103 ZPCA828E, 103 ZPCA829E, 104 ZPCA830E, 104 ZPCA831E, 105 ZPCA832E, 105 ZPCA833W, 105 ZPCA834W, 106 ZPCA835E, 106 ZPCA836E, 106 ZPCA837E, 107 ZPCA838E, 107 ZPCA839E, 108 ZPCA840E, 108 ZPCA841E, 108 ZPCA842E, 109 ZPCA843E, 109 ZPCA844E, 109 ZPCA845E, 110 ZPCA846W, 110 ZPCA847W, 110 ZPCA848W, 111 ZPCA849E, 111 ZPCA850E, 112 ZPCA851E, 112 ZPCA852E, 113 ZPCA853E, 113 ZPCA854E, 113 ZPCA900I, 114 ZPCA901E, 114 ZPCA910I, 115 ZPCA911E, 115 ZPCA912E, 115 ZPCA913E, 115 ZPCA914W, 116 ZPCA915E, 116 ZPCA916E, 116 ZPCA917E, 116 ZPCA920I, 117 ZPCA921E, 117 ZPCA930I, 117 ZPCA931E, 117 ZPCA932E, 118 ZPCA933W, 118 ZPCA934E, 118 ZPCA940I, 119 ZPCA941E, 119 ZPCA942E, 119 ZPCA943E, 120 ZPCA950I, 120 ZPCA951E, 120 ZPCA952W, 120 ZPCA953E, 121 ZPCA954E, 121 ZPCA955E, 121 ZPCA960I, 121 ZPCA961E, 122 ZPCA970I, 122
Index 364
ZPCA971E, 122 ZPCA972E, 122 ZPCA973E, 123 ZPCA978I, 123 ZPCA980I, 123 ZPCA981E, 124 ZPCA990I, 124 ZPCA991E, 124 ZPCE - Compression Engine Messages, 125 ZPCE060T, 125 ZPCE201I, 125 ZPCE204E, 125 ZPCM - Configuration Manager Messages, 126 ZPCM000I, 126 ZPCM001E, 126 ZPCM002E, 127 ZPCM003E, 127 ZPCM004E, 127 ZPCM005E, 128 ZPCM006E, 128 ZPCM007E, 128 ZPCM008E, 129 ZPCM009E, 129 ZPCM010E, 130 ZPCM010I, 130 ZPCM011I, 130 ZPCM012T, 131 ZPCM013T, 131 ZPCM014T, 131 ZPCM015I, 132 ZPCM016I, 132 ZPCM017I, 132 ZPCM018E, 133 ZPCM019E, 133 ZPCM020C, 133 ZPCM020I, 133 ZPCM021C, 134 ZPCM021I, 134 ZPCM022C, 134 ZPCM022I, 135 ZPCM023C, 136 ZPCM023I, 136 ZPCM024C, 137 ZPCM024I, 138 ZPCM025C, 138 ZPCM025I, 139 ZPCM027I, 139 ZPCM028I, 139 ZPCM030T, 140 ZPCM031I, 140 ZPCM032W, 141 ZPCM033I, 141 ZPCM034T, 141 ZPCM035E, 142 ZPCM036T, 142 ZPCM037W, 142 ZPCM038I, 143 ZPCM039I, 143 ZPCM040E, 143 ZPCM041T, 143 ZPCM042W, 144 ZPCM043E, 144
ZPCM044T, 144 ZPCM045W, 145 ZPCM046E, 145 ZPCM047I, 145 ZPCM048I, 146 ZPCM050W, 146 ZPCM051W, 146 ZPCM052I, 147 ZPCM053W, 147 ZPCM055W, 148 ZPCM056W, 148 ZPCM057E, 148 ZPCM058W, 149 ZPCM060T, 149 ZPCM061T, 149 ZPCM062T, 150 ZPCM063T, 150 ZPCM064T, 150 ZPCM065T, 151 ZPCM069E, 151 ZPCM070T, 151 ZPCM071E, 152 ZPCM072E, 152 ZPCM073E, 152 ZPCM074E, 153 ZPCM075E, 153 ZPCM076E, 153 ZPCM077E, 154 ZPCM078E, 154 ZPCM079E, 154 ZPCM088E, 155 ZPCM089E, 155 ZPCM090E, 156 ZPCM100I, 156 ZPCM101W, 156 ZPCM102E, 157 ZPCM132W, 157 ZPCM133I, 157 ZPCM193W, 157 ZPCM199I, 158 ZPCM201T, 159 ZPCM202T, 159 ZPCM203E, 159 ZPCM250C, 160 ZPCM250I, 160 ZPCM251E, 160 ZPCM252I, 161 ZPCM253I, 162 ZPCM254E, 162 ZPCM255C, 162 ZPCM255E, 163 ZPCM256E, 163 ZPCM257E, 164 ZPCM258W, 164 ZPCM259E, 165 ZPCM260W, 165 ZPCM261E, 166 ZPCM262E, 166 ZPCM263E, 167 ZPCM265E, 167 ZPCM266W, 168 ZPCM267E, 168
Index 365
ZPCM268I, 169 ZPCM269W, 169 ZPCM270E, 170 ZPCM270W, 170 ZPCM271W, 171 ZPCM272E, 171 ZPCM273C, 172 ZPCM273E, 172 ZPCM274I, 172 ZPCM275I, 173 ZPCM276C, 173 ZPCM276I, 173 ZPCM277I, 174 ZPCM278I, 174 ZPCM281E, 175 ZPCM282E, 175 ZPCM283E, 176 ZPCM284E, 176 ZPCM285E, 177 ZPCM286E, 177 ZPCM290I, 177 ZPCM291I, 178 ZPCM292E, 179 ZPCM900I, 179 ZPCM900T, 179 ZPCM901E, 180 ZPCM902E, 180 ZPCM950E, 180 ZPCO - Compression Manager Messages, 182 ZPCO060T, 182 ZPCO070T, 182 ZPCO071I, 182 ZPCO080E, 183 ZPCO081E, 184 ZPCO082E, 184 ZPCO083W, 185 ZPCO084W, 185 ZPCO085E, 186 ZPCO095I, 186 ZPCO100I, 187 ZPCO101I, 187 ZPCO109I, 187 ZPCO110I, 188 ZPCO111I, 188 ZPCO900T, 188 ZPCO999E, 189 ZPCS - Common Service Messages, 190 ZPCS010W, 190 ZPCS100T, 190 ZPCS121E, 190 ZPCS200I, 191 ZPCS201W, 191 ZPCS202W, 192 ZPCS203W, 192 ZPCS211I, 193 ZPCS212I, 193 ZPDA - Dynamic Allocation Messages, 194 ZPDA000I, 194 ZPDA001E, 196 ZPDA001I, 197 ZPDA003E, 197 ZPDA004E, 198
ZPDA005E, 198 ZPDA011E, 198 ZPDA020T, 199 ZPDA021T, 199 ZPDA022T, 199 ZPDA023T, 200 ZPDA029T, 200 ZPDA091T, 200 ZPDA101I, 200 ZPDA102I, 201 ZPDA111I, 201 ZPEN - Encryption Processing Messages, 203 ZPEN001I, 203 ZPEN002W, 203 ZPEN003W, 203 ZPEN005I, 204 ZPEN006E, 204 ZPEN007E, 204 ZPEN008E, 205 ZPEN009E, 205 ZPEN010I, 206 ZPEN011W, 206 ZPEN013I, 206 ZPEN014I, 207 ZPEN015I, 207 ZPEN016W, 208 ZPEN017E, 208 ZPEN018W, 209 ZPEN019W, 210 ZPEN020W, 210 ZPEN021I, 210 ZPEN022C, 211 ZPEN022I, 211 ZPEN023I, 211 ZPEN025I, 212 ZPEN029E, 212 ZPEN030I, 213 ZPEN031E, 213 ZPEN032E, 214 ZPEN032I, 214 ZPEN034E, 214 ZPEN035E, 215 ZPEN035I, 215 ZPEN036W, 215 ZPEN037C, 216 ZPEN037W, 216 ZPEN038E, 217 ZPEN039E, 217 ZPEN040W, 218 ZPEN041I, 218 ZPEN045E, 219 ZPEN045I, 219 ZPEN047C, 219 ZPEN047W, 220 ZPEN049E, 220 ZPEN050E, 221 ZPEN050W, 222 ZPEN057C, 222 ZPEN057I, 223 ZPEN057W, 223 ZPEN100E, 224 ZPEN101E, 224
Index 366
ZPEN102E, 225 ZPEN103E, 225 ZPEN104E, 225 ZPEN105E, 226 ZPEN109T, 226 ZPEN110I, 227 ZPEN121E, 228 ZPEN202E, 229 ZPEN203E, 229 ZPEN204E, 230 ZPEN205I, 231 ZPEN300I, 232 ZPEN301E, 232 ZPEN302I, 233 ZPEN303I, 233 ZPEN304I, 234 ZPEN305E, 234 ZPEN306I, 235 ZPEN307I, 236 ZPEN308I, 236 ZPEN309I, 237 ZPEN310I, 238 ZPEN313I, 238 ZPEN314I, 239 ZPEN315I, 239 ZPEN316W, 240 ZPEN317W, 241 ZPEN318W, 241 ZPEN320I, 242 ZPEN321I, 242 ZPEN322I, 244 ZPEN324E, 244 ZPEN325E, 245 ZPEN326E, 245 ZPEN327E, 246 ZPEN328E, 246 ZPEN329E, 247 ZPEN330E, 247 ZPEN331I, 248 ZPEN332E, 249 ZPEN333E, 249 ZPEN335I, 250 ZPEN336I, 250 ZPEN337I, 250 ZPEN340I, 251 ZPEN341C, 252 ZPEN341I, 253 ZPEN342C, 254 ZPEN342I, 255 ZPEN343E, 257 ZPEN343I, 257 ZPEN344I, 258 ZPEN350I, 258 ZPEN351I, 259 ZPEN359I, 259 ZPEN360E, 259 ZPEN361I, 260 ZPEN362I, 260 ZPEN364E, 261 ZPEN365E, 261 ZPEN368I, 261 ZPEN370I, 262
ZPEN373E, 262 ZPEN374I, 263 ZPEN375I, 263 ZPEN377E, 263 ZPEN378I, 264 ZPEN379I, 264 ZPEN380E, 264 ZPEN381I, 265 ZPEN382W, 265 ZPEN383I, 266 ZPEN384I, 266 ZPEN385I, 267 ZPEN392E, 267 ZPEN393E, 268 ZPEN394I, 268 ZPEN399I, 269 ZPEN403E, 269 ZPEN404E, 270 ZPEN405E, 270 ZPEN406E, 271 ZPEN407W, 271 ZPEN411E, 271 ZPEN412E, 272 ZPEN413E, 273 ZPEN414E, 273 ZPEX - Extract Manager Messages, 275 ZPEX000I, 275 ZPEX001C, 275 ZPEX001I, 276 ZPEX001W, 276 ZPEX002C, 277 ZPEX002I, 277 ZPEX003I, 277 ZPEX004I, 277 ZPEX010E, 278 ZPEX011E, 278 ZPEX012E, 278 ZPEX013I, 279 ZPEX013W, 280 ZPEX014W, 280 ZPEX015I, 281 ZPEX016W, 281 ZPEX017W, 282 ZPEX018W, 283 ZPEX060T, 283 ZPEX061I, 284 ZPEX062I, 284 ZPEX070T, 284 ZPEX071E, 285 ZPEX072W, 285 ZPEX073W, 285 ZPEX074E, 286 ZPEX075W, 286 ZPEX076W, 286 ZPEX077E, 287 ZPEX078E, 287 ZPEX079E, 287 ZPEX080W, 288 ZPEX081E, 288 ZPEX082E, 289 ZPEX083I, 289 ZPEX084E, 289
Index 367
ZPEX090E, 290 ZPEX092C, 290 ZPEX092W, 293 ZPEX093I, 294 ZPEX095I, 295 ZPEX100I, 295 ZPEX101I, 296 ZPEX109I, 296 ZPEX193W, 296 ZPEX200I, 297 ZPEX900T, 297 ZPEX999E, 297 ZPFM - File Manager Messages, 299 ZPFM000I, 299 ZPFM001E, 299 ZPFM011W, 299 ZPFM012W, 300 ZPFM013I, 300 ZPFM014W, 301 ZPFM015W, 301 ZPFM019I, 301 ZPFM030E, 302 ZPFM031T, 302 ZPFM032T, 303 ZPFM033T, 303 ZPFM034T, 303 ZPFM040I, 303 ZPFM041E, 304 ZPFM042E, 304 ZPFM050I, 305 ZPFM051I, 305 ZPFM052I, 305 ZPFM053I, 306 ZPFM054I, 306 ZPFM061I, 307 ZPFM062I, 307 ZPFM063I, 308 ZPFM064I, 308 ZPFM071E, 308 ZPFM072E, 309 ZPFM073E, 309 ZPFM074E, 310 ZPFM075E, 310 ZPFM076E, 310 ZPFM077W, 311 ZPFM078I, 311 ZPFM080E, 312 ZPFM080I, 312 ZPFM081I, 312 ZPFM100T, 313 ZPFM101T, 313 ZPFM102E, 314 ZPFM103E, 314 ZPFM104I, 314 ZPFM111E, 315 ZPFM112I, 315 ZPFM113E, 316 ZPFM121E, 317 ZPFM700I, 317 ZPFM701I, 318 ZPFM702I, 318 ZPFM703I, 318
ZPFM704I, 319 ZPFM705I, 319 ZPFM706I, 319 ZPFM707I, 320 ZPFM708I, 320 ZPFM711I, 320 ZPFM712W, 321 ZPFM713E, 321 ZPFM713I, 322 ZPFM714E, 322 ZPFM900T, 323 ZPFM999E, 323 ZPGE - General Messages, 324 ZPGE001I, 324 ZPGE002I, 325 ZPGE111E, 325 ZPGE112I, 325 ZPGE113E, 326 ZPIDCAMS, 326 ZPIS – ISPF User Interface Messages, 327 ZPIS001I, 327 ZPIS002I, 327 ZPIS003I, 327 ZPLI - License Manager Messages, 329 ZPLI001I, 329 ZPLI200I, 329 ZPLI210I, 329 ZPLI220I, 330 ZPLI230E, 330 ZPLI230I, 330 ZPLI235E, 330 ZPLI235I, 331 ZPLI240E, 331 ZPLI250E, 331 ZPLI299E, 331 ZPLI901E, 332 ZPLI901W, 332 ZPLI902E, 332 ZPLI902W, 334 ZPMT - Main Task Messages, 335 ZPMT002I, 335 ZPMT003E, 335 ZPMT011W, 335 ZPMT020I, 335 ZPMT060T, 336 ZPMT101I, 336 ZPMT901E, 337 ZPMT902E, 340 ZPMT903I, 340 ZPMT904E, 340 ZPMT994E, 341 ZPMT999E, 342 ZPTM - Task Manager Messages, 343 ZPTM001I, 343 ZPTM002I, 343 ZPTM003E, 343 ZPTM993W, 341 ZPTM998E, 344 ZPTM999E, 344 ZPTR - Trace Recording Messages, 345 ZPTR000I, 345
Index 368
