From the Böblingen Development Team
August, 2010
Please read the full articles in the z/OS Hot Topics Newsletter #23
 |
Let HCD or HCM generate a disaster recovery plan |
by Martina Weidler, Viola Thierfelder
Are you controlling availability and disaster recovery (D/R) of your IBM z/OS systems and applications through Geographically Dispersed Parallel Sysplex™ (GDPS™)? Do you mirror storage devices over Peer-to-Peer Remote Copy (PPRC) feature connections to have backup solutions available in case of outages, emergencies, or system failures?
If so, then you probably already experienced how time-consuming and susceptible to failure it is, not only to manage a primary site operating system (OS) configuration for every LPAR of your sysplex but also to keep it in sync with adequate definitions for a related D/R site OS configuration ...
|
z/OS storage fabric discovery and auto-configuration |
by Friedrich Beichter, Scott Compton
Defining a DASD or tape subsystem to z/OS requires careful planning on the number and selection of paths to provide for sufficient bandwidth and availability, and to avoid single points of failure. Chosen device numbers have to follow the installation conventions, and data that has already been specified when configuring the subsystem needs to be duplicated for the I/O definition, like LCU numbers, unit address ranges, or device types. Any mistakes or transcription errors can lead to a sub-optimal or nasty, failing configuration ...
|
Feedback on our products |
You can send us feedback for HCD and HCM via e-mail.
|
