Re: Migrating a file to SSD...

I should have mentioned this in the first place.

We are on V7R1 with 12 SSD (58B2) drives all at only 12.3 % used.

David, I have seen documented that if you specify UNIT(*SSD) on a system
with to SSD the system will not complain. The same file if restored on a
system with SSD will attempt to migrate the file. This I have read.

As mentioned 8% has been moved to the SSD and there is plenty more space
available. Am I wrong in assuming that if the space is available on the
SSD the entire file will be migrated?

Thanks,

Rob
On 2013-02-28 11:00 AM, David Gibbs wrote:

On 2/28/2013 9:54 AM, Robert Rogerson wrote:

Am I misunderstanding? If I specify the UNIT on a file to be SSD
does that not mean that the entire file will be migrated to the SSD?

The UNIT parameter on the CHGPF command is "Preferred Unit", not specific unit.

Setting the UNIT parameter to *SSD means you would LIKE it to be put on the SSD ... but it that doesn't guarantee the object will be put there.

I discovered this when testing SSD support for Implementer ... we don't have any SSD's on any of our systems, but I was able to specify *SSD for the unit parameter and the system was happy. It would TRY to put the object on a SSD if one is available.

The UNIT parameter is documented as not supported in 5.4 & 6.1.

david