HP XP7 for Business Continuity Manager Installation Guide Abstract This document describes how to install the following program products: HP XP7 Business Continuity Manager Software Basic, and HP XP7 Business Continuity Manager Continuous Access Journal 4x4 Extended CTG Software. In this manual, these products are collectively referred to as Business Continuity Manager.
© Copyright 2007, 2014 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 XP7 for Business Continuity Manager ....................................7 Licenses provided for Business Continuity Manager.......................................................................7 Prerequisite conditions...............................................................................................................8 Operating system prerequisites..............................................................................................8 Program prerequisites.......
Format for license information datasets.............................................................................40 Naming license information datasets...............................................................................40 Verification procedure following installation and setup............................................................42 Upgrading Business Continuity Manager...................................................................................42 What to check before upgrading.....
Parameters...................................................................................................................64 Multiple specifications of initialization parameters.............................................................68 Examples of specifying initialization parameters.....................................................................68 For Business Continuity Manager agent exclusively on the local site.....................................
Setting up the Resource Access Control Facility (RACF) when multiple versions of Business Continuity Manager exist......................................................................................................................107 Registering a user SVC dynamically........................................................................................107 User SVC for suppressing IOS002A messages..........................................................................
1 Overview of HP XP7 for Business Continuity Manager This chapter explains the provided licenses and prerequisites for using Business Continuity Manager. For more detailed information about Business Continuity Manager, see the HP XP7 for Business Continuity Manager User Guide. In this document, Business Continuity Manager is also called BC Manager.
When you migrate Business Continuity Manager from an older version to a newer version, depending on conditions, you might need to obtain the license keys again. Table 1 (page 8) lists the licenses provided by Business Continuity Manager and functions available for each license.
Program prerequisites Table 3 (page 9) lists the programs required to use Business Continuity Manager.
1 In the TSO/E terminal, lowercase letters might not be correctly displayed, depending on the usage environment.
Figure 1 Optional device configuration NOTE: The XP7 Command View Advanced Edition Management Server is not required for Business Continuity Manager. It is required if the Replication Monitor option for CVAE is used. Prerequisites for using a z/Linux volume on IBM system z Make sure that you are aware of the information in this section before using Business Continuity Manager on a z/Linux IBM system.
To use a z/Linux volume, first specify the following: • (When running z/Linux on z/VM) 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 for I/O operations to and from z/Linux. You cannot use the following functions on a z/Linux volume: 12 • The FlashCopy linkage function. • The Remote DKC Control function that uses a z/Linux volume as a command device.
2 Installing Business Continuity Manager This chapter provides installation preparations and procedures, environment setup procedures, and version upgrade procedures. Overview of installation Figure 2 (page 13) 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 42).
Table 5 Datasets provided on installation tape (continued) Dataset name Contents Label DSORG1 RECFM1 BLKSIZE1 Required/Optional (bytes) HP.CHYLnnn.F2 Business Continuity (3,SL) Manager load modules for LINKLIB PO U 6,144 Required HP.CHYLnnn.F3 Business Continuity Manager load modules for LPALIB (4,SL) PO U 6,144 Required HP.CHYLnnn.F4 Cataloged procedure (for PROCLIB) (5,SL) PO FB 3,120 Required HP.CHYLnnn.F5 REXX scripts (6,SL) PO FB 3,120 Required HP.CHYLnnn.
Table 7 FMID for Business Continuity Manager component FMID Function name CHYLnnn Business Continuity Manager NOTE: In Table 7 (page 15), the nnn portion of CHYLnnn varies depending on the version. Planning DASD storage attributes This section lists distribution libraries (DLIB) and target libraries, and explains the DASD storage attributes required for Business Continuity Manager installation.
Table 9 DASD storage attributes for target libraries (continued) dd name1 DSORG RECFM LRECL BLKSIZE (bytes) (bytes) (bytes) (bytes) HPQYSAMT (Sample Library) PO FB 80 6,160 HPQYLNKT PO U -- 6,144 PO U -- 6,144 PO FB 80 6,160 PO FB 80 6,160 PO VB 255 6,120 PO FB 80 6,160 PO FB 80 6,160 PO FB 80 6,160 (Load Library for LINKLIB) HPQYLPAT (Load Library for LPALIB) HPQYPRCT (Cataloged procedure library) HPQYEXET (REXX Exec Library) HPQYEXVT (REXX Exec library, varia
Table 10 Amount of Business Continuity Manager log data when the system logger service is not used Type of Business Continuity Manager log data Size1 Items per command Messages (excluding those output from the 100 + ISPF panel, or scripts) message-length2 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-anI/O-error-occurred I/O return information, only when an I/O error occurs 256 number-of-time
1 Business Continuity Manager logs are output with a specified value of this size, rounded up by a factor of 32. 2 The maximum message length is 256 bytes. 3 This is 2,051 bytes when the copy pair status is obtained, and 256 bytes or less otherwise. • For sequential datasets: Estimate the disk capacity based on the amount of Business Continuity Manager log data.
+ (C + S) x 1 KB ◦ + (C + S) x 1 KB: Number of copy group parameters specified in the YKMONCG file ◦ S: Number of action parameters specified in the YKMONCG file Preparations for installing Business Continuity Manager from a tape The sample library provides sample JCL that the user can use to install. To install from the Business Continuity Manager product install tape, first copy this sample JCL from the install tape. The sample JCL should be copied from the install tape by the following job.
2. 3. From the PC and using ASCII, transfer the following sample JCL to a host machine: • Dataset creating sample JCL (ALLOUPLD.JCL) • TSO/E RECEIVE processing sample JCL (RECVUPLD.JCL) Edit the JCL transferred in step 2 to match your installation environment. For details, see the header comments in the JCLs. For modification examples, see “Modifying sample JCL” (page 83). 4. Create space for the datasets to be transferred (execute the edited ALLOUPLD job).
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 89). 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 91). 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 19). • When installed from CD-ROM HP.CHYL The sample JCL is stored in the nnn.
Table 12 Items that must be performed for environment setup (continued) Item order Item Description 6 Setting security Security settings for environment configuration “Setting the security” (page 26) commands, CLI commands, and datasets 7 Registering a user SVC User SVC registration1 8 Setting Business Continuity Manager environment variables Setting the environment variables required for “Setting Business Continuity Manager Business Continuity Manager operation.
3. Register the CLI command name YKCONMSG to the AUTHCMD section of the IKJTSOxx parmlib member. Once this update is complete, TSO/E can be updated dynamically using the TSO/E PARMLIB CHECK(nn) and PARMLIB UPDATE(nn) commands. See the TSO/E System Programming Command Reference. Settings for using ISPF panels with Business Continuity Manager YKSTART is a REXX script that provides an ISPF panel interface. Executing the YKSTART command enables Business Continuity Manager for ISPF panels.
/* REXX */ ADDRESS TSO "ALTLIB ACTIVATE APPLICATION(EXEC)", "DATASET('HP.Vnnnnnn.HPQYEXET')"; ADDRESS ISPEXEC; "LIBDEF ISPMLIB DATASET ID('HP.Vnnnnnn.HPQYMSGT') STACK"; "LIBDEF ISPPLIB DATASET ID('HP.Vnnnnnn.HPQYPNLT') STACK"; "LIBDEF ISPTLIB DATASET ID('HP.Vnnnnnn.
command or the Copy Group Definition Generation function for PPRC copy pairs, specify the JCL of the background job for JCL JOB Statement in the Set Defaults panel. Perform either of the following operations to enable YKWPROC to be executed: • Concatenate the cataloged procedures library HPQYPRCT to the dd name IEFPDSI in the MSTJCLxx parmlib member. • Copy the YKWPROC member from the cataloged procedures library HPQYPRCT to a user PROCLIB.
for the RACF FACILITY class, and once view permissions for these profiles have been granted to the users' accounts. To use CLI commands, YKAGENTD (Business Continuity Manager agent), or YKBTSCAN (local batch scanning), you must set up the RACF. Users can use these functions once profiles have been defined for the RACF FACILITYclass, and once view permissions for these profiles have been granted to the users' accounts. There are two types of profiles: operation profiles and reference profiles.
Table 14 Correspondence between profiles defined in the FACILITY class and available CLI commands (continued) Profile defined for the FACILITY class Available functions YKQEXCTG command YKQHPATH command YKQRYDEV command YKQRYPTH command YKQUERY command YKSCAN command YKSTATS command YKWATCH command NOTE: The following commands are available for use even if both of the access permissions are not assigned to a user: • YKCONMSG • YKDROP • YKENV • YKERCODE • YKEXPORT • YKIMPORT • YKINSCHK • YKL
For details about how to activate the RACF FACILITY class, how to define a profile, and how to assign access permissions for profiles to user accounts, see the Security Server RACF Security Administrator's Guide. To assign access permissions for operation profiles to a user account: 1. Activate the RACF FACILITY class. SETROPTS CLASSACT(FACILITY) 2. Define the STGADMIN.YKA.BCM.COMMANDS profile for the FACILITY class. RDEFINE FACILITY STGADMIN.YKA.BCM.COMMANDS UACC(NONE) 3.
3. 4. Link the HPQYLPAT library to LPALST, using one of the following methods: • Define the HPQYLPAT library in the LPALSTxx parmlib member. For details, refer to the MVS Initialization and Tuning Reference. • Use the SETPROG LPA command to update dynamically. For details, refer to the MVS System Commands. Define the following SVCPARM statement in the IEASVCxx parmlib member. SVCPARM SVC-number,REPLACE,TYPE(3),EPNAME(JYUASVC),APF(NO),NPRMPT(NO),AR(NO) 5.
START YKALCSVC,PARM='DELETE' NOTE: • If you delete a user SVC using the YKALCSVC command while Business Continuity Manager is running, CLI commands that are being executed terminate abnormally. • If you use the YKALCSVC command to register a user SVC while Business Continuity Manager is running, CLI commands that are being executed will use the user SVC defined by the IEASVCxx parmlib member. The registered user SVC will take effect the next time a CLI command is executed.
Table 16 Business Continuity Manager environment variables that can be set (continued) Business Continuity Manager environment variable Meaning LOGPUT SYSLOG 1 Whether CLI command-execution logs are output to SYSLOG Corresponding system symbol names Default value &YKLOGPT LOGR: Uses the system logger service &YKSYSLG YES: Outputs CLI command-execution logs to SYSLOG For details about the relationship between the prefix of the license information dataset and the specification status for the YKSETE
Enabling and disabling the system logger service The following specification examples show how to set BCM logs to be output to an external dataset (using the system logger service), or to be output to a sequential dataset (without using the system logger service).
The following shows an example of defining a symbol when you do want to output the CLI command-execution logs to the console: START YKSETENV,PARM='SYSLOG=CONSOLE' 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.
YKSETENV command format The following shows the formats of the YKSETENV commands. For details about command formats, see “Command format” (page 109). START YKSETENV, Format PARM='{YKCMDIF=[host-id] | YKLCNSE=[prefix1]| YKLCNS2=[prefix2]| LOGPUT=[LOGR|SAM]| SYSLOG=[YES|NO]}[,...]' Function Parameters Sets the following Business Continuity Manager environment variables: • Host ID. • Prefix for the license information dataset. • BCM Log output method.
LOGR: BCM logs are output using the system logger service. SAM: BCM logs are output to sequential datasets. SYSLOG=[YES | CONSOLE | NO] Specify whether or not CLI command-execution logs are output to SYSLOG or the console. The value specified for the SYSLOG parameter is given priority over the &YKSYSLG system symbol in the IEASYMxx parmlib member. If this command is executed with the SYSLOG parameter omitted (PARM='SYSLOG=' is specified), the value of the &YKSYSLG system symbol will be used.
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. YKDSPENV command format The following shows the formats of the YKDSPENV commands. For details about command formats, see “Command format” (page 109). START YKDSPENV, Format [PARM='[SUMMARY|DETAIL]'] Function Displays the program product name and the Business Continuity Manager environment variables on the OS console.
Use either of the following methods to install a license key in the license information dataset: • Use a license key file.# • Directly enter a key code. #: The license key file is a text file provided by HP. Figure 3 (page 38) shows an overview of license registration. 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.
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 YK9001I message is output if the license key is installed correctly. 6. Use the Manage Licenses panel to confirm that the licenses have been installed correctly.
• Hyphens cannot be used in the license key dataset name. • Temporary license keys and emergency license keys with an expiration date after 17 September 2042 cannot be installed. Format for license information datasets License information datasets have the following format: • Dataset format: sequential datasets in the fixed-length record format. • Record size: 80 bytes. • Block size: multiple of 80 bytes. • Required access permissions: ◦ User installing the license key: write permission.
Using the YKSETENV command Execute the YKSETENV command to set the Business Continuity Manager environment variables (YKLCNSE and YKLCNS2). For details about the format for the YKSETENV command, see “YKSETENV command format” (page 35). The following example names the license information dataset HP.BCM.CCENTRAL.LICENSE: START YKSETENV,PARM='YKLCNSE=HP' START YKSETENV,PARM='YKLCNS2=BCM' If YKLCNSE is omitted, the value of the &YKLCNSE system symbol is used.
Table 19 License information prefix and YKSETENV/IEASYMxx status (continued) YKSETENV command IEASYMxx parmlib member YKLCNSE YKLCNS2 &YKLCNSE &YKLCNS2 Y -- Y -- YKLCNSE Y -- -- Y YKLCNSE -- Y Y -- &YKLCNSE.YKLCNS2 -- Y -- Y HP -- -- Y Y &YKLCNSE.
What to check before upgrading Checking licenses For Business Continuity Manager 5.5 or later, you cannot use license keys obtained for Business Continuity Manager 5.3 or earlier. You must obtain a license key for Business Continuity Manager version 5.5 or later. Checking environment variables Table 20 (page 43) lists the Business Continuity Manager environment variables that are used when you perform an upgrade installation. Check the settings for these environment variables before you upgrade.
Table 22 System symbol to be checked before upgrading (user SVC number) System symbol name Description &YKSVCNO SVC number to be assigned to the user SVC Backing up datasets Backing up configuration files Acquire backups of the configuration files below. • Copy group definition file (prefix.GRP.copy-group-ID) • Disk configuration definition file (prefix.DSK.SNnnnnn.DAD-ID) • Route list definition file (prefix.ROUTE.route-list-ID) • Command device definition file (prefix.CDEV.
NOTE: Business Continuity Manager and Tiered Storage Manager for Mainframe share a user SVC. Therefore, if Tiered Storage Manager for Mainframe is installed on the system, make sure that Tiered Storage Manager for Mainframe is not running before deleting the user SVC.
When Tiered Storage Manager for Mainframe is installed This section provides notes on registering a user SVC and setting environment variables and system symbols when installing Business Continuity Manager in an environment in which Tiered Storage Manager for Mainframe is installed. Registering a user SVC in an environment in which Tiered Storage Manager for Mainframe is installed Business Continuity Manager and Tiered Storage Manager for Mainframe share a user SVC.
TIP: The following describes how to check the environment setting values that are currently valid in the system. • If Business Continuity Manager has been installed (upgrade): Check the environment setting values you obtained during the check before upgrading. For details, see “Deleting the user SVC” (page 44) in “Pre-upgrade procedure” (page 44).
3 Setting up the environment when linking with XP7 Replication Manager This chapter explains the environment setup when linking with XP7 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.
1. 2. Set up the storage system. For details, see the HP XP7 for Business Continuity Manager 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 53). 3. 4. 5. 6. 7. Install BCM. For details, see “Installing Business Continuity Manager” (page 13). Configure the environment settings for the BCM agent.
Figure 5 Configuring the environment settings using the Remote DKC Control function (before Business Continuity Manager is installed) To configure the environment settings using the Remote DKC Control function: 1. Set up the storage system. For details, see the HP XP7 for Business Continuity Manager User Guide. 2. Install Business Continuity Manager. For details, see “Installing Business Continuity Manager” (page 20). 3. Perform a local scan.
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 53). 6. 7. 8. 9. Configure the environment settings for the Business Continuity Manager agent.
To configure the environment settings in an existing environment: 1. Upgrade Business Continuity Manager. For details, see “Upgrading Business Continuity Manager” (page 42). 2. Create configuration file datasets. These datasets are needed to perform a device scan and set copy group definitions in XP7 Replication Manager for the first time.
1. 2. 3. 4. Configure the environment settings for the Business Continuity Manager agent. For details, see the following sections: • “Setting the TCP/IP port number” (page 54) • “Setting up the security for Business Continuity Manager agents” (page 55) • “Setting up IBM HTTP Server” (page 56) • “Creating initialization parameters” (page 61) • “Creating a cataloged procedure for startup for the Business Continuity Manager agents” (page 72) Start IBM HTTP Server.
The values that can be specified for each variable are explained below. The values specified for prefix and DAD-ID must be the same as the value specified for the Business Continuity Manager agent initialization parameter PREFIX. • Prefix: Prefix of the configuration file Specify a string of 25 characters or fewer that consists of one string or multiple substrings joined together by periods. Only upper-case letters and numbers can be used.
For a job that starts Business Continuity Manager agent, set the UNIX service’s usage attributes (open a port for receiving). For details, refer to the Communications Server: IP Configuration Reference. Set the port number in the TCP/IP environment settings file (PROFILE.TCPIP profile, the definition file related to server functions in the TCP/IP address space). In the PORT definition of the PROFILE.
To enable use of UNIX services, use the RACF command from TSO/E to define the management user and management group IDs held by the OMVS segment in the RACF STARTED class of the Business Continuity Manager agent cataloged procedure for startup. The following is an example of using the TSO/E command with the STARTED class: ->SETROPTS GENERIC(STARTED) ->REDEFINE STARTED YKAGENT.
Figure 8 Example configuration using IPv6 to connect XP7 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 24 (page 57) for the httpd.conf file. Table 24 Settings in the httpd.
Table 24 Settings in the httpd.conf file for IPv6 connections (continued) Directive to be specified Description of directive, and values to be specified Specify a value greater than the timeout values for XP7 Replication Manager (bcmif.socketTimeout). Setting up HTTPS connections HTTPS (HTTP over SSL) connections can be established between XP7 Replication Manager and the Business Continuity Manager agent to improve security.
An overview of the setup procedure for establishing HTTPS connections is shown in Figure 10 (page 59). All of the steps indicated in Figure 10 (page 59) must be performed on all of the sites. Figure 10 Overview of the setup procedure for establishing HTTPS connections The procedure to establish HTTPS connections between XP7 Replication Manager and IBM HTTP Server is described below. The number for each step in Figure 10 (page 59) corresponds to the number in the procedure directly below that.
1. To run IBM HTTP Server as a reverse proxy server, specify the settings described in Table 26 (page 60) in the httpd.conf file. Table 26 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.
4. Enable basic access authentication. a. Execute the htpasswd to set up a user ID and password for authenticating Replication Manager. • After executing the htpasswd command, a file that manages the user ID and password for basic access authentication for the Replication Manager will be created. The following is an execution example of the htpasswd command: htpasswd /usr/local/apache/.htaccess user-name b. See Table 27 (page 61) to edit the httpd.conf file. Table 27 Required settings for the httpd.
Create a dataset to hold the initialization parameters by specifying the following attributes: • LRECL: 80 • BLKSIZE: Multiple of 80 • RECFM: Fixed-length or blocked fixed-length record • DSORG: Sequential or partitioned dataset How to use the SETINIT command This subsection explains the format of the SETINIT command, that sets the initialization parameters. For details about the symbols and syntax elements used in command explanations, see “Command format” (page 109). 0SETINIT[ 1parameter]...
Table 28 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)]PORT(port-number)] [RECVWAITTIME(reception-wait-time)] [HOSTNAME('host-identification-name')] [PREFIX('prefix','local-site's-DAD-ID'[,'route-list-ID[,{routelabel|*}]'[,['local-site's-Non-Gen'ed-DAD-ID'][,'remote-site's-DAD-ID']]])] [DEVN(start-device-number,end-device-number)] [LOGLEVEL(output-level)] [AUDITLOG(SYSMLOG)] [MODE(startup-mode)] [LOCK(lock-mode)] Parameters PORT(port-number) ~ ((1-65535)) <<24042>> Specifies the Business Contin
local-site's-DAD-ID ~ Specifies the device address domain ID of the local site on which the Business Continuity Manager agent is operating. When monitoring PPRC copy pairs, specify the value that was specified in Device Address Domain, Primary or Device Address Domain, Secondary in the Scan Copy Pair Inside Storage System panel when the copy group definition file for PPRC copy pairs was created.
NOTE: • Do not specify the local site's device address domain ID or the local site's Non Gen'ed device address domain ID. • If a site is being used as a local site by another Business Continuity Manager agent, you cannot specify it for use as a remote site. NOTE: Notes about specifying the PREFIX parameter • Do not specify a nonexistent prefix or device address domain ID in the PREFIX parameter.
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. The YKY680I message is output when an error occurs during an update request for a copy pair configuration or a copy pair status. The YKY500I message displays the results of updated configuration files. 3 In addition to the information output with LOGLEVEL(2), BCM logs are output.
Multiple specifications of initialization parameters Table 30 (page 68) explains the results when multiple SETINIT commands are used to specify each initialization parameter. Table 30 Results of multiple specifications of initialization parameters Parameter name Results of multiple specification PORT Last specified parameter is applied. RECVWAITTIME HOSTNAME PREFIX Permitted DEVN LOGLEVEL Last specified parameter is applied.
Figure 11 Example configuration when Business Continuity Manager agent is only on the local site For the configuration shown in Figure 11 (page 69) specify the settings provided in Table 31 (page 69) to connect the Business Continuity Manager agent installed on the local site to Replication Manager.
The following shows an example of specifying the settings shown in Table 31 (page 69) for initialization parameters.
Table 32 Settings for connecting Business Continuity Manager agents installed on the local and remote sites to XP7 Replication Manager Prefix Local site Port number ACCOUNT 24042 Remote site DADID Route list ID Non Gen'ed Port (forward DADID number direction) DADID Route list ID Non Gen'ed (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 32 (page 71) for
Creating a cataloged procedure for startup for the Business Continuity Manager agents This section explains how to create and change a cataloged procedure for starting Business Continuity Manager agent. Standard cataloged procedure for startup The standard cataloged procedure for startup is registered into the sample library during installation.
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 the 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 Manager Monitor. It also explains how to create configuration files, Business Continuity Manager Monitor parameter files, and a cataloged procedure for startup.
If you specified one of the following in the Business Continuity Manager Monitor YKMONCG file, you need to grant the view permission to the STGADMIN.YKA.BCM.COMMANDS profile: • DELETE, MAKE, RESYNC, or SUSPEND for the ACTION parameter • ADJUST as the startup action for the CGSTARTUPSTATUS parameter • DUPLEX as the startup status for the CGSTARTUPSTATUS parameter of Business Copy Z or TrueCopy Asynchronous when NOCANCEL is not specified In other cases, grant the view permission to the STGADMIN.YKA.BCM.
The standard cataloged procedure for startup is shown below. It is registered in the cataloged procedure during installation. Copy this procedure to the PROCLIB dataset of the JES (Job Entry Subsystem) startup procedure, and then modify the procedure as appropriate for your environment. //YKBCMMON PROC //********************************************************************* //* //* ALL RIGHTS RESERVED.
8. STEPLIB DD statement (optional) Specifies the dataset that contains Business Continuity Manager. If the LINKLIB dataset for Business Continuity Manager is linked to the system's LINKLIB, you do not need to specify the STEPLIB DD statement. 9. YKLOG01 DD statement and YKLOG02 DD statement (optional) Specifies the log dataset to which Business Continuity Manager log data will be output, without using the system logger service.
5 Support and other resources Contacting HP For worldwide technical support information, see the HP Support Center: http://www.hp.com/go/hpsc Before contacting HP, collect the following information: • Product model names and numbers • Technical support registration number (if applicable) • Product serial numbers • Error messages • Operating system type and revision level • Detailed questions Related information This manual is part of a related set of manuals.
• Communications Server: IP User's Guide and Commands, GC31-8514 • Program Directory for IBM Library for REXX on zSeries Alternate Library, GI10-3243 • DFSMSdfp Utilities, SC26-7343 • MVS Initialization and Tuning Reference, SC28-1752 • SecureWay Security Server RACF Security Administrator's Guide, SC28-1915 • TSO/E Customization, SC28-1965 • TSO/E Programming Services, SC28-1971 • TSO/E System Programming Command Reference, SC28-1972 • TSO/E REXX Reference, SC28-1975 • eNetwork Communica
HP websites For additional information, see the following HP websites: • http://www.hp.com • http://www.hp.com/go/storage • http://www.hp.com/service_locator • http://www.hp.com/support/manuals • http://www.hp.com/support/downloads • http://www.hp.com/storage/whitepapers Conventions for storage capacity values HP XP storage systems use the following physical storage capacity values (also called disk drive capacity) based on the following conventions.
Table 35 Document conventions (continued) Convention Element Blue, underlined text: http://www.hp.
6 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
A Modifying sample JCL This appendix provides examples of modifying the sample JCL. Values used in the sample JCL modification examples 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.
//********************************************************************* //* //* All Rights Reserved. Copyright (C) 2003, 2014, Hitachi, Ltd. //* //********************************************************************* //* //* This JCL allocates data sets in preparation for storing //* the data files for installation of BC Manager from the //* distribution CD. //* //* Instructions: //* 1. Change 'HP' to the current USERID. //* 2. Change '#tso01' to VOLSER of your device. //* 3.
// // // // //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.F2 DELETE IBM.HWJ9143.F3 DELETE IBM.JWJ9144.F1 SET MAXCC = 0 -----(15) -----(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.
(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.
// 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=HPQYK Prefix of SMP files -----(4) // SET VSN=#smp01 DASD volume serial for SMP files -----(5) //* //* 3) Submit the JCL.
// // //SMPMTS // // // // //SMPSTS // // // // //SMPLOG // // // // //SMPLOGA // // // // DD DD DD DD SPACE=(CYL,(1,5,15)), 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..
//********************************************************************* //ALLOCATE EXEC PGM=IEFBR14 //* Allocate target libraries //HPQYSAMT DD DSN=&PFX..&VRM..HPQYSAMT, SAMPLES LIBRARY // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=&TVSN, // SPACE=(TRK,(15,1,5)), // DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYLNKT DD DSN=&PFX..&VRM..HPQYLNKT, LOAD LIBRARY // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=&TVSN, // SPACE=(TRK,(90,1,20)), // DCB=(BLKSIZE=6144,RECFM=U) //HPQYLPAT DD DSN=&PFX..&VRM..
// UNIT=3390,VOL=SER=&DVSN, // SPACE=(TRK,(60,1,200)), // DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYMSGD DD DSN=&PFX..&VRM..HPQYMSGD, MESSAGE LIBRARY // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=&DVSN, // SPACE=(TRK,(5,1,5)), // DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQYTABD DD DSN=&PFX..&VRM..
//* 3) Submit the JCL to begin execution of SMP/E DDDEF. //* //******************************************************************** //S1 EXEC PGM=GIMSMP //SMPCSI DISP=SHR,DSN=&PFX..SMPCSI.
ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL. SET UCLIN. ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL. SET UCLIN. ADD ADD OLD. DDDEF(HPQYLNKT) DA(HPQYK.Vnnnnnn.HPQYLNKT) OLD. DDDEF(HPQYLPAT) DA(HPQYK.Vnnnnnn.HPQYLPAT) OLD. DDDEF(HPQYPRCT) DA(HPQYK.Vnnnnnn.HPQYPRCT) OLD. DDDEF(HPQYEXET) DA(HPQYK.Vnnnnnn.HPQYEXET) OLD. DDDEF(HPQYEXVT) DA(HPQYK.Vnnnnnn.HPQYEXVT) OLD. DDDEF(HPQYPNLT) DA(HPQYK.Vnnnnnn.HPQYPNLT) OLD. DDDEF(HPQYMSGT) DA(HPQYK.Vnnnnnn.HPQYMSGT) OLD. DDDEF(HPQYTABT) DA(HPQYK.Vnnnnnn.
DA(HPQYK.Vnnnnnn.HPQYSAMD) OLD. DDDEF(HPQYLNKD) DA(HPQYK.Vnnnnnn.HPQYLNKD) OLD. DDDEF(HPQYLPAD) DA(HPQYK.Vnnnnnn.HPQYLPAD) OLD. DDDEF(HPQYPRCD) DA(HPQYK.Vnnnnnn.HPQYPRCD) OLD. DDDEF(HPQYEXED) DA(HPQYK.Vnnnnnn.HPQYEXED) OLD. DDDEF(HPQYEXVD) DA(HPQYK.Vnnnnnn.HPQYEXVD) OLD. DDDEF(HPQYPNLD) DA(HPQYK.Vnnnnnn.HPQYPNLD) OLD. DDDEF(HPQYMSGD) DA(HPQYK.Vnnnnnn.HPQYMSGD) OLD. DDDEF(HPQYTABD) DA(HPQYK.Vnnnnnn.HPQYTABD) OLD. ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL.
//* //* Instructions: //* 1) Modify the JOB statement to match your environment. //* 2) Modify the following values to match your environment: //* //* Value Description //* --------------------------------------//* GIMSMP Installation SMP/E program // SET PFX=HPQYK Prefix of SMP files -----(4) // SET VRM=Vnnnnnn Second level name (VER REL MOD) // SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5) //* HP Refer to 4) for detail.
SET RECEIVE BDY(GLOBAL). SELECT(CHYKLnnn) RFPREFIX(HP) LIST. -----(6) /* HPQYK4AP (creating target libraries) The method for modifying HPQYK4AP, which creates the target library, is explained below. 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) Change the prefix for the dataset name from HPQYK to HPQ.BCM.
// SPACE=(3120,(0364,0380,500)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120) //SMPWRK3 DD UNIT=SYSDA, // SPACE=(3120,(0364,0380,500)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120) //SMPWRK4 DD UNIT=SYSDA, // SPACE=(3120,(0364,0380,500)), // DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120) //SMPWRK6 DD UNIT=SYSDA, // SPACE=(3120,(0364,0380,500)), // DCB=(RECFM=FB,BLKSIZE=3120) //SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760)) //SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760)) //SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760)) //SYSUT4 D
//********************************************************************* //* //* All Rights Reserved. Copyright (C) 2003, 2013, Hitachi, Ltd. //* //********************************************************************* //* //* This JCL executes SMP/E ACCEPT to create the distribution libraries. //* //* Instructions: //* 1) Modify the JOB statement to match your environment.
//SMPCNTL SET ACCEPT DD * BDY(DLIB1). SELECT(CHYLnn) CHECK .
B Notes on upgrading Business Continuity Manager This chapter provides notes on upgrading Business Continuity Manager. When upgrading Business Continuity Manager from a version earlier than 6.6.1 to 6.6.1 or later In Business Continuity Manager version 6.6.1 or later, when the YKIMPORT command is executed, the P-VOLs and S-VOLs of copy pairs to be defined are automatically checked to see whether their capacities are the same.
When upgrading Business Continuity Manager from a version earlier than 7.4 to 7.4 or later If you upgrade Business Continuity Manager to 7.4 or later, a CTG information CSV file is required to execute the YKIMPORT or YKEXPORT command for Continuous Access Journal Z copy groups. Before executing either command, assign and catalog the CSV file datasets, and then, for the YKIMPORT command, specify the CSV file with the DD name INCTG, and, for the YKEXPORT command, specify the CSV file with the DD name OUTCTG.
C Notes 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 earlier than version 4.2 does not support the &YKLOGPT system symbol.
Table 37 If the settings are made by using the YKSETENV command of a version of Business Continuity Manager 7.6 or later (continued) Value set by using the Value set by using YKSETENV command &YKSYSLG Version of Business Continuity Manager being run Earlier than 5.1 From 5.1 to 7.5 7.
Table 39 If the settings are made by using the YKSETENV command of a version of Business Continuity Manager earlier than 5.1 (continued) Value set by using the Value set by using YKSETENV command &YKSYSLG Version of Business Continuity Manager being run Earlier than 5.1 No specification or specification error SYSLOG=NO YES From 5.1 to 7.5 7.
Available versions of user SVCs If you want to install more than one version of Business Continuity Manager, note the minimum user SVC version required by each Business Continuity Manager instance, and then install a version of user SVC that is compatible with all the Business Continuity Manager versions to be installed. For details about the user SVC versions required by Business Continuity Manager, see (page 47).
D Command format This appendix describes the symbols used in command explanations and syntax elements for the commands. Symbols used in command explanations The symbols used in command explanations are shown in Table 40 (page 109). Table 40 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 41 Command syntax elements Syntax elements Text that can be specified Numeric characters 0|1|2|3|4|5|6|7|8|9 Alphabetic uppercase characters A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z Alphabetic characters A|B|C|D|E|F|G|H|I|J|K|L|M|N|O|P|Q|R|S|T|U|V|W|X|Y|Z a|b|c|d|e|f|g|h|i|j|k|l|m|n|o|p|q|r|s|t|u|v|w|x|y|z Alphanumeric characters Alphabetic and numeric characters Hexadecimal numbers 0|1|2|3|4|5|6|7|8|9|A|B|C|D|E|F PREFIX string A character string consists of a single part or mu
E Using Business Continuity Manager 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 more APARs/PTFs may be required.
Second line 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.
Modification for full pack minidisks To perform BCM operations on full pack minidisks, you must insert two macro lines in the HCPMDPCD macro in the HCPTMD z/VM module. Each macro line contains multiple operands.
12895 12896 12897 12898 12899 12900 12901 12902 12903 12904 12905 12906 12907 12908 SIMULAT=NO, MULTI=NO, LAST=NO C @VR4GHR3 C @V11VXPX SPACE 1 HCPMDPCD CCW=3, =======================> NO OPERATION C VALID=YES, C STATMOD=NO, C SEEKREQ=NO, C RONLY=NO, C SPECIAL=YES, Requires special processing C SIMULAT=NO, C MULTI=NO, @VR4GHR3 C LAST=NO @V11VXPX SPACE 1 In the above example, XEDIT lines 12889 through 12897 are the first line of code.
(ASM HL is an option to the LOCALMOD exec that specifies that the assembly operation is to be performed using the High Level Assembler (HLASM). Note that the macros will not assemble successfully using the default assembler provided with z/VM. HLASM must be used.
Install BCM and test Install BCM on the z/OS guest system following the instructions in this manual. After BCM is installed on the z/OS guest, is set up, and runs; install the license keys, and then perform the discover storage operation as described in the HP XP7 for Business Continuity Manager User Guide. When BCM discovers storage using the scan operation, the local modifications are installed and functioning correctly.
Glossary 0–9 (Numbers) 2DC configuration A configuration in which remote copying is performed from the primary site to the secondary site 2DC configuration with HyperSwap and UR A configuration that performs a delta resync between the primary site and a secondary site, after a HyperSwap on the primary site.
Business Continuity Manager agent A program required to link with Replication Manager. Business Continuity Manager agent passes requests between Replication Manager and Business Continuity Manager. Business Continuity Manager environment variable An environment variable used to run Business Continuity Manager, which is set by using the YKSETENV command.
DBCS double byte character set Delta Resync A method used in a 3DC Multi-Target configuration to synchronize a predefined delta resync pair (a UR pair consisting of a local site volume and a remote site volume) by copying only the differences between the volumes in the pair. Delta Resync pair A UR copy pair for performing Delta Resync. This copy pair is either in HOLD, HOLDTRNS, HOLDER, or NODELTA status. device address A unique number assigned to each device in the LCU.
failover The process that occurs when one device assumes the workload of a failed companion device. Failovers can be planned or unplanned. FlashCopy An IBM function that copies data quickly. For details, see DFSMS Advanced Copy Services. FTP file transfer protocol G Gen'ed volume A Gen'ed volume refers to a volume that the OS recognizes. In the case of z/OS, this would be a volume that is in the I/O gen for the LPAR.
journal cache A memory cache installed in the DKC used by UR. Update data to a data volume may be saved temporarily in memory as a journal cache during journal creation processing before it serves as a journal. journal group A group used for UR. A unit used to preserve consistency in the update sequence when updating volumes. L LDEV logical device local DKC One of the two disk controllers connected to the primary host in a 2DC configuration with HyperSwap and UR.
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.
Replication Manager HP XP7 Replication Manager software REPORT command An operator command used to display the information about copy groups monitored by BCM Monitor. You can specify this command in the MODIFY command to display the number of copy pairs in various copy pair statuses, the details for each copy pair, and the operational information and consistency information for copy groups. restore journal The copy destination journal for UR.
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.
XRC XP for Compatible Extended Remote Copy software Y YKAGENT An executable program of the Business Continuity Manager agent. This is also the name of the standard startup cataloged procedure of the Business Continuity Manager agent.
Index A D ALLOUPLD, 83 AUDITLOG, 67 dataset configuration file, creating (Replication Manager linkage), 53 datasets, backing up, 44 DELETE parameter YKALCSVC command, 30 designing storage, 16 DETAIL parameter YKDSPENV command, 37 determining required memory, 18 device capacity required by Business Continuity Manager log data, 16 DEVN format, 66 directive CacheDisable, 57 KeepAlive, 57 Listen, 57 LoadModule, 57 ProxyPassReverse, 57 Timeout, 57 directives (for HTTPS connection) AuthType, 61 AuthUserFile, 6
example of using ALTLIB command and LIBDEF service, 24 EXEC statement, 72, 76 F format license information datasets, 40 YKALCSVC command, 30 YKDSPENV command, 37 YKSETENV command, 35 H help obtaining, 78 Host ID specifying, 32 HOSTNAME parameter, 64 how to use SETINIT command, 62 HP technical support, 78 HPQYK1AL, 83, 91 HPQYK2DF, 83, 93 HPQYK3RC, 83, 96 HPQYK4AP, 83, 98 HPQYK5AC, 83, 99 HPQYKSIN, 83, 87 htpasswd command, 61 I IEASVCxx parmlib member, using to register user SVC, 29 initialization paramet
AuthName, 61 S sample JCL ALLOUPLD, 83 for creating license information datasets, 40 HPQYK1AL, 91 HPQYK2DF, 93 HPQYK3RC, 96 HPQYK4AP, 98 HPQYK5AC, 99 HPQYKSIN, 87 installation from tape, 19 SMPALLOC, 89 UPLD, 85 security, setting dataset security, 55 security: settings, 26 server certificate, 58 SETINIT command format, 62 how to use, 62 setting Business Continuity Manager environment variable, 31 setting the security when linking with XP7 Replication Manager, 55 setting the TCP/IP port number, 54 setting u
DETAIL parameter, 37 format, 37 SUMMARY parameter, 37 YKLCNSE parameter YKSETENV command, 35 YKLIST DD statement, 72 YKLOG01 DD statement, 73, 77 YKLOG02 DD statement, 73, 77 YKMONCG DD statement, 76 YKMONOPT DD statement, 76 YKPARM DD statement, 72 YKSETENV command format, 35 LOGPUT parameter, 35 SYSLOG parameter, 36 YKCMDIF parameter, 35 YKLCNS2 parameter, 35 YKLCNSE parameter, 35 YKSTART dynamically starting, 24 Z z/Linux volume, prerequisites for using, 11 129
