Re: Virtual tape optimal image catalog entry size(s).

Well one thing I was wondering was, if I had the space set to 10GB and I
save 22GB to it will it just grow to accommodate it? I am guessing not.
So that's why I ran CHGIMGCLGE IMGSIZ(25000) on both entries. It didn't
change the allocated size (yet). Perhaps there's three sizes?
These you see with option 8 of WRKLNK:
1 - Size of object data in bytes . . . . . : 12369
2 - Allocated size of object . . . . . . . : 8662810624
And this you see with WRKIMGCLGE VRTCLG, option 2:
3 - Image size . . . . . . . . . . . IMGSIZ 25000

I am guessing that 2 can increase up to 3. And stays at the largest save
size it has completed until you delete/rebuild it.
I am also guessing that 1 increases up to the amount of data saved on that
tape at this time. It shrinks down on an INZTAP (fact).
1 is the size of the data actually sent in my ftp sessions.



Rob Berendt
-- Group Dekko Dept 1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com From: bdietz400@xxxxxxxxx To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>, Date: 02/07/2012 03:33 PM Subject: Re: Re: Virtual tape optimal image catalog entry size(s). Sent by: midrange-l-bounces@xxxxxxxxxxxx Rob, the way I read the ADDIMGCLGE ADDIMGCLGE IMGCLG(TAPE) FROMFILE(*new) TOFILE(tap02) ALCSTG(*MIN) Allocate storage size (ALCSTG) - Help Specifies for tape image files, whether to allocate the entire amount of storage specified on the Image size (IMGSIZ) parameter. *MIN Only allocate storage required to initialize the tape image file at the time of the create. *IMGSIZ Allocate the entire amount of storage specified on the Image size (IMGSIZ) parameter. The test lib I saved to a vrttape had about the size of the library itself. Am I close to what you were wondering about? Bryan
--