How do I download and install BMC AMI DevX (formerly Compuware) products? |
Per BMC Technical bulletin (ID 291721), "Maintenance for BMC Compuware products will be available only through the RECEIVE ORDER process after 31 December 2023". Customers who are unfamiliar with the SMP/E RECEIVE ORDER process are advised to review the following documentation:
Visit the BMC Electronic Product Distribution (EPD) page and place a product order using the "BMC AMI DevX" tab. For details on navigating the EPD ordering website, watch this video. EPD order shipment email When your EPD order has been processed you will receive an email with login credentials for https://epddownload.bmc.com. If you are unable to download EPD shipments directly to your z/OS mainframe, you can download files to your PC using your web browser. Your EPD order email should include one of the following JCL file attachments:
Customers who cannot use their z/OS system for FTP or HTTPS connections can login to https://epddownload.bmc.com using the credentials from their EPD shipment email and download the .TAR file for use with the SMP/E RECEIVE FROMNTS command using the following instructions:
Most Compuware products are installed using the BMC Installer. The BMC Installer creates an INSTLIB PDS dataset with JCL members for SMP/E installation (RECEIVE, APPLY, ACCEPT) and cumulative maintenance via RFN. ThruPut Manager is installed using the TM/Quikload method. Customers who cannot download ThruPut Manager full product files using FTP should read: The BMC Installer can be downloaded using a z/OS FTP client connection via the sample JCL in the CISAMP.txt attachment of your EPD shipment email. The default JCL includes -er TLS in the PARM of the FTPS step EXEC statement and a SYSFTPD DD allocation with FTP.DATA settings for a TLS authenticated connection which uses passive port range 30000-32000 for the protected data connection. Removing -er TLS and the SYSFTPD DD from the JCL will cause the z/OS FTP client to use the local default FTP.DATA settings for the connection. Customers who cannot use the z/OS FTP client connection can use their web browser and https://epddownload.bmc.com/download/cpwr.ins to download the BMC Installer to their PC. From there cpwr.ins should be uploaded to the z/OS server in BINARY mode to a pre-allocated dataset: hlq.CPWR.INS.XMIT with: RECFM=FB LRECL=80 BLOCKSIZE=3120 which is received to the hlq.CPWR.INS PDS dataset using the following JCL: //RECEIVE EXEC PGM=IKJEFT01,DYNAMNBR=20 //SYSPRINT DD SYSOUT=* //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * RECEIVE INDSN('hlq.CPWR.INS.XMIT') NODISPLAY DATASET('hlq.CPWR.INS') /* Downloading BMC AMI DevX (Compuware) Cumulative Maintenance using HTTPS The BMC Installer (cpwr.ins) downloaded from epddownload.bmc.com uses the CPWR.INS($$CWINST) dialog to create JCL members in INSTLIB which use the following default: <CLIENT javahome="/usr/lpp/java/J8.0_64" downloadmethod="https" downloadkeyring="javatruststore"> </CLIENT> NOTE: Existing INSTLIB's which reference ftp.compuware.com must be updated to use epddownload.bmc.com using the <SERVER> settings in the EPD shipment email attachment: smpe_receive.txt. A <CLIENT> with downloadmethod="https" causes SMP/E to open a shell to invoke the SMP/E Java client (GIMJVCLT) to connect to the <SERVER> using port 443 for the <PACKAGE> download from epddownload.bmc.com. Configuring the RACF keyring or Java keystore SSL/TLS authenticated connections to epddownload.bmc.com require the following certificates: If the DigiCert Global Root certificates are not in the javatruststore, try changing to downloadkeyring="*AUTH*/*". Customers unfamiliar with updating the java keystore are advised to review IBM Keytool documentation (IBM SDK, Java Technology Edition, version 8). For details on setting up a RACF keyring, see the Secure File Transfer User Guide for BMC Customers and also the IBM z/OS SMP/E User's Guide; Chapter 4. Preparing to use Internet service retrieval. Diagnosing SMP/E Java Client Problems The SMP/E Java client (GIMJVCLT) requires that the user's OMVS segment has access to any Unix System Services (via BPX) required to complete the SMP/E processing. If a RACF authorization problem occurs, the job output may display an ICH408I message (or similar messages for ACF2 or Top Secret). If the Java client is having problems connecting or completing a certificate handshake, add the following javadebugoptions to the <CLIENT> settings to obtain a detailed trace: -showversion - provides details about java version. -Dcom.ibm.smp.debug=finest - provide trace details for SMP/E java classes. -Djavax.net.debug=SSL,handshake - diagnose SSL connection. -Djava.security.debug=certpath - diagnose PKIX certificate path issues. Use the following <CLIENT> when a proxy server is involved in the connection: <CLIENT javahome="/usr/lpp/java/J8.0_64" downloadmethod="https" downloadkeyring="javatruststore"> <HTTPPROXY host="company.proxy.server" port="8080"> </HTTPPROXY> </CLIENT> Downloading BMC AMI DevX (Compuware) Cumulative Maintenance using FTP Removing the downloadmethod keyword from the <CLIENT> or removing the CLIENT parm from the SMP/E RECEIVE command causes SMP/E to default to FTP for <CLIENT> connections to the <SERVER> to download the <PACKAGE>. See INSTLIB($04RECV) for an example RECEIVE job. Use the following <CLIENT> if you need to download using FTP with a specific FTP.DATA dataset: <CLIENT downloadmethod="ftp"> <FTPOPTIONS>-d -v -f "//'hlq.FTP.DATA'"</FTPOPTIONS> </CLIENT> The following is required for TLS-authenticated z/OS FTP client connections to epddownload.bmc.com
DEBUG ALL
SECURE_MECHANISM TLS TLSMECHANISM FTP SECURE_DATACONN PRIVATE EPSV4 TRUE KEYRING *AUTH*/* PASSIVEIGNOREADDR TRUE If a the z/OS FTP connection requires a SOCKS proxy the FTP.DATA (SYSFTPD DD) parms must include the SOCKSCONFIGFILE statement where that file contains SOCKD statements for the epddownload.bmc.com IP addresses found on the File server and certificate information page. |