Reflex 80:20 TaskMaster for the automation of HP NonStop
Program Object Executables, Obey Files & TACL Macros
The Reflex 80:20 TaskMaster module allows you to configure HP NonStop Tasks - a collection of executables (object programs, obey files, TACL MACROS) that may be run in a particular pre-defined sequence.
Tasks are object orientated responses to situations that may, if required, encapsulate and re-use the manually initiated macros you already employ. The structured Task facility may be used to solve constantly recurring problems that require lengthy operator intervention, with pre-defined routines that can consequently become part of your automation libraries. A task can be configured to react automatically to a chosen situation or it can be invoked automatically.
In brief, a Task is constructed as follows:
1. The individual Progams, TACL macros, OBEY files or other executable steps, that will make up the Task are defined using the Program definition facility.
2. Once defined, the programs are assembled into a Task by simply dragging them from the Program List view into the Task Configuration view. The Task thus formed will execute in parallel or sequential steps (WAIT or NOWAIT). The task may also be run from the Task Configuration view to allow testing.
3. Using the Reflex 80:20 React Module, you can link the Task to an Action Group, triggered by an EMS event. This will automatically run the Task should the event linked to the Action Group occur. For example, an XPNET station, line or interchange process goes down. (NB. Should the Task fail, Reflex will automatically escalate the event in order to ensure that the failed automation cannot be missed).
TaskMaster - automatic or manual HP NonStop task initiation
The automation engine of the Reflex 80:20 product is known as the TaskMaster.
The Reflex 80:20 Event Monitor can intercept EMS events that describe error conditions that can be corrected programmatically and without manual intervention and the details of this event can be forwarded to the Reflex 80:20 TaskMaster who will oversee the execution of the appropriate automated corrective action.
At some Reflex 80:20 installations, the TaskMaster is used to start up and close down applications based on a specific event being received from an external gateway, so this functionality can deal with more than just corrective action.
The TaskMaster interface to other subsystems is not based on using programmatic interfaces but on launching command line processes using low-level procedure calls.
The command line instructions are defined in the TaskMaster “program” screen. Users have the option of specifying standard run options such as object code, IN, OUT, home terminal, CPU, memory, priority, start-up parameters, file assignments and PARAMs.
Users can also select the User Id that they want the program to run as. Information from an event, such as the subject value, can be extracted and fed back into the command line.
For example, the command SCF START ~subject~, could be used to restart a line automatically once an EMS event had been processed stating that the line was down. The subject value within the event, for example $X2510, would be extracted from the event and used in place of ~subject~. Once programs have been defined, they can be linked together to form a Task.
Once built, the Task can then be assigned one or more owners by the Reflex 80:20 administrator. If you are not an owner, then you cannot execute the Task. Executing a Task manually updates the audit log with a record of who started which Task and when it was started.
Tasks can be executed a number of ways. They can be linked to an event in the Reflex 80:20 event database. If you select a Reflex 80:20 monitored event and then choose the Task option as your reaction, a further screen is displayed and you can select a Task from a pull down list. When this event next occurs, your appointed Task will execute.
It is possible to execute Tasks from an icon button. Tasks can be mapped to object types, so your Reflex 80:20 administrator can create a database that states that my start task for X25 lines is “STARTX25”. Stop Tasks and “other” Tasks can also be configured. When you click on the OverDrive icon you can select the start, stop or “other” option and the allocated Task for this type of object will execute.
Tasks can be executed manually from the Task configuration screen. This type of use can provide Operations staff with access to tested, secure and audited obey file scripts that they can execute as Users other than themselves.
Hardware and software pre-requisites for the Reflex product are detailed below:
• HP NonStop (ServerNet or Integrity platforms)
• Guardian D38 Operating System (or above)
• TMF
• SQL runtime system (SQL/MP runtime), or alternatively, NonStop SQL product
• Pathway (TS/MP)
• TCP/IP
• Non-RDF/DRNET Audited Volume *
* It is recommended that Reflex is installed on a Non-RDF/DRNET Audited Volume. If this is a cause for concern, please contact Insider Technologies Ltd to discuss further.
Reflex is installed using a menu driven TACL macro for easy deployment. The macro will perform checks and output the results of each stage of the Reflex product install so that if problems are encountered they can be resolved easily.
Windows Platform for GUI Install:
• Modern Pentium PC Specification
• 32Mb on-board RAM
• 20Mb free hard disk space
• Minimum 17” monitor recommended
• Graphics Resolution: 1027 x 768 x 16 minimum
• Windows XP, Vista, 7
* For escalation of HP NonStop issues to enterprise management solutions, email or mobile SMS, a dedicated Windows box is required.