Bill asks:
>
> Vstore has hung and is now using all available cpu time.  Abort job, =
...
> other options?  Can this be fixed or is it an undocumented feature ;-(.  =
> Below is the vstore job listing:

The problem is caused by a severe design flaw in STORE/TurboSTORE: it
runs critical most of the time *and* doesn't check for user abort
requests adequately.  Discuss this with HP :)

However, it is possible to address the CPU utilization problem on a
per-instance basis in two manners:

   1) (easiest)  use :ALTPROC to set STORE's priority low...*real* low
      (e.g., ALTPROC 123; pri=es)

      This may solve the CPU utilization issue, but it won't get rid of
      the looping process (and therefore, won't release any resources).

   2) (very difficult) use :DEBUG to back STORE out of what it is doing
      until it decides to terminate.

      I've done this a few times, when we could not afford to leave the
      STORE process looping *and* we were unwilling to reboot the machine ...
      but it's risky, and very difficult.  I think my success rate is
      something like 3 good, 1 bad (system failure), and 1 middling
      (STORE still hung, still looping, but no system failure).


--
Stan Sieler                                          [log in to unmask]
                                     http://www.allegro.com/sieler.html