Preparing for installation
Before you begin
Make sure that you have the credentials to access 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.
Also, make sure that you have system programmer credentials as described in Roles and permissions.
To download product installation files
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.
Download the installation files from the EPD website.
Download the following packages and the matching SHA256 text file for each:- BMC AMI Resident Security Server version 2.2.00
- BMC AMI Resident Security Server version 2.2.00 - SPEyymm
SPEs are cumulative, so you must download only the latest SPE. The yymm placeholder represents the year and month of the SPE. - RSS patches released after the latest SPE date
BMC AMI Enterprise Connector for Venafi
version n.n.00BMC AMI Enterprise Connector for Venafi
version n.n.00 - SPEyymm
SPEs are cumulative, so you must download only the latest SPE. The yymm placeholder represents the year and month of the SPE.- Product patches released after the latest SPE date
For the latest information about SPEs and patches, see Notices.
- For each downloaded package, check whether the SHA text file matches the SHA code of the downloaded zip file.
Checking the codes confirms that the files are correct and not corrupted.
To view the SHA code of the zip file, from a Windows command prompt, run the following command from the directory in which the files are downloaded:
certutil -hashfile "<fileName>" SHA256 - For each downloaded package, unzip the zip file to see an XMIT file and the end-user license agreement.
Transmitting and receiving files to the mainframe
You must preallocate data sets to receive the XMIT file from your PC.
You can create one data for each XMIT file, or empty and reuse data sets, but make sure that you install the files in the following order:
- BMC AMI Resident Security Server version 2.2.00
- BMC AMI Resident Security Server version 2.2.00 - SPEyymm (latest SPE)
- RSS patches released after the latest SPE date
BMC AMI Enterprise Connector for Venafi
version n.n.00BMC AMI Enterprise Connector for Venafi
version n.n.00 - SPEyymm (latest SPE)- Product patches released after the latest SPE date
To transmit and receive files to the mainframe
- 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.EC.VENAFI.INSTALL 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
- Use FTP or IND$FILE to transmit the binary XMIT file to the preallocated data set.
You must enter your mainframe user ID and password. - On the mainframe, select ISPF option 6 (ISPF Command Shell) to run the RECEIVE command. Use the XMIT file name as the input file.
Sample FTP session to upload the installation file
In a Windows command prompt, from the directory in which your XMIT file is located, enter the ftp yourLPAR command.
yourLPAR is the LPAR to which you want to upload the 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 installation 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:
>ftp <yourLPAR>Connected to domainName.
220-FTPD1 IBM FTP CS V2R5 at domainName, 13:25:32 on 2022-12-07.
220 Connection will close if idle for more than 30 minutes.User (domainName:(none)): <yourUser>
331 Send password please.Password:230 yourUser is logged on. Working directory is "yourUser.".
ftp> bin200 Representation type is Imageftp> put <localFileName.xmit> '<BMC.product.INSTALL.XMIT>'
200 Port request OK.125 Storing data set BMC.product.INSTALL.XMIT
250 Transfer completed successfully.ftp: 16944400 bytes sent in 16.22Seconds 1044.92Kbytes/sec.ftp> quit221 Quit command received. Goodbye.
Note the following placeholders:
- <yourLPAR> is the LPAR to which you want to upload the 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 XMIT file name on your PC. Enter this name file name.
- <BMC.product.INSTALL.XMIT> is the name of the data set that you created. Enter this data set name.
- BMC.product.INSTALL.XMIT is the name of the data set to which you uploaded your file. This value is automatically added.
Sample IND$FILE command to upload the installation file
If you do not have access to or are prevented from using FTP, you can use the IND$FILE utility instead.
- On the mainframe, select ISPF option 6 (ISPF Command Shell).
- Select to tranfer and upload to the host.
- Enter the localFileName.xmit as the local source file.
This is the unzipped XMIT file name on your PC. Enter '
BMC.EC.VENAFI.INSTALL
' as the remote destination file.
This is the name of the data set that you created.- Select the binary data type and the TSO host.
After you upload the file, it exists in the target z/OS system as BMC.EC.VENAFI.INSTALL. You must run the TSO RECEIVE command for the file as described in the following procedure.
To unload the installation data set
Use the TSO RECEIVE command to unload the XMIT file into an installation data set. The RECEIVE command creates the data set by using the name that you specified in the RECEIVE reply parameter.
In the following example, the RECEIVE command unloads the XMIT file:
receive indsn('hlq.XMIT')
The system responds as followings:
INMR901I Dataset hlq.PACKAGE from userID on NODENAME
INMR906A Enter restore parameters or 'DELETE' or 'END' +
Enter the name of the preallocated installation data set as in the following example:
da('
Unknown macro: confluence_display. Click on this message for details.
')
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.
IEB1135I IEBCOPY FMID HDZ1D10 SERVICE LEVEL UA61306 DATED ... IEB1035I IBMUSER ISPFPROC ISPFPROC 11:15:47 THU 10 APR 2014 ...
COPY INDD=((SYS00009,R)),OUTDD=SYS00007
IEB1013I COPYING FROM PDSU INDD=SYS00009 VOL=ZDSYS1 DSN=SYS14...
IEB1014I TO PDSE OUTDD=SYS00007 VOL=Z13WK5
DSN=
Unknown macro: confluence_display. Click on this message for details.
IEB154I INSTALL HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMRV21 HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMJCLA HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMJCLC HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMJCLE HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMJCLG HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMJCLJ HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMJCLR HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMJCLS HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMVARS HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMWING HAS BEEN SUCCESSFULLY LOADED
IEB154I RSMWIN0 HAS BEEN SUCCESSFULLY LOADED
IEB1098I 12 OF 12 MEMBERS LOADED FROM INPUT DATA SET REFERENCED BY
SYS00025
IEB144I THERE ARE 0 UNUSED TRACKS IN OUTPUT DATA SET REFERENCED BY
SYS00023
IEB149I THERE ARE 5 UNUSED DIRECTORY BLOCKS IN OUTPUT DIRECTORY
IEB147I END OF JOB - 0 WAS HIGHEST SEVERITY CODE
INMR001I Restore successful to dataset '
Unknown macro: confluence_display. Click on this message for details.
'
Where to go from here
To run the installation procedure, see Performing-the-installation.