Call us at 1-866-559-0800

 IBM® Systems Management Specialists...

Click here

The IBM logo and the Business Partner emblem are trademarks of International Business Machines Corporation in the United States, other countries, or both.

Quick Start

Notice

Installation

   Prepare to Install

   Software Installation
   Configure service provider connection
      E-mail connection
      Modem connection

Testing the Installation

   Monitor the QSYSOPR Message Queue

Daily Operations

Completing the Setup

Contact Information

This guide and the software are copyrighted by DDL Systems Consulting, Inc. All rights reserved. The software and this manual are furnished under a license agreement and may be used or copied only in accordance with the terms of this agreement. It is against the law to copy the software, except as specifically allowed in the license agreement. No part of this manual may be reproduced or transmitted in any form, by any means - electronic or mechanical (including photocopying and recording) - or for any purpose, without the express written permission of DDL Systems Consulting, Inc.

The documentation and the software are provided as is without warranty of any kind - either expressed or implied - including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.

This guide could include technical inaccuracies or typographical errors. Changes are periodically made to the product and information herein; these changes will be incorporated in new editions of this publication. DDL Systems Consulting, Inc. reserves the right to make improvements to the product described in this guide at any time and without notice.

ACO PAGER™, ACO NET™, ACO ESI™, and ACO CLIENT™ are trademarks of DDL Systems Consulting, Incorporated. All other products are registered trademarks or trademarks of their respective manufacturers.

Return to table of contents

Installation

This guide is designed to help you quickly install or upgrade ACO PAGER™ on your iSeries (or AS/400) computer system. Use this guide to install and test the software. Once you have completed all of the sections, refer to the Guide to Operations manual for more detailed information on using various product features.

If you are upgrading the software, you only need to perform the steps listed in the Software Installation section. Click here to go there now.

Before you begin installing ACO PAGER™, please ensure the following installation requirements are satisfied:

• At least 50 megabytes of available DASD
• A functional tape or CD-ROM drive
• Access to a workstation that is authorized to the QSECOFR user profile
• OS/400 Version 5 Release 1 or higher

2. Verify that the programmer user profile (QPGMR) exists on your iSeries system and you have access to the master security officer (QSECOFR) password. All ACO PAGER™ objects on the distribution media are owned by the QPGMR user profile.

3.  As a service to you, our SupportLine will test your pager (or cellular phone) and send you the correct set up of the Work with Pagers information. E-mail the following information to support@ddlsystems.com or fax it to (866) 559-0800:

• The name and phone number of your paging (or cellular phone) service provider.
• The modem access number that is used to dial the services computers directly (if known).
• The personal identification number of your pager (or cellular phone).

Return to table of contents

Installing or upgrading ACO PAGER™ on your iSeries system is a simple procedure.

1. Sign on to your system as the master security officer (QSECOFR) or any other user profile that has *ALLOBJ authority. If you don't know the password ask your system administrator.

2. If you are installing the software for the first time continue with the next step. If you are upgrading the software, please perform the following:

• End the ACOPAGER subsystem.
• Clear the ACO message history file ACP0300. If you avoid this step, the installation program will automatically convert the existing data. This could seriously impact the overall time required to perform the upgrade.
• Remove all queued jobs (if any) in the ACOPAGER job queue.
• Make sure there are no users accessing the product.
• Remove or rename the ACOPAGEOLD library (if it exists on your system). This library was created during a previous install of the software.

3. The ACO PAGER™ Message Alert System software is distributed on CD-ROM. Please click the link below to install the software on your iSeries:

Please read the next step carefully!

4. If you are installing the software for the first time, go to step 5 now. Otherwise, complete the software upgrade by performing the steps listed below:

• Verify Work with Execution Options (required). New execution options may have been added to this release. Select Work with Execution Options from the Configuration menu. Press <Enter> through all panels and  make any necessary corrections until you are returned to the menu.
• Configure the ACO Network Monitor (optional). If your iSeries (or AS/400) systems are currently configured to use the ACO PAGER™ Network Monitor (centralized paging/messaging feature), YOU MUST rerun the “Configure Network Monitor” command (ACOCFGNET) on each SOURCE and TARGET system to re-configure your systems.
• Read the ACO Net Change Letter (optional). Please read the KNOWN PROBLEMS section in the ACO Net Change Letter before continuing with your normal system operations.
• Start the ACO Message Monitors (required). Re-start the monitors and the  ACOPAGER subsystem by entering the ACOSTRUP command.
• Check your system for required IBM PTF's (optional). Your system(s) may  require installation of IBM PTF’s to ensure proper operation of the ACO PAGER™ Message Alert System. Several important IBM PTF’s are required to properly run certain SQL statements based on the installed version of OS/400. These PTF’s are included in the latest version of the database group PTF for each release. We STRONGLY recommend that you put in place a process to regularly obtain (and apply) the latest cumulative PTF, HIPER group PTF, and database group PTF packages to your system(s).
  
  Congratulations!, you have completed the software upgrade and should now continue with normal system operations.

5. Sign-off the system and sign-on again with the ACO user id and password. The ACO PAGER™ main menu will be displayed. If the ACO main menu is not shown, type the following command:

The ACO PAGER™ software product has many features and capabilities which are beyond the scope of the topics presented here in this Quick Start guide. If you have questions regarding any aspect of the software, please call our SupportLine at (866) 559-0800 option 2 or send e-mail to support@ddlsystems.com.

6. ACO PAGER™ communicates with your service provider using a modem and/or e-mail connection. Based on the type of connection you are planning to use click on one of the links below:

Return to table of contents

• Starting the Message Monitor against the QSYSOPR message queue.
• Verifying the generic (*ANY) message action record that will send a pager message (to the default pager id *DFT) in response to a test message sent to the QSYSOPR message queue.
• Using the ACOSNDMSG command to send a test message.

Important: The QSYSOPR message queue must be placed in *HOLD delivery status before completing step 1 (below). If your iSeries system console is currently in *BREAK delivery mode just sign off the session or run the command below:

CHGMSGQ MSGQ(QSYSOPR) DLVRY(*HOLD)

1. On the main menu, enter option 1 and press <Enter> to display the user tasks menu. Start the Message Monitor(s) for the QSYSOPR message queue by selecting option 1 from the menu and press <Enter>. This option will start all ACO Message Monitors in the ACOPAGER subsystem including a job with the name QSYSOPR (via the ACOSTRUP command)..

2. On the user tasks menu, select option 3 to View the Execution Status of the Message Monitor(s) and press <Enter>. You should see a panel like the one shown below:

When viewing the execution status, the ACOPAGMON job should appear in the subsystem with a job status of *MSGW. This is the Message Monitor's normal mode of operation while monitoring the message queue(s).

3. Press <Enter> to return to the user tasks menu, then press <F3> to return to the main menu.

4. On the main menu, enter option 2 and press <Enter> to display the configuration menu.

5. Select the Work with Message Actions option by entering a 1 in the selection field, then press <Enter>. In a moment you will see the Work with Message Actions list panel 1 (shown below).

The software is shipped with a sample message action set that you can modify to meet your specific requirements. Please read the Message Monitor Search Hierarchy document for more information on how the Message Monitor determines the appropriate action to be performed. In addition, please refer to Completing the Set Up section in this guide for more information.

To perform a test of the Message Monitor, in this step, you will change the pre-defined generic (*ANY) message id to perform the following user-defined actions:

• Monitors all messages sent to the QSYSOPR message queue.
• Sends the received message to your pager (*DFT) for all messages with a severity of eighty (80) or higher.
• Forwards the received message to the system operator message queue (defined in Work with Execution Options). The software is shipped with a default value of ACO in library QUSRSYS.
• Messages with a lower severity will be filtered from the system operator message queue (QUSRSYS/ACO). The monitored message queue (QSYSOPR) is pre-set with a severity of eighty (80). You can change this value by executing the Work with Message Queues option (not shown).

6. Enter option 2 next to the *ANY (sequence number 50) record on the list panel (shown on the previous page) and press <Enter> twice. You will be shown the Work with Message Actions panel 2 (shown below).

7. Verify or change the message action record (see panel 2 above) to match the entries shown on the above panel. Make sure the severity level field is set to a value of 80. All other fields should be set to their default value or *ANY.

8. When you have completed your entries on panel 2, press <Enter> twice. You will be advanced to panel 8 (shown below).

Refer to the Work with Message Actions section in the ACO PAGER™ Guide to Operations manual for more information on specific message action record parameters.

9. Enter *USER in the type of user and *DFT in the pager or group id field. Once you have completed the entries, press <Enter> to return to list panel 1.

10. On the iSeries system console run the following command:

ACOCONSOLE, then <Enter>

The ACO PAGER™ Message Monitor forwards inquiry and other high priority messages to your system operators via the ACO message queue in library QUSRSYS. These messages break the display panel immediately and await a response (inquiry only).

11. Return to your workstation. The Work with Message Actions list panel should already be displayed.

12. Select the Send Message Command by entering a 12 next to the *ANY (sequence number 50) message action record and press <Enter>. The ACO Send Message Command panel is shown. Enter message id CPA2108, message file QCPFMSG (default), message queue QSYSOPR, message queue library QSYS, message data SYSLIB, and message type *INQ and press <Enter>.

13. The ACOSNDMSG command will send a test message to the monitored message queue (QSYSOPR) to be processed by the Message Monitor. As a result, the Message Monitor interrogates the message action file to determine the specific action to be performed for the received message. Since there is no specific entry in the action file that matches the CPA2108 message id, the Message Monitor selects the generic *ANY entry that you entered in a previous step.

14. In a few moments, the Message Monitor will forward a CPA2108 break message to the iSeries system console (via the ACO message queue) and send the CPA2108 message to your pager (since the severity of the message is 99 as defined in the message description file in QCPFMSG).

15. On the iSeries system console, the test message should have interrupted the display. Enter a reply value of G and press <Enter>. If not shown, enter the DSPMSG MSGQ(ACO) command and then enter the message reply.

16. Return to your workstation and press <F3> to exit the Work with Message Actions program.

18. On selection panel, enter the message queue QSYSOPR, message queue library QSYS, blank out the date field, enter a D in sort sequence, and press <Enter>. When the list panel is shown, review the CPA2108 message sender/response information generated by the Message Monitor by entering option 5 next to the entry on the list panel and press <Enter>. Make certain the Message Monitor has performed the correct action and recorded the message sender/response information properly. Press <F3> to exit this program.

If you experienced problems completing any of the previous steps, or these steps did not produce the expected result, call our SupportLine at (866) 559-0800 option 2 or send e-mail to support@ddlsystems.com. We will be glad to help you!

Please read the Message Monitor Search Hierarchy document for more information on how the Message Monitor determines the appropriate action to be performed.

Return to table of contents

The following summarizes the daily activities that should be performed to allow the ACO PAGER™ software to monitor your system in a production mode. They are as follows:

1. Start the ACOPAGER subsystem and Message Monitor(s) using the ACOSTRUP command. To start the ACO PAGER™ system while the iSeries performs its power-on sequence, you will need to add the ACOSTRUP command to the system start-up program (QSYS/QSTRUP). This program performs basic system start up functions such as starting subsystems and printers.

Important: The QSYSOPR message queue must be placed in *HOLD delivery status before running the ACOSTRUP command. If your iSeries system console is currently in *BREAK delivery mode just sign off the session or run the command below:

CHGMSGQ MSGQ(QSYSOPR) DLVRY(*HOLD)

Make sure the Automatic IPL startup flag is set to Y in the Work with Message Queues option for all message queues you plan to monitor (e.g. QSYSOPR) prior to running this command. The software is shipped to automatically start only the QSYSOPR message queue in library QSYS.

2. (Optional). On the iSeries system console run the following command:

Important: Run this command each time the iSeries system console is signed on.

The ACOCONSOLE command places the default system operator message queue (specified in Work with Execution Options) in *BREAK delivery mode. THE SOFTWARE IS PRE-SET TO USE MESSAGE QUEUE ACO IN LIBRARY QUSRSYS.

If you have system operators they should use the ACO message queue to manage the system. Based on your user-defined instructions, the Message Monitor forwards inquiry and other high priority messages to your system operators via the ACO message queue. These messages break the display panel immediately and await a response (inquiry only). Replies entered into the ACO message queue by your operations personnel (or end users) are simultaneously delivered to the originating message queue (e.g. QSYSOPR). In response, the message (associated with the originating job) is responded to just as if the reply was entered directly into QSYSOPR.

ACO PAGER™ does NOT restrict you from managing the system using the QSYSOPR message queue. Your system operators and end users can continue to display and reply to messages in QSYSOPR while it's being processed by the Message Monitor. Unanswered messages previously sent to the ACO Message queue are automatically synchronized with the QSYSOPR message queue providing the ACOCONSOLE command is running on the iSeries system console.

If you have questions regarding the software’s options and/or set up call our SupportLine at (866) 559-0800 option 2 or send e-mail to support@ddlsystems.com.

3. (Optional). Start any additional ACO monitors as required:

• Enterprise servers (if installed) (STRCMDPST)
• Job event monitor (STRJOBMON)
• Network monitor (STRPAGMON)
• QHST monitor (STRPAGMON)
• RePage (escalation) monitor (STRREPAGE)
• Restricted state monitor (see user guide)
• Security monitor (STRSECMON)
• TCP/IP monitor (STRTCPMON)
• Two-Way reply monitor (STRPAGMON)
• Unattended monitor (see user guide)
• Windows monitor (if installed) (STRWINCLT)
• Workstation monitor (STRPAGMON)

Please refer to the Commands chapter in the Guide to Operations manual for more information.

4. (Optional). Start the Enterprise Servers. If you are using the ACO ESI™ product in conjunction with an Enterprise System, you will need to start the ACO Enterprise Servers (ACO_MSG, ACO_CTL). Start the servers by entering the following command on the iSeries command line:

Note:  To run the above command you must have the ACOESI library in your list.

5. Periodically run the ACOPAGCLR command. When the Message Monitor is processing a message queue (e.g. QSYSOPR), the DSPMSG/WRKMSG command(s) cannot be used to clear messages from the queue (via function keys F11, F13, and/or F16). The command below clears the QSYSOPR message queue of all messages (except those unanswered) while the monitor is active.

6. Verify the iSeries communication status. If the ACO PAGER™ software is configured to send messages via a modem connection verify that the modem is powered on and fully operational. If the software is configured to use the Simple Mail Transport Protocol (SMTP) please verify that the Mail Server Framework (MSF) jobs and the SMTP server jobs are running in the QSYSWRK subsystem. Click on one of the links above to verify your iSeries connection if you are experiencing problems.

If you are experiencing problems or have questions regarding your service provider connection (or iSeries communication configuration) please call our SupportLine at (866) 559-0800 option 2 or send e-mail to support@ddlsystems.com.

7. Verify the run status of the Message Monitor(s). Use the View execution status option from the ACO PAGER™ main menu or the Work with Active Jobs command to verify the run status of the Message Monitor(s). Enter the command below to display the ACOPAGER subsystem:

When viewing the execution status, the ACOPAGMON job should appear in the subsystem with a job status of *MSGW. The message wait status in no way indicates that there is a problem with the Message Monitor. This is the Message Monitor’s normal mode of operation while monitoring the message queues.

8. Add the Clear Message History (ACOCLRHST) command to the AS/400’s internal job scheduler. This command will keep the message history generated by the message monitors down to a reasonable size. The software is pre-configured to retain a maximum of ten (10) days of message history.

9. You’re almost done, so continue with Completing the Setup section below.

Return to table of contents

This section will help you become familiar with more advanced topics concerning the set up and maintenance of the product’s features. Once you complete steps 1 and 2 you should be able to start monitoring your production system. Then, at a later date, you can complete the additional steps when you want to use more advanced features.

Refer to the ACO PAGER™ Installation/User Guide CD-ROM for step-by-step examples on all product features.

1. Select the Work with Message Actions option from the configuration menu. ACO PAGER™ is shipped with a sample message action set for the QSYSOPR message queue in library QSYS. You can use this sample file to tailor the system to meet your specific requirements.

The *ANY message that you set up in Testing the Installation section of this guide will page you with all severity level 80 or higher messages sent to the monitored queue. The sample set contains other messages (e.g. printer, configuration, save/restore and other systems messages) that you can elect to filter, page etc. based on your requirements. These messages are included in the sample file since they are sent by the system with a severity of 99 and will cause the *ANY message action to page you unless the sample entries are modified.

2. Print the sample message action set from the Work with Message Actions panel by pressing <F22> on the list panel. Review the sample messages and the current action defined for each message. Then, change or add any new entries you want to monitor. Now that you have completed steps 1 and 2, you can validate your message action set for QSYSOPR by continuing with step 8.

Please read the Message Monitor Search Hierarchy document for more information on how the Message Monitor determines the appropriate action to be performed. In addition, refer to the ACO PAGER™ Installation/User Guide CD-ROM for step-by-step examples on how to set up special features that utilize the Work with Message Action file.

3. Select the Work with Pagers option from the maintenance window to enter additional pagers that you will use in your organization.

4. Select the Work with Group Call List option from the maintenance window to enter group call lists of pager id's, their priorities, and any associated work schedules to be used during group paging activities. Call lists are used to send broadcast messages to a group of individuals and during message escalation processing.

5. Select the Work with Message Queues option from the maintenance window to enter additional message queues to be monitored by the Message Monitor. The ACO PAGER™ Message Alert System is pre-set to monitor only the QSYSOPR message queue in library QSYS.

6. Select the Work with Job Events option from the maintenance window to enter specific information about system performance, active jobs, job/output queues, and communications status events on your system.

7. If you have multiple iSeries and would like to centralize all paging on a TARGET system, select the Configure ACO NET option from the maintenance window to configure your SOURCE and TARGET machines. Refer to the help text defined in this option to review the specific system requirements necessary to install and utilize this feature.

8. Start the Message Monitor(s) by running the ACOSTRUP command if you have not already done so. View the system generated test messages or generate your own series of test messages to determine the validity of your message action set.

9. Use the Work with message history option to validate the specific actions performed by the Message Monitor based on the contents of the received message. Make any necessary corrections to the message action file based on your unique system requirements. Do not attempt to add every known message id into the Work with Message Actions file. Build this file over time, and concentrate on only those messages that are immediately critical to your system operations.

The ACO PAGER™ Message Monitor(s) perform a specific search hierarchy when selecting the appropriate message action record to execute (based on the received message). The action message id and action sequence fields (shown on panel 2) identify the keys to the actual message action record selected by the Message Monitor.

10. Congratulations, you have completed the software installation/set up and should be ready to use ACO PAGER™ on a daily basis.

If you experienced problems completing any of the previous steps, or if you would like more information on various product features and capabilities, please call our SupportLine at (866) 559-0800 option 2 , or send e-mail to support@ddlsystems.com.

Return to table of contents

We would like to hear from you! Help us make future versions of ACO PAGER™ even better by sending your comments and suggestions for new features or enhancements. Address them to the DDL Systems SupportLine using any of the following methods:

Return to table of contents