Essential implementation
The essential implementation includes setting service goals for your workload and all the housekeeping tasks to have your workload managed by ThruPut Manager AE. In particular this includes:
- Organizing your batch workload into categories called Service Groups.
- Designing and specifying service goals and the accompanying relative importance levels for the Service Groups within a TM AE Policy.
- Adding the requisite WLM Service Classes.
- Creating the requisite JAL rules.
- Specifying datacenter constraints.
Don’t worry if this list doesn’t mean much to you on the first reading of this manual. All of these topics are covered in this space.
Installation of the product is covered in the Installation Guide.
ThruPut Manager
AE is made up of many features and uses several acronyms that appear in commands, messages and dialogs. See the table below for the ones you will encounter during an essential implementation.
Acronym | Name | Description |
|---|---|---|
SLM | Service Level Manager | The automation engine for ThruPut Manager AE is Service Level Manager (or SLM). This is the heart of ThruPut Manager AE and you find it referred to throughout dialogs, commands and JAL rules. |
JBS | Job Binding Services | JBS agents are used to associate jobs with where, or when, a job can run. You use JBS rules and commands to deal with these agents and the jobs they are associated with. If you used classes to route jobs in the past, you now need an alternate mechanism, and binding agents are an elegant solution. |
DCS | Dataset Contention Services | This service automatically prevents contention from occurring and prioritizes which waiting job gets a data set when it becomes available. You use DCS commands to investigate which jobs are held for which data sets and who is currently using the data set. |
JSS | Job Setup Services | This service automatically prepares jobs to run while they are in the queue, including setting up DFSMShsm and virtual volumes. You use JSS commands to display relevant information. |
MHS | Multi-Hold Services | ThruPut Manager AE places and releases holds on jobs for many reasons. These holds can be initiated by operators, users, and TM AE itself. MHS manages these holds and coordinates TM AE interaction with the JES2 holds for the job. |
JAL | Job Action Language | Use JAL rules to assign jobs to the relevant Service Group. (JAL rules also have many other uses to automate the management of your jobs.) |
UDF | User Display Facility | This facility supplements SDSF displays with ThruPut Manager information. You find references to UDF in the displays and HELP text. |
Keep in mind these acronyms. They are referenced throughout the messages, dialogs, commands and rules you encounter during an essential implementation.
As a
ThruPut Manager
AE user you will encounter frequent references to Production Services, General Services, and Automated Capacity Management (ACM).
Production Services refer to all jobs that are managed by SLM in the Production Services queue. Jobs are managed in this queue when they are assigned to a Production Service Group.
Jobs managed by Production Control Services (PCS) feature, which is specifically designed to manage workloads submitted by CA 7, are also processed in the PS queue. Since PCS also uses SLM, you will find references to it in the SLM dialogs. However, at this time, you can assume references to “Production Control Services” and “PCS” do not apply to you.
General Services refer to all jobs that are managed by SLM in the General Services queue. Jobs are managed in this queue when they are assigned to a General Service Group.
Automated Capacity Management (ACM) is a key elective feature that supports users of IBM’s sub-capacity pricing. The cost savings associated with ACM may be of keen interest to your organization. As a best practice, you will start by implementing the
ThruPut Manager
AE essentials as described in this manual. Once that’s done, the incremental effort to implement ACM is described in the Automated Capacity Management Guide. Accordingly, you can ignore references to Automated Capacity Management in the specification dialogs for now.