I put a call in to the folks that manage patches to have them
take a look at that job. Ten minutes seems a tad long IMO.

When we write patches we sometimes have to write up these 'I' jobs
for unique circumstances. I just wrote one yesterday. So it is
possible that this pause was accidentally left over from testing.
The script JAVKXQ8C streams it and it then pauses 30 seconds to
wait for its completion so it seems the 10 min. pause may be a
left over.

I will see what I can find out about this.

+---------------------------------------------------------------------+
|Bill Cadier                         | MURPHY'S LAWS OF COMBAT:       |
|Hewlett-Packard Co.                 | Teamwork is essential, it gives|
|Commercial Systems Division         | the enemy someone else to shoot|
|Albuquerque, New Mexico             | at.                            |
[log in to unmask]          |                                |
+---------------------------------------------------------------------+

>
> Hi all
>
> Just a question, I am waiting for a job to run during the final phase of
> Patch/iX and was trying to figure
> out what had the job stalled. In looking at the STDLIST is see that it is
> waiting on a 'PAUSE 600' to
> expire. My question is why is this command in an installation job stream? The
> job name is IHFKXQ8C,
> and I received the express tape about a week ago.
>
> Thanks for any thoughts.
>
> Bob Schlosser
> (321) 674-4938
>