Here's one way to fine tune that estimate:
http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/rzahc/storageconsiderationsforimagecataloginstallation.htm
I've downloaded the cume and all group ptf's for 7.1 into an image
catalog. That directory takes 24,219,982K.
here's something to consider:
Let's say you go to ESS and download 7.1. Then you FTP them up to your
IBM i into some directory. It knows nothing that this directory is used
for virtual optical yet. Does the stuff stay spread out?
Now you run CRTIMGCLG IMGCLG(V7) DIR('/mydir') CRTDIR(*NO). Does it take
everything in that directory, at this time, and move it to Load Source?
Now you call the new API or you run ADDIMGCLGE IMGCLG(V7)
FROMFILE('/mydir/item1.bin') TOFILE(*fromfile). Does it take that file in
that directory and move it to LS at this time? Normally the command runs
really speedy if you specify TOFILE(*FROMFILE).
Does it really require the image catalog -entries- be on Load Source, or
just the *IMGCLG object itself? If so, when does it pick up and move that
directory to LS?
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.