The ‘AGENTRDF’ macro is used to poll RDF (STATUS VOLUME) and check status of the UPDATER process, or processes. EMS alerts will be issued for the following scenarios :
• AGENTRDF started
• UPDATER processes falling behind
• UPDATER processes up to date
• UPDATER processes have stopped
• UPDATER processes have restarted
• RDF not responding
• Pathway Server AGENT-RDF stopped
• Pathway Server error
An UPDATER prefix needs to be specified in the AGENTRDF macro, to match your environment, e.g. $UP. This value will be used to check status of ALL RDF UPDATER processes beginning with $UP prefix.
The “AGENT-TMF” Pathway Server allows for monitoring of the TMF environment: transaction status (including monitoring of ‘long-running’ and ‘hung’ transactions); tape status; auditdump status; etc. See also Reflex Transaction Monitoring Facility health checking.
The following AGENTTMF parameters are supplied :
TMF-MAX-TX-TIME
Maximum transaction time in minutes. The default is 60 minutes. This parameter overrides the settings of the TMF AUTOABORT parameter.
TMF-AUDITTRAIL-THRESHOLD
Percentage that an audit trail is allowed to be full. The default is 50%.
TMF-TAPES-THRESHOLD
Minimum number for scratch tapes. The default is 10.
POLL-INTERVAL
Interval in minutes, to poll TMF. The default is 30 minutes.
AUTOABORT-PERCENT
The percentage of the TMF autoabort value to use. The default is 80%. This is only valid if the Autoabort value is non zero and there is no TMF-MAX-TX-TIME parameter.
TMF-WAITING-AUDITTRAILS
The number of outstanding audit trail dumps identified before an alert is generated. The default is 1.
TMF-AGENT-MODE
Can be set to PATHWAY or BATCH. Used only in the ‘RUNTMFA’ file.
TMF-SUPPRESS
A mask to suppress the checking of various TMF aspects :-
NNNNNN
| | | | |_ Audittrails waiting to be dumped
| | | | |_Tapemedia
| | | |_Datavols
| | |_Transactions
| |_Auditdump
|_Auditrails
Set any of these to “Y” to suppress the checking. The default is NNNNNN to check everything. Used only in the ‘TMFACONF’ Server config file.
This BATMACRO TACL macro can cater for several types of scenarios, whereby users can execute equivalent MultiBatch BCOM commands via Reflex 80:20 Status Monitor ‘STEP’ objects.
The following BCOM commands are catered for :
• START UNIT
• ABORT UNIT
• RESTART UNIT
• HOLD UNIT
• RELEASE UNIT
• ALTER STEP TO ‘COMPLETE’ STATUS (FLAGS %070101)
The TACL macro – ‘BATMACRO’ - is configured within different Reflex 80:20 TASKS and the TASKS then associated with the MultiBatch STEP (type/subtype) definitions. Users can then execute equivalent BCOM commands via Status Monitor ‘Autodiscovered’ MultiBatch STEP objects.
The ‘JOBSLOTS’ monitoring utility allows a user to monitor the actual “number of jobs” in the spooler, as opposed to the Collector threshold, which complements the Reflex 80:20 Spooler Collector threshold monitoring.
If the number of ‘physical’ jobs in the spooler exceeds a user-configured value in the Reflex 80:20 Admin (Parameters) facility, then an EMS alert is issued, stating that the ‘threshold is broken’.
If the number of jobs falls below this value, then an EMS alert is issued stating that threshold has ‘returned to normal’.
EMS alerts are also issued for when ‘JOBSLOTS’ monitoring is started or stopped and if certain files are missing, which would negate functionality.
Parameters :
SPOOLER-JOBS-CONF
This value needs to be that which is configured in your Tandem Spooler ‘coldload’ file - specified in the system SPOOL startup parameters, e.g. 4095.
SPOOLER-JOBS-THRESH
This value needs to be specified for when you want to be alerted if the number of jobs exceeds this value, e.g. if you specify 3000, then an EMS alert is issued when this value is exceeded. Additionally, a percentage value is included in the EMS event text.
SPOOLER-INTERVAL
+ Polling period to monitor spooler. Value is specified in minutes.
SPOOLER-FREQUENCY
+ Controls frequency that the same spooler state is reported. Used in conjunction with SPOOLER-INTERVAL to control how often EMS alerts are produced. If spooler-jobs-threshold has been exceeded, then an EMS event is issued. If the same state is still occurring N seconds later (SPOOLER-INTERVAL value), then it will not be re-issued until SPOOLER-FREQUENCY x SPOOLERINTERVAL has passed.
MOUNTMON is a TAL program for Reflex to provide alerts against any outstanding tape mounts. It is designed to run as a Pathway server (MOUNT-MONITOR).
MMON-POLL-TIME
The MMON-POLL-TIME parameter is used to determine how often MOUNTMON checks its record of outstanding mount requests. The parameter value should be specified in seconds. If the parameter is not configured in the Reflex GUI, then a default value of 120 seconds will be assumed.
The MMON-POLL-TIME parameter should be added to the ADMIN / PARAMETERS module via the Reflex GUI. MMON-VUL-POLL-COUNT This parameter is used to determine the amount of time a tape mount request may be outstanding before MOUNTMON starts to generate VULNERABLE EMS events. This value, is used in conjunction with MMON-POLL-TIME as follows:
MMON-POLL-TIME x MMON-VUL-POLL-COUNT
For example, if MMON-POLL-TIME is set to 120 seconds and MMON-VUL-POLL-COUNT is set to 5, then if after 10 minutes (120 x 5) a tape mount request is still outstanding a VULNERABLE EMS alert is issued.
MMON-CRIT-POLL-COUNT
This parameter is used to determine the amount of time a tape mount request may be outstanding before MOUNTMON starts to generate CRITICAL EMS events. This value is used in conjunction with MMON-POLL-TIME as follows :
MMON-POLL-TIME x MMON-CRIT-POLL-COUNT
For example, if MMON-POLL-TIME is set to 120 seconds and MMON-CRIT-POLL-COUNT is set to 10, then if after 20 minutes (120 x 10) a tape mount request is still outstanding a CRITICAL EMS alert is issued.
STATCOLL - HP NonStop EMS event message statistical analysis and reporting
The STATCOLL TACL utility allows you to discover what has been happening or has happened to your HP NonStop system(s). By collecting event statistics and displaying them in a management report broken down by subsystem and event, the utility increases your system efficiency by reducing the risk and consequences of missing events.
EMS event data collected can be analysed in order to set priorities for automation, identify trends, bottlenecks etc.
The Statistics Request feature allows you to submit a request to collect event statistics for a specific period. Event statistics can be collected for all events within a specified time period if you are interested in general trends - which EMS events occur most often and so on.
Event Statistics can also be collected for a subset of events if you are interested in specific problems or EMS events - for example, those relating to X25 lines or BASE24 XPNET components. Event filtration and submission in this way can remove irrelevant events and decrease the likelihood of critical events being overlooked.
The gathered event statistics can be viewed on screen or sent to a PC file which can then be ported to a PC for use with a spreadsheet package etc.
STATCOLL is also available as a GUI module within the Reflex product (called Discovery) for producing graphical reports in a bar-chart format and also sent out to SPOOLCOM.