Michael,
It happens according to following scenario:
Preconditions - out.hpspool group is not cleared.
                Machine is not rebooted for al least more than 16383 jobs.

Max job number in MPE is 16383 (AFAIR). When this nomber is reached, job
numbers are 'reset' to 1 and thus gobs get numbers from the beginig again.
If job number (say) #j132 still runs since startup, the OS skips this number
for new jobs to come.

So that after the machine was first rebooted, you run job #j144 that
completes o.k. and now it have OFID #o00347.
You continue to run jobs until you reach #j16383 which has
#o(347+16383=16730). Next youll reach #j144 again - which now have different
OFID (say #o16850).

So now when you do SHOWOUT job=#j144 Youll get from the OS (smart enough)
two outspool files:
16730 and 347.

At least that what I get...

        Regards,
        Noam Koren
        BMC/New Dimension Software
        voice: 972-3-7664508    fax: 972-3-6451100
        [log in to unmask]
>       bmcsoftware


-----Original Message-----
From: Michael Anderson [mailto:[log in to unmask]]
Sent: Wednesday, January 05, 2000 8:59 PM
To: [log in to unmask]; [log in to unmask]
Subject: Re: Out Spoolfile id within a program


I don't mind showing my ignorance, so could anyone explain
in detail the events that must take place for a job to have TWO
$STDLIST's?


>>> "Koren, Noam" <[log in to unmask]> 01/05 10:12 AM >>>
:so j13049

DEV/CL   DFID       JOBNUM  FNAME    STATE FRM SPACE RANK PRI #C
LP       #O18314    #J13049 $STDLIST READY         16    D 1   1
LP       #O34695    #J13049 $STDLIST OPENED       256      1   1