To configure ThruPut Manager include additional statements in your JES2 initialization stream:

1.  LOAD statements fetch the ThruPut Manager executable code.
2.  EXIT statements describe the JES2 exits needed by ThruPut Manager.
3.  A new JES2 control statement, TMPARM, customizes ThruPut Manager to your environment. It must be placed after the LOAD and EXIT statements.

2.1. JES2 Load statements

Include these LOAD statements in your JES2 initialization stream:

LOADMOD(DTMJ2SV7) STORAGE=CSA

DTMJ2SV7 contains exit routines which run in the Job Analyzer and user address spaces. This module is linked in a linklisted data set.

DTMJ2MV7 contains exit routines which run in the JES2 address space (i.e., called by the JES2 main task). This module is linked in a linklisted data set.

2.2. JES2 exit statements

Add the ThruPut Manager JES2 Exit routines to the JES2 initialization statements.

After TMT7126, ThruPut Manager will automatically enable its required JES2 exits at initialization, placing them at the front of the exits list. This means that, except in certain circumstances where you are sharing JES2 exit points, the following exit statements are optional. However, we recommend that you still include them in your JES2 initialization parameters for documentation purposes.

Do not include an EXIT(19) or EXIT(24) statement that does not include DTMJ2X19 or DTMJ2X24 respectively after the two ThruPut Manager LOADMOD statements. For more information on sharing JES2 exit points, refer to Appendix C, Share JES2 Exit Points for details.

Review the following statements carefully. Incorrect statements can have unpredictable results, since JES2 gives control to the wrong exit. In these statements:

• Items enclosed in brackets ‘[ ]’ are optional.
• A list of items in braces ‘{ }’ means 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 exit point.

Note 1: EXIT 19 and EXIT 24 are JES2 initialization exits. As a result, if they are activated through a command, their invocation does not take place until the next JES2 restart.

Note 2: EXIT 2 and EXIT 52 are new for installations moving from TM V6.

2.3. TMPARM statement

The TMPARM statement must be placed after the JES2 LOAD and EXIT statements for ThruPut Manager modules.ThruPut Manager is operational with the TMPARM defaults, and you may not need to change any of the default values. However it is prudent to verify this is the case for your situation.

The TMPARM parameters referring to special classes are no longer supported. If included the following message will be issued:

We recommend you remove them from your TMPARM statement. (You must define all job classes – Primary, Deferred, Analysis, Select, Exempt, and/or Default) via the TM CLASS command. See Technical Bulletin TM140505 for customers converting from ThruPut Manager V6.)

The TMPARM statement customizes the ThruPut Manager JES2 interface. The following functions can be specified:

• Process jobs with a JES2 /*SETUP statement.
• Process jobs submitted with TYPRUN=SCAN.
• Process jobs submitted with TYPRUN=HOLD.
• Define communication character(s) to be used as a signal that a given command belongs to ThruPut Manager.
• Adjust CPU factor to be used if you chose the CPU normalization facilities of ThruPut Manager. For a full explanation of this facility, see CPU-capping-and-normalizing.
• Activate or deactivate product features.
• Set user JECL mapping and processing options.
• Set system affinity for CONVERTER and Job Analysis.

2.4. TMPARM defaults

If no TMPARM statement is coded, the following defaults apply.

 3. Identify the ThruPut Manager Subsystem

 3.1. Update MVS Member IEFSSNxx

ThruPut Manager uses the subsystem interface to communicate with consoles. For documentation purposes, we recommend that you define the subsystem name $$TM to z/OS (IEFSSNxx in SYS1.PARMLIB). At initialization time, ThruPut Manager dynamically creates a subsystem entry for $$TM if it is not defined in member IEFSSNxx.

 4. Allocate and format ThruPut Manager files

Allocate the ThruPut Manager files. All are required for the relevant edition, except the Contention Management Facility file, which is only required when Dataset Contention Services is enabled and the installation wants to collect information about data set contentions.

For ThruPut Manager AE, an additional file, the Automation File is allocated in the Automation Services dialog, and no further action is needed at this time.

For ThruPut Manager AE+, an additional file, the Application Management Database is allocated in the Production Control Services dialog, and no further action is needed at this time.

ThruPut Manager AE+ also requires Battle Plan File, Experience Collection File, and Experience File to be allocated.

For further information on regular maintenance and performance, see File Maintenance and Performance.

The ThruPut Manager control file is a mandatory DASD file and contains critical information essential for managing jobs under the control of ThruPut Manager. This file is as integral to ThruPut Manager as the JES2 checkpoint is to JES2.

To allocate the control file, run INSTALL(I$ALLOC). TMSS automatically formats the file the first time that you use it. TMSS always asks for confirmation before formatting it.

Tip

In a MAS environment, make sure that the control file is on its own volume, and must not be allocated on a volume that contains JES2 PARMLIB libraries or the JES2 duplex data set.

To setup the TM Control File in the Coupling Facility, see XCF Notepad.

If the control file is copied 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 ensure that at least one of the files is usable in a disaster recovery scenario.

4A.2. Volume Information File

The Volume information file (VIF) is a mandatory shared DASD file which 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 upon its first use, and any time VIF=COLD is specified when starting the TMSS started task.

4A.3. Contention Management Facility file

The Contention Management Facility (CMF) is an optional file used exclusively by Dataset Contention Services 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 on how to implement DCS Recording, see the 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 1000 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.

4B.1 Automation File - TM AE and TM AE+ ONLY

The Automation File (AF) is required only for TM AE and TM AE+. It is shared among all systems in JESplex. Installations with more than one JESplex will need one Automation File for each JESplex.

AF is initialized and maintained using ISPF dialogs. The TMISPF dialog performs the actual allocation and initialization.

4B.2 Battle Plan File - TM AE+ ONLY

To allocate Battle Plan File (BPF) run member I$ALLOC2 in the INSTALL data set. See the ThruPut Manager AE+ Installation Companion Guide for more information.

4B.3 Experience Collection File - TM AE+ ONLY

To allocate Experience Collection File (EXPC) run member I$ALLOC2 in the INSTALL data set. See the ThruPut Manager AE+ Installation Companion Guide for more information.

4B.4 Experience File - TM AE+ ONLY

To allocate Experience File (EXPC) run member I$ALLOC2 in the INSTALL data set. See the ThruPut Manager AE+ Installation Companion Guide for more information.

4B.5 Application Management DB - TM AE+ ONLY

The Application Management DB (AMD) is file is defined from the PCS dialog. See the ThruPut Manager AE+ Installation Companion Guide for more information.

5. Tailor the ThruPut Manager started task (TMSS)

5.1. Prepare for TMSS Activation

ThruPut Manager Support Services (TMSS) runs as a started task in its own address space, and must be active for ThruPut Manager to perform any of its functions (excluding job selection).

The following discussion describes the TMSS sample JCL procedure delivered with ThruPut Manager. In most cases, this procedure can be used without modification.

At a minimum, the ThruPut Manager DTMLINK library must be an APF authorized library which is contained in the LINKLIST (concatenated with SYS1.LINKLIB). The TMSS Started Task requires a Control File, a Volume Information File (VIF), and optionally for DCS, a Contention Manager File (CMF). These files are automatically formatted upon initial ThruPut Manager startup.

TMSS Sample Procedure

A sample procedure is in INSTALL(TMPROC). The JCL for this procedure is shown below.

• 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. They are discussed in Section 4: TMSS Initialization Statements.

• Do not add SYSABEND, SYSMDUMP, or SYSUDUMP DD statements to the procedure, since TMSS takes dumps using the z/OS SVC Dump facility.

• The default for the TMSS procedure is JESLOG=SUPPRESS, which means the JESLOG will not be filled with every message issued by TMSS. This can be changed by adding “,JESLOG=…” to the START command, adding a JOBCARD to the TMSS procedure that contains JESLOG= or by changing the JESLOG= value for JOBCLASS(STC).

Sample PROC Parameters

Two of the parameters in the sample PROC are used to indicate where TMSS can find its initialization statements. These are:

Specifies a one or two character qualifier to be appended to the characters TMSS to form the name of a PDS member which contains TMSS initialization statements. The default for this parameter is 00.

Specifies a cataloged data set name indicating a partitioned data set which contains the member TMSSnn, as specified by the TMSS parameter. The default is SYS1.PARMLIB.

The load module name for the TMSS PROC is DTMTMV7. It accepts options in the EXEC PARM field. The options are supported in the sample procedure by parameters, each of which apply to a ThruPut Manager file. They are:

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. You are asked for permission and must confirm the request.

Requests an exceptional action to be taken for the CMF file. Use this parameter only when you want to COLD start this file. Before the CMF is reformatted, you are asked for permission and must confirm the request.

The CMF file is an optional file used only with DCS, and might not be enabled in your installation. Consult your ThruPut Manager systems programmer.

Requests an exceptional action to be taken for the Volume Information File. Use this parameter only when you want to COLD start this file. Before the VIF is reformatted, you are asked for permission and must confirm the request.

The Volume Information File is required by Job Setup Services (JSS).

This sample procedure applies to all editions of 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.

The syntax for the START command using the JCL procedure shown earlier is:

5.2. 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 ThruPut Manager installation follows. A complete description of all the TMSS initialization statements is included in Section 4: TMSS Initialization Statements in this manual. The following table lists the required TMSS initialization statements and their descriptions.

Before attempting to start ThruPut Manager, make sure that your initialization statements include the FILE CF and FILE VIF statements, and that the files have been properly allocated.

Once 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 which processes the start command, allowing you to use secondary subsystems when desired. To run under a secondary subsystem, use the SUB keyword in your START command. For example, to run under JESB type: S TM,...,SUB=JESB

In most installations, the START TM command can be part of an auto-start command string executed 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 you use depends on your environment and the ThruPut Manager files used in your installation.