HP StorageWorks P9000 for Business Continuity Manager Software Installation Guide Abstract This manual describes how to install the following program products: HP StorageWorks Business Continuity Manager Software Basic, HP StorageWorks Business Continuity Manager Universal Replicator 4x4 Extended CT Software, and HP StorageWorks Business Continuity Manager Universal Replicator Extended CT Group.
© Copyright 2007, 2011 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview of HP StorageWorks P9000 for Business Continuity Manager Software......................................................................................................7 Licenses Provided for Business Continuity Manager.......................................................................7 Prerequisite Conditions..............................................................................................................9 Operating System Prerequisites....................................
YKSETENV command format..........................................................................................38 YKDSPENV command format..........................................................................................40 Registering a License..........................................................................................................41 Using the License Key File...............................................................................................
Standard Cataloged Procedure for Startup in the Expanded Format.....................................77 4 Setting Up an Environment for Business Continuity Manager Monitor..............79 General Procedure for Setting Up an Environment for Business Continuity Manager Monitor.............79 Setting Up the Security for Business Continuity Manager Monitor..................................................80 Creating Configuration Files for Business Continuity Manager Monitor.....................................
D Using BCM with z/OS Running as a Guest Under z/VM............................112 Introduction..........................................................................................................................112 APARs/PTFs.........................................................................................................................112 PTF to HCPGDS module....................................................................................................112 PTF to HCPMD2 module............
1 Overview of HP StorageWorks P9000 for Business Continuity Manager Software This chapter explains the provided licenses, prerequisite conditions, and supported storage systems. For more detailed information about Business Continuity Manager, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. In this document, Business Continuity Manager is also called BC Z Manager.
license key for the basic function is installed, you can define and manage the following copy groups: • BC Z - HP Business Copy for Mainframe • Cnt Ac-S Z - HP Continuous Access for Mainframe • TCA - Hitachi TrueCopy™ Asynchronous for Mainframe • Cnt Ac-J Z - HP Continuous Access Journal for Mainframe After a license key is installed in the license information dataset, functions corresponding to that license key become available.
Table 2 License Types License type Effective period Purpose Permanent license Indefinite Used for normal operation. NOTE: When updating to Business Continuity Manager version 5.5 or later from a version earlier than 5.5, a new license key must be obtained and installed. Temporary license 120 days Used for a trial before purchase. NOTE: • When using a Temporary license whose version is earlier than 5.5, a new license key must be installed. • When using a Temporary license whose version is 5.
Program Prerequisites Table 3 (page 10) lists the programs required to use Business Continuity Manager.
Table 3 Prerequisite Programs (continued) Program Name Required / Optional Overview IBM HTTP Server for z/OS Optional An optional product bundled Use version 6.1. with WebSphere Application Server for z/OS. This is required to establish IPv6 connections or HTTPS communication with P9000 Replication Manager. In addition, z/OS Security Level3 is required when establishing HTTPS communication with Replication Manager.
Figure 1 Optional Device Configuration NOTE: The P9000 Command View Advanced Edition Management Server is not required for Business Continuity Manager. It is required if the Replication Monitor option of CVAE is used. Prerequisites for Using a z/Linux Volume Be sure you understand the information in this section before using Business Continuity Manager on a z/Linux volume. Note the following limitations: 12 • OS/390 is not supported.
To use a z/Linux volume, you must first specify the following: • Set the disk layout to CDL (System z compatible disk layout). • To run z/Linux on z/VM, set the DASD sharing type (Dasd Sharing) to Dedicated Disk. • Specify that time stamps be added to I/O operations to and from z/Linux. NOTE: If both z/OS and z/Linux volumes coexist inside a consistency group, synchronize the system clocks.
2 Installing Business Continuity Manager This chapter provides installation preparations and procedures, environment setup procedures, and version upgrade procedures. • “Preparing for Installation” (page 14) • “Installing Business Continuity Manager” (page 22) • “Upgrading Business Continuity Manager” (page 46) Overview of installation The following figure provides an overview of how to install Business Continuity Manager.
Table 5 Datasets Provided on Installation Tape No. Dataset Name Contents Label DSORG1 RECFM1 BLKSIZE1 Required/ (bytes) Optional 1 SMPMCS SMP/E for Business (1,SL) Continuity Manager or the REXX alternate library control statements used for packaging SYSMOD PS FB 3,120 Required 2 HP.CHYLnnn.F1 This sample library (2,SL) includes JCL samples used by SMP/E (for allocation, DDDEF, RECEIVE, APPLY, and ACCEPT), and other samples PO FB 3,120 Required 3 HP.CHYLnnn.
NOTE: In the preceding table, the nnn portion of CHYLnnn varies, depending on the version. Table 6 Files Provided on Installation CD-ROM No. File name Contents 1 HP.CHYLnnn.SMPMCS.XMIT SMP/E for Business Continuity Required Manager or the REXX alternate library control statements used for packaging SYSMOD 2 HP.CHYLnnn.F1.XMIT This sample library includes JCL samples used by SMP/E (for allocation, DDDEF, RECEIVE, APPLY, and ACCEPT), and other samples 3 HP.CHYLnnn.F2.
About Distribution Libraries (DLIB) Table 8 (page 17) shows the DASD storage attributes required for distribution libraries.
Table 9 DASD Storage Attributes for Target Libraries (continued) DD Name1 HPQYEXET DSORG RECFM LRECL BLKSIZE (bytes) (bytes) PO FB 80 6,160 PO VB 255 6,120 PO FB 80 6,160 PO FB 80 6,160 PO FB 80 6,160 (REXX Exec Library) HPQYEXVT (REXX Exec library, variable length format) HPQYPNLT (Panel Library) HPQYMSGT (Message Library) HPQYTABT (Table Library) 1 The DD name specified in the sample job HPQYK1AL (see “HPQYK1AL (Allocating Distribution and Target Libraries)” (page 96)).
Table 10 Amount of Business Continuity Manager Log Data when System Logger Service is Not Used Types of Business Continuity Manager Log Data Size1 Items Per Command Messages (excluding those output from the 100 + message-length2 ISPF panel, or scripts) number-of-messages-output Parameter information for the channel 100 + CCW-length3 command words of the I/O, only when an I/O error occurs number-of-times-an-I/O-error-occurred I/O return information, only when an I/O error occurs 256 number-of-times-
• For staging datasets: Estimate the disk capacity based on the amount of Business Continuity Manager log data. • For log stream datasets: Estimate the disk capacity based on the save period, and the amount of Business Continuity Manager log data after offload. • For external datasets (OUTLOG): Estimate the disk capacity based on the save period, and the amount of log data after offload.
job. A job name, a copy destination dataset name (%DSNAME), and a tape unit name (%TAPEU) should be modified with respect to the install environment. The sample JCL is included in the dataset indicated by the item 2 in “Datasets Provided on Installation Tape” (page 15). In the sample JCL, the nnn portion of CHYLnnn varies depending on the version.
4. Create space for the datasets to be transferred (execute the edited ALLOUPLD job). The ALLOUPLD job creates the sequential dataset space for transferring the Business Continuity Manager object archive and the REXX alternate library archive to the host machine. For examples of modifying sample JCL (ALLOUPLD), see “ALLOUPLD (Creating Transmission Datasets)” (page 88). 5.
1. SMPALLOC Allocate the SMP/E control dataset as necessary. If an existing SMP/E control dataset is to be used, skip this step. For examples of modifying sample JCL (SMPALLOC), see “SMPALLOC (Allocating SMP/E Datasets)” (page 94). 2. HPQYK1AL Allocate the distribution library (DLIB) and the target library. For examples of modifying sample JCL (HPQYK1AL), see “HPQYK1AL (Allocating Distribution and Target Libraries)” (page 96). 3.
The storage destinations for sample jobs are shown below: • When installed from installation tape The sample JCL is stored in a dataset at the destination for the copy operation described in section “Preparations for Installing Business Continuity Manager from a Tape” (page 20). • When installed from CD-ROM The sample JCL is stored in the HP.CHYLnnn.
Table 12 Items that must be performed for environment setup (continued) Item order Item Description See: 7 Setting Business Continuity Manager environment variables Setting the environment variables required for “Setting Business Continuity Manager Business Continuity Manager operation. Environment Variables” (page 35) 8 Registering a license Registering a license key to enable the corresponding functionality.
NOTE: In an environment in which the DBCS functionality is used, concatenate HPQYPNLT to the alternate panel library (DD name ISPPALT) as well. For details, see the ISPF User's Guide Volume I. 3. Concatenate the message library HPQYMSGT to the DD name ISPMLIB. NOTE: In an environment in which the DBCS functionality is used, concatenate HPQYMSGT to the alternate message library (DD name ISPMALT) as well. For details, see the ISPF User's Guide Volume I. 4.
NOTE: In an environment in which the DBCS functionality is used, concatenate HPQYPNLT to the alternate panel library (DD name ISPPALT) as well. Also, concatenate HPQYMSGT to the alternate message library (DD name ISPMALT). For details, see the ISPF User's Guide Volume I. Settings for using the YKWATCH command and the copy group definition generation function for PPRC copy pairs The YKWATCH command and the copy group definition generation function for PPRC copy pairs are executed as background jobs.
START YKALCSVC[,PARM='{SVC-number | DELETE}'] Function Registers or deletes a user SVC. Parameters SVC-number < numeric characters> ~ ((200 to 255)) Specifies an SVC number to assign to a user SVC. DELETE Specified to delete a user SVC. If you omit the optional PARM= part of the command, an unused SVC number between 200 and 255 is assigned. Return Codes Table 14 YKALCSVC Command Return Codes List Return Code Meaning 0 The command ended normally. 4 The SVC number is already registered.
YKLCNSE=[prefix] ~ <8 or fewer alphanumeric characters> Specify a prefix1 for the license information dataset so that the name of the dataset is unique. If the prefix1 is omitted, specify PARM='YKLCNSE='. For details about the prefix1 for the license information dataset, see “Naming Conventions for License Information Datasets” (page 44). YKLCNS2=[prefix2] ~ <8 or fewer alphanumeric characters> Specify a prefix2 for the license information dataset so that the name of the dataset is unique.
Table 15 YKSETENV Command Return Codes List (continued) Return Code Meaning 12 Processing was cancelled due to a system error (such as a GETMAIN error). 16 An internal error occurred. NOTE: For parameters, you can specify multiple items within the allowable length for PARM. If more than one of the same parameter is specified, the latter one will take effect.
YKT402I YKT402I YKT402I YKT402I YKT402I YKCMDIF YKLCNSE YKLCNS2 LOGPUT SYSLOG = = = = = 01 HP BCM SAM NO (&YKCMDIF (&YKLCNSE = (&YKLCNS2 (&YKLOGPT (&YKSYSLG = "00" N/A = N/A = "LOGR" = "YES" ) ) ) ) ) Setting the Security Setting Up the Resource Access Control Facility (RACF) Setting security for the environment configuration commands To use the YKALCSVC or YKSETENV command, you must restrict user access by using the RACF program control function.
Table 17 Correspondence between profiles defined in the FACILITY Class and available CLI commands (continued) Profile Defined for the FACILITY Class Available CLI Command YKWATCH STGADMIN.YKA.BCM.
NOTE: The following commands are available to use even if both of the access permissions are not assigned to a user: • YKCONMSG • YKDROP • YKENV • YKERCODE • YKEXPORT • YKIMPORT • YKINSCHK • YKLOAD • YKSLEEP • YKSTORE • YKWTOMSG NOTE: Use profiles to restrict access to the commands listed below. Unrestricted access to these commands could have an adverse effect on recovery operations at a remote site.
REDEFINE FACILITY STGADMIN.YKA.BCM.YKQUERY UACC(NONE) 3. Add access permissions for the defined profile to the user account. PERMIT STGADMIN.YKA.BCM.YKQUERY CLASS(FACILITY) ID(user-ID) ACCESS(READ) To improve the execution performance of BC Z Manager, HP recommends that you enable the RACLIST function (in-storage profiles) for the FACILITY class. Execute one of the following commands to enable the RACLIST function.
NOTE: For details about steps 2 and 4, see the MVS Initialization and Tuning Reference. Using the YKALCSVC Command to Register To register a user SVC, execute the YKALCSVC command when the system starts or before you use Business Continuity Manager. Before executing the following command, make sure that you perform the procedure described in “Settings for Using CLI Commands in TSO/E Environments” (page 25). For details about the format for the YKALCSVC command, see “YKALCSVC Command Syntax” (page 27).
For details about the YKDSPENV command format, see “YKDSPENV Command Syntax” (page 30). For details about the YKSETENV command format, see “YKSETENV Command Syntax” (page 28). Table 18 (page 36) describes the Business Continuity Manager environment variables that can be set, their meanings, their corresponding system symbol names, and their default values.
The examples below show how to specify a host ID. If neither (a) nor (b) is specified, 00 is assumed. Using the YKSETENV command The following example sets the host ID to 0F: START YKSETENV,PARM='YKCMDIF=0F' NOTE: If you register or change a host ID while BCM is running, the CLI commands will be executed using the previous set value. The registered or changed host ID will take effect the next time the YKLOAD command (with a route list specified) is executed.
The following shows an example of defining a symbol when you do want to output the CLI command-execution logs: START YKSETENV,PARM='SYSLOG=YES' NOTE: The setting made by executing the YKSETENV command (of Business Continuity Manager earlier than version 5.1) with SYSLOG=YES specified has the same effect as the setting made by executing the YKSETENV command (of Business Continuity Manager 5.1 or later) with no SYSLOG parameter specified.
YKLCNS2=[prefix2] ~ <8 or fewer Specify a prefix2 for the license alphanumeric characters> information dataset so that the name of the dataset is unique. If the prefix2 is omitted, specify PARM='YKLCNS2='. For details about the prefix2 for the license information dataset, see section “Naming Conventions for License Information Datasets” (page 44). LOGPUT=[LOGR | SAM] Specify whether or not the system logger service is to be used, when outputting BCM logs.
NOTE: The setting made by executing the YKSETENV command (of Business Continuity Manager earlier than version 5.1) with SYSLOG=YES specified has the same effect as the setting made by executing the YKSETENV command (of Business Continuity Manager 5.1 or later) with no SYSLOG parameter specified. Be careful when multiple versions are used in an environment, or when performing an upgrade.
In the following example, the YKDSPENV command is executed. The version portion in this example varies depending on the version.
Figure 3 Overview of License Registration Using the License Key File With this method, you transfer the obtained license key file to MVS and use the Manage Licenses panel to register the license. For details about the panel used for the following procedure, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide. To use the license key file: 1. Create a license information dataset.
5. In the Manage Licenses panel, enter the license key dataset name (BCM.LICENSE.KEYSFROM.HP) in the License Key Dataset Name field and press Enter. The license keys are read from the license key file and are installed in the license information dataset. The license key file also contains license keys for programs other than Business Continuity Manager and for multiple storage systems. However, this operation collectively installs only license keys for Business Continuity Manager.
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.
If YKLCNSE is omitted, the value of the &YKLCNSE system symbol is used. If YKLCNS2 is omitted, the value of the &YKLCNS2 system symbol is used. The YKLCNS2 value becomes valid when a value is specified in either YKLCNSE or &YKLCNSE. NOTE: The Business Continuity Manager environment variables registered with the YKSETENV command become invalid by Re-IPL, that is, they return to the default or the value of the system symbol &YKLCNSE and &YKLCNS2.
Y: Specified --: Not specified Verification Procedure Following Installation and Setup If some tasks are left unfinished during installation and setup of Business Continuity Manager, Business Continuity Manager cannot be used. You can use either of the following methods to check whether installation and setup have been completed properly: • Check the execution result of the YKINSCHK command. • Check the information displayed in the Installation Verification Summary panel.
Table 22 Business Continuity Manager Environment Variables to Be Checked Before Upgrading (continued) Parameter name Description LOGPUT BCM log output method SYSLOG Whether CLI command-execution logs are to be output to SYSLOG When the Business Continuity Manager version before upgrading is 5.1 or later, you can use the YKDSPENV command to check the values of the Business Continuity Manager environment variables. For details about the YKDSPENV command, see “YKDSPENV Command Syntax” (page 30).
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, DAD ID, route list ID, and path set ID. Therefore, if you change the dataset name, the consistency between the files is lost, and then Business Continuity Manager might become inoperable. For details about configuration files, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide.
DD Name Library Name ISPMLIB Message library HPQYMSGT ISPTLIB Table library HPQYTABT In an environment in which the DBCS functionality is used, remove dataset concatenation from the following libraries: DD Name Library Name ISPPALT Panel library HPQYPNLT ISPMALT Message library HPQYMSGT Removing the Concatenation of the Load Library Remove the load library for LINKLIB (HPQYLNKT) concatenated to LNKLST. Also, remove the load library for LPALIB (HPQYLPAT) concatenated to LPALST.
3 Setting Up the Environment When Linking with P9000 Replication Manager This chapter explains the environment setup when linking with P9000 Replication Manager. It also explains how to set up port numbers, security, and IBM HTTP Server, which are all required to link to Replication Manager. In addition, this chapter explains how to create initialization parameters and a cataloged procedure for startup.
NOTE: • If you use BCM to change a configuration file while storage information is being acquired by P9000 Replication Manager, a configuration file allocation error may occur. If this happens, use BCM to again change the configuration file. • If storage information is being acquired by P9000 Replication Manager while a configuration file is being updated by BCM, an error may occur.
To configure the environment settings without using the Remote DKC Control Function: 1. 2. Set up the storage system. For details, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. Create configuration file datasets. Create datasets for the following configuration files: • Disk configuration definition file • Copy group definition file For details, see “Creating Configuration File Datasets” (page 50). 3. 4. 5. 6. 7. Install BCM.
Figure 5 Configuring the Environment Settings Using the Remote DKC Control Function (New BCM Installation) To configure the environment settings using the Remote DKC Control Function: 1. Set up the storage system. For details, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. 2. Install Business Continuity Manager. For details, see “Installing Business Continuity Manager” (page 22). 3. Perform a local scan.
4. Configure the environment settings for the Remote DKC Control Function. Configure the following settings: • Route list definitions • Command device registrations For details, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. 5. Create configuration file datasets. Create datasets for the following configuration files: • Disk configuration definition file • Copy group definition file For more information, see “Creating Configuration File Datasets” (page 57). 6.
Figure 6 Configuring the Environment Settings in an Existing Environment (Upgrade BCM Installation) To configure the environment settings in an existing environment: 1. Upgrade Business Continuity Manager. For details, see “Upgrading Business Continuity Manager” (page 46). 2. Create configuration file datasets. These datasets are needed to perform a device scan and set copy group definitions in P9000 Replication Manager for the first time.
6. Configure the P9000 Replication Manager initialization settings. For details, see the HP StorageWorks P9000 Replication Manager Software Installation and Configuration Guide. Configuring the Environment Settings to Allow Only Monitoring of Copy Groups Figure 7 (page 56) shows the general procedure for configuring the environment settings in an existing environment to allow only monitoring of copy groups, without allowing copy groups to be defined or copy group operations to be performed.
details, see the description about generating PPRC copy pair copy group definitions in the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. Creating Configuration File Datasets Before doing anything else, you must first create datasets for the following configuration files, which are created in P9000 Replication Manager. You must then catalog the created datasets.
When a disk configuration definition file or a copy group definition file is updated from P9000 Replication Manager, a temporary file is created. After the file is successfully updated, the temporary file is deleted. Do not create a dataset with the same name as that of a temporary file. The following lists the file naming conventions for the temporary files: Name of the temporary file for the disk configuration definition file: prefix.TMP.SNnnnnn.
the Business Continuity Manager agent job. The names of the configuration files to which READ permission is to be granted are the following datasets that has the prefix specified in Business Continuity Manager's Set Defaults panel.
Setting Up IBM HTTP Server This section explains how to set up the IBM HTTP Server for establishing IPv6 connections or HTTPS communication, and how to collect logs. Settings for Connecting via IPv6 When P9000 Replication Manager connects to the Business Continuity Manager agent via IPv6, the reverse proxy function of IBM HTTP Server is required. Figure 8 (page 60) shows a configuration example when P9000 Replication Manager connects to the Business Continuity Manager agent via IPv6.
Table 25 Settings to Be Specified in the httpd.conf File for IPv6 Connections Directive to Be Specified Description of Directive, and Values to Be Specified CacheDisable Specify this directive so that the cache function for requests directed to the Business Continuity Manager agent is disabled. KeepAlive Specify this directive to disable the KeepAlive function. Listen Specify a standby port in IPv6 as shown below.
Figure 9 Configuration Example for HTTPS Connections Between P9000 Replication Manager and IBM HTTP Server Use the IBM HTTP Server httpd.conf settings file to configure IBM HTTP Server. The following table describes authentication methods used between P9000 Replication Manager and IBM HTTP Server.
Figure 10 Overview of Setup Procedure for Establishing HTTPS Connections The procedure to establish HTTPS connections between P9000 Replication Manager and IBM HTTP Server follows. The number for each step in Figure 10 (page 63) corresponds to the number in the procedure directly below that. Step 5 must be performed on P9000 Replication Manager. For details, see the HP StorageWorks P9000 Replication Manager Software User Guide.
1. To run IBM HTTP Server as a reverse proxy server, specify the settings described in “Required Settings for the httpd.conf File to Set Up a Reverse Proxy Server” (page 64) in the httpd.conf file. Table 27 Required Settings for the httpd.conf File to Set Up a Reverse Proxy Server Directives Values CacheDisable Specify this directive to disable the cache function for requests directed to the Business Continuity Manager agent. KeepAlive Specify this directive to disable the KeepAlive function.
3. Enable basic access authentication. a. Execute the htpasswd command to set up a user ID and password for authenticating P9000 Replication Manager. After executing the htpasswd command, a file that manages the user ID and password for basic access authentication of the P9000 Replication Manager will be created. For details on valid user IDs and passwords, refer to the product information on the IBM WebSphere Application Server Information Center.
How to Use the SETINIT Command This subsection explains the format of the SETINIT command, which sets the initialization parameters. For details about the symbols and syntax elements used in command explanations, see “Command Format” (page 110). 0SETINIT[ 1parameter]... Specify a SETINIT command or parameters in columns 1- 71. Any information specified in columns beginning in 72 is ignored. You can specify more than one SETINIT command.
Table 29 Continuation Symbols Continuation Symbol Continuation Method Hyphen (-) The hyphen is removed, and the parameter is continued in the leftmost column of the next line, retaining any contiguous spaces. Plus sign (+) The plus sign is removed, and the parameter is continued on the next line, removing any contiguous spaces. • Coding example for continuing parameters that contain contiguous spaces: SETINITPREFIX('USER01.
[ [ 1MODE(startup-mode)] 1LOCK(lock-mode)] Parameters PORT(port-number) ~ > Specifies the Business Continuity Manager agent port number to be used for TCP/IP communication with P9000 Replication Manager. You cannot specify a port number that is being used by another job. Specify a port number that is not being used in the system.
Replication Manager can use the disk configuration definition file and the copy group definition file with the prefix specified here. local-site's-DAD-ID ~ Specifies the device address domain ID of the local site on which the Business Continuity Manager agent is operating. This is the value specified in Local Device Address Domain ID in Business Continuity Manager's Set Defaults panel.
NOTE: To acquire information about volumes at the remote site, you must specify the remote site's device address domain ID. • Do not specify the local site's device address domain ID or the local site's Non Gen'ed device address domain ID. • If a site is being used as a local site by another Business Continuity Manager agent, you cannot specify it for use as a remote site.
LOGLEVEL(output-level) ~ ((0-3)) <<2>> Specifies the log output level. 0 Logs are not output. If 0 is specified, it is difficult to determine the cause of a communication failure or an error that occurs during execution of a Business Continuity Manager agent command. 1 Communication-related messages (YKY300I, YKY301I, YKY304I, and YKY307I) are output. 2 In addition to the messages that are output when LOGLEVEL(1) is specified, both the YKY680I and YKY500I messages are output.
• CHECK – Does not lock configuration files when the Business Continuity Manager agent starts. When the Business Continuity Manager agent updates a definition, it verifies that no other user has updated the configuration file that it is about to update. • NONE – Does not lock the configuration files when the Business Continuity Manager agent starts.
Figure 11 Example Configuration When Business Continuity Manager Agent Is Only on the Local Site To connect the Business Continuity Manager agent on the local site to Replication Manager in the configuration shown in Figure 11 (page 73), specify the values shown in Table 32 (page 74).
Table 32 Settings to Connect Business Continuity Manager Agents Installed on the Local Site to P9000 Replication Manager Prefix ACCOUNT INFO Local Site Remote Site Port Number DADID Route List ID (Forward Direction) Non Gen'ed DADID DADID 24042 NY ROUTE1 No specification LA ROUTE2 NY2 The following shows an example of specifying the settings shown in Table 32 (page 74) for initialization parameters.
Figure 12 Example Configuration Business Continuity Manager Agent is on the Local Site and a Remote Site To connect the Business Continuity Manager agents on the local and remote sites to their respective sites in the configuration shown in Figure 12 (page 75), specify the values shown in Table 33 (page 76).
Table 33 Settings for Connecting Business Continuity Manager Agents Installed on the Local and Remote Sites to P9000 Replication Manager Prefix Local Site Port Number ACCOUNT 24042 Remote Site DADID Route List ID (Forward Direction) Non Gen'ed Port DADID Number DADID Route List Non Gen'ed ID (Reverse DADID Direction) NY ROUTE1 No 24055 specification LA ROUTE3 No specification ROUTE2 NY2 ROUTE4 LA2 INFO The following shows an example of specifying the settings shown in Table 33 (page 76) f
Creating a Cataloged Procedure for Startup for the Business Continuity Manager Agents This section describes how to create and change a cataloged procedure for starting Business Continuity Manager agent. Standard Startup Cataloged Procedure The standard cataloged procedure for startup is registered into the sample library during installation.
5. • RECFM: FBA • DSORG: Sequential dataset (and a member name for a partitioned dataset) 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 Business Continuity Manager agent terminates abnormally. SYSOUT=* is specified in the standard cataloged procedure for startup.
4 Setting Up an Environment for Business Continuity Manager Monitor This chapter explains how to set up the security for Business Continuity Monitor. It also explains how to create configuration files, Business Continuity Monitor parameter files, and a cataloged procedure for startup.
Setting Up the Security for Business Continuity Manager Monitor This section explains how to set up the security for Business Continuity Manager Monitor. Define the appropriate user ID and group ID in the RACF STARTED class of the cataloged procedure for startup for Business Continuity Manager Monitor. The following is an example of using the TSO/E command with the STARTED class: —>SETROPTS GENERIC (STARTED) ->RDEFINE STARTED YKBCMMON.
NOTE: If you have already created a configuration file with Business Continuity Manager, then there is no need to re-create the file. Creating Business Continuity Manager Monitor Parameter Files Before using Business Continuity Manager Monitor, create the following two parameter files: • YKMONOPT file A file used to specify options necessary for starting Business Continuity Manager Monitor. • YKMONCG file A file used to specify Business Continuity Manager Monitor operations.
To calculate this size, see “Determining Required Memory” (page 20). 2. YKMONOPT DD statement Specifies the name of the dataset that contains the YKMONOPT file. For details on the format of this dataset, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide. 3. YKMONCG DD statement Specifies the name of the dataset that contains the YKMONCG file.
5 Troubleshooting If you need to call HP Technical Support, be sure to provide as much information about the problem as possible. Include the circumstances surrounding the error or failure and the exact content of any error codes and/or messages displayed on the Remote Web Console. To contact HP Technical Support, see “Support and other resources” (page 84).
6 Support and other resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
• Hitachi ShadowImage™ for Mainframe User's Guide: HP XP24000 Disk Array, HP XP20000 Disk Array • HP StorageWorks XP24000/XP20000 External Storage Software User’s Guide Manuals related to OS/390: • MVS Programming: Assembler Services Guide, GC28-1762 • MVS Setting Up a Sysplex, GC28-1779 • MVS System Codes, GC28-1780 • MVS System Commands, GC28-1781 • MVS Programming: Assembler Services Reference, GC28-1910 • Communications Server: IP User's Guide and Commands, GC31-8514 • Program Directory
• Communications Server IP Configuration Reference, SC31-8776 • Communications Server IP User's Guide & Commands, SC31-8780 • Communications Server IP API Guide, SC31-8788 • ISPF User's Guide Volume I, SC34-4822 • DFSMS Advanced Copy Services, SC35-0428 You can find these documents on the HP Manuals website: http://www.hp.com/support/manuals In the Storage section, click Storage Software and then select a product.
Table 35 Logical storage capacity units (continued) Logical Capacity Unit Value 1 EB 1,024 PB or 1,0246 bytes 1 BLOCK 512 bytes Typographic conventions Table 36 Document conventions Convention Element Blue text: Table 36 (page 87) Cross-reference links and e-mail addresses Blue, underlined text: http://www.hp.
A Modifying Sample JCL Values used in the sample JCL modification examples This appendix provides examples of modifying the sample JCL. The table below lists the values used in the sample JCL modification examples. Prerequisites • TSO/E to perform installation TSO/E user ID: BCMUSER • Dataset and volume allocated to the dataset No. Job name Dataset use Prefix for dataset Volume allocated name to the dataset Remarks 1 ALLOUPLD Dataset for transmission BCMUSER.
// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3) //********************************************************************* //* //* All Rights Reserved. Copyright (C) 2003, 2011, Hitachi, Ltd. //* //********************************************************************* //* //* This JCL allocates data sets in preparation for storing //* the data files for installation of BC Z Manager from the //* distribution CD. //* //* Instructions: //* 1. Change 'HP' to the current USERID. //* 2.
// // // // //F3 // // // // //F4 // // // // //F5 // // // // //F6 // // // // //F7 // // // // //F8 // // // // //F9 // // // // //F1REXX // // // // //F2REXX // // // // //F3REXX // // // // //F4REXX // // // // DD DD DD DD DD DD DD DD DD DD DD UNIT=SYSDA,VOL=SER=&VSN, SPACE=(TRK,(60)), DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120), DISP=(,CATLG,DELETE) DSN=&PFX..&VRM..F3.
The following numbers correspond to the numbers appearing on the right side of the sample JCL. Modify the underlined portions in the sample JCL as follows: (1)-(3) Modify the JOB text to match the installation environment. (4)-(13), (18), (20), (22), (24), (26), (28), (30), (32), (34), (36) Change the prefix for the dataset name from HP. to BCMUSER.. (14)-(17), (38), (40), (42), (44) Change the prefix for the dataset name from IBM. to BCMUSER.IBM..
DELETE IBM.HWJ9143.F3 DELETE IBM.JWJ9144.F1 SET MAXCC = 0 -----(16) -----(17) /* //********************************************************************* //* TSO receive to restore portable PDS from BINARY FTP //********************************************************************* //S1 EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * RECEIVE INDSN(CHYLnnn.SMPMCS.XMIT) DSNAME('HP.CHYLnnn.SMPMCS') + -----(18) VOLUME(#tso01) -----(19) RECEIVE INDSN(CHYLnnn.F1.XMIT) DSNAME('HP.CHYLnnn.
(4) Change the prefix for the input dataset name from HP to BCMUSER. (5) Change the prefix for the target library name from HP to HPQ.BCM. (6) Change the volume allocated to the target library from #bcm01 to BCMT00. //HPQYKSIN JOB (ACCT#),'SAMPLE COPY', -----(1) // REGION=0M,CLASS=A, -----(2) // MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3) //********************************************************************* //* //* All Rights Reserved. Copyright (C) 2006, 2011, Hitachi, Ltd.
// SPACE=(TRK,(1,1,1)),DCB=*.INF3 //OUTF4 DD DSN=&TPFX..&TVRM..HPQYPRCT, // UNIT=3390,VOL=SER=&TVSN, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(5,1,10)),DCB=*.INF4 //OUTF5 DD DSN=&TPFX..&TVRM..HPQYEXET, // UNIT=3390,VOL=SER=&TVSN, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(45,1,10)),DCB=*.INF5 //OUTF6 DD DSN=&TPFX..&TVRM..HPQYEXVT, // UNIT=3390,VOL=SER=&TVSN, // DISP=(NEW,CATLG,DELETE), // SPACE=(TRK,(45,1,10)),DCB=*.INF6 //OUTF7 DD DSN=&TPFX..&TVRM..
//********************************************************************* //* //* 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=HPQYKPrefix of SMP files -----(4) SET TVRM=Vnnnnnn Version of target libraries// SET VSN=#smp01 DASD volume serial for SMP files -----(5) //* //* 3) Submit the JCL.
// //SMPMTS // // // // //SMPSTS // // // // //SMPLOG // // // // //SMPLOGA // // // // DD DD DD DD DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) DSN=&PFX..SMPMTS, DISP=(NEW,CATLG,DELETE), UNIT=SYSDA,VOL=SER=&VSN, SPACE=(CYL,(1,5,5)), DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) DSN=&PFX..SMPSTS, DISP=(NEW,CATLG,DELETE), UNIT=SYSDA,VOL=SER=&VSN, SPACE=(CYL,(1,5,5)), DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) DSN=&PFX..
// SET DVSN=#bcm02 Distribution library VOLSER-----(6) //* //* 3) Submit the JCL.
// // // //HPQYPRCD // // // // //HPQYEXED // // // // //HPQYEXVD // // // // //HPQYPNLD // // // // //HPQYMSGD // // // //HPQYTABD // // // // DD DD DD DD DD DD UNIT=3390,VOL=SER= SPACE=(TRK,(1,1,1)), DCB=(BLKSIZE=6144,RECFM=U) DSN=PROC LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER= SPACE=(TRK,(5,1,10)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) DSN=EXEC(F) LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER= SPACE=(TRK,(75,1,10)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) DSN=EXEC(V) LIBRARY DISP=(NEW,CA
// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=-----(3) //********************************************************************* //* //* All Rights Reserved. Copyright (C) 2003, 2011, 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.
ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL. SET UCLIN. ADD ADD ADD ADD ADD ADD (TGT1,HPQYK.SMPCSI.CSI,TARGET))-----(6) SREL(Z038). DDDEF(SMPPTS) DA(HPQYK.SMPPTS)-----(7) OLD. DDDEF(SMPLOG) DA(HPQYK.SMPLOG)-----(8) MOD. DDDEF(SMPLOGA) DA(HPQYK.SMPLOGA)-----(9) MOD. DDDEF(SMPTLIB) DSPREFIX(HPQYK.TM) -----(10) VOLUME(#smp01)-----(11) UNIT(3390) CYL SPACE(5,5) DIR(200) DSNTYPE(PDS). DDDEF(HPQYSAMT) DA(HPQYK.Vnnnnnn.HPQYSAMT) -----(12) OLD. DDDEF(HPQYLNKT) DA(HPQYK.Vnnnnnn.
ADD ADD ADD ADD ENDUCL. SET UCLIN. ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL. SET LIST DA(HPQYK.Vnnnnnn.HPQYEXET)-----(25) OLD. DDDEF(HPQYEXVT) DA(HPQYK.Vnnnnnn.HPQYEXVT) -----(26) OLD. DDDEF(HPQYPNLT) DA(HPQYK.Vnnnnnn.HPQYPNLT)-----(27) OLD. DDDEF(HPQYMSGT) DA(HPQYK.Vnnnnnn.HPQYMSGT-----(28) OLD. DDDEF(HPQYTABT) DA(HPQYK.Vnnnnnn.HPQYTABT)-----(29) OLD. BDY(DLIB1). DLIBZONE(DLIB1) RELATED(TGT1) SREL(Z038). DDDEF(HPQYSAMD) DA(HPQYK.Vnnnnnn.HPQYSAMD)-----(30) OLD. DDDEF(HPQYLNKD) DA(HPQYK.
Change the prefix for the dataset name from HPQYK to HPQ.BCM. (5) Change the volume allocated to the SMP/E dataset from #smp01 to SMP001. (6) Change RFPREFIX from HP to HPQ.BCM. //HPQYK3RC JOB (ACCT#),'RECEIVE BC Z MANAGER', -----(1) // REGION=0M,CLASS=A, -----(2) // MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY= -----(3) //********************************************************************* //* //* All Rights Reserved. Copyright (C) 2003, 2011, Hitachi, Ltd.
//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.
//* GIMSMP Installation SMP/E program // SET PFX=HPQYK 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.
Modify the JOB text to match the installation environment. (4) Change the prefix for the dataset name from HPQYK to HPQ.BCM. (5) Change the volume allocated to the SMP/E dataset from #smp01 to SMP001. (6) When SMP/E ACCEPT is completed successfully, the check is deleted (changed to a comment) and the job is performed again.
// 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= //SMPLOG DD DISP=MOD,DSN= //SMPLOGA DD DISP=MOD,DSN= //SMPCSI DD DISP=SHR,DSN= //GLOBAL DD DISP=SHR,DSN= //TGT1 DD DISP=SHR,DSN= //DLIB1 DD DISP=SHR,DSN= //SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER= //SMPHOLD DD DUMMY //SMPSCDS DD DISP=SHR,DSN= //SMPMTS DD DISP=SHR,DSN= //SMPSTS DD DISP=SHR,DSN= //SYSLIB DD DISP=SHR,DSN=SYS1.
B When Multiple Versions of Business Continuity Manager Exist This section gives notes on upgrade processing when multiple versions of Business Continuity Manager exist in a system. Configuration Files Configuration files created in an older version of Business Continuity Manager can be used in a newer version as they are.
Installing a License In Business Continuity Manager versions 5.0 to 5.3, a license obtained in Business Continuity Manager versions 4.0 to 4.2 is treated as follows: • A permanent license can be used without reinstallation. • A temporary license or emergency license cannot be used as they are. They need to be reinstalled. Specifying Business Continuity Manager Log Output Destination (LOGPUT) Business Continuity Manager before version 4.2 does not support the &YKLOGPT system symbol.
• If the settings are made with the YKSETENV command of a version of Business Continuity Manager 5.1 or later System with Business Continuity Manager 5.1 or later System with a version of Business Continuity Manager earlier than 5.
C Command Format This appendix describes the symbols used in command explanations and syntax elements for the commands. The symbols used in command explanations are shown in Table 37 (page 110). Symbols Used in Command Explanations Table 37 Symbols Used in Command Explanations Font example, or symbol Meaning | (stroke) Separator between multiple items, meaning "or". Example: "A|B|C" means "A, B, or C". [ ] The user can specify the items enclosed between these symbols (or the items may be omitted).
Table 38 Command Syntax Elements (continued) Syntax elements Text that can be specified A character string consists of a single part or multiple parts that are connected by a period (.). A character string for each part consists of alphabetic uppercase characters and numbers. Note that the first character for each part must be an uppercase character. Each part consists of 1 to 8 characters.
D Using BCM with z/OS Running as a Guest Under z/VM Introduction BCM can be used with z/OS running as a guest under z/VM. In such an environment, BCM operates the same as when used with z/OS running in an LPAR. When running on a z/VM guest z/OS, BCM operations must be used with full pack mini-disks and/or dedicated disks. In addition, a local modification to enable the use of CCWs 83 and 84 is required. One or mode APARs/PTFs may be required.
NAME CCW VALID STATMOD RONLY SPECIAL PREPROC LAST VALUE 84 YES NO NO NO NO NO Placing Modifications in the HCPDDPCD Macro The following explains the structure of the macro source code that will be modified later as part of using the LOCALMOD exec. It also explains how to find where to add the additional lines. References to the use of XEDIT are for reference at this point. XEDIT will run as part of the LOCALMOD exec. The use of LOCALMOD will be explained in the Using LOCALMOD section of this appendix.
First Line NAME CCW VALID STATMOD SEEKREQ RONLY SPECIAL SIMULAT MULTI LAST VALUE 83 YES NO NO NO NO NO NO NO Second Line NAME CCW VALID STATMOD SEEKREQ RONLY SECIAL SIMUKAT MULTI LAST VALUE 84 YES NO NO NO NO NO NO NO Placing Modifications in the HCPMDPCD Macro The following explains the structure of the macro source code that will be modified later as part of using the LOCALMOD exec. It also explains how to find where to add the additional lines.
12901 12902 12903 12904 12905 12906 12907 12908 STATMOD=NO, SEEKREQ=NO, RONLY=NO, SPECIAL=YES, SIMULAT=NO, MULTI=NO, LAST=NO C C C Requires special processing C C @VR4GHR3 C @V11VXPX SPACE 1 In the above example, XEDIT lines 12889 through 12897 are the first line of code. The C characters on the right side of some lines indicate the statement is continued. This provides formatting to make the entries easier to read.
LOCALMOD CP HCPTDD ASSEMBLE (ASM HL A typical LOCALMOD command for the full pack minidisk modification would be: LOCALMOD CP HCPTMD ASSEMBLE (ASM HL When the command has been entered, the minidisk/directory assignments will be displayed. If the environment setup is successful, a message indicating successful processing will be displayed and then a message similar to the following will be displayed: VMFLMD1301R Local modification L0005 is being created for update part HCPTDD ASSEMBLE.
Glossary A AP application program APID An ID for identifying the first DAD ID of a route. The same APID value is used for the primary DKC and secondary DKC on the same route.
configuration file A generic name that refers to copy group definition files, disk configuration definition files, command device definition files, route list definition files, and path set definition files. consistency group (C/T group) When updating volumes in the group, this preserves consistency in the update sequence. consistency time (C/T Time) The time indicated by the P-VOL I/O timestamp written to the S-VOL.
DISPLAY command An operator command used to display the status of BCM Monitor. You can specify this command in the MODIFY command to display the current valid value of the parameter in the YKMONOPT or YKMONCG file and the commands that are waiting to be executed.
HTTP HyperText Transfer Protocol HTTPS HyperText Transfrer Protocol Security HyperSwap Function for automatically switching, by using TPC-R, the I/O destination volume from the P-VOL to the S-VOL during a failure or maintenance. This requires that both the P-VOL and S-VOL disk controllers be connected to the same host. There are two types of HyperSwaps: Basic HyperSwaps and GDPS (Geographically Dispersed Parallel Sysplex) HyperSwaps.
logical DKC A collection of storage system volumes, each of which is assigned a CU number in the range from 00 to FE. In Business Continuity Manager, logical DKCs are distinguishable from ordinary DKCs, that is to say, the number assigned to each logical DKC (logical DKC serial number) is called a DKC serial number.
O Open/MF consistency group A consistency group that uses the Open/MF Consistency Preservation Function. This group consists of both open system copy groups and mainframe system copy groups, and can suspend them simultaneously. operational testing A test of the remote site when copy pairs spanning the primary site and one or more other sites are cut off, to check whether operations are being performed properly, such as during a failure.
Remote Web Console A browser-based program installed on the SVP that allows you to configure and manage the disk array. Replication Manager HP StorageWorks P9000 Replication Manager Software REPORT command An operator command used to display the information about copy groups monitored by BCM Monitor.
startup mode An execution permission mode that is specified in an initialization parameter of Business Continuity Manager agents. The startup mode consists of the monitor mode and the edit mode.
YKP2A A command (provided by Mainframe Agent) used to create a copy group definition file for a PPRC copy pair. Note that Business Continuity Manager cannot read the copy group definition files created by the YKP2A command. YKPRM00 A member to which an initialization parameter necessary to run the Business Continuity Manager agent is registered Z z/Linux volume A volume on the DKC that is used on z/Linux. z/Linux volume copy groups can be operated from Business Continuity Manager running on z/OS.
Index Business Continuity Manager for installation from tape, 20 installation from CD-ROM, 21 installing, 14 overview, 7 upgrading, 46 Business Continuity Manager environment variable setting, 35 Business Continuity Manager log data required disk space for, 18 format, 70 disk configuration definition file (temporary file), 58 disk space required by Business Continuity Manager log data, 18 disk space requirements, 18 distribution datasets, choosing, 14 distribution libraries, 17 distribution medium, choosi
specification examples, 72 installation with SMP/E, 22 installation without SMP/E, 23 installing Business Continuity Manager, 14 Business Continuity Manager from CD-ROM, 21 Business Continuity Manager from tape, 20 ISPF interface and YKSTART, 25 YKWPROC, 27 ISPF interface installing, 25 J JES startup procedure, 77 K key code, directly entering, 43 L license registering, 41 license information dataset naming, 44 license information datasets format, 44 license key dataset, 42 license key file, using, 42 li
standard startup cataloged procedure, 77 starting YKSTART dynamically, 26 startup cataloged procedure creating, 77 STEPLIB DD statement, 78 storage designing, 18 storage attributes planning DASD, 16 storage capacity values conventions, 86 storage systems supported models, 7 Subscriber's Choice, HP, 84 SUMMARY parameter YKDSPENV command, 30, 40 SVC-number parameter YKALCSVC command, 28 symbols in text, 87 symbols used in command explanations, 110 SYSABEND DD statement, 78 SYSEXEC DD statement, 78 SYSLOG para
