If your job is looking for a printer which is not spooled, it will hang
in there waiting for the printer. No error message will be displayed. If
this is the case with your job, use
SPOOLER nnn;OPENQ;START ( or use classname instead of device # nnn ).
Abdel

-----Original Message-----
From: Forrest Smith <[log in to unmask]>
To: [log in to unmask] <[log in to unmask]>
Date: Friday, November 06, 1998 7:51 AM
Subject: Job logons taking forever


>Hey there fellow listers,
>
>Here's one for ya.  Yesterday we had a problem with our 996/200.  It was
>that when a job would logon it would take forever to actually start
>processing.  We ran GLANCEXL and the job was getting plenty of CPU but
>wasn't moving past the logon.  Every job had the same symptom.  We checked
>OUT.HPSPOOL, nothing out of the ordinary there but we purged a few
>spoolfiles anyway.  We checked the Q's to see if some @#%$ had messed with
>something but found no changes.  HP logged on and checked our logs and said
>everything looks clean.  I proceeded to limp through the day and started a
>backup as soon as I could.  I eventually ended up shutting the system down
>which took forever and got a weird message which is the only thing I can
>think of that might have caused the problem.  The message was  SYSTEM PIN
>NUMBER 80 TIMED OUT.  After that the system shutdown normally to SHUT6 and
>came up normally as well.  We are doing fine now but if anyone can think of
>another reason this may have been happening I would appreciate the input.
>I need to have some closure to this or at least have a direction other than
>a shutdown to fix the problem if it happens again.  And if it was a system
>process that was slowing everything down why did it not show up in GLANCE.
>Hopefully one of you gurus can give me a little insight.
>
>Thanks
>
>Forrest Smith
>Systems Manager
>Reviewco