EMC TimeFinder Utility for z/OSEMC Corporation Corporate Headquarters : Hopkinton, MA 01748-9103 1-508-435-1000 EMC® TimeFinder® Utility for z/OS Version 7.0 Product Guide …

EMC® TimeFinder® Utility for z/OSVersion 7.0

Product GuideP/N 300-001-871

REV A02

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-9103

1-508-435-1000www.EMC.com

2

Copyright © 2005 - 2009 EMC Corporation. All rights reserved.

Published April, 2009

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.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.

EMC TimeFinder/Utility for z/OS Version 7.0 Product Guide

The EMC TimeFinder Utility for z/OS Product Guide is for use with the EMC TimeFinder Utility for z/OS.

DocumentCoverage

EMC TimeFinder/Utility for z/OS Version 7.0 Product Guide 3

4

Document Coverage


Contents

Document Coverage

Figures

Preface

Chapter 1 Product OverviewEMC Mainframe Enablers and the EMC TimeFinder Utility ..... 14Introduction to the TimeFinder Utility .......................................... 15Processing overview......................................................................... 16ISPF interface ..................................................................................... 19

Chapter 2 Using the TimeFinder UtilityProcessing and model statements .................................................. 22

Restrictions ..................................................................................22Processing statements ...................................................................... 24

Reading syntax diagrams ..........................................................24CATALOG.......................................................................................... 27DEBUG ............................................................................................... 29MESSAGES ........................................................................................ 30PROCESS............................................................................................ 33RELABEL ........................................................................................... 34RENAME............................................................................................ 36SIMULATE......................................................................................... 38SOURCECATALOG ......................................................................... 39Processing statement example ........................................................ 44Using IDCAMS model statements ................................................. 45


Contents

Processing considerations ............................................................... 49

Glossary

Index

EMC TimeFinder/Utility for z/OS Version 7.0 Product Guide6

Title Page

Figures

1 TimeFinder Utility order of processing ...................................................... 162 CATALOG statement syntax diagram........................................................ 273 MESSAGES statement syntax diagram....................................................... 314 PROCESS statement syntax diagram .......................................................... 335 RELABEL syntax diagram ............................................................................ 346 RENAME syntax diagram ............................................................................ 367 SOURCECATALOG syntax diagram.......................................................... 39


Figures

EMC TimeFinder/Utility for z/OS Version 7.0 Product Guide8

Preface

As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information about product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Note: This document was accurate as of the time of publication. However, as information is added, new versions of, or updates to, this document may be released to the EMC Powerlink website. Check the Powerlink website to ensure that you are using the latest version.

Audience This guide is intended for the host system administrator, system programmer, or operator who will be involved in managing or operating the TimeFinder Utility for z/OS.

Relateddocumentation

The following EMC publication provides additional information:

◆ EMC Mainframe Enablers Version 7.0 Release Notes

◆ EMC Mainframe Enablers Version 7.0 Installation and Customization Guide

◆ EMC Mainframe Enablers Version 7.0 Message and Code Guide

◆ EMC TimeFinder/Mirror Version 7.0 Product Guide

◆ EMC TimeFinder/Clone Mainframe SNAP Facility Version 7.0 Product Guide


10

Preface

Conventions used inthis guide

EMC uses the following conventions for special notices.

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

CAUTION!A caution contains information essential to avoid data loss or damage to the system or equipment.

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

Typographical conventionsEMC uses the following type style conventions in this guide.

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, filenames, functions, utilities

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

Bold Used in procedures for:• Names of interface elements (such as names of windows,

dialog boxes, buttons, fields, and menus)• What user specifically selects, clicks, presses, or types

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 command line• User input variables


Preface

Where to get help EMC support, product, and licensing information can be obtained as follows.

Product information — For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support — For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account.

Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this guide to:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject you are addressing.

[ ] Square brackets enclose optional values

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

... Ellipses indicate nonessential information omitted from an example


http://powerlink.emc.com

12

Preface


1Invisible Body Tag

This chapter introduces the TimeFinder Utility for z/OS. The topics are:

◆ EMC Mainframe Enablers and the EMC TimeFinder Utility ...... 14◆ Introduction to the TimeFinder Utility ........................................... 15◆ Processing overview.......................................................................... 16◆ ISPF interface ...................................................................................... 19

Product Overview

Product Overview 13

14

Product Overview

EMC Mainframe Enablers and the EMC TimeFinder UtilityEMC® TimeFinder® Utility is one of the EMC Mainframe Enablers. The EMC Mainframe Enablers include the following components that you can use to monitor and manage your storage:

◆ ResourcePak® Base for z/OS

◆ EMC Consistency Groups for z/OS

◆ SRDF® Host Component for z/OS

◆ TimeFinder/Clone Mainframe SNAP Facility

◆ TimeFinder/Mirror for z/OS

◆ TimeFinder Utility

When you install the Mainframe Enablers kit, you install the software for all the components.

However, to enable any of the components, except ResourcePak Base (which is a persistent address space running on any z/OS processor on which it is installed), you need to install the License Feature Code for that component into the ResourcePak Base initialization parameters file.

Follow the steps outlined in the EMC Mainframe Enablers Installation and Customization Guide and the EMC ResourcePak Base for z/OS Product Guide to install the Mainframe Enablers and activate the TimeFinder Utility.


Product Overview

Introduction to the TimeFinder UtilityThe TimeFinder Utility is a tool you use to condition the catalog by relabeling and recataloging entries. This avoids the issues associated with duplicate volume names in the mainframe environment.

Typically, you use the TimeFinder Utility with the other TimeFinder Family members:

◆ EMC TimeFinder/Mirror

◆ EMC TimeFinder/Clone Mainframe SNAP Facility 1

The TimeFinder Utility extends the processing of Business Continuance Volumes (BCVs) and standard devices.

Note: The EMC TimeFinder/Mirror for z/OS Product Guide provides more information about BCVs and standard devices.

The TimeFinder Utility gives you the following abilities:

◆ With the RELABEL statement, you can condition the device to a point where you can perform logical restores from the physical backup.

Note: “RELABEL” on page 34 gives more information.

◆ You can further condition the volume by re-cataloging and renaming both VSAM and non-VSAM files. You can then store the files processed in:

• An existing catalog

• A new user catalog you create

Note: In special cases, you may need to provide a IDCAMS 2 Model Statement. Usually this is not required unless a password needs to be supplied on a recatalog.

◆ You can run a simulation to view the actions that would be performed.

1. Made up of the TimeFinder/Clone, TimeFinder/Snap, and TimeFinder/Consistency Group functional products.

2. IDCAMS stands for IDC Access Method Services. The ``IDC'' is the International Business Machines product code for VSAM.

Introduction to the TimeFinder Utility 15

16

Product Overview

Processing overviewFigure 1 shows the TimeFinder Utility order of processing.

Figure 1 TimeFinder Utility order of processing

Parse and validate all input

statements

Perform RELABEL processing

Locate and ensure that all volumes

for PROCESS are found

Perform all CATALOG CLEANUP requests

Allocate all NEW catalogs

Ensure that all other referenced

catalogs exist

Determine which datasets are to be

processed

Process each selected dataset/

cluster in alphabetic order

VSAM component dataset?

No

Determine VSAM cluster name

Yes

End


Product Overview

As shown in Figure 1 on page 16, the TimeFinder Utility order of processing is:

1. Parse and validate all input statements.

2. Perform RELABEL processing.

3. Locate and ensure that all volumes necessary for PROCESS are found.

4. Perform all CATALOG CLEANUP requests.

5. Allocate all NEW catalogs.

6. Ensure that all other catalogs referenced exist.

7. Read in the dataset list from all volumes being PROCESSed. Determine which datasets are selected for processing.

8. For each selected VSAM component dataset, determine the VSAM cluster name.

9. Begin processing of each selected dataset/cluster – in alphabetic order.

For non-VSAM datasets:

a. Determine the number and order of volumes for the dataset.

b. For GDG datasets, ensure that the GDG base exists in the target catalog.

c. Rename the dataset in the VTOC and VTOC Index on each volume.

d. Catalog the dataset into the target catalog.

For VSAM datasets:

a. Determine the number and order of volumes for the index component (if present).

b. Determine the number and order of volumes for the data component.

c. Rename the component datasets in the VTOC and VTOC index on each volume.

d. Recatalog the cluster into the target catalog.

e. If the source catalog is available, obtain the path definitions for the cluster.

f. Add the PATHs to the target catalog.

Processing overview 17

18

Product Overview

g. For each alternate index that exists for this cluster and is selected for processing:

– Determine the number and order of volumes for the index component.

– Determine the number and order of volumes for the data component.

– Rename the component datasets in the VTOC and VTOC index on each volume.

– Recatalog the alternate index into the target catalog.– If the source catalog is available, obtain the path definitions

for the alternate index.– Add the PATHs to the target catalog.

10. Processing completed.


Product Overview

ISPF interfaceEMC ResourcePak Base includes (in EMCTOOLS) an ISPF interface that allows you to control several Mainframe Enablers components. The ISPF interface requires the following software:

◆ ISPF 3.3.0 or higher

◆ TSO/E 2.3.1 or higher

The menus and panels of this interface use REXX and ISPF dialogs to:

◆ Query your Symmetrix® environment.

◆ Issue commands to control that environment.

◆ Build and retain customized command streams.

The EMC ResourcePak Base for z/OS Product Guide describes EMCTOOLS.

Note: The ISPF panels illustrated in the EMC ResourcePak Base for z/OS Product Guide are a representation of the interface at the time that document was published. The panels and contents may differ as the software is updated.

ISPF interface 19

20

Product Overview


2Invisible Body Tag

This chapter describes the TimeFinder Utility and provides instruction for its use. Topics are:

◆ Processing and model statements.................................................... 22◆ Processing statements........................................................................ 24◆ CATALOG........................................................................................... 27◆ DEBUG ................................................................................................ 29◆ MESSAGES ......................................................................................... 30◆ PROCESS............................................................................................. 33◆ RELABEL ............................................................................................ 34◆ RENAME............................................................................................. 36◆ SIMULATE.......................................................................................... 38◆ SOURCECATALOG........................................................................... 39◆ Processing statement example ......................................................... 44◆ Using IDCAMS model statements .................................................. 45◆ Processing considerations................................................................. 49

Using the TimeFinderUtility

Using the TimeFinder Utility 21

22

Using the TimeFinder Utility

Processing and model statementsThe TimeFinder Utility has processing statements and optional model statements. The following is a sample JCL:

//EMCTFU EXEC PGM=EMCTFU//SYSOUT DD SYSOUT=*//TFINPUT DD *...processing statements.../*//TFMODEL DD * (optional)model IDCAMS statements (optional)/*

The TFINPUT and TFMODEL files should be 80-byte fixed length. All syntax, keywords and parameters, must be specified in uppercase.

Note: “Processing statement example” on page 44 shows a more detailed example.

Descriptions of processing and model statements are provided in the following sections.

Restrictions◆ The TimeFinder Utility does not process multivolume datasets if

the volumes are not relabeled with a RELABEL statement or by the TimeFinder/Mirror SPLIT command with a VOLID(volser,E) option.

◆ Non-VSAM datasets that have never been opened will not be processed.

◆ Key range VSAM datasets are not supported.

◆ IDF data space and IDF datasets will not be processed because they have different formats in comparison with VSAM cluster.

◆ Volumes and datasets under the GSM environment will not be processed.



◆ A target dataset requires that the original dataset be non-VSAM or a VSAM dataset cataloged to an EDF catalog.

◆ For VSAM datasets, the original catalog and the catalog after RENAME must be different, and must have catalog names of the same length.

Region=4M in the Execution JCL is recommended.

Processing and model statements 23

24


Processing statements The following sections describe TimeFinder Utility processing and model statements. Include statements in the JCL using the format and parameters described here.

You can also include comment lines by using the following format:

/* comment */

Reading syntax diagramsThe statement descriptions that follow include diagrams to explain the syntax of the statement. Read the syntax diagrams from left to right and top to bottom, following the path of the line.

The beginning of a statement:

The end of a statement:

A call to a procedure:

Required items appear on the horizontal line (the main path):

Optional items appear below the horizontal line:

processname

required item

optional item



If you must choose one of the items, one item of the stack appears on the main path:

If choosing none of the items is an option, the entire stack appears below the main path:

If one of the items is the default, it will appear above the main path and the remaining choices will be shown below:

An arrow returning to the left above the main line (a repeat arrow) indicates an item that can be repeated, and the separator character if it is other than a blank:

required Item 1

required Item 2

required Item 3

optional item 1

optional item 2

optional item 3

default

option 1

option 2

option 3

keyword repeatable argument

,

Processing statements 25

26


A repeat arrow above a stack indicates that you can make more than one choice from the stacked items:

Keywords appear in uppercase and must be spelled exactly as shown.

Variables appear in lowercase and italics (for example, column-name). They represent user-supplied names or values in the syntax.

If punctuation marks, parentheses, arithmetic operators, or other such symbols are shown, you must enter them as part of the syntax.

keyword argument

argument

,



CATALOG

Purpose The CATALOG statement specifies the catalog that will be used during processing.

Required syntax CATALOG catalog

Optional parameters Separate the optional parameters from the required syntax and from each other with commas. Do not leave any embedded spaces.

[,NEW]

[,VOLSER=volser]

[,DEFAULT]

[,CLEANUP]

Syntax diagram Figure 2 is a syntax diagram of the CATALOG statement.

Figure 2 CATALOG statement syntax diagram

Parameterdescriptions

catalogname

Specifies a one-to-44 character name of the catalog. If the catalog name specified is the keyword SYSCTLG (also can be SYSTEM_CATALOG or SYSTEMCATALOG), a lookup is performed to determine the appropriate catalog to use. The dataset is then cataloged into the system catalog structure.

You cannot use the SYSCTLG keyword with the CLEANUP parameter. If you want to specify CLEANUP, add additional CATALOG statements for specific catalogs.

NEW

Indicates that the catalog does not yet exist, and should be created on the volume indicated by VOLSER parameter.

CATALOG= catalogname

,NEW

,VOLSER=volser

,DEFAULT ,CLEANUP

CATALOG 27

28


VOLSER=volser

Specifies the volume on which to create a catalog. If you specify a volser by using the keyword ‘SMSVOL,’ TimeFinder Utility ignores the volser and allocates the catalog without specifying a volser.

Normally, model =NEWCATLG is used to allocate a new catalog; but, if you specify ‘SMSVOL,’ model =SMSCATLG is used.

DEFAULT

Specifies that the named catalog is the default catalog for all rename statements that have no catalog reference.

CLEANUP

Indicates that all existing catalog references to datasets on a volume selected for processing should be uncataloged before the recatalog process starts.

Comments Note that no ALIAS is created with the catalog. When RENAME is used, the renamed datasets are unusable until a DEFINE ALIAS is performed.

If you use PROTECT ALL in RACF, the first qualifier used for RENAME must be defined in RACF.

This only applies when creating new catalogs. Existing catalogs can be prepared and made reusable with the CLEANUP parameter on the CATALOG statements.

Examples CATALOG CATALOG.USER,DEFAULT

Makes the specific catalog CATALOG.USER the default for this run.

CATALOG SYSCTLG,DEFAULT

Makes the system catalog the default for this run.

CATALOG CATALOG.MVSICF.USER,CLEANUP

Cleans up volumes being processed of this specific catalog.



DEBUG

Purpose The DEBUG processing statement enables debug reporting during the job.

Required syntax DEBUG

Parameters None.

DEBUG 29

30


MESSAGES

Purpose The MESSAGES statement allows you to customize the output log file. You can suppress individual messages, or redirect messages to the operators console. You can also suppress warning messages about reserved or unselected datasets.

IMPORTANT!You should place MESSAGES statement(s) at the beginning of the input stream before any other statements so that the MESSAGES statement(s) can be processed first.

Required syntax MeSsaGes RESERVED=YES|NO[,UNMATCHED=YES|NO]MeSsaGes UNMATCHED=YES|NO[,RESERVED=YES|NO]

MeSsaGes ID=msgid[,PRINT=YES|NO][,CONSOLE=YES|NO][,ROUTCDE=rtcode,][,DESC=desc]


[,RESERVED=YES|NO]

[,UNMATCHED=YES|NO]

[,ID=msgid]

[,PRINT=YES|NO]

[,CONSOLE=YES|NO]

[,ROUTCDE= rtcode]

[,DESC= desc]

Syntax diagram Figure 3 on page 31 is a syntax diagram of the MESSAGES statement.



Figure 3 MESSAGES statement syntax diagram


RESERVED=YES|NO

Specifies whether warning messages about reserved datasets should be issued. A reserved dataset is not eligible for processing. Catalogs, VVDS, and VTOC Index datasets are reserved datasets.

UNMATCHED=YES|NO

Specifies whether warning messages about unmatched datasets should be issued. An unmatched dataset is one which is not selected for processing.

ID=msgid

Specifies a complete message ID for special processing. This can be suppressed (PRINT=NO) or redirected to the operator’s console (CONSOLE=YES).

PRINT=YES|NO

Used with the ID=msgid parameter to indicate that the message should be printed in the logfile.

CONSOLE=YES|NO

Used with the ID=msgid parameter to indicate that the message should be written to the operator’s console.

ROUTCDE= rtcode

Specifies a particular routing code to be used when sending a message to the operator’s console. Default is no routing code.

Reserved=NO, UNMATCHED=NO,

PRINT=YES,

MeSsaGes

Reserved=YES, UNMATCHED=YES,

ID=msgid,

PRINT=NO,

CONSOLE=YES,

CONSOLE=YES,

ROUTCDE=rtcode, DESC=desc

MESSAGES 31

32


DESC= desc

Specifies a particular descriptor code to be used when sending a message to the operator’s console. The default is no descriptor code.

Comments ◆ Unless you specify PRINT=NO, a message directed to the console is also written to the logfile.

◆ If you are going to manipulate multiple message identifiers, you must specify each in a separate MESSAGES statement.

◆ If you specify the same message multiple times, only the first encountered is used.

Examples MESSAGES RESERVED=NO,UNMATCHED=NO

MESSAGES ID=BCVU010I,CONSOLE=YES,DESC=3



PROCESS

Purpose The PROCESS statement specifies a unit for processing. For multivolume files, you must specify each volume in a process statement.

Required syntax PROCESS CUU=device,VOLSER=volser

Optional parameter Separate the optional parameter from the required syntax with a comma. Do not leave any embedded spaces.

[,BOTH|,VSAM|,NON-VSAM]

Syntax diagram Figure 4 is a syntax diagram of the PROCESS statement.

Figure 4 PROCESS statement syntax diagram


CUU=device

Specifies a device on the controller. The device must be online.

VOLSER=volser

Specifies the volume serial number of the device.

BOTH|VSAM|NON-VSAM

Specifies type of files to be processed.VSAM only processes VSAM files. NON-VSAM only processes non-VSAM files. BOTH (default) processes all files.

Comments If you specify both volser and CUU, then they must both point to the same device.

Example PROCESS CUU=F000,VSAM

PROCESS CUU=device ,,VOLSER=volser

,BOTH

,VSAM

,NON-VSAM

PROCESS 33

34


RELABEL

Purpose Changes the volser of the device. Relabels the device to reflect the new volser by updating:

◆ The VVDS and VTOC Index names

◆ The VVDS name entry

◆ The DSCBs

The device may then be put online.

Required syntax RELABEL CUU=dev,OLD-VOLSER=old,NEW-VOLSER=new

Optional parameter Separate the optional parameter from the required syntax with a comma. Do not leave any embedded spaces.

[,OFFLINE]

Syntax diagram Figure 5 is a syntax diagram of RELABEL.

Figure 5 RELABEL syntax diagram


CUU=device

Specifies the device to be clipped.

OLD-VOLSER=old

Specifies the volser of the volume which the device was attached.

NEW-VOLSER=new

Specifies the new volser for the volume.

OFFLINE

Specifies that after the RELABEL has completed, the volume is to be left offline. Normally the volume is varied online with the new volser. If a PROCESS statement for the new volume is also present in the run, the OFFLINE parameter is ignored.

RELABEL NEW-VOLSER=new

,OFFLINE

CUU=device, OLD-VOLSER=old,



Comments If a RELABEL is specified for a unit that is online and already has the NEW-VOLSER (such as would occur in an accidental rerun), a message is logged and the RELABEL is ignored.

Example RELABEL CUU=F000,OLD-VOLSER=TSO001,NEW-VOLSER=BCV001

RELABEL 35

36


RENAME

Purpose The RENAME statement changes the prefixes (HLQs - high level qualifiers) of datasets.

Required syntax RENAME old-HLQ,new-HLQ

Optional parameter Separate the optional parameter from the required syntax with commas. Do not leave any embedded spaces.

[,CATALOG=catalog]

Syntax diagram Figure 6 is a syntax diagram of RENAME.

Figure 6 RENAME syntax diagram


old-HLQ

Specifies the current prefix of all datasets to be renamed.

new-HLQ

Specifies the replacement prefix for all datasets defined by the old-HLQ parameter.

CATALOG=catalog

Selects the catalog used to catalog the newly renamed dataset. If the catalog name specified is the keyword SYSCTLG (can also be SYSTEM_CATALOG or SYSTEMCATALOG), a lookup is performed to determine the appropriate catalog.

The dataset is then cataloged into the system catalog structure.

Comments Any datasets whose prefix matches old-HLQ is selected for processing. The new-HLQ replaces the matching old-HLQ characters. If the old-HLQ or new-HLQ value ends in an asterisk, then the strings are used as is. If the old-HLQ or new-HLQ value do not end in an asterisk, then a period is added to the string to make it an index level.

RENAME old-HLQ, ,new-HLQ

,CATALOG=catalog



If the catalog operand is omitted, then the default catalog is used. If the catalog operand is omitted and there is no default catalog, then the run is terminated.

If the old-HLQ and the new-HLQ specify the same string, then no rename takes place - only the re-catalog.

Examples RENAME SYS1,SYS1BCV

Selects only datasets beginning with the string “SYS1.” and replaces this with “SYS1BCV.”

RENAME SYS*,SYSBCV*

Selects all datasets beginning with the string “SYS” and replaces this with “SYSBCV.”

RENAME BAP,CATALOG=SYSTEM_CATALOG

Catalogs all the BAP datasets on volumes being processed into the system catalog structure.

RENAME 37

38


SIMULATE

Purpose SIMULATE does not change catalogs. VVDSs or VTOCs are made when you include the SIMULATE statement in the job.

Required syntax SIMULATE

Parameters None.

Comments If a RELABEL and PROCESS are requested for the same device during a simulation run, the RELABEL is simulated and the PROCESS is bypassed, because the device is not actually available until the RELABEL completes successfully.

Errors may occur during the actual RELABEL or PROCESS operations may not be detected when SIMULATE is included in the job. Though no error occurred while processing a job with a SIMULATE statement, errors can be returned when the job is executed with SIMULATE.



SOURCECATALOG

Purpose Under certain circumstances, the source dataset catalog may be unavailable or unnecessary. The TimeFinder Utility normally requires the source catalog to resolve issues regarding multivolume datasets, generation data groups, and path names. You can tailor processing in each of these areas to use or ignore the source dataset catalog.

Required syntax SouRCeCATalog DeFauLT=YES|NO


[,GenerationDataGroup=YES|NO]

[,MultiVOLume=YES|NO]

[,PATH=YES|NO]

[,DIRECT=YES|NO]

Syntax diagram Figure 7 is a syntax diagram of SOURCECATALOG.

Figure 7 SOURCECATALOG syntax diagram

SouRCeCATalog

DEFAULT=NO

,GeneationDataGroup-YES

,GeneationDataGroup-No

,MultiVOLume=YES

,MultiVOLume=NO

,PATH=YES

,PATH=NO

,DIRECT=YES

,DIRECT=NO

DEFAULT=YES

SOURCECATALOG 39

40



DeFauLT=YES|NO

Default option for processing the source dataset catalog. This may be overridden by including additional parameters.

GenerationDataGroup=YES|NO

Indicates whether to use the source dataset catalog to determine the generation data group base options. If the source dataset catalog is not to be used, the model =GDGDFLT is used to create any necessary GDG base entries in the target dataset catalog. If the source dataset catalog is being used, the model GDGBASE is used to create any necessary GDG base entries using information from the source dataset catalog.

MultiVOLume=YES|NO

Indicates that the source dataset catalog will provide the list of original volume serial numbers for processing multivolume datasets. If you select MVOL=NO, processing is determined based upon the DSORG of the selected dataset. For non-VSAM datasets, the DS1VOLSQ field in the format 1 DSCB is used to build the list of volumes. For VSAM datasets, information found in the VVDS is used to build the list of volumes.

PATH=YES|NO

Indicates that the source dataset catalog will be used to determine whether paths exist for selected VSAM datasets. A path may exist for individual clusters, along with AIX sets. Path information can only be found in the catalog, so processing with PATH=NO effectively disables path processing.

DIRECT=YES|NO

Indicates whether a source catalog may be directly accessed during cleanup, and whether a target catalog may be directly accessed when cataloging the datasets.

Comments MULTIVOLUME(YES) parameter — While processing a dataset, the TimeFinder Utility performs a catalog lookup. If the dataset is not cataloged, the TimeFinder Utility checks the VTOC entries for all of the volumes being processed for all of the segments of the dataset.

If all of the dataset segments are in the list of volumes being processed, the TimeFinder Utility catalogs the dataset. If all of the dataset segments are not in the list of volumes being processed, the TimeFinder Utility does not catalog the dataset and processing continues.



If the dataset is cataloged, the TimeFinder Utility uses the list of volumes for the dataset currently cataloged to determine whether this is a multivolume dataset.

If the currently cataloged dataset resides on only one volume, the TimeFinder Utility assumes that the dataset being processed is also a single volume dataset, and processing continues. However, if the currently cataloged dataset is a multivolume dataset, the TimeFinder Utility assumes that the dataset being processed is also a multivolume dataset.

In fact, the TimeFinder Utility uses the volume list from the currently cataloged dataset to determine the order and list of volumes for the dataset being processed. If this dataset segment does not map to the first volume in the volume list, the TimeFinder Utility stops processing this dataset segment.

If this dataset segment does map to the first volume in the volume list, then the TimeFinder Utility checks to make sure that each of the original volumes maps to a volume currently being processed. If any of the original volumes do not map to a volume currently being processed, the TimeFinder Utility stops processing this dataset.

After the TimeFinder Utility has determined all of the new volumes, it continues to process the dataset. The TimeFinder Utility processes ALL of the dataset segments.

MULTIVOLUME(NO) parameter — If you do not have the source catalog, an alternative mode of processing is available to you. You can activate the alternative mode by including a processing statement:

SOURCECATALOG MULTIVOLUME (NO)

In this case, the TimeFinder Utility does not reference the source catalog to determine the number and sequence of dataset extents. The TimeFinder Utility searches all volumes to be processed and locates all extents for a dataset.

For non-VSAM datasets, the TimeFinder Utility uses the DS1VOLSQ field in the format 1 DSCB to determine the order of the volumes. In addition, the TimeFinder Utility uses the flag DS1IND80 in field DS1DSIND to determine that it has found all of the necessary volumes.

SOURCECATALOG 41

42


Note: EMC has found that if a program creating the non-VSAM multivolume dataset abends, the DS1IND80 flag is not set in the DS1DSIND field in the format 1 DSCB. Because the flag is not set, the TimeFinder Utility is unable to determine that all of the necessary volumes have been found.

For VSAM datasets, these fields are not maintained and the TimeFinder Utility uses another method. VSAM file information is maintained in the VVDS on each volume. The TimeFinder Utility uses VVDS to determine:

◆ The order of the volumes

◆ Whether all volumes are present

GENERATIONDATAGROUPS parameter — When the TimeFinder Utility detects that a dataset is a generation data group (GDG) dataset, it performs additional processing. Because the recatalog operation fails if the GDG base does not exist, the TimeFinder Utility first checks the target catalog to ensure that the GDG base already exists.

If the TimeFinder Utility finds the GDG base in the target catalog, it catalogs the dataset. If the TimeFinder Utility does not find the GDG base in the target catalog, then a GDG base must be created prior to cataloging the dataset. If you specify (or default) SOURCECATALOG GENERATIONDATAGROUP (YES), the TimeFinder Utility takes the following steps:

1. Looks up the GDG base in the source catalog.

2. Executes the model =GDGBASE, using override parameters obtained from the source catalog.

Result: TimeFinder Utility creates the GDG base in the target catalog.

3. If the TimeFinder Utility does not find the GDG base in the source catalog then it executes the model =GDGDFLT to create a default GDG base in the target catalog.

4. If you specify SOURCECATALOG GENERATIONDATAGROUP (NO), the TimeFinder Utility executes the model =GDGDFLT to create a default GDG base in the target catalog.

PATH parameter — Paths are available for VSAM datasets and usually connect an active alternate index to a base cluster. You can also define paths for individual clusters.



If you specify (or default) SOURCECATALOG PATH (YES), the TimeFinder Utility picks up existing path definitions and normal RENAME processing takes place. The new path name is then defined into the target catalog.

If you specify SOURCECATALOG PATH (NO), the TimeFinder Utility does not process paths.

Examples SOURCECATALOG DEFAULT=NO,GDG=YES

SRCCAT MVOL=NO,GDG=NO,PATH=YES

SOURCECATALOG 43

44


Processing statement exampleThe following JCL example illustrates the use of the TimeFinder Utility processing statements.

//JOB //EMCTFU EXEC PGM=EMCTFU//SYSOUT DD SYSOUT=*//TFINPUT DD *RELABEL CUU=100,OLD-VOLSER=TSO000,NEW-VOLSER=BCV000RELABEL CUU=101,OLD-VOLSER=TSO001,NEW-VOLSER=BCV001RELABEL CUU=102,OLD-VOLSER=TSO002,NEW-VOLSER=BCV002PROCESS VOLSER=BCV000PROCESS VOLSER=BCV001,VSAMPROCESS VOLSER=BCV002,NON-VSAMCATALOG CATALOG.DEFAULT,DEFAULTCATALOG CATALOG.TEMP,NEW,VOLSER=TS0001RENAME SYS,SYSBCV,CATALOG=CATALOG.TEMPRENAME TSO,TSO.ABC,CATALOG=CATALOG.TEMPRENAME USER,USERBCVRENAME USER1,USER1/*



Using IDCAMS model statements This section describes the syntax and substitution parameters for the TimeFinder Utility IDCAMS model statements.

Syntax =nameline1 -line2 -line n=nameline1 -line2 -line n


=name

A string of up to 8 characters. Current valid names are:

CTLGNV

Catalog non-VSAM dataset using its old name (non-SMS).

RECATNV

Recatalog non-VSAM dataset using its old name (SMS).

RECATIX

Recatalog VSAM indexed cluster using its old name.

RECATAI

Recatalog VSAM alternate index using its old name.

RECATCL

Recatalog VSAM cluster using its old name.

RECATPG

Recatalog VSAM page datasets using its old name.

LISTCTLG

Catalog listing for cleanup phase.

UNCATLG

Remove entries from catalog during cleanup phase.

NEWCATLG

Create a new ICFCatalog (non-SMS).

SMSCATLG

Create a new ICFCatalog (SMS).

Using IDCAMS model statements 45

46


DEFNPATH

Define a path for cluster or an alternate index.

GDGDFLT

Default model to create a GDG base.

GDGBASE

Define a GDG base using information from the source catalog.

line#-

The lines following the =name card make up the IDCAMS statement.

Comments The lines following the =name card make up the IDCAMS statement. Repeating blanks are eliminated. Columns 1-72 are parsed. If a dash (-) is encountered, parsing of that line is terminated. The following embedded substitution values are supported:

%DSNAME% Dataset oldname.

%NEWNAME% Dataset newname.

%CATALOGNAME% Catalog name from RENAME statement or DEFAULT catalog.

%CLUSTERNAME% For a VSAM dataset, its cluster name.

%INDEXTYPE% For a VSAM dataset, its index type.

%VOLUMELIST% For a non-VSAM dataset, the list of volumes containing the non-VSAM dataset.

%INDEXVOLUMELIST% For a VSAM KSDS or AIX dataset, the list of volumes containing the index component.

%DEVICELIST% For a non-VSAM dataset, the list of devices containing it. This is in the same order as the %VOLUMELIST%.

%DATANAME% For a VSAM dataset, the data component name.

%INDEXNAME% For a VSAM indexed dataset, the index component name.

%BASENAME% The base cluster name associated with an alternate index.

%GDGBASE% The GDG base name.

%GDGATTR% GDG attributes - SCRATCH or NOSCRATCH or EMPTY or NOEMPTY.



%GDGLIMIT% GDG generation limit number.

%PAGEATTR% Page dataset attributes - blank or SWAP.

%FILEDDNAME% The DDNAME of the first volume indicated in the %VOLUMELIST%. The presence of the DDNAME parameter in IDCAMS statements improves performance.

Using IDCAMS model statements 47

48


Default model statements

=CTLGNV DEFINE NONVSAM (NAME ('%DSNAME%') DEVICETYPE (%DEVICELIST%) - VOLUMES (%VOLUMELIST%) ) CATALOG ('%CATALOGNAME%')=RECATNV DEFINE NONVSAM (NAME ('%DSNAME%') RECATALOG - DEVICETYPE (%DEVICELIST%) VOLUMES (%VOLUMELIST%) ) - CATALOG ('%CATALOGNAME%')=RECATIX DEFINE CLUSTER (NAME ('%DSNAME%') - %INDEXTYPE% RECATALOG FILE(%FILEDDNAME%) ) - DATA (NAME ('%DATANAME%') VOLUMES (%VOLUMELIST%) ) - INDEX (NAME ('%INDEXNAME%') VOLUMES (%INDEXVOLUMELIST%) ) - CATALOG ('%CATALOGNAME%')=RECATCL DEFINE CLUSTER (NAME ('%DSNAME%') - %INDEXTYPE% RECATALOG FILE(%FILEDDNAME%) - VOLUMES (%VOLUMELIST%) ) DATA (NAME ('%DATANAME%') ) - CATALOG ('%CATALOGNAME%')=RECATAI DEFINE ALTERNATEINDEX (NAME ('%DSNAME%') - RELATE('%BASENAME%') RECATALOG FILE(%FILEDDNAME%) ) - DATA (NAME ('%DATANAME%') VOLUMES (%VOLUMELIST%) ) - INDEX (NAME ('%INDEXNAME%') VOLUMES (%INDEXVOLUMELIST%) ) - CATALOG ('%CATALOGNAME%')=RECATPG DEFINE PAGESPACE (NAME ('%DSNAME%') - RECATALOG FILE(%FILEDDNAME%) %PAGEATTR% - VOLUMES (%VOLUMELIST%) ) CATALOG (''%CATALOGNAME%'')'=LISTCTLG LISTCAT VOLUME CATALOG ('%CATALOGNAME%')=UNCATLG DELETE '%DSNAME%' NOSCRATCH PURGE CATALOG ('%CATALOGNAME%')=NEWCATLG DEFINE USERCATALOG - ( NAME('%CATALOGNAME%') CYLINDERS(1,1) VOL(%VOLUMELIST%) - ICFCATALOG)=SMSCATLG DEFINE USERCATALOG - ( NAME('%CATALOGNAME%') CYLINDERS(1,1) VOL(*) - ICFCATALOG)=DEFNPATH DEFINE PATH (NAME ('%DSNAME%') - PATHENTRY('%BASENAME%') ) CATALOG ('%CATALOGNAME%')=GDGDFLT DEFINE GENERATIONDATAGROUP (NAME ('%GDGBASE%') - LIMIT(255) NOEMPTY NOSCRATCH ) CATALOG ('%CATALOGNAME%')=GDGBASE DEFINE GENERATIONDATAGROUP (NAME ('%GDGBASE%') - LIMIT(%GDGLIMIT%) %GDGATTR% ) CATALOG ('%CATALOGNAME%')



Processing considerationsWhen you use the TimeFinder Utility to process and rename large numbers (thousands) of datasets, you will find that execution time can be very long (in the range of hours). You can take the following steps to minimize the execution time:

◆ Specify a temporary or empty user catalog in the CATALOG statement to eliminate the time spent on the CLEANUP phase.

◆ Specify a SOURCECATALOG statement that includes the DEFAULT=NO and DIRECT=YES parameters.

◆ Implement VLF for the user catalog that is specified in the CATALOG statement to be used by TimeFinder Utility processing. (See the IBM document, MVS Initialization and Tuning Reference, for details.) SYS1.PARMLIB member COFVLFxx should include CLASS NAME IGGCAS and the specified user catalog as an eligible major name (EMAJ).

◆ Review your GRS environment. Run time can be shorter in a GRS STAR configuration than in a RING configuration when in a SYSPLEX and there are more than two systems. In a RING configuration, check GRSCNFxx parmlib member for RESMIL and ACCELSYS parameter specifications, reducing these to smaller values speeds up run time. Also, verify that all systems in the GRS RING have the same settings (when the settings do not agree, the highest value is used).

◆ Keep in mind that the TimeFinder Utility does not support Open Edition HFS datasets.

Processing considerations 49

50



Glossary

This glossary contains terms related to disk storage systems. Many of these terms are used in this manual.

Aabend Termination of a task before its completion because of an error

condition that cannot be resolved by recovery facilities while the task is executing.

adapter Card that provides the physical interface between the director and disk devices (SCSI adapter), director and parallel channels (Bus & Tag adapter), or director and serial channels (serial adapter).

address space The area of virtual storage available for a particular job. In z/OS, an address space can range up to 16 hexabytes of contiguous virtual storage addresses that the system creates for the user. An address space contains user data and programs, as well as system data and programs, some of which are common to all address spaces.

address The unique code assigned to each device, workstation or system connected to a network.

alphanumericcharacter

A letter or a number.

assembler language A symbolic programming language that comprises instructions for basic computer operations which are structured according to the data formats, storage structures, and registers of the computer.


52

Glossary

Bbackup A copy of computer data that is used to recreate data that has been

lost, mislaid, corrupted, or erased. The act of creating a copy of computer data that can be used to recreate data that has been lost, mislaid, corrupted, or erased.

back-up The process of creating a copy of data to ensure against accidental loss.

bandwidth A measure of the data transfer rate of a transmission channel.

batch job A predefined group of processing actions submitted to the system to be performed with little or no interaction between the user and the system.

batch processing A method of running a program or a series of programs in which one or more records (a batch) are processed with little or no action from the user or operator.

BCV device A standard Symmetrix device with special attributes that allow it to independently support applications and processes.

BCV mirror A standard device mirror (one of M2, M3, or M4) that is assigned to the BCV device upon establishing or re-establishing a BCV pair.

BCV pair Consists of a standard device and an associated BCV device.

binary data 1. Any data not intended for direct human reading. Binary data may contain unprintable characters, outside the range of text characters.

2. A type of data consisting of numeric values stored in bit patterns of 0s and 1s. Binary data can cause a large number to be placed in a smaller space of storage.

buffer A portion of storage used to hold input or output data temporarily.

business continuance(BC) processes

Processes that allow customers to access and manage instant copies of Symmetrix standard devices.


Glossary

business continuancevolume (BCV)

A standard Symmetrix device with special attributes that allow it to independently support applications and processes, such as backup operations, restore operations, Decision Support operations, and application testing. BCV devices are available through the EMC TimeFinder software.

Ccache Random access electronic storage used to retain frequently used data

from disk for faster access by the channel.

cache slot Unit of cache equivalent to one track.

cascaded SRDF Cascaded SRDF is a three-site disaster recovery configuration where data from a primary site is synchronously replicated to a secondary site, and then asynchronously replicated to a tertiary site. The core benefit behind a “cascaded” configuration is its inherent capability to continue replicating from the secondary site to the tertiary sites in the event that the primary site goes down. This enables a faster recovery at the tertiary site.

case-sensitive Pertaining to the ability to distinguish between uppercase and lowercase letters.

catalog 1. A directory of files and libraries, with reference to their locations.

2. To enter information about a file or a library into a catalog.

3. The collection of all dataset indexes that are used by the control program to locate a volume containing a specific dataset.

channel 1. A path along which signals can be sent; for example, data channel and output channel.

2. A functional unit, controlled by the processor, that handles the transfer of data between processor storage and local peripheral equipment.

channel director The component in the Symmetrix system that interfaces between the host channels and data storage. It transfers data between the channel and cache.

CKD Count-key-data, a data recording format employing self-defining record formats in which each record is represented by a count area that identifies the record and specifies its format, an optional key area


54

Glossary

that may be used to identify the data area contents, and a data area that contains the user data for the record. CKD can also refer to a set of channel commands that are accepted by a device that employs the CKD recording format.

client 1. A function that requests services from a server, and makes them available to the user. A term used in an environment to identify a machine that uses the resources of the network.

2. A functional unit that receives shared services from a server. See also “client-server.”

client authentication The verification of a client in secure communications where the identity of a server or browser (client) with whom you want to communicate is discovered. A sender's authenticity is demonstrated by the digital certificate issued to the sender.

client-serverrelationship

Any process that provides resources to other processes on a network is a server. Any process that employs these resources is a client. A machine can run client and server processes at the same time.

client-server In TCP/IP, the model of interaction in distributed data processing in which a program at one site sends a request to a program at another site and awaits a response. The requesting program is called a client; the answering program is called a server.

couple dataset A dataset that is created through the XCF couple dataset format utility and, depending on its designated type, is shared by some or all of the z/OS systems in a sysplex. See also “sysplex couple dataset.” A special logical partition that provides high-speed caching, list processing, and locking functions in a sysplex.

coupling facilitychannel

A high bandwidth fiber optic channel that provides the high-speed connectivity required for data sharing between a coupling facility and the central processor complexes directly attached to it.

coupling services In a sysplex, the functions of XCF that transfer data and status between members of a group residing on one or more z/OS systems in the sysplex.

COVD Cache Only Virtual Device (pronounced co-vee-dee). COVD devices are private virtual devices Originally, the term referred to virtual devices used with SRDF/A. Each target R2 had two associated COVDS to track “in progress” and “old” consistent data copies.


Glossary

However, because each COVD required a device number and Global Memory space, SRDF/A was modified to not require COVDS. (The modification was also necessary to make R2s symmetrical to R1s for SRDF/A configuration and for allowing Dynamic SRDF with SRDF/A.) Now, COVDs are required only with Enginuity™ Operating Environment for Symmetrix level 5x70 and earlier.

Currently, the term COVD is also used for diskless, cache-only devices, including virtual devices and thin devices.

DDASD Direct Access Storage Device. This term is common in the z/OS

environment to designate a disk or z/OS volume.

data availability Access to any and all user data by the application.

data definition (DD)statement

A job control statement that describes a dataset associated with a particular job step.

data definition name The name of a data definition (DD) statement that corresponds to a data control block that contains the same name. Abbreviated as ddname.

dataset The major unit of data storage and retrieval, consisting of a collection of data in one of several prescribed arrangements and described by control information to which the system has access.

dataset label 1. A collection of information that describes the attributes of a dataset and is normally stored on the same volume as the dataset.

2. A general term for dataset control blocks and tape dataset labels.

deallocate To release a resource that is assigned to a specific task.

default A value, attribute, or option that is assumed when no alternative is specified by the user.

delayed fast write No existence of room in cache for the data presented by the write operation.

destage The asynchronous write of new or updated data from cache to disk device.


56

Glossary

device A uniquely addressable part of the Symmetrix system that consists of a set of access arms, the associated disk surfaces, and the electronic circuitry required to locate, read, and write data.

device number The value that logically identifies a disk device in a string.

device type The general name for a kind of device; for example, 3390.

diagnostics System level tests or firmware designed to inspect, detect, and correct failing components. These tests are comprehensive and self-invoking.

direct access storagedevice (DASD)

Most commonly known as a magnetic disk device.

director The component in the Symmetrix system that allows the Symmetrix system to transfer data between the host channels and disk devices.

disk director The component in the Symmetrix system that interfaces between cache and the disk devices.

domino mode Symmetrix SRDF domino mode effectively stops all write operations to both primary and secondary volumes if all mirrors of a primary or secondary device fail of if any remote I/O can not be delivered to a secondary volume. If all SRDF links in a link group become unavailable if such a shutdown temporarily halts production processing, domino mode can prevent data integrity exposure caused by rolling disasters.

drive sparing Symmetrix DMX systems have a disk sparing functionality that reserves drives as standby spares. These drives are not user-addressable. Sparing increases data availability without affecting performance. Symmetrix DMX® systems support both dynamic and permanent sparing functions.

dual-initiator A Symmetrix feature that automatically creates a backup data path to the disk devices serviced directly by a disk director, if that disk director or the disk management hardware for those devices fails.

dynamic sparing A Symmetrix feature that automatically transfers data from a failing disk device to an available spare disk device without affecting data availability. This feature supports all non-mirrored devices in the Symmetrix system.


Glossary

EEAV Extended Address Volume. EAV is a volume with more than 65,520

cylinders.

establish A BC process which assigns a BCV device as the next available mirror of a standard device.

Ffast write In Symmetrix systems, a write operation at cache speed that does not

require immediate transfer of data to disk. The data is written directly to cache and is available for later destaging.

FICON An I/O interface based on the Fibre Channel architecture. In this new interface, the ESCON protocols have been mapped to the FC-4 layer, that is, the Upper Level Protocol layer, of the Fibre Channel Architecture.

field replaceable unit(FRU)

A component that is replaced or added by service personnel as a single entity.

Ggateway node A node that is an interface between networks.

gateway In the SAN environment, a gateway connects two or more different remote SANs with each other. A gateway can also be a server on which a gateway component runs.

gigabyte (GB) 109 bytes.

Hhardcopy log In systems with multiple console support or a graphic console, a

permanent record of system activity.

hardwareconfiguration dialog

In z/OS, a panel program that is part of the hardware configuration definition. The program allows an installation to define devices for z/OS system configurations.

hardwaremanagement console

(HMC)

A console used to monitor and control hardware such as the System/390 microprocessors.


58

Glossary

head and diskassembly (hda)

A field replaceable unit in the Symmetrix system containing the disk and actuator.

host bus adapter Also referred to as HBA. A Fibre Channel HBA connection that allows a workstation to attach to the SAN network.

host not ready In this state, the volume responds “not ready” to the host for all read and write operations to that volume.

host Any system that has at least one Internet address associated with it. A host with multiple network interfaces can have multiple Internet addresses associated with it. This is also referred to as a server.

hyper-volumeextension

The ability to define more than one logical volume on a single physical disk device making use of its full formatted capacity. These logical volumes are user-selectable in size. The minimum volume size is one cylinder and the maximum size depends on the disk device capacity and the emulation mode selected.

hypervolume A user-defined storage device allocated within a Symmetrix physical disk.

II/O device An addressable input/output unit, such as a disk device.

I/O group A group containing two SVC nodes defined by the configuration process. The nodes in the I/O group provide access to the vDisks in the I/O group.

identifier (ID) A sequence of bits or characters that identifies a program, device, controller, or system.

IML Initial Microcode program Loading.

incremental restore A business continuance process that reassigns a BCV device as the next available mirror of the standard device with which it was previously paired. The other standard device mirrors are updated with the data that was written to the BCV device during the time of the BCV pair split. The data that was written to the standard device during the split is overwritten with data from the BCV mirror.

index marker Indicates the physical beginning and end of a track.


Glossary

index point The reference point on a disk surface that determines the start of a track.

initial program load(IPL)

The initialization procedure that causes an operating system to begin operation. instruction line. In z/OS, the part of the console screen that contains messages about console control and input errors.

INLINES An EMC-provided host-based cache reporter utility for viewing short and long term cache statistics at the system console.

I/O device An addressable input/output unit, such as a disk device.

ISPF Interactive System Productivity Facility, a software product for IBM mainframes running the z/OS operating system. ISPF primarily provides an IBM terminal interface with a set of menus and panels.

Each panel may include dialogs to run tools on the underlying TSO (Time Sharing Option). Generally, these panels just provide a convenient interface to perform tasks -- most of them execute utility programs that do the actual work. ISPF is user-extensible and it is often used as an application program interface.

JJBOD Just a Bunch Of Disks. A disk group configured without the disk

redundancy of the RAID arrangement. When configured as JBOD, each disk in the disk group is a rank in itself.

JES2 A z/OS subsystem that receives jobs into the system, converts them to internal format, selects them for execution, processes their output, and purges them from the system. In an installation with more than one processor, each JES2 processor independently controls its job input, scheduling, and output processing.

JES3 A z/OS subsystem that receives jobs into the system, converts them to internal format, selects them for execution, processes their output, and purges them from the system. In complexes that have several loosely-coupled processing units, the JES3 program manages processors so that the global processor exercises centralized control over the local processors and distributes jobs to them via a common job queue.

job entry subsystem(JES)

A system facility for spooling, job queuing, and managing the scheduler work area.


60

Glossary

Kkeyword A part of a command operand or SYS1.PARMLIB statement that

consists of a specific character string (such as NAME= on the CONSOLE statement of CONSOLxx).

kilobyte (K) 1024 bytes.

Lleast recently used

algorithm (LRU)The algorithm used to identify and make cache space available by removing the least recently used data.

local volumes Local volumes can reside on an SRDF enabled Symmetrix system, but they do not participate in SRDF activity.

logical partition(LPAR)

A subset of the processor hardware that is defined to support an operating system. An LPAR contains resources (processors, memory, and input/output devices) and operates as an independent system. If hardware requirements are met, multiple logical partitions can exist within a system.

logical partitioning A function of an operating system that enables the creation of logical partitions.

logical volume A user-addressable unit of storage. In the Symmetrix system, the user can define multiple logical volumes on a single physical disk device.

long miss Requested data that is not in cache and is not in the process of being fetched.

Mmaster console

authorityIn a system or sysplex, a console defined with AUTH(MASTER) other than the master console from which all z/OS commands can be entered.

master console In a z/OS system or sysplex, the main console used for communication between the operator and the system from which all z/OS commands can be entered. The first active console with AUTH(MASTER) defined becomes the master console in a system or sysplex.


Glossary

MCS console A non-SNA device defined to z/OS that is locally attached to a z/OS system and is used to enter commands and receive messages.

media The disk surface on which data is stored.

megabyte (MB) 106 bytes.

MII Machine Initiated Interrupt.

mirroring The Symmetrix system maintains identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, the Symmetrix system automatically uses the other disk device(s).

mirrored pair A logical volume comprised of two or more physical devices with all data recorded on each device.

mirroring A Symmetrix system maintains two identical copies of a designated volume on separate disks. Each volume automatically updates during a write operation. If one disk device fails, the Symmetrix system automatically uses the other disk device.

multisystem consolesupport.

Multiple console support for more than one system in a sysplex. Multisystem console support allows consoles on different systems in the sysplex to communicate with each other (send messages and receive commands)

multisystemenvironment

An environment in which two or more z/OS images reside in one or more processors, and programs on one image can communicate with programs on the other images.

multisystem sysplex A sysplex in which two or more z/OS images are allowed to be initialized as part of the sysplex.

Pparallel sysplex A sysplex that uses one or more coupling facilities.

partitioned dataset(PDS) assist

An IBM feature for 3990 Model 6 and 3990 Model 3 with Extended Platform units. PDS Assist improves performance on large, heavily-used partitioned datasets by modifying the directory search process.


62

Glossary

partitioned dataset(PDS)

A dataset on direct access storage that is divided into partitions, called members, each of which can contain a program, part of a program, or data.

partitioned datasetextended (PDSE)

A system-managed dataset that contains an indexed directory and members that are similar to the directory and members of partitioned datasets. A PDSE can be used instead of a partitioned dataset.

password A unique string of characters known to a computer system and to a user, who must specify the character string to gain access to a system and to the information stored within it.

PAV Parallel Access Volume. Implemented within z/OS, Parallel Access Volumes permit multiple applications to access the same information by allowing one I/O to take place for each base unit control block (UCB) and simultaneously by assigning alias UCBs to each additional I/O.

These alias UCBs allow parallel I/O access for volumes. Applicable Enginuity Operating Environment releases provide support for:

• Static PAVs

• Dynamic PAVs

Static PAVs provided the base functionality. Static PAV's are defined by attempting to anticipate how many aliases might be needed to avoid the I/Os queuing. Under static PAVs, a volume could be accessed through its base address or through alias addresses defined to that base. The obvious drawback with static PAVs is that you may waste resources by defining too many aliases or have an insufficient amount by defining too few.

Dynamic PAVs allow fewer aliases to be defined within a logical control unit but allowed the reassignment of aliases to base addresses other than the base to which the alias was originally assigned. With dynamic PAV, aliases are applied to the base UCBs (devices) that need them the most. This enables the z/OS Workload Manager to assign an alias to a device on the fly.

peer-to-peer remotecopy

A hardware-based remote copy option that provides a synchronous volume copy across storage systems for disaster recovery, device migration, and workload migration.


Glossary

permanent sparing Permanent sparing is a process that permanently replaces a failing drive with a spare drive via configuration change. The spare drive must be the same block size, capacity, speed, and in location that conforms to the configuration rules for distributing mirrors. Permanent sparing is used in combination with all protection types. The failed drive becomes a not ready spare in the spare pool and can be replaced at a later time. There should be other spares available should another drive fail. If the process cannot identify a spare in a good location, the dynamic sparing process will take place for RAID 1, RAID 5, and unprotected volumes. See also “drive sparing” and ”dynamic sparing.”

primary SRDF volumes Primary (source, R1) volumes contain production data that is mirrored in a different Symmetrix system. Primary volumes are also referred to as source or R1 volumes. Updates to a primary volume are automatically mirrored to a secondary (target, R2) volume in the remote Symmetrix system.

program function key(PFK)

A key on the keyboard of a display device that passes a signal to a program to call for a particular program operation.

program status word(PSW)

A doubleword in main storage used to control the order in which instructions are executed, and to hold and indicate the status of the computing system in relation to a particular program.

promotion The process of moving data from a track on the disk device to cache. See also “stage.”

Qquery A command that reports the state of all the BCV devices in the

system.

RR21 An Enginuity device type in which the target of one SRDF

relationship is simultaneously the source of another SRDF relationship.

R22 An Enginuity device type that is an R2 device having two RDF mirrors. Each R2 mirror is paired with a different R1 mirror and only one of the R2 mirrors can be RW on the link at a time.


64

Glossary

RACF Resource Access Control Facility, now known as Security Server. The IBM-licensed external security manager, which is primarily intended to work with z/OS software by means of the SAF interface. External security managers from other vendors include CA-ACF2 and CA-Top Secret.

RAID Redundant Array of Independent Disks.

RAID 0 Provides data striping (spreading out blocks of each file across multiple disk drives), but does not provide redundancy. This improves performance but does not deliver fault tolerance. If one drive fails then all data in the array is lost.

RAID 1 Provides disk mirroring at twice the read transaction rate of single disks and the same write transaction rate as single disks.

RAID 10 The combination of RAID 0 and RAID 1, also known as RAID 0+1, RAID 0 & 1, and RAID 1/0. The combination provides enhanced data availability through disk mirroring and enhanced I/O performance through disk striping.

RAID 5 Striped array with rotating parity. To relieve the problem of disk bottleneck, parity information is distributed across all data drives in level 5. This distributed parity increases write performance.

RAID 6 Provides a dedicated, asynchronous cached parity drive that has independent data and control paths, and can receive cached transfers through an independent asynchronous parity bus, a cache bus, or an external bus.

RAID S A Symmetrix feature that provides parity data protection on the disk device-level using physical parity volumes. A RAID S group consists of 3 data drives and 1 parity drive. The RAID S option can be also used with Hyper-Volume Extension to establish distributed parity.

read hit Data requested by the read operation is in cache.

read miss Data requested by the read operation is not in cache.

re-establish A BC process which reassigns a BCV device as the next available mirror of the standard device with which it was previously paired. The BCV mirror is updated with the data that was written to the


Glossary

standard device during the period that the BCV pair was split. The data that was written to the BCV device during the split is overwritten by data from the standard device.

restore A BC process which reassigns a BCV device as the next available mirror of the standard device with which it was previously paired. The other standard device mirrors receive a full data copy from the BCV mirror.

resynchronization A track image copy from the primary volume to the secondary volume of only the tracks which have changed since the volume was last in duplex mode.

REXX REstructured eXtended eXecutor, an interpreted, high-level programming language which was originally developed at IBM. REXX was designed to be both easy to learn and easy to maintain.

SSAF System Authorization Facility. A generic Security Interface in z/OS

software that works with an independent external security manager such as Security Server (or RACF).

scrubbing The background process of reading, checking the error correction bits, and writing corrected data back to the source.

secondary device One of the devices in a dual copy or remote copy logical volume pair that contains a duplicate of the data on the primary device. Unlike the primary device, the secondary device may only accept a limited subset of channel commands.

secondary SRDFvolumes

Secondary (target, R2) volumes contain a mirrored copy of data from a primary volume. Secondary volumes are also referred to as target or R2 volumes.

short miss Requested data is not in cache, but is in the process of being fetched.

single-system sysplex A sysplex in which only one z/OS system is allowed to be initialized as part of the sysplex. In a single-system sysplex, XCF provides XCF services on the system but does not provide signalling services between z/OS systems. See also “multisystem sysplex.”

software 1. All or part of the programs, procedures, rules, and associated documentation of a data processing system.


66

Glossary

2. A set of programs, procedures, and, possibly, associated documentation concerned with the operation of a data processing system. For example, compilers, library routines, manuals, circuit diagrams. Contrast with hardware.

spare drive Symmetrix DMX systems have a disk sparing functionality that reserves drives as standby spares. These drives are not user-addressable. Sparing increases data availability without affecting performance. Symmetrix DMX systems support both dynamic and permanent sparing functions. See also “dynamic sparing” and ”permanent sparing.”

spare pool Symmetrix DMX systems have a disk sparing functionality that reserves drives as standby spares. The collection of spare drives is called the spare pool. See also “drive sparing,” and ”permanent sparing.”

split A BC process which removes the BCV mirror from the existing BCV pair and assigns the BCV mirror back to its original device address. The BCV device then holds an instant copy of the data from the standard device.

SRDF Symmetrix Remote Data Facility. SRDF consists of the microcode and hardware required to support Symmetrix remote mirroring.

SRDF/AutomatedReplication (SRDF/AR)

SRDF/Automated Replication (SRDF/AR) is an automation solution that uses both SRDF and TimeFinder to provide a periodic asynchronous replication of a restartable data image. Use a single-hop SRDF/AR configuration that permits controlled data loss (depending on the cycle time). If the same protection is required over greater distances, a multi-hop SRDF/AR configuration can provide long distance disaster restart with zero data loss at a middle or “bunker” site.

stage The process of writing data from a disk device to cache. See also “promotion” and ”destage.”

standard device A Symmetrix device.

storage administrator A person in the data processing center who is responsible for defining, implementing, and maintaining storage management policies.


Glossary

storage area network A managed, high-speed network that enables any-to-any interconnection of heterogeneous servers and storage systems.

storage class A collection of storage attributes that identify performance goals and availability requirements, defined by the storage administrator, used to select a device that can meet those goals and requirements.

storage control The component in the Symmetrix system that connects the Symmetrix system to the host channels. It performs channel commands and communicates with the disk adapters and cache.

storage managementsubsystem (SMS)

A facility used to automate and centralize the management of storage. Using SMS, a storage administrator describes data allocation characteristics, performance and availability goals, backup and retention requirements, and storage requirements to the system through data class, storage class, management class, storage group, and ACS routine definitions.

string A series of connected disk devices sharing the same disk director.

Symmetrix multi mirrorfacility (SMMF)

A business continuance solution which allows customers to use special devices that contain instant copies of Symmetrix devices while the principal devices are on-line for regular Symmetrix® operation.

sysplex coupledataset

A couple dataset that contains sysplex-wide data about systems, groups, and members that use XCF services. All z/OS systems in a sysplex must have connectivity to the sysplex couple dataset. See also “couple dataset.”

sysplex timer An IBM unit that synchronizes the time-of-day (TOD) clocks in multiple processors or processor sides.

sysplex A set of z/OS systems communicating and cooperating with each other through certain multisystem hardware components and software services to process customer workloads. See also “parallel sysplex.”

system console In z/OS, a console attached to the processor controller used to initialize a z/OS system.

system managementfacilities (SMF)

An optional control program feature of z/OS that provides the means for gathering and recording information that can be used to evaluate system usage.


68

Glossary

system modificationprogram extended

(SMP/E)

In addition to providing the services of SMP, SMP/E consolidates installation data, allows more flexibility in selecting changes to be installed, provides a dialog interface, and supports dynamic allocation of datasets.

system A z/OS image together with its associated hardware, which collectively are often referred to simply as a system, or z/OS system.

Tterminal user In systems with time-sharing, anyone who is eligible to log on.

terminal A device, usually equipped with a keyboard and some kind of display, capable of sending and receiving information over a link.

TSO Time Sharing Option, an interactive, time-sharing environment for IBM mainframe operating systems. “Time-sharing” means that many users can access z/OS concurrently but each is unaware that the operating system is being accessed by others - so it appears to each user that he or she is the only user on the system.

TSO is most commonly used by system programmers and administrators because it provides because it provides a number of facilities useful to anyone maintaining an operating environment.

Vvalidate Action that makes all tracks for a source volume valid on a target

volume.

VERIFY A command that verifies that a BCV synchronization process has been successfully completed.

volume 1. That portion of a single unit of storage which is accessible to a single read/write mechanism, for example, a drum, a disk pack, or part of a disk storage module.

2. A recording medium that is mounted and demounted as a unit, for example, a reel of magnetic tape, a disk pack, a data cell.

VTOC Volume Table of Contents. The area of the disk used to store the directory of components held on that volume. This also contains entries for user catalogs.


Glossary

Wwait state Synonymous with waiting time.

waiting time 1. The condition of a task that depends on one or more events in order to enter the ready condition.

2. The condition of a processing unit when all operations are suspended.

write hit Existence of room in cache for the data presented by the write operation.

write miss No existence of room in cache for the data presented by the write operation.

write-to-operator(WTO) message

A message sent to an operator console informing the operator of errors and system conditions that may need correcting.

write-to-operator-with-reply (WTOR)

message

A message sent to an operator console informing the operator of errors and system conditions that may need correcting. The operator must enter a response.


70

Glossary


Index

BBCVs 15Business Continuance Volumes 15

CCATALOG CLEANUP requests 17CATALOG command 49CATALOG parameter

TimeFinder Utility 27CATALOG statement 27comment syntax 24conditioning volumes 15

DDEBUG parameter

TimeFinder Utility 29DEBUG statement 29descriptor codes 32DS1VOLSQ field 41

EEDF catalogs 23EMC Consistency Groups for z/OS 14EMC Mainframe Enablers 14EMC publications 9EMC ResourcePak Base 19EMC TimeFinder/Mirror 15EMCTOOLS 19

GGDG base entries 40

GDG dataset 42GDG datasets 17generation data group base options 40GRS environment 49GRSCNFxx parmlib member 49

IIDCAMS model statement 15IDCAMS statements statements, overview 45IDCAMS, definition 15IDF data space 22IDF datasets 22ISPF interface

requirements 19

Lline#- ,IDCAMS statements statements 46

MMESSAGES parameter 30MESSAGES statement 30model statements 24, 45multi-volume and general processing issues 49multivolume datasets 22

Nname, IDCAMS model statements 45non-VSAM files 15non-VSAM files, recataloging 15


72

Index

OOpen Edition HFS datasets 49Open Edition HFS datasets, non-support 49order of processing 17

PPROCESS statement 33PROCESS statement, TimeFinder Utility 33processing overview, TimeFinder Utility 16processing statements 24

Rrecataloging non-VSAM files 15recataloging VSAM files 15RELABEL 15RELABEL processing 17RELABEL statement 15, 34RELABEL statement, TimeFinder Utility 34RENAME parameter 36RENAME statement 36reserved datasets 31ResourcePak Base for z/OS 14

SSIMULATE statement 38SIMULATE statement, TimeFinder Utility 38SOURCE CATALOG MULTI VOLUME(YES) 40source dataset catalogs 40SOURCECATALOG command 49SOURCECATALOG parameter 39SOURCECATALOG statement 39SRDF Host Component for z/OS 14standard devices 15suppressing warning messages 30syntax diagrams 24syntax of comments 24SYSCTLG 27SYSCTLG keyword 27

TTFINPUT files 22TFMODEL files 22TimeFinder Utility 14

CATALOG statement 27

DEBUG statement 29MESSAGES statement 30model statements 45PROCESS statement 33processing statements 24RELABEL statement 34RENAME parameter 36SIMULATE statement 38SOURCECATALOG statement 39

TimeFinder Utility, processing overview 16TimeFinder Utility, purpose 15TimeFinder/Clone Mainframe SNAP Facility 14TimeFinder/Mirror for z/OS 14

Uunmatched datasets warning messages 31

VVSAM files 15VSAM files, recataloging 15

Wwarning messages, suppressing 30


Documents

EMC TimeFinder Utility for z/OSEMC Corporation Corporate Headquarters : Hopkinton, MA 01748-9103 1-508-435-1000 EMC® TimeFinder® Utility for z/OS Version 7.0 Product Guide …