TechTip: Email Notification of System Messages

RPG
Typography
  • 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:
    CRTMSGQ QSYS/QSYSMSG
    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:
    QSTGLOWACN = *MSG
    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

PGM

             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))
                          ENDDO

             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
                          ENDDO
          /* 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)

 SNDMSG:     RTVSYSVAL  SYSVAL(QDATE) RTNVAR(&DATE)
             RTVSYSVAL  SYSVAL(QTIME) RTNVAR(&TIME)

             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)
                          RTVSYSVAL SYSVAL(QSTGLOWLMT) RTNVAR(&LWLT1)
                          CHGVAR &LWLT2 &LWLT1
                          CHGVAR &LMSG (&LMSG |> '  The +
                            Aux Stg Lower Limit is ' || &LWLT2 || +
                            '% but ' || &PCUS4 || +
                            '% of system ASP (' || &SYAS4 || +
                            'Gb) is already in use.')
                          ENDDO

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

             GOTO       CMDLBL(LOOP)

             ENDPGM



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.  

BLOG COMMENTS POWERED BY DISQUS

LATEST COMMENTS

Support MC Press Online

$

Book Reviews

Resource Center

  •  

  • 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.

  • 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

  • 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: