Software Access Control_SAC


Relevant to you?

Software Access Control (SAC) is designed to control access to software licensed on certain JESplex members only. SAC makes it very simple to limit licensing while ensuring that all usage is in compliance with the terms of the contract, resulting in significant savings.

How does it work?

At runtime, batch jobs are routed to only the members where the particular product is licensed. For a TSO foreground user, ThruPut Manager intercepts the access request and ensures that the user is running on a licensed member before it allows the request to go ahead.

Setup considerations

Rather than code the conditions to route jobs using regular JAL rules, you set up a table with the software product name and binding agent correspondence and invoke the table by a JAL rule:

JBS BIND FROM_SAC

This externalizes the mapping of the software product name and the associated binding agent. The table can be changed and reloaded without changing the JAL.

Operational considerations

The applicable binding agents are activated on the members where the software is licensed. Jobs requiring that software are automatically routed to the applicable member.

Foreground users are informed via customizable messages that the software is not accessible from the current system, and suggests the appropriate systems where the software is available.

References

See the Job-Binding-Services-System-Programming-Guide for setup and operational information on SAC.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Compuware ThruPut Manager 18.02