Ron,

I got the same message back in October.  It turned out that 'predictive' was
hung somehow and in the process it had also 'tied up' the system process
'diagmon'.  When you invoke 'sysdiag' it tries to communicate with 'diagmon'
and since 'diagmon' was 'tied up' 'sysdiag' would fail with the indicated
message.
Although the RC first indicated that we would have to 'reboot', we ended up
using 'consolan' (I think) and with RC's help I was able to 'kill' the
'predictive' process and free up 'diagmon' but I must say that we eventually
ended up with a system abort 1047.

The problem has *not* reoccurred.  In mid December, however, the RC provided
to us patch MPEKX29A (LPMC's and HPMC's on Non-Monarch Processors Are Not
being Logged) as a direct result of the aforementioned system abort.

BTW we have a 969/220 and are on MPE/iX 5.0 PP6.

I would recommend that you try to schedule a backup and reboot your system.
In our case there was a window of about 20 hours between the time that I
started seeing the 'sysdiag' error messages and the system abort.

Good luck
Paul H. Christidis


______________________________ Reply Separator _________________________________
Subject: Sysdiag Message
Author:  Ron Horner <[log in to unmask]> at CCGATE
Date:    02/09/98 09:33


From: Ron Horner@ILGW  on 02/09/98 10:59 AM


To:   [log in to unmask]
cc:
Subject:  Sysdiag Message


Has anyone ever seen an error message like this, from sysdiag??

*** ERROR - Unable to receive a reply message from the
     diagnostic monitor
. Diagnostic system error  (DUISERVERR 4543)

The Diagnostic System is not available now.

Please let me know what it means.

Thanks!




Ron Horner

Systems Programmer

Stone Container Corporation

[log in to unmask]

(312) 580-2982