This section describes the FOR Group, the syntax for TMSS initialization statements, and each statement in detail.

There are a number of TMSS initialization statements that allow you to customize 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 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.

What follows is a detailed description of all the TMSS initialization statements.

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:

• DEPTH defaults to 25 requests.
• MINDORM defaults to 0; that is, requests are processed immediately.
• MAXDORM defaults to 6000, representing one minute.
• MAXHOLD does not have a default value. See Notes.
• MINHOLD defaults to 50, representing one half of a second.
•  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.  

Represents the number of JES2 action requests that can be queued before the control file Manager waits.

A value from 0 to 100 requests. The default value is 25. A value of 0 means full synchronization.

Represents the time, expressed in 1/100th of a second, that must elapse before the next request is to be serviced.

A value from 0 to 6000, representing up to 1 minute before the next request is to be processed.

Represents the maximum time, expressed in 1/100th of a second, that the system waits (when there are no requests) before ThruPut Manager will access the control file to indicate that it is still active.

A value from 0 to 12000, representing up to 2 minutes. The default value is 6000.

Represents the maximum time, expressed in 1/100th of a second, that the control file Manager holds the control file (after the control record has been read).

This keyword is mutually exclusive with MINHOLD.

A value from 50 to 12000, representing up to 2 minutes.

Represents the minimum time, expressed in 1/100th of a second, that the control file Manager holds the control file (after the control record has been read).

This keyword is mutually exclusive with MAXHOLD.

A value from 0 to 12000, representing up to 2 minutes. The default value is 50.

Unless you have specific requirements, the default value should not be altered.

Allows you to control the way that JBS and JLS jobs are held.

Indicates that JBS and JLS jobs are to be held by removing their system affinity.

Indicates that JBS and JLS jobs are to be held using ThruPut Manager holds. This is the default.

CPS WRITER

Specify CPS Writer Parameters

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

Is a unique name for this CPS Writer. It must be 1 to 8 alphabetic, numeric, or national characters long. This parameter is positional and must be specified.

START | DRAIN

Indicates that this Writer is active when first defined, or after a COLD start (i.e. the Spool File was formatted). This is the default status, and is mutually exclusive with DRAIN.

Indicates that this writer is inactive when first defined, or after a COLD start (i.e. the Spool File was reformatted). This parameter is mutually exclusive with START.

Specifies the number of blank lines printed at the bottom of JVLs produced by this Writer.

nnn must be an integer in the range 0 to 255. The default value is 0.

Directs output to specific console. This keyword is mutually exclusive with the ROUTE keyword. If it is omitted, the Writer uses the ROUTE keyword or its default.

Specifies a console name that identifies the console this Writer uses to print Volume Lists.

Specifies the destinations to be selected by this Writer. The default destination is MVL.

Specifies one or more Destinations that this Writer will select. Destinations are assigned to Volume Lists through JAL.

Specifies the "pacing factor" for this Writer. This is the approximate number of milliseconds per line of output that should elapse between the time printing begins and the time the next Volume List is selected for this Writer. Pacing protects against a sudden influx of Volume Lists depleting the WQEs.

This operand must be an integer in the range 0 to 30000. The default value of 350 is based on the operating speed of a 3287 dedicated to printing Volume Lists. This keyword only applies when a SPOOL File is used. If no spooling is done, this keyword is ignored.

Specifies the page length of Volume Lists printed by this Writer. The page length represents the number of lines that can be printed in a page.

The value must be an integer in the range 0 to 255. If it is omitted, or is specified as 0, no pagination is performed. When PAGELENGTH is not zero, the Writer inserts blank lines at the end of a Volume List to ensure that the number of lines printed is equal to the PAGELENGTH value.

Specifies the MVS route code used for Volume Lists printed by this Writer. This keyword is mutually exclusive with the CONSOLE keyword.

A valid route code.  The default value is 3.

Specifies the number of blank lines printed at the top of Volume Lists.

It must be an integer in the range 0 to 255.  The default value is 0.

DAL LOAD

Load DD Action Language

This statement signals to 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.

Specifies the name of a cataloged data set containing the internal text produced by the Language Processor from your DAL statements.

Specifies a PDS member name. This member contains the DAL internal text produced by the Language Processor from your DAL statements.

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.

Indicates that you want tracing turned on.

This keyword indicates that you want selected job tracing.

Specifies the name of the jobs for which you want to have the DAL execution traced.

You can specify a complete job name, or you can use the form JOBNAME(ABC*). In this case, any job which has a jobname starting with the letters ABC will be traced.

This keyword restricts the actions of the statement to a particular step within the jobs being traced. If this keyword is not specified, all steps are affected. This keyword is not valid unless accompanied by the JOBNAME keyword.

A step number. Step numbers are relative to the beginning of the job and start at 1.

Note that the specified step is traced for all jobs being traced.

Turns DAL tracing ON or OFF for any job that encounters an error. Note that only the first error is traced.

Self-explanatory.

DCS SET

This TMSS initialization statement sets some global defaults for DCS.

Specifies the default destination for an ALERT. This value is used when a JAL or JECL ALERT request did not specify a destination.

If this keyword is not specified in the initialization statement the default value is DCSALERT.

A valid destination name.

Specifies the time, in minutes, after which an ALERT Bulletin is to be written. This value is used when a JAL or JECL ALERT request did not specify a time value.

If this keyword is not specified in the initialization statement the default value is 10 minutes.

A value from 1 to 999 representing the number of minutes.

Enables the automatic freeing of data sets that are allocated to the job submitter TSO session.

Controls data set reservation processing support by DCS.

Indicates that DCS should not obtain an ENQ during job initiation for the absolute data set name associated with a generation data set, or the real data set name associated with an alias. This is the default.

Indicates that DCS should obtain an ENQ during job initiation for the absolute data set name associated with a generation data set, or the real data set name associated with an alias. See Notes for additional information.

This parameter specifies the number of jobs that can wait in an initiator in CLAIM mode. The value applies to a JES2 node. If you have multiple JES2 nodes in your DCS complex, then you can assign different values to each node; however, all systems in a JES2 node must have the same value.

If this keyword is not coded, there is no limit to the number of jobs that can wait in initiators.

A value from 1 to 255.

This parameter is mandatory in MIM environments. It provides the name of MIM's address space to DCS.

A 1 to 8 character string representing the name of the started task or job under which MIM runs. In situations where the name varies, you specify a name pattern. For example, you can run MIMSYS1 in one system and MIMSYS2 in a second system. You can simply code MIMSYS* in both systems.

Provides the defaults to NAG TSO holders of data sets needed by a batch job.

A value from 0 to 99 that represents the number of times a TSO user is to be nagged. If 0 is specified, it suppresses default nagging.

If this value is not specified, the default is 3 times.

a value from 1 to 99 that represents the interval, in minutes, between "nags".

If this value is not specified, the default is 5 minutes.

Specifies the default data set service level. If this keyword is not specified, the default is STANDBY.

Can be CLAIM, CONTEND, or STANDBY.

For an explanation of the meaning of the different service levels refer to Data set Contention Services: System Programming Guide, Chapter 3. Requesting Dataset Service Levels. Unless you have well understood reasons, we recommend that you use the STANDBY default.

Specifies a default destination for all DCS trace statements, including the auto-trace.

A valid destination name. If the specified destination is not valid, $DEFAULT is used instead.

Provides the defaults to NAG TSO holders of data sets needed by a started task.

A value from 0 to 99 that represents the number of times a TSO user is to be nagged. If 0 is specified, it suppresses default nagging.

If this value is not specified, the default is 99 times.

A value from 1 to 99 that represents the interval, in minutes, between "nags".

If this value is not specified, the default is 1 minute.

Controls the use of XCFM support by DCS.

Specifies that DCS is to stop using XCFM for cross-systems communication, i.e. DCS reverts to using the control file.

Specifies that DCS is to start using XCFM for cross-systems communication.

DJC SET

This TMSS initialization statement sets some global defaults for DJC.  

HISTORY_COUNT(n)

Specifies the default for the number of generations of history to keep for a DJC Group.

Is a number from the range 0-9, representing the number of generations to keep. A value of 0 indicates that no DJC Group history is to be kept. If this keyword is not specified, the default value is 1.

Specifies the default number of days that a DJC Group history is to be kept. If this keyword is not specified, the default value is 7.

Is a number from the range 1-365, representing the number of days to keep a DJC Group history.

Indicates that jobs flushed by DJC are to be placed on the JES2 output queue. This keyword is mutually exclusive with PURGE_IF_NOT_RUN, and is the default.

Indicates that jobs flushed by DJC are to be placed on the JES2 purge queue. This keyword is mutually exclusive with OUTPUT_IF_NOT_RUN.

ENDFOR

Control Statement

This statement indicates the end of a FOR Group.  

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 the JES2 MASDEF, as follows:

Represents the data set name of the Alternate control file. It must be cataloged.

The Alternate control file should be used only when "CFM SET XCF_NOTEPAD(ON)" has been specified. In the event of an I/O error to the primary control file, control file data is copied from the XCF_NOTEPAD to the Alternate control file.

The Alternate control file should be allocated in the same way as the primary control file. For more information, see Allocating the CF.

Represents the data set name of the control file. It is dynamically allocated. It must be cataloged.

Represents the number of JES2 action requests that can be queued before the control file Manager waits.

A value from 0 to 100 requests. A value of 0 means full synchronization.

Represents the time, expressed in 1/100th of a second, that must elapse before the next request is to be serviced.

A value from 0 to 6000, representing up to 1 minute before the next request is to be processed.

Represents the maximum time, expressed in 1/100th of a second, that the system waits (when there are no requests) before ThruPut Manager will access the control file to indicate that it is still active.

A value from 0 to 12000, representing up to 2 minutes.

Represents the maximum time, expressed in 1/100th of a second, that the control file Manager holds the control file (after the control record has been read).

This keyword is mutually exclusive with MINHOLD.

A value from 50 to 12000, representing up to 2 minutes.

Represents the time, expressed in 1/100th of a second, that the control file Manager holds the control file (after the control record has been read).

This keyword is mutually exclusive with MAXHOLD.

A value from 0 to 12000, representing up to 2 minutes.

Unless you have specific requirements, the default value should not be altered.

Represents the data set name of the Duplex control file. It must be cataloged. The Duplex control file must be allocated identically to the control file but must be on a different volume.  The volume containing the Duplex ideally should be dedicated to just the Duplex.  If that is not possible, select a low usage volume that is not subject to reserves from other systems.

Specifying this parameter will flag this system as eligible to run the duplex subtask, which copies changes to the Primary control file to the Duplex control file on a set interval.

The Duplex control file is intended to be used if the control file is not useable at ThruPut Manager startup. This can occur when using a control file that was copied on the fly for use in disaster recovery.

If the control file is unusable at startup, use the control file Management Utility to copy the contents of the Duplex to the control file and then restart ThruPut Manager.

Specifies in seconds how often the duplex subtask should copy changes to the Primary control file to the Duplex control file. If not specified, 10 seconds is selected as a default value.

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 may 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. Yiu 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.  

Represents the data set name of the DCS recording file. It is dynamically allocated. It 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.  

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

If this statement is omitted and you are using CPS, 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.  

A required positional parameter which specifies a cataloged data set name for the Volume Information File.

This keyword allows you the specify the time that must elapse before a volume is automatically removed from the VIF.

If you do not code this keyword, the default value is 169 hours. (7 days times 24 hours, plus 1 hour.)

Must be in the range 1 to 999. It represents the number of hours that must elapse before an unreferenced volume is automatically removed from the VIF.

Every time a reference is made to the volume, the elapsed time is reset to zero.

Is the maximum number of entries before the VIF becomes full. This value can be changed only when the VIF is reformatted.

The keyword ENTRY can also be used here.

Must be in the range 1 to 32767.

The default value if this keyword is not present is 7200. (one cylinder of 3380/3390).

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.  

Specifies one or more SMFIDs to be matched.

Represent valid SMFIDs.

Examples:

...
FILE SPOOL SYS2.TMSPOOL
JAL LOAD SYS2.TMJAL(JAL01)
FOR SMFID(SYS1)
       TM UNIT HANDLE(TAPE1) AS(TAPE)
ENDFOR
FOR SMFID(SYS2,SYS3)
       CPS WRITER LIBRARY ...
ENDFOR
VOL SET V(RESB01,RESB02) RETIRED
...

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 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.  

Specifies the name of a cataloged data set containing the internal text produced by the Language Processor from your JAL statements.

Specifies a PDS member name. This member contains the JAL internal text produced by the Language Processor from your JAL statements.

Loads a secondary JAL. See the JAL Compare Facility chapter in the DAL/JAL User Guide for more information.

If no JAL internal text is provided, 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.  

Indicates that you want tracing on.

This keyword indicates that you want selected job tracing.

Specifies the name of the jobs you want to have the JAL execution traced.

You can specify a complete job name, or you can use the form JOBNAME(ABC*). In this case, any job which has a jobname starting with the letters ABC will be traced.

JSS RECALL

Alter the Security Environment for DFSMShsm Recalls

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

Indicates the security environment associated with the batch job which triggered the recalls.

Indicates the security environment associated with the ThruPut Manager started task. This is the default.

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.

PROGRAM_NAMES(program1[,program2,...])

Indicates that you want to bypass allocation processing for the listed programs.

Is a list of one or more program names for which allocation processing is to be bypassed.

Specifies that bypassing allocation processing for HSM data sets with a primary disposition of DELETE is to apply to the listed programs.

Specifies that bypassing tape allocation applies to the listed programs.

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.  

This keyword allows you to alter the default value for AFTERNOON, which is 1300. The value is substituted for the AFTERNOON keyword on the JECL statement /*JTS HOLD_ UNTIL.

The value to be substituted for 1300.

This keyword allows you to alter the default for the job "hold until" time when a /*JTS HOLD_ UNTIL statement does not have a TIME value. The default value is 0800.

The value to be substituted for 0800.

The maximum number of days in the future that a job can be delayed by JTS. The default value for JTS is 60.

The number of days to be substituted for the value 60. The minimum value is 1, the maximum value is 366.

Requests that JTS fail jobs that exceed the maximum number of days (MAXDAYS value). This mode is the default.

This keyword is mutually exclusive with MAXWARN.

Requests that JTS warn jobs that exceed the maximum number of days (MAXDAYS value). A warning message is generated and the /*JTS HOLD_UNTIL statement is ignored. JTS will not manage these jobs.

This keyword is mutually exclusive with MAXFAIL.

This keyword allows you to modify the default value for MORNING, which is 0800. The value is substituted for the MORNING keyword on the JECL statement /*JTS HOLD_ UNTIL.

The value to be substituted for 0800.

Requests that JTS fail jobs that specify a historical (past) date.

This keyword is mutually exclusive with OLDWARN.

Requests that JTS warn jobs that specify a historical (past) date. A warning message is generated and the /*JTS HOLD_UNTIL statement is ignored. JTS will not manage these jobs.

This keyword is mutually exclusive with OLDFAIL.

This keyword allows you to alter the default value for TONIGHT, which is 1830.

This value is substituted for the TONIGHT or NIGHT keyword on the JECL statement /*JTS HOLD_UNTIL.

The value to be substituted for 1830.

SPS DEFINE

SYSOUT Printing Services Options

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

Is a unique name for this definition of SYSOUT characteristics. It must be 1 to 8 alphabetic, numeric, or national characters long. This parameter is positional and must be specified.

Specifies the output class for this SYSOUT definition. This keyword is required.

Is a valid JES2 output class.

Specifies how many copies of the output to print. If this keyword is not specified, SPS generates a single copy.

Is a number in the range 1 to 999.

Specifies the name for special forms on which to print output.

Is a one to four character forms name.

Specifies that the output is to be held after SPS processing and before it is sent to the printer.

Specifies a JES2 destination to which output is sent.

Can be a remote or local terminal, a node, a node and remote workstation, a local device or group of devices, or a node and userid.

Specifies the number of blank lines printed at the bottom of output printed using this SYSOUT definition.

nnn must be an integer in the range 0 to 255. The default value is 0.

Specifies the number of blanks inserted at the left of each line printed using this SYSOUT definition.

nnn must be an integer in the range 0 to 60. The default value is 0.

Specifies the page length of output printed using this SYSOUT definition. The page length represents the number of lines that can be printed on a page.

The value must be an integer in the range 0 to 255. If it is omitted, or is specified as 0, no pagination is performed. When PAGELENGTH is not zero, SPS inserts blank lines at the end of the output to ensure that the number of lines printed is equal to the PAGELENGTH value.

Specifies the number of blank lines printed at the top of the output.

The value must be an integer in the range 0 to 255.  The default value is 0.

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.  

A value from 1 to 9, indicating which table is to be loaded.

Indicates that you want to load the Software Access Control (SAC) table, which links specific program product and commands to JBS Binding Agents.

Specifies the name of the data set where the table is to be loaded from.

The name of the member if the table resides in a PDS.

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.  

This keyword defines to ThruPut Manager the esoteric unit names that must always be served by the Memorex 5400 ATL, regardless of where the volume is located.

Represents a list of one or more actual esoteric unit names, separated by commas.

This keyword indicates to ThruPut Manager the esoteric unit names that are to be served manually regardless of where the volume is located.

Represents a list of one or more actual esoteric unit names, separated by commas.

This keyword indicates to ThruPut Manager the esoteric unit names that are to be used to direct allocation to the Virtual Tape Library.

Represents a list of one or more actual esoteric unit names, separated by commas.

Indicates that 3480 units are not to be considered automated, that is, there are no 3480 units serviced by the automated library.

Indicates that 3490E units are not to be considered automated, that is, there are no 3490E units serviced by the automated library.

Indicates that 3590 units are not to be considered automated, that is, there are no 3590 units serviced by the automated library.

TM BATCH

Submit a Batch of Commands

This statement is used to submit a batch of 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 name of the data set where the commands to be submitted are stored. It can be a sequential or partitioned data set.

If the data set is partitioned, then the member name must be specified.

If this keyword is specified, the commands are displayed before they are executed.

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.

This keyword defines to ThruPut Manager the esoteric unit names that are used for VTS by the IBM 3495 robotic tape library running in BTLS mode.

Represents a list of one or more actual esoteric unit names, separated by commas.

This keyword indicates to ThruPut Manager the library names that are used for VTS by the IBM 3495 robotic tape library running in BTLS mode.

Represents a list of one or more library names, separated by commas.

TM CATALOG SET

Define ThruPut Manager Catalog Search Options

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

Indicates that the Job Analyzer should not terminate analysis of the job when MVS Catalog Management does not respond.

This keyword is mutually exclusive with TIMEOUT and RQ_PRIORITY

Indicates that the Job Analyzer should terminate analysis of the job when MVS Catalog Management has not responded within the time allowed.

This keyword is mutually exclusive with NO_TIMEOUT.

Is from the range 1-99, and specifies the number of minutes the Job Analyzer will wait before terminating a job.

The default value for TIMEOUT is 5 minutes.

Indicates that a job terminated because MVS Catalog Management failed to respond should be assigned a specific JES2 priority when requeued.

If this keyword is omitted, the default requeue priority is 0.

Is a number from the range 1-15, specifying the JES2 priority to be assigned.

TM DLM

Defined DLM Unit Names

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

This keyword defines to ThruPut Manager the esoteric unit names that must always be served by the EMC:DLM, regardless of where the volume is located.

Represents a list of one or more actual esoteric unit names, separated by commas.

This keyword indicates to ThruPut Manager the Storage Groups that are to be for the new EMC:DLM managed volumes.

Represents a list of one or more actual SMS storage groups, separated by commas.

This keyword indicates to ThruPut Manager the IBM tape library names that are to be used to detect existing EMC:DLM volumes.

Represents a list of one or more actual IBM tape library names, separated by commas.

This keyword lets you specify the device type to be used in resource classification.

TM EXIT

Define an Installation Exit

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

Is an exit number, from 1 to 19, 21, 24, or 31. See the Exits: System Programming Guide for detailed descriptions of these exits.

Specifies the name of the module to be given control at the exit point indicated by nn.

Specifies that the exit is loaded and its initial state is active.

This is the default.

Specifies that the exit is loaded but its initial state is inactive. It remains inactive until activated through an operator command.

Specifies that the exit is loaded and its state is permanently active. It cannot be deactivated through the use of the TM EXIT operator command.

This keyword allows you to specify a character string that is passed to the exit at exit invocation time.

A character string up to 255 characters long. If it includes special characters or blanks, it must be enclosed within single apostrophes.

Sets the initial status of this exit as being eligible for tracing.

Sets the initial status of this exit as not being eligible for tracing.

This is the default.

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, as well as which data are to be collected. For a description of how to implement SMF data collection, see SMF Data Collection for Job Analysis.  

Indicates which SMF record is used.

Is a number from the range 128-255.

Indicates that the Job Analyzer is to collect the default SMF data for the Job Analyzer.

Indicates that the Job Analyzer is to collect additional SMF data for the Job Analyzer. See Notes below.

Is a number from the range 1-9, indicating the ThruPut Manager table that contains the token names for data to be collected.

Is a 1-24 character name identifying the portion of the ThruPut Manager table that contains the token names for data to be collected.

Indicates that the DBS application is to collect SMF data. Refer to the Drive Booking Services: System Programming Guide.

Indicates that the DCS application is to collect SMF data. Refer to the Dataset Contention Services: System Programming Guide.

Indicates that a SMF record detailing differences between a Primary and Secondary JAL are to be cut if requested. Refer to the DAL-JAL User Guide.

Indicates that SLM data is to be recorded. For further details, refer to the Setup Guide to ThruPut Manager AE Essentials.

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 ThruPut Manager on the named Sysplex/JESplex.  

IP address of a member of the indicated JESplex. Mutually exclusive with HOSTNAME.

TCP/IP hostname of a member of the indicated JESplex. Mutually exclusive with IP.

Port number assigned to ThruPut Manager on the system associated with the IP address or hostname.

Sysplex name of the remote JESplex

JESplex name of the remote JESplex

TM TCPIP SET

Define TCP/IP Port for ThruPut Manager

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

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

TM TRACE

Enable/Disable Tracing

This statement activates and deactivates the 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.  

Required keywords to enable tracing of 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 chapter, 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 ThruPut Manager of unit name changes that occur after the job has been processed by ThruPut Manager. This facility handles situations where DASD poolers or installation exits alter unit names dynamically.  

Identifies the unit name to be altered.

The unit name as coded in JCL. More accurately, this is the unit name as seen by ThruPut Manager.

Identifies the "new" unit name for Job Analysis purposes.

The "new" unit name.

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.  

Specifies the unit name that is to be used when no unit name is provided in JCL.

Is the default unit name, which must be defined to the system.

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.  

Indicates that you want a user area allocated to each job.

The default value is 100.

Represents the number of bytes to be allocated. It can be from 1 to 255.

Indicates that you want a user area allocated to each volume that is referenced by a job.

The default value is 12.

Represents the number of bytes to be allocated. It can be from 1 to 99.

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.  

This keyword defines to ThruPut Manager the DFSMS DATACLAS used for virtual tape volumes by CA-Vtape support.

Represents a list of one or more DATACLAS names, separated by commas.

This keyword indicates that you want the job's profile to include the physical volumes used to stack the virtual volumes.

Indicates the volumes are to be included and treated as automated (robotic) volumes.

Indicates the volumes are to be included and treated as manual volumes.

TM VTFM

Define VTFM Parameters

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

This keyword defines to ThruPut Manager the esoteric unitname used for virtual tape volumes by VTFM support.

Represents a list of one or more esoteric unitnames, separated by commas.

This keyword defines to ThruPut Manager the generic unitname used for virtual tape volumes by VTFM support.

Represents a list of one or more generic unitnames, separated by commas.

This keyword defines to ThruPut Manager the subsystem name used for virtual tape volumes by VTFM support.

Represents a valid subsystem name.

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.

Is a number ranging from 1-24, indicating the number of hours to be subtracted from the release time to determine the new apparent arrival time for a non-SLM job released from MHS_USER or JTS hold.

Indicates that for a non-SLM job just released from MHS_USER or JTS hold, the arrival time should be reset to the current time.

Indicates that a non-SLM job just released from MHS_USER or JTS hold should retain its original arrival time.

Examples:

Assume JOBA arrives at 8:00 AM but is placed in MHS_USER hold until it is released at 4:00 PM. The initialization statement is:

Because the job has accumulated eight hours of queue time, the value from the UCS SET statement is applied. The release time is decreased by three hours so that the arrival time appears to be 1:00 PM.

Assume JOBB also arrives at 8:00 AM but is released at 10:00 AM. Because less than three hours have elapsed, there is no adjustment.

If there is no UCS SET initialization statement and the UCS SET command has not been issued, there is no adjustment.

When a job is released, UCS applies the UCS SET value specified for the system where the release occurred. Since this could result in asymmetric behavior, we recommend that the UCS SET statement not be included in a FOR Group.

UDF SET

Set UDF JES2 Job Number Heading

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

Specifies the headers that UDF recognizes for the JES2 job number column in UDF displays.

Specifies the spool manager in use at your installation, and can be one of:

Indicates IOF is the spool manager.

Indicates JES Master is the spool manager.

Indicates SDSF is the spool manager.

Indicates CA/Sysview is the spool manager.

Is one or more strings of 1 to 12 characters specifying the headings that the spool manager can use for the JES2 job number column. If the string contains a blank, for example 'JOB ID', it must be enclosed in apostrophes. Specifying more than one string allows UDF to recognize the JES2 job number column in cases where the heading could vary.

Examples:

Here the spool manager is IOF. This statement indicates that the installation has altered the JES2 job number column heading to read JES2 NO.

In this example, the spool manager is CA/Sysview, and UDF is instructed to recognize either JES2# or JOB NUMBERS as the heading for the JES2 job number column.

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 ThruPut Manager DASD Volume Table. This table is used by ThruPut Manager during the Job Analysis process.  

Indicates that a list of DASD volume serial numbers is to be given the status indicated by the keyword following.

Is a list of volume serial numbers. In this list, the wildcard character '*' can be used as part of the volser. To be treated as a wildcard, it must be the last character. When '*' is coded, any volume reference that begins with the characters preceding the '*' results in a match. There must be at least one character preceding the '*'.

If the actual volume serial number you want to code has a trailing asterisk, then you must enclose the volume serial number in apostrophes.

Is the status to be assigned to the volume, and can be one of:

Specifies that when this volume entry is coded as a single VOL=SER entry in JCL, it is to be ignored. This replicates the behavior of the Dummy Storage Group in SMS.

Sets the volume entry as the volume serial number used by your storage management system to detect files that have been migrated. For example, ARCIVE is used for DMS/OS environments.

Sets the volume entry as resident, regardless of physical availability. Such volumes are also treated as already mounted.

Sets the volume entry to indicate that a previously existing online volume has been "retired". Jobs with catalog entries or hard coded values referring to this type of volume are failed with an informative message.

Sets the volume entry as unavailable for use by jobs. Jobs requesting this type of volume are not eligible to be selected for analysis or execution on this system. Once the volume becomes available, the jobs should be released for normal ThruPut Manager processing.

Examples:

In this example any volume that starts with 'RES' or 'MAS' results in a match.

In this case, the first volume serial number in the list is enclosed in apostrophes; therefore is not treated as a wildcard character. For the second element in the list, it is treated as a wildcard character.

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*.

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