Frequently asked questions
Q: My datacenter has been using ThruPut Manager SE (Standard Edition). We've been using features such as Dataset Contention Services (DCS) and Job Limiting Services (JLS), but they are barely in this space. What happened to them? Can I still use the JAL rules we set up to direct them?
A: Yes, your initial JAL rules continue to be applied as your JAL logic directs. The JAL facilities continues to support all the statements in the JAL Reference space.
Q: This manual is all about setting up ThruPut Manager AE from scratch. My datacenter already has ThruPut Manager SE. How will my setup of TM AE differ from what you've included in this space?
A: Policies and Service Groups are new concepts, unique to TM AE, so you will go through the exact same setup steps outlined in this space, except for some minor variations:
- You have to make provision in your JAL logic for the SLM action statements.
- If you have relied on class-based routing, you would have to use binding agents and add JAL rules to have the same effect.
Q. How are ThruPut Manager AE importance levels different than WLMs?
A. Since most datacenters normally use only two or three WLM Importance levels to differentiate a batch job's "importance", TM AE's five levels, in each queue, allow for finer discrimination and more precise management of your batch jobs.
Q. My operators can't seem to access the Operator Commands Interface of TMISPF dialog - why not?
A. In order to use this facility, the appropriate ISPF data sets must be concatenated during installation. TMISPF uses TSO Extended Consoles to provide some of its functions. This means that TSO sessions that use TMISPF must have the correct authority, since the Extended Console has the authority of the TSO session. To use ThruPut Manager AE operator commands through TMISPF, the TSO session must have SYS authority. To display TM AE information, the session must have INFO authority.