DOCUMENT CONTROL INFORMATION First complete the ‘Summary Info’ dialogue box  (File menu) or ‘Properties’ - Win95,  as follows:    Title:   = Product / Project name    Subject:   = Document reference number    Author:   = Your name    Keywords:   = Electronic document location The detail will be automatically inserted into the document when it is printed, or, Choose ‘Select All’ from the Edit menu, click the right mouse button and select  ‘Update fields’ -Win95 users press F9. REMEMBER - you must complete the Issue/version, status & date fields manually.

 

 

 

 

 

 

 

 

 

 

Reflex 80:20

Installation and

Quick-Start Manual

   Contents

 

1.    Reflex 80:20 Installation Script & Quick-start Overview............. 5

1.1.           Introduction................................................................................................................................................................ 5

2.    Reflex 80:20 Software Installation - TANDEM........................................ 6

2.1.           Overview..................................................................................................................................................................... 6

2.2.           TANDEM Requirements – Hardware.................................................................................................................. 6

2.3.           TANDEM Requirements - Software..................................................................................................................... 6

2.4.           Reflex 80:20 Tandem Software............................................................................................................................. 7

2.5.           Required Guardian User IDs.................................................................................................................................. 7

2.6.           Restoring the Supplied Reflex 80:20 PAK file................................................................................................... 8

2.7.           Restoring the supplied Reflex 80:20 Licence files.......................................................................................... 10

2.8.           Licensing Privileged Reflex 80:20 Software................................................................................................... 11

2.9.           Reconciling the Reflex 80:20 ENSCRIBE Files to your own Environment............................................. 11

2.10.             Reconciling the Reflex 80:20 Edit Files to your own Environment...................................................... 13

2.11.             Setting up the Reflex 80:20 SQL Tables and Compiling.......................................................................... 15

3.    Reflex 80:20 Software Installation - PC.................................................. 19

3.1.           PC Requirements - Hardware.............................................................................................................................. 19

3.2.           PC Requirements - Software................................................................................................................................ 19

3.3.           Reflex 80:20 GUI Client Software...................................................................................................................... 19

3.4.           Reflex 80:20 GUI Client Software Installation............................................................................................... 20

4.    Using Fastpipe to Connect the GUI to the Reflex Pathway....... 21

4.1.           Overview................................................................................................................................................................... 21

4.2.           Configuring Fastpipe for Reflex 80:20 on the Tandem................................................................................ 21

4.3.           Configuring Fastpipe for Reflex 80:20 on the PC.......................................................................................... 23

5.    The Reflex 80:20 EMS Template File and EMS Issues.......................... 26

5.1.           Overview................................................................................................................................................................... 26

5.2.           EMS Template Files Required............................................................................................................................. 26

5.3.           Recommended EMS Template File Installation............................................................................................. 26

5.4.           Provide Reflex 80:20 with Access to the EMS Collector............................................................................... 27

5.5.           Problems with the Reflex 80:20 Event Monitor Filter file........................................................................... 28

6.    Starting the Reflex 80:20 Application...................................................... 29

6.1.           Overview................................................................................................................................................................... 29

6.2.           Tandem Files used for Starting Reflex 80:20 on the Tandem..................................................................... 29

6.3.           Starting up Reflex 80:20 on the Tandem Platform........................................................................................ 29

6.4.           Logon to the Reflex 80:20 GUI client................................................................................................................ 31

7.    Preliminary Configuration after Reflex 80:20 Start-up............. 32

7.1.           Setting up a Reflex 80:20 Administrator.......................................................................................................... 32

7.2.           Setting up Reflex 80:20 Security Classes.......................................................................................................... 33

7.3.           Setting up Reflex 80:20 Users.............................................................................................................................. 34

7.4.           Configuring Reflex 80:20 to use Alternate Collectors.................................................................................. 35

8.    Installing Reflex on Multiple Systems and Using Aliases......... 36

8.1.           Overview................................................................................................................................................................... 36

8.2.           Remote Access for Each Tandem Node in the Network................................................................................ 36

8.3.           Configuring Status Monitor Module for Multiple PC Access...................................................................... 37

8.4.           The PC Network Monitor Initialisation File.................................................................................................... 38

8.5.           The Network Hierarchy SQL Table Configuration....................................................................................... 40

8.6.           Logical Aliases for Tandem Nodes.................................................................................................................... 44

8.7.           Clustering Representation of Tandem Nodes.................................................................................................. 45

9.    Configuring a Nonstop Approach to Fastpipe Connectivity.... 47

9.1.           Overview................................................................................................................................................................... 47

9.2.           Nonstop Fastpipe Configuration on the Tandem............................................................................................ 47

9.3.           Nonstop Fastpipe Configuration on the PC Workstation............................................................................. 49

10.     Auto-detecting Tandem Components and Dashboard................ 50

10.1.             Overview.............................................................................................................................................................. 50

10.2.             Automatically Detecting Tandem Hardware.............................................................................................. 50

10.3.             Monitoring Tandem CPUs and Disks............................................................................................................ 51

10.4.             Viewing System Metrics in Dashboard......................................................................................................... 54

11.     Monitoring Processes Graphically in Status Monitor............. 56

11.1.             Overview.............................................................................................................................................................. 56

11.2.             Reflex 80:20 Process Monitoring Parameters............................................................................................ 56

11.3.             Heartbeat Monitoring of a Tandem Process............................................................................................... 57

11.4.             Monitoring of a Tandem Process Through Status Monitor.................................................................... 61

12.     Monitoring Files Graphically in Status Monitor........................... 65

12.1.             Overview.............................................................................................................................................................. 65

12.2.             Reflex 80:20 File Monitoring Parameters................................................................................................... 65

12.3.             Heartbeat Monitoring of a Tandem File...................................................................................................... 66

12.4.             Monitoring of a Tandem File Through Status Monitor........................................................................... 71

13.     APPENDICES................................................................................................................ 76

13.1.             Activating your Tandem SQL Licence......................................................................................................... 76

13.2.             Merging Reflex 80:20 EMS Templates Reference.................................................................................... 77

13.3.             Administration Parameter Settings and Their Use in Reflex 80:20...................................................... 82

13.4.             Currently Delivered Reaction Event Ranges in the Reflex 80:20 Database........................................ 93

13.5.             Viewpoint^TM Configuration for Copying EMS Events into Reflex 80:20............................................ 96

13.6.             Upgrading your own Reflex 80:20 Product Licences............................................................................... 97

13.7.             Reflex 80:20 PATHWAY Server Configuration........................................................................................ 98

13.8.             Reflex 80:20 PATHWAY Server Descriptions......................................................................................... 101

13.9.             Reflex 80:20 Non PATHWAY processes.................................................................................................... 105

13.10.           Reflex 80:20 Facilities and their Abbreviations...................................................................................... 106

13.11.           Monitoring Reflex 80:20 GUI Client Connectivity with Reflex Ping................................................. 111

TO UPDATE THE TABLE OF CONTENTS Click in the contents field above, it should be grey when selected.  Press F9 Chose required option from the dialogue box, You will need to adjust the margins with the margin markers in the page ruler, or, whilst the table is still selected, choose Style from the Format menu, select TOC1 from the style list and select Apply.

1.                Reflex 80:20 Installation Script & Quick-start Overview

 

1.1.             Introduction

This document details the entire process of installing the Reflex 80:20 product on a nominated Tandem node(s) and PC(s). It has been written in an order that can be followed to allow for a quick-and-easy install of the Reflex 80:20 product.

This document should be read in its entirety before installing the Reflex 80:20 software and amended to reflect your own on-site considerations. It can then be used as a reference to both current and future Reflex 80:20 administrators.

Sections [2] through [6] are provided to give a complete installation of the Reflex 80:20 product on a single node. These sections should be followed in sequence. A summary of the steps is as follows:

·       Installing and configuring the Reflex 80:20 Tandem software

·       Installing and configuring the Reflex 80:20 PC software

·       Configuring the Fastpipe^TM to provide TCP/IP socket connectivity between the Tandem PATHWAY and PC Client

·       Installing the Reflex 80:20 EMS templates

·       Starting the Reflex 80:20 application and the logon process

·       Preliminary configuration for the Reflex 80:20 product and adding users.

 

Some of the other topics discussed in later sections include the following:

·       Setting up security profiles for different users of Reflex 80:20

·       Installing Reflex 80:20 on multiple nodes

·       Configuring a non-stop approach to Fastpipe^TM connectivity via TCP/IP

·       Auto-detecting Tandem components and configuring Dashboard (CPU, Disk, Process Metrics)

·       Monitoring Tandem processes graphically.

·       Monitoring Tandem Files graphically.

 

2.                Reflex 80:20 Software Installation - TANDEM

 

2.1.             Overview

The following sections describe both the requirements and the installation process for the Reflex 80:20 Tandem software. The sections are arranged in sequence to provide for the best and quickest approach to installing the Reflex 80:20 product on the nominated Tandem platform(s).

 

 

2.2.             TANDEM Requirements – Hardware

The Reflex 80:20 product software is compatible with both ‘K’ and ‘S’ NSK platforms.

·       An AUDITED disk with 70Mb of free space.

 

 

2.3.             TANDEM Requirements - Software

The software requirements for the Tandem platform are as follows:

·       Guardian D32 or G series Operating Systems or above, for ‘K’ and ‘S’ series respectively

·       Transaction Monitoring Facility (TMF)

·       PATHWAY (TS/MP)

·       TCP/IP connectivity

·       A non-stop SQL run-time licence or better (SQL/MP run-time)

 

 

 

2.4.             Reflex 80:20 Tandem Software

The Reflex 80:20 Tandem software is provided along with the PC Reflex 80:20 GUI client, on a CD-ROM. The Reflex 80:20 Tandem software is contained in a self-extracting PAK file that is uploaded to the appropriate Tandem platform as a binary file. This is achieved using an appropriate means of data transfer, e.g. FTP, IXF. From here, the Tandem software can be extracted by using the notation given in one of the following sections.

Three Reflex 80:20 sub-volumes are provided in a typical install of the Reflex Tandem software. These are as follows:

·       OBJECT sub-volume which contains all of the Reflex 80:20 Tandem executables

·       DDL sub-volume which contains all of the APIs and data file definitions and EMS template file used by the Reflex 80:20 Tandem software

·       DATA sub-volume that contains all of the SQL and ENSCRIBE files used by the Reflex 80:20 Tandem software.

 

 

A separate floppy diskette will have been provided as part of the Reflex 80:20 product delivery. This will contain the Reflex 80:20 product licence for your particular site (in certain cases, the licence file may have been e-mailed or supplied on CD-ROM). Installation of the licence files will allow Reflex 80:20 to run on a specified Tandem node and CPU type for an agreed contracted period.

The licence files are contained in a self-extracting PAK file. This will be uploaded onto the appropriate Tandem as a binary file and run in the same way as for the Reflex 80:20 Tandem software.

 

2.5.             Required Guardian User IDs

It will be necessary to set-up up to 3 Guardian users as part of the Reflex 80:20 Tandem installation process. Typically, these are as follows:

·       REFLEX.MANAGER (e.g. 80,255) - owns both the OWNER below and one or more Reflex 80:20 USERs below

·       REFLEX.OWNER (e.g. 80,20) - owns all the Reflex 80:20 application files and Reflex 80:20 PATHWAY, and is owned by the MANAGER

·       REFLEX.USER (e.g. 79,1 through 79,10) – any number of users can be set-up to LOGON to the Reflex 80:20 GUI client, and are owned by the MANAGER.

·       REFLEX.OPS (e.g. 79,99) – it would be useful to set-up a Reflex Ops User ID which can be used for users who will not be given any Tandem logon IDs for Reflex 80:20 but will be logged on automatically for ‘read only’ access for viewing purposes only. To cut-down on edits, use the REFLEX.OPS group and user name. This user will be discussed in more detail later in this document. If not requiring an automatic logon to Reflex for read only access then this user does not need to be added or can be added at a later date.

The exact hierarchy adopted will be governed by on-site requirements. Two basic observations should be observed however. These are as follows:

·       Neither SUPER.SUPER or any GROUP managers can be used to start the Reflex 80:20 PATHWAY

·       Once having started the Reflex 80:20 PATHWAY, the owner of the PATHWAY (e.g. REFLEX.OWNER) cannot logon to Reflex using the GUI client.

In a basic Reflex 80:20 Guardian user set-up, there should be a Guardian user who owns the Reflex files and starts the Reflex PATHWAY and one or more Guardian users who have been nominated to logon and use the Reflex 80:20 GUI client.

Set-up a Guardian owner for the Reflex 80:20 software and PATHWAY and at least one user ID. This user will be used later to test the logon screen of the Reflex 80:20 GUI client. Once these Guardian users have been added, move onto the next section.

 

2.6.             Restoring the Supplied Reflex 80:20 PAK file

The Reflex 80:20 Tandem software is contained in a self-extracting PAK file located on the supplied CD-ROM. The naming convention for the PAK file is as follows:

                 RFLX<nn>.100

where <nn> is the version number of the supplied Reflex 80:20 Tandem product software.

The extension ‘100’ is a reminder that when the PAK file has been uploaded to the nominated Tandem node, the code for the file should be altered to ‘100’. This is so that it can be run and extracted into the resulting Reflex 80:20 Tandem application files.

Here are the instructions for uploading and restoring the supplied PAK file from the CD-ROM.

1.     Logon to the nominated Tandem node as the REFLEX.OWNER created in the previous section. It is important that this Guardian user owns the PAK file after it has been uploaded.

2.     Select a data transfer mechanism to transfer the supplied PAK file to the Tandem, e.g. FTP, IXF.

 

3.     With the chosen transfer mechanism, ensure that the BINARY option is selected to upload the PAK file to the Tandem.

4.     Select to put the PAK file to a temporary sub-volume associated with the Reflex 80:20 application, e.g. $<VOLUME>.RFLXTEMP. This sub-volume can then be used to store other installation Reflex files and subsequently be deleted after the Reflex installation has been completed. If this is the same volume that will be used for the eventual Reflex 80:20 application, this volume should be AUDITED.

5.     Initiate the transfer of the PAK file to the Tandem node having located the PAK file on the CD-ROM.

 

 

6.     If not already, logon as the nominated Reflex 80:20 Guardian owner and volume to the temporary sub-volume where the Reflex 80:20 PAK file has been placed.

7.     Using Tandems’ File Utility Program (FUP), type the following command:

RFLXTEMP> FUP ALTER RFLX<nn>, CODE 100                                  [return]

where <nn> is the version of Reflex 80:20 being installed.

 

 

8.     Run the software as follows:

RFLXTEMP> RUN RFLX<nn>, $*.*.*, MAP NAMES ($*.RFDAnn.* TO $<your volume>.RFLXDAT.*, $*.RFOBnn.* TO $<your volume>.RFLXOBJ.*, $*.RFDDnn.* TO $<your volume>.RFLXDDL.*),LISTALL, OPEN, AUDITED, MYID                [return]

 

where ‘nn’ is the release number of Reflex 80:20, e.g. RFDA044, RFOB044, RFDD044.

 

9.     Ensure that the ‘3’ Reflex 80:20 sub-volumes have been extracted and copied onto your audited volume.

 

2.7.             Restoring the supplied Reflex 80:20 Licence files

This is a very similar sequence of steps to that of uploading and extracting the Reflex 80:20 Tandem PAK file in the previous section.

The Reflex 80:20 Licence files are contained in a self-extracting PAK file located on a supplied diskette or CD-ROM (in certain cases, the licence PAK file may have been emailed to you).

Here are the instructions for uploading and restoring the supplied PAK file from the diskette.

1.     Logon to the nominated Tandem node as your nominated REFLEX.OWNER. It is important that this Guardian user own the PAK file after it has been uploaded.

2.     Select a data transfer mechanism to transfer the supplied licence PAK file to a Tandem sub-volume, e.g. FTP, IXF.

3.     With the chosen transfer mechanism, ensure that the BINARY option is selected to upload the licence PAK file to the Tandem.

4.     Select to put the licence PAK file into the temporary sub-volume associated with the Reflex 80:20 application, e.g. $<VOLUME>.RFLXTEMP, created in the previous section.

5.     Initiate the transfer of the licence PAK file to the Tandem node having located the PAK file on the diskette.

6.     If not already, logon as the nominated Reflex 80:20 Guardian owner and volume to the temporary sub-volume where the Reflex 80:20 licence PAK file has been placed.

7.     Using Tandems’ File Utility Program (FUP), type the following command:

RFLXTEMP> FUP ALTER <licence-file>, CODE 100                              [return]

where <licence-file> is the licence PAK file for the version of Reflex 80:20 being installed.

 

 

8.     Run the Reflex 80:20 licence PAK file as follows:

RFLXTEMP> RUN <licence-file>, $*.*.*, MAP NAMES ($*.*.* TO $<your REFLEX volume>.RFLXDAT.*),LISTALL, OPEN, AUDITED, MYID             [return]

9.     Ensure that the licence files have been extracted and copied onto your audited data sub-volume by typing the following:

     RFLXTEMP> VOLUME RFLXDAT                                                          [return]

     RFLXDAT> FUP INFO (LICENCE, FACILDB)                                           [return]

where ‘RFLXTEMP’ is your temporary sub-volume and ‘RFLXDAT’ is your Reflex 80:20 data files sub-volume.

 

2.8.             Licensing Privileged Reflex 80:20 Software

It is necessary to license the Reflex 80:20 Taskmaster code as it can be configured to start-up processes as Reflex 80:20 assigned Guardian User Ids. Since certain devices, processes, communication lines, files have a security setting which requires specific Guardian access, the Taskmaster code may need to start processes with varying levels of security to start, stop or remedy problems with these various components. License the taskmaster code as follows:

1.     Logon as SUPER.SUPER.

2.     Volume to your nominated Reflex 80:20 object sub-volume, e.g. RFLXOBJ.

3.     Type the following command:

     RFLXOBJ> FUP LICENSE TASKMAST                                                   [return]

4.     Log down to you’re nominated Reflex 80:20 owner Guardian User ID, e.g. REFLEX.OWNER.

 

 

2.9.             Reconciling the Reflex 80:20 ENSCRIBE Files to your own Environment

The Reflex 80:20 ENSCRIBE files are delivered containing a default database, which consists of both example data as well as required records to configure the Reflex 80:20 application at start-up.

Some of these records will require amending to point to your own volume and sub-volume references for your chosen Reflex 80:20 location. This can be achieved as follows:

1.     Volume to your elected data sub-volume, e.g. RFLXDAT.

2.     Edit/Tedit the ‘RFDEFS’ file in this sub-volume. The left-hand column (column 9 to 16) contains the before image of volume, sub-volume and process references. This column should not be changed. The right hand column should be edited to point to your own elected node, volume and sub-volumes for the restored Reflex 80:20 application. The text box below shows an example of the ‘RFDEFS’ file. The columns in bold should remain unchanged. The last column (column 17 to 24) should be amended for your site-specific references.

 

 

3. In order to make the changes apply globally to your Reflex 80:20 installation based on the RFDEFS files, a program called RFINSTAL should be run. This program is driven by the entries in the RFDEFS file. The RFINSTAL program is contained in your nominated Reflex 80:20 object sub-volume and can be executed from a TACL prompt as follows:

     RFLXDAT> RUN RFLXOBJ.RFINSTAL / IN RFLXDAT.DATACONF /         [return]

     where    RFLXDAT is your Reflex 80:20 data files sub-volume and

                 RFLXOBJ is your Reflex 80:20 object files sub-volume

The RFDEFS file must be resident in the same sub-volume as the DATACONF file. This will be the case with a standard Reflex 80:20 installation.

The Reflex 80:20 ENSCRIBE files updated by executing this code are as follows:

·         DATACONF

·         ACTCOMM

·         ACTPROC

·         PARACONF

·         PROGCONF

·         STRMCONF

The RFINSTAL program will display each of these files, as they are reconciled with your nominated RFDEFS references. There should be no reported errors at the TACL prompt when this process is completed.

2.10.         Reconciling the Reflex 80:20 Edit Files to your own Environment

A number of edit files are shipped with the Reflex 80:20 product, which contain start-up commands for the Reflex 80:20 application. These files contain references that need to be amended to your own site specific references and requirements. These files are as follows and should be edited as stated.

1.     GETPNAME – This edit file accesses parameters required for the other start-up files listed in this section. It contains a site-specific location for a Reflex 80:20 data file. Change the ‘RFDAnn’ reference between the chevrons to your nominated data files sub-volume, e.g. RFLXDAT. The header of this file contains more information.

2.     PWCONF – this is a major edit file which contains all of the server-class definitions found in Reflex 80:20. This file should be edited to change the ‘RFDAnn’ references to your own site-specific data files sub-volume, e.g. RFLXDAT. The ‘RFOBnn’ references should be amended to point to your own Reflex 80:20 object sub-volume, e.g. RFLXOBJ.

Look for possible process name clashes. All Reflex 80:20 servers are prefixed with ‘RX’, e.g. ‘$RXSM’. These should be kept the same where possible unless installing duplicate Reflex environments on the same system node. In this case, change the second letter, e.g. ‘$R2SM’ or ‘$RYSM’.

Amend the CPU references so that the Reflex 80:20 servers execute in your preferred CPUs.

A TCP/IP stack should be nominated for ITL Fastpipe^TM, to allow data transfer between the GUI client and the Reflex 80:20 Tandem PATHWAY, e.g. $ZTC0. Search on ‘$ZTC0’ and replace this reference with your own nominated TCP/IP stack. This change is discussed in greater detail later. See note below.

 

3.     RSQLDEFS – This file is responsible for loading the Reflex 80:20 SQL Table defines and the Reflex 80:20 Catalog define. Change references to ‘RFDAnn’ to your own nominated Reflex 80:20 data files sub-volume, e.g. RFLXDAT. The header of this file contains more information.

 

4.     RUNCGEN – This edit file contains start-up information for the Reflex 80:20
Command/EMS event generator. Change references to ‘RFDAnn’ to your own nominated Reflex 80:20 data files sub-volume, e.g. RFLXDAT. Change the CPU references to your own nominated CPUs. The header of this file contains more information.

5.     RUNEMON – This is the start-up file for the Reflex 80:20 Event Monitor process which is responsible for reading Tandem EMS events and subsequently initiating the appropriate reaction. Change references to ‘RFDAnn’ to your own nominated Reflex 80:20 data files sub-volume, e.g. RFLXDAT. Change the CPU references to your own nominated CPUs. There is a reference to a ‘home_term’ parameter in this file which should be amended to a terminal reference which is available ‘at all times’, e.g. $VHS.

 

6.     RUNPGEN – This is the start-up file for the Reflex 80:20 paging process which is responsible for initiating various paging requests to pagers. Change references to ‘RFDAnn’ to your own nominated Reflex 80:20 data files sub-volume, e.g. RFLXDAT. Change the CPU references to your own nominated CPUs. The header of this file contains more information.

7.     RUNPMON - This is the start-up file for the Reflex 80:20 process monitor that is responsible for periodically monitoring registered processes at a configurable poll rate. Change references to ‘RFDAnn’ to your own nominated Reflex 80:20 data files sub-volume, e.g. RFLXDAT. Change the CPU references to your own nominated CPUs. The header of this file contains more information.

8.     RUNTASKM - This is the start-up file for the Reflex 80:20 task process that is responsible for initiating registered commands, programs or macros. Change references to ‘RFDAnn’ to your own nominated Reflex 80:20 data files sub-volume, e.g. RFLXDAT. Change the CPU references to your own nominated CPUs. The header of this file contains more information.

9.     FLTCOMP – This file is used as part of the automated build of the Reflex 80:20 EMS filter files. The Event Monitor process uses one of the generated filters to restrict event flow to Reflex 80:20 configured events. Change references to ‘RFDAnn’ to your own nominated Reflex 80:20 data files sub-volume, e.g. RFLXDAT. Change the location of ‘ems^spi^defs’ to your own EMS definition files. This, by default is $SYSTEM. Look for the ‘ZSPIDEF’ sub-volume on your system. The disk volume should be inserted after the ‘ems^spi^defs’ reference.

 

2.11.         Setting up the Reflex 80:20 SQL Tables and Compiling

It is now necessary to include the SQL components of the Reflex 80:20 application. This section is concerned with all the SQL aspects and ensuring that Reflex 80:20 can access the appropriate SQL tables.

Carry out the following steps in sequence:

1.     Logon as your nominated owner of the Reflex 80:20 application files, e.g. REFLEX.OWNER.

2.     Start an SQLCI session by typing the following command:

     RFLXOBJ> SQLCI                                                                                 [return]

3.     At the SQL prompt type the following commands:

     >> CREATE CATALOG \<your system>.$<your volume>.RFLXCAT SECURE “OOOO” ;

     where    <your system> is the system node where Reflex 80:20 resides and

                 <your volume> is the audited disk nominated for the Reflex 80:20 application and

                 RFLXCAT is the name of the sub-volume to contain your Reflex 80:20 SQL                     Catalog tables. Use up to seven characters for this sub-volume name. RFLXCAT                  is the recommendation.

     >> EXIT ;                                                                                              [return]

     This command will take you back to a TACL prompt.

The next step is to edit a file called ‘STATSIN’. This file is contained in your nominated Reflex 80:20 DDL sub-volume, e.g. RFLXDDL. This file contains references to your Reflex 80:20 SQL catalog. It will be necessary to edit the current reference in the file to point to your own catalog. Carry out the following:

4.     Tedit/edit the ‘STATSIN’ file and search on the following string:

                 $data02.

5.     This string occurs ‘5’ times in the STATSIN edit file (excluding any comments). Replace all ‘5’ references to ‘$data02.rfcatNN’ with the volume and sub-volume locations for your own Reflex 80:20 SQL catalog as specified above, e.g. $<your nominated volume>.RFLXCAT.

The ‘STATSIN’ file will be responsible later in the SQL procedures, for specifying statistics to the Reflex 80:20 SQL catalog. This file will ensure that the best access paths to the Reflex 80:20 SQL database are chosen, e.g. key access over sequential, index over primary key.

6.     Next, add the defines for the Reflex 80:20 SQL database. These defines need to be in place as the SQL tables are created using the defines provided. Type the following commands:

RFLXCAT> volume RFLXOBJ                                                               [return]

RFLXOBJ> run RSQLDEFS                                                                  [return]

where   RFLXOBJ is your own nominated Reflex object sub-volume and

           RFLXCAT is your Reflex SQL catalog sub-volume

This will load up the complete set of Reflex 80:20 defines for your current TACL session. It reads the files ‘DATACONF’ and ‘PARACONF’ from your nominated data files sub-volume, for the desired location of your Reflex 80:20 SQL tables and the location of your Reflex 80:20 SQL catalog. These locations were set-up in Section [2.9] above.

 

7.     Start an SQLCI session by typing the following command:

     RFLXOBJ> SQLCI                                                                                 [return]

8.     At the SQL prompt type the following commands:

     >> OBEY RFLXDDL.SQLIN ;

     where    RFLXDDL is the name of the sub-volume which contains your Reflex 80:20
Dictionary files.

     >> EXIT ;                                                                                              [return]

     This command will take you back to a TACL prompt.

 

9.     The above command will have created the entire set of Reflex 80:20 SQL tables and inserted a default delivery database. To check the existence of the new SQL tables type the following:

RFLXDAT> FUP INFO *Q                                                                      [return]

where   RFLXDAT is your own nominated Reflex data files sub-volume

 

 

If only TASKQ and MMQ are shown after issuing the FUP INFO command, re-trace the steps above.

10. Locate the file ‘SQLCI2’ on your Tandem system. This is usually contained on the $SYSTEM.SYSTEM sub-volume.

 

11. This following step adds the required Reflex database statistics to your Reflex 80:20 SQL catalog. Ensure you have your Reflex 80:20 SQL defines loaded by carrying out step [6] above and then start an SQLCI session by typing the following command:

     RFLXOBJ> SQLCI                                                                                 [return]

12. At the SQL prompt type the following commands:

     >> OBEY RFLXDDL.STATSIN ;

     >> EXIT ;                                                                                              [return]

     where    RFLXDDL is the name of the sub-volume which contains your Reflex 80:20
Dictionary files.

     This command will take you back to a TACL prompt.

4.     The last step required for the SQL aspects of the installation is to SQLCOMPILE the Reflex 80:20 SQL embedded executables. An obey file is provided for this. The purpose of this step is to inform the Reflex SQL executables on the location of the Reflex 80:20 SQL database that has been created. The SQL compilation also chooses the best access paths through the newly created database based on statistics provided to the SQL catalog in the previous step. Volume to your Reflex 80:20 object files sub-volume and type the following command:

RFLXOBJ> OBEY RESQLCMP                                                             [return]

 

 

5.     Check the SQL compiles have worked OK by checking the spooler for any errors. The output will be listed as spooler reports SQL1 through to SQLnn.

 

 

3.                Reflex 80:20 Software Installation - PC

 

3.1.             PC Requirements - Hardware

The Reflex 80:20 client GUI software has been developed on an IBM-compatible PC. For optimum performance, it is recommended that the minimum specification of your target machine be as follows:

·       A Pentium II Processor

·       32Mb On-Board Ram

·       At least 20Mb free hard disk space

·       Graphics resolution minimum 1024 x 768 x 16 preferably

·       A 17” or larger colour monitor is also recommended.

 

 

3.2.             PC Requirements - Software

The PC software requirements to run the Reflex 80:20 GUI client are as follows:

·       Microsoft Windows NT workstation 4.0 or Microsoft Windows 95/98/2000

·       TCP/IP connectivity

·       Preferably Service Pack 5 or better (check with ITL if this is an issue)

 

 

 

3.3.             Reflex 80:20 GUI Client Software

The PC Reflex 80:20 GUI client software is provided along with the Reflex 80:20 Tandem software, on a CD-ROM. The naming convention for the GUI client ‘.EXE’ file is as follows:

                 XFP<DD><MM>.exe

where <DD><MM> is the day and month the GUI client software was generated by ITL.

XFP stands for Executable for Fastpipe^TM.

Fastpipe^TM is the standard proprietary TCP/IP socket protocol used as the communication layer between the Reflex 80:20 PATHWAY on the Tandem and the PC Reflex 80:20 GUI client. It is delivered as standard in all Reflex 80:20 deliveries.

The Reflex 80:20 GUI client is written in Visual C++.

 

 

3.4.             Reflex 80:20 GUI Client Software Installation

There now follows a step by step guide to installing the Reflex 80:20 GUI client on a nominated PC.

 

1.       Insert the supplied ITL Reflex 80:20 CD-ROM into the appropriate PC drive.

2.       Navigate to the Reflex 80:20 CD by use of Windows Explorer or Desktop/My Computer.

3.       Locate the ‘XFP<DD><MM>.exe’ contained on the Reflex 80:20 CD.

4.       Double-click on the ‘XFP<MM><DD>.exe’ file to initiate the Reflex 80:20 GUI client installation process.

5.       Click ‘Next>’ on the ‘Welcome!’ message screen.

6.       You will be presented with the ‘Select Destination Directory’ screen. Nominate where you would like to install the Reflex 80:20 GUI client. The default is ‘C:\Program Files\Reflex’.

7.       Click ‘Next>’ after you have entered your preferred directory.

8.       You will be presented with the ‘Select Components’ screen. The ‘Reflex 80:20 Client GUI (Fastpipe)’ option is selected by default. This is all that is required. Click ‘Next>’ on this screen.

9.       Click ‘Next>’ on the ‘Ready to Install!’ screen to initiate the installation of the Reflex 80:20 GUI client.

10.   When the installation has finished, the ‘Installation Completed!’ message screen will be displayed. Click on ‘Finish’ and subsequently click ‘OK’ and re-start the PC.

11.   The Reflex 80:20 GUI client files should be resident in your selected PC directory. This directory will include a number of help files, WAV files, 3 executables (including an UNINSTALL program) and a number of configuration files.

If any problems are reported by this set-up program as part of the installation process then contact Insider Technologies Limited.

	Doc loc:

 

 

 

 

4.                Using Fastpipe to Connect the GUI to the Reflex Pathway

 

4.1.             Overview

Reflex 80:20 uses a proprietary TCP/IP socket protocol called Fastpipe^TM to allow data transfer to occur between the Reflex 80:20 GUI client and the corresponding Tandem Pathway. No other third party data communication layers are supported as of release 4.0 of Reflex 80:20. The setting up of Fastpipe is much simpler than for that of other communication layers and this section describes the configuration required at both the Client and Tandem end.

 

4.2.             Configuring Fastpipe for Reflex 80:20 on the Tandem

It will be necessary to nominate a TCP/IP stack, e.g. $ZTC0, $ZTC1, to allow the GUI client to talk to the Tandem Pathway for Reflex 80:20.

Reflex 80:20 can be configured to talk to alternative TCP/IP stacks to allow for non-stop connectivity thereby providing confidence in any Reflex 80:20 GUI status displays.

It may be necessary to contact your own Tandem systems manager to nominate or configure a TCP/IP stack for Reflex 80:20 to use for data transfer. Setting up TCP/IP stacks is outside the scope of this document. Once having identified a suitable stack, perform the following:

1.     Logon as your nominated owner of the Reflex 80:20 application files, e.g. REFLEX.OWNER.

2.     If not already, volume to your nominated Reflex 80:20 objects sub-volume, e.g. RFLXOBJ.

3.     Edit/Tedit the ‘PWCONF’ edit file.

4.     Search for references to the ‘$ZTC0’ process which is the default TCP/IP stack. Change all references to your own nominated TCP/IP stack. See note below.

5.     Still in the Reflex 80:20 object sub-volume, edit/tedit the file ‘FPINI’. The DEBUG_LEVEL can be incremented to provide increasing numbers of trace messages for troubleshooting connectivity problems. Up to the value of ‘10’ can be specified. The LOG_OPTION can be set to ‘4’ to allow the trace messages to be logged to the $0 EMS collector. Set to ‘2’ and the trace messages will be written to the file ‘FPCLNTLG’ in the Reflex 80:20 object sub-volume.

6.     It is necessary to nominate a Reflex 80:20 port number for the application to connect through. The default is ‘5601’. This should be changed in line with your own TCP/IP SERVICES file based on your own on-site allocation of these port settings. See note below.

 

 

 

4.3.             Configuring Fastpipe for Reflex 80:20 on the PC

This sub-section will provide instructions on configuring the Reflex 80:20 GUI client to point at the appropriate Reflex 80:20 PATHWAY to enable connectivity.

Carry out the following sequence of steps:

1.     Using Windows Explorer or Desktop/My Computer, go to your Reflex 80:20 GUI client PC directory installed in section [3].

2.     Double-click on the file ‘SERVER.ini’ in this directory.

3.     You will be presented with the contents of this file. An example of this file is shown below:

4.     The ‘PortNo’ should be set to your nominated port number above.

5.     The ‘IPAddress’ should be set to the TCP/IP address of the Tandem node on which you installed Reflex 80:20.

6.     The ‘PathmonName’ should be set to the Reflex 80:20 PATHWAY process name specified in section [2.9] above.

7.     The ‘TermName’ should be given a unique identifier (up to 16 characters in total), to identify the workstation uniquely, e.g. DEMO_PC, USER1, JOHN_SMITH, EAST_LONDON. This unique identifier (along with the logged on Guardian user ID will help identify who is doing what in the Reflex 80:20 application).

8.     Make all of the edits and exit having saved the file changes.

9.     Double-click on the ‘REFLEX.EXE’ file in the same directory. The following message will appear:

     If this dialog does not appear, move on to step [11] below.

10. Click ‘OK’ and you will be presented with the Reflex 80:20 main GUI client screen.

11. Click on the ‘Configuration’ menu on the main toolbar of the Reflex 80:20 GUI.

12. Click on the ‘Configure Communications (Fastpipe)’ option under this menu to bring up the ‘Comms Configuration’ dialog.

13. Single-click on the first row specified in the ‘Listeners in Order of Precedence’ part of this dialog.

14. Modify the reference to ‘\UNKNOWN’ in the ‘Selected Listener’ part of this dialog, to the Tandem node Reflex 80:20 has been installed on, e.g. \LIVE, \LONDON.

15. After modifying this reference, click on the AMEND button (tick icon) to amend the record on screen.

16. Click on the ACTIVATE button to write these settings to the ‘SERVER.ini’ file.

17. Exit from this dialog by clicking on the green arrow button to the right of the ACTIVATE button.

18. In the Reflex 80:20 directory on your PC, double-click on the ‘NETMON.ini’ file. You will be presented with the contents of this file as shown below:

19. Edit the ‘Displayed Nodes’ line to a value of ‘1’.

 

20. Under the ‘[NODE 1]’ heading, change the name of the node name from ‘\ITLTECH’ to your own Tandem node being used for this installation, e.g. \LIVE, \TEST. Using multiple nodes will be discussed later in this document.

21. Make all of the edits and exit having saved the file changes.

5.                The Reflex 80:20 EMS Template File and EMS Issues

 

5.1.             Overview

On the Tandem platform, Reflex 80:20 is delivered with an EMS template file. This file contains the informational text that accompanies an EMS event generated by the Reflex 80:20 application. It also contains the CAUSE, EFFECT and RECOVERY information viewable in the detail option for any selected event in an EMS viewing console, e.g. Reflex 80:20 Console, View + Point^TM.

 

5.2.             EMS Template Files Required

The Reflex 80:20 EMS template file is contained in the Reflex 80:20 DDL subvolume, e.g. RFLXDDL, and is called ‘NRESTEMP’. The DDL source for the events is also contained in this sub-volume should you wish to change any of the descriptions. This section concerns itself only with the inclusion of these Reflex 80:20 EMS templates into the main system pool of templates to allow meaningful text to be decoded. The explanatory text will then be available for viewing when the Reflex 80:20 product raises an informational, warning or critical event.

If cause, effect and recovery information texts are required for TANDEM native events, in the Console module of Reflex 80:20 (the EMS viewing console for the Reflex product), then the EVENTTD file should also be included in the template build. This file has a file-code of ‘839’ (as for NRESTEMP), and usually resides on the $SYSTEM volume of your Tandem environment.

 

5.3.             Recommended EMS Template File Installation

It is recommended that you refer to the ‘DSM Template Services Manual – Chapter 6 – installing templates’ Tandem documentation for advice on installing EMS templates into your own Tandem environment.

Also refer to ‘DSM/SCM User’s Guide – Chapter 11 – Activating New Software on a Target System – step [7]’ for documentation on installing EMS templates using the ‘INSTALL^TEMPLATES’ macro.

This macro uses either COUP or SCF depending on whether you are on a ‘K’ or ‘S’ series Tandem node respectively.

See appendices for an overview of EMS template installation on a ‘K’ and ‘S’ series node respectively. This Appendix should only be used as a guide and used in conjunction with the above Tandem documentation to provide an insight into Tandem EMS template installation.

 

5.4.             Provide Reflex 80:20 with Access to the EMS Collector

Before moving onto the next section, Reflex 80:20 requires read/write access to the
primary EMS collector $0.

In order to check whether this is the case, use the ‘EMSCINFO’ command as follows:

1.     Logon to the Tandem node as ‘SUPER.SUPER’ on the node where Reflex 80:20 has just been installed

2.     Type the following command:

>EMSCINFO $0                                                                                    [return]

Your $0 collector information will be provided similar to the following display:

 

3.     If the security string requires altering to provide Reflex 80:20 Event Monitor access, then type the following command:

> emscom $0 security ????

where ‘????’ is your security string, e.g. EMSCOM $0 security NNOO

Failure to alter the EMS collector security may result in ‘EMS procedure error 1031’ followed by the termination of the Reflex 80:20 Event Monitor process (by default $EMON).

Reflex 80:20 also requires the appropriate security to read and write the EMS log-files associated with the $0 collector. The location of these files is also given in the EMSCINFO command.

           

5.5.             Problems with the Reflex 80:20 Event Monitor Filter file

The Event Monitor filter file ECALFOBJ (located in the Reflex 80:20 object sub-volume) was compiled under a D4n.n Guardian operating system. This filter passes only Reflex configured EMS events to the Event Monitor process thereby aiding performance.

Problems used to arise when starting Reflex 80:20 on a version of the operating system prior to D3n.n when a filter built on a D3n.n system was supplied. No problems have been reported for the D4n.n ECALFOBJ filter file supplied to either ‘K’ or ‘S’ series systems.

If an error ‘EMS procedure error 1019’ is reported by the Event Monitor process (by default $EMON), carry out the following steps:

1.     Logon as the Reflex 80:20 owner Guardian User ID, e.g. REFLEX.OWNER.

2.     Volume to your nominated Reflex 80:20 object sub-volume, e.g. RFLXOBJ.

3.     Add a required file define as follows:

RFLXOBJ> add define =INSIDER_REFLEX_DATACONF, class map, file
                                                           RFLXDAT.DATACONF               [return]

     where RFLXDAT is the sub-volume which contains your data files

4.     Type the following command from the object file sub-volume

RFLXOBJ> run rflxcom                                                                         [return]

5.     A command prompt ‘RFLX>’ will be displayed. Type:

RFLX> FILTER COMPILE                                                                      [return]

6.     A message, ‘Filter compilation started, check spooler for output’ will appear. Check spooler for any problems.

 

 

 

 

 

6.                Starting the Reflex 80:20 Application

 

6.1.             Overview

This section describes how to start the Reflex 80:20 application and provides some details on how to check for any problems at start-up.

The Reflex 80:20 application is accessible solely by the Reflex 80:20 GUI client. The green-screen interface is no longer supported and should not be used.

 

6.2.             Tandem Files used for Starting Reflex 80:20 on the Tandem

To start Reflex 80:20 on the Tandem, you need to be resident in your nominated Reflex 80:20 object sub-volume, e.g. RFLXOBJ.

The file in this sub-volume used to start Reflex 80:20 is – ‘RUNRFLX’. This is an OBEY file.

The ‘RUNRFLX’ file executes the following files in sequence:

·       PWCOLD – loads up the Reflex 80:20 PATHWAY with the files specified in the PWCONF file

·       RUNTASKM – starts up the taskmaster module of Reflex 80:20 for initiating tasks either automatically or manually

·       RUNPGEN – starts up the paging code which allows paging through a modem plugged into a specified Tandem port

·       RUNCGEN – starts the command/event generator code of Reflex 80:20 which allows commands to be initiated or EMS events to be raised automatically

·       RUNPMON – starts the process monitor code which can monitor for the existence of Tandem processes for specified time windows at a configurable poll interval

·       RUNEMON – starts the back-bone process of Reflex 80:20, the Event Monitor which acts as a junction point for configured EMS events and relays work to the appropriate reaction processes.

 

6.3.             Starting up Reflex 80:20 on the Tandem Platform

If you have access to an EMS viewing console then it would be worth having it on view when starting Reflex 80:20. Any preliminary problems with licences or security can be readily seen by way of the Reflex 80:20 generated EMS messages. If you have not installed the Reflex 80:20 EMS templates at this point as discussed in section [5] then carry out the following steps (if Reflex 80:20 EMS templates have been installed correctly then move on to step [4]):

1.     Logon as the Reflex 80:20 owner Guardian user ID, e.g. REFLEX.OWNER.

2.     Add a define as follows:

            RFLXOBJ> add define =_EMS_TEMPLATES,
                        class map, file RFLXDDL.NRESTEMP                                       [return]

            where    RFLXOBJ is your object files sub-volume and

                        RFLXDDL is your DDL dictionary sub-volume for Reflex 80:20

3.     Type the following command to start an EMS distributor:

RFLXOBJ> EMSDIST /NAME $STRFX, CPU 1, PRI 1, NOWAIT/ TYPE P,                       COLLECTOR $0, TEXTOUT $S.#STRFX                          [return]

This command will send a copy of EMS events from the current time to the spooler so that you can check for any problems reported by Reflex 80:20 to EMS. The =_EMS_TEMPLATES define set-up in step [2] will ensure that the text of the Reflex 80:20 events is clearly visible.

4.     Go to the Reflex 80:20 object sub-volume and as the Reflex owner Guardian user ID, type the following:

RFLXOBJ> OBEY RUNRFLX                                                                [return]

5.     When the RUNRFLX file has completed, stop the EMSDIST process $STRFX at the TACL prompt and check the spooler for the report #STRFX. This step is only required if not viewing events on an EMS event console.

6.     Typical Problems are indicated by events with SSID – INSIDER.50.nn and the following event numbers:

·       2 (file related error – check security – check SQL compilation)

·       persistent 800 events (PATHSEND error)

·       997 (back-up process failed to start)

·       1500 (licence failure – check licence files security/content)

7.     A good check to see if Reflex 80:20 has started OK is to check for the existence of the Event Monitor process, e.g. $EMON (by default) and the Status Monitor process, $RXSM (by default). If you are not sure what your site specific process names are if you have changed them then type:

RFLXOBJ> status *, prog SRVSMOQ                                                   [return]

RFLXOBJ> status *, prog EVNTMON                                                    [return]

A single process should be running for SRVSMOQ and a primary and back-up for EVNTMON.

 

 

 

 

6.4.             Logon to the Reflex 80:20 GUI client

Having followed section [2] through [6] in sequence of this manual, it is now time to logon to the Reflex 80:20 GUI client.

Carry out the following sequence of steps:

1.     Using Windows Explorer or Desktop/My Computer, go to your Reflex 80:20 GUI client PC directory installed in section [3].

 

2.     Double-click on the file ‘REFLEX.EXE’ in this directory.

3.     All being well, you will be presented with the Reflex 80:20 GUI screen. This will have all the toolbar icons greyed out but the LOGON, HELP and EXIT buttons will appear in coloured mode respectively.

If you are presented with this display then the GUI will have already done a fetch to the Tandem through Fastpipe^TM TCP/IP to assess whether an automatic logon has been enabled.

If you received a message of failure, for example:

Review section [4] to make sure that your TCP/IP configuration is correct.

4.     Click on the green log-on arrow button on the top left of the Reflex 80:20 GUI client. You will be presented with a log-on dialog. Log on to the Reflex 80:20 GUI client using SUPER.SUPER. Initially, SUPER.SUPER Guardian access will be required to set-up other Guardian users to log on to the Reflex 80:20 GUI. Type in ‘SUPER.SUPER’ followed by a password that is the same as the Guardian level password for this super user.

5.     Click the ‘Logon’ button to initiate the log on process. The GUI will access your on-site licences (a message will appear in the bottom left hand corner of the Reflex GUI screen, ‘Attempting Logon………..Retrieving Licensing information……..’).

You should now be presented with all the icons on the main toolbar of the Reflex 80:20 GUI client, having turned from grey to coloured.

7.                Preliminary Configuration after Reflex 80:20 Start-up

 

7.1.             Setting up a Reflex 80:20 Administrator

Having logged onto the Reflex 80:20 application via the GUI client using SUPER.SUPER, the next logical step is to set-up one or more Reflex users. The SUPER.SUPER user has access to the whole of the Reflex 80:20 product and can perform any of the tasks and functions within it. This user has global database update access capability.

Each company has its own site-specific hierarchy of security for the Reflex 80:20 product. These range from a single configured Reflex 80:20 administrator logon to an administrator plus a single logon ID per operator assigned to handle the product.

Reflex 80:20 has a one-to-one relationship between ‘logon ID’ and ‘Guardian user ID’. As can be seen with SUPER.SUPER, the user will be required to type his/her own assigned Guardian user ID in at the Reflex 80:20 logon dialog, and their associated password.

Carry out the following steps to assign a Guardian user ID to use the Reflex 80:20 product:

1.     Logon to the Reflex 80:20 GUI using the SUPER.SUPER Guardian user ID, maximise this screen if not already.

2.     Click on the Admin button of the main toolbar of the Reflex 80:20 GUI, maximise this screen if not already.

3.     Click on the ‘Security Profiles’ tab of the GUI client.

4.     Type a Guardian user ID into the space provided at the top of the dialog, group and name respectively, e.g. REFLEX.ADMIN or your own if you are sanctioned with looking after the administration of the product.

5.     Double-click on the ‘ALLFACIL’ security class, which will change the flag setting from ‘N’ to ‘Y’. Click on the AMEND button on this dialog (the tick icon) to provide the given user with access to the entire product.

6.     A message, ‘User ID Security Profile Amended’ will appear, click ‘OK’ to proceed.

7.     Click the ‘Logon’ button on the main toolbar of Reflex 80:20 at the top left of the GUI client.

8.     Type the Guardian user ID you have just added, e.g. REFLEX.ADMIN and his/her associated password and click ‘Logon’ on this dialog.

You are now logged on as a Reflex 80:20 administrator who is now free to add other users to the Reflex 80:20 product.

 

7.2.             Setting up Reflex 80:20 Security Classes

This sub-section leads on from the previous sub-section and describes how to add Reflex 80:20 security classes that enable the Reflex 80:20 administrator to restrict access to certain regions of the product. These classes can then be assigned to Reflex 80:20 users as described in the next sub-section.

Carry out the following steps in sequence:

1.     Logon to the Reflex 80:20 GUI using the Reflex 80:20 Administrator Guardian user added in the previous sub-section (or SUPER.SUPER if no administrator exists currently), maximise this screen if not already.

2.     Click on the Admin button of the main toolbar of the Reflex 80:20 GUI, maximise this screen if not already.

3.     Click on the ‘Security Classes’ tab of the GUI client. Wait a few moments for the class mnemonics to be listed.

4.     Click the ‘down arrow’ on the right of the blank field at the top of the GUI dialog.

5.     Select the ‘ALLFACIL’ security class by just clicking over the name.

6.     The result of this selection will be a screen of all your facilities being displayed with a flag (on the extreme left) showing a value of ‘Y’. This is the set-up for the ALLFACIL security class.

7.     In order to add another security class, OVERTYPE the name ALLFACIL with a unique reference.

8.     Proceed to double-click on any functions in the list that you want to restrict for a particular class, e.g. if you wish to restrict all but the administrative aspects of Reflex 80:20, you might leave only DFU and DPU set to ‘Y’. This class could be called ‘ADMIN’.

9.     Proceed to add this security class by clicking on the ADD button at the top of this dialog, i.e. ‘+’. Click ‘OK’ to the ‘Security Class Added’ message.

10. Proceed with steps ‘5’ through ‘9’ to add any other security classes. These can be split into areas of Reflex 80:20, e.g. ADMIN, TASKS, STATUS, SERVICE, or by name, e.g. JOHNS, MARKW, SUSANL and so on. See appendices for a description of the 3 letter abbreviations.

 

7.3.             Setting up Reflex 80:20 Users

This sub-section leads on from the previous sub-section and describes how to add Reflex 80:20 users with varying levels of access to the Reflex 80:20 product.

Carry out the following steps in sequence:

1.     Logon to the Reflex 80:20 GUI using the Reflex 80:20 Administrator Guardian user added in the previous sub-section (or SUPER.SUPER if no administrator exists currently), maximise this screen if not already.

2.     Click on the Admin button of the main toolbar of the Reflex 80:20 GUI, maximise this screen if not already.

3.     Click on the ‘Security Profiles’ tab of the GUI client.

4.     Type in the name of a Guardian User ID into the two fields provided, e.g. REFLEX.MARKW, REFLEX.OPS1. This may be the name of an already existent operator who is being given access to the product.

5.     Double-click on an appropriate security class that you wish to assign to this user. The flag setting for this security class will change to ‘Y’. More than one security class can be assigned to a user if required, e.g. STATUS and TASKS.

6.     Click the amend button (the tick icon) to assign a security class to a given Guardian user ID.

7.     Repeat step [4] through [6] to provide different Guardian user Ids with levels of access to the Reflex 80:20 product. Once added, these users will subsequently be able to logon to the product.

7.4.             Configuring Reflex 80:20 to use Alternate Collectors

Reflex 80:20 Event Monitor will take EMS event feeds from the primary collector of the Tandem node, i.e. ‘$0’. Up to 9 other alternate collectors can be configured and monitored for configured EMS events, using the Administration module of Reflex 80:20. Having installed the Reflex 80:20 product, logon to the Reflex GUI client with an appropriate Guardian user ID.

Carry out the following steps to set-up Reflex 80:20 to monitor alternate collectors as well as $0:

1.     Logon to the Reflex 80:20 product with an appropriate Guardian user ID.

2.     Click on the Administration module button on the main toolbar to invoke the administration dialogs. Maximise this screen.

3.     The default tab will be displayed which is the ‘File Alias’ tab that displays all of the files used by the Reflex 80:20 product. Scroll down to the alias name ‘EMONCOL0’.

4.     Double-click on this reference so that it appears in full in the ‘File Alias Details’ part of the dialog.

5.     Using ‘EMONCOL0’ as a template, replace the number ‘0’ with a ‘1’, e.g. EMONCOL1 and subsequently modify ‘\INSIDER.$0’ to your nominated alternate collector keeping your system node reference, e.g. \LIVE.$ALT1.

6.     Change the descriptive text to describe this alternate collector, e.g. this collector receives events from the BASE24 application.

7.     Click the ADD button ‘+’ to add this alternate collector to the Reflex 80:20 configuration.

8.     Click ‘OK’ to the ‘DATACONF record inserted’ prompt.

 

9.     After inserting these DATACONF entries, you must first shutdown then restart the Reflex 80:20 product for the configuration changes to be read and for the alternate collectors to be monitored.

 

 

 

 

8.                Installing Reflex on Multiple Systems and Using Aliases

 

8.1.             Overview

This section covers any extra considerations required to install Reflex 80:20 on more than one Tandem node. Sections [2] through [7] should still be carried out in sequence.

If it is the intention to have all Tandem nodes in a network to be represented in the network view of Status Monitor, then the following sub-sections should be carried out as part of the Reflex installation process.

 

8.2.             Remote Access for Each Tandem Node in the Network

The exercise of installing Reflex 80:20 on more than one Tandem node is simply a case of carrying out sections [2] through [7]. It will be less confusing in the future if the same Guardian User Ids are used on all nodes where Reflex 80:20 in installed. It is imperative that the same user that owns the Reflex Pathway on one node is the same as for all others, e.g. REFLEX.OWNER, and that the password assigned is the same. This user then requires remote access to the other node and vice versa. This allows the network and object status data to be forwarded periodically across expand links to other Reflex applications for maintaining an accurate status view of the network.

Setting up network security is discussed in detail in the ‘Expand Network Management Guide’ TIM manual – Chapter 3.

Here is a summary of the commands required:

1.     Logon as the owner of the Reflex 80:20 Pathway, e.g. REFLEX.OWNER.

2.     In the compass point Tandem network example, the commands would be as follows:

>REMOTEPASSWORD \INSIDER,        password                                  [return]

>REMOTEPASSWORD \NORTH,          password                                  [return]

>REMOTEPASSWORD \SOUTH,          password                                  [return]

>REMOTEPASSWORD \EAST,             password                                  [return]

>REMOTEPASSWORD, \WEST,           password                                  [return]

 

3.      Carry out these commands on all other Reflex 80:20 Tandem nodes in the network.

 

 

8.3.             Configuring Status Monitor Module for Multiple PC Access

Edit the PWCONF file contained in your nominated object sub-volume. Search on the REFLEX-SMON server to locate the comment shown below. Edit the MAXLINKS value based on your own configured Reflex network and potential PCs accessing it.

 

 

Carry out this edit to PWCONF on all other Reflex nodes in the Tandem network.

 

8.4.             The PC Network Monitor Initialisation File

The PC file installed in the Reflex 80:20 PC directory, which is concerned with the network view in Status Monitor is called ‘NETMON.ini’. Double-click on this file in the Reflex directory and you will be presented with a file that looks similar to the following text box. Don’t worry if some fields differ or don’t appear in your initialisation file (e.g. AutoArrangeNodes=N, ClusterFraming=N) as some are set up as part of using the Reflex 80:20 GUI client software and will be discussed later in this section. The poll rate parameter represents how often the local Reflex GUI client network screen will poll for Tandem network status.

The above text box illustrates the required network view for 2 Tandem nodes displayed horizontally and joined by a single line between them, i.e. [\INSIDER]------------[\ITLTECH].

There is no reason why the X, Y co-ordinates can’t be changed such that the 2 Tandem nodes are displayed one on top of the other. Here is an example of a ‘NETMON.ini’ file configuration for 5 Tandem nodes arranged in a star like configuration with one in the centre, i.e.                                           [\NORTH]

                                                                   |

                             [\WEST]----------[\INSIDER] ----------[\EAST]

                                                                   |

                                                     [\SOUTH]

If only 1 single node exists where Reflex 80:20 is installed then just 1 node reference is required in the ‘NETMON.ini’ file. Both the displayed nodes and displayed lines parameter at the top of this initialisation file should be set to a value of 1.

    

Setting up this ‘NETMON.ini’ initialisation file will determine the look and feel of the network view of the Reflex GUI on the PC where the edits have been made. If this is the view of the network that you would like all other Reflex users to see on their PCs then take a copy of this file and install it over the ‘NETMON.ini’ on the appropriate PC.

For a partial view of the network where an operator only requires to view a sub-set of the Tandem nodes, take a copy of the full network view file and edit it to show only those required and copy this file over the existing ‘netmon.ini’ file on the nominated PC. In this way different Reflex 80:20 users can see a modified view of the Tandem network, which falls within their marked area of responsibility.

It is imperative that the network set-up dialog in the Reflex 80:20 GUI client matches the node names specified in a complete Reflex Tandem network, e.g. \NORTH, \INSIDER, \EAST, \SOUTH and \WEST if using the above example. This matching is discussed in the next section.

 

8.5.             The Network Hierarchy SQL Table Configuration

A general rule of thumb is that the network configuration set-up for all nodes in a Reflex 80:20 Tandem network (all nodes where Reflex is installed that need to be displayed as nodes on the network screen) should have precisely the same node configuration information. To enable this to occur, the GUI dialog for network set-up should be navigated to for each Reflex 80:20 node. To achieve this, carry out the following steps:

1.     Logon to the Reflex 80:20 GUI client with an appropriate Reflex administrator Guardian user ID.

2.     When the main toolbar is highlighted in colour, click on the menu option ‘Monitor’ and subsequently the ‘Network Setup’ option’.

3.     Maximise the resulting ‘Overdrive Configuration Module’ GUI dialog. This is the dialog that is used to set up the Tandem nodes in the network.

 

4.     Maximise the resulting ‘Overdrive Configuration Module’ GUI dialog. This is the dialog that is used to set up the Tandem nodes in the network.

 

5.     Read all of this point before proceeding to add any network records and moving onto point [6]. Providing an example Tandem network like the compass points network example above, the following field values would be entered on this GUI dialog screen:

Child Node:      \NORTH
Parent Node:    \INSIDER

Click the add button (‘+’) on the dialog toolbar.

Child Node:      \SOUTH
Parent Node:    \INSIDER

Click the add button (‘+’) on the dialog toolbar.

Child Node:      \EAST
Parent Node:    \INSIDER

Click the add button (‘+’) on the dialog toolbar.

Child Node:      \WEST
Parent Node:    \INSIDER

 

Clicking on the ‘Type Setup’ tab and then re-clicking on the ‘Network Hierarchy’ tab to refresh the display, the following records would then be visible.

 

 

 

6.     After setting up your network records for your Reflex installed nodes, click on the ‘!’ icon on the dialog toolbar.

7.     The message below will appear:

            Click ‘OK’ to this message.

8.     The messages for warm-booting both Dashboard and X25 processes will appear.

            Click ‘OK’ to both of these messages.

9.     Logoff the Reflex 80:20 GUI client and logon again as the same Reflex user. If both the network configuration records you have just set-up tally precisely with the ‘NETMON.ini’ records you set up in the previous section, clicking on the ‘Overdrive’ module icon on the main Reflex toolbar should present you with a view of your Tandem network.

 

8.6.             Logical Aliases for Tandem Nodes

It is possible to represent your Reflex 80:20 Overdrive Tandem network using aliases rather than using the physical Tandem node names.

For example, the Overdrive Tandem network:

 

                                                     [\NORTH]

                                                                   |

                             [\WEST]----------[\INSIDER] ----------[\EAST]

                                                                   |

                                                     [\SOUTH]

Might be better represented as follows:

 

                                                     [GLASGOW]

                                                                   |

                             [BRISTOL]------[SALFORD] ------ [YORK]

                                                                   |

                                                     [LONDON]

This can be achieved as follows:

1.     Logon to the Reflex 80:20 GUI client with an appropriate Reflex administrator Guardian user ID.

2.     When the main toolbar is highlighted in colour, click on the menu option ‘Monitor’ and subsequently the ‘Network Setup’ option’.

3.     Maximise the resulting ‘Overdrive Configuration Module’ GUI dialog. This is the dialog that is used to set up the Tandem nodes in the network.

4.     Double-click on the CHILD node you wish to alias. This will be the name of the node in the column on the extreme left of the network list.

5.     Type in the name of the alias you wish to use (up to 20 characters) and subsequently click on the amend button (the ‘tick’ icon) on the GUI dialog.

6.     Repeat steps [4] and [5] for any other nodes you wish to use a node alias for.

7.     After setting up your chosen aliases for your Reflex installed nodes, click on the ‘!’ icon on the dialog toolbar.

8.     The message below will appear:

            Click ‘OK’ to this message.

9.     The messages for warm-booting both Dashboard and X25 processes will appear.

            Click ‘OK’ to both of these messages.

 

 

10. Logoff the Reflex 80:20 GUI client and logon again as the same Reflex user. Clicking on the ‘Overdrive’ module icon on the main Reflex toolbar should present you with a view of your Tandem network with the physical node names changed to the alias names set-up above.

11. Repeat for all the remote Reflex installations on the network by clicking on the ‘Facilities’ function above the Reflex toolbar and selecting the required node (or pointing your GUI at the desired node TCP/IP address by changing SERVER.ini) and carrying out step [1] through [10].

 

 

8.7.             Clustering Representation of Tandem Nodes

This section is only relevant if you have Tandem clusters with Reflex 80:20 installed, i.e. a physical Tandem box with more than 1 system housed within it – one physical box to many logical systems. The configuration for this will result in a representation of 2 or more Tandem nodes within a larger box that will be entitled with the cluster name. Any number of clusters can be represented on the Overdrive network screen of Reflex 80:20.

If you wish to represent more than one Tandem system, e.g. [\INSIDER]…….[\ITLTECH] within a cluster representation, carry out the following steps;

 

1.     Logon to the Reflex 80:20 GUI client with an appropriate Reflex administrator Guardian user ID.

2.     When the main toolbar is highlighted in colour, click on the menu option ‘Monitor’ and subsequently the ‘Network Setup’ option’.

3.     Maximise the resulting ‘Overdrive Configuration Module’ GUI dialog. This is the dialog that is used to set up the Tandem nodes in the network.

4.     Double-click on the CHILD node you wish to include within a cluster. This will be the name of the node in the column on the extreme left of the network list.

5.     Type in the name of the cluster you wish to use (up to 20 characters) and subsequently click on the amend button (the ‘tick’ icon) on the GUI dialog. This is purely a free text field to allow you to provide a general cluster name e.g. LONDON-CLUSTER

6.     Repeat step [4] and [5] for any other nodes you wish to use a node cluster for. Using the same cluster name again will mean that the child node will be inserted into a cluster box on the network display.

7.     After setting up your chosen aliases for your Reflex installed nodes, click on the ‘!’ icon on the dialog toolbar.

8.     The message below will appear:

            Click ‘OK’ to this message.

9.     The messages for warm-booting both Dashboard and X25 processes will appear.

            Click ‘OK’ to both of these messages.

10. Go to the PC directory where you installed Reflex 80:20 and edit the ‘NETMON.ini’ file in this directory and set the cluster flags at the top of this file as follows:

 

11. Logoff the Reflex 80:20 GUI client and logon again as the same Reflex user. Clicking on the ‘Overdrive’ module icon on the main Reflex toolbar should present you with a view of your Tandem network with the node names (or aliases for the nodes) placed inside a cluster box.

12. Re-edit your NETMON.ini file to change the actual positions of the nodes within the cluster to your desired look and feel using the appropriate X,Y co-ordinates. See TIP below.

13. If you require lines between system node names in the Network Hierarchy display then refer back to your ‘NETMON_COPY.ini’ file or the examples given above in Section 8.4 to see how this is done.

14. Add in the ‘Displayed Lines’ and ‘Displayed Nodes’ parameter references to this ‘NETMON.ini’ file as shown in section 8.4 but to reflect your own network set-up.

15. Repeat for all the remote Reflex installations on the network by clicking on the ‘Facilities’ function above the Reflex toolbar and selecting the required node (or pointing your GUI at the desired node TCP/IP address by changing SERVER.ini) and carrying out step [1] through [10]. Ensure that the entries for system node references on the remote nodes are identical to those that you have just set-up.

9.                Configuring a Nonstop Approach to Fastpipe Connectivity

 

9.1.             Overview

Reflex 80:20 has been written to cater for numerous disaster-recovery situations required where critical path applications are being monitored. Import/Export and Reconciliation utilities are provided to resolve Reflex 80:20 database issues and back-up connectivity configuration can be put in place for the GUI-Tandem data transfer.

It is essential that GUI products remain functional in the light of connectivity failures, e.g. a TCP/IP process fails on the Tandem. Confidence in a screen displaying the health and status of a critical path system can be achieved with some simple configuration applied to the Fastpipe^TM transport layer of the Reflex 80:20 product.

This section details how to set-up the Reflex product to maintain a constant level of reliable operation in the event of connection failures due to sporadic TCP/IP failure.

 

9.2.             Nonstop Fastpipe Configuration on the Tandem

It will be necessary to nominate a second TCP/IP stack, e.g. $ZTC0, $ZTC1, to allow the GUI client to talk to the Tandem Pathway for Reflex 80:20 in the event of the primary TCP/IP stack failing. The primary TCP/IP stack is the one you nominated in Section [4] of this document.

Reflex 80:20 can be configured to talk to alternative TCP/IP stacks (up to 10 stacks can be configured for the GUI to talk to) to allow for non-stop connectivity thereby providing confidence in any Reflex 80:20 GUI status displays. The primary will be the only one used unless there is failure of this process.

It may be necessary to contact your own Tandem systems manager to nominate or configure a second TCP/IP stack for Reflex 80:20 to use for data transfer in the event of failure on the primary. Setting up TCP/IP stacks is outside the scope of this document. Once having identified a suitable secondary stack, perform the following:

1.     Logon as your nominated owner of the Reflex 80:20 application files, e.g. REFLEX.OWNER.

2.     If not already, volume to your nominated Reflex 80:20 objects sub-volume, e.g. RFLXOBJ.

3.     Edit/Tedit the ‘PWCONF’ edit file.

4.     Search for reference to the ‘FASTPIPE-BACKUP’ server, which can be configured as the alternative communication process for the Reflex application. See note below.

 

5.     Take out the comment characters on the left of this ‘FASTPIPE-BACKUP’ server configuration entry (at the start of the ‘RESET SERVER’ line - only a single column of ‘[‘ characters up to and including ‘START FASTPIPE-BACKUP’).

6.     Replace the 2 TCP/IP stack references (i.e. $ZTC1) in this ‘FASTPIPE-BACKUP’ server description to your own nominated secondary TCP/IP stack.

7.     Change the reference to file ‘FPINI’ to state ‘FPINI2’ (this may already be the case). Ensure that the process, sub-volume and CPU references fall in line with your system requirements. Exit from the PWCONF file.

8.     Create a second copy of FPINI and call it ‘FPINI2’ in the object sub-volume and subsequently edit it. The DEBUG_LEVEL can be incremented to provide increasing numbers of trace messages for troubleshooting connectivity problems. Up to the value of ‘10’ can be specified. The LOG_OPTION can be set to ‘4’ to allow the trace messages to be logged to the $0 EMS collector. Set to ‘2’ and the trace messages will be written to the file ‘FPCLNTLG’ in the Reflex 80:20 object sub-volume.

9.     It is necessary to nominate a Reflex 80:20 port number for the application to connect through on the secondary TCP/IP stack. The default is ‘5601’. This should be changed in line with your own TCP/IP SERVICES file based on your own on-site allocation of these port settings. See note below.

 

 

10. In order for this second TCP/IP Fastpipe server to become an active Reflex process, stop and start Reflex 80:20 using the ‘STOPRFLX’ and ‘RUNRFLX’ files in the object sub-volume.

 

9.3.             Nonstop Fastpipe Configuration on the PC Workstation

This sub-section will provide instructions on configuring the Reflex 80:20 GUI client to point at the secondary TCP/IP stack and appropriate Reflex 80:20 PATHWAY. This will enable connectivity to continue in the event of primary TCP/IP stack failure.

Carry out the following sequence of steps:

1.     Double-click on the ‘REFLEX.EXE’ file in the Reflex 80:20 PC directory.

2.     Click on the ‘Configuration’ menu on the main toolbar of the Reflex 80:20 GUI.

3.     Click on the ‘Configure Communications (Fastpipe)’ option under this menu to bring up the ‘Comms Configuration’ dialog.

4.     Single-click on the first row specified in the ‘Listeners in Order of Precedence’ part of this dialog. This gives us a context to overtype. This will not affect your primary TCP/IP port settings.

5.     Modify the reference to the Reflex node you would like to connect to (this should be the same as the primary local node). This should already be the case.

6.     Modify the IP address to the address of the TCP/IP stack you are talking to in the event of primary failure.

7.     Modify the Base Port Number to the one you specified in the FPINI2 file on the Tandem Reflex object sub-volume.

8.     Change the description to ‘Secondary Listener’. The PATHMON name and the TERM NAME should already be correct.

9.     After modifying these references, click on the ADD (‘+’) button to insert the record into the list of listeners.

10. Click on the ACTIVATE button to write these settings to the ‘SERVER.ini’ file.

11. Exit from this dialog by clicking on the green arrow button to the right of the ACTIVATE button.

 

This completes the set-up of the back-up TCP/IP stack. Setting up yet another TCP/IP back-up stack is just simply a case of repeating the instructions given in this section.

10.          Auto-detecting Tandem Components and Dashboard

 

10.1.         Overview

Once the Reflex 80:20 product is up and running and you can successfully logon to the application using the GUI client front-end, we can configure Reflex 80:20 to monitor the CPUs and disks of your Tandem systems. Once these have been set-up, the Dashboard module of Reflex 80:20 will be readily accessible to display CPU usage, disk usage and busy and suspect processes per CPU.

This section is a guide to setting up these Tandem components to be monitored as well as providing a good insight into the general set-up approach usually taken in Reflex 80:20 to monitor other components.

 

10.2.         Automatically Detecting Tandem Hardware

It is possible to automatically discover most of your Tandem hardware components by executing a Reflex program utility at a TACL prompt. Running this program executes a Guardian procedure call (DEVICE_GETINFOBYLDEV_) to retrieve hardware devices.

Each hardware device has an associated device type. If the device type is present in the Reflex SQL table =device_type_table (DEVICEQ) in your data sub-volume, then the retrieved device is inserted into the Reflex object component database. The SQL table the data is inserted into is called the =object_table (OBJECTQ) in the data sub-volume.

 

To run the auto detection facility, logon as the owner of the Reflex 80:20 Pathway and type
the command in the text below:

If any devices are displayed after running the command, that are required to be monitored,
take a note of the device type number and enter the details into the =device_type_table using the SQLCI syntax given in the grey box above.

It is possible to add Tandem components in manually using one of the Reflex GUI dialogs. Using the auto-detect as a first step will cut down on typing later. The auto-detect routine is re-runnable so no objects will be deleted if you run this routine at a later date should you say for example, add new disks or new CPUs.

Carry this auto-detect command out on each of your Tandem nodes where Reflex 80:20 has been installed.

Other auto detection utilities exist and these are detailed in the appendices of the Reflex 80:20 User Manual.

 

10.3.         Monitoring Tandem CPUs and Disks

This section will describe the set-up requirements for setting up disks and CPUs to be monitored in the Status Monitor screen of Reflex 80:20. Carry out the following steps:

1.     Logon to the Reflex 80:20 application using the GUI with an appropriate Reflex administrator user ID.

2.     When the main Reflex 80:20 toolbar has turned from grey to coloured, click on the ‘OD Setup’ button on the main toolbar. Maximise the resulting set-up window.

3.     Along the top of the window will be displayed 15-default icons known as ‘Classes’. These represent a supplied set of sub-systems, e.g. DSK (disks), CPU, DEV (Devices), B24 (Base24). This set is not exhaustive and more can be added later but for the moment, the default set will be sufficient to start adding CPU and disk monitoring.

4.     Left-mouse-click on the ‘DSK’ class and you will be presented with a ‘SM Setup: Add Top Level Group’ dialog box. This will allow you to type the name of a group under which you can represent your various disks.

 

5.     Type a suitable top level group name under which to store the disk objects,
e.g. ** DISKS **. The icon field will already be defaulted to DSK to reflect the class.

6.     Click the ADD button (‘+’) on this dialog. The following dialog will be returned:

7.     Click the ‘OK’ button.

8.     The following informational message will appear:

 

9.     Click on the ‘OK’ button.

10. The set-up screen will be refreshed and the new top level group will be displayed under the DSK class.

11. Repeat step [4] through [10] but rather than using the DSK class, add top-level group name ** CPUS ** under the CPU class.

12. Now we will proceed to drag the disk objects under the ** DISKS ** top level group. Either double-click the ** DISKS ** top level group or single-click on it and subsequently click on the folder icon on the spawned floating toolbar.

13. This will take you to the object set-up window that exists below all top-level groups.

14. This is the window from which you can access all of your auto-discovered Tandem objects. Click the note paper icon just to the left of the ADD button on this dialog. This will get the latest list of Tandem objects regardless of type and subtype. Scroll through these to view the objects detected in the previous section.

15. Click on the down arrow to the right of the type and subtype. This will provide a drop-down list of pre-supplied object types and subtypes.

16. Scroll down to ‘TANDEM_HARDWARE     DISK’ and select this entry by clicking on it.

17. This entry will then replace the currently displayed type and subtype.

18. Check the rightmost pager button ‘By Type and Subtype’ and subsequently re-click on the note paper icon to the left of the ADD button.

19. All of your auto-detected disks will be displayed in the list part of the dialog.

20. We now need to drag-and-drop these Tandem objects into the ** DISKS ** top level group. To do this, click on the window option just above the main Reflex toolbar and subsequently click on ‘Tile Vertical’.

21. What is left to do is just a simple case of dragging-and-dropping the disk objects into the ** DISKS ** group just like dragging files in windows explorer, to folders. Click on a disk and keep your finger on the mouse button and drag the disk object directly over the ** DISKS ** group and let go of the mouse button. Using the SHIFT key on the keyboard also caters for group drag-and-drop.

22. Exit from the 2 windows – the object set-up window and the lower level ** DISKS ** window by clicking either on the green arrow which is rightmost on each of these dialogs, or just use the ‘X’ button on the top right corner of each window.

23. This should just leave the top level set-up window with the list of classes. If you have been over-zealous in shutting down windows in the last step then simply re-click on the ‘OD Setup’ button on the main toolbar of Reflex 80:20, and maximise the resulting window.

24. Carry out step [12] through [23] to set-up your CPU object tree under ** CPUS ** in the same manner as for disks. The type and subtype you should use is ‘TANDEM_HARDWARE     CPU’.

25. Having set-up your DISK and CPU object trees, we now need to warm-boot the Reflex 80:20 application.

 

26. Display the top-level set-up screen of Reflex 80:20. This should already be the case if step [23] was observed above. If not, click on the ‘OD Setup’ button on the main toolbar of Reflex 80:20.

27. Click on the ‘!’ icon at the top left of this window to warm-boot the Reflex 80:20 Status Monitor.

28. The message below will appear:

            Click ‘OK’ to this message.

29. The messages for warm-booting both Dashboard and X25 processes will appear.

            Click ‘OK’ to both of these messages.

30. Exit from this top-level screen by clicking on the green arrow to the right of the yellow question mark (?) icon.

31. Click on the Reaction button on the main toolbar of Reflex 80:20. Maximise the resulting window.

32. Click on the ‘!’ icon at the top middle of the resulting window. We now need to re-build the Event Monitor EMS filter which passes configured EMS events to the monitor process. Pre-supplied with the Reflex 80:20 delivery are the dashboard EMS event ranges for monitoring such states as; CPU above n% busy, disk n% full, process n% busy and so on. The Dashboard module raises these EMS events.

33. Click on the ‘Generate Filter Source’ button to initiate the generation of the Event Monitor filter file. This is a waited operation so wait for the completion message to appear. This will be as follows;

34. Click ‘OK’ on this message.

35. Subsequently click on the ‘Compile Filter Program’ button on this dialog. This is a no-waited option so we will need to go to the spooler to check the compilation has worked successfully. The following message will appear;

36. Two EMS events are now generated (check Reflex Console). The subject is FILTER COMPILE and text is:
REFLEX 80:20 : Filter Compilation - Successful   and
REFLEX 80:20 : Inverse Filter Compilation - Successful

 

37. If the outputs show ‘no errors’ on the last page, go back to the Reflex 80:20 GUI and carry out the final step in this 3-step sequence which is ‘Warm-boot Reaction Servers’.

38. This flushes the Event Monitor of currently configured event ranges causing it to re-read the Reflex 80:20 database for newly configured events and also to re-hook up to the newly created EMS filter object – ECALFOBJ.

39. Check the success of the warm-boot by clicking on the ‘Console’ button on the main toolbar of Reflex 80:20. This is an EMS event-viewing module. Scroll using the scroll bars to view the warm-boot EMS messages generated by the processes CEGEN, PROCMON, EVNTMON and so on.

40. Exit from all of the displayed windows leaving only the Reflex 80:20 main toolbar on display.

We have now set-up the disks and CPUs to be monitored by Reflex 80:20. The dashboard module should now be accessible to view the CPU, process and disk metrics for your Tandem system. This is discussed in the next sub-section.

All of these steps can be carried out on all of your other Reflex 80:20 Tandem nodes (if applicable) by clicking on the ‘Facilities – Select Node’ function above the main toolbar of Reflex. Logon with an appropriate Reflex user ID and proceed to carry out step [2] through [39] again.

 

10.4.         Viewing System Metrics in Dashboard

Once having set-up the disks and CPUs to be monitored, we can now see the results. Carry out the following steps;

1.     Having logged on to an appropriate Reflex Tandem node, click on the ‘Overdrive’ button on the main toolbar.

2.     This will show your network view of the Tandem system if you have more than 1 Tandem node otherwise the node you logged onto will be displayed.

3.     Click on the local Tandem node graphic. Maximise the resulting LIVE Status Monitor window.

4.     Both the ** CPUS ** and ** DISKS ** top-level groups should be visible as set-up earlier. It is possible that one or both will be flashing either RED for critical or BLUE for vulnerable.

 

5.     Exit from this top-level LIVE monitor screen by clicking on the green arrow to the right of the yellow question mark (?) icon.

6.     On the network view of the Tandem system, click on the BAR CHART icon to the right of the monitor icon.

7.     Clicking on a Tandem node while in Dashboard mode will result in the system metrics view for that window being displayed.

8.     From here, having set-up both disks and CPUs to be monitored in the previous section, the various metrics can be viewed.

9.     If remote access has been given to the owner of the Reflex 80:20 Pathways then clicking on remote Tandem nodes in the network view will spawn the CPU, process and disk metrics for those nodes also.

11.          Monitoring Processes Graphically in Status Monitor

 

11.1.         Overview

This section is a step-by-step guide to configuring Tandem processes to be monitored graphically by way of the Status Monitor module. It first details the steps required in setting up a process under the Heartbeat module. This will provide for up and down EMS events to be generated by the Reflex 80:20 process monitor. These events can be seen in any EMS viewing console. The second part of this section shows the steps required configuring the Status Monitor module to display graphically the up and down states of configured processes.

 

11.2.         Reflex 80:20 Process Monitoring Parameters

Before setting up a process to be monitored, it is a useful exercise to look at two of the parameters involved in process monitoring. These parameters can be changed depending on your on-site requirements. Carry out the following actions:

1.     Logon to the Reflex 80:20 application using the GUI with an appropriate Reflex administrator user ID.

2.     When the main Reflex 80:20 toolbar has turned from grey to coloured, click on the ‘Administration’ button on the main toolbar. Maximise the resulting set-up window.

3.     Click on the second tab entitled ‘Parameters’ to bring up the list of parameters used by the Reflex 80:20 product.

4.     Scroll down to the 2 parameters prefixed with ‘PMON-‘. Double-click on the first of these called ‘PMON-MSG-FREQUENCY’. This parameter controls how often the same EMS event is output if a process is found to be in the same state. For example, if a process is in a DOWN state then Reflex will generate a down EMS event (as configured by the user in the next section). If the process is down the next time it polls then the process monitor will not raise another EMS message until it has polled ‘PMON-MSG-FREQUENCY’ number of times at which point, it will raise the down EMS message again. This is to cut down on EMS event pollution on the EMS logs.

Amend the value of the parameter based on your own on-site requirements for reporting failed processes.

5.     Double-click on the parameter ‘PMON-POLL-INTERVAL’ to display the detail of this parameter.

6.     This is the poll interval in seconds that the Reflex 80:20 non-stop process monitor will check the configured processes as to their UP/DOWN status. This is used in conjunction with the ‘PMON-MSG-FREQUENCY’ parameter. The defaults are a frequency of ‘10’ and a poll interval of ‘30’ seconds. The result here would be that a process down would not be re-reported until ’10 * 30’ seconds later, i.e. 5 minutes.

7.     Double-click on any of these 2 parameters and click on the tick icon to amend the value in the ‘Parameter Value’ field. These values will taken on board at the next warm-boot which will be carried out as part of the following sub-section.

 

11.3.         Heartbeat Monitoring of a Tandem Process

This section details the first of two steps in monitoring a Tandem process. The end result of this section will be the raising of a down EMS event if the process disappears from the system and an up EMS event if it is present. Carry out the following steps:

1.     Logon to the Reflex 80:20 application using the GUI with an appropriate Reflex administrator user ID.

2.     When the main Reflex 80:20 toolbar has turned from grey to coloured, click on the ‘Heartbeat’ button on the main toolbar. Maximise the resulting set-up window.

3.     You will be presented with the ‘Process Existence’ window. On the left of the window is the list box that will list any currently configured processes. If this is a full install, no processes will appear in the list and you will be presented with the following message:

     Click ‘OK’ if this message appears.

On the right-hand side of the ‘Process Existence’ window is the detail aspect. On this side, details of Tandem Processes can be entered for monitoring.

 

4.     Type the name of the local node and the process you wish to monitor in the two fields provided at the top of the right-hand side of the window, e.g. \INSIDER  $TEST.

5.     The ‘Start Time’ and ‘End Time’ for monitoring defaults to ’00:00’, ’23:59’ respectively. If you wish to monitor the process only at a specific time in the day, enter the times accordingly.

6.     If the process goes down and later gets brought up, a unique EMS event will be raised to indicate this. This EMS event can be seen on an event-viewing console. The next part of the detail window allows the entering of the subsystem identification (SSID) and event numbers to reflect the up and down states of a given process. Enter the owner field (if you wish it to be different to the default – INSIDER), a value field and unique up and down event numbers for the associated owner field. See TIP below.

 

 

 

7.     The output behaviour of an EMS event can be tailored on the extreme bottom right-hand side of the window. If left at the default, a normal EMS event will be generated for both the UP and DOWN EMS events. However, it is possible to generate CRITICAL events by checking the ‘Emphasis’ pager button or action needed/action completion events if the ‘Action Needed’ or ‘Clear Action’ pager buttons are entered.

 

8.     If you require graphical monitoring of the process you have just entered, check both the ‘Status Monitor Object’ and ‘Configure Action Groups’ fields in the ‘Monitoring’ aspect of the detail window.

9.     When the process you have entered is being monitored by the non-stop process monitor (usually $PMON), the subject token of any event raised is the name of the process, e.g. $TEST. This will be used to map onto any equivalent graphical icon in Status Monitor. This will be discussed later. If you require a different subject token other than the name of the process, enter the value here (up to 24 characters).

10. Following on from point [9], the manager token of all events raised from the Reflex 80:20 process monitor will be set to spaces. If this field is filled in then the manager token will be set to the value entered here.

11. Enter the description field to describe the process that is being monitored, e.g. Application, Tandem. This will aid other Reflex users in the future as well as acting as a reminder for you.

12. Click on the ‘+’ button at the top of the window to enter this process record into the Reflex database. You will be presented with the following message:

Click ‘OK’ to clear the message.

 

13. Exit from the Heartbeat window by clicking on the green arrow to the right of the yellow question mark (?) icon.

14. Click on the Reaction button on the main toolbar of Reflex 80:20. Maximise the resulting window.

15. Click on the second tab entitled ‘Reaction List’. This will provide a list of currently configured EMS event ranges in the Reflex 80:20 database. Some of these events have been pre-supplied as part of a full install of the product.

16. Scroll down the list until you see the SSID and event number(s) you specified for your UP and DOWN EMS event messages for the Heartbeat process you added. You should notice that for your event(s) the column ‘Monitor’ has an asterisk (*) character specified. This has been done because you asked Reflex to automatically configure (using the ‘Configure Action Groups’ option) the Reaction engine with your chosen EMS events. The ‘Monitor’ column is short for ‘Graphical Monitoring in Status Monitor’.

17. Double-click on one of the SSIDs you added earlier. You should notice that the green attribute ‘Status Monitor’ turns to light green to denote graphical alerting for this EMS event.

18. Click on the lit green light. A dialog will be spawned to show that you wish the event to reflect a down or up status (depending on which of your events you clicked on) and that you want the subject token to be passed to the Status Monitor screen (in this case the process name).

19.  All of this has been set-up automatically for you as a result of ticking the ‘Configure Action Groups’ option in Heartbeat. Exit from this small dialog window. You should be taken to the ‘Action Group’ tab (third along in the Reaction module).

 

20. A default action group has been assigned to this EMS event (default – INSIDER-UP or INSIDER-DOWN depending on which EMS event you clicked on). The cover period specifies a date that allows you to only monitor these EMS events for graphical alerting between time periods and from/to dates.

 

21. Click on the ‘!’ icon at the top middle of the resulting window. We now need to re-build the Event Monitor EMS filter which passes configured EMS events to the monitor process. This will take on board the newly added events that you associated with a process going UP and DOWN on the Tandem node. Carrying out the following steps will allow us to set-up graphical monitoring discussed in the next sub-section.

22. Click on the ‘Generate Filter Source’ button to initiate the generation of the Event Monitor filter file. This is a waited operation so wait for the completion message to appear. This will be as follows;

23. Click ‘OK’ on this message.

24. Subsequently click on the ‘Compile Filter Program’ button on this dialog. This is a no-waited option so we will need to go to the spooler to check the compilation has worked successfully. The following message will appear;

25. Two EMS events are now generated (check Reflex Console). The subject is FILTER COMPILE and text is:
REFLEX 80:20 : Filter Compilation - Successful   and
REFLEX 80:20 : Inverse Filter Compilation - Successful

26. Logon to the Tandem as the owner of the Reflex 80:20 Pathway and go into PERUSE or SPOOLCOM to check the output from this filter compilation stage. The report output will be entitled ‘#REFLEX’. Two outputs will be produced. One is the Reflex Event Monitor filter file and the other is the inverse filter – see TIP below. If you search through the outputs, you will see the event numbers you allocated for the monitoring of your Heartbeat process.

 

 

27. If the outputs show ‘no errors’ on the last page, go back to the Reflex 80:20 GUI and carry out the final step in this 3-step sequence which is ‘Warm-boot Reaction Servers’.

28. This flushes the Event Monitor of currently configured event ranges causing it to re-read the Reflex 80:20 database for newly configured events and also to re-hook up to the newly created EMS filter object – ECALFOBJ.

29. Check the success of the warm-boot by clicking on the ‘Console’ button on the main toolbar of Reflex 80:20. This is an EMS event-viewing module. Scroll using the scroll bars to view the warm-boot EMS messages generated by the processes CEGEN, PROCMON, EVNTMON and so on.

30. Exit from all of the displayed windows leaving only the Reflex 80:20 main toolbar on display.

We have now set-up the given Tandem process to be monitored by Reflex 80:20 process monitor. So far, this will result on EMS events being seen in an EMS viewing console should the process disappear from the system. The next sub-section discusses how this can be seen graphically in the consolidated view of the system – Status Monitor.

All of these steps can be carried out on all of your other Reflex 80:20 Tandem nodes (if applicable) by clicking on the ‘Facilities – Select Node’ function above the main toolbar of Reflex. Logon with an appropriate Reflex user ID and proceed to carry out step [2] through [23] again.

 

11.4.         Monitoring of a Tandem Process Through Status Monitor

Once we have set-up a process to be monitored by way of the Reflex 80:20 process monitor as detailed in the previous section, we can look to catch the EMS events generated to drive a graphical icon to provide status. Carry out the following steps to enable this:

1.     Logon to the Reflex 80:20 application using the GUI with an appropriate Reflex administrator user ID.

2.     When the main Reflex 80:20 toolbar has turned from grey to coloured, click on the ‘OD Setup’ button on the main toolbar. Maximise the resulting set-up window.

3.     The set-up display for the Status Monitor module will appear. Along the top of the window will be displayed 15-default icons known as ‘Classes’. These represent a supplied set of sub-systems, e.g. DSK (disks), CPU, DEV (Devices), B24 (Base24). This set is not exhaustive and more can be added later but for the moment, the default set will be sufficient to start adding Tandem processes to be monitored.

4.     If you added a Tandem process with the ‘Status Monitor Object’ field set to ON in the Heartbeat screen in the previous section, then you should have a group called ‘REACT/HEARTBEAT:-<DEFAULT SETUP ENTRIES>’ on the set-up display (All of the name may not be visible. You may have to scroll to it but it is located under the DEF class). This is created for you as default. More often than not, you will want to create your own group categories to add processes to. The remaining steps describe how to do this.

5.     Left-mouse-click on the ‘APP’ class (or any preferred class of your choosing) and you will be presented with a ‘SM Setup: Add Top Level Group’ dialog box. This will allow you to type the name of a group under which you can represent your various Tandem processes.

6.     Type a suitable top-level group name under which to store the process you have added,
e.g. ** PROCS **, BASE24 PROCS. Choose an appropriate icon to associate with your process. This is a free text field that will then be used as the key to the group. Groups added should have unique names. The group name ‘** PROCS ** is assumed for the rest of this section.

7.     Click the ADD button (‘+’) on this dialog. The following dialog will be returned:

8.     Click the ‘OK’ button.

9.     The following informational message will appear:

 

10. Click on the ‘OK’ button.

11. The set-up screen will be refreshed and the new top level group will be displayed under the appropriate class.

12. Now we will proceed to drag the Tandem process you added earlier, under the ** PROCS ** top level group. Either double-click the ** PROCS ** top level group or single-click on it and subsequently click on the folder icon on the spawned floating toolbar.

13. This will take you to the object set-up window that exists below all top-level groups.

14. This is the window from which you can access all of your auto-discovered Tandem objects. Click the note paper icon just to the left of the ADD button on this dialog. This will get the latest list of Tandem objects regardless of type and subtype. Scroll through these to view the objects detected in the previous section.

15. Click on the down arrow to the right of the type and subtype. This will provide a drop-down list of pre-supplied object types and subtypes.

16. Scroll down to ‘TANDEM     PROCESS’ and select this entry by clicking on it.

17. This entry will then replace the currently displayed type and subtype.

18. Check the rightmost pager button ‘By Type and Subtype’ and subsequently re-click on the note paper icon to the left of the ADD button.

19. All of your current processes will be displayed in the list part of the dialog. This may only be the one you added in the previous section.

20. We now need to drag-and-drop this Tandem process into the ** PROCS ** top level group. To do this, click on the window option just above the main Reflex toolbar and subsequently click on ‘Tile Vertical’.

21. What is left to do is just a simple case of dragging-and-dropping the process object into the ** PROCS ** group just like dragging files in windows explorer, to folders. Click on a process in the object list window and keep your finger on the mouse button and drag the process object directly over the ** PROCS ** group and let go of the mouse button. Using the SHIFT key on the keyboard also caters for grouped drag-and-drop.

22. Exit from the 2 windows – the object set-up window and the lower level ** PROCS ** window by clicking either on the green arrow which is rightmost on each of these dialogs, or just use the ‘X’ button on the top right corner of each window.

23. This should just leave the top level set-up window with the list of classes. If you have been over-zealous in shutting down windows in the last step then simply re-click on the ‘OD Setup’ button on the main toolbar of Reflex 80:20, and maximise the resulting window.

24. Having set-up your PROCESS object tree (you can set-up as many groups as you like to represent the various categories of process), we now need to warm-boot the Reflex 80:20 application.

 

 

25. Display the top-level set-up screen of Reflex 80:20. This should already be the case if step [23] was observed above. If not, click on the ‘OD Setup’ button on the main toolbar of Reflex 80:20.

26. Click on the ‘!’ icon at the top left of this window too warm-boot the Reflex 80:20 Status Monitor.

27. The message below will appear:

            Click ‘OK’ to this message.

28. The message below will appear:

            Click ‘OK’ to this message.

29. Exit from this top-level screen by clicking on the green arrow to the right of the yellow question mark (?) icon.

30. Click on the ‘Overdrive’ button on the main toolbar to view the network hierarchy display and subsequently click on the appropriate node.

31. The top-level live display screen will be displayed with the group you added in this section.

 

 

 

 

 

12.          Monitoring Files Graphically in Status Monitor

 

12.1.         Overview

This section is a step-by-step guide to configuring Tandem files to be monitored graphically by way of the Status Monitor module. It first details the steps required in setting up a file under the Heartbeat module. This will provide for up, down and vulnerable EMS events to be generated by the Reflex 80:20 file metrics monitor. These events can be seen in any EMS viewing console. The second part of this section, shows the steps required configuring the Status Monitor module to display graphically the up, down and vulnerable states of configured Tandem files.

 

12.2.         Reflex 80:20 File Monitoring Parameters

Before setting up a Tandem file to be monitored, it is a useful exercise to look at three of the parameters involved in file metrics monitoring. These parameters can be changed depending on your on-site requirements. Carry out the following actions:

1.     Logon to the Reflex 80:20 application using the GUI with an appropriate Reflex administrator user ID.

2.     When the main Reflex 80:20 toolbar has turned from grey to coloured, click on the ‘Administration’ button on the main toolbar. Maximise the resulting set-up window.

3.     Click on the second tab entitled ‘Parameters’ to bring up the list of parameters used by the Reflex 80:20 product.

4.     Scroll down to the 3 parameters prefixed with ‘FIME-‘ (as opposed to those prefixed with ‘FIPR-’ (file presence monitoring) which are used in monitoring the delivery of files from remote systems). Double click on the first of these called ‘FIME-METS-SUPPRESS’. This parameter controls whether or not EMS messages generated by the file metrics software are deemed invisible to all but the graphical status monitor display of Reflex 80:20. This is achieved by Reflex inserting a suppress token in the EMS message to instruct event viewing consoles not to display the message. If literally hundreds of files are being monitored for health then EMS messages will not clutter the EMS viewing consoles but will be collected by the Status Monitor module of Reflex alongside the appropriate file, if they have been configured to do so. This is talked about in the second part of this section.

5.     Double-click on the second of these called ‘FIME-MSG-FREQUENCY’. This parameter controls how often the same EMS event is output if a file is found to be in the same state. For example, if a file is in a CORRUPT state then Reflex will generate a vulnerable EMS event (as configured by the user in the next section). If the same Tandem file is corrupt the next time the file monitoring software polls then the software will not raise another EMS message until it has polled ‘FIME-MSG-FREQUENCY’ number of times at which point, it will raise the corrupt EMS message again. This is to cut down on EMS event pollution on the EMS logs.

Amend the value of the parameter based on your own on-site requirements for reporting offending files.

6.     Double-click on the parameter ‘FIME-POLL-INTERVAL’ to display the detail of this parameter.

7.     This is the poll interval in seconds that the Reflex 80:20 non-stop file metrics monitor will check the configured Tandem files as to their UP/DOWN/VULNERABLE status. This is used in conjunction with the ‘FIME-MSG-FREQUENCY’ parameter. The defaults are a frequency of ‘1’ and a poll interval of ‘60’ seconds. The result here would be that a file down or vulnerable would not be re-reported until ’1 * 60’ seconds later.

8.     Double-click on any of these 3 parameters and click on the tick icon to amend the value in the ‘Parameter Value’ field. These values will taken on board at the next warm-boot which will be carried out as part of the following sub-section.

 

12.3.         Heartbeat Monitoring of a Tandem File

This section details the first of two steps in monitoring a Tandem file. The end result of this section will be the raising of a down EMS event if the file disappears from the system, an up EMS event if it is present and a vulnerable event if any of the monitored attributes of the file change. Carry out the following steps:

1.     Logon to the Reflex 80:20 application using the GUI with an appropriate Reflex administrator user ID.

2.     When the main Reflex 80:20 toolbar has turned from grey to coloured, click on the ‘Heartbeat’ button on the main toolbar. Maximise the resulting set-up window.

3.     You will be presented with the ‘Process Existence’ window. Click on the last tab entitled ‘File Metrics’. If there are no records currently registered then the following message will be displayed.

     Click ‘OK’ if this message appears.

On the right-hand side of the ‘File Metrics’ window is the detail aspect. On this side, details of Tandem files can be entered for monitoring.

 

4.     Type the name of the file you wish to monitor in the field provided at the top of the right-hand side of the window, e.g. $DATA02.RFLXDAT.SBJHISTQ.

5.     There are a number of poll periods that can be specified just under the ‘Name of File to Monitor’ field. Only one can be specified. Click on the ‘Critical (secs)’ poll period as part of this example set-up. This will monitor the file in accordance with the parameters set-up above.

6.     If the file is deleted and later gets replaced or has one of the appropriate file attributes changed, a unique EMS event will be raised to indicate this. This EMS event can be seen on an event-viewing console. The next part of the detail window allows the entering of the subsystem identification (SSID) and event numbers to reflect the present, not present and vulnerable states of a given file. Enter the owner field (if you wish it to be different to the default – INSIDER), a value field and unique present, not present and vulnerable event numbers for the associated owner field. See TIP below.

 

 

7.     The output behaviour of an EMS event can be tailored on the extreme right-hand side of the window. If left at the default, a normal EMS event will be generated for the UP, DOWN and VULNERABLE EMS events. However, it is possible to generate CRITICAL events by checking the ‘Emphasis’ pager button or action needed/action completion events if the ‘Action Needed’ or ‘Clear Action’ pager buttons are entered.

 

8.     If you require graphical monitoring of the file you have just entered, check both the ‘Status Monitor Object’ and ‘Configure Action Groups’ fields in the ‘Monitoring’ aspect of the detail window.

9.     When the file you have entered is being monitored by the non-stop file monitor, the subject token of any event raised is the name of the file, e.g. $DATA02.RFLXDAT.SBJHISTQ. This will be used to map onto any equivalent graphical icon in Status Monitor. This will be discussed later. If you require a different subject token other than the name of the file, enter the value here (up to 24 characters).

10. Following on from point [9], the manager token of all events raised from the Reflex 80:20 file monitor will be set to spaces. If this field is filled in then the manager token will be set to the value entered here.

11. Enter the description field to describe the file that is being monitored, e.g. Application, Tandem, ENSCRIBE, SQL, EDIT. This will aid other Reflex users in the future as well as acting as a reminder for you.

12. Click on the ‘+’ button at the top of the window to enter this process record into the Reflex database. You will be presented with the following message (example file):

Click ‘OK’ to clear the message.

 

13. Exit from the Heartbeat window by clicking on the green arrow to the right of the yellow question mark (?) icon.

14. Click on the Reaction button on the main toolbar of Reflex 80:20. Maximise the resulting window.

15. Click on the second tab entitled ‘Reaction List’. This will provide a list of currently configured EMS event ranges in the Reflex 80:20 database. Some of these events have been pre-supplied as part of a full install of the product.

16. Scroll down the list until you see the SSID and event number(s) you specified for your UP, DOWN and VULNERABLE EMS event messages for the Heartbeat file entry you added. You should notice that for you event(s) the column ‘Monitor’ has an asterisk (*) character specified. This has been done because you asked Reflex to automatically configure (using the ‘Configure Action Groups’ option) the Reaction engine with your chosen EMS events. The ‘Monitor’ column is short for ‘Graphical Monitoring in Status Monitor’.

17. Double-click on one of the SSIDs you added earlier. You should notice that the green attribute ‘Status Monitor’ turns to light green to denote graphical alerting for this EMS event.

18. Click on the lit green light. A dialog will be spawned to show that you wish the event to reflect a down, vulnerable or up status (depending on which of your events you clicked on) and that you want the subject token to be passed to the Status Monitor screen (in this case the file name).

19.  All of this has been set-up automatically for you as a result of ticking the ‘Configure Action Groups’ option in Heartbeat File Metrics. Exit from this small dialog window. You should be taken to the ‘Action Group’ tab (third along in the Reaction module).

 

20. A default action group has been assigned to this EMS event (default – INSIDER-UP-FILE, INSIDER-DOWN-FILE or INSIDER-VULN-FILE depending on which EMS event you clicked on). The cover period specifies a date that allows you to only monitor these EMS events for graphical alerting between to date and time periods.

 

21. Click on the ‘!’ icon at the top middle of the resulting window. We now need to re-build the Event Monitor EMS filter which passes configured EMS events to the monitor process. This will take on board the newly added events that you associated with a file present, not present and vulnerable on the Tandem node. Carrying out the following steps will allow us to set-up graphical monitoring discussed in the next sub-section.

22. Click on the ‘Generate Filter Source’ button to initiate the generation of the Event Monitor filter file. This is a waited operation so wait for the completion message to appear. This will be as follows;

23. Click ‘OK’ on this message.

24. Subsequently click on the ‘Compile Filter Program’ button on this dialog. This is a no-waited option so we will need to go to the spooler to check the compilation has worked successfully. The following message will appear;

25. Two EMS events are now generated (check Reflex Console). The subject is FILTER COMPILE and text is:
REFLEX 80:20 : Filter Compilation - Successful   and
REFLEX 80:20 : Inverse Filter Compilation - Successful

26. Logon to the Tandem as the owner of the Reflex 80:20 Pathway and go into PERUSE or SPOOLCOM to check the output from this filter compilation stage. The report output will be entitled ‘#REFLEX’. Two outputs will be produced. One is the Reflex Event Monitor filter file and the other is the inverse filter – see TIP below. If you search through the outputs, you will see the event numbers you allocated for the monitoring of your Heartbeat file.

 

 

27. If the outputs show ‘no errors’ on the last page, go back to the Reflex 80:20 GUI and carry out the final step in this 3-step sequence which is ‘Warm-boot Reaction Servers’.

28. This flushes the Event Monitor of currently configured event ranges causing it to re-read the Reflex 80:20 database for newly configured events and also to re-hook up to the newly created EMS filter object – ECALFOBJ.

29. Check the success of the warm-boot by clicking on the ‘Console’ button on the main toolbar of Reflex 80:20. This is an EMS event-viewing module. Scroll using the scroll bars to view the warm-boot EMS messages generated by the processes CEGEN, PROCMON, EVNTMON and so on.

30. Exit from all of the displayed windows leaving only the Reflex 80:20 main toolbar on display.

We have now set-up the given Tandem file to be monitored by Reflex 80:20 file monitor. So far, this will result in EMS events being seen in an EMS viewing console should the file disappear from the system or changes one of its characteristics. The next sub-section discusses how this can be seen graphically in the consolidated view of the system – Status Monitor.

All of these steps can be carried out on all of your other Reflex 80:20 Tandem nodes (if applicable) by clicking on the ‘Facilities – Select Node’ function above the main toolbar of Reflex. Logon with an appropriate Reflex user ID and proceed to carry out step [2] through [23] again.

 

12.4.         Monitoring of a Tandem File Through Status Monitor

Once we have set-up a file to be monitored by way of the Reflex 80:20 file metrics monitor as detailed in the previous section, we can look to catch the EMS events generated to drive a graphical icon to provide status. Carry out the following steps to enable this:

1.     Logon to the Reflex 80:20 application using the GUI with an appropriate Reflex administrator user ID.

2.     When the main Reflex 80:20 toolbar has turned from grey to coloured, click on the ‘OD Setup’ button on the main toolbar. Maximise the resulting set-up window.

3.     The set-up display for the Status Monitor module will appear. Along the top of the window will be displayed 15-default icons known as ‘Classes’. These represent a supplied set of sub-systems, e.g. DSK (disks), CPU, DEV (Devices), B24 (Base24). This set is not exhaustive and more can be added later but for the moment, the default set will be sufficient to start adding Tandem files to be monitored.

4.     Left-mouse-click on the ‘APP’ class (or any preferred class of your choosing) and you will be presented with a ‘SM Setup: Add Top Level Group’ dialog box. This will allow you to type the name of a group under which you can represent your various Tandem files.

 

5.     Type a suitable top-level group name under which to store the file you have added,
e.g. ** FILES **, BASE24 FILES. Choose an appropriate icon to associate with your file. This is a free text field that will then be used as the key to the group. Groups added should have unique names. The group name ‘** FILES ** is assumed for the rest of this section.

6.     Click the ADD button (‘+’) on this dialog. The following dialog will be returned:

7.     Click the ‘OK’ button.

8.     The following informational message will appear:

 

9.     Click on the ‘OK’ button.

10. The set-up screen will be refreshed and the new top level group will be displayed under the appropriate class.

11. Now we will proceed to drag the Tandem file you added earlier under the ** FILES ** top level group. Either double-click the ** FILES ** top level group or single-click on it and subsequently click on the folder icon on the spawned floating toolbar.

12. This will take you to the object set-up window that exists below all top-level groups.

13. This is the window from which you can access all of your auto-discovered Tandem objects. Click the note paper icon just to the left of the ADD button on this dialog. This will get the latest list of Tandem objects regardless of type and subtype. Scroll through these to view the objects detected in the previous section.

14. Click on the down arrow to the right of the type and subtype. This will provide a drop-down list of pre-supplied object types and subtypes.

15. Scroll down to ‘TANDEM     FILE’ and select this entry by clicking on it.

16. This entry will then replace the currently displayed type and subtype.

17. Check the rightmost pager button ‘By Type and Subtype’ and subsequently re-click on the note paper icon to the left of the ADD button.

18. All of your current processes will be displayed in the list part of the dialog. This may only be the one you added in the previous section.

19. We now need to drag-and-drop this Tandem file into the ** FILES ** top level group. To do this, click on the window option just above the main Reflex toolbar and subsequently click on ‘Tile Vertical’.

20. What is left to do is just a simple case of dragging-and-dropping the files object into the ** FILES ** group just like dragging files in windows explorer, to folders. Click on a file in the object list window and keep your finger on the mouse button and drag the process object directly over the ** FILES ** group and let go of the mouse button. Using the SHIFT key on the keyboard also caters for grouped drag-and-drop.

21. Exit from the 2 windows – the object set-up window and the lower level ** FILES ** window by clicking either on the green arrow which is rightmost on each of these dialogs, or just use the ‘X’ button on the top right corner of each window.

22. This should just leave the top level set-up window with the list of classes. If you have been over-zealous in shutting down windows in the last step then simply re-click on the ‘OD Setup’ button on the main toolbar of Reflex 80:20, and maximise the resulting window.

23. Having set-up your FILE object tree (you can set-up as many groups as you like to represent the various categories of file), we now need to warm-boot the Reflex 80:20 application.

 

24. Display the top-level set-up screen of Reflex 80:20. This should already be the case if step [23] was observed above. If not, click on the ‘OD Setup’ button on the main toolbar of Reflex 80:20.

25. Click on the ‘!’ icon at the top left of this window to warm-boot the Reflex 80:20 Status Monitor.

26. The message below will appear:

            Click ‘OK’ to this message.

27. The message below will appear:

            Click ‘OK’ to this message.

28. Exit from this top-level screen by clicking on the green arrow to the right of the yellow question mark (?) icon.

29. Click on the ‘Overdrive’ button on the main toolbar to view the network hierarchy display and subsequently click on the appropriate node.

30. The top-level live display screen will be displayed with the group you added in this section.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Reflex 80:20

Installation and

Quick-Start Manual

APPENDICES

 

13.          APPENDICES

 

13.1.         Activating your Tandem SQL Licence

 

Read the Tandem manual ‘NonStop SQL/MP Installation and Management Guide – Chapter 2 – Initialising NonStop SQL/MP’.

 

Execute all the steps in this section to initialise your Tandem SQL software.

13.2.         Merging Reflex 80:20 EMS Templates Reference

This appendix is only a guide to be used in conjunction with the Tandem manuals referred to in section [5] of this document.

Installing the Reflex 80:20 EMS templates for the ‘K’ series Tandem node:

1.     Logon as SUPER.SUPER onto your Reflex 80:20 Tandem node.

2.     At a TACL prompt type:

>COUP                                                                                                [return]

3.     Once in COUP, type the following:

1) INFO ALLPROCESSORS                                                                  [return]

A display similar to the text box below will be shown. This output shows where both the resident on non-resident EMS template files are located on your Tandem system.

4.     Exit from COUP by typing ‘EXIT [return]’.

5.     At a TACL prompt, type the following (replace the references given with your own site-specific references retrieved with your COUP commands).

> FUP DUP $system.sys10.nresiden, $system.sys10.zznresid                [return]

6.     Type the following command (using your own file references):

>TEMPLI $system.sys10.resident, $system.sys10.nresiden                    [return]

7.     Once in TEMPLI, type the following command (using your own file references):

           > FILE ZZNRESID                                                         [           [return]

> FILE $<your Reflex 80:20 volume>.RFLXDDL.NRESTEMP                  [return]

> FILE $system.system.EVENTTD                                                        [return]

> FILE <other third-party product templates>                                         [return]

> EXIT                                                                                                 [return]

where   RFLXDDL is your Reflex 80:20 Dictionary sub-volume and

           EVENTTD are your Tandem templates (usually on $system)

8.     After the build has taken place, type the following (with your own references):

> alter define =_ems_templates, file $system.sys10.nresiden                 [return]

9.     Type the following commands (with your own references):

> FUP RENAME $system.sys10.nresiden, $system.sys10.ZZOLDNRE   [return]

> FUP RENAME $system.sys10.ZZTP0000, $system.sys10.nresiden      [return]

where the ZZTP0000 is the name of the file produced in step [6].

10. Type the following command:

> COUP                                                                                               [return]

11. Once in COUP, type the following commands (with your own references):

> ASSUME ALLPROCESSORS                                                            [return]

> INFO ALLPROCESSORS                                                                   [return]

> ALTER ems^templates (resident $system.sys10.resident, nonresident                                                                 $system.sys10.nresiden)                   [return]

> EXIT                                                                                                 [return]

12. At a TACL prompt, type the following commands (with your own references):

> FUP SECURE $system.sys10.resident, “NNOO”                                  [return]

> FUP SECURE $system.sys10.nresiden, “NNOO”                                 [return]

These commands allow applications to see the template files. Amend your ‘rwep’ security in line with your security settings for the Tandem system.

 

 

 

 

 

          

 

 

Installing the Reflex 80:20 EMS templates for the ‘S’ series Tandem node:

 

1.     Logon as SUPER.SUPER onto your Reflex 80:20 Tandem node.

2.     At a TACL prompt type:

>SCF                                                                                                   [return]

3.     Once in SCF, type the following:

1-> ASSUME SUBSYS $ZZKRN                                                           [return]

2-> INFO                                                                                              [return]

 

A display similar to the text box above will be shown. This output shows where both the resident on non-resident EMS template files are located on your Tandem system.

4.     Exit from SCF by typing ‘EXIT [return]’.

5.     At a TACL prompt, type the following (replace the references given with your own site-specific references retrieved with your SCF commands).

> FUP DUP $system.sys02.template, $system.sys10.zztempla              [return]

6.     Type the following command (using your own file references):

>TEMPLI $system.sys02.rtmplate, $system.sys02.template                   [return]

7.     Once in TEMPLI, type the following command (using your own file references):

> FILE ZZtempla                                                                                  [return]

> FILE $<your Reflex 80:20 volume>.RFLXDDL.NRESTEMP                  [return]

> FILE $system.system.EVENTTD                                                        [return]

> FILE <other third-party product templates>                                         [return]

> EXIT                                                                                                 [return]

where   RFLXDDL is your Reflex 80:20 Dictionary sub-volume and

           EVENTTD are your Tandem templates (usually on $system)

8.     After the build has taken place, type the following (with your own references):

> alter define =_ems_templates, file $system.sys02.template                 [return]

9.     Type the following commands (with your own references):

> FUP RENAME $system.sys02.template, $system.sys02.ZZTEMPLA   [return]

> FUP RENAME $system.sys02.ZZTP0000, $system.sys02.template     [return]

where the ZZTP0000 is the name of the file produced in step [6].

10. Type the following command:

> SCF                                                                                                  [return]

11. Once in SCF, type the following commands (with your own references):

> ASSUME SUBSYS $ZZKRN                                                              [return]

> INFO ALLPROCESSORS                                                                   [return]

> ALTER SUBSYS $ZZKRN, RESIDENT $system.sys02.rtmplate,                                                           NONRESIDENT $system.sys02.template           [return]

> EXIT                                                                                                 [return]

 

12. At a TACL prompt, type the following commands (with your own references):

> FUP SECURE $system.sys02.template, “NNOO”                                 [return]

> FUP SECURE $system.sys02.rtmplate, “NNOO”                                 [return]

These commands allow applications to see the template files. Amend your ‘rwep’ security in line with your security settings for the Tandem system.

 

 

 

13.1.         Administration Parameter Settings and Their Use in Reflex 80:20

This section describes the use and the value settings for each of the parameters configurable in the Reflex 80:20 product. A list of these parameters can be seen by going into the Administration module of Reflex 80:20 and clicking on the second tab.

 

Parameter Name	Value(s)	Warmboot	Description of Use
ACTION-GROUP-DOWN	INSIDER-DOWN	Stop/Start Reflex	Set-up to whatever 30 character value you require. INSIDER-DOWN is the default. This can be set to a generic value which is more site-specific, e.g. ACTION-COMPAQ-DOWN or BANK-DOWN-EVENT-REACTION. This parameter is usually set-up at the beginning of using the product. It is used as a file key to embrace all down messages sent to the Status Monitor graphical display for both processes and files set-up using the Heartbeat module. If the user wants the product to automatically set-up a graphical reaction to a process down or file not present situation, the reaction key in the Reaction module will be set to the value given here.
ACTION-GROUP-UP	INSIDER-UP	Stop/Start Reflex	As above but for the ‘UP’ graphical reaction cases relating to Heartbeated processes and files.
ACTION-GROUP-VULN	INSIDER-VULN	Stop/Start Reflex	As above but for the ‘VULNERABLE’ graphical reaction cases relating to Heartbeated files (files only).  NOTE: Whereas a process can either be up or down in the Reflex context, a file can be present or not present but also have an offending attribute, e.g. file corrupt, file broken, file full and so forth, which represent vulnerable scenarios.
AUDIT-FLAG	Y, N, S Default – Y	Stop/Start Reflex	If this flag is set to ‘Y’ then all of the configuration carried out in the Reflex GUI screens will be audited and any actions carried out wriiten to the AUDLOG file. This file is accessible from the Administration module and the contents can be ordered by timestamp, facility, Guardian User ID and terminal ID. The AUDLOG file can be archived. Details of how to do this are contained in the Reflex user manual. In previous version of Reflex, setting this flag to ‘S’ would write a detail record of before and after images or records changed to AUDDET. This is no longer supported.
CACHE-CPU	The range of values is 0 to 15. Default value is set to 0	Stop/Start Reflex	This parameter is used to supply the CPU that will be used for the PUP/SCF process.
CACHE-PRIORITY	The range of values is 50 to 150. Default value is set to 50.	Stop/Start Reflex.	This parameter is used to supply the PRIORITY that will be used for the PUP/SCF process.
CACHE-PROCESS	Default value is set to $RFCA.	Stop/Start Reflex.	This parameter is used to supply the PROCESS NAME that will be used for the PUP/SCF process.
CONSOLE-AERTS-FLAG	0(none), 1(critical), 2(action), 3(critical & action) Default – 0	Freeze, Stop, Thaw & Start CONSOLE server in Reflex 80:20 Pathway	This flag enables any critical or action needed EMS events not currently configured in Reflex to be monitored, to still be passed to the status monitor graphical alerting screen. This is achieved by attaching the inverse filter (ECALFOB2) to the primary view in CONSOLE. Icons can be set-up in status monitor to catch the alerts thrown out by console. Event 2602 for critical events and 2603 for action needed events. These events are pre-delivered and associated with graphical alerting as a default. See the Reflex 80:20 user manual for more details.

 

Parameter Name	Value(s)	Warmboot	Description of Use
CPU-BUSY-THRESHOLD	0 thru 99 Default – 70	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	This parameter controls 2 functions within Reflex. The first is the CPU threshold observed in the Dashboard module of Reflex. Any breech of threshold will render the appropriate graph or the CPU summary, a red colour indicating threshold compromised. The second effect of this parameter is to control the EMS messages (exceeded - 2553) and (no longer exceeded - 2561) which correspond to threshold crossed and no longer crossed respectively. These events are pre-delivered and associated with graphical alerting as a default.
CPU-DASH-MSG-FREQ	1 thru 99 Default – 10	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	This parameter is used in conjunction with all the other Dashboard parameters. It controls ‘how often’ to output a CPU threshold breeched message. An example would be, if the CPU-POLL-INTERVAL is set to 15 seconds and CPU-DASH-MSG-FREQ set to 5 then a CPU busy message would only be output if the CPU was seen to be busy 15 * 5 seconds (1 minute 15 seconds). At this point, a CPU busy EMS message would be raised by Dashboard.
CPU-POLL-INTERVAL	15 thru 3600 (seconds) Default – 30	Warm-boot Dashboard by going into status monitor set-up and clicking warm-boot (!) icon.	This parameter controls the interval at which the Dashboard GUI polls the Reflex Pathway for CPU metrics.
CPU-QUEUE-THRESHOLD	0 thru 50 Default – 20	Warm-boot Dashboard by going into status monitor set-up and clicking warm-boot (!) icon.	The parameter represents how many queued processes are allowed in a CPU before a threshold message is raised. The appropriate graph in the Dashboard will show red for the appropriate CPU when the threshold is compromised. Queue threshold exceeded EMS event – 2555 Queue threshold no longer exceeded EMS event – 2563
DASH-SUSPECT-INTERVAL	1 thru 99 Default – 1	Warm-boot Dashboard by going into status monitor set-up and clicking warm-boot (!) icon.	This parameter controls how often a suspect process is reported on by Dashboard. An example would be, if the CPU-POLL-INTERVAL is set to 15 seconds and DASH-SUSPECT-INTERVAL is set to 5 then a suspect process EMS message would only be output if the process was seen to be suspect 15 * 5 seconds (1 minute 15 seconds). At this point, a suspect process EMS message would be raised by Dashboard. Current suspect states are as follows: SUSPENDED/ DEBUG BREAKPOINT/ DEBUG TRAP/ DEBUG REQUEST/ INSPECT MEM ACCESS BREAKPOINT/ INSPECT BREAKPOINT/ INSPECT TRAP/ INSPECT REQUEST/ SAVEABEND/ TERMINATING.
DASH-SUSPECT-SUPPRESS                             PPRESS	Y, N Default – N	Warm-boot Dashboard by going into status monitor set-up and clicking warm-boot (!) icon.	This parameter does NOT stop the suspect process EMS messages from being emitted but controls whether they are seen in normal EMS viewing consoles like CONSOLE, ViewpointTM and View + PointTM. This is achieved by Reflex placing a suppress token in the EMS event to make it invisible on the system. The purpose of this is to allow the event to be seen in the Reflex graphical status monitor display where important events have been consolidated rather than adding more noise to the collectors on the Tandem node.

 

Parameter Name	Value(s)	Warmboot	Description of Use
DASH-THRESH-SUPPRESS	Default value is set to NNNNNNN	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	This parameter is used to control whether the various DISK/CPU threshold events are suppressed. By using a series of Y/N values individual thresholds can be toggled on or off. The values refer to: CPU Busy, CPU Queue Length, CPU Page Faults, Disk Full, Process Busy, Process Priority and Disk Fragment Respectively.
DASH-THRESH-SUPPRESS-X25	Default value is set to NNNNNNNNNNN	Stop/Start Reflex	This parameter is used to control whether the various X25 threshold events are suppressed. By using a series of Y/N values individual thresholds can be toggled on or off. The values refer to: Line Quality, SU In Use, Modem Error, Frame Sent RNR, Frame Sent REJ, Frame Received RNR, Frame Received REJ, Packet Sent RNR, Packet Sent Restart, Packet Received RNR, Packet Received Restart Respectively.
DATA-ANALYSIS-TRACE-FLAG	Y, N Default – N	Warm-boot service monitor set-up using the (!) icon.	This parameter controls whether unrecognised APIs forwarded into the service monitor module are written to a trace file (TRACEFIL) in the data subvolume. These will be any APIs not set-up in the data definition dialog under the configuration menu of Reflex 80:20. See Reflex user manual for more details.
DEFAULT-GUARDIAN-USER	<group-name>.<user-name>, e.g. REFLEX.OPS Default: REFLEX.OPS	Stop/Start Reflex	This parameter can be set-up if you wish to supply users with a direct connection with Reflex without the need for a logon ID. This is typical of where business users just require to access the service level state of objects for viewing but cannot actually change any details in Reflex. The Guardian user ID specified here would normally be associated with a READ-ONLY security class in the administration module of Reflex 80:20. See the Reflex user manual for more details.
DEFAULT-GUARDIAN-USER-ENABLED	Y, N Default – N	Stop/Start Reflex	This flag is used in conjunction with the last parameter for controlling whether users have access to the Reflex Pathway without the need for a Guardian user ID. In practice, only a Reflex administrator would have access to the parameters screen for updating these parameters. The facility ID for this function is (DPU).
DISK-AUDIT-FORCES-THRESHOLD	Default value is set to 0.1. The range of values is 0.1 to 9.9.	Stop/Start Reflex	This parameter is used by dashboard to determine what percentage of Cache Calls were Audit Forces during a disk cache poll interval, before Reflex flags a warning on the cache audit forces block.
DISK-CACHE-FAULTS-THRESHOLD	Default value is set to 0.1. The range of values is 0.1 to 9.9.	Stop/Start Reflex	This parameter is used by dashboard to determine what percentage of Cache Calls were Cache faults during a disk cache poll interval, before Reflex flags a warning on the cache faults block.
DISK-CACHE-POLL-INTERVAL	Default value is set to 60. The range of values is 60 to 28800.	Stop/Start Reflex	This parameter is the Cache poll interval that is used in Dashboard to poll at the configured number of seconds the Cache status.
DISK-CACHE-READ-HITS-THRESHOLD	Default value is set to 90. The range of values is 0 to 100.	Stop/Start Reflex	This parameter is used by dashboard to determine what percentage of Cache Reads were Cache Read Hits during a disk cache poll interval, before Reflex flags a warning on the cache faults block.

 

Parameter Name	Value(s)	Warmboot	Description of Use
DISK-DASH-MSG-FREQ	1 thru 99 Default – 10	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	This parameter is used in conjunction with all the other dashboard disk parameters. It controls ‘how often’ to output a DISK threshold breeched message. An example would be, if the DISK-POLL-INTERVAL is set to 15 seconds and DISK-DASH-MSG-FREQ set to 5 then a DISK full message would only be output if the DISK was seen to be busy 15 * 5 seconds (1 minute 15 seconds). At this point, a DISK full EMS message would be raised by Dashboard.
DISK-FRAGMENT-THRESHOLD	1 thru 99999 Default – 1500	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	The parameter represents how many DISK FRAGMENTS are allowed on a DISK before a threshold message is raised. The appropriate graph in the Dashboard will show red for the appropriate disk when the threshold is compromised. Fragment threshold exceeded EMS event – 2566 Fragment threshold no longer exceeded EMS event – 2567
DISK-FULL-THRESHOLD	1 thru 99 Default – 85	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	Dashboard will periodically poll (based on the DISK-POLL-INTERVAL) the amount of disk space that is being used (as a percentage). This will then be used to highlight any disks in Dashboard that have breached the threshold and subsequently colour the appropriate disk red on a graph or in the disk summary. Disk Threshold exceeded EMS event – 2556 Disk Threshold no longer exceeded EMS event – 2564
DISK-HITS-THRESHOLD	(Default value is set to 100. The range of values is 0 to 1000	Stop/Start Reflex	This parameter is used by dashboard to determine the number of Disk Cache Hits per second that are allowed during a CPU poll interval, before Reflex flags a warning.
DISKIOS-THRESHOLD	Default value is set to 2. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by dashboard to determine the number of Disk I/O’s per second that are allowed during a CPU poll interval, before Reflex flags a warning.
DISK-POLL-INTERVAL	60 thru 28 800 (seconds – maximum 8 hours) Default – 60	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	This is the disk poll interval which is used by Dashboard to poll at the configured number of seconds for disk status.
ENT-MNGR-FEED-DISARM	Y, N Default – Y	Warm-boot the Reaction module of Reflex by carrying out the third step under the (!) icon.	This paramter controls whether alerts are sent to a nominated TCP/IP address and then onto an allocated Enterprise Manager or to allow SMS paging or to ITL SENTRA (NT monitoring). The ENT-MNGR-FEEDER Pathway server in the Reflex 80:20 Pathway is a Fastpipe client responsible for relaying Enterprise Manager alerts. Setting this flag to a value of ‘Y’ will enable this function.

 

Parameter Name	Value(s)	Warmboot	Description of Use
FILE-INTERVAL	1 thru 3600 Default – 1	Stop/Start the file agent.	The use of this parameter has been superceeded by the FIME and FIPR prefixed parameters listed lower down. It is used by the FILEAGNT code in the object subvolume which monitors any files referenced in the object table for percent full at the configured interval. See the Reflex 80:20 user manual for more details. The Heartbeat module takes over from this monitoring as of release 4.0 onwards.
FILE-THRESHOLD	0 thru 99 Default – 1	Stop/Start the file agent.	The use of this parameter has been superceeded by the FIME and FIPR prefixed parameters listed lower down. It is used by the FILEAGNT code in the object subvolume which monitors any files referenced in the object table for percent full at the configured interval. See the Reflex 80:20 user manual for more details. The Heartbeat module takes over from this monitoring as of release 4.0 onwards.
FIME-METS-SUPPRESS	Y, N Default – N	Warm-boot Reaction module	This parameter does NOT stop the file monitoring EMS messages from being emitted but controls whether they are seen in normal EMS viewing consoles like CONSOLE, ViewpointTM and View + PointTM. This is achieved by Reflex placing a suppress token in the EMS event to make it invisible on the system. The purpose of this is to allow the event to be seen in the Reflex graphical status monitor display where important events have been consolidated rather than adding more noise to the collectors on the Tandem node.
FIME-MSG-FREQUENCY	1 thru 99 Default – 1	Warm-boot Reaction module	This parameter controls the frequency that the same state is reported by way of an EMS event message. For instance, if a file is found to be corrupt an EMS message will be generated. If it is found to be corrupt N seconds (FIME-POLL-INTERVAL) later, it will not be reported until this frequency parameter is reached. If it is set to ‘1’ then it will be reported constantly until the file problem is resolved.
FIME-POLL-INTERVAL	15 thru 1800 seconds Default – 60	Warm-boot Reaction module	This parameter is used by the file monitoring software within the Heartbeat module of Reflex. It only relates to the CRITICAL period of monitoring and can be set to 15 seconds thru 30 minutes depending on the user assigned requirement for critical. Any files being monitored at a CRITICAL rate will be assigned this period.
FIPR-MSG-FREQUENCY	1 thru 99 Default – 1	Warm-boot Reaction module	This parameter controls the frequency that the same state is reported by way of an EMS event message. For instance, if a file is found to be corrupt an EMS message will be generated. If it is found to be corrupt N seconds (FIPR-POLL-INTERVAL) later, it will not be reported until this frequency parameter is reached. If it is set to ‘1’ then it will be reported constantly until the file problem is resolved.
FIPR-POLL-INTERVAL	15 thru 1800 seconds Deafult – 60	Warm-boot Reaction module	This parameter is used by the file monitoring software within the Heartbeat module of Reflex. It can be set to 15 seconds thru 30 minutes depending on the user assigned requirement. A file will be checked for existence between an assigned calendar period at the interval specified here.
FIPR-PRES-SUPPRESS	Y, N Default – N	Warm-boot Reaction module	This parameter does NOT stop the file existence monitoring EMS messages from being emitted but controls whether they are seen in normal EMS viewing consoles like CONSOLE, ViewpointTM and View + Point. This is achieved by Reflex placing a suppress token in the EMS event to make it invisible on the system. The purpose of this is to allow the event to be seen in the Reflex graphical status monitor display where important events have been consolidated rather than adding more noise to the collectors on the Tandem node.

 

Parameter Name	Value(s)	Warmboot	Description of Use
HEARTBEAT-EMS-SUPPRESS	Y, N Default – N	Warm-boot Reaction module	This parameter does NOT stop the Heartbeat process monitoring EMS messages from being emitted but controls whether they are seen in normal EMS viewing consoles like CONSOLE, ViewpointTM and View + PointTM. This is achieved by Reflex placing a suppress token in the EMS event to make it invisible on the system. The purpose of this is to allow the event to be seen in the Reflex graphical status monitor display where important events have been consolidated rather than adding more noise to the collectors on the Tandem node.
MAX-DISCS	Default value is set to 1200. The range of values is 500 to 1500.	Stop/Start Reflex	This parameter is used to determine the maximum number of disks that can be configured on Reflex.
MEM-PRESSURE-THRESHOLD	Default value is set to 1. The range of values is 0 to 7.	Stop/Start Reflex	This parameter is used by Dashboard to determine the frequency of page faults on a CPU during a CPU poll interval, before Reflex flags a warning.
MEM-Q-LEN-THRESHOLD	Default value is set to 1. The range of values is 0 to 100.	Stop/Start Reflex	This parameter is used by Dashboard to determine the current number of processes waiting for a page fault to be serviced on a CPU during a CPU poll interval, before Reflex flags a warning.
MULTIBATCH-INVESTIGATE	Y, N Default - N	Warm-boot Reaction module	This parameter is used in conjunction with the Multibatch product. If you have autodetected a Multibatch schedule (using MULTIBAG), the resulting object tree will consist of a jobs, segments and units. When a Status Monitor warm-boot takes place, each job will not be investigated for status using the Multibatch agent (AGENT-MULBAT). Instead, the Multibatch environment will be interrogated using the same agent, for failed jobs only at the end of the warm-boot. This will speed up the warm-boot operation for large scheduling environments.
NUM-TRXS-PER-TMF	0 thru 500 Default – 100	Stop/Start Reflex	This parameter determines how many SQL database record changes are allowed to takes place (delete, insert, amend) before the changes are commited to the Reflex 80:20 database. The default is usually recommended.
PAGE-FAULT-THRESHOLD	0 thru 999 Default – 20	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	This parameter is used by Dashboard to determine how many page faults are allowed before Reflex flags a performance lack on the appropriate CPU. An EMS event will be raised and the appropriate graph will show RED for the offending CPU. Page fault exceeded EMS event - 2554 Page fault no longer exceeded EMS event - 2562
PATHMON-PROCESS	The name of the Reflex Pathmon process Default $RFLX 5 characters including the ‘$’ sign.	Stop/Start Reflex	This parameter should be set-up at the beginning of a product install of Reflex 80:20. It is the name of the Pathway process. It should not exceed 5 characters which includes the ‘$’ sign. It is used by Tandem processes for internal message sending to appropriate servers within the Reflex application. For networked Reflex applications, this process name should be the same, be owned by the same user with the same remote passwords.
PCBS-HI-PIN-THRESHOLD	Default value is set to 1024. The range of values is 0 to 9000.	Stop/Start Reflex	This parameter is used by Dashboard to determine the number of High Pin Process Control Blocks in the Processor that are in use during a CPU poll interval, before Reflex flags a warning.

 

Parameter Name	Value(s)	Warmboot	Description of Use
PCBS-LOW-PIN-THRESHOLD	Default value is set to 768. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine the number of Low Pin Process Control Blocks in the Processor that are in use during a CPU poll interval, before Reflex flags a warning.
PMON-MSG-FREQUENCY	1 thru 99 Default – 10	Warm-boot Reaction module	This parameter controls how often the same EMS event is output if a process is found to be in the same state. For example, if a process is in a DOWN state then Reflex will generate a down EMS event (as configured by the user in the next section). If the process is down the next time it polls then the process monitor will not raise another EMS message until it has polled ‘PMON-MSG-FREQUENCY’ times at which point, it will raise the down EMS message again. This is to cut down on EMS event pollution on the EMS logs.
PMON-POLL-INTERVAL	15 thru 1800 Default – 30	Warm-boot Reaction module	This is the poll interval in seconds that the Reflex 80:20 non-stop process monitor will check the configured processes as to their UP/DOWN status. This is used in conjunction with the ‘PMON-MSG-FREQUENCY’ parameter. The defaults are a frequency of ‘10’ and a poll interval of ‘30’ seconds. The result here would be that a process down would not be re-reported until ’10 * 30’ seconds later, i.e. 5 minutes.
PROCESS-BUSY-THRESHOLD	0 thru 99 Default – 30	Stop/Start Reflex (alternatively warm-boot status monitor set-up (!) icon and freeze, stop thaw a start Reflex REFLEX-THRESH Pathway server)	This parameter is used by Dashboard module to determine when a process should be flagged as being unusually busy for a particular Tandem node. This will result in an EMS message being raised to the EMS log which can optionally be used to drive a graphical icon in the status monitor screen. Exceeded threshold event – 2559 No longer exceeded threshold event – 2565
REFLEX-CATALOG	A valid SQL catalog subvolume Default \INSIDER. $DATA02. RFCATnn	Stop Reflex – reSQLCOMPile and restart Reflex	This parameter is set up at the beginning of a full Reflex 80:20 installation to instruct the SQL compiler to register any Reflex SQL embedded objects with the catalog named here. Once an SQL catalog is created it should not be touched.
REFLEX-FEEDER-FLAG	Y, N Default – N	Stop/Start Reflex	This parameter determines whether or not CPU, Disk, File and Status Monitor metrics are relayed to a Fastpipe client on the Tandem which then forwards them to a nominated NT server. The Tandem will affix a timestamp to each record sent. On the NT box, the data is written to an OCBC database where it can be accessed for graphing and trending for management reporting. For more information on this aspect of Reflex, contact ITL. The feeder mechanism requires licensing. The AVAILAB-FEEDER server configuration within PWCONF should be amended with the appropriate details.
REMOTE-SYSTEM-MONIT	Y, N Default – N	Stop/Start Reflex	It is possible (with the aid of forwarding distributors) to send events to a central Reflex 80:20 application where they can be used to drive graphical icons on the Status Monitor screen. If this flag is set to ‘Y’ then the system check within the Reflex 80:20 ECALLFLT filter (object – ECALFOB) will be taken out and all events from all Tandem platforms with the same SSID and event number will be processed if they have been configured in the local Reaction engine.

 

Parameter Name	Value(s)	Warmboot	Description of Use
RUNTASK-LOCATION	Free text Default \INSIDER. $DATA02. RFOB41. RUNTASK	Stop/Start Reflex	This parameter informs the TASKMASTER module of the location of the RUNTASK code. This code is used to initiate any programs set-up in the Tasks module of the Reflex client GUI.
SCF-PUP-LOCATION	Default value is set to $SYSTEM.SYSTEM.PUP	Stop/Start Reflex	This parameter is used to determine the location of the PUP / SCF process.
SELECT-REMOTE-ALERT	Default - NNNNN	Warmboot Status Monitor and re-logon to the GUI.	Reflex 80:20 can alert to both TIVOLI and COMMAND/POST as well as the ITL product SENTRA which monitors NT servers in the same way Reflex monitors Tandems. The flags represent: Tivoli NT, Tivoli Tec, Command/Post, SMS, Sentra Respectively. Flag 2 is not currently in use. The ENT-MNGR-FEED-DISARM flag (discussed above) should be turned on if using this flag. Also, edit the RUNEMON file and change the ENT^MGR flag to point to either CMND-POST-REACT or TIVOLI-REACT depending on your chosen enterprise manager. For SMS and SENTRA, either specification is OK.
SMON-GRP-HEALTH	Y, N Default – N	Warmboot Status Monitor	This parameter dictates whether an EMS event is generated if a top-level group changes status. This event could be used to generate an appropriate reaction of forward to an Enterprise Manager. The Events generated are 2457 thru 2459.
SMON-GRP-HEALTH-SUPP	Y, N Default – Y	Warmboot Status Monitor.	This parameter does NOT stop the Status Monitor group level monitoring EMS messages from being emitted but controls whether they are seen in normal EMS viewing consoles like CONSOLE, ViewpointTM and View + Point. This is achieved by Reflex placing a suppress token in the EMS event to make it invisible on the system. The purpose of this is to allow the event to be seen in the Reflex graphical status monitor display where important events have been consolidated rather than adding more noise to the collectors on the Tandem node.
SMON-SERVERCLASS	Name of the Reflex 80:20 status monitor server – legacy	Legacy.	No longer used.
SPOOLER-FREQUENCY	1 thru 99 Defualt – 1	Stop/Start Agent-spooler in the Reflex 80:20 Pathway	This parameter controls the frequency that the same state is reported by way of an EMS event message. For instance, if a spooler component is found to be in error or other offending state, an EMS message will be generated. If it is found to be in the same state N seconds (SPOOLER-INTERVAL) later, it will not be reported until this frequency parameter is reached. If it is set to ‘1’ then it will be reported constantly until the spooler problem is resolved.
SPOOLER-INTERVAL	5 thru 720 seconds Default – 5	Stop/Start Agent-spooler in the Reflex 80:20 Pathway	This is the poll minutes in seconds that the Reflex 80:20 spooler monitor will check the configured spooler components as to their UP/DOWN/VULNERABLE status. This is used in conjunction with the ‘SPOOLER-FREQUENCY’ parameter. The defaults are a frequency of ‘5’ and a poll interval of ‘1’ minute. The result here would be that a spooler component in an offending state would not be re-reported until ’5 * 1’ minutes later, i.e. 5 minutes.

 

Parameter Name	Value(s)	Warmboot	Description of Use
SPOOLER-SUPPRESS	Y, N Default – N	Stop/Start Agent-spooler in the Reflex 80:20 Pathway	This parameter does NOT stop the spooler monitoring EMS messages from being emitted but controls whether they are seen in normal EMS viewing consoles like CONSOLE, ViewpointTM and View + Point. This is achieved by Reflex placing a suppress token in the EMS event to make it invisible on the system. The purpose of this is to allow the event to be seen in the Reflex graphical status monitor display where important events have been consolidated rather than adding more noise to the collectors on the Tandem node.
SPOOLER-THRESHOLD	0 thru 99 Default – 70	Stop/Start Agent-spooler in the Reflex 80:20 Pathway	This is the threshold at which an EMS event will be generated for a spooler collector should it become close to full. The event raised is 5071 (over threshold), 5072 (spooler full).
STATS-COLLECTOR	Free text Default - $DATA02. RFOBnn. STATCOLL	Stop/Start Reflex	Consumer Distributor That Collects And Tabulates Statistics To Be Output To a printer, disc file or PC Format file. This parameter represents the location of the object file which collects the EMS events for the nominated time window.
STATS-DICT	Free text Default - $DATA02. RFDDnn	Stop/Start Reflex	A Reflex 80:20 sub-volume that contains the REFLEX Data Dictionary. The PCFORMAT program used by the Discovery module uses the dictionary to produce a CSV file for the PC. PCFORMAT is supplied by Tandem in earlier release of the K series operating system.
STATS-PROCESS	Valid process name Default - $STAT	Stop/Start Reflex	When Discovery is selected and a request submitted to graph the various EMS alerts that have occurred within the given time period, the discovery program specified by STATS-COLLECTOR will be given the process name specified here. Only 1 of these processes can be running at any one time.
SUBJECT-HISTORY-SIZE	Less than 1000 Default – 10	Warmboot Status Monitor	This parameter represents the number of EMS messages held for a particular Status Monitor object.  For example, if 5 were selected then up to 5 events would be held before the oldest event was replaced by the newest. The value entered should preferably be greater than the last entered unless emptying out the history tables and restarting Reflex 80:20.
TASK-Q-LEN	Default – 5	Stop/Start Reflex	The number of tasks of the same name which will be queued for action by TaskMaster.
TIME-OUT	>= 120 seconds Default - 3600 seconds	Legacy.	Used previously for the green screen time out if the product is not used. The green screen is no longer suppported.
TITLE	Free tex Default ‘.’	Legacy.	Used for the totle bar in the green screen version of Reflex. This version is no longer supported.
TLES-CURRENT-THRESHOLD	Default value is set to 1000. The range of values is 0 to 1250.	Stop/Start Reflex	This parameter is used by Dashboard to determine the number of Time List Elements in the Processor that are in use during a CPU poll interval, before Reflex flags a warning.
TREE-PROCESSING-QUEUE	Default – 70, Maximum 100	Warmboot	Used between the event monitor and status monitor during a warmboot so that events are not lost when this is being carried out.
X25-DASH-MSG-FREQ	Default value is set to 2. The range of values is 1 to 99.	Stop/Start Reflex	This parameter is used in conjunction with all the other Dashboard parameters. It controls ‘how often’ to output a X25 threshold breached message.
X25-FRAME-RECV-REJ-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many Rejects were received at the Frame Level, during a Frame Level Threshold interval, before Reflex flags a warning on the X25 line.

 

Parameter Name	Value(s)	Warmboot	Description of Use
X25-FRAME-RECV-RNR-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many RNR’s were received at the Frame Level, during a Frame Level Threshold interval, before Reflex flags a warning on the X25 line.
X25-FRAME-SENT-REJ-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many Rejects were sent at the Frame Level, during a Frame Level Threshold interval, before Reflex flags a warning on the X25 line.
X25-FRAME-SENT-RNR-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many RNR’s were sent at the Frame Level, during a Frame Level Threshold interval, before Reflex flags a warning on the X25 line.
X25-FRAME-THRESHOLD-INTERVAL	Default value is set to 60. The range of values is 1 to 1440.	Stop/Start Reflex	This is the interval that is used by Dashboard Thresholding to check if a X25 Frame Level threshold has been exceeded.
X25-LINE-QUALITY-THRESHOLD	Default value is set to 90. The range of values is 0 to 100.	Stop/Start Reflex	This parameter is used by Dashboard to determine the percentage of Line Quality before Reflex flags a warning on the X25 line. Note that this is a minimum value, i.e. the threshold is breached if the Line Quality falls below this value.
X25-MODEM-ERR-THRESH-INTERVAL	The range of values is 1 to 1440. Default value is set to 60.	Stop/Start Reflex	This is the interval that is used by Dashboard to determine if the Modem Errors threshold has been exceeded.
X25-MODEM-ERROR-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many Modem Errors occur during a Modem Error Threshold interval before Reflex flags a warning on the X25 line.
X25-NUMBER-OF-SU-TO-MONITOR	Default value is set to 50. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to allocate memory for an internal table holding the state of the Su’s Reflex will monitor. It should be large enough to accommodate the number of Su’s on all the X25 lines that are configured for monitoring.
X25-PACKET-RECV-REST-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many Restarts were received at the Packet Level, during a Packet Level Threshold interval, before Reflex flags a warning on the X25 line.
X25-PACKET-RECV-RNR-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many RNR’s were received at the Packet Level, during a Packet Level Threshold interval, before Reflex flags a warning on the X25 line.
X25-PACKET-SENT-REST-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many Restarts were sent at the Packet Level, during a Packet Level Threshold interval, before Reflex flags a warning on the X25 line.
X25-PACKET-SENT-RNR-THRESHOLD	Default value is set to 10. The range of values is 0 to 1000.	Stop/Start Reflex	This parameter is used by Dashboard to determine how many RNR’s were sent at the Packet Level, during a Packet Level Threshold interval, before Reflex flags a warning on the X25 line.
X25-PACKET-THRESHOLD-INTERVAL	Default value is set to 60. The range of values is 1 to 1440.	Stop/Start Reflex	This is the interval that is used by Dashboard Thresholding to check if a X25 Packet Level threshold has been exceeded.
X25-POLL-INTERVAL	Default value is set to 60. The range of values is 60 to 2880.	Stop/Start Reflex	This parameter is the X25 poll interval, which is used by Dashboard to poll for X25 status.

 

Parameter Name	Value(s)	Warmboot	Description of Use
X25-SU-IN-USE-THRESHOLD	Default value is set to 70. The range of values is 0 to 100.	Stop/Start Reflex	This parameter is used by Dashboard to determine the percentage of how many SU’’s are in use (started) out of the available SU’s before Reflex flags a warning on the X25 line.
X25-SU-NOT-STARTED-SUPPRESS	Default value is set to N.	Stop/Start Reflex	This parameter is used to control whether events are suppressed for any X25 SU’s that are not started on a line that is being monitored.

13.2.         Currently Delivered Reaction Event Ranges in the Reflex 80:20 Database

This section describes the pre-delivered Reaction module database that can be seen by clicking on the Reaction button on the main toolbar of Reflex 80:20, maximising the Reaction window and then clicking on the Reaction List tab to display the list of currently set-up event ranges.

If any of these events are not required to be alerted on, amend the cover period for the event range by double clicking on the event and subsequently going into the Action Group tab to amend the cover period. After this, warm-boot the reaction servers by clicking on the ‘!’ icon and carrying out the third option. For a description of the cause, effect and recovery texts (for the ‘INSIDER.50’ events), edit the TEMPLATE file in your Reflex DDL dictionary sub-volume and search on the event numbers.

 

Subsystem ID	Event Number Range	Cover Period From	Cover Period To	Action Group Name	Description
INSIDER.50	+00001	20-03-1996 00:00	20-03-1998 23:59	TAP-PROTOCOL-EXAMPLE	This is an example of a typical set-up for paging to a modem plugged into the back of the Tandem node. Cover period not active for this event range.
INSIDER.50	+02553 - +02556	20-03-1996 00:00	20-03-2020   23:59	DASHBOARD-SYSTEM-MET	These events are threshold exceeded messages for CPUs and disks; CPU busy, > Page Faults, > CPU Queue and > disk space respectively. See administration module – parameters.
INSIDER.50	+02558 - +02560	20-03-1996 00:00	20-03-2020   23:59	DASHBAORD-SYSTEM-MET	Suspect process messages; non-running state, > % busy, priority changed respectively. See administration module – parameters.
INSIDER.50	+02561 - +02565	20-03-1996 00:00	20-03-2020   23:59	DASHBOARD-SYSTEM-MET	These events are threshold NO LONGER exceeded messages for CPUs and disks; CPU not busy, < Page Faults, < CPU Queue and < disk space respectively. See administration module – parameters.
INSIDER.50	+02566	20-03-1996 00:00	20-03-2020   23:59	DASHBOARD-SYSTEM-MET	Disk fragmentation parameter has been exceeded. See administration module – parameters.
INSIDER.50	+02567	20-03-1996 00:00	20-03-2020   23:59	DASHBOARD-SYSTEM-MET	Disk fragmentation parameter is no longer exceeded. See administration module – parameters.
INSIDER.50	+02602	20-03-1996   00:00	20-03-2020 23:59	CONSOLE-ALERT-CRITIC	It is possible to have Reflex spot any CRITICAL token EMS events that have not been configured in the reaction database for graphical reporting. With this event, any critical event can be sent to an icon in Status Monitor to flash an icon red thereby indicating to an operator that a critical event may need to be included in the general Reflex configuration.
INSIDER.50	+02603	20-03-1996 00:00	20-03-2020   23:59	CONSOLE-ALERT-VULN	As above but for ACTION NEEDED events.
INSIDER.50	+05060	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-UP	Spooler supervisor active message.
INSIDER.50	+05061 - +05064	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	In Order:  Spooler Drain  Spooler is Warm Starting  Spooler is Cold starting  Spooler has a PROC ERROR.
INSIDER.50	+05066	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	Reflex 80:20 configured spooler not found. A spooler is present in a Status Monitor object tree but is not present in the SPOOLCOM configuration.

 

Subsystem ID	Event Number Range	Cover Period From	Cover Period To	Action Group Name	Description
INSIDER.50	+05070	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-UP	Spooler collector active.
INSIDER.50	+05071	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-VULN	Spooler collector is over threshold.
INSIDER.50	+05072 - +05073	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	In Order:    Collector is full   Collector is draining.
INSIDER.50	+05074	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-UP	Collector is dormant
INSIDER.50	+05075	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	Collector has a PROC ERROR.
INSIDER.50	+05077	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	Reflex 80:20 configured collector not found. A collector is present in a Status Monitor object tree but is not present in the SPOOLCOM configuration.
INSIDER.50	+05080 - +05081	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-UP	In Order:  Print process active  Print process is dormant.
INSIDER.50	+05082	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	Print process has a PROC ERROR.
INSIDER.50	+05084	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	Reflex 80:20 configured print process not found. A print process is present in a Status Monitor object tree but is not present in the SPOOLCOM configuration.
INSIDER.50	+05090 - +05091	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-UP	In Order:  Device is waiting  Device is busy.
INSIDER.50	+05092	20-03-1996 00:00	20-03-2020      23:59	SPOOLER-OBJECT-DOWN	Device is OFFLINE.
INSIDER.50	+05093	20-03-1996    00:00	20-03-2020      23:59	SPOOLER-OBJECT-UP	Device is printing.
INSIDER.50	+05095 - +05096	20-03-1996 00:00	20-03-2020      23:59	SPOOLER-OBJECT-DOWN	In Order:  Device has a DEVICE ERROR  Device has a PROC ERROR.
INSIDER.50	+05098	20-03-1996 00:00	20-03-2020   23:59	SPOOLER-OBJECT-DOWN	Reflex 80:20 configured device not found. A device is present in a Status Monitor object tree but is not present in the SPOOLCOM configuration.
INSIDER.50	+05110	20-03-1996    00:00	20-03-2020   23:59	FILE-AGENT-UP	This action group is no longer required as at release 4.0 of Reflex 80:20.
INSIDER.50	+05111 - +05112	20-03-1996 00:00	20-03-2020    23:59	FILE-AGENT-DOWN	As for previous.
TANDEM.4	+00406	01-01-1995 00:00	01-01-2020   23:59	TAPECHANGE	Tandem tape change event.
TANDEM.8	+01043	20-03-1996 00:00	20-03-2020   23:59	PATHWAY-OBJ-STARTED	Pathway server has been started within an application Pathway. Note that Pathway events are only written to the EMS log if activated.
TANDEM.8	+01047	20-03-1996 00:00	20-03-2020   23:59	PATHWAY-OBJ-TCPTERM	Pathway TCP Terminal aborted.
TANDEM.8	+01064 - +01065	20-03-1996 00:00	20-03-2020   23:59	PATHWAY-FREEZE-THAW	Freeze and thaw operations on servers being carried out.
TANDEM.12	+00007	01-01-1994 09:00	01-12-2020   18:00	ASYNC-DOWN	Asynchronous line is down.
TANDEM.15	+00100	10-05-1995 00:00	10-05-2020   23:59	INSIDER-UP	CPU up event.

 

Subsystem ID	Event Number Range	Cover Period From	Cover Period To	Action Group Name	Description
TANDEM.15	+00100	20-03-1996 00:00	20-03-2020   23:59	INSIDER-DOWN	CPU down event.
TANDEM.31	+05015	09-03-1995 00:00	31-12-2020   23:59	DISK-DOWN	Tandem disk down event.
TANDEM.31	+05018	09-03-1995 00:00	31-12-2020   23:59	DISK-UP	Tandem disk up event.
TANDEM.41	+00006	09-09-1994 00:00	31-12-2020   23:59	X25-RAISED	X25 line started.
TANDEM.41	+00007	09-09-1994 00:00	31-12-2020   23:59	X25-RESTART	X25 line has been restarted.
TANDEM.45	+00009	20-03-1996 00:00	20-03-2020   23:59	MHS-STATE-PLUS-NINE	X400 messaging component down.
TANDEM.45	-00003	20-03-1996 00:00	20-03-2020   23:59	MINUS-STATE-MINUS-THREE	X40 messaging component is UP.
TANDEM.160	+06508	01-01-1995 00:00	01-01-2020   23:59	RESTART-TCPIPPORT	Restart of RSC TCPIP ports.

 

13.3.         Viewpoint^TM Configuration for Copying EMS Events into Reflex 80:20

If you have Viewpoint on the Tandem system where Reflex 80:20 has been installed, then there is a further facility available which enables Viewpoint events to be placed in the Reflex 80:20 database. This is done using the Viewpoint “EXTRAS” function key (SF15) provided as standard with Viewpoint.

In order to make use of this facility (described in Chapter 4 of the user manual) the following conditions must be satisfied:

·         You must have Viewpoint on your Tandem system

·         The file supplied by Insider Technologies (ZVPT-EXTRAS) which is called by the SF15=EXTRAS function key in Viewpoint must be in the Viewpoint PATHWAY. This is done (while logged on with sufficient security privilege to modify Viewpoint) as follows:

> SCUP COPY RFLXOBJ.POBJ (ZVPT-EXTRAS (*)),

                                    <Viewpoint Sub-Volume>.POBJ                                                 [return]

where RFLXOBJ is your Reflex 80:20 object sub-volume

·         The Viewpoint PATHWAY must be modified to include the Insider Technologies supplied server, REFLEX-CONTEXT.

Carry out the following command after the above edit:

> PATHCOM / in

            RFLXOBJ.VWPTSERV / $<Viewpoint PATHMON Process>    [return]

where RFLXOBJ is your Reflex 80:20 object sub-volume

 

13.4.         Upgrading your own Reflex 80:20 Product Licences

Insider Technologies will provide licence files with all their software. These files are used to restrict the use of the product to specific Tandem nodes and CPUs for a specific period of time.

When the product is purchased, you are provided with an ENSCRIBE licence file and a Tandem edit file containing relevant licence details.

When the licence requires updating (e.g. when additional modules are purchased), you can edit the files provided (see note above). Normally this would involve modifying:

·         the expiry date

·         the Tandem node name and/or CPU type

·         the product field of any added facilities to the relevant product name

·         the appropriate CHECK_FIELD field (this is supplied by Insider Technologies)

To re-load your licence file you must:

·         Set-up the following defines:

=INSIDER_LICENCE (pointing to the licence file, normally RFLXDAT.LICENCE where
RFLXDAT is your nominated Reflex 80:20 data files sub-volume)

=INSIDER_FACILITY_FILE (pointing to RFLXDAT.FACILDB where RFLXDAT is your nominated Reflex 80:20 data files sub-volume)

·         LOAD the licence files as follows:

            C30LLICO / in <edit_licence_file> /

            C30LFACO / in <edit_facility_file> /

 

·         Load the PATHWAY application and so on.

 

 

The CHECK_FIELD supplied is checked and, if valid, the new licence details are activated.

 

 

13.5.         Reflex 80:20 PATHWAY Server Configuration

This section categorises the various servers that execute within the Reflex 80:20 PATHWAY in terms of their functional areas. The process names are given although the prefix of ‘$RX’ may have been changed to avoid clashes with your own environment.

 

SERVER NAME :	PROCESS :	OBJECT :	SQL :	PATHWAY PARAMS :	GUI ADMINISTRATION PARAMETERS (PARACONF) :
Administration:
Reflex-admin	$RXAD	SRVADMIN	No		Time-out, audit-flag, title, NB: validates all entered parameters
Reflex-auditlog	$RXAU	SRVALL	No
Status Monitor:
Agent-file	$RXFI	FILEAG	No
Agent-mulbat	$RXMB	MULTIBAG	No
Agent-osimhs	$RXOS	OSIMHSAG	No
Agent-path	$RXPA	PATHAG	No
Agent-proc	$RXAP	PROCAG	No
Agent-tandem-hw	$RXHW	TANHWAG	No
Reflex-smon	$RXSM	SRVSMOQ	Yes	Interval	Num-trxs-per-tmf, pathmon-process, subject-history-size, reflex-feeder-flag, smon-grp-health, smon-grp-health-supp, select-remote-alert
Reflex-smon-db	$RXSD	SRVSMDB	Yes		Action-group-down, action-group-up, audit-flag
Reflex-todrive	$RXOD	SRVTOD	No
Smon-setup	$RXSE	SRVSETUP	Yes		Audit-flag, num-trxs-per-tmf, pathmon-process,
Smon-processing	$RXPM	SRVSMPQ	Yes	Interval	Num-trxs-per-tmf, pathmon-process, subject-history-size, reflex-feeder-flag, smon-grp-health, smon-grp-health-supp, multibatch-investigate, select-remote-alert, tree-processing-queue
Status-queue	$RXQU	SRVQUECO	Yes	Max-queue	Reflex-smon, pathmon-process
Service Monitor:
Data-analysis	$RXDT	SRVDAACO	Yes		Pathmon-process, num-trxs-per-tmf, data-analysis-trace-flag
Data-def-setup	$RXDF	SRVDDEFQ	Yes		Audit-flag
Data-forwarding	$RXFW	SRVFWDCO	Yes	Errorinterval, Heartinterval	Pathmon-process
Rules-analysis	$RXRA	SRVRUACO	Yes		Pathmon-process, num-trxs-per-tmf
Rules-bld-setup	$RXRB	SRVSMRCO	Yes		Audit-flag
Service-display	$RXDP	SRVDISMQ	Yes
Service-setup	$RXS1	SRVSEMSC	Yes		Pathmon-process, audit-flag
Dashboard:
Dash-master	$RXDB	SRVDASH	Yes		Cpu-poll-interval, disk-poll-interval, cpu-busy-threshold, cpu-queue-threshold, disk-full-threshold, disk-frag-threshold, page-fault-threshold, dash-suspect-interval, process-busy-threshold, dash-thresh-suppress, cpu-dash-msg-freq, disk-dash-msg-freq, dash-suspect-suppress
Dash-thresh	$RXTH	SRVTHRSH	No

 

SERVER NAME :	PROCESS :	OBJECT :	SQL :	PATHWAY PARAMS :	GUI ADMINISTRATION PARAMETERS (PARACONF) :
Discovery:
Reflex-stats	$RXAT	SRVSTAT	No		Stats-dict, stats-collector, stats-process, audit-flag
Gateway:
Reflex-s-stats	$RXSS	SRVSPS	No
Reflex-stream	$RXES	SRVESTRM	No		Audit-flag,
Console:
Console	$RXCO	SRVCONS	No		Console-alerts-flag
Event Database:
Reflex-ec-list	$RXLS	SRVRAL	No
Reflex-eventcx	$RXCX	SRVCX	No		Audit-flag
Reflex-eventdb	$RXEV	SRVEVDB	No		Audit-flag
Reflex-eventtd	$RXTD	SRVEVT	No
Enterprise Management:
Cmnd-post-react	$RXCR	CMDPGENC	Yes	Max-cmnd-msgs	Pathmon-process, select-remote-alert
Cmnd-post-setup	$RXPS	SRVCMDPC	Yes		Audit-flag
Ent-mngr-feeder	$RXEM	EMGRFDCP	No	RA, RD, RG, RH,RI	Ent-mngr-feed-disarm
Remote-delivery	$RXRD	REMOTECQ	Yes	Remote, tivoli, tcpip	Pathmon-process
Tivoli-react	$RXTV	TIVOGENC	Yes	Array-entries, heartbeat, interval	Pathmon-process, select-remote-alert
Taskmaster:
Reflex-tasks	$RXTA	SRVTASK	Yes		Audit-flag, task-q-len
Miscellaneous:
Availab-feeder	$RXAV	RFLXFDCO	No	RA through RI	Reflex-feeder-flag
Calendar-setup	$RXCS	SRVCALEQ	Yes		Audit-flag, num-trxs-per-tmf,
Dash-datacol	$RXDA	SRVDACOL	Yes		Reflex-feeder-flag
Insider-help	$RXHP	SRVHELP	No
Pagegen-taps	$RXTS	SRVTAPS	Yes
Reflex-calmon	$RXCA	CALMON	Yes
Reflex-egen	$RXEG	SRVEGEN	No		Audit-flag
Reflex-ping	$RXPI	SRVPING	No
Reflex-wildcard	$RXAL	SRVWILD	No

 

SERVER NAME :	PROCESS :	OBJECT :	SQL :	PATHWAY PARAMS :	GUI ADMINISTRATION PARAMETERS (PARACONF) :
Heatbeat:
File-mets-monit	$RXF1-5	FIMEMONQ	Yes	Max-files, info-events	Fime-poll-interval, fime-msg-frequency, fime-mets-suppress, reflex-feeder-flag, pathmon-process
File-mon-set-up	$RXFS	SRVFMNSQ	Yes		Audit-flag, action-group-down, action-group-up, action-group-vuln
File-pres-monit	$RXFM	FIPRMONQ	Yes	Max-files, info-events	Fipr-poll-interval, fipr-msg-frequency, fipr-mets-suppress, reflex-feeder-flag, pathmon-process
Reflex-procmon	$RXPR	SRVRPM	Yes		Action-group-down, action-group-up, audit-flag
Reaction:
Reflex-c-action	$RXAE	SRVRAU	Yes		Audit-flag
Reflex-c-cmnds	$RXCM	SRVRCU	No		Runtask-location, audit-flag
Reflex-c-events	$RXMG	SRVRDE	No		Audit-flag
Reflex-c-ops	$RXOP	SRVRCM	No		Audit-flag, remote-system-monit
Reflex-c-page	$RXPG	SRVRRP	No		Audit-flag
Reflex-c-wdog	$RXWD	SRVRWA	No		Audit-flag
Reflex-p-cancel	$RXCP	SRVAPL	No
Snmp-details	$RXS2	SRVSNMP	No		Audit-flag
Snmp-out	$RXSN	SNMPT	No
Connectivity:
Fastpipe-backup	$RXFB	FASTPIPE	No	Location of FPINI
Fastpipe-server	$RXFP	FASTPIPE	No	Location of FPINI2
Spooler Monitoring:
Agent-spooler	$RXSG	SPOOLAG	Yes		Spooler-interval, spooler-threshold, spooler-frequency, spooler-suppress
X25 Monitoring:
Agent-X25	$RX25 (used in SMON)	X25AG	No
Dash-X25	$RXDX (used in Dashboard)	SRVDX25	Yes		X25-poll-interval, x25-dash-msg-freq, x25-su-not-started-msg-freq, x25-su-not-started-suppress, x25-number-of-su-to-monitor
BASE24 XPNET Monitoring (Status Monitor):
ACI-XPNET-AGENT	$RXXP	XPNETAGC	No	XA $PPMN XB SERVER-NCP XC 1500 XD 0 XE 0 XF 0	Pathmon-process Note: Also reads RFLXDAT.xpnetcnf for configuration values for Base24 application.

 

13.6.         Reflex 80:20 PATHWAY Server Descriptions

This section categorises the various servers that execute within the Reflex 80:20 PATHWAY in terms of their functional areas as well as providing a description of each.

 

SERVER NAME :	PROCESS :	DESCRIPTION:
Administration:
Reflex-admin	$RXAD	Takes care of the logon dialog and session of the GUI client and the maintenance of the files and parameter records and both the security classes and profiles.
Reflex-auditlog	$RXAU	Responsible for the browsing of the Reflex 80:20 audit log by terminal, timestamp, facility and Guardian user.
Status Monitor:
Aci-xpnet-agent	$RXXP	This server is responsible for retrieving information, status and statistics of a particular BASE24 XPNET object. It is called when Detailed Information of a XPNET object is requested from the Status Monitor screen.
Agent-file	$RXFI	This server allows for the passing back of complete Tandem file details to the info request of the Overdrive - Status Monitor screen. It will also accept a status request which will reply with either file present or not present.
Agent-mulbat	$RXMB	This server allows for the passing back of complete MULTIBATCH job details to the info request of the Overdrive - Status Monitor screen. It will also accept a status request which will reply with either job failed or OK.
Agent-osimhs	$RXOS	This server allows for the passing back of complete messaging X400 details to the info request of the Overdrive - Status Monitor screen. It will also accept a status request which will reply with either messaging component in error or otherwise.
Agent-path	$RXPA	This server allows for the passing back of complete Pathway component details to the info request of the Overdrive - Status Monitor screen. It will also accept a status request which will reply with either Pathway component (e.g. server) failed or otherwise.
Agent-proc	$RXAP	This server allows for the passing back of complete Tandem process details to the info request of the Overdrive - Status Monitor screen. It will also accept a status request which will reply with either process present or not present.
Agent-tandem-hw	$RXHW	This server allows for the passing back of Tandem hardware device details to the info request of the Overdrive - Status Monitor screen. It will also accept a status request which will reply with either hardware present or not present.
Agent-x25	$RX25	This server is responsible for retrieving information, status and statistics of a particular X25 Line or X25 Sub Unit. It is called when Detailed Information of a X25 object is requested from the Status Monitor screen.
Reflex-smon	$RXSM	This is the Status Monitor server which hooks up to the live Overdrive – Status Monitor screen. This server and process should always be running and is key to displaying critical, vulnerable and acknowledged objects in the drill down object trees. The Event Monitor process passes status EMS events directly to it to provide graphical status information about Tandem components to operators.
Reflex-smon-db	$RXSD	Responsible for the maintenance of the Network Hierarchy SQL table (NETWHIEQ) and the maintenance of Status Monitor reactions (ACTWDOG) for graphical alerting purposes.
Reflex-todrive	$RXOD	Server no longer used.
Smon-setup	$RXSE	Server that sets up the various trees in Status Monitor as part of the dragging and dropping of Tandem object components into drill down trees. It also handles requests for Status Monitor set-up warm-boot.
Smon-processing	$RXPM	This server is responsible for handling the more time consuming processing previously handled by the REFLEX-SMON server-class, for example checking the status of a tree.
Status-queue	$RXQU	Used only in cases where the sheer volume of Tandem objects (e.g. a large Pathway tree) causes slow response times in the live Status Monitor screens after warm-boot. This process handles status requests by passing indeterminate status (orange) back to Status Monitor and subsequently chasing the actual status of a Tandem component that it will feed to Status Monitor in a NOWAITed mode.

 

SERVER NAME :	PROCESS :	DESCRIPTION:
Service Monitor:
Data-analysis	$RXDT	Server that breaks up incoming APIs from the forwarding processes into their component parts based on definitions provided to it in the data definition dialogs of the Reflex client. This server then writes these individual field values to the cache table (DATCACHQ) for analysis by the RULES-ANALYSIS server.
Data-def-setup	$RXDF	This server is provided to allow for the setting up of data definition APIs for any APIs that require to be fed through to Service Monitor for analysis. This circumvents the necessity to hard-code API structure definitions in the Reflex product so that third party applications can plug in easily to the Server Monitor infrastructure.
Data-forwarding	$RXFW	A DATA-FORWARDING server exists on all Reflex nodes in a Service Monitor network to allow for the passing of APIs up to the parent node for rules analysis. Reflex service monitoring takes place on the nominated parent node.
Rules-analysis	$RXRA	This server will search for any rules set-up in service monitor, which have been tagged by the DATA-ANALYSIS server as requiring a scan for status. This will be based on the fact that 1 or more field attributes referenced within the rule have changed value.
Rules-bld-setup	$RXRB	A server supplied to enable the setting up of rules for the Service Monitor module. Fields within incoming APIs can be grouped and compared to various values to establish whether agreed service level agreements are about to be or are being compromised.
Service-display	$RXDP	This server receives status information about services from the RULES-ANALYSIS server and subsequently allows for status relating to these services to be displayed on the live service screen. This server plugs directly into the live Service Monitor display.
Service-setup	$RXS1	Server that sets up the various trees in Service Monitor as part of the dragging and dropping of Tandem object components from various Tandem nodes into drill down trees. It also handles requests for Service Monitor set-up warm-boot.
Dashboard:
Dash-master	$RXDB	A server that plugs directly into the Dashboard display of the GUI client for displaying system metric information at configured polling intervals. This metric information relates to disks, CPUs and processes. The server starts a baby process per CPU to pass back CPU information locally to the master process.
Dash-thresh	$RXTH	A process responsible for comparing retrieved system metric values against agreed threshold limits. If those thresholds have been exceeded then EMS events are generated which can then be configured to cause graphical alerting of processes, CPUs and disks in the live Status Monitor screen.
Dash-X25	$RXDX	This server is responsible for retrieving X25 metrics for use in the Dashboard screens. It also handles some of the threshold alerts based on the X25 metrics.
Discovery:
Reflex-stats	$RXAT	Server used for setting up EMS analysis requests over a period of time with specified filter and collector values. The server will initiate a distributor to peruse EMS log files and pass back EMS graphical bar-chart readouts of events generated over time, from most down to least reported.
Gateway:
Reflex-s-stats	$RXSS	This server handles requests for streamer statistics based on text event throughput through the configured streamer process.
Reflex-stream	$RXES	Handles the configuration of streamer records from streamer process through to the set-up of the translation rules for incoming text events.
Console:
Console	$RXCO	This is the event viewing console in Reflex 80:20 which extracts EMS events and the mandatory EMS tokens from an event for display. Up to 16 user views can be configured with various filters and collectors assigned. Searches and extended filters can be configured to allow for advanced analysis of the EMS event logs for problem events.
Event Database:
Reflex-ec-list	$RXLS	Server to pass back a list of reaction records with their corresponding reaction settings for display in the Reaction module.

 

SERVER NAME :	PROCESS :	DESCRIPTION:
Reflex-eventcx	$RXCX	This server allows for the customising of the CAUSE and RECOVERY texts seen in the detail function of the Console display. This text is substituted for the pre-delivered texts of any third-party software in the Console display only.
Reflex-eventdb	$RXEV	Individual EMS event records can be added to the Reflex event database with this server which hooks up to the Database module of the Reflex 80:20 GUI client.
Reflex-eventtd	$RXTD	This server passes back any pre-supplied CAUSE and RECOVERY Tandem event texts. It is not currently in use as at release 4.1 of Reflex 80:20.
Enterprise Management:
Cmnd-post-react	$RXCR	This server will build any event messages that require to be passed to the COMMAND/POST Enterprise Manager from tables ACTCMDPQ and CMDPCNFQ. This will be as a result of EMS events that have been nominated as requiring an Enterprise Manager reaction to be initiated.
Cmnd-post-setup	$RXPS	This server caters for the setting up of Enterprise Manager attribute (TIVOLI, COMMAND/POST, SENTRA or SMS) alerts to a remote NT platform.
Ent-mngr-feeder	$RXEM	This process is key to relaying any Enterprise Manager alerts (TIVOLI, COMMAND/POST, SENTRA and SMS) to a nominated NT platform. It uses Fastpipe TCP/IP socket protocol to achieve this. The Reflex NT server process will need to be installed on the NT box in order for this relay to work correctly.
Remote-delivery	$RXRD	This server will relay an API directly to a nominated platform. It is not currently in use as at release 4.1.
Tivoli-react	$RXTV	This server will build any event messages that require to be passed to the TIVOLI Enterprise Manager from tables ACTCMDPQ and CMDPCNFQ. This will be as a result of EMS events that have been nominated as requiring an Enterprise Manager reaction to be initiated.
Taskmaster:
Reflex-tasks	$RXTA	This server plugs directly into the GUI for setting up Reflex tasks and programs in the Taskmaster module.
Miscellaneous:
Availab-feeder	$RXAV	This process is responsible for piping time-stamped system metric data to a nominated NT workstation (NOTE: this nomination is carried out at the server level as a start-up parameter). The data consists of CPU, disk, file and status monitor object status data. It requires for the appropriate NT software to be installed to provide trending using graphing software and accompanying SQL queries.
Calendar-setup	$RXCS	This server plugs into the administration module of Reflex 80:20 for setting up both calendar time windows and year records for stating statutory and bank holidays.
Dash-datacol	$RXDA	This process plugs into DASH-MASTER server for collecting data for both the Service Monitor module and the AVAILAB-FEEDER module. It polls DASH-MASTER at the same rate as for the Dashboard GUI windows in the client to collect this data so the parameters for specifying polling intervals apply.
Insider-help	$RXHP	This is a legacy server for passing back help on the green screen Pathway version of Reflex 80:20. The green screen in Reflex is no longer supported.
Pagegen-taps	$RXTS	The modification of the TAP parameter details for BT text paging can be achieved with this server. It only allows amending of the configured TAP record.
Reflex-calmon	$RXCA	This server process is the Reflex calendar process for informing of started and elapsed calendar time periods. Any process can start up and register with this process for subsequently receiving calendar information for registered calendar periods. This includes third party software using ITL supplied APIs.
Reflex-egen	$RXEG	This server allows for reactions to be tested by writing an EMS event into the GUI dialog and raising it to the event log by clicking on the client toolbar. It is useful when severe events cannot be created for testing purposes, e.g. CPU down, X25 line down.
Reflex-ping	$RXPI	For more information on this server, see appendices in this quick-start manual. It acts to monitor for workstations that have been locked up due to spurious window problems. Locked out workstations can then be reported the graphical displays of working workstations.

 

SERVER NAME :	PROCESS :	DESCRIPTION:
Reflex-wildcard	$RXAL	This server enables the use of wildcards for searching on event reactions. It is a legacy server only invoked by the green-screen Pathway version of Reflex where scroll bars where not available. The green-screen version is no longer supported.
Heatbeat:
File-mets-monit	$RXF1-5	This server-class consists of 5 file monitoring server processes that monitor files at 4 different intervals (the fifth is for sub-volume monitoring). The intervals are critical (user configurable), hourly, half-daily and daily.
File-mon-set-up	$RXFS	This server enables the set-up of files to be monitored on the Tandem platform at 5 configurable intervals. It also allows the set-up of files to be monitored for arrival at the Tandem platform at configurable calendar time windows.
File-pres-monit	$RXFM	This process monitors files for their arrival at a given calendar period. In order to do this, it registers itself with the REFLEX-CALMON process to receive information about started calendar periods.
Reflex-procmon	$RXPR	This server allows for the set-up of process records in the heart beat module of Reflex 80:20. These processes will then be monitored for their existence by the process monitor process $PMON at the configured time window.
Reaction:
Reflex-c-action	$RXAE	This server allows for the setting up of action groups and cover periods for events that should be reacted to by the Reflex 80:20 product.
Reflex-c-cmnds	$RXCM	This server allows for the entering of commands under the reaction module of Reflex 80:20. Tasks are now the preferred approach to kicking off both commands and a sequence of programs.
Reflex-c-events	$RXMG	This server allows for the set-up of an EMS event to be generated to the log as a result of an incoming EMS event.
Reflex-c-ops	$RXOP	This server allows for the generation and compilation of an EMS Tandem filter. It allows for the servicing of the request to warm boot the reaction module.
Reflex-c-page	$RXPG	This server allows for the set-up of paging details under the reaction module by service number and a list of 10 contact pagers.
Reflex-c-wdog	$RXWD	This server is well used in Reflex as it allows for the passing of EMS events from the event monitor ($EMON) through to the Status Monitor module for graphical alerting of Tandem health of configured hardware and software components.
Reflex-p-cancel	$RXCP	This server actions requests to cancel currently active pager requests. NOTE: these are not SMS page requests that are handled by off-line NT server but Tandem port to modem page requests.
Snmp-details	$RXS2	This server allows for the set-up of SSID to OID number part number for SNMP traps in Reflex 80:20. These are for outgoing SNMP traps.
Snmp-out	$RXSN	This process handles SNMP trap messages which have been configured using a standard ITL message format for all Reflex SNMP traps.
Connectivity:
Fastpipe-backup	$RXFB	This server is used only if the GUI is using a Non-stop approach to TCP/IP connectivity to the Reflex 80:20 application. It acts to support connection if the primary TCP/IP stack fails. Up to 9 of these back-up servers can be configured to talk to 9 other TCP/IP stacks.
Fastpipe-server	$RXFP	This is the primary server to enable connectivity between the Reflex GUI client and the Tandem Pathway. It uses ITLs’ standard TCP/IP socket protocol which is proprietary within ITL products.
Spooler Monitoring:
Agent-spooler	$RXSG	This server allows for the monitoring of spooler entities, i.e. print processes, devices, collectors and supervisors. Events are generated to the EMS log which can be reported to the Status Monitor screen for graphical alerting.

 

13.7.         Reflex 80:20 Non PATHWAY processes

This section categorises the various processes that execute outside the Reflex 80:20 PATHWAY. The process names are given although the names may have been changed to avoid clashes with your own environment.

 

PROCESS :	OBJECT :	SQL :	EXTERNAL: PARAMS :	GUI ADMINISTRATION PARAMETERS (PARACONF) :
$EMON	EVNTMON	Yes	Server^queue, ent^mgr	Emoncol0 through emoncol9, pathmon-process
$PMON	PROCMON	No	Max-processes	Pmon-poll-interval, pmon-msg-frequency, heartbeat-ems-suppress
$CGEN	CEGEN	No
$RTSK	TASKMAST			Task-q-len (RUNTASK),
$PGEN	PAGEGEN	Yes	Call-retries, success-attempts

 

13.8.         Reflex 80:20 Facilities and their Abbreviations

This section describes the purpose of each 3-letter facility. Those that are greyed out are no longer used but are included for completeness. This section is useful when setting up security classes for Reflex 80:20 users. Using this table as a guide will enable the restriction of certain functional areas of Reflex while allowing access to others.

 

Abbrev.	Description of Use	Security Class Restriction	Checked By	Area of Reflex Product
ACI	Used to licence both the Base24 XPNET status agent and the auto detection utility, XPNETAGC and XPNETADC respectively.	No	Tandem	Base24 Monitoring
ALL	Audit screen	No	GUI	Administration
APL	The ability to cancel live page requests using GUI	Yes	GUI	Reaction – Paging
AVL	This function controls the successful start-up of the trending facility that sends CPU, DISK, SMON and File data to an NT box for graphing.	No	Tandem	ITL supply an offline process for the populating of a relational database for graphing and trending the aforementioned components
CEG	This function allows the command/ event generator process to start-up successfully	No	Tandem	This process will invoke a configured command or raise an EMS event
CHU	The ability to add Calendar time periods	Yes	GUI	Administration
CML	List CPU Records – no longer used - legacy	No	-	Overdrive
CMU	Update CPU records - no longer used - legacy	Yes	-	Overdrive Set-up
CNU	This facility allows for the update of Console views – not validated	Yes	-	Console
CON	This function is to allow for the use of the event viewing screen	Yes	Tandem & GUI	Console
CPT	Remote Alert set-up and alerting to NT, CP, SENTRA, Tivoli, SMS	Yes	Tandem & GUI	Reaction – Enterprise Management
CXL	Listing customised event detail information	No	-	Database
CXM	Menu for customised event detail information – Pathway menu no longer used	No	-	Database
CXU	Update customised event detail information	Yes	GUI	Database
CYU	Update calendar year records	Yes	GUI	Administration
DAU	Update service monitor data definition records	Yes	GUI	Service Monitor
DBA	List Aliases for EMS Events – Pathway screen no longer used	Yes	-	Database
DBL	List Event Database records	No	-	Database
DBM	A Pathway menu for the event database - Pathway screen no longer used	No	-	Database
DBU	Event Database function for event add, delete and amend	Yes	GUI	Database
DCM	A Pathway menu for the files/parameters screens - Pathway screen no longer used	No	-	Administration
DDC	The function controls the successful start-up of the dashboard data collector	No	Tandem	This process passes metric data to service monitor and optionally, NT ITL trending software
DEF	Pathway screen used to set event defaults - Pathway screen no longer used	Yes	-	Administration
DFL	List the file alias records in the administration module	No	GUI	Administration
Abbrev.	Description of Use	Security Class Restriction	Checked By	Area of Reflex Product
DFU	Update the file alias records in the administration module	Yes	GUI	Administration
DPL	List the parameter records in the administration module	No	GUI	Administration
DPU	Update the parameter records in the administration module	Yes	GUI	Administration
EEX	Allows the EMS Extraction utility to run	Yes	Tandem	EMS EXTRA
EMN	Allows the Event Monitor process to start-up successfully	No	Tandem	Tandem platform process which acts as a junction point to all configured event reactions
EVC	Display the customised event detail information for the EMS database	Yes	GUI	Database
EVD	Pathway menu screen for the database module - - Pathway screen no longer used	No	-	Database
EVM	Display the context of an EMS message in terms of explanatory (expanded) text	No	GUI	Discovery
EVT	Display the Tandem event details for a Tandem EMS event	No	GUI	Database
FMU	This allows for the File Monitoring module to be fully activated	Yes	Tandem & GUI	Heartbeat
LIC	Show the Reflex License details for a particular customer	No	GUI	Miscellaneous
HML	This is a Pathway screen to list hardware monitor records - Pathway screen no longer used	No	-	Overdrive Set-up
HMU	This is a Pathway screen to update hardware monitor records - Pathway screen no longer used	Yes	-	Overdrive Set-up
LOG	The main introduction screen in the Reflex Pathway - Pathway screen no longer used	No	-	Miscellaneous
MEN	Reflex 80:20 Pathway main menu screen - Pathway screen no longer used	No	-	Miscellaneous
MME	This function is for activating SMS alerting	Yes	Tandem	SMS Alerting
MON	Action View monitor function – not used	No	-	Miscellaneous
NAV	Pathway green screen which displays all 3 letter facilities and their descriptions - Pathway screen no longer used	No	-	Miscellaneous
NHL	List the network hierarchy records for the Tandem network	No	GUI	Overdrive & Service Monitor
NHU	This function allows for the update of the network hierarchy list	Yes	GUI	Overdrive & Service Monitor
PAD	This function controls the Pathway auto-detection facility	No	Tandem	This function builds Pathway object trees for the Status Monitor code
PAG	This function allows for the successful start-up of the Tandem port paging process	No	Tandem	This process allows for page requests to be raised via a configured Tandem port
PMO	This function code allows for the successful start-up of the process monitor function	No	Tandem	This process checks at a configurable rate for Tandem processes

 

Abbrev.	Description of Use	Security Class Restriction	Checked By	Area of Reflex Product
PSA	This function controls the successful use of the Pathway status agent	No	Tandem	This process passes back both status and metric information relating to servers and TDPs.
PSW	This is the security function that requires a user to logon with a Guardian ID.	No	GUI	Administration – LOGON
RAL	This function allows for the list of reactions to be returned in the reaction module	No	GUI	Reaction
RAM	This is a Pathway menu screen under the Reaction module - Pathway screen no longer used	No	-	Reaction
RAU	This function allows for the addition of Action Groups in the Reaction module	Yes	GUI	Reaction
RCM	This option allows for the generating and compiling of filters and subsequent warm-boot of Reflex 80:20	Yes	GUI	Reaction
RCU	This function allows for the entering of command details under Action Groups	Yes	GUI	Reaction – Command
RDE	This function allows for the entering of event details under Action Groups	Yes	GUI	Reaction – Event
RED	This function controls the successful start-up of the remote sending TCP/IP facility	No	Tandem	This process allows for the sending of a formatted message to a given remote platform
REM	This is a Pathway menu controlling access to the various reaction functions – Pathway screen no longer used	No	-	Reaction
RES	This allows Status Monitor objects to be reset back to the up state.	Yes	Tandem	Status Monitor
RFA	This function allows for the freezing of reactions at object level	Yes	GUI	Overdrive / Reaction
RPD	This is a program definition menu - Pathway screen no longer used	No	-	Tasks / Reaction
RPM	This function allows for the set-up of process monitor records	Yes	GUI	Heartbeat – process existence
RPL	This function allows for the listing of programs in the tasks function	No	GUI	Taskmaster
RPU	This function allows for the maintenance of programs in tasks	Yes	GUI	Taskmaster
RRP	This function allows for the entering of Tandem port paging details under Action Groups	Yes	GUI	Reaction – Paging
RSM	This function allows for the setting up of SSID to OID translation rules for SNMP traps	Yes	GUI	Administration – SNMP
RTA	This function allows for the configuration of tasks with program records. Optionally can be set to enforce the entering of passwords for alternative start-up user Ids.	Yes	GUI	Taskmaster
RTI	Function to allow the passing back of the task ownership list	No	GUI	Taskmaster
RTO	This function allows the adjoining of Guardian owners to tasks set up	Yes	GUI	Taskmaster
RTL	The function allows for the listing of Tasks	No	GUI	Taskmaster

 

Abbrev.	Description of Use	Security Class Restriction	Checked By	Area of Reflex Product
RTM	This is the Pathway menu screen for the taskmaster module - Pathway screen no longer used	No	-	Taskmaster
RTU	This function allows for the adjoining of tasks to action groups for automation purposes	Yes	GUI	Reaction / Tasks
RUB	This function allows for the building of rules under service trees on the parent node	Yes	GUI	Service Monitor
RWA	This function allows for the building of a Status Monitor reaction to an incoming event for graphical alerting	Yes	GUI	Reaction / Overdrive
SCL	This function allows the addition and modification of security classes	Yes	GUI	Administration
SEL	This function allows the listing of security classes for viewing	No	GUI	Administration
SEM	This function allows for the start-up of all Service Monitor processes on the parent node and some GUI control	No	GUI	Service Monitor
SMM	This is a Pathway Status Monitor menu - Pathway screen no longer used	No	-	Overdrive Set-up
SMO	This function is used for Overdrive operational control – Pathway screen no longer used	No	-	Live Overdrive
SPD	This function allows for the addition of Streamer process details	Yes	GUI	Gateway
SPI	This function caters for the displaying of streamer process details	Yes	GUI	Gateway
SPL	The function allows known streamer definitions to be displayed in a list	No	GUI	Gateway
SPR	This function allows for the adjoining of security classes to security profiles	Yes	GUI	Administration
SPS	This facility allows for the display of streamer threshold information	No	GUI	Gateway
STA	This function allows for the display of the Discovery event statistics	Yes	GUI	Discovery
STI	This function allows for the addition of streamer configuration rule records in the translation tab	Yes	GUI	Gateway
STL	This function allows for the listing of configuration rules in the GUI	No	GUI	Gateway
STM	This is a Pathway screen for the various streamer functions - Pathway screen no longer used	No	-	Gateway
STR	This function code allows for the successful start-up of any streamer processes	No	Tandem	This process allows for the conversion of basic text messages to unique tokenised EMS messages
STU	This function allows for the update of streamer configuration rules in the translation tab	Yes	GUI	Gateway
TAP	This function allows for the changing of BT TAP protocol settings	No	GUI	Tandem Port Paging
TAS	This function allows for the successful start-up of the task-master process	No	Tandem	This process can invoke tasks that have been set-up in Reflex

 

Abbrev.	Description of Use	Security Class Restriction	Checked By	Area of Reflex Product
TES	This function allows a user to raise a test event onto the EMS primary collector	Yes	GUI	Reaction – Test
TSL	This facility allows for the listing of both object types and subtypes	No	GUI	Overdrive / Service Monitor / Reaction
TSU	This facility allows for the modification of both object types and subtypes	Yes	GUI	Overdrive / Service Monitor / Reaction
TTL	This function allows the user to list tasks and their corresponding object types and subtypes	No	GUI	Overdrive / Reaction
TTU	This function allows the user to modify tasks and their corresponding object types and subtypes	Yes	GUI	Overdrive / Reaction
TXM	This is a Pathway menu function - Pathway screen no longer used	No	-	Event Database
WAR	This allows for a FULL warm-boot of the Status Monitor	Yes	Tandem	Status Monitor Set-up & RFLXCOM
WIF	This function represents the overdrive interface and is no longer used	No	-	Live Overdrive
XCS	This function allows for the display of CPU metric statistics in Dashboard	No	GUI	Dashboard
XDS	This function allows for the display of disk metric statistics in Dashboard	No	GUI	Dashboard
XPD	This function allows for the display of the top 5 busy process metric statistics per CPU in Dashboard	No	GUI	Dashboard

 

 

13.9.         Monitoring Reflex 80:20 GUI Client Connectivity with Reflex Ping

It is not unheard of in the PC world, for PC workstations (or GUIs) to become frozen or locked out in some manner. If more than one PC is being configured with the Reflex 80:20 GUI client, then it will be useful to implement some workstation monitoring. In this regime, one workstation looks out for the interests of another.

How it works:

To activate the ‘pulses’ from the workstation, the following parameter needs to be added to the ‘REFLEX.ini’ file under [APPLICATIONS].

     Workstation Ping = n

                 n = 1 – Ping Activated

                 n = 0 – Ping Deactivated

The PC workstation where the Reflex 80:20 GUI client is installed can be configured to send a pulse message to the Tandem at minutely intervals. To configure this to occur for your Reflex 80:20 client, edit the ‘REFLEX.ini’ file on your Reflex PC directory (as shown below) and change the flag ‘Workstation Ping’ to a value of ‘1’.

If this parameter is not present in the ‘REFLEX.ini’ file then Ping Deactivated is assumed.

    

 

If the ping server ‘REFLEX-PING’ does not receive a pulse message for more than a 2 minutes then it raises an EMS message. This is a parameter set-up in your own ‘REFLEX.ini’ file. The ping server takes the decision that the PC is no longer operational.

The EMS message produced has the following format ‘INSIDER.50.2650’. This message can then be seen on an operators EMS viewing console (or can be configured to alert to the Status Monitor graphical display – see later – for another Reflex GUI client to flash as critical).

The manager token of this EMS message is set to the ‘REFLEX-PING’ process and subject token set to the TERM name of your PC workstation stated in your ‘SERVER.ini’ file.