OnDemand User Group

Support Forums => iSeries => Topic started by: Joe Wolken on July 09, 2009, 02:01:32 PM

Title: How to get Common Server load errors to QSYSOPR message queue?
Post by: Joe Wolken on July 09, 2009, 02:01:32 PM

I know how to find Common Server file loading errors by using the OnDemand Client System Log folder and searching for message number 88. However, this requires a proactive search.  Does anyone know how to automate the process so that the error message is displayed in the iSeries QSYSOPR message queue automatically whenever a message #88 error is generated? (or perhaps as a job that runs once a day to see if any errors were generated that day)?

Any ideas or codes?

Title: Re: How to get Common Server load errors to QSYSOPR message queue?
Post by: Darrell Bryant on July 13, 2009, 11:18:21 AM

OnDemand already sends system log message 88, and most other error messages, to QSYSOPR.  The OD error messages are sent using message OND1002.  If you display the message it will look something like the following:
Message ID . . . . . . :   OND1002       Severity . . . . . . . :   20       
Message type . . . . . :   Diagnostic                                         
Date sent  . . . . . . :   07/13/09      Time sent  . . . . . . :   14:10:25 
                                                                             
Message . . . . :   Instance 'QUSROND' sent severity 2 message number 88 for 
  user 'DBRYANT' at '07/13/09 14:10:24'.                                     
Cause . . . . . :   'ApplGroup Failed Load: Name(CHECKSTMTS) LoadId(--INDEXING
  ONLY--)                                                                     
  File(/QIBM/USERDATA/ONDEMAND/QUSROND/TMP/DB_ONDSAMPLES_FLASHSALES_FLASHSALES
  )'.                                                                         
Recovery  . . . :   Look at the OnDemand system log for instance 'QUSROND' for
  more information.                                                           
Technical description . . . . . . . . :   Account:  Log id: '33243'.         

Another option is to use the arslog exit program.  Using the arslog exit program you can decide on a message by message basis what action, if any, to take.  We include a sample arslog program in file QSAMPLES2 in library QRDARS.  An update is required to the shipped sample arslog program.  If you send me an e-mail, I will send you the updated (and enhanced) source code.