HP HPE XP P9500 Instruction Manual

HP P9000 for Business Continuity Manager
Software 6.6.1-01
Release Notes
HP Part Number: T5253-96056
Published: September 2011
Edition: Second

© Copyright 2009, 2011 Hewlett-Packard Development Company, L.P.

Version: 6.6.1
Description
This document contains release notes on the HP P9000 for Business Continuity Manager Software.
Update recommendation:
Recommended
Supersedes:
6.6.0-00
Product models
Table 1 Storage system firmware levels
Hardware support functionRequired microcode versionStorage system
0x22 or lower60-02-33 or laterHP XP24000 Disk Array
HP XP20000 Disk Array
0x16 or lower50-09-11 or laterHP XP12000 Disk Array
HP XP10000 Disk Array
0x04 or lower21-14-28 or laterHP XP1024 Disk Array
0x30 or lower70-00-35 or laterHP P9500 Disk Array
Devices supported
HP for Business Continuity Manager Software on IBM.
Operating systems
Either one of the operating systems shown in the following table is required.
Table 2 Applicable operating systems
Required versionOperating systems
V2R10OS/390
V1R1 - V1R12z/OS
License keys
You cannot use the license keys that you installed for release 05-03 or earlier. This version requires a
new style license key. The new style license key length is 75 characters.
Languages
International English
Enhancements
This version of Business Continuity Manager (BCM) supports the following functions and features:
Table 3 Supported enhancements and features
New Features and EnhancementsItem
As a hardware enhancement, the Open/MF Consistency
Preservation Function in Continuous Access Synchronous is
Storage System features
Description 3

Table 3 Supported enhancements and features (continued)
New Features and EnhancementsItem
available (P9500). This function preserves a consistency of
a C/T group including a copy group for Open and a copy
group for MF.
When a local disk is scanned by YKSCAN command, the
capacity of volume is obtained in cylinder. Also the capacity
is obtained by YKQRYDEV.
Operation improvement
When generating a copy group definition, the volumes of
P-VOL and S-VOL are checked. When the capacity is not
obtained or their capacities are not equal, a warning screen
will be displayed.
BCM can use each function by the shown storage system.
Table 4 BCM function by storage system
Required firmware versionStorage systemFunction
60-05-00 or laterXP24000/XP20000Compatible FlashCopy linkage function is
enabled when the Cnt Ac-J copy pair is in
the DUPLEX status 70-01-23 or laterP9500
60-08-01 or laterXP24000/XP20000Compatible FlashCopy linkage using the
Preserve Mirror function when the Cnt Ac-S
copy pair is in the DUPLEX status
60-05-00 or laterXP24000/XP20000Delta Resync function using the Delta Resync
control path
60-03-00 or laterXP24000/XP20000Cnt Ac-J ATTIME suspend function under
4x4x4 Multi-Target configuration
60-06-00 or laterXP24000/XP200002DC Configuration with HyperSwap and Cnt
Ac-J 70-02-02 or laterP9500
60-06-00 or laterXP24000/XP20000Open/MF Consistency Preservation Function
70-02-5x or laterP9500
60-07-00 or laterXP24000/XP20000Suspend mode 'QUICK' with Cnt Ac-J
ATTIME suspend function 70-02-02 or laterP9500
70–01–62 or laterP95003DC Cascade configuration
70–01–62 or laterP95003DC Multi-Target configuration
70–01–62 or laterP9500Delta resync function
70–01–62 or laterP95004x4 configuration
70–02–02 or laterP95004x4x4 Multi-target configuration
BCM can use other functions by the storage system with the microcode shown by firmware levels.
Fixes
Table 5 Fixes
Applied OSApplied productsFixes
All supported operating systemsBC ManagerWhen the Fast Query function on ISPF
panel or the YKEWAIT command is
executed to a Shadow Image pair, the
4 Fixes

Table 5 Fixes (continued)
Applied OSApplied productsFixes
copy pair status is reported wrongly as
the SIMPLEX status.
This problem may occur when all of the
following conditions are met:
•Create an BC copy pair structured
by more than two S-VOLs to one
P-VOL.
•Remove a part of the copy pair
created above.
•Execute Fast Query function or
YKEWAIT command to the copy
pairs remained.
Temporary Restrictions
Table 6 Removal of restrictions
Removal of restrictions#
The following restriction of 06-60-00 was removed.
The following features cannot be used with P9500.
•Open/MF Consistency Preservation function
1
Table 7 Restrictions
Restrictions#
In a configuration in which supported XP and P9000 disk arrays coexist, BCM can manage a configuration only
when it consists of devices whose serial numbers are not duplicates. Each device in the configuration must have a
unique serial number.
1
If you issue the YKQUERY,YKQRYDEV, or YKEWAIT command to a BC copy group in an XP1024 disk array
immediately after executing the YKDELETE command, these commands may report the status of a copy pair to be
2
SIMPLEX even though the actual status is in the middle of transition to SIMPLEX (not fully becoming SIMPLEX).
Therefore, when issuing the YKMAKE command to the same BC volumes after executing the YKDELETE command,
wait for approximately 10 seconds before issuing the YKMAKE command.
When using BCM to operate from L-site in a 4x4x4 Multi-Target configuration with Delta Resync, do not perform
the resync operation on a Cnt Ac-J copy pair that automatically became suspended after performing Reverse Resync
on Cnt Ac-S copy pairs to avoid forming 3DC Cascade configuration.
3
When using BCM to operate from L-site in a 4x4x4 Multi-Target configuration with Delta Resync, start the business
operation after Cnt Ac-S and Cnt Ac-J copy pairs are formed so that the Multi-Target configuration is established.
4
BCM does not support recovery procedure from failure in 4x4x4 Multi-Target configuration with Delta Resync by
misoperation. In this case, the following assistance is provided if needed.
If you need to call technical support, make sure to provide as much information about the problem as possible,
including:
5
•The circumstances surrounding the error or failure.
•The content of any error message(s) displayed on the host system(s).
•The content of any error message(s) displayed on Remote Web Console.
•The Remote Web Console configuration information (use the FD Dump Tool).
•The service information messages (SIMs), including reference codes and severity levels, displayed by Remote
Web Console.
Fixes 5

Table 7 Restrictions (continued)
Restrictions#
Do not specify the following values to the DADID of a Disk Configuration Definition, a copy group and a route list.
Specifying those values may cause the information displayed in Discover HP Storage Arrays panel to become
incorrect.
6
•“R”
•“CMD”
•“I”
•“K”
•“RC”
Example that cannot be specified
•“R”
•“xx.R”
•“R.xx”
•“xx.R.xx”
where xx is an arbitrary string of one or more characters.
The following features cannot be used with P9500.
•4x4x4 Cascade configuration
7
Specification differences from previous versions
This section describes the specification differences between V6.6 and V6.6.1 of BCM.
CLI commands
Table 8 Overall
VersionNew Specification in V6.6.1Specification in V6.6Item
6.6.1-00CAPACITY parameter is
available (default). When
NoneYKIMPORT
checks a volume, specify
CAPACITY (CHECK)
parameter. When not checks
volume, specify CAPACITY
(NOCHECK).
The capacity of volume
(cylinder) is obtained.
NoneYKQRYDEV
The capacity of volume
(cylinder) is obtained.
NoneYKSCAN
6 Fixes

ISPF panels
Table 9 Overall
VersionNew Specification in V6.6.1Specification in V6.6Item
6.6.1-00“Cyls” is displayed as a unit
of a volume capacity.
NoneCommand Control Address
(CCA) Selection List
“Cyls” is displayed as a unit
of a volume capacity.
NonePair Selection List (Primary)
“Cyls” is displayed as a unit
of a volume capacity.
NonePair Selection List (Secondary)
Check a volume of capacity
and “Cyls” is displayed as a
unit of a capacity.
Compare a defined copy pair
P-VOL and S-VOL if they are
NoneCopy Group Pair Detail
an equal number of cylinders.
When the capacity is not
obtained or the capacities are
not equal, a warning screen
will be displayed.
“Cyls” is displayed as a unit
of a volume capacity.
NoneBrowse Copy Group Pair
Detail
Messages
None
Prerequisites
Prerequisite programs
The following software programs must be installed to use BCM.
Table 10 Prerequisite programs to install
NotesProgram name
Standard OS componentDFSMS
Standard OS componentISPF
Standard OS componentTSO/E
Standard OS componentTSO/E REXX
To use the resource access control facility (RACF)Security Server
IBM Library for REXX on zSeries Alternate Library is also
bundled with BCM (FMID: HWJ9143, JWJ9144). If any of
IBM Library for REXX on zSeries Release 4 (FMID HWJ9140)
or the REXX Libraries shown left is not available, use the bundled
Alternate Library.
IBM Library for REXX on zSeries Alternate Library (FMID
HWJ9143) The REXX Alternate Library is included in standard OS
component since z/OS V1R9.
Related programs
Linking Replication Manager
The following software programs are required when Replication Manager is used to collect mainframe
system storage information.
Prerequisites 7

Table 11 Prerequisite programs when linking Replication Manager
NotesDescriptionProgram name#
Standard OS componentA communication programIBM Communication Server1
7.1.0A program required to define, use,
and monitor copy pairs.
Replication Manager2
Use Version 6.1An optional product bundled with
WebSphere™ Application Server for
IBM HTTP Server for z/OS3
z/OS. This is required when
establishing IPv6 connections or
HTTPS communication with
Replication Manager.
In addition, z/OS Security Level3 is
required when establishing HTTPS
communication with Replication
Manager.
Operating z/OS on z/VM
The following software programs are required when operating BC Manager z/OS on z/VM.
Table 12 Prerequisite programs when operating Business Continuity Manager z/OS on z/VM
NotesProgram name#
V5R3 (PTF is necessary)z/VM1
Performing operations in a 2DC configuration with HyperSwap and Continuous Access Journal
The following software program is required when running BCM in a 2DC configuration with HyperSwap
and Continuous Access Journal.
Table 13 Prerequisite programs when performing operations in a 2DC configuration with HyperSwap
and Cnt Ac-J
NotesProgram name#
4.2.0 or laterIBM Tivoli Storage Productivity Center for Replication
for System z
1
8 Prerequisites

Memory and disk space requirements
Virtual memory space requirements
The following indicates the user region necessary to run BCM.
•User region under 16 MB: 1,024 KB
•Extended user region over 16 MB
For TSO/E:
–4,000 KB + (2 x number of volumes) KB
◦
◦For Batch:
–4,000 KB + ↑(1.5 x number of volumes)↑ KB
number of volumes: Number of all volumes included in DAD used. When two or more
copy groups are operated, they are sum totals of the number of volumes that each copy
group uses.
The following indicates the user region necessary when linking with Replication Manager. The PREFIX
parameter and DEVN parameter in the formula below are the initialization parameters of the BCM
agent.
•User region under 16 MB: 2,048 KB
•Extended user region over 16 MB
6,000 KB + AKB
+ ↑(512 x number-of-specified-PREFIX-parameters) ÷ 1,024 ↑ KB
+ ↑ (64 x number-of-specified-DEVN-parameters) ÷ 1,024 ↑ KB
A: The larger value of the following: the value of (1.5 x D) and the result of (3 x P)
D: Among the numbers of devices specified for the DEVN parameters, the highest number of
devices.
P: Among the copy groups used by the BCM agent, the highest number of copy pairs in any
group.
The amount of memory required to use BCM Monitor is shown below.
•For a user region of 16 MB or less
2,048 KB
•For an extended user region of 16 MB or more
6,000 KB + (3 number-of-copy-pairs) KB + (C + S) 1 KB
C: Number of copy group parameters specified in the YKMONCG file.
S: Number of action parameters specified in the YKMONCG file.
Table 14 Disk space requirements
Number of directoriesRequired space (in unit of tracks*1)Files to be installed
515 tracksHPQSYSAMT
2075 tracksHPQSYLNKT
11 trackHPQSYLPAT
105 tracksHPQSYPRCT
1045 tracksHPQSYEXET
1045 tracksHPQSYEXVT
Prerequisites 9

Table 14 Disk space requirements (continued)
Number of directoriesRequired space (in unit of tracks*1)Files to be installed
20060 tracksHPQSYPNLT
55 tracksHPQSYMSGT
55 tracksHPQSYTABT
Prerequisite conditions
The following tables show prerequisite conditions for 4x4x4 Multi-Target configuration with Delta
Resync.
Table 15 Prerequisite hardware
RemarksDescriptionItem
z/OS or OS/390 should be installed.Primary site: 1 hostHost
Local site: 1 host if operation is to be
performed from the Local site.
Remote site: 1 host if operation is to be
performed from the Remote site.
Primary site: 1 or more
XP12000/XP10000,
Storage System
XP24000/XP20000, or P9500 disk
arrays
Local site: 1 or more
XP12000/XP10000,
XP24000/XP20000, or P9500 disk
arrays
Remote site: 1 or more
XP12000/XP10000,
XP24000/XP20000, or P9500 disk
arrays
Arbitration paths must be set up with
Remote Web Console.
Primary site <—> Local site: Fibre
Channel, bi-directional.
Inter-DKC link (physical path)
Primary site <—> Remote site: Fibre
Channel, bi-directional.
Local site <—> Remote site: Fibre
Channel, bi-directional.
Arbitration path in remote site: Fibre
Channel, single direction from the
supervisor DKC to each subordinate
DKC.
Table 16 Prerequisite software
DescriptionItem
Versions supported by BCM V6.6.1z/OS or OS/390 V2R10
V6.6.1BCM
•Basic License
•Cnt Ac-J 4x4 Extended CTG License
10 Prerequisites

Table 17 Hardware settings
RemarksDescriptionItem
Arbitration command devices must be set
up with Remote Web Console.
DKCs at the Remote site: One or more
arbitration command devices for each
subordinate DKC.
Arbitration command devices
Journal groups for Cnt Ac-J. Timer type
must be “System.”
Journal groups •Required at the Primary, Remote, and
Local sites.
•Journal groups must be set up with the
Remote Web Console before running
a script.
•One or more of journal volumes are
required at each of the Primary,
Remote, and Local sites.
Journal volumes for Cnt Ac-J.Journal volumes
In 2x2x2 configuration: 3 devices for
each DKC, 18 devices in total.
Command devices
In 4x4x4 configuration: 3 devices for
each DKC, 36 devices in total.
Between the Primary and Local sites:
Inter-CU logical paths (bi-directional).
Logical paths
Between the Primary and Remote sites:
Inter-DKC logical paths (bi-directional).
Between the Local and Remote sites:
Inter-DKC logical paths (bi-directional).
Prerequisites 11

Table 18 Software settings (OS and BCM)
RemarksDescriptionItem
As in the basic 3DC Multi-Target
configuration with Delta Resync pairs,
Route list (Configuration file)
the host at each site must have its own
route list.
See “Preparing the Software (OS,
Business Continuity Manager)” in the
User Guide to set up a route list.
Cnt Ac-S Consistency Preservation
function must be applied.
Cnt Ac-S copy group (Configuration file)
Setting has to be done before running a
script.
4x4 Cnt Ac-J copy group (Configuration
file)
•4x4 Cnt Ac-J copy groups are
required for the Primary-Remote sites
and the Local-Remote sites.
•Timer type of the Cnt Ac-J copy
groups must be “SYSTEM.”
•Either C/T group ID or sub C/T
group ID of a journal group must be
different from those of another
journal group.
•The S-VOL journal group of the Delta
Resync pairs must be the same as
the S-VOL journal group of Cnt Ac-J
copy pairs, but they must have the
different mirror ID specified.
•EXCTG ID of a forward direction of
Cnt Ac-J copy pairs (EXCTG in the
Remote site) must be the same as
EXCTG ID of a forward direction of
Delta Resync copy pairs (EXCTG in
the Remote site).
Overview of CLI commands for 4x4x4 Multi-Target configuration with Delta Resync
The following table shows the CLI commands that support 4x4x4 Multi-Target configuration with Delta
Resync and how they differ from their behavior on 4x4 configuration and Delta Resync configuration.
Table 19 Overview of CLI commands
RemarksDifferences from previous
version
4x4x4 configurationCLI command#
Not applicableNot applicableYKBLDCMD1
Not applicableNot applicableYKBLDPTH2
NoneSupportedYKCONMSG3
Not applicableNot applicableYKDELCMD4
If this situation occurs, issue
either the YKMAKE command
After performing Delta Resync,
if the Delta Resync copy pairs
between the Primary and
SupportedYKDELETE5
with the HOLD parameter to the
Remote sites are dissolved, Delta Resync copy pairs
EXCTG information of Cnt Ac-J between the Primary and
copy pairs between the Local Remote sites, or the YKMAKE
and Remote sites is also deleted. command with the
Therefore, issuing the YKQUERY SELECT(COND) parameter to
command to such copy pairs the Cnt Ac-J copy pairs between
causes the YKZ296E error
message to occur.
the Local and the Remote sites
to re-register them to EXCTG.
12 Prerequisites

Table 19 Overview of CLI commands (continued)
RemarksDifferences from previous
version
4x4x4 configurationCLI command#
Not applicableNot applicableYKDELPTH6
NoneSupportedYKEWAIT7
Not applicableNot applicableYKFCSTAT8
NoneSupportedYKFREEZE9
NoneSupportedYKLOAD10
NoneSupportedYKMAKE11
NoneSupportedYKQRYDEV12
Not applicableNot applicableYKQRYPTH13
NoneSupportedYKQUERY14
If this situation occurs, issue
either the YKMAKE command
After performing Delta Resync,
if the Delta Resync copy pairs
between the Primary and
SupportedYKRECVER15
with the HOLD parameter to the
Remote sites are dissolved, Delta Resync copy pairs
EXCTG information of Cnt Ac-J between the Primary and
copy pairs between the Local Remote sites, or the YKMAKE
and Remote sites is also deleted. command with the
Therefore, issuing the YKQUERY SELECT(COND) parameter to
command to such copy pairs Cnt Ac-J copy pairs between the
causes the YKZ296E error
message to occur.
Local and Remote sites to
re-register them to EXCTG.
NoneSupportedYKRESYNC16
NoneSupportedYKRUN17
Not applicableNot applicableYKSCAN18
Not applicableNot applicableYKSLEEP19
NoneSupportedYKSTATS20
NoneSupportedYKSTORE21
NoneSupportedYKSUSPND22
NoneSupportedYKWATCH23
Setup procedure of 4x4x4 Multi-Target configuration with Delta Resync is equivalent to that of 4x4
configuration and 3DC Multi-Target configuration with Delta Resync except that there are some
restrictions on definition of Cnt Ac-S and 4x4 Cnt Ac-J.
Operation of 4x4x4 Multi-Target configuration with Delta Resync is same as that of 4x4 configuration
and 3DC Multi-Target configuration with Delta Resync.
Prerequisites 13

Table 20 Operation procedure of 4x4x4 Multi-Target configuration with Delta Resync
Difference from 3DC
Multi-Target configuration
ConfigurationDescriptionOperation procedure#
Preparation
Arbitration paths and
command devices for 4x4
configuration are necessary.
1DCHardware setup1 •Bi-directional paths must be set
between P-L, P-R and L-R sites.
•One ore more Journal groups in
each site.
•Arbitration paths and arbitration
command devices.
A command device is
necessary for each DKC.
1DCCreate a route list of 3DC
Multi-Target configuration that
Route list2
contains definition or routes that start
from each site. This route list is
equivalent to that of 3DC Multi-Target
configuration with Delta Resync.
Once a route list is defined, establish
routes according to the route list.
Cnt Ac-S must be with C/T ID,
and Cnt Ac-J must be of 4x4
1DCCreate a copy group definition file
for TC between P-site and L-site
Definition of copy pairs3
Cnt Ac-J. See Table 18 (page
12) for more details.
(G1/G4), 4x4 Cnt Ac-J between
P-site and R-site (G2/G5), and 4x4
Cnt Ac-J between L-site and R-site
(G3/G6).
None2DCEstablish Cnt Ac-S copy group
(G1/G4).
Establish Cnt Ac-S copy
pairs (G1/G4)
4
None3DCEstablish Cnt Ac-J copy group
(G2/G5).
Establish Cnt Ac-J copy
pairs (G2/G5)
5
None3DCEstablish Delta Resync Cnt Ac-J copy
group (G3/G6) into HOLD status.
Establish Delta Resync Cnt
Ac-J copy pairs (G3/G6)
6
Normal operation
None3DCKeep DUPLEX status on both Cnt Ac-S
(G1/G4) and Cnt Ac-J (G2/G5)
copy groups.
....7
Installation instructions
Installation precautions
Please review the following manual references for installation:
•Before starting installation, please ensure that there are sufficient dataset capacity and the number
of directories in the distribution libraries and the target libraries that are required for installation.
•See the installation chapter of the HP P9000 for Business Continuity Manager Software Installation
Guide for full details.
Compatibility/Interoperability
System configuration
1. BCM supports 2DC configurations (1:1). By making multiple units of 2DC configurations, it is
possible to create N:N configuration.
2. BCM supports 3DC (Cnt Ac-S and Cnt Ac-J) configurations (Cascade configuration and Multi-Target
configuration). Note that 3DC configurations are supported only when all DKCs in the
14 Installation instructions

configurations are XP10000/XP12000 disk arrays, XP20000/XP24000 disk arrays, or P9500
disk arrays. N:1 configuration and a configuration that consists of 4 or more DCs are not
supported.
3. BCM supports 4x4 and 4x4x4 Multi-Target configurations. Note that the configuration should
consist entirely of XP10000/XP12000 disk arrays, XP20000/XP24000 disk arrays, or P9500
disk arrays.
4. BCM supports 4x4x4 Cascade configurations. Note that the configuration should consist entirely
of XP12000/XP10000 disk arrays or XP24000/XP20000 disk arrays.
Remote DKC control function
1. When using Remote DKC control function, use Fibre link for connection between DKCs. ESCON
link is not supported. When you define the logical path between CUs for Remote DKC control
function, you must define the path between CUs that belong to the command device volumes.
2. To share a command device among multiple operating systems, ensure that the &YKCMDIF variable
is either defined in the IEASYM member or set by the START YKSETENV command.
3. When allocating a command device, note the following items:
•Parity group cannot be moved if a command device is defined within the parity group.
•Parity group type cannot be changed if the command device is defined within the parity
group.
•The command device between LCUs cannot be moved.
•The volume size of the command device cannot be changed (550 cylinders are required for
XP128 or XP1024 disk arrays).
Copy types
There should not be mix of copy types within a single copy group. Ensure that all volumes are SIMPLEX
in the initial state. BCM does not display the pair status correctly in the following conditions:
•Copy group definition is changed when not all pairs are SIMPLEX.
•Pair configuration in copy group definition differs from the actual pair configuration.
Other
1. From BCM 04-00, CLI Command-Execution Logs are output to SYSLOG. This applies to the CLI
commands that are executed from within the ISPF panels of BCM. Therefore, large amount of
data will be output to SYSLOG when you make frequent operation of BCM or issue many CLI
commands.
2. BCM does not support the multiplatform volume.
3. From z/OS V1R8, a console ID cannot be specified to the CN operand of the TSO/E SEND
command. Because of this, a console ID cannot be specified for the CN operand of the YKWATCH
command when using it on z/OS V1R8 or later. If the console ID is specified, the TSO/E SEND
command that is used in the YKWATCH command will fail and the YKWATCH does not return the
expected message.
4. From BCM 06-00, it becomes impossible to use the configuration file made by versions earlier
than 02-00. (APIInfo Level in the configuration file is “1.1.0” or earlier).
5. After the DKC microcode is replaced, scan the DKC.
6. Specify a different DKC serial number for P-VOL and S-VOL when you define the copy group
definition of the copy type other than Business Copy.
7. Not to specify the different DADID from the DADID in copy group definition when you specify a
DADID in the Set Defaults panel or the YKLOAD command's operand.
8. From BCM 06-00, it is necessary to set up the resource access control facility (RACF) to use the
CLI commands or BCM agent.
Compatibility/Interoperability 15

9. Do not perform PPRC operation to the BCM copy pairs. If you performed PPRC operation to the
BCM copy pairs, dissolve and re-establish them by BCM. But only if you performed CSUSPEND
operation with default operands on the BCM copy pairs as Cnt Ac-S copy group without the C/T
group ID, you can resynchronize such copy pairs with CESTPAIR operation with default operands.
10. If there is already a configuration file that was generated by the YKP2A command of the Mainframe
Agent program, make sure to use the different prefix value for BCM so that not reference the
configuration file generated by the YKP2A command. BCM does not accept a configuration file
generated by the YKP2A command. If such file is given for any BCM operations, it causes an
error.
11. With BCM versions earlier than V6.1, user SVCs cannot be used to suppress output of IOS002A
messages when the I/O path between the host and the DKC is disconnected while disk scanning
is being performed. Therefore, in a mixed-version environment, make sure to always use user
SVCs of BCM version V6.1 or later.
Determining current version
1. The Main Menu panel displays the version number of this product as follows: Release 6.6.1-01
2. The Setting Information panel displays the version number of this product as follows: Version
6.6.1-01 (00)
3. YKT400I message that is produced by using the YKDSPENV command contains the version number
of this product as follows: 6.6.1-01
4. YKY001I message that is produced upon starting up Agent contains the version number of this
product as follows: 06-61–/A
5. The YKENV command displays the version number of this product as follows: 6.6.1-01(00)
6. YK8001I message that is produced upon starting up BCM Monitor contains the version number
of this product as follows: 6.6.1-01
7. Replace CHYKnnn and Vnnnnn as follows:
Table 21 Versioning Replacements
Replace withIn the manual
CHYK634CHYKnnn
V066101Vnnnnn
16 Determining current version