| [AFFINITY={* | ANY | (member1,member2,...)}]
[,ANALYZER=(aa,nnnnn,mmmmm)
[,CNVTERR={NO | YES | PROC}]
[,COMCHAR=({{chars | / }[,NR] | NONE})]
[,CUSTOM=(UMnnnn,UMnnnn,...,UMnnnn)
[,EDITION=AE]
[,FACTORn={ff.ff | (ff.ff smfid)[,(ff.ff smfid), ...]}
[,HEALTHCHECK={NO | YES}]
[,JECL=({$JCSSTC | $JCSTSO | old-verb1},old-verb2,JES2-action,TMaction)]
[,JECLEXEMPT]
[,NUMINITS=nnnn | NONE | JES2]
[,OPTIONS=(ON(feature1,...,featuren),OFF(feature1,...,featuren))]
[,RECYCLE=(hh,jjjj)]
[,SETUP]
[,TMINITS=(ii,hh,jjjj,aa,nnnnn,mmmmm)]
[,TRACE={NO | YES}]
[,TYPHOLD]
[,TYPSCAN] |
| |
|---|
AFFINITY={* | ANY | (member1,member2,...)} | Specifies to the Job Selector the system affinity for the conversion and Job Analysis process for jobs - *—Sets the affinity for this JES2 member, that is, the system on which the job was submitted
- ANY—Sets the affinity for any eligible JES2 member.
- (member1,member2,...)—Sets the affinity up to 32 valid JES2 member names
Important - If you do not specify AFFINITY, BMC ThruPut Manager takes no action, and the job is selected for analysis on any eligible system. This system might be different from that on which it will run.
- After the job has completed analysis, the job affinity reverts to ANY.
- If you submit the job in an EXEMPT class (no BMC ThruPut Manager processing), the affinity reverts to ANY after conversion is complete.
- If the job contains a /*JOBPARM statement that requests affinity, or if the RDR that processed the job is set to a specific affinity, their values override the AFFINITY value in TMPARM.
For more information, see Job-analysis-affinity. |
ANALYZER=(aa,nnnnn,mmmmm) | (For ThruPut Manager Automation Edition and Automation Edition+ only) Specifies parameters to control dynamic analyzer initiators These parameters are positional and optional. The parentheses must be specified. Use a comma to indicate a missing value. You can omit trailing commas. Specifying ANALYZER=(aa,nnnnn,mmmmm) overrides the specification of TMINITS=(,,,aa,nnnnn,mmmmm). The TMINITS= values are used only if ANALYZER= is not specified. Valid values are as follows: - aa—Specifies the number of dynamic BMC ThruPut ManagerJob Analyzer initiators per 100 jobs in the analysis queue excluding the first 100 jobs. aa is a number from 0 to 99. The default is 0.
- nnnnn—Specifies the minimum number of dynamic BMC ThruPut ManagerJob Analyzer initiators that should always be available for the first 100 jobs in the analysis queue. nnnnn is a number from 0 to 32767. The default is 0.
- If the nnnnn value is 0, then aa specifies the number of dynamic BMC ThruPut Manager Job Analyzer initiators for the first 100 jobs in the analysis queue.
- If the aa value is 0 then the number of dynamic Job Analyzer initiators is fixed at the nnnnn value - because the number of dynamic Job Analyzer initiators cannot increase.
- If both the nnnnn and aa values are 0, then no dynamic Job Analyzer initiators is started.
- mmmmm—Specifies the maximum number of dynamic BMC ThruPut ManagerJob Analyzer initiators that could be started. mmmmm is a number from 0 to 32767. The default is 0.
- If the mmmmm value is 0, then the number of dynamic Job Analyzer initiators is unlimited.
- If the aa value is specified as 0, then the mmmmm value must be 0 (by specification or default), because the number of dynamic Job Analyzer initiators cannot increase.
- If mmmmm value is not 0, it must exceed the nnnnn value by the number specified by aa.
|
CNVTERR={NO | YES | PROC} | Specifies how converter errors are handled for jobs that are transmitted to another node This attribute is useful only for a multi-node or multi-member environment in which systems have asymmetric JCL procedures. Valid values are as follows: - NO—(Default) Specifies that JCL errors detected by the converter should cause the job to fail.
- YES—Specifies that JCL errors detected by the converter are ignored until after JAL processing.
- PROC—Specifies that only PROC–related errors detected by the converter are ignored. The check for this type of error does not occur until the job is selected by the analyzer.
Important Jobs that have been failed by the converter receive a minimal analysis pass. At the end of JAL processing, the job might be bound to an JBS agent, which might allow the job to reconvert and run on another member or node. If this happens the job might remain in the queue on the assumption that the error does not occur at the target node. If the job attempts to run locally, it fails with a JCL error. |
COMCHAR=({{chars | / }[,NR] | NONE}) | Specifies 1 to 8 characters to be used to identify BMC ThruPut Manager commands issued from local consoles to the subsystem interface. You can omit the parentheses if you code only a communication character value or NONE. Valid values are as follows: chars—One to eight of the following characters in any combination. This prefix must not currently exist, or exist as a subset or superset, for any other subsystem.
- NONE—Specifies not to use communication character. Use the z/OS MODIFY (F) command to issue BMC ThruPut Manager commands.
- NR—Specifies not to register the communication character with the z/OS service CPF DEFINE.
The default COMCHAR is / |
CUSTOM=UMnnnn,UMnnnn,...,UMnnnn) | Important These options are non-standard functions. Before activating them, contact with BMC Support. |
| Specifies the following details of an AE (Automation Edition) installation: - Who purchased and installed the AE (Automation Edition) license on every member in the JESPlex
- Who has tried to run AE without having to download and re-install it.
BMC Compuware ThruPut Manager Automation Edition is now the BMC AMI Ops Automation for Batch ThruPut product. Important - After using this attribute, do not remove it. If you do, the setting reverts to SE. Do not migrate all systems in the JESplex at the same time.
- Do not update your JAL to SLM to manage any batch jobs or perform any other setup activity for AE until all systems in the JESplex have been migrated to AE.
|
FACTORn={ff.ff | (ff.ff smfid) [,(ff.ff smfid),...]} | Specifies the normalization factor used to adjust JOB and STEP CPU run times. You can specify up to eight unique FACTORn keywords Valid values are as follows: - ff.ff—Specifies a factor, where 00.00 < ff.ff ≤ 99.99. If the factor is a whole number, you can omit the the decimal point and trailing zeros. Any decimal point must be preceded by at least one digit (for example, 0.11).
- n—Specifies a number from 1 to 8 that identifies the set of normalization factors
- smfid—Specifies the SMF identifier for the system which uses the preceding normalization factor. Using this identifier allows you to have the same TMPARM for systems in the same MAS that require different factors.
Important You can use FACTOR instead of FACTOR1. For more information about this facility, see CPU-capping-and-normalizing. |
| Disables the Health Checks that are added when JES2 is started. By default, BMC ThruPut Manager adds the Health Checks that can be examined under SDSF. |
JECL=({$JCSTSO | $JCSSTC | verb1},verb2,JES2-action,TM-action) | Specifies the BMC ThruPut Manager instance to handle named user JECL statements. You can code this attribute as many times as required to accommodate all your user JECL statements. Make sure that installations that use the $JCSSTC option JES2 initialization statement the CMSC task from any BMC ThruPut Manager dependencies. If it is not excluded, operations are required to respond IGNORE to messages DTM3800A to allow CMSC to continue. BMC ThruPut Manager does not initialize until LMS is initialized via CMSC. Use the following statement to make sure that the task under which LMS starts bypasses TM control: JECL=($JCSSTC,CMSC*,IGNORE,IGNORE), Valid values are as follows: - $JCSTSO—A unique subparameter indicating that this JECL keyword is specifying a JCS batch name to be added to one or more TSUs.
- $JCSSTC—A unique subparameter indicating that this JECL keyword is specifying a JCS batch name to be added to one or more STCs.
- verb1—The first verb to find in the user JECL statement. For example, for a JECL statement /*RESOURCE, verb1 is RESOURCE. This verb is translated or ignored.
- verb2—(Optional) A second verb to handle compound JECL names, representing the second word to find the user JECL statement. Because verb2 Since this is a positional parameter, if you don't include it in the code, you must include an intervening comma.
- JES2-action—One of the following actions that JES2 to take:
- IGNORE—(Default) JES2 does not take any action.
- PROCESS—The JECL statement is passed to JES2 for processing.
- CANCEL—Cancels the job..
- PURGE—Cancels and purges the job
- TM-action—One of the following action that you want BMC ThruPut Manager to take:
- IGNORE—BMC ThruPut Manager does not take any action.
- PROCESS[(PROC)]—(Default) BMC ThruPut Manager processes the statement. If you include the PROC subparameter, the statement is allowed in accordance with the JCL procedures for batch jobs.
- EXIT19[(PROC)]—The JECL statement is presented to BMC ThruPut Manager Exit 19, if the exit is active. If you include the PROC subparameter, the statement is allowed in accordance with the JCL procedures for batch jobs.
- JES2XLATE(new-verb1,new-verb2)—(Optional) Map the statement into a JECL statement. You must provide at least one newVerb value. you can map single verb statement into a two-verb statement, and a two-verb statement into a single-verb statement.
- XLATE(new-verb1,new-verb2)—(Optional) Map the statement into a BMC ThruPut Manager JECL (//*+) statement. You must provide at least one newVerb value.
- newVerb1—(Required) For JECL translation, this indicates the first target verb that will be substituted. To add a batch name to a TSU or STC ($JCSTSO or $JCSSTC was specified), this is the first level of the desired batch name.
- newVerb2—(Optional) For JECL translation, this indicates the second target verb, which is added to the substitution. To add a batch name to a TSU or STC ($JCSTSO or $JCSSTC was specified), this is the second level of the desired batch name.
For more information, see JECL-Reference-Guide. |
| Specifies that BMC ThruPut Manager should usually ignore jobs submitted in Exempt classes, even if they include JECL statements that would otherwise require BMC ThruPut Manager services. Without this keyword, jobs in Exempt classes are examined to determine whether they contain JECL requesting BMC ThruPut Manager services. Exceptions are as follows: - If DCS is installed and Customization Option UM0052 is enabled, even jobs in Exempt classes are managed for data set contention.
- JECL processed by the XLATE/JES2XLATE capability of the JECL keyword of the TMPARM statement continues to be translated.
For more information, see JECL-Reference-Guide. |
| (For ThruPut Manager Automation Edition and Automation Edition+ only) Specifies parameters to control the number of dynamic initiators Specifying NUMINITS=nnnn|NONE|JES2 overrides the specification of TMINITS=(ii). The TMINITS= value is used only if NUMINITS= is not specified. Valid values are as follows: - nnnn—Specifies the maximum number of dynamic initiators that BMC ThruPut Manager is allowed to start. nnnn is a number from 50 to 9999.
- NONE—Specifies that BMC ThruPut Manager is not to start any dynamic initiators.
- JES2—Specifies that the number of BMC ThruPut Manager dynamic initiators started is the number of JES2 initiators defined or 100, whichever is greater. JES2 is the default if the NUMINITS= value is missing, or both NUMINITS= and TMINITS= are not specified.
|
OPTIONS=ON(feature1,...,featuren),OFF(feature1,...,featuren)) | Instructs BMC ThruPut Manager to enable or disable certain features after they are installed. Valid values are as follows: - ON(feature1,...,featuren)—The listed features are enabled.
- OFF(feature1,...,featuren)—The listed features are disabled. It is not necessary to disable components that are not installed.
You can enable or disable the following features: - (BMC AMI Ops Automation for Batch ThruPut and ThruPut Manager Automation Edition+ only) DBS for Drive Booking Services. The default is ON.
- DCS for Dataset Contention Services. The default is ON.
- DJC for Dependent Job Control. The default is ON.
- JBS for Job Binding Services. The default is ON.
- JES3 for JES3 Compatibility Services. The default is OFF.
- JCS for Job Chaining Services. The default is ON.
- JLS for Job Limiting Services. The default is ON.
- JSS for Job Setup Services. The default is ON.
- JTS for Job Timing Services. The default is ON.
- MELLON for Mellon Bank Compatibility. The default is OFF.
- MHS for Multi-Hold Services. The default is ON.
- NET for JES3 //* NET support. The default is OFF.
- (BMC AMI Ops Automation for Batch ThruPut and ThruPut Manager Automation Edition+ only) SLM for Service Level Manager. The default is ON.
- UCS for User Control Services. The default is ON.
- UHS for User Hold Services. The default is ON.
|
| (For ThruPut Manager Automation Edition and Automation Edition+ only) Specifies parameters to control dynamic initiator These parameters are positional and optional. The parentheses must be specified. Use a comma to indicate a missing value. You can omit trailing commas. Specifying RECYCLE=(hh,jjjj) overrides the specification of TMINITS=(,hh,jjjj). The TMINITS= values are used only if RECYCLE= is not specified. Valid values are as follows: - hh—Specifies the initiator recycle time expressed in hours. hh is a number from 0 to 99. The default is 24.
- jjjj—Specifies the number of jobs that must run before BMC ThruPut Manager recycles an initiator. jjjj is a number from 0 to 9999. The default is 1000.
|
| Specifies not to hold jobs that use the /*SETUP statement. The standard /*SETUP message is sent to the console. This attribute does not affect jobs that are exempt from BMC ThruPut Manager processing. The /*SETUP statement functions normally for exempt jobs. If you omit this attribute, jobs with a /*SETUP statement receive standard JES2 processing. Important If you specify this attribute, the message $HASP101 jobname HELD is not issued. For more information, see Job-validation-services. |
TMINITS=(ii,hh,jjjj,aa,nnnnn,mmmmm) | (For ThruPut Manager Automation Edition and Automation Edition+ only) Specifies parameters to control dynamic initiators These parameters are positional and optional. The parentheses must be specified. Use a comma to indicate a missing value. You can omit trailing commas. Valid values are as follows: - ii—When multiplied by 100 specifies the maximum number of dynamic initiators thatBMC ThruPut Manager is allowed to start. If you omit ii or specify it as 0, the number of initiators started is the number of JES2 initiators defined or 100, whichever is greater.
- hh—Specifies the initiator recycle time, expressed in hours. hh is a number from 0 to 99. The default is 24 hours.
- jjjj—Specifies the number of jobs that must run before BMC ThruPut Manager recycles initiators. jjjj is a number from 0 to 9999. The default is 1000.
- aa—Specifies the number of dynamic BMC ThruPut Manager Job Analyzer initiators per 100 jobs in the analysis queue excluding the first 100 jobs. aa is a number from 0 to 99. The default is 0.
- nnnn—Specifies the minimum number of dynamic BMC ThruPut Manager Job Analyzer initiators that should always be available for the first 100 jobs in the analysis queue. nnnn is a number from 0 to 32767. The default is 0.
- If the nnnnn value is 0, then aa specifies the number of dynamic BMC ThruPut Manager Job Analyzer initiators for the first 100 jobs in the analysis queue.
- If the aa value is 0 then the number of dynamic Job Analyzer initiators is fixed at the nnnnn value - because the number of dynamic Job Analyzer initiators cannot increase.
- If both the nnnnn and aa values are 0, then no dynamic Job Analyzer initiators is started.
- mmmmm—Specifies the maximum number of dynamic BMC ThruPut Manager Job Analyzer initiators that should start. mmmmm is a number from 0 to 32767. The default is 0.
- If the mmmmm value is 0, then the number of dynamic Job Analyzer initiators is unlimited.
- If the aa value is specified as 0, then the mmmmm value must be 0 (by specification or default), because the number of dynamic Job Analyzer initiators cannot increase.
- If the mmmmm value is not 0, it must exceed nnnnn by the number specified by aa.
Important BMC ThruPut Manager recycles its initiators based on whichever limit is reached first. Recycling is performed to minimize system pollution. You can alter the recycling parameters with the TM INITS operator command. |
| Specifies the tracing option for JES2 exit routines for BMC ThruPut Manager that are added automatically without an EXIT initialization statement Valid values are as follows: - YES—The tracing option, is applied by default to automatically added exit routines.
- NO—Disables tracing for automatically added exit routines.
|
| Specifies that BMC ThruPut Manager should process jobs that are submitted with TYPRUN=HOLD or any jobs submitted in a class that is marked HOLD by JES2. After Job Analysis, the jobs are put in HOLD status. The installation can alter this status with JAL. If you omit this attribute, jobs submitted with TYPRUN=HOLD receive standard JES2 processing and are held before BMC ThruPut Manager analysis. Important If you specify this attribute, the message $HASP101 jobname HELD is not issued. For more information, see Job-validation-services. |
| Specifies BMC ThruPut Manager to perform JCL analysis for jobs submitted with TYPRUN=SCAN. After the JCL analysis phase, the jobs are not allowed to continue to run. When errors occur, messages appear with the JCL listing. If you omit this this attribute, jobs submitted with TYPRUN=SCAN receive standard JES2 processing and BMC ThuPut Manager does not process jobs, so they do not benefit from the JCL analysis provided by the Job Analyzer. For more information, see Job-validation-services. |