IBM has stated they are fixing the QFileSvr.400 size limitation in
V6R1 via a PTF. The CAAC brought this up to IBM during one of our
requirements meeting last year, and IBM developed a fix for this. They said
it was too difficult to retrofit back to V5R4, but had created a fix for
V6R1. I use QFileSvr.400 all the time to move images around between
machines and LPARs at my clients. The CAAC and IBM have done a great job in
putting through a lot of requirements that the COMMON members have put
forth. V6R1 is filled with resolutions to requirements that have been put
through the requirement process. I know there will also be a booth at the
upcoming COMMON conference where people can write up their requirements to
COMMON & CAAC. It has really been great working with Steve Will and Guy
Havelick in getting IBM to address our concerns.
It's also easier to save an Image catalogue in V6R1 than it was in
V5R4, as there is some more information in the IFS directory so that when
you restore the directory you don't have to re-add the images to the IMGCAT
any longer.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, April 17, 2009 1:04 PM
To: Midrange Systems Technical Discussion
Subject: RE: VFYIMGCLG and ALWSAV Attribute
Well, when you go to V6R1 and start getting your image catalogs in DVD
size you will find out that QFileSvr.400 does not support files that big.
Heck, just try it with the DVD size install media for V6R1 even when are
still at V5R4.
I FTP mine around. I don't save them like Larry. But if I was doing an
unload/reload I'd really be concerned.
The big clue being not to load them into an image catalog prior to the
save. Load them into the image catalog after the restore.
Put that in your GO SAVE runbook to do a WRKIMGCLG first and unload any
loaded ones.
Rob Berendt
midrange.com
