My guess is that it abended. It doesn't write that event in its log ... (obviously). Look in the spool for a dump file from PERFSVM, and you'll have no other choice then to send that to the support center.
2011/1/23 Shimon Lebowitz <shim...@iname.com> > Hi, > On Thursday (actually, it was just past midnight, Wednesday night), PERFSVM > was forced > off by SYSTEM, while running DSC as usual: > > The operator log showed these lines: > 00:51:51 USER DSC LOGOFF AS PERFSVM USERS = 66 FORCED BY SYSTEM > 00:51:51 HCPMNI6245I The monitor IUCV path was abnormally severed by userid > PERFSVM with error > code 0000. > > > The PERFSVM console log shows nothing abnormal occurring, just a > reinitialization: > > +c+14 00:19:16 FCXUSL317A User TM IO/s 951 exceeded threshold 800 for 45 > min. > +c+15 00:19:16 FCXUSL317A User IM IO/s 88.8 exceeded threshold 50.0 for 35 > min. > (c+16 00:25:16 FCXUSL317A User IM IO/s 70.9 exceeded threshold 50.0 for 5 > min. > ( > **************************************************************************** > ( * Log started on 2011/01/20 at > 00:51:53 * > ( > **************************************************************************** > c FCXBAS500I Performance Toolkit for VM FL540 > ¬ 1FCONX $PROFILE *: > ******************************************************** > ¬ 1FCONX $PROFILE *: > ******************************************************** > ¬ 1FCONX $PROFILE *: ** Initialization profile for 'Performance > Toolkit > ¬ 1FCONX $PROFILE *: > ******************************************************** > ¬ 1FCONX $PROFILE *: > ******************************************************* > > Does anyone have any idea what might have happened? > > Thanks, > Shimon > > -- Kris Buelens, IBM Belgium, VM customer support
