SLACVX problems and solutions

 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

4.3.95  xdm_server 

The process xdm_server has been taking 80-90% of the CPU on some of
the sld a and b nodes.  This is thought to be a result of Bob Cook
running the SATAN program on these nodes.  

One solution is to reset the xdm server:

$ mu netc xdm restart

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

4.3.95 	staging problem

A user reported a problem with the staging system as follows:

SLDB5>IDA

        **************************
        ** SLD IDA version 1.40 **
        **************************
        **************************
        ** JAZELLE version 3.50 **
        **************************

HANDYPAK  --  RELEASE 6.58 --  HCOM SIZE =  200000
%UPROC-I-INIT Processor support package (UPROC version 1.20) initialized
Ida>  OPENTAPE READ MUPAIR_[1-2] STAGE WAIT
.
.
.
Job STAGE_RK0483 (queue SLDA4_SLD_MEDIUM, entry 370) completed
%NONAME-E-NOMSG, Message number 0FCE8322
%STAGE-E-ERRSYNC, Error syncing to STAGE job STAGE$Q.
-SYSTEM-S-NORMAL, normal successful completion
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC


Tony Johnson replies:

The correct way to diagnose this type of problem is to look at the log
file for the staging job, STAGE$LOG:STAGE_RK0050.log in this case.

Here you will normally find the explanation of the problem, in this
case:

%FOR-F-ERRDURWRI, error during write
  unit 117  file $SLD_DAT:[STAGEDIR]RK0050.RK0050$5NMUPAIR_2$7B1;1
  user PC 00000000
-RMS-F-FUL, device full (insufficient space for allocation)

This probably means that the default size reserved for your stage file
(200 MB) wasnt big enough. Try something like

        OPENTAPE READ RK0050.1/WHATEVER/ STAGE SIZE 400


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=