MESSENGER - HelpSystems · downtime. Messenger has the tools necessary to prevent server downtime....
142
MESSENGER User’s Guide—Version 8.1
Transcript of MESSENGER - HelpSystems · downtime. Messenger has the tools necessary to prevent server downtime....
MESSENGER User’s Guide—Version 8.1
MessengerPlus Version 8.10
MessengerConsole Version 8.10
Documentation Revised: September 10, 2014
LICENSE AGREEMENTBy installing and/or using the version of BYTWARE Product that you are licensing, or as scheduled in any attachment to this Agreement, you are agreeing to become bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, do not install or use the Product—consult with your sales representative or other BYTWARE representative. This Agreement cannot be modified or amended except in writing signed by an authorized representative of BYTWARE. The BYTWARE software, its documentation, and any Upgrades to the software that may be provided, are the “Product.” The Product and all related documents, including copyright rights, is owned by BYTWARE.
Upon receipt of Your payment for the Product(s), BYTWARE grants to You a limited, nontransferable, and nonexclusive license to use the Product, subject to the terms herein.
Product Try and Buy Offer. Subject to the terms of this Agreement, BYTWARE grants a limited, revocable, royalty-free, onetime license to use the Product for a temporary period of up to 15 days. The Product will automatically cease to work at the end of the temporary usage period.
Product License Fees. BYTWARE Product(s) are licensed per each copy installed or based on usage per system, CPU, or partition, depending on your Order Confirmation. You may only install or use the Product according to the number of copies or use parameters indicated for each system, CPU, or partition, on the Order Confirmation.
Continuing Fulfillment. If BYTWARE elects, in its sole discretion, to produce subsequent upgrades and revisions to the Product (collectively, “Updates”), You may order such Updates as they become available. Fees may charged for Updates if You do not have a current support sub-scription. BYTWARE only provides product fulfillment and support for BYTWARE products so long as the underlying or necessary IBM OS and McAfee scanning engines are supported—BYTWARE cannot provide ongoing fulfillment or support for IBM OS operating system or McAfee-owned scanning engine issues in the event that such third-party products are no longer offered or supported. If a product is no longer being supported and an Upgrade is available, You must upgrade to the then-current supported version of the Product in order to obtain any sup-port that you may otherwise have subscribed to. All Updates are subject to the terms of this Agreement.
Copies. You may not copy or duplicate the Product, except as necessary solely for archival purposes or disaster recovery. In the event of an emergency, BYTWARE will grant a temporary authorization code for the Product to be operated on a disaster recovery machine. You may not remove any copyright or other proprietary notices contained in any Product.
Transfer. You may not sell, lease, rent, lend, copy, sublicense, transfer, disclose or distribute this Agreement or the Product, in any form, to any third party; provided, however, you may, with BYTWARE’s prior written approval and payment of applicable transfer fees to BYTWARE, transfer the Product to a new or upgraded system. Partition Products licensed for a partition may only be transferred to another partition on the same CPU. BYTWARE may assign any or all rights in this Agreement or any maintenance agreement at any time without notice.
Confidentiality. You may not reverse-assemble, decompile, or otherwise reverse-engineer the Product, in whole or in part, or direct any other person, or permit any other person under your control, to do so. You agree to keep the Product and all such copies confidential and in Your secure possession.
WARRANTY/LIABILITY: The Product and related materials are provided on an “AS IS” basis. No other warranties, either express or implied apply, ex-cept that BYTWARE warrants that to its actual knowledge as of the license grant that the Product (excluding any third-party components such as the McAfee scanning engine) does not infringe or violate any U.S. patents, copyright, trademark or other proprietary rights of a third party. BYTWARE shall not be liable for any lost revenue, profit, or data, or any indirect, incidental or consequential damages arising out of Your use or inability to use the Product, or the breach of any warranty provided herein, even if BYTWARE has been advised of possible or such damages. In no event shall the liability of BYTWARE for any losses, damages, or costs arising from Your use or inability to use the Product, or the breach of any warranty provided herein, exceed the fee paid by You for this license. The foregoing limitations shall apply even if this remedy fails of its essential purpose.
GENERAL: This Agreement and any dispute arising from or relating to it shall be governed by and construed and enforced in accordance with Min-nesota law, without reference to conflicts of laws principles. Any legal action or proceeding shall be instituted in a state or federal court in Hennepin County, Minnesota, USA. You agree that this document represents the complete agreement between You and Help/Systems, LLC, doing business as Bytware (BYTWARE) and supersedes all previous oral and written agreements. Any breach of this agreement shall subject the breaching party to liability for actual damages sustained by the other for said breach, including reasonable attorney’s fees and costs of contract enforcement to the prevailing party. BYTWARE may terminate this Agreement immediately if You cease to carry on Your present business or become insolvent, make a general assignment for the benefit of creditors, or are involved in a bankruptcy or receivership proceeding. BYTWARE’s right to terminate the Agreement is in addition to and not in limitation of any other available remedies. Upon termination, Purchaser agrees to destroy the original and all copies of the Product in its possession or control.
Copyright © HelpSystems, LLC. All rights reserved. Bytware is a division of HelpSystems. Bytware, 6455 City West Parkway, Eden Prairie, MN 55344 USA
iii
Contents
ContentsTable of Contents
About this Guide ...................................................................................................... 1Glossary of terms ........................................................................................................................................................ 1Using online help ........................................................................................................................................................ 1
Chapter 1 - Introduction ........................................................................................... 3MessengerPlus Features ............................................................................................................................................... 3Pre-Configured Monitors ............................................................................................................................................... 7Event Consolidation with MessengerConsole ................................................................................................................ 8
Chapter 2 - Installation ............................................................................................. 9Requirements ................................................................................................................................................................ 9What the installation program does .............................................................................................................................. 9Installing Messenger ...................................................................................................................................................... 9
Chapter 3 - MessengerPlus Menus.......................................................................... 11Main Menu ................................................................................................................................................................. 11Setup Menu ................................................................................................................................................................. 11Support Menu .............................................................................................................................................................. 12Reports Menu .............................................................................................................................................................. 13
Chapter 4 - System Options .................................................................................... 15
Chapter 5 - Modem Configuration and Setup .......................................................... 17Working with Modems .............................................................................................................................................. 17Modem Details ............................................................................................................................................................ 18IBM Internal Modem ................................................................................................................................................... 22IBM 7852-400 .............................................................................................................................................................. 22MultiTech MultiModem GPRS Wireless Modem ......................................................................................................... 22Other Modems ............................................................................................................................................................ 24Testing your modem .................................................................................................................................................... 24
Chapter 6 - Paging Companies ................................................................................ 25Working with Paging Companies ................................................................................................................................ 25Paging Company Details .............................................................................................................................................. 26
Chapter 7 - Paging .................................................................................................. 29About Paging ............................................................................................................................................................... 29Working with Pagers .................................................................................................................................................... 32Pager Details ................................................................................................................................................................ 33SYSLOG Options ........................................................................................................................................................... 38Pager List Options ........................................................................................................................................................ 39Pager Schedule Options ............................................................................................................................................... 39Pager Authorities ......................................................................................................................................................... 40Sending Pager Messages .............................................................................................................................................. 46Working with Pager Messages ..................................................................................................................................... 47Working with Pager Message History .......................................................................................................................... 48
iv
Messenger V8R1M0
Troubleshooting ........................................................................................................................................................... 49Pager Message Error Codes ......................................................................................................................................... 51Restricted State Paging ................................................................................................................................................ 53
Chapter 8 - Monitoring ........................................................................................... 55Introduction ................................................................................................................................................................ 55Working with Monitors ................................................................................................................................................ 55Monitor Details ............................................................................................................................................................ 57Working with Event Monitors ...................................................................................................................................... 58Event Monitor Details .................................................................................................................................................. 60System Default Pager Setup ......................................................................................................................................... 62Audit Journal Monitoring ............................................................................................................................................. 62CPU Monitoring ........................................................................................................................................................... 72Disk Monitoring ........................................................................................................................................................... 72Line Status Monitoring (WRKCFGSTS) .......................................................................................................................... 73Message Queue Monitoring ........................................................................................................................................ 74Job Start or Complete (by specified time) Monitoring ................................................................................................ 82Job Status monitoring .................................................................................................................................................. 83JOBRUN (*JOBRUN) Monitoring - Setup ...................................................................................................................... 87Job Log (*JOBLOG) Monitoring - Setup ........................................................................................................................ 88Job Queue Monitoring ................................................................................................................................................. 89Output Queue Monitoring ........................................................................................................................................... 90Ping Monitoring ........................................................................................................................................................... 90Setting Up a Numeric Pager to Receive Event Notifications ........................................................................................ 91Troubleshooting ........................................................................................................................................................... 92
Chapter 9 - Actions ................................................................................................. 93Working with Actions ................................................................................................................................................... 94Action Details ............................................................................................................................................................... 96
Chapter 10 - Schedules ......................................................................................... 101Working with Schedules ........................................................................................................................................... 101
Chapter 11 - Events .............................................................................................. 105Working with events .................................................................................................................................................. 105Event Details .............................................................................................................................................................. 106Action History ............................................................................................................................................................ 106Working with User Actions ........................................................................................................................................ 107Working with Event Queues ...................................................................................................................................... 108Event Queue Details................................................................................................................................................... 109Event Queue Lists ...................................................................................................................................................... 110
Chapter 12 - MessengerConsole ........................................................................... 111Introduction ............................................................................................................................................................... 111Working with Systems................................................................................................................................................ 114Console System Setup ................................................................................................................................................ 116Remote System Setup ................................................................................................................................................ 116Testing connectivity ................................................................................................................................................... 117Distributing a Monitor ............................................................................................................................................... 118Alternate Console Setup ............................................................................................................................................ 119Testing ........................................................................................................................................................................ 120
v
Contents
Chapter 13 - Downloading Program Temporary Fixes (PTF) ................................... 121About PTFs ................................................................................................................................................................ 121Setup .......................................................................................................................................................................... 121Example ..................................................................................................................................................................... 123Troubleshooting ......................................................................................................................................................... 123Recommendations ..................................................................................................................................................... 123
Chapter 14 - Appendix .......................................................................................... 125Analyzing QHST Messages ........................................................................................................................................ 125Changing the date format .......................................................................................................................................... 125Changing the system date/time ................................................................................................................................. 125Command APIs ........................................................................................................................................................... 126Configuring the Attention key pop-up window .......................................................................................................... 126Entering your security code ....................................................................................................................................... 127Local Data Area (*LDA) usage .................................................................................................................................... 127Removing MessengerPlus from your system ............................................................................................................. 128Security and *PUBLIC authority ................................................................................................................................. 128Starting MessengerPlus automatically at IPL ............................................................................................................. 129Bytware Technical Support ........................................................................................................................................ 130
Index .................................................................................................................... 133
vi
Messenger V8R1M0
1
About this Guide
About this GuideGlossary of terms
ActionRefers to an automated operation that MessengerPlus performs when an event occurs, such as sending a pager message, running a command, and so on.
EventRefers to any type of detectable change that occurs on the system. An event could be a message, or the absence of a message or job.
Event MonitorRefers to collection of filters and actions, combined into a single group.
FilterRefers to a record that defines a specific data item that you want to include or exclude from monitoring, such as a specific message or job. MessengerPlus creates events as a results of the filters you define.
MonitorRefers to a collection of event monitors that are defined over a common data group, such as a message queue or active job. Monitors are the highest level of grouping that occurs within MessengerPlus.
PagerRefers to traditional pagers of various types as well as many types of virtual pager types, such as email addresses, Syslog servers, telephones, groups, schedules, and so on.
Using online help
Online help is available from every panel. Press F1 or Help to open the Help Window. Help is cursor-sensitive, meaning the help that is displayed depends upon where you position your cursor. You can access help about a specific field, topic, or entire panel. The online help may contain updated information not detailed in this guide.
Text conventionsInformation that follows this icon provides step-by-step instructions for accomplishing a task. These general instructions can be easily adapted to your own needs.
Information that follows this icon includes helpful hints, caveats and tips to help you avoid problems and save time.
Information that follows this icon refers to other sections of the guide that are related to the current topic.
About this Guide
2
Messenger V8R1M0
3
Introduction
Chapter 1 - IntroductionAn IBM i system can generate and log thousands of events in a 24-hour period to dozens of message queues. Many of these events are vital to the health and status of the system and business operations. Missing any number of critical events such as a job failure or impending DASD failure could cost your company thousands of dollars in lost revenue as a result of computing downtime. Messenger has the tools necessary to prevent server downtime.
MessengerPlus Features
Monitors• Filters messages and events from any number of messages queues, including QSYSOPR and QSYSMSG by a wide variety
of selection criteria: - Message ID, Type and/or Severity. - Job name or generic job name. - User or generic user name. - Program or generic program name. - Accounting code or generic accounting code. - Message text and substitution variables. - Time periods.
• Jobs that do not start or complete by specific time.
• Messages from job logs and IBM i procedures.
• Program error messages from specified interactive jobs.
• System History Log (QHST).
• Work with Active Jobs (WRKACTJOB): - Jobs consuming excessive CPU resources. - Jobs exceeding a specified length of time. - Jobs that must be running during specified times. - Jobs with poor response times. - Jobs with too low priority. - Jobs with a specific status, that is, LCKW or MSGW. - Jobs with specific functions, that is, IBM i procedure abends; a user is running a specific program.
• Total CPU usage (WRKSYSSTS).
• Job queues (WRKJOBQ).
• System Audit Journal (QAUDJRN).
• Output queues (WRKOUTQ).
• Lines, controllers, devices, servers (WRKCFGSTS).
• TCP/IP device status: routers, firewalls, Netware servers, and so on.
• Disk monitoring to detect common DASD storage problems: - Remaining disk space. - Growth over a period of hours, days, weeks or months.
Create your own monitors.
You can also define additional parameters for each monitor:
• The scheduled time periods when to monitor for the event.
• How the events for that monitor should appear on the screen (color, if the workstation alarm should be sounded).
Introduction
4
Messenger V8R1M0
• The text of the event. For example, you may want to reword the system message “Checksum suspended on disk DSK01” to “Disk DSK01 failed, contact Operations Manager immediately!”
• The actions you want performed. You can perform actions to page, email, run commands, send replies, escalate to other users, and so on.
• The severity of the event. For messages, you can override the severity to a higher or lower value.
• The allowed replies, which can be secured by an authorization list.
• The actions to perform (if any) when a specific reply is issued.
• If the event is informational or inquiry. For messages, you can override an informational message to an inquiry message.
EventsAs Messenger detects events that occur as a result of the monitoring you have configured, events are created, which can be configured to trigger actions, and managed by operations staff using the Messenger Event Console™.
Event ConsoleThe Messenger Event Console shows you the list of messages and events that have been logged as a result of the monitoring you have defined. From an Event Console you can:
• Link directly from an event to the event monitor where you can customize the setup of the event.
• View all monitored messages and events from all systems and partitions on a single screen.
• Automatically refresh to show new events.
• Define colors and alarm important messages and events by severity, job, and user.
• Easily exclude unwanted messages from further monitoring.
• Show the history of actions that were performed.
• Easily run frequently used actions on events using user-defined actions, similar to PDM (the Programming Development Manager).
• Easily change the filtering of monitored messages and events, excluding or modifying monitoring and actions as you go.
• Subset events by system, event type, severity, and so on.
• Copy or move events to other centers and systems.
ActionsPerform unlimited actions for an event. With Action Scripts, Action Escalation, and Action Scheduling, you define how errors are responded to.
• Pre-configured to automatically page on critical events.
• Send pager and email messages.
• Send messages to users or workstations.
• Send IFS attachments, system printouts, and joblogs with email messages.
• Run CL commands.
• Reply to inquiry messages.
• Send events to other servers (SNMP or Syslog).
• Escalate unanswered messages.
5
Introduction
Paging and NotificationGetting messages is reliable and easy. By far the industry’s easiest-to-use and most flexible paging system, Messenger takes care of all the complexities of communication for you.
Pager/Notification Device Types Supported:• Alphanumeric pagers and cell phones, using a wide variety of industry standard protocols (TAP,GSM/SMS, SNPP, SkyTel
2-way, and so on).
• Numeric pagers
• Workstations
• Telephones
• Syslog servers
• SNMP network traps
• Other wireless devices
Network Paging/Dispatching:• Give all your Windows TCP/IP users graphical paging capabilities without the need for emulation software, modems,
and so on.
• Graphical interface for end user paging/messaging.
• Send messages from your existing applications.
• Send messages to any pager or email address.
Message Formatting:• Message text
• Job and User name that sent the message
• Date and time stamping
• Message lengths up to 999 characters
• Custom
Additional Paging Features:• Message dispatching with user-friendly “Send a Pager Message” graphical interface or green screen pop-up window,
save and recall frequently used messages and automatic cleanup.
• Shares with your Service Director/ESC/Fax line and modem without having to manually switch modem between synchronous and asynchronous.
• Modem pooling.
• Group paging.
• Pager escalation, schedules and “on-call” paging.
• Pager security.
• Sends pages during restricted states.
• Easily integrates with job schedulers, high availability solutions, exit-point security solutions, and other applications.
• Automatic cleanup.
Paging Companies:• Popular paging company details are pre-configured.
• Supports multiple paging companies.
6
Messenger V8R1M0
Escalation• Automatically escalates messages to the next pager on list.
• Event escalation.
• User adjustable intervals and time periods.
Reply ManagementEvery message waiting for a reply results in lost minutes of processing, causing operational crises. Not only is it important to answer messages quickly but correctly. Answering a message with the wrong reply could cause an even larger crises. MessengerConsole and MessengerPlus can:
• Automate procedures for reoccurring events.
• Answer routine messages automatically and quickly.
• Reply by pager.
• Reply by email.
• Assist you in answering non-routine messages.
SchedulingWant to monitor or send a page only during nights and weekends? You can create schedules to define time periods that you can attach to monitors and actions. When a schedule is attached to an event monitor, the events are monitored only during the scheduled time. When attached to actions, the actions are performed only during the scheduled time. This allows you to perform different actions during different time periods.
• Pre-configured schedules for unattended, attended, weekdays, week nights, and weekends.
• Create your own schedules.
• Apply schedules to monitoring, actions, and pagers.
Reporting• Event History
• Action History
• Paging History
• Monitor Configuration
• QHST Analyzer
• Usage tracking: Easily view the number of times a specific message or type of message has occurred over a period of time.
Security• Prevent unauthorized users from changing pager and monitoring setups.
• Non-administrators cannot see other users’ messages.
• Users cannot see pager numbers or mailbox passwords.
QHST AnalyzerContains a utility to analyze your system history logs (QHST) and display the number of occurrences of messages. This utility is useful in assisting you in determining the QHST messages you want to monitor.
You can use the severity column to identify the number and types of messages you would receive at different severity levels. The Message ID column can be used to identify specific messages to include or exclude from monitoring.
7
Introduction
UsagesNeed to know how many times a program has crashed this year? MessengerConsole and MessengerPlus maintain a counter for each filter you define, allowing you to easily view the number of times a specific message or type of message has occurred over a period of time. The following statistics can be reported:
• The number of times an event has occurred by type (power outage, job failure, job queue limits, and so on) over a period a time.
• The date and time of the last time the event occurred.
• The number of unanswered events by type of event, such as printer messages, batch errors, and so on.
• The number of events waiting to be sent to a remote system.
• The number of times an action was performed in response to an event.
Pre-Configured Monitors
Bytware leverages its extensive expertise in systems monitoring to pre-configure MessengerConsole and MessengerPlus to automatically detect many types of common events and critical messages. These events can be easily changed, removed, or added to the monitoring list.
• Automatically detects many types of common events and critical messages.
• QSYSOPR, QSYSMSG and QHST pre-configured for easy set up.
• Pre-configured schedules for unattended, attended, weekdays, week nights, and weekends.
• Pre-configured to automatically page on critical events.
• Pre-configured to escalate unanswered message.
Pre-configured monitors include:• RPG, CL and COBOL batch error messages.
• Backups not completed by a specified time.
• Jobs that end abnormally.
• Tape related messages.
• Printer related messages.
• Disk and hardware related messages.
• Communications error messages.
• Security related messages.
• Power failures and Uninterruptible Power Supply (UPS) related messages.
• Interactive jobs waiting on a message.
• Interactive jobs using over 30% CPU. This event monitor detects programs that may be “looping”.
• Batch jobs running for 2 or more hours.
• Batch jobs using over 50% CPU.
• Interactive response times over 30 seconds.
• Interactive run priority under 20.
• Batch run priority under 30.
• Job queue QBATCH with 10 or more jobs.
8
Messenger V8R1M0
• Output queue PRT01 with 20 or more spooled files.
• All messages severity 80 and above, excluding printer messages.
• Over 20 different types of security and system-related events from the IBM i audit journal.
Event Consolidation with MessengerConsole
Do you want to console and manage messages and events from multiple systems and partitions? If so, you will need MessengerConsole, the easy-to-implement consoling solution designed to centrally manage events occurring on local and remote IBM i systems, as well as across multiple partitions. From a single point of control, MessengerConsole helps you streamline systems monitoring, message management, paging/email notification, and statistical reporting.
MessengerConsole combines pre-configured and user-configurable monitoring of important events, with event consolidation, distributed set-up and alternate consoles to deliver the best 24/7 protection for all your IBM i systems.
The Alternate ConsoleMessengerConsole can redirect events to a backup or alternate console. The alternate console can become the primary console at any time in the event of a failure or planned outage of the primary console.
Monitor DistributionMessengerConsole’s unique monitor distribution feature allows you to create and maintain all monitoring setups from a single central system. Any changes made from the central system are distributed to remote systems and partitions—automatically. Once you have defined the events you want to monitor, you can distribute those definitions to remote systems without the need to manually recreate those setups for each and every system. This provides the following benefits:
• Reduces the time and effort to setup and maintain the remote monitoring software.
• Ensures consistency of the monitoring policies implemented at each system.
• Secures distributed monitors at the remote sites from being changed by remote users.
EscalationEvents can be escalated to the central console after a specified period of time. This allows a remote operator time to respond to an event. For remote unattended systems, the events are escalated immediately.
ActionsMessengerConsole can perform actions on consoled events from the central system and at remote systems.
• Send pager and email messages (supporting all protocols, including 2-way pagers).
• Send messages to local and remote users, workstations, or systems.
• Run CL commands.
• Reply to inquiry messages.
• Send events to other users.
• Escalate unanswered message.
IntegrationMessengerConsole can be integrated with Enterprise Monitoring Solutions, providing a more complete monitoring solution for enterprise environments.
9
Installation
Chapter 2 - InstallationInstalling MessengerPlus is easy, and takes only a few minutes.
Requirements
• If you will be using dial-up for sending pager messages, an asynchronous modem is required. Most paging companies use a 300 or 1200bps modem. Many IBM synchronous modems can be configured to operate in asynchronous modes. You can use the internal modem or V.24 communications port for sending pager messages. You can display a list of resource names using the Work with Hardware Resources (WRKHDWRSC *CMN) command.
• Approximately 90MB of DASD to install.
• IBM i V5R4 or higher. Discuss requirements with a Bytware Technical Specialist for details on compatibility.
What the installation program does
The installation program:
• Creates the user profile MPLUSOWN for the purposes of owning the application objects.
• Creates the authorization list MPLUSAUTL for the purposes of securing the application objects.
• Restores the library MPLUS.
• Restores licensed program 0MP2000.
• Adds an autostart job entry to your controlling subsystem so MessengerPlus will startup after an IPL.
• Duplicates the following objects to QGPL:
Object name Object type DescriptionENDMP *CMD Ends MessengerPlus.MPLUS *MENU The MessengerPlus menu.MPLUS *CMD The command to display the MessengerPlus menu.SNDPGRMSG *PGM Send Pager Message API.SNDPGRMSG *CMD Send Pager Message command.STRMP *CMD Start MessengerPlus.
Installing Messenger
You will need a license key in order to use MessengerPlus. Please contact Bytware to obtain your key.
Installation
10
Messenger V8R1M0
Installing from the WebNew customers:Follow the link in the email you received. If you haven't received an email, contact Bytware for assistance.
Existing customers:1. Go to http://www.helpsystems.com/bytware and log in. Note: You may need to create a new username and password to
log into this site.
2. Click the Your Account link.
3. From Your Account page, add a serial number for one of your systems licensed for MessengerPlus or MessengerConsole. If you do not have a current support contract, please contact Bytware.
4. Click the Download link by MessengerPlus or MessengerConsole to access the download page.
To move Messenger from one system to anotherOn source system:
1. Run the command:
MPLUS/ENDMP
2. Run the command SAVLICPGM to save product 0MP2000 to a save file.
3. Run the command:
MPLUS/STRMP
4. Send the save file to the target system.
On target system:1. Run the command RSTLICPGM for product 0MP2000 to restore products from the save file.
2. Enter the license keys using the instructions provided by Bytware.
3. Run the command:
MPLUS/STRMP
11
MessengerPlus Menus
Chapter 3 - MessengerPlus MenusMain Menu
The Main Menu provides commonly used options and access to the submenus.
To access the MessengerPlus Menu, type the command MPLUS/MPLUS (or just MPLUS) at a command line and press Enter.
Option 1. Start MessengerPlusSelect this option to start the paging and monitoring subsystem and activate MessengerPlus.
Option 2. Work with EventsSelect this option to display and manage events that have been logged as a result of the monitoring you have defined.
Option 3. Send a Pager MessageSelect this option to send messages to pagers and email.
Option 4. Work with Pager MessagesSelect this option to view and change the status of pager messages.
Option 50. Setup MenuSelect this option to access the Setup Menu. The Setup Menu provides options for configuring the monitoring and paging features of the product.
Option 51. Support MenuSelect this option to access the Support Menu. The Support Menu provides utility type options for managing the status of the product.
Option 52. Reports MenuSelect this option to access the Reports Menu. The Reports Menu provides options for running various reports.
Option 53. Work with License InformationSelect this option to work with the license information, and to enter software license keys. License keys are obtained from Bytware or an Authorized Distributor. You must add license keys before the product features will function properly.
Setup Menu
The Setup menu provides options to configure the monitoring and paging features.
Option 1. Work with ModemsSelect this option to configure and view the status of your modems and the pager messages scheduled to be sent.
Option 2. Work with PagersSelect this option to manage pagers.
MessengerPlus Menus
12
Messenger V8R1M0
Option 3. Work with Paging CompaniesSelect this option to configure parameters necessary to route messages to text pagers.
Option 4. Work with System OptionsSelect this option to configure preferences such as default pager name, automatic cleanup frequency, logging level, etc.
Option 5. Work with MonitoringSelect this option to create, change, and manage monitoring of your system.
Option 6. Work with Event QueuesSelect this option to display, change, and create Event Queues.
Option 7. Work with AS/400 SystemsSelect this option to set up the remote IBM i systems in your network. Only available with MessengerConsole.
Option 9. Work with SchedulesSelect this option to manage schedules.
Option 10. Work with Command/Menu AuthoritiesSelect this option to configure which users can access the various functions within Messenger.
Support Menu
Option 1. Start MessengerPlusSelect this option to start the paging and monitoring subsystem and activate MessengerPlus.
Option 10. Configure Automatic Update Select this option to configure how and when to retrieve and apply updates to the product.
Option 11. Run automatic updateSelect this option to download product temporary fixes (PTFs).
Option 12. Display updates (PTFs) Select this option to display the program temporary fixes (PTFs) that are installed.
Option 13. Display output from last FTP downloadSelect this option to display the output from the last FTP download.
Option 14. Display Contact InformationSelect this option to display the support contact information for the product.
Option 30. End MessengerPlusSelect this option to end the MessengerPlus subsystem, paging and monitoring functions.
Option 31. Work with MessengerPlus ProcessesSelect this option to work with the processes or jobs that make up MessengerPlus.
Option 33. Simulate a System MessageSelect this option to send a program message to a message queue to simulate a particular condition.
13
MessengerPlus Menus
Option 34. Change Event QueueSelect this option to change an Event Queue method delivery to hold or break on your screen when new events arrive.
Reports Menu
Option 1. Pager Message History Report (by Pager)Select this option to print the messages sent to a single pager or all pagers.
Option 2. Pager Message History Report (by User)Select this option to print the messages sent by a specific user or all users.
Option 3. Pager Report Select this option to print a list of pagers that have been created.
Option 4. Events ReportsSelect this option to print a list of events that have been created as a result of the monitoring you have defined.
Option 5. Schedules ReportSelect this option to print a list of schedules that have been created.
Option 10. Analyze QHST Messages (ANZQHST)Select this option to display a summary of the messages in QHST between a date range.
14
Messenger V8R1M0
15
System Options
Chapter 4 - System OptionsThe System Options display allows you to specify system preferences.
To access the Systems Options choose option 4 from the Setup Menu.
Any changes made to System Options require a restart of the software before they will take effect.
Default pager nameSpecifies the name of the pager to receive messages from the various monitors. Although you can specify a different pager name for each monitor and event, the pager name specified here is used only when the pager name has not been overridden at a lower level. This can simplify setup. For example, by specifying the primary system administrator’s pager name here, you only need to override the pager name for events that do not go to the system administrator.
ICF logging levelThe level of ICF data logged. Logging the ICF data can assist with troubleshooting paging problems.
*DATA Only operations with data lengths greater than zero are logged.
*NONE No ICF data logging.
Paging run priorityThe run priority of the paging process. You should set this parameter lower than the priority of your regular batch jobs to avoid time out problems.
Message prefixSpecifies the character value to automatically insert in front of every alphanumeric pager message. This parameter is provided primarily for compatibility with a previous version. You can obtain more control over message formatting using the message format parameter when you set up your alpha pager.
Number of days to keep pager messagesSpecifies the number of days pager messages are retained. Messages older than the specified number of days are automatically deleted.
Number of days to keep eventsSpecifies the number of days events are retained in the Work with Events display. Events older than the specified number of days are automatically deleted.
Callback wait timeSpecifies the number of minutes MessengerPlus will wait between each pager message for an incoming call to the modem to stop the escalation of the pager message.
Using the Modem Details display, you can specify a callback number that is a code such as the modem’s phone number that will be automatically appended to escalating alpha and numeric messages. When you receive a message with this code at the end, you will know to call the modem if you want to stop escalation. Only escalating messages will show this code. Messages that will be sent only once, or the last page of an escalated message, will not show this code.
System Options
16
Messenger V8R1M0
The Callback Feature is intended for use with monitored messages that occur during unattended operations. If your paging volume is more than a few messages per hour and all or most of these messages will be escalated, do not use the Callback Feature since it will not be possible for MessengerPlus to determine which message to acknowledge. Instead, acknowledge the message manually, using the Work with Pager Messages display.
1- The callback feature is disabled. Incoming calls to the modem will not acknowledge pager messages.
0 MessengerPlus will check for a callback only while the modem is idle. If a call comes in, MessengerPlus will acknowledge the oldest escalating message. This method will not affect the volume of pager messages that can be sent per hour, but can acknowledge the wrong message when there are several escalating messages. Use this method if you page more than a few messages per hour.
Number-of-minutesMessengerPlus waits a specified number of minutes for a callback after sending an escalating pager message. This method is less likely to acknowledge the wrong message since no other messages will be sent while MessengerPlus is waiting for a callback. This method disables the streaming of alpha messages (only one message will be sent per connection). Use this method if your paging volume is very low, since a 15 minute callback time will only allow 4 escalating messages per hour to be sent (60 minutes / 15 minutes = 4 messages). When calculating the Callback wait time, you must consider the number of minutes it takes the paging company to deliver the message, plus the number of minutes you need to phone in. When you call the modem, you will hear a series of short beeps to indicate the message has been acknowledged. If you do not hear the beeps, then you have not called within the allotted time. Do not call back again, or you might acknowledge the wrong message.
17
Modem Configuration and Setup
Chapter 5 - Modem Configuration and SetupMessengerPlus manages the creation of the communications line for you. You do not have to create or vary lines, controller, and devices to send pager messages. MessengerPlus can dynamically share the modem with synchronous applications such as Service Director and ECS without having to manually configure the modem between uses. This chapter is a step-by-step explanation of configuring and testing your modem.
Working with Modems
The Work with Modems display shows you the status of the modems available to MessengerPlus. This display is typically used by a systems operator or administrator to manage the transmission of pager messages.
MessengerPlus can use several modems simultaneously using modem pooling. Pager messages are automatically routed to the modem with the lowest load. You can add as many modems as necessary to handle your paging volume. Each modem can process hundreds of pager messages per hour, depending on modem speed. If your paging volume is light to moderate, chances are you need only a single modem.
To access the Work with Modems display, choose option 1 from the Setup Menu.
If you want to: Do the following:Refresh the display to see the number of waiting messages and the status of the modems.
Press F5.
Add a modem to the modem pool. Press F6.Change a modem’s parameters. Type a 2 next to the modem you want to change, press Enter.Temporarily remove a modem from the modem pool. Type a 3 next to the modem name, press Enter. To return
the modem to the modem pool, type a 6 next to the modem name, press Enter. You cannot hold the *ROUTER queue.
Permanently remove a modem from the modem pool. Type a 4 next to the modem you want to remove, press Enter. You cannot delete the *ROUTER queue. Any messages that were allocated to the modem are reallocated back to the router.
Display the messages queued for a modem. Type a 5 next to the modem you want to display, press Enter.Display the messages waiting to be routed to a modem. Type a 5 next to *ROUTER, press Enter.Display the data the modem is sending and receiving. Type a 9 next to the modem you want to display, press Enter.
The Work with ICF display is shown. Start a modem so it can send messages. Type an 11 next to the modem you want to start, press Enter.Stop a modem from sending messages. Type a 12 next to the modem you want to stop, press Enter.See the job log of the modem process. Type a 13 next to the modem name, press Enter. On the Work
with Job display, choose option 10: Display job log.Test a modem. Type a 14 next to the modem you want to test, press Enter.
You cannot test a modem once it has been started.See the status of the IBM i communications line. Type a 15 next to the modem you want to display, press Enter.
Modem Configuration and Setup
18
Messenger V8R1M0
Modem Details
The Modem Details display allows you to change the modem parameters.
From the Work with Modems display, if you are adding a new modem, press F6. Type Line name, press Enter. If you are changing an existing modem, type a 2 next to the modem you want to change, press Enter.
Line nameSpecifies the name of the IBM i line description that MessengerPlus will create automatically.
Resource nameSpecifies the name of the Power Systems hardware resource to use. For a list of available resources, press F4. You must choose a resource name with a description of V.24 or V.24 port Enhanced (external modems) or Comm Port (internal modems).
DescriptionThe name or description of the modem. This field is required, but used for informational purposes only.
Modem typeThe type of modem connected to the V.24 port.
*ASYNCA standard Hayes compatible asynchronous modem.
*AUTOSYNC A modem capable of automatically switching between synchronous and asynchronous modes, such as the IBM Options 7852 400 and internal modem. The modem is automatically switched between asynchronous and synchronous operation as needed. The line is automatically varied off between pages to free resources needed to share with other applications. MessengerPlus will vary on the line as needed, switch the modem to asynchronous, send the pages, disconnect, switch the line to synchronous and vary the line off. If the modem is in use when needed by MessengerPlus, the line will be retried every 15 minutes.
*NULL A null modem, also know as a modem eliminator cable.
*V250A V.250 capable cellular modem.
Switched OptionsThe Switched Options display allows you to specify parameters for a dial-up connection.
Modem DSR settingThe Data-Set-Ready (DSR) setting of the modem. It is very important this parameter is set correctly.
*HIGH The modem keeps the DSR signal high/on at all times (preferred).
*NORMAL The modem turns on the DSR signal when a connection is made.
19
Modem Configuration and Setup
Initialization stringThe initialization string sent to the modem before the first pager message is sent. The initialization string contains commands necessary to prepare the modem for sending messages. If the resource will be shared, the initialization string will be sent each time before a batch of messages.
Reset stringThe reset string sent to the modem after a communications error occurs or the last pager message is sent. The reset string contains commands necessary to reset the modem to its original state. If the resource will be shared, the reset string will be sent each time after a batch of messages.
Wait for silence commandUsed for numeric paging only, specifies the command string to send to the modem to wait for silence after dialing the pager number. If your modem does not support wait for silence, such as the IBM 5853, 7855 and 7857 modems, type several commas where each comma represents a 2 second delay. For the Bocamodem, specify a single @ character.
Dialing prefixSpecifies the number the modem must dial to access an outside line. If a dialing prefix is used, you should end it with a comma to add a 2-second delay before dialing the phone number. For example: 9,
ShareSpecifies if MessengerPlus is sharing the modem with another asynchronous application, such as fax or remote access.
*NO The modem is not shared with another asynchronous application. MessengerPlus will keep the line allocated at all times.
*YES The modem is shared with another asynchronous application, such as remote access dial-in. MessengerPlus will vary the line off/on as needed to send pager messages. If the line cannot be varied on because it is in use, MessengerPlus will automatically retry as needed.
MessengerPlus runs the command specified in the second level text of the message description BYT0495 in message file MPBYT-MSG before accessing the line, allowing you to vary off the shared-with line or run a command to end an application using the shared-with line. When MessengerPlus has completed sending pager messages, the paging line is varied off and the command specified in the second level text of message description BYT0494 is run, allowing you to vary on the shared-with line or run a command to restart an application using the shared-with line. Example: CHGMSGD MSGID(BYT0494) MSGF(MPLUS/MPBYTMSG) SECLVL(‘VRYCFG SHAREDLINE *LIN STATUS(*ON)’)
Callback numberSpecifies the code that is automatically appended to escalating pager messages, providing the callback feature is enabled. For a discussion of the callback feature, see System Options later in this chapter.
Non-switched OptionsThe Non-switched Options display allows you to specify parameters for a direct connection to your paging company.
Paging CompanyThe name of the Paging Company created using the Work with Paging Companies displays the modem that it is dedicated to. Pager messages sent to this paging company will always use this modem. Pager messages sent to other paging companies will be sent using another modem in the modem pool.
20
Messenger V8R1M0
The *ROUTER QueueThe *ROUTER queue contains unsent and scheduled pager messages. The messages are automatically routed at the appropriate time to the modems in the modem pool with the lowest load. Before a message is routed to a modem, the following conditions must be met:
• The modem must not be held.
• MessengerPlus must be started.
• The *ROUTER status must be DLYW.
• The pager must not be held.
• The paging company must not be held.
• If a schedule is attached to the pager, the scheduled time periods must be current.
• If a previous transmission to a paging company ended in error, the paging company error retry interval period must have elapsed.
CountThe number of waiting and scheduled messages.
StatusEach modem runs as a separate batch process in the ZMPLUS subsystem. The Status (Sts) column shows you the status of the modem process:
STOP The modem has not been started or submitted. Messages allocated to a modem with this status will not be sent until the modem is started. Start the modem by typing an 11 next to the modem name, press Enter.
SBM The modem process has been submitted, but has not started yet. The job may be held, waiting on a job queue or ended abnormally. Press F5 to refresh the status.
DLYW The modem is ready to receive messages from the *ROUTER.
RUN The modem process or router is running and currently processing messages.
SND The modem is currently sending messages.
HLD The modem is held. The modem will not send messages until it is released using option 6.
EHLD The modem was held by MessengerPlus due to a modem error. More information about the modem error was sent to the QSYSOPR message queue. The modem will release automatically after 5 minutes. You can release the modem manually using option 6.
Working with ICFMessengerPlus maintains a detailed history log of the data sent to and received from the modem. The ICF detail display allows you to use this information to diagnose communication problems and also serves as verification that sent pager messages were received by your paging company. ICF data older than the number of days specified on the System Options display is automatically deleted.
You can view the ICF detail for a modem and for a pager message. When you view the ICF for a modem, you see all of the ICF data sent to and received from the modem for all pager messages. When you view the ICF for a pager message, you see the ICF data associated with a specific pager message only.
To view ICF for a modem, using the Work with Modems display, type a 9 next to the modem you want to display, press Enter. To view ICF for a pager message, using the Work with Pager Messages display, type a 9 next to the message you want to display, press Enter.
21
Modem Configuration and Setup
The data is displayed starting with the newest information at the top of the display.
If you want to: Do the following:Refresh the display to see the latest data sent to or received from the modem.
Press F5.
Print a listing of the ICF data. Press F19.Display the details of an entry. Type a 5 next to the entry you want to display, press Enter.
Date and TimeThe date and time the information was recorded.
OperationThe type of operation.
W Data is being sent to the modem.
R Data has been received from the modem.
Return codeThe APPC return code of the operation. Details of APPC return codes can be found in the AS/400 Advanced Program to Program Communications Programming Guide, Document Number SC41 3443 00. With some return codes, a message is also sent to the job log or the system operator message queue (QSYSOPR). You can refer to the message for additional information.
0000 Successful operation.
0016 On a successful input operation, some data containing a parity error and/or a stop bit error (framing) was received.
0310 No data available.
80XX Permanent system or file error (non-recoverable). The underlying communications support may have ended or failed.
8191 A permanent line or controller error occurred on an input or output operation, and the system operator attempted recovery in response to the error message. You can learn what type of line error occurred by checking the system operator’s message queue.
82AB The open or acquire operation was not successful because the device description for the remote location was not varied on.
82B3 The open or acquire operation was not successful because the device description is in use by another job.
22
Messenger V8R1M0
LengthThe length of the data sent or received.
DataThe ASCII data sent or received. Data that cannot be normally displayed is shown using the following special characters:
*M Carriage return (CR)
*L Line feed (LF)
*S Start-of-Text (STX)
*E End-of-Text (ETX)
IBM Internal Modem
1. From the Work with Modems display, type 2 to change PAGERQ, press Enter.
2. Change Resource name to the hardware resource used by your internal modem. You can press F4 for a list of resource names. If you are using the ECS modem, you can determine the resource name using the DSPLIND LIND(QESLINE) command.
3. If necessary, change the Description.
4. Change Modem Type to *AUTOSYNC.
5. Press Enter. The Switched Options display will appear.
6. Ensure the Modem DSR setting is set to *NORMAL and Share is *YES.
7. Ensure the Initialization string is ATTE0M1S0=0&D3&C0&S0
8. If you need to dial 9 or other prefix to access an outside line, type it in the Dialing prefix followed by a comma (i.e. 9,). If you do not need to dial 9 or other prefix, ensure Dialing prefix is blank.
9. Press Enter to return to the Work with Modems display.
10. Continue with the section Testing your Modem below
IBM 7852-400
Use the same procedure as the IBM Internal Modem
MultiTech MultiModem GPRS Wireless Modem
The MultiTech MultiModem GPRS Wireless Modem is used to send and receive GSM SMS text messages. This modem is also capable of sending and receiving text messages to non-GSM phones.
Requirements• MultiTech MultiModem GPRS wireless modem
• 9-25 pin adapter
• GSM SMS service and SIM card (obtained from your GSM service provider)
23
Modem Configuration and Setup
Connect the modem as pictured below. You must use a 9-to-25 pin adapter to connect between the MultiTech modem cable and the Power Systems V.24 cable. Insert the SIM card as instructed per the modem guide.
Setup1. From the Work with Modems display, type 2 to change PAGERQ, press Enter.
2. Change Modem Type to *V250.
3. Change Resource name to the hardware resource name attached to your modem. If you are using the ECS line, you can determine the resource name using the DSPLIND LIND(QESLINE) command. You can press F4 for a list of resource names. You must choose a resource name with a description of V.24 port or V.24 port enhanced.
4. Press Enter. The GSM Options display will appear.
5. Specify the following parameters, press Enter.
Parameter ValueMaximum message length 160DSR setting *NORMALInitialization string ATTE0M1S0=0Baud rate 1200Parity NData bits 8Stop bits 1Share *NO
6. Press Enter to return to the Work with Modems display.
7. Continue with the Testing your Modem later in this chapter.
24
Messenger V8R1M0
Other Modems
Use the table below to configure the following popular modems:
Modem Modem type DSR NotesBocamodem *ASYNC *HIGH US Robotics *ASYNC *HIGH Switch settings 3, 5, 8 DOWN
Testing your modem
1. From the Work with Modems display, type option 14 next to its name and press Enter. If the message ‘Paging queue initialized successfully’ is not displayed, verify that the Resource name and/or Modem DSR setting parameters are correct.
2. Once tested successfully, release the modem by typing 6 next to its name and pressing Enter.
3. Press Enter to return to the MessengerPlus Menu.
25
Paging Companies
Chapter 6 - Paging CompaniesMessengerPlus and MessengerConsole can send messages using any number of service providers at the same time. You may use PageNet pagers, while another office or business partner uses Verizon phones. When using a single modem, all messages for a service provider will be sent before connecting to another provider.
You can easily add your paging company in just a few simple steps. MessengerConsole and MessengerPlus are pre-configured to send messages to multiple service providers:
Working with Paging Companies
A Paging Company provides you with the appropriate service that transmits messages to your device. MessengerPlus sends alpha messages to your paging company using your modem. The paging company then converts it to a radio signal that is transmitted to your device. The Work with Paging Companies display is used to define the parameters needed to communicate with your service provider.
To access the Working with Paging Companies display, choose option 3 from the Setup Menu.
If you want to: Do the following:Add a new paging company. Press F6, type the name you want to assign to the paging
company, press Enter.Change a paging company’s parameters. Type a 2 next to the paging company you want to change,
press Enter.Hold transmissions to a paging company. Messages sent to a held paging company stay in a scheduled (SCH) status until the paging company is released.
Type an 3 next to the paging company you want to hold, press Enter.
Delete a paging company. Type a 4 next to the paging company you want to delete, press Enter. You cannot delete a paging company with pagers assigned.
Work with pager messages for a specific paging company. Type a 5 next to the paging company you want to work with, press Enter. The Work with Pager Messages display is shown.
Resume transmissions to a paging company previously held. Type a 6 next to the paging company you want to release, press Enter.
Work with pagers for a specific paging company. Type an 8 next to the paging company you want to work with, press Enter. The Work with Pagers display is shown.
Paging Company IDThe identifier of the paging company. You assign the identifier when the paging company is created. When creating a paging company, do not use dashes or hyphens in the name or identifier.
DescriptionThe description of the paging company. This field is for informational purposes only.
CountThe number of scheduled messages waiting to be sent.
Paging Companies
26
Messenger V8R1M0
StatusThe status of the paging company.
blank The paging company is released.
HLD The paging company is held.
EHLD The paging company was held by MessengerPlus due to errors. More information about the error was sent to message queue QSYSOPR. The paging company will release automatically after the number of minutes specified on the Paging Company Details: Additional Options display.
Paging Company Details
The Paging Company Details display allows you to define the parameters required to communicate with your paging company’s modem.
From the Work with Paging Companies display, if you are adding a new paging company, press F6. Type Paging Company ID, press Enter. If you are changing an existing paging company, type a 2 next to the paging company you want to change, press Enter.
Paging Company IDThe identifier of the paging company. You assign the identifier when the paging company is created.
DescriptionThe description of the paging company. This field is for informational purposes only.
ProtocolThe type of protocol the paging company uses.
*TAP The Telelocator Alphanumeric Protocol is used. Most U.S. alphanumeric pagers and PCS phones use this setting.
*SMTP For outgoing email.
*POP3 For incoming email.
*TMEX The SkyTel™ 2-Way protocol. MessengerPlus sends the message to SkyTel and periodically calls back to retrieve the reply. The time intervals used to call back are on a sliding scale: The first callback attempt is in 5 minutes, then 10 minutes; 15 minutes; 30 minutes; every 1 hour for 4 hours, then every 4 hours for 24 hours. Messages not answered within 24 hours are disregarded.
*ASCII A simple ASCII protocol is used. MessengerPlus converts the messages to ASCII and terminates with a carriage return and line feed. The *ASCII protocol can be used to interface with other consoling products, such as Boole & Babbage’s Command Post™.
*DT The German Deutsche Telekom protocol is used.
*MTN The South African MTN Cellnote network protocol is used.
*SNPP The SNPP (Simple Network Paging Protocol) is used. The server name, port number, User ID and Password (if required) is defined here.
*UCP The European Universal Computer Protocol is used.
*DNTC The Denmark Minitekst protocol is used.
*PTT The Netherlands PTT Telekom protocol is used.
*GSM The GSM protocol is used.
27
Paging Companies
*VODA The UK Vodaphone protocol is used.
*XTAP BellSouth 2-way protocol.
Maximum message lengthThe maximum message length allowed by the paging company.
Modem phone numberThe telephone number of the paging company’s modem. You should enter the number as if you were dialing the number from the phone line attached to your modem; do not enter the area code unless you would normally dial the area code. If you need to dial a 9 for an outside line, do not type the 9 before the number; the dialing prefix is specified on the Modem Details display. Before entering the number you should dial the number from your telephone and verify a modem answers.
Baud rateThe speed of the paging company’s modem. The default value of 300 is compatible with most paging companies.
Specifying a higher value than your paging company’s modem may result in frequent disconnects by the paging company.
ParityThe parity setting of the paging company’s modem. The default value of even is compatible with most paging companies.
Data bitsThe data bits setting of the paging company’s modem. The default value of 7 is compatible with most paging companies.
Stop bitsThe stop bits setting of the paging company’s modem. The default value of 1 is compatible with most paging companies.
Maximum message countThe maximum number of messages the paging company will accept in a single call.
PasswordThe password required (if any) by the paging company.
*NONE A password is not required.
Password The password required by the paging company.
Recovery Limits: CountThe number of times to try sending a pager message before delaying further pages. Pages will be delayed by the value specified for the retry interval. When the retry count has been reached, the Paging Company status will change to EHLD and a message is sent to QSYSOPR. The status will change back to normal after the retry interval has passed. If the retry count and retry interval has been exceeded 3 times, the page is cancelled.
Recovery Limits: IntervalThe number of minutes to wait before calling the paging company again after a communications error.
28
Messenger V8R1M0
29
Paging
Chapter 7 - PagingAbout Paging
Because an IBM i system can generate thousands of messages in a day, many vital to the health and status of the system and business operations, it is critical that your paging solutions be sophisticated enough to deliver only the important messages and not bog you down with repetitive paging, over and over and over again. MessengerConsole and MessengerPlus are the industry’s easiest and most flexible paging solutions for the IBM i. Whether it is automatically sending a vital message or end users are using our graphical ‘Send a Pager Message’ interface, getting a message from the IBM i is reliable and easy.
MessengerPlus supports the following pager types:
• Alphanumeric A type of pager this is capable of displaying text messages.
• Numeric A type of pager that is capable of displaying numeric characters only.
• Telephone A type of pager that sends a tonal message to a standard telephone.
• Escalation A type of pager used to escalate messages to other pagers after a specified time period.
• Group A type of pager used to broadcast a single message to multiple pagers at the same time.
• Schedule A type of pager that automatically selects the appropriate pagers (or lists) based on the current date and time.
• 2-Way A type of pager that is capable of 2-way messaging.
• Message Queue A user or workstation message queue.
• Email Sends a pager message to the specified SMTP Internet email address.
• SNMP Sends an SNMP network trap.
• SNPP Sends a text message to wireless devices using the SNPP protocol through the internet.
• GSM / SMS GSM/SMS devices.
• Syslog Sends a message to a Syslog server to integrate data from many different types of systems into a central repository.
Alphanumeric PagingIncludes extensive alphanumeric paging support (1-way and 2-way), using a variety of industry standard international protocols. Most cellular/mobile phones that have text paging capabilities can receive messages just like an alphanumeric pager.
Numeric PagingSupports all numeric pagers and can send up to 16 digits. For system messages, MessengerPlus sends a code that you can specify with the type of situation that has occurred. For example, 400-911 for a power outage, 400-999 for a program failure, and so on.
2-Way PagingWant to answer system messages directly from your 2-way pager? MessengerConsole and MessengerPlus can send 2-Way messages to certain types of 2-Way pagers. You can reply to the message directly from the pager by choosing one of the multiple choice responses or type a custom reply using the pager’s data entry capabilities. 2-Way pagers offer the following benefits:
• You do not have to sign on to the system to answer a message. Replying to a system message from the pager answers the message on the message queue.
• Users are immediately notified of your response. Your responses are sent back to the user’s message queue.
Paging
30
Messenger V8R1M0
• Choose to Acknowledge the message only, which does not answer the message but stops the message from automatically escalating to another pager.
• You can integrate 2-Way paging capabilities with your applications using the Send a Pager Message (SNDPGRMSG) and Retrieve Pager Message (RTVPGRMSG) APIs.
• Pager message delivery is guaranteed because the paging network will automatically hold your pager messages for up to 72 hours when your pager is out of a service area (depending on service provider).
Email SupportMessengerPlus and MessengerConsole can send email messages to your desktop or pager. You can attach IFS files, system printouts such as WRACTJOB and WRKSYSSTS, or joblogs to your email messages. You can control the formatting of the email messages and how they will appear on the target devices.
2-Way Email• Gives you the ability to answer system messages from any internet based email.
• Allows administrators to answer system and application messages from any of the fast growing array of wireless internet devices, such as Palm Pilots, cellular phones, and pagers.
• Answer system and application messages via desktop email clients such as Eudora, Netscape, Outlook, Notes, and so on., eliminating the necessity for access to a green screen.
• Allow applications to communicate with mobile workers.
SNPP SupportMessenger Plus and MessengerConsole can send messages via SNPP to wireless devices through the internet.
WorkstationsWhen MessengerPlus sends a page to a *MSGQ pager, the message appears in the specified message queue which can break on your workstation. Replies are automatically sent back to the sender. For system messages, answering the message on your workstation will automatically answer the system message on QSYSOPR. Answering a message automatically stops escalation of the message to other users.
Telephone PagingCan send a tonal message to a telephone. This method can be used to alert someone that does not have a pager, or leave tonal messages on voice mail systems.
Network Paging/Message DispatchingWhether you use our graphical WIN98/95/NT Send a Pager Message interface or green screen pop-up window, they both guide you through sending messages to any number of pagers or email device types, complete with prompting and online help text. Unlike competing products that use CL commands, MessengerConsole and MessengerPlus include CL command interface and user-friendly windows/GUI interface:
• Users can access the Send a Pager Message window from within any application.
• You can easily add the Send a Pager Message window to your application menus.
• Users can select one or many pagers from a list of authorized pagers.
• Eliminates retyping of frequently used messages by allowing you to save and resend messages again later.
• Unlike competing products, each user can send and check the status of their own messages. Users cannot see other users’ messages. Only system operators and administrators can see all messages.
• Eliminates the need for setting up each PC with emulation software, modems, and so on.
31
Paging
EscalationWant to automatically page another pager if a problem goes unresolved? MessengerConsole and MessengerPlus provides the most extensive escalation capabilities in the industry. When you send a message to an escalation list pager, MessengerConsole and MessengerPlus will automatically page the next pager on the list at specified intervals. You can specify the time it will wait between pages, allowing the flexibility to escalate more critical messages faster. The escalation process ends when the message is answered or after a specified number of tries.
Message FormattingMessengerConsole and MessengerPlus allow you to easily personalize the format of the messages sent to you by using any of the following special variables that you can mix and match in any order:
• Message text
• Message help text
• Job name that sent the message
• User name that sent the message
• Number of the job that sent the message
• Number of the pager message assigned by the system for your pager. The inclusion of this number tells you if any pager messages have been missed since your last message from the system.
• Date and time of the message
For example, the message “Load next volume on TAP01 (CG)” can be formatted to read: SYSA:QSYSOPR/BACKUP, Load next vol-ume on TAP01 (CG).
Extended message lengths. Allows you to send up to 999 characters, even if your pager allows less. Most alpha pagers have restrictions on the message length, usually 80 to 240 characters. The messages are numbered (1/3, 2/3, and 3/3) so that you are aware of the total number of messages making up the whole message.
Shares with Service Director/ECS/Fax line and modemIf you are using IBM i V4R1 or later and the IBM 7852-400 Options modem, MessengerConsole and MessengerPlus can automatically share the modem with synchronous applications such as Service Director, ECS and remote dial-in access, saving you valuable V.24 ports. You do not have to manually switch the modem between uses.
Modem PoolingIf your paging volume is very high, you will appreciate the ability to utilize multiple modems simultaneously to deliver thousands of pager messages per hour.
Group PagersWant to send a single message to multiple pagers at once? If so, you’ll like the ability to create Group pagers. When you send a pager message to a group pager, all of the pagers in the group will receive the same message.
Pager SchedulesWould you like to specify which pagers receive system messages during certain time periods? You can create a Schedule Pager that automatically pages the appropriate pagers based on the current time of day. When you send a message to a Schedule Pager MessengerConsole and MessengerPlus will determine the pager names to receive the message based on the time periods you have specified. You can also attach a schedule to a pager, or groups of pagers, that will determine the time periods the pager is eligible to receive messages. Messages sent to pagers outside scheduled times are held and then delivered at the appropriate time.
If you specify a severity code with your Pager Schedule, MessengerConsole and MessengerPlus will send the message to the pager only if the severity of the message is above the level you specified. You can use this to have your low severity messages delivered during a certain time, such as early morning, while delivering your high severity messages immediately.
32
Messenger V8R1M0
Pager SecurityNeed to prevent users from accessing unauthorized pagers? The pager security features allows you to attach authorization lists to pagers so you can prevent unauthorized users from viewing, changing or sending messages to unauthorized pagers. Non-administrators cannot see pager numbers.
Add Paging to your ProgramsWant to page from your application? The Send Pager Message (SNDPGRMSG) API can be easily called from your RPG and CL applications. You can send 1000 characters to one or many pagers without having to deal with the complexity of communications protocols. You can even designate your message to be sent at a later time. Using pager lists and schedules, your messages can escalate to other pagers automatically and page on-call staff.
Working with Pagers
A Pager refers to traditional pagers of various types as well as many virtual pager types, such as email addresses, telephones, groups, schedules, and so on. The Work with Pagers display is used to create and manage the pagers that will receive messages from MessengerPlus or MessengerConsole.
To access the Work with Pagers display, choose option 2 from the Setup Menu.
If you want to: Do the following:Create a new pager. Press F6, type the name you want to assign to the pager, press Enter.Change a pager’s parameters. Type a 2 next to the pager you want to change, press Enter.Hold transmissions to a pager. Type a 3 next to the pager you want to hold, press Enter.Delete a pager. Type a 4 next to the pager you want to delete, press Enter. All pager
messages and history associated with the pager will be deleted.Work with pager messages sent to a specific pager. Type a 5 next to the pager you want to work with, press Enter.Resume transmissions to a pager previously held. Type a 6 next to the pager you want to release, press Enter.Change the time periods messages are delivered to a pager. Messages sent outside the time periods are held until the appropriate time.
Type a 7 next to the pager name, press Enter. For more information, see the section Pager Schedule Details later in this chapter.
Copy a pager to a new one. Type an 8 next to the pager you want to copy, press Enter. Type the new pager name, press Enter.
Change the authorities to a pager. Type a 9 next to the pager you want to change, press Enter. For more information, see the section Pager Authorities later in this chapter.
Display a partial list of pagers to help locate pagers that use a specific paging company, contain a certain description, and so on.
Press F17. Type your choices, press Enter.
33
Paging
Pager Details
The Pager Details display allows you to change your pager’s parameters, such as the pager type. When you press Enter, you will be prompted for additional information depending on the type of pager you selected.
From the Work with Pagers display, if you are creating a new pager, press F6. Type a pager name, press Enter. If you are changing an existing pager, type a 2 next to the pager you want to change, press Enter.
Pager nameThe name assigned to the pager, such as the person’s name or user ID.
DescriptionThe description of the pager, such as the persons name or department.
Pager typeThe type of pager.
*ALPHA An alphanumeric pager (or other wireless device capable of receiving a text message).
*NUMERIC A numeric pager.
*PHONE A special type of pager that sends a tonal message to a standard telephone.
*ESC A list of pagers that is used to escalate messages to other pagers after a specified time period.
*GRP A group of pagers used to broadcast a single message to multiple pagers at the same time.
*SCHED Automatically selects the appropriate pagers based on the current date and time.
*SNMP Generates an SNMP trap
*2WAY A SkyTel™ 2-Way pager
*MSGQ A user or workstation message queue.
*EMAIL An Internet email address.
*SNPP Messages will be sent as text messages.
*SMS Messages will be sent as SMS messages (requires MultiTech GPRS modem).
*SYSLOG Messages will be sent to a syslog server.
Public authorityThe public authority to the pager.
*CHANGE The public can change the pager using the Work with Pagers display.
*USE The public can send messages to the pager but cannot change it.
*EXCLUDE The public cannot display, change or send messages to the pager.
Authorization-list-name The authority to the pager is determined by the specified authorization list. For more information about authorization lists, see the WRKAUTL command.
34
Messenger V8R1M0
Alpha Pager OptionsThe Alpha Pager Options display allows you to change the parameters for an alphanumeric pager.
Paging Company IDThe name of the paging company created for the pager. You can select from a list of paging companies by pressing F4.
Pager PIN The PIN number of the pager. The PIN number is supplied by the paging company. PIN numbers are typically the ten (10) digit pager phone number. At the option of the paging company, it may be an arbitrary identifier. Do not use punctuation characters in the Pager PIN.
Preferred message lengthThe maximum preferred length of your pager messages. If the pager message sent to your pager exceeds the maximum allowed length supported by your paging company, MessengerPlus will break your messages into several smaller messages, each of the length supported by your pager. MessengerPlus will also insert numbering before each part (1/3, 2/3, 3/3) so you know the message is continued with another message.
Message patternSpecifies the format of the messages sent to the pager. You can type literal text in addition to specifying any of the following variables that MessengerPlus will replace with actual data when sending your page. You can specify the variables in any combination and order.
&M The message text.
&J The job name that sent the message.
&U The user name that sent the message.
&N The number of the job that sent the message.
&C The number of the Pager Message assigned by the system for your pager. By including this number with your pages, you will be able to tell if any pages have been missed since your last message.
&D The date and time of the message.
&S The system name that generated the message.
Example:Message pattern: From &s:&u/&j &mResult: From SYSA:QSYSOPR/BACKUP Load next volume on TAP01 (C G)
E-mail OptionsThe E-mail Options display allows you to change the parameters for an email pager. This panel is displayed when the pager type is *EMAIL. Messages sent to this type of pager are sent as an email message to your SMTP email server.
E-mail addressThe Internet SMTP email address where the message will be sent.
SubjectSpecifies the subject line for the email messages. You can type literal text in addition to specifying any of the following variables that MessengerPlus will replace with actual data when sending the message. You can specify the variables in any combination and order.
&M The message text.
&J The job name that sent the message.
35
Paging
&U The user name that sent the message.
&N The number of the job that sent the message.
&C The number of the Pager Message assigned by the system for your pager. By including this number with your pages, you will be able to tell if any pages have been missed since your last message.
&D The date and time of the message.
&S The system name that generated the message.
Example:Subject: From &s:&u/&j &mResult: From SYSA:QSYSOPR/BACKUP Load next volume on TAP01 (C G)
Service ProviderThe identifier of the Paging Company that sends messages to your mail server, most likely named *SMTP. To verify press F4 for a list.
Numeric Pager OptionsThe Numeric Pager Options display allows you to change the parameters for a numeric pager.
Pager numberThe phone number of the pager. You should enter the number as if you were dialing the number from the phone line attached to your modem. Do not enter the area code unless you would normally dial the area code. If you need to dial a 9 for an outside line, do not type the 9 before the number; the dialing prefix is specified on the Modem Details display. Before entering the number you should dial the number from your telephone and verify a pager answers.
If your pager uses an 800 number and a PIN, type the 1-800 number, followed by 4 comma’s, the PIN number and the #.
Paging Company IDDo not specify a Paging Company ID unless you want to transmit the numeric messages using the alpha protocol. Not all paging companies support this method. If you want to use the alpha method, specify a Paging Company ID and enter the pager’s PIN or ID as the Pager Number, without dashes (“-”).
Phone Pager OptionsThe Phone Pager Options display allows you to change the parameters for a phone pager.
Phone numberThe phone number of the telephone. You should enter the number as if you were dialing the number from the phone line attached to your modem. Do not enter the area code unless you would normally dial the area code. If you need to dial a 9 for an outside line, do not type the 9 before the number; the dialing prefix is specified on the Modem Details display.
Number of secondsThe number of seconds MessengerPlus will ring the telephone. You could specify more time to ring a phone with an answering machine, for example.
Message Queue OptionsThe Message Queue Options display allows you to change the parameters for a Message Queue pager. This panel is displayed when the pager type is *MSGQ. When MessengerPlus sends a page to a *MSGQ pager, the message appears in the specified message queue. If the message was sent due to monitoring of a system message, the user can answer the message and MessengerPlus will automatically answer the associated message in the system message queue and stop escalation of the message.
36
Messenger V8R1M0
Message QueueThe name of the message queue where MessengerPlus will send the pager message.
Message patternSpecifies the format of the messages sent to the message queue. You can type literal text in addition to specifying any of the following variables that MessengerPlus will replace with actual data when sending the message. You can specify the variables in any combination and order.
&M The message text.&J The job name that sent the message.&U The user name that sent the message.&N The number of the job that sent the message.&C The number of the Pager Message assigned by the system for your pager. By including this number with your
pages, you will be able to tell if any pages have been missed since your last message.&D The date and time of the message.&S The system name that generated the message.
Example:Message pattern: From &s:&u/&j &mResult: From SYSA:QSYSOPR/BACKUP Load next volume on TAP01 (C G)
SNMP OptionsThe SNMP Options display allows you to change the parameters for an SNMP pager. This panel is displayed when the pager type is *SNMP. Messages sent to this type of pager are sent as an SNMP network trap that can be monitored using an SNMP manager.
Messenger sends multiple object identifiers (OID) with each trap. In addition, a MIB (Management Information Base) document is available that can be loaded into your trap manager. The MIB defines the following OIDs:
1.3.6.1.4.1.5187.1.2.4.0 Event key to be used for replies.
1.3.6.1.4.1.5187.1.2.5.0 Event date
1.3.6.1.4.1.5187.1.2.6.0 Event time
1.3.6.1.4.1.5187.1.2.7.0 Event status
1.3.6.1.4.1.5187.1.2.8.0 Event type
1.3.6.1.4.1.5187.1.2.9.0 Event text
1.3.6.1.4.1.5187.1.2.10.0 System
1.3.6.1.4.1.5187.1.2.11.0 MSGQ name
1.3.6.1.4.1.5187.1.2.12.0 MSGQ library name
1.3.6.1.4.1.5187.1.2.13.0 Severity
1.3.6.1.4.1.5187.1.2.14.0 Message type
1.3.6.1.4.1.5187.1.2.15.0 Message ID
1.3.6.1.4.1.5187.1.2.16.0 Message file
1.3.6.1.4.1.5187.1.2.17.0 Message file library
1.3.6.1.4.1.5187.1.2.18.0 Message data
1.3.6.1.4.1.5187.1.2.20.0 Program
1.3.6.1.4.1.5187.1.2.21.0 Job
37
Paging
1.3.6.1.4.1.5187.1.2.22.0 User
1.3.6.1.4.1.5187.1.2.23.0 Job number
To obtain the MIB file, please contact Bytware Support. After importing the MIB file into your SNMP trap manager, you can configure any of the above OIDs to appear on the enterprise console. You might choose to see the system name, date & time, message severity and/or message text.
SMS OptionsThe SMS Options display allows you to change the parameters for a SMS pager. This panel is displayed when the pager type is *SMS. Messages sent to this type of pager are sent as SMS text messages (requires *V250/GSM modem).
Mobile numberSpecifies the mobile number for the SMS device in international format, no punctuation.
Preferred message lengthThe maximum preferred length of your pager messages. If the pager message sent to your pager exceeds the maximum allowed length supported by your paging company, MessengerPlus will break your messages into several smaller messages, each of the length supported by your pager.
MessengerPlus will also insert numbering before each part (1/3, 2/3, 3/3) so you know the message is continued with another message.
Message patternSpecifies the format of the messages sent to the trap manager. You can type literal text in addition to specifying any of the following variables that MessengerPlus will replace with actual data when sending the message. You can specify the variables in any combination and order.
&M The message text.
&J The job name that sent the message.
&U The user name that sent the message.
&N The number of the job that sent the message.
&C The number of the Pager Message assigned by the system for your pager. By including this number with your pages, you will be able to tell if any pages have been missed since your last message.
&D The date and time of the message.
&S The system name that generated the message.
Example:Message pattern: From &s:&u/&j &mResult: From SYSA:QSYSOPR/BACKUP Load next volume on TAP01 (C G)
SNPP OptionsThe SNPP Options display allows you to change the parameters for a SNPP pager. This panel is displayed when the pager type is *SNPP. Messages sent to this type of pager are sent as SMS text messages (requires *SNPP Paging Company).
Paging Company Specifies the *SNPP Paging Company to use.
38
Messenger V8R1M0
Pager numberThe number of the wireless device to receive the message. Typically, this is the 10-digit phone number. Do not use punctuation.
Subject patternSpecifies the format of the subject line sent to the pager. You can type literal text in addition to specifying any of the following variables that MessengerPlus will replace with actual data when sending the message. You can specify the variables in any combination and order. The body of the message will include the message text.
&M The message text.
&J The job name that sent the message.
&U The user name that sent the message.
&N The number of the job that sent the message.
&C The number of the Pager Message assigned by the system for your pager. By including this number with your pages, you will be able to tell if any pages have been missed since your last message.
&D The date and time of the message.
&S The system name that generated the message.
Example:Message pattern: From &s:&u/&j &mResult: From SYSA:QSYSOPR/BACKUP Load next volume on TAP01 (C G)
SYSLOG Options
The SYSLOG Options display allows you to change the parameters for a SYSLOG pager. This panel is displayed when the pager type is *SYSLOG. Messages sent to this type of pager are sent to a syslog server to integrate data from multiple systems into a central repository.
Server NameSpecifies the name or IP address of the Syslog server.
Message pattern Specifies the format of the messages sent to the trap manager. You can type literal text in addition to specifying any of the following variables that MessengerPlus will replace with actual data when sending the message. You can specify the variables in any combination and order.
&M The message text.
&J The job name that sent the message.
&U The user name that sent the message.
&N The number of the job that sent the message.
&C The number of the Pager Message assigned by the system for your pager. By including this number with your pages, you will be able to tell if any pages have been missed since your last message.
&D The date and time of the message.
&S The system name that generated the message.
39
Paging
Pager List Options
A pager list is a list of pagers, which can include any combination of other pagers. You can specify a pager list name anywhere you can specify a pager name. The following display is used to define both *ESC and *GRP pager types. An *ESC pager list will escalate messages to the pagers on the list one a time at the defined intervals. At any time during the escalation period, if the message is acknowledge or answered, then the escalation process is ended and the remaining pagers will not be paged. A *GRP pager list will page all persons on the list simultaneously, for as many times and at the intervals specified. When messages are sent to a *GRP list, MessengerPlus and MessengerConsole will create a message for each pager in the list, and they all act independently of each other.
Sequence numberThe Sequence number specifies the order the pagers will be paged. Pagers with the lowest sequence numbers are paged first. You can change the sequence number by typing over the old value with the new one, or you can press F13 to renumber the list starting with 10 and increment by 10.
CountThe number of times to page the specified pager.
MinutesThe number of minutes between pages.
Pager nameThe name of the pager that will be paged.
Pager Schedule Options
You can create a pager schedule by typing a 7 next to a pager or pager list name and pressing Enter. A pager schedule allows you to specify the time periods messages are sent to the pager. Messages sent outside the time period are automatically delivered at the appropriate time.
You can create a schedule pager by pressing F6 and specifying *SCHED as the pager type. A pager schedule allows you to specify the pager names to receive messages during specific time periods. Messages sent to a schedule pager are sent only to the pagers specified for the current time period.
Use a schedule pager when you want MessengerPlus to automatically select the appropriate pagers based on a specific time period, such as first shift, second shift, and so on.
If you want to: Do the following:Add pagers to the list. Press F6, type the time periods and pagers you want to add,
press Enter.Remove pagers from the list. Space over the time periods and pagers you want to remove,
press Enter.
Include/ExcludeSpecifies if the schedule time period is included or excluded.
Start date/day typeThe starting date or day type.
40
Messenger V8R1M0
date The starting date of the schedule entry (MMDDYY).
day type The starting day type of the schedule entry. Valid day types are *SUN, *MON, *TUE, *WED, *THU, *FRI and *SAT.
End date/day typeThe ending date or day type. If you do not specify an ending date, the starting date is used.
date The ending date of the schedule entry.
day type The ending day type of the schedule entry. Valid day types are *SUN, *MON, *TUE, *WED, *THU, *FRI and *SAT.
Start/end timeThe starting and ending time period of each day during the schedule entry period (in 24 hour format). For schedule entries that span several days, such as Monday through Friday, the starting time specifies the starting time of each day (as opposed to the starting time of the first day only).
SeverityFor monitored messages only, the minimum severity level of the message required by the pager schedule entry.
Pager name (shown for *SCHED pager types only)The name of the pager that will receive the pager message during the scheduled time period.
Example: Setting up a pager schedule to automatically escalate pages between the following shifts:
Shift 1: Monday through Friday, 6am - 3pm, Operators 1, 2 and 3.
Shift 2: Monday through Friday, 3pm - 11pm, Operators 4, 5 and 6.
Shift 3: Monday through Friday, 11pm - 6am, Operators 7, 8 and 9.
Shift 4: Saturday and Sunday, 24hrs, Operations Manager only.
1. Using the Work with Pagers display, create the pagers OPER1 through OPER6.
2. Create a pager list LIST1 of type *ESC. Add pagers OPER1, OPER2 and OPER3 to the list, specifying the number of times to page and interval between pages for each entry.
3. Repeat step 2 for list LIST2, specifying pagers OPER4, OPER5 and OPER6.
4. Repeat step 2 for list LIST3, specifying pagers OPER7, OPER8 and OPER9.
5. Create pager SCHED of type *SCHED, specifying the time periods and pager names as shown above.
6. Messages sent to the pager name SCHED will page the appropriate groups based on the time period.
Pager Authorities
The Work with Pager Authorities display is used to specify the authority users have to specific pagers. MessengerPlus tests authority using the user’s ID, then the user’s group profile name, then *PUBLIC. For example, if SUE has group profile CFO, MessengerPlus will check SUE’s authority, and if not found, checks CFO’s authority, and if still not found, checks *PUBLIC.
From the Work with Pagers display, type a 9 next to the pager you want to change, press Enter. Press F6 to add new users.
41
Paging
User nameSpecifies the name of the user you want to grant or revoke authority. You can specify a specific user profile name, a group profile name, *PUBLIC or an authorization list name.
AuthoritySpecifies the level of authority granted to the user.
*CHANGE The user is allowed to change the pager.
*USE The user is allowed to send messages to the pager but cannot change.
*EXCLUDE The user cannot display or send message to the pager.
Authorization-list-nameThe authority to the pager is determined by the specified authorization list. For more information about authorization lists, see the WRKAUTL command.
If you want to: Do the following:Add users to the list of authorities. Press F6, type the user names and authority, press Enter.Remove users from the list of authorities. Space over the user names and authorities you want to
remove, press Enter.
Alpha Pager SetupThis setup is used for an alphanumeric pager or any wireless device capable of displaying text messages.
1. If necessary, setup a Paging Company using the steps described in Chapter 6.
2. Using the Work with Pagers display, press F6 to create a new pager. Type a name for your pager (for instance, your user ID or first name), press Enter.
3. Type Description (such as your name) and change the Pager type to *ALPHA, press Enter.
4. Type the Paging Company ID you created earlier (or press F4 and choose from the list).
5. Type the Pager PIN. Typically the pager PIN is the 10 digits of the pager number (area code + number). It is a common mistake to enter a 1 before a 10 digit number. A 1 is not needed. The Pager PIN is not a telephone number that is dialed (the number dialed is specified during the paging company setup). Think of the Pager PIN as a user ID on the paging company’s system.
6. Press Enter to return to the Work with Pagers display.
7. Continue with the section Sending a Pager Message.
Numeric Pager Setup1. Using the Work with Pagers display, press F6 to create a new pager. Type a name for your pager (for instance, your user ID
or first name), press Enter.
2. Type Description (such as your name) and change the Pager type to *NUMERIC, press Enter.
3. Type the Pager number, without the 1-area code unless it is a long distance call. You may use punctuation characters in the number to improve readability. If you need to dial a 9 for an outside line, do not type the 9 (it is specified on the modem setup).
4. Press Enter to return to the Work with Pagers display
5. Continue with the section Sending a Pager Message
42
Messenger V8R1M0
Phone Pager SetupThis setup is used for a standard telephone. Pager messages sent to a phone pager can be heard through the handset as a series of DTMF tones . For wireless devices that receive text messages (pagers, cellular phones, PDAs, and so on) refer to Alpha Paging Setup or Email Pager Setup.
1. Using the Work with Pagers display, press F6 to create a new pager. Type a name for your pager (for instance, your user ID or first name), press Enter.
2. Type Description (such as your name) and change the Pager type to *PHONE, press Enter.
3. Type the Phone number, without the 1-area code unless it is a long distance call. You may use punctuation characters in the number to improve readability. If you need to dial a 9 for an outside line, do not type the 9, (it is specified on the modem setup).
4. Press Enter to return to the Work with Pagers display.
5. Continue with the section Sending a Pager Message.
Email Pager SetupRequirements
1. The name or IP address of the SMTP mail server. You can obtain this information from your mail administrator.
2. To reply to messages via email, you need:
a. A POP3 mailbox to temporarily store the email responses. Have your mail administrator create a new POP3 mailbox for you. If an existing POP3 mailbox is used, please be aware that it will be cleared every time Messenger checks it. You could use a POP3 account on your corporate mail server or any “free” Internet POP3 email account.
b. The IP address of the POP3 server. If you use the name, it must exist in the Host table on your system.
c. The account name and password of the POP3 mailbox that the mail administrator created.
SMTP Server Setup1. From the Setup Menu, choose option 3: Work with Paging Companies.
2. If a *SMTP entry exists, type a 2 to change it and press Enter. If *SMTP does not exist, create it by pressing F6, type *SMTP and press Enter.
3. If necessary, specify a description such as (SMTP outgoing email) and change Protocol to *SMTP, press Enter.
4. Type the name or IP address of your SMTP mail server. To use a port other than the industry-standard port 25, type the server name or IP address, a colon, then the port number (ex: smtp.bytware.com:2525).
5. If you will be replying to email messages, type the POP3 ‘From email address’. If you will not be replying, type any valid email address or: [email protected].
6. Set the Max Attachments size by specifying a value in megabytes. If an attachment will cause the entire email message to exceed that size, the attachment will be dropped and a note will be added to the end of the email message notifying you the attachment exceeded the size limit.
Attachments will be received as .txt files. Job logs that exceed 500KB will be delivered in a zip file.
7. Press Enter to return to the ‘Work with Paging Companies’ display. If necessary, release *SMTP by typing a 6 next to it and pressing Enter.
43
Paging
POP3 Server SetupThis section is required if you want to reply to messages via email. If you will be sending email only, continue with the next section.
1. From the Setup Menu, choose option 3: Work with Paging Companies.
2. If a *POP3 entry exists, type a 2 to change it and press Enter. If *POP3 does not exist, create it by pressing F6, type *POP3 and press Enter.
3. Type the name or IP address of your POP3 mail server. To use a port other than the industry-standard port 110, type the server name or IP address, a colon, then the port number (ex: pop3.bytware.com:995).
4. Type the account/mailbox name and password.
5. Press Enter to return to the ‘Work with Paging Companies’ display. If necessary, release *POP3 by typing a 6 next to it and pressing Enter.
Email Pager Setup1. Using the Work with Pagers display, press F6 to create a new pager. For instance, your user ID or first name), press Enter.
2. Type the following, press Enter.
a. Description: Type a description (such as your name)
b. Pager type: *EMAIL.
3. Type the following, press Enter.
a. E-mail address: The email address of the client, cell phone or pager.
b. Subject: Type the desired subject. Press Help for information about various options available.
c. Allow reply: Yes or No. Selecting No will remove the message number (###) from the subject line of the email. This pager will not be able to reply to system messages.
d. Service provider: Type *SMTP, or the name of the SMTP service provider created in the previous section.
Email Pager RepliesYou can reply to email pager messages sent by Messenger to answer messages on your system.
1. Set your E-mail Pager Options Allow reply to Yes.
2. Send a new message to your Messenger email account with the message number and reply in the Subject line.
Example: You receive this email page and want to reply with an ‘R’:
From: [email protected] To: [email protected] Subject: (973) From: SYSNAME - USER/JOB QPADEV000L USER 231919 Verify Message text . . . . . . . . : Maximum number of
records reached for file &1. (C R NOMAX 1-999999)
Send this as your reply:
From: [email protected] To: [email protected] Subject: 973 R
44
Messenger V8R1M0
SNPP Pager SetupRequirementsThe name or IP address, username and password of the SNPP server. You can obtain this information from your SNPP server administrator.
SNPP Server Setup1. From the Setup Menu, choose option 3: Work with Paging Companies.
2. Create an entry for *SNPP by pressing F6, type *SNPP and press Enter.
3. Specify a description such as (SNPP outgoing messages) and change Protocol to *SNPP, press Enter.
4. Type the name or IP address of your SNPP mail server.
5. Type the User ID for your SNPP account
6. Type the Password (if required) for your SNPP account
7. Press Enter to return to the ‘Work with Paging Companies’ display. If necessary, release *SNPP by typing a 6 next to it and pressing Enter.
SNPP Pager Setup1. Using the Work with Pagers display, press F6 to create a new pager. For instance, your user ID or first name), press Enter.
2. Type the following, press Enter.
a. Description: Type a description (such as your name)
b. Pager type: *SNPP.
3. Type the following, press Enter.
Paging Company: Type *SNPP, or the name of the *SNPP Paging company you created
Pager number: The 10-digit phone number of the wireless device.
Subject: Type the desired subject. Press Help for information about various options available.
Skytel 2-way Pager SetupOverview The following overview explains how a Skytel 2-way message is processed.
Step Approximate time (from start of mes-sage) HH:MM:SS
Action Message status
1 0:00:00 A message is entered (either manually or from a system mes-sage).
SCH
2 0:00:01 0:02:00
MessengerPlus dials and transmits the message to Skytel SND
3 0:02:00 Skytel transmits the message to the pager. SNT4 0:02:15
0:03:00User replies to message.
5 0:03:30 Skytel receives reply from the pager and stores for retrieval.
45
Paging
Step Approximate time (from start of mes-sage) HH:MM:SS
Action Message status
6 0:05:00 MessengerPlus calls Skytel to retrieve the reply. 7 0:05:30 MessengerPlus replies to user or system message. ACK
If, in step 5, the reply has not been received by Skytel from the pager, MessengerPlus will continue to call Skytel at the following increasing time intervals:
Attempt* Time interval before next call
1 - 3 Every 5 minutes
4 - 7 Every 15 minutes
8 - 11 Every 1 hour
12 - 24 Every 4 hours
25 Never
* If the message is acknowledged1 prior to MessengerPlus retrieving the reply, no further attempts will be tried.
Skytel 2-way Pager Setup1. From the Setup Menu, choose option 3: Work with Paging Companies.
2. Release SKYTEL2 by typing a 6 next to it and pressing Enter.
3. Press F3 to return to the Setup Menu.
4. Choose option 2: Work with Pagers.
5. Press F6. Type a name for your pager (for instance, your user ID or first name), press Enter.
6. Type Description (such as your name) and change the Pager type to *2WAY, press Enter.
7. Type SKYTEL2 for the Paging Company ID (or press F4 and choose from the list).
8. Type your pager’s PIN for the Pager PIN. You can find the pager’s PIN on the underside of the pager box.
9. Press Enter to return to the Work with Pagers display.
10. Press F3 to return to the Setup Menu. Press F3 to return to the Main Menu.
11. Select option 3: Send Pager Message. Type your pager name, press Enter. Type your message and press F10 to send message.
12. Select option 4: Work with Pager Messages. Press F5 periodically and verify your message status changes to SND, then SNT (this should take 1 to 2 minutes).
13. When the message appears on your pager, enter a reply (refer to your pager manual on how to reply to a message).
14. Wait at least 5 minutes. This is how long it takes MessengerPlus to retrieve the reply.
15. Using the Work with Pager Messages display, verify the status of your messages changes to ACK (periodically press F5 to refresh the status if necessary).
16. If your message queue is in *BREAK mode, your reply will break on your screen. You can also type an 8 (History) next to your pager message to see your reply.
1 Messages can be acknowledged by using the Work with Pager Messages display and typing a 1 next to the message. Additionally, if the message is a system inquiry message, you can simply answer the message on the message queue.
46
Messenger V8R1M0
Sending Pager Messages
Sending Pager Messages is easier than ever when using the Attention key, which lets you send pager messages at any time, from any program! MessengerPlus can guide you through choosing pagers and entering a pager message, using the prompted mode of the SNDPGRMSG command. If you want to send pager messages from within a CL program or typed directly at a command line, see the following section.
Manual Method
If you have configured the Attention key, press Attn. Otherwise, from the command line, type SNDPGRMSG and press Enter.
Type the pager name and press Enter or press F4 to choose from a list. If you press F4, a list of authorized pagers is shown and you can choose one or more of them by typing a 1 in the Opt column beside the pagers you want. If you have several screens of pagers to choose from, you can reposition the list by entering the starting pager name in the “Position to” field. When you have finished making your choices, press Enter.
If you selected one or more numeric pagers, the “Numeric message” field is shown. If you selected one or more alpha pagers, the “Alpha pager message” field is shown.
1. To schedule a page to be sent at a later time, enter the desired date and time in the “Date/Time to send” field.
2. To specify the message is to be sent several times, enter the number of times and the minutes between pages.
3. To save your message so it can be reused again without retyping it, press F4.
4. To retrieve a saved message, position the cursor to the Alpha pager message field, press F4.
5. To expand the “Alpha pager message” field to its full length, press F11.
6. To display or change the pagers that you have chosen, press F16.
7. When you are ready to send your message, press F10.
Using the Menu1. If necessary, go to the MessengerPlus menu by typing MPLUS at a command line and pressing Enter.
2. Ensure MessengerPlus is started by choosing option 1 to Start MessengerPlus.
3. Choose option 3: Send a Pager Message.
4. Type your Pager name, press Enter, or press F4 and choose from the list.
5. Type your message and press F10 (your screen may vary slightly depending upon the type of pager selected).
6. From the MessengerPlus Menu, select option 4: Work with Pager Messages. Press F5 periodically and verify your message status changes to SND, then SNT (this should take 1 to 2 minutes). If the status does not change to SNT, or if your pager does not receive the message, see Chapter 8 for Troubleshooting notes.
Using the SNDPGRMSG CL commandTo send pager messages using CL commands from a command line or from within your CL programs, type the SNDPGRMSG command and press F4.
Type the pager names, press Enter. If you want to enter more than two pagers, type a plus “+” (without quotes) in the “+ for more values” field, press Enter. Type the Pager Names, press Enter.
You can press F10 from the SNDPGRMSG command to display the Additional Parameters and specify an IFS stream file path name (ie /home/user1/file.txt) that Messenger will send with the email. Please note the name should not contain quotes and
47
Paging
must start with a slash ‘/’ character. Be sure the user profile MPLUSOWN has *X access to all directories in the path name and *RX authority to the file. Type your choices, press Enter.
You cannot enter more than 512 characters for the “Alpha message” field on this screen (this is an IBM i restriction). However, you can access the full field length in CL programs.
**********************Beginning of data******************************0001.00 PGM0002.000003.00 MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(ERROR))0004.000005.00 SAVLIB LIB(*NONSYS) DEV(TAP01)0006.00 SNDPGRMSG TOPGR(OPERATIONS) MSG(‘#NONSYS backup complete.”)0007.00 RETURN0008.000009.00 ERROR: SNDPGRMSG TOPGR(OPERATIONS) MSG(‘Error occurred on +0010.00 *NONSYS backup.’)0011.000012.00 ENDPGM**********************End of data************************************
Example:In this example, a backup program uses the SAVLIB command. If any errors occur, the program branches to ERROR, which sends the pager message ‘Backups failed’ to the OPERATIONS pager.
Working with Pager Messages
MessengerPlus has two Work with Pager Messages displays: one that shows only the messages you have sent and another that shows all messages from all users. When you press F11 from the Send a Pager Message Window, you see only your messages. This display is used by users to check the status of their messages. When you use option 4: Work with Pager Messages or the WRKPGRMSG command, you will see all messages from all users. This display is typically used by system operators and administrators.
To work with your pager messages only, type the following command at a command line:
MPLUS
Select Option 3. Then, press F11.
Or,
SNDPGRMSG
Then, press F11
Or, if you have configured the Attention key, press Attn, wait for the Send Pager Message window, press F11.
To work with all pager messages, type the following command at a command line:
MPLUS
Select option 4.
Or,
WRKPGRMSG
48
Messenger V8R1M0
If you want to: Do the following:Refresh the display to see the status of the messages. Press F5.Change the parameters of a message. Type a 2 next to the message you want to change, press Enter.Permanently remove a message. Type a 4 next to the message you want to remove, press Enter.Stop escalation of a message. Type a 1 next to the message you want to acknowledge, press Enter.
The message status changes to ACK.Resend a message. Type a 7 next to the message you want to resend, press Enter. The
message status changes to SCH.Display the communications detail about the message. Type a 9 next to the message you want to display, press Enter. For
more information, see Working with ICF. This option is useful to diagnose communications problems and also provides as a receipt from the paging company, which can be printed and retained for sensitive information.
Display the dates, times and results of transmissions of a pager message.
Type an 8 next to the message, press Enter.
Hold a message from sending. Type an 3 next to the messages you want to hold, press Enter.Sort the messages by status. Press F11. Pressing F11 again will return the sort order to date/time.Display a subset of messages for a particular pager, and so on.
Press F17. Type your choices, press Enter. The list will be redisplayed showing you the entries that match the specified criteria.
Print a list of pager messages. Press F19. You will be prompted for selection criteria and printing options, type your choices and press Enter.
Working with Pager Message History
MessengerPlus maintains a detailed history of paging and email activity. Users can print reports of their pager messages showing the date and time entered, the message text, which pagers the message was sent to, and dates and times of those transmissions. Filtering options allow you to restrict the report to specific pagers, date ranges, message text, and so on. You can view or print a list of messages that meet a specified criteria:
• The messages that were sent.
• Date and time.
• Job name.
• Users that were notified and when.
• Paging company responses.
• Replies from 2-way pagers.
• Communications detail (ICF) allowing you to diagnose any paging problems.
• The number of messages waiting to be sent.
• The number of messages waiting to be sent for a Paging Company.
• The number of messages waiting to be sent for a pager.
To access the Work with Pager Message History display, use the Work with Pager Messages display and choose option 8 next to a pager message, press Enter.
49
Paging
Troubleshooting
Pager messages stay in SCH status1. Using the Work with Modems display, verify *ROUTER status is DLYW. If necessary, return to the Main Menu and choose
option 1: Start MessengerPlus.
2. Verify PAGERQ status is not HLD. If necessary, release PAGERQ by typing a 6 next to its name and pressing Enter.
3. Verify PAGERQ status is not STOP. If necessary, start PAGERQ by typing an 11 next to its name and pressing Enter twice.
4. Using the Work with Pagers display, verify the pager is not held.
5. Verify the pager does not have a schedule restricting its send times.
6. If using an alpha pager, use the Work with Paging Companies display to verify the paging company is not held.
Pager messages go to SND status, then back to SCH1. Use the Work with Modems display to verify dialing prefix is correct.
2. If using an alpha pager, use the Work with Paging Companies display to verify paging company’s modem phone number: Dial the phone number from your telephone and verify a modem answers.
3. Listen to the modem as it dials to diagnose any dialing problems.
4. Use the Work with ICF display to verify there are no protocol problems. Following is an example of a transmission. Your results may vary slightly. The time column represents the relative elapsed time between steps. The sequence of events is listed in reverse chronological order to coincide with the data on your display.
Time Data Description00:00:50 *M*LOK*M*L The modem hangs up.00:00:46 ATH*M MessengerPlus instructs the modem to hang up.00:00:42 +++ MessengerPlus instructs the modem to hang up.00:00:40 *M*A*M The paging company responds with *A if the message is
accepted. If this line contains *1, the message was rejected by the paging company, probably due to an invalid pager number. If this line contains a *N, the message is being rejected (could be caused by unprintable characters in the message text, or message too long, or possibly line noise).
00:00:38 *S1234567*Mthis is a test*M[ep*M MessengerPlus sends the pager message. Verify the number between the *S and *M is your alpha pager number, without any punctuation characters.
00:00:37 Processing please wait ¢p*A*M *A instructs MessengerPlus to send the page.00:00:36 *4PG1*M MessengerPlus logs onto the paging company.00:00:35 ID=*M If ID= is not shown, the baud rate may be incorrect. Power the
modem off then on again.00:00:32 *M MessengerPlus sends *M every 2 seconds until ID= is received.00:00:30 *M*LCONNECT*M*L The paging company’s modem answers. If this line contains
BUSY, the line is busy. If it contains NO CARRIER, there was no answer or the modem speed is incorrect. If it contains NO DIAL TONE, there is no phone line connected to the modem.
50
Messenger V8R1M0
Time Data Description00:00:00 ATD9,555-1212*M MessengerPlus dials the paging company.
Recoverable error messages on QSYSOPR.1. Listen to the modem as it dials to diagnose any dialing problems.
2. Use the Work with ICF display to verify there are no protocol problems.
Alpha pager messages go to SNT status but are not received on pager.Call your paging company, verify alpha PIN number.
Email pager messages have incorrect time stamp.The time stamped on email pages is determined by the Coordinated Universal Time Offset system value. To correct the time, use WRKSYSVAL QUTCOFFSET. For the offset value, specify the number in hours your current system time differs from Coordinated Universal Time by subtracting from local time to obtain the Greenwich Mean Time. For example, in the Pacific Time Zone (US & Canada) during Pacific Standard Time, the Greenwich Mean Time is -07:00 and during Pacific Daylight Time, the Greenwich Mean Time is -08:00, therefore the QUTCOFFSET system value should be set to -0:700 or -08:00 depending on the time of year.
Numeric pager messages go to SNT status but are truncated or not received.Listen to the modem as it dials to diagnose any dialing or timing problems:
1. The modem should go off-hook, and you will hear a dial tone. If you do not, use the Work with Modems display to ensure the queue status is SND. You should also ensure the phone line is properly connected to the modem.
2. You should hear the dialing of the phone number.
3. You should hear ringing and the pager will answer. If the pager does not answer, Use the Work with Modems display to verify dialing prefix.
4. You should hear a short beep or a recording, such as “Please enter your telephone number after the beep”.
5. You should hear one or more short beeps.
6. You should hear the DTMF tones of the numeric message being sent.
7. The line is hung up.
If step 6 is completed before step 5, use the Work with Modems display to change the modem wait for silence command. Insert additional commas to further delay step 6 (each comma is 2 seconds).
If step 7 is completed before step 6, use the Work with Modems display to change the modem wait for silence command. Re-move commas to further delay step 7 (each comma is 2 seconds).
If pages sent using Send A Pager Message display are received, but monitored messages are not, verify there is a numeric mes-sage specified on the Action Details display.
Pager messages appear garbled.Contact your paging company .
Pager messages are taking a long time to reach your pager.Use the Work with Pager Message History display to verify the time displayed on the line containing a *A is close to the time you received the page. If not, call your paging company (or email administrator if using email to send messages).
51
Paging
Pager Message Error Codes
Code Description Solution21 No carrier. The Paging Company did
not answer. Could be a wrong modem number.
Use the Work with Paging Companies display to verify modem number and baud rate. Use the Work with Modems display to verify dialing prefix. Listen to the modem dial to diagnose any dialing problems.
22 Line is busy. Check phone line. Use the Work with Modems display to verify dialing prefix. Listen to the modem dial to diagnose any dialing problems.
24 Timeout. The paging company did not respond with the expected information within the allotted time.
Use the Work with Paging Companies display to verify protocol and baud rate.
31 Pager message rejected by the paging company.
Use the Work with Pagers display to verify pager number. Verify pager number does not contain area code or dashes.
Troubleshooting SMTP Distributions
Problem SolutionsUsing the Work with Pager Messages display to locate your message and verify the message status is SNT.
If the message status is SNT, the message was accepted successfully by the mail server. If you don’t receive the message, ensure the email address is correct or contact your mail administrator.
If the status is ERR, view the history by typing an 8 next to the message and press Enter. Review the error messages with your mail administrator and correct as needed.
If the status is SCH, continue with the following section.Using the Work with Paging Companies display, verify the *SMTP service provider status is blank.
If the status is blank, the message may be currently queued for sending. Force the message to send immediately by choosing Setup Menu option 1: Work with Modems and pressing F10. Then check the status of your message again.
If the status is HLD, release it by typing a 6 next to *SMTP and pressing Enter.
If the status is EHLD, view the job log by choosing Setup Menu option 1: Work with Modems, typing a 13 next to *ROUTER and pressing Enter. Choose option 10, then press F10 and F18. Review any error messages with your mail administrator and take corrective actions as needed.
Release the *SMTP service provider by typing a 6 next to it and pressing Enter.
TELNET to the remote system using port 25 and verify a 220 response code is returned.
Verify the *SMTP host name or IP address is correct.Using the Work with Modems display, verify the *ROUTER status is DLYW.
If the status is DLYW, this is the normal status. If the count is 0, there are no messages waiting to send. You can press F10 to force the sending of any queued messages.
If the status is STOP, restart MessengerPlus using the commands MPLUS/ENDMP and MPLUS/STRMP.
Review the job log by typing a 13 next to *ROUTER and pressing Enter. Choose option 10, then press F10 and F18. Review any error messages with your mail administrator and take corrective actions as needed.
52
Messenger V8R1M0
Troubleshooting POP3 replies
Problem SolutionsUsing the Work with Pager Messages display to locate your message and verify the message status is SNT.
If the message is SCH, see the previous section “Troubleshooting SMTP Distributions”
If the status is ACK, the reply was successfully received. You can view the reply by typing an 8 (History) next to the message and pressing Enter.
If the status is SNT and the message was not received:
1. Use Setup menu option 2: Work with Pagers to change the pager and verify the email address is correct.
2. Contact the mail administrator of the SMTP server to verify the message is being routed to the Internet.
Using the Work with Paging Companies display, verify the *POP3 service provider status is blank.
If the status is blank, this is the normal status. The message may be currently queued for sending. Force the message to send immediately by choosing Setup Menu option 1: Work with Modems and pressing F10. Then check the status of your message again.
If the status is HLD, release it by typing a 6 next to it and pressing Enter.
If the status is EHLD, view the job log by choosing Setup Menu option 1: Work with Modems, typing a 13 next to *ROUTER and pressing Enter. Press F10 and F18. Review any error messages with your mail administrator and take corrective actions as needed.
Release the *POP3 service provider by typing a 6 next to it and pressing Enter.
TELNET to the remote system using port 110 and verify a +OK response is returned.
Verify that the pager the reply is coming from has the “Allow reply” parameter set to Y=Yes.
Verify the *POP3 host name or IP address is correct.The reply received is incorrect. Ensure the reply was at the top of the email (as opposed to the bottom) and that it was
the only thing in the body.
53
Paging
Troubleshooting SNPP Distributions
Problem SolutionsUsing the Work with Pager Messages display to locate your message and verify the message status is SNT.
If the message status is SNT, the message was accepted successfully by the SNPP server.
If you don’t receive the message, ensure the pager number is correct or contact your SNPP server administrator.
If the status is ERR, view the history by typing an 8 next to the message and press Enter. Review the error messages with your SNPP server administrator and correct as needed.
If the status is SCH, continue with the following section.Using the Work with Paging Companies display, verify the *SNPP service provider status is blank.
If the status is blank, the message may be currently queued for sending. Force the message to send immediately by choosing Setup Menu option 1: Work with Modems and pressing F10. Then check the status of your message again.
If the status is HLD, release it by typing a 6 next to *SNPP and pressing Enter.
If the status is EHLD, view the job log by choosing Setup Menu option 1: Work with Modems, typing a 13 next to *ROUTER and pressing Enter. Choose option 10, then press F10 and F18. Review any error messages with your SNPP server administrator and take corrective actions as needed.
Release the *SNPP service provider by typing a 6 next to it and pressing Enter.
TELNET to the remote system using port 444 and verify a 220 response code is returned.
Verify the *SNPP server name or IP address is correct.Using the Work with Modems display, verify the *ROUTER status is DLYW.
If the status is DLYW, this is the normal status. If the count is 0, there are no messages waiting to send. You can press F10 to force the sending of any queued messages.
If the status is STOP, restart MessengerPlus using the commands MPLUS/ENDMP and MPLUS/STRMP.
Review the job log by typing a 13 next to *ROUTER and pressing Enter. Choose option 10, then press F10 and F18.
Review any error messages with your mail administrator and take corrective actions as needed.
Restricted State Paging
Want to know when your SAVLIB *NONSYS needs another tape? MessengerConsole and MessengerPlus can monitor for inquiry messages issued during a restricted state, such as a SAVSYS asking for another tape, and send a pager message to one or more pagers while your system remains in a restricted state. Unlike competing products that only page during restricted state by requiring you to embed a send pager message command into the restricted state function, MessengerConsole and MessengerPlus have restricted state monitoring features ready to detect errors and page you.
54
Messenger V8R1M0
Before sending restricted state pages for the first time, you must add a communications entry to the controlling subsystem. This is only necessary if you are sending pages over the modem and only needs to be performed once. To determine your controlling subsystem name, use the DSPSYSVAL QCTLSBSD command. Example:
ADDCMNE SBSD(QSYS/QCTL) DEV(PAGERQ) DFTUSR(*SYS)
Note: If you have changed the name of your line from the default name PAGERQ, replace PAGERQ with the name of your line. To determine the names of your paging lines, use the Work with Modems display.
To monitor for inquiry messages and redirect to one or more pagers, add the STRRSMP (Start Restricted State Monitoring and Paging) command to your restricted state program or type the command at a command line before issuing restricted state commands, such as SAVSYS, and so on.
Example:
**********************Beginning of data******************************001.00 PGM002.00003.00 DCL VAR(&MSG) TYPE(*CHAR) LEN(132) 004.00 MONMSG MSGID(CPF0000) EXEC(GOTO CMDLBL(ERROR))005.00006.00 ADDLIBLE LIB(MPLUS) 007.00 STRRSMP TOPGR(OPERATIONS) MSGQ(QSYSOPR) /* Start monitoring on QSYSOPR */008.00 009.00 SAVLIB LIB(*NONSYS) DEV(TAP01)010.00 CHGMSGQ MSGQ(QSYSOPR) PGM(*DSPMSG) /* Stop Monitoring on QSYSOPR */011.00012.00 RETURN013.00014.00015.00 ERROR:015.01016.00 RCVMSG MSGTYPE(*EXCP) MSG(&MSG) /* Get message */017.00 SNDPGRMSG TOPGR(OPERATIONS) MSG(&MSG) /* Submit page */018.00 CALL MPRCRX3 PARM(X) /* Send pages NOW */019.00020.00: ENDPGM**********************End of data******************************
If you are using an alphanumeric pager, setup your pager as numeric also. Create a *GRP pager list with your numeric pager first, then your alphanumeric pager. On the STRRSMP command, specify the *GRP pager name. MessengerPlus will send a numeric and an alpha page to your pager. This will cover any situations where the paging company’s modem may not be answering. If you are using an email pager, TCP/IP must be configured when the operating system is in restricted state. This is only possible with IBM i V5R2 or greater.
55
Monitoring
Chapter 8 - MonitoringIntroduction
MessengerPlus and MessengerConsole allow you to create Monitors to detect many types of critical events occurring on your IBM i server. The following types of monitors are provided:
CPU percentage CPU monitors allow you to detect when the total CPU % of the system exceeds a specified threshold (WRKSYSSTS). This monitor gives you the ability to handle systems with multiple processors.
Disk Disk monitors allow you to detect DASD events, such as low disk space remaining, or disk usage growth exceeding a specified threshold.
Job log Joblog monitors allow you to detect messages occurring in interactive jobs.
Job run Job run monitors allow you to detect whenever specific jobs are not running.
Job Job monitors allow you to detect conditions about specific active jobs, such as their status, or CPU usage.
Job queue Job queue monitors allow you to detect when a job queue is greater than, less than, or equal to a specified number of jobs and/or the status of the job queue (WRKJOBQ).
Journal Journal monitors allow you to detect events that appear in the system audit journal (QAUDJRN).
Line Line monitors allow you to detect the changes in status of Power Systems lines, controllers and devices (WRKCFGSTS).
Message Message monitors allow you to trap message events that appear in IBM i message queues (WRKMSGQ).
Output queue Output queue monitors allow you to detect when an output queue is greater than, less than, or equal to a specified number of spooled files (WRKOUTQ).
Ping Ping monitors allow you to detect changes of a network IP device status. You can also detect changes in specific ports, such as FTP, Telnet, SMTP and POP3.
Working with Monitors
The Work with Monitors display allows you to define the monitoring parameters for your system. To access the Work with Moni-tors display, choose option 5 from the Setup menu. Using this display, you can:
• Create new monitors
• Change the parameters of an existing monitor, such as the scheduled time periods, authorities, and so on.
• Delete monitors from your system
• Start and stop monitoring for particular events
• Access the Work with Event Monitors display, which allows you to manage the individual events for a monitor, such as power failures, jobs ending abnormally, and so on.
• Display the number of events logged by each monitor
• Access the Work with Events display, which allows you to work with the events logged by the monitor
Monitoring
56
Messenger V8R1M0
• Display and reset the last time a monitor has logged an event and the number of events that have been logged since the last time it was reset
• Print reports of the monitor’s configurations and details
If you want to: Do the following:Refresh the display to see the latest status of the monitors and the number of events.
Press F5.
Restart all monitors without having to wait for the refresh interval.
Press F10.
Create a new monitor. Press F6.Change the parameters of a monitor. Type a 2 next to the monitor you want to change, press Enter. Temporarily suspend a monitor until it is later released. Type a 3 next to the monitors you want to hold, press Enter.
The status changes to HLD. Permanently remove a monitor. Type a 4 next to the monitor you want to remove, press Enter.Display the events logged by the monitor. Type a 5 next to the monitor you want to display, press Enter.
The Work with Events display is shown. Release a monitor previously held. Type a 6 next to the monitor you want to release, press Enter.Print the details about a monitor. Type a 7 next to the monitor you want to print, press Enter.Copy a monitor to a new one. Type an 8 next to the monitor you want to copy, press Enter.
Type the new monitor name, press Enter.Work with the Event Monitors for a monitor. Type a 9 next to the monitor you want to work with, press
Enter. The Work with Event Monitors display is shown.
MonitorThe name of the monitor.
TypeThe type of the monitor.
*CFGD Work with Configuration Status (WRKCFGSTS) monitor.
*CPU CPU percentage
*DISK Disk monitoring
*MSG Message monitor.
*JOBPFR Work with Active Jobs (WRKACTJOB) monitor.
*JOBQ Work with Job Queues (WRKJOBQ) monitor.
*JOBRUN Job Run
*JRN Journal monitor.
*OUTQ Work with Output Queues (WRKOUTQ) monitor.
*RMT Remote event monitor.
*TCP TCP/IP (PING) monitor.
DescriptionThe description of the monitor. This field is for informational purposes only.
57
Monitoring
CountThe number of unacknowledged events logged by the monitor.
StsThe status of the monitor.
RDY The monitor process is running, but currently servicing another monitor.
RUN The monitor is running.
STOP The monitor is stopped.
HLD The monitor is held.
SCH The monitor is scheduled to run at a later time.
DLYW The monitor is waiting the specified time period before checking for new events.
EHLD The monitor had a critical error which prevented further monitoring. The object being monitored may no longer exist. For more information, use 2=Change next to the monitor, press F15 to view the messages in the job log. Once the error has been corrected, release the monitor.
Monitor Details
The Monitor Details display allows you to change the parameters of a monitor.
From the Work with Monitors display, if you are adding a new monitor, press F6. Type a name for the monitor, press Enter. If you are changing an existing monitor, type a 2 next to the monitor you want to change, press Enter.
If you want to: Do the following:Display or change the schedule time periods the monitor will monitor for events.
Press F11. For more information about schedules, see Working with Schedules.
Display or reset the usage data. The usage data shows you the last time and the number of times the monitor has logged events since the last time it was reset.
Press F14. Press F14 again to reset.
Edit the actions to perform when events are logged by the monitor.
Press F10. The Work with Actions display is shown. For more information about actions, see Working with Actions.
Monitor name
The name of the monitor.
Monitor type
The type of monitor.
*CFGD Work with Configuration Status (WRKCFGSTS) monitor.
*CPU CPU percentage
*DISK Disk monitor
*MSG Message monitor.
58
Messenger V8R1M0
*JOBPFR Work with Active Jobs (WRKACTJOB) monitor.
*JOBQ Work with Job Queues (WRKJOBQ) monitor.
*JOBRUN Job Run
*JRN Journal monitor.
*OUTQ Work with Output Queues (WRKOUTQ) monitor.
*RMT Remote event monitor.
*TCP TCP/IP (PING) monitor. The monitor will test the TCP/IP connection between the local system and a remote system using the PING command at the specified time intervals. If the remote device (also known as a host) fails to respond, an event is created and the associated actions are performed.
DescriptionThe description of the monitor. This field is for informational purposes only.
Check everyThe frequency (in minutes) the monitor will check for new events.
Default pager nameThe name of the pager that will be assigned to pager message actions that specify *DFT as the pager name.
Process nameThe name of the IBM i job that is submitted to perform monitoring of the events. You can create additional processes by pressing F4, then F6. Additional processes may be needed if your monitoring volume exceeds the capabilities of a single job.
Authorization listThe name of the IBM i authorization list to secure changes to the monitor.
Working with Event Monitors
The Work with Event Monitors display allows you to define the specific events you want to monitor. Using the Work with Event Monitors display, you can:
• Create new events to monitor.
• Change the parameters of an existing Event Monitor, such as the scheduled time periods, colors, and so on.
• Delete Event Monitors from your system.
• Display the number of events logged by each Event Monitor.
• Start and stop monitoring for particular events.
• Access the Work with Actions display, allowing you to define the actions to perform for a particular event.
• Access the Work with Events display, allowing you to work with the events logged by the Event Monitor.
• Access the Work with Message Filters, if you are working with a message monitor.
• Access the Work with Job Filters display, if you are working with a job monitor.
• Access the Configuration Status Details display if you are working with a configuration status monitor.
• Access the PING details display if you are working with a TCP/IP monitor.
• Access the Display Journal details if you are working with a Journal monitor.
59
Monitoring
From the Monitor Details display, press Enter. If the Message Queue Options display is shown, press Enter again.
If you want to: Do the following:Refresh the display to see the latest status of the Event Monitors and the number of events.
Press F5.
Create a new Event Monitor. Press F6.Change the parameter of an Event Monitor, such as the message filters, job filters, and so on.
Type a 2 next to the Event Monitor you want to change, press Enter.
Temporarily suspend an Event Monitor until it is later released.
Type a 3 next to the Event Monitor you want to hold, press Enter. The status changes to HLD.
Permanently remove an Event Monitor. Type a 4 next to the Event Monitor you want to remove, press Enter.Display the events logged by the Event Monitor. Type a 5 next to the Event Monitor you want to display, press Enter.
The Work with Events display is shown.Release a held Event Monitor. Type a 6 next to the Event Monitor you want to release, press Enter.Work with the Actions that are performed when the Event Monitor logs an event.
Type a 7 next to the Event Monitor you want to work with, press Enter. The Work with Actions display is shown.
Copy an Event Monitor to a new one. Type an 8 next to the monitor you want to copy, press Enter.Display the filters for an Event Monitor. Type a 9 next to the Event Monitor you want to work with, press Enter.
The Work with Message Filters or Work with Job Filters display is shown.
Display or reset the usage data. The usage data shows you the last time and the number of times the Event Monitor has occurred since the last time it was reset.
Type a 2 next to the Event Monitor you want to display or reset, press F14. Press F14 again to reset.
Sequence numberThe sequence number of the Event Monitor. Event monitors with the lowest sequence numbers are tested first, before Event Monitors with higher sequence numbers. You should assign lower sequence numbers to specific events such as power failure, than generic events such as all severity 99 messages. This allows you to trap the specific event before it would be monitored by a generic event handler.
DescriptionThe description of the Event Monitor. This field is for informational purposes only.
CountThe number of unacknowledged events logged by the Event Monitor.
StsThe status of the event monitor.
RLS The Event Monitor is released. The Event Monitor will monitor for events if the monitor is started.
HLD The Event Monitor is held. Held Event Monitors do not monitor for events.
SCH The Event Monitor is scheduled to run at a later time. To view or change the schedule, type 2 to change and press F11.
60
Messenger V8R1M0
Event Monitor Details
The Event Monitor Details display allows you to define parameters for monitoring a specific event and how the event is displayed using the Work with Events display.
From the Work with Event Monitors display, if you are adding a new Event Monitor, press F6. If you are changing an existing Event Monitor, type a 2 next to the Event Monitor you want to change, press Enter.
If you want to: Do the following:Display or change the actions to perform when the event occurs. Press F10. Display or change the time periods the event will be monitored. Press F11. For more information about schedules, see
Working with Schedules.Display or reset the usage data. The usage data shows you the last time and the number of times the Event Monitor has occurred since the last time it was reset.
Press F14. Press F14 again to reset.
Display or change the time the event is expected to occur. When you specify an expected time, MessengerPlus logs an event when the event you are monitoring for does not occur before the time specified.
Press F15.
Event IDThe ID automatically assigned to the event. The Event ID can be used to monitor for specific events across a network using the optional MessengerConsole module.
StatusThe status of the Event Monitor.
Sequence numberThe sequence number of the Event Monitor. Event monitors with the lowest sequence numbers are tested first, before Event Monitors with higher sequence numbers. You should assign lower sequence numbers to specific events such as power failure, than generic events such as all severity 99 messages. This allows you to trap the specific event before it would be monitored by a generic event handler.
DescriptionThe description of the Event Monitor. This field is for informational purposes only.
Expected time/increment (F15)The time the event is expected to occur. When an expected time is specified, the actions are performed only when the event does not occur by the specified time. If the event does occur before the specified time, no actions are performed. This allows you to monitor for jobs that must complete before a specified time and send a pager message or perform other actions as needed.
The increment specifies the recurring time interval for subsequent monitoring. For events that are expected once per day (such as a daily job completion message), specify 24H. To check for an event more frequently (such as a the existence of a job expected to always be running), specify one of the following increment values:
5M 5 minutes15M 15 minutes30M 30 minutes
61
Monitoring
1H 1 hour2H 2 hours4H 4 hours12H 12 hours24H 24 hours
Event QueueThe name of the Event Queue that will receive the event. If specified, the event will appear in the Work with Event Queues display. If the Event Queue is in *BREAK mode (using the CHGEVTQ command), the event will automatically appear on the user’s display. If the Event Queue is a list (type *LIST), MessengerPlus will automatically escalate the event to the Event Queues on the list at the appropriate time periods. If the optional MessengerConsole™ module is installed, and the Event Queue is monitored by a remote system, the event will be automatically routed to the remote system.
SeverityThe severity of the event. You can view events by severity using the Work with Events display. You can also specify a severity filter on the Change Event Queue (CHGEVTQ) command.
1- The severity of the event is the default severity. For messages, the default severity is the severity of the message. For other events, the default severity is automatically provided by MessengerPlus.
0 - 99 Specifies the severity of the event.
Override color severity codeThe color code to assign to the event. If you do not specify a color code, the color is automatically assigned based on the severity of the event. You can assign different color codes for informational and inquiry events. To assign a color code, press F4. The colors can be viewed using the Work with Events display.
32 Green33 Green/Reverse34 White35 White/Reverse40 Red41 Red/Reverse42 Red/Blink43 Red/Reverse/Blink48 Turquoise49 Turquoise/Reverse50 Yellow51 Yellow/Reverse56 Pink57 Pink/Reverse58 Blue59 Blue/Reverse
Response requiredSpecifies if you want to require a response to the event.
N A response is not required. For inquiry messages, this parameter is ignored, since a response is automatically required.
Y A response is required. For informational messages, this parameter overrides the message type to inquiry.
62
Messenger V8R1M0
AlarmSpecifies if the workstation alarm is sounded when the event is displayed.
N The workstation alarm is not sounded.
Y The workstation alarm is sounded when the event appears on the Work with Events display.
Event textThe text of the event as it appears in the Work with Events display. You can type literal text and the following substitution variables that are automatically inserted by MessengerPlus when the event is logged:
&MT The text of the message. For non message events, the default text is assigned by MessengerPlus.&MQ The message queue name.&ML The message queue library name.&MI The message identifier.&MD The first 256 characters of the message data.&MJ The job name.&MU The user name.&MN The job number.&MK The 4 character message key.&MP The program name.&MV The severity code.&MY The message type code.&MH The first 256 characters of the message help.&MF The message file name.&MB The message file library name.&MS The name of the system the event originated.&1 .. &99 The message data variable from the message description (valid for message events only).
Example:Event text: Job &MN/&MU/&MJ received message &MI in program &MP.Results: Job 045680/QSYSOPR/TAP01 received message CPF0001 in program SAVALL.
System Default Pager Setup
MessengerPlus uses a System Default Pager to simplify the setup of monitoring for events that are typically sent to the same pagers. Later, you will be able to override the default pager if needed for specific types of error messages.
1. Select option 4 from the Setup Menu.
2. Change the Default pager name to the name of your pager. MessengerPlus is pre configured to automatically page the default pager name whenever a message or other event occurs that does not have an action specified.
3. If you need to page more than one pager as the default pager, choose a pager group or escalation list.
Audit Journal Monitoring
The Security Audit Journal (QAUDJRN) is the primary source of information about security-related events on your system. You can use the journal monitor to filter events from the audit journal and alert administrators by pager or email:
• Changes to auditing
• System management changes
• Changes to system values
63
Monitoring
• Authority failures
• Programs changed to adopt authority
• Users obtaining adopted authority
• Authority changes
• Authority changes during restore
• Restoring programs that adopt authority
• Use of system service tools
• Profile swapping
• Invalid passwords
• Command string audits
• User profiles changed, created, restored
• Actions that affect jobs
• Objects created, deleted, moved, renamed, or restored
• Audited object accessed
SetupThe System Audit Journal is the primary resource for security related events occurring on the IBM i. MessengerPlus can monitor these events and perform actions, such as disabling a user profile or alerting a system administrator. Here are examples of the types of events recorded to the audit journal:
Authorization failures: Unsuccessful attempts to sign onto the system and to access objects are logged. *AUTFAIL can be used regularly to monitor users trying to perform unauthorized functions on the system. *AUTFAIL can also be used to assist with migration to a higher security level and to test resource security for a new application.
Commands: The system logs command strings run by a user. If a command is run from a CL program that is created with LOG(*NO) and ALWRTVSRC(*NO), only the command name and library name are logged. *CMD may be used to record the actions of a particular user, such as the security officer.
Creating objects: The system writes a journal entry when a new or replacement object is created. *CREATE may be used to monitor when programs are created or recompiled.
Deleting objects: The system writes a journal entry when an object is deleted.
Job tasks: Actions that affect a job are logged, such as starting or stopping the job, holding, releasing, canceling, or changing it. *JOBDTA may be used to monitor who is running batch jobs.
Object management tasks: Moving an object to a different library or renaming it is logged. *OBJMGT may be used to detect copying confidential information by moving the object to a different library.
OfficeVision tasks: Changing the system distribution directory and opening a mail log are recorded. Actions performed on specific items in the mail log are not recorded. *OFCSRV may be used to detect attempts to change how mail is routed or to monitor opening another user’s mail log.
Optical functions: All optical functions are audited, including functions related to optical files, optical directories, optical volumes, and optical cartridges. *OPTICAL may be used to detect attempts to create or delete an optical directory.
Network Communications Auditing: The violations detected by the APPN Filter support are logged to the security auditing journal when the Directory search filter and the End point filter are audited.
64
Messenger V8R1M0
Adopting authority: The system writes a journal entry when adopted authority is used to gain access to an object. *PGMADP may be used to test where and how a new application uses adopted authority.
Program failures: The system writes a journal entry when a program causes an integrity error. *PGMFAIL may be used to assist with migration to a higher security level or to test a new application.
Printing functions: Printing a spooled file, printing directly from a program, or sending a spooled file to a remote printer is logged. *PRTDTA may be used to detect printing confidential information.
Save and restore operations: Saving objects from the system and restoring objects to the system is logged. *SAVRST may be used to detect attempts to restore unauthorized objects or to track attempts to save objects.
Security tasks: Security relevant events, such as changing a user profile or system value, are logged. *SECURITY may be used to keep a record of all security activity.
Service tasks: The use of service tools, such as DMPOBJ (Dump Object) and STRCPYSCN (Start Copy Screen), is logged. *SERVICE may be used to detect attempts to circumvent security by using service tools.
Operations on spooled files: Actions performed on spooled files are logged, including creating, copying, and sending. *SPLFDTA may be used to detect attempts to print or send confidential data.
System management tasks: The system writes a journal entry for system management activities, such as changing a reply list or the power on/off schedule. *SYSMGT may be used to detect attempts to use system management functions to circumvent security controls.
You must take specific steps to set up security auditing. A complete discussion of the security audit journal is beyond the scope of this document. For more information, see “OS/400 Security Reference” Document Number SC41 4302 01, and “Keep an Eye on Your AS/400 with Auditing” News/400 magazine February 1998.
If you have not already started security auditing, do the following steps. Setting up auditing requires *AUDIT special authority.
1. Create a journal receiver in a library of your choice by using the Create Journal Receiver (CRTJRNRCV) command. This example uses a library called JRNLIB for journal receivers.
CRTJRNRCV JRNRCV(JRNLIB/AUDRCV0001) THRESHOLD(5000) AUT(*EXCLUDE) TEXT('AUDITING JOURNAL RECEIVER')
• Place the journal receiver in a library that is saved regularly.
• Choose a journal receiver name that can be used to create a naming convention for future journal receivers, such as AUDRCV0001. You can use the *GEN option when you change journal receivers to continue the naming convention. Using this type of naming convention is also useful if you choose to have the system manage changing your journal receivers.
• Specify a receiver threshold appropriate to your system size and activity. The size you choose should be based on the number of transactions on your system and the number of actions you choose to audit. If you use system change journal management support, the journal receiver threshold must be at least 5,000KB.
• For more information on journal receiver threshold refer to the Backup and Recovery Advanced book.
• Specify *EXCLUDE on the AUT parameter to limit access to the information stored in the journal.
2. Create the QSYS/QAUDJRN journal by using the Create Journal (CRTJRN) command:
CRTJRN JRN(QSYS/QAUDJRN)JRNRCV(JRNLIB/AUDRCV0001) MNGRCV(*SYSTEM) DLTRCV(*NO) AUT(*EXCLUDE) TEXT('AUDITING JOURNAL')
• The name QSYS/QAUDJRN must be used.
• Specify the name of the journal receiver you created in the previous step.
65
Monitoring
• Specify *EXCLUDE on the AUT parameter to limit access to the information stored in the journal. You must have authority to add objects to QSYS to create the journal.
• Use the Manage receiver (MNGRCV) parameter to have the system change the journal receiver and attach a new one when the attached receiver exceeds the threshold specified when the journal receiver was created. If you choose this option, you do not have to use the CHGJRN command to detach receivers and create and attach new receivers manually.
• Do not have the system delete detached receivers. Specify DLTRCV(*NO), which is the default. The QAUDJRN receivers are your security audit trail. Ensure that they are adequately saved before deleting them from the system.
• The Backup and Recovery Advanced book provides more information about working with journals and journal receivers.
3. Set the audit level (QAUDLVL) system value using the WRKSYSVAL command. The QAUDLVL system value determines which actions are logged to the audit journal for all users on the system. For more information, see “OS/400 Security Reference” Document Number SC41 4302 01, “Planning the Auditing of Actions”.
4. Set action auditing for individual users if necessary using the CHGUSRAUD command. For more information, see “OS/400 Security Reference” Document Number SC41 4302 01, “Planning the Auditing of Actions”.
5. Set object auditing for specific objects if necessary using the CHGOBJAUD and CHGDLOAUD commands. For more information, see “OS/400 Security Reference” Document Number SC41 4302 01, “Planning the Auditing of Object Access”.
6. Set object auditing for specific users if necessary using the CHGUSRAUD command.
7. Start auditing by setting the QAUDCTL system value to a value other than *NONE. The QSYS/QAUDJRN journal must exist before you can change the QAUDCTL system value to a value other than *NONE. When you start auditing, the system attempts to write a record to the audit journal. If the attempt is not successful, you receive a message and auditing does not start.
To view or change the audit journal events monitored by MessengerPlus:
1. Select option 5 from the Setup Menu.
2. If necessary, release QAUDJRN by typing a 6 next to its name and pressing Enter.
3. Type a 9 next to QAUDJRN and press Enter. The Work with Event Monitors display is shown.
4. Release the desired event monitors as needed. If you want to perform an action (such as paging an administrator) type a 7 next to the desired event monitor and press Enter. Press F6 to add a new action. For more information about actions, press the Help key or see the section Reference: Working with Actions.
5. To view or change the journal filters, type a 9 next to an event monitor and press Enter. The Work with Journal Filters display is shown.
For more information about working with Event Monitors and Journal Filters, see the sections Working with Event Monitors and Working with Journal Filters.
Journal DetailsThe Journal Details display is shown automatically when you press Enter from the Event Monitor Details display when the monitor type is *JRN. This display allows you to define parameters for monitoring of journals. For more information about the options available on this display, press Help. For additional options, press F10.
Journal nameSpecifies the name and library of the journal to monitor.
66
Messenger V8R1M0
Working with Journal FiltersThe Work with Journal Filters display allows you to define the specific journal entries you want to include and exclude from monitoring. Journal filters allow you to include and exclude the entries you want by any combination of:
• Entry type
• Job name
• User name
• Program name
• Object name
• Entry specific compare data
Using the Work with Journal Filters display, you can:
• Add filters for journal entries to monitor, or exclude from monitoring.
• Change the parameters of an existing filter.
• Remove filters from monitoring.
If you are monitoring the system audit journal (QAUDJRN), many of the parameters on the following displays can be determined by displaying the journal using the DSPJRN QAUDJRN command.
From the Event Monitor Details display for a journal (*JRN) monitor, press Enter. Or, from the Work with Event Monitors display, type a 9 next to an event monitor and press Enter.
You can create as many filters as needed to define the event you are monitoring. Each filter has several parameters. Specifying more than one parameter for a filter are ANDed together: all of the parameters specified on a filter must be met. Specifying more than one filter are ORed together: any of the filters matched will log the event.
If you want to: Do the following:Add a new journal filter. Press F6.Change the parameter of an existing filter. Type a 2 next to the filter you want to change, press Enter. Remove a filter. Type a 4 next to the filter you want to remove, press Enter.
Sequence numberThe sequence number of the filter. MessengerPlus filters journal entries starting with the lowest numbered sequence numbers, starting at the top and working down the list. You should assign lower sequence number to the highest priority filters, such as excluding a specific type of entry, and higher sequence numbers to generic filters, such as including all other entries.
Include/ExcludeSpecifies if the filter is including or excluding. If you have only exclude filters, all other entries not matching the exclude filter are automatically included. If you have only include filters, all other filters not matching the include filter are automatically excluded. If you have a combination of include and exclude filters, journal entries are specifically included and excluded in the order you specified.
I The filter is including entries.
E The filter is excluding entries.
67
Monitoring
Entry typeSpecifies the type of journal entry being filtered. For the system audit journal, press the Help key for details about available entry types.
JobThe name of the job being filtered.
UserThe name of the user being filtered.
ObjectSpecifies the name of the object being filtered.
CmpSpecifies if entry-specific data is being compared.
UsageSpecifies the number of times the filter has been used since a starting date.
Journal Filter DetailsThe Journal Filter Details display allows you to define the parameters for filtering journal entries.
From the Work with Journal Filters display, if you are creating a new filter, press F6. If you are changing an existing filter, type a 2 next to the filter you want to change, press Enter.
Sequence numberThe sequence number of the filter. MessengerPlus starts filtering with the lowest numbered sequence numbers, starting at the top and working down the list. You should assign lower sequence numbers to the highest priority filters, such as excluding a specific type of entry, and higher sequence numbers to generic filters, such as including all other entries.
Include/ExcludeSpecifies if the filter is including or excluding entries. If you have only exclude filters, all other entries not matching the exclude filter are automatically included. If you have only include filters, all other entries not matching the include filter are automatically excluded. If you have a combination of include and exclude filters, journal entries are specifically included and excluded in the order you specified.
I The filter is including journal entries.
E The filter is excluding journal entries.
Entry typeSpecifies the type of journal entry being monitored. For the system audit journal, the following table identifies the entry types and the associated message description. You can learn more about the specific event using the DSPMSGD command. The entry type can be specified as either two or three characters. Two character entry types will match all entry types starting with the specified characters.
68
Messenger V8R1M0
JobThe name of the job being filtered.
*ALL Entries are not filtered on job name.
job-name Specifies the name of the job of which entries are filtered.
UserThe name of the user being filtered.
*ALL Entries are not filtered by user name.
user-name Specifies the name of the user of which entries are filtered.
ProgramThe name of the program being filtered.
*ALL Entries are not filtered by program name.
Program-name Specifies the name of the program of which entries are filtered.
Object
The name of the object being filtered.
*ALL Entries are not filtered by object name.
Object-name Specifies the name of the object of which entries are filtered.
Entry specific data starting positionSpecifies the starting position to begin the comparison of the entry specific data portion of the journal entry.
blank No comparison is performed on the entry specific data portion of the journal entry.
Starting-position Specifies the starting position to begin the comparison.
Entry specific data testSpecifies the type of comparison to perform on the entry specific data portion of the journal entry.
EQ The comparison value is tested for an equal match. The comparison is successful if the entry specific data matches the comparison value at the specified starting location.
NE The comparison value is tested for a not-equal match. The comparison is successful if the entry specific data does not match the comparison value at the specified starting location.
CT The comparison value is tested for a contains match. The comparison is successful if the entry specific data contains the comparison value.
NC The comparison value is tested for non contains match. The comparison is successful if the entry specific data does not contain the comparison value.
Entry specific data valueSpecifies the value to compare. The value is case sensitive, so you need to type the data exactly as it appears. Do not type quotes around the value. To specify a generic value, type only as many characters as you want to test, without an asterisk. For example, to test for PRT01, PRT02, or PRT03, type PRT.
69
Monitoring
Audit Journal Entry TypesThe following table lists the Entry type values and the corresponding message identifier and description. You can learn more about the event by displaying the associated message description using the DSPMSGD command.
Audit Journal Entry Type
Message
ADD CPI2285 CHGDLOAUDADO CPI2285 CHGOBJAUDADU CPI2285 CHGUSRAUDAFA CPI2246 Object authority failureAFB CPI2268 Blocked instruction violationAFC CPI2250 Program validation value error during restoreAFD CPI2247 Object domain violationAFJ CPI2248 SBMJOB and not authorized to user in JOBDAFP CPI2270 Profile handle specified on QWTSETP not validAFR CPI2274 Read only storage violationAFS CPI2249 Signon requested using default user profileAFU CPI2296 User not authorized to work on behalf of userAPE CPI2287 Program adopt endedAPS CPI2287 Program adopt startedCAA CPI2253 Object authority changeCDC CPI2286 Command runCDL CPI2286 S/36E operator control language statementCDO CPI2286 S/36E operator control commandCDP CPI2286 S/36E procedureCDU CPI2286 S/36E utility control statementCON CPI2277 Create of a new objectCOR CPI2278 Create of an object with REPLACE(*YES)CPA CPI2266 User profile created, changed or restoredCQA CPI2298 *CRQD object changedDOA CPI2263 Object deletedDSA CPI2267 DST Security Officer password resetGSG CPI2299 Give socket APIJDA CPI2264 Create/change of a JOBD with a user profileJSA CPI2288 ENDJOBABN commandJSB CPI2288 Submit jobJSC CPI2288 Change jobJSE CPI2288 End jobJSH CPI2288 Hold jobJSI CPI2288 Disconnect job
JSM CPI2288 Change job user profile
70
Messenger V8R1M0
Audit Journal Entry Type
Message
JSN CPI2288 ENDJOB commandJSP CPI2288 PSR attach to PJJSR CPI2288 Release jobJSS CPI2288 Start jobLDK CPI229A Lookup directoryLDL CPI229A Link directoryLDU CPI229A Unlink directoryMLO CPI2289 Maillog openedNAA CPI2257 Network attribute changed
OMM CPI2281 Move objectOMR CPI2282 Rename objectORE CPI2280 Restore object over previously existing objectORN CPI2279 Restore object of a new objectOWA CPI2254 Object owner changePAA CPI2255 CHGPGM used to adopt a user profilePGA CPI229B Object primary group changePOD CPI2290 Direct printPOR CPI2290 Spooled file sent to remote sysPOS CPI2290 Spooled output printPSA CPI2273 Target user profile changed during passthruPSE CPI2291 End work on behalf of another userPSH CPI2272 Profile handle created by QSYGETPHPSS CPI2291 Start work on behalf of another user
PWA CPI2292 APPC bind failurePWP CPI2251 Invalid password enteredPWU CPI2252 Invalid user ID enteredRAA CPI2261 Restore object and authority changedRJA CPI2259 Restore of a JOBD containing a user profileROA CPI2260 Restore of object and ownership changeRPA CPI2258 Restore of a program that adoptsRQA CPI229C *CRQD object restoredRUA CPI2262 Restore authority for a user profileRZA CPI229D Primary group changed on restoreSDS CPI2293 System distribution directorySEA CPI2265 Routing entry changed in subsystemSFA CPI2294 Spool file readSFC CPI2294 Spool file createdSFD CPI2294 Spool file deleted
71
Monitoring
Audit Journal Entry Type
Message
SFH CPI2294 Spool file heldSFI CPI2294 Create of inline fileSFR CPI2294 Spool file releasedSFU CPI2294 Spool file changedSMB CPI228E OA backup listSMC CPI228E OA cleanup optionsSMD CPI228E DRDASMF CPI228E HFS file systemSMN CPI228E Network file operationsSMO CPI228E OA backup optionsSMP CPI228E OA power schedulerSMS CPI228E System reply listSMT CPI228E Access path recovery times changedSTA CPI228F Service tool usedSVA CPI2256 System value changedVAF CPI229E IOP access control list change failedVAS CPI229E FSIOP access control list change successfulVCE CPI229F FSIOP connection endedVCR CPI229F FSIOP connection rejectedVCS CPI229F FSIOP connection startedVFA CPI227A FSIOP server file closed, administrative disconnectVFN CPI227A SIOP server file closed, normal disconnectVFS CPI227A FSIOP server file closed, session disconnectVLA CPI227B FSIOP account limit exceeded, account expiredVLD CPI227B FSIOP account limit exceeded, account disabledVLL CPI227B FSIOP account limit exceeded, logon hours exceededVLU CPI227B FSIOP account limit exceeded, unknown accountVLW CPI227B FSIOP account limit exceeded, invalid work stationVNF CPI227C FSIOP network logoffVNO CPI227C FSIOP network logonVNR CPI227C FSIOP network logon rejectedVPP CPI227D FSIOP password errorVRF CPI227E FSIOP network resource access failedVRS CPI227E FSIOP network resource access successfulVSE CPI227F FSIOP server session endedVSS CPI227F FSIOP server session startedVUG CPI226B FSIOP network profile change, group recordVUM CPI226B FSIOP network profile change, global information
72
Messenger V8R1M0
Audit Journal Entry Type
Message
VUU CPI226B FSIOP network profile change, user recordVVC CPI226C FSIOP service status change, service status changeVVE CPI226C FSIOP service status change, server stoppedVVP CPI226C FSIOP service status change, server pausedVVR CPI226C FSIOP service status change, server restartedVVS CPI226C FSIOP service status change, server startedYCC CPI228A Change of a DLOYRR CPI228B Read of a DLOZCC CPI228C Change of an objectZRR CPI228D Read of an object
CPU Monitoring
MessengerConsole and MessengerPlus can monitor the length of time your system remains at a specified CPU percentage:
• Specific CPU percentage
• Length of time system stays at CPU percentage
Setup1. Select option 5 from the Setup Menu.
2. If necessary, release CPU by typing a 6 next to it and pressing Enter.
3. Type a 2 next to CPU and press Enter.
4. Change information as needed. When completed, press Enter. The CPU% Monitor Options screen will be displayed.
5. Change information as needed. When completed, press Enter.
Disk Monitoring
The *DISK monitor checks the growth of disk storage on an hourly, daily, weekly, or monthly basis. When specified thresholds are reached, the software triggers an alert that tells the administrators of the impending disk disaster.
• Monitor disk on an hourly, daily, weekly, and monthly basis.
• Monitor for disk space remaining in percentage or megabytes.
• Monitor for disk space growth in percentage or megabytes.
• Monitor multiple ASPs.
Setup1. Select option 5 from the Setup Menu.
2. If necessary, release DISK by typing a 6 next to it and pressing Enter.
3. Type a 2 next to DISK and press Enter.
73
Monitoring
4. Change information as needed. When completed, press Enter. The Work with Event Monitors display will appear.
5. Create or change an Event Monitor. Type a description, such as “5% per day”, or “80% remaining”. Press Enter. The Disk Filter Details display will appear (see Disk Filter Details, below).
6. Type choices, press Enter.
7. If necessary, release the Event Monitor by typing a 6 next to it and pressing Enter.
8. Press F3 to return the Work with Monitors display.
Disk Filter DetailsASP: Type the number of the Auxiliary Storage Pool (ASP) you want to monitor. To see a list of available ASPs, use the command DSPASPBRM. The system ASP is 1.
Last ASP MB Used: The amount of DASD used at the start of the monitoring period. This value is captured by the product at the start of the monitoring period, and is for display only. This value represents the current baseline for calculating measurements.
Threshold value and type: The amount of DASD that can be used before triggering an event, expressed in either megabytes or as a percentage of total DASD. Threshold monitors detect when disk usage reaches a specified amount, either in megabytes used, or a percentage of disk (for example, 90%).
Growth value and type: The amount of storage utilization that can increase over a period of time before triggering an event, ex-pressed in megabytes or as a percentage of total DASD. Growth monitors detect disk usage exceeding a percentage over a period of time (Hourly, Daily, Weekly, Monthly).
Growth period: The length of the monitoring period: Hourly, Daily, Weekly, Monthly.
Detect spikes: Specifies if the product should create events if spikes are detected during the growth period. When this value is on (Y=Yes), the product will create an event whenever the threshold is exceeded, and not just at the end of the monitoring period. The product will automatically acknowledge existing events if the condition clears.
Line Status Monitoring (WRKCFGSTS)
Do you need to know when a critical communications line is down? MessengerConsole and MessengerPlus can monitor the Work with Configuration Status (WRKCFGSTS) display for lines, controllers, devices and network servers for abnormal status. Simply define the configuration object names and their normal status. If the status changes to any that is not checked, MessengerPlus will log an event and perform the specified actions, which can include resetting the line and/or paging an operator.
Setup1. Select option 5 from the Setup Menu.
2. Release LINEMON by typing a 6 next to it and pressing Enter.
3. Type a 9 next to the LINEMON and press Enter. Press F6 to create a new Event Monitor.
4. Type description, press Enter.
5. On the Configuration Status Details display, type choices (see details below), press Enter.
6. Release the newly created Event Monitor by typing a 6 next to it and pressing Enter. MessengerPlus is pre configured to send a pager message to the default pager. If you want to override this action, type a 7 next to the appropriate Event Monitor and press Enter. For more information about creating actions, see Working with Actions.
74
Messenger V8R1M0
Configuration Status DetailsThe Configuration Status Details display is shown automatically when you press Enter from the Event Monitor Details display when the monitor type is *CFGD. This display allows you to define parameters for monitoring of communications lines, controllers, devices, network servers, and network interfaces.
Configuration objectSpecifies the name of the line, controller, device, network server or network interface you want to monitor. This is the same as the ‘Configuration description’ parameter on the Work with Configuration Status (WRKCFGSTS) command.
Configuration object typeSpecifies the type of the configuration object you are monitoring. This is the same as the ‘Type’ parameter on the Work with Configuration Status (WRKCFGSTS) command.
Type ‘X’ next to NORMAL statusType an X next to each of the statuses the line, controller or device should be in during normal operations. MessengerPlus will log an event whenever the status changes to any that is not checked.
Message Queue Monitoring
MessengerConsole and MessengerPlus can monitor any number of message queues including QSYSOPR and QSYSMSG. They offer the most extensive user configurable filters on all monitors and can filter messages and events from any number of messages queues.
Do you need to know when a batch job halts due to an error? MessengerConsole and MessengerPlus can filter messages from any number of messages queues using Message Filters. Message Filters allow you to easily customize the specific sets of messages you want to monitor by including or excluding messages by the following:
• Message Id
• Message type
• Severity
• Job name, or generic job name
• User, or generic user name
• Program, or generic program name
• Accounting code, or generic accounting code
• Message text and substitution variables (compare data)
• Time periods
You can easily create Message Filters to accommodate situations such as all severity 99 messages excluding printers. MessengerConsole and MessengerPlus are pre-configured with many common Message Filter Sets that you can use immediately or customize to meet your specific needs.
Message Filters can be combined, so you can monitor for situations such as all severity 99 messages excluding printer alignment, and so on. You can easily monitor your personal message queue and redirect messages to your pager or email to see messages from others when you are not signed on. You will be notified when files and Office documents sent from other users or systems have arrived in your mailbox.
75
Monitoring
System History Log (DSPLOG QHST)One of the most powerful features of the IBM i is its ability to log system activity and error messages to the history log QHST. The problem with QHST is that it contains so many messages that without adequate filtering tools, QHST contains too much information to be utilized proactively using the DSPLOG command. The result is important messages logged to QHST are never seen. MessengerConsole and MessengerPlus can monitor QHST using Message Filter Sets to automatically and proactively detect important messages. Examples of messages to monitor from QHST:
• When a specific job has started or ended.
• Jobs that end abnormally.
• Changes to system values.
• Changes to system pool sizes.
• Security messages.
• When a specific subsystem is started or ended.
• Other messages
Message Queue OptionsThe Message Queue Options display is shown when you are changing a monitor for type *MSG. The following options allows you to define parameters for monitoring of a message queue.
Message queue and libraryThe name of the message queue and library to monitor.
Severity filterThe minimum severity of messages to filter from the queue. Messages with severities below the specified severity will not be monitored, even if they are specifically included. It is best to leave this parameter zero, unless you are sure you do not want any messages below the specified severity level. A slight performance improvement can be realized on message queues with many low severity messages (such as QSYSOPR). This is because messages below the specified severity are not read from the message queue and not filtered. You can filter messages by severity using the Work with Message Filters display.
Message delaySpecifies the number of minutes messages on the queue must wait before being monitored. This allows time for a local operator to handle a message before MessengerPlus will begin monitoring the message. If the message is inquiry, MessengerPlus will not monitor the message if the message is answered within the specified time period by a local operator (this does not apply to messages answered by the system reply list). If the message is informational, MessengerPlus will not monitor the message if the message is removed within the specified time period.
Read back limitSpecifies the number of minutes prior to starting MessengerPlus you want messages monitored. Messages that have already been monitored will not be monitored again (not valid for QHST).
Lock message queueSpecifies if you want MessengerPlus to lock the message queue to prevent users from answering messages on the message queue, bypassing MessengerPlus’ security and auditing controls.
76
Messenger V8R1M0
Working with Message FiltersThe Work with Message Filters display allows you to define the specific messages you want to include and exclude from monitoring. Message filters allow you to include and exclude the messages you want by any combination of:
• Message Id
• Message type
• Severity
• Job name, or generic job name
• User, or generic user name
• Program, or generic program name
• Accounting code, or generic accounting code
• Compare data, or generic compare data
Message Filters can be combined, so you can monitor for situations such as all severity 99 messages excluding printer alignment, and so on. Using the Work with Message Filters display, you can:
• Add new messages to monitor, or exclude from monitoring.
• Change the parameters of a message filter, such as the message ID, job name, and so on.
• Remove messages from monitoring.
From the Event Monitor Details display for a message monitor, press Enter. Or, from the Work with Event Monitors display, type 9 next to the Event Monitors you want to change, press Enter.
You can create as many message filters as needed to define the event you are monitoring. Each message filter has several parameters. Specifying more than one parameter for a message filter are ANDed together: all of the parameters specified on a filter must be met. Specifying more than one message filter are ORed together: any of the message filters matched will log the event.
Many of the message filter parameters allow generic values. Generic values allow you to match a range of values by typing as much of the value you want to compare and end with an asterisk (*). For example, to filter for DSP01, DSP02, DSP03 but not DSP10, you would specify DSP0*.
0
If you want to: Do the following:Add a new message filter. Press F6.Change the parameter of a message filter. Type a 2 next to the message filter you want to change, press Enter. Remove a message filter. Type a 4 next to the message filter you want to remove, press Enter.Display or reset the usage data. The usage data shows you the last time and the number of times the message filter has been used since the last time it was reset.
Type a 2 next to the filter you want to change, press Enter. Press F14. Press F14 to reset.
Sequence numberThe sequence number of the message filter. MessengerPlus filters messages starting with the lowest numbered sequence numbers, starting at the top and working down the list. You should assign lower sequence number to the highest priority filters, such as excluding a message, and higher sequence numbers to generic filters, such as all inquiry messages.
77
Monitoring
Include/Exclude
Specifies if the message filter is including messages or excluding messages. If you have only exclude filters, all other messages not matching the exclude filter are automatically included. If you have only include filters, all other messages not matching the include filter are automatically excluded. If you have a combination of include and exclude filters, messages are specifically included and excluded in the order you specified.
I The message filter is including messages.
E The message filter is excluding messages.
Message IDThe identifier of the message being filtered.
*ALL Messages are not filtered on message identifier.
generic-message-identifier The message ID, or generic message ID to monitor. Example: CPA0701, CPF*
Message typeThe type of message being filtered.
*ALL Messages are not filtered on message type.
message-type The type of messages being filtered. You can select the message type from a list of message types by pressing F4.
SeverityThe minimum severity of the message being filtered.
0 Messages are not filtered on severity.
1 - 99 The minimum severity required of messages being filtered. Messages with severities lower than the specified value are not selected by the message filter. Messages with severities equal to or greater than the specified value are selected by the message filter.
JobThe job name, or generic job name of the messages to filter.
*ALL Messages are not filtered by job name.
generic-job-name The job name, or generic job name to monitor. Example: PRT01, PRT*
UserThe user name, or generic user name of the messages to filter.
*ALL Messages are not filtered by user name.
generic-user-name The user name, or generic user name to monitor. Example: QPGMR, PAY*
CmpSpecifies if the message filter has compare data specified.
UsageSpecifies the number of times the message filter has matched a message since a starting date.
78
Messenger V8R1M0
Message Filter DetailsThe Message Filter Details display allows you to define the parameters of the messages you want to monitor.
From the Work with Message Filters display, if you are creating a new message filter, press F6. If you are changing an existing message filter, type a 2 next to the filter you want to change, press Enter.
Most of the parameters on this display can be determined by positioning the cursor on the message you want to monitor and pressing Help.
If you want to: Do the following:Change the compare data for the filter. Press F16. For more information about compare data, see
Compare Data Details later in this section.Display or reset the usage data. The usage data shows you the last time and the number of times the message filter has occurred since the last time it was reset.
Press F14. Press F14 again to reset.
Sequence numberThe sequence number of the message filter. MessengerPlus filters messages starting with the lowest numbered sequence numbers, starting at the top and working down the list. You should assign lower sequence number to the highest priority filters, such as excluding a message, and higher sequence numbers to generic filters, such as all inquiry messages.
OptionSpecifies if the message filter is including messages or excluding messages. If you have only exclude filters, all other messages not matching the exclude filter are automatically included. If you have only include filters, all other messages not matching the include filter are automatically excluded. If you have a combination of include and exclude filters, messages are included and excluded in the order they appear.
I The message filter is including messages.
E The message filter is excluding messages.
Message IDThe identifier of the message being filtered.
*ALL Messages are not filtered on message identifier.
*BLANK Messages with a blank message ID are selected. Blank message IDs occur when the message is sent using the SNDMSG command (instead of SNDPGMMSG).
generic-message-identifier The message ID, or generic message ID to monitor. Example: CPA0701, CPF*
Message file and libraryThe name of the message file and library of the message. The message file and library are used to retrieve the description of the message on the Work with Message Filters display. They are not used to filter messages.
79
Monitoring
Message typeThe type of message being filtered.
*ALL Messages are not filtered on message type.
message-type The type of messages being filtered. You can select the message type from a list of message types by pressing F4.
SeverityThe minimum severity of the message being filtered. Messages below this severity are not monitored. The higher the severity code, the more serious the condition is.
0 Messages are not filtered on severity.
1 - 99 The following list of severity codes and their meanings are consistent with the severity codes assigned to system messages:
00: Information. For information purposes only; no error was detected and no reply is needed. The message could indicate that a function is in progress or that a function has completed successfully.
10: Warning. A potential error condition exists. The program may have taken a default, such as supplying missing input. The results of the operation are assumed to be successful.
20: Error. An error has been detected, but it is one for which automatic recovery procedures probably were applied; processing has continued. A default may have been taken to replace erroneous input. The results of the operation may not be valid. The function may have been only partially completed; for example, some items in a list processed correctly while others failed.
30: Severe error. The error detected is too severe for automatic recovery, and no defaults are possible. If the error was in source data, the entire input record was skipped. If the error occurred during program processing, it leads to an abnormal end of the program (severity 40). The results of the operation are not valid.
40: Abnormal end of program or function. The operation has ended, possibly because the program was unable to handle data that was not valid, or possibly because the user has canceled it.
50: Abnormal end of job. The job was ended or was not started. A routing step may have ended abnormally or failed to start, a job-level function may not have been performed as required, or the job may have been canceled.
60: System Status: A message of this severity is issued only to the system operator. It gives either the status of or a warning about a device, a subsystem, or the whole system.
70: Device integrity. Issued only to the system operator. It indicates that a device is malfunctioning or in some way is no longer operational. The user may be able to recover from the failure, or the assistance of a service representative may be required.
80: System alert. A message with a severity code of 80 is issued for immediate messages. It also warns of a condition that, although not severe enough to stop the system now, could become more severe unless preventive measures are taken.
90: System integrity. Issued only to the system operator. It describes a condition that renders either a subsystem or the system inoperative.
99: Action. Some manual action is required, such as entering a reply, changing printer forms, or replacing diskettes.
80
Messenger V8R1M0
JobThe job name, or generic job name of the messages to filter.
*ALL Messages are not filtered by job name.
generic-job-name The job name, or generic job name to monitor. Example: PRT01, PRT*
UserThe user name, or generic user name of the messages to filter.
*ALL Messages are not filtered by user name.
generic-user-name The user name, or generic user name to monitor. Example: QPGMR, PAY*
ProgramThe program name, or generic program name of the messages to filter.
*ALL Messages are not filtered by program name.
generic-program-name The program name, or generic program name to monitor.
Accounting codeThe accounting code, or generic accounting code of the messages to filter.
*ALL Messages are not filtered by accounting code.
generic-accounting code The accounting code, or generic accounting code to monitor.
Search other filtersFor messages that match this filter only, specifies if you want MessengerPlus to search other Event Monitors for inclusion of the message.
N Do not continue filtering the message through other Event Monitors.
Y Continue filtering the message through other Event Monitors. This allows you to monitor for a message more than once. For example, a message could create a Power failed event, then continue to create another event Critical system condition.
Compare dataTo add or change the compare data for the filter, press F16. For more information about compare data, see the following section Compare Data Details.
Compare Data DetailsThe Compare Data Details display allows you to specify filtering criteria on message data. Message data is the variables contained within the message. For example, message “Verify alignment on device PRT01” contains the message data PRT01 (the device name). You can determine the message data using the Display Message Description (DSPMSGD) command and choosing the option to view field data.
Each message filter can specify up to 5 comparisons. You can compare for more than 5 by creating additional message filters.
From the Message Filter Details display, press F16.
81
Monitoring
Field/PositionThe message field name or relative starting position. You can determine the message field name by pressing F10 and choosing the option to view field data. You can choose field types of *CHAR and *BIN only. For example, message CPF1240 has field names &1 for job, &2 for user and &3 for job number. To specify field names as a relative starting position, count the number of characters used by fields starting before the one you want to compare and add 1. For example, CPF1240 uses relative starting positions 001 for job, 011 for user and 021 for job number.
TestThe type of test.
EQ Equal.
NE Not equal.
CT Contains. The Field/Position parameter specifies the starting position of the comparison. To search the entire message data, specify a Field/Position of &1 or 001.
NC Not contains. The Field/Position parameter specifies the starting position of the comparison. To search the entire message data, specify a Field/Position of &1 or 001.
Compare valueThe value to compare. This value is case-sensitive; if the value you want to compare is upper-case, you must type the compare value in upper-case. Do not type quotes around the compare value.
And/OrSpecifies for multiple compare operations only, the relationship the comparison has to the others specified on this display. If you want to compare a single field for multiple values, specify Or. If you want to compare multiple fields, specify And. For example, to compare for user names BOB or JOE or SUSAN, specify Or. To compare for job name DAYEND and user QPGMR, specify And.
QSYSOPR, QSYSMSG and QHST Setup1. Select option 5 from the Setup Menu.
2. Release QSYSOPR, QSYSMSG and QHST by typing a 6 next to them and pressing Enter.
3. Type a 9 next to QSYSOPR and press Enter.
4. On the Work with Event Monitors screen, release the messages you want to monitor by typing a 6 next to them and pressing Enter. For more information about Event Monitors, see Working with Event Monitors.
5. MessengerPlus is preconfigured to send a pager message to the default pager. If you want to override this action for a specific message filter, type a 7 next to the appropriate Event Monitor and press Enter. For more information about creating actions, see Working with Actions.
6. Repeat steps 4 through 6 for QSYSMSG and QHST.
Auto-replying to System Messages1. Select option 5 from the Setup Menu.
2. Type a 9 next to the message queue you want to work with, press Enter.
3. Press F6 to create a new Event Monitor. Specify a sequence number of 10 and type a description (such as ‘Reply I to Verify Alignment messages’). Press Enter.
4. The Work with Message Filters display is shown.
82
Messenger V8R1M0
5. Press F6 to create a new filter. Specify a sequence number of 10, Option is I (Include) and the identifier of the message you want to auto-reply. For example, the ‘Verify alignment’ message identifier is CPA4002. Be careful specifying generic message identifiers (such as CPA0701, CPF9898, CPA2401 and *BLANK) as this will cause messages to be answered that you may not want. To reply to generic message identifiers, you must specify additional filtering criteria such as job name, user name or compare data. For more information about these parameters, see Working with Message Filters.
6. Press Enter until you return to the Work with Event Monitors display.
7. Type a 7 next to the Event Monitor you created. The Work with Actions display is shown.
8. Press F6 to create a new Action. Specify a sequence number of 10 and *REPLY for ‘Action to perform’, press Enter. The Reply Options display is shown. Type reply, press Enter.
9. Press Enter to return to the Work with Event Monitors display.
10. Release your Event Monitor by typing a 6 next to it and pressing Enter.
Job Start or Complete (by specified time) Monitoring
Do you need to know if a time-critical job does not complete on time? Sometimes a very serious problem is identified by the absence of an event. You probably have a job that runs every night that is critical to your business. Would you like to know if that job does not start or end by a certain time? MessengerConsole and MessengerPlus can monitor for specified jobs not starting or ending on time and alert you to a potential problem.
MessengerPlus can monitor for a specific message to occur by a specified time, such as backups or day end processing job completion message (‘Job 123456/QSYSOPR/BACKUPS completed normally’). If the message does not arrive before the specified time, MessengerPlus can page you to alert you of a potential problem.
1. Determine the name of the message queue that contains the job completion message. In most cases, the message queue name is QSYSOPR. If the message queue name varies, use QHST.
2. Display the message queue using the DSPMSG command (if using QHST, use DSPLOG).
3. Position the cursor on the message and press Help. Press F9 to display the message details.
4. Record the Message ID, Time and Job name. (Job completion messages on QSYSOPR are CPF1241. QHST job completion messages are CPF1164).
5. Go to the MessengerPlus menu by typing MPLUS at a command line and pressing Enter.
6. Select option 5 from the Setup Menu.
7. Type a 9 next to the appropriate monitor (QSYSOPR or QHST) and press Enter.
8. Type a 2 next to the Event Monitor ‘1150 Backups not completed on time’, press Enter.
9. Change Description if necessary. Press F15. Change Expected time as needed (leave Increment set to 24H). Press Enter. If you want to schedule the monitor for specific days of the week, press F11.
10. Press Enter until the Message Filters display appears.
11. Type a 2 to change the message filter, press Enter.
12. Change the Message ID and Job name as needed, press Enter.
13. Press Enter to return to the Work with Event Monitors display.
14. Release the Event Monitor by typing a 6 next to it and pressing Enter.
MessengerPlus is preconfigured to send a pager message to the default pager if the message does not occur on time. If you want to override this action, type a 7 next to the Event Monitor and press Enter. For more information about creating actions, see Working with Actions.
83
Monitoring
Job Status monitoring
Do you need to know when a specific job is using 90 percent of the CPU? Perhaps the most important command used by system operators is Work with Active Jobs (WRKACTJOB), the display used to monitor the throughput of the system. MessengerConsole and MessengerPlus can pro-actively monitor the Work with Active Jobs display for:
• Jobs consuming excessive CPU resources.
• Jobs exceeding a specified length of time.
• Jobs that must be running during specified times.
• Jobs with poor response times.
• Jobs with too low priority.
• Jobs with a specific status, ie. LCKW or MSGW.
• Jobs with a specific function, for example, S/36 procedure abends or when a user is running a specific program.
Jobs are monitored using Job Filters. You can include or exclude the jobs you want by any combination of:
• Job name, or generic job name
• User name, or generic user name
• Subsystem name
• Job type: interactive, batch, and so on.
• Job function
Filters can be combined, so you can monitor for situations such as all batch jobs with user QSYSOPR, and so on.
Working with Job FiltersThe Work with Job Filters display allows you to define the specific jobs you want to include and exclude from monitoring. Job filters allow you to include and exclude the jobs you want by any combination of:
• Job name
• User name
• Job type: interactive, batch, and so on.
• Subsystem name
• Function
You can test the selected jobs for any of the following conditions:
• Priority is lower than a specified value.
• CPU % exceeds a specified value.
• Response time exceeds a specified value.
• Status is a specified value: LCKW, MSGW, and so on..
• Run length: Hours, Minutes, CPU seconds.
84
Messenger V8R1M0
Job Filters can be combined, so you can monitor for situations such as all interactive jobs lower than severity 20 excluding the console, and so on. Using the Work with Job Filters display, you can:
• Add new jobs to monitor, or exclude from monitoring.
• Change the parameters of a job filter.
• Remove jobs from monitoring.
From the Event Monitor Details display for a job monitor, press Enter. Or, from the Work with Event Monitors display, type 9 next to the Event Monitors you want to change, press Enter.
You can create as many job filters as needed to define the event you are monitoring. Each job filter has several parameters. Specifying more than one parameter for a job filter are ANDed together: all of the parameters specified on a filter must be met. Specifying more than one job filter are ORed together: any of the job filters matched will log the event.
If you want to: Do the following:Add a new job filter. Press F6.Change the parameter of a job filter. Type a 2 next to the job filter you want to change, press Enter. Remove a job filter. Type a 4 next to the job filter you want to remove, press Enter.
Sequence numberThe sequence number of the job filter. MessengerPlus filters jobs starting with the lowest numbered sequence numbers, starting at the top and working down the list. You should assign lower sequence number to the highest priority filters, such as excluding a job, and higher sequence numbers to generic filters, such as all interactive jobs.
Include/ExcludeSpecifies if the job filter is including jobs or excluding jobs. If you have only exclude filters, all other jobs not matching the exclude filter are automatically included. If you have only include filters, all other jobs not matching the include filter are automatically excluded. If you have a combination of include and exclude filters, jobs are specifically included and excluded in the order you specified.
I The job filter is including jobs.
E The job filter is excluding jobs.
JobThe name of the job being filtered.
UserThe name of the user being filtered.
Job typeThe type of jobs being filtered.
SubsystemThe name of the subsystem of the jobs being filtered.
85
Monitoring
FunctionThe function of the jobs being filtered.
PrioritySpecifies the lowest priority the filtered jobs may have before an event is logged.
CPU % exceedsSpecifies the highest CPU percentage the filtered jobs may have before logging an event.
Response timeSpecifies the highest response time the filtered jobs may have before logging an event.
StatusSpecifies the status the filtered jobs may have before logging an event.
Job Filter DetailsThe Job Filter Details display allows you to define the parameters for filtering jobs. Specifying more than one parameter for a job filter are ANDed together (all of the parameters specified on a filter must be met).
From the Work with Job Filters display, if you are creating a new job filter, press F6. If you are changing an existing job filter, type a 2 next to the filter you want to change, press Enter.
Most of the parameters on this display can be determined from the Work with Active Jobs (WRKACTJOB) display.
Sequence numberThe sequence number of the job filter. MessengerPlus filters jobs starting with the lowest numbered sequence numbers, starting at the top and working down the list. You should assign lower sequence numbers to the highest priority filters, such as excluding a job, and higher sequence numbers to generic filters, such as all interactive jobs.
Include/ExcludeSpecifies if the job filter is including jobs or excluding jobs. If you have only exclude filters, all other jobs not matching the exclude filter are automatically included. If you have only include filters, all other jobs not matching the include filter are automatically excluded. If you have a combination of include and exclude filters, jobs are specifically included and excluded in the order you specified.
I The job filter is including jobs.
E The job filter is excluding jobs.
JobThe name of the job being filtered.
*ALL Jobs are not filtered on job name.
job-name The name of the job as it appears on the Work with Active Jobs (WRKACTJOB) display.
86
Messenger V8R1M0
UserThe name of the user being filtered.
*ALL Jobs are not filtered by user name.
user-name The name of the user as it appears on the Work with Active Jobs (WRKACTJOB) display.
Job typeThe type of jobs being filtered.
*ALL Jobs are not filtered by job type.
job-type The type of the job as it appears on the Work with Active Jobs (WRKACTJOB) display.
SubsystemThe name of the subsystem of the jobs being filtered.
*ALL Jobs are not filtered by subsystem name.
subsystem-name The name of the subsystem as it appears on the Work with Active Jobs (WRKACTJOB) display.
FunctionThe function of the jobs being filtered.
*ALL Jobs are not filtered by function name.
function-name The name of the function as it appears on the Work with Active Jobs (WRKACTJOB) display.
Job statusSpecifies the status the filtered jobs may have before logging an event. Job status can be determined from the Work with Active Jobs (WRKACTJOB) display.
blank Jobs are not tested for a status.
job-status Jobs with the specified status are selected.
PrioritySpecifies the lowest priority the filtered jobs may have before an event is logged. Priorities can be determined from the Work with Active Jobs (WRKACTJOB) display.
blank Jobs are not tested for priority.
priority is below Jobs with priorities lower than the specified value are selected.
CPU % exceedsSpecifies the highest CPU percentage the filtered jobs may have before logging an event. CPU percentages can be determined from the Work with Active Jobs (WRKACTJOB) display.
blank Jobs are not tested for CPU percentage usage.
CPU-%-limit Jobs with CPU percentages exceeding the specified value are selected.
87
Monitoring
Response timeSpecifies the highest response time the filtered jobs may have before logging an event. Response times can be determined from the Work with Active Jobs (WRKACTJOB) display.
blank Jobs are not tested for response time.
response-time-limit Jobs with response times exceeding the specified value are selected.
Run timeSpecifies the amount of time a job may run before an event is logged. The time value can be represented as CPU seconds, minutes or hours depending on the value specified for the run time type.
Run time typeSpecifies the type of value specified for run time.
H The run time is specified in hours.
M The run time is specified in minutes.
C The run time is specified in CPU seconds. Monitoring for CPU seconds is useful when the job has not been running very long, but is using excessive CPU resources. You can determine the number of CPU seconds a job has used by running the WRKJOB OPTION(*RUNA) command. The value specified for CPU time used is represented in milliseconds, so you need to convert the value to seconds by dividing by 1000. For example, a value of 3600 is 1 hour of CPU time (60 seconds * 60 minutes).
Setup1. Select option 5 from the Setup Menu.
2. Release JOBMON by typing a 6 next to it and pressing Enter.
3. Type a 9 next to JOBMON and press Enter.
4. Release the events you want to monitor by typing a 6 and pressing Enter. For more information about Event Monitors, see Working with Event Monitors.
5. MessengerPlus is preconfigured to send a pager message to the default pager. If you want to override this action, type a 7 next to the appropriate Event Monitor and press Enter. For more information about creating actions, see Working with Actions.
JOBRUN (*JOBRUN) Monitoring - Setup
This section describes how to monitor for one or more jobs that should be running during a specified time period.
1. Select option 5 from the Setup Menu.
2. If necessary, release JOBRUN by typing a 6 next to it and pressing Enter.
3. Type a 9 next to JOBRUN, press Enter.
4. If necessary, release ‘Jobs that should be running’ by typing a 6 next to it and pressing Enter.
5. Type a 9 next to ‘Jobs that should be running’ and press Enter.
6. Add or change the list of jobs as needed. When completed, press Enter until you return to the Work with Event Monitors display (above). For more information about creating Job Filters, see Working with Job Filters.
88
Messenger V8R1M0
7. MessengerPlus is preconfigured to send a pager message to the default pager. If you want to override this action, type a 7 next to the Event Monitor and press Enter. If you have different groups of jobs that need to be paged to pagers other than the default pager, you need to create them in a separate Event Monitor by pressing F6. For more information about creating actions, see Working with Actions.
8. By default, the list of jobs will be monitored for status of running at all times (7x24). If you want to change the time periods the list of jobs are monitored, use option 2 to change the Event Monitor, then press F11 for Schedule. If you have different groups of jobs that need to be monitored during different times, you need to create them in separate Event Monitors by pressing F6. For more information about schedules, see Working with Schedules.
Job Log (*JOBLOG) Monitoring - Setup
MessengerPlus can monitor for messages appearing in the job log of another active job. You can use the *JOBLOG Monitor to monitor for:
• Error messages in System 36 procedures
• Error messages in interactive jobs, such as the messages on the ‘Program Messages Display’
• Messages occurring in CL programs that ignore messages due to the use of MONMSG CPF0000.
Obviously, monitoring for every message in every job would use too many system resources and probably generate many unnecessary events. MessengerPlus allows you to monitor specific jobs without using the resources otherwise needed to monitor every job. You control what jobs are monitored by running the MPLUS/STRMON command in the job you want to monitor. You can accomplish this by using any of the following methods:
By running the MPLUS/STRMON MON(*JOBLOG) command at a command line before calling the program you want to monitor. Example:
MPLUS/STRMON MON(*JOBLOG)
CALL DAYEND
By adding the MPLUS/STRMON MON(*JOBLOG) command to the startup program of the job you want to monitor. Example:
PGM
MPLUS/STRMON MON(*JOBLOG)
... PROGRAM STATEMENTS ...
ENDPGM
The STRMON command submits a job with the same name as the job to the ZMPLUS subsystem. The monitoring job retrieves the new messages from the job log every 60 seconds, and filters the messages using the *JOBLOG filters in MessengerPlus. The monitoring job ends automatically when the job that is being monitored ends.
To view or change the *JOBLOG filters:1. Select option 5 from the Setup Menu.
2. Type a 9 next to *JOBLOG and press Enter. (If you are upgrading from a previous release, you may need to add the monitor by pressing F6. Specify *JOBLOG as the monitor name and accept the defaults).
3. The Work with Event Monitors display is shown:
MessengerPlus ships with the following default filters. You can change these filters or create your own filters as needed.
89
Monitoring
S/36 SYS* Messages: Monitors for S/36 error messages. These messages are identified by messages starting with SYS and having a severity of 10 or higher.
Inquiry messages sent to *EXT: Monitors for inquiry messages sent to the Program Messages display. These messages are identified by having a message type of *INQ and sent to program *EXT.
To view or change the message filters, type a 9 next to an event monitor and press Enter. The Work with Message Filters display is shown.
For more information about working with Event Monitors and Message Filters, see the sections Reference: Working with Event Monitors and Reference: Working with Message Filters.
Job Queue Monitoring
Do you need to know if QBATCH has 10 jobs waiting? MessengerConsole and MessengerPlus can monitor the Work with Job Queues (WRKJOBQ) display for job queues that have a specified number of waiting jobs, are held/not held and perform the appropriate actions upon them, such as paging, releasing, moving to another job queue, and so on.
Setup1. Select option 5 from the Setup Menu.
2. If necessary, release JOBQ by typing a 6 next to it and pressing Enter.
3. Type a 2 next to JOBQ and press Enter.
4. Change information as needed. When completed, press Enter. The Work with Events Monitors screen will be displayed.
5. If necessary, release ‘Monitor for QBATCH 10 or more jobs’ by typing a 6 next to it and pressing Enter.
6. Type a 2 next to ‘Monitor for QBATCH 10 or more jobs’ and press Enter. The Event Monitor details screen will be displayed.
7. Change information as needed. When completed, press Enter. The Job Queue Options screen is displayed.
8. Change information as needed. When completed, press Enter until you return to the Work with Monitors screen.
Job Queue DetailsThe Job Queue Details display is shown automatically when you press Enter from the Event Monitor Details display when the monitor type is *JOBQ. This display allows you to define parameters for monitoring a job queue.
Job queueSpecifies the name of the job queue and library to monitor.
Number of jobsSpecifies the number of jobs that can be waiting in the job queue before an event is created. A positive value compares greater than or equal to. A negative value compares less than or equal to.
StatusSpecifies the status of the job queue.
Blank The status of the job queue is not monitored.
HLD The job queue is monitored for a held status. This value is useful to monitor when a job queue is held when it normally should be released.
RLS The job queue is monitored for a released status. This value is useful to monitor when a job queue is released when it normally should be held.
The values for Number of Jobs and Status are ANDed together, that is, if number and status are specified, then they both must be true to trigger the event.
90
Messenger V8R1M0
Output Queue Monitoring
Do you need to know if the system printer is held? MessengerConsole and MessengerPlus can monitor the Work with Output Queues (WRKOUTQ) display for output queues that have a specified number of spooled files, are held/not held and perform the appropriate actions upon them, such as paging, releasing, moving to another output queue, and so on.
Setup1. Select option 5 from the Setup Menu.
2. If necessary, release OUTQ by typing a 6 next to it and pressing Enter.
3. Type a 2 next to OUTQ and press Enter.
4. Change information as needed. When completed, press Enter. The Work with Events Monitors screen will display.
5. If necessary, release ‘Monitor for PRT01 50 or more files’ by typing a 6 next to it and pressing Enter.
6. Type a 2 next to ‘Monitor for PRT01 50 or more files’ and press Enter. The Event Monitor details screen will display.
7. Change information as needed. When completed, press Enter. The Job Queue Options screen is displayed.
8. Change information as needed. When completed, press Enter until back to the Work with Monitors screen.
Output Queue DetailsThe Output Queue Details display is shown automatically when you press Enter from the Event Monitor Details display when the monitor type is *OUTQ. This display allows you to define parameters for monitoring an output queue.
Output queueSpecifies the name of the output queue and library to monitor.
Number of spooled filesSpecifies the number of spooled files that can be in the output queue before an event is created. A positive value compares greater than or equal to. A negative value compares less than or equal to.
StatusSpecifies the status of the output queue.
Blank The status of the output queue is not monitored.
HLD The output queue is monitored for a held status. This value is useful to monitor when an output queue is held when it normally should be released.
RLS The output queue is monitored for a released status. This value is useful to monitor when an output queue is held when it normally should be held.
Ping Monitoring
Do you need to know when a PC server is down? Unlike the SNA environment, the IBM i does not generate an error message when TCP/IP devices are down. MessengerPlus can detect the up/down status of TCP/IP devices anywhere on your TCP/IP network, such as routers, firewalls, Windows 95/NT servers, Netware servers, and so on. If your IBM i is connected to the Internet, you can detect the status of virtually any device in the world. Simply define the host names or IP addresses and MessengerConsole and MessengerPlus will quietly interrogate those devices at regular intervals. If a device fails to respond, MessengerConsole and MessengerPlus will log an event and perform the specified actions, such as paging or emailing a network administrator.
91
Monitoring
Setup1. Ensure TCP/IP communications are configured and you are able to PING the hosts/devices you want to monitor.
2. Select option 5 from the Setup Menu.
3. Release the *TCP monitor by typing a 6 next to its name and pressing Enter.
4. Type a 9 next to the *TCP monitor and press Enter.
5. Press F6 to create a new Event Monitor. Type the following:
Sequence number: Start with 10 and increment by 10 for each additional Event Monitor you create.
Description: The name associated with the server.
Notify when: Specify *CHANGE to be notified when the status of the server changes from up to down or down to up.
Port: Specifying 0 will use ping to test the server, which tests to see if IP is running. Specifying a port number will test to see if a specific service is running on the server. For a list of common port numbers, press Help or contact your network administrator.
6. On the Verify TCP/IP Connection (PING) display, type the name of the remote system used in step 1, press Enter. For more information about the parameters available on the PING display, press Help.
7. Release the Event Monitor you have just created by typing a 6 next to it and pressing Enter.
8. Repeat steps 6 and 7 for each device you want to monitor.
9. MessengerPlus is preconfigured to send a pager message to the default pager. If you want to override this action, type a 7 next to the Event Monitor and press Enter. For more information about creating actions, see Working with Actions.
10. By default, the server will be monitored at all times (7x24). If you want to change the time periods, use option 2 to change the Event Monitor, then press F11 for schedule. For more information about schedules, see Working with Schedules.
PING DetailsThe PING Details display is shown automatically when you press Enter from the Event Monitor Details display when the monitor type is *TCP. This display allows you to define parameters for monitoring of TCP/IP devices.
For more information about the options available on this display, press Help. For additional options, press F10.
Remote systemSpecifies the name of the host to PING. To be successful, the name must be valid, and the remote system must be able to communicate with the local system. You can assign names to an internet address by using either of the following:
Work with Hosts Table menu, which is an option on the Configure TCP/IP menu (GO CFGTCP).
Remote name server to map a remote system name to an internet address.
Setting Up a Numeric Pager to Receive Event Notifications
MessengerPlus automatically sends the event text to an alphanumeric pager. However, if you are using a numeric pager you need to tell MessengerPlus what numeric code you want displayed on your pager when the event occurs.
Setting up a numeric code for each message would be very time consuming. Without the ability to see the text of a message, it would be difficult to memorize all the possible codes and what they mean. To overcome these problems, MessengerPlus allows you to specify a code at a Monitor level and at an Event Monitor (message) level.
Specifying a code at a Monitor level allows you to receive the same numeric code for all events occurring within the Monitor. For example, you could associate 999 with QSYSOPR, and whenever a monitored event occurs on QSYSOPR you would receive 999.
92
Messenger V8R1M0
There will be times when you want a specific code for a specific type of message. For example, you may want the code 110 displayed when a power failure occurs, or 998 for an inquiry message. MessengerPlus allows you to override the Monitor code at an Event Monitor (message) level. If you do not specify a numeric code for a specific Event Monitor then MessengerPlus will default to the Monitor numeric code instead. At a minimum, you should configure a numeric code for the Monitor, and optionally configure numeric codes for specific messages.
1. Configure and test your numeric pager using the instructions described in Chapter 7.
2. Select option 5 from the Setup Menu.
3. If you want to change the number displayed on your pager for all events associated with a monitor, type a 2 next to the monitor you want to change and press Enter. Press F10. Or, If you want to change the number displayed on your pager for a specific message, type a 9 next to the monitor and press Enter. Locate the event monitor you want to change and type a 7 next to it and press Enter.
4. You will either change or create a *PAGE action depending if an action already exists. If you see an existing *PAGE action, type a 2 next to it and press Enter. If ‘No data to display’ appears, press F6 to create a new one. Type 10 for ‘Sequence number’, *PAGE for ‘Action to perform’, and press Enter.
5. The Pager Message Details screen will appear. Type the numeric code you want in the ‘Numeric message’ field. Press Enter.
Troubleshooting
Monitored messages not appearing in Work with Events Log.Verify MessengerPlus is active: Go to the MessengerPlus Menu by typing MPLUS at a command line. Choose 51 Support menu, option 31: Work with MessengerPlus Processes. Verify the subsystem ZMPLUS is shown and the job MPLUS is listed. If necessary, return to the MessengerPlus Menu and choose option 1: Start MessengerPlus.
Choose 50 Setup menu, option 5: Work with Monitoring, verify the monitor is not held. Type a 6 next to the monitor, press Enter. Verify the Event Monitor you created to monitor for the condition is not held.
93
Actions
Chapter 9 - ActionsMessengerConsole and MessengerPlus can perform unlimited actions for an event. With Action Scripts, Action Escalation and Action Scheduling, you define how errors are responded to. You can create Actions to:
• Send pager and email messages.
• Send IFS attachments, system printouts, and joblogs with email messages.
• Send messages to users or workstations.
• Run CL commands.
• Send replies to automate routine messages.
• Send events to other servers.
• Reply to messages.
• Escalate unanswered messages.
• Send message, reply, or run a command when an event is acknowledged or reset.
Action ScriptingWhen a line fails do you vary it off and leave it off, or do you vary it off and back on again? MessengerConsole and MessengerPlus allow you to specify as many actions as needed to perform a task. This is important because in many cases you need more than one action to correct a problem. For example, you need 2 actions to recover from a failed line: one to vary the line off, and another to vary the line on again.
Substitution VariablesMessengerConsole and MessengerPlus allow you to pass parameters from the event to the action, such as the message ID, job name, and so on. You can use this information in your own event handling programs, or as part of an action that MessengerConsole and MessengerPlus will perform:
• &MT The text of the message. For non message events, the default text is assigned by MessengerPlus.
• &MQ The message queue name.
• &ML The message queue library name.
• &MI The message identifier.
• &MD The first 256 characters of the message data.
• &MJ The job name.
• &MU The user name.
• &MN The job number.
• &MK The 4 character message key.
• &MP The program name.
• &MV The severity code.
• &MY The message type code.
• &MH The first 256 characters of the message help.
• &MF The message file name.
• &MB The message file library name.
• &MS The name of the system the event originated.
Actions
94
Messenger V8R1M0
• &1 .. &99 The message data variable from the message description.
• \n Inserts carriage return into email messages. Use this to force a line break within the message body.
Example 1: Automate a CPI593D (line &23 failed) message by varying the line off and on:
VRYCFG CFGOBJ(&23) CFGTYPE(*LIN) STATUS(*OFF)
VRYCFG CFGOBJ(&23) CFGTYPE(*LIN) STATUS(*ON)
Example 2: Automate procedures to hold a job using 90% CPU and page an operator:
HLDJOB JOB(&MN/&MU/&MJ)
*PAGE TOPRG(QSYSOPR) MSG(‘Job &mn/&mu/&mj using 90% has been held’)
Action EscalationWhen a program is looping and filling a file, you wouldn’t endlessly answer the file full message with an “I” every time. If you did, the program would fill up all available disk and your system would probably crash. Yet many competing products do exactly that, blindly answering the same message with the same reply every time. You can configure limits on the number of times an action is run. This is important because you would never want to repeatedly run an action that is not correcting a problem. For example: you may want to send an “I” (Ignore) reply to a file full message, but after the third try within 60 minutes, send a “C” (Cancel) reply or notify a pager.
Action SchedulingWhen a job queue has too many jobs in it waiting to run, do you want a pager message every time, or just on weekends and during unattended processing? MessengerConsole and MessengerPlus give you the option to attach schedules to actions, so you can specify when actions are performed. For example, if a job queue is overloaded you can specify that a pager message is sent during unattended operations and a break message is sent during normal hours.
Action ShortcutsYou can create powerful time-saving shortcuts using abbreviated codes that run one or more actions. When you type the code next to an event, the actions associated with the code are performed. You can create user actions to execute commands, send pager messages, replies, escalate to other users and systems, and so on.
Example: Instead of typing: DSPJOBLOG JOB(123456/QSYSOPR/DSP01), you can create a shortcut command called JL to display the job log of the job with the error message.
Working with Actions
The Work with Actions display allows you to define actions to perform for events. Examples of actions are:
• Sending pager and email messages
• Sending replies
• Running commands
• Copying the event to an Event Queue
Actions can be specified at several levels, depending on when you want the actions performed. You can attach actions to:
• Monitors - Performs the specified actions whenever the monitor logs an event. For example, attaching a pager message action to the QSYSOPR monitor will send a pager message whenever a message you are monitoring for occurs on QSYSOPR. Actions attached to monitors can be considered default actions; they are performed only when there are no actions specified at the Event Monitor level.
95
Actions
• Event Monitors - Performs the specified actions whenever a specific event occurs. For example, attaching a reply action to a ‘Verify alignment’ Event Monitor will answer the message. When you specify an action at the Event Monitor level it overrides any actions specified at the monitor level (actions at the monitor level will not be performed).
• Event Queues - Performs the specified actions whenever an event is added to the Event Queue.
• User Actions - Performs the specified actions whenever the user action code is typed next to the event using the Work with Events display.
Using the Work with Actions display, you can:
• Add new actions to perform.
• Change the parameters of existing actions.
• Remove actions.
To attach actions to a monitor, using the Work with Monitors display, type a 2 next to the monitor you want to change, press Enter. Press F10.
To attach actions to an Event Monitor, using the Work with Event Monitors display, type a 7 next to the Event Monitor you want to change, press Enter.
To attach actions to an Event Queue, using the Work with Event Queues display, type a 2 next to the Event Queue you want to change, press Enter. Press F10.
To attach actions to action codes, using the Work with Events display, press F18.
If you want to: Do the following:Add a new action. Press F6.Change the parameter of existing action. Type a 2 next to the action you want to change, press Enter. Remove an action. Type a 4 next to the action you want to remove, press Enter.Add an alternate action to be performed only when the Limit settings have been exceeded.
Type a 7 next to the action you want to perform alternate actions for, press Enter.
Display or reset the usage data. The usage data shows you the last time and the number of times the action was performed since the last time it was reset.
Type a 2 next to the action you want to change, press Enter. Press F14. Press F14 again to reset.
Sequence numberThe sequence number of the action. MessengerPlus performs the lowest numbered actions first, starting at the top and working down the list.
ActionThe type of action to perform.
*ACK Acknowledges the event. Acknowledging an event removes the event from the Work with Events display, removes the event from all Event Queues and cancels any pending actions.
*COPY Copies the event to an Event Queue.
*CMD Runs a CL command.
*PAGE Sends messages to a pager, email, or workstation.
96
Messenger V8R1M0
*REPLY Sends a reply.
*RMV Removes the event from an Event Queue.
ParametersThe parameters of the action.
LimitThe maximum number of times the action is run within the specified time period.
DelayThe number of minutes to delay execution of the action.
Action Details
The Action Details display is used to define the parameters of the type of action you want to perform.
From the Work with Actions display, if you are adding a new action, press F6. If you are changing an existing action, type a 2 next to the action you want to change, press Enter.
If you want to: Do the following:Change the time periods the action is performed. Press F11. For more information about schedules, see Working
with Schedules.Display or reset the usage data. The usage data shows you the last time and the number of times the action was performed since the last time it was reset.
Press F14. Press F14 again to reset.
Sequence numberThe sequence number of the action. MessengerPlus performs the lowest numbered actions first, starting at the top and working down the list.
ActionThe type of action to perform.
*ACK Acknowledges the event. Acknowledging an event removes the event from the Work with Events display, removes the event from all Event Queues and cancels any pending actions.
*COPY Copies the event to an Event Queue.
*CMD Runs a CL command.
*PAGE Sends messages to pagers, email, Syslog servers, or workstation.
*REPLY Sends a reply.
*RMV Removes the event from an Event Queue.
DelaySpecifies the number of minutes to delay execution of the action and if you want the action canceled automatically when the event is acknowledged before the delay period has expired.
97
Actions
RepeatSpecifies the number of minutes before the action is repeated. The action will continue to repeat as specified until the event is acknowledged.
LimitSpecifies the maximum number of times to perform the action within the specified time period. For example, to limit the number of times to send a reply to a File full message to 3 times within 30 minutes, specify 3 for Number of times and 30 for Within minutes.
Page Action DetailsThe Page Action Details display allows you to define parameters for sending a message to pagers, email and workstations.
Pager nameThe name of the pager to receive the message.
*DFT If you are working with event actions, the pager name is the default pager name specified on the Monitor Details display. If you are working with Event Queue actions, the pager name is the default pager name specified on the Event Queue Details display or option 4 from the Setup Menu.
pager-name The name of the pager to receive the message.
Numeric messageThe message to send to numeric and telephone pagers.
Alpha messageThe message to send. You can type literal text and the following substitution variables that are automatically inserted by MessengerPlus when the event is logged:
&MT The text of the message. For non message events, the default text is assigned by MessengerPlus.
&MQ The message queue name.
&ML The message queue library name.
&MI The message identifier.
&MD The first 256 characters of the message data.
&MJ The job name.
&MU The user name.
&MN The job number.
&MK The 4 character message key.
&MP The program name.
&MV The severity code.
&MY The message type code.
&MH The first 256 characters of the message help.
&MF The message file name.
&MB The message file library name.
98
Messenger V8R1M0
&MS The name of the system the event originated.
&1 .. &99 The message data variable from the message description (valid for message events only).
\n Inserts carriage return into email messages. Use this to force a line break within the message body.
Example:Alpha message: Job &MN/&MU/&MJ received message &MI in program &MP.Results: Job 045680/QSYSOPR/TAP01 received message CPF0001 in program SAVALL.
Send replies (2-Way pager)Specifies if the message replies are retrieved from the IBM i message description (ADDMSGD command) and sent as Multiple Choice Responses to a 2-Way pager.
Escalation parametersSpecifies the number of times the message will be sent to the specified pager and time interval between pages. If the escalation parameters are blank and a pager list or pager schedule is specified, the escalation parameters specified on the pager list are used.
AttachmentsDisplays number of attachments that will be sent with email messages. To access the Work with Attachments display, press F10 from the Page Details display when you are changing a *PAGE action.
You can attach IFS stream files, and special values that will cause Messenger to send joblogs, active jobs, and system status reports. Possible values are:
path-name A user-specified IFS stream file path name (ie /home/user1/file.txt) that Messenger will send with the email. Please note the name should not contain quotes and must start with a slash ‘/’ character. Be sure the user profile MPLUSOWN has *X access to all directories in the path name and *RX authority to the file.
*JOBLOG Specifies that Messenger is to attach a job log for the job associated with the event.
*ACTJOB Specifies that Messenger is to attach a Work with Active Jobs (WRKACTJOB) text file.
*SYSSTS Specifies that Messenger is to attach a Work with System Status (WRKSYSSTS) text file.
Attachment size allowed is determined in the *SMTP Paging Company.
Attachments will be received as .txt files. Job logs that exceed 500KB will be delivered in a zip file.
Command Action DetailsThe Command Action Details display allows you to define parameters for running a CL command.
Command
The command to run. You can type literal text and the following substitution variables that are automatically inserted by MessengerPlus when the event is logged:
&MT The text of the message. For non message events, the default text is assigned by MessengerPlus.
&MQ The message queue name.
&ML The message queue library name.
&MI The message identifier.
&MD The first 256 characters of the message data.
&MJ The job name.
&MU The user name.
&MN The job number.
99
Actions
&MK The 4 character message key.
&MP The program name.
&MV The severity code.
&MY The message type code.
&MH The first 256 characters of the message help.
&MF The message file name.
&MB The message file library name.
&MS The name of the system the event originated.
&1 .. &99 The message data variable from the message description (valid for message events only).
Example:
Command: CALL PGM(CL1) PARM(&MI &23)
Results: CALL PGM(CL1) PARM(CPA5817 QESLINE)
MessengerPlus initializes the local data area with information about the event before running *CMD actions. This allows your program to retrieve the information from the *LDA as needed. For more information, see Local Data Area (*LDA) usage.
Reply Action DetailsThe Reply Action Details display allows you to define the parameters for sending a reply.
ReplyThe reply to send to an inquiry event.
*DFT The default reply stored in the message description of the inquiry message that was sent is sent as the reply.
Character-value Specifies the reply to send to an inquiry event.
Remove messageSpecifies whether the message is removed from the Work with Events display.
Y The message is removed from the display.
N The message is not removed from the display.
100
Messenger V8R1M0
101
Schedules
Chapter 10 - SchedulesWorking with Schedules
Using schedules, you can specify the days of the week and a starting and ending time period. For more complex scheduling, you can create schedules that contain a list of days and times. When you see F11=Schedule on any of the Messenger displays, you can press F11 to specify time periods when processing will be performed.
When you are working with: Schedules:Monitors Allow you to specify time periods the monitor is searching for events.Event Monitors Allow you to specify time periods the event is monitored.Actions Allow you to specify time periods the action is performed.Event Queue Lists Allow you to specify time periods that events are escalated to an Event
Queue.
To access the Work with Schedules display, choose option 9 from the Setup Menu. To access the Schedule Details display for a specific monitor, event monitor or action, press F11 from a display showing F11=Schedule.
If you want to: Do the following:Create a new schedule. Press F6.Change the parameter of existing schedule. Type a 2 next to the schedule you want to change, press Enter. Remove a schedule. Type a 4 next to the schedule you want to remove, press Enter.Copy a schedule to a new one. Type an 8 next to the schedule you want to copy, press Enter.Send a schedule to a remote system or distribution list
Type an S next to the schedule you want to send, press Enter.
ScheduleThe name of the schedule used for scheduling.
DescriptionThe optional description of the schedule.
Schedule DetailsThe Schedule Details display is shown when you are creating or changing a schedule.
From the Work with Schedules display, if you are creating a new schedule, press F6. If you want to change an existing schedule, type a 2 next to the schedule you want to change, press Enter.
ScheduleThe name of the schedule used for scheduling.
Schedules
102
Messenger V8R1M0
DescriptionThe optional description of the schedule.
Working with Schedule EntriesThe Schedule Entries display is used to define the time periods of the schedule.
From the Schedule Details display, press Enter.
If you want to: Do the following:Add new time periods to the schedule. Press F6, type the time periods you want to add, press EnterRemove time periods from the list. Space over the time periods you want to remove, press Enter
Include/ExcludeSpecifies if the time range is included or excluded from scheduling. In general, it is not necessary to use both include and exclude entries on the same schedule. You should use whichever creates the fewest entries. For example, to define a schedule for weekends only, it would be easier to create an Include entry for *SAT and *SUN than to create exclude entries for *MON, *TUE, *WED, *THU and *FRI.
I (Include) The time period is included in the schedule. All other time periods not explicitly included are implicitly excluded. For example, including Sunday would automatically exclude Monday through Saturday.
E (Exclude) The time period is excluded from the schedule. All other time periods not explicitly excluded are implicitly included. For example, excluding Sunday would automatically include Monday through Saturday.
Start date/day typeThe starting date or day type.
date The starting date of the schedule entry (MMDDYY).
day type The starting day type of the schedule entry. Valid day types are *SUN, *MON, *TUE, *WED, *THR, *FRI and *SAT.
End date/day typeThe ending date or day type. If you do not specify an ending date, the starting date is used.
date The ending date of the schedule entry.
day type The ending day type of the schedule entry. Valid day types are *SUN, *MON, *TUE, *WED, *THR, *FRI and *SAT.
Start timeThe starting time of each day during the schedule period in 24 hour format. For schedule entries that span several days, such as Monday through Friday, the start time refers to the starting time on each day, not the starting time for the first day only.
End timeThe ending time of each day during the schedule period in 24 hour format.
103
Schedules
Schedule Options
To access the Schedule Options display, press F11 from a display showing F11=Schedule.
If you want to: Do the following:Create a new schedule. Position the cursor on Schedule name, press F4. Press F6.
Days of the weekThe scheduled days of the week, starting with 1 for Sunday, 2 for Monday, 3 for Tuesday and so on. Multiple days are specified by typing the relative values of each day with no intervening spaces (246 = Monday, Wednesday and Friday, for example).
blank All days are scheduled.
days-of-week The scheduled days of the week:
1 Sunday
2 Monday
3 Tuesday
4 Wednesday
5 Thursday
6 Friday
7 Saturday
Starting/Ending timeThe scheduled starting and ending times.
ScheduleThe name of the schedule used for scheduling.
104
Messenger V8R1M0
105
Events
Chapter 11 - EventsThe Work with Events display shows you the events that have occurred on your system. If you are using the optional MessengerConsole™ module, the display can also include events from other IBM i systems. Newest events are shown at the top of the display with older events scrolling off the bottom. Unanswered events always remain at the top of the display until they are answered or acknowledged. Using the Work with Events display, you can:
• See the events that have occurred on your system. As new events occur, they appear on the screen automatically. Events are displayed using the attributes specified using the Event Monitor Details display, which allows you to specify settings for color, alarm, severity and message text.
• Send a copy of the event to another Event Queue. If you are using the optional MessengerConsole™ module, the event can be exported to another IBM i.
• Acknowledge an event to remove it from the display and all other displays with a copy of the event. If you are using the optional MessengerConsole™ module, the event is removed from all remote systems.
• Display the history of the event. The event history shows you when the event occurred, the actions that were performed and the users that have a copy of the event.
• Exclude the event from further monitoring, providing you are authorized to make changes to the monitor that logged the event.
• Display a subset of events, such as those from a specific job, user, and so on.
• Access the Work with User Actions display, which allows you to associate a 2-character option code with actions. The actions are performed when the option code is typed next to an event, similar to the IBM i Programming Development Manager (PDM). This allows you to create options to work with jobs, vary lines, send pager messages, and so on. User Actions greatly extend the capabilities of the Work with Events display by allowing you to create shortcuts to the commands you use most often to resolve problems.
Working with events
To access the Work with Events display, use MPLUS menu option 2 or run the MPLUS/WRKEVT command.
If you want to: Do the following:Refresh the display. Press F5.Acknowledge an event, removing it from all user’s displays and remote systems.
Type a 1 next to the event you want to acknowledge, press Enter. If the event occurred on a remote system, MessengerPlus will connect to the remote system and acknowledge the event on the remote system.
Send a copy of the event to another Event Queue. Type a 3 next to the event you want to copy, press Enter. If you are working with events from an Event Queue, you will have the option to either move or copy the event.
Display the details about the event and type a reply. Type a 5 next to the event you want to display, press Enter.Display the history of the actions that have been performed for an event.
Type an 8 next to the event you want to display, press Enter.
Exclude an event from further monitoring. Type a 9 next to the event you want to exclude, press Enter. If necessary, change any parameters shown, press Enter.
Display a subset of the events, such as those for a specific job, user, and so on.
Press F17, type your choices, press Enter.
Events
106
Messenger V8R1M0
To view event details press F11 and the following will be displayed:
MessageThe message or description of the event. You can customize the message text using the Event Monitor Details display.
SeverityThe severity of the event. You can customize the severity using the Event Monitor Details display.
StatusThe status of the event.
MSGW The event is waiting for a reply.
ACK The event has been acknowledged.
‘blank’ The event has not been acknowledged and is not waiting for a reply. You should acknowledge the event by typing a 1 next to it and press Enter.
Event Details
The Event Details display shows you the details about a specific event.
From the Work with Events display, type a 5 next to the event you want to display, press Enter
If you want to: Do the following:Acknowledge the event, removing it from the Work with Events display.
Press F10.
Enter a reply for an inquiry event. Type your reply, press Enter.Display the history of actions that have been performed for the event.
Press F11.
Change the details of the Event Monitor. Press F14.Display additional details about the event. Press Page Down.
Action History
Maintains a detailed audit trail of the actions performed. For any given event, you can quickly view the actions that were performed, the users that were notified, the replies that were entered, and so on.
107
Events
Working with User Actions
The Work with User Actions display allows you to define 2-character codes for frequently used actions, similar to the IBM i Programming Development Manager (PDM). When you type a User Action code next to an event on the Work with Events display, MessengerPlus runs the action on the specified event. You can specify substitution variables in your actions and MessengerPlus will automatically replace the substitution variables with the actual values taken from the event. You can set up user actions to:
• Vary a line off and on again for a line failure message.
• Send a pager message.
• Show the Work with Job Queue display for a job queue full event.
• Show the Work with Job menu for a job performance event.
• Hold a job and automatically release it after a specified number of minutes.
• Reduce the number of keystrokes for frequently run procedures.
• Automate recovery procedures for different types of events.
To work with User Actions, press F18 from the Work with Events display..
If you want to: Do the following:Add a new user action. Press F6. Type a user action code, sequence number and action type, press Enter.
For information about defining actions, see Working with Actions in this chapter. Change an existing user action. Type a 2 next to the user action you want to change, press Enter. Delete a user action. Type a 4 next to the user action you want to delete, press Enter.
User OptionThe identifier or abbreviated code of the user action.
Sequence numberThe sequence number of the action. MessengerPlus performs all of the actions with the same user action code starting with the lowest sequence numbers first, starting at the top and working down the list.
ActionThe type of action to perform.
*ACK Acknowledges the event. Acknowledging an event removes the event from the Work with Events display, removes the event from all Event Queues and cancels any pending actions.
*COPY Copies the event to an Event Queue.
*CMD Runs a CL command.
*PAGE Sends a pager message.
*REPLY Sends a reply.
*RMV Removes the event from an Event Queue.
108
Messenger V8R1M0
Working with Event Queues
The Work with Event Queues display allows you to manage Event Queues. Event queues are similar to message queues but are more powerful; they contain all types of events, not just messages. Additionally, Event Queues can:
• Break on your screen in more than one location at a time.
• Show events in colors and sound alarms.
• Can be distributed across a network of IBM i systems.
• Allow multiple users to access the same event. When an event is acknowledged, the event is automatically removed from all Event Queues.
• Run actions whenever a new event is added to the queue.
• Secure other users from displaying or changing events in the queue.
• Escalate to other Event Queues after a specified time period.
To access the Work with Event Queues display, choose option 6 from the Setup Menu, or type the command MPLUS/WRKEVTQ from a command line.
If you want to: Do the following:Create a new Event Queue. Press F6.Change the parameter of a existing Event Queue. Type a 2 next to the Event Queue you want to change, press
Enter. Add or change the actions performed when an event is added to the Event Queue.
Type a 2 next to the Event Queue you want to change, press Enter. Press F20. For more information about actions, see Working with Actions earlier in this chapter.
Delete an Event Queue. Type a 4 next to the Event Queue you want to remove, press Enter.
Work with the events in the Event Queue using the Work with Events display.
Type a 5 next to the Event Queue you want to display, press Enter. For more information about working with events, see Working with Events earlier in this chapter.
Event queue nameThe name of the Event Queue.
DescriptionThe description of the Event Queue. This field is for informational purposes only.
CountThe number of unanswered and unacknowledged events in the Event Queue.
109
Events
Event Queue Details
The Event Queue Details display is used to define the parameters and type of Event Queue.
From the Work with Event Queues display, if you are creating a new Event Queue, press F6. Type your Event Queue name, press Enter. If you are changing an existing Event Queue, type a 2 next to the Event Queue you want to change, press Enter.
If you want to: Do the following:Add or change the actions MessengerPlus will perform when an event is added to the queue.
Press F10. For more information about actions, see the Working with Actions section in this chapter.
Display or reset the usage data. The usage data shows you the last time and the number of times an event was added to the queue since the last time it was reset.
Press F14. Press F14 again to reset.
Event Queue nameThe name of the Event Queue.
DescriptionThe description of the Event Queue. This field is for informational purposes only.
TypeThe type of the Event Queue.
*EVTQ The Event Queue is a standard Event Queue that will contain events.
*LIST The Event Queue is a special Event Queue that contains a list of standard Event Queues. An Event Queue list is used to escalate events to other queues after a specified time period.
Authorization listSpecifies the name of the IBM i authorization list to secure changes to the Event Queue. If an authorization list name is specified, users must have *CHANGE authority to make changes to the Event Queue.
Default pager nameSpecifies for standard Event Queues only, the name of the pager to assign to pager message actions when a pager name is not specified. The default pager name is typically the owner of the Event Queue.
Send To SystemFor MessengerConsole, specifies the name of the system or group where events will be consoled.
110
Messenger V8R1M0
Event Queue Lists
The Event Queue List display is used to define the parameters for escalating events to one or more Event Queues after a period of elapsed time. By specifying the elapsed time periods and Event Queue names, MessengerPlus will automatically copy the event to the Event Queues at the appropriate times.
The Event Queue List display is shown automatically after the Event Queue Details when you specify *LIST as the Event Queue type and press Enter.
If you want to: Do the following:Add new entries to the Event Queue list. Press F6. Type the elapsed time and Event Queue name, press
Enter.Schedule an entry so events will escalate to it only during specific time periods.
Type a 2 next to the entry you want to schedule, press Enter. For more information about schedules, see Working with Schedules later in this chapter.
Elapsed minutesThe number of minutes since the event was created that must lapse before the event is copied to the specified Event Queue.
Event queue nameThe name of the Event Queue to copy the event after the specified elapsed number of minutes since the event was created. If you want to copy the event to more than 1 Event Queue, add an entry for each Event Queue you want and specify the same value on each entry for elapsed minutes.
Days of the weekThe days of the week to restrict when the event is copied to the specified queue.
blank The day of week is not used to restrict the time periods when the event is copied to the specified Event Queue.
days-of-week Specifies the days of the week, starting with 1 for Sunday, 2 for Monday, and so on, to restrict the time period when the event is copied to the specified Event Queue.
Start time/End timeThe starting and ending time period to restrict when the event is copied to the specified queue.
Schedule nameThe name of the schedule use to restrict when the event is copied to the specified queue.
111
MessengerConsole
Chapter 12 - MessengerConsoleIntroduction
In addition to all of the monitoring, filtering and notification features of MessengerPlus, MessengerConsole provides Event Consolidation and Monitor Distribution. Event Consolidation is the process of collecting events from multiple systems to a central location where they can be viewed and managed. This central location is called a Console. You can easily see the events that have occurred on remote systems and those waiting for a reply. Remote inquiry messages can be answered without the need to manually sign on to the remote system.
A major hurdle to automating remote monitoring is the amount of time and effort required to setup and maintain the remote monitoring software at each site. Even if you initially setup your remote systems by restoring the software from a pre-configured system, the ongoing maintenance becomes a major problem over time. MessengerConsole solves this problem by allowing you to create and maintain all of your monitoring setups from a single central system (the Console). Any changes you make from the central system can be synchronized with remote systems automatically. Once you have defined the events you want to monitor, you can distribute those definitions to remote systems without the need to manually recreate those setups for each and every system.
Benefits• Reduces the time and effort to maintain the remote monitoring software.
• Ensures consistency of the monitoring policies implemented on each system.
• Secures distributed monitors at the remote sites from being changed by remote users. All administration and maintenance must be performed from the Console. Remote users can continue to create new monitors of their own (providing they are authorized), but they will not be able to change or delete the monitors you distribute.
• Reduces the time and effort to monitor and diagnose problems on remote systems by providing a consolidated view of the events from all of your remote systems.
• Manage multiple remote servers from a central site, reducing the necessity for 24 x 7 technical staff at remote locations.
• Reduces downtime associated with unanswered remote messages by escalating these messages to the centralized Console.
• Reduces the cost associated with remote monitoring by dispatching pager messages or email alerts from the central system. You do not need V.24 ports, modems, phone lines, or connectivity to a mail server for each system.
Features• Remote monitoring and automation continues to run in real time while events are being transferred to the console
system, because the transferring of events is handled asynchronously by a separate batch process. Remote monitoring does not require or depend on continuous connectivity to the consoling system.
MessengerConsole
112
Messenger V8R1M0
• Remote events will queue when console connectivity is unavailable and will be automatically sent when connectivity is restored.
• An alternate console can be utilized to serve as a temporary console when the primary console is unavailable. The switching can be initiated from the primary console, the alternate console, or any system in the Messenger ‘network’.
• From the console you can easily define which events are automated at the remote sites and which events are sent to the console system for handling or automation.
• Events can be escalated to the central console after a specified period of elapsed time or during specific time periods. This allows a remote operator time to respond to an event. For remote unattended systems, the events can be escalated immediately.
• Events can be escalated to the central console after a specified threshold, such as after the third “I” reply to a file full message.
• Works with SNA and TCP/IP communications. The communication between systems is accomplished using Distributed Data Management (DDM) or TCP/IP sockets.
• Automatic Checking of Remote System Processes. MessengerConsole provides a command (works with SNA and TCP/IP) that allows you to determine if the required processes are running on one or more remote systems. You can run the command interactively, or automate the command to run at regular intervals to test the system communications. Status messages can be logged on both the sending and receiving systems, where they can be monitored for abnormal conditions and automated to appear on the console and/or notify an administrator by pager/email.
The ConsoleThe Work with Events display shows you the list of messages and events that have been logged from all your remote systems.
• Messages waiting for a reply are sorted to the top of the display and displayed in reverse image.
• Displays important messages in color and alarms.
• Answered and acknowledged messages are automatically removed from the console display, even if the reply occurs at a remote site.
• Allows replying to remote messages without signing on to the remote system.
• Automatically refreshes to show new events without pressing F5.
• Easily exclude unwanted messages from further monitoring.
• Subset events by system, event type, severity, and so on.
113
MessengerConsole
The Alternate Console MessengerConsole allows you to define a backup system, or alternate console. The alternate console can become the primary console at any time in the event of a failure or planned outage of the primary console.
• The Start System Redirection (STRSYSR) and End System Redirection (ENDSYSR) CL command can be easily integrated with a job scheduler or your custom CL program to start and end redirection at scheduled times.
• The redirection commands can be run from any system with Mes-senger installed in the event of unplanned downtime of the Primary Console.
• Remote systems will then redirect events to the Alternate Console instead of the Primary Console until redirection is ended.
• You do not have to run redirection commands from all remote systems, this is handled for you automatically once the redirection command has been issued.
Distribution Lists MessengerConsole allows you to group your remote systems into logical groups called Distribution Lists, which are simply groups of systems that you want to monitor in the same way - such as Production, Development, Manufacturing Plants, and so on. You can configure a monitor to run across a distribution list, and any changes you make to the monitor are automatically distributed to the systems in the list.
• A system can be a member of one or many lists.
• A distribution list is applied to a monitor.
Monitor Distribution Monitor Distribution is the process of distributing a set of policies (monitors) to one or more systems. Once you create your distribution lists, you specify the monitors that will use the distribution list. MessengerConsole will automatically distribute those monitors to the proper systems for you. Any future changes you make from the console to a distributed monitor will be automatically updated at the proper remote systems.
• Distribution occurs as a background process. If connectivity to a remote system is unavailable, the distributions will automatically queue until remote connectivity is restored.
• The distributed monitors can be protected from changes at the remote systems, ensuring integrity and security. If protected, all administration to a distributed monitor must occur from the console.
114
Messenger V8R1M0
How it Works The following high level diagram shows the processes involved in consoling a remote event.
Step 1 - An event occurs, such as an error message or critical job is not running.
Step 2 - The event is detected by an Event Monitor (which was previously defined at the console system and distributed to the remote system). The Event Monitor contains the filters that define the event, the actions to perform when the event occurs, and the name of the Event Queue (an Event Queue is simply a list of events/messages, similar to an email inbox).
Step 3 - If any remote Actions were defined for the Event Monitor (such as an automated reply, sending a pager or email message, running a command, and so on), they are performed on the remote system at this time.
Step 4 - If an Event Queue was specified, the Event is copied to the specified Event Queue. If the Event Queue is defined on the Console, the Event is transmitted to the Event Queue on the console system.
Step 5 - The Event appears on the Console.
Step 6 - If any console Actions were defined for the Event Monitor they are performed at this time (such as paging, emailing, running a command, and so on). If you are sending pager messages from the Console system they would be performed in this step.
Working with Systems
The Work with Systems display is used to create and manage the remote systems in your network that will receive events from MessengerConsole.
To access the Work with Systems display, choose option 7 from the Setup Menu.
If you want to: Do the following:Add a new system to MessengerConsole. Press F6, type the remote system name, press Enter.Change a system’s parameters. Type a 2 next to the system you want to change, press Enter.Remove a system from MessengerConsole. Type a 4 next to the system you want to remove, press Enter.Suspend transmission of events to a remote system. Type an 3 next to the system you want to hold, press Enter.Resume transmission of events to a remote system previously suspended.
Type a 6 next to the system you want to release, press Enter.
Start the job that sends events to the remote system. Type an 11 next to the system you want to start, press Enter.End the job that sends events to the remote system. Type a 12 next to the system you want to end, press Enter.Synchronize all Monitors for a single system or Distribution List
Type a 15 next to the system or list.
System nameThe name of the system. The system name can be determined using the Display Network Attributes (DSPNETA) command, and the same name must be used on all systems where it is identified within MessengerConsole.
115
MessengerConsole
TypeSpecifies the type of the system.
DescriptionThe description of the system. This field is used for informational purposes only.
CountThe number of events waiting to be sent to the remote system or being received by the local system.
StatusThe status of the process that communicates with the system.
DLYW The process is in a delay-wait status. This may be because there are no events to send.
RUN The process is sending events to the remote system.
STOP The process is not running.
EHLD The process has an error, preventing the systems from communicating.
HLD The system is held, preventing the systems from communicating.
System DetailsThe System Details display is used to define the parameters for the system.
From the Work with Systems display, if you are creating a new system, press F6. Type the system name, press Enter. If you are changing an existing system, type a 2 next to the system you want to change, press Enter.
System nameThe name of the system. The system name can be determined using the Display Network Attributes (DSPNETA) command.
System typeThe type of system which can include a console system that will distribute monitoring setups to the local system, the local system, or a remote system that will send console events to the local system and receive monitoring setups from the local system.
Alternate ConsoleSpecifies the name of the alternate system that events will be redirected to if the primary system is not accessible.
Socket PortThe port to use for the connection. Specify 0 if using DDM communications.
IP address/host nameThe IP address or host name of the remote system.
DDM keep alive timerThe elapsed time in HH:MM:SS of inactivity before MessengerConsole will end the session with the remote system. If the connection to the remote system is dial-up, the connection will be dropped. This parameter applies only to systems using DDM communications.
116
Messenger V8R1M0
Console System Setup
Define the *LOCAL system1. Setup monitoring and paging for the console system as desired.
2. From the MessengerConsole menu, choose option 7 from the Setup Menu.
3. If the *LOCAL system already exists, continue with the next step. Otherwise, skip to step 5.
4. Type 2 to change and press Enter. Press enter again to proceed to the System Details screen. Skip to step 6.
5. Press F6. Type the name of the local system, press Enter (the local system name can be determined using the Display Network Attributes (DSPNETA) command). Change ‘System type’ to *LOCAL, type Description, press Enter.
6. If you want remote systems to communicate with the console system using DDM, type 0 for socket, press Enter. If you want to use sockets, type the port number for socket, press Enter. The socket number must be a unique number not already being used by other TCP/IP applications on the system. You must specify the same port number on all your systems running MessengerConsole. You may need to check with your network administrator for help.
7. Start the local system process using option 11. If the local system process is already started, it will need to be restarted if any changes were made in step 6. To restart, use option 12 to stop, press F5 until the status changes to STOP, then start using option 11.
8. Press F5 and verify the status changes to DLYW. If the status is JOBQ, return to the MPLUS menu and choose option 1: Start MessengerPlus.
Define Remote Systems1. From the MessengerConsole menu, choose option 7 from the Setup Menu.
2. Press F6. Type the name of the remote system, press Enter (the remote system name can be determined using the Display Network Attributes (DSPNETA) command on the remote system).
3. Change ‘System type’ to *RMT, type Description, press Enter.
4. If the console system will communicate with the remote system using DDM, specify 0 for socket. If sockets will be used, type the port number for socket and the remote system’s IP address.
5. Press Enter.
6. If DDM was specified, the ‘Create DDM File (CRTDDMF) command will appear. Type the communications parameters as needed used to establish communications with the remote system (You can press Help for more information about parameters on this display or contact your Network Administrator). For SNA, you will need to specify the remote location name (same name used on STRPASTHR). For IP, type the host name or IP address and change the ‘Address type’ parameter to *IP. Press Enter.
7. Start the system by placing an 11 next to its name and pressing Enter. Press F5 and verify the status changes to DLYW.
8. Repeat steps 2 - 7 as needed for additional remote systems.
Remote System Setup
Define the *LOCAL system1. From the MessengerConsole menu, choose option 7 from the Setup Menu.
2. If the *LOCAL system already exists, continue with the next step. Otherwise, skip to step 4.
3. Type 2 to change and press Enter. Press enter again to proceed to the System Details screen. Skip to step 5.
117
MessengerConsole
4. Press F6. Type the name of the local system, press Enter (the local system name can be determined using the Display Network Attributes (DSPNETA) command). Change ‘System type’ to *LOCAL, type Description, press Enter.
5. If DDM is being used, type 0 for socket, press Enter. If you want to use sockets, type the port number for socket, press Enter. The socket number must be a unique number not already being used by other TCP/IP applications on the system. You must specify the same port number on all your systems running MessengerConsole. You may need to check with your network administrator for help.
6. Start the local system process using option 11. If the local system process is already started, it will need to be restarted if any changes were made in the previous step. To restart, use option 12 to stop, press F5 until the status changes to STOP, then start using option 11.
7. Press F5 and verify the status changes to DLYW. If the status is JOBQ, return to the MPLUS menu and choose option 1: Start MessengerPlus.
Define the *CONS System1. From the MessengerConsole menu, choose option 7 from the Setup Menu.
2. Press F6. Type the name of the console system, press Enter (the name must match the *LOCAL name used on the console system).
3. Change ‘System type’ to *CONS, type Description, press Enter.
4. If DDM is being used, specify 0 for socket. If sockets will be used, type the port number for socket and the remote system’s IP address.
5. If DDM was specified, the ‘Create DDM File (CRTDDMF) command will appear. Type the communications parameters as needed used to establish communications with the remote system (You can press Help for more information about parameters on this display or contact your Network Administrator). For SNA, you will need to specify the remote location name (same name used on STRPASTHR). For IP, type the host name or IP address and change the ‘Address type’ parameter to *IP.
6. Press Enter to return to the Work with Systems display.
7. Start the *CONS system by placing an 11 next to its name and pressing Enter. Press F5 and verify the status changes to DLYW.
Event Queue SetupOn the remote system, perform the following:
1. From the MessengerPlus menu, choose option 6 from the Setup Menu.
2. Change Event Queue QSYSOPR by typing a 2 next to its name and pressing Enter.
3. On the ‘Event Queue Details’ screen, press Enter.
4. On the ‘Event Queue Options’ screen, change ‘Send to system’ to the console system name, press Enter.
5. Press Enter to return to the MessengerPlus menu.
Testing connectivity
1. From the console system, use the Work with Systems display to verify all remote systems have a status of DLYW.
2. Test the connectivity to each remote system by typing a 14 in the option column next to a *RMT system and pressing Enter. If communications are established successfully, the message ‘System ... is OK’ will appear.
3. Repeat as necessary for all *RMT systems.
118
Messenger V8R1M0
Distributing a Monitor
MessengerConsole uses a distribution list to distribute a monitor to one or more remote systems. When you make changes to a monitor with a distribution list associated with it, MessengerConsole will distribute those changes to the systems in the group automatically. Distribution lists are only needed on the console system. The following instructions explain how to create a distri-bution list that includes all remote systems. You may need to create additional distribution lists needed for other logical groups of systems (such as development) if needed. A remote system can be used in as many distribution lists as needed.
Create a Distribution ListPerform the following on the Console system:
1. From the MessengerPlus menu, choose option 7 from the Setup Menu.
2. Press F6 to Add. Type ALL, press Enter.
3. Change ‘System type’ to *DSTL, type Description, press Enter.
4. The ‘Work with Distribution List Entries’ screen will appear. Press F6.
5. The ‘Add Systems to List’ screen will appear. You should see the console system and one or more remote systems. Type a 1 next to all of them, press Enter.
6. Press Enter to return to the ‘Work with Systems’ display.
7. Press Enter to return to the MessengerPlus menu.
If a Monitor is distributed and it has a schedule attached to it, a schedule of the same name must exist on each remote system where the Monitor will run. Otherwise, the Monitor will run anytime Messenger is active. You can easily send copies of schedules from the Console system to Remote systems. See Working with Schedules.
Distribute a MonitorOnce you have created the distribution list, you can then distribute the monitors.
Perform the following on the Console system:
1. Select option 5 from the Setup Menu.
2. Type a 2 next to the monitor you want to distribute (such as QSYSOPR), press Enter.
3. Press F22=Messenger Console Options.
4. Change the Distribution list parameter to ALL, press Enter.
5. Continue to press Enter until you return to the ‘Work with Monitors’ display.
6. Type an S next to the monitor name, press Enter. Press Enter again to confirm.
7. Return to the Setup Menu and choose option 7.
8. Press F5 periodically and verify the ‘Count’ column returns to 0.
9. On the remote systems, choose option 7 from the Setup Menu.
10. Press F5 periodically until the ‘Count’ column is 0.
11. Still on the remote system, choose option 5 from the Setup Menu and verify the distributed monitor appears, and the ‘Type’ is highlighted. This indicates the monitor has been distributed and is protected from changes. At this point the monitor is synchronized with the console.
Distribute Multiple Monitors to a Single System or Distribution ListTo distribute or resend multiple monitors to a single system or group of systems, perform the following on the Console System:
119
MessengerConsole
1. Select option 5 from the Setup Menu.
2. Type a 2 next to the monitor you want to distribute (such as QSYSOPR), press Enter.
3. Press F22=Messenger Console Options.
4. Change the Distribution list parameter to a single system or a Distribution List, press Enter.
5. Continue to press Enter until you return to the Setup Menu.
6. Take Option 7 from the Setup Menu.
7. Type 15 next to a system or list and press enter. Confirm and press Enter.
8. On the remote system, choose option 5 from the Setup Menu. Verify that the distributed monitor appears and the ‘Type’ is highlighted.
Excluding Systems from a Monitor Sometimes you will need to have different monitoring setups to accommodate system-unique requirements. For example, assume you have multiple systems in the ALL distribution list, and you have a distributed *JOBRUN monitor that checks for a critical system processes running on each system. If one of those systems is a development system which does not have the critical process, MessengerConsole would incorrectly notify you the process isn’t running.
To accommodate this scenario, you can specify a different distribution list for an Event Monitor:
1. Create a new distribution list that includes the group of systems without the systems you want to exclude.
2. Choose option 5 from the Setup Menu.
3. Type a 9 next to the monitor you want to change, press Enter.
4. Type option 2 next to the specific Event Monitor you want to change, press Enter.
5. Press F22=Messenger Console Options.
6. Type the name of the new distribution list, press Enter. Press Enter to return to the Work with Event Monitors display.
7. MessengerConsole will remove or add the Event Monitor to the appropriate remote systems.
Alternate Console Setup
MessengerConsole can redirect events to an Alternate Console system when there is a failure or planned outage of the Primary Console. For a planned outage, the Start System Redirect (STRSYSR) and End System Redirect (ENDSYSR) commands can be easily integrated with a job scheduler or your custom CL program to start and end redirection at scheduled times. In the event of unplanned downtime of the Primary Console, the redirection commands can be run from any system and all remote systems will be redirected.
On Primary Console system, perform the following:1. Choose option 7 from the Setup Menu.
2. Verify *LOCAL system exists and all remote systems (including Alternate Console) are listed as System Type *RMT.
3. Stop and restart all systems listed (Options 12 and 11) to confirm changes are effective.
On Alternate Console system, perform the following:1. Choose option 7 from the Setup Menu.
2. Verify *LOCAL system exists and all other remote systems are listed as System Type *RMT.
3. Verify Primary Console system is listed as System Type *CONS and Alternate Console field on the System Options screen specifies the name of the alternate system the events will be redirected to (*LOCAL system, in this case).
120
Messenger V8R1M0
4. Stop and restart all systems listed (Options 12 and 11) to confirm changes are effective.
On all other Remote systems, perform the following:1. Choose option 7 from the Setup Menu.
2. Verify *LOCAL system exists.
3. Verify Primary Console system is listed as System Type *CONS and Alternate Console field on the System Options screen specifies the name of the alternate system the events will be redirected to.
4. Press F6. Type the name of the Alternate Console system, press Enter. Change System Type to *CONS, type description, press Enter. Leave Alternate Console field blank. If DDM is being used, specify 0 for socket. If sockets are being used, type the port number for socket and the Alternate Console system’s IP address, press Enter.
5. Stop and restart all systems listed (Options 12 and 11) to confirm changes are effective.
Manual RedirectionTo start system redirection, on the alternate console system run STRSYSR SYSTEM(xxxxx) replacing xxxxx with the Primary system name. You can verify the redirect is in place by looking in Setup Menu option 7 on any of the remote systems and you will see ***Redirected to Alternate*** for the system’s description.
To end the system redirection, on either the Primary Console system or the alternate console system, run ENDSYSR SYSTEM(xxxxx) replacing xxxxx with the name of the Primary system that is now available again.
Testing
The following procedures will test your console setup to ensure it is working correctly.
On the console system, perform the following:1. Choose option 5 from the Setup Menu.
2. Type a 9 next to QSYSOPR, press Enter.
3. If sequence number 1100 is HLD, release it by placing a 6 next to in and pressing Enter. Press F3 until you return to the MPLUS menu.
On a remote system, perform the following:1. From the MPLUS Support menu, choose option 33: Simulate a system message.
2. For Message ID, type CPA0701. For Message queue, type QSYSOPR. Change Message type to *INQ, press Enter.
3. Choose option 5 from the Setup Menu.
4. Press F10. Press F5 periodically until the QSYSOPR monitor returns to DLYW.
5. Type a 5 next to QSYSOPR and verify the message “received by at (C D I R)” appears.
On the console system, perform the following:1. Choose MPLUS option 2: Work with Events.
2. Verify the message appears from the remote system (the system name is located on the second line below the message.
3. Type a 5 next to the event, press Enter. Type a reply and press F10.
On the remote system, perform the following:1. Display the QSYSOPR message queue (using the DSPMSG QSYSOPR command) and verify the message was replied to.
121
Downloading PTFs
Chapter 13 - Downloading Program Temporary Fixes (PTF)About PTFs
Bytware releases Program Temporary Fixes (PTFs) and/or enhancements to the product from time to time. To ensure you have the latest fixes and enhancements, you should update the product right after installing for the first time, and thereafter, we recommend that you automate program updates to take advantage of the latest program features as they become available.
Bytware PTFs are implemented the same as IBM PTFs. The Messenger product ID is 0MP2000, and you can run the command DSPPTF LICPGM(0MP2000) to see what PTFs are applied to the product. You can configure the product to download PTFs and apply them automatically, or you can simply download them manually on an as-needed basis. If you have multiple IBM i servers or partitions, you can configure each system to automatically download PTFs individually, or use System i Navigator Management Central to automatically distribute PTFs throughout your network (not discussed in this guide).
Messenger is pre-configured to download PTFs directly from Bytware’s FTP server using anonymous FTP.
Setup
The Change Update Attributes (MPCHGUPDA) and Run Update (MPRUNUPD) commands are used to configure and run PTF processing. To configure settings, use Support menu option 10 or type the command MPLUS/MPCHGUPDA and press F4.
You must run the command as a user with *ALLOBJ authority (such as QSECOFR).
Transfer method (FROM)
Specifies the transfer method that will be used to retrieve the files.
*FTP The data will be downloaded from an FTP server using the File Transfer Protocol (FTP).
*PATH The data will be retrieved from a network path. The path option is typically used in a network environment where you have one or more IBM i servers downloading from an FTP site and saving to a local path. This improves performance and security by using one server or partition to download the files to a secured share. The remaining servers or partitions can use this option to access the files over the local network.
Remote System (RMTSYS)
Specifies the name or IP address of the remote FTP server.
*DFT The default FTP server bytware.com will be used.
name Specifies the name or IP address of the FTP server.
FTP User (FTPUSER)
Specifies the user name to use when logging into the FTP server. This option applies only if the RMTSYS parameter is not *DFT.
user name Specify the remote user name for the FTP server login.
Downloading PTFs
122
Messenger V8R1M0
FTP Password (FTPPWD)
Specifies the password for the remote user name when logging into the FTP server. This parameter applies only if the RMTSYS parameter is not *DFT
The password is stored unencrypted in file MPPAU. The file is shipped with public *EXCLUDE authority. The password is sent to the FTP server unencrypted.
Path (PATH)
Specifies the network path name that will be used to retrieve the files. This parameter applies only if the RMTSYS parameter is not *DFT, or the FROM parameter is *PATH.
‘/’ The root path is used to located the update files.
path-name Specify the path name to locate the update files.
Schedule (SCHEDULE)
Specifies the type of scheduling for the command or process.
*DAILY Run automatic upgrade every day (recommended).
*WEEKLY Run automatic upgrade once per week.
*MONTHLY Run automatic upgrade once per month.
*NONE Automatic upgrade is disabled. This setting is not recommended unless you choose to handle automatic upgrading outside the product.
Note: When you specify a schedule and press Enter, the product adds the job schedule entry MPRUNUPD using the ADDJOB-SCDE command.
Day, Days, Time
Specifies the specific time period for the automatic upgrade process to run, depending on the choice selected for Schedule. For more information on the values allowed for these parameters, press Help.
Save path (SAVEPATH)
Specifies the path name to save the retrieved update files.
*NONE The update files are not saved.
path-name The update files are copied to the specified path name.
Run command (RUNCMD)
Specifies the command name to run after a successful update.
*NONE A command is not run after an update.
command-string The specified command string is run automatically after a successful update.
123
Downloading PTFs
Example
To schedule an automatic upgrade to run once per week:
MPCHGUPDA FROM(*FTP) RMTSYS(*DFT) SCHEDULE(*DAILY) SCHEDDAYS(*WED) SCHEDTIME(083000)
To manually run an upgrade, choose option 11 from the Support Menu or type the command MPRUNUPD and press Enter.
MPRUNUPD
Troubleshooting
• Run the command FTP BYTWARE.COM from a command line. Verify you are able to connect and log in with user anonymous. Run a dir command to verify passive ftp is working. Get assistance from your network administrator if possible.
• If the connection message is similar to “Cannot connect to host BYTWARE.COM . Try again later.“, you either have a firewall blocking FTP traffic from your IBM i, or no default route configured. You can check your default route using the command CFGTCP, option 2. Typically the default route is the IP address of your firewall or router. Consult with your security or system administrator.
• If the connection message is similar to “Cannot find host BYTWARE.COM”, then most likely DNS is not configured or misconfigured. Use CFGTCP, option 12 and verify your Domain Name Server settings. Consult with your network administrator. You may be able to use the same value as your PC’s - For Windows PCs go to a dos window and type ipconfig /all. Cross reference the DNS server IP address with the values specified in CFGTCP option 12.
• Use Support Menu option 13 to view the output from the FTP process. Review the log for error messages. Contact Bytware Technical support, if necessary.
• You can check the status of updates that have been installed and applied using Support menu option 13.
Recommendations
• Do not hardcode the IP address of BYTWARE.COM in any scripts or firewalls. The IP address of BYTWARE.COM could change at any time.
• If you have multiple IBM i servers or partitions with Messenger installed, we suggest configuring one system or partition to retrieve program upgrades from the default path and save the files to a shared path on the local network. On the remaining systems and partitions, use the PATH options to retrieve the upgrades over the local network.
• You can use System i Navigator’s Management Central to distribute PTFs throughout your network. For more information, got to the iSeries Information Center and search for “management central manage fixes”.
124
Messenger V8R1M0
125
Appendix
Chapter 14 - AppendixAnalyzing QHST Messages
MessengerPlus contains a utility to analyze your system history logs (QHST) and display the number of occurrences of messages. This utility is useful in assisting you in determining the QHST messages you want to monitor.
To access the QHST analyzer utility, choose Reports Menu option 3 from the MPLUS menu.
If this is the first time running the utility, the message ‘No data to display’ will appear at the bottom.
Press F6 to start analyzing QHST. Change options as necessary, press Enter. Note: The analysis process reads through all of the QSYS/QHST* files interactively. This could be a long running process. You must have sufficient authority to the QSYS/QHST* files (QSYSOPR or *ALLOBJ).
Once the data is displayed, you can use the severity column to identify the number and types of messages you would receive at different severity levels. The Message ID column can be used to identify specific messages to include or exclude from monitoring.
Changing the date format
You can change the format MessengerPlus uses to display dates by changing the data area Y2DTFMA in library MPLUS to one of the following:
MDY: Month/Day/Year
DMY: Day/Month/Year
YMD: Year/Month/Day
Changing the system date/time
MessengerPlus processes messages by time. The date and time of the last message is saved, and only new messages appearing after the date and time of the last saved message are monitored. If you need to change the system date or time back (such as for Daylight savings), complete the following steps:
1. End MessengerPlus using the MPLUS/ENDMP command.
2. Set the date and/or time to the desired time.
3. Clear the messages from the message queues being monitored using the CLRMSGQ command (or F13/F16). If you do not clear the messages, MessengerPlus will re-monitor the messages in the queue after the time is set back.
4. Start MessengerPlus using the MPLUS/STRMP command.
If you do not follow the above steps, MessengerPlus may pick up old messages again, or fail to pick up messages until the previous date and time setting is reached.
Appendix
126
Messenger V8R1M0
Command APIs
The following commands may be used to interface your applications with MessengerPlus.
Be sure to have MPLUS in your library list before running the command. You can also qualify the command by typing MPLUS/ and the command name.
Command DescriptionABOUT Displays information about MessengerPlus, such as the distributor contact information and release level.ENDMON Ends the Monitor.ENDMP Ends MessengerPlus’ subsystem, Paging Queues, and message monitor.ENDPGRQ Ends a Paging Queue.HLDEVTMON Holds an Event Monitor.HLDMON Holds a monitor from monitoring.HLDPGR Holds a pager.MPLUS Displays the MessengerPlus Menu.PGMMSG Send a program message.RLSEVTMON Releases an Event Monitor.RLSMON Releases a held monitor.RLSPGR Releases a held pager.SNDPGRMSG Sends a message to a pager, email, and workstation.STRMON Starts the Monitor.STRMP Starts MessengerPlus’ subsystem, Paging Queues, and message monitor.STRPGRQ Starts a Paging Queue.STRRSMP Start Restricted State Monitoring and Paging.WRKMON Shows the Work with Monitors display.WRKEVT Shows the Work with Events display.WRKPGR Shows the Work with Pagers display.WRKPGRC Shows the Work with Paging Companies display.WRKPGRMSG Shows the Work with Pager Messages display.WRKPGRQ Shows the Work with Modems display.WRKSYS Shows the Work with Systems display.
Configuring the Attention key pop-up window
To access the Send Pager Message window by pressing the Attention key, choose one of the following methods:
1. To change a single user, enter the following command: (replacing XXX with the user profile name):
CHGUSRPRF USRPRF(XXX) ATNPGM(SNDPGRMSG)
127
Appendix
2. To change a single job, enter the following command (or add to a CL program):
SETATNPGM PGM(SNDPGRMSG)
3. To change all users on the system, enter the following command:
CHGSYSVAL SYSVAL(QATNPGM) VALUE('SNDPGRMSG')
Entering your security code
Use MPLUS menu Option 53 and add the license key.
Local Data Area (*LDA) usage
Messenger initializes the Local Data Area (*LDA) with data about the event before running command (*CMD) actions. You can retrieve event information from the local data area using the RTVDTAARA DTAARA(*LDA) command. The following table describes the type of data available to be retrieved:
Starting Position
Character Length
Description
6 10 Message queue name16 10 Message queue library26 7 Message ID37 10 Message file47 10 Message file library61 10 Job name71 10 User name81 6 Job number87 10 Program
103 7 Date - CYYMMDD110 6 Time - HHMMSS116 2 Severity 00 - 99118 2 Message type120 8 System name128 4 Message key132 2 Event type146 512 Message data658 256 Message text
128
Messenger V8R1M0
Example:
PGM /* Sample program to retrieve event data from the *LDA */
DCL VAR(&DATE) TYPE(*CHAR) LEN(7)
DCL VAR(&TIME) TYPE(*CHAR) LEN(6)
DCL VAR(MSGTXT) TYPE(*CHAR) LEN(256)
DCL VAR(&SEV) TYPE(*CHAR) LEN(2)
DCL VAR(&MSGID) TYPE(*CHAR) LEN(7)
RTVDTAARA DTAARA(*LDA (103 7)) RTNVAR(&DATE)
RTVDTAARA DTAARA(*LDA (110 6)) RTNVAR(&TIME)
RTVDTAARA DTAARA(*LDA (116 2)) RTNVAR(&SEV)
RTVDTAARA DTAARA(*LDA (658 256)) RTNVAR(&MSGTXT)
RTVDTAARA DTAARA(*LDA (26 7)) RTNVAR(&MSGID)
/* other program statements */
ENDPGM
Removing MessengerPlus from your system
To remove MessengerPlus from your system, run the following commands:
1. DLTLICPGM 0MP2000
2. DLTUSRPRF USRPRF(MPLUSOWN) OWNOBJOPT(*DLT)
Security and *PUBLIC authority
OwnershipAll objects created or installed as required for the application are owned by the user profile MPLUSOWN. This profile is created during installation, has no password, and cannot be used to sign on to the system. The public authority to this profile is *EXCLUDE. The special authority *IOSYSCFG is granted for the purposes of configuring communications objects as needed by the application.
129
Appendix
Public AuthorityExcept for the objects listed in the table below, the public is excluded from accessing the application. You must grant specific users the appropriate privileges (explained in the following section) before they can access the application.
Object Library Type Public authorityMPLUS QSYS *LIB *USESNDPGRMSG MPLUS *CMD *USE
The public authority for the MPLUS library is set to *USE so the above commands can be used by public users.
Adopted AuthoritySeveral programs within the MPLUS library adopt the MPLUSOWN authority. This is required so the application can access its own data files and does not present any security exposure. No programs adopt any other profile’s authority. The public authority to all programs that adopt authority is set to *EXCLUDE, and are controlled using an authorization list (below). To see the list of programs that adopt the MPLUSOWN profile, run the following command: DSPPGMADP USRPRF(MPLUSOWN).
Authorization ListDuring installation the authorization list MPLUSAUTL is created. All programs that adopt owner authority are controlled using this authorization list. To see a list of objects secured by the authorization list, run the following command: DSPAUTLOBJ AUTL(MPLUSAUTL).
Adding and/or removing user’s ability to use and configure MessengerPlusWith exception of the SNDPGRMSG command, all users without *ALLOBJ authority are by default excluded from using or configuring the application.
To add a user to the list of user’s that are authorized to use and configure the application, run the command: ADDAUTLE AUTL(MPLUSAUTL) USER(user-name)
To remove a user from the list, run the command: RMVAUTLE AUTL(MPLUSAUTL) USER(user-name)
To edit the list of authorized users, run the command: EDTAUTL AUTL(MPLUSAUTL)
Please note that while it is not necessary to add users with *ALLOBJ authority to the authorization list, it is a good idea for documentation purposes. However, removing a user with *ALLOBJ authority from the list will not prevent them from accessing the application.
The authorization list does not distinguish between use or change. If a user is on the authorization list as either *USE or *CHANGE, they will be able to change the product’s settings.
Starting MessengerPlus automatically at IPL
Upon installation, an autostart job entry is created in your controlling subsystem to start MessengerPlus automatically after a system IPL. If you choose to remove the autostart job entry you can add the following command to your startup program: MPLUS/STRMP. It is recommended to add the MPLUS startup after TCP/IP startup.
130
Messenger V8R1M0
Using MessengerPlus with Job SchedulersIBM Job Scheduler
1. Type GO JS, press Enter.
2. Choose option 5: System controls.
3. Choose option 6: Change pager command.
4. Type the following including quotes: ‘MPLUS/SNDPGRMSG TOPGR(&RCP) MSG(‘’&MSGTXT’’)’
5. Press Enter.
6. Press F12 to return to the Job Scheduler menu.
7. Choose option 4: Job controls.
8. Choose option 1: Change/Work with job defaults.
9. In the ‘Recipient abnormal’ field, type your pager name.
10. In the ‘Message’ field, type *COMP.
11. Press Enter.
12. Press F3 to exit the Job Scheduler.
Other job schedulersA standard feature in most job schedulers is a ‘reactive’ or ‘alternate’ job that is executed if the dependent job ends in error.
Create a reactive job that runs the command MPLUS/SNDPGRMSG specifying the appropriate information based on the dependent job. This way, if the dependent job fails, the job scheduler will run MessengerPlus’ SNDPGRMSG command, which sends you a pager message.
Bytware Technical Support
ANNUAL SUPPORT CONTRACTS: Annual Support Contracts are optional and may be purchased for each copy of the software you have purchased, and may be renewed annually. Annual Support includes email and voice support, problem determination, problem logging, and problem resolution as is technically feasible, as well as PTFs, release updates, and new versions for each copy of the Software that has current Annual Support. Annual Support does not include hardware change fees, or transfers. Software PTFs, release updates and new versions are provided upon Purchaser’s request only.
If you decline the Annual Support Contract at time of purchase and/or at time or renewal, support and/or upgrade fees will apply at time of any support or upgrade request (for current fees please contact your Bytware Sales Representative).
Purchase, support and upgrade fees are subject to change without notice.
Before calling, please take a moment to collect the following information:
• The version of operating system you are running.
• Write down any error messages you’ve received, and a brief description of the problem. The best way to accomplish this is DSPJOBLOG OUTPUT(*PRINT). If the error message is from another job, use DSPJOBLOG JOB(xxx) OUTPUT(*PRINT), replacing the xxx with the job name.
• If you are having a modem communications problem, have the make and model of your modem available. Be prepared to put your phone as close to the modem as possible.
131
Appendix
Contacting Bytware:Phone: 800-932-5557 or +1-775-851-2900
FAX: +1-775-851-2997
Internet: http://www.helpsystems.com/bytware
Email: [email protected]
132
Messenger V8R1M0
133
Index
IndexIndexSymbols*LDA Usage ....................................................................... 127*ROUTER Queue ................................................................. 20
AAccounting code ..................................................... 74, 76, 80Action ................................................................................... 1Action Details ..................................................................... 96Action Escalation ................................................................ 94Action History ................................................................... 106Actions ............................................................................ 4, 93
Working with .............................................................. 94Action Scheduling ............................................................... 94Action Scripting .................................................................. 93Action Shortcuts ................................................................. 94Adopted Authority............................................................ 129Alpha Pager ........................................................................ 34Alternate Console ............................................................. 113Alternate Console setup ................................................... 119Attachments
To email messages ...................................................... 98Attention key pop-up window
Configuring ............................................................... 126Audit Journal Entry Types ................................................... 69Audit Journal Monitoring ................................................... 62Authority
Adopted .................................................................... 129Public ........................................................................ 129
CChanging
Date Format .............................................................. 125System Date/Time .................................................... 125
Command Action Details .................................................... 98Command APIs ................................................................. 126Console setup, alternate .................................................. 119Console system setup ....................................................... 116Contacting Bytware .......................................................... 131CPU Monitoring .................................................................. 72CPU percentage .................................................................. 55
DDate Format
Changing ................................................................... 125Disk Monitoring .................................................................. 72Distributing
Monitor .................................................................... 118Distribution Lists
MessengerConsole ................................................... 113Downloading Program Temporary Fixes ........................... 121
EEmail
2-Way ......................................................................... 30Attachments ............................................................... 98
Escalation ............................................................................. 6Event ..................................................................................... 1Event Consolidation .............................................................. 8Event Details ..................................................................... 106Event Monitor Details ......................................................... 60Event Monitors ................................................................... 58Event Queue Details ......................................................... 109Event Queue Lists ............................................................. 110Event Queues ................................................................... 108
Working with ............................................................ 108Events ........................................................................... 4, 105
Working with ............................................................ 105
FFeatures
Actions .......................................................................... 4Escalation ..................................................................... 6Event Console ............................................................... 4Events ........................................................................... 4Monitors ....................................................................... 3Paging and Notification ................................................ 5QHST Analyzer .............................................................. 6Reply Management ...................................................... 6Reporting ...................................................................... 6Scheduling .................................................................... 6Security ......................................................................... 6Usages .......................................................................... 7
Filter ..................................................................................... 1
GGlossary of terms ................................................................. 1Group Pagers ...................................................................... 31
IIBM Internal Modem .......................................................... 22ICF
Date and Time ............................................................ 21Operation ................................................................... 21Return code ................................................................ 21Working with .............................................................. 20
Installation ............................................................................ 9From the Web ............................................................. 10Obtaining pagers .......................................................... 9Requirements ............................................................... 9
Installing Messenger............................................................. 9
134
Messenger V8R1M0
JJob log Monitoring ............................................................. 88Job Queue Monitoring ....................................................... 89JOBRUN Monitoring ........................................................... 87Job Start or Complete Monitoring ...................................... 82Job Status monitoring ......................................................... 83Journal Details .................................................................... 65Journal Filter Details ........................................................... 67
LLine Status Monitoring ....................................................... 73Local Data Area Usage ...................................................... 127
MMessage Filter Details ........................................................ 78Message Filters
Working with .............................................................. 76Message ID ............................................................. 77, 78, 82Message Queue Monitoring ............................................... 74Message type ................................................... 74, 76, 77, 79MessengerConsole ........................................................... 111MessengerPlus Menus ....................................................... 11Modem
ASYNC ......................................................................... 18AUTOSYNC .................................................................. 18Description ................................................................. 18DSR setting ................................................................. 18Initialization string ...................................................... 19Line name ................................................................... 18NULL ........................................................................... 18Reset string ................................................................. 19Resource name ........................................................... 18type ............................................................................ 18V250 ........................................................................... 18
Modem Configuration ........................................................ 17Modem Details ................................................................... 18
Non-switched Options ................................................ 19Switched Options ....................................................... 18
Modem Pooling .................................................................. 31Modem Setup ..................................................................... 17
IBM 7852-400 ............................................................. 22IBM Internal Modem .................................................. 22MultiTech MultiModem GPRS Wireless Modem ........ 22Other .......................................................................... 24Testing ........................................................................ 24
Monitor ................................................................................ 1Distributing ............................................................... 118
Monitor Details .................................................................. 57Monitor Distribution
MessengerConsole ................................................... 113Monitoring ......................................................................... 55
Audit Journal .............................................................. 62CPU ............................................................................. 72
Disk ............................................................................. 72Job log ........................................................................ 88Job Log ........................................................................ 88Job Queue................................................................... 89JOBRUN ...................................................................... 87Job Start or Complete ................................................. 82Job Status ................................................................... 83Line Status .................................................................. 73Message Queue .......................................................... 74Output Queue ............................................................ 90Ping ............................................................................. 90
Monitors ............................................................................... 3Working with .............................................................. 55
PPager .................................................................................... 1Pager Authorities ................................................................ 40Pager Details ....................................................................... 33
Description ................................................................. 33Name .......................................................................... 33Public authority .......................................................... 33Type ............................................................................ 33
Pager List Options ............................................................... 39Pager Message
Error Codes ................................................................. 51History ........................................................................ 48Troubleshooting.......................................................... 49
Pager MessagesWorking with .............................................................. 47
Pager OptionsAlpha .......................................................................... 34Email ........................................................................... 34Message Queue .......................................................... 35Numeric ...................................................................... 35Phone ......................................................................... 35SMS ............................................................................. 37SNMP .......................................................................... 36
PagersDefault ........................................................................ 15Working with .............................................................. 32
Pager Security ..................................................................... 32Pager Setup
Alpha .......................................................................... 41Email ........................................................................... 42Numeric ...................................................................... 41Phone ......................................................................... 42POP3 ........................................................................... 43Skytel 2-way ............................................................... 44SMTP .......................................................................... 42
Paging ................................................................................. 292-Way ......................................................................... 29Alphanumeric ............................................................. 29Message Formatting ................................................... 31
135
Index
Numeric ...................................................................... 29Shares ......................................................................... 31Telephone ................................................................... 30
Paging and Notification ........................................................ 5Paging Companies .............................................................. 25
Details ......................................................................... 26Working with .............................................................. 25
Ping ............................................................................... 55, 90PING Details ........................................................................ 91Pre-Configured Monitors ...................................................... 7Public Authority ................................................................ 129
QQHST Analyzer ...................................................................... 6QHST Messages ................................................................ 125
RRemote system setup ....................................................... 116Reply Action Details ............................................................ 99Reply Management .............................................................. 6Reporting .............................................................................. 6
SSchedule Details ............................................................... 101Schedule Entries ............................................................... 102Schedule Options ............................................................. 103Schedules ......................................................................... 101
Working with ............................................................ 101Scheduling ............................................................................ 6Security ................................................................................. 6
and *PUBLIC Authority ............................................. 128Setup
Alternate Console ..................................................... 119Console system ......................................................... 116Remote system ......................................................... 116Testing ...................................................................... 120
Severity ................................................. 61, 74, 75, 76, 77, 79SNDPGRMSG ...................................................................... 46SNPP
Options ....................................................................... 37Pager setup ................................................................. 44
Sts ................................................................................. 57, 59Substitution Variables ......................................................... 93
SYSLOGOptions ....................................................................... 38
System date/timeChanging ................................................................... 125
System Default Pager Setup ............................................... 62System Options ................................................................... 15
TTesting Console setup ....................................................... 120Testing your modem ........................................................... 24
UUsages .................................................................................. 7User Actions
Working with ............................................................ 107
WWorking with
Actions ........................................................................ 94Event Monitors ........................................................... 58Event Queues ........................................................... 108Events ....................................................................... 105Job Filters.................................................................... 83Journal Filters ............................................................. 66Message Filters ........................................................... 76Modems ..................................................................... 17Monitors ..................................................................... 55Pager Message History ............................................... 48Pager Messages .......................................................... 47Pagers ......................................................................... 32Paging Companies ...................................................... 25Schedule Entries ....................................................... 102Schedules ................................................................. 101Systems ..................................................................... 114User Actions ............................................................. 107
WRKEVT ............................................................................ 126WRKMON ......................................................................... 126WRKPGR ........................................................................... 126WRKPGRC ......................................................................... 126WRKPGRMSG ................................................................... 126WRKPGRQ ........................................................................ 126WRKSYS ............................................................................ 126
136
Messenger V8R1M0
