HP P9000 Software Installation Manual

Hp storageworks p9000 for business continuity manager software installation guide (t5253-96052, may 2011).
Hide thumbs
Also See for P9000
Reference manual - 399 pages
Manual - 333 pages
User manual - 322 pages
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.
HP Part Number: T5253-96052
Published: May 201 1
Edition: Tenth

Advertising

   Also See for HP P9000

HP P9000 Manual
HP P9000 Manual 333 pages

   Related Manuals for HP P9000

   Summary of Contents for HP P9000

  • Page 1

    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.

  • Page 2

    © Copyright 2007, 201 1 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.21 1 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.

  • Page 3: Table Of Contents

    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....................9 Program Prerequisites......................10 Supported Storage Systems....................11 Prerequisites for Using a z/Linux Volume................12 2 Installing Business Continuity Manager............14 Overview of installation......................14 Preparing for Installation......................14...

  • Page 4: Table Of Contents

    Setting the TCP/IP Port Number....................58 Setting Up the Security for Business Continuity Manager Agents...........58 Setting the Dataset Security....................58 Setting Up the Resource Access Control (RACF) Facility When Linking with P9000 Replication Manager..........................59 Setting Up IBM HTTP Server.....................60 Settings for Connecting via IPv6...................60 Setting Up HTTPS Connections.....................61...

  • Page 5: Table Of Contents

    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...........80 Creating Business Continuity Manager Monitor Parameter Files............81 Creating a Cataloged Procedure for Startup for Business Continuity Manager Monitor....81...

  • Page 6: Table Of Contents

    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....................112 Local Modification to Enable BCM Functions................112 HLASM...........................112 Modification for Dedicated Disks....................112 Placing Modifications in the HCPDDPCD Macro..............113 Modification for Full Pack Minidisks..................113 Placing Modifications in the HCPMDPCD Macro..............114 Overall Process for Implementing a Local Modification..............115 The LOCALMOD Step......................115...

  • Page 7: Software, Licenses Provided For Business Continuity Manager

    P9500 and XP disk arrays. The XP disk array copy products can be configured and controlled using the P9000 version of BCM. With the exception of TrueCopy Asynchronous, the HP product names are used in this manual. For compatibility with existing implementations on XP disk arrays, the Hitachi abbreviations shown in parenthesis are accepted by the user interface.

  • Page 8

    Cnt Ac-J Z in a 4x4 configuration The length of time you can use Business Continuity Manager depends on the type of installed license. Table 2 (page 9) lists the license types. Overview of HP StorageWorks P9000 for Business Continuity Manager Software...

  • Page 9: Prerequisite Conditions, Operating System Prerequisites

    Business Continuity Manager can be used on the following operating systems: OS/390 V2R10 z/OS V1R1 to V1R12 To establish IPv6 connections or HTTPS communication between P9000 Replication Manager and Business Continuity Manager agent, you must use z/OS V1R9 or later. NOTE: The above versions of z/OS are supported as guests in z/VM environments.

  • Page 10: Program Prerequisites

    Business Continuity Manager agent. IBM Communications Server Optional A communication program None (standard OS component) This program is required for linking with P9000 Replication Manager. Overview of HP StorageWorks P9000 for Business Continuity Manager Software...

  • Page 11: Supported Storage Systems

    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. IBM Tivoli Storage...

  • Page 12: Prerequisites For Using A Z/linux Volume

    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.

  • Page 13

    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.

  • Page 14: Installing Business Continuity Manager, Overview Of Installation, Preparing For Installation, Types Of Distribution Media

    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. Figure 2 Overview of the Business Continuity Manager installation procedure To upgrade Business Continuity Manager, see “Upgrading Business Continuity Manager”...

  • Page 15

    Table 5 Datasets Provided on Installation Tape Dataset Name Contents Label DSORG RECFM BLKSIZE Required/ Optional (bytes) SMPMCS SMP/E for Business (1,SL) 3,120 Required Continuity Manager or the REXX alternate library control statements used for packaging SYSMOD HP.CHYLnnn.F1 This sample library (2,SL) 3,120 Required...

  • Page 16: Planning Dasd Storage Attributes

    NOTE: In the preceding table, the nnn portion of CHYLnnn varies, depending on the version. Table 6 Files Provided on Installation CD-ROM File name Contents Required/Optional HP.CHYLnnn.SMPMCS.XMIT SMP/E for Business Continuity Required Manager or the REXX alternate library control statements used for packaging SYSMOD HP.CHYLnnn.F1.XMIT This sample library includes JCL...

  • Page 17: About Distribution Libraries (dlib), About Target Libraries

    About Distribution Libraries (DLIB) Table 8 (page 17) shows the DASD storage attributes required for distribution libraries. Table 8 DASD Storage Attributes for Distribution Libraries (DLIB) DD Name DSORG RECFM LRECL BLKSIZE (bytes) (bytes) HPQYSAMD 6,160 (Sample Library) HPQYLNKD 6,144 (Load Library for LINKLIB) HPQYLPAD 6,144...

  • Page 18: About Rexx Library, Designing Storage, Required Device Capacity For Business Continuity Manager Log Data

    Estimate the amount of Business Continuity Manager log data as follows, according to the log output destination. For details about the ISPF log, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. When System Logger Service is OFF...

  • Page 19

    Table 10 Amount of Business Continuity Manager Log Data when System Logger Service is Not Used Types of Business Continuity Manager Log Size Items Per Data Command Messages (excluding those output from the 100 + message-length number-of-messages-output ISPF panel, or scripts) Parameter information for the channel 100 + CCW-length number-of-times-an-I/O-error-occurred...

  • Page 20: Determining Required Memory, Preparations For Installing Business Continuity Manager From A Tape

    For external datasets (OUTLOG): Estimate the disk capacity based on the save period, and the amount of log data after offload. For details about the format for external datasets (OUTLOG), see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide.

  • Page 21: Preparations For Installing Business Continuity Manager From A Cd-rom

    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 22: Installing Business Continuity Manager With Smp/e, Installing Business Continuity Manager

    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 23: Simple Installation (without Smp/e) Installation

    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). 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 24: Setting Up The Environment

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

  • Page 25: Settings For Using Cli Commands In Tso/e Environments

    Table 12 Items that must be performed for environment setup (continued) Item Item Description See: order Setting Business Setting the environment variables required for “Setting Business Continuity Manager Continuity Manager Business Continuity Manager operation. Environment Variables” (page 35) environment variables Registering a license Registering a license key to enable the “Registering a License”...

  • Page 26: Starting Ykstart Dynamically

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

  • Page 27: For Pprc Copy Pairs, Settings For Using Environment Configuration Commands, Ykalcsvc Command Syntax

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

  • Page 28: Yksetenv Command Syntax

    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.

  • Page 29

    NO: CLI command-execution logs are not output to SYSLOG. For details about commands that collect CLI command-execution logs, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. NOTE: The setting made by executing the YKSETENV command (of Business Continuity Manager earlier than version 5.1) with SYSLOG=YES specified has the...

  • Page 30: Ykdspenv Command Syntax

    In the following example, the YKDSPENV command is executed. The version portion in this example varies depending on the version. Execution Example 1 START YKDSPENV YKT403I HP StorageWorks P9000 for Business Continuity Manager Software YKT400I BC Z Manager environment variables version YKT401I Host ID: 00 YKT401I License info DSN prefix: HP...

  • Page 31: Setting The Security, Setting Up The Resource Access Control Facility (racf)

    YKT402I YKCMDIF = 01 (&YKCMDIF = "00" YKT402I YKLCNSE = HP (&YKLCNSE = N/A YKT402I YKLCNS2 = BCM (&YKLCNS2 = N/A YKT402I LOGPUT = SAM (&YKLOGPT = "LOGR" YKT402I SYSLOG = NO (&YKSYSLG = "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.

  • Page 32

    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.YKQUERY YKEWAIT (Reference profiles) YKFCSTAT YKH2B YKQHPATH YKQRYDEV YKQRYPTH YKQUERY YKSCAN YKSTATS YKWATCH Installing Business Continuity Manager...

  • Page 33

    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.

  • Page 34: Configuring Dataset Security, Registering A User Supervisor Call Interruption (svc)

    REDEFINE FACILITY STGADMIN.YKA.BCM.YKQUERY UACC(NONE) 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.

  • Page 35: Using The Ykalcsvc Command To Register, Example Of Specifying The Svc Number

    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 36: Specifying The Host Id

    “Naming Conventions for License Information Datasets” (page 44). For details about the system logger service, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. Alternatively, you can define the corresponding system symbols in the IEASYMxx parmlib member and then perform a re-IPL of the system to set values for the Business Continuity Manager environment variables.

  • Page 37: Enabling And Disabling The System Logger Service, Specifying Whether To Output Cli Command-execution Logs

    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.

  • Page 38: Yksetenv Command Format

    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.

  • Page 39

    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 40: Ykdspenv Command Format

    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.

  • Page 41: Registering A License

    In the following example, the YKDSPENV command is executed. The version portion in this example varies depending on the version. Execution example 1 START YKDSPENV YKT403I Hitachi Business Continuity Manager YKT400I BC Manager environment variables (version) YKT401I Host ID: 00 YKT401I License info DSN prefix: HITACHI YKT401I BCM log output method: LOGR YKT401I CLI log output settings: YES...

  • Page 42: 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: Create a license information dataset.

  • Page 43: Directly Entering A Key Code, Notes When Operating License Keys

    With this method, you directly enter a key code in the Manage Licenses panel to install the license. For details about the panel used in the following procedure, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide.

  • Page 44: Format For License Information Datasets, Naming Conventions For License Information Datasets

    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.

  • Page 45

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

  • Page 46: Verification Procedure Following Installation And Setup, What To Check Before Upgrading, Checking Licenses

    For details on the YKINSCHK command and the items output to the Installation Verification Summary panel, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide. In the JCL execution example that follows, the execution result of the YKINSCHK command is output to dd-name SYSTSPRT.

  • Page 47: Checking The User Svc Number, Backing Up Datasets, Backing Up Configuration Files

    Table 22 Business Continuity Manager Environment Variables to Be Checked Before Upgrading (continued) Parameter name Description BCM log output method LOGPUT Whether CLI command-execution logs are to be output to SYSLOG 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.

  • Page 48: Backing Up The Program Before Migration, Pre-upgrade Procedure, Deleting The User Svc

    Business Continuity Manager might become inoperable. For details about configuration files, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide. Backing Up the Program Before Migration Before migration, acquire a backup of the dataset where Business Continuity Manager will be installed.

  • Page 49: Removing The Concatenation Of The Load Library, Upgrading Business Continuity Manager

    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.

  • Page 50: Setting Up The Environment When Linking With P9000 Replication Manager, Overview Of Environment Settings

    Notes on Changing Configuration Files with BCM Perform the following operations as necessary if you use BCM to change the disk configuration definition file, route list definition file, or copy group definition file while it is linked with P9000 Replication Manager: If you use BCM to change a configuration file, the P9000 Replication Manager information is not automatically updated.

  • Page 51: General Procedure For Setting Up An Environment For Business Continuity Manager Agents

    BCM, an error may occur. If this happens, the information is acquired when it is next requested (at the fixed interval set in P9000 Replication Manager). General Procedure for Setting Up an Environment for Business Continuity Manager...

  • Page 52

    “Creating a Cataloged Procedure for Startup for the Business Continuity Manager Agents” (page 77) Start IBM HTTP Server. Start the BCM agent. For details, see the chapter about linking the BCM agent to P9000 Replication Manager in the HP StorageWorks P9000 for Business Continuity Manager Software User Guide.

  • Page 53

    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: Set up the storage system. For details, see the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. Install Business Continuity Manager. For details, see “Installing Business Continuity Manager”...

  • Page 54

    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. Create configuration file datasets. Create datasets for the following configuration files:...

  • Page 55

    Manager” (page 46). 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. Create datasets for the following configuration files: Disk configuration definition file...

  • Page 56

    Configuring the Environment Settings for Monitoring PPRC Copy Pairs To monitor PPRC copy pairs from P9000 Replication Manager, you must create a PPRC copy group definition file with BCM before you configure the environment settings for the BCM agent. For...

  • Page 57: Creating Configuration File Datasets

    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. Disk configuration definition file Copy group definition file The following indicates the time at which each configuration file is created.

  • Page 58: Setting The Dataset Security, Setting The Tcp/ip Port Number

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

  • Page 59: Manager

    Route list definition file Command device definition file To create or update the copy group definition from P9000 Replication Manager, grant WRITE permission for the datasets listed below to the Business Continuity Manager agent job. For details on dataset names, see “Creating Configuration File Datasets”...

  • Page 60: Settings For Connecting Via Ipv6, Setting Up Ibm Http Server

    P9000 Replication Manager connects to the Business Continuity Manager agent via IPv6. Figure 8 Example Configuration When Using IPv6 to Connect P9000 Replication Manager to the Business Continuity Manager Agent To set up IBM HTTP Server to run as a reverse proxy server, specify the settings described in Table 25 (page 61) for the httpd.conf file.

  • Page 61: Setting Up Https Connections

    A reverse proxy server uses HTTPS to receive requests from P9000 Replication Manager, and then uses HTTP to send those requests to the Business Continuity Manager agent, which is the origin server. In addition, basic access authentication can be used to authorize P9000 Replication Manager.

  • Page 62

    P9000 Replication Manager Basic access authentication (HTTP) When HTTP is used to connect P9000 Replication Manager and IBM HTTP Server, P9000 Replication Manager cannot send the information necessary for performing basic access authentication. An overview of the setup procedure for establishing HTTPS connections is shown in . All of the...

  • Page 63

    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. In addition, for details on how to set up IBM HTTP Server for establishing HTTPS connections, refer to the product information on the IBM WebSphere Application Server Information Center.

  • Page 64

    ProxyPass / http://0.0.0.0:port-number/ ProxyPassReverse / http://0.0.0.0:port-number/ Specify how long to wait before issuing a timeout. Timeout Specify a value greater than P9000 Replication Manager's timeout value (bcmif.socketTimeout). Enable SSL. Setting Up the Environment When Linking with P9000 Replication Manager...

  • Page 65: Collecting The Trace Log, Creating Initialization Parameters

    Communications Server IP Configuration Reference. Collecting the Trace Log To collect error logs and access logs between P9000 Replication Manager and IBM HTTP Server, use the log function of the latter. To determine whether to collect logs of IBM HTTP Server, follow the instructions from the web administrator.

  • Page 66: How To Use The Setinit Command, Continuing To The Next Line

    Continuing to the Next Line To continue a parameter onto the next line, enter a continuation symbol at the end of the line. The following table shows the continuation symbols. Setting Up the Environment When Linking with P9000 Replication Manager...

  • Page 67: Entering Comments, Notes During Creation Of Initialization Parameters, Details On Initialization Parameters, Format

    Do not specify an empty member as an initialization parameter when you start Business Continuity Manager agent. Although empty members do not result in an error, information cannot be returned to P9000 Replication Manager. Details on Initialization Parameters This subsection explains details on initialization parameters.

  • Page 68: Parameters

    ~ <PREFIX string consisting of 1 to 16 characters> Specifies the file name prefix of the Business Continuity Manager configuration files that are used by P9000 Replication Manager. This must be the value specified in Configuration File Prefix in Business Continuity Manager's Set Defaults panel. P9000...

  • Page 69

    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 ~ <DAD string consisting of 1 to 28 characters> Specifies the device address domain ID of the local site on which the Business Continuity Manager agent is operating.

  • Page 70

    To modify a configuration file that has a prefix specified in the PREFIX parameter, make sure you use the ISPF panel or P9000 Replication Manager. If you use another method, information might not be displayed on P9000 Replication Manager, or an error might occur.

  • Page 71

    LOGLEVEL(output-level) ~ <numeric character> ((0-3)) <<2>> Specifies the log output level. Logs are not output. If 0 is specified, it is difficult to determine the cause of a communication failure or an error that occurs during execution of a Business Continuity Manager agent command.

  • Page 72: Multiple Specifications Of Initialization Parameters, Examples Of Specifying Initialization Parameters

    MODE LOCK Examples of Specifying Initialization Parameters This subsection provides examples of initialization parameters for linking to P9000 Replication Manager. When Business Continuity Manager Agent Is Only on the Local Site This subsection explains how to specify initialization parameters when Business Continuity Manager agent is only on the local site and not on a remote site.

  • Page 73

    Figure 1 1 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 1 1 (page 73), specify the values shown in Table 32 (page 74).

  • Page 74: When Business Continuity Manager Agent Is On The Local Site And A Remote Site

    Manager agents on the local and remote sites so that they can perform local scans for their respective sites. The following example configuration is used to explain the specification method. Setting Up the Environment When Linking with P9000 Replication Manager...

  • Page 75

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

  • Page 76: Examples Of Initialization Parameter Analysis Results

    PREFIX parameter. The YKY002I message is displayed. *** AGENT nn-nn LISTING INFORMATION *** DATE=2009-10-15 TIME=13:34:35 PAGE=0001 SETINIT PORT(24042) 00010002 /* PREFIX */ 00020002 SETINIT PREFIX('ACCOUNT') 00030002 YKY002I INVALID INITIALIZATION PARAMETER: PREFIX SETINIT PREFIX('INFO','NY') 00040002 Setting Up the Environment When Linking with P9000 Replication Manager...

  • Page 77: Standard Startup Cataloged Procedure

    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. Copy the standard cataloged procedure for startup to the PROCLIB dataset of the JES (Job Entry Subsystem) startup procedure, and then modify the procedure to fit your environment.

  • Page 78

    For details on how to specify DD statements for BCM logs and output BCM log data, see the description about outputting the BCM log data in the HP StorageWorks P9000 for Business Continuity Manager Software User Guide.

  • Page 79: Setting Up An Environment For Business Continuity Manager Monitor

    “Creating Business Continuity Manager Monitor Parameter Files” (page 81). “ Creating a Cataloged Procedure for Startup for Business Continuity Manager Monitor” (page 81). See the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. General Procedure for Setting Up an Environment for Business Continuity Manager Monitor...

  • Page 80: Setting Up The Security For Business Continuity Manager Monitor

    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.

  • Page 81: Creating Business Continuity Manager Monitor Parameter Files

    What actions to take when copy groups are not in their specified startup statuses ◦ For details on the format of these files, see the HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide. Creating a Cataloged Procedure for Startup for Business Continuity...

  • Page 82

    For details on specifying DD statements for Business Continuity Manager logs and outputting Business Continuity Manager log data, see the description of the Business Continuity Manager log output method in the HP StorageWorks P9000 for Business Continuity Manager Software User Guide.

  • Page 83: Troubleshooting

    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: Support And Other Resources, Contacting Hp, Subscription Service, Documentation Feedback, Related Information

    HP StorageWorks P9000 for Business Continuity Manager Software Installation Guide HP StorageWorks P9000 for Business Continuity Manager Software Reference Guide A manual related to HP StorageWorks P9000 Command View Advanced Edition Software products: HP StorageWorks P9000 Replication Manager Software User Guide Manuals related to OS/390 and z/OS: Hitachi TrueCopy™...

  • Page 85

    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- 1 762 MVS Setting Up a Sysplex, GC28- 1 779 MVS System Codes, GC28- 1 780 MVS System Commands, GC28- 1 781 MVS Programming: Assembler Services Reference, GC28- 1 910...

  • Page 86: Hp Websites, Conventions For Storage Capacity Values

    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.

  • Page 87: Typographic Conventions

    Table 35 Logical storage capacity units (continued) Logical Capacity Unit Value 1 EB 1,024 PB or 1,024 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.com Website addresses...

  • Page 88: A Modifying Sample Jcl, Alloupld (creating Transmission Datasets)

    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 Job name Dataset use...

  • Page 89

    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.

  • Page 90: Recvupld (tso/e Receive Processing)

    UNIT=SYSDA,VOL=SER=&VSN, SPACE=(TRK,(60)), DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120), DISP=(,CATLG,DELETE) //F3 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 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 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 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 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 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 DSN=&PFX..&VRM..F9.XMIT, UNIT=SYSDA,VOL=SER=&VSN,...

  • Page 91

    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.

  • Page 92: Hpqyksin (simple Installation)

    DELETE IBM.HWJ9143.F3 -----(16) DELETE IBM.JWJ9144.F1 -----(17) SET MAXCC = 0 //********************************************************************* //* TSO receive to restore portable PDS from BINARY FTP //********************************************************************* //S1 EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=* //SYSTSIN RECEIVE INDSN(CHYLnnn.SMPMCS.XMIT) DSNAME('HP.CHYLnnn.SMPMCS') + -----(18) VOLUME(#tso01) -----(19) RECEIVE INDSN(CHYLnnn.F1.XMIT) DSNAME('HP.CHYLnnn.F1') + -----(20) VOLUME(#tso01) -----(21)

  • Page 93

    Change the prefix for the input dataset name from HP to BCMUSER. Change the prefix for the target library name from HP to HPQ.BCM. Change the volume allocated to the target library from #bcm01 to BCMT00. //HPQYKSIN JOB (ACCT#),'SAMPLE COPY', -----(1) REGION=0M,CLASS=A, -----(2)

  • Page 94: Smpalloc (allocating Smp/e Datasets)

    SPACE=(TRK,(1,1,1)),DCB=*.INF3 Target library //OUTF4 DSN=&TPFX..&TVRM..HPQYPRCT, UNIT=3390,VOL=SER=&TVSN, DISP=(NEW,CATLG,DELETE), PROCLIB SPACE=(TRK,(5,1,10)),DCB=*.INF4 Target library //OUTF5 DSN=&TPFX..&TVRM..HPQYEXET, UNIT=3390,VOL=SER=&TVSN, DISP=(NEW,CATLG,DELETE), EXECLIB(F) SPACE=(TRK,(45,1,10)),DCB=*.INF5 Target library //OUTF6 DSN=&TPFX..&TVRM..HPQYEXVT, UNIT=3390,VOL=SER=&TVSN, DISP=(NEW,CATLG,DELETE), EXECLIB(V) SPACE=(TRK,(45,1,10)),DCB=*.INF6 Target library //OUTF7 DSN=&TPFX..&TVRM..HPQYPNLT, UNIT=3390,VOL=SER=&TVSN, DISP=(NEW,CATLG,DELETE), PANEL SPACE=(TRK,(60,1,200)),DCB=*.INF7 Target library //OUTF8 DSN=&TPFX..&TVRM..HPQYMSGT, UNIT=3390,VOL=SER=&TVSN, DISP=(NEW,CATLG,DELETE), MESSAGE SPACE=(TRK,(5,1,5)),DCB=*.INF8 Target library //OUTF9...

  • Page 95

    //********************************************************************* //* 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 -------- -------------------------------- PFX=HPQYKPrefix of SMP files -----(4) SET TVRM=Vnnnnnn Version of target libraries// VSN=#smp01 DASD volume serial for SMP files -----(5) //* 3) Submit the JCL.

  • Page 96: Hpqyk1al (allocating Distribution And Target Libraries)

    DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) //SMPMTS DSN=&PFX..SMPMTS, DISP=(NEW,CATLG,DELETE), UNIT=SYSDA,VOL=SER=&VSN, SPACE=(CYL,(1,5,5)), DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) //SMPSTS DSN=&PFX..SMPSTS, DISP=(NEW,CATLG,DELETE), UNIT=SYSDA,VOL=SER=&VSN, SPACE=(CYL,(1,5,5)), DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB) //SMPLOG DSN=&PFX..SMPLOG, DISP=(NEW,CATLG,DELETE), UNIT=SYSDA,VOL=SER=&VSN, SPACE=(CYL,(1,5)), DCB=(BLKSIZE=32720,LRECL=80,RECFM=FB) //SMPLOGA DSN=&PFX..SMPLOGA, DISP=(NEW,CATLG,DELETE), UNIT=SYSDA,VOL=SER=&VSN, SPACE=(CYL,(1,5)), DCB=(BLKSIZE=32720,LRECL=80,RECFM=FB) HPQYK1AL (Allocating Distribution and Target Libraries) The method for modifying HPQYK1AL, which allocates the distribution library and the target library, is explained below.

  • Page 97

    SET DVSN=#bcm02 Distribution library VOLSER-----(6) //* 3) Submit the JCL. //********************************************************************* //ALLOCATE EXEC PGM=IEFBR14 Allocate target libraries //HPQYSAMT DD DSN=,SAMPLES LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER=, SPACE=(TRK,(15,1,5)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYLNKT DD DSN=,LOAD LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER=, SPACE=(TRK,(75,1,20)), DCB=(BLKSIZE=6144,RECFM=U) //HPQYLPAT DD DSN= LPA LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER=, SPACE=(TRK,(1,1,1)), DCB=(BLKSIZE=6144,RECFM=U) //HPQYPRCT DD...

  • Page 98: Hpqyk2df (defining Distribution And Target Libraries)

    UNIT=3390,VOL=SER= SPACE=(TRK,(1,1,1)), DCB=(BLKSIZE=6144,RECFM=U) //HPQYPRCD DD DSN=PROC LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER= SPACE=(TRK,(5,1,10)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYEXED DD DSN=EXEC(F) LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER= SPACE=(TRK,(75,1,10)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYEXVD DD DSN=EXEC(V) LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER= SPACE=(TRK,(45,1,10)), DCB=(BLKSIZE=6120,LRECL=255,RECFM=VB) //HPQYPNLD DD DSN=PANEL LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER= SPACE=(TRK,(60,1,200)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYMSGD DD DSN=MESSAGE LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER=//SPACE=(TRK,(5,1,5)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYTABD DD...

  • Page 99

    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. //* 2) Modify the following values to match your environment: Value Description...

  • Page 100

    (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) SPACE(5,5) DIR(200) DSNTYPE(PDS). DDDEF(HPQYSAMT) DA(HPQYK.Vnnnnnn.HPQYSAMT) -----(12) OLD. DDDEF(HPQYLNKT) DA(HPQYK.Vnnnnnn.HPQYLNKT)-----(13) OLD. DDDEF(HPQYLPAT) DA(HPQYK.Vnnnnnn.HPQYLPAT)-----(14) OLD. DDDEF(HPQYPRCT) DA(HPQYK.Vnnnnnn.HPQYPRCT)-----(15) OLD. DDDEF(HPQYEXET) DA(HPQYK.Vnnnnnn.HPQYEXET)-----(16) OLD. DDDEF(HPQYEXVT) DA(HPQYK.Vnnnnnn.HPQYEXVT) -----(17) OLD. DDDEF(HPQYPNLT) DA(HPQYK.Vnnnnnn.HPQYPNLT)-----(18) OLD.

  • Page 101: Hpqyk3rc (smp/e Receive Processing)

    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. ENDUCL. BDY(DLIB1). UCLIN. DLIBZONE(DLIB1) RELATED(TGT1) SREL(Z038). DDDEF(HPQYSAMD) DA(HPQYK.Vnnnnnn.HPQYSAMD)-----(30) OLD. DDDEF(HPQYLNKD) DA(HPQYK.Vnnnnnn.HPQYLNKD)-----(31) OLD. DDDEF(HPQYLPAD) DA(HPQYK.Vnnnnnn.HPQYLPAD)-----(32) OLD. DDDEF(HPQYPRCD) DA(HPQYK.Vnnnnnn.HPQYPRCD)-----(33) OLD. DDDEF(HPQYEXED) DA(HPQYK.Vnnnnnn.HPQYEXED)-----(34) OLD. DDDEF(HPQYEXVD) DA(HPQYK.Vnnnnnn.HPQYEXVD) -----(35) OLD. DDDEF(HPQYPNLD) DA(HPQYK.Vnnnnnn.HPQYPNLD)-----(36) OLD.

  • Page 102

    Change the prefix for the dataset name from HPQYK to HPQ.BCM. Change the volume allocated to the SMP/E dataset from #smp01 to SMP001. 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.

  • Page 103: Hpqyk4ap (creating Target Libraries)

    //SYSUT3 UNIT=SYSDA,SPACE=(3120,(0380,0760)) //SYSUT4 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 DISP=SHR,DSN= //SMPLOG DISP=MOD,DSN= //SMPLOGA DISP=MOD,DSN= //SMPCSI DISP=SHR,DSN= //GLOBAL DISP=SHR,DSN= //TGT1 DISP=SHR,DSN= //DLIB1 DISP=SHR,DSN= //SMPHOLD DUMMY //SMPTLIB DISP=SHR,UNIT=3390,VOL=SER= //* Use DASD files if installing from .XMIT distribution...

  • Page 104: Hpqyk5ac (creating Distribution Libraries)

    GIMSMP Installation SMP/E program PFX=HPQYK Prefix of SMP files -----(4) VRM=Vnnnnnn Second level name (VER REL MOD) 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.

  • Page 105

    Modify the JOB text to match the installation environment. Change the prefix for the dataset name from HPQYK to HPQ.BCM. Change the volume allocated to the SMP/E dataset from #smp01 to SMP001. When SMP/E ACCEPT is completed successfully, the check is deleted (changed to a comment) and the job is performed again.

  • Page 106

    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 DISP=SHR,DSN= //SMPLOG DISP=MOD,DSN= //SMPLOGA DISP=MOD,DSN= //SMPCSI DISP=SHR,DSN= //GLOBAL DISP=SHR,DSN= //TGT1 DISP=SHR,DSN= //DLIB1 DISP=SHR,DSN= //SMPTLIB DISP=SHR,UNIT=3390,VOL=SER= //SMPHOLD DUMMY //SMPSCDS DISP=SHR,DSN= //SMPMTS DISP=SHR,DSN= //SMPSTS...

  • Page 107: B When Multiple Versions Of Business Continuity Manager Exist, Configuration Files, License Information Dataset

    Business Continuity Manager. Changed Display for the License Name In Business Continuity Manager 5.0, display of the P9000 for Business Continuity Manager Extended CT Group Software license in the Manage Licenses panel was changed. If Basic is displayed, the Cnt Ac-S Z consistency preservation function has been installed. For the XP24000/XP20000, the Cnt Ac-S Z consistency function can be used as soon as Basic is installed.

  • Page 108: Installing A License, Specifying Business Continuity Manager Log Output Destination (logput)

    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.

  • Page 109: Exist, Registering A User Svc Dynamically, User Svc For Suppressing Ios002a Messages

    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.1 Setting in the YKSETENV Setting value of &YKSYSLG Whether to output the CLI Whether to output the CLI...

  • Page 110: C Command Format, Symbols Used In Command Explanations, Command Syntax Elements

    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)

  • Page 111

    Table 38 Command Syntax Elements (continued) Syntax elements Text that can be specified <PREFIX strings> 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.

  • Page 112: D Using Bcm With Z/os Running As A Guest Under Z/vm, Introduction, Apars/ptfs

    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.

  • Page 113: Placing Modifications In The Hcpddpcd Macro, Modification For Full Pack Minidisks

    NAME VALUE VALID STATMOD RONLY SPECIAL PREPROC LAST 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.

  • Page 114: Placing Modifications In The Hcpmdpcd Macro

    First Line NAME VALUE VALID STATMOD SEEKREQ RONLY SPECIAL SIMULAT MULTI LAST Second Line NAME VALUE VALID STATMOD SEEKREQ RONLY SECIAL SIMUKAT MULTI LAST 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.

  • Page 115: Overall Process For Implementing A Local Modification, The Localmod Step, Used Syntax Of Localmod, Examples

    12901 STATMOD=NO, 12902 SEEKREQ=NO, 12903 RONLY=NO, 12904 SPECIAL=YES, Requires special processing 12905 SIMULAT=NO, 12906 MULTI=NO, @VR4GHR3 C 12907 LAST=NO @V11VXPX 12908 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.

  • Page 116: The Service Step, The Put2prod Step, The Re-ipl Step, Install Bcm And Test

    , is setup, and runs; install the license keys and then perform the discover storage operation as described in the HP StorageWorks P9000 for Business Continuity Manager Software User Guide. When BCM discovers storage using the scan operation, the local modifications are installed and functioning correctly.

  • Page 117: Glossary

    A generic name for the following products: Manager HP StorageWorks P9000 for Business Continuity Manager Basic HP StorageWorks P9000 for Business Continuity Manager Universal Replicator 4x4 HP StorageWorks P9000 for Business Continuity Manager Universal Replicator Extended Business Continuity A program required to link with Replication Manager. Business Continuity Manager agent passes Manager agent requests between Replication Manager and Business Continuity Manager.

  • Page 118

    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.

  • Page 119

    DKC serial number In the HP StorageWorks XP1024/XP128 Disk Array and the HP StorageWorks XP12000/XP10000 Disk Array and the HP StorageWorks P9000 Disk Array, a number is assigned to each storage system (physical DKC serial number). In the HP StorageWorks XP24000/XP20000 Disk Array, a number is assigned to each logical DKC (logical DKC serial number).

  • Page 120

    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.

  • Page 121

    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.

  • Page 122

    Once the test is completed, the primary site and the remote site need to be synchronized again. operating system P-VOL Primary volume. P9000 Replication HP StorageWorks P9000 Replication Manager Software Manager pair information A CSV file in which copy information in a copy group container is described CSV file...

  • Page 123

    A browser-based program installed on the SVP that allows you to configure and manage the disk Console array. Replication HP StorageWorks P9000 Replication Manager Software Manager REPORT command An operator command used to display the information about copy groups monitored by BCM Monitor.

  • Page 124

    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. STOP command An operator command used to stop a Business Continuity Manager agent or BCM Monitor subordinate DKC A DKC that is a non-supervisor remote DKC subjected to arbitration processing in a 4x4 configuration...

  • Page 125

    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. For details about prerequisites for using z/Linux volumes, see the HP StorageWorks P9000 for Business Continuity Manager Software Installation Guide.

  • Page 126: Index

    YKALCSVC, YKDSPENV command, YKDSPENV, YKSETENV command, YKSETENV, configuration example when connecting P9000 Replication Manager and the help Business Continuity Manager agent via IPv6, obtaining, configuration example for connecting to P9000 Replication Host ID Manager, specifying,...

  • Page 127

    HPQYKSIN, installation from tape, memory space, required, SMPALLOC, modifying sample JCL UPLD, example, security setting the security when linking with P9000 Replication Manager, note security, setting specifying DEVN parameter, dataset security, specifying PREFIX parameter, Security: Setting the Security, notes when multiple versions of Business Continuity...

  • Page 128

    standard startup cataloged procedure, starting YKAGENT YKSTART dynamically, expanded format, startup cataloged procedure YKALCSVC command, creating, command syntax, STEPLIB DD statement, DELETE parameter, storage installing with, designing, return code, storage attributes SVC-number parameter, planning DASD, to register user SVC, storage capacity values YKCMDIF parameter conventions, YKSETENV command, 28,...

This manual also for:

Xp p9500

Comments to this Manuals

Symbols: 0
Latest comments: