Thanks Tom!! I knew it was something simple.. or in this case stupid.
Our operator decided to run an older version of the job and the command file
which
finds the STDLIST could not find it.... It must be a Monday!!!


 JOB FULLFRI,OPERATOR.SYS,SYSOPR.
 Priority = CS; HIPRI; Time = UNLIMITED seconds.
 Job number = #j957.
 FRI, AUG 11, 2000, 11:14 PM.


Rick 'brain still on weekend mode' Clark



-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Tom Brandt
Sent: Monday, August 14, 2000 9:21 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Monday morning Spoolfiles


I note the the spool file name (FILEDES) is FULLDUMP, which is not
necessarily the name of the job which created it.  Probably the JOBNAME of
the job which created the FULLDUMP file is not FULLDUMP,  but
FULL<something else>.

At 09:19 AM 08/14/00, Rick Clark wrote:
>Can anyone please explain to me why one flavor of this command works and
the
>other one doesn't???? I am on version 5.5 PP7.
>Note that the spoolfiles are 'restored' to the system (the ' in the
Jobnum).
>Is this a 'feature'?
>
>DPAICMD SYS:SPOOLF @;SELEQ=[JOBNAME=FULLDUMP];SHOW
>No qualified spoolfile(s). (CIWARN 4809)
>
>DPAICMD SYS:SPOOLF @;SELEQ=[JOBNAME=FULL@];SHOW
>
>SPOOLID    JOBNUM   FILEDES  PRI COPIES DEV      STATE  RSPFN OWNER
>
>#O27       J'957    FULLDUMP   1      1 LP5      READY        OPERATOR.SYS
>#O26       J'957    $STDLIST   1      1 CLP5     READY        OPERATOR.SYS


Tom Brandt
Northtech Systems, Inc.
http://www.northtech.com