Phase 2: Configure BMC ThruPut Manager
If you are an existing customer, the current settings might already be completed and sufficient, based on your previous installations and upgrades. However, if you are installing a new version at an existing site, you must revisit this phase to discover any changes, removals, or additions with the new version.
This phase might be unnecessary for existing sites upgrading to a new maintenance level.
Task 1: Adding JES2 statements
LOADMOD statement
The LOADMOD statement fetches the executable code for BMC ThruPut Manager.
Include the following LOADMOD statement in your JES2 initialization stream:
LOADMOD(DTMJ2MV8)
This is the only LOADMOD statement required by ThruPut Manager.
Previous releases of ThruPut Manager required two LOADMOD statements. Only a LOADMOD statement for DTMJ2MV8 is required.
EXIT statements
In many installations, no EXIT statements are required for the BMC ThruPut Manager JES2 exit routines. BMC ThruPut Manager uses JES2 exits 2, 4, 5, 7, 8, 10, 14, 19, 24, 36, 49, 51, 52, and 54. It automatically defines and enables these required JES2 exit routines. If you do not have any other JES2 exit routines installed, skip to the section below on the TMPARM statement.
By default the BMC ThruPut Manager JES2 exit routines for a given exit point run before any other JES2 exit routines supplied by a third party software product or by your installation. If a non BMC ThruPut Manager exit routine must run first, define the full exit routine list with DTMJ2Xnn (where nn is the exit number in two digits) in its place in the calling sequence.
EXIT statements for exits 19 and 24 that include non BMC ThruPut Manager exit routines should be placed before the LOADMOD statement for DTMJ2MV8. However, if you place these EXIT statement after the LOADMOD statement for DTMJ2MV8 you must include DTMJ2X19 (for exit 19) or DTMJ2X24 (for exit 24) in the exit routine list.
Review the following optional statements carefully. Incorrect statements can have unpredictable results, because JES2 might give control to the wrong exit. In these statements:
- Items enclosed in square brackets ([ ]) are optional.
- A list of items enclosed in braces ({ }) means that you should choose one from the list.
- Defaults are indicated by underlining.
- yourExit represents the names of your installation exits, if any, that are to be given control at that the exit point.
Here is an example for JES2 exit 10. Note that the format of BMC ThruPut Manager JES2 exit names is DTMJ2Xnn where nn is the exit number.
TMPARM statement
A TMPARM statement, which is processed by BMC ThruPut Manager, customizes the BMC ThruPut Manager JES2 interface. You must place the TMPARM statement after the JES2 LOADMOD statement for DTMJ2MV8 module. We recommend using parameters included in INSTALL(JESPARM).
TMPARM parameters that refer to to special classes are not supported , so we recommend that you remove them from your TMPARM statement. If not, the following message is issued:
You must define all job classes—Primary, Deferred, Analysis, Select, Exempt, and Default—via the TM CLASS command.
You can specify the following functions:
- Process jobs with a JES2 /*SETUP statement
- Process jobs submitted with TYPRUN=SCAN
- Process jobs submitted with TYPRUN=HOLD
- Communication characters to be used as a signal that a given command belongs to BMC ThruPut Manager.
- Adjust CPU factor to be used if you chose the CPU normalization facilities of BMC ThruPut Manager. For a full explanation of these facilities, see CPU-capping-and-normalizing.
- Activate or deactivate product features
- User JECL mapping and processing options.
- System affinity for CONVERTER and job analysis.
- The number of BMC ThruPut Managerdynamic initiators.
- TRACE=NO option for automatically created JES2 exits.
If no TMPARM statement is coded, the following defaults apply:
CNVTERR = NO
COMCHAR = /
OPTIONS = (see following chart)
The options and their statuses are as follows:
Option | Default status | BMC AMI Ops Automation for Batch ThruPut | ThruPut Manager Automation Edition Plus (AE+) | ThruPut Manager Standard Edition (SE) |
|---|---|---|---|---|
DCS | ACTIVE |
|
|
|
DJC | ACTIVE |
|
|
|
JBS | ACTIVE |
|
|
|
JCS | ACTIVE |
|
|
|
JES3 | INACTIVE |
|
|
|
JLS | ACTIVE |
|
|
|
JSS | ACTIVE |
|
|
|
JTS | ACTIVE |
|
|
|
Mellon | INACTIVE |
|
|
|
MHS | ACTIVE |
|
|
|
NET | INACTIVE |
|
|
|
UCS | ACTIVE |
|
|
|
UHS | ACTIVE |
|
|
|
DBS | ACTIVE |
|
| NA |
SLM | ACTIVE |
|
| NA |
PCS | ACTIVE | NA |
| NA |
For more information about the TMPARM initialization statement, see TMPARM-initialization-statement.
Task 2: Defining your subsystem name
BMC ThruPut Manager uses the subsystem interface to communicate with consoles. We recommend that you define the subsystem name $$TM to z/OS (IEFSSNxx in SYS1.PARMLIB). At initialization time, BMC ThruPut Manager dynamically creates a subsystem entry for $$TM if it is not defined in member IEFSSNxx.
Task 3: Allocating and format BMC AMI Ops Automation for Batch ThruPut files
Allocate the following BMC ThruPut Manager files, depending on the product that you are using. For more information about a file, click the file name.
Name | BMC AMI Ops Automation for Batch ThruPut | ThruPut Manager Automation Edition Plus (AE+) | ThruPut Manager Standard Edition (SE) |
|---|---|---|---|
Control File (CF) |
|
|
|
Volume Information File (VIF) |
|
|
|
Contention Manager Facility File (CMF) |
|
| Opt |
Automation File (AF) |
|
| |
Battle Plan File (BPF) |
| ||
Experience Collection File (EXPC) |
| ||
Experience File (2 files) (Experience) |
| ||
Application Management Data Base (AMD) |
|
For more information about regular maintenance and performance, see File Maintenance and Performance.
Control file
The Control File (CF) is a mandatory DASD file and contains critical information essential for managing jobs controlled by BMC ThruPut Manager. This file is as integral to BMC ThruPut Manager as the JES2 checkpoint is to JES2.
To allocate the CF, run INSTALL(I$ALLOC). BMC ThruPut Manager Support Services (TMSS) automatically formats the file the first time that you use it. TMSS always asks for confirmation before formatting it.
If you copy the control file constantly for use in disaster recovery, allocate a duplex control file with identical space attributes on a different low-usage volume. Also copy the duplex file to make sure that at least one of the files is usable in a disaster recovery scenario.
Volume Information File
The Volume Information File (VIF) is a mandatory shared DASD file that tracks volumes that are being managed by Job Setup Services (JSS) primarily for Virtual Volume Staging.
To allocate the VIF, run INSTALL(I$ALLOC).
The VIF is formatted automatically on its first use, and any time that VIF=COLD is specified when starting the TMSS started task.
Contention Management Facility File
You can use the Contention Management Facility (CMF) File exclusively with Dataset Contention Services (DCS) to record contention records that are used by the management reports produced by DCS. This file is shared by all the systems that are part of the DCS complex. For more information about how to implement DCS Recording, see Dataset-Contention-Services-System-Programming-Guide.
The nature of the CMF File does not permit an exact calculation of its size. One cylinder of a 3390 device holds records for approximately 600 to 1,000 jobs in contention. Consider your reporting cycle (daily, weekly, on demand, or any other interval you may choose) and the frequency of data set conflicts.
Calculate the number of jobs that might run into contention during your cycle time, then double the space needed. This approach should provide you with a comfortable margin of error.
To allocate the CMF, run INSTALL(I$ALLOC). The data set is formatted if DCS detects that it has not been formatted. TMSS asks for operator confirmation before formatting the CMF file.
Automation File
The Automation File (AF) is required only for BMC AMI Ops Automation for Batch ThruPut and BMC ThruPut Manager Automation Edition Plus (AE+). It is shared among all systems in JESplex. Installations with more than one JESplex will need one Automation File for each JESplex.
You initialize and maintain the AF via ISPF panels. You allocate and initialize it via the TMISPF panel.
Battle Plan File
You must allocate the Battle Plan File (BPF) for BMC ThruPut Manager AE+ only. To allocate the BPF run member I$ALLOC2 in the INSTALL data set. For more information, see the BMC ThruPut Manager AE+ Installation Companion Guide.
Experience Collection File
You must allocate the Experience Collection (EXPC) File for BMC ThruPut Manager AE+ only. To allocate the EXPC run member I$ALLOC2 in the INSTALL data set. For more information, see the BMC ThruPut Manager AE+ Installation Companion Guide.
Experience File
You must allocate the Experience File for BMC ThruPut Manager AE+ only. To allocate Experience File (EXPC) run member I$ALLOC2 in the INSTALL data set. For more information, see the BMC ThruPut Manager AE+ Installation Companion Guide.
Application Management Database File
You define the Application Management Database (AMD) File via the PCS panel. For more information, see the BMC ThruPut Manager AE+ Installation Companion Guide.
Task 4: Configuring the BMC ThruPut Manager started task
BMC ThruPut Manager
Support Services (TMSS) runs as a started task in its own address space, and must be active for
BMC ThruPut Manager
to perform any of its functions (excluding job selection).This section describes the TMSS sample JCL procedure delivered with
BMC ThruPut Manager
. In most cases, you can perform this procedure without modification.At a minimum, the BMC ThruPut Manager DTMLINK library must be an APF-authorized library that is contained in the LINKLIST (concatenated with SYS1.LINKLIB). The TMSS started task requires a Control File (CF), a Volume Information File (VIF), a Contention Manager File (CMF) for Dataset Contention Services (DCS). These files are automatically formatted when you first start BMC ThruPut Manager.
TMSS sample procedure
A sample procedure is in INSTALL(TMPROC). The JCL for this procedure as follows:
//TM EXEC PGM=DTMTMV8,TIME=1440,REGION=0K,
// PARM=’CF=&CF,CMF=&CMF,SPOOL=&SPOOL,VIF=&VIF’
//* PARAMETERS USED TO SUPPORT THRUPUT MANAGER FILES:
//* CF USED TO FORMAT THE CONTROL FILE, OR A PART OF
//* THE CONTROL FILE ASSOCIATED WITH AN FEATURE
//* CMF USED TO FORMAT THE CMF FILE
//* SPOOL USED TO FORMAT THE SPOOL FILE
//* VIF USED TO FORMAT THE VOLUME INFORMATION FILE
//* PARAMETERS FOR FILES NOT USED ARE CHECKED FOR SYNTAX BUT
//* ARE OTHERWISE IGNORED
//SYSPARM DD DSN=&P(TMSS&TMSS),DISP=SHR,FREE=CLOSE
- This procedure needs only one DD statement, SYSPARM, from which TMSS reads sequential input. TMSS dynamically allocates any other required data sets. This DD statement points to the data set that contains the TMSS initialization statements and allows the installation to customize the product to your installation requirements. For more information, see TMSS-initialization-statements.
- Do not add SYSABEND, SYSMDUMP, or SYSUDUMP DD statements to the procedure, because TMSS takes dumps by using the z/OS SVC Dump facility.
- The default for the TMSS procedure is JESLOG=SUPPRESS, which means the JESLOG is not filled with every message issued by TMSS. To change the default, add ,JESLOG=… to the START command, adding a JOBCARD to the TMSS procedure that contains JESLOG= or by changing the JESLOG= value for JOBCLASS(STC).
This sample procedure applies to all editions of BMC ThruPut Manager. Parameters from this procedure apply to specific files, some of which might not be used in your installation. If you specify a parameter for a file that your installation does not use, the parameter is checked for syntax but is otherwise ignored.
Sample procedure parameters
The sample procedure contains the following parameters:
Parameter | Description |
|---|---|
TMSS=nn | Indicates where TMSS can find its initialization statements nn represents a one- or two-character qualifier to be appended to the characters TMSS to form the name of a PDS member that contains TMSS initialization statements. The default value 00. |
P=dataSetName | Specifies a cataloged data set name indicating a partitioned data set that contains the member TMSSnn, as specified by the TMSS parameter. The default value is SYS1.PARMLIB. |
CF=COLD or CF=’FORMAT(feature1[,...,featuren])’ | Requests an exceptional action to be taken for the area of the Control File used by one or more features. This is a request to reformat the area (or areas) associated with the features listed. When prompted for permission, confirm the request. The load module name for the TMSS PROC is DTMTMV8. It accepts options in the EXEC PARM field. The options are supported in the sample procedure by these parameters, each of which applies to a ThruPut Manager file. They are: |
CMF=COLD | Cold starts the CMF file. When prompted for permission before the CMF is reformatted, confirm the request. |
VIF=COLD | Cold start the Volume Information File. When prompted for permission before the VIF is reformatted, confirm the request. The Volume Information File is required by Job Setup Services (JSS). |
START command
The syntax for the START command using the sample JCL procedure as follows:
[,P=dsname | SYS1.PARMLIB]
[,CF=COLD | CF=’FORMAT(feature1[,...,featuren])’]
[,CMF=COLD]
[,VIF=COLD]
TMSS initialization statements
A sample TMSSnn is provided in member TMSS00 in the INSTALL data set. A summary of the required initialization statements for a basic BMC ThruPut Manager installation follows. A complete description of all the TMSS initialization statements is included in TMSS-initialization-statements. The following table lists the required TMSS initialization statements and their descriptions. Additional recommended statements have been provided in INSTALL(TMSS00).
Statement | Description |
|---|---|
FILE CF | Specifies the name of the Control File and some timing parameters to ensure that all systems can access the file. You must also specify the name of the Duplex Control File. |
FILE CMF | Specifies the name of the file used for data set contention data recording |
FILE VIF | Specifies the name of the data set used for the Volume Information File |
TMSS startup considerations
Before attempting to start BMC ThruPut Manager, make sure that your initialization statements include the FILE CF and FILE VIF statements, and that the files have been properly allocated.
After the cataloged procedure is in place, you can start and stop the TMSS started task just as you would any other started task. TMSS always runs under the subsystem that processes the start command, so you can use secondary subsystems. To run under a secondary subsystem, use the SUB keyword in your START command. For example, to run under JESB type, run S TM,...,SUB=JESB
In most installations, the START TM command can be part of an auto-start command string that runs during system IPL.
TMSS is identified by the task identifier TM (for example, in the display from a z/OS D A command).
The precise START command that you use depends on your environment and the BMC ThruPut Manager files used in your installation.