Hitachi Business Continuity Manager

(1)

Hitachi Business Continuity Manager

Installation Guide

Document Organization

Product Version

Getting Help

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 https://support.hds.com/en_us/contact-us.html. 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.

(3)

Preface... ix

Intended audience... x

Product version...x

Release notes... x

Document organization...x

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...1-1

Licenses provided by Business Continuity Manager...1-2

Prerequisite conditions... 1-3

Operating system prerequisites...1-3

Program prerequisites...1-3

Supported storage systems... 1-4

Prerequisites for using a volume on Linux

®

_{on IBM System z...1-4}

2 Installing Business Continuity Manager...2-1

Overview of installation... 2-2

Preparing for installation... 2-2

Types of distribution media... 2-2

Provided datasets... 2-2

Planning DASD storage attributes... 2-4

About distribution libraries (DLIB)...2-4

About target libraries...2-5

Designing storage...2-5

Required device capacity for BCM log data... 2-6

Determining required memory...2-7

Preparations for installing Business Continuity Manager...2-9

Installing Business Continuity Manager... 2-10

Installing Business Continuity Manager with SMP/E... 2-10

Simple installation (installation without SMP/E)... 2-12

(4)

Setting up the environment... 2-12

Settings for using CLI commands in TSO/E environments... 2-14

Settings for using ISPF panels with Business Continuity Manager... 2-15

Concatenating the libraries needed to execute the YKSTART command... 2-15

Starting YKSTART dynamically...2-16

Settings in the ISPF panel ... 2-16

Setting the position of the command line... 2-16

Setting the number of PF keys that are displayed... 2-17

Settings for using the YKWATCH command and the copy group definition generation

function for PPRC copy pairs...2-17

Settings for using environment configuration commands... 2-17

Setting the security...2-18

Setting security for the environment configuration commands... 2-18

Setting security for CLI commands, YKAGENTD, and YKBTSCAN... 2-18

Setting security when the extended access control function is installed...2-20

Procedure for setting the READ permission for the RACF profile to the user2-21

Setting security for starting a System REXX environment...2-22

Configuring dataset security... 2-23

Registering a user SVC...2-23

Using the IEASVCxx parmlib member to register...2-23

Using the YKALCSVC command to register... 2-24

Setting Business Continuity Manager environment variables...2-25

Specifying the host ID... 2-27

Enabling and disabling the system logger service...2-28

Specifying whether to output CLI command-execution logs... 2-29

YKSETENV command format... 2-30

YKDSPENV command format... 2-32

Registering a license... 2-33

Using the license key file...2-34

Directly entering a key code... 2-35

Notes when operating license keys... 2-36

Format for license information datasets...2-36

Naming for license information datasets...2-37

Verification procedure following installation and setup... 2-39

Check whether the installation and environment settings are completed....2-39

Checking the access permissions when the extended access control function is

installed...2-40

Upgrading Business Continuity Manager... 2-40

What to check before upgrading... 2-40

Checking licenses... 2-40

Checking environment variables... 2-40

Checking the user SVC number...2-41

Backing up datasets...2-42

Backing up configuration files...2-42

Backing up the program before migration...2-42

Pre-upgrade procedure... 2-42

Deleting the user SVC...2-42

Removing the concatenation of the cataloged procedures library... 2-43

Removing the concatenation of the REXX Exec library and the libraries used by

ISPF interface... 2-43

Removing the concatenation of the load library... 2-44

Upgrading Business Continuity Manager... 2-44

(5)

What to check after upgrading...2-44

Notes on system setup when a related product is installed...2-44

Notes on user SVC registration when a related product is installed... 2-44

Notes on setting environment variables or system symbols when a related product is

installed... 2-45

Notes on specifying a prefix when a related product is installed... 2-46

User SVC versions required by Business Continuity Manager... 2-46

3 Setting up the environment when linking with Replication Manager... 3-1

Overview of environment settings... 3-2

Configuring the environment settings without using the Remote DKC Control function

(before Business Continuity Manager is installed)...3-2

Configuring the environment settings using the Remote DKC Control function (before

Business Continuity Manager is installed)... 3-4

Configuring the environment settings in an existing environment (with Business

Continuity Manager installed)... 3-6

Configuring the environment settings to allow only monitoring of copy groups... 3-8

Configuring the environment settings for monitoring PPRC copy pairs...3-9

Creating configuration file datasets... 3-9

Configuration file dataset names...3-9

Dataset format and required disk capacity for the configuration file...3-11

Setting the TCP/IP port number... 3-11

Setting up the security for Business Continuity Manager agents...3-12

Setting the dataset security... 3-12

Setting up the Resource Access Control Facility (RACF) when linking with Replication

Manager... 3-12

Setting up IBM HTTP Server... 3-13

Settings for connecting via IPv6...3-13

Setting up HTTPS connections... 3-15

Collecting the trace log...3-19

Creating initialization parameters... 3-19

How to use the SETINIT command... 3-20

Continuing to the next line... 3-21

Entering comments...3-22

Notes during creation of initialization parameters...3-22

Details of initialization parameters...3-22

Format... 3-22

Parameters... 3-23

Multiple specifications of initialization parameters... 3-28

Examples of specifying initialization parameters... 3-28

For Business Continuity Manager agent exclusively on the local site... 3-28

For Business Continuity Manager agent on local and remote sites... 3-30

Examples of initialization parameter analysis results... 3-32

Creating a cataloged procedure for startup for the Business Continuity Manager agents

... 3-33

Standard cataloged procedure for startup...3-33

Standard cataloged procedure for startup in the expanded format... 3-33

Description... 3-34

Changing the cataloged procedure for startup...3-35

(6)

4 Setting up an environment for BCM Monitor...4-1

General procedure for setting up an environment for BCM Monitor... 4-2

Setting up the security for BCM Monitor...4-2

Creating configuration files for BCM Monitor... 4-3

Creating BCM Monitor parameter files...4-3

Creating a cataloged procedure for startup for BCM Monitor... 4-4

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 6.6.1 to 6.6.1

or later... C-2

When upgrading Business Continuity Manager from a version earlier than 6.7.1 to 6.7.1

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 7.6.1 to 7.6.1

or later... C-3

When upgrading Business Continuity Manager from a version earlier than 8.1.4 to 8.1.4

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

(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

(8)

(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

(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 USP V, VSP, VSP G1000, VSP G1500, or VSP F1500 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.5 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. Release notes are available on Hitachi Data Systems Support Connect: https://

knowledge.hds.com/Documents.

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 Description

Chapter 1, Overview of Hitachi Business Continuity Manager on page 1-1

Explains the provided licenses and prerequisites for using Business Continuity Manager.

Chapter 2, Installing Business Continuity Manager on page 2-1

Explains installation preparations and procedures, memory estimation, and version upgrade procedures. Chapter 3, Setting up the

environment when linking with Replication Manager on page 3-1

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. Chapter 4, Setting up an

environment for BCM Monitor on page 4-1

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.

(11)

Chapter/Appendix Description Appendix A, Modifying

sample JCL on page A-1

Explains how to modify sample JCL. Appendix B, Sample Scripts

on page B-1 Explains how to use sample scripts. Appendix C, Notes on

upgrading Business

Continuity Manager on page C-1

Provides notes on upgrading Business Continuity Manager.

Appendix D, Notes when multiple versions of Business Continuity Manager exist on page D-1

Provides notes on upgrade processing when multiple versions of Business Continuity Manager exist in a system.

Appendix E, Conventions in syntax explanations on page E-1

Explains the conventions in syntax explanations and the syntax elements that are used.

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 Indicates text that is displayed on screen or entered by the user. Example:

pairdisplay -g oradb [ ] square

brackets Indicates optional values. Example: [ a | b ] indicates that you canchoose 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:

(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,0003_bytes 1 terabyte (TB) 1,000 GB or 1,0004_bytes 1 petabyte (PB) 1,000 TB or 1,0005_bytes 1 exabyte (EB) 1,000 PB or 1,0006_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,0243_bytes 1 TB 1,024 GB or 1,0244_bytes 1 PB 1,024 TB or 1,0245_bytes 1 EB _{1,024 PB or 1,024}6_bytes

Accessing product documentation

Product documentation is available on Hitachi Data Systems Support Connect: https://knowledge.hds.com/Documents. 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: https://support.hds.com/en_us/contact-us.html.

Hitachi Data Systems Community is a global online community for HDS customers, partners, independent software vendors, employees, and

(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: [email protected].

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.

(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

(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 theRemote 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.

(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 V1R13, and V2R1 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:

• 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.

Program prerequisites

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 managementproduct None TSO/E REXX Required This program is required to run

Business Continuity Manager.

Standard OS component.

TSO/E# _Required

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.

(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 8.5.0 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 bundledwith 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 8.5.5 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:

• Universal Storage Platform V/VM (USP V) • Hitachi Virtual Storage Platform (VSP)

• Hitachi Virtual Storage Platform G1000 (VSP G1000) • Hitachi Virtual Storage Platform G1500 (VSP G1500) • Hitachi Virtual Storage Platform F1500 (VSP F1500)

Prerequisites for using a volume on Linux

®

_{on IBM System z}

To use a z/Linux volume, first specify the following:

(19)

• (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

(20)

(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

(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 2-40.

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 Required/_Optional

1 HITACHI.CHYKnnn.SMPMCS.XMIT SMP/E for Business Continuity Manager control statements used for packaging SYSMOD

(23)

No. File name Contents Required/_Optional 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

Required

3 HITACHI.CHYKnnn.F2.XMIT Business Continuity Manager load modules for LINKLIB

Required

4 HITACHI.CHYKnnn.F3.XMIT Business Continuity Manager load modules for LPALIB

Required

5 HITACHI.CHYKnnn.F4.XMIT Cataloged procedure

library 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)

Optional

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

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.

(24)

Table 2-2 FMID for Business Continuity Manager component

FMID Function name

CHYKnnn 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)

PO FB 80 6,160

HDSYLNKD

(Load library for LINKLIB)

PO U -- 6,144

HDSYLPAD

(Load library for LPALIB)

PO U -- 6,144

HDSYPRCD

(Cataloged procedure library)

PO FB 80 6,160

HDSYEXED

(REXX Exec Library)

PO FB 80 6,160

HDSYEXVD

(REXX Exec library, variable length format) PO VB 255 6,120 HDSYPNLD (Panel Library) PO FB 80 6,160 HDSYMSGD (Message Library) PO FB 80 6,160 HDSYTABD (Table Library) PO FB 80 6,160

(25)

#: 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.

About target libraries

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)

PO FB 80 6,160

HDSYLNKT

(Load library for LINKLIB)

PO U -- 6,144

HDSYLPAT

(Load library for LPALIB)

PO U -- 6,144

HDSYPRCT

(Cataloged procedure library)

PO FB 80 6,160

HDSYEXET

(REXX Exec Library)

PO FB 80 6,160

HDSYEXVT

(REXX Exec library, variable length format) PO VB 255 6,120 HDSYPNLT (Panel Library) PO FB 80 6,160 HDSYMSGT (Message Library) PO FB 80 6,160 HDSYTABT (Table Library) PO FB 80 6,160

#: 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

dd-name library indicates a library type.

Designing storage

Operating Business Continuity Manager entails calculating the amount of device capacity and memory that you require and planning accordingly.

(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) 100 + message-length#2

number-of-messages-output

Parameter information for the channel command words of the I/O, only when an I/O error occurs

100 + CCW-length#3 number-of-times-an-I/O-error-occurred I/O return information, only when an

I/O error occurs 256 number-of-times-an-I/O-error-occurred Sense byte information, only when an

I/O error occurs

256

number-of-times-an-I/O-error-occurred

Timestamps 128 2

Command parameter information 256 1

#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-messages-output

(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

68 + CCW-length#3 number-of-times-an-I/O-error-occurred I/O return information, only when an

I/O error occurs 224 number-of-times-an-I/O-error-occurred Sense byte information, only when an

I/O error occurs 224 number-of-times-an-I/O-error-occurred

Timestamps 96 2

Command parameter information 224 1

#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):

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.

Determining required memory

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

(28)

4,000 KB + (1 of-volumes) KB + (2.5

number-of-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

(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-1. 4. 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-2.

5. 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 2-2.

6. 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

(30)

page 2-10, or by the simple installation as described in section Simple installation (installation without SMP/E) on page 2-12.

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-8.

2. 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-10.

3. 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-12.

(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-15.

5. 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 re-execute the job.

For examples of modifying sample JCL (HDSYK4AP), see HDSYK4AP (creating target libraries) on page A-17.

6. 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 re-execute 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-20.

8. 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).

(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-22.

9. 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.

(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

Settings needed for using CLI

commands in TSO/E environments Settings for using CLI commands inTSO/E environments on page 2-14

2 Settings for using ISPF panels with Business Continuity Manager

The YKSTART command must be configured to use ISPF panels with Business Continuity Manager.

Settings for using ISPF panels with Business Continuity Manager on page 2-15

3 Settings in the ISPF

panel The following settings are in theISPF panel: • PF key usage

• Command line position settings • Settings for the number of PF

keys to display

Settings in the ISPF panel on page 2-16

4 Settings for using the YKWATCH command and the copy group definition

generation function for PPRC copy pairs

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 the YKWATCH command and the copy group definition generation function for PPRC copy pairs on page 2-17

5 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 2-17

6 Setting security Security settings for environment configuration commands, CLI commands, and datasets

Setting the security on page 2-18

7 Registering a user

SVC User SVC registration

# _{Setting the security on page 2-18} 8 Setting Business

Continuity Manager environment variables

Setting the environment variables required for Business Continuity Manager operation.#

Setting Business Continuity Manager environment variables on page 2-25

9 Registering a license

Registering a license key to enable the corresponding functionality.

(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 2-44.

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

(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.

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 site-specific selection menu.

(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;

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.

(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 Function

YKALCSVC Registers the user SVC.

(38)

Command name Function • Host ID

• Prefix for the license information dataset • BCM log output method

• Whether CLI command-execution logs are output to SYSLOG or the console

YKDSPENV Displays the specified Business Continuity Manager environment variables and the program product name.

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 2-14.

• 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 the security

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.

(39)

Table 2-9 Correspondence between profiles defined in the FACILITY class and available functions

Profile defined for the FACILITY class Available functions STGADMIN.YKA.BCM.COMMANDS (Operation profiles) YKAGENTD YKBLDCMD command 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

(40)

Profile defined for the FACILITY class Available functions YKQRYDEV command YKQRYPTH command YKQUERY command YKSCAN command YKSTATS command YKWATCH command

Note: A user can use commands other than those in the preceding table,

even if the user has not been assigned READ permissions for these two profiles.

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

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 2-21.

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.

(41)

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 Profiles to be defined to the FACILITY class Copy group access control

function 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)

Specific command access

control function 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:

prefix: Configuration file prefix 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 2-21.

Procedure for setting the READ permission for the RACF profile to the user

(42)

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)

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

(43)

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: • Static registration using the IEASVCxx parmlib member

• Dynamic 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 statically register a user SVC 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')

Note:

• For SVC-number, specify a decimal number between 200 and 255. • You must define the SYMDEF statement. If the SYMDEF statement is

not defined, Business Continuity Manager is unable to recognize the SVC number to be registered.

3. 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.

¢ 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

SVC-number,REPLACE,TYPE(3),EPNAME(JYUASVC),APF(NO),NPRMPT(NO),AR(NO)

Hitachi Business Continuity Manager