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

PKZIP(R) for z/OS Version 16.0aCopyright 1989-2016 PKWARE, Inc.&nbsp=
; 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.&nb=
sp;Last Updated on April 5, 2016

-------------------------=
---------------------------------------------I. INSTALLATION GUIDE:=
----------------------------------------------------------------------&=
nbsp; This README is intended to provide a quick procedure to inst=
all PKZIP for z/OS version 16.0.

This product i=
s designed to run on the following platforms:

* All rel=
eases of z/OS supported by IBM

To find out what is new i=
n this release, please refer to the $WHATNEW member of the pkware.=
mvs.HELP or the "WHATSNEW.TXT"

------=
---------------------------------------------------------------------V.=
TRANSFERRING THE XMIT DATASET TO THE HOST:----------------------------=
-----------------------------------------------

When tra=
nsferring the INSTALL.XMIT file to the host, it is imperative that&nbsp=
;BINARY mode is used to prevent any kind of translation of the data.<=
br> If any form of translation occurs, your uploaded dataset will be c=
orrupted.

(1) Allocate the INSTALL.XMIT to the installat=
ion HLQ (Example: pkware.mvs.INSTALL.XMIT).=
A suitable allocation is as follows:

--------------------------------------------=
-------------------------------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 Configura=
tion section to do an SMPE_INSTALL setup, and/or an OVERWRITE.=
(1) Before you submit the INSTALL.JCL, you will need to mod=
ify the job card.

(2) You will also need to specify the =
correct INDSN and DSNAME values in the RECVXMIT=
STEP.

a) INDSN is the hi=
gh level qualifier of the XMIT'd data set you &n=
bsp; transferred from the PC to the host. =
b) DSNAME is the DSN that gets cre=
ated by this job. =
It's what you want to call the installed PKZIP product libraries.&nbsp=
; (3) Next, modify the job variables in the RUNINST step.&nbsp=
; For Example:

(4) Submit the job, and review and correct any non-=
zero return codes.

(5) If a NON SMP/E installation is se=
lected, confirm the final RC=3D0 for a successf=
ul completion of all steps and product installation.

(6)=
If an SMP/E installation is selected, confirm the final RC=3D0 for a&n=
bsp; successful completion of all steps and then continue=
on to step VII. SMP/E INSTALLATION. <=
br>------------------------------------------------------------------------=
---VII. SMP/E INSTALLATION:----------------------------------------=
-----------------------------------

The installation and=
software management of PKZIP for z/OS can be accomplished with SM=
P/E. Although the product requires no operating system modif=
ications or authorized routines, the ability to manage the softwar=
e is enhanced using IBM's SMP/E facilities.

The high level qualifier (pkware.=
mvs) you selected to use must be defined in the defaults module us=
ed for the installation of PKZIP for z/OS. This is accomplis=
hed by editing and assembling the sample provided in pkware.mvs.IN=
STLIB(ACZDFLT).

****** There is an SM=
P usermod in &nbsp=
; pkware.mvs.INSTLIB(ACZDFLUM) which can &=
nbsp; take the place of ACZDFLT AND ASM=
DFLT. *******

(1) Verify the fol=
lowing parameters to match your data set name high level &nb=
sp; qualifier for the installation of PKZIP for z/OS:

The above "PARMLIB_DSNAME_ZIP/UNZIP=
" statements may be coded with the value "NULLF=
ILE" if you choose not to use PARMLIB for ZIP a=
nd UNZIP defaults. Doing this will prevent PKZIP from allocating &=
nbsp; the PARMLIB during ZIP and UNZIP jobs.

&nbsp=
;(2) **NOTE** You may modify the other values i=
n this module, or you may add to it. However, t=
his can also be accomplished through the ISPF i=
nterface 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 a=
ssembling.

(3) Save any changes made to the ACZDFLT memb=
er.

(4) Edit the ASMDFLT member of the INSTLIB. You will=
need to use this member to re-assemble the ACZ=
DFLT module you modified in the previous steps.=

(5) Be sure to verify the high level qualifiers and UNI=
Ts before you save and execute this job.&nb=
sp; (6) *** NOTE*** Do not modify anyt=
hing within pkware.mvs.MACLIB(MCZDFLTS).

(7) A PDS (with=
out a member) may be specified to support -INCLUDE_CMD.

You will =
need to contact PKWARE, Inc. Sales at 937.847.2374 and select opti=
on 1, or email sales at pksales@pkware.com to initialize your versi=
on 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 deale=
r in your region.

You will need to provide Sales with a =
license report. To run a license report, please edit and run the L=
ICSHSYS member of the pkware.mvs.INSTLIB.

Please have th=
e output of this report available when speaking with the account r=
ep. You will be expected to supply the following information:

The license keys will be sent =
via email. To apply the key simply follow the step-by-step i=
nstructions contained within the body of the email.

Afte=
r the license key has been successfully applied, you may proceed to&nbs=
p;the next step.

---------------------------------------------=
------------------------------X. ACTIVATING THE ISPF INTERFACE:----=
-----------------------------------------------------------------------=
To configure PKZIP ISPF, you may need to make a few modific=
ations to the pkware.mvs.INSTLIB(PKZSTART) member.

------------------------------------=
---------------------------------------Copyright (c) 1989-2016 PKWARE, =
Inc. All rights reserved.Any reproduction or distribution of this conte=
nt without explicit writtenpermission of PKWARE is prohibited.&nbsp=
;The PKWARE name and logo, PKZIP, and SecureZIP are registered trademar=
ks ofPKWARE, Inc. in the United States and elsewhere. Smartcrypt and Sm=
artkeys aretrademarks of PKWARE, Inc. Use of various PKWARE corporate i=
dentity assets issubject to the Branding Guidelines & Terms of PKWA=
RE, Inc. Trademarks of othercompanies mentioned appear for identificati=
on purposes only and are property oftheir respective companies and are =
hereby acknowledged.

Any reference to licensed programs or oth=
er material belonging to a third partyis not intended to state or imply=
that such programs or material are endorsedby PKWARE, Inc. and/or curr=
ently available for use.-----------------------------------------------=
----------------------------