Refine Access Control to Licensed Software and Save
And yet, if you can do it, won’t you make management happy? While the tech work is great, it often isn’t as visible. Saving money always gets recognized.
ThruPut Manager includes Software Access Control (SAC), a facility that enables refined access control to licensed software. Without this facility, it’s easy to make the mistake of running a job on a system that isn’t licensed for a required software, or to run it on a system you choose but that is at variance with the contract. In both cases, it’s going to cost you more money.
Who can keep up with what should run where and how? Systems are so complex today that no one can manage this manually, and coding it job by job is too much trouble. IBM does have some facilities to address this issue but they are cumbersome to setup. SAC ensures that the system routes batch jobs only to licensed JESplex members.
What about TSO?
It also handles TSO users. The software intercepts their access and makes sure that they choose a licensed system.
You simply set up a SAC table with the software product name and the binding agents, and then invoke the table according to a JAL (Job Action Language) rule already established. ThruPut Manager activates binding agents on the JESplex member where the software is licensed.
For a one-time effort, you can be sure that you won’t incur penalties by violating your contracts.
Latest posts by Denise Kalm (see all)
- How Developers Can Boost DevOps Through Automated Batch Processing - December 7, 2017
- How to Control Your CPU Demand and Costs at the Job Level - November 16, 2017
- Why ThruPut Manager Is the Real-time Cost-cutting Robot for You - November 9, 2017