Automated Command Center

Through ASI Processing, ACC manages the software that manages the Data Center

ACC Automation Specific Intelligence allows the user to describe what the system must do in standard operational terms, without the requirement to tell ASI how to do those functions.
ASI Processing™ allows proactive automation of any operational function that can be written down – without message dependency. ASI Processing provides an intelligent approach to automating system processes, automatically controlling the operating system, on-line systems, time sharing systems and/or batch applications including Start Up, Damage Assessment, Restart, and Shutdown.

ASI Processing eliminates manual runbooks forever and invokes automation procedures based on:

  1. User Events
  2. Ad Hoc Events
  3. Timed Interval
  4. Job State
  1. System State
  2. Generated Events
  3. Optional Message Interception
  4. Optional Command Interception

How does ASI Processing work?

ASI Processing is comprised of system PROBES and automation DIRECTORS. ASI PROBES interrogate the system status to provide crucial information, triggering powerful ASI automation DIRECTORS to take the appropriate actions.

ASI PROBES interrogate the operating environment and test the system state including:

  1. Device status: Is SYS001 online?
  2. Job status: Is Job in step 7A?
  3. Dataset existence: Does A.B.CYZ exist?
  1. Started Task status: Is NET up?
  2. Time Sharing User status: Is user XYZ logged on?
ASI PROBES determine and control the state of the system without the requirement of message triggering. Should the user desire, message triggering is supported.

ASI DIRECTORS are open ended automation processes that understand and perform the internal functions required to automate systems and applications. ASI DIRECTORS operate independently, responding to system changes, restoring the desired system state, and automating unique functions. ACC provides over 100 sample ASI DIRECTORS for convenience. Simply rearrange or insert the installation unique system, subsystem and task names to completely automate most operational functions. ACC does not require REXX or TSO CLISTs for automation and NO message dependency programming is required!

Counterpart Communications allows a single console to control the functions of multiple processors.

Utilizing ACC Counterpart Communications, decisions made on one system can be based on the events occurring on other systems. ACC Counterpart Communications will:

  1. Monitor multiple systems from a single console
  2. Operate effectively without additional or dedicated hardware
  1. Communicate via VTAM paths OR shared DASD
  2. Use BOTH VTAM and shared DASD
ACC Counterpart Communications allows messages, commands and user generated events to be routed for execution on any system. Events may be identified as “Routed” and special processing invoked, or they can be processed as normal events. An additional routing func ion allows the status of each system to be available to all other systems.

back …