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

Warnings Regarding Volume Security for Mainframe
This section provides specific warnings and advice related to security settings.
WARNING!
1. Do not apply security to volumes on which any job is running. If you apply security to such a
volume, the job may end abnormally.
2. When applying security, make sure that your security settings are correct. If incorrect security
settings are made, the system will be difficult or impossible to control.
3. If the CPU of a mainframe host is upgraded after you apply security settings, you must execute
the system command "D M=CPU" at the mainframe host to obtain the latest information about
the host. Next, you must use the latest information to update host information in the
Add/Change Host dialog box. If you do not update host information, the system will be
impossible to control.
4. If the port level security is applied to a configuration that has alternate paths, set the port level
security to all ports including alternate paths. If the port level security is not set to alternate
paths, jobs end abnormally on alternate paths.
When making security settings, it is important to be aware of these admonitions.
• If you are using P9500 copy software (Continuous Access Synchronous Z (Cnt Ac-S Z),
Continuous Access Journal Z (Cnt Ac-J Z), Business Copy for Mainframe (BC Z), and Compatible
FlashCopy or FC Z): When you use Volume Security for Mainframe to make security settings,
you must register the primary volume, the copy source, and the secondary volume, copy
destination volume, in the same LDEV group. For details on how to register volumes in LDEV
groups, see (page 50). If you apply security to a primary volume and a secondary volume of
a pair of Volume Security for Mainframe copy software, some or all mainframe hosts might
be unable to read from and write to the primary volume and a secondary volume. However,
the copy operation will be performed normally and the data will be copied from the primary
volume to the secondary volume.
If you register a primary volume or secondary volume in a security group and then make a
setting for preventing the volume from being used as a secondary volume, this setting will take
effect after the pair is split.
Mainframe hosts cannot access volumes in pool groups. If a volume in a pool group is specified
as a primary volume, the pair creation command might fail.
In the P9000 Continuous Access Synchronous for Mainframe Systems User Guide, primary
volumes (copy source volumes) are often referred to as M-VOLs or main volumes. Also,
secondary volumes (copy destination volumes) are often referred to as R-VOLs or remote
volumes.
In the P9000 Business Copy for Mainframe Systems User Guide, primary volumes (copy source
volumes) are often referred to as S-VOLs or source volumes. Also, secondary volumes (copy
destination volumes) are often referred to as T-VOLs or target volumes.
• When the license key for the Volume Security for Mainframe program product expires, the
volume setting that cannot be used for a secondary volume (copy target volume) becomes
invalid. After that, the volume can be used as a secondary volume in Continuous Access
Synchronous Z and Continuous Access Journal Z.
• When security is applied to the volume for a command device, copying from a primary volume
to a secondary volume is performed normally. However, when the port level security is applied
to the volume for a command device, a copy operation that uses the Business Continuity
Manager command can be performed only from a port for which access was permitted.
• If you are using Virtual LVI/LUN (VLL) volumes: If you apply security to a VLL volume, you will
be unable to change the VLL settings on the volume. If you want to change the VLL settings,
you must use Volume Security for Mainframe to disable security on the VLL volume.
144 Protecting volumes from I/O operations