The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact firstname.lastname@example.org.
It appears that it's safe to purge them with the 'chhmcfs
> ' command. I
would think that the HMC would handle the purging on it's own though.
Interestingly enough, I recently started getting this event code as well,
but it was accompanied by my HMC hanging in limbo; it was on, but it would
lose connection to the managed systems. I couldn't open up 5250 consoles to
my partitions, although I was able to SSH to the HMC. However, multiple CLI
commands were unavailable, such as hmcshutdown, and failed with the error "A
Connection to the Command Server failed." The HMC was failing on a
"Rearbitrate Primary Analysis Console Scheduled Operation" task. The cause
of failure was that there was not enough disk space (probably at
I took note of the filesystem usage and then cleaned out what I could. Here
are the commands for future reference:
-Check filesystem usage
monhmc -r disk
-Check what can be gained after cleaning
lshmcfs -o c -d 0
-Perform actual cleanup. This will still keep what is currently in use. If
you want to hold on to a few days, increment 0 to your desired number of
chhmcfs -o f -d 0
For reference, I had this issue on a vHMC x86, V9R2, M952, MH01921.
I don't suppose you're supposed to purge these logs manually? Most research
says "call next level of support".
As an Amazon Associate we earn from qualifying purchases.