Gordon,

So far, the best I've figured is calling for the most immediate issue of the
monthly archive.  This will be "current" from the point of "shipment" plus
everything prior through the month's start.

The group's collective wisdom may arrive at "instructions" to get
Maelstrom to recognize requests for the most "current" 100.

Otherwise you'll need to rough it.

The specific monthly archive log can be obtained by requesting an Index.

Hope this helps.

S.


----- Original Message -----

To: "I. Stephen Margolis" <[log in to unmask]>
Sent: Monday, September 25, 2000 1:40 AM
Subject: Re: Output of your job "ismarki"


> > Get CO-PALSY LOG0009
> File "C-PALSY LOG0009" has been mailed to you under separate cover.
>
> Summary of resource utilization
> -------------------------------
>  CPU time:        0.860 sec                Device I/O:      184
>  Overhead CPU:      N/A                    Paging I/O:        0
>  CPU model:         AlphaServer 1000A 5/400 (640M)
>  DASD model:        4 Member RAID 0+1
>  Job origin:      [log in to unmask]
>