[This note has been sent to the following InterNet address(es):
[log in to unmask]]
 
 
I asked :
>> Has anyone written anything or know of anything that can calculate the number
>> of sectors required by the filesets included in an indirect file for a STORE
 
Stan Sieler replied :
>This question has a variety of partial answers/comments:
> 1) no
> 2) yes, try doing:
 
>       :file null = $null
>       :STORE <your complete fileset/indirect/whatever>; *NULL; SHOW
>
>     capture the output of the STORE, add up the "sectors" column, and
>     presto...your answer.
[Snip remainder of interesting notes about files]
 
I tried this but got the message below :
 
:file null=$null
:store ^ind;*null;show
          >> TURBO-STORE/RESTORE  VERSION  A.40.20  HP36398A <<
                    (C) 1986 HEWLETT-PACKARD CO.
THU, AUG  3, 1995,  9:17 AM
 
 
FILENAME GROUP    ACCOUNT  VOLUME RESTRICTIONS             SECTORS CODE   MEDIA
DEVICE FILE "NULL" HAS A INVALID RECORD SIZE OF  BYTES (MINIMUM
SIZE IS 8192 BYTES, MAX IS 16384 IN MULTIPLES OF 2048 BYTES).
DEFAULT OF 16384 BYTES WILL BE USED  (S/R 2225)
DEVICE FILE "NULL" REFERENCES STORAGE MEDIA THAT CANNOT
BE USED BY STORE/RESTORE.  ONLY 1/2 INCH TAPE, DIGITAL DATA
STORAGE (DDS) DEVICE AND MAGNETO-OPTICAL MEDIA IS SUPPORTED
IN NATIVE MODE  (S/R 2215)
 
which seems a little verbose for an error message, still..I guess you cannot
file equate a STORE to null (although you can to $null). Anyway, I believe a
STORE to $null would still have to set all the store bits on and off again and
for a large fileset it would be a bit excessive. Evan Rudderow (I hope I spelt
it right) had another suggestion to use MPEX and the LISTF ^indirectfile
command which lists the total sectors for the "contents" of the indirectfile.
Unfortunately it falls down if any "exclude" filesets or parameters are in the
indirect file. Still, it seems promising and I will continue to investigate.
Thank you for your feedback.
John "I wish I could make it to Toronto" Dunlop ([log in to unmask])