-----------------------------

Nameing Convention
-----------------------------
rootvg: lparname_R_LunID
Swapvg: lparname_S_LunID

Normal Dataluns: lparname_lunID
-----------------------------
Creating LUNS
-----------------------------
mkfbvol -extpool P2 -name qa6apod_R_5456 -cap 20 -volgrp V151 -eam rotateexts 54
56
mkfbvol -extpool P2 -name qb8apod_S_5457 -cap 20 -volgrp V152 -eam rotateexts 54
57
---------------------------
Listing LUNS in Vol Group:-
---------------------------
dscli> lsfbvol -volgrp V63
----------------------------
Vol groups Commands
----------------------------
lsvolgrp
showvolgrp V44
-----------------------------
Renameing the LUNs
-----------------------------
chfbvol -name qb3apod_R_5458 5458
chfbvol -name qb3apod_S_5565 5565
chfbvol -name CS_01E3 01E4
shareing the luns
-------------------------------------
chvolgrp -action add -volume 00E1 V45
-------------------------------------
chextpool -dev IBM.2107-75xxxxx -merge P5 P9
The first pool mentioned will be merged into the second pool so here you would e
nd up with P8 and P9
It is not possible to merge extent pools both of which contain space efficient r
epositories. Therefore in order to merge extent pools P2 and P3 into the larger
pool the space efficient repository and devices in these pools will have to be d
eleted and redefined.
Looking at the current usage of the extent pools it might actually make sense to
use the P0/P1 repository for the GM journal devices in P2/3 as this would be on
RAID5 disks which is better for random writes and if the workload is generally
low here the capacity usage for the GM journals should not be high. I'm not sure
I would want to place the space efficient repository for this in P8/P9 as we ha
ve two very different uses in the same repository.
Regards
mkhostconnect -dev IBM.2107-75xxxxx -wwnname -hosttype "pseries" -volgrp name_fc
s0/fcs1