Re: Help w/ AS/400 power crash

>  Someone else mentioned running RCLSTG.  
>  Would that show up in the system log if it had been run?

Perhaps I have a misconception here ... I thought RCLSTG was included in an 
IPL.
I do an IPL about once a month for a number of reasons, and DSPSYSSTS before 
& after shows that we buy several percentage points of disk space in the 
process, to which I attribute our humongous reports, that come & go with 
regularity.

>  Too bad there isn't better filtering available on the DSPLOG command, like 
to
>  EXCLUDE certain message IDs.  Is there an API available to read through the
>  system log, with the goal of being able to use F1 to get at second-level
>  message text?

Have you tried print wrap?  You get more info but I find regular print to be 
more readable.

Just in case you overlooked a nuance?
You do know that with DSPLOG on screen you can cursor a line & F1 more info 
there.
You do know that DSPLOG can go to spool then from there to DB, such as a 
source member for ease of edit chopping out the irrelevancies & searching for 
key words.
You do know that you do not have to go to the message source to get the 
message then 2nd level ... you can key on command line to display the message 
file story on message of your choice & drill from there.
You do know that there is a RTV to get at the message source & 2nd level 
detail, so if you had a list of errors in your DB from DSPLOG distilled .... 
but I suspect what you will be finding is a small range of error messages 
repeated frequently on a large number of objects.

I just don't know off hand the precise commands to do some of this because I 
am either at my home PC or at the 400 at work - not both at same time.

I suspect that someone at a PC might be able to cut & paste the message ID 
from DSPLOG & put that in another session where you identifying messages you 
want the full details on.

MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac)


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---