Having done many 6.0 updates it still amazes me that this pause is still in
there. The job limits are set down and run single threaded. Autoinst does
not stream a job until the previous job completes so I really don't
understand why the pause is necessary at all.

I haven't gone back to look at the 3000-L archives from when this was first
discussed, but the way I understand it, the pause was put in during testing
of the patch installation job. I suspect this is because the test was not
performed under a "normal" update environment, which could have made the
pause necessary. Then it was never removed from the patch installation when
it went GR.

Doug.

Doug Werth                             Beechglen Development Inc.
[log in to unmask]                               Cincinnati, Ohio

----- Original Message -----
From: H Lassiter <[log in to unmask]>
To: <[log in to unmask]>
Sent: Wednesday, November 29, 2000 6:01 PM
Subject: Re: Long 'pause' during 6.0 upgrade


> I had the same thing happen to me but also do not remember what job it was
in.
> I thought the system was hung until I looked at the $stdlist spool file
and saw
> the PAUSE 600.  HP should have put a warning on the console.  I was
getting
> ready to go for the phone and call the RC.  I guess they really wanted the
> preceeding jobs to finish first!
>
> Paul H Christidis wrote:
>
> > Fellow listers,
> >
> > During our recent 6.0 upgrade I noticed a long pause (around 10 minutes)
> > during step 5.15 (Rerunning AUTOINST).  Closer examination showed that a
> > batch job had been submitted that contained a 'pause 600' command just
> > prior to its end.
> >
> > We are about to upgrade another server and I'd like to eliminate most of
> > that additional wait.  Unfortunately I did not make a note of the file
name
> > involved, and the corresponding spool file has been deleted.
> >
> > Does anyone happen to have that name on their notes?
> >
> > Regards
> > Paul Christidis