How SAC works

SAC uses an installation-generated table (the SAC table) to identify the products that are to be restricted to specific system images. The SAC table links requests to JBS Binding Agents and lets you specify whether the request is failed or allowed to proceed with a warning. You can control requests according to the way they are made. The facilities for TSO are:

  • ISPF_PANEL, to control the invocation of specific ISPF panels.
  • ISPF_PGM, for programs that are invoked only from ISPF.
  • ISPF_COMMAND, for TSO commands issued from ISPF.
  • READY_COMMAND, for programs and commands invoked only from a TSO READY prompt (not under ISPF).
  • COMMAND, for programs and commands that can be invoked from a TSO READY prompt or under ISPF.

The facilities for batch include matches for:

  • Account.
  • Accounting field.
  • DD name.
  • Data set (DS) name.
  • Step library name or LINKLIST.
  • PROCSTEP name.
  • STEP name.

For unusual circumstances, you can use TM DAL to determine the requirements and set a global variable. This takes advantage of the fact that SAC has the ability to test a GLOBAL variable similar to that which exists in JAL. You can then use this variable to route the job accordingly. (See the JAL_GLOBAL keyword.)

The SAC table is normally loaded during TMSS initialization, and links a product to a JBS Binding Agent. TMSS enhancement provides an initialization statement and operator commands to manage the SAC table. It is worth noting at this point that the scope of the SAC table is limited to the scope of the JES2 subsystem that loads it.

For batch, you simply make a reference in JAL to request that the SAC table be used to control the routing of the job. The normal JBS mechanisms do the rest.

  • In the world of TSO, SAC gets control prior to invocation of a product or execution of a command. If a link to one or more Binding Agents is defined in the SAC table for the product or command, all Agents are queried. If at least one of the Agents is active on the ambient system, invocation of the product is allowed.
  • If none of the Agents is active on the ambient system, but at least one of the Agents is defined on any system, installation defined message(s) are issued. Invocation of the product is denied or allowed to proceed with a warning, depending on your settings.
  • If none of the Agents linked to the product are defined, or if the query cannot be answered (BMC ThruPut Manager is unavailable, for example), an error message is issued and the request is denied.


 

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