Phase 3: Review BMC ThruPut Manager interfaces

6. Accommodate changes introduced with this package

Refer to the Release Details manual for any changes introduced by a PTF, (initialization parms, messages, JAL descriptors, etc.) that may affect your automation operations or general implementation, and make appropriate accommodations.

ThruPut Manager at level 22.4 no longer supports the JES2 checkpoint at level z11. The JES2 checkpoint must be at level z22 before proceeding with this install.

Issue the JES2 command "$ACTIVATE,LEVEL=Z22" to set the JES2 checkpoint to level z22.

7. Verify BMC ThruPut Manager and OEM interfaces

This section describes additional steps to tailor BMC ThruPut Manager after the initial installation or maintenance upgrade. Also refer to this section, after OEM upgrades, for possible information specific to products that interface with BMC ThruPut Manager, such as JES2, CA products, or automated tape.

The following can be performed after an IPL.

7.1. Implementing the ISPF interfaces TMISPF AND UDF

BMC ThruPut Manager includes ISPF data sets to provide support for the TMISPF and UDF facilities. Verify the following:

• For both TMISPF and UDF, concatenate the DTMMENU, DTMPENU, and DTMTENU data sets defined during the INSTALL process to your current ISPF environment.
• To activate ISPF, we recommend you invoke it through a CLIST. Please tailor the CLIST sample provided in member $TMISPF of the BMC ThruPut Manager INSTALL data set. For details about using TMISPF, refer to BMC ThruPut Manager ISPF Services (TMISPF): System Programming Guide: Base Product.
• To activate UDF, we recommend you invoke it through a CLIST. Please use the documentation provided in members $READUDF and $UDF of the BMC ThruPut Manager INSTALL data set. Alternatively, if invoked as a command, update your ISPF command table (ISPCMDS) to include the command to invoke the User Display Facility. The required entry is:

Once these steps have been taken, the UDF is activated. To invoke it, simply enter the TMUSER command at any ISPF command prompt. For more information about using UDF, see User-Display-Facility: System Programming Guide: Base Product.

7.2. Implement the DFSMShsm interface - BMC AMI Ops Automation for Batch ThruPut and TM AE+ ONLY

BMC AMI Ops Automation for Batch ThruPut and BMC ThruPut Manager AE+ prioritize DFSMShsm recalls. Accordingly, the DFSMShsm exit ARCRPEXT is required and is installed with BMC AMI Ops Automation for Batch ThruPut and TM AE+. If the site has not already implemented this exit point, the routine must be activated either via a F HSM,SETSYS EXITON(RP) command or permanently enabled by updating the parmlib member ARCCMD00 to include:

The exit can be disabled via the command F HSM,SETSYS EXITOFF(RP).

7.3. OEM considerations

7.3.1. JES2

When maintaining JES2, refer to Synchronize JES2 and BMC ThruPut Manager for the instructions to keep BMC ThruPut Manager and JES2 synchronized.

7.3.2. XCF

BMC AMI Ops Automation for Batch ThruPut and BMC ThruPut Manager SE or AE+ all default to use XCF for DCS communications.

Sites that do not use XCF will see enqueues for QNAME DTMDCSQX as outlined in the Dataset-Contention-Services: System Programming Guide. For more information, see DCS-XCF-setup.

7.3.3. StorageTek/HSC

BMC ThruPut Manager auto-detects OEM tape software. This functionality allows BMC ThruPut Manager to automatically obtain correct tape unit definitions.

This auto-detect functionality requires HSC (and SMC when using HTTP communication) be fully initialized before BMC ThruPut Manager is started. In addition, BMC ThruPut Manager requires that the following STK install libraries be available via the LINKLST on each system running:

• HSC, the LINKLST must include SLSLINK
• SMC 6.2, the LINKLST must include SLSLINK and SMCLINK
• ELS (7.0), the LINKLST must include SEALINK

7.3.4. CA-JMR - BMC AMI Ops Automation for Batch ThruPut and TM AE+ ONLY

If a job is managed by Service Level Manager (SLM) and then processed by JMR, the JMR status will be invalid. This is because the HASP373 message issued to both the console and the joblog is modified by SLM to alter the initiator name and to expand the message beyond its normal length, in response to TM INIT. If this behavior is undesirable, please contact BMC Support.

7.3.5. CA-Deliver - BMC AMI Ops Automation for Batch ThruPut and TM AE+ ONLY

Define SLM job classes (GS and PS) to the CA-DELIVER class table. If the job classes are not defined, delivery of some CA output may not occur.

7.3.6. ZEKE/ZEBB (ASG Software)

With ZEKE or ZEBB enabled, installations should activate the TM interfaces by adding the following parms to the ZEKE/ZEBB configurations, as directed by the ASG documentation:

• For ZEKE, set ZekeCtl to Y (the default value). This enables ZEKECTL statements to be passed to BMC ThruPut Manager Job Analysis. Refer to the ZEKE user documentation for more information.
• For ZEBB, set ThruPutMgr=Y in the Generation Options Multi Product Interface panels. This enables compatibility with BMC ThruPut Manager. Refer to the ZEBB user documentation for more information.
• For BMC AMI Ops Automation for Batch ThruPut users, Scheduler Intelligence is available for use. For more information on Scheduler Intelligence, see BMC AMI Ops Automation for Batch ThruPutUsage-guide.

7.3.7. Control-M

The CTPARMs must be updated to include TPMINTG=Y in SUBMIT statement. This will allow additional comment statements to be inserted into the job, which will be reflected in the $CONTROL_M JAL descriptors. Additionally for Identify the BMC AMI Ops Automation for Batch ThruPut customers, Scheduler Intelligence is available for use. For more information, see BMC AMI Ops Automation for Batch ThruPutUsage-guide.

Control-M APAR IM10384 (PTF PG05664) is required for these values to be accurate.

7.3.8. IBM z Workload Automation

For IBM z Workload Automation (IZWS), all ThruPut Manager installations can use an IBM z Workload Automation (IZWS) exit to obtain scheduler information for individual jobs.  This information can be used as follows:

• For BMC ThruPut Manager Editions (SE/AE+) and BMC AMI Ops Automation for Batch ThruPut, new JAL variables ($IZWSxxxx) are available . These provide installations with general information from the scheduler to help denote special handling for jobs scheduled through IZWS. 
• For BMC AMI Ops Automation for Batch ThruPut customers, Scheduler Intelligence is also made available through this exit. For more information on Scheduler Intelligence, see BMC AMI Ops Automation for Batch ThruPut Usage Guide.

This exit requires setting of the EXIT01SZ parameter on the IZWS OPCOPTS initialization statement. The keyword indicates that EXIT 01 (EQQUX001) can change the size of the JCL. The value to specify is the size of your largest expected JCL stream + 4.

To install this exit copy DTMIZWS1 to a new member called EQQUX001. If this exit is already used, contact BMC Support.

For more information about the installation of this exit, see IBM Workload Scheduler for z/OS: Customization and Tuning guide from IBM Documentation.

7.3.9. Broadcom ESP Workload Automation

For Broadcom ESP Workload Automation (ESP), all ThruPut Manager installations can enable the Job Scheduler Support by adding CUSTOM=(UM0053) to your JES2 TMPARM statement.

You can activate this option without restarting JES2. Use the TM CUSTOM ENABLE(UM0053) command to signal the call to ESP, which obtains ESP information for jobs within an ESP application.

Because the call to ESP might come from a system where the ESP master is not started, it requires the high availability or the service governor option installed for ESP.

7.4. Implementing the Software Access Control (SAC) interfaces

Job Binding Services includes the Software Access Control (SAC) facility. This optional Software License control facility extends the existing mechanism of JBS to allow an installation to restrict access to a specified function that is invoked via TSO, ISPF, REXX or a CLIST.

For more information and the complete Implementation Process, see Software-Access-Control-guide.