USP/NSC
MICROCODE VERSION 50-09-98-00/16-M362
RELEASED 10/07/2012
Newly supported features and functions for Version 50-09-98-00/16-M362
1. Mainframe & OPEN System
1-1 Support for HUS and HUS VM as new external storages
Description Hitachi storages, HUS and HUS VM, are supported as external storages without profile
installation tools required.
Changed Part DKCMAIN
Note Upgrade of micro-program:
If any volumes have been mapped as external HUS/HUS VM volumes, delete all the
external volumes and then upgrade the micro-program to the supported version.
Downgrade of micro-program:
Before downgrading the micro-program to an unsupported version, delete the HUS/HUS
VM mapping devices. (online, offline)
Documented Appendix-I I-1 (Support Conditions)
2. Mainframe System
NONE
3. Open System
NONE
The change of contents for Version 50-09-98-00/16-M362
1 Failure of maintenance or SI pair operation after failure reset
Phenomena After a failure reset, SSB=15B9 was output and cache, LDEV, or PDEV
related maintenance or an SI pair operation failed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when a failure reset occurs after the following
operation (1) or (2) is performed.
(1) Cache, LDEV or PDEV related maintenance.
(2) SI pair operation.
* The problem occurs when a failure reset occurs in a specific program
step during queue operations on job management areas.
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 50-09-98-00/16
Category Open and Mainframe
Changed Part DKCMAIN
HDS Confidential 1 of 4
2 Failures of UR/URz pair creation and following JNLG deletion
Phenomena Phenomenon1
When a pair creation failed, the pair status was SMPL but licensed
capacity of the failed pair increased. (SSB=E883, Storage Navigator
message=6505-58088, CCI/BCM error code=E883). At that time, an
existing UR/URz pair was suspended due to failure.
Phenomenon2
After the phenomenon1, when an LDEV used for the failed pair creation
was selected and then a pair creation was performed again, a message
saying that UR had already been registered was output and the pair
creation failed. (SSB=EA01 or EA03, Storage Navigator message=6505-
58288 or 6505-58289, CCI/BCM error code=EA01 or EA03)
Phenomenon3
After the phenomenon1, when all pairs in a mirror were deleted and then a
JNL group was deleted, a message was output saying that a data volume
existed and deletion of the JNL group failed. (SSB=E81B, Storage
Navigator message=6505-58037, CCI/BCM error code=E81B)
Phenomenon4
After the phenomenon1, when all pairs in a mirror were deleted and then a
pair was created again, a message was output saying that the number of
data volumes that could be registered in a mirror exceeded the maximum
and the pair creation failed. (SSB=E891, Storage Navigator
message=6505-58092 or 6505-58281, CCI/BCM error code=E891)
Severity (High, Medium, Low) Medium
Conditions of Occurrence The phenomenon1 may occur when the following conditions (1) to (4) are
met.
The phenomenon2 may occur when all the following conditions are met.
(1) Universal Replicator or Universal Replicator for z/OS
(2) A pair is registered in a mirror.
(3) A pair is created for the above mirror as its 2nd pair.
(4) The above pair creation fails.
(5) A pair creation is performed while specifying LDEV# and mirror#
which are specified in the pair creation of (3).
The phenomenon3 may occur when the following conditions (6) to (9) are
met after the phenomenon1 occurs.
The phenomenon4 may occur when the following conditions (6) to (8) and
(10) are met after the phenomenon1.
(6) PS OFF/ON
(7) All pairs in the mirror of (2) is deleted.
(8) Force Delete with LU specified is performed from Storage Navigator
for the LDEV in SMPL to which the pair creation of (3) fails.
(9) The JNL group to which deletion of all pairs is performed in (7) is
deleted.
(10) Pair creation is performed for the JNL group to which deletion of all
pairs is performed in (7).
Affected Products/Version DKCMAIN: 50-03-30-00/00 and higher
Fixed Product/Version DKCMAIN: 50-09-98-00/16
Category Universal Replicator, Universal Replicator for z/OS
Changed Part DKCMAIN
HDS Confidential 2 of 4
3 Unable to display Battery Life SIM Warning window
Phenomena When trying to set Battery Life warning SIM, the Battery Life SIM setting
window could not be displayed.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem occurs when Remained Battery life value exceeding the year
of 2038 as SIM reporting date is set during Battery Life Sim setting.
Affected Products/Version SVP: All
Fixed Product/Version SVP: 50-09-96/00
Category SVP
Changed Part SVP
4 Maintenance failure when DKP is blocked
Phenomena After maintenance of DKA/DKU/FSW/HDD while a DKP was blocked
due to failure, maintenance such as SI pair split and parity group removal
failed with time-out and SVP message ONL0117E was output.
Severity (High, Medium, Low) Medium
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) 3 or more DKPs are blocked.
(2) One of the following maintenance operations is performed.
- DKA/DKU installation/removal
- DKA/FSW/HDD replacement
- HDD micro-program exchange
- DKU inline
- Particular PCB replacement (such as ALPA LED)
- User replacement (simplification)
Affected Products/Version DKCMAIN: All
Fixed Product/Version DKCMAIN: 50-09-98-00/16
Category Open or Mainframe
Changed Part DKCMAIN
5 Failure of WWN performance data collection and SVP reboot
Phenomena When there were 256 or more channels registered as monitoring targets
between ports and WWNs, if Export Tool with "PPCGWWN" specified
was executed or the WWN tab on SPM window of Storage Navigator was
displayed, Storage Navigator message 4-6001 was output, WWN
performance data was not obtained and SVP was rebooted.
Severity (High, Medium, Low) Medium
Conditions of Occurrence Issue occurs with conditions (1) and (2), or (3) and (4) met.
(1) There are 256 or more channels registered as monitoring targets
between ports and WWNs in DKC.
(2) Export Tool is executed with group PPCGWWN specified in a
parameter (command.txt).
(3) There are 256 or more channels registered as monitoring targets
between ports and WWNs for an SPM group.
(4) The WWN tab on SPM window is opened and information of the
above SPM group is displayed.
Affected Products/Version DKCMAIN: 50-06-11-00/00 and higher
Fixed Product/Version DKCMAIN: 50-09-98-00/16
Category Performance Monitor
Changed Part SVP
HDS Confidential 3 of 4
6 Failure of pair status change when external VOL is blocked
Phenomena When an external VOL that was an SI/SIz copy target was blocked during
SI/SIz Split copy processing while SOM459 was set to ON, the pair status
did not change correctly as follows.
SI: The pair status did not change to PSUE but SSB=2151 was output and
then the status changed to PSUS, or the status did not change but remained
copying in some cases.
SIz: The pair status did not change to Suspend but SSB=2151 was output
and then the status changed to Split, or the status did not change but
remained copying in some cases.
Severity (High, Medium, Low) Low
Conditions of Occurrence The problem may occur when all the following conditions are met.
(1) SOM459 is set to ON.
(2) SI/SIz Split copy is performed using an external VOL as an SI/SIz
copy target.
(3) The external VOL is blocked when the SI pair status is COPY (SP) or
PSUS (SP), or the SIz pair status is SP-PEND or V-Split.
Affected Products/Version DKCMAIN: 50-03-93-00/00 and higher
Fixed Product/Version DKCMAIN: 50-09-98-00/16
Category Shadow Image, Shadow Image for z/OS
Changed Part DKCMAIN
HDS Confidential 4 of 4
