This step verifies that the upgrade level is valid and available. If you choose to manually download the upgrade packages, this step verifies that all required files are available and ready for the upgrade.

1. Select Minor Step 2, Verify Upgrade Files.
2. Select the method to load upgrade files:
   • Use RECEIVE ORDER to RECEIVE files directly from a BMC server over the internet.
   • Manually download the upgrade packages from the EPD site and make them available in datasets on the mainframe.
3. If you chose to use RECEIVE ORDER, use the S option to submit the Verify job.

   If the specified upgrade level is valid and available, the job will complete OK. Otherwise, the job will fail with an appropriate message.

   After the job completes successfully, press PF3 (END) to return to the Minor Steps Selection panel.

   NOTE: If you have not yet completed the initial configuration for RECEIVE ORDER, first enter C to view and edit the details of certificates/client environment for RECEIVE ORDER. On the Parameter Data Entry screen, set local values for the required/relevant parameters, as discussed in Parameters for RECEIVE ORDER, and then press PF3 (END).

4. If you chose to download the upgrade packages manually, a list of upgrade package files is displayed in the Verify Upgrade Files panel, one file for each required upgrade level, up to the specified target level. There is also an additional line for the EHD file, as explained below.

   Each upgrade level (VV – Version and MMM – maintenance), is represented by a single binary file. In order to minimize the number of files that need to be uploaded, each file that contains an upgrade to a new VV (Version) (that is, maintenance 000), also contains all maintenance levels above the previous VV level (for example, 19.000 would contain version 19.000 and all maintenances above 18.000 up to 19.000).

   Perform the following steps:

   • Ensure that all upgrade package files are in Ready status.

     The following table lists the possible statuses and the action to take in each case. After taking action, press Enter to refresh the panel and display the updated status.

   Status	Action
   Ready	No action necessary. This is the desired status.
   Compressed	Uncompress all Compressed upgrade package files: To submit an Uncompress job for each file, enter the U line command next to the file name. To submit one Uncompress job for all compressed files, enter the UU command next to any file with a Compressed status.
   Missing	No file with the specified name was detected on DASD. Check DASD and perform the appropriate action: Make the file available on DASD, as described in Manually loading the upgrade files. Rename the file to the displayed name (outside of ICE).
   Invalid	The file has incorrect DCB attributes or is an incomplete uncompressed file. Type ? next to the file name to view possible reasons why the file has an Invalid status and how to proceed.

   • BMC strongly recommends using EHD (Enhanced Hold Data file), which is an SMP/E mechanism that assists in identifying PTFs that are in error, and identifying corrective PTFs, if available. To retrieve the current EHD file, go to ftp://ftp.bmc.com/bmc/holddata and download the yrs3.bin file.

     The yrs3.bin file is refreshed frequently. To ensure that you are using the latest version, download the file immediately before you upload it to the mainframe.

     Upload the file to the mainframe using binary transfer and the following dataset attributes:

     • Dataset Name: mlprefa.Evv#mTRS (where vv#m represents the target version and maintenance level)
     • RECFM: FB
     • LRECL: 1024

     After uploading the EHD dataset file, ensure that it is in Ready status.

     NOTE: If you prefer to proceed without EHD support (not recommended), see Proceeding without EHD support.

   • After all files are Ready, press PF3 (END) to return to the Minor Steps Selection panel.