Phase 1: Install the BMC ThruPut Manager software

Download ECC from BMC Support website and configure the CMSC and LMS in your environment.

BMC ThruPut Managerperforms licensing authentication at two points in processing. The first is when the TM STC is initializing and the second is a daily check performed at 12:00 p.m. When the check is performed, TM attempts to communicate with the LMS task. If it is not successful, it will retry every 30 minutes for 24 hours. Once that time expires, the TM STC will be shut down with appropriate messages.

Install BMC ThruPut Manager

Step 1A and 1B are mutually exclusive.

Step 1A is directed at first time installation of BMC ThruPut Manager, new version installations, as well as those wishing to completely replace their BMC ThruPut Manager environment with a new maintenance level.

Step 1B describes an incremental SMP/E upgrade.

We recommend the first alternative whenever possible.

1A. Use QUIKLOAD Technique

Step 1B is an alternative to Step1A. Complete one or the other.

The installation of BMC ThruPut Manager can be accomplished using the QUIKLOAD technique. The installation materials contain an SMP/E environment with BMC Support defined options.

Steps 1A.1 through 1A.6 must be executed in their entirety for the process to function correctly. This method:

• Unloads the complete SMP/E installed BMC ThruPut Manager edition, current accumulative maintenance (PTFs in ACCEPT’d status), and APARs (not ACCEPT’d).
• Provides the corresponding self-contained SMP/E environment needed for future maintenance.
• Can remain a standalone environment or be merged into an existing SMP/E environment.

1A.1. Restore the BMC ThruPut Manager Datasets

Restore the installation files using the JCL link and password provided on the Electronic Delivery page received via the email response to your order.

This job unloads the  DTMINST data set, the BMC ThruPut Manager libraries and the respective SMP/E environment needed to maintain BMC ThruPut Manager.

The DTMINST data set may contain updated information and should be used in place of any existing installation materials.

The following chart lists the data sets and 3390 DASD space recommendations required for installation. Adjust these accordingly for different DASD device types. These estimates include additional space for SMP/E maintenance.

1A.2. Modify the BMC ThruPut Manager SMP/E JCL PROC

DTMINST(TMSMPE) contains the SMP/E PROC needed to run the SMP/E steps referenced by some of the installation JCL via the JCLLIB statement. This PROC should be tailored to meet your installation requirements and assumes the target and distribution libraries are defined by DDDEF.

1A.3. Restore SMP/E Environment

Run DTMINST(I$FSMPE) to build and load the SMP/E environment. JCL is provided, in a step 1A.6, to change internal SMP/E options and incorporate the SMP/E environment into an existing environment if necessary.

1A.4. Alter SMP/E Definitions/Settings

Run DTMINST(I$ZONE) to alter the zone settings and DDDEF data set names in your new environment. Make sure the DDDEFs refer to the BMC ThruPut Manager libraries allocated during the installation process. Return Code 04 is expected.

The VERIFY step lists the PTFs and APARs shipped with the downloaded environment. This list can be compared with the output of the BMC ThruPut Manager command TM D LEVEL to validate the resulting SMP/E environment against the product environment.

The final optional step is sample JCL to allow installations to alter target or distribution zone settings.

1A.5. Reassemble/Link BMC ThruPut Manager Source Stubs

Run DTMINST(I$JESLNK) to assemble and link the BMC ThruPut Manager source stubs with the targeted level of JES2 macros. This step provides accurate JES2 addressing. Make sure the job’s system and JES2 libraries are pointing to the system level for which BMC ThruPut Manager is targeted.

A dummy usermod for BMC ThruPut Manager has been provided to manage the synchronization of the BMC ThruPut Manager source stubs. TTM8120 triggers a warning message or re-assembly of BMC ThruPut Manager JES2 source stubs DTMJ2MV8 and DTMJ2SV8 when required (See Synchronize JES2 and BMC ThruPut Manager for details).

1A.6. Merge SMP/E Environment (optional)

Run DTMINST(I$ZNEIMP) to merge the newly created SMP/E information with an existing BMC ThruPut Manager SMP/E environment. This job does the following:

• Creates transportable copy of newly installed BMC ThruPut Manager zones
• Defines new zoneset in existing GLOBAL environment
• Imports copies into new zoneset in existing environment
• Merges new BMC ThruPut Manager GLOBAL information into existing GLOBAL

Make sure unique TARGETZONE and DZONE names are selected. This ensures any existing BMC ThruPut Manager Target and DLIB zones are not replaced, thereby serving as backups. Also, verify the DDDEFs point to the correct level of data sets. (This should have been done in a previous tailoring step and the information carried with the zone).

This completes the QUIKLOAD process.

Proceed to Phase 2: Configure BMC ThruPut Manager if you are:

• Installing the product for the first time.
• Installing (an edition of) the product on a system for the first time.
• installing a new version of the product for the first time

Proceed to Phase 3: Review BMC ThruPut Manager interfaces if you are:

• Upgrading to a new maintenance level.
  Run DTMINST(TMVERIFY) to obtain the Thruput Manager Level information for the installed environment.

1A.7 Verify Thruput Manager Level

Run DTMINST(TMVERIFY) to obtain the Thruput Manager Level information for any given environment. The DTMTMLV8 program executes against a given TM library and provides the output from the TM D LEVEL command. The library in question can be specified in a JOBLIB or STEPLIB DD. If neither is provided, then the job will run against the modules found on the system where the job executes. This function allows the installation to ensure that the modules they are about to implement include the expected maintenance levels. 

1B. Use SMP/E Technique

Step 1A is an alternative to Step 1B. Complete one or the other.

This technique is applicable to installations where BMC ThruPut Manager is already installed and is being upgraded; it is not applicable to new installations. The following jobs, in their entirety, install the current SMP/E PTF updates to your existing SMP/E environment.

1B.1. Download the BMC ThruPut Manager Installation Files

Restore the installation files using the JCL link and password provided on the Electronic Delivery page received via the email response to your order.

This job unloads the DTMINST data set, and the BMC ThruPut Manager libraries providing the accumulated maintenance.

1B.2. ACCEPT Previous Maintenance

Run DTMINST(I$SMP1) to ACCEPT any installed PTFs that have not been previously ACCEPT’d. APARs should not be ACCEPT’d. This provides the option of using the SMP/E RESTORE function to back out the SMP/E upgrade if problems with the installation are encountered.

1B.3. Receive BMC ThruPut Manager Upgrade

Run DTMINST(I$SMP2) to RECEIVE the PTFs and APARs that were downloaded from the BMC ThruPut Manager FTP site. The LIST option allows the display of PTF details and APAR descriptions and requirements to the SMPOUT DD for your review.

1B.4. APPLY BMC ThruPut Manager Upgrade

Run DTMINST(I$SMP3) to APPLY the PTFs to the target libraries in the zone where BMC ThruPut Manager has been APPLY’d.

• Do not use the GROUPEXTEND option on the APPLY statement. This option can produce unpredictable results.
• Add the RECEIVED PTFs to the APPLY control statement.
• The level of system and JES2 macro libraries in the SYSLIB concatenation must match the level of JES2 that is running on the system where ThruPut Manager is going to be initialized. This ensures BMC ThruPut Manager and JES2 remain in sync by providing BMC ThruPut Manager with proper JES2 addressing.
• If your JES2 source has been modified by either USERMODS or other vendor software, ensure the libraries containing the modified JES2 macros are also concatenated ahead of the JES2 macro library in the SYSLIB DD statement or in the SYSLIB DDDEF.
• Return code 0 is expected from the APPLY. If a RC=4 is received, check the SMPOUT/SYSPRINT sysouts for space problems, missing DD statements, incomplete link edits, APARs being regressed, etc. Rectify these conditions and rerun the APPLY with the REDO option.

1B.5. APPLY APARs

Run DTMINST(I$SMP3) to APPLY all APARs contained in the APARs zip file supplied with the installation package. All APARs should be applied to avoid encountering known problems.

• Run an APPLY CHECK with all APARs.
• SMP/E restrictions dictate the application of only one APAR to a CSECT in any single APPLY statement. Use an APPLY CHECK to determine if any APARs cannot be applied together in the same APPLY statement and code separate APPLY statements for those identified.
• All of the APARs available at the time of shipment are contained in this install. Any additional APARs made available after creating the shipment can be obtained by visiting the Download APARS/Fixes section of the Support Center on the BMC ThruPut Manager website. If relevant, apply these additional APARs.
• An ACCEPT of the APARs is not recommended.

1B.6. Reassemble/Link BMC ThruPut Manager Source Stubs

Once BMC ThruPut Manager is installed, it may be necessary to re-assemble the source stubs to synchronize BMC ThruPut Manager with the JES2 and system level macros of the target system. This ensures BMC ThruPut Manager is provided with proper JES2 addressing.

A dummy usermod for BMC ThruPut Manager has been provided to manage the synchronization of the BMC ThruPut Manager source stubs. TTM8120 triggers a warning message or re-assembly of BMC ThruPut Manager JES2 source stubs DTMJ2MV8 and DTMJ2SV8 when required (See Synchronize JES2 and BMC ThruPut Manager ​​​​​​for details).

This completes the SMP/E process.

Proceed to Phase 2: Configure BMC ThruPut Manager if you are:

• Installing the product for the first time.
• Installing (an edition of) the product on a system for the first time.

Proceed to Phase 3: Review BMC ThruPut Manager interfaces if you are:

• Upgrading to a new maintenance level.