emc mainframe enablers · pdf file4 mainframe enablers version 7.6 installation and...

EMC® Mainframe EnablersVersion 7.6

Installation and Customization GuideREV 02

Mainframe Enablers Version 7.6 Installation and Customization Guide2

Copyright © 2015 EMC Corporation. All rights reserved. Published in the USA.

Published March, 2015

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.

CONTENTS
Preface
Chapter 1 Introduction

Product description..................................................................................... 14Mainframe Enablers components .......................................................... 14Additional features................................................................................ 15

Mainframe Enablers documentation............................................................ 15

Chapter 2 Installation

Preinstallation steps ................................................................................... 18Hardware and software requirements.................................................... 18Installation information......................................................................... 20

Installing the Mainframe Enablers suite....................................................... 21Loading PRODvrm.XMITFILE to disk........................................................ 21Running PRODvrm.XMITLIB(#EXTRACT) .................................................. 23Customizing the RIMLIB JCL ................................................................... 23Running the installation jobs................................................................. 27Applying maintenance .......................................................................... 28Licensing your software......................................................................... 29Shutting down and restarting ResourcePak Base................................... 44

Chapter 3 Customization

ResourcePak Base....................................................................................... 48Locating the ResourcePak Base SAMPLIB .............................................. 48Performing customization and integration ............................................. 48

SRDF Host Component ................................................................................ 48Locating the Host Component SAMPLIB................................................. 48Performing customization and integration ............................................. 48Implementing SRDF Auto Recovery ........................................................ 49Implementing command logging ........................................................... 49

ConGroup ................................................................................................... 51Locating the ConGroup SAMPLIB ........................................................... 51Performing customization and integration ............................................. 51Implementing ECGTRIP .......................................................................... 51

TimeFinder/Mirror ....................................................................................... 51Locating the TimeFinder/Mirror SAMPLIB............................................... 51Performing customization and integration ............................................. 51

TimeFinder/Clone Mainframe Snap Facility.................................................. 52Locating the TimeFinder/Clone Mainframe Snap Facility SAMPLIB ......... 52Performing customization and integration ............................................. 52

TimeFinder Utility ........................................................................................ 52 Customizing the REXX interface ................................................................... 52

SRDF Host Component .......................................................................... 53

Chapter 4 EMCSAFI Security Interface

Overview..................................................................................................... 56 Class names and resource names used ....................................................... 56

ResourcePak Base class and resource names........................................ 56SRDF Host Component class and resource names ................................. 60AutoSwap class and resource names .................................................... 61ConGroup class and resource names..................................................... 61

Mainframe Enablers Version 7.6 Installation and Customization Guide 3

Contents

TimeFinder/Clone Mainframe Snap Facility class and resource names... 62TimeFinder/Mirror class and resource names ........................................ 65TimeFinder Utility class and resource names ......................................... 67

Disabling the security interface ................................................................... 67Disabling the EMC SAF interface............................................................ 67

Customizing the security interface............................................................... 68Customizing EMCSAFI............................................................................ 68Customizing EMCSAFRB ........................................................................ 70XFACILIT class name.............................................................................. 70QS#BASE class name ............................................................................ 71DATASET class name (ConGroup) .......................................................... 71DATASET class name (SRDF Host Component) ....................................... 71TF#BASE class name ............................................................................. 71The EMCSAFRB macro ........................................................................... 72

Restoring the EMC-supplied SAF interface.................................................... 75

Appendix A Determining Current Maintenance Levels

AutoSwap ................................................................................................... 78 ConGroup ................................................................................................... 78 GNS ............................................................................................................ 79 MSC............................................................................................................ 79 ResourcePak Base....................................................................................... 79 SDV and DSE Monitors ................................................................................ 80 SRDF Host Component ................................................................................ 80 TimeFinder/Clone Mainframe Snap Facility.................................................. 81 TimeFinder/Mirror ....................................................................................... 81

4 Mainframe Enablers Version 7.6 Installation and Customization Guide

Title Page

FIGURES

1 EMC JCL customization utility panel............................................................................. 252 Completed customization utility panel ........................................................................ 263 Sample EMCSAFD........................................................................................................ 684 EMCSAFRB macro........................................................................................................ 72


Figures


Title Page

TABLES

1 Mainframe Enablers documentation............................................................................ 152 Symmetrix system requirements ................................................................................. 183 Symmetrix Hardware and software requirements......................................................... 194 RIMLIB contents .......................................................................................................... 235 Symmetrix-based licenses supported with Enginuity 5876 and Enginuity 5875 ........... 306 Host-based licenses required for Enginuity versions lower than 5875.......................... 327 Host-based licenses unchanged, regardless of Enginuity level .................................... 338 Product title capacity types ......................................................................................... 349 ResourcePak Base resource validation requests with XFACILIT..................................... 5710 EMCQOS resource validation requests with XFACILIT ................................................... 5911 EMCQOS resource validation requests with QS#BASE ................................................. 5912 AutoSwap resource validation requests....................................................................... 6113 ConGroup resource validation requests....................................................................... 6114 TimeFinder/Clone Snap Facility resource validation requests ...................................... 6215 Command resources with XFACILIT .............................................................................. 6416 TimeFinder/Mirror resource validation requests with XFACILIT ..................................... 6517 TimeFinder/Mirror resource validation requests with TF#BASE..................................... 6618 TimeFinder Utility resource validation requests ........................................................... 6719 EMCSAFI routine: Return code zero.............................................................................. 6920 EMCSAFI routine: Return code non-zero....................................................................... 7021 Authority level............................................................................................................. 7322 Requestor information................................................................................................. 7423 Resource information .................................................................................................. 7424 Return codes............................................................................................................... 74


Tableses


PREFACE

As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features.

Contact your EMC representative if a product does not function properly or does not function as described in this document.

Note: This document was accurate at publication time. New versions of this document might be released in EMC Online Support. Check EMC Online Support to ensure that you are using the latest version of this document.

AudienceThis document is intended for use by systems programmers who are responsible for installing and configuring the Mainframe Enablers software.

Related documentationTable 1 on page 15 provides a list of the related documentation.

Conventions used in this document EMC uses the following conventions for special notices:

Note: A note presents information that is important, but not hazard-related.

IMPORTANT

An important notice contains information essential to software or hardware operation.

Typographical conventions

EMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements, such as names of windows, dialog boxes,

buttons, fields, and menus• Names of resources, attributes, pools, Boolean expressions, buttons,

DQL statements, keywords, clauses, environment variables, functions, and utilities

• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, and notifications

Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages

Used in procedures for:• Names of interface elements, such as names of windows, dialog boxes,

buttons, fields, and menus• What the user specifically selects, clicks, presses, or types


Preface

Where to get helpEMC support, product, and licensing information can be obtained on EMC Online Support, as described next.

Note: To open a service request through EMC Online Support, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Product information

For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to EMC Online Support (registration required) at:

https://support.EMC.com

Technical support

EMC offers a variety of support options.

Support by Product — EMC offers consolidated, product-specific information on the Web at:

https://support.EMC.com/products

The Support by Product web pages offer quick links to Documentation, White Papers, Advisories (such as frequently used Knowledgebase articles), and Downloads, as well as more dynamic content, such as presentations, discussion, relevant Customer Support Forum entries, and a link to EMC Live Chat.

EMC Live Chat — Open a Chat or instant message session with an EMC Support Engineer.

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis, for example, a new term• Variables

Courier Used for:• System output, such as an error message or script• URLs, complete paths, filenames, prompts, and syntax when shown

outside of running text

Courier bold Used for specific user input, such as commands

Courier italic Used in procedures for:• Variables on the command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections — the bar means “or”

{ } Braces enclose content that the user must specify, such as x or y or z

... Ellipses indicate nonessential information omitted from the example


http://support.EMC.com

https://support.EMC.com/products

Preface

eLicensing support

To activate your entitlements and obtain your Symmetrix license files, visit the Service Center on https://support.EMC.com, as directed on your License Authorization Code (LAC) letter emailed to you.

For help with missing or incorrect entitlements after activation (that is, expected functionality remains unavailable because it is not licensed), contact your EMC Account Representative or Authorized Reseller.

For help with any errors applying license files through Solutions Enabler, contact the EMC Customer Support Center.

If you are missing a LAC letter, or require further instructions on activating your licenses through the Online Support site, contact EMC's worldwide Licensing team at [email protected] or call:

◆ North America, Latin America, APJK, Australia, New Zealand: SVC4EMC (800-782-4362) and follow the voice prompts.

◆ EMEA: +353 (0) 21 4879862 and follow the voice prompts.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]


http://support.EMC.com

Preface


Introduction

This chapter introduces the Mainframe Enablers components.

◆ Product description................................................................................................. 14◆ Mainframe Enablers documentation........................................................................ 15

Introduction 13

Introduction

Product descriptionThe EMC® Mainframe Enablers is a suite of components that you can use to monitor and manage your EMC Symmetrix® system. The components listed below are distributed and installed as a single package. This combined packaging simplifies installation and maintenance, and provides assurance of component compatibility.

Mainframe Enablers components

Mainframe Enablers includes:

ResourcePak® Base for z/OS

ResourcePak Base facilitates communication between the Symmetrix system and mainframe-based applications provided by EMC or independent software vendors.

SRDF® Host Component for z/OS

SRDF Host Component monitors SRDF status and controls SRDF processes through the use of commands executed from a host. SRDF maintains a real-time copy of data at the logical volume level in multiple Symmetrix systems located in physically separate sites.

TimeFinder®/Clone Mainframe Snap Facility

TimeFinder/Clone Mainframe Snap Facility is the software foundation for three functional products:

◆ TimeFinder/Clone allows creating point-in-time copies of full volumes or individual datasets

◆ TimeFinder/Snap allows creating pointer-based copies where only the pre-images of changed data are written to the save area.

◆ TimeFinder/Consistency Group allows performing snap and clone operations on volumes so that the target is dependent write consistent.

TimeFinder/Mirror for z/OS

TimeFinder/Mirror allows you to create Business Continuance Volumes (BCVs) and gives you the ability to ESTABLISH, SPLIT, RE-ESTABLISH and RESTORE from the source logical volumes.

Consistency Groups for z/OS

Consistency Groups is designed to ensure the consistency of data remotely copied by the Symmetrix SRDF feature in the event of a rolling disaster.

TimeFinder Utility for z/OS

TimeFinder Utility is used in conditioning SPLIT BCVs by relabeling the volume and (optionally) renaming and recataloging datasets. This allows the BCV to be mounted and used.

AutoSwap™ for z/OS

AutoSwap can move (swap) workloads from volumes in one set of Symmetrix systems to volumes in other Symmetrix systems without operational interruption.


Introduction

Additional features

The Mainframe Enablers also include other features that can be enabled by the major components. These include:

◆ Multi-Session Consistency ◆ EMC SRDF/AR

Multi-Session Consistency (MSC) provides consistency across multiple Symmetrix systems for SRDF/A groups. The MSC task executes in the EMCSCF (ResourcePak Base) address space.

SRDF/AR allows you to automate data copies across SRDF links to provide a restartable image of the data at a remote site in the event of a disaster at the production site.

Mainframe Enablers documentationThis Mainframe Enablers Installation and Customization Guide and the other manuals for the Mainframe Enablers are available on the EMC online support website.

Note: As information is added, new versions of these documents may be released to EMC Online Support at https://support.EMC.com. Check the website to ensure that you are using the latest versions of these documents.

Table 1 lists the documentation for Mainframe Enablers.

Table 1 Mainframe Enablers documentation

Component Document

Mainframe Enablers Mainframe Enablers Installation and Customization Guide

Mainframe Enablers Message Guide

Mainframe Enablers Release Notes

ResourcePak Base for z/OS ResourcePak Base for z/OS Product Guide

REXX Interface Programmer’s Reference Guide

SRDF Host Component for z/OS SRDF Host Component for z/OS Product Guide

TimeFinder/Clone Mainframe Snap Facility

TimeFinder/Clone Mainframe Snap Facility Product Guide

TimeFinder/Mirror for z/OS TimeFinder/Mirror for z/OS Product Guide

TimeFinder Utility TimeFinder Utility Product Guide

Consistency Groups for z/OS Consistency Groups for z/OS Product Guide

AutoSwap for z/OS Product Guide

Mainframe Enablers documentation 15

http://powerlink.emc.com

Introduction


CHAPTER 2Installation

This chapter describes how to install the EMC Mainframe Enablers software components.

◆ Preinstallation steps ............................................................................................... 18◆ Installing the Mainframe Enablers suite................................................................... 21

Installation 17

Installation

Preinstallation stepsBefore you begin installing the Mainframe Enablers, complete the following steps:

❑ Review the Mainframe Enablers Release Notes.

❑ Review the interoperability information in the E-Lab™ Interoperability Navigator which can be reached at http://elabnavigator.EMC.com.

❑ Make sure that you meet the hardware and software requirements listed in this chapter.

❑ Gather installation information.

Hardware and software requirements

Table 2 lists the Symmetrix system requirements for the Mainframe Enablers. Note that component-specific rows indicate where a particular component has specific requirements.

Table 2 Symmetrix system requirements (page 1 of 2)

Item Requirements

Hardware All currently-supported Symmetrix systems.

Enginuity™ operating environment for Symmetrix

General: Enginuity 5671 (the minimum supported levela) and higher.

TimeFinder/Clone Mainframe Snap Facility: The following are the minimum Enginuity levels required for specified features:

• 5x71 for the following:TimeFinder/Consistency Group - Remote full device snapSYMDV# parameter on local snaps CONFIGPOOL commandsRAID 5 BCV support The DIFFERENTIAL_DATASET and TERMINATE_SESSION_WHEN_COMPLETE parameters

• 5772 for the following:RAID 6 supportThe CCUU, DEVICE, EXTENT_ALLOCATION, and VDEVWAIT parametersRe snaps issued before the current snap is finished with protected and indirect tracks presentNative ExtentsNative FlashCopy

• 5773 for the following:R21 support

• 5874 for the followingVirtual Snap improvementsMulti-device capabilitiesThin device supportCascaded clone supportExtended address volume support


http://elabnavigator.emc.com

http://elabnavigator.emc.com

Installation

The Mainframe Enablers have the mainframe hardware and software requirements listed in Table 3. Before you install the Mainframe Enablers software, make sure your mainframe system meets these requirements.

Symmetrix devices TimeFinder/Clone Mainframe Snap Facility:

If you are going to use your Symmetrix system for Virtual Snapshot, your Symmetrix system must be configured with Virtual and Snap Pool devices.

TimeFinder/Mirror: Your Symmetrix system must be configured with BCV volumes.

Symmetrix configuration parameters

Consistency Groups:

• Prevent auto links recovery after all links failure?: YES.• Force RAs Links off-line after power-up?: YES.• Enable page dataset Mode? YES.

TimeFinder/Mirror (Required for SRDF/AR only.):

• Prevent auto links recovery after all links failure?: YES.• Force RAs Links off-line after power-up?: YES.

a. This minimum supported release level is accurate at the time of publication; but, the minimum release level is subject to change. Please check the EMC Support Matrix on https://support.EMC.com for the most current information. Contact your EMC Customer Support Engineer to verify that your system meets these requirements.

Table 2 Symmetrix system requirements (page 2 of 2)

Item Requirements

Table 3 Symmetrix Hardware and software requirements

Item Requirements

Hardware • Any system that supports versions of the z/OS operating system currently supported by IBM.

• FTP or TSO connection to an open systems host (if you are installing by download or CD).• Open system host with a CD-ROM drive (if you are installing by CD).

Software • Any version of the z/OS operating system currently supported by IBM.• JES2 or JES3 environments. • RACF 1.9 or higher, or an equivalent SAF compliant security product, must be installed and

activated.The Mainframe Enablers are not supported in native VM. However, you can run on an MVS guest under VM. VM does not allow volumes defined as unsupported to be attached to SYSTEM, or used to IPL a virtual machine. When running on a guest under VM, the Mainframe Enablers require special consideration. You must define volumes to VM (SET RDEV) as TYpe UNSUPorted DEVClass DASD DPS Yes RESERVE_RELease Yes. You must attach volumes to the guest.

Special requirements

ResourcePak Base:

Running your PROC with the parameter SUB=MSTR. a

Consistency Groups:

Running your PROC with the parameter SUB=MSTR. b TimeFinder/Mirror:

TimeFinder/Clone and TimeFinder/Consistency Group must be enabled if you are using clone emulation.

a. Required if you are planning to swap page datasets, JES2 checkpoint datasets, or to use couple datasets.

b. Required if you are running EMC AutoSwap.

Preinstallation steps 19

Installation

Installation information

Before beginning the Mainframe Enablers installation, identify or decide upon the following items:

CLIST library and EDIT macro — Determine a name for the edit macro created by the installation dialog. You also need to choose the name of a CLIST library where you can store the edit macro.

Product dataset name prefix — Choose the dataset prefix you will use to install the Mainframe Enablers. Names for the product datasets consist of a final qualifier, such as LINKLIB, and a dataset prefix. EMC recommends that you use EMC.SMFEvrm as the dataset prefix if it agrees with your site standards.

However, you can use any dataset prefix. For example, if you choose a dataset prefix of EMC.PRODvrm, the LINKLIB dataset will be named EMC.PRODvrm.LINKLIB.

IMPORTANT

Hereafter, datasets created using this dataset prefix are referred to as if they had been created with the suggested prefix EMC.PRODvrm. The actual fmid for your installation may be different.

Ensure that you have RACF ALTER authority (or the equivalent from another security manager) for the datasets created with this dataset prefix.

SMP/E dataset name prefix — Choose the name prefix for the SMP/E datasets into which you install the Mainframe Enablers. You should install all the components into the same CSI.

For example, if you already have SMP/E maintained EMC products and the SMPLOG dataset is called “EMC.SMPE.SMPLOG,” the SMP/E dataset prefix should be “EMC.SMPE.”

If you are installing an EMC SMP/E maintained product for the first time, EMC recommends using “EMC.SMPE.”

SMP/E datasets volser — Choose the disk volume onto which you will install the distribution libraries (required by SMP/E). This may be the same volume as you use for the product libraries. However, many customer sites prefer to keep SMP/E-related datasets on separate volumes from product libraries. An amount of space similar to that needed for the product libraries is required.

Install-to-disk volser — Choose the disk volume onto which you will install the target (that is, runtime) datasets. The space required is nominal.

Note: EMC suggests that you use EMC.SMFEvrm if it agrees with your site standards. However all examples in this chapter use EMC.PRODvrm.

Disk unit name — Decide upon a disk unit name for the above volumes. For many users, “SYSDA” will suffice. However, use whatever generic or esoteric name your local standards require.


Installation

Installing the Mainframe Enablers suiteThe Mainframe Enablers kit includes a PDS containing TSO TRANSMIT images of files. You must use these files to perform SMP/E indirect-library installation. This PDS is packaged as a TSO TRANSMIT file on CD or as an electronic download from the EMC online support website.

To install the Mainframe Enablers on an IBM mainframe, take the following steps:

1. Load the TSO TRANSMIT file, PRODvrm.XMITFILE, to the mainframe disk. Use TSO Receive to receive the XMITFILE into a PDS.

2. Run PRODvrm.XMITLIB(#EXTRACT) to extract ds-prefix.RIMLIB and the SMP/E indirect libraries.

3. Customize the RIMLIB JCL.

4. Run the installation jobs.

5. Apply any available maintenance.

6. License your software.

7. Shut down and restart ResourcePak Base.

The following sections describe these steps in more details.

Loading PRODvrm.XMITFILE to disk

1. Take one of the following steps:

• If you are installing the Mainframe Enablers from a CD, mount the CD on an open system host. Allocate a working directory on the open system for the installation. Copy the contents of the CD to the working directory.

• If you are installing the Mainframe Enablers from an EMC online support download, complete the following steps:

a. Log in to a privileged account on an open systems host (root on UNIX or administrator on Windows).

b. Allocate a working directory on the open system for the installation.

c. Log on to:


d. Click Downloads, and type Mainframe Enablers in the Find a Product text field.

Note: If you are not able to access this location, you may not have registered your software or registered it incorrectly. Follow the prompts to correct your registration, or contact EMC in the event of a problem.

Result: You see a page for the product you selected.

e. Click the product version you want to download. The product version consists of a zip file that contains the installation kit and the installation instructions.

f. Download the installation kit into the working directory.

Installing the Mainframe Enablers suite 21

Installation

2. If your current host is a Windows system, unzip the file into the working directory. If your current host is a UNIX system, unzip and untar the file into the working directory.

3. Locate PRODvrm.XMITFILE. This file is in TSO TRANSMIT format and contains:

• a flattened copy of PRODvrm.XMITLIB

• a PDS that holds other TRANSMIT images

• JCL to extract them

• SMP/E installation files

4. On the target mainframe, allocate a file to which you can FTP PRODvrm.XMITFILE. Use the dataset name prefix you intend to use for product installation. The final qualifier must be XMITFILE.

For example, if you intend to install the product with a dataset name prefix of EMC.PRODvrm, name the file EMC.PRODvrm.XMITFILE.

5. Allocate the dataset with the following characteristics:

LRECL=80BLKSIZE=3120DSORG=PSSPACE=(CYL,(60,2))

Note: The SPACE parameter here and elsewhere assumes that you are allocating the dataset on a 3390 device.

6. FTP the file to the mainframe in binary format. Your FTP session may look like:

ftp hostname

(username and password prompts)

cd..

25 “’’” is working directory name prefix

binary

200 Representation type is image

put PRODvrm.XMITFILE ‘EMC.PRODvrm.XMITFILE’

7. Use TSO RECEIVE to receive the file into a PDS. The PDS is created by the RECEIVE command and does not have to be preallocated. However, you must specify a dataset name using the DA[dataset] parameter or the file will be allocated using your TSO prefix (usually your logonid). The dataset name specified must have the final qualifier of XMITLIB. For example:

receive indataset(‘EMC.PRODvrm.XMITFILE’)

INMR901I Dataset EMC.PRODvrm.XMITLIB from userid on nodename

INMR906A Enter restore parameters or ‘DELETE’ or ‘END’ +

da(‘EMC.PRODvrm.XMITLIB’)


Installation

If you did not specify “DA(…)” as above, the dataset would be allocated as userid.XMITLIB.

Running PRODvrm.XMITLIB(#EXTRACT)

Run PRODvrm.XMITLIB(#EXTRACT) to extract ds-prefix.RIMLIB and the SMP/E indirect libraries. Complete the following steps:

1. Edit the #EXTRACT member of the newly RECEIVED library. You can edit the #EXTRACT job by running the SETUP REXX program in the XMITLIB dataset. The SETUP REXX program prompts you for all of the information needed to edit the JOB.

To edit the JOB manually, make the following changes:

a. Change the JOB card to one that conforms to your standards.

b. Globally change ds-prefix to the dataset prefix of this library (which will be the dataset prefix for the product libraries).

c. Globally change DVOL to the disk volser onto which you want to place the extracted libraries.

d. Globally change DISK-UNIT to an esoteric unit name such as “SYSDA” that is appropriate for your site.

2. Submit #EXTRACT. Step completion codes should be zero (0), except for the DELETE step. DELETE will have a step completion code of eight (8) unless the job is a rerun.

Customizing the RIMLIB JCL

The RIMLIB library (ds-prefix.RIMLIB) is a PDS containing JCL to install the product. After you extract the RIMLIB PDS, RIMLIB has the contents shown in Table 4.

Table 4 RIMLIB contents (page 1 of 2)

File Contents

#U1ALLOC Allocate target and distribution libraries (for upgrade install only).

#U2DFZON (Placeholder) Job #02 is not used during an upgrade install.

#U3REPRO (Placeholder) Job #03 is not used during an upgrade install.

#U4DDDEF Add or replace product library DDDEFS in the SMP/E CSI (upgrade install only).

#01ALLOC Allocate target and distribution libraries.

#02DFZON Define the SMP/E CSI dataset.

#03REPRO Repro to load the SMP/E CSI dataset.

#04DDDEF Add or replace product library DDDEFS in the SMP/E CSI.

#05RECEV SMP/E RECEIVE function into global zone.

#06APPLY SMP/E APPLY function into target zone.

#07ACCPT SMP/E ACCEPT product sysmods into distribution zone.

#08CLEAN Delete indirect libraries and DDDEFs used for them.


Installation

Take the following steps to customize the installation JCL using the automated dialog:

1. Edit the RIMLIB library (ds-prefix.RIMLIB).

2. Locate the member named SETUP on the member selection list and type EX in the selection column next to it and press Enter.

Menu Functions Confirm Utilities Help ------------------------------------------------------------------------------ EDIT EMC.PRODvrm.RIMLIB Row 00001 of 00013 Command ===> Scroll ===> CSR Name Prompt Size Created Changed ID _________ #U1ALLOC 45 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #U2DFZON 80 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #U3REPRO 55 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #U4DDDEF 51 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #01ALLOC 45 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #02DFZON 80 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #03REPRO 55 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #04DDDEF 51 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #05RECEV 22 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #06APPLY 22 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #07ACCPT 22 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #08CLEAN 53 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #90SAFJB 28 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #91SNPJB 80 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #92SAFJB 28 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ #99MAINT 27 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ MFEJCL 206 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740_________ MFEWIN1 51 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740ex_______ SETUP 13 yyyy/mm/dd yyyy/mm/dd hh:mm:ss MFE740 **End**

Result: The panel shown in Figure 1 on page 25 is displayed.

#90SAFJB (Optional) JCL to remove EMCSAFI and replace it with EMCSAFD or with your own modified EMCSAFI. (Chapter 4 provides more information.)

#91SNPJB (Optional) JCL to change the TimeFinder/Clone Mainframe Snap Facility defaults.

#92SAFJB (Optional) JCL to restore the default EMCSAFI object code (not the SAMPLIB member) to its state when the Mainframe Enablers was first installed (including any maintenance that was installed at that time).

#99MAINT Sample file for SMP/E RECEIVE and APPLY service.

MFEJCL REXX to customize the install process.

MFEWIN1 Panel used in REXX install process.

SETUP REXX to simplify the customization process.

Table 4 RIMLIB contents (page 2 of 2)

File Contents


Installation

Figure 1 EMC JCL customization utility panel

3. Enter or change the following information on the panel shown in Figure 1 to customize your installation:

a. The “CLIST library” field is set by default to RIMLIB library. This field should contain the name of a library in which you want the edit macro created by this dialog to be stored.

The default value is fine for most users and need not be changed.

b. In the ”Edit macro name” field, either:

– Accept the default name displayed.

– If necessary, change the name of the edit macro.

Note: Normally, you should not have to change the name.

Result: The edit macro is created in the CLIST or EXEC library from the data entered on this panel and applied to all members of RIMLIB that start with a # character.

c. In the “Product dsname prefix” field, enter the dataset name prefix you want to use for the target datasets. EMC suggests EMC.fmid (for example, EMC.PRODvrm).

d. In the “SMP/E dsname prefix” field, enter the dataset name prefix of the SMP/E datasets into which you installed ResourcePak Base (EMCSCF).

For example, if you called the SMPSCDS dataset EMC.SMPE.SMPSCDS, enter EMC.SMPE.

e. In the “SMP/E datasets volser” field, enter the six-character volume serial number of the disk volume on which you want to allocate the SMP/E distribution libraries for PROD.

This volume may be the same as the volume you specify in step f, or you may select to keep these datasets on a separate volume.

f. In the “Install-to disk volser” field, enter the six-character volume serial number of the disk volume to which you want to install the PROD libraries.

EMC JCL Customization Utility COMMAND ==> _____________________________________________________ Type EXEC on the command line and press ENTER to proceed, or PF3 to exit.

CLIST library ==> ____________________________________________ Edit macro name ==> PROD Product dsname prefix ==> EMC.PRODvrm SMP/E dsname prefix ==> EMC.SMPE SMP/E datasets volser ==> ______ Install-to disk volser==> ______ Disk unit name ==>


26

Installation

g. In the “Disk unit name” field, you can specify an esoteric disk name that is appropriate to your site. SYSDA is the default, but you can overtype it with another esoteric disk name.

h. Enter a site-appropriate job card.

The job card is initially set to a value which may be suitable to many users. The first seven characters of the job name is set to your TSO userid, plus “X.”

You can set the job name to %MEMBER%. This causes the edit macro to set each job name equal to the JCL member name (that is, #01ALLOC, #02DDDEF, and so forth).

Do not use any parameter that contains an ampersand (&), such as NOTIFY=&SYSUID. An ampersand in the job card can cause edit macro errors.

Figure 2 on page 26 shows an example of a completed panel.

Figure 2 Completed customization utility panel

4. When you are satisfied with your entries, type exec on the command line and press Enter.

Result: If the dialog completes successfully, you see something similar to the following:

BUILDING AN EDIT MACRO(PROD) IN 'EMC.PRODvrm.RIMLIB'PROCESSING MEMBER: #U1ALLOCPROCESSING MEMBER: #U2DFZON

EMC JCL Customization Utility COMMAND ==> _____________________________________________________ Type EXEC on the command line and press ENTER to proceed, or PF3 to exit.

CLIST library ==> ____________________________________________ Edit macro name ==> PROD Product dsname prefix ==> EMC.PRODvrm SMP/E dsname prefix ==> EMC.SMPE SMP/E datasets volser ==> ______ Install-to disk volser==> PRODvrm Disk unit name ==> SYSDA Enter your job card below (’%MEMBER%’ will be replaced by member name): ==> %MEMBER% JOB MSGCLASS=A,CLASS=A,NOTIFY=TPRODUSER

Mainframe Enablers Version 7.6 Installation and Customization Guide

Installation

PROCESSING MEMBER: #U3REPROPROCESSING MEMBER: #U4DDDEFPROCESSING MEMBER: #01ALLOCPROCESSING MEMBER: #02DFZONPROCESSING MEMBER: #03REPROPROCESSING MEMBER: #04DDDEFPROCESSING MEMBER: #05RECEVPROCESSING MEMBER: #06APPLYPROCESSING MEMBER: #07ACCPTPROCESSING MEMBER: #08CLEANPROCESSING MEMBER: #90SAFJBPROCESSING MEMBER: #91SNPJBPROCESSING MEMBER: #92SAFJBPROCESSING MEMBER: #99MAINT***

Running the installation jobs

Carefully examine each job before you submit it to make sure that it was customized in the way you intended.

If installing into a new set of SMP/E libraries, submit the customized jobs in the following order, making sure that each job completes successfully before submitting the next one:

1. #01ALLOC

2. #02DFZON

3. #03REPRO

4. #04DDDEF

5. #05RECEV

6. #06APPLY

7. #07ACCPT

If installing into an old set of SMP/E libraries (Mainframe Enablers V7.0 or higher only), submit the customized jobs in the following order, making sure that each job completes successfully before submitting the next one:

1. #U1ALLOC

2. #U4DDDEF

3. #05RECEV

4. #06APPLY

5. #07ACCPT

You should expect completion codes of 0 (zero) for all jobs except for #U4DDDEF or #04DDDEF and #07ACCPT, where 04 is acceptable.

SMP/E installation is now complete.


Installation

Applying maintenance

You must install any available maintenance for the Mainframe Enablers before you restart ResourcePak Base or start any of the other started tasks in the Mainframe Enablers suite (Consistency Groups and SRDF Host Component). If there is no current maintenance, keep these instructions for future use when you do need to download maintenance.

Note: Do not apply maintenance until after the Mainframe Enablers are accepted.

You can obtain the latest maintenance updates and current release and service notes from the Software Downloads and Licensing option on the Support menu at the EMC online support website:

You can obtain the latest maintenance updates and current release and service notes in the Downloads page at EMC Online Support (https://support.EMC.com).

Note: You must register on EMC Online Support as a valid EMC customer before you can access it. Make sure as well that your license for this software is registered. If it is not, you will not be able to access the Downloads option of the website.

On the page for your product, you will see files for different product versions. For your version, you may see the following types of files:

◆ ReadMe_prodvrm_Fixes.txt - contains a list of the fixes included in the release.

◆ Service_Notes_prodvrm.txt - is an update of the release notes. It contains information discovered after initial release of the product.

◆ prodvrm_fixes.zip - contains all the previous files as well as a binary file that contains all available PTFs (prodvrmFIX.BIN) and a sample job (smpjob.txt) with instructions about how to apply the maintenance.

Where:

prod = The product prefix.

vrm = The version, revision level, and modification level of the software you want.

Complete the following steps to download these files:

1. Log on to:


2. Click Downloads and type Mainframe Enablers in the Find a Product text field.

Result: You see a page for the product you selected. On the page is a table of zip files and document files.

3. Complete either of the following steps:

• To download a copy of a document, click ReadMe_prodvrm.txt, ReadMe_prodvrm_Fixes.txt, or Service_Notes_prodvrm.txt.

• Download and extract the zip file. Follow the instructions in it.

4. After reading or copying, return to previous pages to view other products and services, or choose logout from the menu bar at the top of any page.


http://Powerlink.EMC.com



Installation

5. Upload the prodvrmFIX.BIN in binary mode to your mainframe host. Use the TSO RECIEVE command to create an SMPPTFIN dataset.

6. Upload the SMPJOB.TXT file in text mode. Edit smpjob.txt (in prodvrm_FIXES.ZIP) to install the maintenance. You can find editing instructions in the smpjob.txt comments.

7. Submit the smpjob.txt file to receive and apply the maintenance.

Note: Appendix A describes how you can determine the current maintenance level of your Mainframe Enablers.

Licensing your software

Starting with the release of Enginuity 5875, Mainframe Enablers introduced support for Electronic Licensing (eLicensing). eLicensing is an end-to-end license management solution to help you track and comply with software license entitlement. eLicensing leverages embedded locking functions and back-office IT systems and processes. It provides you with better visibility into software assets, easier upgrade, and capacity planning and reduces risk of non-compliance, while still adhering to a strict “do no harm” policy to your operations. This ensures that when upgrades are performed from a Symmetrix VMAX Series system running Enginuity versions lower than 5875 to a system running Enginuity 5875 or higher, the system is scanned for Enginuity features currently in use that require eLicenses. If Enginuity features are found in use, and there are no eLicenses registered and applied to support their use, they are internally reported as "IN USE," which allows continued access to the Enginuity features while reporting that these features require proper licensing to ensure compliance. By only reporting this information, it prevents disruption to normal operations of your system and business. If your eLicensing report does display one or more Enginuity features as "IN USE," it is your responsibility to work with your EMC Sales team to obtain proper eLicensing for those features.

With the introduction of eLicensing, Symmetrix licensing moved from a host-based model to a Symmetrix-based model, with the majority of licenses now being stored internally on the Symmetrix system.

When installing licenses with eLicensing, you obtain license files from the EMC online support website, copy them to a Solutions Enabler or a Unisphere for VMAX host, and push them out to Symmetrix systems. Each license file fully defines all of the entitlements for a specific system, including the type of license (Individual or Enterprise), the licensed capacity, and the date the license was created. If you want to add a product title or increase the licensed capacity of an entitlement, you must obtain a new license file from the EMC online support website and push it out to the Symmetrix system.

Note: If there is no open host attached to your Symmetrix system, contact your EMC Service Engineer for installation and activation of your license files.

When managing your licenses, Mainframe Enablers, Solutions Enabler, Unisphere for VMAX, EMC z/OS Storage Manager (EzSM), TPF, and IBM i platform console allow you to view detailed usage reports so that you can better manage your capacity and compliance planning.


Installation

Note: For more information on eLicensing, refer to EMC KnowledgeBase article emc251709 on the EMC online support website.

LicensesMost Symmetrix licenses use the Symmetrix-based model. However, there are still a number of Symmetrix licenses that remain host-based. In addition, there are a number of retired host-based licenses.

Note: The process for obtaining the remaining host-based licenses will remain the same as previous versions of Mainframe Enablers.

Symmetrix-based licenses

With the release of Enginuity 5876, Mainframe Enablers provides support for Symmetrix-based license bundles. A license bundle is a single license that enables multiple features. For example, the Symmetrix Remote Replication Suite license bundle enables the SRDF, SRDF/A and SRDF/S product titles. For Symmetrix systems running versions of Enginuity 5875, Mainframe Enablers continues to support individual Symmetrix-based licenses.

Note: Bundles are available only if all features are enabled.

Table 5 lists the Symmetrix-based licenses supported with Enginuity 5876 and Enginuity 5875.

Table 5 Symmetrix-based licenses supported with Enginuity 5876 and Enginuity 5875 (page 1 of 2)

License/Description Allows you to With the commands

Enginuity 5876 and higher Enginuity 5875

SYMM_VMAX_ENGINUITY

License for whole arrayIncludes:

Dynamic Cache PartitioningSymmetrix Priority Controls

SYMM_VMAX_ENGINUITY

License for whole system

N/A N/A

SYMM_DCP

Dynamic Cache Partitioning

Enable cache partitions for a Symmetrix array

Create cache partitions

Set cache partitions

SETCACHE

SETCPxxx

SYMM_SPC

Symmetrix Priority Controls

Enable priority of service for a Symmetrix array

Set host I/O priority

Set copy QoS priority

SETSPC

SETDIR

SETDEV

SETDEVP

SYMM_VMAX_FAST_TIERING

Symmetrix Tiering SuiteIncludes:

FAST for disk groupsFAST for virtual pools

N/A Enable FAST N/A

FAST is configured via Solutions Enabler or Symmetrix Management Console


Installation

SYMM_VMAX_TIMEFINDER

Symmetrix TimeFinder SuiteIncludes:

TimeFinder/CloneTimeFinder/Snap

SYMM_TF_CLONE

TimeFinder/Clone

Create new native clone sessions

Create new TimeFinder/Clone emulations

SNAP TARGET

TimeFinder Mirror ESTABLISH

SYMM_TF_SNAP

TimeFinder/Snap

Create new sessions

Duplicate existing sessions

Create snap pools

Create SAVE devices

SNAP VDEV

SYMM_VMAX_SRDF_REPLICATION

Symmetrix Remote Replication SuiteIncludes:

SRDFSRDF/Asynchronous modeSRDF/Synchronous mode

SYMM_SRDFa

SRDF

Create new RDF groups

Create dynamic RDF pairs in Adaptive Copy mode

Create RDF devices

Convert non-RDF devices to RDF

Add RDF mirrors to devices in Adaptive Copy mode

Set the dynamic-RDF capable attribute on devices

Create SAVE devices

SC RDFGRP ADD

SC VOL CREATEPAIR(ADCOPY)

SC VOL CREATEPAIR(ADCOPY-DISK)

SC VOL CASCRE(ADCOPY)

SC VOL CASCRE(ADCOPY-DISK)

SYMM_SRDF_A

SRDF/Asynchronous mode

Create dynamic RDF pairs in Asynchronous mode

Set RDF pairs into Asynchronous mode

Add RDF mirrors to devices in Asynchronous mode

Create RDFA_DSE pools

Set any of the following SRDF/A attributes on an SRDF group:

• Minimum Cycle Time• Transmit Idle• DSE attributes• Write Pacing attributes

SC SRDF_CMPR

SC SRDFA ACT

SC SRDFA_DSE ACT | AUTO_ACT | THRESHOLD | xxxx_POOL

SC SRDFA_WP ACT | AUTO_ACT

SYMM_SRDF_S

SRDF/Synchronous mode

Create dynamic RDF pairs in Synchronous mode

Set SRDF pairs into Synchronous mode

Add an RDF mirror to a device in Synchronous mode

Startup (EXEC PGM=CGRPMAIN)

SC SRDFA CONS_DEACT

SC SRDFA PEND_DEACT

SC SRDFA PEND_DROP

SC VOL NADCOPY

SC VOL CASCRE

SC VOL CREATEPAIR

SYMM_VMAX_SRDF_STAR

SRDF/Star

SYMM_SRDF_STAR

SRDF/Star

Perform a setup to initialize the environment

MSC_STAR parameter at SRDF Host Component startup

a. Requires that the Symmetrix array also be licensed for SRDF/A (SYMM_Model_SRDF_A) and/or SRDF/S (SYMM_Model_SRDF_S).

Table 5 Symmetrix-based licenses supported with Enginuity 5876 and Enginuity 5875 (page 2 of 2)

License/Description Allows you to With the commands

Enginuity 5876 and higher Enginuity 5875


Installation

Host-based licenses

Table 6 lists the host-based licenses required to perform operations on Symmetrix systems running Enginuity versions lower than 5875 from a Mainframe Enablers V7.4 host and the elements used to validate the presence of the applicable license.

Table 6 Host-based licenses required for Enginuity versions lower than 5875

Feature Model numberRequired Mainframe Enablers component Function/command

Parameter or keyword checked

SRDF/DM a SRDFDM-RN-ZOS SRDF Host Component SC VOL command SYNC

SRDF Host Component and Consistency Group

SRDFS-RN-ZOS SRDF Host Component Startup (EXEC PGM=EMCINIT)

N/A

Consistency Groups Startup (EXEC PGM=CGRPMAIN)

N/A

SRDF/A MSC SRDFA-RN-ZOS SRDF Host Component Initialization MSC_INCLUDE_SESSION

SRDF/AR b SRDFAR-RN-ZOS TimeFinder/Mirror SRDF/AR ADD

SRDF/AR DELETE

SRDF/AR MODIFY

N/A

EMC AutoSwap™ for z/OS AUTOSWAPMSUxx Consistency Group CAX configuration parameter

N/A

AutoSwap N/A N/A

SRDF/Star for z/OS SRDFSTAR-RN-Z SRDF Host Component Initialization MSC_STAR

TimeFinder/Clone for z/OS c TF-C-RN-ZOS TimeFinder/Clone Mainframe Snap Facility

Startup (EXEC PGM=EMCSNAP)

SNAP command

N/A

TARGET or TRG

TimeFinder/Mirror (for clone emulation) d

ESTABLISH command

GLOBAL command

CLONEemulation

CLONEemulation

TimeFinder/Snap for z/OS c TF-S-RN-ZOS TimeFinder/Clone Mainframe Snap Facility

Startup (EXEC PGM=EMCSNAP)

N/A

SNAP command VDEV

Dynamic Cache Partitioning for z/OS

DYNCP-RN-ZOS ResourcePak Base SETCACHE command

SETCPxxx command

N/A

Symmetrix Priority Control for z/OS

SYMPRCNT-RN-Z ResourcePak Base SETSPC command

SETDIR command

SETDEV command

SETDEVP command

N/A

N/A

N/A

N/A

Host-based Compatible Flash for z/OSe

CMPFLASH-xxx ResourcePak Base N/A N/A

a. SRDF/DM requires an EMC Customer Support defined Symmetrix configuration setting. It does not require an LFC.

b. In addition to the SRDF/AR LFC, TimeFinder/Mirror also requires the TimeFinder/Consistency Group LFC (SRDF/AR does a consistent SPLIT) and the Timefinder/Clone (TARGET LFC) for Clone Emulation.

c. TimeFinder/Clone and TimeFinder/Snap LFCs are processed at ResourcePak Base (EMCSCF) initialization, and validated at batch EMCSNAP execution.

d. TimeFinder/Mirror under Enginuity 5874 or higher uses only clone emulation. It also requires use of devices configured with the BCV attribute.

e. Compatible Flash for z/OS is available only with Enginuity 5773 and lower.


Installation

Table 7 lists the host-based licenses that remain unchanged, regardless of Enginuity level.

Retired licenses

The following licenses are retired. The features that required these licenses still exist, they just no longer require licenses.

◆ Base◆ Cache◆ Configuration Manager◆ Config Mgr - Create VDEVs (Snap Configure)◆ Delta Mark◆ Device Masking◆ IPsec◆ Open Replicator/LM◆ Secure Erase◆ SRDF/Automated Replication◆ SRDF/Cascading RDF◆ SRDF/Consistency Groups◆ SRM_BASE◆ SRM_Enabler◆ SRM_FULL◆ SYMAPI Server◆ TimeFinder/Consistency Groups◆ TimeFinder/Exchange Integration Module◆ TimeFinder/SQL Integration Module◆ Virtual Provisioning◆ Worm

Managing Symmetrix systems running different Enginuity versionsThe operations that you can perform from a host are based on the host-based licenses in the host’s SCFINI file, if any, and the Symmetrix-based licenses in the system’s feature registration database (Enginuity 5875 and higher).

The remainder of this section describes how the operations you can perform from a Mainframe Enablers host are determined when accessing various Enginuity versions.

Mainframe Enablers V7.4 (or higher) host

When accessing a Symmetrix system running Enginuity 5875 or higher from a host running Mainframe Enablers V7.4 or higher, the operations you can perform on the system are based on:

◆ The licenses in the system’s feature registration database (Table 5 on page 30).◆ The licenses in the host’s SCFINI file, if using any of the host-based features listed in

Table 6 on page 32.

Table 7 Host-based licenses unchanged, regardless of Enginuity level

License Commands included

AutoSwap for z/OS AutoSwap: N/A

Consistency Group: CAX configuration parameter

z/OS Migrator N/AStartup (EXEC PGM=EFMMMAIN)


Installation

When accessing a Symmetrix system running an Enginuity version lower than 5875 from the same host, the operations you can perform on the system are based on the licenses in the host’s SCFINI file, if using any of the host-based features listed in Table 6 on page 32. If not, you can only perform operations that do not require a license.

When accessing a Symmetrix VMAX Series system upgraded from Enginuity 5874 to Enginuity 5875 or higher from a host upgraded to Mainframe Enablers V7.2 or higher, any product title that you were currently using will still function (even if it does not have an entitlement). However, to use any of the new Enginuity 5875 or higher product titles or any of the older product titles you were not using, you must obtain and install a Symmetrix-based license file on the system. “Installing Symmetrix-based licenses” on page 37 describes how to install license files.

Mainframe Enablers V7.0 host

When accessing a Symmetrix system running Enginuity 5876 or lower from a host running Mainframe Enablers V7.0, the operations you can perform are based on the licenses in the host’s SCFINI file.

Capacity measurementsSymmetrix-based licenses include a capacity licensed value that defines the scope of the license. The method for measuring this value depends on the license’s capacity type (“Raw capacity”, “Registered capacity”, or “External capacity”).

Not all product titles are available in both capacity types, as shown in Table 8.

Raw capacity

Raw capacity is the sum of the rated capacity of all disks of type SATA or Non-SATA in the system (in TB, where 1kB = 1000 bytes), excluding spares for that type.

The type of raw capacity disks can be the SATA disks in the system, or the Non-SATA disks in the system (both types can and do appear in the license file).

Table 8 Product title capacity types

Raw only Raw or Registered External

Enginuity SRDF/Asynchronous mode SRDF/Asynchronous modea

Dynamic Cache Partitioning SRDF/Synchronous mode SRDF/Synchronous modea

Symmetrix Optimizer SRDF/Star SRDF/Star

Symmetrix Priority Controls TimeFinder/Clone Synthesized SRDFb

Unisphere for VMAX TimerFinder/Snap TimeFinder/Clonec

RCOPY FAST for disk groups TimeFinder/Snapc

FAST for virtual pools FAST for virtual poolsd

a. With Enginuity 5876 or higher, this license is distributed with the Symmetrix Remote Replication Suite.

b. Created from SRDF/A and SRDF/S entitlements in the license file.

c. With Enginuity 5876 or higher, this license is distributed with the Symmetrix TimeFinder Suite.

d. With Enginuity 5876 or higher, this license is distributed with the Symmetrix Tiering Suite.


Installation

Registered capacity

Registered capacity is the amount of user data that will be managed or protected by each particular product title. It is independent of the type or size of the disks in the system.

The methods for measuring registered capacity depends on whether the licenses are part of a bundle or individual.

Registered capacity for license bundles (Enginuity 5876 or higher)

For license bundles, registered capacity is measured according to the following:

◆ Symmetrix Tiering Suite

• The registered capacity for this bundle is measured as the sum of the following two parts:

– The registered capacity of all devices associated with all FAST_VP policies.

– The registered capacity of all devices associated with all FAST policies but not associated with a FAST_VP policy.

• For virtually provisioned devices, the registered capacity is equal to the total space allocated to the thin device. For devices that have compressed allocations, the un-compressed size is used.

• For disk group provisioned devices, the registered capacity is equal to the total size of the device.

◆ Symmetrix Remote Replication Suite

• The registered capacity for this bundle is measured by the amount of data that can be stored in all forms of SRDF devices (R1s, R2s, R21s, R11, and R22s) on a Symmetrix system.

– Concurrent SRDF sources are counted only once when measuring registered capacity usage.

– In the case of diskless SRDF (Extended Data Protection), no registered capacity is reported as used.



◆ Symmetrix TimeFinder Suite

• The registered capacity of this bundle is measured as the sum of the capacity of a device if it is a clone Source or Target, a snap Source, or SAVE device in a snap pool. Regardless of whether a device meets two or more of the following criteria, it is only counted once.




Installation

Registered capacity for individual licenses

For individual licenses, registered capacity is measured according to the following:

◆ FAST registered capacity is measured as the sum of the registered capacity of all devices that are associated with all FAST policies that contain disk group tiers.

◆ FAST VP registered capacity is measured as the registered capacity of all devices that are associated with all FAST policies that contain virtual pool tiers.

◆ SRDF registered capacity is measured as the configured size of all forms of SRDF standard devices (R1s, R2s, R21s, R11, and R22s). In the case of thin devices, it is the size of allocated tracks associated with all forms of SRDF devices (R1s, R2s, R21s, R11, and R22s).

• Concurrent SRDF sources are counted only once when measuring registered capacity usage.

• In the case of diskless SRDF (Extended Data Protection), no registered capacity is reported as used.

◆ SRDF/Star registered capacity is measured as the configured size of all standard devices participating in SRDF/Star configurations. In the case of thin devices, it is the size of allocated tracks on devices associated with SRDF/Star configurations.

◆ TimeFinder/Clone registered capacity is measured as the configured size of all standard devices that are clone sources or clone targets. In the case of thin devices, it is the size of allocated tracks on devices that are clone sources or clone targets.

The registered capacity of a device that is both a clone target and a clone source for another is counted once.

◆ TimeFinder/Snap registered capacity is measured as the configured size of all save pools, plus the configured size of all standard devices that are snap source devices. In the case of thin devices, it is the size of allocated tracks on devices that are snap source devices.

The following devices are not counted in registered capacity:

◆ SAVE devices not in any pool◆ DATA devices not in any pool◆ Devices not associated with SRDF or TimeFinder

Registered capacity is reported in a tenth of a terabyte format (e.g., 42.3 TB) and rounded up or down to the nearest GB. For example, 42.31 TB and 42.25 TB will round to 42.3 TB.

External capacity

External capacity is measured by the sum of the sizes of virtualized LUNs from external storage.

If an entitlement is licensed for registered and external capacity, any external usage will be added to the internal usage.


Installation

Installing Symmetrix-based licenses

IMPORTANT

If there is no open host attached to your Symmetrix system, contact your EMC Service Engineer for installation and activation of your license files.

This section explains how to use the Solutions Enabler symlmf add command to install Symmetrix-based licenses.

Note: Installing licenses requires a Symmetrix authorization role of Storage Admin or higher.

You can only install Symmetrix-based licenses from a host running one of the following operating systems:

◆ Windows: x86, AMD64, IA64◆ Linux: x86, AMD64, IA64◆ Solaris: 32 bit (Sparc), 64 bit (Sparc) ◆ HPUX 11.11: PA-Risc 32, PA-Risc 64◆ HP-UX 11.21: IA64◆ AIX 5.3 and 6.1: PPC 32, PPC 64

For instructions on installing from a host running a supported operation systems, refer to “Installing from a supported host” on page 37. For instructions on installing from a host running a non-supported operating system, refer to “Installing from a non-supported host” on page 38.

Note: To obtain Symmetrix-based licenses from the EMC online support website you will need the License Authorization Code (LAC) identification number from the LAC letter e-mailed to you.

Installing from a supported host

To install a Symmetrix-based license file from a host running a supported operating system:

1. Obtain a license file from the EMC online support website and copy it to your host.

2. Use the following symlmf command to push the license file to the Symmetrix system:

symlmf add -type emclm -sid SymmID -file FileName -v

Where:

SymmID — Specifies the Symmetrix system on which you are installing the license file.

FileName — Specifies the name of the license file.

Output similar to the following displays:

License SYMM_VMAX_SPC 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_DCP 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_FAST_VP 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_FAST 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_OPTIMIZER 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_TF_SNAP 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_TF_CLONE 000000001234 15-Jan-2011: Processed successfully


Installation

License SYMM_VMAX_SRDF_STAR 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_SRDF_S 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_SRDF_A 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_SRDF 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_ENGINUITY 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_OR-DM 000000001234 15-Jan-2011: Processed successfullyLicense SYMM_VMAX_SMC 000000001234 15-Jan-2011: Processed successfully

Total Licenses Processed: 13Total Licenses Not Processed: 0

Note: Issuing the add command without the -v option will eliminate all but the last two lines of the above output.

Installing from a non-supported host

To install Symmetrix-based licenses from a host running a non-supported operating system, use one of the following methods:

◆ Run symlmf directly on the Symmetrix service processor. This method requires that you contact EMC Customer Support.

◆ Run symlmf on one of the supported platforms via client/server to a SYMAPI server on one of the unsupported platforms. This method is recommended when installing Symmetrix-based licenses from the Solutions Enabler Virtual Appliance Configuration Manager.

Installing host-based licenses

Note: Installing licenses requires a Symmetrix authorization role of Storage Admin or higher.

To install a host-based license:

1. Use the following symlmf command to install a license key on a host:

symlmf add -type se -license LicenseNumber

2. Use the following command to list the licenses installed on the host:

symlmf list -type se

Deleting host-based licensesUse the following command to delete a host-based license:

symlmf delete -type se -license LicenseName

Where LicenseName is one of the licenses in Table 6 on page 32 and Table 7 on page 33.

Note: You cannot delete Symmetrix-based licenses.


Installation

Displaying licenses Use the ELM,LIST,CONTROLLER command to list all the eLicensing features included in the Symmetrix system identified in the CONTROLLER field:

F scftaskname,ELM,LIST,CONTROLLER|CNTRL(id)

These commands can be entered as a full word, or can be abbreviated to the first character:

◆ LIST can be abbreviated to L, LI, or LIS

◆ QUERY can be abbreviated to Q, QU, QUE, or QUER

Note: The ResourcePak Base for z/OS Product Guide provides more details about this command syntax.

Example 1 When you issue ELM,LIST,CONTROLLER from a system with Enginuity level 5876 or higher, a report similar to the following displays the licensed bundles:

SCF5005I Report for (Remote) Controller follows 473 Symmetrix ID : 000195600140 Issue Date : 04/04/2012 Activation Capacity Install Feature Name Type ID Type Licensed Date -------------------- ----- ---------- ------------- -------- ----------SYMM_VMAX_ENGINUITY P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0 SYMM_VMAX_FAST_TIERI P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0 SYMM_VMAX_SRDF_REPLI P-IND UNKNOWN 0 00/00/0000SYMM_VMAX_TIMEFINDER P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0 SYMM_VMAX_SRDF_STAR P-IND R-TB-Non-Sata 0 00/00/0000 R-TB-Sata 0

Legend: Act(ivation Type): E-IND = Evaluation Individual P-IND = Permanent Individual P-ENT = Permanent Enterprise Agreement P-LTD = Permanent Limited

Example 2 When you issue ELM,LIST,CONTROLLER from system with Enginuity level 5875, a report similar to the following displays the individual feature licenses:

SCF0341I ELM,LIST,CNTRL(00215) SCF5005I Report for (Local) Controller follows Symmetrix ID : 000192600215 Activation ID: 1234567 Issue Date : 02/16/2011 Capacity Expiration Install Feature Name Act Type Licensed Date Date -------------------- ----- ------------- -------- ---------- ----------SYMM_VMAX_ARRAY P-IND R-TB-Non-Sata 20 - 02/16/2011 R-TB-Sata 10 SYMM_VMAX_TF_CLONE P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_TF_SNAP P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SRDF_S P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SRDF_A P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3


Installation

SYMM_VMAX_SRDF_STAR P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_DCP P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SPC P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_OPTIMIZER P-IND R-TB-Non-Sata 3 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_FAST P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_FAST_VP P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SRDF P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_ORS_DM P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 SYMM_VMAX_SMC P-IND R-TB-Non-Sata 5 - 02/16/2011 R-TB-Sata 3 Legend: Act(ivation Type): E-IND = Evaluation Individual P-IND = Permanent Individual P-ENT = Permanent Enterprise Agreement

Output field descriptions

The following explains the output for the ELM,LIST,CONTROLLER command:

◆ Act(ivation): Whether the feature's license is P(ermanent) or an E(valuation) copy. Evaluation licenses include an Expiration Date for reporting purposes only; the product title can still be used. Permanent licenses can be assigned to Ind(ividual) Symmetrix systems or to all the Symmetrix systems in the Ent(erprise).

◆ Capacity Licensed: The maximum quantity of data for which the functionality of the software is licensed to use, in Terabytes.

◆ Capacity Type: Qualifies the capacity licensed. Possible values are:

• R-TB-Non-SATA: Indicates that the capacity licensed applies to the raw capacity of all devices on the system, excluding SATA.

• R-TB-SATA: Indicates that the capacity licensed applies to the raw capacity of all SATA devices on the system.

• REG-TB: Indicates that the capacity licensed applies to the registered capacity of the Symmetrix system.

◆ Capacity Units: The maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

◆ Days Until Expr: For an Evaluation license, this field displays the number of days until expiration. For a Permanent license, this field displays a hyphen (-). This field only applies to SPA.

◆ Expiration Date: For an Evaluation license, this field displays the expiration date. For a Permanent license, this field displays a hyphen (-).

◆ Feature Name: The name of the licensed feature.

◆ Install Date: The date the license was installed.

◆ Lic(ense) Type: The type of license.

◆ SymmID: The Symmetrix system to which the license is applied.


Installation

Querying licenses Use the ELM,QUERY,CONTROLLER command to display the current state and usage report for all licenses stored on the Symmetrix system defined by the CONTROLLER field. This usage report is updated only once a day. Any licensing changes since the previous generation of the report will not be included in the ELM,QUERY command output.

Note: The ResourcePak Base for z/OS Product Guide provides more details about this command.

This command is available with z/OS V1R8 and higher. If you are running z/OS V1R7 and lower, you will receive an ELM LIST CONTROLLER report in place of the ELM QUERY CONTROLLER command.

For example, to display the state and usage number for all activated licenses on Symmetrix system 1234, enter the following:

F scftaskname,ELM,QUERY,CNTRL *1234

Example 1 When you issue ELM,QUERY,CONTROLLER from a Symmetrix system with Enginuity level 5876 or higher, a report similar to the following displays the licensed bundles:

SCF0341I ELM QUERY CNTRL(000195600140) SCF5005I Report for (Remote) Controller follows Symmetrix ID : 000195600140 Activation ID: N/A Issue Date : N/A Capacity ------------------------------- Feature Name Act Type Licensed Usage -------------------- ----- ------------- -------- -------- SYMM_VMAX_ENGINUITY MAN R-TB-Non-SATA 0 50.4 R-TB-SATA 0 0.0 SYMM_VMAX_TIMEFINDE MAN REG-TB 0 3.3 SYMM_VMAX_SRDF_REPL MAN REG-TB 0 0.0 SYMM_VMAX_SRDF_STAR MAN REG-TB 0 0.0 SYMM_VMAX_OR_DM MAN R-TB-Non-SATA 0 50.4 R-TB-SATA 0 0.0

Legend: Act(ivation Type): ENT = Entitlement MAN = Manual Override USE = In Use

Example 2 When you issue ELM,QUERY,CONTROLLER from a Symmetrix system with Enginuity level 5875, a report similar to the following displays the individual feature licenses:

SCF0341I ELM,QUERY,CNTRL(00215) SCF5005I Report for (Local) Controller follows Symmetrix ID : 000192600215 Activation ID: 1234567 Issue Date : 9/4/2010 Capacity ------------------------------- Feature Name Act Type Licensed Usage -------------------- ----- ------------- -------- -------- SYMM_ARRAY ENT R-TB-non-SATA 60 50.4 R-TB-SATA 40 0.0 SYMM_TF_CLONE ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_TF_SNAP ENT R-TB-non-SATA 3 50.4


Installation

R-TB-SATA 0 0.0 SYMM_SRDF_S ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_SRDF_A ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_SRDF_STAR ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_DCP R-TB-non-SATA 5 50.4 R-TB-SATA 5 0.0 SYMM_SPC ENT R-TB-non-SATA 5 50.4 R-TB-SATA 4 0.0 SYMM_OPTIMIZER ENT R-TB-non-SATA 5 50.4 R-TB-SATA 0 0.0 SYMM_FAST ENT REG-TB 50 0.0 SYMM_FAST_VP ENT REG-TB 5 0.0 SYMM_SRDF ENT R-TB-non-SATA 3 50.4 R-TB-SATA 0 0.0 SYMM_RP MAN REG-TB 0 0.0 Legend: Act(ivation Type): ENT = Entitlement MAN = Manual Override USE = In Use


The following explains the output for the ELM,QUERY,CONTROLLER command:

◆ Feature Name: The name of the licensed feature.

◆ Act(ivation): How the product title was activated. Possible values are:

• ENT: Indicates that product title was activated through an entitlement.

• MAN: Indicates that the product title was manually activated by EMC.

• USE: Indicates that the product title is activated because it was in use prior to upgrading from Enginuity 5874 to Enginuity 5875.

Product titles activated manually (MAN) or because they were in use (USE) are not considered properly entitled, in which case you should contact EMC for proper entitlement.

◆ Capacity Type: Qualifies the capacity licensed. Possible values are:

• R-TB-Non-SATA: Indicates that the capacity licensed applies to the raw capacity of all devices on the system, excluding SATA.

• R-TB-SATA: Indicates that the capacity licensed applies to the raw capacity of all SATA devices on the system.

• REG-TB: Indicates that the capacity licensed applies to the registered capacity of the Symmetrix system.

◆ Capacity Licensed: The maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

◆ Capacity Usage: The amount Capacity Licensed currently being used.


Installation

Displaying licenses with EzSMThe procedures in this section explain how to use EzSM to display installed licenses. This requires Enginuity 5874 or higher.

Note: For field descriptions of the output examples in this section, refer to “Output field descriptions” on page 44.

To display the current Symmetrix-based licenses activated by a license file, select the following EzSM option:

Symmetrix Device Management > Explore Symmetrix Controllers > Feature Licenses

Select this option to display the available features that have been licensed for this Symmetrix controller. Output similar to the following displays:

To display the usage statistics for each feature license, select the following EzSM option:

Symmetrix Device Management > Explore Symmetrix Controllers > License Usage

Output similar to the following displays:

Function Utilities ------------------------------------------------------------------------------ (X00C-ECHRDELM) Feature Licenses Row 1 to 17 of 24 Command ===> Scroll ===> PAGE === Symmetrix ID=000192600296 Activation ID=1234567 Issue Date= 21 Apr 2027 == _______Capacity________ Expiration_ __Install__ Feature Name Act Type Licensed Date Date SYMM_ARRAY P-IND R-TB-non-SATA 9 - 10 Aug 2010 R-TB-SATA 16 SYMM_TF_CLONE P-IND R-TB-non-SATA 9 - 10 Aug 2010 R-TB-SATA 16 SYMM_TF_SNAP P-IND R-TB-non-SATA 9 - 10 Aug 2010 R-TB-SATA 16 SYMM_SRDF_S P-IND N/A - - 10 Aug 2010 SYMM_SRDF_A P-IND N/A - - 10 Aug 2010 SYMM_SRDF_STAR P-IND R-TB-non-SATA 9 - 10 Aug 2010 R-TB-SATA 16 SYMM_DCP P-IND R-TB-non-SATA 9 - 10 Aug 2010 R-TB-SATA 16 SYMM_SPC P-IND R-TB-non-SATA 9 - 10 Aug 2010 R-TB-SATA 16 SYMM_OPTIMIZER P-IND R-TB-non-SATA 9 - 10 Aug 2010 R-TB-SATA 16 SYMM_FAST P-IND R-TB-non-SATA 9 - 10 Aug 2010

Function Utilities ------------------------------------------------------------------------------ (X00C-ECHRDEL2) License Usage Row 1 to 17 of 24 Command ===> Scroll ===> PAGE === Symmetrix ID=000192600296 Activation ID=1234567 Issue Date= 21 Apr 2027 == ____________Capacity____________ Feature Name Act Type Licensed Usage SYMM_ARRAY N/A R-TB-non-SATA 9 9.3 R-TB-SATA 16 16.0 SYMM_TF_CLONE N/A R-TB-non-SATA 9 9.3 R-TB-SATA 16 16.0 SYMM_TF_SNAP N/A R-TB-non-SATA 9 9.3 R-TB-SATA 16 16.0 SYMM_SRDF_S N/A N/A - - SYMM_SRDF_A N/A N/A - - SYMM_SRDF_STAR N/A R-TB-non-SATA 9 9.3 R-TB-SATA 16 16.0 SYMM_DCP N/A R-TB-non-SATA 9 9.3 R-TB-SATA 16 16.0 SYMM_SPC N/A R-TB-non-SATA 9 9.3 R-TB-SATA 16 16.0 SYMM_OPTIMIZER N/A R-TB-non-SATA 9 9.3 R-TB-SATA 16 16.0 SYMM_FAST N/A R-TB-non-SATA 9 9.3


Installation


◆ Feature name — The name of the licensed feature.

◆ Act(ivation) — Whether the feature was activated through ENT(titlement), because it was already being USE(d) on the mainframe host prior to Enginuity level 5875, or through MANual override.

◆ Capacity — Qualifies the capacity license. Values include:

• Type

– R-TB-Non-SATA — Indicates that the capacity licensed applies to the raw capacity of all the devices on the system, excluding SATA.

– R-TB-SATA — Indicates that the capacity licensed applied to the raw capacity of the SATA devices on the system.

– RG-TB — Indicates that the capacity licensed applies to the registered capacity of the Symmetrix system.

• Capacity License — The maximum quantity of data for which the functionality of the software is licensed to use, in terabytes.

• Capacity Usage — The amount of capacity licensed currently being used.

If the Enginuity (microcode) level of the selected Symmetrix controller is lower than 5874, or if an error occurs retrieving the license information from the controller, an error message is displayed.

Shutting down and restarting ResourcePak Base

After you install the Mainframe Enablers, any available maintenance, and install the LFCs, you need to shut down and restart the latest version of ResourcePak Base (EMCSCF). Take the following steps:

1. If MSC is active, you must shut it down before you can shut down ResourcePak Base. To shut down MSC, enter:

F jobname,MSC,DISABLE

Function Utilities ------------------------------------------------------------------------------(X00C-ECHRSYDM) Symmetrix Serial Number Objects Row 1 to 7 of 7 Command ===> Scroll ===> PAGE ============================================================================== +-------------------------------------------------------------------------+ | Error | | Command ===> Scroll ===> HALF | | EMC z/OS Storage Manager v3.1.0 Copyright (c) EMC Corp., 2010 | | | | ESM9492E ECHRDELM - Bad RC (303) from Call: ECH@FREG Symmetrix | | microcode level does not support feature licenses | | | * | | * | | | | | PF03: Cancel PF07: Up PF08: Down | +-------------------------------------------------------------------------+


Installation

Note: If there is more than one MSC group defined, issue F jobname,MSC,DISABLE,MSCG(*) to shut down MSC.

2. If SRDF/AR (SAR) is active, you must shut it down before you can shut down ResourcePak Base. To shut down SRDF/AR, enter:

F jobname,SAR,STOP,process_name

3. Shut down ResourcePak Base. Enter:

F emcscftaskname,INI,SHUTDOWN

If EMCSCF has not been shut down with INI,SHUTDOWN, or if it failed or otherwise did not shut down properly, then run the SCF global environment cleanup utility SCFUTL01 in the PRODvrm SAMPLIB.

Note: When running the SCFUTL01 utility, use the TERMSCF parameter if the SCF task was shut down with just the P SCFNAME to clean up the persistent API. Use the CLEANSCF parameter if the SCF task ended abnormally.

4. Restart EMCSCF with the new installed SCF library.

Running multiple EMCSCF copiesYou can run multiple instances of EMCSCF (ResourcePak Base) as separate subsystems. You may want to do this when you are testing new versions of EMCSCF or EMCSCF-enabled products.

To run multiple instances of EMCSCF as separate subsystems, add the following DD statement to the EMCSCF test procedure.

//SCF$nnnn DD DUMMY

Where nnnn defines this instance of EMCSCF as a unique z/OS subsystem, and may be any characters permitted in a JCL ddname. The identical DD statement would then be included in the JCL of any task where you want to use this copy of EMCSCF.

For example:

Test version of EMCSCF//EMCSCF EXEC PGM=SCFMAIN,TIME=1440,REGION=0M//STEPLIB DD DISP=SHR,DSN=test.load_library//SCFINI DD DISP=SHR,DSN=init_dataset//SYSABEND DD SYSOUT=*//SCF$0100 DD DUMMY

Any task needing to use this instance of EMCSCF would add the SCF$0100 DD statement. If a version of SRDF Host Component needed to use this version of EMCSCF, the JCL for SRDF Host Component would add the DD statement:

//HCTEST EXEC PGM=EMCSTC//SYSOUT DD SYSOUT=A//SYSIN DD *//SCF$0100 DD DUMMY

CleanupWhen you install the Mainframe Enablers successfully, run the #08CLEAN job to delete datasets and DDDEFS used during the installation process that are no longer needed.


Installation


CHAPTER 3Customization

This chapter describes how to customize and integrate the individual Mainframe Enablers components that you are using.

◆ ResourcePak Base................................................................................................... 48◆ SRDF Host Component ............................................................................................ 48◆ ConGroup ............................................................................................................... 51◆ TimeFinder/Mirror ................................................................................................... 51◆ TimeFinder/Clone Mainframe Snap Facility.............................................................. 52◆ TimeFinder Utility .................................................................................................... 52

Customization 47

Customization

ResourcePak BaseThe following sections describe how to customize ResourcePak Base.

Locating the ResourcePak Base SAMPLIB

All SAMPLIB members for ResourcePak Base are distributed in the PRODvrm SAMPLIB (SMP/E DDNAME: EMCSAMP). The #01ALLOC job (discussed in “Customizing the RIMLIB JCL” on page 23) allocates the SAMPLIB.

Performing customization and integration

Either APF-authorize the ResourcePak Base LINKLIB or copy the related load modules to an APF-authorized library. The library may be specified in the system linklist or copied to a linklist dataset.

The ResourcePak Base for z/OS Product Guide and the SCFINI member provide the information needed to customize the SCF parameters. A sample SCFINI file can be found in EMCSAMP. The startup parameters in this file are displayed as comments to be used as sample parameters. Before using this file, remove the asterisks (*) and edit the parameters to match your configuration.

SRDF Host ComponentThe following sections describe how to customize SRDF Host Component.

Locating the Host Component SAMPLIB

All SAMPLIB members for SRDF Host Component are distributed in PRODvrm SAMPLIB (SMP/E DDNAME: EMCSAMP). The #01ALLOC job (discussed in “Customizing the RIMLIB JCL” on page 23) allocates the SAMPLIB.


To integrate SRDF Host Component into your environment, perform the following steps:

1. Copy the EMCRDF member in PRODvrm SAMPLIB to a PROCLIB.

Note: If you are executing a previous version of SRDF Host Component and do not intend to copy and use the sample procedure EMCRDF in the PRODvrm SAMPLIB, please review the member for changes, such as added, changed, or removed DD and EXEC statements. For example, the EXEC statement now specifies REGION=0M.

2. Add the subsystem name specified on the SUBSYSTEM_NAME initialization parameter to your IEFSSNxx member.

Note: For z/OS, the SRDF Host Component can dynamically add the subsystem. Dynamically adding the subsystem eliminates the need for an IPL before you use the product. However, EMC still recommends that you add the subsystem to the IEFSSNxx member so that after an IPL is done, the dynamic installation is not required.


Customization

3. If you intend to issue EMC TimeFinder/Mirror commands using the Host Component command interface, you must enter the LFCs required to use TimeFinder/Mirror into the ResourcePak Base initialization parameters file.

Implementing SRDF Auto Recovery

SRDF Auto Recovery is installed as part of the base SRDF Host Component product. If the SRDF Automated Recovery feature is to be implemented, perform the following steps to complete the installation:

1. Customize and submit the EHCGLOCK SAMPLIB member to allocate the global lock dataset used by the auto recovery procedure.

See the EDIT instructions in the EHCGLOCK SAMPLIB member.

2. Customize the recovery PROC and copy it to your PROCLIB.

See the EDIT instructions in the EMCRCVRY SAMPLIB member.

3. Specify the SRDF Host Component LOGONLY_FOR_TRACKED_COMMANDS initialization parameter.

When LOGONLY_FOR_TRACKED_COMMANDS is specified, command output for commands entered from the batch and REXX interfaces do not appear in the syslog or system consoles. This output is still returned to the submitter of the command, and will appear in the hclog.

4. Configure the following SRDF Host Component initialization parameters to support SRDF Automated Recovery:

• SRDFA_AUTO_RECOVER

• SRDFA_AUTO_RECOVER_MINDIR

• SRDFA_AUTO_RECOVER_ITRK

• SRDFA_AUTO_RECOVER_BCV

• SRDFA_AUTO_RECOVER_PROC

The SRDF Host Component Product Guide for z/OS describes how to set these parameters.

Implementing command logging

SRDF Host Component logs all commands presented to SRDF Host Component. Commands are logged by writing a copy of the associated EMCMN00E message with:

◆ The date and time of the command at the left.

◆ The console ID and userid appended on the right.

The data and time at the left of each log entry has the format:

mm/dd/yyyy hh.mm.ss

Where:

mm/dd/yyyy indicates the month/day/year

hh.mm.ss indicates the hour.minute.second

SRDF Host Component 49

Customization

If you add an HCLOG= initialization statement, you may request that the responses to those commands also be logged.

To implement logging, add the following DD statement(s) to the SRDF Host Component startup JCL (EMCRDF):

//HCLOG1 DD SYSOUT=class

or

//HCLOG1 DD DISP=SHR,DSN=desired.log.data.set

Note: Refer to member RDFALLOG in the Mainframe Enablers SAMPLIB for an example of JCL to allocate the log files.

SRDF Host Component also writes all initialization statements and any related messages to the log file. If you desire an alternate log file, add either of the following DD statements to the startup JCL:

//HCLOG2 DD SYSOUT=class

or

//HCLOG2 DD DISP=SHR,DSN=desired.log.data.set

These datasets must be in fixed-length format with a record length of 121. Log records exceeding this length are truncated.

Note: The EMC Mainframe Enablers Message and Code Guide describes the SRDF Host Component message formats and meanings.

SRDF Host Component writes to DDname HCLOG1 until the #SC GLOBAL,SWAPLOG command is entered, at which time, commands are logged to DDname HCLOG2. If the log DD statements are not present, command logging is not performed.

When a log is swapped, the existing contents of the new log file are overwritten. For example, you start recording on HCLOG1. When that log file fills up, Host Component automatically switches to HCLOG2.

At some point, you issue a #SC GLOBAL,SWAPLOG command. The effect of this swap log is that the current log (HCLOG2) is closed and the previous log (HCLOG1) is opened for output and its contents are overwritten with the new log.

Note: Log files cannot be shared between multiple systems running SRDF Host Component. When you run SRDF Host Component on multiple z/OS images concurrently, each SRDF Host Component subsystem must have its own log file.


Customization

ConGroupTo integrate ConGroup into your environment, perform the following steps.

Locating the ConGroup SAMPLIB

All SAMPLIB members for ConGroup are distributed in the PRODvrm SAMPLIB (SMP/E DDNAME: EMCSAMP). The #01ALLOC job (discussed in “Customizing the RIMLIB JCL” on page 23) allocates the PRODvrm SAMPLIB.


Conduct all necessary testing.

Implementing ECGTRIP

As described in the EMC Consistency Groups for z/OS Product Guide, ConGroup provides an optional ECGTRIP program. When invoked, the program ECGTRIP requests the trip of a named consistency group.

To install ECGTRIP:

1. Copy the TRIP REXX exec to an appropriate CLIST library.

2. Modify the TRIP REXX exec to point to the load library you chose.

3. Define the resource EMC.CG.API.TRIP (class FACILITY) to RACF, and authorize users to update that resource.

TimeFinder/MirrorTo integrate TimeFinder/Mirror into your environment, perform the following steps.

Locating the TimeFinder/Mirror SAMPLIB

All SAMPLIB members for TimeFinder/Mirror are distributed in the PRODvrm SAMPLIB (SMP/E DDNAME: EMCSAMP). The #01ALLOC job (discussed in “Customizing the RIMLIB JCL” on page 23) allocates the PRODvrm SAMPLIB.



ConGroup 51

Customization

TimeFinder/Clone Mainframe Snap FacilityTo integrate TimeFinder/Mirror into your environment, perform the following steps.

Locating the TimeFinder/Clone Mainframe Snap Facility SAMPLIB

All SAMPLIB members for TimeFinder/Clone Mainframe Snap Facility are distributed in the PRODvrm SAMPLIB (SMP/E DDNAME: EMCSAMP). The #01ALLOC job (discussed in “Customizing the RIMLIB JCL” on page 23) allocates the PRODvrm SAMPLIB.



TimeFinder UtilityEdit the sample JCL supplied in the PRODvrm SAMPLIB members TFSAMP04 and TFSAMP05.

Customizing the REXX interfaceThe following sections describe how to customize the REXX interface for the Mainframe Enablers products.

If the following programs do not reside in an authorized library, then complete the steps below to set up your REXX interface environment:

◆ EMCTF (TimeFinder/Mirror)◆ EMCTFU (TimeFinder Utility)◆ EMCSNAP (TimeFinder/Clone Mainframe Snap Facility)◆ EMCTFA (SRDF/AR)◆ EMCGROUP (Group Name Services)◆ EMCQOS (Quality of Service)◆ SCFRDFME (MSC Star)◆ EHCMSCME (MSC Star)◆ EHCGCOPY (MSC Star)◆ EHCRCVRY (MSC Star)◆ ECORAFIF (MSC Star)◆ SCFRDFM6 (MSC Star)◆ EHCMSCM6 (MSC Star)

1. Update the IKJTSOxx member in the SYS1.PARMLIB by adding the following program names to AUTHPGM NAMES, AUTHTSF NAMES and AUTHCMD NAMES statements:

• EMCTF• EMCTFU• EMCSNAP• EMCTFA• EMCGROUP• EMCQOS• SCFRDFME


Customization

• EHCMSCME• EHCGCOPY• EHCRCVRY• ECORAFIF• SCFRDFM6• EHCMSCM6

2. For these changes to take effect, perform one of the following:

• Use the “PARMLIB” TSO authorize command to dynamically change the IKJTSOxx active member without an IPL.1

or

• IPL your system.

AUTHPGM NAMES( /* AUTHORIZED PROGRAMS */+EMCTF /* TF INTERFACE */+EMCTFU /* TF INTERFACE */+EMCSNAP /* TF INTERFACE */+EMCTFA /* TF INTERFACE

SCFRDFME /* MSC CLEANUP */ +EHCMSCME /* MSC CLEANUP */ +EHCGCOPY /* MSC CLEANUP - GOLD COPY */ +EHCRCVRY /* MSC CLEANUP - RECOVERY */ +EC0RAFIF /* MSC CLEANUP - REXX */ +EHCMSCM6 /* MSC CLEARBOX */)

/* */

AUTHTSF NAMES( /* PROGRAMS TO BE AUTHORIZED */+/* WHEN CALLED THROUGH THE */+/* TSO SERVICE FACILITY. */+EMCTF /* TF INTERFACE */+EMCTFU /* TF INTERFACE */+EMCSNAP /* TF INTERFACE */+EMCTFA /* TF INTERFACE */)

AUTHCMD NAMES( /* AUTHORIZED PROGRAMS */+SCFRDFME /* MSC CLEANUP */ +EHCMSCME /* MSC CLEANUP */ +EHCGCOPY /* MSC CLEANUP G COPY */ +EHCRCVRY /* MSC CLEANUP */ +EC0RAFIF /* MSC CLEANUP */ +EHCMSCM6 /* MSC CLEARBOX */ )

Note: The AUTHCMD NAMES entries allow you to execute MSC Auto Recovery procedures.

SRDF Host Component

To set up your REXX interface environment for SRDF Host Component, perform the following steps:

1. Copy the following REXX interface load modules from the target library to an installation LINKLIST library:

• EMCSRDFR• SRDFDASD

1. It is recommended that you examine PARMLIB CHECK(xx) (where xx is the member name suffix) to ensure that there are no syntax errors.

Customizing the REXX interface 53

Customization

• SAISRDF

Note: The EMCSRDFR, SRDFDASD, and SAISRDF modules must reside in an authorized LINKLIST library because they are called through the TSO/E Service Facility Routine IKJESTSR.

2. Remove any older version of the Host Component REXX interface (if installed) by performing the following steps:

Note: Do the following tasks as part of the installation of the REXX interface.

a. Delete the following modules from the LINKLIST dataset:

– SRDFDCNS– SRDFDEAC– SRDFESTA– SRDFISPI– SRDFISSS– SRDFTMCS

b. In the IKJTSOnn member of PARMLIB, remove the following from the AUTHTSF name list:

– SRDFDCNS– SRDFTMCS– SRDFDEAC


CHAPTER 4EMCSAFI Security Interface

This chapter describes the EMCSAFI security interface and discusses how to enable, disable, and customize the interface.

◆ Overview................................................................................................................. 56◆ Class names and resource names used ................................................................... 56◆ Disabling the security interface ............................................................................... 67◆ Customizing the security interface........................................................................... 68◆ Restoring the EMC-supplied SAF interface................................................................ 75

EMCSAFI Security Interface 55

EMCSAFI Security Interface

OverviewTo use resources, the EMCSAFI security interface uses z/OS SAF calls (RACROUTE) to request authorization. The input to this program is the EMCSAFRB request block. EMCSAFRB describes the authorization.

EMCSAFI requires that RACF version 1.9 or higher, or an equivalent SAF-compliant security product be installed and activated. The security interface is active by default. If you choose not to use the security interface, “Disabling the security interface” on page 67 describes how to disable it.

Note: When running with the security interface active, check with your security administrator to make sure that the proper classes are active and the proper resources are defined. The class and resource names used by the EMCSAFI security interface are described in “Class names and resource names used” on page 56.

Class names and resource names usedThe following sections describe the class and resource names for the individual Mainframe Enablers.

IMPORTANT

Be aware that the EMCSAFI security interface is affected by changes to some of the defaults for a dynamically defined CDT class. This causes resource classes that are dynamically defined to act differently than if they were created with the ICHERCDE macro. Review the resource names regarding the default values for special characters.

ResourcePak Base class and resource names

The following sections describe the resource names used by ResourcePak Base.

XFACILIT class and resource namesTable 9 lists the resource validation requests for the ResourcePak Base environment commands.



Update authority to these resources is required to issue commands. If the resource profile is not present, all users will be allowed to issue the commands.

Table 9 ResourcePak Base resource validation requests with XFACILIT (page 1 of 3)

Command environment Function Class Resource name Attribute

ASY DISABLEENABLEREFRESHSSAR

EMC.ADMIN.CMD.ASY

AUTOSWAP DEFINEVALIDATESWAPDELETESETSETSWAPDISPLAY

XFACILIT EMC.ADMIN.CMD.AUTOSWAP

UpdateUpdateUpdateUpdateUpdateUpdateRead

DSE DISABLEENABLEREFRESH

XFACILIT EMC.ADMIN.CMD.DSE Update

FLS CLEANUPQUIESCESTART/ENABLESTOP/DISABLE

XFACILIT EMC.ADMIN.CMD.FLS Update

GPM ADDALLOCATEBINDCREATECOMPRESSDECOMPRESSDELETEDISABLEDISPLAYDRAINENABLEHALTTASTHDRAINMOVEPERSIST OFFPOOLATTRREBALANCEREBINDREMOVERENAMEUNBINDUSR_NRDYUSR_RDY

XFACILIT EMC.ADMIN.CMD.GPM Update

Note: Only QUERY GPM command is not RACF-protected. DISPLAY GPM command is RACF-protected.

Class names and resource names used 57


INI RELOADSHUTDOWNCSTOP

XFACILIT EMC.ADMIN.CMD.INI Update

MSC ADDDEVDEACTDEACTREFRESHDEACTRESTARTDEACTRESTARTTOSECDEACTRESTARTTOZERODELDEVDISABLEENABLEPENDDROPRECOVERREFRESHRESTARTRESTARTTOSECRESTARTTOZEROTAKEOVERVERBOSE

XFACILIT EMC.ADMIN.CMD.MSC Update

REC RELDLOCK EMC.ADMIN.CMD.REC

REG COMPOSITEDETAILDISABLEENABLEHELPLISTGRP=applicationLOADMOD=moduleREFRESHSUMMARY

XFACILIT EMC.ADMIN.CMD.REG Update

Note: These REG commands are protected when issued as SSCF commands; the batch interface method is not RACF-protected. The DISPLAY and QUERY REG commands are not RACF-protected.

SAR MODIFYPAUSERESTARTSTARTSTOP

XFACILIT EMC.ADMIN.CMD.SAR Update

SDV DISABLEENABLEREFRESH

XFACILIT EMC.ADMIN.CMD.SDV Update





Controller naming security with XFACILITResourcePak Base allows you to assign a name to an EMC controller. SAF security for the controller name feature uses the XFACILIT general resource class. The resource name is:

EMC.ADMIN.SCF.CTRL.nnnnnnnnnnnn

Where

nnnnnnnnnnnn

Indicates the 12-character controller serial number. Update authority to this resource is required to assign a name to a controller. If the profile for the resource is not present, then all users will be allowed to assign names to controllers.

QOS Utility class and resource namesWith the Mainframe Enablers Version 7.0 and higher, QOS also supports the use of the XFACILIT class. EMC recommends that XFACILIT be used for new installations. Table 10 summarizes the resource validation requests for each ResourcePak Base QOS Utility feature and function with XFACILIT.

The QS#BASE class remains available for compatibility reasons.

THN DISABLEENABLEREFRESH

EMC.ADMIN.CMD.THN

TRU HOLD RECLAIM REFRESH RELEASESCAN START STOP

XFACILIT EMC.ADMIN.CMD.TRU Update



Table 10 EMCQOS resource validation requests with XFACILIT

Function Class Resource name Attribute

QOS Symmetrix Priority Control XFACILIT EMC.ADMIN.CMD.QOS-SPC Read

QOS Dynamic Cache Partitioning XFACILIT EMC.ADMIN.CMD.QOS-DCP Read

Table 11 EMCQOS resource validation requests with QS#BASE


QOS Symmetrix Priority Control QS#BASE QOS-SPC Read

QOS Dynamic Cache Partitioning QS#BASE QOS-DCP Read



SRDF Host Component class and resource names

To set SRDF Host Component class and resource names, use the SRDF Host Component initialization parameters:

◆ SAF_CLASS

◆ SAF_PROFILE

SAF_CLASSYou can specify the SAF class name with the SAF_CLASS initialization parameter. The SAF class name is used to validate access to the SRDF Host Component commands.

The format is:

SAF_CLASS=SAF class name

Where:

SAF class name

Specifies the SAF class name (from 1 through 8 characters). If you do not specify SAF_CLASS, the SAF_CLASS parameter defaults to a class name of DATASET.

If you set SAF_CLASS or allow it to default to DATASET, you must define the resource as a generic dataset profile. Generic dataset checking must be active.

SAF_PROFILE

You can specify the resource name to be used for SAF validation calls using the SAF_PROFILE initialization parameter. The resource name can be from 1 through 44 characters.

The format is:

SAF_PROFILE=EMC.VALIDATE.ACCESS[,APPEND_COMMAND=YES]

Where:

EMC.VALIDATE.ACCESS

Specifies that access must be validated. If you do not specify this parameter, SAF_PROFILE defaults to a resource name of EMC.VALIDATE.ACCESS.

APPEND_COMMAND=YES

For more granularity in RACF validations, you can specify an optional APPEND_COMMAND=YES subparameter. This option allows you to have a security check about an SRDF Host Component command that you entered. If you choose this option, any SRDF Host Component command you enter is appended to your SAF profile resource name.

Note: The resource name is limited to 35 characters in length when using the APPEND_COMMAND=YES subparameter.



More informationChapter 3 in the SRDF Host Component for z/OS Product Guide describes how to set these parameters and provides a table of SRDF Host Component commands that are returned, along with their corresponding suffixes, when you issue a command with the APPEND_COMMAND option specified for the SAR_PROFILE parameter.

AutoSwap class and resource names

Table 13 summarizes the resource validation requests for each AutoSwap feature and function.

Message ESWP633I indicates the status of resource checking.

ConGroup class and resource names

Table 13 summarizes the resource validation requests for each ConGroup feature and function.

Note: DATASET is the default SAF class and EMC VALIDATE.ACCESS is the default SAF profile. You can localize both in the ConGroup global initialization parameters.

Table 12 AutoSwap resource validation requests


DEFINE DELETE SET SETSWAP SWAP VALIDATE

XFACILIT EMC.ADMIN.CMD.AUTOSWAP Update

DISPLAY XFACILIT EMC.ADMIN.CMD.AUTOSWAP Read

Table 13 ConGroup resource validation requests (page 1 of 2)


ADD/DELETE devices FACILITY EMC.CG.API.ADDDEL Update

CANCEL DATASET EMC.VALIDATE.ACCESS.CGMANAGE Update

DISABLE DATASET EMC.VALIDATE.ACCESS.CGMANAGE Update

DISPLAY CGROUP DATASET EMC.VALIDATE.ACCESS.CGDISP Read

DISPLAY CONGROUP DATASET EMC.VALIDATE.ACCESS.CGDISP Read

DISPLAY DEBUG DATASET EMC.VALIDATE.ACCESS.CGDISP Read

ENABLE DATASET EMC.VALIDATE.ACCESS.CGMANAGE Update

MOVEOWNER DATASET EMC.VALIDATE.ACCESS.CGREFR Update

REFRESH DATASET EMC.VALIDATE.ACCESS.CGREFR Update

REMSPLIT DATASET EMC.VALIDATE.ACCESS.CGMANAGE Update



TimeFinder/Clone Mainframe Snap Facility class and resource names

Table 14 summarizes the basic resource validation requests for each TimeFinder/Clone Mainframe Snap Facility feature and function.

RESUME DATASET EMC.VALIDATE.ACCESS.CGMANAGE Update

Run CLEAN utility FACILITY EMC.UTL.ECGUTIL Update

Run TRIP API FACILITY EMC.CG.API.TRIP Update

STOP DATASET EMC.VALIDATE.ACCESS.CGSTOP Update

TAKEOVER DATASET EMC.VALIDATE.ACCESS.CGREFR Update

Table 13 ConGroup resource validation requests (page 2 of 2)


Table 14 TimeFinder/Clone Snap Facility resource validation requests

Function Class Resource name Attribute Dstyp Volser

Snap volume DASDVOL Old-volser Read

DASDVOL New-volser Alter

Snap dataset DATASET Old-dsname Read N or V Volser

Normal z/OS security processing is performed for output dataset.



Enhanced TimeFinder/Clone Mainframe Snap Facility securityTimeFinder/Clone Mainframe Snap Facility includes enhanced security for:

◆ Devices

◆ Groups

◆ Pools

◆ Commands

Device securityThe EMCSAFI security interface supplies additional security checks for environments where multiple groups of users are using different devices in a single controller. These security checks are provided through the SYMDV# parameter. When you use SYMDV#, TimeFinder/Clone Mainframe Snap Facility now checks to ensure that devices are logically only available to an authorized user.

For example, if you specify VDEV(FREE) within TimeFinder/Clone Mainframe Snap Facility the software now supports a check that a device assigned is logically accessible for a particular user. Or, if a SNAP VOLUME occurs, TimeFinder/Clone Mainframe Snap Facility checks to make sure both the source and target devices are logically accessible only to a particular user.

To implement this check at the Symmetrix device number level, the SAF checking provided by ResourcePak Base supports the XFACILIT resource name.

The requested access authority is READ for source devices and UPDATE for target devices. The format of the SAF request is as follows:

EMC.DEVC.12digitserialnumber.ssid.dev#

Where:

12-digitserialnumber

Specifies the 12-digit Symmetrix controller ID.

ssid

Specifies the subsystem ID.

dev#

Specifies the internal Symmetrix device number. This must be a 4-digit value.

Example The following example identifies a Symmetrix system with serial number 000000006185. The SSID is 0C02, and the specific internal device number is 0230.

EMC.DEVC.000000006185.0C02.0230

You can use an asterisk (*) wildcard character to specify more than a specific internal device number. For example, the following statement protects an entire SSID:

EMC.DEVC.000000006185.0C02.*

The following wildcard protects the entire controller:

EMC.DEVC.000000006185.*



GROUP securityYou may control who may modify, display, and use groups with the XFACILIT resource class. The requested authority for all commands that reference a group is READ. The requested authority for commands that define or delete groups is UPDATE. The format for the SAF resource name is:

EMC.ADMIN.GROUP.EMCSNAP.grpname

Where:

grpname

Specifies the group name.

Pool securityYou may control who may modify, display, and use pools through the XFACILIT resource class. The requested authority for all commands that reference a pool is READ. The quested authority for all CONFIGPOOL commands is UPDATE. The format for the SAF resource name is:

EMC.ADMIN.POOL.EMCSNAP.poolname

Where:

poolname

Specifies the pool name.

Note: The ResourcePak Base for z/OS Product Guide provides more information about the CONFIGPOOL commands.

Command securityYou may also control who can issue commands through the XFACILIT resource class. The requested authority for all commands is READ. Table 15 shows the format for the SAF resources.

Table 15 Command resources with XFACILIT (page 1 of 2)

Command Resource

ACTIVATE EMC.ADMIN.CMD.EMCSNAP.ACTIVATE

CLEANUP EMC.ADMIN.CMD.EMCSNAP.CLEANUP

CONFIG EMC.ADMIN.CMD.EMCSNAP.CONFIG

CONFIGPOOL ADD EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.ADD

CONFIGPOOL CREATE EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.CREATE

CONFIGPOOL DELETE EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.DELETE

CONFIGPOOL DISABLE EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.DISABLE

CONFIGPOOL DISPLAY EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.DISPLAY

CONFIGPOOL DRAIN EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.DRAIN

CONFIGPOOL ENABLE EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.ENABLE



TimeFinder/Mirror class and resource names

TimeFinder/Mirror supports the use of the XFACILIT class. EMC recommends that XFACILIT be used for new installations.

Table 16 summarizes the resource validation requests for each TimeFinder/Mirror (EMCTF) features and functions with XFACILIT.

CONFIGPOOL REMOVE EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.REMOVE

CONFIGPOOL UNDRAIN EMC.ADMIN.CMD.EMCSNAP.CONFIGPL.UNDRAIN

DEBUG DATASET EMC.ADMIN.CMD.EMCSNAP.DEBUG.DATASET

DEFINE GROUP EMC.ADMIN.CMD.EMCSNAP.GROUP.DEFINE

DEFINE SOURCE_VOLUME_LIST EMC.ADMIN.CMD.EMCSNAP.DEFINE.SRCLIST

DELETE GROUP EMC.ADMIN.CMD.EMCSNAP.GROUP.DELETE

END GROUP EMC.ADMIN.CMD.EMCSNAP.GROUP.END

GLOBAL EMC.ADMIN.CMD.EMCSNAP.GLOBAL

Perform a group operation EMC.ADMIN.CMD.EMCSNAP.GROUP

QUERY DATASET EMC.ADMIN.CMD.EMCSNAP.QUERY.DATASET

QUERY GLOBAL EMC.ADMIN.CMD.EMCSNAP.QUERY.GLOBAL

QUERY GROUP EMC.ADMIN.CMD.EMCSNAP.QUERY.GROUP

QUERY SNAPPOOL EMC.ADMIN.CMD.EMCSNAP.QUERY.SNAPPOOL

QUERY VDEV EMC.ADMIN.CMD.EMCSNAP.QUERY.VDEV

QUERY VOLUME EMC.ADMIN.CMD.EMCSNAP.QUERY.VOLUME

RESET EMC.ADMIN.CMD.EMCSNAP.RESET

RESTORE EMC.ADMIN.CMD.EMCSNAP.RESTORE

SNAP DATASET EMC.ADMIN.CMD.EMCSNAP.SNAP.DATASET

SNAP VOLUME EMC.ADMIN.CMD.EMCSNAP.SNAP.VOLUME

STOP SNAP TO DATASET EMC.ADMIN.CMD.EMCSNAP.STOP.DATASET

STOP SNAP TO VOLUME EMC.ADMIN.CMD.EMCSNAP.STOP.VOLUME

Table 15 Command resources with XFACILIT (page 2 of 2)

Command Resource

Table 16 TimeFinder/Mirror resource validation requests with XFACILIT (page 1 of 2)


Query XFACILIT EMC.ADMIN.CMD.TF.QUERY Read

Establish XFACILIT EMC.ADMIN.CMD.TF.ESTABLISH Update

Re-establish XFACILIT EMC.ADMIN.CMD.TF.RE-ESTABLISH Update

Split XFACILIT EMC.ADMIN.CMD.TF.SPLIT Update



CLASS TF#BASE remains available for compatibility reasons. Table 17 summarizes the resource validation requests for each TimeFinder/Mirror (EMCTF) feature and function with TF#BASE.

Restore (incremental) XFACILIT EMC.ADMIN.CMD.TF.PARTIAL-RESTORE Update

Restore (incremental) XFACILIT EMC.ADMIN.CMD.TF.PARTIAL-RESTORE-BYPASS-WTOR Update

Restore (full) XFACILIT EMC.ADMIN.CMD.TF.FULL-RESTORE-NOVERIFY Update

Restore (full) XFACILIT EMC.ADMIN.CMD.TF.FULL-RESTORE-BYPASS-WTOR Update

Config XFACILIT EMC.ADMIN.CMD.TF.CONFIG Update

SRDF/AR ADD XFACILIT EMC.ADMIN.CMD.TF.SAR-ADD Update

SRDF/AR DELETE XFACILIT EMC.ADMIN.CMD.TF.SAR-DELETE Update

SRDF/AR START XFACILIT EMC.ADMIN.CMD.TF.SAR-START Update

SRDF/AR STOP XFACILIT EMC.ADMIN.CMD.TF.SAR-STOP Update

SRDF/AR MODIFY XFACILIT EMC.ADMIN.CMD.TF.SAR-SMODIFY Update

All Functions XFACILIT EMC.ADMIN.CMD.TF.BYPASS-ONLINE-CHECK Update

Table 16 TimeFinder/Mirror resource validation requests with XFACILIT (page 2 of 2)


Table 17 TimeFinder/Mirror resource validation requests with TF#BASE

Function Class Resource Attribute

Query TF#BASE QUERY Read

Establish TF#BASE ESTABLISH Read

Re-establish TF#BASE RE-ESTABLISH Read

Split TF#BASE SPLIT Read

Restore (incremental) TF#BASE PARTIAL-RESTORE Read

Restore (incremental) TF#BASE PARTIAL-RESTORE-BYPASS-WTOR Read

Restore (full) Noverify TF#BASE FULL-RESTORE-NOVERIFY Read

Restore (full) BYPASS WTOR

TF#BASE FULL-RESTORE-BYPASS-WTOR Read

Config TF#BASE CONFIG Read

SRDF/AR ADD TF#BASE SAR-ADD Read

SRDF/AR DELETE TF#BASE SAR-DELETE Read

SRDF/AR START TF#BASE SAR-START Read

SRDF/AR STOP TF#BASE SAR-STOP Read

SRDF/AR MODIFY TF#BASE SAR-MODIFY Read

All Functions TF#BASE BYPASS-ONLINE-CHECK Read



TimeFinder Utility class and resource names

Table 18 summarizes the resource validation requests for each TimeFinder Utility (EMCTFU) features and functions.

Disabling the security interfaceMember EMCSAFD in the Mainframe Enablers SAMPLIB contains assembler source code that you can use to disable the EMCSAFI security interface. Use member #90SAFJB in Mainframe Enablers RIMLIB to assemble and link the modules.

Note: #90SAFJB assembles the EMCSAFD exit and links it to all products. If the SAF interface is to be disabled in selected products, the link edit control statements will have to be removed for the products that will still use the SAF security process. (See the instructions included with #90SAFJB in the RIMLIB library.)

This source replaces CSECT EMCSAFI with a routine that returns a return code of zero (0) or four (4), depending on the content in RNAME_TBL. Entries in RNAME_TBL returns four. No attempt to call RACF is made and the following message is placed in ESRBMSG:

EMC SAF INTERFACE IS DISABLED

Note: The ESRBMSG message field is part of the EMCAFRB structure. Refer to the ESRBMSG area for messages related to the EMCSAFT routine.

Disabling the EMC SAF interface

To disable the EMC SAF interface for any of the Mainframe Enablers:

1. Read the instructions in the #90SAFJB to ensure that the SAF security process will be disabled in the intended products.

2. Change the JCL to conform to your installation standards.

3. Run the job.

This relinks the component program.

Table 18 TimeFinder Utility resource validation requests

Function Class Resource name Attribute Dstyp Volser

Relabel Vol DASDVOL Old-volser Alter

DASDVOL New-volser Alter

Rename nvsam DATASET Old-dsname Alter N Volser

DATASET New-dsname Alter N Volser

Rename cluster DATASET Old-dsname Alter V Old cat vol

DATASET New-dsname Alter V New cat vol

Rename path DATASET Old-pathname Alter V Old cat vol

DATASET New-pathname Alter V New cat vol

Disabling the security interface 67


The sample EMCSAFD (Figure 3 on page 68) includes MNOTE statements to identify RNAME_TBL table. Refer to Figure 3 on page 68. After reviewing this code, comment the MNOTE statements.

Figure 3 Sample EMCSAFD

Customizing the security interfaceThe following sections describe how to customize the security interface.

Member EMCSAFI in the Mainframe Enablers SAMPLIB contains assembler source code for the security interface. The source code included in the Mainframe Enablers SAMPLIB is the code linked with the other mainframe components. This source is provided to allow you to customize the behavior of the security code to match your installation requirements.

Use member #90SAFJB in the Mainframe Enablers RIMLIB to assemble and link the modules, making sure to change all occurrences of literal *SAFMBR* to EMCSAFI.

IMPORTANT

Be aware that the EMCSAFI security interface is affected by changes to some of the defaults for a dynamically-defined CDT class. This causes resource classes that are dynamically defined to act differently than if they were created with the ICHERCDE macro. Review the resource names regarding the default values for special characters.

Customizing EMCSAFI

To customize the interface:


2. Change the source for EMCSAFI to suit your needs.

3. Run the job.

This relinks the component.

*** IF THE SUPPLIED RESOURCE NAME MATCHES AN ENTRY IN THE RNAME_TBL,* RETURN WITH RC 4.** MNOTE 12,'*-------------------------------------------------*' MNOTE 12,'* Please review the new functionality added with *' MNOTE 12,'* the RNAME_TBL. A rc 4 will be returned for *' MNOTE 12,'* each resource name in the table, allowing for *' MNOTE 12,'* protection of these functions when a full SAF *' MNOTE 12,'* interface is not desired. *' MNOTE 12,'* *' MNOTE 12,'* To run without this enhancement, replace the *' MNOTE 12,'* first character of the first entry in the table *' MNOTE 12,'* with a hex FF. *' MNOTE 12,'* *' MNOTE 12,'* Before submitting this module for assembly, *' MNOTE 12,'* delete or comment these MNOTE statements. *' MNOTE 12,'*-------------------------------------------------*' LA R2,RNAME_TBL PRIME POINTER TO RNAME TBL



Note: Customization of the EMCSAFI routine should only be attempted by experienced systems programmers who have extensive knowledge of assembler language and standard linkage conventions, and who understand the RACF RACROUTE interface. Normal precautions must be taken to test changes in an isolated environment, and to protect working production code.

On entry to EMCSAFI, R1 points to a full word containing the address of the EMCSAFRB. The information in this request block is used to build a RACROUTE request.

On return, R15 contains one of the following return codes:

Note: Take care when customizing EMCSAFI to maintain re-entrancy.

Return code zeroIf the return code is zero, then field ESRBMSG contains one of the messages shown in Table 19.

0 For ESRBATTR T: Security subsystem is active.For ESRBATTR T: Access is allowed.

8 Access is denied.

12 EMCSAFRB failed validation.

16 RACF is not active.

Table 19 EMCSAFI routine: Return code zero

Message Description

ACCESS ALLOWED Access to the requested resource is allowed.

ACCESS ALLOWED - (WARN MODE)

Access to the requested resource would have been denied; however, warn mode is in effect, so access is allowed.

ACCESS ALLOWED - CLASS NOT ACTIVE

The requested class is not defined, and PROTECT ALL is not in effect.

ACCESS ALLOWED - RESOURCE NOT PROTECTED

The requested resource is not defined, and PROTECT ALL is not in effect.

SECURITY SUBSYSTEM IS ACTIVE The request was to determine if the security subsystem is active and it is.

Customizing the security interface 69


Return code non-zeroIf the return code is non-zero, then field ESRBMSG contains one of the messages shown in Table 20.

Customizing EMCSAFRB

The EMCSAFRB macro describes the resource access request and is built by the caller and passed to the EMCSAFI routine. The macro is included in the Mainframe Enablers SAMPLIB, and is also shown in Figure 4 on page 72.

XFACILIT class name

When the class name is XFACILIT, the following statements are true:

◆ The ESRBP1 contains two halfword values. The first halfword is the SSID of the device. The second halfword is the SYMDV# of the device.

◆ There are situations where the first halfword may be zero because internal processing has not yet progressed to the point of determining the SSID.

Table 20 EMCSAFI routine: Return code non-zero

Message Description

ACCESS DENIED The security subsystem has denied access to the resource. Contact your security administrator for proper access.

SECURITY SUBSYSTEM IS NOT ACTIVE

The security subsystem is not running. Start the security subsystem or run job EMCSAFD from the SCF SAMPLIB to disable the security feature.

EMCSAFRB ERROR - CLASS NOT SPECIFIED

The EMCSAFRB control structure passed to the security interface is in error. Field ESRBCLAS is not filled in. If you have customized the SAF interface, review your changes for errors. If you have not customized the SAF interface, contact the EMC Customer Support Center for technical assistance.

EMCSAFRB ERROR - INVALID AUTHORITY LEVEL REQUESTED

The EMCSAFRB control structure passed to the security interface is in error. Field ESRBATTR has an invalid value. If you have customized the SAF interface, review your changes for errors. If you have not customized the SAF interface, contact the EMC Customer Support Center for technical assistance.

EMCSAFRB ERROR - RESOURCE NAME NOT SPECIFIED

The EMCSAFRB control structure passed to the security interface is in error. Field ESRBRNAM is not filled in. If you have customized the SAF interface, review your changes for errors. If you have not customized the SAF interface, contact the EMC Customer Support Center for technical assistance.

EMCSAFRB ERROR - INVALID DSTYPE VALUE SPECIFIED

The EMCSAFRB control structure passed to the security interface is in error. Field ESRBDSTY has an invalid value. If you have customized the SAF interface, review your changes for errors. If you have not customized the SAF interface, contact the EMC Customer Support Center for technical assistance.

EMCSAFRB ERROR - DSTYPE IS NOT M AND VOLSER NOT SPECIFIED

The EMCSAFRB control structure passed to the security interface is in error. Field ESRBDSTY has an invalid value. The value is not M, and field ESRBVSER is not filled in. If you have customized the SAF interface, review your changes for errors. If you have not customized the SAF interface, contact the EMC Customer Support Center for technical assistance.



Depending on the action specified, some fields may not be filled in. These fields can be used to customize the security exit.

QS#BASE class name

When the class name is QS#BASE, the following statements are true:

◆ The ESRBP1 contains the cuur in the first halfword and cuus in the second halfword.

◆ The ESRBP2 contains the Primary Symmetrix device number in the first halfword and the Secondary Symmetrix device number in the second halfword.

Depending on the action specified, some fields may not be filled in. You can use these unused fields to customize the security exit.

DATASET class name (ConGroup)

When the class name is DATASET (or the class name specified in the initialization of ConGroup), the following are true:

Depending on the action specified, some fields may not be filled in. You can use these fields to customize the security exit.

DATASET class name (SRDF Host Component)

When the class name is DATASET, the following statements are true:

◆ The ESRBP1 contains the cuup in the first halfword and cuus in the second halfword.



TF#BASE class name

When the class name is TF#BASE, the following statements are true:

◆ The ESRBP1 contains the cuur in the first halfword and cuus in the second halfword.



ESRBCLAS Set the class name (QNAME).

ESBRNAM Set to the resource name (RNAME).

ESRBATTR U (update) or R (read).

ESRBUTOK Security token supplied in the CIB representing the operator command.

ESRBDSTY M (model profile).

ESRBUID Set to spaces.

ESRBGID Set to spaces.



The EMCSAFRB macro

Figure 4 on the following pages shows a sample EMCSAFRB macro.

Figure 4 EMCSAFRB macro

MACRO.**********************************************************************.* *.* EMCSAFRB *.* *.* STRUCTURE PASSED AS INPUT TO THE EMCSAFI SECURITY INTERFACE *.* ROUTINE. *.* *.*--------------------------------------------------------------------*.* CHANGE LOG: *.* *.* 02/09/08 BASE *.* 09/28/08 ADD OPTIONAL PARMS *.* *.********************************************************************** EMCSAFRBEMCSAFRB DSECT************************************************************************* AUTHORITY LEVEL ************************************************************************ESRBATTR DS CL1 REQUEST AUTHORITY LEVEL* T - TEST RACF ACTIVE* R - READ* U - UPDATE* A - ALTER* C - CONTROL DS CL3 .. OPEN ..************************************************************************ REQUESTOR INFORMATION ************************************************************************** SET ESRBUID AND ESRBGID TO BLANK UNLESS 3RD PARTY AUTHORIZATION* CHECKING IS TO BE USED*ESRBUID DS CL8 USERID OR BLANKESRBGID DS CL8 GROUPID OR BLANKESRBACEE DS A | 0 OR ADDR OF ACEE OR 4X'FF'* | IF ESRBUTOK POINTS TO UTOKEN*



Figure 4 (continued) EMCSAFRB macro

Tables 21 through 24 describe the fields in the EMCSAFRB structure.

************************************************************************ RESOURCE INFORMATION ************************************************************************ESRBCLAS DS CL8 RESOURCE CLASSESRBRNAM DS CL44 RESOURCE NAMEESRBVSER DS CL6 VOLSER (IF CLASS=DATASET)ESRBDSTY DS CL1 DSTYPE: (IF CLASS=DATASET)* N - NONVSAM* V - VSAM* M - MODEL PROFILE* T - TAPE DS CL5 | .. OPEN ..************************************************************************ RETURN CODES ************************************************************************ESRBR15 DS F RETURN CODE FROM RACROUTEESRBRRET DS F RACF RETURN CODEESRBRREA DS F RACF REASON CODEESRBSRET DS F SAF RETURN CODEESRBSREA DS F SAF REASON CODE************************************************************************ ERROR MESSAGE ************************************************************************ESRBMSG DS CL100 AREA FOR MESSAGE RETURN************************************************************************ REUSE ERROR MESSAGE AREA FOR ADDITIONAL PARAMETERS. NOTE THAT ** THESE PARAMETERS WILL BE OVERLAYED ON RETURN FROM EMCSAFI. ************************************************************************ ORG ESRBMSG |ESRBP1 DS XL4 | OPTIONAL PARAMTERS PASSEDESRBP2 DS XL4 | . BY APPLICATIONESRBP3 DS XL4 | . . .ESRBP4 DS XL4 | . . .ESRBUTOK DS XL4 | A(USER TOKEN) ORG ESRBMSG+L'ESRBMSG |EMCSAFRL EQU *-EMCSAFRB AREA LENGTH MEND

Table 21 Authority level

ESRBATTR 1 byte field describing the level of access required. Valid values are: • T - tests whether the security interface is active. A

return code of zero indicates that it is active, a non-zero return code indicates that it is not active.

• R - requests READ access to the resource. • U - requests UPDATE access to the resource. • A - requests ALTER access to the resource. • C - requests CONTROL access to the resource.



Note: The RACROUTE, RACF, and SAF return codes and reason codes are documented in the IBM publication, External Security Interface (RACROUTE) Macro Reference for MVS and VM, or, in later releases, SecureWay Security Server RACROUTE Macro Reference.

Table 22 Requestor information

ESRBUID 8 byte field containing the userid of the user requesting access. If ESRBACEE is specified, this field is ignored.

ESRBGID 8 byte field containing the groupid of the user requesting access. If this field is blank and the ESRBUID field is specified, the default group for the userid is used. If ESRBUID is blank or ignored, then this field is ignored.

ESRBACEE 8 byte field containing the address of a valid ACEE for the user requesting access. If this field is zero and ESRBUID is blank, the ACEE associated with the current address space is used.

Table 23 Resource information

ESRBCLAS 8 byte field containing the class name.

ESRBRNAM 44 byte field containing the resource name.

ESRBVSER Volume serial. Used only when ESRBCLAS = DATASET and ESRBDSTY is not equal to ‘M’.

ESRBDSTY Dataset type when ESRBCLAS = DATASET. Valid values are:• N - NonVSAM • V - VSAM• M –Model Profile • T – Tape dataset

Table 24 Return codes

ESRBR15 On return, contains the return code from the RACROUTE macro.

ESRBRRET On return, contains the RACF return code.

ESRBRREA On return, contains the RACF reason code.

ESRBSRET On return, contains the SAF return code.

ESRBSREA On return, contains the SAF reason code.



Restoring the EMC-supplied SAF interfaceUse member #92SAFJB in the Mainframe Enablers RIMLIB to restore the EMC-supplied SAF interface.

Take the following steps for all of the Mainframe Enablers components:

1. Read the instructions in #92SAFJB to ensure that the SAF security process will be reenabled in the intended products.


3. Run the job.

4. Restart all Mainframe Enablers components.

Restoring the EMC-supplied SAF interface 75

APPENDIX ADetermining Current Maintenance Levels

This appendix describes how to determine the current maintenance levels of your Mainframe Enablers components. (The maintenance level is sometimes referred to as the base level.)

◆ AutoSwap ............................................................................................................... 78◆ ConGroup ............................................................................................................... 78◆ GNS ........................................................................................................................ 79◆ MSC........................................................................................................................ 79◆ ResourcePak Base................................................................................................... 79◆ SDV and DSE Monitors ............................................................................................ 80◆ SRDF Host Component ............................................................................................ 80◆ TimeFinder/Clone Mainframe Snap Facility.............................................................. 81◆ TimeFinder/Mirror ................................................................................................... 81

Determining Current Maintenance Levels 77

Determining Current Maintenance Levels

AutoSwapTo determine the latest maintenance level that has been applied to AutoSwap, look at the initial task startup message:

SCFS234I AutoSwap version v.r.m, level xxx (SFvrmnn mm/dd/yy)

This message reports:

◆ Vv.r.m = AutoSwap release information:

v = Version.

r = Release.

m = Modification level.

◆ level xxx = an additional release level

◆ SF VRmnn = ResourcePak Base release information: where v indicates the software version, r indicates the software release level, m indicates the software modification level, and nn indicates the latest EMC PTF maintenance that was applied to ResourcePak Base.

◆ mm/dd/yy = The date the latest module was assembled.

ConGroupTo determine the latest maintenance level that has been applied to ConGroup, look at the initial task startup message:

CGRP000I ConGroup Vv.r (mm/dd/yy-hh.mm ConGroup module-PTF) Initializing


◆ Vv.r = ConGroup release information:

v = Version.

r = Release.

◆ mm/dd/yy-hh.mm = The date, hour, and minute of the build. If there is no PTF, the build date-time shows the build date-time of the ConGroup main module. If there is a PTF, the build time is the build date-time is that of the PTF.

◆ ConGroup module = The name of the ConGroup module. Including the version, release, and modification level.

◆ PTF = The full name of the PTF (for example, SC64001). If no maintenance has been applied, the name of the PTF contains multiple zeros.

Note: You can also find the information in CGRP281I, a message that documents the data on which the most recently assembled module (or PTF) was assembled. The Mainframe Enablers Message and Code Guide has more information about CGRP281I.



GNSTo determine the latest maintenance level that has been applied to the GNS module, look at the initial task startup message:

SCF0890I SCFGNST - GNS task is now active. SCFGNST-mm/dd/yy-hh.mm-Vvrm-SFvrmnn-SSCF


◆ ResourcePak Base release information, where v indicates the software version, r indicates the software release level, m indicates the software modification level, and nn indicates the latest EMC PTF maintenance that was applied to ResourcePak Base.

◆ The date, hour, and minute the latest module was assembled is also provided here.

MSCTo determine the latest maintenance level that has been applied to the MSC modules, look at the initial task startup messages:

SCF1315I MSC MODULE= EHCMSCMA VER= Vv.r.m PATCH= SRvrmnn SCF1315I MSC MODULE= EHCMSCMB VER= Vv.r.m PATCH= SRvrmnn SCF1315I MSC MODULE= EHCMSCMC VER= Vv.r.m PATCH= SRvrmnn SCF1315I MSC MODULE= EHCMSCMD VER= Vv.r.m PATCH= SRvrmnn SCF1315I MSC MODULE= EHCMSCM8 VER= Vv.r.m PATCH= SRvrmnn


◆ VER= Vv.r = SRDF Host Component release information release information:

v = Version.

r = Release.


◆ PATCH= SRvrmnn = The latest EMC maintenance that was applied to SRDF Host Component (PATCH), where vrm indicates the Host Component version and nn indicates the latest EMC PTF maintenance that was applied to ResourcePak Base. If no maintenance has been applied, the PTF value is 00.

ResourcePak BaseTo determine the latest maintenance level that has been applied to ResourcePak Base, look at the header of the initial task startup message:

SCF0100I EMC SYMMETRIX CONTROL FACILITY VERSION vrm NOW ACTIVE (nn)


◆ VERSION vrm = ResourcePak Base release information:

v = Version.

r = Release.


◆ (nn) = The last two digits of the latest EMC PTF maintenance that was applied to ResourcePak Base. If no maintenance has been applied, the PTF value is 00.

GNS 79


SDV and DSE MonitorsTo determine the latest maintenance level that has been applied to the SDV and DSE Monitors, look at the initial task startup messages:

SCF1100I SDV MONITOR SNAPPOOL TASK STARTED - SCFMNLOG-mm/dd/yy-hh.mm-Vv.r.m(nnn) SCF1100I DSE MONITOR DSEPOOL TASK STARTED - ESFMNDSE-mm/dd/yy-hh.mm-Vv.r.m(nnn)


◆ mm/dd/yy-hh.mm = The date, hour, and minute the latest module was assembled.

◆ Vv.r.m = ResourcePak Base release information:

v = Version.

r = Release.


◆ nnn = The latest EMC PTF maintenance that was applied to ResourcePak Base.

SRDF Host ComponentTo determine the latest maintenance level that has been applied to SRDF Host Component, issue an #SQ GLOBAL command. This example illustrates the #SQ GLOBAL output display:

EMCMN03I SRDF HOST COMPONENT Vn.n.n NOW ACCEPTING COMMANDS EMCMN81I SRDF HOST COMPONENT Vn.n.n NOW PROCESSING COMMANDS

EMCMN00I SRDF-HC : (5) &SQ GLOBAL EMCQG00I SRDF-HC DISPLAY FOR (5) &SQ GLOBAL 084 VERSION: n.n.n SYNCH_DIR_CURR: R1>R2 MSG_PROC: YES,512 OPER_VERIFY: NONE SYNCH_DIR_ALWD: R1<>R2 LOG_DDNAM: HCLOG1 CONFIG_FBA: ENABLED MAX_QUERY: 4096 MAX_CMDQ: 4096 DISPLAY_SORT_ORDER: SYMDEV MESSAGE_EXIT: INACTIVE HC-PTF: 0001 SCF-VERSION: s.s.s SCF-PTF: 0001 CRPAIR_NCPY: STAR

The command output displays the following:

◆ SRDF Host Component version information (HC-VERSION)

◆ The last four digits of the latest EMC maintenance that was applied to SRDF Host Component (HC-PTF)

◆ ResourcePak Base version information (SCF-VERSION)

◆ The last four digits of the latest EMC maintenance that was applied to ResourcePak Base (SCF-PTF)

Note: The SRDF Host Component Product Guide fully describes this display under the reference section for the SQ GLOBAL command.

If no maintenance has been applied, the PTF value is 0000.



TimeFinder/Clone Mainframe Snap FacilityTo determine the latest maintenance level that has been applied to the high-level TimeFinder/Clone Mainframe Snap Facility module, look at the header of the initial task startup message:

SCF2023I SCFGBLSN MODULE FOUND, LFC WAS SPECIFIED, SNAP Vv.r ACTIVE


◆ SNAP module release information.

v = Version.

r = Release.

TimeFinder/MirrorTo determine the maintenance level that has been applied to TimeFinder/Mirror, look at the header of the application batch report:

hh:mm:ss BCVM046I *** EMC TimeFinder Vv.r.m (nn) - SCF Vv.r.m (nn) *** mm/dd/yyyy


◆ hh:mm:ss = The hour, minute, and second in hh:mm:ss format.

◆ Vv.r.m =TimeFinder release information:

v = Version.

r = Release.


◆ (nn) = The last two digits (in parentheses) of the latest EMC maintenance (PTF) that was applied to TFCMSF. If no maintenance has been applied, the value within the parentheses is (00).

◆ SCF Vv.r.m = SCF (ResourcePak Base) release information (version, release, and modification level).

◆ (nn) = The last two digits (in parentheses of the latest EMC maintenance (PTF) that was applied to SCF. If no maintenance has been applied, the value within the parentheses is (00).

◆ mm/dd/yyyy = The month, day, and year when the maintenance was built. If there is no maintenance applied, the date is the build date of the module.

TimeFinder/Clone Mainframe Snap Facility 81

emc mainframe enablers · pdf file4 mainframe enablers version 7.6 installation and...

Documents