Re: Migrating a file to SSD...

Remember, IBM stopped caring what you put in UNIT many releases ago. It
put the data wherever it darned well wanted to. It just left the
parameter there for compatibility reasons. UNIT was deprecated.

With SSD UNIT has risen from the ashes. The ONLY use for unit to to
specify ssd or not. If you have unit 100 in there and you mimix the file
over and you don't have 100 disk drives you will not have a problem. IBM
treats a value of 100 as (not 255) aka (not ssd).

Does that answer your question?

Nowadays, if you want to force files to reside on certain disks (outside
of the SSD discussion) you have to build an ASP containing those disks.
Understand?


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 02/28/2013 01:23 PM
Subject: Re: Migrating a file to SSD...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Rob, if your using MIMIX on a file such as this, how does this effect it
on
the target side or doesn't it really matter. Wouldn't the SSD unit number
need to match up.

On Thu, Feb 28, 2013 at 1:17 PM, <rob@xxxxxxxxx> wrote:

And if you fail to set the SST options to respect what you put in there
for media preference that file may be moved OFF of SSD if you run a
STRASPBAL with either *USAGE or *CAPACITY.

Lots of fun to get an approval for an outage to save/restore a library
where you already ran chgpf unit(*ssd) and then you run a STRASPBAL to
find it all moved back. :-(
Set the SST option!


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: rob@xxxxxxxxx
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 02/28/2013 01:01 PM
Subject: Re: Migrating a file to SSD...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



If you have the tool RTVCMDSRC you will see that unit SSD get's

translated

to unit 255. On 6.1 (and I think V5R4), where you didn't have the
parameter *SSD you just used 255.

So the question is:
Changing the unit to SSD, and having plenty of space doesn't force the
file to SSD immediately. (As verified by syspartitiondisk). How does

one

move it all physically over there:
- Save/restore?
- Some option in STRSST to activate it?
- STRASPBAL *MP?

Read the following two documents:
http://www.ibm.com/developerworks/ibmi/library/i-db2ssd/index.html

http://www-912.ibm.com/s_dir/slkbase.NSF/0/d42db94d78598d038625785c006ddc31?OpenDocument&ExpandSection=3

Document Number: 592252201

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
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: Robert Rogerson <rogersonra@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 02/28/2013 10:56 AM
Subject: Migrating a file to SSD...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Hi All,

Yesterday we attempted to migrate a large file (37 Gig) to the SSD
using
CHGPF. When I check the file (DSPFD) it confirms that UNIT(*SSD) is
now
changed.
This morning when I ran a query on syspartitiondisk it told my that

8%

(33
Gig on HDD and 4 Gig on SDD) had been migrated. I was expecting this
percentage to be higher if not at 100%.

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?

Thanks,

Rob
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.