| |
|
|
|
| |
 |
 |
- Why are there z/OS Web deliverables?
Why are there z/OS Web deliverables? Stated simply, because we want you to be
able to select new non-priced functions for your z/OS or OS/390 releases
(releases for which Web deliverables are offered may or may not be currently
orderable).
Since we can’t offer new features to products that aren’t currently marketed,
we're using the Internet to provide you with these functions
What utilities are used to install a z/OS Web deliverable?
Assuming that you are able to download from the Internet
(through your Internet browser) and upload to your z/OS host (through FTP, for example),
there are only two other utilities that you need to be familiar with:
the z/OS UNIX System Services pax utility and SMP/E.
The z/OS UNIX pax utility can be found on your z/OS host system
in the /bin directory of your version HFS.
The pax utility makes a single archive file from many files, and un-archives
those files in the HFS. You should already be familiar with the SMP/E utility
and the associated z/OS utilities it calls; for example, the program management binder.
Even though you may not know much about UNIX on z/OS, you will receive a
pax sample job with the package. Just remember to submit the job from a
user ID that has an OMVS segment defined. (That is, it is a user ID with OMVS authority.)
There is a fairly new SMP/E function that you'll need to be aware of:
GIMUNZIP. This function simply takes an HFS file and creates
SMP/E RELFILEs. Again, you'll receive a sample to do this, and remember to submit
the job from an OMVS user ID.
The GIMUNZIP function is provided in SMP/E V3R1 (with z/OS V1R2 and later),
and rolled back to SMP/E for OS/390 V2R10 and z/OS V1R1 with PTF UR52471.
If you want to perform hash checking during GIMUNZIP, you must configure ICSF.
Hashing provides additional security and verification for the download file.
You'll find the ICSF configuration requirements in
Appendix C. Helpful Hints for ICSF First Time Startup of the
z/OS Cryptographic Services ICSF System Programmer's Guide
for your z/OS release.
And you'll find GIMUNZIP documentation in the
GIMUNZIP File Extract Service Routine topic in the
SMP/E Reference manual
for your z/OS or SMP/E release.
What's in a z/OS Web deliverable package?
A binary file, containing all the SMP/E RELFILEs, and a ReadMe file
constitute the download package. The ReadMe file contains the instructions and
sample jobs for the package.
In addition, for your convenience, a link to the enhanced HOLDDATA file may be
provided, since it is highly recommended that you receive the latest HOLDDATA during
the installation of a Web Deliverable.
No service is included in the Web deliverables so you'll need to get the service
for the Web deliverable FMIDs using your normal preventive service process.
Service is not included in your Web deliverable because the package is
stabilized once it is made available.
How are z/OS Web deliverables installed?
To install a Web deliverable, do the following:
- Go to the
z/OS downloads Web page and select your download.
There are several pages you need to click through to get to the actual Web
deliverable files.
-
Download the files in the package to your workstation through your
Internet browser and upload it to your z/OS host using FTP, for instance.
(An example is in the ReadMe file.) The ReadMe file contains sample JCL to
process the pax and can be uploaded to a sequential file or to an HFS file.
The pax file contains the actual FMIDs and should be uploaded into an
HFS file.
Hint:
If you use SMB (Server Message Block), you can omit uploading to the host by
downloading to an shared directory. For instance, using SMB,
you can have a directory in your z/OS HFS shared with your workstation as your
M: drive.
Then, when you download, you can save the files on your
M: drive and then reference them directly from your z/OS system.
See the
z/OS Distributed File Service SMB Administration manual
for your release of z/OS for more information about setting up SMB.
Whatever method you use to get the files to your host, make sure that the
target file system is mounted R/W (read/write) on z/OS, and you transfer
the pax file in binary format.
You'll need to write to the file system later.
-
Follow the instructions on the Web site and in the ReadMe JCL.
There are several steps in the sample ReadMe job that:
- Invoke the UNIX pax utility to extract the component archive files into
the same HFS directory. (The HFS files contain the
zipped up RELFILEs you will create in Step b.)
-
Invoke SMP/E to perform GIMUNZIP on the archive files.
This produces SMP/E RELFILEs from the files in the HFS directory.
-
Invoke SMP/E to perform a RECEIVE on the FMID RELFILEs.
-
Obtain service for the Web deliverable from your regular preventive service
deliverable. (No service is provided for the Web deliverable.)
-
Continue the installation, following the program directory available from
the z/OS download Web page.
From this point onward, the FMID installs just as any other FMID does
— with the SMP/E APPLY, ACCEPT that you know and love.
Where can I find the documentation for z/OS Web deliverables?
The program directory is found on the Web deliverable page in
PDF, BookManager book, or browseable format.
The documentation for the enhancement you downloaded can be found at the
product's online library.
Contact z/OS.
Send us your questions and comments.
| |
|
