Preparing for installation

Perform the following tasks before you run the product installation.

To prepare an installation data set on the z/OS system

The product runs on any supported version of z/OS and z/OS compatible hardware.

Use ISPF option 3.2 (Data Set Utility) to preallocate the product installation data set with the following attributes to receive the installation objects. The data set has enough space to avoid issues later if you need to apply SMP/E maintenance to the product.

To prepare the PC for product use

The product is supplied as a binary offload of a TSO XMIT file and requires a PC capable of using FTP to transfer the installation file to the target z/OS system. If you cannot use FTP, you can perform the upload by using IND$FILE instead.

The RSS browser interface requires Internet Explorer (IE) version 8 or later, any Mozilla-based browser such as Firefox, Chrome, Opera, or Safari, with JavaScript enabled.

To upload the product binary

Save the installation package to your networked PC and upload it to your target z/OS system. The installation package is a binary offload of a z/OS TSO XMIT file.

1. Download the installation files from the BMC Electronic Product Distribution (EPD) website. Your access to product pages on the EPD website depends on the license entitlements purchased by your company.

2. Use FTP (or IND$FILE if you do not have access to FTP) to upload the installation package file to the data set created in the "To prepare an installation data set on the z/OS system" section.

Sample FTP session to upload the installation file

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

The LITERAL SITE (some FTP clients use QUOTE rather than LITERAL) command ensures that the data set has the correct characteristics when it is written to the target system.

If you do not have access to or are prevented from using FTP, you can use the IND$FILE utility instead. The following code shows the general command format:
IND$FILE PUT dataSetName RECFM(FB) LRECL(80) BLKSIZE(3120)

dataSetName represents the name of the product XMIT file. This statement must not have ASCII or CRLF appended. If you experience any issues uploading the file, preallocate the data set using the attributes given above. These will override the RECFM, LRECL, and BLKSIZE specified on the IND$FILE PUT statement.

After you upload the product binary, it exists on the target z/OS system as profilePrefix.companyAbbreviation.XMIT. This file needs to be TSO RECEIVED.

To unload the installation data set

The next step is to use a TSO RECEIVE command to unload the binary XMIT install file into the installation data set we have created for the purpose. Use the command shell session (option 6 from the ISPF menu) to issue the RECEIVE command.

Here is an example:
receive indsn('ibmuser.rss.xmit')

The system responds with something similar to the following sample:

Respond to this with the name of the pre-allocated installation data set previously allocated like this:
da('rss.v210.install')
)

Here are some of the output messages issued during the RECEIVE process. When you press Enter on this command, the system unloads the RSS members into the named data set issuing a confirmation message for each one.

If you remain in your TSO command session, you can run the INSTALL procedure next to create the SMP/E installation of the product.

Where to go from here

To run the installation procedure, see Running-the-INSTALL-procedure.