A fix is available
APAR status
Closed as new function.
Error description
New Function APAR
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of FlashCopy command. * **************************************************************** * PROBLEM DESCRIPTION: This APAR implements support for * * Space-Efficient FlashCopy (FC/SE) that * * provides for the creation of Persistent * * FlashCopy Relationships that may be * * used for instant point-in-time backups * * and test data replication scenarios. * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** This APAR implements support for Space-Efficient FlashCopy (FC/SE) and provides for the creation of Persistent FlashCopy Relationships that may be used for instant point-in-time backups and test data replication scenarios. Space-Efficient volumes, available with appropriate Licensed Internal Code on the DS8000 System Storage (D/T2107), are real volumes whose tracks are allocated from a repository of space that is defined and maintained within an IBM System Storage Subsystem. As data are written onto Space-Efficient tracks, space is dynamically allocated to the volume only for tracks that are actually written. This can provide significant space savings in environments where sparse data update patterns exist. The IBM DS8000 System Storage FlashCopy feature enables the creation and control of point-in-time copies of volumes and extents by using persistent relationships. It is now possible for a FlashCopy target extent to exist on a normal or Space-Efficient volume. When a track on the source volume of any persistent FlashCopy relationship is updated, the older version of the track is copied by the hardware to the target device before the update to the source device is committed. For a Space-Efficient FlashCopy target, the older version of the track is written to space taken from a repository and assigned to the Space-Efficient volume. A storage repository provides the physical space for many Space-Efficient volumes. In this manner, the amount of physical space consumed by the target volume of a Space-Efficient FlashCopy relationship is limited to the minimum amount of space required to maintain the copy. The following use cases are envisioned for this functionality: System Backups: The use of the FlashCopy NOCOPY option in conjunction with a target can be used to facilitate system backups. Using such a setup would allow the customer to create a target that is a logical point-in-time duplicate image of the source that would only allocate DASD space from the repository to preserve tracks that are subsequently modified on the source by active applications. At the completion of the backup to tape then the target would be released and the preserved tracks returned to the repository... FLASHCOPY ESTABLISH SOURCE D000 TARGET D007 NOCOPY DDR input 3390 D007 output 3490 E000 copy all FLASHCOPY WITHDRAW TARGET D007 FORCE RELEASE Test data replication: Often systems designers and testers need to create a repeatable test database in order to test new software designs. In such a scenario the test data is "mastered" on a source volume and cloned onto a test volume. After the test is run the data is "resynced" from the master to the source in order to set it back to the source's current state in preparation for the next test run. New Modules/Copies/Macros: HCP28BIT HCPPFC HCPPFC$ HCPPFCR Changed Modules/Copies/Macros: BLDCPRLE BLDCPWLE HCPCUZ HCPDDQ HCPDPD HCPENTER HCPENTR HCPERP HCPEXCP HCPGTWKA HCPICU HCPIORBK HCPLENTR HCPLNS HCPMD3 HCPMD5 HCPMES HCPMESB HCPMXRBK HCPNFC HCPPROC HCPPROLG HCPQDA HCPQDB HCPQFL HCPQVC HCPRDEV HCPRDEV HCPRELST HCPRLWKA HCPXIO SDMCCWEQ SDMCCWEQ
Problem conclusion
Temporary fix
Comments
SC24-6083 CP Planning and Administration Guide Added sections to Chapter 21, DASD Sharing: * Using Persistent FlashCopy - How and where does the hardware read and write data to the source and target(s) during a persistent relationship? - Instant point-in-time backups (disk-to-disk) - Instant point-in-time backups (disk-to-tape) - Test data replication - Multiple LPAR FlashCopy considerations - CP-Owned areas and FlashCopy * Space-Efficient Volumes - Space-Efficient Volumes with CP areas -- Don't! - Space-Efficient Volumes and FlashCopy Backups - Space-Efficient Volumes and FlashCopy Test Data Replication SC24-6081 CP Commands and Utilities Reference The responses to the following commands have been enhanced: ATTACH LINK DEFINE MDISK QUERY VIRTUAL DASD The syntax of the following commands has been altered: FLASHCOPY QUERY VIRTUAL FLASHCOPY QUERY DASD QUERY CU DASD The following commands are new: FLASHCOPY BACKGNDCOPY FLASHCOPY ESTABLISH FLASHCOPY RESYNC FLASHCOPY TGTWRITE FLASHCOPY WITHDRAW QUERY FLASHCOPY GC24-6119 CP Messages and Codes Added messages: HCP0116I NOTE: Cylinders n though n of minidisk vdev are the source for FlashCopy relationship hhhhhhhh. WARNING: Cylinders n though n of minidisk vdev are the target for FlashCopy relationship hhhhhhhh. HCP2450E SOURCE operand missing. HCP2451E SOURCE must be a full-pack extent. HCP2452E SOURCE must be a minidisk extent. HCP2453E TARGET operand missing HCP2454E TARGET must be a full-pack extent. HCP2455E TARGET must be a minidisk extent. HCP2456E SOURCE and TARGET must both be full-pack or minidisk extents. HCP2458E SOURCE vdev specifies number cylinders but TARGET vdev specifies number cylinders. HCP2459E Unable to read or verify the current volume label on vdev. HCP2460E Unable to update current volume label on vdev. HCP2461I Volume label on vdev is now volser. HCP2462E extenttype extent on CP-OWNED volume volser, tracks cccc/hh to cccc/hh, is the Source for FlashCopy Relationship sequence. HCP2463E extenttype extent on CP-OWNED volume volser, tracks cccc/hh to cccc/hh, is the Target for FlashCopy Relationship sequence. HCP2464E Volser is missing after LABEL operand. HCP2465I No matches found. HCP2466I Device rdev - No FlashCopy relationships reported. HCP2467E The CP-OWNED volume volser is allocated on Space-Efficient device rdev. Space-Efficient volumes are not allow as CP-OWNED volumes. HCP2468E FlashCopy relationship(s) on CP-OWNED volume volser on device rdev, cylinders number through number, have been terminated. HCP2469E WITHDRAW failed because number tracks remain to be copied to vdev. HCP3201E DASD Error: message1 Message n: message2 Reason nn: message3 HCP9050W CP-OWNED volume is on a Space-Efficient DASD. HCP9051W FlashCopy relations were found in CP-OWNED, non-PERM space. Relations will be withdrawn. ž**** AE09/05/05 FIX IN ERROR. SEE APAR VM64636 FOR DESCRIPTION ž**** PE09/07/16 PTF IN ERROR. SEE APAR VM64644 FOR DESCRIPTION ž**** PE09/06/29 FIX IN ERROR. SEE APAR VM64684 FOR DESCRIPTION ž**** PE09/08/17 FIX IN ERROR. SEE APAR VM64713 FOR DESCRIPTION
APAR Information
APAR number
VM64449
Reported component name
VM CP
Reported component ID
568411202
Reported release
540
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
YesSpecatt / New Function
Submitted date
2008-05-27
Closed date
2008-12-05
Last modified date
2015-05-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UM32583 UM32584 UM32585
Modules/Macros
ATTACH BLDCPRLE BLDCPWLE CU DASD FLASHBND FLASHC FLASHCOP FLASHEST FLASHRES FLASHTGT FLASHWIT HCPCUZ HCPDDQ HCPDPD HCPENTER HCPENTR HCPEQUAT HCPERP HCPEXCP HCPGTWKA HCPICU HCPIORBK HCPISA HCPLENTR HCPLNS HCPMD3 HCPMD5 HCPMES HCPMESA HCPMESB HCPMESE HCPMXRBK HCPNFC HCPOCO HCPOM1 HCPOM2 HCPPARSE HCPPFC HCPPFC$ HCPPFCR HCPPOCO HCPPROC HCPPROLG HCPPSI HCPQDA HCPQDB HCPQFL HCPQUY HCPQVC HCPRDA HCPRDEV HCPRDX HCPRELST HCPRLWKA HCPRP HCPXIO HCP116I HCP2450E HCP2451E HCP2452E HCP2453E HCP2454E HCP2455E HCP2456E HCP2458E HCP2459E HCP2460E HCP2461I HCP2462E HCP2463E HCP2464E HCP2465I HCP2466I HCP2467E HCP2468E HCP2469E HCP28BIT HCP3201E HCP9050W HCP9051W LINK MDISK SDMCCWEQ VIRTDASD VIRTFLC VM64449
| SC24608306 | SC24608106 | GC24611906 |
Fix information
Fixed component name
VM CP
Fixed component ID
568411202
Applicable component levels
RA54 PSY UM32583
UP09/03/24 P 0901
RE54 PSY UM32584
UP09/03/24 P 0901
R540 PSY UM32585
UP08/12/15 P 0901
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"540","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
13 May 2015