Page Comparison

...

Step 1	Download one of the Universal Agent 7.02.x for z/OS cumulative PTF maintenance distribution files. Cumulative PTFs are packaged as a compressed tarball (`sb-v.r.m.l-zos-PTFs.tar.Z`) or as a ZIP file (`sb-v.r.m.l-zos-PTFs.zip`).
Step 2a	If the distribution files with the `.tar.Z` extension was downloaded, decompress it using any utility that can process files in Lempel-Ziv (that is, compress) format. Use tar to extract the files from the uncompressed file. To do both in a single statement, decompress the file to stdout and pipe the result to tar (for example, `zcat sb-v.r.m.l-zos-PTFs.tar.Z \| tar xvf -)`.
Step 2b	If the distribution file with the `.zip` extension was downloaded, decompress it using any utility that can process files in ZIP (or, PKZIP) format. The `.zip` file can also be extracted using Windows native file extraction tools.
Step 3	Modify the `UNVFTP-PTF.TXT` script provided by the distribution file to upload the PTF files and the JCL (which resides in `UNVRECV-PTF.JCL`) to process them. Two versions of these files are included in the distribution file. The files in the main directory are EBCDIC-encoded files. ASCII-encoded versions of these files are in the `./ascii subdirectory`. Look for the #HOSTNAME, #USERID, #PSWD, and #HLQ placeholders in `UNVFTP-PTF.TXT` and set them to the appropriate values.
Step 4	Modify the JCL uploaded from `UNVRECV-PTF.JCL` and run the job to receive the cumulative PTF XMIT file.

...

sb-Version.Release.Modification Level.Maintenance Level-operating system-PTFs.zip

For example: sb-7.02.0.1-zos-PTFs.zip.

To unzip the file, use a third-party ZIP-based extraction application or the native Windows file extraction tool available from Windows Explorer.

...

This file can be decompressed using any utility that can process files in Lempel-Ziv (that is, compress) format. The decompressed file's contents can be extracted using tar.

For example:

zcat sb-67.52.10.1-zos.PTFs.tar.Z | tar xvf -

This decompresses and extracts the 67.52.10.1 Universal Agent for z/OS distribution file that contains the cumulative PTF file on a UNIX-based system.

...

This file (for example, sb-67.52.10.1-zos-PTFs.zip) can be decompressed using any utility that can process files in ZIP (or, PKZIP) format.

...

After uploading, review the comments contained in '#HLQ.UNV.V6R4M2V7R2M1.RECVPTF.JCL' and make the necessary changes. Submit the job to receive and restore the install file.

...

After transferring the cumulative PTF file to z/OS, you must unpack it using the JCL uploaded from UNVRECV-PTF.JCL (which should now reside in #HLQ.UNV.V6R4M2V7R2M1.RECVPTF.JCL).

The sample JCL to receive and restore the cumulative PTF file, below, shows the statements contained in UNVRECV-PTF.JCL. The job performs a TSO RECEIVE on the UNV6511.XMT file uploaded by UNVFTP-PTF.TXT.

...

Step 1	Member UNVMTRCV performs an SMP/E RECEIVE of the PTFs. Change the data set allocated on ddname SMPPTFIN to the PTF data set. Modify the JCL to meet local requirements, and submit the job.
Step 2	Member UNVMTAPL performs an SMP/E APPLY of the PTFs. Modify the JCL to meet local requirements, and submit the job. The job should end with condition code 0. If the job does not end with condition code 0, it is most likely due to a HOLD on one of the PTFs. This is indicated by message GIM30206E printed on ddname SMPOUT. In this case, see #PTF PTF HOLDs, above.
Step 3	Fully test the maintenance. Only after all testing is completed should you proceed to the next step.
Step 4	Member UNVMTACC performs an SMP/E ACCEPT of the PTFs. Modify the JCL to meet local requirements, then submit the job. The job should end with condition code 0 or 4. If it does not, it is most likely due to a HOLD on one of the PTFs. This is indicated by message GIM30206E printed on ddname SMPOUT. In this case, see #PTF PTF HOLDs, above.

Versions Compared

Old Version 1

New Version 2

Key