Installers for z/OS

Technical_Advisory-OMVS_Segment_Messages_in_PKZIP_and_PK_Encrypt_v17.0_for_zOS

Contact your PKWARE Customer Development Manager for evaluation copies of PK Encrypt for z  part of the PK Protect family or email pkcs@pkware.com

Installation instructions are included in the self extracting EXE that contains the install files as Readme.txt

PKZIP(R) for z/OS Version 16.0a
Copyright 1989-2016 PKWARE, Inc.  All rights reserved.
PKZIP(R) is a registered trademark of PKWARE(R), Inc.
SecureZIP(R) is a registered trademark of PKWARE(R), Inc.
 
Change Font to Arial size 10 for best printing of this document.
 
Last Updated on April 5, 2016
 
----------------------------------------------------------------------
I. INSTALLATION GUIDE:
----------------------------------------------------------------------
 
 This README is intended to provide a quick procedure to install
 PKZIP for z/OS version 16.0.
 
 This product is designed to run on the following platforms:
 

• All releases of z/OS supported by IBM

 
 To find out what is new in this release, please refer to the
 $WHATNEW member of the pkware.mvs.HELP or the "WHATSNEW.TXT"
 
---------------------------------------------------------------------------
II. BEFORE THE INSTALLATION:
---------------------------------------------------------------------------
 
 The installation of PKZIP is comprised of 9 steps:
 

1. Downloading the product file from the PKWARE, Inc. website, or copy

     the self-extracting file from the cd media.

2. Double-clicking the file to extract the installation files on your PC

     (See section III. FILES INCLUDED IN SELF-EXTRACTING ZIP FILE).

3. Transferring the INSTALL.JCL to the Host z/OS system

     (See section IV. TRANSFERRING THE INSTALL JCL TO THE HOST).

4. Transferring the INSTALL.XMIT dataset from your PC to the host

     OS/390 or z/OS system (See section V. TRANSFERRING THE XMIT
     DATASET TO THE HOST).

5. Running the INSTALL.JCL job which also provides the optional configuration

     for an SMP/E install and OVERWRITE option.
     (See section VI. RUNNING THE INSTALL.JCL).

6. OPTIONAL- Editing the INSTALL.JCL to select the SMP/E installation JCL

     (See section VII. SMP/E INSTALLATION).

7. Tailoring the installation by modifying the defaults module:(ACZDFLT)

     (See section VIII. TAILORING YOUR PROD_U INSTALLATION).

8. Running License Report and calling PKWARE to obtain the product key

     (See section IX. INITIALIZING PROD_U FOR z/OS FOR A TRIAL).

9. Installing the ISPF panels and libraries (See section X. ACTIVATING

     THE ISPF INTERFACE).
 
---------------------------------------------------------------------------
III. FILES INCLUDED IN SELF-EXTRACTING ZIP FILE
---------------------------------------------------------------------------
 
 -------------------------------------------------------------------
 DOCUMENTATION IS DISTRIBUTED IN ADOBE(R) ACROBAT(R) (*.PDF) FORMAT.
 -------------------------------------------------------------------
 
 The PKZIP-SecureZIP for zOS v16.0 portfolio.pdf includes the following:
   PKZIP-SecureZIP for zOS v16.0 Users Guide
   PKZIP-SecureZIP for zOS v16.0 Messages Guide
   PKZIP-SecureZIP for zOS v16.0 System Administrators Guide
   PKZIP-SecureZIP for zOS v16.0 Application Integration Guide
 
 The portfolio provides the ability to search one or all manuals.
 If separate manuals are preferred, please contact Technical Support
 at 937.847.2687.
 
 -------------------------------------------------------------------
 TEXT FILES
 -------------------------------------------------------------------
 
 LICENSE.TXT         - PKWARE's software license agreement
 GLOBAL CONTACTS.TXT - How to contact Domestic and international
                       resellers
 README.TXT          - This file you are reading
 INSTALL.JCL         - Receive the Transmitted XMIT file. Default to
                       a NON SMP/E or alternatively specify an SMP/E
                       install with optional OVERWRITE to perform a
                       DELETE during TSO RECEIVE
 WHATSNEW.TXT        - A text file documenting product changes
 
 -------------------------------------------------------------------
 BINARY FILES
 -------------------------------------------------------------------
 
 INSTALL.XMIT        - A binary XMIT containing the following library
                       files to be RECEIVED:
 

• CEXEC    (Compiled REXX Library)

• HELP     (Message Library)

• INSTLIB  (Installation Library - FB)

• INSTLIB2 (Installation Library - VB)

• LOAD     (Load Library)

• MACLIB   (Macro Library)

• SPKZCLIB (REXX Library)

• SPKZMLIB (Message Library)

• SPKZPLIB (Panel Library)

• SPKZSLIB (Skeleton Library)

• SPKZTLIB (Table Library)

• MCS      (SMP/E Only)

 
---------------------------------------------------------------------------
IV.  TRANSFERRING THE INSTALL.JCL TO THE HOST:
---------------------------------------------------------------------------
 
 (1) Transfer the text file "INSTALL.JCL" to the host. You may
     transfer the file into an existing PDS or you may use the
     allocation in step "2" below.
 

• Convert the data from ASCII to EBCDIC

• Insert CR/LFs

 
 (2) A suitable allocation for "INSTALL.JCL" is as follows:
 
     SPACE UNITS: BLKS
     BLKS:        5 (PRI)
                  1 (SEC)
     DIRBLKS:     0
     RECFM:       FB
     LRECL:       80
     BLKSIZE:     3120
     DSORG:       PS
 
---------------------------------------------------------------------------
V. TRANSFERRING THE XMIT DATASET TO THE HOST:
---------------------------------------------------------------------------
 
 When transferring the INSTALL.XMIT file to the host, it is imperative that
 BINARY mode is used to prevent any kind of translation of the  data.
 If any form of translation occurs, your uploaded dataset will be corrupted.
 
 (1) Allocate the INSTALL.XMIT to the installation HLQ
     (Example: pkware.mvs.INSTALL.XMIT).
     A suitable allocation is as follows:
 
     SPACE UNITS: CYLS
     BLKS:        100 (PRI)
                  10  (SEC)
     DIRBLKS:     0
     RECFM:       FB
     LRECL:       80
     BLKSIZE:     3120
     DSORG:       PS
 
 (2) Transfer the distribution dataset INSTALL.XMIT from your PC
     into the target data set.
 

• Do not translate the data

• Do not insert CR/LFs

 
---------------------------------------------------------------------------
VI.  RUNNING THE INSTALL.JCL:
---------------------------------------------------------------------------
 
 The INSTALL.JCL will perform either a NON SMP/E or SMP/E install.
 There is a built-in user switch in the Optional Configuration section
 to do an SMPE_INSTALL setup, and/or an OVERWRITE.
 
 (1) Before you submit the INSTALL.JCL, you will need to modify the job card.
 
 (2) You will also need to specify the correct INDSN and DSNAME values in
     the RECVXMIT STEP.
 
       a) INDSN is the high level qualifier of the XMIT'd data set you
          transferred from the PC to the host.
 
       b) DSNAME is the DSN that gets created by this job.
          It's what you want to call the installed PKZIP product libraries.
 
 (3) Next, modify the job variables in the RUNINST step.
 
     For Example:
 
       PHLQ = 'pkware.mvs'
       PUNT = 'sysda'
       PVOL = 'volume'
 
 (4) Submit the job, and review and correct any non-zero return codes.
 
 (5) If a NON SMP/E installation is selected, confirm the final RC=0 for a
     successful completion of all steps and product installation.
 
 (6) If an SMP/E installation is selected, confirm the final RC=0 for a
     successful completion of all steps and then continue on to step
     VII. SMP/E INSTALLATION.
 
---------------------------------------------------------------------------
VII. SMP/E INSTALLATION:
---------------------------------------------------------------------------
 
 The installation and software management of PKZIP for z/OS can be
 accomplished with SMP/E.  Although the product requires no operating
 system modifications or authorized routines, the ability to manage the
 software is enhanced using IBM's SMP/E facilities.
 
 (1) OPTIONAL: To delete existing PKZIP data sets, add a job card,
  modify and run the pkware.mvs.INSTALL.OUT($SMPCLN)
 
 (2) To complete the SMP/E installation, add a job card, modify and run the
  pkware.mvs.INSTALL.OUT($SMPINST)
 
  The following steps will be performed:
 
    S01DFCSI - Define SMP CSI
    S02ALLOC - Define PKZIP data sets
    S03UCLIN - Update SMP configuration via UCLIN
    S04RECV  - SMP Receive PKZIP
    S05APPLY - SMP Apply PKZIP
    S06ACCPT - SMP Accept PKZIP
    S07UPDAT - Update INSTLIB Sample members
 
---------------------------------------------------------------------------
VIII. TAILORING YOUR PKZIP INSTALLATION:
---------------------------------------------------------------------------
 
 The high level qualifier (pkware.mvs) you selected to use must be
 defined in the defaults module used for the installation of PKZIP for
 z/OS.  This is accomplished by editing and assembling the sample provided
 in pkware.mvs.INSTLIB(ACZDFLT).
 
  ******    There is an SMP usermod in
            pkware.mvs.INSTLIB(ACZDFLUM) which can
            take the place of ACZDFLT AND ASMDFLT.     *******
 
 (1) Verify the following parameters to match your data set name high level
     qualifier for the installation of PKZIP for z/OS:
 
     MCZDFLTS TYPE=CSECT,                                         *
          LICENSE_HLQ=pkware.mvs,                                 *
          PARMLIB_DSNAME_ZIP=pkware.mvs.INSTLIB,        NOTE2     *
          PARMLIB_DSNAME_UNZIP=pkware.mvs.INSTLIB,      NOTE2     *
 
     The above "PARMLIB_DSNAME_ZIP/UNZIP" statements may be coded with
     the value "NULLFILE" if you choose not to use PARMLIB for ZIP
     and UNZIP defaults. Doing this will prevent PKZIP from allocating
     the PARMLIB during ZIP and UNZIP jobs.
 
 (2) **NOTE**
     You may modify the other values in this module, or you may add
     to it. However, this can also be accomplished through the
     ISPF interface and selecting ZD or UD to further tailor the
     defaults. At minimum, the above three lines need to be modified,
     saved, and assembled in batch - see step (4) for assembling.
 
 (3) Save any changes made to the ACZDFLT member.
 
 (4) Edit the ASMDFLT member of the INSTLIB. You will need to
     use this member to re-assemble the ACZDFLT module you modified
     in the previous steps.
 
 (5) Be sure to verify the high level qualifiers and UNITs before you
     save and execute this job.
 
 (6) *** NOTE***
     Do not modify anything within pkware.mvs.MACLIB(MCZDFLTS).
 
 (7) A PDS (without a member) may be specified to support -INCLUDE_CMD.
 
---------------------------------------------------------------------------
IX. INITIALIZING PKZIP for z/OS FOR A TRIAL:
---------------------------------------------------------------------------
 
 You will need to contact PKWARE, Inc. Sales at 937.847.2374 and select
 option 1, or email sales at pksales@pkware.com to initialize your version
 of PKZIP for z/OS for the trial. If you do not work in the USA, please
 refer to the "Global Contacts.txt" file to contact a dealer in your region.
 
 You will need to provide Sales with a license report. To run a license
 report, please edit and run the LICSHSYS member of the pkware.mvs.INSTLIB.
 
 Please have the output of this report available when speaking with the
 account rep. You will be expected to supply the following information:
 

• Company Name

• Company Contact

• Phone number

• Contact Email

 
 The license keys will be sent via email.  To apply the key simply follow
 the step-by-step instructions contained within the body of the email.
 
 After the license key has been successfully applied, you may proceed to
 the next step.
 
---------------------------------------------------------------------------
X. ACTIVATING THE ISPF INTERFACE:
---------------------------------------------------------------------------
 
 To configure PKZIP ISPF, you may need to make a few modifications
 to the pkware.mvs.INSTLIB(PKZSTART) member.
 
 (1) Verify the following REXX environment variables:
 
   env     = 'CEXEC'
   ispfhlq = 'pkware.mvs'
   llib    = 'pkware.mvs.LOAD'
 
   a) If your environment doesn't support compiled REXX, change the value
      of 'env' to 'EXEC'. This defaults to 'CEXEC'
 
   b) Change the value of 'ispfhlq' to reflect the high level qualifier
      for the ISPF data sets. This defaults to 'pkware.mvs'
 
   c) Change the value of 'llib' to indicate the name of the installed
      load library. The default is 'pkware.mvs.LOAD'
 
 (2) Now save your changes to the PKZSTART member.
 
 (3) To test whether your configuration has worked, simply type "EXEC"
     next to the PKZSTART member, or on the "Option" line enter
     TSO EXEC 'pkware.mvs.INSTLIB(PKZSTART)'.
 
---------------------------------------------------------------------------
GETTING HELP WITH YOUR INSTALLATION OR AUTHORIZATION CODE:
---------------------------------------------------------------------------
 
 If you have questions concerning licensing or general account matters,
 please contact Customer Service at 937.847.2374 and select option 3, then 2
 or email Customer Service at pkcs@pkware.com.
 
 For Technical Support assistance, please contact the Product
 Services Division at 937.847.2687, or visit the support web site at
 http://www.pkware.com/support/zos .
 
 The "Contact Information" section in the User's Guide lists the types of
 information needed to resolve issues with the product.
 
 Thank you.
 
 Product Services Division
 http://www.pkware.com/support
 
 PKWARE,Inc.                  Tel: +1 937.847.2374
 201 E. Pittsburgh Ave.       WWW: http://www.pkware.com
 Suite 400
 Milwaukee, WI 53204
 USA
 
---------------------------------------------------------------------------
Copyright (c) 1989-2016 PKWARE, Inc. All rights reserved.
Any reproduction or distribution of this content without explicit written
permission of PKWARE is prohibited.
 
The PKWARE name and logo, PKZIP, and SecureZIP are registered trademarks of
PKWARE, Inc. in the United States and elsewhere. Smartcrypt and Smartkeys are
trademarks of PKWARE, Inc. Use of various PKWARE corporate identity assets is
subject to the Branding Guidelines & Terms of PKWARE, Inc. Trademarks of other
companies mentioned appear for identification purposes only and are property of
their respective companies and are hereby acknowledged.
 
Any reference to licensed programs or other material belonging to a third party
is not intended to state or imply that such programs or material are endorsed
by PKWARE, Inc. and/or currently available for use.