HP XP P9000 Provisioning for Mainframe Systems User Guide
Table Of Contents
- HP XP P9000 Provisioning for Mainframe Systems User Guide
- Contents
- 1 Introduction to provisioning
- About provisioning
- Basic provisioning
- Fixed-sized provisioning
- Disadvantages
- When to use fixed-sized provisioning
- Custom-sized provisioning
- When to use custom-sized provisioning
- Basic provisioning workflow
- Thin Provisioning Overview
- Thin Provisioning Z
- Thin Provisioning Z concepts
- When to use Thin Provisioning Z
- Thin Provisioning Z advantages
- Thin Provisioning Z advantage example
- Thin Provisioning Z work flow
- Smart Tiers Z
- Tiers concept
- When to use Smart Tiers Z
- Resource groups strategies
- Complimentary strategies
- Key terms
- Before you begin
- About pool volumes
- 2 Configuring resource groups
- System configuration using resource groups
- Resource groups examples
- Meta_resource
- Resource lock
- User groups
- Resource group assignments
- Resource group license requirements
- Resource group rules, restrictions, and guidelines
- Creating a resource group
- Adding resources to a resource group
- Removing resources from a resource group
- Managing Resource Groups
- Using Resource Partition and other P9500 products
- 3 Configuring custom-sized provisioning
- Virtual LVI/Virtual LUN functions
- VLL requirements
- VLL specifications
- SSID requirements
- VLL size calculations
- Create LDEV function
- Blocking an LDEV
- Restoring a blocked LDEV
- Editing an LDEV name
- Deleting an LDEV (converting to free space)
- Formatting LDEVs
- Making external mainframe system volumes usable
- Assigning a processor blade
- Using a system disk
- 4 Configuring thin provisioning
- Thin Provisioning Z overview
- Smart Tiers Z overview
- Thin provisioning requirements
- Using Thin Provisioning Z or Smart Tiers Z with other P9500 products
- Thin Provisioning Z workflow
- Smart Tiers Z
- About tiered storage
- Tier monitoring and data relocation
- Smart Pool
- Tier monitoring and relocation cycles
- Tier relocation flow
- Tier relocation rules, restrictions, and guidelines
- Buffer area of a tier
- Smart Tiers Z cache specifications and requirements
- Execution modes for tier relocation
- Monitoring modes
- Notes on performing monitoring
- Downloading the tier relocation log file
- Tiering policy
- Tiering policy expansion
- Tiering policy examples
- Setting tiering policy on a THP V-VOL
- Tiering policy levels
- Viewing the tiering policy in the performance graph
- Reserving tier capacity when setting a tiering policy
- Example of reserving tier capacity
- Notes on tiering policy settings
- New page assignment tier
- Relocation priority
- Assignment tier when pool-VOLs are deleted
- Formatted pool capacity
- Rebalancing the usage level among pool-VOLs
- Execution mode settings and tiering policy
- Changing the tiering policy level on a THP V-VOL
- Changing new page assignment tier of a V-VOL
- Opening the Edit Tiering Policies window
- Changing a tiering policy
- Changing relocation priority setting of a V-VOL
- Smart Tiers Z workflow
- Smart Tiers Z tasks and parameters
- Managing Smart Tiers Z
- Changing a pool for Smart Tiers Z to a pool for Thin Provisioning Z
- Working with pools
- Working with THP V-VOLs
- Thresholds
- Working with SIMs
- Managing pools and THP V-VOLs
- Viewing pool information
- Viewing formatted pool capacity
- Viewing the progress of rebalancing the usage level among pool-VOLs
- Increasing pool capacity
- Changing a pool name
- Recovering a blocked pool
- Decrease pool capacity
- Deleting a tier in a pool
- Deleting a pool
- Changing external LDEV tier rank
- Increasing THP V-VOL capacity
- Changing the name of a THP V-VOL
- About releasing pages in a THP V-VOL
- Enabling/disabling tier relocation of a THP V-VOL
- Deleting a THP V-VOL
- 5 Configuring access attributes
- 6 Protecting volumes from I/O operations
- Overview of Volume Security for Mainframe
- Volume Security for Mainframe Requirements
- Volume Security for Mainframe Functions
- Protecting Volumes from I/O Operations at Mainframe Hosts
- Warnings Regarding Volume Security for Mainframe
- Supported Volume Emulation Types
- Maximum Number of Groups
- Maximum Number of Hosts and Volumes
- Launching Volume Security for Mainframe
- Viewing Security Settings
- Locating Volumes in a Specified Security Group
- Locating Security Groups that Contain a Specified Host
- Locating Volumes in a Security Group that Contains a Specified Host
- Locating Ports through Which Hosts Can Access Volumes
- Locating Security Groups that Contain a Specified Volume
- Locating Hosts in a Security Group that Contains a Specified Volume
- Locating Security Groups that Contain a Specified Host Group
- Locating Security Groups that Contain a Specified LDEV Group
- Limiting Host Access
- Prohibiting Host Access
- Protecting Volumes from Copy Operations
- Disabling Volume Security for Mainframe
- Editing Security Groups
- Editing Host Groups
- Editing LDEV Groups
- 7 Troubleshooting
- 8 Support and other resources
- A RAID Manager command reference
- B Resource Partition GUI reference
- C LDEV GUI reference
- Parity Groups window
- Parity Groups window after selecting Internal (or External) under Parity Groups
- Window after selecting a parity group under Internal (or External) of Parity Groups
- Window after selecting Logical Devices
- Create LDEVs wizard
- Edit LDEVs wizard
- Change LDEV Settings window
- View SSIDs window
- Select Free Spaces window
- Select Pool window
- View LDEV IDs window
- View Physical Location window
- Edit SSIDs window
- Change SSIDs window
- Format LDEVs wizard
- Restore LDEVs window
- Block LDEVs window
- Delete LDEVs window
- LDEV Properties window
- Top window when selecting Components
- Top window when selecting controller chassis under Components
- Edit Processor Blades wizard
- Assign Processor Blade wizard
- View Management Resource Usage window
- D Thin Provisioning Z and Smart Tiers Z GUI reference
- Pools window after selecting pool (Pools window)
- Top window when selecting a pool under Pools
- Create Pools wizard
- Expand Pool wizard
- Edit Pools wizard
- Delete Pools wizard
- Expand V-VOLs wizard
- Restore Pools window
- Shrink Pool window
- Stop Shrinking Pools window
- Complete SIMs window
- Select Pool VOLs window
- Reclaim Zero Pages window
- Stop Reclaiming Zero Pages window
- Pool Property window
- View Tier Properties window
- Monitor Pools window
- Stop Monitoring Pools window
- Start Tier Relocation window
- Stop Tier Relocation window
- View Pool Management Status window
- Edit External LDEV Tier Rank wizard
- Edit Tiering Policies wizard
- Change Tiering Policy Window
- E Volume Retention GUI reference
- F Volume Security for Mainframe GUI reference
- Volume Security for Mainframe window
- Add/Change Security Group Dialog Box
- Add/Change Host Group Dialog Box
- Add/Change LDEV Group Dialog Box
- Select LDEV Dialog Box
- Select Port Dialog Box
- Specify Security Group Dialog Box
- Host to Security Group Dialog Box
- Host to LDEV Dialog Box
- Host Group to Security Group Dialog Box
- Host Group to Port Dialog Box
- LDEV to Security Group Dialog Box
- LDEV to Host Dialog Box
- LDEV Group to Security Group Dialog Box
- Error Detail Dialog Box
- Glossary
- Index

LDEVs. Then, you can establish virtual THP volumes (THP V-VOLs) and connect them to the individual
THP pools. In this way, capacity to support data can be randomly assigned on demand within the
pool.
THP V-VOLs are of a user-specified logical size without any corresponding physical space. Actual
physical space (in 38-MB pool page units) is automatically assigned to a THP V-VOL from the
connected THP pool as that volume’s logical space is written to over time. A new volume does not
have any pool pages assigned to it. The pages are loaned out from its connected pool to that THP
volume until the volume is reformatted or deleted. At that point, all of that volume’s assigned pages
are returned to the pool’s free page list. This handling of logical and physical capacity is called
thin provisioning. In many cases, logical capacity will exceed physical capacity.
Thin Provisioning Z enhances volume performance by default. This is an automatic result of how
THP V-VOLs map capacity from individual THP pools. A pool is created using from one to 1024
LDEVs (pool volumes) of physical space. Each pool volume is sectioned into 38-MB pages. Each
page is consecutively laid down on a number of RAID stripes from one pool volume. The pool’s
38-MB pool pages are assigned on demand to any of the THP V-VOLs that are connected to that
pool. Other pages assigned over time to that THP V-VOL randomly originate from the next free
page of some other pool volume in the pool.
Setting up a Thin Provisioning Z environment requires a few extra steps. You still configure various
array groups to a desired RAID level and create one or more 3390-V volumes (LDEVs) on each of
them (see “Creating an LDEV” (page 41)). Then set up a Thin Provisioning Z environment by creating
one or more THP pools of physical storage space that are each a collection of some of these
3390-V LDEVs (THP pool volumes). This pool structure supports creation of 3390-A Thin Provisioning
Z virtual volumes (THP V-VOLs), where 38-MB pages of data are randomly assigned on demand.
For detailed information, see “Configuring thin provisioning ” (page 54).
When to use Thin Provisioning Z
Thin Provisioning Z is a best fit in a mainframe environment in the following scenarios:
• Where the aggregation of storage pool capacity usage across many volumes provides the
best opportunity for performance optimization.
• For stable environments and large consistently growing files or volumes.
• Where device addressing constraints are a concern.
Thin Provisioning Z advantages
With Thin Provisioning ZWithout Thin Provisioning ZAdvantages
You can logically allocate more capacity than
is physically installed. You can purchase less
You must purchase physical disk capacity for
expected future use. The unused capacity adds
Reduces initial costs
capacity, reducing initial costs and you can add
capacity later by expanding the pool.
costs for both the storage system and software
products.
When physical capacity becomes insufficient,
you can add pool capacity without service
interruption.
Additional capacity is added without service
interruption. Additional capacity requires
additional addresses and may require
modification of the IOGEN.
Reduces
management costs
You can allocate volumes of up to 262,668 cyl
(223,257 GB) regardless of the physical disk
capacity. This improves management flexibility.
As the expected physical disk capacity is
purchased, the unused capacity of the storage
system also needs to be managed on the
Reduces
management labor
and increases
P9500 product licenses are based on used
capacity rather than the total defined capacity.
storage system and on licensed P9500
products.
availability of
storage volumes for
replication
Effectively combines I/O patterns of many
applications and evenly spreads the I/O activity
Because physical disk capacity is initially
purchased and installed to meet expected
Increases the
performance
across available physical resources, preventingfuture needs, portions of the capacity may be
14 Introduction to provisioning