HP StorageWorks XP Remote Web Console Software User Manual
Page 94
94
Hitachi TrueCopy z/OS for HP XP12000/XP10000 and SVS 200 storage systems
storage overload (see ”
” on page 31). Make sure to set the SCP delay time after
you have added all MCU-RCU paths.
NOTE:
SCP Delay Time of TrueCopy for z/OS and the state-change-pending time of FlashCopy Mirror
Version 2 are same. To determine the SCP Delay Time of TrueCopy for z/OS, take into account the fact
that if you change the SCP Delay Time setting by the CU Option panel, the state-change-pending time of
FlashCopy Mirror Version 2 will change. For more information on state-change-pending time of FlashCopy
Mirror Version 2, see the Hitachi ShadowImage for z/OS user guide.
CAUTION:
You must click OK on the RCU Option window to register the SCP Delay Time setting, even if
you did not make any changes to the RCU options. Ensure to select the appropriate SCP delay time for
your TC390 system configuration.
The RIO MIH Time setting specifies the time value for the remote I/O (RIO) missing interrupt handler (MIH),
which is the wait time until data transfer from the MCU to RCU is complete. The RIO MIH time value must
be from 10 to 100 seconds. The default setting is 15 seconds. This setting is available for both serial and
Fibre Channel interfaces. For more information on the MIH, see the ”
Installing the TrueCopy hardware
page 49.
The Path Blockade Watch setting specifies the time for monitoring blockade in the Fibre Channel paths on
the MCU side. The path blockade watch value must be from 0 to 45 seconds. The default setting is 40
seconds. This setting is available for Fibre Channel interface only.
NOTE:
If you create a pair with the synchronous mode, and if the status of all paths becomes
“Monitoring” because of a path error, MIH may occur in the host. The time of the Path blockade Watch
must be shorter than the setting time of MIH timer in the host.
Use the Incident of RCU option to specify which host(s) the RCUs will report link incident records to. When
to any host is selected, the RCUs will send link incident records to all RCU hosts and to all MCU hosts.
When only to RCU host is selected, the RCUs send link incident records only to the RCU host(s). Verify that
RCU link incidents are reported to the proper host(s) so that corrective action, if needed, can be taken. The
to any host setting is recommended when TC390 is being used for disaster recovery purposes.
Use the PPRC support option to specify whether the MCU will generate sense information that is
compatible with IBM PPRC. This option is extremely important for TC390 disaster recovery planning. If the
host does not support PPRC, select No to configure the MCU to report SIMs. If the host system supports
PPRC, select Yes to configure the MCU to generate PPRC-compatible sense information when a TC390 pair
is suspended instead of a service information message (SIM). If Yes is selected, the MCU will still report
moderate- and serious-level SIMs, as well as DF40 and DF48 device SIMs. For more information on PPRC
support, see ”
Using PPRC commands for TrueCopy
NOTE:
If you plan to use the CGROUP (FREEZE/RUN) command for TC390 pairs, you must select Yes.
Use the Service SIM of Remote Copy option to specify whether the MCU will report the service-level
remote-copy SIMs to the host(s). (The moderate-, serious-, and acute-level SIMs are always reported to the
host.) Select Report to configure the MCU to report the service-level remote-copy SIMs to the host(s). The
Report setting should be selected for TC390 disaster recovery planning. Select Not Report to suppress
service-level SIM reporting. For a description of the TC390 and TC390A SIMs, see ”
page 187. All service-level SIMs will be logged in the SSB.LOG file on the XP12000/XP10000 SVP,
regardless of this setting.
The FREEZE Option setting enables or disables support for the CGROUP (FREEZE/ RUN) PPRC TSO
command (see ”
” on page 173). The FREEZE option is available only
when PPRC support = Yes. If you select Enable, the MCU will accept and perform the CGROUP command.