This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM does not intend to provide a solution to this request at this time, so it is being closed.
Marking all files in a library to use SSD is not generally a good practice, so IBM is not going to implement this request. In the rare situation where this might be appropriate, you could automate the task with an SQL procedure, something like provided below.
This procedure is passed the library name and then alters every table in the library to specify SSD as its preferred storage.
create or replace procedure coolstuff.alter_to_ssd (schema_name varchar(128))
begin
for table_list as select * from qsys2.systables where table_schema = schema_name and table_type = 'T' do
execute immediate 'ALTER TABLE ' concat schema_name concat '.' concat table_name concat ' ALTER UNIT SSD ';
end for;
end;
call coolstuff.add_to_ssd ('MYLIB');
The CEAC has reviewed this requirement and recommends that IBM not implement this request.
We can see why this would seem appealing but generally it is not considered good practice to put every object in a library on SSD, some objects will not benefit from this and given the additional cost of SSD over HDD then then handling it on an object by object basis for seem more sensible, especially if you automate it.
That said, if you wanted to achieve this today there are three options you consider on current versions of IBM i with out the need for enhancement.
1) You could create a new ASP
This would be comprised only of SSDs, you could then create a library / schema in this new ASP and then any objects you place in there will reside on the SSD disks in that ASP.
2) If you just wanted to move Files / Tables to SSD
You could create a simple routine even CL would work to DSPOBJD all *FILE objects in a Library into a file, then read through the objects and assign the UNIT(*SSD) to them.
3) BRMS has the ability to automate the management of the two options described above.
More information at the link below:
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Backup,%20Recovery%20and%20Media%20Services%20(BRMS)%20for%20i/page/Migration
We hope that this helps.
Background: The COMMON Europe Advisory Council (CEAC) members have a broad range of experience in working with small and medium-sized IBM i customers. CEAC has a key role in working with IBM i development to help assess the value and impact of individual RFEs on the broader IBM i community, and has therefore reviewed your RFE.
For more information about CEAC, http://www.comeur.org/i4a/pages/index.cfm?pageid=3285
Dawn May - CEAC Program Manager