Synchronize JES2 and BMC ThruPut Manager

Synchronization considerations

When JES2 (z/OS) is upgraded/downgraded, BMC ThruPut Manager modules DTMJ2MV8 and DTMJ2SV8 must be synchronized with the changed JES2. BMC provides two techniques, outlined below, for handling JES2 macro changes on which BMC ThruPut Manager relies for its addressing.

USERMOD TTM8120 is also provided for synchronizing the BMC ThruPut Manager source stubs and JES2 source maintenance. Members UCLINU, UCLING and UCLINUG (a combination of the two) are found in the INSTALL data set.

Technique 1 adds a UMID entry of TTM8120 to any existing UMID entry for each JES2 macro on which BMC ThruPut Manager is dependent. During APPLY CHECK processing for the JES2 maintenance, SMP/E indicates the JES2 maintenance being applied does not PRE or SUP the ThruPut Manager USERMOD TTM8120.

This signals to the installation that BMC ThruPut Manager has been affected by the JES2 maintenance being APPLY’d. SMP/E BYPASS ID processing is used to allow the maintenance to be applied. If a RESTORE of the JES2 maintenance is required, the UMID entries must be removed after the BYPASS ID of TTM8120 is performed.

Notify the BMC ThruPut Manager support personnel that the JES2 maintenance has affected BMC ThruPut Manager. INSTALL(I$JESLNK) can then be used to re-assemble and link the BMC ThruPut Manager source stubs with the new level of JES2 macros, keeping the two synchronized. Care must be taken to implement the JES2 level with the BMC ThruPut Manager level at the same time.

Technique 2 adds a GENASM entry of DTMJ2MV8 and/or DTMJ2SV8 to each JES2 macro that BMC ThruPut Managerr is dependent on. The source stub is reassembled and re-linked if any of the macros listed in the UCLIN are altered during the APPLY of JES2 maintenance. This allows the installation to install JES2 maintenance without having to worry about BMC ThruPut Manager being out of synchronization with JES2.

For the assembly to be automatic, the BMC ThruPut Manager Source and Macro libraries (both target and distribution) must be added to the SYSLIB concatenation for JES2. Failure to add these libraries results in the inability to assemble the BMC ThruPut Manager source stubs, preventing the successful application of the JES2 maintenance.

Synchronizing BMC AMI Ops Automation for Batch ThruPut and JES2

The following outlines the steps necessary to keep the BMC ThruPut Manager source stubs and JES2 source maintenance synchronized:

  • Choose one of the synchronization techniques outlined previously.
  • To implement both methods, follow Technique 2 using the UCLINUG member provided in the INSTALL data set instead of UCLING.


Desired Effect

Implementation

Technique 1

Add UMID Entries

”Warning Bell” is issued when JES2 maintenance is applied.

SMP/E indicates the JES2 maintenance does not PRE or SUP the ThruPut Manager USERMOD TTM8120.

SMP/E BYPASS ID may be used to APPLY the JES2 maintenance.

BMC ThruPut Manager Support personnel must reassemble source stubs outside of JES2 maintenance by APPLY-ing TTM8120.

Execute member INSTALL(UCLINU)

Technique 2

Add GENASM Entries

Occurs Automatically when JES2 maintenance is applied.

Most current BMC ThruPut Manager source and macro libraries must be added as part of the SYSLIB concatenation for JES2 maintenance.

Define BMC ThruPut Manager libraries in JES2 target zone (DTMLINK, DTMSRC, ADTMLIB, ADTMSRC).

Add ADTMMAC and DTMMAC to the SYSLIB concatenation for the JES2 zone.

Apply the USERMOD UMxxxxxx (usermod name selected by the installation) to the JES2 zone. Use INSTALL(@UMOD1) to inform SMP/E how to link to the source stubs when they are reassembled.

Use INSTALL(UCLING) to ADD the ASSEM entry for the JES2 macros upon which BMC ThruPut Manager is dependent.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*