Hitachi Business Continuity Manager

Transcription

1 Hitachi Business Continuity Manager Installation Guide Document Organization Product Version Getting Help Contents MK-95HC104-25

2 2014, 2016 Hitachi, Ltd. All rights reserved. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including copying and recording, or stored in a database or retrieval system for commercial purposes without the express written permission of Hitachi, Ltd., or Hitachi Data Systems Corporation (collectively Hitachi ). Licensee may make copies of the Materials provided that any such copy is: (i) created as an essential step in utilization of the Software as licensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not make any other copies of the Materials. Materials mean text, data, photographs, graphics, audio, video and documents. Hitachi reserves the right to make changes to this Material at any time without notice and assumes no responsibility for its use. The Materials contain the most current information available at the time of publication. Some of the features described in the Materials might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi Data Systems Corporation at Notice: Hitachi products and services can be ordered only under the terms and conditions of the applicable Hitachi agreements. The use of Hitachi products is governed by the terms of your agreements with Hitachi Data Systems Corporation. By using this software, you agree that you are responsible for: 1) Acquiring the relevant consents as may be required under local privacy laws or otherwise from authorized employees and other individuals to access relevant data; and 2) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws. Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products. Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. AIX, AS/400e, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, eserver, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, PowerPC, RS/6000, S/390, System z9, System z10, Tivoli, z/os, z9, z10, z13, z/vm, and z/vse are registered trademarks or trademarks of International Business Machines Corporation. Active Directory, ActiveX, Bing, Excel, Hyper-V, Internet Explorer, the Internet Explorer logo, Microsoft, the Microsoft Corporate Logo, MS-DOS, Outlook, PowerPoint, SharePoint, Silverlight, SmartScreen, SQL Server, Visual Basic, Visual C++, Visual Studio, Windows, the Windows logo, Windows Azure, Windows PowerShell, Windows Server, the Windows start button, and Windows Vista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screen shots are reprinted with permission from Microsoft Corporation. All other trademarks, service marks, and company names in this document or website are properties of their respective owners. ii

3 Contents Preface... ix Intended audience... x Product version...x Release notes... x Document organization...x Related documents...xi Document conventions...xii Conventions for storage capacity values...xii Accessing product documentation... xiii Getting help... xiii Comments... xiv 1 Overview of Hitachi Business Continuity Manager Licenses provided by Business Continuity Manager Prerequisite conditions Operating system prerequisites Program prerequisites Supported storage systems Prerequisites for using a volume on Linux on IBM System z Installing Business Continuity Manager Overview of installation Preparing for installation Types of distribution media Provided datasets Planning DASD storage attributes About distribution libraries (DLIB) About target libraries Designing storage Required device capacity for BCM log data Determining required memory Preparations for installing Business Continuity Manager Installing Business Continuity Manager Installing Business Continuity Manager with SMP/E Simple installation (installation without SMP/E) iii

4 Setting up the environment Settings for using CLI commands in TSO/E environments Settings for using ISPF panels with Business Continuity Manager Concatenating the libraries needed to execute the YKSTART command Starting YKSTART dynamically Settings in the ISPF panel Setting the position of the command line Setting the number of PF keys that are displayed Settings for using the YKWATCH command and the copy group definition generation function for PPRC copy pairs Settings for using environment configuration commands Setting the security Setting security for the environment configuration commands Setting security for CLI commands, YKAGENTD, and YKBTSCAN Setting security when the extended access control function is installed Procedure for setting the READ permission for the RACF profile to the user2-22 Setting security for starting a System REXX environment Configuring dataset security Registering a user SVC Using the IEASVCxx parmlib member to register Using the YKALCSVC command to register Setting Business Continuity Manager environment variables Specifying the host ID Enabling and disabling the system logger service Specifying whether to output CLI command-execution logs YKSETENV command format YKDSPENV command format Registering a license Using the license key file Directly entering a key code Notes when operating license keys Format for license information datasets Naming for license information datasets Verification procedure following installation and setup Check whether the installation and environment settings are completed Checking the access permissions when the extended access control function is installed Upgrading Business Continuity Manager What to check before upgrading Checking licenses Checking environment variables Checking the user SVC number Backing up datasets Backing up configuration files Backing up the program before migration Pre-upgrade procedure Deleting the user SVC Removing the concatenation of the cataloged procedures library Removing the concatenation of the REXX Exec library and the libraries used by ISPF interface Removing the concatenation of the load library Upgrading Business Continuity Manager iv

5 What to check after upgrading Notes on system setup when a related product is installed Notes on user SVC registration when a related product is installed Notes on setting environment variables or system symbols when a related product is installed Notes on specifying a prefix when a related product is installed User SVC versions required by Business Continuity Manager Setting up the environment when linking with Replication Manager Overview of environment settings Configuring the environment settings without using the Remote DKC Control Function (before Business Continuity Manager is installed) Configuring the environment settings using the Remote DKC Control Function (before Business Continuity Manager is installed) Configuring the environment settings in an existing environment (with Business Continuity Manager installed) Configuring the environment settings to allow only monitoring of copy groups Configuring the environment settings for monitoring PPRC copy pairs Creating configuration file datasets Configuration file dataset names Dataset format and required disk capacity for the configuration file Setting the TCP/IP port number Setting up the security for Business Continuity Manager agents Setting the dataset security Setting up the Resource Access Control Facility (RACF) when linking with Replication Manager Setting up IBM HTTP Server Settings for connecting via IPv Setting up HTTPS connections Collecting the trace log Creating initialization parameters How to use the SETINIT command Continuing to the next line Entering comments Notes during creation of initialization parameters Details of initialization parameters Format Parameters Multiple specifications of initialization parameters Examples of specifying initialization parameters For Business Continuity Manager agent exclusively on the local site For Business Continuity Manager agent on local and remote sites Examples of initialization parameter analysis results Creating a cataloged procedure for startup for the Business Continuity Manager agents Standard cataloged procedure for startup Standard cataloged procedure for startup in the expanded format Description Changing the cataloged procedure for startup v

6 4 Setting up an environment for BCM Monitor General procedure for setting up an environment for BCM Monitor Setting up the security for BCM Monitor Creating configuration files for BCM Monitor Creating BCM Monitor parameter files Creating a cataloged procedure for startup for BCM Monitor A Modifying sample JCL... A-1 Values used in the sample JCL modification examples... A-2 ALLOUPLD (creating transmission datasets)...a-2 RECVUPLD (TSO/E RECEIVE processing)... A-5 HDSYKSIN (simple installation)...a-6 SMPALLOC (allocating SMP/E datasets)... A-8 HDSYK1AL (allocating distribution and target libraries)... A-10 HDSYK2DF (defining distribution and target libraries)... A-12 HDSYK3RC (SMP/E RECEIVE processing)... A-15 HDSYK4AP (creating target libraries)...a-17 HDSYK5AC (creating distribution libraries)... A-19 HDSYK6RC (SMP/E RECEIVE processing for extended access control function)... A-20 HDSYK7AP (creating target libraries for extended access control function)... A-22 HDSYK8AC (creating distribution libraries for extended access control function)... A-24 B Sample Scripts... B-1 HDSRFEPR (viewing access permissions for the extended access control function)... B-2 C Notes on upgrading Business Continuity Manager... C-1 When upgrading Business Continuity Manager from a version earlier than to or later... C-2 When upgrading Business Continuity Manager from a version earlier than to or later... C-2 Route Config panel...c-2 Route list structure... C-2 When upgrading Business Continuity Manager from a version earlier than 7.4 to 7.4 or later... C-3 When upgrading Business Continuity Manager from a version earlier than to or later... C-3 When upgrading Business Continuity Manager from a version earlier than to or later... C-3 D Notes when multiple versions of Business Continuity Manager exist... D-1 Configuration files... D-2 License information dataset...d-2 Changed display for the license name... D-2 Prefix for the license information dataset... D-2 Installing a license...d-3 Specifying Business Continuity Manager log output destination (LOGPUT)... D-3 Specifying whether to output the CLI command-execution logs (SYSLOG)... D-3 Setting up the Resource Access Control Facility (RACF) when multiple versions of Business Continuity Manager exist... D-6 vi

7 Registering a user SVC dynamically...d-7 User SVC for suppressing IOS002A messages...d-7 Available versions of user SVCs... D-7 E Conventions in syntax explanations...e-1 Conventions in syntax explanations...e-2 Acronyms and abbreviations Index vii

8 viii

9 Preface This document describes how to install the following program products. In this manual, these products are collectively referred to as Business Continuity Manager: - Hitachi Business Continuity Manager Basic - Hitachi Business Continuity Manager UR 4x4 Extended CTG This preface includes the following information: Intended audience Product version Release notes Document organization Related documents Document conventions Conventions for storage capacity values Accessing product documentation Getting help Comments Preface ix

10 Intended audience This document is intended for users who want to install Business Continuity Manager. Readers of this document are assumed to have a basic understanding of the following: Functions of Lightning 9900V Series, USP, USP V, VSP or VSP G1000 storage systems. How to create a system that uses Hitachi Replication Manager if linking with Hitachi Replication Manager. Product version This document revision applies to Hitachi Business Continuity Manager v8.4 or later. Release notes Read the release notes before installing and using this product. They may contain requirements or restrictions that are not fully described in this document or updates or corrections to this document. Document organization The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter. The first page of each chapter provides links to the sections in that chapter. Chapter/Appendix Chapter 1, Overview of Hitachi Business Continuity Manager on page 1-1 Chapter 2, Installing Business Continuity Manager on page 2-1 Chapter 3, Setting up the environment when linking with Replication Manager on page 3-1 Chapter 4, Setting up an environment for BCM Monitor on page 4-1 Appendix A, Modifying sample JCL on page A-1 Description Explains the provided licenses and prerequisites for using Business Continuity Manager. Explains installation preparations and procedures, memory estimation, and version upgrade procedures. Explains how to set up port numbers, security, and IBM HTTP Server, which are all required to link to Replication Manager. It also explains how to create initialization parameters and a cataloged procedure for startup. Explains how to set up the security for BCM Monitor. It also explains how to create configuration files, BCM Monitor parameter files, and a cataloged procedure for startup. Explains how to modify sample JCL. x Preface

11 Chapter/Appendix Appendix B, Sample Scripts on page B-1 Appendix C, Notes on upgrading Business Continuity Manager on page C-1 Appendix D, Notes when multiple versions of Business Continuity Manager exist on page D-1 Appendix E, Conventions in syntax explanations on page E-1 Description Explains how to use sample scripts. Provides notes on upgrading Business Continuity Manager. Provides notes on upgrade processing when multiple versions of Business Continuity Manager exist in a system. Explains the conventions in syntax explanations and the syntax elements that are used. Related documents Manuals related to Business Continuity Manager: Hitachi Business Continuity Manager User Guide, MK-94RD247 Hitachi Business Continuity Manager Reference Guide, MK-96HC135 Manuals related to Hitachi Command Suite products: Hitachi Command Suite Tiered Storage Manager for Mainframe User Guide, MK-92HC207 Hitachi Command Suite System Requirements, MK-92HC209 Hitachi Command Suite Mainframe Analytics Recorder User Guide, MK-92HC226 Hitachi Command Suite Replication Manager Configuration Guide, MK-98HC151 Hitachi Command Suite Replication Manager User Guide, MK-99HC166 A manual related to Hitachi Storage Management Software for Mainframe: Hitachi Storage Management Software for Mainframe Messages, MK-92HC227 Manuals related to Hitachi storage systems: Hitachi Command Control Interface User and Reference Guide Hitachi ShadowImage for Mainframe User Guide Hitachi TrueCopy for Mainframe User Guide Hitachi Universal Replicator for Mainframe User Guide Hitachi Universal Volume Manager User Guide Hitachi Virtual Storage Platform G1000 System Administrator Guide Preface xi

12 Document conventions This document uses the following typographic conventions: Convention Description Bold Indicates text in a window, including window titles, menus, menu options, buttons, fields, and labels. Example: Click OK. Indicates a emphasized words in list items. Italic Indicates a document title or emphasized words in text. Indicates a variable, which is a placeholder for actual text provided by the user or for output by the system. Example: pairdisplay -g group Monospace [ ] square brackets Indicates text that is displayed on screen or entered by the user. Example: pairdisplay -g oradb Indicates optional values. Example: [ a b ] indicates that you can choose a, b, or nothing. { } braces Indicates required or expected values. Example: { a b } indicates that you must choose either a or b. vertical bar Indicates that you have a choice between two or more options or arguments. Examples: [ a b ] indicates that you can choose a, b, or nothing. { a b } indicates that you must choose either a or b. This document uses the following icons to draw attention to information: Icon Label Description Note Calls attention to important or additional information. Tip Provides helpful information, guidelines, or suggestions for performing tasks more effectively. Caution Warns the user of adverse conditions or consequences (for example, disruptive operations). WARNING Warns the user of severe conditions or consequences (for example, destructive operations). Conventions for storage capacity values Physical storage capacity values (for example, disk drive capacity) are calculated based on the following values: xii Preface

13 Physical capacity unit Value 1 kilobyte (KB) 1,000 (10 3 ) bytes 1 megabyte (MB) 1,000 KB or 1,000 2 bytes 1 gigabyte (GB) 1,000 MB or 1,000 3 bytes 1 terabyte (TB) 1,000 GB or 1,000 4 bytes 1 petabyte (PB) 1,000 TB or 1,000 5 bytes 1 exabyte (EB) 1,000 PB or 1,000 6 bytes Logical storage capacity values (for example, logical device capacity) are calculated based on the following values: Logical capacity unit Value 1 block 512 bytes 1 cylinder Mainframe: 870 KB Open-systems: OPEN-V: 960 KB Others: 720 KB 1 KB 1,024 (2 10 ) bytes 1 MB 1,024 KB or 1,024 2 bytes 1 GB 1,024 MB or 1,024 3 bytes 1 TB 1,024 GB or 1,024 4 bytes 1 PB 1,024 TB or 1,024 5 bytes 1 EB 1,024 PB or 1,024 6 bytes Accessing product documentation Product documentation is available on Hitachi Data Systems Support Connect: Check this site for the most current documentation, including important updates that may have been made after the release of the product. Getting help Hitachi Data Systems Support Connect is the destination for technical support of products and solutions sold by Hitachi Data Systems. To contact technical support, log on to Hitachi Data Systems Support Connect for contact information: Hitachi Data Systems Community is a global online community for HDS customers, partners, independent software vendors, employees, and Preface xiii

14 prospects. It is the destination to get answers, discover insights, and make connections. Join the conversation today! Go to community.hds.com, register, and complete your profile. Comments Please send us your comments on this document: Include the document title and number, including the revision level (for example, -07), and refer to specific sections and paragraphs whenever possible. All comments become the property of Hitachi Data Systems Corporation. Thank you! xiv Preface

15 1 Overview of Hitachi Business Continuity Manager This chapter explains the provided licenses and prerequisites for using Business Continuity Manager. Licenses provided by Business Continuity Manager Prerequisite conditions Overview of Hitachi Business Continuity Manager 1-1

16 Licenses provided by Business Continuity Manager To use Business Continuity Manager, you need to install the appropriate license. There are two types of licenses for Business Continuity Manager: a license for using basic functions, and licenses for using optional functions. When the license for using basic functions is installed, you can define and manage ShadowImage (SI), TrueCopy (TC), TrueCopy Asynchronous (TCA) and Universal Replicator (UR) copy groups. To use optional functions, install the required license. After a license key is installed in the license information dataset, functions corresponding to the license you installed become available. When you migrate Business Continuity Manager from an older version to a newer version, depending on conditions, you might need to obtain the license keys again. The following table lists the licenses provided by Business Continuity Manager and functions available for each license. Table 1-1 Licenses and available functions License name Available function Mandatory or optional Business Continuity Manager Basic Basic functions (including the Remote DKC Control Function and TrueCopy consistency preservation function). Mandatory Business Continuity Manager UR 4x4 Extended CTG Consistency preservation function of Universal Replicator in a 4x4 configuration Optional The length of time you can use Business Continuity Manager depends on the type of installed license. The following table lists the license types. Table 1-2 License types License type Effective period Purpose Permanent license None Used for normal operation. Temporary license 120 days Used for a trial before purchase. Emergency license 30 days Used when the temporary license is about to expire, but a permanent license cannot be purchased. Note: When you operate a storage system using Business Continuity Manager on a Secondary site, the license is also required for the Secondary site. You cannot use license keys obtained from version 5.3 or earlier. 1-2 Overview of Hitachi Business Continuity Manager

17 Prerequisite conditions This section describes the prerequisites for using the Business Continuity Manager. Operating system prerequisites Business Continuity Manager can be used on the following operating systems: z/os V1R10 to V2R2 Use version z/os V2R1 or later to establish HTTPS communication between Replication Manager and Business Continuity Manager by using TLS 1.2. Note: Program prerequisites VM environments are supported. For details about operating conditions and other information, contact the product vendor. Note that VM environments do not support HTTPS communication. The devices in the alternate subchannel set are not supported. The following table lists the programs required to use Business Continuity Manager. Table 1-3 Prerequisite programs Program name Required / Optional Overview Description DFSMS Required A data facility storage management subsystem Standard OS component. ISPF Required A full-screen interface Standard OS component. Security Server (RACF) Required An IBM security management product None TSO/E REXX Required This program is required to run TSO/E # Required Business Continuity Manager. Standard OS component. IBM Library for REXX on zseries Release 4 (FMID HWJ9140) or IBM Library for REXX on zseries Alternate Library (FMID HWJ9143) Required IBM Library for REXX on zseries Alternate Library (FMID HWJ9143) is a Standard OS component. System REXX Optional This program is required for executing CLI commands in a System REXX environment. Standard OS component. Overview of Hitachi Business Continuity Manager 1-3

18 Program name Required / Optional Overview Description Replication Manager Optional One of the Hitachi Command Suite products. Replication Manager is required for defining, using, and monitoring copy pairs, as accomplished by linking with the Business Continuity Manager agent. Use version or a later version. IBM Communications Server Optional A communication program. This program is required for linking with Replication Manager. Standard OS component. IBM HTTP Server for z/os Optional An optional product bundled with WebSphere Application Server for 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. Use version 6.1 or a later version. Use version or a later version to establish HTTPS communication between Replication Manager and Business Continuity Manager by using TLS 1.2. IBM Tivoli Storage Productivity Center for Replication for System z Optional This program is required to perform operations in 2DC configurations with HyperSwap and Universal Replicator. Use version 4.2 or a later version. #: In the TSO/E terminal, lower-case letters might not be correctly displayed, depending on the usage environment. Supported storage systems Business Continuity Manager can be used to operate any of the following Hitachi storage systems: Lightning 9900V Series Hitachi USP (USP) Universal Storage Platform V/VM (USP V) Virtual Storage Platform (VSP) Virtual Storage Platform G1000 (VSP G1000) Prerequisites for using a volume on Linux on IBM System z Make sure that you are aware of the information in this section before using Business Continuity Manager on a Linux IBM System z/linux volume. Note the following limitations: 1-4 Overview of Hitachi Business Continuity Manager

19 Only USP, USP V, VSP, and VSP G1000 storage systems are supported. Allowed copy types are ShadowImage, TrueCopy, TrueCopy Asynchronous, or Universal Replicator. To use a z/linux volume, first specify the following: Set the disk layout to CDL (System z compatible disk layout). (When running z/linux on z/vm) Set the DASD sharing type (DASD Sharing) to Dedicated Disk. Specify that time stamps for I/O operations to and from z/linux. Note: If both z/os and z/linux volumes coexist inside a consistency group, synchronize the system clocks. You cannot use the following functions on a z/linux volume: The FlashCopy Linkage Function The Remote DKC Control Function that uses a z/linux volume as a command device Overview of Hitachi Business Continuity Manager 1-5

20 1-6 Overview of Hitachi Business Continuity Manager

21 2 Installing Business Continuity Manager This chapter provides installation preparations and procedures, environment setup procedures, and version upgrade procedures. Overview of installation Preparing for installation Installing Business Continuity Manager Setting up the environment Upgrading Business Continuity Manager Notes on system setup when a related product is installed User SVC versions required by Business Continuity Manager Installing Business Continuity Manager 2-1

22 Overview of installation The following figure provides an overview of how to install Business Continuity Manager. Figure 2-1 Overview of the Business Continuity Manager installation procedure The following sections explain the details about each step. To upgrade Business Continuity Manager, see Upgrading Business Continuity Manager on page Preparing for installation The sections below describe the preparations required for installing Business Continuity Manager. Types of distribution media Business Continuity Manager is available through both of the following distribution media: CD-ROM Provided datasets The following table lists the files that are provided on the installation CD- ROM. Table 2-1 Files provided on installation CD-ROM No. File name Contents 1 HITACHI.CHYKnnn.SMPMCS.XMIT SMP/E for Business Continuity Manager control statements used for packaging SYSMOD Required/ Optional Required 2-2 Installing Business Continuity Manager

23 No. File name Contents 2 HITACHI.CHYKnnn.F1.XMIT This sample library includes JCL samples used by SMP/E (for allocation, DDDEF, RECEIVE, APPLY, and ACCEPT), and other samples 3 HITACHI.CHYKnnn.F2.XMIT Business Continuity Manager load modules for LINKLIB 4 HITACHI.CHYKnnn.F3.XMIT Business Continuity Manager load modules for LPALIB 5 HITACHI.CHYKnnn.F4.XMIT Cataloged procedure library Required/ Optional Required Required Required Required 6 HITACHI.CHYKnnn.F5.XMIT REXX scripts Required 7 HITACHI.CHYKnnn.F6.XMIT REXX scripts Required 8 HITACHI.CHYKnnn.F7.XMIT ISPF panel library Required 9 HITACHI.CHYKnnn.F8.XMIT ISPF message library Required 10 HITACHI.CHYKnnn.F9.XMIT ISPF table library Required 11 HITACHI.CHYKaaa.SMPMCS.XMIT SMP/E control statement used for packaging SYSMOD for the copy group access control function (extended access control function) 12 HITACHI.CHYKbbb.SMPMCS.XMIT SMP/E control statement used for packaging SYSMOD for a specific command access control function (extended access control function) Optional Optional Note: In the above table, the nnn part of CHYKnnn, the aaa part of CHYKaaa, and the bbb part of CHYKbbb vary depending on the version. The following table indicates the keyword (FMID: Function Modification Identifier) required for installation by SMP/E. Installing Business Continuity Manager 2-3

24 Table 2-2 FMID for Business Continuity Manager component CHYKnnn FMID Function name Hitachi Business Continuity Manager Note: In the above table, the nnn part of CHYKnnn varies depending on the version. Planning DASD storage attributes This section lists distribution libraries (DLIB) and target libraries, and explains the DASD storage attributes required for Business Continuity Manager installation. About distribution libraries (DLIB) The following table shows the DASD storage attributes required for distribution libraries. Table 2-3 DASD storage attributes for distribution libraries (DLIB) dd name # DSORG RECFM LRECL (bytes) BLKSIZE (bytes) HDSYSAMD (Sample Library) HDSYLNKD (Load library for LINKLIB) HDSYLPAD (Load library for LPALIB) HDSYPRCD (Cataloged procedure library) HDSYEXED (REXX Exec Library) HDSYEXVD (REXX Exec library, variable length format) HDSYPNLD (Panel Library) HDSYMSGD (Message Library) HDSYTABD (Table Library) PO FB 80 6,160 PO U -- 6,144 PO U -- 6,144 PO FB 80 6,160 PO FB 80 6,160 PO VB 255 6,120 PO FB 80 6,160 PO FB 80 6,160 PO FB 80 6, Installing Business Continuity Manager

25 About target libraries #: The dd name specified in the sample job HDSYK1AL (see HDSYK1AL (allocating distribution and target libraries) on page A-10). The name of each dataset is the one specified in each DD statement. The following table shows the DASD storage attributes required for target libraries. Table 2-4 DASD storage attributes for target libraries dd name # DSORG RECFM LRECL (bytes) BLKSIZE (bytes) HDSYSAMT (Sample Library) HDSYLNKT (Load library for LINKLIB) HDSYLPAT (Load library for LPALIB) HDSYPRCT (Cataloged procedure library) HDSYEXET (REXX Exec Library) HDSYEXVT (REXX Exec library, variable length format) HDSYPNLT (Panel Library) HDSYMSGT (Message Library) HDSYTABT (Table Library) PO FB 80 6,160 PO U -- 6,144 PO U -- 6,144 PO FB 80 6,160 PO FB 80 6,160 PO VB 255 6,120 PO FB 80 6,160 PO FB 80 6,160 PO FB 80 6,160 Designing storage #: The dd name specified in the sample job HDSYK1AL (see HDSYK1AL (allocating distribution and target libraries) on page A-10). The name of each dataset is the one specified in each DD statement. In this manual, a ddname library indicates a library type. Operating Business Continuity Manager entails calculating the amount of device capacity and memory that you require and planning accordingly. Installing Business Continuity Manager 2-5

26 Required device capacity for BCM log data Estimate the amount of BCM log data as follows, according to the log output destination. For details about the ISPF log, see the Hitachi Business Continuity Manager User Guide. When the system logger service is not used The following table shows the amount of data when BCM logs are output without the system logger service being used (when LOGPUT=SAM). Table 2-5 Amount of BCM log data when the system logger service is not used Type of BCM log data Size #1 Items per command Messages (excluding those output from the ISPF panel, or scripts) messagelength #2 number-of-messagesoutput Parameter information for the channel command words of the I/O, only when an I/O error occurs I/O return information, only when an I/O error occurs Sense byte information, only when an I/O error occurs CCW-length #3 number-of-times-an- I/O-error-occurred 256 number-of-times-an- I/O-error-occurred 256 number-of-times-an- I/O-error-occurred Timestamps Command parameter information #1: BCM logs are output with a specified value of this size, rounded up by a factor of 32. #2: The maximum message length is 256 bytes. #3: This is 2,051 bytes when the copy pair status is obtained, and 256 bytes or less otherwise. When the system logger service is used The following table shows the amount of log data output when the system logger service is used for BCM log output (for LOGPUT=LOGR). Table 2-6 Amount of log data output when the system logger service is used Type of BCM log data Size #1 Items per command Messages (excluding those output from the ISPF panel, or scripts) 68 + message-length #2 number-of-messagesoutput 2-6 Installing Business Continuity Manager

27 Type of BCM log data Size #1 Items per command Parameter information for the channel command words of the I/O, only when an I/O error occurs I/O return information, only when an I/O error occurs Sense byte information, only when an I/O error occurs 68 + CCW-length #3 number-of-times-an- I/O-error-occurred 224 number-of-times-an- I/O-error-occurred 224 number-of-times-an- I/O-error-occurred Timestamps 96 2 Command parameter information #1: BCM logs are output with a specified value of this size, rounded up by a factor of 32. #2: The maximum message length is 256 bytes. #3: This is 2,051 bytes when the copy pair status is obtained, and 256 bytes or less otherwise. For staging datasets: Estimate the disk capacity based on the amount of BCM log data. For log stream datasets: Estimate the disk capacity based on the save period, and the amount of BCM log data after offload. For external datasets (OUTLOG): Determining required memory Estimate the disk capacity based on the save period, and the amount of Business Continuity Manager log data after offload. For details about the format for external datasets (OUTLOG), see the Hitachi Business Continuity Manager User Guide. The following indicates the required memory necessary to run Business Continuity Manager. For a user region of 16 MB or less: 1,024 KB For an extended user region of 16 MB or more: For TSO/E: 4,000 KB + (1 number-of-volumes) KB + (3.5 number-of-copy-pairs) KB For batches: 4,000 KB + (1 number-of-volumes) KB + (2.5 number-of-copy-pairs) KB For executing the YKIMPORT command: Installing Business Continuity Manager 2-7

28 4,000 KB + (1 number-of-volumes) KB + (2.5 numberof-copy-pairs-to-be-created) KB + (3 number-of-basegroup-copy-pairs) KB For executing YKBTSCAN: 4,000 KB + (1.5 number-of-volumes-to-be-scanned) KB + (2 number-of-scanned-volumes) KB number-of-volumes: Total number of volumes in the device address domain to be used. If multiple copy groups are used, the sum of the volumes in each copy group. number-of-copy-pairs: Number of copy pairs in the copy group definition file to be used. number-of-copy-pairs-to-be-created: Number of copy pairs to be created by using the YKIMPORT command. number-of-basegroup-copy-pairs: Number of copy pairs in the copy group definition file to be based on. number-of-volumes-to-be-scanned: Total number of volumes included in the range to be scanned by YKBTSCAN. number-of-scanned-volumes: Total number of volumes in the disk configuration definition file if YKBTSCAN is executed to add volumes to an existing disk configuration definition file. A B : Indicates that the result of A B is rounded up to the nearest integer. The memory required when linking with Replication Manager is shown below. The PREFIX parameter and DEVN parameter in the formula below are the initialization parameters of the Business Continuity Manager agent: For a user region of 16 MB less than: 2,048 KB For an extended user region of 16 MB or more: 6,000 KB + A KB + (512 number-of-specified-prefix-parameters) 1,024 KB + (64 number-of-specified-devn-parameters) 1,024 KB A: The larger of (1.5 D) and (3 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 Business Continuity Manager agent, the highest number of copy pairs in any group. Where " A B " indicates rounding up the decimal numbers from the result of A B. The amount of memory required to use BCM Monitor is shown below. For a user region of 16 MB less than: 2,048 KB 2-8 Installing Business Continuity Manager

29 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 Preparations for installing Business Continuity Manager To transmit the Business Continuity Manager load module from the CD-ROM to a host machine: 1. Copy the following files provided on the installation CD-ROM to the PC. Business Continuity Manager object archive Dataset creating sample JCL (ALLOUPLD.JCL) TSO/E RECEIVE processing sample JCL (RECVUPLD.JCL) 2. From the PC and using ASCII, transfer the following sample JCLs to a host machine: Dataset creating sample JCL (ALLOUPLD.JCL) TSO/E RECEIVE processing sample JCL (RECVUPLD.JCL) 3. Edit the JCLs transferred in step 2 to match your installation environment. For details, see the header comments in the JCLs. For modification examples, see Appendix A, Modifying sample JCL on page A Create space for the datasets to be transferred (execute the edited ALLOUPLD job). The ALLOUPLD job creates the sequential dataset space for transferring the Business Continuity Manager object archive to the host machine. For examples of modifying sample JCL (ALLOUPLD), see ALLOUPLD (creating transmission datasets) on page A Transfer the Business Continuity Manager object archive from the PC to the host machine. From the PC, in binary mode, transfer the Business Continuity Manager object archive (that you created in step 4) to the sequential dataset space on the host machine. For details about the archive files to be transmitted, see Table 2-1 Files provided on installation CD-ROM on page Perform TSO/E RECEIVE processing (execute the edited RECVUPLD job). Execute the RECVUPLD job modified in accordance with the installation environment, and extract the dataset provided from the archives transmitted in step 5. For examples of modifying sample JCL (RECVUPLD), see RECVUPLD (TSO/E RECEIVE processing) on page A-5. Business Continuity Manager is ready to be installed using SMP/E as described in section Installing Business Continuity Manager with SMP/E on Installing Business Continuity Manager 2-9

30 page 2-10, or by the simple installation as described in section Simple installation (installation without SMP/E) on page Installing Business Continuity Manager Business Continuity Manager installation involves multiple steps. Use SMP/E or simple installation to complete an installation. To install the extended access control function, you need to use SMP/E for installation. For details about the extended access control function, see the Hitachi Business Continuity Manager User Guide. Installing Business Continuity Manager with SMP/E These sample JCL library members that are installed with SMP/E must be modified in accordance with the user installation environment. Details are shown at the beginning of each sample JCL. For modification examples, see Appendix A, Modifying sample JCL on page A-1. The storage locations for the sample jobs are as follows: The sample JCL is stored in the HITACHI.CHYKnnn.F1 dataset (the nnn part varies depending on the version) after the procedure in section Preparations for installing Business Continuity Manager on page 2-9 is performed. If you change the RECVUPLD job and the output destination dataset name for the TSO/E RECEIVE command, the sample JCL is stored in the dataset after the changes. JCL member names and their functions are listed below. To install the Business Continuity Manager product with SMP/E, execute the sample jobs below in the following order: 1. SMPALLOC Allocate the SMP/E control dataset as necessary. If an existing SMP/E control dataset is to be used, skip this step. For examples of modifying sample JCL (SMPALLOC), see SMPALLOC (allocating SMP/E datasets) on page A HDSYK1AL Allocate the distribution library (DLIB) and the target library. When upgrading Business Continuity Manager, if an existing SMP/E control dataset is to be used, skip this step. For examples of modifying sample JCL (HDSYK1AL), see HDSYK1AL (allocating distribution and target libraries) on page A HDSYK2DF Execute SMP/E DDDEF to define the distribution library (DLIB) and target library. When upgrading Business Continuity Manager, if an existing SMP/E control dataset is to be used, skip this step. For examples of modifying sample JCL (HDSYK2DF), see HDSYK2DF (defining distribution and target libraries) on page A HDSYK3RC 2-10 Installing Business Continuity Manager

31 Execute SMP/E RECEIVE to load the provided datasets and store them in the global zone. For examples of modifying sample JCL (HDSYK3RC), see HDSYK3RC (SMP/E RECEIVE processing) on page A HDSYK4AP Execute SMP/E APPLY to install the provided dataset in the target library (the library shown in Table 2-4 DASD storage attributes for target libraries on page 2-5). The APPLY command in the sample JCL specifies the CHECK operand. If execution with the CHECK operand does not generate an error, delete the CHECK operand and re-execute the job. When upgrading Business Continuity Manager, if the dataset is to be installed in an existing target library, change the CHECK operand to the COMPRESS(ALL) operand and reexecute the job. For examples of modifying sample JCL (HDSYK4AP), see HDSYK4AP (creating target libraries) on page A HDSYK5AC Execute SMP/E ACCEPT to install the provided dataset in the distribution library (the library shown in Table 2-3 DASD storage attributes for distribution libraries (DLIB) on page 2-4). The ACCEPT command in the sample JCL specifies the CHECK operand. If execution with the CHECK operand does not generate an error, delete the CHECK operand and re-execute the job. When upgrading Business Continuity Manager, if the dataset is to be installed in an existing target library, change the CHECK operand to the COMPRESS(ALL) operand and reexecute the job. For examples of modifying sample JCL (HDSYK5AC), see HDSYK5AC (creating distribution libraries) on page A-19. Note: When the HDSYK4AP job executes successful, the new release of Business Continuity Manager is installed. Verify that this new release of Business Continuity Manager executes correctly and then accept it by executing the HDSYK5AC job. To install the extended access control function, perform the following steps. 7. HDSYK6RC Execute SMP/E RECEIVE for the extended access control function to load the provided datasets and store them in the global zone. For examples of modifying sample JCL (HDSYK6RC), see HDSYK6RC (SMP/E RECEIVE processing for extended access control function) on page A HDSYK7AP Execute SMP/E APPLY for the extended access control function to install the provided dataset in the target library (the library shown in Table 2-4 DASD storage attributes for target libraries on page 2-5). Installing Business Continuity Manager 2-11

32 The APPLY command in the sample JCL specifies the CHECK operand. If execution with the CHECK operand does not generate an error, delete the CHECK operand and re-execute the job. For examples of modifying sample JCL (HDSYK7AP), see HDSYK7AP (creating target libraries for extended access control function) on page A HDSYK8AC Execute SMP/E ACCEPT for the extended access control function to install the provided dataset in the distribution library (the library shown in Table 2-3 DASD storage attributes for distribution libraries (DLIB) on page 2-4). The ACCEPT command in the sample JCL specifies the CHECK operand. If execution with the CHECK operand does not generate an error, delete the CHECK operand and re-execute the job. For examples of modifying sample JCL (HDSYK8AC), see HDSYK8AC (creating distribution libraries for extended access control function) on page A-24. Simple installation (installation without SMP/E) This section explains installation that does not use SMP/E. This method does not use SMP/E; instead, installation is performed directly from the provided dataset to the target library. Members of the sample JCL library being installed must be changed according to the user's installation environment. Details are shown at the beginning of each sample JCL. For modification examples, see Appendix A, Modifying sample JCL on page A-1. The storage destinations for sample jobs are shown below: The sample JCL is stored in the HITACHI.CHYKnnn.F1 dataset (the nnn part varies depending on the version) after the procedure in section Preparations for installing Business Continuity Manager on page 2-9 is performed. If the RECVUPLD job is changed and the output destination dataset name for the TSO/E RECEIVE command is changed, the sample JCL is stored in the dataset after the changes. JCL member names and functions are shown below. The following sample JCL is executed during a simple installation. HDSYKSIN Copies the content of the provided datasets to the target library. For examples of modifying sample JCL (HDSYKSIN), see HDSYKSIN (simple installation) on page A-6. Setting up the environment This section describes how to set up a Business Continuity Manager environment Installing Business Continuity Manager

33 The following table lists the items that must be performed to set up the environment. Perform these items in the order listed in the table. Table 2-7 Items that must be performed for environment setup Item order Item Description See: 1 Settings for using CLI commands in TSO/E environments 2 Settings for using ISPF panels with Business Continuity Manager 3 Settings in the ISPF panel 4 Settings for using the YKWATCH command and the copy group definition generation function for PPRC copy pairs Settings needed for using CLI commands in TSO/E environments The YKSTART command must be configured to use ISPF panels with Business Continuity Manager. The following settings are in the ISPF panel: PF key usage Command line position settings Settings for the number of PF keys to display YKWPROC must be configured for executing the YKWATCH command and the copy group definition generation function for PPRC copy pairs as background jobs. Settings for using CLI commands in TSO/E environments on page 2-14 Settings for using ISPF panels with Business Continuity Manager on page 2-15 Settings in the ISPF panel on page 2-16 Settings for using the YKWATCH command and the copy group definition generation function for PPRC copy pairs on page Settings for using environment configuration commands Settings needed for using the following environment configuration commands: YKALCSVC command: Registers a user SVC. YKSETENV command: Sets the Business Continuity Manager environment variables. YKDSPENV command: Displays the Business Continuity Manager environment variables. Settings for using environment configuration commands on page Setting security Security settings for environment configuration commands, CLI commands, and datasets Setting the security on page Registering a user SVC User SVC registration # Setting the security on page Setting Business Continuity Manager environment variables 9 Registering a license Setting the environment variables required for Business Continuity Manager operation. # Registering a license key to enable the corresponding functionality. Setting Business Continuity Manager environment variables on page 2-26 Registering a license on page 2-34 Installing Business Continuity Manager 2-13

34 Item order Item Description See: 10 Verification procedure following installation and setup Verify that the installation and environment setup have been performed correctly. Verification procedure following installation and setup on page 2-39 # Business Continuity Manager shares a User SVC, environment variables, and system symbols, with Tiered Storage Manager for Mainframe and MAR. Therefore, you need to take this into consideration in environments in which Tiered Storage Manager for Mainframe or MAR is installed. For details, see Notes on system setup when a related product is installed on page Settings for using CLI commands in TSO/E environments Business Continuity Manager provides TSO/E commands such as YKBLDCMD, YKMAKE and YKSUSPND. These commands require access to services granted on MVS in order to perform I/Os to offline devices. To allow access and to make these commands available in a TSO/E environment: 1. Concatenate the HDSYLNKT library (the load library where CLI commands are stored) to LNKLST. The library can be concatenated via either of the following: Add the HDSYLNKT library to the PROGxx parmlib member as a data set to be concatenated to LNKLST. Use the SETPROG LNKLST command to dynamically concatenate to LNKLST. For details on the SETPROG command, see the IBM manual MVS System Commands. 2. Register the HDSYLNKT library for APF authorization. The library can be registered via either of the following: Add the HDSYLNKT library to the PROGxx parmlib member as a data set to be authorized as APF. Use the SETPROG APF,ADD command to dynamically register APF authorization. For details on the SETPROG command, see the IBM manual MVS System Commands. Note: LNKLST has APF authorization by default. For this reason, you do not have to perform step 2 if the HDSYLNKT library was concatenated to LNKLST in step 1. Note that there are exceptions to this rule as well. For details on APF authorization related to LNKLST, see the IBM manual MVS Initialization and Tuning Reference Installing Business Continuity Manager

35 3. Register the CLI command name YKCONMSG to the AUTHCMD section of the IKJTSOxx parmlib member. Once this update is complete, TSO/E can be updated dynamically using the TSO/E PARMLIB CHECK(nn) and PARMLIB UPDATE(nn) commands. See the IBM manual TSO/E System Programming Command Reference. Settings for using ISPF panels with Business Continuity Manager YKSTART is a REXX script that provides an ISPF panel interface. Executing the YKSTART command enables Business Continuity Manager for ISPF panels. Concatenating the libraries needed to execute the YKSTART command To concatenate the libraries needed to execute the YKSTART command: 1. Concatenate the REXX Exec library HDSYEXET or HDSYEXVT to the dd name SYSEXEC. If the library that is concatenated to the dd name SYSEXEC is a fixed length format (RECFM=FB), concatenate to the REXX Exec library HDSYEXET. If the library that is concatenated to the dd name SYSEXEC is a variable length format (RECFM=VB), concatenate to the REXX Exec library HDSYEXVT. 2. Concatenate the panel library HDSYPNLT to the dd name ISPPLIB. Note: In an environment in which the DBCS functionality is used, concatenate HDSYPNLT to the alternate panel library (dd name ISPPALT) as well. For details, see the IBM manual ISPF User's Guide Volume I. 3. Concatenate the message library HDSYMSGT to the dd name ISPMLIB. Note: In an environment in which the DBCS functionality is used, concatenate HDSYMSGT to the alternate message library (dd name ISPMALT) as well. For details, see the IBM manual ISPF User's Guide Volume I. 4. Concatenate the table library HDSYTABT to the dd name ISPTLIB. When you concatenate datasets, determine RECFM and LRECL, considering the attributes in Table 2-4 DASD storage attributes for target libraries on page 2-5 and those of the datasets to be concatenated. For example, if DSORG=PO and RECFM=FB, LRECL must be the same in all the datasets. For details, see the IBM manual DFSMS: Using Data Sets. For details on how to change RECFM and LRECL, refer to the information on IEBGENER and IEBCOPY in the IBM manual DFSMSdfp Utilities. Once configured, YKSTART can be started by selecting 6 Command in the ISPF Primary Option Menu and is included as a selection in each sitespecific selection menu. Installing Business Continuity Manager 2-15

36 Starting YKSTART dynamically You can start YKSTART by dynamically concatenating the libraries required to execute YKSTART. The REXX Exec library HDSYEXET or HDSYEXVT can be dynamically concatenated by the ALTLIB command of TSO/E. The panel library HDSYPNLT, message library HDSYMSGT, and table library HDSYTABT can be dynamically concatenated by the LIBDEF service of ISPF. The example below shows how to use the ALTLIB command and LIBDEF service. By executing the REXX script below during ISPF startup, you can start Business Continuity Manager with individual libraries being dynamically concatenated to the dd names SYSEXEC, ISPPLIB, ISPMLIB, and ISPTLIB. /* REXX */ ADDRESS TSO "ALTLIB ACTIVATE APPLICATION(EXEC)", "DATASET('HDSYK.Vnnnnnn.HDSYEXET')"; ADDRESS ISPEXEC; "LIBDEF ISPMLIB DATASET ID('HDSYK.Vnnnnnn.HDSYMSGT') STACK"; "LIBDEF ISPPLIB DATASET ID('HDSYK.Vnnnnnn.HDSYPNLT') STACK"; "LIBDEF ISPTLIB DATASET ID('HDSYK.Vnnnnnn.HDSYTABT') STACK"; "SELECT CMD(%YKSTART) NEWAPPL(YK) PASSLIB"; "LIBDEF ISPTLIB"; "LIBDEF ISPPLIB"; "LIBDEF ISPMLIB"; ADDRESS TSO "ALTLIB DEACTIVATE APPLICATION(EXEC)"; Return 0; Note: In an environment in which the DBCS functionality is used, concatenate HDSYPNLT to the alternate panel library (dd name ISPPALT) as well. Also, concatenate HDSYMSGT to the alternate message library (dd name ISPMALT). For details, see the IBM manual ISPF User's Guide Volume I. Settings in the ISPF panel Setting the position of the command line You can select whether to position the command line (Command line) at the top or at the bottom of each panel. To set the position of the command line: 1. Start Business Continuity Manager, type SETTINGS on the command line, and then press the Enter key. The ISPF Settings panel appears Installing Business Continuity Manager

37 2. To display the command line at the top of panels, clear the Command line at bottom checkbox. To display the command line at the bottom of panels, select the Command line at bottom checkbox. Setting the number of PF keys that are displayed You can set the number of PF keys that are displayed. This setting is saved in the profile even after Business Continuity Manager is stopped. To set the number of PF keys that are displayed: 1. Start Business Continuity Manager, type PFSHOW TAILOR on the command line, and then press the Enter key. The ISPF Settings panel appears. 2. Set a value in Number of keys. Caution: If the specified value is between F1 and F12, the F17=DispConf and F18=Exctg keys are not displayed. Settings for using the YKWATCH command and the copy group definition generation function for PPRC copy pairs The YKWATCH command and the copy group definition generation function for PPRC copy pairs are executed as background jobs. YKWPROC is the procedure for a background job of YKWATCH and of the Copy Group Definition Generation Function for PPRC copy pairs. To use the YKWATCH command or the Copy Group Definition Generation Function for PPRC copy pairs, specify the JCL of the background job for JCL JOB Statement in the Set Defaults panel. Perform either of the following operations to enable YKWPROC to be executed: Concatenate the cataloged procedures library HDSYPRCT to the dd name IEFPDSI in the MSTJCLxx parmlib member. Copy the YKWPROC member from the cataloged procedures library HDSYPRCT to a user PROCLIB. Note: Modify the dataset names in this procedure according to the names used for the target library HDSYLNKT and HDSYEXET. Settings for using environment configuration commands The following table lists the functions of the environment configuration commands. Table 2-8 Environment configuration commands and their functions Command name YKALCSVC YKSETENV Registers the user SVC. Function Sets the following environment variables: Installing Business Continuity Manager 2-17

38 Command name YKDSPENV Host ID Function Prefix for the license information dataset BCM log output method Whether CLI command-execution logs are output to SYSLOG or the console Displays the specified Business Continuity Manager environment variables and the program product name. Setting the security To use environment configuration commands, perform one of the procedures below. Before performing either procedure, perform the procedure described in section Settings for using CLI commands in TSO/E environments on page Link the HDSYPRCT cataloged procedure library to the IEFPDSI dd name of the MSTJCLxx parmlib member. Copy the YKALCSVC member, YKSETENV member, and YKDSPENV member from the HDSYPRCT cataloged procedure library to the user's PROCLIB. Once you have added these commands in the COMMNDxx parmlib member, it is automatically executed at the time of an IPL. Setting security for the environment configuration commands To use the YKALCSVC or YKSETENV command, you must restrict user access by using the RACF program control function. Note that you do not need to restrict user access for the YKDSPENV command. For details, see the IBM manual Security Server RACF Security Administrator's Guide. If you use the YKALCSVC or YKSETENV command without restricting user access, Business Continuity Manager might not operate properly. Setting security for CLI commands, YKAGENTD, and YKBTSCAN Business Continuity Manager controls access regarding the CLI commands, YKAGENTD (Business Continuity Manager agent), and YKBTSCAN (local batch scanning) as a basic access control function. Therefore, to use these commands and functionality, you must set up the RACF. Users can use these functions once profiles have been defined for the RACF FACILITY class, and once READ permissions for these profiles have been set to the users' accounts. For details about the extended access control function, see the Hitachi Business Continuity Manager User Guide. There are two types of profiles: operation profiles and reference profiles. The following table lists the correspondence between profiles defined in the FACILITY class and available functions Installing Business Continuity Manager

39 Table 2-9 Correspondence between profiles defined in the FACILITY class and available functions Profile defined for the FACILITY class STGADMIN.YKA.BCM.COMMANDS (Operation profiles) YKAGENTD YKBLDCMD command Available functions YKBLDPTH command YKBTSCAN YKDELCMD command YKDELETE command YKDELPTH command YKEWAIT command YKFCSTAT command YKFREEZE command YKH2B command YKMAKE command YKQEXCTG command YKQHPATH command YKQRYDEV command YKQRYPTH command YKQUERY command YKRECVER command YKRESYNC command YKRUN command YKSCAN command YKSTATS command YKSUSPND command YKWATCH command STGADMIN.YKA.BCM.YKQUERY (Reference profiles) YKAGENTD YKBTSCAN YKEWAIT command YKFCSTAT command YKH2B command YKQEXCTG command YKQHPATH command Installing Business Continuity Manager 2-19

40 Profile defined for the FACILITY class Available functions YKQRYDEV command YKQRYPTH command YKQUERY command YKSCAN command YKSTATS command YKWATCH command Note: The following commands are available for use even if both of the access permissions are not assigned to a user: YKCONMSG YKDROP YKENV YKERCODE YKEXPORT YKGETHDA YKIMPORT YKINSCHK YKLOAD YKSLEEP YKSTORE YKWTOMSG YKWTOR Caution: Use profiles to restrict access to the following commands. Unrestricted access to these commands could have an adverse affect on recovery operations at a remote site. YKBLDCMD YKBLDPTH YKDELCMD YKDELETE YKDELPTH YKFREEZE YKMAKE YKRECVER YKRESYNC YKRUN YKSUSPND 2-20 Installing Business Continuity Manager

41 For details on how to set the READ permissions for the profiles to the user, see Procedure for setting the READ permission for the RACF profile to the user on page Setting security when the extended access control function is installed When the extended access control function (copy group access control function, specific command access control function) is installed in Installing Business Continuity Manager with SMP/E on page 2-10, you need to set the access control (RACF settings). After defining the profile to the RACF FACILITY class, set the READ permission for that profile to the user. This section describes about the profile types to be defined in the FACILITY class and how to set the READ permission for the profile. For details on how to design the access permissions, such as which READ permission for the profile is to be set to which user's account, see "Extended access control functions" in the Hitachi Business Continuity Manager User Guide. Profiles to be defined to the FACILITY class used by the extended access control function The following table shows the profiles to be defined to the FACILITY class used by the extended access control function: Table 2-10 Profiles to be defined to the FACILITY class used by the extended access control function Extended access control function Copy group access control function Specific command access control function Profiles to be defined to the FACILITY class STGADMIN.YKA.BCM.PFX.prefix (prefix profile) STGADMIN.YKA.BCM.CGTYPE.copy-type (copy type profile) STGADMIN.YKA.BCM.CGNAME.copy-group-ID (copy group profile) STGADMIN.YKA.BCM.CLI.YKDELETE (YKDELETE command profile) STGADMIN.YKA.BCM.CLI.YKMAKE (YKMAKE command profile) STGADMIN.YKA.BCM.CLI.YKRECVER (YKRECVER command profile) STGADMIN.YKA.BCM.CLI.YKQRYDEV (YKQRYDEV command profile) STGADMIN.YKA.BCM.CGTYPE.copy-type (copy type profile) Legend: Installing Business Continuity Manager 2-21

42 prefix: Prefix for the configuration file name copy-type: SI, TC, TCA, or UR copy-group-id: Copy group ID Tip: Generic term names can be used for profile names. Procedure for setting the READ permission for the profile to the user For details on how to set the READ permission for the profile to the user, see Procedure for setting the READ permission for the RACF profile to the user on page Procedure for setting the READ permission for the RACF profile to the user To set READ permissions for profiles to a user account: One of the following is set for profile-name: STGADMIN.YKA.BCM.CGNAME.copy-group-ID STGADMIN.YKA.BCM.CGTYPE.copy-type STGADMIN.YKA.BCM.CLI.YKDELETE STGADMIN.YKA.BCM.CLI.YKMAKE STGADMIN.YKA.BCM.CLI.YKQRYDEV STGADMIN.YKA.BCM.CLI.YKRECVER STGADMIN.YKA.BCM.COMMANDS STGADMIN.YKA.BCM.PFX.prefix STGADMIN.YKA.BCM.YKQUERY 1. Activate the RACF FACILITY class. SETROPTS CLASSACT(FACILITY) 2. Define the profile-name profile for the FACILITY class. RDEFINE FACILITY profile-name UACC(NONE) 3. Add READ permissions for the defined profile to the user account. PERMIT profile-name CLASS(FACILITY) ID(user-ID) ACCESS(READ) If you want to improve the execution performance of Business Continuity Manager, we recommend that you enable the RACLIST function (in-storage profiles) for the FACILITY class. Execute one of the following commands to enable the RACLIST function. If the FACILITY class has not been activated by RACLIST: SETROPTS RACLIST(FACILITY) 2-22 Installing Business Continuity Manager

43 If the FACILITY class has already been activated by RACLIST: SETROPTS RACLIST(FACILITY) REFRESH For details about how to activate the RACF FACILITY class, how to define a profile, and how to assign READ permissions for profiles to user accounts, see the IBM manual Security Server RACF Security Administrator's Guide. Setting security for starting a System REXX environment The Business Continuity Manager CLI commands can be executed in a System REXX environment. To start a System REXX environment, you must set up the RACF. Define the AXR*.* profile for the STARTED class of the RACF, and then define the SYSREXX.* profile for the SURROGAT class. Then, set the READ permissions for these profiles to users. For details, see the IBM manual MVS Programming: Authorized Assembler Services Guide. Configuring dataset security The Business Continuity Manager configuration file is created and saved based on the prefix value of the user-provided dataset name. Once the storage manager has decided on a prefix value, a data security mechanism must be implemented to control the READ and WRITE permissions, depending on the TSO/E user's storage management role. Registering a user SVC You must use one of the following methods to register the user SVC: Registration using the IEASVCxx parmlib member Registration using the YKALCSVC command If you use the IEASVCxx parmlib member to perform registration, you must reload the system (that is, perform an initial program load (IPL)). If you cannot perform a re-ipl while the system is running, use the YKALCSVC command to perform registration. Using the IEASVCxx parmlib member to register To register using IEASVCxx parmlib: 1. Choose a number between 200 and 255 to assign to the user SVC. 2. Insert the following SYMDEF statement (&YKSVCNO system symbol) into the IEASYMxx parmlib member: SYMDEF(&YKSVCNO= SVC-number') For SVC-number, specify a decimal number between 200 and Link the HDSYLPAT library to LPALST, using one of the following methods: Define the HDSYLPAT library in the LPALSTxx parmlib member. For details, see the IBM manual MVS Initialization and Tuning Reference. Installing Business Continuity Manager 2-23

44 Use the SETPROG LPA command to update dynamically. For details, see the IBM manual MVS System Commands. 4. Define the following SVCPARM statement in the IEASVCxx parmlib member. SVCPARM SVCnumber,REPLACE,TYPE(3),EPNAME(JYUASVC),APF(NO),NPRMPT(NO),AR(NO) 5. Perform re-ipl with the CLPA parameter specified. Tip: For details about steps 2 and 4, see the IBM manual MVS Initialization and Tuning Reference. Caution: If you perform a new installation of Business Continuity Manager in an environment in which Tiered Storage Manager for Mainframe or MAR is installed, you need to be careful when registering a user SVC. For details, see Notes on user SVC registration when a related product is installed on page Using the YKALCSVC command to register To register a user SVC, execute the YKALCSVC command when the system starts or before you use Business Continuity Manager. YKALCSVC command format The following shows the formats of the YKALCSVC commands. For details about command formats, see Appendix E, Conventions in syntax explanations on page E-1. Format START YKALCSVC[,PARM='{SVC-number DELETE}'] Function Registers or deletes a user SVC. Parameters SVC-number <numeric characters> ~ ((200 to 255)) DELETE Specifies a SVC number to assign to a user SVC. Specified to delete a user SVC. If you omit the optional PARM= part of the command, an unused SVC number between 200 and 255 is assigned. Return codes Table 2-11 YKALCSVC command return codes list Return code Meaning 0 The command ended normally Installing Business Continuity Manager

45 Return code Meaning 4 The SVC number is already registered. 16 Registration or deletion of the SVC number failed. 20 Processing stopped due to an error (the specified value or execution environment is invalid). Example of specifying the SVC number Execute the following command to specify the SVC number: START YKALCSVC,PARM='SVC-number' An error is returned if another user SVC is already assigned to the SVC number specified here. By omitting the PARM parameter, an unused SVC number between 200 and 255 is assigned. START YKALCSVC To delete a user SVC, specify DELETE as the parameter and execute YKALCSVC command. START YKALCSVC,PARM='DELETE' Note: If you delete a user SVC using the YKALCSVC command while Business Continuity Manager is running, CLI commands that are being executed terminate abnormally. If you use the YKALCSVC command to register a user SVC while Business Continuity Manager is running, CLI commands that are being executed will use the user SVC defined by the IEASVCxx parmlib member. The registered user SVC will take effect the next time a CLI command is executed. The user SVC registered with YKALCSVC command is lost when an IPL is performed. Before you perform another IPL, we recommend you specify one of the following settings: -Add the YKALCSVC command to the COMMNDxx parmlib member; so that the user SVC is automatically registered each time an IPL is performed. -Define the user SVC in the IEASVCxx parmlib member, and then use the user SVC that is registered at the next IPL. The user SVC routine registered with the YKALCSVC command of Business Continuity Manager 5.1 or later cannot be deleted by using a YKALCSVC command of Business Continuity Manager earlier than version 5.1. So, be careful when you perform an upgrade in an environment where multiple versions are used. Installing Business Continuity Manager 2-25

46 If you perform a new installation of Business Continuity Manager in an environment in which Tiered Storage Manager for Mainframe or MAR is installed, you need to be careful when registering a user SVC. For details, see Notes on user SVC registration when a related product is installed on page Setting Business Continuity Manager environment variables Before starting Business Continuity manager, use the YKSETENV command to set Business Continuity Manager environment variables. A re-ipl will invalidate Business Continuity Manager environment variables set using the YKSETENV command. Therefore, we recommend that you use one of the following methods to automatically set Business Continuity Manager environment variables when a re-ipl takes place: Add the YKSETENV command to the COMMNDxx parmlib member. Specify values for the system symbols in the IEASYMxx parmlib member, which correspond to the Business Continuity Manager environment variables. After setting the Business Continuity Manager environment variables, use the YKDSPENV command to verify that they have been specified correctly. For details about the YKSETENV command format, see YKSETENV command format on page For details about the YKDSPENV command format, see YKDSPENV command format on page The following table describes the Business Continuity Manager environment variables that can be set, their meanings, their corresponding system symbol names, and their default values. Table 2-12 Business Continuity Manager environment variables that can be set Business Continuity Manager environment variable Meaning Corresponding system symbol names Default value YKCMDIF Host ID &YKCMDIF 00 YKLCNSE YKLCNS2 Prefix of the license information dataset &YKLCNSE and &YKLCNS2 HITACHI #1 LOGPUT Whether the system logger service #2 is used &YKLOGPT LOGR: Uses the system logger service SYSLOG Whether CLI command-execution logs are output to SYSLOG or the console &YKSYSLG YES: Outputs CLI commandexecution logs to SYSLOG 2-26 Installing Business Continuity Manager

47 #1: For details about the relationship between the prefix of the license information dataset and the specification status for the YKSETENV command or IEASYMxx parmlib member, see section Naming for license information datasets on page #2: For details about the system logger service, see the Hitachi Business Continuity Manager User Guide. Alternatively, you can define the corresponding system symbols in the IEASYMxx parmlib member and then perform a re-ipl of the system to set values for the Business Continuity Manager environment variables. If you cannot perform the re-ipl because the system is running, use the YKSETENV command to set environment variables. The priority order for specifying values is as follows: 1. value-specified-by-the-yksetenv-command 2. value-specified-for-the-ieasymxx-parmlib-member 3. default-value Specifying the host ID If the YKSETENV command is executed without specifying parameters, the corresponding system symbol values are used as the Business Continuity Manager environment variables. If no value is specified for the YKSETENV command parameters and the corresponding system symbols, the default values are used as the Business Continuity Manager environment variables. The following sections provide examples of configuring the environment. For details about how to specify the prefixes for license information datasets, see section Naming for license information datasets on page Note: If you use the YKSETENV command to set Business Continuity Manager environment variables, perform the procedure described in section Settings for using CLI commands in TSO/E environments on page When the Remote DKC Control Function is being used, if you want to make multiple hosts (OSs) on the same site use Business Continuity Manager and share one command device in a storage system, specify the host IDs. If there is only one host (OS) on the site, or you do not make multiple hosts share one command device, you do not need to specify the host ID. For the host ID, specify a hexadecimal two-digit number from 00 to 1F that is unique for each OS. In an LPAR environment, specify a different number for each LPAR. The examples below show how to specify a host ID. If neither (a) nor (b) is specified, 00 is assumed. Using the YKSETENV command The following example sets the host ID to 0F: Installing Business Continuity Manager 2-27

48 START YKSETENV,PARM='YKCMDIF=0F' Note: If you register or change a host ID while Business Continuity Manager is running, the CLI commands will be executed using the previous set value. The registered or changed host ID will take effect the next time the YKLOAD command (with a route list specified) is executed. Defining a system symbol in the IEASYMxx parmlib member The following example sets the host ID to 0F: SYMDEF(&YKCMDIF='0F') Enabling and disabling the system logger service The following specification examples show how to set Business Continuity Manager logs to be output to an external dataset (using the system logger service), or to be output to a sequential dataset (without using the system logger service). Using the YKSETENV command The following shows an example of defining a symbol when you do not want to use the system logger service: START YKSETENV,PARM='LOGPUT=SAM' The following shows an example of defining a symbol when you do want to use the system logger service: START YKSETENV,PARM='LOGPUT=LOGR' Caution: If you use the YKSETENV command to change the BCM log output destination while Business Continuity Manager is running, Business Continuity Manager will be run using the previously set value. The change will take effect when you log on to the TSO/E terminal again. The LOGPUT environment variable is shared by Business Continuity Manager, Tiered Storage Manager for Mainframe, and MAR. Therefore, you need to be careful when setting the LOGPUT environment variable in an environment in which Tiered Storage Manager for Mainframe or MAR is installed. For details, see Notes on setting environment variables or system symbols when a related product is installed on page Defining a system symbol in the IEASYMxx parmlib member Define the system symbol &YKLOGPT for the IEASYMxx parmlib member. After making the definition, enable the setting by re-performing the IPL of the host Installing Business Continuity Manager

49 The following shows an example of defining a symbol when you do not want to use the system logger service: SYMDEF(&YKLOGPT='SAM') The following shows an example of defining a symbol when you do want to use the system logger service: SYMDEF(&YKLOGPT='LOGR') If &YKLOGPT is omitted, or if an incorrect value is specified, LOGR is assumed. Caution: The &YKLOGPT system symbol is shared by Business Continuity Manager, Tiered Storage Manager for Mainframe, and MAR. Therefore, you need to be careful when setting the &YKLOGPT system symbol in an environment in which Tiered Storage Manager for Mainframe or MAR is installed. For details, see Notes on setting environment variables or system symbols when a related product is installed on page Specifying whether to output CLI command-execution logs The following specification examples show how to specify whether to output CLI command-execution logs to SYSLOG or the console. Using the YKSETENV command The following shows an example of defining a symbol when you do not want to output the CLI command-execution logs: START YKSETENV,PARM='SYSLOG=NO' The following shows an example of defining a symbol when you do want to output the CLI command-execution logs to SYSLOG: START YKSETENV,PARM='SYSLOG=YES' The following shows an example of defining a symbol when you do want to output the CLI command-execution logs to the console: START YKSETENV,PARM='SYSLOG=CONSOLE' Caution: The SYSLOG environment variable is shared by Business Continuity Manager and Tiered Storage Manager for Mainframe. Therefore, you need to be careful when setting the SYSLOG environment variable in an environment in which Tiered Storage Manager for Mainframe is installed. For details, see Notes on setting environment variables or system symbols when a related product is installed on page Installing Business Continuity Manager 2-29

50 Defining a system symbol in the IEASYMxx parmlib member The following shows an example of defining a symbol when you do not want to output the CLI command-execution logs: SYMDEF(&YKSYSLG='NO') The following shows an example of defining a symbol when you do want to output the CLI command-execution logs to SYSLOG: SYMDEF(&YKSYSLG='YES') The following shows an example of defining a symbol when you do want to output the CLI command-execution logs to the console: SYMDEF(&YKSYSLG='CONSOLE') If &YKSYSLG is omitted, or if an incorrect value is specified, YES is assumed. If you output a CLI command-execution log to the console, the log is output to the console by using ROUTCODE=11 (output as the YKZ910I message and the YKZ911I message). Therefore, include 11 in the ROUTCODE parameter of the CONSOLE statement or in the ROUTCODE parameter of the HARDCOPY statement in the CONSOLxx parmlib member. Perform either of the following operations to change the ROUTCODE value for the CLI command-execution log (the YKZ910I message and the YKZ911I message) to a value other than 11: In MPFLSTxx, register USEREXIT that targets the YKZ910I message and the YKZ911I message. In the USEREXIT to be registered, change the ROUTCODE value for the YKZ910I message and the YKZ911I message from 11 to a different value (the value included in the ROUTCODE parameter in the CONSOLxx parmlib member). Use WTO/WTOR Message Processing Facility Installation Exit (IEAVMXIT) to change the ROUTCODE value for the YKZ910I message and the YKZ911I message from 11 to a different value (the value included in the ROUTCODE parameter in the CONSOLxx parmlib member). For a sample exit routine (YKUSRXIT) that changes the ROUTCODE value of the YKZ910I message and the YKZ911I message, see the sample library provided by Business Continuity Manager. Caution: The &YKSYSLG system symbol is shared by Business Continuity Manager and Tiered Storage Manager for Mainframe. Therefore, you need to be careful when setting the &YKSYSLG system symbol in an environment in which Tiered Storage Manager for Mainframe is installed. For details, see Notes on setting environment variables or system symbols when a related product is installed on page Caution: For the output of CLI command-execution logs in an environment where multiple versions of Business Continuity Manager exist, see Specifying 2-30 Installing Business Continuity Manager

51 whether to output the CLI command-execution logs (SYSLOG) on page D-3. YKSETENV command format The following shows the formats of the YKSETENV commands. For details about command formats, see Appendix E, Conventions in syntax explanations on page E-1. Format START YKSETENV, PARM='{YKCMDIF=[host-id] YKLCNSE=[prefix1] YKLCNS2=[prefix2] LOGPUT=[LOGR SAM] SYSLOG=[YES CONSOLE NO]}[,...]' Function Sets the following Business Continuity Manager environment variables: Host ID. Prefix for the license information dataset. BCM Log output method. Whether or not CLI command-execution logs are output to SYSLOG or the console. Parameters YKCMDIF=[host-id] ~ <2-digit hexadecimals> ((00 to 1F)) For the host ID, specify a value that is unique among hosts (operating systems). The specified value for the host ID is given priority over the &YKCMDIF system symbol in the IEASYMxx parmlib member. If this command is executed with the host ID omitted (PARM='YKCMDIF=' is specified), the value of the &YKCMDIF system symbol will be used. YKLCNSE=[prefix1] ~ <8 or fewer alphanumeric characters> Specify a prefix1 for the license information dataset so that the name of the dataset is unique. If the prefix1 is omitted, specify PARM='YKLCNSE='. For details about the prefix1 for the license information dataset, see section Naming for license information datasets on page YKLCNS2=[prefix2] ~ <8 or fewer alphanumeric characters> Specify a prefix2 for the license information dataset so that the name of the dataset is unique. If the prefix2 is omitted, specify PARM='YKLCNS2='. For details about the prefix2 for the license information dataset, see section Naming for license information datasets on page LOGPUT=[LOGR SAM] Specify whether or not the system logger service is to be used, when outputting BCM logs. Installing Business Continuity Manager 2-31

52 The specified value for the LOGPUT parameter is given priority over the &YKLOGPT system symbol in the IEASYMxx parmlib member. If this command is executed with the LOGPUT parameter omitted (PARM='LOGPUT=' is specified), the value of the &YKLOGPT system symbol will be used. LOGR: BCM logs are output using the system logger service. SAM: BCM logs are output to sequential datasets. SYSLOG=[YES CONSOLE NO] Return codes Specify whether or not CLI command-execution logs are output to SYSLOG or the console. The value specified for the SYSLOG parameter is given priority over the &YKSYSLG system symbol in the IEASYMxx parmlib member. If this command is executed with the SYSLOG parameter omitted (PARM='SYSLOG=' is specified), the value of the &YKSYSLG system symbol will be used. YES: CLI command-execution logs are output to SYSLOG. CONSOLE: CLI command-execution logs are output to the console. NO: CLI command-execution logs are not output to SYSLOG. For details about commands that collect CLI command-execution logs, see the Hitachi Business Continuity Manager User Guide. Caution: For the output of CLI command-execution logs in an environment where multiple versions of Business Continuity Manager exist, see Specifying whether to output the CLI command-execution logs (SYSLOG) on page D-3. Table 2-13 YKSETENV command return codes list Return code Meaning 0 Successful completion. 4 The specified value is incorrect. Another value was used for execution. 8 The specified value is incorrect. Processing was cancelled. 12 Processing was cancelled due to a system error (such as a GETMAIN error). 16 An internal error occurred. Note: For parameters, you can specify multiple items within the allowable length for PARM. If more than one of the same parameter is specified, the latter one will take effect Installing Business Continuity Manager

53 YKDSPENV command format The following shows the formats of the YKSETENV commands. For details about command formats, see Appendix E, Conventions in syntax explanations on page E-1. Format START YKDSPENV, [PARM='[SUMMARY DETAIL]'] Function Displays the program product name and the Business Continuity Manager environment variables on the OS console. Parameters SUMMARY Displays the program product name and values of the Business Continuity Manager environment variables. DETAIL Return codes Displays the program product name, values of the Business Continuity Manager environment variables, values set by using the YKSETENV command, and values set by using system symbols. Table 2-14 YKDSPENV command return codes list Return code Meaning 0 Successful completion. 4 There is an error in the specified value. The command is executed assuming SUMMARY is input. In the following example, the YKDSPENV command is executed. The version part in this example varies depending on the version. Execution example 1 START YKDSPENV YKT403I Hitachi Business Continuity Manager YKT400I BC Manager environment variables (version) YKT401I Host ID: 00 YKT401I License info DSN prefix: HITACHI YKT401I BCM log output method: LOGR YKT401I CLI log output settings: YES Execution example 2 START YKDSPENV,PARM='DETAIL' YKT403I Hitachi Business Continuity Manager YKT400I BC Manager environment variables (version) YKT401I Host ID: 01 YKT401I License info DSN prefix: HTC1.BCM YKT401I BCM log output method: SAM YKT401I CLI log output settings: NO Installing Business Continuity Manager 2-33

54 YKT402I YKCMDIF = 01 (&YKCMDIF = "00" ) YKT402I YKLCNSE = HTC1 (&YKLCNSE = N/A ) YKT402I YKLCNS2 = BCM (&YKLCNS2 = N/A ) YKT402I LOGPUT = SAM (&YKLOGPT = "LOGR" ) YKT402I SYSLOG = NO (&YKSYSLG = "YES" ) Registering a license When you register a license, the corresponding functionality becomes available. Use either of the following methods to install a license key in the license information dataset: Use a license key file. # Directly enter a key code. #: The license key file is a text file provided by Hitachi. The following figure shows an overview of license registration. Using the license key file Figure 2-2 Overview of license registration With this method, you transfer the obtained license key file to MVS and use the Manage Licenses panel to register the license. For details about the panel used for the following procedure, see the Hitachi Business Continuity Manager Reference Guide. To use the license key file: 1. Create a license information dataset Installing Business Continuity Manager

55 For details on the license information dataset attributes, see section Format for license information datasets on page For details on license information dataset names, see section Naming for license information datasets on page Transfer the license key file to the host. Perform file transfer from the license key file to the MVS dataset (called the license key dataset) in the following format: ASCII mode Encoded (to EBCDIC) Assign the following attributes to the license key dataset in which the license key file is stored: Dataset format: VB or FB sequential dataset Record length: 200 bytes or greater Block size: optional The file transfer destination is assumed to be a license key dataset named BCM.LICENSE.KEYSFROM.HITACHI. 3. Start Business Continuity Manager. 4. Display the Main Menu panel and select 2 Manage Licenses. The Manage Licenses panel appears. 5. In the Manage Licenses panel, enter the license key dataset name (BCM.LICENSE.KEYSFROM.HITACHI) in the License Key Dataset Name field and press Enter. The license keys are read from the license key file and are installed in the license information dataset. The YK9001I message is output if the license key is installed correctly. 6. Use the Manage Licenses panel to confirm that the licenses have been installed correctly. Tip: If the license key file contains the license key for Tiered Storage Manager for Mainframe, that license key will also be installed. Directly entering a key code With this method, you directly enter a key code in the Manage Licenses panel to install the license. For details about the panel used in the following procedure, see the Hitachi Business Continuity Manager Reference Guide. To directly enter a key code: 1. Create a license information dataset. For details about the attributes of license information datasets, see section Format for license information datasets on page For details about license information dataset names, see section Naming for license information datasets on page Start Business Continuity Manager. 3. Display the Main Menu panel and select 2 Manage Licenses. Installing Business Continuity Manager 2-35

56 The Manage Licenses panel appears. 4. In the Manage Licenses panel, enter the key code in the Key Code field and press Enter. The key code is installed in the license information dataset as the license key. The YK9001I message is output if the license key is installed correctly. 5. Use the Manage Licenses panel to confirm that the licenses have been installed correctly. Tip: If you enter the key code for Tiered Storage Manager for Mainframe in the Manage Licenses panel, the license key for Tiered Storage Manager for Mainframe can also be installed. Notes when operating license keys Notes when operating license keys are as follows: You cannot use license keys obtained for Business Continuity Manager or earlier. Do not delete the license information dataset. Business Continuity Manager requires the license information dataset, and if it is deleted, Business Continuity Manager cannot be used. Do not use editors or similar applications to edit the license information dataset. Doing so may result in Business Continuity Manager becoming inoperable. If the specified license key is invalid, all or part of Business Continuity Manager will not be available. Make sure that you enter the correct license key. If an I/O error occurs in the license dataset, it is assumed that no license key exists. If you use the YKSETENV command to set or change the license information dataset name while Business Continuity Manager is running, CLI commands that are being executed will be executed using the previously set value. The set or updated license information dataset name will take effect once the YKLOAD command is executed. Hyphens cannot be used for the license key dataset name. Temporary license keys and emergency license keys that exceed a license period of 17 September 2042 cannot be installed. Format for license information datasets License information datasets have the following format: Dataset format: sequential datasets in the fixed-length record format Record size: 80 bytes Block size: multiple of 80 bytes Required access permissions: 2-36 Installing Business Continuity Manager

57 User installing the license key: WRITE permission Users other than the above that operate Business Continuity Manager: READ permission The following job is a sample JCL that allocates license information datasets. Change the dataset prefix (%PREFIX) and VOLSER (%VSN) according to the installation environment. //ALLOC JOB job info // SET PFX=%PREFIX Data set prefix1 // SET VSN=%VSN VOLSER //BR14 EXEC PGM=IEFBR14 //LICENSE DD DSN=&PFX..CCENTRAL.LICENSE, // UNIT=SYSDA,VOL=SER=&VSN, // SPACE=(TRK,(15)), // DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120), // DISP=(,CATLG,DELETE) Naming for license information datasets License information dataset names are specified and formatted as follows: prefix1.prefix2.ccentral.license A prefix of the license information dataset consists of prefix1 and prefix2. The length of each prefix is from 1 to 8 characters. You can select one of the following two prefix specification methods: Specify a value for the Business Continuity Manager environment variable (YKLCNSE and YKLCNS2) with the YKSETENV command. Specify a value for the system symbol &YKLCNSE and &YKLCNS2 in the IEASYMxx parmlib member. The following lists the priority for specified values, in descending order: 1. value-specified-by-the-yksetenv-command 2. value-specified-for-the-ieasymxx-parmlib-member 3. default-value (HITACHI) The method for specifying a value in the IEASYMxx parmlib member requires a re-ipl of the system. If a re-ipl cannot be executed because the system is running, use the YKSETENV command to specify a value. Note: If you use the YKSETENV command to set Business Continuity Manager environment variables, perform the procedure described in section Settings for using CLI commands in TSO/E environments on page Using the YKSETENV command Execute the YKSETENV command to set the Business Continuity Manager environment variables (YKLCNSE and YKLCNS2). For details about the format Installing Business Continuity Manager 2-37

58 for the YKSETENV command, see section YKSETENV command format on page The following example names the license information dataset HTC1.BCM.CCENTRAL.LICENSE: START YKSETENV,PARM='YKLCNSE=HTC1' START YKSETENV,PARM='YKLCNS2=BCM' If YKLCNSE is omitted, the value of the &YKLCNSE system symbol is used. If YKLCNS2 is omitted, the value of the &YKLCNS2 system symbol is used. The YKLCNS2 value becomes valid when a value is specified in either YKLCNSE or &YKLCNSE. Note: A re-ipl will invalidate the Business Continuity Manager environment variables registered with the YKSETENV command, that is, they return to the default or the value of the system symbol &YKLCNSE and &YKLCNS2. We recommend that you perform the either of the following settings for the next re-ipl: Add the YKSETENV command to the COMMNDxx parmlib member to set the Business Continuity Manager environment variables again automatically by re-ipl. Define the prefix value in the system symbol &YKLCNSE and &YKLCNS2 of the IEASYMxx parmlib member, and use this prefix value, which will be registered at the next IPL. Caution: The environment variables YKLCNSE and YKLCNS2 are shared by Business Continuity Manager and Tiered Storage Manager for Mainframe. Therefore, you need to be careful when setting the environment variables YKLCNSE and YKLCNS2 in an environment in which Tiered Storage Manager for Mainframe is installed. For details, see Notes on setting environment variables or system symbols when a related product is installed on page Defining a system symbol in the IEASYMxx parmlib member Define the system symbol &YKLCNSE and &YKLCNS2 for the IEASYMxx parmlib member. After the definition, enable the setting by re-ipl of the host. The following example names the license information dataset HTC1.BCM.CCENTRAL.LICENSE: SYMDEF(&YKLCNSE='HTC1') SYMDEF(&YKLCNS2='BCM') If &YKLCNSE is omitted, HITACHI is assumed. If &YKLCNS2 is omitted, only &YKLCNSE is used. &YKLCNS2 is valid only when &YKLCNSE has been specified. Caution: The system symbols &YKLCNSE and &YKLCNS2 are shared by Business Continuity Manager and Tiered Storage Manager for Mainframe. Therefore, you need to be careful when setting the system symbols &YKLCNSE 2-38 Installing Business Continuity Manager

59 and &YKLCNS2 in an environment in which Tiered Storage Manager for Mainframe is installed. For details, see Notes on setting environment variables or system symbols when a related product is installed on page The following table shows the relationship between the prefix of the license information dataset name and the specification status for the YKSETENV command or IEASYMxx parmlib member: YKSETENV command IEASYMxx parmlib member YKLCNSE YKLCNS2 &YKLCNSE &YKLCNS2 Prefix Y Y Y Y YKLCNSE.YKLCNS2 Y Y Y -- YKLCNSE.YKLCNS2 Y Y -- Y YKLCNSE.YKLCNS2 Y -- Y Y YKLCNSE.&YKLCNS2 -- Y Y Y &YKLCNSE.YKLCNS2 Y Y YKLCNSE.YKLCNS2 Y -- Y -- YKLCNSE Y Y YKLCNSE -- Y Y -- &YKLCNSE.YKLCNS2 -- Y -- Y HITACHI Y Y &YKLCNSE.&YKLCNS2 Y YKLCNSE -- Y HITACHI Y -- &YKLCNSE Y HITACHI HITACHI Legend: Y: Specified --: Not specified Verification procedure following installation and setup Check whether the installation and environment settings are completed If any tasks do not complete when Business Continuity Manager installation and setup of Business Continuity Manager concludes, Business Continuity Manager cannot be used. You can use either of the following methods to check whether all installation and setup processes have completed properly: Check the execution result of the YKINSCHK command. Installing Business Continuity Manager 2-39

60 Check the information displayed in the Installation Verification Summary panel. If some installation or setup tasks have not completed, follow the provided instructions to complete them. The following JCL execution example outputs the execution result of the YKINSCHK command to dd-name SYSTSPRT. If the job terminates with a return code other than 0, check the execution result that is output to SYSTSPRT. //YKINSCHK JOB //IEFPROC EXEC PGM=IKJEFT01,TIME=1440,REGION=4096K //SYSTSPRT DD SYSOUT=* //SYSABEND DD SYSOUT=* //STEPLIB DD DISP=SHR,DSN=HDSYK.Vnnnnnn.HDSYLNKT //SYSTSIN DD * YKINSCHK /* // For more information about the YKINSCHK command and the items output to the Installation Verification Summary panel, see the Hitachi Business Continuity Manager Reference Guide. Checking the access permissions when the extended access control function is installed When the extended access control function is installed, operations to the copy groups and the execution of a specific command cannot be performed unless the READ permissions of the RACF FACILITY class for the profiles are set. Use the sample script (HDSRFEPR) to check which profiles of the READ permissions are set. For details about the sample scripts (HDSRFEPR), see HDSRFEPR (viewing access permissions for the extended access control function) on page B-2. Upgrading Business Continuity Manager This section explains how to upgrade Business Continuity Manager. For notes on performing an upgrade installation, see the Appendix C, Notes on upgrading Business Continuity Manager on page C-1. When multiple versions of Business Continuity Manager exist on a system, you must check the items in Appendix D, Notes when multiple versions of Business Continuity Manager exist on page D-1 before starting the upgrade process Installing Business Continuity Manager

61 What to check before upgrading Checking licenses For Business Continuity Manager 5.5 or later, you cannot use license keys obtained for Business Continuity Manager 5.3 or earlier. You must obtain a license key for Business Continuity Manager version 5.5 or later. Checking environment variables The following table lists the Business Continuity Manager environment variables that are used when you perform an upgrade installation. Check the settings for these environment variables before you upgrade. Table 2-15 Business Continuity Manager environment variables to be checked before upgrading Parameter name YKCMDIF YKLCNSE YKLCNS2 LOGPUT SYSLOG Host ID Description Prefix of the license information dataset Business Continuity Manager log output method Whether CLI command-execution logs are to be output to SYSLOG or the console When the Business Continuity Manager version before upgrading is 5.1 or later, you can use the YKDSPENV command to check the values of the Business Continuity Manager environment variables. For details about the YKDSPENV command, see section YKDSPENV command format on page The following table lists the system symbols that are used when you perform an upgrade installation. Check the settings for these system symbols before you upgrade. Table 2-16 System symbols to be checked before upgrading (Business Continuity Manager environment variables) System symbol name &YKCMDIF &YKLCNSE &YKLCNS2 &YKLOGPT &YKSYSLG Host ID Description Prefix of the license information dataset Business Continuity Manager log output method Whether CLI command-execution logs are to be output to SYSLOG or the console Installing Business Continuity Manager 2-41

62 Checking the user SVC number Check the user SVC number because you must assign the same number after upgrading. The method of checking the user SVC number varies depending on whether the user SVC was registered with the YKSETENV command or the IEASVCxx parmlib member. When the user SVC was registered by using the YKSETENV command Check the value (user SVC number) specified in the YKALCSVC command parameter because you will use this value during an upgrade installation. When the user SVC was registered by using the IEASVCxx parmlib member Check the value set for the system symbol in the following table. Table 2-17 System symbol to be checked before upgrading (user SVC number) System symbol name &YKSVCNO Description SVC number to be assigned to the user SVC Backing up datasets Backing up configuration files Acquire backups of the configuration files below. Copy group definition file (prefix.grp.copy-group-id) Disk configuration definition file (prefix.dsk.snnnnnn.dad-id) Route list definition file (prefix.route.route-list-id) Command device definition file (prefix.cdev.dad-id) Path set definition file (prefix.path.path-set-id) If you change the dataset name when backing up the configuration files, make sure that you change the prefix only. The configuration files contain the copy group ID, device address domain ID (DAD ID), route list ID, and path set ID. Therefore, if you change the dataset name, the consistency between the files is lost, and then Business Continuity Manager might become inoperable. For details about configuration files, see the Hitachi Business Continuity Manager Reference Guide. Backing up the program before migration Before migration, acquire a backup of the dataset where Business Continuity Manager will be installed Installing Business Continuity Manager

63 Pre-upgrade procedure Deleting the user SVC If the version of the user SVC which is in effect in the current system is older than the version required after upgrading Business Continuity Manager, you must delete the user SVC before you install the new version of Business Continuity Manager. To check the version of the user SVC which is in effect in the current system, use the YKINSCHK command. If the user SVC was registered by using the YKALCSVC command, you can use the YKALCSVC command to delete the user SVC. If the user SVC was registered by using the IEASVCxx parmlib member, you cannot use the YKALCSVC command to delete the user SVC. In this case, perform the procedure below. To delete a user SVC that was registered by using the IEASVCxx parmlib member: 1. Disable (comment out) the SYMDEF statement containing the &YKSVCNO system symbol in the IEASYMxx parmlib member. /* SYMDEF(&YKSVCNO='SVC-number') */ 2. Disable (comment out) the SVCPARM statement containing the JYUASVC module in the IEASYMxx parmlib member. /* SVCPARM SVC-number,REPLACE,TYPE(3),EPNAME(JYUASVC),APF(NO),NPRMPT(NO),AR(NO) */ 3. Perform re-ipl with the CLPA parameter specified. For details on steps 1 and 2, see the IBM manual MVS Initialization and Tuning Reference. Caution: Business Continuity Manager, Tiered Storage Manager for Mainframe, and MAR share a user SVC. Therefore, if Tiered Storage Manager for Mainframe or MAR is installed on the system, make sure that the program is not running before deleting the user SVC. Removing the concatenation of the cataloged procedures library Remove the dataset concatenation of the following library: IEFPDSI dd name Library name Cataloged procedures library HDSYPRCT If you copied the HDSYPRCT library members to a user PROCLIB, delete the copied members. Installing Business Continuity Manager 2-43

64 Removing the concatenation of the REXX Exec library and the libraries used by ISPF interface Remove the dataset concatenation of the following libraries: dd name Library name SYSEXEC ISPPLIB ISPMLIB ISPTLIB REXX Exec library Panel library HDSYPNLT Message library HDSYMSGT Table library HDSYTABT In an environment in which the DBCS functionality is used, remove dataset concatenation from the following libraries: dd name Library name ISPPALT ISPMALT Panel library HDSYPNLT Message library HDSYMSGT Removing the concatenation of the load library Remove the load library for LINKLIB (HDSYLNKT) concatenated to LNKLST. Also, remove the load library for LPALIB (HDSYLPAT) concatenated to LPALST. Upgrading Business Continuity Manager Install the post-migration Business Continuity Manager as described in section Overview of installation on page 2-2. If the version of the user SVC which is in effect in the current system satisfies the conditions placed on the version required by Business Continuity Manager, you do not need to perform Registering a user SVC on page For versions of user SVC that are required by Business Continuity Manager, see User SVC versions required by Business Continuity Manager on page If the pre-migration licenses can be used and no licenses need to be added, you do not need to perform the procedure described in section Registering a license on page What to check after upgrading After upgrading the post-migration Business Continuity Manager, make sure that the post-upgrade settings are the same as those checked in section What to check before upgrading on page Installing Business Continuity Manager

65 Notes on system setup when a related product is installed This section provides notes on registering a user SVC and setting environment variables and system symbols when installing Business Continuity Manager or MAR in an environment in which Tiered Storage Manager for Mainframe is installed. Notes on user SVC registration when a related product is installed Business Continuity Manager, Tiered Storage Manager for Mainframe, and MAR share a user SVC. Therefore, you need to compare the version of the user SVC that is registered by using Tiered Storage Manager for Mainframe or MAR and currently in effect in the system and the version of the user SVC that is required for Business Continuity Manager, and then use the newer version of user SVC. To check the version of the user SVC that is currently in effect in the system, use the KTINSCHK command of Tiered Storage Manager for Mainframe, or the RSINSCHK command of MAR. If the user SVC version you checked does not satisfy the conditions placed on the required version (the version is older than the required version): Delete the user SVC by using Tiered Storage Manager for Mainframe or MAR, and register a user SVC by using Business Continuity Manager. If the user SVC version you checked satisfy the conditions placed on the required version: You can use the user SVC currently in effect in the system without change. Tip: For details about the user SVC versions required for Business Continuity Manager, see User SVC versions required by Business Continuity Manager on page For details about the KTINSCHK command and how to delete a user SVC by using Tiered Storage Manager for Mainframe, see the Tiered Storage Manager for Mainframe User Guide. For details about the RSINSCHK command and deleting the user SVC in MAR, see the Mainframe Analytics Recorder User Guide. This procedure is available when you perform a new installation of Business Continuity Manager. If you upgrade Business Continuity Manager, see Deleting the user SVC on page 2-43 in Pre-upgrade procedure on page Notes on setting environment variables or system symbols when a related product is installed Business Continuity Manager, Tiered Storage Manager for Mainframe, and MAR use the same environment variables and system symbols. Therefore, if Installing Business Continuity Manager 2-45

66 Tiered Storage Manager for Mainframe or MAR is running on the system, we recommend that you do not change the environment setting values (environment variables or the values set for system symbols) that are currently valid in the system. In particular, if you change the prefix for the license information dataset, you need to re-register the license for Tiered Storage Manager for Mainframe because the license information dataset is shared by Business Continuity Manager and Tiered Storage Manager for Mainframe. Keep this fully in mind when you need to change an environment setting value. Tip: The following describes how to check the environment setting values that are currently valid in the system. If Business Continuity Manager has been installed (upgrade): Check the environment setting values you obtained during the check before upgrading. For details, see Checking environment variables on page 2-41 in What to check before upgrading on page If Business Continuity Manager has not been installed (new installation): Use the KTDSPENV command of Tiered Storage Manager for Mainframe or the RSDSPENV command of MAR to check the values. For details on the KTDSPENV command, see the Tiered Storage Manager for Mainframe User Guide.For details on the RSDSPENV command, see the Mainframe Analytics Recorder User Guide. Notes on specifying a prefix when a related product is installed If you want to install and use Business Continuity Manager in the same system as Tiered Storage Manager for Mainframe or MAR, specify a character string different from the prefix of Tiered Storage Manager for Mainframe or MAR as the prefix of the configuration files. If the same prefix is used, the product might operate abnormally. User SVC versions required by Business Continuity Manager The following table lists the versions of user SVCs that are required in each version of Business Continuity Manager. Table 2-18 User SVC versions required by Business Continuity Manager Version of Business Continuity Manager User SVC version required or later or later or later or later or later or later 2-46 Installing Business Continuity Manager

67 Version of Business Continuity Manager User SVC version required or later or later or later or later or later or later or later to or later or later to or later or later to or later Installing Business Continuity Manager 2-47

68 2-48 Installing Business Continuity Manager

69 3 Setting up the environment when linking with Replication Manager This chapter explains the environment setup when linking with Replication Manager. It also explains how to set up port numbers, security, and IBM HTTP Server, which are all required to link to Replication Manager. In addition, this chapter explains how to create initialization parameters and a cataloged procedure for startup. Overview of environment settings Creating configuration file datasets Setting the TCP/IP port number Setting up the security for Business Continuity Manager agents Setting up IBM HTTP Server Creating initialization parameters Creating a cataloged procedure for startup for the Business Continuity Manager agents Setting up the environment when linking with Replication Manager 3-1

70 Overview of environment settings This section explains how to configure the environment settings that are necessary for linking to Replication Manager. HTTPS connections can be established between Replication Manager and the Business Continuity Manager agent. For details on how to establish HTTPS connections, see Setting up HTTPS connections on page In addition, for details on how to set up IBM HTTP Server for establishing HTTPS connections, see the product information on the IBM WebSphere Application Server Information Center. Configuring the environment settings without using the Remote DKC Control Function (before Business Continuity Manager is installed) The following figure shows the general procedure for configuring the environment settings starting from before Business Continuity Manager is installed, without using the Remote DKC Control Function. 3-2 Setting up the environment when linking with Replication Manager

71 Figure 3-1 Configuring the environment settings without using the Remote DKC Control Function (before Business Continuity Manager is installed) To configure the environment settings without using the Remote DKC Control Function: 1. Set up the storage system. For details, see the Hitachi Business Continuity Manager User Guide. 2. Create configuration file datasets. Create datasets for the following configuration files: Disk configuration definition file Copy group definition file For details, see section Creating configuration file datasets on page Install Business Continuity Manager. For details, see Chapter 2, Installing Business Continuity Manager on page 2-1. Setting up the environment when linking with Replication Manager 3-3

72 4. Configure the environment settings for the Business Continuity Manager agent. For details, see the following sections: Setting the TCP/IP port number on page 3-11 Setting up the security for Business Continuity Manager agents on page 3-12 Setting up IBM HTTP Server on page 3-13 Creating initialization parameters on page 3-19 Creating a cataloged procedure for startup for the Business Continuity Manager agents on page Start IBM HTTP Server. 6. Start the Business Continuity Manager agent. For details, see the chapter about linking the Business Continuity Manager agent to Replication Manager in the Hitachi Business Continuity Manager User Guide. 7. Configure the Replication Manager initialization settings. For details, see the Replication Manager User Guide. Configuring the environment settings using the Remote DKC Control Function (before Business Continuity Manager is installed) The following figure shows the general procedure for configuring the environment settings starting from before installation of Business Continuity Manager, using the Remote DKC Control Function. 3-4 Setting up the environment when linking with Replication Manager

73 Figure 3-2 Configuring the environment settings using the Remote DKC Control Function (before Business Continuity Manager is installed) To configure the environment settings by using the Remote DKC Control Function: 1. Set up the storage system. For details, see the Hitachi Business Continuity Manager User Guide. 2. Install Business Continuity Manager. For details, see Chapter 2, Installing Business Continuity Manager on page Perform a Local Scan. Setting up the environment when linking with Replication Manager 3-5

74 Perform a Local Scan to create the disk configuration definition file needed for setting the route list definitions. For details, see the description about using a Local Scan to acquire storage system information in the Hitachi Business Continuity Manager User Guide. 4. Configure the environment settings for the Remote DKC Control Function. Configure the following settings: Route list definitions Command device registrations For details, see the Hitachi Business Continuity Manager User Guide. 5. Create configuration file datasets. Create datasets for the following configuration files: Disk configuration definition file Copy group definition file For details, see section Creating configuration file datasets on page Configure the environment settings for the Business Continuity Manager agent. For details, see the following sections: Setting the TCP/IP port number on page 3-11 Setting up the security for Business Continuity Manager agents on page 3-12 Setting up IBM HTTP Server on page 3-13 Creating initialization parameters on page 3-19 Creating a cataloged procedure for startup for the Business Continuity Manager agents on page Start IBM HTTP Server. 8. Start the Business Continuity Manager agent. For details, see the chapter about linking the Business Continuity Manager agent with Replication Manager in the Hitachi Business Continuity Manager User Guide. 9. Configure the Replication Manager initialization settings. For details, see the Replication Manager User Guide. Configuring the environment settings in an existing environment (with Business Continuity Manager installed) The following figure shows the general procedure for configuring the environment settings in an existing environment with Business Continuity Manager installed (that is, with the storage system configured, and with the environment set up for using the Remote DKC Control Function). 3-6 Setting up the environment when linking with Replication Manager

75 Figure 3-3 Configuring the environment settings in an existing environment (with Business Continuity Manager installed) To configure the environment settings in an existing environment: 1. Upgrade Business Continuity Manager. For details, see Upgrading Business Continuity Manager on page Create configuration file datasets. These datasets are needed to perform a device scan and set copy group definitions in Replication Manager for the first time. Create datasets for the following configuration files: Disk configuration definition file Copy group definition file For details, see section Creating configuration file datasets on page Configure the environment settings for the Business Continuity Manager agent. For details, see the following sections: Setting the TCP/IP port number on page 3-11 Setting up the security for Business Continuity Manager agents on page 3-12 Setting up the environment when linking with Replication Manager 3-7

76 Setting up IBM HTTP Server on page 3-13 Creating initialization parameters on page 3-19 Creating a cataloged procedure for startup for the Business Continuity Manager agents on page Start IBM HTTP Server. 5. Start the Business Continuity Manager agent. For details, see the chapter about linking the Business Continuity Manager agent with Replication Manager in the Hitachi Business Continuity Manager User Guide. 6. Configure the Replication Manager initialization settings. For details, see the Replication Manager User Guide. Configuring the environment settings to allow only monitoring of copy groups The following figure shows the general procedure for configuring the environment settings in an existing environment to allow only monitoring of copy groups, without allowing copy groups to be defined or copy group operations to be performed. Figure 3-4 Configuring the environment settings to allow only monitoring of copy groups To configure the environment settings to allow only monitoring of copy groups: 1. Configure the environment settings for the Business Continuity Manager agent. For details, see the following sections: 3-8 Setting up the environment when linking with Replication Manager

77 Setting the TCP/IP port number on page 3-11 Setting up the security for Business Continuity Manager agents on page 3-12 Setting up IBM HTTP Server on page 3-13 Creating initialization parameters on page 3-19 Creating a cataloged procedure for startup for the Business Continuity Manager agents on page Start IBM HTTP Server. 3. Start the Business Continuity Manager agent. For details, see the chapter about linking the Business Continuity Manager agent with Replication Manager in the Hitachi Business Continuity Manager User Guide. 4. Configure the Replication Manager initialization settings. For details, see the Replication Manager User Guide. Configuring the environment settings for monitoring PPRC copy pairs To monitor PPRC copy pairs from Replication Manager, you must create a PPRC copy group definition file with Business Continuity Manager before you configure the environment settings for the Business Continuity Manager agent. For details, see the description about generating PPRC copy pair copy group definitions in the Hitachi Business Continuity Manager User Guide. Creating configuration file datasets Before doing anything else, you must first create datasets for the following configuration files, which are created in Replication Manager. You must then catalog the created datasets. Disk configuration definition file Copy group definition file The following indicates the time at which each configuration file is created. Disk configuration definition file: When a device is scanned (for example, during a Local Scan, NG Scan, or Remote Scan) Copy group definition file: When a copy group is defined Configuration file dataset names The following lists the naming convention for each dataset: Disk configuration definition file name: prefix.dsk.snnnnnn.dad-id Copy group definition file name: prefix.grp.copy-group-id Setting up the environment when linking with Replication Manager 3-9

78 The values that can be specified for each variable are explained below. The values specified for prefix and DAD-ID must be the same as the value specified for the Business Continuity Manager agent initialization parameter PREFIX. prefix: Prefix of the configuration file Specify a string of 25 characters or fewer that consists of one or more parts, joined by periods (.). Only uppercase alphabetic characters and numeric characters can be used. Note that the string or each substring must begin with an uppercase alphabetic character, and consist of 1 to 8 characters. copy-group-id Specify a string or multiple substrings joined together by periods. Uppercase alphabetic characters, numeric characters, and special characters ($, #, can be used. Note that the string or each substring must begin with an uppercase alphabetic characters or special character, and consist of 1 to 8 characters. Maximum specifiable length = 44 - (5 + prefix-length) nnnnn: Serial number of the scanned storage system DAD-ID: Device address domain ID of the scanned storage system The following values can be specified: When creating for a Local Scan: Device address domain ID of the local site When creating for an NG Scan: Non Gen'ed Device address domain ID When creating for a Remote Scan: Device address domain ID of the remote site Specify a string or multiple substrings joined together by periods. Uppercase alphabetic characters, numeric characters, and special characters ($, #, can be used. Note that the string or each substring must begin with an uppercase alphabetic characters or special character, and consist of 1 to 8 characters. Maximum specifiable length = 44 - (13 + prefix-length) When a disk configuration definition file or a copy group definition file is updated from Replication Manager, a temporary file is created. After the file is successfully updated, the temporary file is deleted. Do not create a dataset with the same name as that of a temporary file. The following lists the file naming conventions for the temporary files: Name of the temporary file for the disk configuration definition file: prefix.tmp.snnnnnn.dad-id Name of the temporary file for the copy group definition file: prefix.tmp.copy-group-id 3-10 Setting up the environment when linking with Replication Manager

79 Dataset format and required disk capacity for the configuration file For details about the dataset format and the required disk capacity, see the descriptions for the configuration file in the Hitachi Business Continuity Manager Reference Guide. Note: When you estimate the required disk capacity, allow for no less than three times the disk capacity required for each dataset, to provide enough disk capacity for backup files and temporary files. Setting the TCP/IP port number Before performing this procedure, you need to reserve a port number for communicating with Replication Manager. For a job that starts Business Continuity Manager agent, set the UNIX service's usage attributes (open a port for receiving). For details, see the IBM manual Communications Server: IP Configuration Reference. Set the port number in the TCP/IP environment settings file (PROFILE.TCPIP profile, the definition file related to server functions in the TCP/IP address space). In the PORT definition of the PROFILE.TCPIP profile, specify the member name or identification name of the Business Continuity Manager agent start job. For details about the identification name, see the chapter that describes Business Continuity Manager agent startup in the Hitachi Business Continuity Manager User Guide. For the port number to be used by the YKAGENT job, you cannot specify a number that is already being used by another job. Specify a port number that is not being used in the system. Example of specifying the port number The following specification sets the port number as 24042: TCP YKAGENT ;YKAGENT START NAME Note: The Business Continuity Manager agent requires 2 sockets of IBM Communications Server (OS standard equipment). Make sure that the total number of sockets does not exceed the maximum number of sockets that IBM Communications Server can provide, keeping in mind the number of sockets required for other services that IBM Communications Server handles. For details about the maximum number of sockets that IBM Communications Server can provide, see the IBM manual Communications Server IP Configuration Guide. Setting up the environment when linking with Replication Manager 3-11

80 Setting up the security for Business Continuity Manager agents This section describes how to set the security. Setting the dataset security When a Business Continuity Manager agent is linked to Replication Manager, the Business Continuity Manager agent job references Business Continuity Manager's configuration files. Therefore, be sure to grant the Business Continuity Manager agent job READ permission for the configuration files that are accessed by the Business Continuity Manager agent job. The names of the configuration files to which READ permission is to be granted are the following datasets, which have their prefixes specified in Business Continuity Manager's Set Defaults panel. Disk configuration definition file Copy group definition file Route list definition file Command device definition file To create or update the copy group definition from Replication Manager, grant WRITE permission for the datasets listed below to the Business Continuity Manager agent job. For details on dataset names, see Creating configuration file datasets on page 3-9. Disk configuration definition file Copy group definition file Temporary disk configuration definition file Temporary copy group definition file Setting up the Resource Access Control Facility (RACF) when linking with Replication Manager To enable Business Continuity Manager agent communications, set an environment for the security program (RACF). To enable use of UNIX services, use the RACF command from TSO/E to define the management user and management group IDs held by the OMVS segment in the RACF STARTED class of the Business Continuity Manager agent cataloged procedure for startup. The following is an example of using the TSO/E command with the STARTED class: ->SETROPTS GENERIC(STARTED) ->RDEFINE STARTED YKAGENT.* STDATA(USER(user-ID) GROUP(group-ID)) ->SETROPTS RACLIST(STARTED) REFRESH 3-12 Setting up the environment when linking with Replication Manager

81 To start Business Continuity Manager agent, you need to define one of the following profiles in the RACF FACILITY class, and then grant the view permission for the defined profile to the administrator user ID: The profiles for which view permissions are granted to the Business Continuity Manager agent vary depending on whether the Business Continuity Manager agent is started in monitor mode or in edit mode. For details about these startup modes, see Details of initialization parameters on page If the Business Continuity Manager agent is started in monitor mode, grant view permissions for the following profile: STGADMIN.YKA.BCM.YKQUERY profile If the Business Continuity Manager agent is started in edit mode, grant view permissions for the following profile: STGADMIN.YKA.BCM.COMMANDS profile Following is an example of using the TSO/E command with the FACILITY class: ->SETROPTS CLASSACT(FACILITY) ->RDEFINE FACILITY STGADMIN.YKA.BCM.YKQUERY UACC(NONE) ->PERMIT STGADMIN.YKA.BCM.YKQUERY CLASS(FACILITY) ID(user-ID) ACCESS(READ) For details, see Setting security for the environment configuration commands on page 2-18 in section Setting the security on page Setting up IBM HTTP Server This section explains how to set up IBM HTTP Server in order to establish IPv6 connections or HTTPS communication, and it also explains how to collect logs. Settings for connecting via IPv6 When Replication Manager is connected to the Business Continuity Manager agent via IPv6, IBM HTTP Server is required to act as a reverse proxy server. When the reverse proxy server receives a request from Replication Manager via IPv6, it changes the request to IPv4 format and then provides the request to the Business Continuity Manager agent, which acts as the origin server. The following shows a configuration example of when Replication Manager connects to the Business Continuity Manager agent via IPv6. Setting up the environment when linking with Replication Manager 3-13

82 Figure 3-5 Example configuration using IPv6 to connect Replication Manager to the Business Continuity Manager agent To set up IBM HTTP Server to run as a reverse proxy server, specify the settings described in the following table for the httpd.conf file. Table 3-1 Settings to be specified in the httpd.conf file for IPv6 connections Directive to be specified CacheDisable KeepAlive Listen LoadModule Description of directive, and values to be specified Specify this directive so that the cache function for requests directed to the Business Continuity Manager agent is disabled. Specify this directive to disable the KeepAlive function. Specify a standby port in IPv6 as shown below. The port number can be changed: Listen [::]:80 Add the following modules to the list so that the reverse proxy function will be enabled: proxy_module modules/mod_proxy.so proxy_http_module modules/mod_proxy_http.so 3-14 Setting up the environment when linking with Replication Manager

83 Directive to be specified ProxyPass and ProxyPassReverse Timeout Description of directive, and values to be specified Specify the following options to set up Business Continuity Manager agent to act as the origin server for Replication Manager: The host name or IPv4 address of the host that is running Business Continuity Manager agent The port number that was specified for the PORT parameter when initially setting up Business Continuity Manager agent ProxyPass / ProxyPassReverse / address:port-number/ This directive is used to specify how long to wait before issuing a timeout. Specify a value greater than the timeout values of Replication Manager (bcmif.sockettimeout). Setting up HTTPS connections HTTPS (HTTP over SSL) connections can be established between Replication Manager and the Business Continuity Manager agent to improve security. To establish HTTPS connections between Replication Manager and the Business Continuity Manager agent, IBM HTTP Server is required as a reverse proxy server. A reverse proxy server uses HTTPS to receive requests from Replication Manager, and then uses HTTP to send those requests to the Business Continuity Manager agent, which is the origin server. In addition, basic access authentication can be used to authorize Replication Manager. A configuration example for HTTPS connections between Replication Manager and IBM HTTP Server is shown below: Setting up the environment when linking with Replication Manager 3-15

84 Figure 3-6 Configuration example for HTTPS connections between Replication Manager and IBM HTTP Server Use the IBM HTTP Server httpd.conf settings file to configure IBM HTTP Server. The following table describes authentication methods used between Replication Manager and IBM HTTP Server. Table 3-2 Authentication methods used between Replication Manager and IBM HTTP Server Authenticating Being authenticated Authentication method Replication Manager IBM HTTP Server Server certificate (SSL) IBM HTTP Server Replication Manager Basic access authentication (HTTP) Note that when HTTP is used to connect Replication Manager and IBM HTTP Server, Replication Manager cannot send the information necessary for performing basic access authentication. An overview of the setup procedure for establishing HTTPS connections is shown in the figure below. All of the steps indicated in the figure below must be performed on all of the sites Setting up the environment when linking with Replication Manager

85 Figure 3-7 Overview of the setup procedure for establishing HTTPS connections The procedure to establish HTTPS connections between Replication Manager and IBM HTTP Server is described below. The number for each step in Figure 3-7 Overview of the setup procedure for establishing HTTPS connections on page 3-17 corresponds to the number in the procedure directly below that. 1. To run IBM HTTP Server as a reverse proxy server, specify the settings described in Table 3-3 Required settings for the httpd.conf file to set up a reverse proxy server on page 3-17 in the httpd.conf file. Table 3-3 Required settings for the httpd.conf file to set up a reverse proxy server Directives CacheDisable Values Specify this directive to disable the cache function for requests directed to the Business Continuity Manager agent. Setting up the environment when linking with Replication Manager 3-17

86 Directives KeepAlive LoadModule Listen ProxyPass and ProxyPassReverse Timeout Values Specify this directive to disable the KeepAlive function. Add the following modules to the list: proxy_module modules/mod_proxy.so proxy_http_module modules/mod_proxy_http.so Specify a standby port for IBM HTTP Server. For example, to set up port number 443 for a standby port, specify the following: IPv4: Listen 443 IPv6: Listen [::]:443 Specify the following options to make the Business Continuity Manager agent the origin server for Replication Manager: The host name or IP address of the host on which the Business Continuity Manager agent is running The port number in the PORT parameter, which was specified when the Business Continuity Manager agent was initially set up ProxyPass / ProxyPassReverse / Specify how long to wait before issuing a time out. Specify a value greater than Replication Manager's timeout value (bcmif.sockettimeout). 2. Create a server certificate. 3. Enable SSL/TLS. 4. Enable basic access authentication. (a) Execute the htpasswd command to set up a user ID and password for authenticating Replication Manager. After executing the htpasswd command, a file that manages the user ID and password for basic access authentication of the Replication Manager will be created. The following is an execution example of the htpasswd command: htpasswd /usr/local/apache/.htaccess user-name (b) See Table 3-4 Required settings for the httpd.conf file to set up authentication on page 3-18 to edit the httpd.conf file. Table 3-4 Required settings for the httpd.conf file to set up authentication Directives AuthName AuthType Values Specify the realm that will be used for authentication. Specify the type of user authentication. Specify Basic Setting up the environment when linking with Replication Manager

87 Directives AuthUserFile Require Values Specify the location of the management file for the user ID and password created by the htpasswd command. Specify the users that are allowed access. 5. Restrict access to the TCP/IP port used by the Business Continuity Manager agent. IBM HTTP Server is the only program that can communicate with the Business Continuity Manager agent. 6. Import the IBM HTTP Server server certificate into the truststore (jssecacerts). 7. Set a protocol for communicating with IBM HTTP Server. For detailed procedures, see the following: For steps 1 to 4 (IBM HTTP Server settings) IBM HTTP Server for WebSphere Application Server product information available from the IBM WebSphere Application Server information center For step 5 (z/os settings) IBM manual Communications Server IP Configuration Reference For steps 6 and 7 (Hitachi Command Suite settings) Replication Manager Configuration Guide Collecting the trace log To collect error logs and access logs between Replication Manager and IBM HTTP Server, use the log function of IBM HTTP Server. To determine whether to collect logs of IBM HTTP Server, follow the instructions from the Web administrator. Note that, if you do not collect logs, it might be difficult to determine the cause of an access error. Creating initialization parameters This section describes how to create the initialization parameters for setting up the environment required to start the Business Continuity Manager agent. YKPRM00 is a member of the initialization parameter samples registered in the sample library during initialization. Adjust the parameters to fit your environment. Create a dataset to hold the initialization parameters by specifying the following attributes: LRECL: 80 BLKSIZE: Multiple of 80 RECFM: Fixed-length or blocked fixed-length record DSORG: Sequential or partitioned dataset Setting up the environment when linking with Replication Manager 3-19

88 How to use the SETINIT command This subsection explains the format of the SETINIT command, that sets the initialization parameters. For details about the symbols and syntax elements used in command explanations, see Appendix E, Conventions in syntax explanations on page E-1. 0SETINIT[ 1parameter]... Specify a SETINIT command and parameters in columns 1 through 71. Any information specified in a column after column 72 is ignored. You can specify more than one SETINIT command. You can specify different parameters for one SETINIT command, but cannot specify the same parameter more than once. If you specify the same parameters more than once for one SETINIT command, the last specified parameter is applied. To specify the same parameter more than once, use a separate SETINIT command. If a parameter that cannot be specified more than once in separate SETINIT commands is specified in that way, the last specified parameter is applied. For details about the specifiable parameters and whether they can be specified multiple times by using separate SETINIT commands, see section Details of initialization parameters on page Example of specifying the same parameter more than once for one SETINIT command: If you specify the same parameter more than once for one SETINIT command, the last specified parameter is applied. Do not specify parameters as shown in this example. In the following example, only DEVN(7500,750F) is applied, and DEVN(7300,730F) and DEVN(7400,740F) become invalid: SETINIT DEVN(7300,730F) DEVN(7400,740F) DEVN(7500,750F) Example of specifying the same parameter more than once for separate commands: If the parameter can be specified more than once for separate commands: All the specified parameters are applied. If you specify parameters as follows, DEVN(7300,730F), DEVN(7400,740F), and DEVN(7500,750F) are applied: SETINIT DEVN(7300,730F) 3-20 Setting up the environment when linking with Replication Manager

89 SETINIT DEVN(7400,740F) SETINIT DEVN(7500,750F) If the parameter cannot be specified more than once for separate commands: The last specified parameter is applied. If you specify parameters as follows, RECVWAITTIME(180) is applied: SETINIT RECVWAITTIME(65535) SETINIT RECVWAITTIME(180) Continuing to the next line To continue a parameter onto the next line, enter a continuation symbol at the end of the line. The following table shows the continuation symbols. Table 3-5 Continuation symbols Continuation symbol Hyphen (-) Plus sign (+) Continuation method The hyphen is removed, and the parameter is continued in the leftmost column of the next line, retaining any contiguous spaces. The plus sign is removed, and the parameter is continued on the next line, removing any contiguous spaces. Coding example for continuing parameters that contain contiguous spaces: SETINIT- PREFIX('USER01.V1','NY') If you continue to specify parameters by using a hyphen (-) as shown above, the command will be interpreted as follows: SETINIT PREFIX('USER01.V1','NY') Coding example for continuing parameters, removing contiguous spaces: SETINIT PREFIX('USER01.V1',+ 'NY') If you continue to specify parameters by using a plus sign (+) as shown above, the command will be interpreted as follows: Setting up the environment when linking with Replication Manager 3-21

90 SETINIT PREFIX('USER01.V1','NY') Entering comments Enclose a comment in /* and */. No comment can be entered inside a parameter. Example of a valid comment: /* COMMENT */ SETINIT PORT(24042) /* COMMENT */ Example of invalid comment: If you specify a comment as follows, the text /* ERROR COMMENT */ will be interpreted as a part of the parameter instead of being interpreted as a comment: SETINIT PREFIX(7300, + /* ERROR COMMENT */ 730F) Notes during creation of initialization parameters Do not specify an empty member as an initialization parameter when you start the Business Continuity Manager agent. Although empty members do not result in an error, information cannot be returned to Replication Manager. Details of initialization parameters Format This subsection explains details of initialization parameters. SETINIT [ 1PORT(port-number)] [ 1RECVWAITTIME(reception-wait-time)] [ 1HOSTNAME('host-identification-name')] [ 1PREFIX('prefix','local-site's-DAD-ID'[,'route-list-ID[,{route- label *}]'[,['local-site's-non-gen'ed-dad-id'][,'remote-site's-dad- ID']]])] [ 1DEVN(start-device-number,end-device-number)] [ 1LOGLEVEL(output-level)] [ 1AUDITLOG(SYSLOG)] 3-22 Setting up the environment when linking with Replication Manager

91 [ 1MODE(startup-mode)] [ 1LOCK(lock-mode)] Parameters PORT(port-number) ~ <numeric characters> (( )) <<24042>> Specifies the Business Continuity Manager agent port for TCP/IP communication with Replication Manager. You cannot specify a port number that is being used by another job. Specify a port number that is not being used in the system. RECVWAITTIME(reception-wait-time) ~ <numeric characters> (( )) <<180>> When TCP/IP communication with Replication Manager is performed, this parameter specifies the wait time (in seconds) from when a receive request is initiated to when data is received. A value of 0 means that the Business Continuity Manager agent is to wait for data indefinitely. HOSTNAME('host-identification-name') ~ <1 to 50 alphanumeric characters> <<value specified for the &SYSNAME system symbol>> Specify this parameter when Replication Manager needs to identify the Business Continuity Manager agent. When the Business Continuity Manager agent is running on more than one host, and a HOSTNAME (host identification name) value is duplicated in these hosts, Replication Manager cannot identify the host on which the target Business Continuity Manager agent is running. To ensure that Replication Manager can identify the host on which the Business Continuity Manager agent is running, specify a unique HOSTNAME value for each host. When this parameter is omitted, the value of the &SYSNAME system symbol is assumed. For details about the &SYSNAME system symbol, see the IBM manual MVS Initialization and Tuning Reference. When the Business Continuity Manager agent runs on more than one host and an &SYSNAME system symbol value is duplicated in these hosts, Replication Manager cannot distinguish between the hosts. When the &SYSNAME system symbol value is duplicated, make sure that HOSTNAME values are unique among the hosts. PREFIX('prefix','local-site's-DAD-ID'[,'route-list-ID[,{route-label *}'[, ['local-site's-non-gen'ed-dad-id'][,'remote-site's-dad-id']]]) To enable Replication Manager to manipulate the Business Continuity Manager agent, the prefix of the configuration files managed by Business Continuity Manager must be specified. You can specify multiple PREFIX parameters. Specify multiple PREFIX parameters when the storage information to be acquired is information registered in multiple configuration files that have different prefixes, in an environment where Replication Manager and the Business Continuity Manager agent are one-to-one. prefix ~ <PREFIX string consisting of 1 to 16 characters> Setting up the environment when linking with Replication Manager 3-23

92 Specifies the file name prefix of the Business Continuity Manager configuration files that are used by Replication Manager. Specify the value that was specified in Configuration File Prefix in Business Continuity Manager's Set Defaults panel when the configuration file was created. Replication Manager can use the disk configuration definition file and the copy group definition file with the prefix specified here. For details about the Set Defaults panel in Business Continuity Manager, see the Hitachi Business Continuity Manager Reference Guide. local-site's-dad-id ~ <DAD string consisting of 1 to 28 characters> Specifies the device address domain ID of the local site on which the Business Continuity Manager agent is operating. When monitoring PPRC copy pairs, specify the value that was specified in Device Address Domain, Primary or Device Address Domain, Secondary in the Scan Copy Pair Inside Storage System panel when the copy group definition file for PPRC copy pairs was created. For details about the Scan Copy Pair Inside Storage System panel in Business Continuity Manager, see the Hitachi Business Continuity Manager Reference Guide. If you specify multiple PREFIX parameters, we recommend that you use the same device address domain ID for all of the device address domain IDs on the local site. Note: Do not specify the local site's Non Gen'ed device address domain ID or the remote site's device address domain ID. route-list-id ~ <ROUTE string consisting of 1 to 8 characters> Specifies the route list ID for the Business Continuity Manager agent when the Remote DKC Control Function is used. You must specify a route list ID in order to use the Remote DKC Control Function. {route-label *} ~ <ROUTELABEL string consisting of 1 to 8 characters> If you specify a route label, command devices that have the specified route label are used. If you specify *, all command devices are used regardless of whether they have a route label. If you specify neither a route label nor *, command devices that have no route label are used. local-site's-non-gen'ed-dad-id ~ <DAD string consisting of from 1 to 28 characters> Specifies the Non Gen'ed device address domain ID used by the local site on which the Business Continuity Manager is operating. Specify an asterisk (*) in place of the local site's Non Gen'ed device address domain ID to omit it while specifying the following value (remote site's device address domain ID). Note also that to acquire information about Non Gen'ed volumes, you must specify the local site's Non Gen'ed device address domain ID Setting up the environment when linking with Replication Manager

93 Note: Do not specify the local site's device address domain ID or the remote site's device address domain ID. If you specify multiple PREFIX parameters, specify the same device address domain ID for all of the local site's Non Gen'ed device address domain IDs. remote-site's-dad-id ~ <DAD string consisting of from 1 to 28 characters...> Specifies the device address domain ID of the remote site on which the Business Continuity Manager agent performs Remote Scans. To specify multiple device address domain IDs, separate consecutive device address domain IDs with a colon (:), as shown in the following example: Example: DAD1:DAD2:... Note: Note also that to acquire information about volumes at the remote site, you must specify the remote site's device address domain ID. Do not specify the local site's device address domain ID or the local site's Non Gen'ed device address domain ID. If a site is being used as a local site by another Business Continuity Manager agent, you cannot specify it for use as a remote site. Note: Notes about specifying the PREFIX parameter Do not specify a nonexistent prefix or device address domain ID in the PREFIX parameter. Even though specifying a nonexistent prefix or device address domain ID does not result in an error during Business Continuity Manager agent startup, an error will occur during a Replication Manager request. In the PREFIX parameter, do not specify any value other than the prefix of the configuration file. If multiple datasets correspond to the specified prefix (such as the SYS1 prefix), Business Continuity Manager agent processing might slow down. If you specify the same prefix multiple times for MODE(MONITOR), the monitoring processing of Replication Manager might slow down. If you specify the same prefix multiple times for MODE(EDIT), an error will occur and you will be unable to start the Business Continuity Manager agent. If you specify multiple PREFIX parameters, it will take time to switch the configuration files for each prefix during a Replication Manager request. Therefore, if there are many configuration files, we recommend that you aggregate prefixes in the configuration files so that there is only one PREFIX parameter, to shorten the access time for a request from or a response to Replication Manager. If you want to modify a configuration file that has a prefix specified in the PREFIX parameter, make sure you use the ISPF panel or Replication Setting up the environment when linking with Replication Manager 3-25

94 Manager. If you use another method, information might not be displayed on Replication Manager, or an error might occur. The access time for a Replication Manager request or response becomes longer according to the number of copy pairs defined in the copy group definition file that has the specified prefix. Therefore, specify the monitoring interval of Replication Manager to fit the environment (the host capability corresponding to the number of copy pairs). DEVN(start-device-number,end-device-number) ~ <4 hexadecimal characters> Specifies a range of devices from which to collect information when filtering the host volume information to be passed to Replication Manager. Specify the start-device-number and end-device-number in the ascending order of hexadecimal characters. If the DEVN parameter has not been specified before, DEVN(0000,FFFF) is assumed. Note: Notes about specifying the DEVN parameter To reduce the access time required for requests and replies from Replication Manager, we recommend that you specify a range of target devices from which information is collected. When you specify more than one DEVN parameter, even if there are duplicate devices, they are not eliminated, so make sure you avoid specifying such duplications. LOGLEVEL(output-level) ~ <numeric character> ((0-3)) <<2>> Specifies the log output level Logs are not output. If 0 is specified, it is difficult to determine the cause of a communication failure or an error that occurs during execution of a Business Continuity Manager agent command. Communication-related messages (YKY300I, YKY301I, YKY304I, and YKY307I) are output. In addition to the messages that are output when LOGLEVEL(1) is specified, both the YKY680I and YKY500I messages are output. The YKY680I message is output when an error occurs during an update request for a copy pair configuration or a copy pair status. The YKY500I message displays the results of updated configuration files. In addition to the information output with LOGLEVEL(2), BCM logs are output. The following table shows the LOGLEVEL specification and the messages that are output Setting up the environment when linking with Replication Manager

95 Table 3-6 LOGLEVEL specification and the output messages LOGLEVEL Output messages 0 No output 1 YKY300I, YKY301I, YKY304I, and YKY307I 2 YKY300I, YKY301I, YKY304I, YKY307I, YKY500I, and YKY680I 3 YKY300I, YKY301I, YKY304I, YKY307I, YKY500I, and YKY680I AUDITLOG(SYSLOG) Specifies whether to output audit logs. When specified, the following additional information will be output to SYSLOG: Name and return code of CLI commands that end with an error Name and return code of CLI commands that end successfully (only for operational commands) Audit logs are not output if the AUDITLOG parameter is not specified. If the AUDITLOG parameter is specified, operations are performed as if LOGLEVEL(2) or later was specified. MODE(startup-mode) ~ ({EDIT MONITOR}) <<MONITOR>> Specifies the permission level at which the Business Continuity Manager agent starts. EDIT Allows definition, processing, and monitoring of copy groups. MONITOR Allows monitoring of copy groups. LOCK(lock-mode) ~ ({PREFIX CHECK NONE}) <<PREFIX>> Specifies the lock mode of the configuration files. The LOCK parameter is valid only when MODE(EDIT) is specified. An error occurs if the LOCK parameter is specified when MODE(MONITOR) is specified. PREFIX CHECK NONE Locks configuration files based on file name prefixes when the Business Continuity Manager agent starts. Other users cannot update configuration files that are locked. Does not lock configuration files when the Business Continuity Manager agent starts. When the Business Continuity Manager agent updates a definition, it verifies that no other user has updated the configuration file that it is about to update. Does not lock the configuration files when the Business Continuity Manager agent starts. Setting up the environment when linking with Replication Manager 3-27

96 Multiple specifications of initialization parameters The following table explains what results when multiple SETINIT commands are used to specify each initialization parameter: Table 3-7 Results of multiple specification of initialization parameters PORT Parameter name RECVWAITTIME Results of multiple specification Last specified parameter is applied. HOSTNAME PREFIX DEVN LOGLEVEL AUDITLOG Permitted Last specified parameter is applied. MODE LOCK Examples of specifying initialization parameters This subsection provides examples of specifying initialization parameters used for linking to Replication Manager. For Business Continuity Manager agent exclusively on the local site When Business Continuity Manager agent is installed on the local site, set up the Business Continuity Manager agent to perform both local and Remote Scans. The following figure shows an example of this configuration Setting up the environment when linking with Replication Manager

97 Figure 3-8 Example configuration when Business Continuity Manager agent is only on the local site For the configuration shown in Figure 3-8 Example configuration when Business Continuity Manager agent is only on the local site on page 3-29 specify the settings provided in the following table to connect Business Continuity Manager agent installed on the local site to Replication Manager. Setting up the environment when linking with Replication Manager 3-29

98 Table 3-8 Settings to connect Business Continuity Manager agent installed on the local site to Replication Manager Local site Remote site Prefix Port number DADID Route list ID (forward direction) Non Gen'ed DADID DADID ACCOUNT NY ROUTE1 No specification LA INFO ROUTE2 NY2 The following shows an example of specifying the settings shown in Table 3-8 Settings to connect Business Continuity Manager agent installed on the local site to Replication Manager on page 3-30 for initialization parameters. SETINIT PORT(24042) SETINIT MODE(EDIT) SETINIT LOCK(PREFIX) /* PREFIX */ SETINIT PREFIX('ACCOUNT','NY','ROUTE1',*,'LA') SETINIT PREFIX('INFO','NY','ROUTE2','NY2','LA') For Business Continuity Manager agent on local and remote sites When Business Continuity Manager agent is on both the local and remote sites, configure the Business Continuity Manager agent on each site to perform a scan on that site, only. The following figure shows an example of this configuration Setting up the environment when linking with Replication Manager

99 Figure 3-9 Example configuration when Business Continuity Manager agent is on the local site and a remote site For the configuration shown in Figure 3-9 Example configuration when Business Continuity Manager agent is on the local site and a remote site on page 3-31 specify the settings provided in the following table to connect Business Continuity Manager agent to the Replication Manager installed on each site. Setting up the environment when linking with Replication Manager 3-31

100 Table 3-9 Settings for connecting Business Continuity Manager agents installed on the local and remote sites to Replication Manager Local site Remote site Prefix Port numb er DADI D Route list ID (forward direction ) Non Gen'ed DADID Port numb er DADI D Route list ID (reverse directio n) Non Gen'ed DADID ACCOU NT NY ROUTE1 No specificat ion LA ROUTE3 No specification INFO ROUTE2 NY2 ROUTE4 LA2 The following shows an example of specifying the settings shown in Table 3-9 Settings for connecting Business Continuity Manager agents installed on the local and remote sites to Replication Manager on page 3-32 for initialization parameters. Settings for the Business Continuity Manager agent on the local site SETINIT PORT(24042) SETINIT MODE(EDIT) SETINIT LOCK(PREFIX) /* PREFIX */ SETINIT PREFIX('ACCOUNT','NY','ROUTE1') SETINIT PREFIX('INFO','NY','ROUTE2','NY2') Settings for the Business Continuity Manager agent on the remote site SETINIT PORT(24055) SETINIT MODE(EDIT) SETINIT LOCK(PREFIX) /* PREFIX */ SETINIT PREFIX('ACCOUNT','LA','ROUTE3') SETINIT PREFIX('INFO','LA','ROUTE4','LA2') Note: When Business Continuity Manager agent is on a remote site, you cannot scan the remote site by using Business Continuity Manager agent on the local site. Therefore, do not specify the device address domain ID of the remote site in the PREFIX parameter. Examples of initialization parameter analysis results When the Business Continuity Manager agent starts, the results of the initialization analysis is output to the dataset specified in the YKLIST DD statement Setting up the environment when linking with Replication Manager

101 The following examples show results. Result list with no error *** AGENT v.r.n-mm LISTING INFORMATION *** DATE= TIME=16:09:53 PAGE=0001 SETINIT PORT(24042) /* PREFIX */ SETINIT PREFIX('ACCOUNT','NY') SETINIT PREFIX('INFO','NY') Result list with an error This example shows an error condition where the local device address domain ID operand that is required for the first PREFIX parameter is missing. The YKY002I message is displayed. *** AGENT v.r.n-mm LISTING INFORMATION *** DATE= TIME=13:34:35 PAGE=0001 SETINIT PORT(24042) /* PREFIX */ SETINIT PREFIX('ACCOUNT') YKY002I INVALID INITIALIZATION PARAMETER: PREFIX SETINIT PREFIX('INFO','NY') Creating a cataloged procedure for startup for the Business Continuity Manager agents This section explains how to create and change a cataloged procedure for starting Business Continuity Manager agent. Standard cataloged procedure for startup The standard cataloged procedure for startup is registered into the sample library during installation. Copy the standard cataloged procedure for startup to the PROCLIB dataset of the JES (Job Entry Subsystem) startup procedure, and then modify the procedure to fit your environment. Standard cataloged procedure for startup in the expanded format Member name: YKAGENT //YKAGENT PROC MEMBER=YKPRM00 ******************************************************************** All Rights Reserved. Copyright (C) 2006, 2016, Hitachi, Ltd. ******************************************************************** //IEFPROC EXEC PGM=IKJEFT01,PARM=YKAGENTD, // TIME=1440,REGION=4096K Setting up the environment when linking with Replication Manager 3-33

102 //YKPARM DD DSN=HDSYK.Vnnnnnn.HDSYSAMT(&MEMBER),DISP=SHR //YKLIST DD DDNAME=IEFRDER //SYSTSPRT DD DUMMY //SYSTSIN DD DUMMY //SYSABEND DD SYSOUT=* //SYSEXEC DD DSN=HDSYK.Vnnnnnn.HDSYEXET,DISP=SHR //STEPLIB DD DSN=HDSYK.Vnnnnnn.HDSYLNKT,DISP=SHR Description In the sample JCL, the nnnnnn part of Vnnnnnn varies depending on the version. 1. PROC statement Specifies the member name of the initialization parameter that is used during the startup of the Business Continuity Manager agent. The member specified in this statement is the default value. To use a nonstandard member, execute the START command to change the member during the startup. 2. EXEC statement Specifies the following operands: TIME (CPU cut-off time) whose value is REGION (region size). To calculate this value, see section Determining required memory on page YKPARM DD statement Specifies the name of the dataset that contains the initialization parameters, and a member name for a partitioned dataset. 4. YKLIST DD statement Specifies the dataset to which the initialization parameter analysis result is to be output. The specified dataset must have the following attributes: LRECL: 121 BLKSIZE: Multiple of 121 RECFM: FBA DSORG: Sequential dataset (and a member name for a partitioned dataset) 5. SYSTSPRT DD statement Specifies DUMMY. 6. SYSTSIN DD statement Specifies DUMMY. 7. SYSABEND DD statement Specifies the location to which the dump is output when the Business Continuity Manager agent terminates abnormally. SYSOUT=* is specified in the standard cataloged procedure for startup. If the DUMMY output class is assigned as the output destination class for system messages in a job that is started by the START command, we recommend that you specify 3-34 Setting up the environment when linking with Replication Manager

103 SYSOUT=SYSOUT-class-enabled-for-output, since the dump is not output with SYSOUT=* specified. 8. SYSEXEC DD statement Specifies the dataset that contains the REXX exec library. 9. STEPLIB DD statement (optional) Specifies the Business Continuity Manager load library dataset. If the Business Continuity Manager load library dataset is linked to the system's LINKLIB, you do not need to specify the STEPLIB DD statement. 10. YKLOG01 DD and YKLOG02 DD statements (optional) Note: Specifies the log dataset to which BCM log data will be output to without using the system logger service. For details on how to specify DD statements for BCM logs and output BCM log data, see the description about outputting the BCM log data in the Hitachi Business Continuity Manager User Guide. Because the Business Continuity Manager agent is a resident program that waits for client requests, specify TIME=1440 in the EXEC statement so that no timeout occurs. Additionally, specify Purge as the output class of the job log and system messages so that the output messages do not cause a shortage of spool space. If z/os V1R3 or later is running, use the JOB statement keyword of the START command to specify that the JESLOG dataset is to be output using the SUPPRESS setting. Changing the cataloged procedure for startup You can change the contents of the standard cataloged procedure for startup according to the system environment and create a separate cataloged procedure for startup for the Business Continuity Manager agent. The cataloged procedure (member) can have any name. By adding the SYSTCPD DD statement to the cataloged procedure for startup, you can set up an environment for TCP/IP clients and programs used by the Business Continuity Manager agent. For example, when the standard TCP stack environment is not used, you can specify the TCP/IP environment settings file by adding the SYSTCPD DD statement. For details on how to specify the TCP/IP environment settings file without using the SYSTCPD DD statement and how to define the TCP/IP environment settings file to be specified in the SYSTCPD DD statement, see the explanation of a basic TCP/IP system in the IBM manual Communications Server IP Configuration Guide. Setting up the environment when linking with Replication Manager 3-35

104 3-36 Setting up the environment when linking with Replication Manager

105 4 Setting up an environment for BCM Monitor This chapter explains how to set up the security for BCM Monitor. It also explains how to create configuration files, BCM Monitor parameter files, and a cataloged procedure for startup. General procedure for setting up an environment for BCM Monitor Setting up the security for BCM Monitor Creating configuration files for BCM Monitor Creating BCM Monitor parameter files Creating a cataloged procedure for startup for BCM Monitor Setting up an environment for BCM Monitor 4-1

106 General procedure for setting up an environment for BCM Monitor This section contains the general procedure for configuring the environment settings that are necessary for BCM Monitor. Figure 4-1 General procedure for configuring the environment settings necessary for BCM Monitor The following sections explain the details about each step. Setting up the security for BCM Monitor This section explains how to set up the security for BCM Monitor. Define the appropriate user ID and group ID in the RACF STARTED class of the cataloged procedure for startup for BCM Monitor. The following is an example of using the TSO/E command with the STARTED class: ->SETROPTS GENERIC(STARTED) ->RDEFINE STARTED YKBCMMON.* STDATA(USER(user-ID) GROUP(group-ID)) ->SETROPTS RACLIST(STARTED) REFRESH BCM Monitor uses a Business Continuity Manager CLI command to monitor copy groups. To use the CLI command, you need to define one of the following profiles in the RACF FACILITY class, and then grant the view permission for the defined profile to the previously defined user ID or group ID. If you specified one of the following in the BCM Monitor YKMONCG file, you need to grant the view permission to the STGADMIN.YKA.BCM.COMMANDS profile: 4-2 Setting up an environment for BCM Monitor