We had a similar problem for over a year. The Response Center kept
suggesting that our tape/tapeheads were dirty. Once the DAT drive itself
was replaced. But the problem persisted until last summer. It disappeared
after we loaded 5.0 of the OS and has shown up only once since.
 
*****************************************************
George Bennett                  Library Director
Houghton College                [log in to unmask]
Library                         716-567-9241
Houghton, NY 14744              FAX: 716-567-9248
******************************************************
 
 
On Mon, 12 Feb 1996, Pete Crosby wrote:
 
> "James B. Byrne" <[log in to unmask]> wrote:
>
> >I am having a problem, which is extraordinary in my experience
> >on HP3000.  The situation is that my weekend fullbackup job will
> >not start!  By this I mean that despite being streamed on time
> >and having a status of exec when I do a SHOWJOB the job itself
> >does not open a spool file, does not execute and when cancelled
> >via ABORTJOB, does not leave any trace that it ever existed.
> >
> >I originally thought that this problem was being caused by the
> >HP1511A DDS-1 DAT drive being put offline by power failures,
> >operator neglect or whatever.  To solve this problem I obtained
> >ONLINE from Allegro and inserted into my Job File.  But it seems
> >to me that the problem must be deeper than this.  The absence of
> >a Standard List is most disturbing.
> >
> <<some deleted>>
> >
> >Our environment is HP3000/935 c/w 96Mb MPE/iX 5.0 push - no
> >patches.
>
> It sounds like a CPU utilization problem. Because the job never opens
> a spoolfile, there is no listing generated when the job is aborted.
> The job is never getting past initialization for some reason and it is
> most likely the fact that it is a job and you could have a CPU hog
> running in the CQ that is keeping the backup job from getting any time.
>
> First of all, determine if the job is actually ready to run or is it
> hung up waiting for some resource. Execute the ":SHOWQ ;ACTIVE"
> command to see if the job is listed. If not, there is sme sort of
> resource it needs and is waiting for. Call the RC and we can help
> determine what it is.
>
> If the job is listed and you have GLANCE or SOS, take a look at the
> system and see what process is getting all of the CPU time. If you don't
> either, then the ":SHOWQ ;ACTIVE" command can be used; just look for
> a higher priority process that seems to always be ready to run. It will
> generally be at the limit of the CQ (assuming you don't have the CQ set
> to "OSCILLATE".
>
> Once you have identified the process you will need to figure out if
> it is in fact the culprit. Try altering it's priority to the EQ and see
> if the backup job starts running. If not, you may have chosen the wrong
> process or there are more than one. You will then, of course need to
> decide if the problem is with these proceses or if they just should
> not be running at the same time as your backup.
>
> If all else fails, just call the RC and we will see what we can do to
> help. OBTW, I would not recommend running 5.0 PUSH with no patches.
> Please order and install the latest POWERPATCH.
>
>
> --
>                             --Pete Crosby
>                               [log in to unmask]
>
> ************************************************************************
> *  Note: my comments are my own and do not reflect the views of my     *
> *        employer or necessarily anyone else.     [log in to unmask]       *
> ************************************************************************