halcyon software guide to Vision iTERA Availability templates Copyright
Copyright 2010 - 2014 Halcyon Software Limited. All rights reserved.
This document is intended as a guide to the reports generated by using Halcyon software.
This documentation contains Halcyon proprietary and confidential information and may not be
disclosed, used, or copied without the prior consent of Halcyon Software Limited, or as set forth
in the applicable license agreement. Users are solely responsible for the proper use of the
software and the application of the results obtained.
Although Halcyon Software Limited has tested the software and reviewed the documentation,
the sole warranty for the software may be found in the applicable license agreement between
Halcyon Software Limited and the user.
Publication Revision: January 2014
Overview
Halcyon Templates are designed to provide the same level of monitoring across a number of
similar devices by applying a set of user-defined filters with a single-click. This greatly reduces
set-up time and ensures all systems are covered by at least a basic level of monitoring.
Should you need to make a system-wide change at a later date, a single update covers all
systems using the template.
Halcyon IBM i Templates also are available for the following specialized environments:
• Lawson M3 (Movex)
• Misys
• Misys Midas Plus
• JD Edwards
• Maxava
• Quick/EDD
• SAP
• Infor XA
• Infor System21
• Vision Replication Monitoring
C
HAPTER
INSTALLATION
CHAPTER 1
If you already use any of Halcyon's Level 1 to 4 software suites then follow
these instructions to install templates to a customized environment on the IBM i.
If you do not currently use Halcyon's tools in your IBM environment but wish to
have more information, an on-line demonstration or a free trial then please see
the list of contacts on the back page of this guide.
Installation of Customized Environment
Follow these instructions to install templates to a customized environment.
1 Install the Halcyon solution, using the appropriate installation guide.
2 Once successfully installed, log into the environment to which you wish to
apply the customized template, for example, HALPROD/HALCYON.
Note:
3 From the command line run ENDMON and press F4. Follow the prompts to
complete the ending of the monitors.
The installation of the customized environment fails if the monitors are not
stopped.
4 From the command line type CSTENV and press F4.
5 Type the required authorization code for the template you wish to apply and
press Enter.
Installation
1-1
Figure 1.1
Note:
Entering the customization code
Each customized environment requires an authorization code.
Please contact [email protected] or your local
Halcyon office or reseller for details on how to obtain this code.
The Customized environment is now installed.
6 From the main menu of your Halcyon solution, select option 5=Work with
Rules. The template rules applicable to the customized environment that you
installed can be found in the listed queue and rule groups. Default action
schedules are installed and additionally, where appropriate, changes to
system defaults may also be made.
In most cases, the templates supplied can be used immediately upon
completion of installation, but there may be instances where you need to
change rule properties to match those of your own environment. This can be
done by taking option 2=Change against the rule and making the required
changes. Similarly, should you require multiple rules for different message
queues or devices and so on you can use option 3=Copy against the rule
and then make the required amendments.
1- 2
Halcyon Templates
Rule Actions
Unless otherwise specified, all template rules are implemented with a default
action schedule which sends an alert message to your local console (option
10=Message Console from the main menu). Should you wish to amend this
option, take option 2=Change against the action within the rule and make the
amendments as required.
Note:
Please refer to the user reference guide for your Halcyon solution for details
of actions that may be applied to rules.
Installation
1-3
C
HAPTER
VISION ITERA AVAILABILITY
CUSTOMIZATION TEMPLATES
CHAPTER2
Vision iTERA Availability Monitoring
Vision iTERA Availability for IBM i provides business continuity for small to
medium business enterprises, virtually eliminating planned and unplanned
downtime by maintaining a real-time backup system that can quickly take over
as the production system when required.
Halcyon iTERA templates have been created to monitor iTERA versions 6.0
and 6.1. Apply the rules relevant to the version of Vision iTERA that you are
using.
Template Assignment
In most cases, the templates supplied can be used immediately upon
completion of installation, but there may be instances where you need to
change rule properties to match those of your own environment. This can be
done by taking option 2=Change against the rule and making the required
changes. Similarly, should you require multiple rules for different message
queues or devices and so on you can use option 3=Copy against the rule and
then make the required amendments.
Actions
Unless otherwise specified, all template rules are implemented with a default
action schedule which sends an alert message to your local console (option
10=Message Console from the main menu). Should you wish to amend this
option, take option 2=Change against the action within the rule and make the
amendments as required.
Note:
2- 4
Please refer to the user reference guide for your Halcyon solution for details
of actions that may be applied to rules.
Halcyon Templates
Message Queue Rules
There are two specialist iTERA Message Queue Rule Groups, each containing
a selection of rules to monitor v6.0 and v6.1 iTERA message queues.
E2MSGQ HA61A1 v6.1 iTera Message Queue
Note:
The following 6 rules are deemed as being critical to monitor to ensure
stability and accuracy of the iTERA replication.
No Global Exclusions Defined
Sequence number 0 is a special sequence number which cannot be deleted,
even if you do not define any global exclusions for the named message queue.
If you have messages that are to be totally excluded from any type of action,
take option 2=Change against sequence 0 to define the exact criteria for the
exclusion. If a global exclusion exists for a message, then none of the other
sequence numbers for this message queue are searched for a match and no
action is taken.
v.6.1: Hard drives in system ASP are degraded
When hard drives in system ASP become degraded, performance issues can
arise with disk I/O while writing to disks, especially when journaling.
This message rule, which operates on a 24/7 basis, monitors for message
HAE0189 being received in Message File E2MSGF within library ITERA.
v6.1: Disk space exceeds error threshold RSR monitor
The RSR Monitor continuously shows you are ready to role swap.
This message rule, which operates on a 24/7 basis, monitors to see if the
available disk space exceeds the error threshold specified for the RSR Monitor.
If so, message HAE0190 is generated and this is received in Message File
E2MSGF within library ITERA.
v6.1: Disk space exceeds warning threshold RSR monitor
The RSR Monitor continuously shows you are ready to role swap.
This message rule, which operates on a 24/7 basis, monitors to see if the
available disk space exceeds the warning threshold specified for the RSR
Monitor. If so, message HAE0191 is generated and this is received in Message
File E2MSGF within library ITERA.
Vision iTERA Availability Customization Templates
2-5
v6.1: Disk space exceeds sysval threshold
When the disk space exceeds the System Value threshold, the system starts to
shut down services in order to conserve disk space.
This message rule, which operates on a 24/7 basis, monitors to see if the
available disk space exceeds the System Value threshold. If so, message
HAE0200 is generated and this is received in Message File E2MSGF within
library ITERA.
v6.1: RSR check object out of sync
This rule checks to see if RSR object is out of sync, object is not journaled, not
syncing or has been omitted from syncing.
This message rule, which operates on a 24/7 basis, monitors to see if the RSR
object is out of sync (or any of the other conditions listed above). If so, message
HAE0421 is generated and this is received in Message File E2MSGF within
library ITERA.
v6.1: RSR check for record count audit errors
This rule checks RSR record count audit errors which if present, could indicate
objects are out of sync.
This message rule, which operates on a 24/7 basis, monitors the RSR for
record count audit errors. If any exist, message HAE0432 is generated and this
is received in Message File E2MSGF within library ITERA.
Note:
The next 18 rules are deemed as recommended to monitor to ensure stability
and accuracy of the iTERA application.
v6.1: One of the systems could not ping the other
If one system is unable to ping the other, it may suggest that there is a
communication breakdown or that one of the systems is offline, both of which
will affect the ability to perform accurate replication.
This message rule, which operates on a 24/7 basis, monitors the ping
availability between systems. If any discrepancies exist, message HAE0101 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.1: One of the apply jobs is not running on tgt
The iTERA apply jobs apply any updates to the replication between systems. If
one of the apply jobs is not running on the target machine, replication may be
not be accurate.
This message rule, which operates on a 24/7 basis, monitors the results of RSR
apply job tests against the apply jobs on the target machine and if any are found
not to be running, message HAE0181 is generated and this is received in
Message File E2MSGF within library ITERA.
2- 6
Halcyon Templates
v6.1: Apply job in message wait
The iTERA apply jobs apply any updates to the replication between systems. If
one of the apply jobs is in message wait status, replication may be not be
accurate.
This message rule, which operates on a 24/7 basis, monitors the results of RSR
apply job tests against the apply jobs on the target machine and if any are found
to be in message wait status within the subsystem, message HAE0182 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.1: Apply job on hold on the target
The iTERA apply jobs apply any updates to the replication between systems. If
one of the apply jobs is not running on the target machine, replication may be
not be accurate.
This message rule, which operates on a 24/7 basis, monitors the results of RSR
apply job tests against the apply jobs on the target machine and if any are found
to be in hold status, message HAE0183 is generated and this is received in
Message File E2MSGF within library ITERA.
v6.1: Jrnrcv disk used > threshold set in MONTHR
This rule monitors to see when a system check of journal receiver disk space
used reveals a value over the threshold set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the journal
receiver disk space used against the threshold set in the MONTHR test in RSR.
If the value exceeds the threshold, message HAE0201 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.1: Rmt jrn not active from primary to target
This rule checks if a remote journal is not active from the primary system to the
target system.
This message rule, which operates on a 24/7 basis, monitors the remote
journals for activity between the primary and target system. If a receiver is found
to be inactive, message HAE0204 is generated and this is received in Message
File E2MSGF within library ITERA.
v6.1: 1+ apply jobs not active on target
This rule checks if one or more apply jobs are not active on the target system.
This message rule, which operates on a 24/7 basis, monitors the apply jobs on
the target system and if one or more are found to be inactive, message
HAE0205 is generated and this is received in Message File E2MSGF within
library ITERA.
v6.1: Apply pnd > threshold set in MONTHR
This rule checks if the apply pending entries value is over the threshold limit set
in the MONTHR test in RSR.
Vision iTERA Availability Customization Templates
2-7
This message rule, which operates on a 24/7 basis, monitors the apply pending
entries value against the threshold set in MONTHR test in RSR. If the value
exceeds the threshold, message HAE0208 is generated and this is received in
Message File E2MSGF within library ITERA.
v6.1: Apply pnd latency > nbr mins set in MONTHR
This rule checks if the apply pending latency is higher than the number of
minutes set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the apply pending
latency against the number of minutes set in MONTHR test in RSR. If the value
exceeds the set number of minutes, message HAE0209 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.1: Network latency > nbr mins set in MONTHR
This rule checks if the network latency is higher than the number of minutes set
in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the network
latency against the number of minutes set in MONTHR test in RSR. If the value
exceeds the set number of minutes, message HAE0210 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.1: Nbr objs req sync > threshold set in MONTHR
This rule checks if the number of objects requesting sync is over the threshold
limit set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the number of
objects requesting sync being greater than the threshold set in MONTHR test in
RSR. If the value exceeds the threshold, message HAE0211 is generated and
this is received in Message File E2MSGF within library ITERA.
v6.1: Objs req resync > threshold set in MONTHR
This rule checks if the number of objects requesting resync is greater than the
threshold limit set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the number of
objects requesting resync being greater than the threshold set in MONTHR test
in RSR. If the value exceeds the threshold, message HAE0212 is generated
and this is received in Message File E2MSGF within library ITERA.
v6.1: Obj in obj sync status test is out of sync
This rule checks if an object in the object sync status test is out of sync, not
journaled, not selected or omitted. If an object in the object sync status test is
out of sync (or in any of the other conditions listed above), message HAE0219
is generated and this is received in Message File E2MSGF within library ITERA.
2- 8
Halcyon Templates
v6.1: Mirrored object is not currently journaled
This rule checks if a mirrored object is not currently journaled. If this condition is
found, message HAE0272 is generated and this is received in Message File
E2MSGF within library ITERA.
v6.1: One apply job has had seq overridden
This rule checks if a one of the apply jobs has had the sequence number
overridden indicating a possible ‘out-of-sync condition. If this condition is found
in any of the apply jobs , message HAE0374 is generated and this is received in
Message File E2MSGF within library ITERA.
v6.1: One apply job has had seq overridden
Similar to the previous rule, this rule also checks if a one of the apply jobs has
had the sequence number overridden indicating a possible ‘out-of-sync
condition. If this condition is found in any of the apply jobs , message HAE0375
is generated and this is received in Message File E2MSGF within library ITERA.
v6.1: DTAARA E2CURINFO contains an invalid CRG
This rule checks if data area E2CURINFO contains an invalid CRG. If this
condition is found, message HAE0623 is generated and this is received in
Message File E2MSGF within library ITERA.
Note:
This indicates a configuration issue which should be resolved by Vision
Customer Care department.
v6.1: Error occurred while processing object
This rule, which operates on a 24/7 basis, monitors the processing of objects. If
an error occurs with the processing of any object, message HAE0987 is
generated and this is received in Message File E2MSGF within library ITERA.
Note:
The next 10 rules are deemed as optional to monitor to ensure stability and
accuracy of the iTERA application.
v6.1: Unable to change owner on target
This rule checks the ability to change the owner on the target system. If it is not
possible to change the owner it could lead to a potential application issue during
a role swap.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if unable to change owner on the target system, message HAE0157 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.1: Unable to change authority on target
This rule checks the ability to change the authority on the target system. If it is
not possible to change the authority it could lead to a potential application issue
during a role swap.
Vision iTERA Availability Customization Templates
2-9
This message rule, which operates on a 24/7 basis, monitors this functionality
and if unable to change authority on the target system, message HAE0158 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.1: Audits did not complete successfully
This rule monitors the system audits. If one of the audits did not complete
correctly it may cause an issue with replication.
Note:
This message rule, which operates on a 24/7 basis, monitors this functionality
and if one of the audits has not completed successfully, message HAE0242 is
generated and this is received in Message File E2MSGF within library ITERA.
If this message is received, it is recommended by VISION that you choose
option 6 from the iTERA main menu in order to investigate.
v6.1: Audit job in message wait
This rule monitors the audit jobs in the iTERA subsystem. If one of the audit jobs
is in a status of message wait this may cause an issue with replication.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if this condition is found in one of the audit jobs in the iTERA subsystem,
message HAE0243 is generated and this is received in Message File E2MSGF
within library ITERA.
v6.1: Audit has not run within warning interval
This rule monitors the system audits. If an audit has not run within the warning
interval specified in the Audit Command Console this may cause an issue with
replication.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if this condition is found in one of the system audits, message HAE0245 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.1: Audit has not run within severe interval
This rule monitors the system audits. If an audit has not run within the severe
interval specified in the Audit Command Console this may cause an issue with
replication.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if this condition is found in one of the system audits, message HAE0246 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.1: Some part of the Mirror down job not valid
This rule monitors the Mirror down job and is only required if you are using this
functionality. If the Mirror down job is not valid, possible due to the program not
being on the target system, this may cause an issue with replication.
This message rule, which operates on a 24/7 basis, monitors the Mirror down
job and if this condition is found, message HAE0507 is generated and this is
received in Message File E2MSGF within library ITERA.
2- 1 0
Halcyon Templates
v6.1: Mirror down job command in error
This rule monitors the Mirror down job and is only required if you are using this
functionality. If the Mirror down job command is in error status this may cause
an issue with replication.
This message rule, which operates on a 24/7 basis, monitors the Mirror down
job and if this condition is found, message HAE0509 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.1: Apply latency > RSR MONTHR warning
This rule, which operates on a 24/7 basis, monitors the apply latency and if the
current value is greater than the RSR MONTHR value, message HAE0611 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.1: Apply latency > RSR MONTHR error
This rule, which operates on a 24/7 basis, monitors the apply latency and if the
current value is greater than the RSR MONTHR error value, message HAE0612
is generated and this is received in Message File E2MSGF within library ITERA.
E2MSGQ ITHAA1 v6.0 iTera Message Queue
Note:
The following 6 rules are deemed as being critical to monitor to ensure
stability and accuracy of the iTERA replication.
No Global Exclusions Defined
Note:
See the “No Global Exclusions Defined” section for more information.
v.6.0: Hard drives in system ASP are degraded
When hard drives in system ASP become degraded, performance issues can
arise with disk I/O while writing to disks, especially when journaling.
This message rule, which operates on a 24/7 basis, monitors for message
HAE0189 being received in Message File E2MSGF within library ITERA.
v6.0: Disk space exceeds error threshold RSR monitor
The RSR Monitor continuously shows you are ready to role swap.
This message rule, which operates on a 24/7 basis, monitors to see if the
available disk space exceeds the error threshold specified for the RSR Monitor.
If so, message HAE0190 is generated and this is received in Message File
E2MSGF within library ITERA.
Vision iTERA Availability Customization Templates
2-11
v6.0: Disk space exceeds warning threshold RSR monitor
The RSR Monitor continuously shows you are ready to role swap.
This message rule, which operates on a 24/7 basis, monitors to see if the
available disk space exceeds the warning threshold specified for the RSR
Monitor. If so, message HAE0191 is generated and this is received in Message
File E2MSGF within library ITERA.
v6.0: Disk space exceeds sysval threshold
When the disk space exceeds the System Value threshold, the system starts to
shut down services in order to conserve disk space.
This message rule, which operates on a 24/7 basis, monitors to see if the
available disk space exceeds the System Value threshold. If so, message
HAE0200 is generated and this is received in Message File E2MSGF within
library ITERA.
v6.0: RSR check object out of sync
This rule checks to see if RSR object is out of sync, object is not journaled, not
syncing or has been omitted from syncing.
This message rule, which operates on a 24/7 basis, monitors to see if the RSR
object is out of sync (or any of the other conditions listed above). If so, message
HAE0421 is generated and this is received in Message File E2MSGF within
library ITERA.
v6.0: RSR check for record count audit errors
This rule checks RSR record count audit errors which if present, could indicate
objects are out of sync.
This message rule, which operates on a 24/7 basis, monitors the RSR for
record count audit errors. If any exist, message HAE0432 is generated and this
is received in Message File E2MSGF within library ITERA.
Note:
The next 18 rules are deemed as recommended to monitor to ensure stability
and accuracy of the iTERA application.
v6.0: One of the systems could not ping the other
If one system is unable to ping the other, it may suggest that there is a
communication breakdown or that one of the systems is offline, both of which
will affect the ability to perform accurate replication.
This message rule, which operates on a 24/7 basis, monitors the ping
availability between systems. If any discrepancies exist, message HAE0101 is
generated and this is received in Message File E2MSGF within library ITERA.
2- 1 2
Halcyon Templates
v6.0: One of the apply jobs is not running on tgt
The iTERA apply jobs apply any updates to the replication between systems. If
one of the apply jobs is not running on the target machine, replication may be
not be accurate.
This message rule, which operates on a 24/7 basis, monitors the results of RSR
apply job tests against the apply jobs on the target machine and if any are found
not to be running, message HAE0181 is generated and this is received in
Message File E2MSGF within library ITERA.
v6.0: Apply job in message wait
The iTERA apply jobs apply any updates to the replication between systems. If
one of the apply jobs is in message wait status, replication may be not be
accurate.
This message rule, which operates on a 24/7 basis, monitors the results of RSR
apply job tests against the apply jobs on the target machine and if any are found
to be in message wait status within the subsystem, message HAE0182 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.0: Apply job on hold on the target
The iTERA apply jobs apply any updates to the replication between systems. If
one of the apply jobs is not running on the target machine, replication may be
not be accurate.
This message rule, which operates on a 24/7 basis, monitors the results of RSR
apply job tests against the apply jobs on the target machine and if any are found
to be in hold status, message HAE0183 is generated and this is received in
Message File E2MSGF within library ITERA.
v6.0: Jrnrcv disk used > threshold set in MONTHR
This rule monitors to see when a system check of journal receiver disk space
used reveals a value over the threshold set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the journal
receiver disk space used against the threshold set in the MONTHR test in RSR.
If the value exceeds the threshold, message HAE0201 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.0: Rmt jrn not active from primary to target
This rule checks if a remote journal is not active from the primary system to the
target system.
This message rule, which operates on a 24/7 basis, monitors the remote
journals for activity between the primary and target system. If a receiver is found
to be inactive, message HAE0204 is generated and this is received in Message
File E2MSGF within library ITERA.
Vision iTERA Availability Customization Templates
2-13
v6.0: 1+ apply jobs not active on target
This rule checks if one or more apply jobs are not active on the target system.
This message rule, which operates on a 24/7 basis, monitors the apply jobs on
the target system and if one or more are found to be inactive, message
HAE0205 is generated and this is received in Message File E2MSGF within
library ITERA.
v6.0: Apply pnd > threshold set in MONTHR
This rule checks if the apply pending entries value is over the threshold limit set
in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the apply pending
entries value against the threshold set in MONTHR test in RSR. If the value
exceeds the threshold, message HAE0208 is generated and this is received in
Message File E2MSGF within library ITERA.
v6.0: Apply pnd latency > nbr mins set in MONTHR
This rule checks if the apply pending latency is higher than the number of
minutes set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the apply pending
latency against the number of minutes set in MONTHR test in RSR. If the value
exceeds the set number of minutes, message HAE0209 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.0: Network latency > nbr mins set in MONTHR
This rule checks if the network latency is higher than the number of minutes set
in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the network
latency against the number of minutes set in MONTHR test in RSR. If the value
exceeds the set number of minutes, message HAE0210 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.0: Nbr objs req sync > threshold set in MONTHR
This rule checks if the number of objects requesting sync is over the threshold
limit set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the number of
objects requesting sync being greater than the threshold set in MONTHR test in
RSR. If the value exceeds the threshold, message HAE0211 is generated and
this is received in Message File E2MSGF within library ITERA.
2- 1 4
Halcyon Templates
v6.0: Objs req resync > threshold set in MONTHR
This rule checks if the number of objects requesting resync is greater than the
threshold limit set in the MONTHR test in RSR.
This message rule, which operates on a 24/7 basis, monitors the number of
objects requesting resync being greater than the threshold set in MONTHR test
in RSR. If the value exceeds the threshold, message HAE0212 is generated
and this is received in Message File E2MSGF within library ITERA.
v6.0: Obj in obj sync status test is out of sync
This rule checks if an object in the object sync status test is out of sync, not
journaled, not selected or omitted. If an object in the object sync status test is
out of sync (or in any of the other conditions listed above), message HAE0219
is generated and this is received in Message File E2MSGF within library ITERA.
v6.0: Mirrored object is not currently journaled
This rule checks if a mirrored object is not currently journaled. If this condition is
found, message HAE0272 is generated and this is received in Message File
E2MSGF within library ITERA.
v6.0: One apply job has had seq overridden
This rule checks if a one of the apply jobs has had the sequence number
overridden indicating a possible ‘out-of-sync condition. If this condition is found
in any of the apply jobs , message HAE0374 is generated and this is received in
Message File E2MSGF within library ITERA.
v6.0: One apply job has had seq overridden
Similar to the previous rule, this rule also checks if a one of the apply jobs has
had the sequence number overridden indicating a possible ‘out-of-sync
condition. If this condition is found in any of the apply jobs , message HAE0375
is generated and this is received in Message File E2MSGF within library ITERA.
v6.0: DTAARA E2CURINFO contains an invalid CRG
This rule checks if data area E2CURINFO contains an invalid CRG. If this
condition is found, message HAE0623 is generated and this is received in
Message File E2MSGF within library ITERA.
Note:
This indicates a configuration issue which should be resolved by Vision
Customer Care department.
Vision iTERA Availability Customization Templates
2-15
Note:
The next 10 rules are deemed as optional to monitor to ensure stability and
accuracy of the iTERA application.
v6.0: Unable to change owner on target
This rule checks the ability to change the owner on the target system. If it is not
possible to change the owner it could lead to a potential application issue during
a role swap.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if unable to change owner on the target system, message HAE0157 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.0: Unable to change authority on target
This rule checks the ability to change the authority on the target system. If it is
not possible to change the authority it could lead to a potential application issue
during a role swap.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if unable to change authority on the target system, message HAE0158 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.0: Audits did not complete successfully
This rule monitors the system audits. If one of the audits did not complete
correctly it may cause an issue with replication.
Note:
This message rule, which operates on a 24/7 basis, monitors this functionality
and if one of the audits has not completed successfully, message HAE0242 is
generated and this is received in Message File E2MSGF within library ITERA.
If this message is received, it is recommended by VISION that you choose
option 6 from the iTERA main menu in order to investigate.
v6.0: Audit job in message wait
This rule monitors the audit jobs in the iTERA subsystem. If one of the audit jobs
is in a status of message wait this may cause an issue with replication.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if this condition is found in one of the audit jobs in the iTERA subsystem,
message HAE0243 is generated and this is received in Message File E2MSGF
within library ITERA.
v6.0: Audit has not run within warning interval
This rule monitors the system audits. If an audit has not run within the warning
interval specified in the Audit Command Console this may cause an issue with
replication.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if this condition is found in one of the system audits, message HAE0245 is
generated and this is received in Message File E2MSGF within library ITERA.
2- 1 6
Halcyon Templates
v6.0: Audit has not run within severe interval
This rule monitors the system audits. If an audit has not run within the severe
interval specified in the Audit Command Console this may cause an issue with
replication.
This message rule, which operates on a 24/7 basis, monitors this functionality
and if this condition is found in one of the system audits, message HAE0246 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.0: Some part of the Mirror down job not valid
This rule monitors the Mirror down job and is only required if you are using this
functionality. If the Mirror down job is not valid, possible due to the program not
being on the target system, this may cause an issue with replication.
This message rule, which operates on a 24/7 basis, monitors the Mirror down
job and if this condition is found, message HAE0507 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.0: Mirror down job command in error
This rule monitors the Mirror down job and is only required if you are using this
functionality. If the Mirror down job command is in error status this may cause
an issue with replication.
This message rule, which operates on a 24/7 basis, monitors the Mirror down
job and if this condition is found, message HAE0509 is generated and this is
received in Message File E2MSGF within library ITERA.
v6.0: Apply latency > RSR MONTHR warning
This rule, which operates on a 24/7 basis, monitors the apply latency and if the
current value is greater than the RSR MONTHR value, message HAE0611 is
generated and this is received in Message File E2MSGF within library ITERA.
v6.0: Apply latency > RSR MONTHR error
This rule, which operates on a 24/7 basis, monitors the apply latency and if the
current value is greater than the RSR MONTHR error value, message HAE0612
is generated and this is received in Message File E2MSGF within library ITERA.
Vision iTERA Availability Customization Templates
2-17
TCP/IP Rules
There is one set of iTERA TCP/IP rules regardless of whether you are using
v6.0 or v6.1
ITERA TCP/IP check
There are two rules in the ITERA TCP/IP rule group.
Note:
These two rules use system variables, (such as the IP addresses of the
relevant systems) that will need amending to your localized settings prior to
the rule being activated.
Check status of source system
This rule, that runs every 5 minutes on a 24/7 basis, checks if there has been a
change in the status (from available to not available or vice versa) of the source
system since the last check was made.
If the status has changed, an alert is raised and sent to the system console
specified within the action schedule.
Check status of target system
This rule, that runs every 5 minutes on a 24/7 basis, checks if there has been a
change in the status (from available to not available or vice versa) of the target
system since the last check was made.
If the status has changed, an alert is raised and sent to the system console
specified within the action schedule.
Job Queue Rules
There are two sets of iTERA Job Queue rules depending on whether you are
using v6.0 or v6.1. Select the version appropriate to your current iTERA
installation.
E2JOBQ ITHAA1 iTera Job Queue v6.0
The rule in this group runs constantly and makes a check every 60 seconds.
v6.0: Check job queue E2JOBQ is not held
This rule checks that the E2JOBQ is not in a status of held. If the status of the
E2JOBQ is held, an alert is raised and sent to the system console specified
within the action schedule. The rule is also suspended for 15 minutes to allow
you time to investigate and resolve the issue.
E2SYSJOBQ HA61A1 iTera Job Queue v6.1
The rule in this group runs constantly and makes a check every 60 seconds.
2- 1 8
Halcyon Templates
v6.1: Check job queue E2SYSJOBQ is not held
This rule checks that the E2YSYSJOBQ is not in a status of held. If the status of
the E2SYSJOBQ is held, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
Performance Rules
There are two sets of iTERA Performance rules depending on whether you are
using v6.0 or v6.1. Select the version appropriate to your current iTERA
installation.
ITERAV60 iTera v6.0 Performance Checks
Note:
In the ITHAxx library (for default installations this will be ITHAA1) on both
nodes is a file called E2PJOBS. This file holds a list of jobs that should be
running in your subsystems based on the role that machine is performing.
When the subsystems start up, it will automatically start those jobs.
Check E2A1SBS subsystem is active
It is most likely that you will have one subsystem per Cluster Resource Group
(CRG) on both the primary machine and the target machine. If you have
multiple CRGs defined, then you will have more than one subsystem. The
subsystem names are based on the two-character CRG code designated during
installation (for example E2A1SBS). All iTERA HA jobs run in the subsystem.
Note:
This rule checks that the E2A1SBS subsystem is always active. If the
subsystem becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
If you have not used E2A1SBS as the default subsystem, change the name
of the subsystem in this rule to the one used by your organization.
Check no jobs on hold in subsystem E2A1SBS
This rule checks that there are no jobs in a status of HELD within the E2A1SBS
subsystem. If any jobs are found in this status, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
Note:
If you have not used E2A1SBS as the default subsystem, change the name
of the subsystem in this rule to the one used by your organization.
Check no jobs in MSGW in subsystem E2A1SBS
This rule checks that there are no jobs in a status of MSGW within the
E2A1SBS subsystem. If any jobs are found in this status, an alert is raised and
sent to the system console specified within the action schedule. The rule is also
suspended for 15 minutes to allow you time to investigate and resolve the issue.
Vision iTERA Availability Customization Templates
2-19
Note:
If you have not used E2A1SBS as the default subsystem, change the name
of the subsystem in this rule to the one used by your organization.
PRIMARY: A1_HEALNnn job must be active
This is the job for the Autonomic Heal technology. The job processes the Heal
requests. The alphanumeric prefix and numerical suffix are system dependent.
Check with your system administrator for the actual naming convention of the
heal job used in your iTERA replication process.
This rule checks that the A1_HEALNnn job is always active on the primary
system. If the heal job becomes inactive, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_JSNDRC must be active
This is the Java Send Remote Command which runs a multi-threaded Java
application that sends, receives, and executes remote commands. The
alphanumeric prefix is system dependent. Check with your system administrator
for the actual naming convention of the Java Send Remote Command used in
your iTERA replication process.
This rule checks that the A1_JSNDRC job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_OBJMON1 must be active
This is the Object Monitor Job. This job uses the QAUDJRN system journal to
identify object-level changes in mirrored libraries. These changes include
creates, deletes, changes, renames, moves from one library to another and so
on. The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of the Object Monitor job used in
your iTERA replication process.
This rule checks that the A1_OBJMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_OBJMON2 must be active
This job processes ZC entries, audit level changes, authority audits, object
authority changes, alternate name audit, user profile changes, system value
audit and changes, save files. it also processes audits that go through the
transport journal, such as source member, library, logical file attributes and also
submits a purge job that removes old records from several files.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
2- 2 0
Halcyon Templates
This rule checks that the A1_OBJMON2 job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_OBJMON3 must be active
This job processes the same jobs as A1_OBJMON2.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_OBJMON3 job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_RSRMON must be active
This job initiates the individual tests contained in the Role Swap Readiness
Monitor.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_RSRMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_RJTSAA must be active
The remote journal transport syncing sending job(s) are used to replicate both
mirrored and non-mirrored objects to the target using remote journaling.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_RJTSAA job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_RMTCMD must be active
The Remote Command Monitor job monitors for any remote commands coming
from the target system that are to be run on the primary.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
Vision iTERA Availability Customization Templates
2-21
This rule checks that the A1_RMTCMD job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_SYNC_Nnn must be active
This job uses DDM to processes sync requests from the E2POSR file which
resides on the target machine (nn is the two digit number of the target node
machine).
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_SYNC_Nnn job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: A1_SYSMON must be active
This job submits the MONSTS job, which updates the information displayed in
the System Monitor screen, such as local journal status, remote journaling
status, apply job status, and unapplied journal entries. It is initiated every fifteen
minutes but can be adjusted, if needed.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_SYSMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: JSNDRCJAVA must be active
JSNDRCJAVA is the Java application started by the xx_JSNDRC job.
This rule checks that the JSNDRCJAVA is always active on the primary system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
TARGET: A1_OBJMON1 must be active
This is the Object Monitor Job on the target device. This job uses the
QAUDJRN system journal to keep track of restoration of libraries, objects, and
so on, in order for the system to know when to carry on and perform other
functions.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
2- 2 2
Halcyon Templates
This rule checks that the A1_OBJMON job is always active on the target
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
TARGET: A1_RSRMON must be active
This is the Role Swap Readiness Monitor job that initiates the individual tests
contained in the monitor on the target system.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_RSRMON job is always active on the target
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
TARGET: A1_RMTCMD must be active
This is the Remote Command Monitor job which monitors for any remote
commands coming from the primary system that are to run on the target
system.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_RMTCMD job is always active on the target
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
TARGET: A1_JSNDRC must be active
This is the Java Send Remote Command which runs a multi-threaded Java
application that sends, receives, and executes remote commands.
The alphanumeric prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the A1_JSNDRC job is always active on the target system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
TARGET: JSNDRCJAVA must be active
This is the Java application started by xx_JSNDRC.
This rule checks that the JSNDRCJAVA job is always active on the target
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
Vision iTERA Availability Customization Templates
2-23
TARGET: ZMA1JRNA must be active
This is the apply job(s) for mirrored journals. Mirrored journals are journals that
were created for the iTERA HA product. There is an apply job for each mirrored
journal.
This rule checks that the ZMA1JRNA job is always active on the target system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
TARGET: ZMA1RJRA must be active
This is the apply job for transport journals. There is one transport journal apply
job per transport journal. There is one transport journal apply job per transport
journal.
This rule checks that the ZMA1TRJRA job is always active on the target system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
TARGET: ZRA1SJNA must be active
These are the apply jobs for RJT syncing journals process the journal entries
from the xx_RJTSAA job on the primary system. There is one ZR job for each
RJT Sync journal.
This rule checks that the ZMA1SJNA jobs are always active on the target
system. If any of these jobs becomes inactive, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
TARGET: ZU_xxxx must be active
These are the apply jobs for user journals. This job only runs if user journals
(journals that have been set up by third-party software vendors or created
outside of iTERA HA) have been incorporated into iTERA HA.
The alphanumeric suffix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the ZU_xxxx jobs are always active on the target system.
If any of these jobs becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
TARGET: ZZA1JRNA must be active
The ZZxxAudit jobs audit the local journal receiver for any changes that occur
on the target that did not originate from the primary. The ZZxxAudits are a major
component of the Virtual Role Swap, which allows you to perform a complete
test of the target environment’s processes that are redundant (for example:
applications that are being replicated).
2- 2 4
Halcyon Templates
The alphanumeric (A1) is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the ZZA1JRNA jobs are always active on the target
system. If any of these jobs becomes inactive, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
TARGET: XPJRNMGT must be active
This is the Journal Manager Job. This job manages and cleans up journal
receivers.
This rule checks that the XPJRNMGT job is always active on the target system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
ITERAV61 iTera v6.1 Performance Checks
Check HA61A1 subsystem is active
This rule checks that the HA61A1 subsystem, the default installation subsystem
for the iTERA Availability v6.1 product, is always active.
If the subsystem becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
Check MIMIXSBS subsystem is active
The MIMIXSBS is used by iTERA to run the jobs necessary for auditing.
If the subsystem becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
Check no jobs on hold in subsystem HA61A1
This rule checks that there are no jobs in a status of HELD within the HA61A1
subsystem.
Note:
If any jobs are found in this status, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
If you have not used HA61A1 as the default subsystem, change the name of
the subsystem in this rule to the one used by your organization.
Check no jobs in MSGW in subsystem HA61A1
This rule checks that there are no jobs in a status of MSGW within the HA61A1
subsystem. If any jobs are found in this status, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
Vision iTERA Availability Customization Templates
2-25
Note:
If you have not used HA61A1 as the default subsystem, change the name of
the subsystem in this rule to the one used by your organization.
PRIMARY: HA_ALERT job must be active
This starts iTERA Alert processing. This job is displayed and enabled only when
iTERA Alert is enabled.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_ALERT job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_APRBMON job must be active
This job monitors the operating system for completion of unique key access
path rebuild, then notifies the apply job that it can process the journal entries for
files.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_APRBMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_AUDMON job must be active
This job processes audits in the Audit Command Console.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_AUDMON job is always active on the primary
system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
PRIMARY: HA_CHK_E2A job must be active
This job checks whether Alert is running.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
2- 2 6
Halcyon Templates
This rule checks that the HA_AUDMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_CHK_Z_ job must be active
This job checks whether the ZZ Audit jobs are running.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_CHK_Z_ job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_CHKOBJM job must be active
This job performs an obsolete object check. If data area ALWDLT is set to Y
(the default), then any objects that exist on the target that do not exist on the
primary will be deleted.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_CHKOBJM job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_CLRSNCO job must be active
This job performs a daily clean up of data queues, save files, and purge of heal
records.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_CLRSNCO job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_CSTANZ job must be active
This job analyzes the system for constraints and loads the 4.24 screen with the
ones that iTERA can manage.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
Vision iTERA Availability Customization Templates
2-27
This rule checks that the HA_CSTANZ job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_DEVREP job must be active
This job ensures that Device Replication is running and assists in the efficiency
and speed of the replication process for configuration devices.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_DEVREP job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_DIRREP job must be active
This job ensures that Directory Entry Replication is running. This job is
displayed and enabled only when Directory Entry Replication is enabled.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_DIRREP job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_HEAL+++ job must be active
This job processes the Heal requests.
The alphanumeric (HA) prefix and +++ suffix are system dependent. Check with
your system administrator for the actual naming convention of this job as used
in your iTERA replication process.
This rule checks that the HA_HEAL+++ job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_IFSCMD job must be active
This is a supporting job for the IFS apply jobs. Executes the instructions for
changes to authority and owner attributes for a directory being synced.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
2- 2 8
Halcyon Templates
This rule checks that the HA_IFSCMD job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_IFSMON job must be active
This job handles object syncing during the initial sync, object level replication,
and audit resyncs.This job is displayed and enabled only when IFS Replication
is enabled.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
PRIMARY: HA_IFSPRG job must be active
This job purges IFS audit history. This job is displayed and enabled only when
IFS Replication is enabled.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_IFSPRG job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_JBSREP job must be active
This job ensures that Job Scheduler Replication is running. This job is displayed
and enabled only when Job Scheduler Replication is enabled.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_JBSREP job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_JOBMON job must be active
This job periodically checks the subsystem and restarts any jobs that should be
running.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_JOBMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
Vision iTERA Availability Customization Templates
2-29
PRIMARY: HA_JRNMGT job must be active
This job ensures that the Journal Manager is running and manages and cleans
up receivers.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_JRNMGT job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_OBJMON1 job must be active
This job uses the QAUDJRN system journal to identify object-level changes in
mirrored libraries. These changes include creates, deletes, changes, renames,
moves from one library to another, and so on.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_OBJMON1 job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_OBJMON2 job must be active
This job processes ZC entries, audit level changes, authority audits, object
authority changes, alternate name audit, user profile changes, system value
audit and changes, and save files. Also processes audits that go through the
transport journal, such as source member, library, and logical file attributes.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_OBJMON2 job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_OBJMON3 job must be active
This job processes longer running jobs, including some Audit Command
Console audits, such as DIRE, JOBSCDE, DEV, and SPLF audits.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
2- 3 0
Halcyon Templates
This rule checks that the HA_OBJMON3 job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_OBJMON4 job must be active
This job processes IFS entries retrieved from QAUDJRN.This job is displayed
and enabled only when IFS Replication is enabled.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_OBJMON4 job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_PRGLOG job must be active
This job deletes any records found in history and log files older that the retention
period.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_PRGLOG job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_RJTSAA job must be active
The remote journal transport syncing sending job(s) are used to replicate both
mirrored and non-mirrored objects to the target using remote journaling.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_RJTSAA job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_RMTCMD job must be active
This job monitors for any remote commands coming from the target system that
are to be run on the primary system.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
Vision iTERA Availability Customization Templates
2-31
This rule checks that the HA_RMTCMD job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_RPTREP job must be active
This job is displayed and enabled only when Spool File Replication is enabled
and ensures that Spool File Replication is running in order to monitor for copied
spool files.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_RPTREP job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_RSRMON job must be active
This job initiates the individual tests contained in the Role Swap Readiness
Monitor.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_RSRMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_SNC_+++ job must be active
This job monitors and processes resync requests for objects on the target node
requesting resync.
The alphanumeric (HA) prefix and +++ suffix are system dependent. Check with
your system administrator for the actual naming convention of this job as used
in your iTERA replication process.
This rule checks that the HA_SNC_+++ job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_SYNCNML job must be active
This job controls the synchronization flow.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
2- 3 2
Halcyon Templates
This rule checks that the HA_SYNCNML job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_SYSINFO job must be active
This job is used to monitor the system and track potential issues.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_SYSINFO job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_SYSMON job must be active
This job submits the MONSTS job, which updates the information displayed in
the System Monitor screen, such as local journal status, remote journaling
status, apply job status, and unapplied journal entries.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_SYSMON job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_TRGANZ job must be active
This job analyzes the system for triggers and loads them in the 4.23 screen.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_TRGANZ job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_TRNEXT job must be active
This job controls pass-through processing to off load long running jobs.
Eliminates special setup for multiple nodes.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
Vision iTERA Availability Customization Templates
2-33
This rule checks that the HA_TRNEXT job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_USRANZ job must be active
This job collects user profile information.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_USRANZ job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
PRIMARY: HA_VLDIFS job must be active
This validates the IFS configuration by verifying the following are valid: node
code, CRG, object’s FID, parent’s FID, and journal assignments. Obsolete
records are deleted. This job is displayed and enabled only when IFS
Replication is enabled.
The alphanumeric (HA) prefix is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the HA_VLDIFS job is always active on the primary
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
TARGET: ZMHAC01A & ZMHAC02A jobs must be active
These are communications journal apply jobs. Communications journals are
support journals used to report status and other information between nodes,
including Heal requests, parameter updates, database updates, status
changes, IFS replication status, etc. The originating node sends entries to all
other nodes via the communications remote journal. The entries are then read
and applied by the communications apply job.
This rule checks that the ZMHAC01A & ZMHAC02A jobs are always active on
the target system. If this job becomes inactive, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
TARGET: ZMHAJRNA job must be active
This is the apply job for a mirror journal. A mirror journal is a journal that is
usually created in the iTERA product for purposes of mirroring objects. There is
one apply job for each mirrored journal.
2- 3 4
Halcyon Templates
This rule checks that the ZMHAJRNA job is always active on the target system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
TARGET: ZMHATJRA job must be active
This is the apply job for a transport journal. There is one apply job per transport
journal.
This rule checks that the ZMHATJRA job is always active on the target system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
TARGET: ZRHASJNA job must be active
This is the apply job for an RJT sync journal. Processes the journal entries from
the xx_RJTSAA job on the primary. There is one ZR job for each RJT Sync
journal.
This rule checks that the ZMHATJRA job is always active on the target system.
If this job becomes inactive, an alert is raised and sent to the system console
specified within the action schedule. The rule is also suspended for 15 minutes
to allow you time to investigate and resolve the issue.
TARGET: ZU_JOURNALNAME job must be active
This is the apply job for user journal. User journal apply jobs only exist if a user
journal (a journal that has been set up by a third-party software vendor or
created outside of iTERA) has been incorporated into iTERA. There is one ZU
job per user journal.
This rule checks that the ZU_JOURNALNAME job is always active on the target
system. If this job becomes inactive, an alert is raised and sent to the system
console specified within the action schedule. The rule is also suspended for 15
minutes to allow you time to investigate and resolve the issue.
TARGET: ZZHAJRNA job must be active
The ZZxxAudit jobs audit the local journal receiver for any changes that occur
on the target that did not originate from the primary. The ZZxxAudit functions
like a safety net. There have been a significant number of instances where
these jobs have identified data on the target machine that had been modified by
some unauthorized process.
The alphanumeric (HA) is system dependent. Check with your system
administrator for the actual naming convention of this job as used in your iTERA
replication process.
This rule checks that the ZZA1JRNA jobs are always active on the target
system. If any of these jobs becomes inactive, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
Vision iTERA Availability Customization Templates
2-35
Audit Journal Rules
There are two sets of iTERA Performance rules depending on whether you are
using v6.0 or v6.1. Select the version appropriate to your current iTERA
installation.
ITERAV60 iTera v6.0 Audit Journal
This performance rule group contains 4 rules to monitor the audit journal
settings of the iTERA v6.0 replication product.
E2CSTMGR must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the E2CSTMGR user profile since the
last check was made.
If any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
ITERAOWNER must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the ITERAOWNER user profile since
the last check was made.
If any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
HAA1SUP must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the HAA1SUP user profile since the last
check was made.
If any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
HAA1ADMIN must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the HAA1ADMIN user profile since the
last check was made.
If any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
2- 3 6
Halcyon Templates
ITERAV61 iTera v6.1 Audit Journal
This performance rule group contains 4 rules to monitor the audit journal
settings of the iTERA v6.1 replication product.
MIMIXOWN must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the MIMIXOWN user profile since the
last check was made.
If any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
ITERAOWNER must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the ITERAOWNER user profile since
the last check was made.
If any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
LAKEVIEW must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the LAKEVIEW user profile since the
last check was made.
If any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
ADMIN must not change
This rule, that runs on a 24/7 basis, checks for any change in the Special
Authority, Limit Capabilities or Status of the ADMIN user profile since the last
check was made.
f any of the above conditions have changed, an alert is raised and sent to the
system console specified within the action schedule. The rule is also suspended
for 15 minutes to allow you time to investigate and resolve the issue.
Vision iTERA Availability Customization Templates
2-37
APPENDIX: TEMPLATE ASSIGNMENTS
Sample forms for customizing your own environment. Print and complete as required.
Halcyon Templates
-39
Template Assignment
C
HAPTER
TEMPLATE ASSIGNMENT
CHAPTER1
Overview
The following forms are provided for your use to assist you in your application and configuration of the Halcyon IBM Service Monitoring
Templates within your organization. You can print these forms for manual completion which you can then use when applying the
template rules within your own organization.
Each example Rule Group is listed, together with the individual rules contained within. You can determine whether or not you wish to
activate the rule, which values you wish to apply and any comments that you wish to make (such as specific inclusions or omissions for
example).
A sample form is shown overleaf.
Halcyon Templates
1-40
Template Assignment
Sample Form
Rule Type: MESSAGE QUEUE
Rule Group: QHST System History Log
Rule #
Description
Activate?
Values
900
Backup Objects NOT saved
Yes
Omit job BKUP999
910
Password invalid for
QSECOFR
Yes
Omit for workstation ITDEPT*
920
Job Ended Abnormally
No
980
Check Run job completed
Yes
CHECKRUN
Comments
Action: Run HJS job CHECKPRT
*Text in blue indicates where the user has completed the form ready for input.
Halcyon Templates
1-41
Message Queue Example Rules
C
HAPTER
MESSAGE QUEUE EXAMPLE RULES
CHAPTER2
Overview
The following chapter covers example Message Queue template rules supplied with the Vision iTERA Availability Monitoring Template.
The following example templates are available:
• E2MSGQ HA61A1 v6.1 iTera Message Queue
• E2MSGQ ITHAA1 v6.0 iTera Message Queue
Halcyon Templates
2-42
Message Queue Example Rules
E2MSGQ HA61A1 V6.1 iTera Message Queue
Rule #
Description
0
No Global Exclusions Defined
10
v6.1: Hard drives in system
ASP are degraded
20
v6.1: Disk space exceeds
error threshold RSR monitor
30
v6.1: Disk space exceeds
warning threshold RSR
monitor
40
v6.1: Disk space exceeds
sysval threshold
50
v6.1: RSR check object out of
sync
Halcyon Templates
Activate?
Values
Comments
2-43
Message Queue Example Rules
Rule #
Description
60
v6.1: RSR check for record
count errors
70
v6.1: One of the systems
could not ping the other
80
v6.1: One of the apply jobs is
not running on tgt
90
v6.1: Apply job in message
wait
100
v6.1: Apply job on hold on the
target
110
v6.1: Jrnrcv disk used >
threshold set in MONTHR
Halcyon Templates
Activate?
Values
Comments
2-44
Message Queue Example Rules
Rule #
Description
120
v6.1: Rmt jrn not active from
primary to target
130
v6.1: 1+ apply jobs not active
on target
140
v6.1: Apply pnd > threshold
set in MONTHR
150
v6.1: Apply pnd latency > nbr
mins set in MONTHR
160
v6.1: Network latency > nbr
mins set in MONTHR
170
v6.1: Nbr objs req sync >
threshold set in MONTHR
Halcyon Templates
Activate?
Values
Comments
2-45
Message Queue Example Rules
Rule #
Description
Activate?
180
v6.1: Objs req resync >
threshold set in MONTHR
N/A
190
v6.1: Obj in obj sync status
test is out of sync
200
v6.1: Mirrored object is not
currently journaled
210
v6.1: One apply job has had
seq overridden
220
v6.1: One apply job has had
seq overridden
230
v6.1: DTAARA E2CURINFO
contains an invalid CRG
Halcyon Templates
Values
Comments
2-46
Message Queue Example Rules
Rule #
Description
240
v6.1: Unable to change owner
on target
250
v6.1: Unable to change
authority on target
260
v6.1: Audits dis not complete
successfully
270
v6.1: Audit job in message
wait
280
v6.1: Audit has not run within
warning interval
290
v6.1: Audit has not run within
severe interval
Halcyon Templates
Activate?
Values
Comments
2-47
Message Queue Example Rules
Rule #
Description
300
v6.1: Some part of the MIrror
down job not valid
310
v6.1: Mirror down job
command in error
320
v6.1: Apply latency > RSR
MONTHR warning
330
v6.1: Apply latency >RSR
MONTHR
340
v6.1: Error occurred while
processing object
Halcyon Templates
Activate?
Values
Comments
2-48
Message Queue Example Rules
E2MSGQ ITHAA1 v6.0 iTera Message Queue
Rule #
Description
0
No Global Exclusions Defined
10
v6.0: Hard drives in system
ASP are degraded
20
v6.0: Disk space exceeds
error threshold RSR monitor
30
v6.0: Disk space exceeds
warning threshold RSR
monitor
40
v6.0: Disk space exceeds
sysval threshold
50
v6.0: RSR check object out of
sync
Halcyon Templates
Activate?
Values
Comments
2-49
Message Queue Example Rules
Rule #
Description
60
v6.0: RSR check for record
count errors
70
v6.0: One of the systems
could not ping the other
80
v6.0: One of the apply jobs is
not running on tgt
90
v6.0: Apply job in message
wait
100
v6.0: Apply job on hold on the
target
110
v6.0: Jrnrcv disk used >
threshold set in MONTHR
Halcyon Templates
Activate?
Values
Comments
2-50
Message Queue Example Rules
Rule #
Description
120
v6.0: Rmt jrn not active from
primary to target
130
v6.0: 1+ apply jobs not active
on target
140
v6.0: Apply pnd > threshold
set in MONTHR
150
v6.0: Apply pnd latency > nbr
mins set in MONTHR
160
v6.0: Network latency > nbr
mins set in MONTHR
170
v6.0: Nbr objs req sync >
threshold set in MONTHR
Halcyon Templates
Activate?
Values
Comments
2-51
Message Queue Example Rules
Rule #
Description
Activate?
180
v6.0: Objs req resync >
threshold set in MONTHR
N/A
190
v6.0: Obj in obj sync status
test is out of sync
200
v6.0: Mirrored object is not
currently journaled
210
v6.0: One apply job has had
seq overridden
220
v6.0: One apply job has had
seq overridden
230
v6.0: DTAARA E2CURINFO
contains an invalid CRG
Halcyon Templates
Values
Comments
2-52
Message Queue Example Rules
Rule #
Description
240
v6.0: Unable to change owner
on target
250
v6.0: Unable to change
authority on target
260
v6.0: Audits dis not complete
successfully
270
v6.0: Audit job in message
wait
280
v6.0: Audit has not run within
warning interval
290
v6.0: Audit has not run within
severe interval
Halcyon Templates
Activate?
Values
Comments
2-53
Message Queue Example Rules
Rule #
Description
300
v6.0: Some part of the MIrror
down job not valid
310
v6.0: Mirror down job
command in error
320
v6.0: Apply latency > RSR
MONTHR warning
330
v6.0: Apply latency >RSR
MONTHR
340
v6.0: Error occurred while
processing object
Halcyon Templates
Activate?
Values
Comments
2-54
TCP/IP Rules
C
HAPTER
TCP/IP RULES
CHAPTER3
iTera TCP/IP check
Rule #
Description
10
Check status of source
system
20
Check status of target system
Halcyon Templates
Activate?
Values
Comments
3-55
Job Queue Rules
C
HAPTER
JOB QUEUE RULES
CHAPTER4
E2JOBQ ITHAA1 iTera Job Queue v6.0
Rule #
Description
10
v6.0: Check job queue
E2JOBQ is not held
Halcyon Templates
Activate?
Values
Comments
4-56
Job Queue Rules
E2SYSJOBQ HA61A1 iTera Job Queue v6.1
Rule #
Description
10
v6.1: Check job queue
E2SYSJOBQ is not held
Halcyon Templates
Activate?
Values
Comments
4-57
Performance Rules
C
HAPTER
PERFORMANCE RULES
CHAPTER5
iTERAV60 iTera v6.0 Performance Checks
Rule #
Description
10
Check E2A1SBS subsystem
is active
20
Check no jobs on hold in
subsystem E2A1SBS
25
Check no jobs in MSGW in
subsystem E2A1SBS
Halcyon Templates
Activate?
Values
Comments
5-58
Performance Rules
Rule #
Description
30
PRIMARY: A1_HEALNnn job
must be active
40
PRIMARY: A1_JSNDRC
must be active
50
PRIMARY: A1_OBJMON1
must be active
60
PRIMARY: A1_OBJMON2
must be active
70
PRIMARY: A1_OBJMON3
must be active
80
PRIMARY: A1_RSRMON
must be active
Halcyon Templates
Activate?
Values
Comments
5-59
Performance Rules
Rule #
Description
90
PRIMARY: A1_RJTSAA must
be active
100
PRIMARY: A1_RMTCMD
must be active
110
PRIMARY: A1_SYNC_Nnn
must be active
120
PRIMARY: A1_SYSMON
must be active
130
PRIMARY: JSNDRCJAVA
must be active
140
TARGET: A1_OBJMON1
must be active
Halcyon Templates
Activate?
Values
Comments
5-60
Performance Rules
Rule #
Description
150
TARGET: A1_RSRMON
must be active
160
TARGET: A1_RMTCMD
170
TARGET: A1_JSNDRC must
be active
180
TARGET: ZMA1JRNA must
be active
190
TARGET: ZMA1JRNA must
be active
200
TARGET: ZMA1TJRA must
be active
Halcyon Templates
Activate?
Values
Comments
5-61
Performance Rules
Rule #
Description
210
TARGET: ZRA1SJNA must
be active
220
TARGET: ZU_xxxx must be
active
230
TARGET: ZZA1JRNA must
be active
240
TARGET: XPJRNMGT must
be active
Halcyon Templates
Activate?
Values
Comments
5-62
Performance Rules
iTERAV61 iTera v6.1 Performance Checks
Rule #
Description
10
Check HA61A1 subsystem is
active
15
Check MIMIXSBS subsystem
is active
20
Check no jobs on hold in
subsystem HA61A1
30
Check no jobs in MSGW in
subsystem HA61A1
40
PRIMARY: HA_ALERT job
must be active
50
PRIMARY: HA_APRBMON
job must be active
Halcyon Templates
Activate?
Values
Comments
5-63
Performance Rules
Rule #
Description
60
PRIMARY: HA_AUDMON job
must be active
70
PRIMARY: HA_CHK_E2A job
must be active
80
PRIMARY: HA_CHK_Z_ job
must be active
90
PRIMARY: HA_CHKOBJM
job must be active
100
PRIMARY: HA_CLRSNCO
job must be active
110
PRIMARY: CSTANZ job must
be active
Halcyon Templates
Activate?
Values
Comments
5-64
Performance Rules
Rule #
Description
120
PRIMARY: HA_DEVREP job
must be active
130
PRIMARY: HA_DIRREP job
must be active
140
PRIMARY: HA_HEAL+++ job
must be active
150
PRIMARY: HA_IFSCMD job
must be active
160
PRIMARY: HA_IFSMON job
must be active
170
PRIMARY: HA_IFSPRG job
must be active
Halcyon Templates
Activate?
Values
Comments
5-65
Performance Rules
Rule #
Description
180
PRIMARY: HA_JBSREP job
must be active
190
PRIMARY: HA_JOBMON job
must be active
200
PRIMARY: HA_JRNMGT job
must be active
210
PRIMARY: HA_OBJMON1
job must be active
220
PRIMARY: HA_OBJMON2
job must be active
230
PRIMARY: HA_OBJMON3
job must be active
Halcyon Templates
Activate?
Values
Comments
5-66
Performance Rules
Rule #
Description
240
PRIMARY: HA_OBJMON4
job must be active
250
PRIMARY: HA_PRGLOG job
must be active
260
PRIMARY: HA_RJTSAA job
must be active
270
PRIMARY: HA_RMTCMD job
must be active
280
PRIMARY: HA_RPTREP job
must be active
290
PRIMARY: HA_RSRMON job
must be active
Halcyon Templates
Activate?
Values
Comments
5-67
Performance Rules
Rule #
Description
300
PRIMARY: HA_SNC_+++ job
must be active
310
PRIMARY: HA_SYNCNML
job must be active
320
PRIMARY: HA_SYSINFO job
must be active
330
PRIMARY: HA_SYSMON job
must be active
340
PRIMARY: HA_TRGANZ job
must be active
350
PRIMARY: HA_TRNEXT job
must be active
Halcyon Templates
Activate?
Values
Comments
5-68
Performance Rules
Rule #
Description
360
PRIMARY: HA_USRANZ job
must be active
370
PRIMARY: HA_VLDIFS job
must be active
380
TARGET: ZMHAC01A &
ZMHAC02A jobs must be
active
390
TARGET: ZMHAJRNA job
must be active
400
TARGET: ZMHATJRA job
must be active
410
TARGET: ZRHASJNA job
must be active
Halcyon Templates
Activate?
Values
Comments
5-69
Performance Rules
Rule #
Description
420
TARGET:
ZU_JOURNALNAME job
must be active
430
TARGET: ZZHAJRNA job
must be active
Halcyon Templates
Activate?
Values
Comments
5-70
Audit Journal Rules
C
HAPTER
AUDIT JOURNAL RULES
CHAPTER6
iTERAV60 iTera v6.0 Audit Journal
Rule #
Description
10
E2CSTMGR must not change
20
ITERAOWNER must not
change
30
HAA1SUP must not change
Halcyon Templates
Activate?
Values
Comments
6-71
Audit Journal Rules
40
HAA1ADMIN must not
change
iTERAV61 iTera v6.1 Audit Journal
Rule #
Description
10
MIMIXOWN must not change
20
ITERAOWNER must not
change
30
LAKEVIEW must not change
40
ADMIN must not change
Halcyon Templates
Activate?
Values
Comments
6-72
What Next?
Book a one-to-one, pre-evaluation webinar with our technical experts. We'll focus on areas
relevant to your organization, making the whole session as productive as possible for you.
www.halcyonsoftware.com/learnmore
Learn More
Subscribe to product updates www.halcyonsoftware.com/halcyonnews
For white papers, online product tours, datasheets, Technical Tips, FAQs and manuals
www.halcyonsoftware.com/technical
Contact
Halcyon Software Inc (US)
t: 215 240 8838
e: [email protected]
w: www.halcyonsoftware.com
Halcyon Software (Europe)
t: +44 (0) 1733 234995
e: [email protected]
w: www.halcyonsoftware.com
Halcyon Software (Australia) Pty Ltd
t: 613 9495 6600
e: [email protected]
w: www.halcyonsoftware.com
Trademarks
IBM®, iSeries®, Power/System i®, IBM i®, i5/OS® and AIX® are registered trademarks of
International Business Machines Corporation in the United States and in other countries.
Vision Solutions® and iTERATM are trademarks of Vision Solutions, Inc.
Linux® is a registered trademark of Linus Torvalds
All other trademarks are respective of their own companies.