ThruPut Manager may have introduced changes that affect its current implementation or interaction with other software products, e.g., messages for automated operators.

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.

Also, for customers upgrading from TM V6, refer to the following Technical Bulletin:

• TM140505 – ThruPut Manager V6 to 18.02 Considerations

7. Verify ThruPut Manager and OEM interfaces

This section describes additional steps to tailor 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 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

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 ThruPut Manager INSTALL data set. For details about using TMISPF, refer to 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 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 details about using UDF, refer to User-Display-facility: System Programming Guide: Base Product.

7.2. Implement the DFSMShsm interface - TM AE and TM AE+ ONLY

ThruPut Manager AE and ThruPut Manager AE+ prioritize DFSMShsm recalls. Accordingly, the DFSMShsm exit ARCRPEXT is required and is installed with TM AE 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 ThruPut Manager for the instructions to keep ThruPut Manager and JES2 synchronized.

7.3.2. XCF

The XCF Manager allows ThruPut Manager to use cross systems communications to support separate Control Files for each node in a SYSplex, resulting in significant performance improvements and reduced management overhead. Installations are encouraged to use XCF.

ThruPut Manager starts up with DCS enabled. Sites that do not use XCF will see enqueues for QNAME DTMDCSQX as outlined in the Dataset-Contention-Services: System Programming Guide.

To allow DCS to use XCF for communication across SYSplexes, you should code DCS SET XCF(YES) in the TMSS initialization statement. For further information, see Section-6-DCS-XCF-setup in this manual.

7.3.3. StorageTek/HSC

ThruPut Manager auto-detects OEM tape software. This functionality allows 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 ThruPut Manager is started. In addition, 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 7 JAL Variables in JAL

To collect CA 7 schedule information for JAL, ensure the TM interface for CA 7 has been implemented.

In conjunction with TM maintenance PTF TMT7110 a new interface to CA 7 is introduced. This interface is used to provide CA installations with the JAL descriptors representing CA 7 information along with providing functionality to communicate with CA 7 terminals for DCS Alerts and Messages issued from JAL.

This interface will allow ThruPut Manager to populate the existing CA 7 descriptors as follows (see the JAL-Reference-Guide for more information):

$CA7
$CA7_DUEOUT_DATE
$CA7_DUEOUT_TIME
$CA7_ENTRY
$CA7_INSTANCE_ALIAS
$CA7_INSTANCE_ID
$CA7_JCLID
$CA7_JOB#
$CA7_SCHID
CARTRIDGES $LIST_VOL_AUTO
$JECL_CA7(YES|NO) -indicates if a //*CA-7 statement was found in the JCL

In addition, it allows TM JAL to send messages to the CA 7 console as described in the MSGDEF and WTCA7 JAL statements

The interface is packaged as a new FMID (TTM7105) and a new Usermod (TTM7115). The FMID provides the code to allow TM to interface with CA 7 . The Usermod is provided as a convenience. If there is a need to reassemble the provided interface routine (DTMCA7UI), then an APPLY REDO of this Usermod (TTM7115) will accomplish this.

The procedure to install the CA 7 interface is as follows

• Customise the CA 7 interface JCL provided in the install data set (I$CA7)
• Execute the customized JCL I$CA7

As delivered this JCL performs a RECEIVE and APPLY CHECK of TM FMID TTM7105. Be sure to rerun the APPLY step removing the CHECK keyword. The affected module is DTMJAV7. Be sure this module is copied to the system execution library.

Once this interface is running with TM PTF TMT7110, then all of the CA 7 facilities described in the CA 7 JAL-Reference-Guide are available for the installation to use.

If TMT7110 is implemented and this interface is NOT installed, then message DTM3869I will be issued if the loaded JAL references any of the CA7 facilities. The message will be issued once to the system log (non-deletable) the first time a JAL is loaded and a job is analyzed. Jobs will continue to process, but the lack of CA 7 functionality may result in JAL logic flaws and the job may not be processed correctly.

7.3.5. CA-JMR - TM AE 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 Compuware.

7.3.6. CA-Deliver - TM AE 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.7. 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 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 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 ThruPut Manager AE Usage Guide.

7.3.8. 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 AE customers, Scheduler Intelligence is available for use. Refer to the AE Usage Guide for more details.

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

7.3.9. 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 ALL ThruPut Manager Editions (SE/AE), 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 ThruPut Manager Automation Edition customers, Scheduler Intelligence is also made available through this exit. For more information on Scheduler Intelligence, see ThruPut Manager AE 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.

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

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.

See Software Access Control (SAC) Guide for more information and the complete Implementation Process.