Sat, Apr
5 New Articles

TechTip: Email Notification of System Messages

  • Smaller Small Medium Big Bigger
  • Default Helvetica Segoe Georgia Times
When you are a one-man administrator for a country-wide distributed network of over 10 aging AS/400s that run 24x7 with very minimal operator interaction, it is no simple task to constantly monitor all of them for potential problems. For one thing, events can happen anytime and anywhere. Unless you perform hourly (or so) checkups on each machine, you could easily miss out on critical warnings preceding a disaster. However, if you do the hourly checkups, you won't have time for anything else. In effect, you just downgraded yourself from an administrator to a mere watchdog.

You can solve this dilemma by delegating the tedious--yet critical--monitoring task to a non-human assistant. The solution consists of a CL program that constantly monitors, in real time, the QSYSMSG message queue and sends an email to the administrator(s) whenever an error message of interest is detected.

This solution ensures that you have a 24-hour guard watching over each AS/400 on which you have installed the program. You, the administrator, need only keep your email client running, and you will receive email alerts within minutes of any critical event.

Why monitor QSYSMSG? Why not QSYSOPR?

There are reasons a-plenty:

  1. The operating system loads only critical messages to QSYSMSG. So the CL monitoring program will have fewer messages to process, and thus consume less CPU cycles.
  2. It is much easier to find specific messages in QSYSMSG rather than wade through volumes of non-critical messages in QSYSOPR.
  3. You avoid conflict with the occasional operator or programmer who wants to reduce or clear the QSYSOPR message queue via F13 or F16.
  4. Sooner or later, messages in QSYSOPR have to be purged. This is not the case with QSYSMSG, where critical messages may be retained indefinitely. This is particularly useful when you are analyzing the history of problems for the particular AS/400. For example: Which particular disk unit has been failing regularly, how often has it failed, and when was the last failure?

Some Important Notes:

  1. IBM created QSYSMSG to ensure that critical messages wouldn't get buried in QSYSOPR and overlooked. However, the QSYSMSG message queue does not exist by default. You have to create this yourself in library QSYS:
    Once you've created QSYSMSG, the operating system automatically sends critical messages to this queue.
  2. This tip assumes that you already have AS/400 SNADS and email working.
  3. In the main RCVMSG command, there is a "wait" parameter set for 180 seconds. This is purely arbitrary. It only controls how often the program checks for a controlled job-end condition.
  4. There is no need to run this program in the QCTL subsystem. You may submit this to QINTER, but if your operations require that QINTER be shut down once in a while, I suggest that you create a separate subsystem for this program (and others like it)..
  5. If possible, send the email message to more than one person. You may be the only administrator in the company, but it helps to have a close colleague who can tap you on the shoulder in case you are distracted by something less critical.
  6. Once your AS/400's ASP threshold has been reached (CPF0907), email will cease to function. Your message gets sent only after the disk utilization is reduced below the ASP threshold! You need something to warn you before this condition is reached. The solution is to set the following systems values as illustrated:
    QSTGLOWLMT = (100 minus warning-threshold-limit)
    Example: If you have an ASP threshold of 90% and you want a warning message at 88%, you should set
    QSTGLOWLMT = 100 - 88 = 12
    Once your disk utilization reaches 88%, the system will send CPI099C to QSYSMSG, which can be emailed well before the ASP threshold of 90% is reached.
  7. Once in a while, especially if your ASP threshold has been reached, you may have to reset QSNADS and QMSF; otherwise, your email won't move!
  8. The message-ids that are monitored in this code are not all-inclusive. It is up to you to add whatever other message-ids you wish to monitor (as long as you know it is sent by the OS to QSYSMSG).
  9. The sample code works, but it could do with some additional enhancements (which I leave up to you). Some possibilities:
  10. A routine to stop sending repetitive messages (e.g., CPI1165).
  11. A routine to SNDMSG to selected users whenever CPF0907 is encountered. Once the ASP threshold is reached, SNADS and email freeze up, but internal message-sending still works.
  12. If you have an administrative user profile other than QSECOFR, it would be a good idea to include it in the CPF1393 monitored message.
  13. You might want to consider incorporating pager or cell phone text messaging.

--Ricardo P. Ang
This email address is being protected from spambots. You need JavaScript enabled to view it.

Sample CL Program to Monitor QSYSMSG Message Queue


             DCL        &ADDR1 *CHAR LEN(32) +
                            VALUE('system-admin-address-1          ')
             DCL        &ADDR2 *CHAR LEN(32) +
                            VALUE('system-admin-address-2          ')

             DCL        &SYS   *CHAR LEN(8)
             DCL        &MLIB  *CHAR LEN(10) VALUE('QSYS')
             DCL        &MSGQ  *CHAR LEN(10) VALUE('QSYSMSG')
             DCL        &WAIT  *CHAR LEN(4)  VALUE('0180')

             DCL        &STRT  *LGL  LEN(1)
             DCL        &ENDD  *CHAR LEN(1)
             DCL        &MKEY  *CHAR LEN(4)
             DCL        &MDAT  *CHAR LEN(120)
             DCL        &USER  *CHAR LEN(10)

             DCL        &RKEY  *CHAR LEN(4)
             DCL        &UMSG  *CHAR LEN(132)
             DCL        &LMSG  *CHAR LEN(256)
             DCL        &SUBJ  *CHAR LEN(60)
             DCL        &DATE  *CHAR LEN(6)
             DCL        &DAT8  *CHAR LEN(8)
             DCL        &TIME  *CHAR LEN(6)
             DCL        &TIMER *CHAR LEN(8)
             DCL        &MSID  *CHAR LEN(7)

             DCL        &LWLT1 *DEC  LEN(8 4)
             DCL        &LWLT2 *CHAR LEN(8)

             DCL        &DTA   *CHAR LEN(68)
             DCL        &LEN   *DEC  LEN(4) VALUE(68)
             DCL        &FMT   *CHAR LEN(8) VALUE('SSTS0200')
             DCL        &RST   *CHAR LEN(10) VALUE(*YES)
             DCL        &ERR   *CHAR LEN(8) VALUE(X'0000000000000000')

             DCL        &PCUS1 *CHAR LEN(4)
             DCL        &PCUS2 *DEC  LEN(9 2)
             DCL        &PCUS3 *DEC  LEN(9 6)
             DCL        &PCUS4 *CHAR LEN(9)
             DCL        &SYAS1 *CHAR LEN(4)
             DCL        &SYAS2 *DEC  LEN(12 2)
             DCL        &SYAS3 *DEC  LEN(12 5)
             DCL        &SYAS4 *CHAR LEN(12)

             CHGVAR     VAR(&STRT) VALUE('1')

             RTVNETA    SYSNAME(&SYS)

 LOOP:       IF         COND(*NOT &STRT) THEN(+
                          RCVMSG MSGQ(&MLIB/&MSGQ) +
                            MSGKEY(&RKEY) MSGTYPE(*NEXT) +
                            MSGDTA(&MDAT) +
                            WAIT(&WAIT) RMV(*NO) +
                            KEYVAR(&MKEY) MSG(&UMSG) MSGID(&MSID))

             ELSE       CMD(DO)
                          CHGVAR VAR(&STRT) VALUE('0')
                          RCVMSG MSGQ(&MLIB/&MSGQ) +
                            MSGTYPE(*LAST) +
                            KEYVAR(&RKEY) +
                            WAIT(0) RMV(*NO)
                          RCVMSG MSGQ(&MLIB/&MSGQ) +
                            MSGKEY(&RKEY) MSGTYPE(*NEXT) +
                            MSGDTA(&MDAT) +
                            WAIT(&WAIT) RMV(*NO) +
                            KEYVAR(&MKEY) MSG(&UMSG) MSGID(&MSID)
                          MONMSG CPF2410 EXEC(+
                            RCVMSG MSGQ(&MLIB/&MSGQ) +
                              MSGTYPE(*ANY) +
                              MSGDTA(&MDAT) +
                              WAIT(&WAIT) RMV(*NO) +
                              KEYVAR(&MKEY) MSG(&UMSG) MSGID(&MSID))

             RTVJOBA    ENDSTS(&ENDD)
             IF         COND(&ENDD = '1') THEN(RETURN)
             IF         COND(&MSID = '       ') THEN(GOTO LOOP)
             CHGVAR     VAR(&RKEY) VALUE(&MKEY)

          /* User-id was Disabled  */
             IF         COND(&MSID = 'CPF1393') THEN(DO)
                          CHGVAR &USER %SST(&MDAT 11 10)
                          IF (&USER = 'QPGMR     ') THEN(GOTO SNDMSG)
                          IF (&USER = 'QSECOFR   ') THEN(GOTO SNDMSG)
                          IF (&USER = 'QSRV      ') THEN(GOTO SNDMSG)
                          IF (&USER = 'QSYSOPR   ') THEN(GOTO SNDMSG)
                          IF (&USER = 'QUSER     ') THEN(GOTO SNDMSG)
                          GOTO LOOP
          /* Serious Storage Condition may Exist */
             IF         COND(&MSID = 'CPF0907') THEN(GOTO SNDMSG)
          /* Critical Storage Limit Reached  */
             IF         COND(&MSID = 'CPI099C') THEN(GOTO SNDMSG)
          /* Device Parity Error  */
             IF         COND(&MSID = 'CPI1165') THEN(GOTO SNDMSG)
          /* Device Parity Fixed  */
             IF         COND(&MSID = 'CPI1166') THEN(GOTO SNDMSG)
          /* Call Hdw Srv Provider (Disk Device Parity Error) */
             IF         COND(&MSID = 'CPPEA05') THEN(GOTO SNDMSG)
          /* Call Hdw Srv Provider (Disk IO Cache Card Failure) */
             IF         COND(&MSID = 'CPPEA12') THEN(GOTO SNDMSG)
          /* Operating System/400 grace period expires in nn days. */
             IF         COND(&MSID = 'CPF9E7D') THEN(GOTO SNDMSG)
          /* Operating System/400 grace period expired. */
             IF         COND(&MSID = 'CPF9E7C') THEN(GOTO SNDMSG)

             GOTO       CMDLBL(LOOP)


             CVTDAT     DATE(&DATE) TOVAR(&DAT8) FROMFMT(*MDY) +
                          TOFMT(*MDY) TOSEP('/')
             CHGVAR     VAR(&TIMER) VALUE(%SST(&TIME 1 2) || ':' || +
                                          %SST(&TIME 3 2) || ':' || +
                                          %SST(&TIME 5 2))
             CHGVAR     VAR(&SUBJ) VALUE(&SYS  |> &UMSG)
             CHGVAR     VAR(&LMSG) VALUE(&SYS  |> &DAT8 |> &TIMER |> +
                                         &MSID |> &UMSG)

             IF         COND(&MSID = 'CPI099C') THEN(DO)
                          CALL PGM(QWCRSSTS) +
                            PARM(&DTA &LEN &FMT &RST &ERR)
                          CHGVAR &PCUS1 (%SST(&DTA 53 4))
                          CHGVAR &PCUS2 (%BINARY(&PCUS1))
                          CHGVAR &PCUS3 (&PCUS2 / 10000)
                          CHGVAR &PCUS4 (&PCUS3)
                          CHGVAR &SYAS1 (%SST(&DTA 49 4))
                          CHGVAR &SYAS2 (%BINARY(&SYAS1))
                          CHGVAR &SYAS3 (&SYAS2 / 1000)
                          CHGVAR &SYAS4 (&SYAS3)
                          CHGVAR &LWLT2 &LWLT1
                          CHGVAR &LMSG (&LMSG |> '  The +
                            Aux Stg Lower Limit is ' || &LWLT2 || +
                            '% but ' || &PCUS4 || +
                            '% of system ASP (' || &SYAS4 || +
                            'Gb) is already in use.')

             SNDDST     TYPE(*LMSG) +
                          TOINTNET((&ADDR1) (&ADDR2)) +
                          DSTD('QSYSMSG Message') LONGMSG(&LMSG) +
                          IMPORTANCE(*HIGH) PTY(*HIGH) +

             GOTO       CMDLBL(LOOP)


Just do it!
Got a tip that makes you a star?
Send it to
This email address is being protected from spambots. You need JavaScript enabled to view it.

Ricardo Ang


In earlier years, Ric worked as a programmer analyst for a variety of IBM midrange machines. Most of his experience was with inventory systems for construction companies, book stores, and pharmaceutical distributors.
Since 1995, his experience has centered on operations support and systems management for a network of AS/400s. His passion is in developing automation software to ease the tedious day-to-day operations tasks, such as networked monitors for alerts, security logs, leased-line performance, UPS-shutdown/restarts, and disk-utilization. His most satisfying achievement is an automated source and object code change-management system that can work over any number of AS/400, iSeries, or System i systems.
Currently, Ric is a private contractor hired by a large IT company to perform and monitor operations over a large number of AS/400 operations for a big client.  



Support MC Press Online

$0.00 Raised:

Book Reviews

Resource Center

  • SB Profound WC 5536 Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application. You can find Part 1 here. In Part 2 of our free Node.js Webinar Series, Brian May teaches you the different tooling options available for writing code, debugging, and using Git for version control. Brian will briefly discuss the different tools available, and demonstrate his preferred setup for Node development on IBM i or any platform. Attend this webinar to learn:

  • SB Profound WP 5539More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.

  • SB HelpSystems ROBOT Generic IBM announced the E1080 servers using the latest Power10 processor in September 2021. The most powerful processor from IBM to date, Power10 is designed to handle the demands of doing business in today’s high-tech atmosphere, including running cloud applications, supporting big data, and managing AI workloads. But what does Power10 mean for your data center? In this recorded webinar, IBMers Dan Sundt and Dylan Boday join IBM Power Champion Tom Huntington for a discussion on why Power10 technology is the right strategic investment if you run IBM i, AIX, or Linux. In this action-packed hour, Tom will share trends from the IBM i and AIX user communities while Dan and Dylan dive into the tech specs for key hardware, including:

  • Magic MarkTRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now!  Request Now.

  • SB HelpSystems ROBOT GenericForms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.

  • SB HelpSystems ROBOT GenericIT security is a top priority for businesses around the world, but most IBM i pros don’t know where to begin—and most cybersecurity experts don’t know IBM i. In this session, Robin Tatam explores the business impact of lax IBM i security, the top vulnerabilities putting IBM i at risk, and the steps you can take to protect your organization. If you’re looking to avoid unexpected downtime or corrupted data, you don’t want to miss this session.

  • SB HelpSystems ROBOT GenericCan you trust all of your users all of the time? A typical end user receives 16 malicious emails each month, but only 17 percent of these phishing campaigns are reported to IT. Once an attack is underway, most organizations won’t discover the breach until six months later. A staggering amount of damage can occur in that time. Despite these risks, 93 percent of organizations are leaving their IBM i systems vulnerable to cybercrime. In this on-demand webinar, IBM i security experts Robin Tatam and Sandi Moore will reveal:

  • FORTRA Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:

  • FORTRAManaging messages on your IBM i can be more than a full-time job if you have to do it manually. Messages need a response and resources must be monitored—often over multiple systems and across platforms. How can you be sure you won’t miss important system events? Automate your message center with the Robot Message Management Solution. Key features include:

  • FORTRAThe thought of printing, distributing, and storing iSeries reports manually may reduce you to tears. Paper and labor costs associated with report generation can spiral out of control. Mountains of paper threaten to swamp your files. Robot automates report bursting, distribution, bundling, and archiving, and offers secure, selective online report viewing. Manage your reports with the Robot Report Management Solution. Key features include:

  • FORTRAFor over 30 years, Robot has been a leader in systems management for IBM i. With batch job creation and scheduling at its core, the Robot Job Scheduling Solution reduces the opportunity for human error and helps you maintain service levels, automating even the biggest, most complex runbooks. Manage your job schedule with the Robot Job Scheduling Solution. Key features include:

  • LANSA Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.

  • LANSAWhen it comes to creating your business applications, there are hundreds of coding platforms and programming languages to choose from. These options range from very complex traditional programming languages to Low-Code platforms where sometimes no traditional coding experience is needed. Download our whitepaper, The Power of Writing Code in a Low-Code Solution, and:

  • LANSASupply Chain is becoming increasingly complex and unpredictable. From raw materials for manufacturing to food supply chains, the journey from source to production to delivery to consumers is marred with inefficiencies, manual processes, shortages, recalls, counterfeits, and scandals. In this webinar, we discuss how:

  • The MC Resource Centers bring you the widest selection of white papers, trial software, and on-demand webcasts for you to choose from. >> Review the list of White Papers, Trial Software or On-Demand Webcast at the MC Press Resource Center. >> Add the items to yru Cart and complet he checkout process and submit

  • Profound Logic Have you been wondering about Node.js? Our free Node.js Webinar Series takes you from total beginner to creating a fully-functional IBM i Node.js business application.

  • SB Profound WC 5536Join us for this hour-long webcast that will explore:

  • Fortra IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn: