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

Hitachi Business Continuity ManagerInstallation Guide

MK-95HC104-25

Document Organization

Product Version

Getting Help

Contents

© 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 retrievalsystem for commercial purposes without the express written permission of Hitachi, Ltd., or HitachiData Systems Corporation (collectively “Hitachi”). Licensee may make copies of the Materialsprovided that any such copy is: (i) created as an essential step in utilization of the Software aslicensed and is used in no other manner; or (ii) used for archival purposes. Licensee may not makeany other copies of the Materials. “Materials” mean text, data, photographs, graphics, audio, videoand documents.

Hitachi reserves the right to make changes to this Material at any time without notice and assumesno responsibility for its use. The Materials contain the most current information available at the timeof publication.

Some of the features described in the Materials might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi 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 theapplicable Hitachi agreements. The use of Hitachi products is governed by the terms of youragreements 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 fromauthorized employees and other individuals to access relevant data; and

2) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordancewith relevant laws.

Notice on Export Controls. The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility toobtain 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 InternationalBusiness 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 WindowsVista are registered trademarks or trademarks of Microsoft Corporation. Microsoft product screenshots are reprinted with permission from Microsoft Corporation.

All other trademarks, service marks, and company names in this document or website areproperties of their respective owners.

iiHitachi Business Continuity Manager Installation Guide

https://support.hds.com/en_us/contact-us.html

Contents

Preface.................................................................................................. ixIntended audience..................................................................................................... xProduct version..........................................................................................................xRelease notes............................................................................................................ xDocument organization...............................................................................................xRelated documents....................................................................................................xiDocument conventions..............................................................................................xiiConventions for storage capacity values.....................................................................xiiAccessing product documentation............................................................................. xiiiGetting help............................................................................................................ xiiiComments.............................................................................................................. xiv

1 Overview of Hitachi Business Continuity Manager....................................1-1Licenses provided by Business Continuity Manager....................................................1-2Prerequisite conditions............................................................................................ 1-3

Operating system prerequisites..........................................................................1-3Program prerequisites.......................................................................................1-3Supported storage systems............................................................................... 1-4Prerequisites for using a volume on Linux® on IBM System z...............................1-4

2 Installing Business Continuity Manager...................................................2-1Overview of installation........................................................................................... 2-2Preparing for installation......................................................................................... 2-2

Types of distribution media............................................................................... 2-2Provided datasets............................................................................................. 2-2Planning DASD storage attributes...................................................................... 2-4

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

Designing storage.............................................................................................2-5Required device capacity for BCM log data................................................ 2-6Determining required memory..................................................................2-7

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

Installing Business Continuity Manager with SMP/E........................................... 2-10Simple installation (installation without SMP/E)................................................. 2-12

iiiHitachi Business Continuity Manager Installation Guide

Setting up the environment................................................................................... 2-12Settings for using CLI commands in TSO/E environments.................................. 2-14Settings for using ISPF panels with Business Continuity Manager....................... 2-15

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

Settings in the ISPF panel .............................................................................. 2-16Setting the position of the command line................................................ 2-16Setting the number of PF keys that are displayed.................................... 2-17

Settings for using the YKWATCH command and the copy group definition generationfunction for PPRC copy pairs............................................................................2-17Settings for using environment configuration commands................................... 2-17Setting the security.........................................................................................2-18

Setting security for the environment configuration commands.................. 2-18Setting security for CLI commands, YKAGENTD, and YKBTSCAN............... 2-18Setting security when the extended access control function is installed......2-21Procedure for setting the READ permission for the RACF profile to the user2-22Setting security for starting a System REXX environment..........................2-23Configuring dataset security...................................................................2-23

Registering a user SVC....................................................................................2-23Using the IEASVCxx parmlib member to register......................................2-23Using the YKALCSVC command to register.............................................. 2-24

Setting Business Continuity Manager environment variables...............................2-26Specifying the host ID........................................................................... 2-27Enabling and disabling the system logger service.....................................2-28Specifying whether to output CLI command-execution logs...................... 2-29YKSETENV command format.................................................................. 2-31YKDSPENV command format..................................................................2-33

Registering a license....................................................................................... 2-34Using the license key file........................................................................2-34Directly entering a key code...................................................................2-35Notes when operating license keys......................................................... 2-36Format for license information datasets...................................................2-36Naming for license information datasets..................................................2-37

Verification procedure following installation and setup....................................... 2-39Check whether the installation and environment settings are completed....2-39Checking the access permissions when the extended access control function isinstalled................................................................................................2-40

Upgrading Business Continuity Manager................................................................. 2-40What to check before upgrading...................................................................... 2-41

Checking licenses.................................................................................. 2-41Checking environment variables............................................................. 2-41Checking the user SVC number...............................................................2-42

Backing up datasets........................................................................................2-42Backing up configuration files.................................................................2-42Backing up the program before migration................................................2-42

Pre-upgrade procedure................................................................................... 2-43Deleting the user SVC............................................................................2-43Removing the concatenation of the cataloged procedures library.............. 2-43Removing the concatenation of the REXX Exec library and the libraries used byISPF interface....................................................................................... 2-44Removing the concatenation of the load library....................................... 2-44

Upgrading Business Continuity Manager........................................................... 2-44

ivHitachi Business Continuity Manager Installation Guide

What to check after upgrading.........................................................................2-44Notes on system setup when a related product is installed.......................................2-45

Notes on user SVC registration when a related product is installed..................... 2-45Notes on setting environment variables or system symbols when a related product isinstalled......................................................................................................... 2-45Notes 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-1Overview of environment settings............................................................................ 3-2

Configuring the environment settings without using the Remote DKC ControlFunction (before Business Continuity Manager is installed).................................. 3-2Configuring the environment settings using the Remote DKC Control Function(before Business Continuity Manager is installed)................................................3-4Configuring the environment settings in an existing environment (with BusinessContinuity Manager installed)............................................................................ 3-6Configuring the environment settings to allow only monitoring of copy groups......3-8Configuring the environment settings for monitoring PPRC copy pairs...................3-9

Creating configuration file datasets.......................................................................... 3-9Configuration file dataset names........................................................................3-9Dataset format and required disk capacity for the configuration file....................3-11

Setting the TCP/IP port number............................................................................. 3-11Setting up the security for Business Continuity Manager agents................................3-12

Setting the dataset security............................................................................. 3-12Setting up the Resource Access Control Facility (RACF) when linking with ReplicationManager........................................................................................................ 3-12

Setting up IBM HTTP Server.................................................................................. 3-13Settings for connecting via IPv6.......................................................................3-13Setting up HTTPS connections......................................................................... 3-15Collecting the trace log....................................................................................3-19

Creating initialization parameters........................................................................... 3-19How to use the SETINIT command.................................................................. 3-20

Continuing to the next line..................................................................... 3-21Entering comments................................................................................3-22Notes during creation of initialization parameters.....................................3-22

Details of initialization parameters....................................................................3-22Format................................................................................................. 3-22Parameters........................................................................................... 3-23Multiple specifications of initialization parameters.................................... 3-28

Examples of specifying initialization parameters................................................ 3-28For Business Continuity Manager agent exclusively on the local site.......... 3-28For Business Continuity Manager agent on local and remote sites............. 3-30

Examples of initialization parameter analysis results.......................................... 3-32Creating a cataloged procedure for startup for the Business Continuity Manager agents........................................................................................................................... 3-33

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

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

vHitachi Business Continuity Manager Installation Guide

4 Setting up an environment for BCM Monitor............................................4-1General procedure for setting up an environment for BCM Monitor............................. 4-2Setting up the security for BCM Monitor....................................................................4-2Creating configuration files for BCM Monitor............................................................. 4-3Creating BCM Monitor parameter files.......................................................................4-3Creating a cataloged procedure for startup for BCM Monitor...................................... 4-4

A Modifying sample JCL........................................................................... A-1Values used in the sample JCL modification examples............................................... A-2ALLOUPLD (creating transmission datasets)..............................................................A-2RECVUPLD (TSO/E RECEIVE processing).................................................................. A-5HDSYKSIN (simple installation)................................................................................A-6SMPALLOC (allocating SMP/E datasets).................................................................... A-8HDSYK1AL (allocating distribution and target libraries)............................................ A-10HDSYK2DF (defining distribution and target libraries).............................................. A-12HDSYK3RC (SMP/E RECEIVE processing)................................................................A-15HDSYK4AP (creating target libraries)......................................................................A-17HDSYK5AC (creating distribution libraries).............................................................. A-19HDSYK6RC (SMP/E RECEIVE processing for extended access control function).......... A-20HDSYK7AP (creating target libraries for extended access control function)................ A-22HDSYK8AC (creating distribution libraries for extended access control function)........ A-24

B Sample Scripts..................................................................................... B-1HDSRFEPR (viewing access permissions for the extended access control function)...... B-2

C Notes on upgrading Business Continuity Manager................................... C-1When upgrading Business Continuity Manager from a version earlier than 6.6.1 to 6.6.1or later.................................................................................................................. C-2When upgrading Business Continuity Manager from a version earlier than 6.7.1 to 6.7.1or later.................................................................................................................. C-2

Route Config panel...........................................................................................C-2Route list structure........................................................................................... C-2

When upgrading Business Continuity Manager from a version earlier than 7.4 to 7.4 orlater...................................................................................................................... C-3When upgrading Business Continuity Manager from a version earlier than 7.6.1 to 7.6.1or later.................................................................................................................. C-3When upgrading Business Continuity Manager from a version earlier than 8.1.4 to 8.1.4or later.................................................................................................................. C-3

D Notes when multiple versions of Business Continuity Manager exist.........D-1Configuration files.................................................................................................. D-2License information dataset.....................................................................................D-2Changed display for the license name...................................................................... D-2Prefix for the license information dataset................................................................. D-2Installing a license..................................................................................................D-3Specifying Business Continuity Manager log output destination (LOGPUT).................. D-3Specifying whether to output the CLI command-execution logs (SYSLOG).................. D-3Setting up the Resource Access Control Facility (RACF) when multiple versions ofBusiness Continuity Manager exist........................................................................... D-6

viHitachi Business Continuity Manager Installation Guide

Registering a user SVC dynamically..........................................................................D-7User SVC for suppressing IOS002A messages...........................................................D-7Available versions of user SVCs............................................................................... D-7

E Conventions in syntax explanations........................................................E-1Conventions in syntax explanations..........................................................................E-2

Acronyms and abbreviations

Index

viiHitachi Business Continuity Manager Installation Guide

viiiHitachi Business Continuity Manager Installation Guide

Preface

This document describes how to install the following program products. Inthis manual, these products are collectively referred to as Business ContinuityManager:

- 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 ixHitachi Business Continuity Manager Installation Guide

Intended audienceThis document is intended for users who want to install Business ContinuityManager.

Readers of this document are assumed to have a basic understanding of thefollowing:

• Functions of Lightning 9900V Series, USP, USP V, VSP or VSP G1000storage systems.

• How to create a system that uses Hitachi Replication Manager if linkingwith Hitachi Replication Manager.

Product versionThis document revision applies to Hitachi Business Continuity Manager v8.4or later.

Release notesRead the release notes before installing and using this product. They maycontain requirements or restrictions that are not fully described in thisdocument or updates or corrections to this document.

Document organizationThe following table provides an overview of the contents and organization ofthis 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 ofHitachi Business ContinuityManager on page 1-1

Explains the provided licenses and prerequisites for usingBusiness Continuity Manager.

Chapter 2, Installing BusinessContinuity Manager on page2-1

Explains installation preparations and procedures,memory estimation, and version upgrade procedures.

Chapter 3, Setting up theenvironment when linkingwith Replication Manager onpage 3-1

Explains how to set up port numbers, security, and IBMHTTP Server, which are all required to link to ReplicationManager. It also explains how to create initializationparameters and a cataloged procedure for startup.

Chapter 4, Setting up anenvironment for BCM Monitoron page 4-1

Explains how to set up the security for BCM Monitor. Italso explains how to create configuration files, BCMMonitor parameter files, and a cataloged procedure forstartup.

Appendix A, Modifyingsample JCL on page A-1

Explains how to modify sample JCL.

x PrefaceHitachi Business Continuity Manager Installation Guide

Chapter/Appendix Description

Appendix B, Sample Scriptson page B-1

Explains how to use sample scripts.

Appendix C, Notes onupgrading BusinessContinuity Manager on pageC-1

Provides notes on upgrading Business ContinuityManager.

Appendix D, Notes whenmultiple versions of BusinessContinuity Manager exist onpage D-1

Provides notes on upgrade processing when multipleversions of Business Continuity Manager exist in asystem.

Appendix E, Conventions insyntax explanations on pageE-1

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

Related documentsManuals 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 UserGuide, 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 xiHitachi Business Continuity Manager Installation Guide

Document conventionsThis document uses the following typographic conventions:

Convention Description

Bold • Indicates text in a window, including window titles, menus, menuoptions, 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

[ ] squarebrackets

Indicates optional values. Example: [ a | b ] indicates that you canchoose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicatesthat you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options orarguments. 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 forperforming tasks more effectively.

Caution Warns the user of adverse conditions or consequences (forexample, disruptive operations).

WARNING Warns the user of severe conditions or consequences (forexample, destructive operations).

Conventions for storage capacity valuesPhysical storage capacity values (for example, disk drive capacity) arecalculated based on the following values:

xii PrefaceHitachi Business Continuity Manager Installation Guide

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

1 megabyte (MB) 1,000 KB or 1,0002 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) arecalculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

1 cylinder Mainframe: 870 KBOpen-systems:• OPEN-V: 960 KB• Others: 720 KB

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 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,0246 bytes

Accessing product documentationProduct documentation is available on Hitachi Data Systems SupportConnect: https://support.hds.com/en_us/documents.html. Check this sitefor the most current documentation, including important updates that mayhave been made after the release of the product.

Getting helpHitachi Data Systems Support Connect is the destination for technical supportof products and solutions sold by Hitachi Data Systems. To contact technicalsupport, log on to Hitachi Data Systems Support Connect for contactinformation: https://support.hds.com/en_us/contact-us.html.

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

Preface xiiiHitachi Business Continuity Manager Installation Guide

https://support.hds.com/en_us/documents.html

https://support.hds.com/en_us/contact-us.html

prospects. It is the destination to get answers, discover insights, and makeconnections. Join the conversation today! Go to community.hds.com,register, and complete your profile.

CommentsPlease send us your comments on this document: [email protected] the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!

xiv PrefaceHitachi Business Continuity Manager Installation Guide

https://community.hds.com/welcome

1Overview of Hitachi Business Continuity

Manager

This chapter explains the provided licenses and prerequisites for usingBusiness Continuity Manager.

□ Licenses provided by Business Continuity Manager

□ Prerequisite conditions

Overview of Hitachi Business Continuity Manager 1-1Hitachi Business Continuity Manager Installation Guide

Licenses provided by Business Continuity ManagerTo use Business Continuity Manager, you need to install the appropriatelicense.

There are two types of licenses for Business Continuity Manager: a license forusing basic functions, and licenses for using optional functions. When thelicense for using basic functions is installed, you can define and manageShadowImage (SI), TrueCopy (TC), TrueCopy Asynchronous (TCA) andUniversal Replicator (UR) copy groups. To use optional functions, install therequired license.

After a license key is installed in the license information dataset, functionscorresponding to the license you installed become available.

When you migrate Business Continuity Manager from an older version to anewer version, depending on conditions, you might need to obtain the licensekeys again.

The following table lists the licenses provided by Business Continuity Managerand functions available for each license.

Table 1-1 Licenses and available functions

License name Available function Mandatory or optional

Business ContinuityManager Basic

Basic functions (including theRemote DKC Control Functionand TrueCopy consistencypreservation function).

Mandatory

Business ContinuityManager UR 4x4 ExtendedCTG

Consistency preservationfunction of Universal Replicator ina 4x4 configuration

Optional

The length of time you can use Business Continuity Manager depends on thetype of installed license. The following table lists the license types.

Table 1-2 License types

License type Effectiveperiod 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 toexpire, but a permanent license cannot bepurchased.

Note:

• When you operate a storage system using Business Continuity Manageron 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 ManagerHitachi Business Continuity Manager Installation Guide

Prerequisite conditionsThis section describes the prerequisites for using the Business ContinuityManager.

Operating system prerequisitesBusiness Continuity Manager can be used on the following operating systems:

• z/OS® V1R10 to V2R2Use version z/OS V2R1 or later to establish HTTPS communicationbetween Replication Manager and Business Continuity Manager by usingTLS 1.2.

Note:

• VM environments are supported. For details about operatingconditions and other information, contact the product vendor. Notethat VM environments do not support HTTPS communication.

• The devices in the alternate subchannel set are not supported.

Program prerequisitesThe following table lists the programs required to use Business ContinuityManager.

Table 1-3 Prerequisite programs

Program name Required /Optional Overview Description

DFSMS Required A data facility storagemanagement 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 runBusiness Continuity Manager.


TSO/E# Required

IBM Library forREXX on zSeriesRelease 4 (FMIDHWJ9140) or IBMLibrary for REXX onzSeries AlternateLibrary (FMIDHWJ9143)

Required IBM Library for REXX on zSeriesAlternate Library (FMIDHWJ9143) is a Standard OScomponent.

System REXX Optional This program is required forexecuting CLI commands in aSystem REXX environment.



Program name Required /Optional Overview Description

Replication Manager Optional One of the Hitachi CommandSuite products. ReplicationManager is required fordefining, using, and monitoringcopy pairs, as accomplished bylinking with the BusinessContinuity Manager agent.

Use version 8.4.0 or a laterversion.

IBMCommunicationsServer

Optional A communication program.This program is required forlinking with ReplicationManager.


IBM HTTP Server forz/OS

Optional An optional product bundledwith WebSphere ApplicationServer for z/OS. This isrequired when establishingIPv6 connections or HTTPScommunication with ReplicationManager.In addition, z/OS SecurityLevel3 is required whenestablishing HTTPScommunication with ReplicationManager.

Use version 6.1 or a laterversion.Use version 8.5.5 or a laterversion to establish HTTPScommunication betweenReplication Manager andBusiness Continuity Manager byusing TLS 1.2.

IBM Tivoli StorageProductivity Centerfor Replication forSystem z

Optional This program is required toperform operations in 2DCconfigurations with HyperSwapand Universal Replicator.

Use version 4.2 or a laterversion.

#: In the TSO/E terminal, lower-case letters might not be correctly displayed,depending on the usage environment.

Supported storage systemsBusiness Continuity Manager can be used to operate any of the followingHitachi 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 zMake sure that you are aware of the information in this section before usingBusiness Continuity Manager on a Linux IBM System z/Linux volume.

Note the following limitations:


• 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 consistencygroup, 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



2Installing Business Continuity Manager

This chapter provides installation preparations and procedures, environmentsetup 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-1Hitachi Business Continuity Manager Installation Guide

Overview of installationThe following figure provides an overview of how to install BusinessContinuity Manager.

Figure 2-1 Overview of the Business Continuity Manager installationprocedure

The following sections explain the details about each step.

To upgrade Business Continuity Manager, see Upgrading Business ContinuityManager on page 2-40.

Preparing for installationThe sections below describe the preparations required for installing BusinessContinuity Manager.

Types of distribution mediaBusiness Continuity Manager is available through both of the followingdistribution media:

• CD-ROM

Provided datasetsThe 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 BusinessContinuity Managercontrol statementsused for packagingSYSMOD

Required

2-2 Installing Business Continuity ManagerHitachi Business Continuity Manager Installation Guide

No. File name Contents Required/Optional

2 HITACHI.CHYKnnn.F1.XMIT This sample libraryincludes JCL samplesused by SMP/E (forallocation, DDDEF,RECEIVE, APPLY, andACCEPT), and othersamples

Required

3 HITACHI.CHYKnnn.F2.XMIT Business ContinuityManager loadmodules for LINKLIB

Required

4 HITACHI.CHYKnnn.F3.XMIT Business ContinuityManager loadmodules for LPALIB

Required

5 HITACHI.CHYKnnn.F4.XMIT Cataloged procedurelibrary

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 controlstatement used forpackaging SYSMODfor the copy groupaccess controlfunction (extendedaccess controlfunction)

Optional

12 HITACHI.CHYKbbb.SMPMCS.XMIT SMP/E controlstatement used forpackaging SYSMODfor a specificcommand accesscontrol function(extended accesscontrol 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 ModificationIdentifier) required for installation by SMP/E.


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

Planning DASD storage attributesThis section lists distribution libraries (DLIB) and target libraries, and explainsthe DASD storage attributes required for Business Continuity Managerinstallation.

About distribution libraries (DLIB)

The following table shows the DASD storage attributes required fordistribution 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, variablelength 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


#: The dd name specified in the sample job HDSYK1AL (see HDSYK1AL(allocating distribution and target libraries) on page A-10). The name ofeach dataset is the one specified in each DD statement.

About target libraries

The following table shows the DASD storage attributes required for targetlibraries.

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, variablelength 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 ofeach dataset is the one specified in each DD statement. In this manual, a dd-name library indicates a library type.

Designing storageOperating Business Continuity Manager entails calculating the amount ofdevice capacity and memory that you require and planning accordingly.


Required device capacity for BCM log data

Estimate the amount of BCM log data as follows, according to the log outputdestination.

For details about the ISPF log, see the Hitachi Business Continuity ManagerUser Guide.

When the system logger service is not used

The following table shows the amount of data when BCM logs are outputwithout the system logger service being used (when LOGPUT=SAM).

Table 2-5 Amount of BCM log data when the system logger service is notused

Type of BCM log data Size#1 Items percommand

Messages (excluding those output fromthe ISPF panel, or scripts)

100 + message-length#2

number-of-messages-output

Parameter information for the channelcommand words of the I/O, only whenan I/O error occurs

100 + CCW-length#3 number-of-times-an-I/O-error-occurred

I/O return information, only when anI/O error occurs

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

Sense byte information, only when anI/O error occurs


Timestamps 128 2

Command parameter information 256 1

#1: BCM logs are output with a specified value of this size, rounded up by afactor 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 bytesor less otherwise.

When the system logger service is used

The following table shows the amount of log data output when the systemlogger service is used for BCM log output (for LOGPUT=LOGR).

Table 2-6 Amount of log data output when the system logger service isused


Messages (excluding those output fromthe ISPF panel, or scripts)

68 + message-length#2 number-of-messages-output



Parameter information for the channelcommand words of the I/O, only whenan I/O error occurs

68 + CCW-length#3 number-of-times-an-I/O-error-occurred

I/O return information, only when anI/O error occurs


Sense byte information, only when anI/O error occurs


Timestamps 96 2

Command parameter information 224 1

#1: BCM logs are output with a specified value of this size, rounded up by afactor 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 bytesor 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 ofBCM log data after offload.

• For external datasets (OUTLOG):Estimate the disk capacity based on the save period, and the amount ofBusiness Continuity Manager log data after offload. For details about theformat for external datasets (OUTLOG), see the Hitachi Business ContinuityManager User Guide.

Determining required memory

The following indicates the required memory necessary to run BusinessContinuity 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:


4,000 KB + (1 number-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) KBnumber-of-volumes: Total number of volumes in the device addressdomain to be used. If multiple copy groups are used, the sum of thevolumes in each copy group.number-of-copy-pairs: Number of copy pairs in the copy group definitionfile to be used.number-of-copy-pairs-to-be-created: Number of copy pairs to be createdby using the YKIMPORT command.number-of-BASEGROUP-copy-pairs: Number of copy pairs in the copygroup definition file to be based on.number-of-volumes-to-be-scanned: Total number of volumes included inthe range to be scanned by YKBTSCAN.number-of-scanned-volumes: Total number of volumes in the diskconfiguration definition file if YKBTSCAN is executed to add volumes to anexisting disk configuration definition file.

A B : Indicates that the result of A B is rounded up to the nearestinteger.

The memory required when linking with Replication Manager is shown below.The PREFIX parameter and DEVN parameter in the formula below are theinitialization 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


• 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 ManagerTo transmit the Business Continuity Manager load module from the CD-ROMto 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 hostmachine:

¢ 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 modificationexamples, see Appendix A, Modifying sample JCL on page A-1.

4. Create space for the datasets to be transferred (execute the editedALLOUPLD job).The ALLOUPLD job creates the sequential dataset space for transferringthe 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 tothe host machine.From the PC, in binary mode, transfer the Business Continuity Managerobject archive (that you created in step 4) to the sequential dataset spaceon the host machine.For details about the archive files to be transmitted, see Table 2-1 Filesprovided 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 installationenvironment, and extract the dataset provided from the archivestransmitted 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 asdescribed in section Installing Business Continuity Manager with SMP/E on


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

Installing Business Continuity ManagerBusiness Continuity Manager installation involves multiple steps. Use SMP/Eor simple installation to complete an installation.

To install the extended access control function, you need to use SMP/E forinstallation. For details about the extended access control function, see theHitachi Business Continuity Manager User Guide.

Installing Business Continuity Manager with SMP/EThese sample JCL library members that are installed with SMP/E must bemodified in accordance with the user installation environment. Details areshown at the beginning of each sample JCL. For modification examples, seeAppendix 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 partvaries depending on the version) after the procedure in section Preparationsfor installing Business Continuity Manager on page 2-9 is performed. If youchange the RECVUPLD job and the output destination dataset name for theTSO/E RECEIVE command, the sample JCL is stored in the dataset after thechanges.

JCL member names and their functions are listed below. To install theBusiness Continuity Manager product with SMP/E, execute the sample jobsbelow in the following order:

1. SMPALLOCAllocate the SMP/E control dataset as necessary. If an existing SMP/Econtrol 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. HDSYK1ALAllocate the distribution library (DLIB) and the target library. Whenupgrading Business Continuity Manager, if an existing SMP/E controldataset 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. HDSYK2DFExecute SMP/E DDDEF to define the distribution library (DLIB) and targetlibrary. When upgrading Business Continuity Manager, if an existingSMP/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.

4. HDSYK3RC


Execute SMP/E RECEIVE to load the provided datasets and store them inthe global zone.For examples of modifying sample JCL (HDSYK3RC), see HDSYK3RC(SMP/E RECEIVE processing) on page A-15.

5. HDSYK4APExecute SMP/E APPLY to install the provided dataset in the target library(the library shown in Table 2-4 DASD storage attributes for targetlibraries on page 2-5).The APPLY command in the sample JCL specifies the CHECK operand. Ifexecution with the CHECK operand does not generate an error, delete theCHECK operand and re-execute the job. When upgrading BusinessContinuity Manager, if the dataset is to be installed in an existing targetlibrary, 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. HDSYK5ACExecute SMP/E ACCEPT to install the provided dataset in the distributionlibrary (the library shown in Table 2-3 DASD storage attributes fordistribution libraries (DLIB) on page 2-4).The ACCEPT command in the sample JCL specifies the CHECK operand. Ifexecution with the CHECK operand does not generate an error, delete theCHECK operand and re-execute the job. When upgrading BusinessContinuity Manager, if the dataset is to be installed in an existing targetlibrary, 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 ofBusiness Continuity Manager is installed. Verify that this new release ofBusiness Continuity Manager executes correctly and then accept it byexecuting the HDSYK5AC job.To install the extended access control function, perform the followingsteps.

7. HDSYK6RCExecute SMP/E RECEIVE for the extended access control function to loadthe 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 pageA-20.

8. HDSYK7APExecute SMP/E APPLY for the extended access control function to installthe provided dataset in the target library (the library shown in Table 2-4DASD storage attributes for target libraries on page 2-5).


The APPLY command in the sample JCL specifies the CHECK operand. Ifexecution with the CHECK operand does not generate an error, delete theCHECK operand and re-execute the job.For examples of modifying sample JCL (HDSYK7AP), see HDSYK7AP(creating target libraries for extended access control function) on pageA-22.

9. HDSYK8ACExecute SMP/E ACCEPT for the extended access control function to installthe provided dataset in the distribution library (the library shown in Table2-3 DASD storage attributes for distribution libraries (DLIB) on page 2-4).The ACCEPT command in the sample JCL specifies the CHECK operand. Ifexecution with the CHECK operand does not generate an error, delete theCHECK operand and re-execute the job.For examples of modifying sample JCL (HDSYK8AC), see HDSYK8AC(creating distribution libraries for extended access control function) onpage 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 directlyfrom the provided dataset to the target library.

Members of the sample JCL library being installed must be changed accordingto the user's installation environment. Details are shown at the beginning ofeach sample JCL. For modification examples, see Appendix A, Modifyingsample 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 partvaries depending on the version) after the procedure in section Preparationsfor installing Business Continuity Manager on page 2-9 is performed. If theRECVUPLD job is changed and the output destination dataset name for theTSO/E RECEIVE command is changed, the sample JCL is stored in the datasetafter the changes.

JCL member names and functions are shown below. The following sample JCLis executed during a simple installation.

• HDSYKSINCopies 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 environmentThis section describes how to set up a Business Continuity Managerenvironment.


The following table lists the items that must be performed to set up theenvironment. Perform these items in the order listed in the table.

Table 2-7 Items that must be performed for environment setup

Itemorder Item Description See:

1 Settings for usingCLI commands inTSO/Eenvironments

Settings needed for using CLIcommands in TSO/E environments

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

2 Settings for usingISPF panels withBusiness ContinuityManager

The YKSTART command must beconfigured to use ISPF panels withBusiness Continuity Manager.

Settings for using ISPF panels withBusiness Continuity Manager onpage 2-15

3 Settings in the ISPFpanel

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 page2-16

4 Settings for usingthe YKWATCHcommand and thecopy groupdefinitiongeneration functionfor PPRC copy pairs

YKWPROC must be configured forexecuting the YKWATCH commandand the copy group definitiongeneration function for PPRC copypairs as background jobs.

Settings for using the YKWATCHcommand and the copy groupdefinition generation function forPPRC copy pairs on page 2-17

5 Settings for usingenvironmentconfigurationcommands

Settings needed for using thefollowing environment configurationcommands:• YKALCSVC command: Registers a

user SVC.• YKSETENV command: Sets the

Business Continuity Managerenvironment variables.

• YKDSPENV command: Displaysthe Business Continuity Managerenvironment variables.

Settings for using environmentconfiguration commands on page2-17

6 Setting security Security settings for environmentconfiguration commands, CLIcommands, and datasets

Setting the security on page 2-18

7 Registering a userSVC

User SVC registration# Setting the security on page 2-18

8 Setting BusinessContinuity Managerenvironmentvariables

Setting the environment variablesrequired for Business ContinuityManager operation.#

Setting Business Continuity Managerenvironment variables on page2-26

9 Registering alicense

Registering a license key to enablethe corresponding functionality.

Registering a license on page 2-34


Itemorder Item Description See:

10 Verificationprocedure followinginstallation andsetup

Verify that the installation andenvironment setup have beenperformed correctly.

Verification procedure followinginstallation and setup on page 2-39

#Business Continuity Manager shares a User SVC, environment variables,and system symbols, with Tiered Storage Manager for Mainframe andMAR. Therefore, you need to take this into consideration in environmentsin which Tiered Storage Manager for Mainframe or MAR is installed. Fordetails, see Notes on system setup when a related product is installed onpage 2-45.

Settings for using CLI commands in TSO/E environmentsBusiness Continuity Manager provides TSO/E commands such as YKBLDCMD,YKMAKE and YKSUSPND. These commands require access to services grantedon MVS in order to perform I/Os to offline devices.

To allow access and to make these commands available in a TSO/Eenvironment:

1. Concatenate the HDSYLNKT library (the load library where CLI commandsare stored) to LNKLST.The library can be concatenated via either of the following:

¢ Add the HDSYLNKT library to the PROGxx parmlib member as a dataset to be concatenated to LNKLST.

¢ Use the SETPROG LNKLST command to dynamically concatenate toLNKLST.For details on the SETPROG command, see the IBM manual MVSSystem 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 dataset to be authorized as APF.

¢ Use the SETPROG APF,ADD command to dynamically register APFauthorization.For details on the SETPROG command, see the IBM manual MVSSystem Commands.

Note: LNKLST has APF authorization by default. For this reason, you donot have to perform step 2 if the HDSYLNKT library was concatenated toLNKLST in step 1. Note that there are exceptions to this rule as well. Fordetails on APF authorization related to LNKLST, see the IBM manual MVSInitialization and Tuning Reference.


3. Register the CLI command name YKCONMSG to the AUTHCMD section ofthe IKJTSOxx parmlib member.Once this update is complete, TSO/E can be updated dynamically usingthe TSO/E PARMLIB CHECK(nn) and PARMLIB UPDATE(nn) commands. Seethe IBM manual TSO/E System Programming Command Reference.

Settings for using ISPF panels with Business Continuity ManagerYKSTART is a REXX script that provides an ISPF panel interface. Executing theYKSTART 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 ddname SYSEXEC.

¢ If the library that is concatenated to the dd name SYSEXEC is a fixedlength format (RECFM=FB), concatenate to the REXX Exec libraryHDSYEXET.

¢ If the library that is concatenated to the dd name SYSEXEC is avariable length format (RECFM=VB), concatenate to the REXX Execlibrary 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 nameISPMALT) as well. For details, see the IBM manual ISPF User's GuideVolume 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 targetlibraries on page 2-5 and those of the datasets to be concatenated. Forexample, if DSORG=PO and RECFM=FB, LRECL must be the same in allthe datasets. For details, see the IBM manual DFSMS: Using Data Sets.For details on how to change RECFM and LRECL, refer to the informationon IEBGENER and IEBCOPY in the IBM manual DFSMSdfp Utilities.Once configured, YKSTART can be started by selecting 6 Command in theISPF Primary Option Menu and is included as a selection in each site-specific selection menu.


Starting YKSTART dynamically

You can start YKSTART by dynamically concatenating the libraries required toexecute YKSTART.

• The REXX Exec library HDSYEXET or HDSYEXVT can be dynamicallyconcatenated by the ALTLIB command of TSO/E.

• The panel library HDSYPNLT, message library HDSYMSGT, and tablelibrary HDSYTABT can be dynamically concatenated by the LIBDEF serviceof ISPF.

The example below shows how to use the ALTLIB command and LIBDEFservice.

By executing the REXX script below during ISPF startup, you can startBusiness Continuity Manager with individual libraries being dynamicallyconcatenated 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) aswell. Also, concatenate HDSYMSGT to the alternate message library (dd nameISPMALT). 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 thetop 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.


2. To display the command line at the top of panels, clear the Commandline at bottom checkbox. To display the command line at the bottom ofpanels, 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 inthe 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 commandline, 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, theF17=DispConf and F18=Exctg keys are not displayed.

Settings for using the YKWATCH command and the copy groupdefinition generation function for PPRC copy pairs

The YKWATCH command and the copy group definition generation function forPPRC copy pairs are executed as background jobs. YKWPROC is the procedurefor a background job of YKWATCH and of the Copy Group Definition GenerationFunction for PPRC copy pairs. To use the YKWATCH command or the CopyGroup Definition Generation Function for PPRC copy pairs, specify the JCL ofthe 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 nameIEFPDSI in the MSTJCLxx parmlib member.

• Copy the YKWPROC member from the cataloged procedures libraryHDSYPRCT to a user PROCLIB.

Note: Modify the dataset names in this procedure according to the namesused for the target library HDSYLNKT and HDSYEXET.

Settings for using environment configuration commandsThe following table lists the functions of the environment configurationcommands.

Table 2-8 Environment configuration commands and their functions

Command name Function

YKALCSVC Registers the user SVC.

YKSETENV Sets the following environment variables:


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 Managerenvironment variables and the program product name.

To use environment configuration commands, perform one of the proceduresbelow. Before performing either procedure, perform the procedure describedin section Settings for using CLI commands in TSO/E environments on page2-14.

• Link the HDSYPRCT cataloged procedure library to the IEFPDSI dd name ofthe MSTJCLxx parmlib member.

• Copy the YKALCSVC member, YKSETENV member, and YKDSPENV memberfrom the HDSYPRCT cataloged procedure library to the user's PROCLIB.

Once you have added these commands in the COMMNDxx parmlib member, it isautomatically 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 byusing the RACF program control function. Note that you do not need torestrict user access for the YKDSPENV command. For details, see the IBMmanual Security Server RACF Security Administrator's Guide. If you use theYKALCSVC or YKSETENV command without restricting user access, BusinessContinuity 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 batchscanning) as a basic access control function. Therefore, to use thesecommands and functionality, you must set up the RACF. Users can use thesefunctions once profiles have been defined for the RACF FACILITY class, andonce READ permissions for these profiles have been set to the users'accounts.

For details about the extended access control function, see the HitachiBusiness 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 theFACILITY class and available functions.


Table 2-9 Correspondence between profiles defined in the FACILITY classand 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)

YKAGENTDYKBTSCAN

YKEWAIT command

YKFCSTAT command

YKH2B command

YKQEXCTG command

YKQHPATH command


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 theaccess 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 onrecovery 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 theuser on page 2-22.

Setting security when the extended access control function is installed

When the extended access control function (copy group access controlfunction, specific command access control function) is installed in InstallingBusiness Continuity Manager with SMP/E on page 2-10, you need to set theaccess control (RACF settings). After defining the profile to the RACFFACILITY class, set the READ permission for that profile to the user.

This section describes about the profile types to be defined in the FACILITYclass and how to set the READ permission for the profile. For details on howto design the access permissions, such as which READ permission for theprofile is to be set to which user's account, see "Extended access controlfunctions" in the Hitachi Business Continuity Manager User Guide.

Profiles to be defined to the FACILITY class used by the extendedaccess control function

The following table shows the profiles to be defined to the FACILITY classused by the extended access control function:

Table 2-10 Profiles to be defined to the FACILITY class used by theextended access control function

Extended access controlfunction Profiles to be defined to the FACILITY class

Copy group access controlfunction

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 accesscontrol 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: Prefix for the configuration file namecopy-type: SI, TC, TCA, or URcopy-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, seeProcedure for setting the READ permission for the RACF profile to the user onpage 2-22.

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.YKQUERY1. 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 ContinuityManager, we recommend that you enable the RACLIST function (in-storageprofiles) 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 aprofile, and how to assign READ permissions for profiles to user accounts, seethe 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 aSystem REXX environment. To start a System REXX environment, you mustset 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 theREAD permissions for these profiles to users. For details, see the IBM manualMVS Programming: Authorized Assembler Services Guide.

Configuring dataset security

The Business Continuity Manager configuration file is created and savedbased on the prefix value of the user-provided dataset name. Once thestorage manager has decided on a prefix value, a data security mechanismmust be implemented to control the READ and WRITE permissions, dependingon the TSO/E user's storage management role.

Registering a user SVCYou 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 mustreload the system (that is, perform an initial program load (IPL)). If youcannot perform a re-IPL while the system is running, use the YKALCSVCcommand 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 255.3. Link the HDSYLPAT library to LPALST, using one of the following methods:

¢ Define the HDSYLPAT library in the LPALSTxx parmlib member. Fordetails, 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 parmlibmember.

SVCPARM SVC-number,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 MVSInitialization and Tuning Reference.

Caution: If you perform a new installation of Business Continuity Manager inan environment in which Tiered Storage Manager for Mainframe or MAR isinstalled, you need to be careful when registering a user SVC. For details, seeNotes on user SVC registration when a related product is installed on page2-45.

Using the YKALCSVC command to register

To register a user SVC, execute the YKALCSVC command when the systemstarts or before you use Business Continuity Manager.

YKALCSVC command format

The following shows the formats of the YKALCSVC commands. For detailsabout command formats, see Appendix E, Conventions in syntax explanationson page E-1.

FormatSTART YKALCSVC[,PARM='{SVC-number | DELETE}']

FunctionRegisters or deletes a user SVC.

Parameters

SVC-number <numeric characters> ~ ((200 to 255))Specifies a SVC number to assign to a user SVC.

DELETESpecified to delete a user SVC.

If you omit the optional PARM= part of the command, an unused SVCnumber between 200 and 255 is assigned.

Return codes

Table 2-11 YKALCSVC command return codes list

Return code Meaning

0 The command ended normally.


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 orexecution 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 SVCnumber specified here.

By omitting the PARM parameter, an unused SVC number between 200 and255 is assigned.

START YKALCSVC

To delete a user SVC, specify DELETE as the parameter and execute YKALCSVCcommand.

START YKALCSVC,PARM='DELETE'

Note:

• If you delete a user SVC using the YKALCSVC command while BusinessContinuity Manager is running, CLI commands that are being executedterminate abnormally.

• If you use the YKALCSVC command to register a user SVC while BusinessContinuity Manager is running, CLI commands that are being executedwill use the user SVC defined by the IEASVCxx parmlib member. Theregistered user SVC will take effect the next time a CLI command isexecuted.

• The user SVC registered with YKALCSVC command is lost when an IPL isperformed. Before you perform another IPL, we recommend you specifyone of the following settings:-Add the YKALCSVC command to the COMMNDxx parmlib member; so thatthe user SVC is automatically registered each time an IPL is performed.-Define the user SVC in the IEASVCxx parmlib member, and then use theuser SVC that is registered at the next IPL.

• The user SVC routine registered with the YKALCSVC command of BusinessContinuity Manager 5.1 or later cannot be deleted by using a YKALCSVCcommand of Business Continuity Manager earlier than version 5.1. So, becareful when you perform an upgrade in an environment where multipleversions are used.


• If you perform a new installation of Business Continuity Manager in anenvironment in which Tiered Storage Manager for Mainframe or MAR isinstalled, you need to be careful when registering a user SVC. For details,see Notes on user SVC registration when a related product is installed onpage 2-45.

Setting Business Continuity Manager environment variablesBefore starting Business Continuity manager, use the YKSETENV command toset Business Continuity Manager environment variables.

A re-IPL will invalidate Business Continuity Manager environment variablesset using the YKSETENV command. Therefore, we recommend that you useone of the following methods to automatically set Business ContinuityManager 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 environmentvariables.

After setting the Business Continuity Manager environment variables, use theYKDSPENV command to verify that they have been specified correctly.

For details about the YKSETENV command format, see YKSETENV commandformat on page 2-31. For details about the YKDSPENV command format, seeYKDSPENV command format on page 2-33.

The following table describes the Business Continuity Manager environmentvariables that can be set, their meanings, their corresponding system symbolnames, and their default values.

Table 2-12 Business Continuity Manager environment variables that canbe set

BusinessContinuityManager

environmentvariable

Meaning Corresponding systemsymbol names Default value

YKCMDIF Host ID &YKCMDIF 00YKLCNSEYKLCNS2

Prefix of the licenseinformation dataset

&YKLCNSE and &YKLCNS2 HITACHI#1

LOGPUT Whether the systemlogger service#2 isused

&YKLOGPT LOGR: Uses thesystem loggerservice

SYSLOG Whether CLIcommand-executionlogs are output toSYSLOG or theconsole

&YKSYSLG YES: Outputs CLIcommand-execution logs toSYSLOG


#1: For details about the relationship between the prefix of the licenseinformation dataset and the specification status for the YKSETENV commandor IEASYMxx parmlib member, see section Naming for license informationdatasets on page 2-37.

#2: For details about the system logger service, see the Hitachi BusinessContinuity Manager User Guide.

Alternatively, you can define the corresponding system symbols in theIEASYMxx parmlib member and then perform a re-IPL of the system to setvalues for the Business Continuity Manager environment variables. If youcannot perform the re-IPL because the system is running, use the YKSETENVcommand to set environment variables.

The priority order for specifying values is as follows:

1. value-specified-by-the-YKSETENV-command2. value-specified-for-the-IEASYMxx-parmlib-member3. default-value

If the YKSETENV command is executed without specifying parameters, thecorresponding system symbol values are used as the Business ContinuityManager environment variables. If no value is specified for the YKSETENVcommand parameters and the corresponding system symbols, the defaultvalues are used as the Business Continuity Manager environment variables.

The following sections provide examples of configuring the environment. Fordetails about how to specify the prefixes for license information datasets, seesection Naming for license information datasets on page 2-37.

Note: If you use the YKSETENV command to set Business Continuity Managerenvironment variables, perform the procedure described in section Settingsfor using CLI commands in TSO/E environments on page 2-14.

Specifying the host ID

When the Remote DKC Control Function is being used, if you want to makemultiple hosts (OSs) on the same site use Business Continuity Manager andshare one command device in a storage system, specify the host IDs. If thereis only one host (OS) on the site, or you do not make multiple hosts shareone 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 isunique for each OS. In an LPAR environment, specify a different number foreach LPAR.

The examples below show how to specify a host ID. If neither (a) nor (b) isspecified, 00 is assumed.

Using the YKSETENV command

The following example sets the host ID to 0F:


START YKSETENV,PARM='YKCMDIF=0F'

Note: If you register or change a host ID while Business Continuity Manageris 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 YKLOADcommand (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 ContinuityManager logs to be output to an external dataset (using the system loggerservice), or to be output to a sequential dataset (without using the systemlogger service).


The following shows an example of defining a symbol when you do not wantto use the system logger service:

START YKSETENV,PARM='LOGPUT=SAM'

The following shows an example of defining a symbol when you do want touse the system logger service:

START YKSETENV,PARM='LOGPUT=LOGR'

Caution:

• If you use the YKSETENV command to change the BCM log outputdestination while Business Continuity Manager is running, BusinessContinuity Manager will be run using the previously set value. The changewill take effect when you log on to the TSO/E terminal again.

• The LOGPUT environment variable is shared by Business ContinuityManager, Tiered Storage Manager for Mainframe, and MAR. Therefore,you need to be careful when setting the LOGPUT environment variable inan environment in which Tiered Storage Manager for Mainframe or MAR isinstalled. For details, see Notes on setting environment variables orsystem symbols when a related product is installed on page 2-45.


Define the system symbol &YKLOGPT for the IEASYMxx parmlib member. Aftermaking the definition, enable the setting by re-performing the IPL of thehost.


The following shows an example of defining a symbol when you do not wantto use the system logger service:

SYMDEF(&YKLOGPT='SAM')

The following shows an example of defining a symbol when you do want touse 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 ContinuityManager, Tiered Storage Manager for Mainframe, and MAR. Therefore, youneed to be careful when setting the &YKLOGPT system symbol in anenvironment in which Tiered Storage Manager for Mainframe or MAR isinstalled. For details, see Notes on setting environment variables or systemsymbols when a related product is installed on page 2-45.

Specifying whether to output CLI command-execution logs

The following specification examples show how to specify whether to outputCLI command-execution logs to SYSLOG or the console.


The following shows an example of defining a symbol when you do not wantto output the CLI command-execution logs:

START YKSETENV,PARM='SYSLOG=NO'

The following shows an example of defining a symbol when you do want tooutput 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 tooutput the CLI command-execution logs to the console:

START YKSETENV,PARM='SYSLOG=CONSOLE'

Caution: The SYSLOG environment variable is shared by Business ContinuityManager and Tiered Storage Manager for Mainframe. Therefore, you need tobe careful when setting the SYSLOG environment variable in an environmentin which Tiered Storage Manager for Mainframe is installed. For details, seeNotes on setting environment variables or system symbols when a relatedproduct is installed on page 2-45.



The following shows an example of defining a symbol when you do not wantto output the CLI command-execution logs:

SYMDEF(&YKSYSLG='NO')

The following shows an example of defining a symbol when you do want tooutput the CLI command-execution logs to SYSLOG:

SYMDEF(&YKSYSLG='YES')

The following shows an example of defining a symbol when you do want tooutput 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 outputto the console by using ROUTCODE=11 (output as the YKZ910I message andthe YKZ911I message). Therefore, include 11 in the ROUTCODE parameter ofthe CONSOLE statement or in the ROUTCODE parameter of the HARDCOPYstatement in the CONSOLxx parmlib member.

Perform either of the following operations to change the ROUTCODE value forthe CLI command-execution log (the YKZ910I message and the YKZ911Imessage) to a value other than 11:

• In MPFLSTxx, register USEREXIT that targets the YKZ910I message andthe YKZ911I message. In the USEREXIT to be registered, change theROUTCODE value for the YKZ910I message and the YKZ911I message from11 to a different value (the value included in the ROUTCODE parameter inthe CONSOLxx parmlib member).

• Use WTO/WTOR Message Processing Facility Installation Exit (IEAVMXIT)to change the ROUTCODE value for the YKZ910I message and the YKZ911Imessage from 11 to a different value (the value included in the ROUTCODEparameter in the CONSOLxx parmlib member).

For a sample exit routine (YKUSRXIT) that changes the ROUTCODE value of theYKZ910I message and the YKZ911I message, see the sample library providedby Business Continuity Manager.

Caution: The &YKSYSLG system symbol is shared by Business ContinuityManager and Tiered Storage Manager for Mainframe. Therefore, you need tobe careful when setting the &YKSYSLG system symbol in an environment inwhich Tiered Storage Manager for Mainframe is installed. For details, seeNotes on setting environment variables or system symbols when a relatedproduct is installed on page 2-45.

Caution: For the output of CLI command-execution logs in an environmentwhere multiple versions of Business Continuity Manager exist, see Specifying


whether to output the CLI command-execution logs (SYSLOG) on pageD-3.

YKSETENV command format

The following shows the formats of the YKSETENV commands. For detailsabout command formats, see Appendix E, Conventions in syntax explanationson page E-1.

FormatSTART YKSETENV, PARM='{YKCMDIF=[host-id] | YKLCNSE=[prefix1]| YKLCNS2=[prefix2]| LOGPUT=[LOGR|SAM]| SYSLOG=[YES|CONSOLE|NO]}[,...]'

FunctionSets 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 (operatingsystems). The specified value for the host ID is given priority over the&YKCMDIF system symbol in the IEASYMxx parmlib member. If thiscommand is executed with the host ID omitted (PARM='YKCMDIF=' isspecified), 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 nameof the dataset is unique. If the prefix1 is omitted, specifyPARM='YKLCNSE='.For details about the prefix1 for the license information dataset, seesection Naming for license information datasets on page 2-37.

YKLCNS2=[prefix2] ~ <8 or fewer alphanumeric characters>Specify a prefix2 for the license information dataset so that the nameof the dataset is unique. If the prefix2 is omitted, specifyPARM='YKLCNS2='.For details about the prefix2 for the license information dataset, seesection Naming for license information datasets on page 2-37.

LOGPUT=[LOGR | SAM]Specify whether or not the system logger service is to be used, whenoutputting BCM logs.


The specified value for the LOGPUT parameter is given priority over the&YKLOGPT system symbol in the IEASYMxx parmlib member. If thiscommand is executed with the LOGPUT parameter omitted(PARM='LOGPUT=' is specified), the value of the &YKLOGPT systemsymbol 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]Specify whether or not CLI command-execution logs are output toSYSLOG or the console.The value specified for the SYSLOG parameter is given priority over the&YKSYSLG system symbol in the IEASYMxx parmlib member. If thiscommand is executed with the SYSLOG parameter omitted(PARM='SYSLOG=' is specified), the value of the &YKSYSLG systemsymbol 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 anenvironment where multiple versions of Business Continuity Managerexist, see Specifying whether to output the CLI command-executionlogs (SYSLOG) on page D-3.

Return codes

Table 2-13 YKSETENV command return codes list

Return code Meaning

0 Successful completion.

4 The specified value is incorrect. Another value was used forexecution.

8 The specified value is incorrect. Processing was cancelled.

12 Processing was cancelled due to a system error (such as aGETMAIN error).

16 An internal error occurred.

Note: For parameters, you can specify multiple items within the allowablelength for PARM. If more than one of the same parameter is specified, thelatter one will take effect.


YKDSPENV command format

The following shows the formats of the YKSETENV commands. For detailsabout command formats, see Appendix E, Conventions in syntax explanationson page E-1.

FormatSTART YKDSPENV, [PARM='[SUMMARY|DETAIL]']

FunctionDisplays the program product name and the Business Continuity Managerenvironment variables on the OS console.

Parameters

SUMMARYDisplays the program product name and values of the BusinessContinuity Manager environment variables.

DETAILDisplays the program product name, values of the Business ContinuityManager environment variables, values set by using the YKSETENVcommand, and values set by using system symbols.

Return codes

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 isexecuted assuming SUMMARY is input.

In the following example, the YKDSPENV command is executed. The versionpart in this example varies depending on the version.

Execution example 1

START YKDSPENVYKT403I Hitachi Business Continuity ManagerYKT400I BC Manager environment variables (version)YKT401I Host ID: 00YKT401I License info DSN prefix: HITACHIYKT401I BCM log output method: LOGRYKT401I CLI log output settings: YES

Execution example 2

START YKDSPENV,PARM='DETAIL'YKT403I Hitachi Business Continuity ManagerYKT400I BC Manager environment variables (version)YKT401I Host ID: 01YKT401I License info DSN prefix: HTC1.BCMYKT401I BCM log output method: SAMYKT401I CLI log output settings: NO


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 licenseWhen you register a license, the corresponding functionality becomesavailable.

Use either of the following methods to install a license key in the licenseinformation 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.

Figure 2-2 Overview of license registration

Using the license key file

With this method, you transfer the obtained license key file to MVS and usethe Manage Licenses panel to register the license. For details about the panelused for the following procedure, see the Hitachi Business Continuity ManagerReference Guide.

To use the license key file:

1. Create a license information dataset.


For details on the license information dataset attributes, see sectionFormat for license information datasets on page 2-36. For details onlicense information dataset names, see section Naming for licenseinformation datasets on page 2-37.

2. Transfer the license key file to the host.Perform file transfer from the license key file to the MVS dataset (calledthe license key dataset) in the following format:

¢ ASCII mode¢ Encoded (to EBCDIC)Assign the following attributes to the license key dataset in which thelicense key file is stored:

¢ Dataset format: VB or FB sequential dataset¢ Record length: 200 bytes or greater¢ Block size: optionalThe file transfer destination is assumed to be a license key dataset namedBCM.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 Namefield and press Enter.The license keys are read from the license key file and are installed in thelicense 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 beeninstalled correctly.

Tip: If the license key file contains the license key for Tiered StorageManager 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 panelto install the license. For details about the panel used in the followingprocedure, 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, seesection Format for license information datasets on page 2-36. For detailsabout license information dataset names, see section Naming for licenseinformation datasets on page 2-37.

2. Start Business Continuity Manager.3. Display the Main Menu panel and select 2 Manage Licenses.


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 licensekey.The YK9001I message is output if the license key is installed correctly.

5. Use the Manage Licenses panel to confirm that the licenses have beeninstalled correctly.

Tip: If you enter the key code for Tiered Storage Manager for Mainframe inthe Manage Licenses panel, the license key for Tiered Storage Manager forMainframe 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 Manager05-03 or earlier.

• Do not delete the license information dataset. Business ContinuityManager 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 informationdataset. Doing so may result in Business Continuity Manager becominginoperable.

• If the specified license key is invalid, all or part of Business ContinuityManager will not be available. Make sure that you enter the correctlicense key.

• If an I/O error occurs in the license dataset, it is assumed that no licensekey exists.

• If you use the YKSETENV command to set or change the licenseinformation dataset name while Business Continuity Manager is running,CLI commands that are being executed will be executed using thepreviously set value. The set or updated license information dataset namewill 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:


¢ 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 theinstallation 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.LICENSEA prefix of the license information dataset consists of prefix1 and prefix2. Thelength 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 theIEASYMxx parmlib member.

The following lists the priority for specified values, in descending order:

1. value-specified-by-the-YKSETENV-command2. value-specified-for-the-IEASYMxx-parmlib-member3. default-value (HITACHI)

The method for specifying a value in the IEASYMxx parmlib member requiresa re-IPL of the system. If a re-IPL cannot be executed because the system isrunning, use the YKSETENV command to specify a value.

Note: If you use the YKSETENV command to set Business Continuity Managerenvironment variables, perform the procedure described in section Settingsfor using CLI commands in TSO/E environments on page 2-14.


Execute the YKSETENV command to set the Business Continuity Managerenvironment variables (YKLCNSE and YKLCNS2). For details about the format


for the YKSETENV command, see section YKSETENV command format on page2-31.

The following example names the license information datasetHTC1.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. IfYKLCNS2 is omitted, the value of the &YKLCNS2 system symbol is used. TheYKLCNS2 value becomes valid when a value is specified in either YKLCNSE or&YKLCNSE.

Note: A re-IPL will invalidate the Business Continuity Manager environmentvariables registered with the YKSETENV command, that is, they return to thedefault or the value of the system symbol &YKLCNSE and &YKLCNS2. Werecommend that you perform the either of the following settings for the nextre-IPL:

• Add the YKSETENV command to the COMMNDxx parmlib member to set theBusiness Continuity Manager environment variables again automaticallyby re-IPL.

• Define the prefix value in the system symbol &YKLCNSE and &YKLCNS2 ofthe IEASYMxx parmlib member, and use this prefix value, which will beregistered at the next IPL.

Caution: The environment variables YKLCNSE and YKLCNS2 are shared byBusiness Continuity Manager and Tiered Storage Manager for Mainframe.Therefore, you need to be careful when setting the environment variablesYKLCNSE and YKLCNS2 in an environment in which Tiered Storage Manager forMainframe is installed. For details, see Notes on setting environmentvariables or system symbols when a related product is installed on page2-45.


Define the system symbol &YKLCNSE and &YKLCNS2 for the IEASYMxx parmlibmember. After the definition, enable the setting by re-IPL of the host.

The following example names the license information datasetHTC1.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 byBusiness Continuity Manager and Tiered Storage Manager for Mainframe.Therefore, you need to be careful when setting the system symbols &YKLCNSE


and &YKLCNS2 in an environment in which Tiered Storage Manager forMainframe is installed. For details, see Notes on setting environmentvariables or system symbols when a related product is installed on page2-45.

The following table shows the relationship between the prefix of the licenseinformation dataset name and the specification status for the YKSETENVcommand or IEASYMxx parmlib member:

YKSETENV command IEASYMxx parmlibmember Prefix

YKLCNSE YKLCNS2 &YKLCNSE &YKLCNS2

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 installationand setup of Business Continuity Manager concludes, Business ContinuityManager cannot be used. You can use either of the following methods tocheck whether all installation and setup processes have completed properly:

• Check the execution result of the YKINSCHK command.


• Check the information displayed in the Installation Verification Summarypanel.

If some installation or setup tasks have not completed, follow the providedinstructions to complete them.

The following JCL execution example outputs the execution result of theYKINSCHK command to dd-name SYSTSPRT. If the job terminates with areturn code other than 0, check the execution result that is output toSYSTSPRT.//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 tothe Installation Verification Summary panel, see the Hitachi BusinessContinuity Manager Reference Guide.

Checking the access permissions when the extended access control function isinstalled

When the extended access control function is installed, operations to the copygroups and the execution of a specific command cannot be performed unlessthe READ permissions of the RACF FACILITY class for the profiles are set. Usethe sample script (HDSRFEPR) to check which profiles of the READpermissions are set. For details about the sample scripts (HDSRFEPR), seeHDSRFEPR (viewing access permissions for the extended access controlfunction) on page B-2.

Upgrading Business Continuity ManagerThis section explains how to upgrade Business Continuity Manager. For noteson performing an upgrade installation, see the Appendix C, Notes onupgrading 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 ofBusiness Continuity Manager exist on page D-1 before starting the upgradeprocess.


What to check before upgrading

Checking licenses

For Business Continuity Manager 5.5 or later, you cannot use license keysobtained for Business Continuity Manager 5.3 or earlier. You must obtain alicense key for Business Continuity Manager version 5.5 or later.

Checking environment variables

The following table lists the Business Continuity Manager environmentvariables that are used when you perform an upgrade installation. Check thesettings for these environment variables before you upgrade.

Table 2-15 Business Continuity Manager environment variables to bechecked before upgrading

Parameter name Description

YKCMDIF Host ID

YKLCNSE Prefix of the license information dataset

YKLCNS2LOGPUT Business Continuity Manager log output method

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

When the Business Continuity Manager version before upgrading is 5.1 orlater, you can use the YKDSPENV command to check the values of theBusiness Continuity Manager environment variables. For details about theYKDSPENV command, see section YKDSPENV command format on page 2-33.

The following table lists the system symbols that are used when you performan upgrade installation. Check the settings for these system symbols beforeyou upgrade.

Table 2-16 System symbols to be checked before upgrading (BusinessContinuity Manager environment variables)

System symbol name Description

&YKCMDIF Host ID

&YKLCNSE Prefix of the license information dataset

&YKLCNS2&YKLOGPT Business Continuity Manager log output method

&YKSYSLG Whether CLI command-execution logs are to be output toSYSLOG or the console


Checking the user SVC number

Check the user SVC number because you must assign the same number afterupgrading. The method of checking the user SVC number varies dependingon whether the user SVC was registered with the YKSETENV command or theIEASVCxx parmlib member.

• When the user SVC was registered by using the YKSETENV commandCheck the value (user SVC number) specified in the YKALCSVC commandparameter because you will use this value during an upgrade installation.

• When the user SVC was registered by using the IEASVCxx parmlibmemberCheck the value set for the system symbol in the following table.

Table 2-17 System symbol to be checked before upgrading (user SVCnumber)

System symbol name Description

&YKSVCNO 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 datasetname, the consistency between the files is lost, and then Business ContinuityManager might become inoperable.

For details about configuration files, see the Hitachi Business ContinuityManager Reference Guide.

Backing up the program before migration

Before migration, acquire a backup of the dataset where Business ContinuityManager will be installed.


Pre-upgrade procedure

Deleting the user SVC

If the version of the user SVC which is in effect in the current system is olderthan the version required after upgrading Business Continuity Manager, youmust delete the user SVC before you install the new version of BusinessContinuity 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 usethe YKALCSVC command to delete the user SVC.

If the user SVC was registered by using the IEASVCxx parmlib member, youcannot 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 parmlibmember:

1. Disable (comment out) the SYMDEF statement containing the &YKSVCNOsystem symbol in the IEASYMxx parmlib member.

/* SYMDEF(&YKSVCNO='SVC-number') */

2. Disable (comment out) the SVCPARM statement containing the JYUASVCmodule 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 andTuning Reference.

Caution: Business Continuity Manager, Tiered Storage Manager forMainframe, and MAR share a user SVC. Therefore, if Tiered Storage Managerfor Mainframe or MAR is installed on the system, make sure that the programis not running before deleting the user SVC.

Removing the concatenation of the cataloged procedures library

Remove the dataset concatenation of the following library:

dd name Library name

IEFPDSI Cataloged procedures library HDSYPRCT

If you copied the HDSYPRCT library members to a user PROCLIB, delete thecopied members.


Removing the concatenation of the REXX Exec library and the libraries used byISPF interface

Remove the dataset concatenation of the following libraries:


SYSEXEC REXX Exec library

ISPPLIB Panel library HDSYPNLT

ISPMLIB Message library HDSYMSGT

ISPTLIB Table library HDSYTABT

In an environment in which the DBCS functionality is used, remove datasetconcatenation from the following libraries:


ISPPALT Panel library HDSYPNLT

ISPMALT 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 toLPALST.

Upgrading Business Continuity ManagerInstall the post-migration Business Continuity Manager as described insection Overview of installation on page 2-2.

If the version of the user SVC which is in effect in the current system satisfiesthe conditions placed on the version required by Business ContinuityManager, you do not need to perform Registering a user SVC on page 2-23.For versions of user SVC that are required by Business Continuity Manager,see User SVC versions required by Business Continuity Manager on page2-46.

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 alicense on page 2-34.

What to check after upgradingAfter upgrading the post-migration Business Continuity Manager, make surethat the post-upgrade settings are the same as those checked in sectionWhat to check before upgrading on page 2-41.


Notes on system setup when a related product is installedThis section provides notes on registering a user SVC and settingenvironment variables and system symbols when installing BusinessContinuity Manager or MAR in an environment in which Tiered StorageManager for Mainframe is installed.

Notes on user SVC registration when a related product is installedBusiness Continuity Manager, Tiered Storage Manager for Mainframe, andMAR share a user SVC. Therefore, you need to compare the version of theuser SVC that is registered by using Tiered Storage Manager for Mainframe orMAR and currently in effect in the system and the version of the user SVCthat is required for Business Continuity Manager, and then use the newerversion 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 theRSINSCHK command of MAR.

• If the user SVC version you checked does not satisfy the conditionsplaced on the required version (the version is older than the requiredversion):Delete the user SVC by using Tiered Storage Manager for Mainframe orMAR, and register a user SVC by using Business Continuity Manager.

• If the user SVC version you checked satisfy the conditions placed on therequired version:You can use the user SVC currently in effect in the system withoutchange.

Tip:

• For details about the user SVC versions required for Business ContinuityManager, see User SVC versions required by Business Continuity Manageron page 2-46.

• For details about the KTINSCHK command and how to delete a user SVCby using Tiered Storage Manager for Mainframe, see the Tiered StorageManager for Mainframe User Guide.

• For details about the RSINSCHK command and deleting the user SVC inMAR, see the Mainframe Analytics Recorder User Guide.

• This procedure is available when you perform a new installation ofBusiness Continuity Manager. If you upgrade Business ContinuityManager, see Deleting the user SVC on page 2-43 in Pre-upgradeprocedure on page 2-43.

Notes on setting environment variables or system symbols when arelated product is installed

Business Continuity Manager, Tiered Storage Manager for Mainframe, andMAR use the same environment variables and system symbols. Therefore, if


Tiered Storage Manager for Mainframe or MAR is running on the system, werecommend that you do not change the environment setting values(environment variables or the values set for system symbols) that arecurrently valid in the system. In particular, if you change the prefix for thelicense information dataset, you need to re-register the license for TieredStorage Manager for Mainframe because the license information dataset isshared by Business Continuity Manager and Tiered Storage Manager forMainframe. Keep this fully in mind when you need to change an environmentsetting value.

Tip: The following describes how to check the environment setting valuesthat are currently valid in the system.

• If Business Continuity Manager has been installed (upgrade):Check the environment setting values you obtained during the checkbefore upgrading. For details, see Checking environment variables onpage 2-41 in What to check before upgrading on page 2-41.

• If Business Continuity Manager has not been installed (new installation):Use the KTDSPENV command of Tiered Storage Manager for Mainframe orthe RSDSPENV command of MAR to check the values. For details on theKTDSPENV command, see the Tiered Storage Manager for Mainframe UserGuide.For details on the RSDSPENV command, see the Mainframe AnalyticsRecorder User Guide.

Notes on specifying a prefix when a related product is installedIf you want to install and use Business Continuity Manager in the samesystem as Tiered Storage Manager for Mainframe or MAR, specify a characterstring different from the prefix of Tiered Storage Manager for Mainframe orMAR as the prefix of the configuration files. If the same prefix is used, theproduct might operate abnormally.

User SVC versions required by Business Continuity ManagerThe following table lists the versions of user SVCs that are required in eachversion of Business Continuity Manager.

Table 2-18 User SVC versions required by Business Continuity Manager

Version of Business Continuity Manager User SVC version required

03-00 03-00 or later

04-00 04-00 or later

04-01 04-01 or later

04-02 04-02 or later

05-00 05-00 or later

05-01 05-01 or later


Version of Business Continuity Manager User SVC version required

05-02 05-02 or later

05-03 05-03 or later

05-05 05-05 or later

05-06 05-06 or later

06-00 06-00 or later

06-10 06-10 or later

6.2.0 6.2.0 or later

6.3.0 to 6.6.0 6.3.0 or later

6.6.1 6.6.1 or later

6.7.0 to 7.3.0 6.7.0 or later

7.4.0 7.4.0 or later

7.5.0 to 8.4.0 7.5.0 or later



3Setting up the environment whenlinking with Replication Manager

This chapter explains the environment setup when linking with ReplicationManager. It also explains how to set up port numbers, security, and IBMHTTP Server, which are all required to link to Replication Manager. Inaddition, this chapter explains how to create initialization parameters and acataloged 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 ContinuityManager agents

Setting up the environment when linking with Replication Manager 3-1Hitachi Business Continuity Manager Installation Guide

Overview of environment settingsThis section explains how to configure the environment settings that arenecessary for linking to Replication Manager.

HTTPS connections can be established between Replication Manager and theBusiness Continuity Manager agent. For details on how to establish HTTPSconnections, see Setting up HTTPS connections on page 3-15.

In addition, for details on how to set up IBM HTTP Server for establishingHTTPS connections, see the product information on the IBM WebSphereApplication Server Information Center.

Configuring the environment settings without using the Remote DKCControl Function (before Business Continuity Manager is installed)

The following figure shows the general procedure for configuring theenvironment settings starting from before Business Continuity Manager isinstalled, without using the Remote DKC Control Function.

3-2 Setting up the environment when linking with Replication ManagerHitachi Business Continuity Manager Installation Guide

Figure 3-1 Configuring the environment settings without using theRemote DKC Control Function (before Business Continuity Manager is

installed)

To configure the environment settings without using the Remote DKC ControlFunction:

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 fileFor details, see section Creating configuration file datasets on page3-9.

3. Install Business Continuity Manager.For details, see Chapter 2, Installing Business Continuity Manager onpage 2-1.


4. Configure the environment settings for the Business Continuity Manageragent.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 3-335. Start IBM HTTP Server.6. Start the Business Continuity Manager agent.

For details, see the chapter about linking the Business Continuity Manageragent to Replication Manager in the Hitachi Business Continuity ManagerUser Guide.

7. Configure the Replication Manager initialization settings.For details, see the Replication Manager User Guide.

Configuring the environment settings using the Remote DKC ControlFunction (before Business Continuity Manager is installed)

The following figure shows the general procedure for configuring theenvironment settings starting from before installation of Business ContinuityManager, using the Remote DKC Control Function.


Figure 3-2 Configuring the environment settings using the Remote DKCControl Function (before Business Continuity Manager is installed)

To configure the environment settings by using the Remote DKC ControlFunction:

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

3. Perform a Local Scan.


Perform a Local Scan to create the disk configuration definition fileneeded for setting the route list definitions.For details, see the description about using a Local Scan to acquirestorage system information in the Hitachi Business Continuity ManagerUser Guide.

4. Configure the environment settings for the Remote DKC Control Function.Configure the following settings:

¢ Route list definitions¢ Command device registrationsFor details, see the Hitachi Business Continuity Manager User Guide.

5. Create configuration file datasets.Create datasets for the following configuration files:






For details, see the chapter about linking the Business Continuity Manageragent with Replication Manager in the Hitachi Business ContinuityManager User Guide.


Configuring the environment settings in an existing environment(with Business Continuity Manager installed)

The following figure shows the general procedure for configuring theenvironment settings in an existing environment with Business ContinuityManager installed (that is, with the storage system configured, and with theenvironment set up for using the Remote DKC Control Function).


Figure 3-3 Configuring the environment settings in an existingenvironment (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 2-40.

2. Create configuration file datasets.These datasets are needed to perform a device scan and set copy groupdefinitions in Replication Manager for the first time.Create datasets for the following configuration files:




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




Configuring the environment settings to allow only monitoring ofcopy groups

The following figure shows the general procedure for configuring theenvironment settings in an existing environment to allow only monitoring ofcopy groups, without allowing copy groups to be defined or copy groupoperations to be performed.

Figure 3-4 Configuring the environment settings to allow only monitoringof copy groups

To configure the environment settings to allow only monitoring of copygroups:








Configuring the environment settings for monitoring PPRC copy pairsTo monitor PPRC copy pairs from Replication Manager, you must create aPPRC copy group definition file with Business Continuity Manager before youconfigure the environment settings for the Business Continuity Manageragent. For details, see the description about generating PPRC copy pair copygroup definitions in the Hitachi Business Continuity Manager User Guide.

Creating configuration file datasetsBefore doing anything else, you must first create datasets for the followingconfiguration files, which are created in Replication Manager. You must thencatalog 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 namesThe 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


The values that can be specified for each variable are explained below. Thevalues specified for prefix and DAD-ID must be the same as the valuespecified for the Business Continuity Manager agent initialization parameterPREFIX.

• prefix: Prefix of the configuration fileSpecify a string of 25 characters or fewer that consists of one or moreparts, joined by periods (.). Only uppercase alphabetic characters andnumeric characters can be used. Note that the string or each substringmust begin with an uppercase alphabetic character, and consist of 1 to 8characters.

• copy-group-IDSpecify a string or multiple substrings joined together by periods.Uppercase alphabetic characters, numeric characters, and specialcharacters ($, #, and @) can be used. Note that the string or eachsubstring must begin with an uppercase alphabetic characters or specialcharacter, 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 localsite

¢ 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 siteSpecify a string or multiple substrings joined together by periods.Uppercase alphabetic characters, numeric characters, and specialcharacters ($, #, and @) can be used. Note that the string or eachsubstring must begin with an uppercase alphabetic characters or specialcharacter, 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 isupdated from Replication Manager, a temporary file is created. After the file issuccessfully updated, the temporary file is deleted.

Do not create a dataset with the same name as that of a temporary file. Thefollowing 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


Dataset format and required disk capacity for the configuration fileFor details about the dataset format and the required disk capacity, see thedescriptions for the configuration file in the Hitachi Business ContinuityManager Reference Guide.

Note: When you estimate the required disk capacity, allow for no less thanthree times the disk capacity required for each dataset, to provide enoughdisk capacity for backup files and temporary files.

Setting the TCP/IP port numberBefore performing this procedure, you need to reserve a port number forcommunicating with Replication Manager.

For a job that starts Business Continuity Manager agent, set the UNIXservice's usage attributes (open a port for receiving). For details, see the IBMmanual Communications Server: IP Configuration Reference.

Set the port number in the TCP/IP environment settings file (PROFILE.TCPIPprofile, the definition file related to server functions in the TCP/IP addressspace).

In the PORT definition of the PROFILE.TCPIP profile, specify the membername or identification name of the Business Continuity Manager agent startjob. For details about the identification name, see the chapter that describesBusiness Continuity Manager agent startup in the Hitachi Business ContinuityManager User Guide.

For the port number to be used by the YKAGENT job, you cannot specify anumber that is already being used by another job. Specify a port number thatis not being used in the system.

Example of specifying the port number

The following specification sets the port number as 24042:

24042 TCP YKAGENT ;YKAGENT START NAME

Note: The Business Continuity Manager agent requires 2 sockets of IBMCommunications Server (OS standard equipment). Make sure that the totalnumber of sockets does not exceed the maximum number of sockets thatIBM Communications Server can provide, keeping in mind the number ofsockets required for other services that IBM Communications Server handles.For details about the maximum number of sockets that IBM CommunicationsServer can provide, see the IBM manual Communications Server IPConfiguration Guide.


Setting up the security for Business Continuity Manageragents

This section describes how to set the security.

Setting the dataset securityWhen a Business Continuity Manager agent is linked to Replication Manager,the Business Continuity Manager agent job references Business ContinuityManager's configuration files. Therefore, be sure to grant the BusinessContinuity Manager agent job READ permission for the configuration files thatare accessed by the Business Continuity Manager agent job. The names ofthe configuration files to which READ permission is to be granted are thefollowing datasets, which have their prefixes specified in Business ContinuityManager'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 BusinessContinuity Manager agent job. For details on dataset names, see Creatingconfiguration 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 linkingwith Replication Manager

To enable Business Continuity Manager agent communications, set anenvironment for the security program (RACF).

To enable use of UNIX services, use the RACF command from TSO/E to definethe management user and management group IDs held by the OMVSsegment in the RACF STARTED class of the Business Continuity Manager agentcataloged procedure for startup. The following is an example of using theTSO/E command with the STARTED class:

->SETROPTS GENERIC(STARTED)->RDEFINE STARTED YKAGENT.* STDATA(USER(user-ID) GROUP(group-ID))->SETROPTS RACLIST(STARTED) REFRESH


To start Business Continuity Manager agent, you need to define one of thefollowing profiles in the RACF FACILITY class, and then grant the viewpermission for the defined profile to the administrator user ID:

The profiles for which view permissions are granted to the BusinessContinuity Manager agent vary depending on whether the Business ContinuityManager agent is started in monitor mode or in edit mode. For details aboutthese startup modes, see Details of initialization parameters on page 3-22.

If the Business Continuity Manager agent is started in monitor mode, grantview permissions for the following profile:

• STGADMIN.YKA.BCM.YKQUERY profile

If the Business Continuity Manager agent is started in edit mode, grant viewpermissions for the following profile:

• STGADMIN.YKA.BCM.COMMANDS profile

Following is an example of using the TSO/E command with the FACILITYclass:

->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 commandson page 2-18 in section Setting the security on page 2-18.

Setting up IBM HTTP ServerThis section explains how to set up IBM HTTP Server in order to establishIPv6 connections or HTTPS communication, and it also explains how to collectlogs.

Settings for connecting via IPv6When Replication Manager is connected to the Business Continuity Manageragent via IPv6, IBM HTTP Server is required to act as a reverse proxy server.When the reverse proxy server receives a request from Replication Managervia IPv6, it changes the request to IPv4 format and then provides the requestto the Business Continuity Manager agent, which acts as the origin server.

The following shows a configuration example of when Replication Managerconnects to the Business Continuity Manager agent via IPv6.


Figure 3-5 Example configuration using IPv6 to connect ReplicationManager to the Business Continuity Manager agent

To set up IBM HTTP Server to run as a reverse proxy server, specify thesettings described in the following table for the httpd.conf file.

Table 3-1 Settings to be specified in the httpd.conf file for IPv6connections

Directive to bespecified Description of directive, and values to be specified

CacheDisable Specify this directive so that the cache function for requestsdirected to the Business Continuity Manager agent isdisabled.

KeepAlive Specify this directive to disable the KeepAlive function.

Listen Specify a standby port in IPv6 as shown below. The portnumber can be changed:Listen [::]:80

LoadModule Add the following modules to the list so that the reverseproxy function will be enabled:proxy_module modules/mod_proxy.soproxy_http_module modules/mod_proxy_http.so


Directive to bespecified Description of directive, and values to be specified

ProxyPass andProxyPassReverse

Specify the following options to set up Business ContinuityManager agent to act as the origin server for ReplicationManager:• 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 ContinuityManager agent

ProxyPass / http://host-name-or-IPv4-address:port-number/ProxyPassReverse / http://host-name-or-IPv4-address:port-number/

Timeout This directive is used to specify how long to wait beforeissuing a timeout.Specify a value greater than the timeout values ofReplication Manager (bcmif.socketTimeout).

Setting up HTTPS connectionsHTTPS (HTTP over SSL) connections can be established between ReplicationManager and the Business Continuity Manager agent to improve security. Toestablish HTTPS connections between Replication Manager and the BusinessContinuity Manager agent, IBM HTTP Server is required as a reverse proxyserver. A reverse proxy server uses HTTPS to receive requests fromReplication Manager, and then uses HTTP to send those requests to theBusiness 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 Managerand IBM HTTP Server is shown below:


Figure 3-6 Configuration example for HTTPS connections betweenReplication Manager and IBM HTTP Server

Use the IBM HTTP Server httpd.conf settings file to configure IBM HTTPServer.

The following table describes authentication methods used betweenReplication Manager and IBM HTTP Server.

Table 3-2 Authentication methods used between Replication Manager andIBM 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 HTTPServer, Replication Manager cannot send the information necessary forperforming basic access authentication.

An overview of the setup procedure for establishing HTTPS connections isshown in the figure below. All of the steps indicated in the figure below mustbe performed on all of the sites.


Figure 3-7 Overview of the setup procedure for establishing HTTPSconnections

The procedure to establish HTTPS connections between Replication Managerand IBM HTTP Server is described below. The number for each step in Figure3-7 Overview of the setup procedure for establishing HTTPS connections onpage 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 settingsdescribed in Table 3-3 Required settings for the httpd.conf file to set up areverse 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 reverseproxy server

Directives Values

CacheDisable Specify this directive to disable the cache function forrequests directed to the Business Continuity Manager agent.


Directives Values

KeepAlive Specify this directive to disable the KeepAlive function.

LoadModule Add the following modules to the list:proxy_module modules/mod_proxy.soproxy_http_module modules/mod_proxy_http.so

Listen 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

ProxyPass andProxyPassReverse

Specify the following options to make the Business ContinuityManager 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 agentwas initially set up

ProxyPass / http://0.0.0.0:port-number/ProxyPassReverse / http://0.0.0.0:port-number/

Timeout Specify how long to wait before issuing a time out.Specify a value greater than Replication Manager's timeoutvalue (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 forauthenticating Replication Manager.

After executing the htpasswd command, a file that manages the userID and password for basic access authentication of the ReplicationManager 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 upauthentication on page 3-18 to edit the httpd.conf file.

Table 3-4 Required settings for the httpd.conf file to set upauthentication

Directives Values

AuthName Specify the realm that will be used for authentication.

AuthType Specify the type of user authentication.Specify Basic.


Directives Values

AuthUserFile Specify the location of the management file for the user ID andpassword created by the htpasswd command.

Require Specify the users that are allowed access.

5. Restrict access to the TCP/IP port used by the Business ContinuityManager agent.IBM HTTP Server is the only program that can communicate with theBusiness 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 informationavailable 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 logTo collect error logs and access logs between Replication Manager and IBMHTTP Server, use the log function of IBM HTTP Server.

To determine whether to collect logs of IBM HTTP Server, follow theinstructions 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 parametersThis section describes how to create the initialization parameters for settingup the environment required to start the Business Continuity Manager agent.YKPRM00 is a member of the initialization parameter samples registered in thesample library during initialization. Adjust the parameters to fit yourenvironment.

Create a dataset to hold the initialization parameters by specifying thefollowing attributes:

• LRECL: 80• BLKSIZE: Multiple of 80• RECFM: Fixed-length or blocked fixed-length record• DSORG: Sequential or partitioned dataset


How to use the SETINIT commandThis subsection explains the format of the SETINIT command, that sets theinitialization parameters. For details about the symbols and syntax elementsused in command explanations, see Appendix E, Conventions in syntaxexplanations on page E-1.

0SETINIT[ 1parameter]...

Specify a SETINIT command and parameters in columns 1 through 71. Anyinformation specified in a column after column 72 is ignored.

You can specify more than one SETINIT command. You can specify differentparameters for one SETINIT command, but cannot specify the sameparameter more than once. If you specify the same parameters more thanonce for one SETINIT command, the last specified parameter is applied.

To specify the same parameter more than once, use a separate SETINITcommand. If a parameter that cannot be specified more than once inseparate SETINIT commands is specified in that way, the last specifiedparameter is applied.

For details about the specifiable parameters and whether they can bespecified multiple times by using separate SETINIT commands, see sectionDetails of initialization parameters on page 3-22.

Example of specifying the same parameter more than once for oneSETINIT command:

If you specify the same parameter more than once for one SETINITcommand, the last specified parameter is applied. Do not specify parametersas shown in this example.

In the following example, only DEVN(7500,750F) is applied, andDEVN(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 forseparate commands:

• If the parameter can be specified more than once for separatecommands: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)


SETINIT DEVN(7400,740F)SETINIT DEVN(7500,750F)

• If the parameter cannot be specified more than once for separatecommands: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 atthe end of the line. The following table shows the continuation symbols.

Table 3-5 Continuation symbols

Continuationsymbol Continuation method

Hyphen (-) The hyphen is removed, and the parameter is continued in theleftmost column of the next line, retaining any contiguous spaces.

Plus sign (+) The plus sign is removed, and the parameter is continued on thenext line, removing any contiguous spaces.

Coding example for continuing parameters that contain contiguousspaces:

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

SETINIT PREFIX('USER01.V1',+

'NY')

If you continue to specify parameters by using a plus sign (+) as shownabove, the command will be interpreted as follows:


SETINIT PREFIX('USER01.V1','NY')

Entering comments

Enclose a comment in /* and */. No comment can be entered inside aparameter.

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 beinterpreted as a part of the parameter instead of being interpreted as acomment:

SETINIT PREFIX(7300, + /* ERROR COMMENT */ 730F)

Notes during creation of initialization parameters

Do not specify an empty member as an initialization parameter when youstart the Business Continuity Manager agent. Although empty members donot result in an error, information cannot be returned to Replication Manager.

Details of initialization parametersThis subsection explains details of initialization parameters.

Format

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


[ 1MODE(startup-mode)][ 1LOCK(lock-mode)]

Parameters

PORT(port-number) ~ <numeric characters> ((1-65535)) <<24042>>Specifies the Business Continuity Manager agent port for TCP/IPcommunication with Replication Manager. You cannot specify a portnumber that is being used by another job. Specify a port number that isnot being used in the system.

RECVWAITTIME(reception-wait-time) ~ <numeric characters> ((0-65535))<<180>>

When TCP/IP communication with Replication Manager is performed, thisparameter specifies the wait time (in seconds) from when a receiverequest is initiated to when data is received. A value of 0 means that theBusiness 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 theBusiness Continuity Manager agent. When the Business ContinuityManager agent is running on more than one host, and a HOSTNAME (hostidentification name) value is duplicated in these hosts, ReplicationManager cannot identify the host on which the target Business ContinuityManager agent is running. To ensure that Replication Manager canidentify the host on which the Business Continuity Manager agent isrunning, specify a unique HOSTNAME value for each host.When this parameter is omitted, the value of the &SYSNAME systemsymbol is assumed. For details about the &SYSNAME system symbol, seethe IBM manual MVS Initialization and Tuning Reference.When the Business Continuity Manager agent runs on more than one hostand 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 HOSTNAMEvalues 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 ContinuityManager agent, the prefix of the configuration files managed by BusinessContinuity Manager must be specified.You can specify multiple PREFIX parameters. Specify multiple PREFIXparameters when the storage information to be acquired is informationregistered in multiple configuration files that have different prefixes, in anenvironment where Replication Manager and the Business ContinuityManager agent are one-to-one.

prefix ~ <PREFIX string consisting of 1 to 16 characters>


Specifies the file name prefix of the Business Continuity Managerconfiguration files that are used by Replication Manager. Specify thevalue that was specified in Configuration File Prefix in BusinessContinuity Manager's Set Defaults panel when the configuration filewas created. Replication Manager can use the disk configurationdefinition file and the copy group definition file with the prefixspecified here. For details about the Set Defaults panel in BusinessContinuity Manager, see the Hitachi Business Continuity ManagerReference 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 theBusiness Continuity Manager agent is operating. When monitoringPPRC copy pairs, specify the value that was specified in DeviceAddress Domain, Primary or Device Address Domain,Secondary in the Scan Copy Pair Inside Storage System panel whenthe copy group definition file for PPRC copy pairs was created. Fordetails about the Scan Copy Pair Inside Storage System panel inBusiness Continuity Manager, see the Hitachi Business ContinuityManager Reference Guide.If you specify multiple PREFIX parameters, we recommend that youuse the same device address domain ID for all of the device addressdomain IDs on the local site.

Note: Do not specify the local site's Non Gen'ed device address domainID 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 agentwhen the Remote DKC Control Function is used.You must specify a route list ID in order to use the Remote DKCControl Function.

{route-label|*} ~ <ROUTELABEL string consisting of 1 to 8 characters>If you specify a route label, command devices that have the specifiedroute label are used.If you specify *, all command devices are used regardless of whetherthey have a route label.If you specify neither a route label nor *, command devices that haveno route label are used.

local-site's-Non-Gen'ed-DAD-ID ~ <DAD string consisting of from 1 to 28characters>

Specifies the Non Gen'ed device address domain ID used by the localsite on which the Business Continuity Manager is operating.Specify an asterisk (*) in place of the local site's Non Gen'ed deviceaddress 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, youmust specify the local site's Non Gen'ed device address domain ID.


Note:

• Do not specify the local site's device address domain ID or the remotesite's device address domain ID.

• If you specify multiple PREFIX parameters, specify the same deviceaddress domain ID for all of the local site's Non Gen'ed device addressdomain IDs.

remote-site's-DAD-ID ~ <DAD string consisting of from 1 to 28characters...>

Specifies the device address domain ID of the remote site on whichthe Business Continuity Manager agent performs Remote Scans.To specify multiple device address domain IDs, separate consecutivedevice address domain IDs with a colon (:), as shown in the followingexample:Example: DAD1:DAD2:...Note also that to acquire information about volumes at the remotesite, you must specify the remote site's device address domain ID.

Note:

• Do not specify the local site's device address domain ID or the localsite's Non Gen'ed device address domain ID.

• If a site is being used as a local site by another Business ContinuityManager 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 thePREFIX parameter. Even though specifying a nonexistent prefix or deviceaddress domain ID does not result in an error during Business ContinuityManager agent startup, an error will occur during a Replication Managerrequest.

• In the PREFIX parameter, do not specify any value other than the prefixof the configuration file. If multiple datasets correspond to the specifiedprefix (such as the SYS1 prefix), Business Continuity Manager agentprocessing might slow down.

• If you specify the same prefix multiple times for MODE(MONITOR), themonitoring processing of Replication Manager might slow down. If youspecify the same prefix multiple times for MODE(EDIT), an error will occurand you will be unable to start the Business Continuity Manager agent.

• If you specify multiple PREFIX parameters, it will take time to switch theconfiguration files for each prefix during a Replication Manager request.Therefore, if there are many configuration files, we recommend that youaggregate prefixes in the configuration files so that there is only onePREFIX parameter, to shorten the access time for a request from or aresponse to Replication Manager.

• If you want to modify a configuration file that has a prefix specified in thePREFIX parameter, make sure you use the ISPF panel or Replication


Manager. If you use another method, information might not be displayedon Replication Manager, or an error might occur.

• The access time for a Replication Manager request or response becomeslonger according to the number of copy pairs defined in the copy groupdefinition file that has the specified prefix. Therefore, specify themonitoring interval of Replication Manager to fit the environment (thehost capability corresponding to the number of copy pairs).

DEVN(start-device-number,end-device-number) ~ <4 hexadecimalcharacters>

Specifies a range of devices from which to collect information whenfiltering the host volume information to be passed to Replication Manager.Specify the start-device-number and end-device-number in the ascendingorder of hexadecimal characters. If the DEVN parameter has not beenspecified before, DEVN(0000,FFFF) is assumed.

Note: Notes about specifying the DEVN parameter

• To reduce the access time required for requests and replies fromReplication Manager, we recommend that you specify a range of targetdevices from which information is collected.

• When you specify more than one DEVN parameter, even if there areduplicate devices, they are not eliminated, so make sure you avoidspecifying such duplications.

LOGLEVEL(output-level) ~ <numeric character> ((0-3)) <<2>>Specifies the log output level.

0Logs are not output. If 0 is specified, it is difficult to determine thecause of a communication failure or an error that occurs duringexecution of a Business Continuity Manager agent command.

1Communication-related messages (YKY300I, YKY301I, YKY304I, andYKY307I) are output.

2In addition to the messages that are output when LOGLEVEL(1) isspecified, both the YKY680I and YKY500I messages are output. TheYKY680I message is output when an error occurs during an updaterequest for a copy pair configuration or a copy pair status. TheYKY500I message displays the results of updated configuration files.

3In addition to the information output with LOGLEVEL(2), BCM logs areoutput.

The following table shows the LOGLEVEL specification and the messages thatare output.


Table 3-6 LOGLEVEL specification and the output messages

LOGLEVEL Output messages

0 No output

1 YKY300I, YKY301I, YKY304I, and YKY307I2 YKY300I, YKY301I, YKY304I, YKY307I, YKY500I, and YKY680I3 YKY300I, YKY301I, YKY304I, YKY307I, YKY500I, and YKY680I

AUDITLOG(SYSLOG)Specifies whether to output audit logs. When specified, the followingadditional 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 ifLOGLEVEL(2) or later was specified.

MODE(startup-mode) ~ ({EDIT|MONITOR}) <<MONITOR>>Specifies the permission level at which the Business Continuity Manageragent starts.

EDITAllows definition, processing, and monitoring of copy groups.

MONITORAllows monitoring of copy groups.

LOCK(lock-mode) ~ ({PREFIX|CHECK|NONE}) <<PREFIX>>Specifies the lock mode of the configuration files. The LOCK parameter isvalid only when MODE(EDIT) is specified. An error occurs if the LOCKparameter is specified when MODE(MONITOR) is specified.

PREFIXLocks configuration files based on file name prefixes when theBusiness Continuity Manager agent starts. Other users cannot updateconfiguration files that are locked.

CHECKDoes not lock configuration files when the Business ContinuityManager agent starts. When the Business Continuity Manager agentupdates a definition, it verifies that no other user has updated theconfiguration file that it is about to update.

NONEDoes not lock the configuration files when the Business ContinuityManager agent starts.


Multiple specifications of initialization parameters

The following table explains what results when multiple SETINIT commandsare used to specify each initialization parameter:

Table 3-7 Results of multiple specification of initialization parameters

Parameter name Results of multiple specification

PORT Last specified parameter is applied.

RECVWAITTIMEHOSTNAMEPREFIX Permitted

DEVNLOGLEVEL Last specified parameter is applied.

AUDITLOGMODELOCK

Examples of specifying initialization parametersThis subsection provides examples of specifying initialization parameters usedfor 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 upthe Business Continuity Manager agent to perform both local and RemoteScans.

The following figure shows an example of this configuration.


Figure 3-8 Example configuration when Business Continuity Manageragent is only on the local site

For the configuration shown in Figure 3-8 Example configuration whenBusiness Continuity Manager agent is only on the local site on page 3-29specify the settings provided in the following table to connect BusinessContinuity Manager agent installed on the local site to Replication Manager.


Table 3-8 Settings to connect Business Continuity Manager agent installedon the local site to Replication Manager

Prefix

Local site Remote site

Portnumber DADID

Route list ID(forwarddirection)

Non Gen'edDADID DADID

ACCOUNT 24042 NY ROUTE1 Nospecification

LA

INFO ROUTE2 NY2

The following shows an example of specifying the settings shown in Table 3-8Settings to connect Business Continuity Manager agent installed on the localsite 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 remotesites, configure the Business Continuity Manager agent on each site toperform a scan on that site, only.

The following figure shows an example of this configuration.


Figure 3-9 Example configuration when Business Continuity Manageragent is on the local site and a remote site

For the configuration shown in Figure 3-9 Example configuration whenBusiness Continuity Manager agent is on the local site and a remote site onpage 3-31 specify the settings provided in the following table to connectBusiness Continuity Manager agent to the Replication Manager installed oneach site.


Table 3-9 Settings for connecting Business Continuity Manager agentsinstalled on the local and remote sites to Replication Manager

Prefix

Local site Remote site

Portnumb

er

DADID

Routelist ID

(forwarddirection

)

NonGen'edDADID

Portnumb

er

DADID

Routelist ID

(reversedirectio

n)

Non Gen'edDADID

ACCOUNT

24042 NY ROUTE1 Nospecification

24055 LA ROUTE3 Nospecification

INFO ROUTE2 NY2 ROUTE4 LA2

The following shows an example of specifying the settings shown in Table 3-9Settings for connecting Business Continuity Manager agents installed on thelocal and remote sites to Replication Manager on page 3-32 for initializationparameters.

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 remotesite

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, youcannot scan the remote site by using Business Continuity Manager agent onthe local site. Therefore, do not specify the device address domain ID of theremote site in the PREFIX parameter.

Examples of initialization parameter analysis resultsWhen the Business Continuity Manager agent starts, the results of theinitialization analysis is output to the dataset specified in the YKLIST DDstatement.


The following examples show results.

Result list with no error

*** AGENT v.r.n-mm LISTING INFORMATION *** DATE=2015-12-03 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 domainID operand that is required for the first PREFIX parameter is missing. TheYKY002I message is displayed.

*** AGENT v.r.n-mm LISTING INFORMATION *** DATE=2015-12-03 TIME=13:34:35 PAGE=0001

SETINIT PORT(24042) /* PREFIX */ SETINIT PREFIX('ACCOUNT') YKY002I INVALID INITIALIZATION PARAMETER: PREFIXSETINIT PREFIX('INFO','NY')

Creating a cataloged procedure for startup for the BusinessContinuity Manager agents

This section explains how to create and change a cataloged procedure forstarting Business Continuity Manager agent.

Standard cataloged procedure for startupThe standard cataloged procedure for startup is registered into the samplelibrary during installation. Copy the standard cataloged procedure for startupto 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


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

In the sample JCL, the nnnnnn part of Vnnnnnn varies depending on theversion.

Description

1. PROC statementSpecifies the member name of the initialization parameter that is usedduring the startup of the Business Continuity Manager agent. Themember specified in this statement is the default value. To use a non-standard member, execute the START command to change the memberduring the startup.

2. EXEC statementSpecifies the following operands:

¢ TIME (CPU cut-off time) whose value is 1440.¢ REGION (region size). To calculate this value, see section Determining

required memory on page 2-7.3. YKPARM DD statement

Specifies the name of the dataset that contains the initializationparameters, and a member name for a partitioned dataset.

4. YKLIST DD statementSpecifies the dataset to which the initialization parameter analysis resultis 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 BusinessContinuity Manager agent terminates abnormally. SYSOUT=* is specified inthe standard cataloged procedure for startup. If the DUMMY output class isassigned as the output destination class for system messages in a jobthat is started by the START command, we recommend that you specify


SYSOUT=SYSOUT-class-enabled-for-output, since the dump is not outputwith SYSOUT=* specified.

8. SYSEXEC DD statementSpecifies the dataset that contains the REXX exec library.

9. STEPLIB DD statement (optional)Specifies the Business Continuity Manager load library dataset. If theBusiness Continuity Manager load library dataset is linked to the system'sLINKLIB, you do not need to specify the STEPLIB DD statement.

10. YKLOG01 DD and YKLOG02 DD statements (optional)Specifies the log dataset to which BCM log data will be output to withoutusing the system logger service.For details on how to specify DD statements for BCM logs and output BCMlog data, see the description about outputting the BCM log data in theHitachi Business Continuity Manager User Guide.

Note:

• Because the Business Continuity Manager agent is a resident programthat waits for client requests, specify TIME=1440 in the EXEC statement sothat no timeout occurs. Additionally, specify Purge as the output class ofthe job log and system messages so that the output messages do notcause a shortage of spool space.

• If z/OS V1R3 or later is running, use the JOB statement keyword of theSTART command to specify that the JESLOG dataset is to be output usingthe SUPPRESS setting.

Changing the cataloged procedure for startupYou can change the contents of the standard cataloged procedure for startupaccording to the system environment and create a separate catalogedprocedure for startup for the Business Continuity Manager agent. Thecataloged 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 theBusiness Continuity Manager agent. For example, when the standard TCPstack environment is not used, you can specify the TCP/IP environmentsettings file by adding the SYSTCPD DD statement.

For details on how to specify the TCP/IP environment settings file withoutusing the SYSTCPD DD statement and how to define the TCP/IP environmentsettings file to be specified in the SYSTCPD DD statement, see the explanationof a basic TCP/IP system in the IBM manual Communications Server IPConfiguration Guide.



4Setting up an environment for BCM

Monitor

This chapter explains how to set up the security for BCM Monitor. It alsoexplains how to create configuration files, BCM Monitor parameter files, and acataloged 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-1Hitachi Business Continuity Manager Installation Guide

General procedure for setting up an environment for BCMMonitor

This section contains the general procedure for configuring the environmentsettings that are necessary for BCM Monitor.

Figure 4-1 General procedure for configuring the environment settingsnecessary for BCM Monitor

The following sections explain the details about each step.

Setting up the security for BCM MonitorThis 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 thecataloged procedure for startup for BCM Monitor.

The following is an example of using the TSO/E command with the STARTEDclass:

->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 monitorcopy groups. To use the CLI command, you need to define one of thefollowing profiles in the RACF FACILITY class, and then grant the viewpermission for the defined profile to the previously defined user ID or groupID.

If you specified one of the following in the BCM Monitor YKMONCG file, youneed to grant the view permission to the STGADMIN.YKA.BCM.COMMANDSprofile:

4-2 Setting up an environment for BCM MonitorHitachi Business Continuity Manager Installation Guide

• DELETE, MAKE, RESYNC, or SUSPEND for the ACTION parameter• ADJUST as the startup action for the CGSTARTUPSTATUS parameter• DUPLEX as the startup status for the CGSTARTUPSTATUS parameter of

ShadowImage or TrueCopy Asynchronous when NOCANCEL is not specified

In other cases, grant the view permission to the STGADMIN.YKA.BCM.YKQUERYprofile.

The following is an example of using the TSO/E command with the FACILITYclass:

->SETROPTS CLASSACT(FACILITY)->RDEFINE FACILITY STGADMIN.YKA.BCM.COMMANDS UACC(NONE)->PERMIT STGADMIN.YKA.BCM.COMMANDS CLASS(FACILITY) ID(user-ID) ACCESS(READ)

Creating configuration files for BCM MonitorBefore using BCM Monitor, you need to use Business Continuity Manager tocreate the configuration files shown below. They should match theconfigurations of the copy groups to be monitored from BCM Monitor.

• Disk configuration definition file (mandatory)• Copy group definition file (mandatory)• Route list definition file

The route list definition file is required when using the Remote DKCControl Function and the TrueCopy Consistency Preservation Function.

Note: If you have already created a configuration file from using BusinessContinuity Manager, then there is no need to re-create the file.

Creating BCM Monitor parameter filesBefore using BCM Monitor, create the following two parameter files:

• YKMONOPT fileA file used to specify options necessary for starting BCM Monitor

• YKMONCG fileA file used to specify BCM Monitor operations. In this file, specify thefollowing:

¢ What action to take when a copy group that is being monitoredchanges to the target status.

¢ What actions to take when executed actions fail.¢ What actions to take when copy groups are not in their specified

startup statuses.


For details on the format of these files, see the Hitachi Business ContinuityManager Reference Guide.

Creating a cataloged procedure for startup for BCM MonitorThis section explains how to create a cataloged procedure for startup for BCMMonitor.

The standard cataloged procedure for startup is shown below. It is registeredin the cataloged procedure during installation. Copy this procedure to thePROCLIB dataset of the JES (Job Entry Subsystem) startup procedure, andthen modify the procedure as appropriate for your environment.

//YKBCMMON PROC//******************************************************************//*//* All Rights Reserved. Copyright (C) 2010, 2016, Hitachi, Ltd.//*//******************************************************************//YKBCMMON EXEC PGM=IKJEFT01,PARM=YKBCMMON,TIME=1440,REGION=4096K//YKMONOPT DD DSN=HDSYK.Vnnnnnn.HDSYSAMT(YKMOPT00),DISP=SHR//YKMONCG DD DSN=HDSYK.Vnnnnnn.HDSYSAMT(YKMCG00),DISP=SHR//SYSTSPRT DD SYSOUT=*//SYSTSIN DD DUMMY//SYSABEND DD SYSOUT=*//SYSEXEC DD DSN=HDSYK.Vnnnnnn.HDSYEXET,DISP=SHR//STEPLIB DD DSN=HDSYK.Vnnnnnn.HDSYLNKT,DISP=SHRIn the sample JCL, the nnnnnn portion of Vnnnnnn varies, depending on theversion.

Description

1. EXEC statementSpecifies the following operands:

¢ TIME (CPU cut-off time). The value is 1440.¢ REGION (region size). The default is 4,096 KB, but it can be overridden

to fit your system.To calculate this size, see Determining required memory on page 2-7.

2. YKMONOPT DD statementSpecifies the name of the dataset that contains the YKMONOPT file. Fordetails on the format of this dataset, see the Hitachi Business ContinuityManager Reference Guide.

3. YKMONCG DD statementSpecifies the name of the dataset that contains the YKMONCG file. Fordetails on the format of this dataset, see the Hitachi Business ContinuityManager Reference Guide.

4. SYSTSPRT DD statementSpecifies the location to output monitoring information to. SYSOUT=* isspecified in the standard cataloged procedure for startup. If the DUMMY


output class is assigned as the output destination class for systemmessages in a job that is started by the START command, we recommendthat you specify SYSOUT=SYSOUT-class-enabled-for-output because themonitoring information is not output with SYSOUT=* specified.

5. SYSTSIN DD statementSpecifies DUMMY.

6. SYSABEND DD statementSpecifies the location to which the dump is to be output when BCMMonitor terminates abnormally. SYSOUT=* is specified in the standardcataloged procedure for startup. If the DUMMY output class is assigned asthe output destination class for system messages in a job that is startedby the START command, we recommend that you specifySYSOUT=SYSOUT-class-enabled-for-output because the dump is not outputwith SYSOUT=* specified.

7. SYSEXEC DD statementSpecifies the dataset that contains Business Continuity Manager.

8. STEPLIB DD statement (optional)Specifies the dataset that contains Business Continuity Manager. If theLINKLIB dataset for Business Continuity Manager is linked to the system'sLINKLIB, you do not need to specify the STEPLIB DD statement.

9. YKLOG01 DD statement and YKLOG02 DD statement (optional)Specifies the log dataset to which BCM log data will be output, withoutusing the system logger service.For details on specifying DD statements for BCM logs and outputting BCMlog data, see the description of the BCM log output method in the HitachiBusiness Continuity Manager User Guide.

Note: If z/OS V1R3 or later is running, use the JOB statement keyword of theSTART command to specify that the JESLOG dataset is to be output using theSUPPRESS setting.



AModifying sample JCL

This appendix provides examples of modifying the sample JCL.

□ Values used in the sample JCL modification examples

□ ALLOUPLD (creating transmission datasets)

□ RECVUPLD (TSO/E RECEIVE processing)

□ HDSYKSIN (simple installation)

□ SMPALLOC (allocating SMP/E datasets)

□ HDSYK1AL (allocating distribution and target libraries)

□ HDSYK2DF (defining distribution and target libraries)

□ HDSYK3RC (SMP/E RECEIVE processing)

□ HDSYK4AP (creating target libraries)

□ HDSYK5AC (creating distribution libraries)

□ HDSYK6RC (SMP/E RECEIVE processing for extended access controlfunction)

□ HDSYK7AP (creating target libraries for extended access control function)

□ HDSYK8AC (creating distribution libraries for extended access controlfunction)

Modifying sample JCL A-1Hitachi Business Continuity Manager Installation Guide

Values used in the sample JCL modification examplesThe table below lists the values used in the sample JCL modificationexamples.

Prerequisites

¢ TSO/E to perform installationTSO/E user ID: BCMUSER

¢ Dataset and volume allocated to the dataset

No. Job name Dataset use Prefix fordataset name

Volumeallocated

to thedataset

Remarks

1 ALLOUPLD Dataset fortransmission

BCMUSER. TSOW00 The prefixfor the userdatasetname

2 RECVUPLD For TSO/E RECEIVE BCMUSER TSOW00 The prefixfor the userdatasetname

3 HDSYKSIN Target Library HTC1.BCM. BCMT00 --

4 SMPALLOC SMP/E datasets HTC1.BCM. BCMS00 --

5 • HDSYK1AL• HDSYK4AP• HDSYK5AC• HDSYK7AP• HDSYK8AC

Target Library HTC1.BCM. BCMT00 --

Distribution Library HTC1.BCM. BCMD00 --

6 • HDSYK2DF• HDSYK3RC• HDSYK6RC

Global Zone (SMPTLIB) HTC1.BCM. BCMS00 --

In the sample JCL, the nnn part of CHYKnnn, the nnnnnn part of Vnnnnnn,and the aaa and the bbb parts of CHYKaaa,CHYKbbb vary depending on theversion.

ALLOUPLD (creating transmission datasets)The method for modifying ALLOUPLD created from transmitted datasets isexplained below.

The following numbers correspond to the numbers appearing on the right sideof the sample JCL. Modify the underlined parts in the sample JCL as follows:

(1)-(3)Modify the JOB text to match the installation environment.

A-2 Modifying sample JCLHitachi Business Continuity Manager Installation Guide

(4)-(15)Change the prefix for the name for the dataset transmission destinationfrom HITACHI. to the TSO/E user ID (BCMUSER.).

(16)Change the prefix for the name for the dataset transmission destinationfrom HITACHI to the TSO/E user ID (BCMUSER).

(17)Change VOLSER from #tso01 to TSOW00.

//ALLOUPLD JOB (ACCT#),'ALLO UPLD FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL allocates data sets in preparation for storing//* the data files for installation of BC Manager from the//* distribution CD.//*//* Instructions://* 1. Change 'HITACHI' to the current USERID.//* 2. Change '#tso01' to VOLSER of your device.//* 3. Submit this JCL to allocate the data sets for storing//* the data files.//* 4. Transfer the unzipped .XMIT files to the allocated data sets//* via FTP in "BINARY" mode.//* 5. See RECVUPLD for further procedures.//*//*//* Remove all BC Manager files.//*//CLEAN EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD * DELETE HITACHI.CHYKnnn.SMPMCS.XMIT -----(4) DELETE HITACHI.CHYKnnn.F1.XMIT -----(5) DELETE HITACHI.CHYKnnn.F2.XMIT -----(6) DELETE HITACHI.CHYKnnn.F3.XMIT -----(7) DELETE HITACHI.CHYKnnn.F4.XMIT -----(8) DELETE HITACHI.CHYKnnn.F5.XMIT -----(9) DELETE HITACHI.CHYKnnn.F6.XMIT -----(10) DELETE HITACHI.CHYKnnn.F7.XMIT -----(11) DELETE HITACHI.CHYKnnn.F8.XMIT -----(12) DELETE HITACHI.CHYKnnn.F9.XMIT -----(13) DELETE HITACHI.CHYKaaa.SMPMCS.XMIT -----(14) DELETE HITACHI.CHYKbbb.SMPMCS.XMIT -----(15) SET MAXCC = 0/*//*//* Allocate the data sets for storing the data files.//*//* Value Description//* -------- --------------------------------// SET PFX=HITACHI Data set prefix -----(16)// SET VRM=CHYKnnn Version of BC Manager// SET VSN=#tso01 VOLSER -----(17)// SET VRMF1=CHYKaaa Version of addition function// SET VRMF2=CHYKbbb Version of addition function//*


//BR14 EXEC PGM=IEFBR14//SMPMCS DD DSN=&PFX..&VRM..SMPMCS.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F1 DD DSN=&PFX..&VRM..F1.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(30)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F2 DD DSN=&PFX..&VRM..F2.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(75)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F3 DD DSN=&PFX..&VRM..F3.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F4 DD DSN=&PFX..&VRM..F4.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F5 DD DSN=&PFX..&VRM..F5.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F6 DD DSN=&PFX..&VRM..F6.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F7 DD DSN=&PFX..&VRM..F7.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F8 DD DSN=&PFX..&VRM..F8.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F9 DD DSN=&PFX..&VRM..F9.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//SMPMCSF1 DD DSN=&PFX..&VRMF1..SMPMCS.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//SMPMCSF2 DD DSN=&PFX..&VRMF2..SMPMCS.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)


RECVUPLD (TSO/E RECEIVE processing)The method for modifying RECVUPLD, which performs TSO/E RECEIVEprocessing, is explained below.



(4)-(16), (18), (20), (22), (24), (26), (28), (30), (32), (34), (36), (38)Change the prefix for the dataset name from HITACHI. to BCMUSER..

(17), (19), (21), (23), (25), (27), (29), (31), (33), (35), (37), (39)Change VOLSER from #tso01 to TSOW00.

//RECVUPLD JOB (ACCT#),'TSO RECEIVE', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JOB uses TSO RECEIVE command to receive the data sets//* that were allocated by ALLOUPLD JCL and contain the unzipped//* .XMIT files that were uploaded via binary FTP transfer.//*//* Instructions://* 1. Logon with the same USERID used for ALLOUPLD job.//* 2. Change 'HITACHI.' prefixes to suit your naming convention.//* 3. Change '#tso01' to VOLSER of your device.//* 4. Submit this JCL.//* 5. See this product's documentation for SMP/E instructions.//* Modify the .SMPMCS file so that the chosen file prefix//* is indicated in the RFDSNPFX() parameter of the//* FUNCTION() statement.//* Allocate the .SMPMCS file directly to the SMP/E//* SMPPTFIN DD statement on the receive step. SMP/E will//* locate the other files via the catalog.//*//*//* Remove all BC Manager files.//*//CLEAN EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD * DELETE HITACHI.CHYKnnn.SMPMCS -----(4) DELETE HITACHI.CHYKnnn.F1 -----(5) DELETE HITACHI.CHYKnnn.F2 -----(6) DELETE HITACHI.CHYKnnn.F3 -----(7) DELETE HITACHI.CHYKnnn.F4 -----(8) DELETE HITACHI.CHYKnnn.F5 -----(9) DELETE HITACHI.CHYKnnn.F6 -----(10) DELETE HITACHI.CHYKnnn.F7 -----(11) DELETE HITACHI.CHYKnnn.F8 -----(12) DELETE HITACHI.CHYKnnn.F9 -----(13) DELETE HITACHI.CHYKaaa.SMPMCS -----(14) DELETE HITACHI.CHYKbbb.SMPMCS -----(15) SET MAXCC = 0/*//*********************************************************************


//* TSO receive to restore portable PDS from BINARY FTP//*********************************************************************//S1 EXEC PGM=IKJEFT01//SYSTSPRT DD SYSOUT=*//SYSTSIN DD * RECEIVE INDSN(CHYKnnn.SMPMCS.XMIT) DSNAME('HITACHI.CHYKnnn.SMPMCS') + -----(16) VOLUME(#tso01) -----(17) RECEIVE INDSN(CHYKnnn.F1.XMIT) DSNAME('HITACHI.CHYKnnn.F1') + -----(18) VOLUME(#tso01) -----(19) RECEIVE INDSN(CHYKnnn.F2.XMIT) DSNAME('HITACHI.CHYKnnn.F2') + -----(20) VOLUME(#tso01) -----(21) RECEIVE INDSN(CHYKnnn.F3.XMIT) DSNAME('HITACHI.CHYKnnn.F3') + -----(22) VOLUME(#tso01) -----(23) RECEIVE INDSN(CHYKnnn.F4.XMIT) DSNAME('HITACHI.CHYKnnn.F4') + -----(24) VOLUME(#tso01) -----(25) RECEIVE INDSN(CHYKnnn.F5.XMIT) DSNAME('HITACHI.CHYKnnn.F5') + -----(26) VOLUME(#tso01) -----(27) RECEIVE INDSN(CHYKnnn.F6.XMIT) DSNAME('HITACHI.CHYKnnn.F6') + -----(28) VOLUME(#tso01) -----(29) RECEIVE INDSN(CHYKnnn.F7.XMIT) DSNAME('HITACHI.CHYKnnn.F7') + -----(30) VOLUME(#tso01) -----(31) RECEIVE INDSN(CHYKnnn.F8.XMIT) DSNAME('HITACHI.CHYKnnn.F8') + -----(32) VOLUME(#tso01) -----(33) RECEIVE INDSN(CHYKnnn.F9.XMIT) DSNAME('HITACHI.CHYKnnn.F9') + -----(34) VOLUME(#tso01) -----(35) RECEIVE INDSN(CHYKaaa.SMPMCS.XMIT) DSNAME('HITACHI.CHYKaaa.SMPMCS') + -----(36) VOLUME(#tso01) -----(37) RECEIVE INDSN(CHYKbbb.SMPMCS.XMIT) DSNAME('HITACHI.CHYKbbb.SMPMCS') + -----(38) VOLUME(#tso01) -----(39)END/*

HDSYKSIN (simple installation)The method for modifying HDSYKSIN, which performs a simple installation, isexplained below.



(4)Change the prefix for the input dataset name from HITACHI to BCMUSER.

(5)Change the prefix for the target library name from HITACHI to HTC1.BCM.

(6)


Change the volume allocated to the target library from #bcm01 to BCMT00.

//HDSYKSIN JOB (ACCT#),'SAMPLE COPY', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2006, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* JCL template for simplified installation of BC Manager.//*//* This sample shows an installation method that copies//* distribution data sets directly to the target libraries,//* without using SMP/E.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- ----------------------------------// SET IPFX=HITACHI Prefix of distribution data sets --(4)// SET IVRM=CHYKnnn Version of distribution data sets// SET TPFX=HITACHI Prefix of target libraries --(5)// SET TVRM=Vnnnnnn Version of target libraries// SET TVSN=#bcm01 VOLSER of target libraries --(6)//*//* 3) Submit the JCL.//*//*********************************************************************//COPY EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//* Input data sets//INF1 DD DSN=&IPFX..&IVRM..F1,DISP=SHR SAMPLIB data set//INF2 DD DSN=&IPFX..&IVRM..F2,DISP=SHR LINKLIB data set//INF3 DD DSN=&IPFX..&IVRM..F3,DISP=SHR LPALIB data set//INF4 DD DSN=&IPFX..&IVRM..F4,DISP=SHR PROCLIB data set//INF5 DD DSN=&IPFX..&IVRM..F5,DISP=SHR EXEC(F) data set//INF6 DD DSN=&IPFX..&IVRM..F6,DISP=SHR EXEC(V) data set//INF7 DD DSN=&IPFX..&IVRM..F7,DISP=SHR PANEL data set//INF8 DD DSN=&IPFX..&IVRM..F8,DISP=SHR MESSAGE data set//INF9 DD DSN=&IPFX..&IVRM..F9,DISP=SHR TABLE data set//* Output libraries//OUTF1 DD DSN=&TPFX..&TVRM..HDSYSAMT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), SAMPLIB// SPACE=(TRK,(15,1,5)),DCB=*.INF1 Target library//OUTF2 DD DSN=&TPFX..&TVRM..HDSYLNKT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), LINKLIB// SPACE=(TRK,(105,1,30)),DCB=*.INF2 Target library//OUTF3 DD DSN=&TPFX..&TVRM..HDSYLPAT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), LPALIB// SPACE=(TRK,(1,1,1)),DCB=*.INF3 Target library//OUTF4 DD DSN=&TPFX..&TVRM..HDSYPRCT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), PROCLIB// SPACE=(TRK,(5,1,10)),DCB=*.INF4 Target library//OUTF5 DD DSN=&TPFX..&TVRM..HDSYEXET,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), EXECLIB(F)// SPACE=(TRK,(45,1,10)),DCB=*.INF5 Target library//OUTF6 DD DSN=&TPFX..&TVRM..HDSYEXVT,// UNIT=3390,VOL=SER=&TVSN,


// DISP=(NEW,CATLG,DELETE), EXECLIB(V)// SPACE=(TRK,(45,1,10)),DCB=*.INF6 Target library//OUTF7 DD DSN=&TPFX..&TVRM..HDSYPNLT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), PANEL// SPACE=(TRK,(60,1,200)),DCB=*.INF7 Target library//OUTF8 DD DSN=&TPFX..&TVRM..HDSYMSGT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), MESSAGE// SPACE=(TRK,(5,1,5)),DCB=*.INF8 Target library//OUTF9 DD DSN=&TPFX..&TVRM..HDSYTABT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), TABLE// SPACE=(TRK,(5,1,5)),DCB=*.INF9 Target library//SYSIN DD * COPY OUTDD=OUTF1,INDD=INF1 COPYMOD OUTDD=OUTF2,INDD=INF2 COPYMOD OUTDD=OUTF3,INDD=INF3 COPY OUTDD=OUTF4,INDD=INF4 COPY OUTDD=OUTF5,INDD=INF5 COPY OUTDD=OUTF6,INDD=INF6 COPY OUTDD=OUTF7,INDD=INF7 COPY OUTDD=OUTF8,INDD=INF8 COPY OUTDD=OUTF9,INDD=INF9/*

SMPALLOC (allocating SMP/E datasets)The method for modifying SMPALLOC, which allocates SMP/E datasets, isexplained below.



(4)Change the prefix for the SMP/E dataset name from HDSYK to HTC1.BCM.

(5), (8)Change the volume allocated to the SMP/E dataset from #smp01 toSMP001.

(6), (7), (9), (10)Change the prefix for the dataset name from HDSYK. to HTC1.BCM..

//SMPALLOC JOB (ACCT#),'ALLO SMP FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL allocates a CSI data set.//*//* Instructions:


//* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------// SET PFX=HDSYK Prefix of SMP files --(4)// SET VSN=#smp01 DASD volume serial for SMP files --(5)//*//* 3) Submit the JCL.//*//*********************************************************************//STEP01 EXEC PGM=IDCAMS//CSIVOL DD UNIT=SYSDA,VOL=SER=&VSN,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSIN DD * DELETE HDSYK.SMPCSI.CSI -----(6) SET MAXCC=0 DEFINE CLUSTER( - NAME(HDSYK.SMPCSI.CSI) - -----(7) FREESPACE(10 5) - KEYS(24 0) - RECORDSIZE(24 143) - SHAREOPTIONS(2 3) - UNIQUE - VOLUMES(#smp01) - -----(8) ) - DATA( - NAME(HDSYK.SMPCSI.CSI.DATA) - -----(9) CONTROLINTERVALSIZE(4096) - CYLINDERS(1 1) - ) - INDEX( - NAME(HDSYK.SMPCSI.CSI.INDEX)- -----(10) CYLINDERS(1 1) - )/*//*//* Initialize a CSI data set. Refer to SMP/E User's Guide.//*//STEP02 EXEC PGM=IDCAMS//SMPCSI DD DISP=OLD,DSN=&PFX..SMPCSI.CSI//ZPOOL DD DISP=SHR,DSN=SYS1.MACLIB(GIMZPOOL)//SYSPRINT DD SYSOUT=*//SYSIN DD * REPRO OUTFILE(SMPCSI) - INFILE(ZPOOL)/*//*//* Allocate data sets for SMP installation of NC//*//STEP03 EXEC PGM=IEFBR14//* Data sets required by SMP//SMPPTS DD DSN=&PFX..SMPPTS,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,10)),// DCB=(BLKSIZE=27920,LRECL=80,RECFM=FB)//SMPSCDS DD DSN=&PFX..SMPSCDS,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,15)),// DCB=(LRECL=80,BLKSIZE=27920,RECFM=FB)//SMPMTS DD DSN=&PFX..SMPMTS,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,5)),// DCB=(LRECL=80,BLKSIZE=27920,RECFM=FB)//SMPSTS DD DSN=&PFX..SMPSTS,// DISP=(NEW,CATLG,DELETE),


// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,5)),// DCB=(LRECL=80,BLKSIZE=27920,RECFM=FB)//SMPLOG DD DSN=&PFX..SMPLOG,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5)),// DCB=(BLKSIZE=27998,LRECL=510,RECFM=VB)//SMPLOGA DD DSN=&PFX..SMPLOGA,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5)),// DCB=(BLKSIZE=27998,LRECL=510,RECFM=VB)

HDSYK1AL (allocating distribution and target libraries)The method for modifying HDSYK1AL, which allocates the distribution libraryand the target library, is explained below.



(4)Change the prefix for the dataset name from HDSYK to HTC1.BCM.

(5)Change the volume allocated to the target library from #bcm01 to BCM001.

(6)Change the volume allocated to the distribution library from #bcm02 toBCM002.

//HDSYK1AL JOB (ACCT#),'ALLO UPLD FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL allocates the data sets for SMP/E installation of//* BC Manager.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET TVSN=#bcm01 Target library VOLSER -----(5)// SET DVSN=#bcm02 Distribution library VOLSER -----(6)//*//* 3) Submit the JCL.


//*//*********************************************************************//ALLOCATE EXEC PGM=IEFBR14//* Allocate target libraries//HDSYSAMT DD DSN=&PFX..&VRM..HDSYSAMT, SAMPLES LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(15,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYLNKT DD DSN=&PFX..&VRM..HDSYLNKT, LOAD LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(105,1,30)),// DCB=(BLKSIZE=6144,RECFM=U)//HDSYLPAT DD DSN=&PFX..&VRM..HDSYLPAT, LPA LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(1,1,1)),// DCB=(BLKSIZE=6144,RECFM=U)//HDSYPRCT DD DSN=&PFX..&VRM..HDSYPRCT, PROC LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(5,1,10)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYEXET DD DSN=&PFX..&VRM..HDSYEXET, EXEC(F) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYEXVT DD DSN=&PFX..&VRM..HDSYEXVT, EXEC(V) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6120,LRECL=255,RECFM=VB)//HDSYPNLT DD DSN=&PFX..&VRM..HDSYPNLT, PANEL LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(60,1,200)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYMSGT DD DSN=&PFX..&VRM..HDSYMSGT, MESSAGE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYTABT DD DSN=&PFX..&VRM..HDSYTABT, TABLE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//* Allocate distribution libraries//HDSYSAMD DD DSN=&PFX..&VRM..HDSYSAMD, SAMPLES LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(15,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYLNKD DD DSN=&PFX..&VRM..HDSYLNKD, LOAD LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(105,1,30)),// DCB=(BLKSIZE=6144,RECFM=U)//HDSYLPAD DD DSN=&PFX..&VRM..HDSYLPAD, LPA LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(1,1,1)),// DCB=(BLKSIZE=6144,RECFM=U)//HDSYPRCD DD DSN=&PFX..&VRM..HDSYPRCD, PROC LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(5,1,10)),


// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYEXED DD DSN=&PFX..&VRM..HDSYEXED, EXEC(F) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYEXVD DD DSN=&PFX..&VRM..HDSYEXVD, EXEC(V) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6120,LRECL=255,RECFM=VB)//HDSYPNLD DD DSN=&PFX..&VRM..HDSYPNLD, PANEL LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(60,1,200)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYMSGD DD DSN=&PFX..&VRM..HDSYMSGD, MESSAGE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSYTABD DD DSN=&PFX..&VRM..HDSYTABD, TABLE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)

HDSYK2DF (defining distribution and target libraries)The method for modifying HDSYK2DF, which defines the distribution libraryand the target library, is explained below.



(4)Change the prefix for the SMP/E dataset name, target library name, anddistribution library name from HDSYK to HTC1.BCM.

(5)-(10)Change the prefix for the SMP/E dataset name from HDSYK. toHTC1.BCM..

(11)Change the volume allocated to SMPTLIB from #smp01 to SMP001.

(12)-(29)Change the prefix for the target library name from HDSYK. to HTC1.BCM..

(30)-(38)Change the prefix for the distribution library name from HDSYK. toHTC1.BCM..


//HDSYK2DF JOB (ACCT#),'DO THE DDDEFS', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E DDDEF for the distribution libraries//* and the target libraries.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)//* #smp01 DASD volume serial for SMPTLIB//*//* 3) Submit the JCL to begin execution of SMP/E DDDEF.//*//*********************************************************************//S1 EXEC PGM=GIMSMP//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//* SMP/E control record input//SMPCNTL DD *SET BDY(GLOBAL).UCLIN.ADD GLOBALZONE ZONEINDEX(


(DLIB1,HDSYK.SMPCSI.CSI,DLIB), -----(5) (TGT1,HDSYK.SMPCSI.CSI,TARGET)) -----(6) SREL(Z038).ADD DDDEF(SMPPTS) DA(HDSYK.SMPPTS) -----(7) OLD.ADD DDDEF(SMPLOG) DA(HDSYK.SMPLOG) -----(8) MOD.ADD DDDEF(SMPLOGA) DA(HDSYK.SMPLOGA) -----(9) MOD.ADD DDDEF(SMPTLIB) DSPREFIX(HDSYK.TM) -----(10) VOLUME(#smp01) -----(11) UNIT(3390) CYL SPACE(5,5) DIR(200) DSNTYPE(PDS).ADD DDDEF(HDSYSAMT) DA(HDSYK.Vnnnnnn.HDSYSAMT) -----(12) OLD.ADD DDDEF(HDSYLNKT) DA(HDSYK.Vnnnnnn.HDSYLNKT) -----(13) OLD.ADD DDDEF(HDSYLPAT) DA(HDSYK.Vnnnnnn.HDSYLPAT) -----(14) OLD.ADD DDDEF(HDSYPRCT) DA(HDSYK.Vnnnnnn.HDSYPRCT) -----(15) OLD.ADD DDDEF(HDSYEXET) DA(HDSYK.Vnnnnnn.HDSYEXET) -----(16) OLD.ADD DDDEF(HDSYEXVT) DA(HDSYK.Vnnnnnn.HDSYEXVT) -----(17) OLD.ADD DDDEF(HDSYPNLT) DA(HDSYK.Vnnnnnn.HDSYPNLT) -----(18) OLD.ADD DDDEF(HDSYMSGT) DA(HDSYK.Vnnnnnn.HDSYMSGT) -----(19) OLD.ADD DDDEF(HDSYTABT) DA(HDSYK.Vnnnnnn.HDSYTABT) -----(20) OLD.ENDUCL.SET BDY(TGT1).UCLIN.ADD TARGETZONE(TGT1) RELATED(DLIB1) SREL(Z038).ADD DDDEF(HDSYSAMT) DA(HDSYK.Vnnnnnn.HDSYSAMT) -----(21) OLD.ADD DDDEF(HDSYLNKT) DA(HDSYK.Vnnnnnn.HDSYLNKT) -----(22) OLD.ADD DDDEF(HDSYLPAT) DA(HDSYK.Vnnnnnn.HDSYLPAT) -----(23) OLD.ADD DDDEF(HDSYPRCT) DA(HDSYK.Vnnnnnn.HDSYPRCT) -----(24) OLD.ADD DDDEF(HDSYEXET) DA(HDSYK.Vnnnnnn.HDSYEXET) -----(25) OLD.ADD DDDEF(HDSYEXVT)


DA(HDSYK.Vnnnnnn.HDSYEXVT) -----(26) OLD.ADD DDDEF(HDSYPNLT) DA(HDSYK.Vnnnnnn.HDSYPNLT) -----(27) OLD.ADD DDDEF(HDSYMSGT) DA(HDSYK.Vnnnnnn.HDSYMSGT) -----(28) OLD.ADD DDDEF(HDSYTABT) DA(HDSYK.Vnnnnnn.HDSYTABT) -----(29) OLD.ENDUCL.SET BDY(DLIB1).UCLIN.ADD DLIBZONE(DLIB1) RELATED(TGT1) SREL(Z038).ADD DDDEF(HDSYSAMD) DA(HDSYK.Vnnnnnn.HDSYSAMD) -----(30) OLD.ADD DDDEF(HDSYLNKD) DA(HDSYK.Vnnnnnn.HDSYLNKD) -----(31) OLD.ADD DDDEF(HDSYLPAD) DA(HDSYK.Vnnnnnn.HDSYLPAD) -----(32) OLD.ADD DDDEF(HDSYPRCD) DA(HDSYK.Vnnnnnn.HDSYPRCD) -----(33) OLD.ADD DDDEF(HDSYEXED) DA(HDSYK.Vnnnnnn.HDSYEXED) -----(34) OLD.ADD DDDEF(HDSYEXVD) DA(HDSYK.Vnnnnnn.HDSYEXVD) -----(35) OLD.ADD DDDEF(HDSYPNLD) DA(HDSYK.Vnnnnnn.HDSYPNLD) -----(36) OLD.ADD DDDEF(HDSYMSGD) DA(HDSYK.Vnnnnnn.HDSYMSGD) -----(37) OLD.ADD DDDEF(HDSYTABD) DA(HDSYK.Vnnnnnn.HDSYTABD) -----(38) OLD.ENDUCL.SET BDY(GLOBAL).LIST ALLZONES DDDEF./*

HDSYK3RC (SMP/E RECEIVE processing)The method for modifying HDSYK3RC, which performs SMP/E RECEIVEprocessing, is explained below.





(5)Change the volume allocated to the SMP/E dataset from #smp01 toSMP001.

(6)Change RFPREFIX from HITACHI to HTC1.BCM.

//HDSYK3RC JOB (ACCT#),'RECEIVE BC MANAGER', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E RECEIVE to uncompress .XMIT files.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//* HITACHI Refer to 4) for detail.//*//* 3) Select form of SMPPTFIN DD statement depending upon whether//* installing from tape or uploaded .XMIT file.//*//* 4) Modify the value of RFPREFIX to match the prefix of the data set//* that you created with the JCL 'RECVUPLD'. Refer to the comment//* (refer to 3.) in 'RECVUPLD' for more detail.//*//* 5) Submit the JCL.//*//*********************************************************************//RECEIVE EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)


//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPHOLD DD DUMMY//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//* Use DASD files if installing from .XMIT distribution//SMPPTFIN DD DSN=&PFX..CHYKnnn.SMPMCS,DISP=SHR//* Use tape files if installing from cartridge tape//*SMPPTFIN DD DSN=SMPMCS,DISP=OLD,//* VOL=SER=HDSYK,UNIT=3480,LABEL=(1,SL)//SMPCNTL DD *SET BDY(GLOBAL).RECEIVE SELECT(CHYKnnn) RFPREFIX(HITACHI) -----(6) LIST./*

HDSYK4AP (creating target libraries)The method for modifying HDSYK4AP, which creates the target library, isexplained below.





(6)When SMP/E APPLY is completed successfully, deleted the CHECK operand(changed to a comment) and re-execute the job. When upgradingBusiness Continuity Manager, if the dataset is to be installed in anexisting target library, change the CHECK operand to the COMPRESS(ALL)operand and re-execute the job.

//HDSYK4AP JOB (ACCT#),'APPLY BC MANAGER', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E APPLY to create the target libraries.


//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//*//* 3) Submit the JCL and make sure that no error occurs.//* 4) Remove CHECK operand from APPLY and re-submit the JCL to//* complete.//*//*********************************************************************//APPLY EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//SMPHOLD DD DUMMY//SMPSCDS DD DISP=SHR,DSN=&PFX..SMPSCDS//SMPMTS DD DISP=SHR,DSN=&PFX..SMPMTS//SMPSTS DD DISP=SHR,DSN=&PFX..SMPSTS//SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB// DD DISP=SHR,DSN=&PFX..SMPMTS//SMPCNTL DD *SET BDY(TGT1).APPLY SELECT(CHYKnnn) CHECK -----(6) ./*


HDSYK5AC (creating distribution libraries)The method for modifying HDSYK5AC, which creates the distribution library,is explained below.





(6)When SMP/E ACCEPT is completed successfully, deleted the CHECKoperand (changed to a comment) and re-execute the job. Whenupgrading Business Continuity Manager, if the dataset is to be installed inan existing distribution library, change the CHECK operand to theCOMPRESS(ALL) operand and re-execute the job.

//HDSYK5AC JOB (ACCT#),'ALLO UPLD FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2003, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E ACCEPT to create the distribution//* libraries.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//*//* 3) Submit the JCL and make sure that no error occurs.//* 4) Remove CHECK operand from ACCEPT and re-submit the JCL to//* complete.//*//*********************************************************************//ACCEPT EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)


//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//SMPHOLD DD DUMMY//SMPSCDS DD DISP=SHR,DSN=&PFX..SMPSCDS//SMPMTS DD DISP=SHR,DSN=&PFX..SMPMTS//SMPSTS DD DISP=SHR,DSN=&PFX..SMPSTS//SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB// DD DISP=SHR,DSN=&PFX..SMPMTS//SMPCNTL DD *SET BDY(DLIB1).ACCEPT SELECT(CHYKnnn) CHECK -----(6) ./*

HDSYK6RC (SMP/E RECEIVE processing for extended accesscontrol function)

The method for modifying HDSYK6RC, which performs SMP/E RECEIVEprocessing for the extended access control function, is explained below.





(6)


If you do not want to install the copy group access control function, delete"CHYKaaa,". If you do not want to install the specific command accesscontrol function, delete ",CHYKbbb".

(7)Change RFPREFIX from HITACHI to HTC1.BCM.

//HDSYK6RC JOB (ACCT#),'RECEIVE BC MANAGER', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2015, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E RECEIVE to uncompress .XMIT files.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//* HITACHI Refer to 4) for detail.//*//* 3) Select form of SMPPTFIN DD statement depending upon whether//* installing from tape or uploaded .XMIT file.//*//* 4) Modify the value of RFPREFIX to match the prefix of the data set//* that you created with the JCL 'RECVUPLD'. Refer to the comment//* (refer to 3.) in 'RECVUPLD' for more detail.//*//* 5) Submit the JCL.//*//*********************************************************************//RECEIVE EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.


//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPHOLD DD DUMMY//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//* Use DASD files if installing from .XMIT distribution//SMPPTFIN DD DSN=&PFX..CHYKnnn.SMPMCS,DISP=SHR//* Use tape files if installing from cartridge tape//*SMPPTFIN DD DSN=SMPMCS,DISP=OLD,//* VOL=SER=HDSYK,UNIT=3480,LABEL=(1,SL)//SMPCNTL DD *SET BDY(GLOBAL).RECEIVE SELECT( CHYKaaa /*adds the access control of copy groups.*/ -(6) ,CHYKbbb /*adds the access control of commands. */ -(6) ) RFPREFIX(HITACHI) -----(7) LIST./*

HDSYK7AP (creating target libraries for extended accesscontrol function)

The method for modifying HDSYK7AP, which creates the target library for theextended access control function, is explained below.





(6)If you do not want to install the copy group access control function, delete"CHYKaaa,". If you do not want to install the specific command accesscontrol function, delete ",CHYKbbb".

(7)When SMP/E APPLY is completed successfully, deleted the CHECK operand(changed to a comment) and re-execute the job.

//HDSYK7AP JOB (ACCT#),'APPLY BC MANAGER', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)


//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2015, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E APPLY to create the target libraries.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//*//* 3) Submit the JCL and make sure that no error occurs.//* 4) Remove CHECK operand from APPLY and re-submit the JCL to//* complete.//*//*********************************************************************//APPLY EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//SMPHOLD DD DUMMY//SMPSCDS DD DISP=SHR,DSN=&PFX..SMPSCDS//SMPMTS DD DISP=SHR,DSN=&PFX..SMPMTS//SMPSTS DD DISP=SHR,DSN=&PFX..SMPSTS//SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB// DD DISP=SHR,DSN=&PFX..SMPMTS//HDSYLNKD DD DISP=SHR,DSN=&PFX..&VRM..HDSYLNKD//SMPCNTL DD *SET BDY(TGT1).APPLY SELECT(


CHYKaaa /*adds the access control of copy groups.*/-(6) ,CHYKbbb /*adds the access control of commands. */-(6) ) CHECK -----(7) ./*

HDSYK8AC (creating distribution libraries for extendedaccess control function)

The method for modifying HDSYK8AC, which creates the distribution libraryfor the extended access control function, is explained below.





(6)If you do not want to install the copy group access control function, delete"CHYKaaa,". If you do not want to install the specific command accesscontrol function, delete ",CHYKbbb".

(7)When SMP/E ACCEPT is completed successfully, deleted the CHECKoperand (changed to a comment) and re-execute the job.

//HDSYK8AC JOB (ACCT#),'ALLO UPLD FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2015, 2016, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E ACCEPT to create the distribution libraries.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSYK Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)


//*//* 3) Submit the JCL and make sure that no error occurs.//* 4) Remove CHECK operand from ACCEPT and re-submit the JCL to//* complete.//*//*********************************************************************//ACCEPT EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//SMPHOLD DD DUMMY//SMPSCDS DD DISP=SHR,DSN=&PFX..SMPSCDS//SMPMTS DD DISP=SHR,DSN=&PFX..SMPMTS//SMPSTS DD DISP=SHR,DSN=&PFX..SMPSTS//SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB// DD DISP=SHR,DSN=&PFX..SMPMTS//SMPCNTL DD *SET BDY(DLIB1).ACCEPT SELECT( CHYKaaa /*adds the access control of copy groups.*/-(6) ,CHYKbbb /*adds the access control of commands. */-(6) ) CHECK -----(7) ./*



BSample Scripts

This appendix explains the sample scripts.

□ HDSRFEPR (viewing access permissions for the extended access controlfunction)

Sample Scripts B-1Hitachi Business Continuity Manager Installation Guide

HDSRFEPR (viewing access permissions for the extendedaccess control function)

The following shows the details of HDSRFEPR for viewing the accesspermissions that are set by the extended access control function.

Input parameterSpecify the resources or commands for which you want to check theaccess control, in the following format:

[ 1PREFIX(prefix_name)][ 1CGNAME(cg_name)][ 1CGTYPE({SI|TC|TCA|UR})][ 1CLI({YKQRYDEV|YKMAKE|YKDELETE|YKRECVER})]

OutputEither of the following is output depending on the parameter youspecified:AUTHORIZED: AccessibleUNAUTHORIZED: Not accessible

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2015, 2016, Hitachi, Ltd. *//* *//**********************************************************************//* *//* HDSRFEPR - This is a sample script that uses the RLIST *//* RACF command to collect information about RACF profiles for *//* the BCM advanced access control facility. *//* *//* The script response indicates whether you have been granted *//* view permission for each element specified in a parameter. *//* *//* The available parameters are as follows: *//* *//* [ PREFIX(prefix_name)] *//* [ CGNAME(cg_name)] *//* [ CGTYPE({SI|TC|TCA|UR})] *//* [ CLI({YKQRYDEV|YKMAKE|YKDELETE|YKRECVER})] *//* *//**********************************************************************//**********************************************************************//* Note: When this sample program is executed in SYSTEM REXX, *//* please uncomment the instructions lines below. *//**********************************************************************//* * If ADDRESS() /= 'TSO' Then * Do; * SAY 'TSO service is not available.' * EXIT -3; * End; * Else * Nop; */ /* Parse argument specified in the EXEC command. */ Parse Upper Arg @options ;

B-2 Sample ScriptsHitachi Business Continuity Manager Installation Guide

Parse Upper Value @options with 'PREFIX(' opt_prefix ')'; Parse Upper Value @options with 'CGNAME(' opt_cgname ')'; Parse Upper Value @options with 'CGTYPE(' opt_cgtype ')'; Parse Upper Value @options with 'CLI(' opt_cli ')'; /* Execute OUTTRAP function. *//* Responses of RLIST command are stored line. temporary. */ push_trap = OUTTRAP(); void = OUTTRAP('line.',,'NOCONCAT'); /* When PREFIX requested -------------------------------------------- */If opt_prefix /= "" Then Do; Call check_auth "PFX."opt_prefix ; If result = 0 Then SAY "PREFIX("opt_prefix") : AUTHORIZED" ; Else SAY "PREFIX("opt_prefix") : UNAUTHORIZED" ; End; Else Nop; /* ------------------------------------------------------------------ */ /* When CGNAME requested -------------------------------------------- */If opt_cgname /= "" Then Do; Call check_auth "CGNAME."opt_cgname ; If result = 0 then SAY "CGNAME("opt_cgname") : AUTHORIZED" ; Else SAY "CGNAME("opt_cgname") : UNAUTHORIZED" ; End; Else Nop; /* ------------------------------------------------------------------ */ /* When CGTYPE requested -------------------------------------------- */If opt_cgtype /= "" Then Do; Call check_auth "CGTYPE."opt_cgtype ; If result = 0 Then SAY "CGTYPE("opt_cgtype") : AUTHORIZED" ; Else SAY "CGTYPE("opt_cgtype") : UNAUTHORIZED" ; End; Else Nop; /* ------------------------------------------------------------------ */ /* When CLI requested ----------------------------------------------- */If opt_cli /= "" Then Do; Call check_auth "CLI."opt_cli ; If result = 0 Then SAY "CLI("opt_cli") : AUTHORIZED" ; Else SAY "CLI("opt_cli") : UNAUTHORIZED" ; End; Else Nop; /* ------------------------------------------------------------------ */ /* When no available parameter exist, show the syntax --------------- */If line.0 = 0 Then Do; SAY "-------- Available Parameters ---------" SAY " PREFIX(prefix_name)" SAY " CGNAME(cg_name)"

Sample Scripts B-3Hitachi Business Continuity Manager Installation Guide

SAY " CGTYPE(SI|TC|TCA|UR)" SAY " CLI(YKQRYDEV|YKMAKE|YKDELETE|YKRECVER)" SAY "---------------------------------------" End; Else Nop; /* ------------------------------------------------------------------ */ void = OUTTRAP(push_trap); Exit 0; /* Exec RLIST ------------------------------------------------------- */check_auth : Parse Upper Arg opt_element ; Address TSO "RLIST FACILITY STGADMIN.YKA.BCM."opt_element ; If rc = 0 Then Do ; Parse Upper Var line.7 ent_lvl ent_own ent_uac ent_acc ent_wrn ; If ent_acc /== "NONE" Then Return 0 ; Else Nop ; End ; Else Nop ; Return 4 ; /* ------------------------------------------------------------------ */

B-4 Sample ScriptsHitachi Business Continuity Manager Installation Guide

CNotes on upgrading Business Continuity

Manager

This section provides notes on upgrading Business Continuity Manager.

□ When upgrading Business Continuity Manager from a version earlier than6.6.1 to 6.6.1 or later


□ When upgrading Business Continuity Manager from a version earlier than7.4 to 7.4 or later



Notes on upgrading Business Continuity Manager C-1Hitachi Business Continuity Manager Installation Guide

When upgrading Business Continuity Manager from aversion earlier than 6.6.1 to 6.6.1 or later

In Business Continuity Manager version 6.6.1 or later, when the YKIMPORTcommand is executed, the P-VOLs and S-VOLs of copy pairs to be defined areautomatically checked to see whether their capacities are the same.

If the P-VOL and S-VOL capacities are not the same, the YKJ215E message isoutput and the copy group definition file is not created. If a volume capacitycannot be acquired, the YKJ214W message is output and the copy groupdefinition file is created.

To define a copy pair without checking the capacities of its volumes (as is thecase in Business Continuity Manager versions earlier than 6.6.1), specifyNOCHECK for the CAPACITY parameter of the YKIMPORT command.


Note the following when upgrading to Business Continuity Manager version6.7.1 or later.

Route Config panelFrom the Route Config panel, when you select a route list definition file andedit it, the route list definition files for the route list IDs that are not selectedare also loaded. If there are any unnecessary route list definition files, deletethem.

If there is an error in a route list definition file for a route list ID that is notselected, the Exception Message panel is displayed. By closing the ExceptionMessage panel, you can edit a selected route list definition file.

Route list structureBecause multiple command device line definitions are now supported, theroute list structure has been changed. If a REXX variable shown in thefollowing table is in a route list structure that is referenced by a script that isin a version of Business Continuity Manager earlier than 6.7.1, and multiplecommand device lines are defined for a route, the script must be edited.

Table C-1 REXX variables in a route list structure edited in BusinessContinuity Manager 6.7.1 or later

No. REXX variables Description

1 HCC.ROUTELIST.dadid.APID APID

2 HCC.ROUTELIST.dadid.n.n.CDEV.Devn Device number of the command devicein the storage system

C-2 Notes on upgrading Business Continuity ManagerHitachi Business Continuity Manager Installation Guide

No. REXX variables Description

3 HCC.ROUTELIST.dadid.n.n.CDEV.Volser Volume serial number of the commanddevice in the storage system

4 HCC.ROUTELIST.dadid.n.n.CDEV.CUNum Control unit number of the commanddevice in the storage system

5 HCC.ROUTELIST.dadid.n.n.CDEV.SSID SSID of the command device in thestorage system

6 HCC.ROUTELIST.dadid.n.n.CDEV.CCA Command control address of thecommand device in the storage system

When upgrading Business Continuity Manager from aversion earlier than 7.4 to 7.4 or later

If you upgrade Business Continuity Manager to 7.4 or later, a CTGinformation CSV file is required to execute the YKIMPORT or YKEXPORTcommand for Universal Replicator copy groups. Before executing eithercommand, assign and catalog the CSV file datasets, and then, for theYKIMPORT command, specify the CSV file with the DD name INCTG, and, forthe YKEXPORT command, specify the CSV file with the DD name OUTCTG. Ifyou execute either command without specifying the CTG information CSV file,the command will fail with the YKJ150E message.


If you upgrade Business Continuity Manager to 7.6.1 or later, the defaultvalue of the unit to manage the differential data when defining copy groupsfor TrueCopy and TrueCopy Asynchronous will be changed from cylinder totrack. Specifically, the default value of DIF UNIT in the following panels willchange from CYL to TRK:

• Copy Group Attributes For Container (TC) panel• Copy Group Attributes (TC) panel• Copy Group Attributes For Container (TCA) panel• Copy Group Attributes (TCA) panel

For details, see the Hitachi Business Continuity Manager Reference Guide.


If you upgrade Business Continuity Manager to 8.1.4 or later, journal volumeinformation will not be acquired by Remote Scan or NG Scan. Take note ofthe following points:

Notes on upgrading Business Continuity Manager C-3Hitachi Business Continuity Manager Installation Guide

• If you only upgrade Business Continuity Manager to 8.1.4 or later, thejournal volume information in the disk configuration definition files thatwere created by using a Remote Scan or NG Scan when the version ofBusiness Continuity Manager was earlier than 8.1.4 will not be deleted. Todelete the journal volume information, delete the disk configurationdefinition files, and then scan the storage system to re-create diskconfiguration definition files.

• If you assign dummy device numbers in the Edit Device Number for CUpanel, dummy device numbers are assigned in ascending order of thecommand control address values. Scans for Business Continuity Managerversion 8.1.4 or later skip the command control addresses of journalvolumes. For this reason, the command control addresses will notcorrespond to the dummy device numbers on one-to-one basis. Forexample, if the command control address of a journal volume is 02 andthe beginning value of the dummy device numbers is 0000, therelationship of "command control address: dummy device number" will beas follows:

¢ 00: 0000¢ 01: 0001¢ 03: 0002¢ 04: 0003If necessary, in the CCA Selection List for Edit devn panel, correct therelationship of "command control address: dummy device number".

• If you link Business Continuity Manager with Replication Manager, journalvolume information will not be acquired by Remote Scan or NG Scan.

C-4 Notes on upgrading Business Continuity ManagerHitachi Business Continuity Manager Installation Guide

DNotes when multiple versions of

Business Continuity Manager exist

This section gives notes on upgrade processing when multiple versions ofBusiness Continuity Manager exist in a system.

□ Configuration files

□ License information dataset

□ Changed display for the license name

□ Prefix for the license information dataset

□ Installing a license

□ Specifying Business Continuity Manager log output destination (LOGPUT)

□ Specifying whether to output the CLI command-execution logs (SYSLOG)

□ Setting up the Resource Access Control Facility (RACF) when multipleversions of Business Continuity Manager exist

□ Registering a user SVC dynamically

□ User SVC for suppressing IOS002A messages

□ Available versions of user SVCs

Notes when multiple versions of Business Continuity Manager exist D-1Hitachi Business Continuity Manager Installation Guide

Configuration filesConfiguration files created in an older version of Business Continuity Managercan be used in a newer version as they are. However, once you edit theconfiguration files created in an older version of Business Continuity Managerby using a newer version, the older version can no longer read thoseconfiguration files.

Therefore, in an environment where multiple versions of Business ContinuityManager exist, Hitachi recommends that you use different configuration filesfor each version of Business Continuity Manager.

License information datasetThe license information dataset can be shared by old and new versions ofBusiness Continuity Manager. However, the license will be dealt with as aninvalid license unless that license is valid for the relevant version of BusinessContinuity Manager.

Changed display for the license nameIn Business Continuity Manager 5.0, display of the Business ContinuityManager Extended CT Group license in the Manage Licenses panel waschanged.

Business Continuity Manager versions 4.0 to 4.2 and Business ContinuityManager versions 5.0 to 5.3 display different license names in this panel, butuse the same key code. Copycentral 2.0, Business Continuity Manager 3.0,and Business Continuity Manager 4.0 to 4.2 display the same license name inthe panel, but use different key codes.

• In Copycentral 2.0, Business Continuity Manager 3.0, and BusinessContinuity Manager 4.0 to 4.2:The Business Continuity Manager Extended CT Group license is displayedas Extended CT Group.

• In Business Continuity Manager 5.0 to 5.3:The Business Continuity Manager Extended CT Group license is displayedas TC Sync Extended CTG.

• In Business Continuity Manager 5.5 or later:The Business Continuity Manager Extended CT Group license wascombined with the Business Continuity Manager Basic license. If Basic isdisplayed, the TrueCopy consistency preservation function can be used.

Prefix for the license information datasetBusiness Continuity Manager versions earlier than 4.1 do not support theBusiness Continuity Manager environment variable YKLCNS2. Therefore, ifboth Business Continuity Manager versions earlier than 4.1 and Business

D-2 Notes when multiple versions of Business Continuity Manager existHitachi Business Continuity Manager Installation Guide

Continuity Manager versions 4.1 or later exist in a system, do not specify theenvironment variable YKLCNS2. If this parameter is specified, one of theBusiness Continuity Managers will not be able to read the license informationdataset.

Installing a licenseIn Business Continuity Manager versions 5.0 to 5.3, a license obtained inBusiness Continuity Manager versions 4.0 to 4.2 is treated as follows:

• A permanent license can be used without re-installation.• A temporary license or emergency license cannot be used as they are.

They need to be re-installed.

Specifying Business Continuity Manager log outputdestination (LOGPUT)

Business Continuity Manager earlier than version 4.2 does not support the&YKLOGPT system symbol. Therefore, in an environment where BusinessContinuity Manager earlier than version 4.2 and Business Continuity Manager4.2 or later exist, to specify the Business Continuity Manager log outputmethod, Hitachi recommends that you execute the YKSETENV command withthe LOGPUT parameter specified.

Specifying whether to output the CLI command-executionlogs (SYSLOG)

The output method of the CLI command-execution logs is determined by thecombination of the value set by the YKSETENV command, the value set by the&YKSYSLG system symbol, and the version of Business Continuity Manager tobe used.

The following table lists whether to output the CLI command-execution logsand the output destination determined by the combination of the value set bythe YKSETENV command, the value set by &YKSYSLG, and the version ofBusiness Continuity Manager.

Caution:

• The settings made by &YKSYSLG are enabled in Business ContinuityManager 5.1 or later versions.

• The SYSLOG=CONSOLE setting of the YKSETENV command and the CONSOLEsetting specified by &YKSYSLG are enabled in Business Continuity Manager7.6 or later versions.


Table D-1 If the settings are made by using the YKSETENV command of aversion of Business Continuity Manager 7.6 or later

Value set by usingthe YKSETENV

command

Value set byusing &YKSYSLG

Version of Business Continuity Managerbeing run

Earlier than5.1

From 5.1 to7.5 7.6 or later

SYSLOG=YES YES Output to SYSLOG

CONSOLENO

No specificationor specificationerror

SYSLOG=CONSOLE YES Output to SYSLOG Output to theconsoleCONSOLE

NO


SYSLOG=NO YES Not output

CONSOLENO


'SYSLOG='No specification

YES Output toSYSLOG

Output toSYSLOG

Output toSYSLOG

CONSOLE Output to theconsole

NO Not output Not output


Output toSYSLOG

Output toSYSLOG

Table D-2 If the settings are made by using the YKSETENV command of aversion of Business Continuity Manager from 5.1 to 7.5

Value set byusing theYKSETENVcommand



Earlier than5.1


SYSLOG=YES YES Output to SYSLOG Output toSYSLOG#





Earlier than5.1


CONSOLENO



CONSOLENO


'SYSLOG='No specification

YES Output toSYSLOG

Output toSYSLOG

Output toSYSLOG

CONSOLE Output to theconsole

NO Not output Not output


Output toSYSLOG

Output toSYSLOG

#This is output to the console if the following condition is met:SYSLOG=CONSOLE was first set by using the YKSETENV command of version7.6 or later of Business Continuity Manager, and SYSLOG=YES was then setby using the YKSETENV command of version 5.1 to 7.5 of BusinessContinuity Manager.

Table D-3 If the settings are made by using the YKSETENV command of aversion of Business Continuity Manager earlier than 5.1




Earlier than5.1


SYSLOG=YESNo specification

YES Output toSYSLOG

Output toSYSLOG

Output toSYSLOG#1

CONSOLE Output to theconsole#2

NO Not output#3 Not output#1#2





Earlier than5.1



Output toSYSLOG

Output toSYSLOG#1


CONSOLENO


#1This is output to the console if the following condition is met:SYSLOG=CONSOLE was first set by using the YKSETENV command of version7.6 or later of Business Continuity Manager, and SYSLOG=YES was then setby using the YKSETENV command of a version of Business ContinuityManager earlier than 5.1.

#2This is output to SYSLOG if the following condition is met: SYSLOG=YESwas first set by using the YKSETENV command of version 5.1 or later ofBusiness Continuity Manager, and SYSLOG=YES was then set by using theYKSETENV command of a version of Business Continuity Manager earlierthan 5.1.

#3This is output to SYSLOG if the following condition is met: SYSLOG=YES orSYSLOG=CONSOLE was first set by using the YKSETENV command of version5.1 or later of Business Continuity Manager, and SYSLOG=YES was then setby using the YKSETENV command of a version of Business ContinuityManager earlier than 5.1.

Setting up the Resource Access Control Facility (RACF)when multiple versions of Business Continuity Managerexist

In Business Continuity Manager 6.0 and later versions, you must set up theResource Access Control Facility (RACF) before using the product. In theseversions, CLI command execution permissions are checked by RACF.

Also, if you register user SVCs in an environment where a Business ContinuityManager whose version is earlier than 6.0 coexists with a Business ContinuityManager whose version is 6.0 or later, CLI command execution permissions


are checked by RACF. Therefore, you must also set up RACF before using theproduct in such an environment.

When you set up the RACF, you must add CLI command executionpermissions to user accounts. For details, see Setting security for CLIcommands, YKAGENTD, and YKBTSCAN on page 2-18.

Registering a user SVC dynamicallyIf a user SVC was registered using the YKALCSVC command of BusinessContinuity Manager 5.1 or later, you cannot use the YKALCSVC command forBusiness Continuity Manager versions earlier than 5.1 to delete the user SVC.Therefore, if multiple versions exist in an environment, make sure that youuse the YKALCSVC command of Business Continuity Manager 5.1 or later.

User SVC for suppressing IOS002A messagesWith Business Continuity Manager versions earlier than 6.1, user SVCs cannotbe used to suppress output of IOS002A messages when the I/O path betweenthe host and the storage system is disconnected while device scanning isbeing performed. Therefore, in a mixed-version environment, make sure toalways use user SVCs) of Business Continuity Manager version 6.1 or later.

Available versions of user SVCsIf you want to install more than one version of Business Continuity Manager,note the minimum user SVC version required by each Business ContinuityManager instance, and then install a version of user SVC that is compatiblewith all the Business Continuity Manager versions to be installed. For detailsabout the user SVC versions required by Business Continuity Manager, seeUser SVC versions required by Business Continuity Manager on page 2-46.



EConventions in syntax explanations

This section describes the conventions in syntax explanations and the syntaxelements that are used.

□ Conventions in syntax explanations

Conventions in syntax explanations E-1Hitachi Business Continuity Manager Installation Guide

Conventions in syntax explanationsThe following table shows the conventions used in syntax explanations.

Table E-1 Conventions in syntax explanations

Example font orsymbol Convention

| (stroke) Indicates delimiters between multiple items and represents theword "or".Example:"A|B|C" means "A, B, or C".

[ ] Items enclosed by these brackets can be omitted.If multiple items are described, all the items are omitted oronly one of them is selected.Example:[A] means either "specify nothing" or "specify A".

{ } (curly brackets) One of items must be selected from among the multiple itemsenclosed by these brackets. Delimiters between items areindicated as |.

Example:{A|B|C} means you must specify A, B, or C.

... (dotted line) The item indicated immediately before this symbol can berepeated and specified multiple times.Example:"A, ..." means you can specify the items after A as manytimes as necessary.

Italics This indicates that the item is an optional value specified bythe user.

_ (underscore) Indicates the assumed value for the system when the itemsenclosed in the selection symbol are omitted.

Indicates exactly one space character.

nIndicates n or more space characters.

~ This indicates that the item before this symbol should bedescribed according to the syntax enclosed by < >, << >>, or(( )) following this symbol.

< > Indicates a syntax element that must be used when specifyingthe item.

<< >> Indicates a default value used by the system if the item isomitted.

(( )) Indicates the range of values that can be specified.

The following table shows the syntax elements that are used.

E-2 Conventions in syntax explanationsHitachi Business Continuity Manager Installation Guide

Table E-2 Syntax elements

Syntax element Valid value Example

numeric characters 0|1|2|3|4|5|6|7|8|9 --

alphabeticcharacters

A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z|a|b|c|d|e|f|g|h|i|j|k|l|m|n|o|p|q|r|s|t|u|v|w|x|y|z

--

alphanumericcharacters

alphabetic-characters and numeric-characters --

hexadecimalnumbers

0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F --

PREFIX stringDAD stringROUTE stringROUTELABEL string

A string consisting of one or more parts, joined byperiods (.). Each part consists of uppercasealphabetic characters and numeric characters. Thefirst character for each part must be an uppercasecharacter. Each part consists of 1 to 8 characters.

ABC.DEF

Conventions in syntax explanations E-3Hitachi Business Continuity Manager Installation Guide

E-4 Conventions in syntax explanationsHitachi Business Continuity Manager Installation Guide

Acronyms and abbreviations

The following acronyms and abbreviations might be used in this guide.

A

APapplication program

APIapplication programming interface

B

Business Continuity ManagerA generic name for the following products:Hitachi Business Continuity Manager BasicHitachi Business Continuity Manager UR 4x4 Extended CTG

C

CCAcommand control address

CCWchannel command word

CHAchannel adapter

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Acronyms-1Hitachi Business Continuity Manager Installation Guide

CLIcommand line interface

CSAcommon service area

CSBchannel status byte

CUcontroller unit

D

DADdevice address domain

DASDdirect access storage device

DBCSdouble byte character set

Device ManagerHitachi Device Manager

DKCdisk controller

DLIBdistribution libraries

DSBdevice status byte

DSORGdata set organization

E

EXCTGextended consistency group



F

FTPfile transfer protocol

G

GTFgeneralized user interface

GUIgraphical user interface

H

HTTPHyperText Transfer Protocol

HTTPSHyperText Transfer Protocol Security

I

IBM HTTP ServerIBM HTTP Server for z/OS

IDIdentifier

IPv4Internet Protocol Version 4

IPv6Internet Protocol Version 6

ISPFinteractive system productivity facility



L

LDEVlogical device

LPARlogical partition

LRECLlogical record length

M

M-JNLmaster journal

Mainframe AgentHitachi Device Manager Mainframe Agent

MCUmain control unit

MIHmissing interrupt handler

O

OSoperating system

P

P-VOLprimary volume

PPRCPeer to Peer Remote Copy

PSWprogram status word



R

R-JNLrestore journal

RACFresource access control facility

RAIDredundant array of independent disks

RCUremote control unit

RECFMrecord format

Replication ManagerHitachi Replication Manager

REXXrestructured extended executor

RPORecovery Point Objective

S

S-VOLsecondary volume

SAFsystem authorization facility

SCPstate change pending

SDSFsystem display and search facility

ShadowImageShadowImage for Mainframe

SMP/Esystem modification program extended



SSIDstorage system ID

SVCsupervisor call

T

TCTrueCopy for Mainframe (TrueCopy Synchronous)

TCATrueCopy for Mainframe (TrueCopy Asynchronous)

Tiered Storage Manager for MainframeHitachi Tiered Storage Manager for Mainframe

TPC-RIBM Tivoli Storage Productivity Center for Replication for System z

TSEtrack space-efficient

TSO/ETime Sharing Option/Extensions

U

Universal ReplicatorUniversal Replicator for Mainframe

USPA generic name for the following products:Hitachi Universal Storage PlatformHitachi Network Storage Controller

USP VA generic name for the following products:Hitachi Universal Storage Platform VHitachi Universal Storage Platform VM



V

VMVirtual Machine

VSPHitachi Virtual Storage Platform

VSP G1000Hitachi Virtual Storage Platform G1000

X

XMLextensible markup language

XRCextended remote copy

Z

z/LinuxLinux on IBM System z





Index

A

AUDITLOG 3-27authentication method

between Replication Manager and IBM HTTPServer 3-16

B

BCM log datarequired device capacity for 2-6

Business Continuity Managerinstallation with SMP/E 2-10installing 2-1, 2-10licenses 1-2overview 1-1prerequisites 1-3setting environment variable 2-26settings for using ISPF panel 2-15upgrading 2-40, 2-44

C

cataloged procedure for startup (for BusinessContinuity Manager agents)

changing 3-35changing

cataloged procedure for startup (for BusinessContinuity Manager agents) 3-35

choosingdataset to be used 2-2

CLI command-execution logs, outputting 2-29CLI commands

settings for using in TSO/E environments 2-14

collecting trace logcreating 3-19

commandssettings for environment configuration 2-17

configuration exampleHTTPS connections between ReplicationManager and IBM HTTP Server 3-16when connecting Replication Manager and theBusiness Continuity Manager agent via IPv63-14

configuration files, backing up 2-42conventions in syntax explanations E-1copy group definition file (temporary file name)3-10creating

initialization parameter 3-19creating BCM Monitor parameter file 4-3creating cataloged procedure for startup for BCMMonitor 4-4creating configuration file for BCM Monitor 4-3

D

dataset configuration file, creating (ReplicationManager linkage) 3-9datasets, backing up 2-42DELETE parameter

YKALCSVC command 2-24designing

storage 2-5DETAIL parameter

YKDSPENV command 2-33determining

required memory 2-7device capacity

Index-1Hitachi Business Continuity Manager Installation Guide

required by BCM log data 2-6DEVN

format 3-26directive

CacheDisable 3-14KeepAlive 3-14Listen 3-14LoadModule 3-14ProxyPass 3-15ProxyPassReverse 3-15Timeout 3-15

directives (for HTTPS connection)AuthType 3-18AuthUserFile 3-19CacheDisable 3-17KeepAlive 3-18Listen 3-18LoadModule 3-18ProxyPass 3-18ProxyPassReverse 3-18Require 3-19Timeout 3-18

disk configuration definition file (temporary file)3-10distribution libraries 2-4DLIB 2-4

E

environmentsetting up 2-12

environment configuration commandssettings for using 2-17

environment variables, checking 2-41environment, setting up (Replication Managerlinkage) 3-2example of using ALTLIB command and LIBDEFservice 2-16EXEC statement 3-34, 4-4

F

FMID 2-3format

license information dataset 2-36YKALCSVC command 2-24YKDSPENV command 2-33YKSETENV command 2-31

G

general procedure for setting up environment forBCM Monitor 4-2

H

HDSRFEPR (sample scripts) B-2host ID

specifying 2-27HOSTNAME parameter 3-23how to use

SETINIT command 3-20htpasswd command 3-18httpd.conf

settings to be specified for IPv6 connection 3-14

I

IEASVCxx parmlib member, using to register userSVC 2-23initialization parameter

creating 3-19initialization parameters

specification examples 3-32installation

Business Continuity Manager 2-10preparing 2-2

installation without SMP/E 2-12installing

Business Continuity Manager 2-1Business Continuity Manager with SMP/E 2-10

ISPF panelsettings 2-16using with Business Continuity Manager 2-15

J

JES (Job Entry Subsystem) startup procedure 4-4JES startup procedure 3-33

K

key code, directly entering 2-35


L

licenseregistering 2-34

license information datasetformat 2-36

license key dataset 2-35license key file, using 2-34licenses

checking 2-41licenses provided by Business Continuity Manager

1-2LOGLEVEL parameter 3-26LOGPUT parameter

YKSETENV command 2-31

M

MODE 3-27modifying

sample JCL A-1

N

notespecifying DEVN parameter 3-26specifying PREFIX parameter 3-25

note when multiple versions of Business ContinuityManager exist D-1notes on upgrading Business Continuity Manager

C-1

O

operating system prerequisites 1-3overview

Business Continuity Manager 1-1setup procedure for establishing HTTPSconnections 3-17

overview of environment settings 3-2

P

parametersdetermining whether parameters can bespecified more than once 3-28

planning DASDstorage attributes 2-4

PORT parameter 3-23pre-upgrade procedure 2-43PREFIX parameter 3-23Preparations for installing Business ContinuityManager 2-9preparing

installation 2-2prerequisite conditions 1-3prerequisites for using

z/Linux volume 1-4PROC statement 3-34PROFILE.TCPIP profile 3-11program prerequisites 1-3program, backing up before migration 2-42

R

RECVWAITTIME parameter 3-23required memory

determining 2-7Required settings for the httpd.conf file to set up areverse proxy server 3-17Required settings for the httpd.conf file to set upauthentication 3-18required settings in the httpd.conf file to set upauthentication

AuthName 3-18

S

sample JCLALLOUPLD A-2for creating license information datasets 2-37HDSYK1AL A-10HDSYK2DF A-12HDSYK3RC A-15HDSYK4AP A-17HDSYK5AC A-19HDSYK6RC A-20HDSYK7AP A-22HDSYK8AC A-24HDSYKSIN A-6modifying A-1RECVUPLD A-5SMPALLOC A-8

sample scripts B-1security settings 2-18security, setting


dataset security 3-12server certificate 3-16SETINIT command

format 3-22how to use 3-20

settingBusiness Continuity Manager environmentvariable 2-26TCP/IP port number 3-11

settingsISPF panel 2-16

setting up HTTPS connection (IBM HTTP Server)3-15setting up IBM HTTP Server 3-13setting up security for BCM Monitor 4-2setting up security for Business ContinuityManager Agents 3-12setting up the environment when linking withReplication Manager 3-1setting up the Resource Access Control Facility(RACF) when linking with Replication Manager 3-12settings for connecting via IPv6 (IBM HTTP Server)

3-13simple installation 2-12specifying

host ID 2-27standard cataloged procedure for startup (forBusiness Continuity Manager agents) 3-33standard cataloged procedure for startup in theexpanded format (for Business Continuity Manageragents)

expanded format 3-33starting YKSTART dynamically 2-16STEPLIB DD statement 3-35, 4-5storage

designing 2-5storage attributes

planning DASD 2-4storage systems, supported 1-4SUMMARY parameter

YKDSPENV command 2-33SVC-number parameter

YKALCSVC command 2-24syntax elements E-3SYSABEND DD statement 3-34, 4-5SYSEXEC DD statement 3-35, 4-5SYSLOG parameter

YKSETENV command 2-32system logger service

disabling 2-28enabling 2-28

SYSTSIN DD statement 3-34, 4-5SYSTSPRT DD statement 3-34, 4-4

T

target library 2-5TCP/IP port number

setting 3-11TSO/E environments

settings for CLI commands 2-14types

distribution media 2-2

U

upgradingBusiness Continuity Manager 2-44what to check after 2-44what to check before 2-41

user SVCregistering 2-23

user SVC numberchecking 2-42

V

verification after installation and setup 2-39

Y

YKAGENTexpanded format 3-33

YKALCSVC commandDELETE parameter 2-24format 2-24SVC-number parameter 2-24to register user SVC 2-24

YKCMDIF parameterYKSETENV command 2-31

YKDSPENV commandDETAIL parameter 2-33format 2-33SUMMARY parameter 2-33

YKLCNSE parameterYKSETENV command 2-31


YKLIST DD statement 3-34YKLOG01 DD statement 3-35, 4-5YKLOG02 DD statement 3-35, 4-5YKMONCG DD statement 4-4YKMONOPT DD statement 4-4YKPARM DD statement 3-34YKSETENV command

format 2-31LOGPUT parameter 2-31SYSLOG parameter 2-32YKCMDIF parameter 2-31YKLCNS2 parameter 2-31YKLCNSE parameter 2-31

YKSTARTstarting dynamically 2-16



Hitachi Business Continuity Manager Installation Guide

Hitachi Data Systems

Corporate Headquarters2845 Lafayette StreetSanta Clara, California 95050-2639U.S.A.www.hds.com

Regional Contact Information

Americas+1 408 970 [email protected]

Europe, Middle East, and Africa+44 (0)1753 [email protected]

Asia Pacific+852 3189 [email protected]

MK-95HC104-25

Documents

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