Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Macro name changed from html to html-bobswift during server to cloud migration processing.

...

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.

...

Step 1

Change #HOSTNAME to the z/OS host name or IP address.

Step 2

Change #USERNAME to a z/OS user ID that has updated access to the XMIT data sets being updated.

Step 3

Change #PASSWORD to the z/OS user ID's password.

Step 4

Change #HLQ to the data set high level qualifier used to allocate the XMIT data sets.

Panel
Html bobswift
<pre>
open #HOSTNAME
user #USERNAME #PASSWORD

ascii
quote site blksize=3120 recfm=fb lrecl=80 pri=1 sec=1 cyl
put UNVRECV-PTF.JCL '#HLQ.UNV.V7R2M1.RECVPTF.JCL'

;Uncomment these lines when transferring from a
;Unix- or Windows-based system.
;put ascii/UNVRECV-PTF.JCL '#HLQ.UNV.V7R2M1.RECVPTF.JCL'

bin
quote site blksize=3120 recfm=fb lrecl=80 pri=1000 sec=100 cyl
del '#HLQ.UNV.V7R2M1.PTFS.XMIT'
put UNV72101.XMT '#HLQ.UNV.V7R2M1.PTFS.XMIT'

quit
</pre>


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.

...

After the data set is successfully unpacked, it is longer required and can be deleted. The files then are ready to be installed.
 

Panel
Html bobswift
<pre>
//UNVRECV  JOB CLASS=A,MSGCLASS=X,MSGLEVEL=(1,1),NOTIFY=&SYSUID,
//             COND=(0,NE),REGION=(0M)
//*********************************************************************
//* (C) COPYRIGHT 2000-2021 STONEBRANCH, INC.  ALL RIGHTS RESERVED.
//*
//* STONEBRANCH, INC.
//* UNIVERSAL PRODUCTS
//*
//* UNVRECV
//*
//* DESCRIPTION
//* -----------
//* PERFORM A TSO RECEIVE ON THE TRANSMITTED DISTRIBUTION DATA SET
//* AND A DFHSMdss RESTORE TO PREPARE FOR INSTALLATION.
//*
//* ALL STEPS MUST END WITH RC 0.
//*
//* MODIFICATIONS
//* -------------
//* 1  MODIFY THE JOB STATEMENT TO MEET LOCAL REQUIREMENTS.
//*
//* 2  CHANGE ALL '#HLQ' TO THE HIGH-LEVEL QUALIFIER OF THE
//*    UNIVERSAL PRODUCTS DATA SETS.
//*
//* 3  CHANGE ALL '#VOLSER' TO THE VOLUME SERIAL NAME ON WHICH TO
//*    ALLOCATE THE DISTRIBUTION DATA SETS.
//*********************************************************************
//*
//DEL00    EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
  DELETE #HLQ.V721.UNV.PTFS
  SET MAXCC=0
/*
//*
//*********************************************************************
//* RECEIVE PTF DISTRIBUTION FILE
//*********************************************************************
//RECV     EXEC PGM=IKJEFT01
//SYSLBC   DD  DISP=SHR,DSN=SYS1.BRODCAST
//SYSPROC  DD  DUMMY
//SYSPRINT DD  SYSOUT=*
//SYSTSPRT DD  SYSOUT=*
//SYSTERM  DD  SYSOUT=*
//SYSTSIN  DD  *
  RECEIVE INDA('#HLQ.UNV.V7R2M1.PTFS.XMIT')
    DA('#HLQ.V721.UNV.PTFS') +
    UNIT(SYSALLDA) VOL(#VOLSER) +
    CYL SPACE(750 100) RELEASE
/*
//*
</pre>

Anchor
Installing a Cumulative PTF File
Installing a Cumulative PTF File
Installing a Cumulative PTF File

...

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.