Submission and analysis

As part of the setup process you identify the job classes significant to ThruPut Manager:

• The set of job classes from which ThruPut Manager selects for analysis.
• The job class dedicated to the Production Service queue, 1 in the example.
• The job class dedicated to the General Service queue, 2 in the example.
• The job class for the analysis queue, defaults to 9.

With ThruPut Manager AE, your datacenter’s users submit  a job  exactly  as they would in the traditional manner, with the same JCL. If its input job class (the one it’s submitted with) is in the selectable set, it is analyzed by ThruPut Manager in the analysis queue. At the end of analysis, one of three things occurs:

• If the job is to be managed by SLM, the job class  is  changed  to one of the two job classes dedicated to ThruPut Manager AE. Jobs assigned to a PS Group are assigned to the class associated with the PS queue, and, jobs assigned to a GS Group are assigned to the class associated with the GS queue. 
• If the job is not to be managed  by SLM, the  job  class  remains as submitted, (or a datacenter JAL rule may have changed it to another job class) and ThruPut Manager SE processes it.
• The job may be deferred or cancelled by a JAL rule.

While in analysis, ThruPut Manager AE analyzes each job and creates its Job Profile. Regardless of the JCL coded, ThruPut Manager can accurately determine what resources the job requires, and for data set/volume resources, the state they are in, such as archived, in exclusive use, offline and so on. It knows about any DFSMShsm recalls, virtual volume staging, data set enqueues and all tapes required at each step of the job. Then TM AE applies the JAL rules to the job. Typically, the datacenter sets up rules to categorize the job, assign it to a Service Group, and set other values and variables to affect downstream processing. Binding rules are provided to control routing in this two job class environment.