USP/NSC

MICROCODE VERSION 50-09-40-00/00

RELEASED 10/09/2007

Newly supported features and functions for Version 50-09-40-00/00

1. Mainframe & OPEN System

1-1 / New storage support
Description / If external storage connection, the following storages are supported without profile tools.
SUN ST2540
SUN SVA V2X2 (alternate path is not supported.)
To use this function, install the UVM program product.
Changed Part / DKCMAIN

2. Mainframe System

2-1 / URZ 4x4x4 3DC multi target function support
Description / This function is a combination of the following two-supportedUR for z/OS functions: 4x4 and differential data resync.This function enables users to perform remote copy of up to 65,498 pairs for URZ and TCZ respectively while guaranteeing data consistency. In addition, since the differential resync function is included, even if one of the sites in 3 Data Center fails, the production can switch to the rest of the 2 sitesin a short periodand without interruption.
Related program products:
- Universal Replicator for z/OS
- True Copy for z/OS
- True CopyAsynchronous for z/OS
To use the function, System Option Mode506 must be set on each site.
Changed Part / DKCMAIN

3. OPEN System

3-1 / AIX MPIO ODM VER. 5.4.0.2 support
Description / It is available to identify RAID500 and RAID600 on the AIX MPIO ODM VER. 5.4.0.2 in the configuration that the AIX MPIO host connects both RAID500 and RAID600.
For example: the following are able to be displayed:
Hitachi MPIO:
Hitachi MPIO Disk USP V (Fibre) (USP V/VM connection)
Hitachi MPIO Disk USP (Fibre) (USP/NSC connection)
HP MPIO:
HP MPIO Disk XP24000 (Fibre) (XP24000/20000 connection)
HP MPIO Disk XP12000 (Fibre) (XP12000/10000 connection)
Changed Part / ODM

The change of contents for Version 50-09-40-00/00

1 / Delta resync failure
Phenomena / The difference resynchronization operation to 1,000 or more pairs failed. When the status of the UR pair became HOLD, which was expected, the status of the UR pair for delta resync operation also became HOLD.
Severity (High, Medium, Low) / Low
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. HUR
2. Perform the difference resync operation to 1,000 or more pairs
Affected Products/Version / DKCMAIN: 50-07-51-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
2 / WCHK1 during difference resync in delta configuration
Phenomena / In the 3DC delta configuration with TC and UR used, and performing the difference resynchronization operation, WCHK1 occurred.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem occurs with all of the following conditions met.
1. UR for z/OS or Open
2. 3DC delta configuration where TC and UR were used
3. A JNLG has 1,000 or more pairs
4. Perform difference resync to differential UR pair in HOLD state
5. During #4, failure suspend occurs due to failure of status transition
Affected Products/Version / DKCMAIN: 50-07-51-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
3 / Status change problem after failure suspend during CM maintenance with URZ
Phenomena / During an initial copy with URZ in the 4x4 configuration, failure suspend occurred at the CM maintenance operation with SSB=EF3B output. After the failure suspend, however, the JNLG remained in the Suspending state, without changing to Suspend.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. UR for z/OS
2. In the JNLG that is registered in an EXCTG on RCU, status change (Flush/ Delete/ MCU failure/ RCU failure) occurs
3. During Suspend processing caused by #2, a failure occurs on RCU in such cases that JNL VOL blocked, both sides of SM (CM) are blocked, or an error occurs or maintenance is performed in highly loaded environment
Affected Products/Version / DKCMAIN: 50-07-51-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS
Changed Part / DKCMAIN
4 / SSB=0xb6d8 at RCU highly loaded
Phenomena / When RCU of TC was highly utilized, SSB=0xb6d8 may occur.
Severity (High, Medium, Low) / Low
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. True Copy for z/OS or Open
2. RCU is highly loaded
Affected Products/Version / DKCMAIN: 50-06-11-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy for z/OS or Open
Changed Part / DKCMAIN
5 / IOS050I (ICC) and SSB=0x5838(CHK2) with FICON 8M-Mfibre (FPP) PCB
Phenomena / With FICON 8M-Mfibre (FPP) PCB, IOS050I (ICC) was sometimes reported to the host, and SSB=0x5838 (CHK2) was sometimes output inside the DKC.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. Mainframe
2. FICON 8M-Mfibre (FPP)
3. Use PAV
Affected Products/Version / DKCMAIN: 50-09-34-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Mainframe
Changed Part / DKCMAIN
6 / EC=EBA9 at difference resynchronization
Phenomena / During a difference resynchronization operation, EC=eba9 was output.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. UR for z/OS
2. BCM used to issue command to third DKC for information acquisition
3. The third DKC is highly loaded
Affected Products/Version / DKCMAIN: 50-03-14-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS
Changed Part / DKCMAIN
7 / SSB=8f88 during initial copy of HUR pair using LUSE volume
Phenomena / During the initial copy operation of an HUR pair using a LUSE volume, failure suspend may occur with SSB=8f88 output.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. During the initial copy operation of an HUR pair using a LUSE volume
2. A reset occurs
Affected Products/Version / DKCMAIN: 50-09-01-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Open or mainframe
Changed Part / DKCMAIN
8 / SSB=bbf3 on PDKC and SSB=e909 on RDKC at HUR status transition
Phenomena / In the difference resynchronization configuration, when changing the HUR pair status during I/O operation, SSB=bbf3 and SSB=e909 occurred on PDKC and RDKC respectively.
Severity (High, Medium, Low) / Low
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. In the difference resynchronization configuration
2. Issue an I/O to an HUR pair
3. Perform Flush Suspend or Normal Delete to HUR pair specifying group
Affected Products/Version / DKCMAIN: 50-09-12-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
9 / Unrecognizable device from Standby path
Phenomena / Device unrecognized from Standby path when discovery operation performed for EVA Active/Standby or MSA Active/Standby.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / Problem occurs when external storage is EVA Active/Standby or MSA Active/Standby, and performing discovery operation via Standby path.
Affected Products/Version / DKCMAIN: 50-09-04-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Volume Manager
Changed Part / DKCMAIN
10 / Host I/O error or invalid status transition of UR pair
Phenomena / In a UR-TC configuration, the host I/O issued to the Open volumes suspended due to an I/O error. Or the status of the UR pair remained in COPY after changing from Suspend, without changing to PAIR.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / Problem may occur with any one condition A, B, or C met.
(A) With all of the following conditions met
1. Issue a write I/O to an OPEN-VOL
2. The P-VOL is used in the UR delta resync configuration
3. The status of the UR pair has changed from Suspend to Copy
(B) With all of the following conditions met
1. Issue a write I/O to an OPEN-VOL
2. The P-VOL is used in the UR multi target or delta resync configuration
3. A timeout occurs during the update copy operation of the TC pair
(C) With all of the following conditions met
1. Issue a write I/O to an OPEN-VOL
2. The P-VOL is used in the UR pair
3. The status of UR pair changed from PAIR or COPY to failure suspend
Affected Products/Version / DKCMAIN: 50-09-37-00/02 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for Open
Changed Part / DKCMAIN
11 / Suspend with EC=ecbc or ec94 during HUR 4x4 initial copy
Phenomena / In the restore processing on RCU during the HUR Initial Copy operation, TOV due to overload was detected when securing a cache segment, and Suspend occurred with EC=ecbc or ec94 output.
Severity (High, Medium, Low) / Low
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. HUR 4x4
2. During an HUR initial copy operation
Causes and Updates / System option mode 544 is available to fix the problem
Public Mode - No Permission Required to Use
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
12 / No output of SCSI reset logs
Phenomena / 1. A SCSI reset occurred, but no log for the reset was output
2. When using TC, a SCSI reset occurred on RCU, but SSB=da99 for confirmation of receiving the SCSI reset was not output
Severity (High, Medium, Low) / Low
Conditions of Occurrence / Phenomena #1 is currently undefined
Phenomena #2 when using TC, ABTS occurs on RCU
Causes and Updates / For Phenomena #1Information enhancement performed to acquire trace information for outputting the reset log
For Phenomena #2micro-program modified to fix the problem.
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy for Open
Changed Part / DKCMAIN
13 / Some UR pairs remaining in Suspend at group resync
Phenomena / When performing a UR group resync, some of the pairs in the group remained in Suspend, without changing to Duplex.
Severity (High, Medium, Low) / Low
Conditions of Occurrence / The problem may occur with all the following conditions met.
1. UR for z/OS or Open
2. Perform group resync after suspending pairs with UR purge spec
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / FDKCMAIN
14 / HUR pair remaining in Suspending after failure suspend during HUR copy
Phenomena / When a failure suspends occurred during the HUR copy operation, 1 out of 4,096 pairs remained in Suspending.
Severity (High, Medium, Low) / Low
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. UR for z/OS or Open
2. Preprocessing of HUR copy operation in either the following conditions
(1) Resync
(2) Perform MCU planned PS Off during the copy operation (in Duplex-Pending), and then resume the copy operation at PS On
3. During preprocessing in #2, a failure suspend for group of pairs occurs
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
15 / Failure of JNLG registration in ExCTG
Phenomena / Registering a JNLG in an EXCTG failed with the following error message (6505-58629) output:"The specified operation failed because of a temporary path failure. Retry the operation."(SSB=b762 (Host Program Error occurs), dd07 (LM dir bit remains))
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem occurs with all of the following conditions met.
1. UR for z/OS or Open
2. As a command device, use the JNLVOL that was used by the UR pair
Affected Products/Version / DKCMAIN: 50-03-30-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
16 / P-VOL left after deleting UR pairs with group specification
Phenomena / After deleting all the pairs in RJNL group with the S-VOL specification, when deleting all the pairs in the specified MJNL group, some P-VOL in the MJNL group left undeleted.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all the following conditions met.
1. UR for z/OS or Open
2. A JNL group has 1,000 or more pairs
3. After deleting all the pairs in the RJNL group with the S-VOL specification, delete pairs in the MJNL group with the group specification
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
17 / Force Delete unavailable to volumes in Suspending or Deleting
Phenomena / The Force Delete operation with LU specified was unavailable to a volume in the Suspending/Deleting state.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem occurs with all of the following conditions met.
1. UR for z/OS or Open
2. Pair deleteoperation to volume in Suspending/Deleting status from Storage Navigator
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
18 / TCZ pair suspended with EC=C992
Phenomena / During the micro-program update, GDPS freeze occurred, and one of the TC pairs suspended with EC=C992, which indicates that the transfer data for update copy is not available (Dirty Bit in SGCB is Off). SSB EC=C992 shows sense of'101010f0 0a0000fb b14a0ca5 00eaf60ca500eaf4 8700feb1 160060e0 0b000000'Byte x07,08=fbb1
Severity (High, Medium, Low) / Low
Conditions of Occurrence / The problem occurs with all of the following conditions met.
1. TC for z/OS (ESCON or FICON)
2. Perform Sync update copy by remote IO (other than GIO)
Affected Products/Version / DKCMAIN: 50-07-51-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy for z/OS
Changed Part / DKCMAIN
19 / TC pair failure suspend at Resync
Phenomena / When performing Resync to TC pairs from BCM, failure suspend occurred to one out of the 4,878 pairs.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem occurs with all of the following conditions met.
1. When using TC, TCA, or UR, perform PS On to a pair in the Pair create or Pairresync operation , or in the pending state
2. Use two or more CUs
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy Sync/Async z/OS/Open, Universal Replicator z/OS/Open
Changed Part / DKCMAIN
20 / TC Sync/Async pair creation delay after EC=cb23
Phenomena / The TC pair creation took longer time after EC=cb23 occurred.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. During the TC Sync/Async pair creation, EC=cd23 occurs.
2. After the error occurs, perform TC Sync/Async pair creation.
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy Sync/Async for z/OS or Open
21 / IPL failure with MIH at defrag from BCM
Phenomena / When using command device of BCM online and performing defrag, an MIH occurred. After that, host IPL occurred, but operation failed.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. To command device of BCM, configure two or more host paths each of which belongs to different path groups
2. To command device of BCM, perform an operation, such as long-term Reserve, that causes an I/O from another path group to be in DEVBUSY
3. Under situation #2, perform a pair operation or Read/Write operation from a host path in another path group to the command device of BCM
4. Status as result of operation #3 becomes DEVBUSY, and MIH occurs
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy for z/OS
Changed Part / DKCMAIN
22 / Long processing time of TC Take Over
Phenomena / When performing TC Take Over, it took time to start the differential copy processing and the SWAP might take long time (10 seconds) to complete (10 MB/2 LDEV).The differential copy processing referenced the I/O execution information and operated when no I/O was in progress. However, since the I/O execution information remained for a period, the differential copy processing could not start immediately so that the SWAP took long time to complete.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem occurs when performing a TC Take Over operation.
Causes and Updates / The micro-program modified so that system option mode 541 releases I/O execution information immediately.
Restricted Mode –RSD Permission Required to Use
Affected Products/Version / DKCMAIN: 50-09-37-00/02 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy
Changed Part / DKCMAIN
23 / Coexistence of M-VOL and R-VOL in TCA LUSE
Phenomena / In the same TCA LUSE volume, M-VOL might coexist with R-VOL.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem may occur with all of the following conditions met.
1. TCA R-VOL
2. LUSE
3. When LDEV in Suspend and Suspending coexist in a LUSE volume, perform Swap Resync with group specification
Affected Products/Version / DKCMAIN: All
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / True Copy Async for Open
Changed Part / DKCMAIN
24 / When deleting UVM device or V-VOL, SSID is deleted falsely
Phenomena / When deleting an external device or a V-VOL group, there is a volume to which the same SSID as the volume to be deleted is assigned, but the SSID is deleted falsely. As a result, the following phenomena could occur.
(a) Install CV, Make Volume, and Volume Initialize performed from Storage Navigator fail with Storage Navigator Error Code [0003-1045]‘The specified Subsystem ID already exists. Specify another SSID.’
(b) Volumes unrecognized from the mainframe host
(c) Pair creation and pair recovery of True Copy, True Copy for z/OS, Universal Replicator, Universal Replicator for z/OS, and HODM not performed.
(d) RCU registration of True Copy, True Copy for z/OS, Universal Replicator, Universal Replicator for z/OS, and HODM not performed.
(e) Data migration copy from RAID500 volumes using HODM fails.
Severity (High, Medium, Low) / High
Conditions of Occurrence / With all the following A to C met, SSID is deleted falsely.
A. Micro-program version is 50-09-34-00/00 or later
B. UVM device deleted, or Snapshot V-VOL group deleted
C. A volume not to be deleted exists in the SSID boundary to which the volume to be deleted belongs
Phenomena (a) to (e) occur with SSID deleted falsely with conditions of occurrence described in the following (a-1) to (a-5) met.
(a-1) Phenomenon (a): A volume with SSID deleted exists in subsystem
(a-2) Phenomenon (b): Occurs with either conditions D or E met
D. The volume with SSID deleted reports SCI (DKC status change)
E. At time of VARY ON, same system contains multiple deleted SSID
(a-3) Phenomenon (c): With SSID of MCU or RCU deleted
(a-4) Phenomenon (d): With SSID of MCU deleted
(a-5) Phenomenon (e): With SSID of RCU (RAD500) deleted, and SCI (DKC status change) reported
Causes and Updates / At the time of deleting an external device or a V-VOL group, the SSID assigned to the boundary deleted only when all volumes in the SSID boundary are deleted. In this case, the process of detecting volumes to be deleted in the SSID boundary has a problem. Due to the problem, even though a volume to be deleted exists, the SSID is deleted, and an invalid value, 0xFFFF, is specified. This makes the configuration information invalid. As a result, an error is detected with the SSID check logic, and the phenomena (a), (c), and (d) occur.In addition, when a volume in the deleted SSID boundary is accessed, 0xFFFF is reported to the host as an SSID. Consequently, the inconsistency with the SSID that is recognized by the host is detected, and the phenomena (b) and (e) occur.
Furthermore, when multiple SSID are deleted in the same system, multiple SSID whose values are 0xFFFF exist. As a result, the overlapping SSID is detected by the check of overlapping SSID performed by the host, and the phenomenon (b) occurs.
Affected Products/Version / DKCMAIN: 50-09-34-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Volume Manager, Copy-on-Write Snapshot, True Copy, True Copy for z/OS
Universal Replicator, Universal Replicator for z/OS
Changed Part / DKCMAIN
25 / Non-specified LDEV# deleted at S-VOL deleting in LU range
Phenomena / When deleting S-VOL in the range of LU, LDEV#:0x0000 was deleted, which was not the specified LDEV.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem occurs with all of the following conditions met.
1. UR for z/OS or Open
2. Delete S-VOL in the range of LU by selecting pairs in Suspend
3. The S-VOL of LDEV#:0x0000 exists in the same DKC/Mirror# where the S-VOL for deletion belongs
Affected Products/Version / DKCMAIN: 50-09-14-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for z/OS or Open
Changed Part / DKCMAIN
26 / Suspend with SSB=8ea3 on PDKC at UR pair status change
Phenomena / During the I/O operation to the P-VOL of a UR delta resync pair, if the pairresync operation was performed to change the pair status from SUSPEND to COPY, failure suspend occurred on the primary DKC with SSB=8ea3 output.
Severity (High, Medium, Low) / Medium
Conditions of Occurrence / The problem occurs with all of the following conditions met.
1. Open volumes
2. UR delta resync pair
3. I/O to the P-VOL of the UR pair is in progress
4. Perform the pairresync operation to the UR pair in SUSPEND
Affected Products/Version / DKCMAIN: 50-06-11-00/00 and higher
Fixed Product/Version / DKCMAIN: 50-09-40-00/00
Category / Universal Replicator for Open
Changed Part / DKCMAIN

HDS Confidential1 of 10