websphere mq monitoring - helpsystems€¦ · websphere mq monitoring template 2-3 figure 2.1...

guide to WebSphere MQ monitoring

CopyrightCopyright 2010 - 2019 Halcyon - A division of HelpSystems. All rights reserved.

This documentation contains Halcyon proprietary and confidential information and may not bedisclosed, used, or copied without the prior consent of Halcyon Software or as set forth in theapplicable license agreement. Users are solely responsible for the proper use of the softwareand the application of the results obtained.

Although Halcyon Software has tested the software and reviewed the documentation, the solewarranty for the software may be found in the applicable license agreement between HalcyonSoftware and the user.

Publication Revision: June 2019

Overview Halcyon Templates are designed to provide the same level of monitoring across a number ofsimilar devices by applying a set of user-defined filters with a single-click. This greatly reducesset-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 allsystems using the template.

C H A P T E R

CHAPTER 1INTRODUCTION

WebSphere MQ, a member of the WebSphere family from IBM, is the mostpopular system for cross- platform messaging, providing assured delivery ofmessages across 35 plus IBM and non-IBM platforms, including IBM mainframeand midrange, Windows, Linux, and UNIX. WebSphere MQ is often referred toas "MQ" or "MQ Series".

Key components of WebSphere MQ that require monitoring are:

• "MQ Channels” (up/down)

• "Listeners” (up/down)

• "MQ Queue Depth” (alert if a large build up of messages)

• "Dead Letter Queue”

• "Individual MQ elements” (jobs)

A specialist template has been created to monitor IBM message queues for thecommonest messages generated by the WebSphere MQ application.

Halcyon's Record & Playback utility can be used to record key events,keystrokes, command entry and activity checking routines on these criticalareas of WebSphere MQ. The resulting scripts can then be replayed using thesession play command PLAYSSN from within the IBM Job Scheduler.

For added flexibility and to control the scheduled running of the Record andPlayback scripts, the Halcyon Advanced Job Scheduler can be deployed.

Alternatively, the session can be replayed using the COMMAND action fromwithin any Halcyon Rule (supplied as standard within any of our IBM i ProductSuites). Should an error be found, an alert can be sent to a message queue, viaemail, SMS or to Halcyon's centralized GUI Enterprise Console.

I n t r o d u c t i o n 1-1

C H A P T E R

CHAPTER 2WEBSPHERE MQ MONITORINGTEMPLATE

If you already use any of Halcyon's Level 1 to 4 software suites then followthese instructions to install templates to a customized environment on the IBM i.

If you do not currently use Halcyon's tools in your WebSphere MQ environmentbut wish to have more information, an on-line demonstration or a free trial thenplease see the list of contacts on the back page of this guide.

Installation of Customized EnvironmentFollow 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.

3 From the command line run ENDMON and press F4. Follow the prompts to complete the ending of the monitors.

Note: 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.

2- 2 H a l c y o n S p e c i a l i s t M o n i t o r i n g

Figure 2.1 Entering the customization code

Note: 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 withRules. The template rules applicable to the customized environment that youinstalled can be found in the listed queue and rule groups. Default actionschedules are installed and additionally, where appropriate, changes tosystem defaults may also be made.

In most cases, the templates supplied can be used immediately uponcompletion of installation, but there may be instances where you need tochange rule properties to match those of your own environment. This can bedone by taking option 2=Change against the rule and making the requiredchanges. Similarly, should you require multiple rules for different messagequeues or devices and so on you can use option 3=Copy against the ruleand then make the required amendments.

W e b S p h e r e M Q M o n i t o r i n g t e m p l a t e 2-3

ActionsUnless otherwise specified, all template rules are implemented with a defaultaction schedule which sends an alert message to your local console (option10=Message Console from the main menu). Should you wish to amend thisoption, take option 2=Change against the action within the rule and make theamendments as required.

Note: Please refer to the user reference guide for your Halcyon solution for details of actions that may be applied to rules.

Message Queue Rules

QMQMMSG QMQM MQ Message Queue

0 No Global ExclusionsSequence 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 theexclusion. If a global exclusion exists for a message, then none of the othersequence numbers for this message queue are searched for a match and noaction is taken.

10 WebSphere MQ was unable to display an error messageWebSphere MQ has attempted to display the message associated with ahexadecimal return code that has no associated message text. This issue canarise if the message catalog is missing or has become corrupted. On Linuxinstallations that use NPTL threading, this can occur when environment variableLD_ASSUME_KERNEL is not set.

This rule, which runs 24/7, monitors for message AMQ6090 in message fileAMQMSG within library QMQM. If found to be present, an alert is raised and amessage sent to the Message Console.

Possible solutions to this issue include:

• Copy the amq.cat file from another Websphere MQ installation (at the same MQ version) that is not experiencing this problem

• Increase the number of file descriptors

• WebSphere MQ 5.3 operating in Linux requires the environment variable:

export LD_ASSUME_KERNEL=2.4.19

prior to installing the product, creating/starting a queue manager or prior to issuing any command.


20 An internal Websphere error has occurredWebSphere MQ has detected an unexpected error when calling the operatingsystem. This error can be caused by many reasons and the message raised isvery generic.

This rule, which runs 24/7, monitors for messages AMQ6119, AMQ6125 andAMQ6183 in message file AMQMSG within library QMQM. If any of thesemessages are found to be present, an alert is raised and a message sent to theMessage Console.


• An FFDC report is generated that may help you diagnose the cause of failure. Use the probe id in the FFDC to search for known problems.

• The queue manager error logs and @System error log may have other messages related to the failure that may help you with resolution.

30 (Windows) WebSphere MQ semaphore is busyWebSphere MQ was unable to acquire a semaphore within the normal timeoutperiod. This usually occurs as a result of applications ending normally orabnormally without disconnecting from WebSphere MQ.

This rule, which runs 24/7, monitors for message AMQ6150 in message fileAMQMSG within library QMQM. If any of these messages are found to bepresent, an alert is raised and a message sent to the Message Console.


• Ensure that all applications disconnect from WebSphere MQ before ending.



40 Internal WebSphere MQ error on queue managerAn error has been detected and the WebSphere MQ error recording processhas been called. This is a very generic error informing you that another processhas failed. Use the process number in the message to correlate it with theFFDC record for the failing process.






50 Transactions rolled back to release log spaceThe log space for the queue manager is becoming full. One or more long-running transactions have been rolled back to release log space so that thequeue manager can continue tot process requests. The size of the log dependsprimarily upon the duration of the longest running Unit of Work (UOW) and thethroughput on the log. When the log starts to become full, the queue managerstarts backing out long running transactions and penalizing heavy log users.



• Committing Units of Work more frequently.

• Increase the number of log files

• Increase the size of the log files

60 WebSphere MQ error &1 has occurredAn unexpected reason code with a hexadecimal value was received from theWebSphere MQ queue manager during command processing. Moreinformation might be available in the log. This is a serious error that usuallyprevents you from staring or creating a queue manager.





70 Remote host &4 not available, retry laterThe attempt to allocate a conversation a remote host was not successful.However the error may be a transitory one and it may be possible tosuccessfully allocate a remote host conversation later. This is caused by achannel connection problem and happens most frequently when:

• Listener is not running

• Incorrect settings in inted.conf

• QMGR is not running

• Routing information in the queue remote’s rname or rqmname is incorrect

• Routing information in the channel’s conname or xmitq is incorrect






80 Error on receive from host &3An error occurred when receiving data from a host. This may be due to acommunications failure. Return codes 10054 (Windows), 73 (AIX), 131(Solaris), 232 (HP-UX), 104 (Linux) or 3246 (iSeries) means that the connectionis reset by peer (ECONNRESET). This usually indicates a problem in the TCP/IP network.



• Use TCP/IP packet and sniffer traces to determine why the reset occurred.

90 Connection to host &3 closedAn error occurred receiving data from a host connection. The connection to theremote host has unexpectedly terminated. This is most likely caused byincorrect settings in the /etc/services and INETD.CONF files.



• Verify that INETD.CONF and /etc/services files match the name of the queue manager and listener port

• Try using the runmqlsr command on the remote queue manager (receiver side).

100 A communications error for &4 occurredAn unexpected error occurred in communications. This is most likely caused by the inetd configuration file not having the correct information or syntax.



• Try using the runmqlsr command on the remote queue manager (receiver side)


110 The &4 responder program could not be startedAn attempt was made to start an instance of the responder program, but theprogram was rejected. The most common cause of this issue is that the inetdconfiguration file did not have the correct information or syntax.



• Try using the runmqlsr command on the remote queue manager (receiver side)

120 Channel negotiation failedChannel between this machine and the remote machine could not be established due to a negotiation failure. This error can be raised for many reasons.





130 Message sequence number error for channel &3The local and remote queue managers do not agree on the next message sequence number. A message with sequence number &1 has been sent when sequence number &2 was expected. The most common causes of this issue are:

• Manually resetting a receiver channel message sequence number

• Deleting and redefining a channel

• Two instances of the same receiver channel



• Never reset a receiver channel’s message sequence number.


C H A P T E R

CHAPTER 3WEBSPHERE MQ MONITORING

MQ Monitoring Record & Playback Scripts

Halcyon’s Record & Playback is used to run 4 specially created scripts tomonitor WebSphere’s MQ Channels.

Providing that you have Record & Playback installed on your system, at thecommand line type:

GO HRP400/HRP

Figure 3.1 Starting Halcyon Record & Playback

W e b S p h e r e M Q M o n i t o r i n g 3-9

The Record & PlayBack main menu is displayed.

Figure 3.2 Record & Playback main menu

Select Option 3=Edit Scripts to open the Edit Scripts display.

Figure 3.3 Edit Scripts display

Within this display are the four scripts which monitor WebSphere MQ. They are:

• CHKMQM

• CHKMQMCHL

• CHKMQMCHLG

• CHKMQMQ

CHKMQM (WebSphere MQ Manager Checking) ScriptThe CHKMQM script checks the queue managers to ensure that they areactive. In its default format, this script checks for two queue managers. If youhave more (or less) than two queue managers you must edit the script toinclude the additional managers.

Figure 3.4 CHKMQM script

If a queue manager is found to be in an inactive status, the following program iscalled:

HRPDATA/SNDMGRSTS

This sends the Message ID:

MQM0003

to Message Queue:

QSYSOPR


The message text of this message ID reads:

MQ Queue Manager &1 is &2

where:

&1 represents the Queue Manager name

&2 represents the current status

CHKMQMCHL (Active MQ Channels Running) ScriptThe CHKMQMCHL script checks that MQ Channels that are meant to be active,are running. As this script checks for specific channels, it requires editing withthe correct channel configuration for your operating environment. You mayneed to add further channels as required

Figure 3.5 CHKMQMCHL script

The MQ Manager Name is identified in line 7 of this script:

0007.00 K 20/7 'WRKMQMCHL MQMNAME('VLEARTHQM')'

Lines 15, 28 and 35 of this script identify the MQ Channels that exist within the MQ Manager.

0015.00 P IF &SCR(&Y/8:20) = 'FIPVP01.TO.NEPTUNE '

0028.00 P IF &SCR(&Y/8:20) = 'VLMERCURY.TO.VENUS '

0035.00 P IF &SCR(&Y/8:20) = 'VLSATURN.TO.VLCPAD '

Note: Remember to edit the MQ Manager Name and Active MQ Channels within this script to replicate your own environment.

If a channel is found to be inactive, the following program is called:

HRPDATA/SNDCHLSTS


MQM0002

to Message Queue:

QSYSOPR


MQ Channel &1 has status &2

where:

&1 represents the Channel name

&2 represents the current status

CHKMQMCHLG (ALL MQ Channels Running) ScriptThis is basically the same as the CHKMQMCHL script but it checks ALL MQChannels rather than just those that specified within the CHKMQMCHL script.

Figure 3.6 CHGMQMCHLG Script


Note: Remember to edit this script to reflect your own operating environment configuration.

CHKMQMQ (Message Queue Depth) ScriptThis script checks the Message Queue Depth on the System Dead LetterQueue and any other queue beginning with Q*.

Figure 3.7 CHKMQMQ Script

There are two separate checks made against two variables:

• &LOWCOUNT=500

• &HIGHCOUNT=5000

These limits can be amended so that they are more representative of the queuedepths experienced in your environment. In both cases, an alert is raised if thequeue depth exceeds the specified value. The first criteria (&LOWCOUNT) isdesigned as a type of ‘early-warning’ safeguard to the second (&HIGHCOUNT)criteria.

Using the &LOWCOUNT criteria as an example: If the depth of System Dead Letter Queue exceeds 500, the following programis called:

HRPDATA/SNDMQDEPTH

3- 1 4 H a l c y o n S p e c i a l i s t M o n i t o r i n g


MQM0001

to Message Queue:

QSYSOPR


MQ Message Queue &1 at depth &2

where:

&1 represents the Message Queue name

&2 represents the current queue depth

Editing the script for remaining message queues:Page down the script so that line 48 is visible:

0048.00 K 20/7 'WRKMQMQ QNAME(Q*)'

Edit this line to determine the additional message queues to be monitored.


C H A P T E R

CHAPTER 4SETTING MQ MONITORING RULES

Once the Record and Playback Scripts have been amended for your ownenvironment, you need to set a Message Queue rule in order that the generatedmessages cause actions to be invoked.

Providing that you are using Halcyon’s Level 2 - Systems Operations Suite orabove, you can additionally set Performance Rules to ensure that subsystemsare active and that MQ jobs are running.

Creating the MQ Message Rule

1 Log onto your Halcyon Suite and operating environment as usual:

GO HALxxxx/HALCYON

(where xxxx represents the name of your environment).

2 From the main menu select option 5=Work with Rules.

3 With the cursor positioned next to the Message Queue Rules, press F11 to expand the display.

4 Position the cursor next to the QSYSOPR Message Queue and press F11 again to display the rules that already exist in this group.

5 Page Down and position the cursor against the last entry in this Rule Group.

6 Type 1 and press <ENTER> to insert a new rule into this Rule Group.

You are now ready to enter the details of the rule.

1 Type the Rule Description as All HRP Messages

2 Press Page Down.

3 Type 2 against the existing entry to change the rule detail. Press <ENTER>


4 Tab down to the Library parameter and type HRPDATA over the existing entry.

5 Move the cursor back up to the Message File parameter and press F4.

6 From the pop-up display, select the HRPALTMSGF entry. Press <ENTER>.

Note: At this point a warning message, advising that the entered criteria may cause unpredictable results is displayed. This can be ignored.

Press <Enter> again.

Figure 4.1 Amending Message Queue Rule detail

7 Against the newly amended rule, select option 8=Count/Method to change the current count method. Press <ENTER>.

8 Change the Message Count method from *JOBNBR to *MSGDTA. Press <ENTER>.

You are now ready to start adding actions to this rule.

Adding ActionsThis rule will have three actions applied in order to:

• Notify you of the alert

• Reset the rule

• Delete any repeats of the alert occurring within the following 60 minute period

S e t t i n g M Q M o n i t o r i n g R u l e s 4-17

Adding a Console actionThis action sends a notification of the rule alert to a Console view of yourchoice.

1 Position the cursor so that it is in the lower half of the Add Message Queue Action display (under the Actions line). Press F6. This opens the Add Message Queue Action display.

2 In the Action Type field, type CONSOLE and press <ENTER>.

3 In the System parameter, leave the setting as *LOCAL to send the alert to the iSeries Message Console or specify the name of the Remote Location on which another Message Console or Enterprise Console version is running.

4 Press <ENTER> to confirm.

Adding a Reset Rule actionThis action resets the rule following an alert being sent to the console.


2 In the Action Type field, type RSTRULE and press <ENTER>.

3 In the Delay parameter, type 3600 to specify the delay before the reset rule action runs, as being 60 minutes.


Adding a Delete Alert actionThis action deletes the alert providing all actions have been completed withouterror.


2 Change the Action Sequence Number to 20.

3 In the Action Type field, type DELETE and press <ENTER>.


Changing the Console CountTo prevent multiple alerts being sent to the Console, change the message countto 1, so that the rule only triggers on the first occurrence of the alert beingraised. To do this:

1 Position the cursor next to the Console action in the list of actions. Type 8 and press <ENTER>.

2 Change the ‘Perform action for’ parameter to 1. Press <ENTER>.

3 The Console action (and its associated Reset Rule action) now have a count of 1 applied.


Press <ENTER> to complete the creation of the Message Queue rule.

Figure 4.2 Message Queue Rule with associated actions

Creating Performance Rules

Performance Rules are used to ensure that critical subsystems are active andthat required MQ Jobs are running.

Note: You must have Halcyon Level 2 - Systems Operations Suite or higher to be able to set Performance Rules.

1 Log onto your Halcyon Suite and operating environment as usual:

GO HALxxxx/HALCYON

(where xxxx represents the name of your environment).

2 From the main menu select option 5=Work with Rules.

3 With the cursor positioned next to Performance Rules, type 1 to create a new Performance Rule Group.

4 Enter the Performance Group Name as HRP and the Description as HRP Performance Rules. Press <ENTER> to confirm.


You are now ready to create the first rule.

Checking the WebSphere MQ Subsystem is active1 Type 1 against the HRP Performance Rules Group to insert a new rule.

Press <ENTER>.

2 Enter the Rule description as WebSphere MQ Subsystem Monitoring. Press <PAGE DOWN>.

3 Type 2 against the existing entry to change the rule detail. Press <ENTER>.

4 Change the Rule Type to *SUBSYSTEM. Press <ENTER>.

5 Enter the Subsystem Name as QMQM and the Value as *INACTIVE. Press <ENTER>

6 Position the cursor so that it is in the lower half of the Add Message Queue Action display (under the Actions line). Press F6. This opens the Add Performance Action display.

7 Add an action that is suitable for your notification requirements. Press <ENTER>.

8 Add further actions as required.

Checking MQ Listener JobsThis rule checks that the WebSphere MQ Listener Jobs are running asexpected.

1 Type 1 against the HRP Performance Rules Group to insert a new rule. Press <ENTER>.

2 Enter the Rule description as Check MQ Listener Jobs. Press <PAGE DOWN>.


4 Change the Rule Type to *JOB. Press <ENTER>.

5 Change the Job Name from *ALL to RUNMQLSR. Tab down to the Subsystem parameter.

6 Enter the Subsystem as QMQM. Tab down to the Statistic parameter.

7 Enter the Statistic as JOBCOUNT. Tab down to the Comparison parameter.

8 Enter the Comparison as *LT (Less than). Tab down to the Value parameter.

9 Enter the values as 1 (or the number of MQ listeners that currently operate in your WebSphere environment. Press <ENTER>.

10Position the cursor so that it is in the lower half of the Add Message Queue Action display (under the Actions line). Press F6. This opens the Add Performance Action display.

11Add an action that is suitable for your notification requirements. Press <ENTER>.

12Add further actions as required.


Checking WebSphere MQ JobsThis rule checks that there are Jobs running within the MQ Subsystem.

1 Type 1 against the HRP Performance Rules Group to insert a new rule. Press <ENTER>.

2 Enter the Rule description as Check WebSphere Jobs. Press <PAGE DOWN>.


4 Change the Rule Type to *JOB. Press <ENTER>.

5 Leave the Job Name as *ALL. Tab down to the Subsystem parameter.

6 Enter the Subsystem as QMQM. Tab down to the Statistic parameter.

7 Enter the Statistic as JOBCOUNT. Tab down to the Comparison parameter.

8 Enter the Comparison as *LT (Less than). Tab down to the Value parameter.

9 Enter the values as 1 (or the number of MQ listeners that currently operate in your WebSphere environment. Press <ENTER>.

10Type 2 against the existing entry to change the rule detail again. Press <ENTER>.

11Tab down to the Allow alerts when subsystem not active parameter and change the entry from *YES to *NO. Press <ENTER>.

12Add an action that is suitable for your notification requirements. Press <ENTER>.

13Add further actions as required.

Performance Rules are now complete. Use the Chapter 5 - “Checking/EditingCL Source and Message File” to amend any CL Source and Message Fileconfigurations


C H A P T E R

CHAPTER 5SCHEDULING THE RUNNING OF THERECORD & PLAYBACK SCRIPTS

In order that the Record & Playback scripts monitor WebSphere MQ on aregular and ongoing basis, a schedule must be created and applied to ensureconsistent monitoring.

In best practice and for ease-of use, Halcyon recommends that the schedule isset up using Halcyon Advanced Job Scheduler (available in Halcyon’s Level 4 -Operations Center Suite or as a standalone product).

Otherwise, a TCP/IP rule can be created (using a false IP Address) that thencauses a command action to be run that invokes the Record & Playback scripts.

Creating a TCP/IP rule to schedule the Record & Playback scripts

To create a TCP/IP schedule rule:

1 From the Halcyon Suite main menu select option 5=Work with Rules.

2 Position the cursor next to the TCP/IP rule. Type 1 and press <ENTER>.

3 Type HRPSched as the Group Name and HRP Scheduler as the Description. Press <ENTER>.

4 Against this newly created group, type 1 (to insert a new rule) and press <ENTER>.

5 Type HRP Script Scheduling as the Rule Description. Tab down to the Check Interval parameter and ensure the entry is set to 300. Press <PAGE DOWN>.


7 Tab down to the Remote Internet Address field and type 1.2.3.4. (or any other IP address that does not exist). Enter the Description as HRP Scheduler.


8 Tab down to the Wait Time parameter and change the current entry to 1 (must be right-aligned). Press <ENTER>.

9 Position the cursor below the Actions line and press F6.

10Enter COMMAND as the Action and press <ENTER>.

11Type the following command:

HRP400/PLAYSSN SCRIPT(CHKMQMQ)and press <ENTER>

12Repeat steps 9 to 11 for the following commands:

HRP400/PLAYSSN SCRIPT (CHKMQMCHL)

HRP400/PLAYSSN SCRIPT (CHKMQM)

Note: This rule uses QSYSOPR Action Monitor profile by default. If QSYSOPR is not authorized to play Record & Playback scripts, the action monitor user profile system default (HAL/ACTMONUSER) requires editing to provide a user profile with the correct level of authorization.

13Finally, press F6 again to add a DELETE action.

14Enter DELETE as the Action Type and press <ENTER>. Tab down to the Condition parameter and select *COMP as the entry.

15Tab down to the Delay parameter and type 200 as the entry. Press <ENTER>

Your completed screen should now look like the one below:

Figure 5.1 Completed TCP/IP rule

S c h e d u l i n g t h e R u n n i n g o f t h e R e c o r d & P l a y b a c k S c r i p t s 5-23

16Press <ENTER> to complete the rule.

The TCP/IP rule is now complete.

As the Remote Internet address is False, an alert is generated every fiveminutes which then runs the Record & Playback scripts required to monitorWebSphere MQ. Once completed the alert is deleted and the five minutechecking schedule continues.


C H A P T E R

CHAPTER 6CHECKING/EDITING CL SOURCE ANDMESSAGE FILE

Use the following routines to check and edit the CL Source Files and theMessage File details used within Record and Playback scripting

Viewing the CL Source Files

From within Record & Playback, use the following command to view the CLSource Files:

WRKMBRPDM

and press F4. This opens the Work with Members using PDM display.

1 In the File parameter, type QCLSRC.

2 In the Library parameter, type HRPDATA.

C h e c k i n g / E d i t i n g C L S o u r c e a n d M e s s a g e F i l e 6-25

Figure 6.1 Work with Members using PDM Display with completed parameters

3 Press <ENTER>. The members within the HRPDATA Library and QCLSRC file are now displayed:

Figure 6.2 HRPDATA members


From this screen, you can display and edit the contents of each of the programscalled when using any of the WebSphere MQ Monitoring scripts used withinHalcyon Record and Playback.

Viewing the Message File

From within Record & Playback, use the following command to view theMessage File that contains the Record & Playback alert messages:

WRKMSGF

and press F4 to open the Work with Message Files display.

1 In the File parameter, type HRPALTMSGF.

2 In the Library parameter, type HRPDATA.

3 Press <ENTER>.

Figure 6.3 Work with Message Files display

Take option 5=Display Message Descriptions followed by 5=Display Detailsto show the details of the individual messages.

To amend the message details, use option 2=Change.

C h e c k i n g / E d i t i n g C L S o u r c e a n d M e s s a g e F i l e 6-27

Halcyon TemplatesThe following system templates are available for use with Halcyon IBMi and Windows monitoring solutions:

• AIX• AIX TEMENOS 24• AIX VIOS• HP DATA PROTECTOR• IBM SERVICES MONITORING

iCLUSTER• INFOR M3• INFOR SYSTEM 21• INFOR XA• JD EDWARDS• LINUX• MAXAVA• MISYS EQUATION• MISYS MIDAS PLUS• POWER HA• QUICK EDD• ROBOT HA• SAP• STAND GUARD ANTI VIRUS• SYMANTEC BACKUP EXEC• SYMANTEC NETBACKUP• VISION iTERA• VISION OMS/ODS REPLICATION• WEBSPHERE MQ MONITORING• WINDOWS

Learn MoreFor white papers, online product tours, datasheets, technical tips and manuals, please visit: https://www.helpsystems.com/halcyon

Contactwww.helpsystems.com

US: Toll-free: 800-328-1000

+1 952-933-0609

Outside the U.S.: +44 (0) 1252 618030

TrademarksIBM®, 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,

All other trademarks are respective of their own companies.

https://www.helpsystems.com/halcyon

https://www.helpsystems.com/halcyon

websphere mq monitoring - helpsystems€¦ · websphere mq monitoring template 2-3 figure 2.1...

Documents