There are a number of TMSS initialization statements that allow you to customize BMC ThruPut Manager to your environment.

These statements provide TMSS with the information needed to create a framework to interpret the rules that you define with the Job Action Language.

An example illustrates the point: the 'JAL LOAD data set-name' initialization statement tells BMC ThruPut Manager where to find the Job Action Language that you have written. At initialization time, TMSS brings the JAL (your rules) from the specified data set.

Associating TMSS statements with a system

To facilitate sharing common TMSS initialization statements for multiple systems, the "FOR Group" facility is provided. Use this facility only when you have unique statements for a particular system. The format is as follows:

Where represents the SMFID of a system that should honor the TMSS initialization statements that follow.

To terminate the FOR condition, use the ENDFOR statement.

The rules for using the FOR group facility are as follows:

• Statements that are not within a "FOR Group" are always applicable regardless of the system that processes them.
• Nested FOR groups are not allowed. If another FOR statement is encountered before an ENDFOR terminates the previous group, it is treated as an error.
• You can specify a list of SMFIDs, separated by commas.
• The FOR and ENDFOR statements can begin in any column of the record. Only columns 1 through 72 are scanned.
• If the SMFID of the system processing a FOR Group does not match the FOR SMFID, the statements are ignored-almost. The statements receive simple syntax checking, so they must conform to the TMSS initialization statement format. Unless there is a gross syntax error, however, these statements are totally ignored.

TMSS statements in a FOR Group

A number of TMSS statements, because they represent resources that are to be shared, cannot be included within a FOR Group. If any of the following statements is found within a FOR Group, an error message is generated and TMSS processing terminates:

FILE CF 
FILE SPOOL 
FILE VIF
TM USER

FOR Group example

The following is an example of the use of the FOR Group. Only some of the TMSS initialization statements are shown here:

Coding rules for TMSS statements

The coding rules for TMSS initialization statements are:

• Physical input records must be 80 bytes long.
• Control statements can begin in any column of the record. Only columns 1 through 72 are scanned.
• Only one definition per control statement.
• Statements exceeding 72 characters can be continued by putting a '+' or '-' as the very last non-blank character of the statement, and continuing the statement on the next input record.
• the '+' continuation character strips leading blanks on the following statement
• the '-' continuation character does not.
• Comments start with the characters '/*' and end with the characters '*/'. They can appear anywhere within a statement and can cross input records if the continuation characters '+' or '-' are used as described previously.
• Nested comment delimiters are not allowed. For example:
  /* OUTER /* INNER COMMENT */ COMMENT */ 
  is incorrect.
• Strings which include blanks must be enclosed within apostrophes. Blanks outside of enclosed strings delimit parameters.

Descriptions of all the TMSS initialization statements follow. 

CFM SET

Set Values for control file

This TMSS initialization statement allows the DEPTH, MINDORM, MAXDORM, MAXHOLD, and MINHOLD values for the control file to be specified within a FOR group, so that these values can vary between individual systems. The values specified by this statement can override values set by the FILE CF initialization statement. If these values are not set by CFM SET or FILE CF, the defaults are:

 As a starting point, the recommended settings for MINDORM, MAXDORM and MINHOLD are the values in the MASDEF HOLD and DORMANCY parameters on each member for your JES2 checkpoint.  

The FILE CF syntax is as follows:

CPS WRITER

Specify CPS Writer Parameters

This statement defines and activates a CPS Writer. One statement is needed for each Writer.

The CPS Writer syntax is as follows:

DAL LOAD

Load DD Action Language

This statement signals to BMC ThruPut Manager that DAL installation rules are to be activated. It also identifies the data set that contains the DAL output from the Language Processor. The data set must be cataloged, and can be either sequential or partitioned.

The DAL LOAD syntax is as follows:

DAL TRACE  

Trace DAL Execution

This statement allows you to activate DAL tracing at TMSS start time. You can either do it for all jobs or for selected jobs.

The DAL LOAD syntax is as follows:

DCS SET

This TMSS initialization statement sets some global defaults for DCS.

The DCS SET syntax is as follows:

DJC SET

This TMSS initialization statement sets some global defaults for DJC.  

The DJC SET syntax is as follows:

ENDFOR

Control Statement

This statement indicates the end of a FOR Group.  

The ENDFOR syntax is as follows:

FILE CF

Control File Initialization Statement

This TMSS initialization statement defines and activates the control file.

You can also specify the DEPTH, MINDORM, MAXDORM, MAXHOLD, and MINHOLD keywords by using a CFM SET statement. If these values are not set by CFM SET or FILE CF, the defaults are as follows:

The FILE CF syntax is as follows:

Duplexing has very low overhead, one EXCP per cycle fixed overhead, and the necessary I/O when changes are detected. A very low DUPINT parameter (for example, 2 or 3) seconds increases the overhead, but ensures a seamless recovery from the duplex file. A high DUPINT parameter (for example, 30 to 60 seconds) yields an almost negligible overhead at a risk of small data loss during the recovery process. This choice might require more operator intervention after recovery. For example, you might need to reanalyze some jobs.

The duplex is updated by only one of the systems that use the control file and is never written at the same time as the control file to ensure data integrity of at least one of the copies of the files at the disaster recovery site.

The control file is automatically formatted on its first use. To reformat, specify CF=COLD when starting TMSS.

You can override the specified DEPTH, MINDORM, MAXDORM, MAXHOLD, and MINHOLD values via the CFM SET initialization statement. You can use FILE CF to set global values for a complex, and then use CFM SET within a FOR group to set different values for individual systems.

MAXHOLD and MINHOLD are mutually exclusive. If you do not specify MAXHOLD or MINHOLD, the default is MINHOLD(50) or half a second.

If you specify FILE CF more than once, the last statement encountered is used.

If more than one source is specified for DEPTH, MINDORM, MAXDORM, MAXHOLD, or MINHOLD, the last setting encountered takes effect, regardless of whether the source was a CFM SET or FILE CF statement.

FILE CMF

DCS Recording File Definition

This statement specifies the name of the file to be used for Contention Management Facility (CMF) data set contention data recording. This file is a "wrap-around" file that is shared by all systems in a DCS complex. This statement is not accepted within a FOR GROUP.  

The FILE CMF syntax is as follows:

Specifies the data set name of the DCS recording file, which is dynamically allocated and must be cataloged

If this statement is omitted, DCS does not record data set contention data.

The CMF File is automatically formatted upon its first use. Subsequent reformatting can be requested by coding CMF=COLD when starting TMSS.

If FILE CMF is specified more than once, the last statement encountered is used.

FILE SPOOL

Spool File Definition

This statement specifies that TMSS is to provide spooling services, and provides the name of the SPOOL File. This statement is not accepted within a FOR GROUP.  

The FILE SPOOL syntax is as follows:

Specifies a cataloged data set name, pointing to the SPOOL File.

If this statement is omitted and you are using CPS, BMC ThruPut Manager does not perform:

• DCS ALERT spooling.
• CPS Writer status checkpointing.
• DCS ALERTs on a system other than the system on which they were created.

The SPOOL file is automatically formatted upon its first use. Subsequent reformatting can be requested by coding SPOOL=COLD when starting TMSS.

If FILE SPOOL is specified more than once, the last statement encountered is used.

FILE VIF

Define VIF

This statement specifies the name of the data set used for the Volume Information File. This data set is mandatory, and must be allocated in a single extent. This data set must be accessible to any system sharing the SPOOL File for which CPS Writers are activated. This statement is not accepted within a FOR GROUP.  

The FILE VIF syntax is as follows:

The Volume Information File is a required file. Failure to specify a VIF results in a non-deletable warning message, and Job Setup Services cannot function. TMSS continues in order to provide a diagnostic environment.

If you let the VIF assume the default values, the space required is 1 cylinder of a 3380/3390 DASD device. Cylinder allocation improves the efficiency of the VIF channel programs.

The VIF is automatically formatted upon its first use. Subsequent reformatting can be requested by coding VIF=COLD when starting TMSS.

Once the VIF has been formatted, it cannot be moved to an unlike device (e.g. from an IBM 3380 to an IBM 3390). If this occurs, TMSS requests permission to reformat the file. The existing VIF cannot be used on the new device type.

If more than one FILE VIF statement is specified, the last statement encountered is used.

FOR

Control Statement

This statement indicates the beginning of a FOR Group. If The SMFID of the system processing the statement matches one of the SMFIDs in this statement, then the initialization statements following the FOR statement are processed. Otherwise, they are bypassed.  

The FOR syntax is as follows:

If another FOR statement is encountered before an ENDFOR, it is considered an error. The following initialization statements cannot be included within a FOR Group:

FILE CF 
FILE SPOOL 
FILE VIF T
M USER

JAL LOAD

Load Job Action Language

This statement signals to BMC ThruPut Manager that installation rules are to be activated. It also identifies the data set which contains the output from the Language Processor. The data set must be cataloged, and can be either sequential or partitioned.  

The JAL LOAD syntax is as follows:

If no JAL internal text is provided, BMC ThruPut Manager provides JCL checking only. The jobs are requeued with the same attributes they had when they were submitted.

If multiple JAL LOAD statements are specified for a system, the last statement encountered is used. A different JAL LOAD statement can be applied to each system by using a FOR group.

JAL TRACE

Trace JAL Execution

This statement allows you to activate JAL tracing at TMSS start time. You can either do it for all jobs or for selected jobs.  

The JAL TRACE syntax is as follows:

JSS RECALL

Alter the Security Environment for DFSMShsm Recalls

This statement allows you to alter the security environment under which DFSMShsm recalls are processed.  

The JAL RECALL syntax is as follows:

JSS SET

Bypass Allocation Processing for IEFBR14-type Programs

This statement allows you to specify a list of programs for which certain types of allocation processing should not be performed, such as IEFBR14. Allocation processing will be bypassed under these circumstances:

• If the primary disposition for a data set allocated by this type of program is DELETE, HSM recalls are not necessary.
• If the data set is a tape data set, it will never be opened, and allocation is not needed.

The JSS SET syntax is as follows:

If multiple JSS SET statements are specified for the same program name, the last one encountered takes effect. This means that if both BYPASS_RECALLS and BYPASS_TAPE_ALLOCATION are desired, they should be specified on the same JSS SET statement.

If the primary disposition is DELETE, the data set is deleted even though allocation processing is bypassed.

DAL is invoked for data sets in steps that execute a listed program, even if all data sets are bypassed.

Bypassed data sets are not reflected in the counts shown by the JAL Descriptors $HRECALL, $HRECALL_DASD, and $HRECALL_TAPE.

JTS OPTIONS

Set Defaults

This TMSS initialization statement allows you to change the defaults provided with UCS for JTS. It is optional.

The JTS OPTIONS syntax is as follows: 

SYSOUT Printing Services Options

This statement defines a set of options to be used for output printed using JES2 SYSOUT.  

The SPS DEFINE syntax is as follows: 

In an environment using only SPS, output without a valid destination is queued in SYSOUT class A and is held. For a description of how such output is handled in an environment that also uses CPS refer to Printing Services

TBL LOAD

Load Table for DAL or JAL

This statement specifies that TMSS is to load a table to be used in DAL or JAL.  

The TBL LOAD syntax is as follows: 

The SAC table is only available with JBS.

TM ATL

Define ATL Unit Names

This statement is used to indicate the esoteric unit names associated with the Memorex (Sutmyn) 5400 ATL.  

The TM ATL syntax is as follows: 

TM BATCH

Submit a Batch of Commands

This statement is used to submit a batch of BMC ThruPut Manager commands at TMSS initialization time. Note that the commands are processed after TMSS initialization is completed. That is, this initialization statement simply queues all the commands for later execution. You can have more than one 'TM BATCH' command in your initialization stream.

The rules for storing the text representing the commands are as follows:

• Only columns 1 to 72 inclusive are processed.
• Records containing /* starting in column 1 are treated as comments.
• Commands must be contained within a single statement. That is, continuation to another statement is not allowed.
• The response from a command is sent to the master console, unless the L= keyword was specified on the command.

The TM ATL syntax is as follows: 

Define BTLS Unit Names for VTS

This statement is used to indicate the esoteric unit names and library names used for VTS by the IBM 3495 robotic tape library running in Basic Tape Library System (BTLS) mode.

The TM BTLS syntax is as follows: 

TM CATALOG SET

Define BMC ThruPut Manager Catalog Search Options

This statement specifies the options used by BMC ThruPut Manager when searching catalogs.  

The TM CATALOG SET syntax is as follows: 

TM DLM

Defined DLM Unit Names

This statement defines the device characteristics and tape management library that are associated with this pool of devices.

The TM DLM syntax is as follows: 

TM EXIT

Define an Installation Exit

This statement specifies which installation exits are to receive control, and their initial status.  

The TM EXIT syntax is as follows: 

Specifying a TM EXIT statement more than once for the same exit number causes an error.

Because installation exits associated with the Job Analyzer can run in any active initiator address space, the TM EXIT statement processor enforces the requirement that Job Analyzer exits must come from LPA or a LINKLIST data set.

The TRACE/NOTRACE keywords of the TM EXIT statement determine the eligibility of the exit for tracing. No tracing is actually done unless there is also a TM TRACE initialization statement, or a TM TRACE command is issued. See the description of the TM TRACE statement below, or the TM TRACE operator command in the Command Reference Guide.

The TRACE/NOTRACE keywords establish the initial status of the exit's trace eligibility. This status can be altered after TMSS is started by using the TM EXIT command. 

TM SMF

Define SMF Data Collection Parameters

This statement specifies which SMF user record is used to write SMF data, and which data is collected. For information about SMF data collection, see SMF-data-collection-for-job-analysis.  

The TM SMF syntax is as follows: 

TM TCPIP ADD

Add TCP/IP Configuration for Remote JESplex

The TM TCPIP ADD statement specifies TCP/IP information that is used to connect to BMC ThruPut Manager on the named Sysplex/JESplex.  

The TM TCPIP ADD syntax is as follows: 

TM TCPIP SET

Define TCP/IP Port for BMC ThruPut Manager

The TM TCPIP SET statement specifies the port used on the local BMC ThruPut Manager to receive data from JESplexes in other Sysplexes.  

The TM TCPIP ADD syntax is as follows: 

The port number assigned to the BMC ThruPut Manager started task used to receive data from instances of BMC ThruPut Manager in other Sysplexes.

TM TRACE

Enable/Disable Tracing

This statement activates and deactivates the BMC ThruPut Manager tracing facility. The options described here allow you to trace installation exit activity. The trace facility can also be used to gather data for problem reporting, but these options should only be activated on the explicit instructions of Customer Support, therefore they are not documented here. If there is a need for this capability, Customer Support will provide the specific commands you should use.  

The TM TCPIP ADD syntax is as follows: 

Required keywords to enable tracing of BMC ThruPut Manager installation exits.

Tracing for TMSS exits (10 through 18, 30, and 31) goes to GTF; therefore, GTF must be active and the GTF trace options include tracing for USR event number 249.

An installation exit must be made eligible for tracing, either through the TM EXIT statement or the TM EXIT command. See the TM EXIT statement description in this section, or the TM EXIT command description in the Operating Guide.

If exit tracing is active for an exit when analysis of a job starts, all calls to that exit for that job are traced, even if an operator command disables tracing before the analysis is finished.

If more than one TM TRACE statement is specified for a system, the last statement is effective. A different TM TRACE statement can be applied to each system by using a FOR group.

TM UNIT HANDLE

Define Unit Name Mapping

This statement allows you to inform BMC ThruPut Manager of unit name changes that occur after the job has been processed by BMC ThruPut Manager. This facility handles situations where DASD poolers or installation exits alter unit names dynamically.  

The TM UNIT HANDLE syntax is as follows: 

TM UNIT HANDLE statements are cumulative.

If more than one TM UNIT HANDLE statement is specified for a particular unit name, the last statement is effective.

TM UNIT SET

Set Default Unit Name

This statement establishes a default unit name to be used when a unit name is required but has not been provided in JCL.

The TM UNIT SET syntax is as follows:  

If more than one TM UNIT SET statement is specified, the last statement is effective.

TM USER

Define User Areas

This statement defines user areas that can be associated with each job. Space is then provided for you to place data. This statement is not accepted within a FOR GROUP.  

The TM USER syntax is as follows: 

TM VTAPE

Define DFSMS DATACLAS for CA-Vtape

This statement is used to indicate the DFSMS DATACLAS used for virtual tape volumes by CA-Vtape (formerly known as SAMS:VTAPE) support.  

The TM VTAPE syntax is as follows: 

TM VTFM

Define VTFM Parameters

This statement is used to indicate the esoteric and generic unitnames, and the subsystem name needed for VTFM support.  

The TM VTFM syntax is as follows: 

Multiple TM VTFM statements are cumulative.

 UCS SET

Adjust Accumulated Queue Time for UCS Held Jobs

UCS allows users to place jobs in either MHS_USER or JTS hold. Since these jobs cannot run until released, the accumulated queue time does not represent a delay in service. The UCS SET initialization statement provides a way to adjust the accumulated queue time for non-SLM jobs that have been placed in MHS_USER or JTS hold. Assuming that a numeric value is specified:

• If the job has not accumulated at least the specified number of hours in the queue, there is no adjustment.
• Otherwise, the specified number of hours is subtracted from the release time, resulting in an apparent more recent arrival time.

The UCS SET syntax is as follows:

Set UDF JES2 Job Number Heading

This TMSS initialization statement sets the column heading that UDF recognizes for the column containing JES2 job numbers.  

The UDF SET syntax is as follows: 

VOL SET

Set Status of Volumes in DASD Volume Table

This initialization statement sets the status of a given DASD volume serial number in the BMC ThruPut Manager DASD Volume Table. This table is used by BMC ThruPut Manager during the Job Analysis process.  

The VOL SET syntax is as follows: 

When more than one entry in the list results in a match, the most specific entry is used. For example, if your list contains the following entries:

RES*  RETIRED
RESB* UNAVAILABLE

A volume with a serial number of RESB40 will be treated as UNAVAILABLE because RESB* is more specific than RES*.

BMC ThruPut Manager automatically detects volumes migrated by DFHSM, therefore you do not need to a VOL SET statement for this environment. BMC ThruPut Managerassumes that the volume serial for the migrated volume will be MIGRAT, which is the default defined by IBM.