Upgrading

Uploading and receiving PTFs

The PTF is a binary TSO XMIT data set consisting of 80-byte records in a 3,120-byte fixed-length block.

To transmit and receive PTF files to the mainframe

1. On the mainframe, select ISPF option 3.2 (Data Set Utility) to preallocate a data set to receive the XMIT file from your PC.
   For example, create a data set named BMC.SPM.PTF.XMIT with the following DCB information:
   • Clear the volume serial entry

   • Space units: BLKS

   • Primary quantity: 5000

   • Secondary quantity: 2000

   • Record format: FB

   • Record length: 80

   • Block size: 3120

   • Organization: PS
2. Use FTP or IND$FILE to transmit the binary PTF XMIT file to the preallocated data set.
   See the To upload the PTF file with FTP and To upload the PTF file with the IND$FILE command examples later in this topic.
3. On the mainframe, select ISPF option 6 (ISPF Command Shell) to run the RECEIVE command.
   Use the PTF XMIT file name as the input file. For details, see To unload the PTF into the hlq.PTFLIB data set later in this topic.

To upload the PTF file with FTP

At a Windows command prompt, from the directory in which your PTF XMIT file is located, enter the ftp <yourLPAR> command. <yourLPAR> is the LPAR to which you want to upload the PTF XMIT file. If your LPAR has a domain name, the domain name is displayed.

The following sample is from an FTP session used to upload the PTF file to a system at IP address 192.0.2.0. This session includes the client commands issued at the PC and the server responses:

Note the following placeholders:

• <yourLPAR> is the LPAR to which you want to upload the PTF XMIT file. Enter this LPAR name.
• domainName is the name linked to the IP address. This value is automatically added.
• <yourUser> is the user ID that you use to log in to your LPAR. Enter this user ID.
• yourUser is your user ID. This value is automatically added.
• <localFileName.xmit> is the unzipped PTF XMIT file name on your PC. Enter this name file name.
• <BMC.product.PTF.XMIT> is the name of the preallocated PTF XMIT data set (BMC.SPM.PTF.XMIT) that you created. Enter this data set name.
• BMC.product.PTF.XMIT is the name of the preallocated PTF XMIT data set to which you uploaded your file. This value is automatically added.

To upload the PTF file with the IND$FILE command

If you do not have access to or are prevented from using FTP, you can use the IND$FILE utility instead.

1. On the mainframe, select ISPF option 6 (ISPF Command Shell).
2. Select to tranfer and upload to the host.
3. Enter the localFileName.xmit as the local source file.
   This is the unzipped PTF XMIT file name on your PC.
4. Enter 'BMC.SPM.PTF.XMIT' as the remote destination file.
   This is the name of the preallocated PTF XMIT data set that you created. Make sure that you include the single quotation marks.
5. Select the binary data type and the TSO host.

After you upload the PTF file, it exists in the target z/OS system as BMC.SPM.PTF.XMIT. You must run the TSO RECEIVE command for the file as described in the following procedure.

To unload the PTF into the hlq.PTFLIB data set

1. Use the TSO RECEIVE command to unload the PTF XMIT file into an installation data set.
   In the following example, the RECEIVE command unloads the BMC.SPM.PTF.XMIT file into the hlq.PTFLIB:
   receive indsn('BMC.SPM.PTF.XMIT')
   The system responds as follows:

   INMR901I Dataset hlq.PTFLIB from userID on NODENAME
INMR902I Members: ptfName
INMR154I The incoming data set is a 'DATA LIBRARY'.
INMR906A Enter restore parameters or 'DELETE' or 'END' + 


2. Enter the name of the preallocated installation data set as in the following example:
   da('hlq.PTFLIB')
   The following code block displays some of the output messages issued during the RECEIVE process. After you enter this command, the system unloads the members into the named data set, issuing a confirmation message for each one.

                                             IEBCOPY MESSAGES AND CONTROL STATEMENTS                              PAGE     1
IEB1135I IEBCOPY  FMID HDZ2240  SERVICE LEVEL UJ05519  DATED 20210505 DFSMS 02.04.00 z/OS    02.04.00 HBB77C0  CPU 3931 
IEB1035I userID    $STD     $STD     05:51:51 WED 01 FEB 2023 PARM=''
 COPY INDD=((SYS00053,R)),OUTDD=SYS00051
IEB1013I COPYING FROM PDSU  INDD=SYS00053 VOL=RSMP02 DSN=SYS23032.T055151.RA000.R0112021
IEB1014I           TO PDS  OUTDD=SYS00051 VOL=RSMP02 DSN=hlq.PTFLIB
IEB167I FOLLOWING MEMBER(S) LOADED FROM INPUT DATA SET REFERENCED BY SYS00053
IEB154I ptfName  HAS BEEN SUCCESSFULLY LOADED
IEB1098I 1 OF 1 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY SYS00053
IEB144I THERE ARE 35 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY SYS00051
IEB149I THERE ARE 48 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE
INMR001I Restore successful to dataset 'hlq.PTFLIB'
***                                                                                                                    


To run the PTF procedure

In the installation data set, hlq.INSTALL (which was built during the product installation process), is the APPLYPTF REXX procedure. Use this procedure to build the job control that applies the service to your product.

1. In the hlq.INSTALL data set member list, locate the APPLYPTF procedure and enter the EX command.

   Tip

   You can also issue the following command from ISPF option 6:

   ex <hlq>.INSTALL(APPLYPTF)

2. In the procedure's panel, enter the PTF name (<ptfName>) and jobcard name (<jobcardName), such as in the following example:

   ---------------------------- <product> PTF Installation ----------------------------
   Command ===> _________________________________________________________________
   
   PTFs to be installed : <ptfName>
   
   
   Jobcard:
   //<jobcardName>
   
   Press Enter to generate PTF JCL.
   Press PF3 to terminate

3. Press Enter.
   The procedure builds the JCL and opens an edit session so that you can make any installation-specific changes before submitting the job.
4. Submit the job.
   A successful job completes with a return code of 0.
   
5. Perform a cold start on the product or products to bring the updated service into production.