Hitachi Tiered Storage Manager for Mainframe User Guide

7/23/2019 Hitachi Tiered Storage Manager for Mainframe User Guide

http://slidepdf.com/reader/full/hitachi-tiered-storage-manager-for-mainframe-user-guide 1/353

Hitachi Command Suite

Tiered Storage Manager for MainframeUser Guide

MK-92HC207-0

Document Organization

Product Version

Getting Help

Contents



©2014 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means,electronic or mechanical, including photocopying and recording, or stored in a database or retrievalsystem for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd., reserves the right to make changes to this document at any time without notice andassumes no responsibility for its use. This document contains the most current information availableat the time of publication. When new or revised information becomes available, this entire

document will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the mostrecent product announcement for information about feature and product availability, or contactHitachi Data Systems Corporation at https://portal.hds.com

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products isgoverned by the terms of your agreements with Hitachi Data Systems Corporation.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. HitachiData Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States andother countries.

Archivas, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft,

Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform areregistered trademarks of Hitachi Data Systems.

AIX, AS/400, DB2, Domino, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON,FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA,z/OS, z9, z10, zSeries, z/VM, and z/VSE are registered trademarks or trademarks of InternationalBusiness Machines Corporation.

All other trademarks, service marks, and company names in this document or web site areproperties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

Notice on Export Controls. The technical data and technology inherent in this Document may besubject to U.S. export control laws, including the U.S. Export Administration Act and its associatedregulations, and may be subject to export or import regulations in other countries. Reader agrees tocomply strictly with all such regulations and acknowledges that Reader has the responsibility toobtain licenses to export, re-export, or import the Document and any Compliant Products.

ii

Hitachi Tiered Storage Manager for Mainframe User Guide

https://portal.hds.com/



Contents

Preface.................................................................................................. xiIntended audience....................................................................................................xiiProduct version........................................................................................................ xiiRelease notes...........................................................................................................xiiDocument revision level............................................................................................ xii

Document organization.............................................................................................xiiRelated documents..................................................................................................xivDocument conventions............................................................................................. xvConventions for storage capacity values.....................................................................xv

Accessing product documentation.............................................................................xviGetting help............................................................................................................ xviComments..............................................................................................................xvii

1 Overview of Hitachi Tiered Storage Manager for Mainframe..................... 1-1 About Tiered Storage Manager for Mainframe........................................................... 1-2Overview of the Tiered Storage Manager for Mainframe functionality..........................1-4

Concepts of terms used in Tiered Storage Manager for Mainframe..............................1-5 About tiering policy groups................................................................................1-5 About tiering policies........................................................................................ 1-6 About tiering policy levels..................................................................................1-8 About the new-page assignment tier..................................................................1-9

Prerequisites for Tiered Storage Manager for Mainframe..........................................1-10System configuration of Tiered Storage Manager for Mainframe............................... 1-11

About files used by Tiered Storage Manager for Mainframe......................................1-12Overview of files used by Tiered Storage Manager for Mainframe.......................1-12Workflow f or files used in Tiered Storage Manager for Mainframe...................... 1-12

Workflow for using Tiered Storage Manager for Mainframe...................................... 1-13

2 Installation and setup........................................................................... 2-1Overview of installation and setup............................................................................2-3Installing Tiered Storage Manager for Mainframe...................................................... 2-4

Workflow f or during installation.........................................................................2-4Transferring the load module to a host machine................................................. 2-5Performing an installation using SMP/E...............................................................2-8Installing directly from the provided datasets in the target library........................ 2-9

iii




Library datasets to be registered after the installation........................................2-10Settings required for using CLI commands (registration for authentication)...............2-11

Registering the load library for LINKLIB and the KTQRYSMS command forauthentication................................................................................................ 2-11Example of dynamically linking the LINKLIB load library to LNKLST.................... 2-12

Setting RACF security for CLI commands................................................................ 2-13Settings for using environment configuration commands..........................................2-14Registering a user SVC.......................................................................................... 2-15

Registering a user SVC using the KTALCSVC command..................................... 2-15Registering a user SVC using the IEASVCxx parmlib member............................. 2-17Setting the operating environment for Tiered Storage Manager for Mainframe (settingenvironment variables or system symbols)..............................................................2-18

About the operating environment for Tiered Storage Manager for Mainframe...... 2-18List of operating environment setting items for Tiered Storage Manager forMainframe......................................................................................................2-19Setting the operating environment by using environment variables.....................2-19Setting the operating environment by using system symbols..............................2-21

Settings required to use Tiered Storage Manager for Mainframe on the ISPF panel....2-22Using DD names to concatenate the libraries required for executing the KTSTARTcommand.......................................................................................................2-23Using the ALTLIB command and LIBDEF service to concatenate the libraries requiredfor executing the KTSTART command.............................................................. 2-24

Registering licenses...............................................................................................2-25Workflow for registering a license.................................................................... 2-25Creating a license information dataset..............................................................2-26Registering a license by using a license key file.................................................2-27Registering a license by entering a license key..................................................2-29

Verifying the setup information.............................................................................. 2-31Overview of verifying the setup information......................................................2-31

Verifying the setup information........................................................................2-31Preparing to use Tiered Storage Manager for Mainframe..........................................2-32

Calculating required memory........................................................................... 2-32Settings required for collecting event logs.........................................................2-32

Backing up Tiered Storage Manager for Mainframe to the distribution library...... 2-33Notes on setting up Tiered Storage Manager for Mainframe when Business ContinuityManager is already installed...................................................................................2-34

Notes on registering a user SVC if Business Continuity Manager is installed.........2-35Notes on setting environment variables or system symbols if Business ContinuityManager is installed........................................................................................ 2-35

Prerequisite user SVC versions for Tiered Storage Manager for Mainframe................ 2-36Notes for when multiple versions of Tiered Storage Manager for Mainframe coexist... 2-36

Notes on collection of CLI command execution logs...........................................2-36

3 Tiered Storage Manager for Mainframe operations when using the ISPF

panel...................................................................................................3-1Operation description method for the ISPF panels..................................................... 3-2Workflow for when defining and checking tiering policy groups when using the ISPFpanel..................................................................................................................... 3-2Starting Tiered Storage Manager for Mainframe and displaying the main panel........... 3-4Basic ISPF panel settings of Tiered Storage Manager for Mainframe........................... 3-4Defining tiering policy groups when using the ISPF panel...........................................3-5

Scanning storage systems when using the ISPF panel......................................... 3-5

iv




Creating a tiering policy information CSV file when using the ISPF panel...............3-7Defining tiering policy groups when using the ISPF panel.................................... 3-8

Applying tiering policies when using the ISPF panel.............................................3-8 Verification after scanning storage systems when using the ISPF panel.......................3-9

Checking volume information for the scanned storage system when using the ISPFpanel...............................................................................................................3-9Checking pool information for the scanned storage system when using the ISPFpanel............................................................................................................. 3-11

Verification after defining a tiering policy group when using the ISPF panel...............3-13 Verifying definition information for the tiering policy group when using the ISPFpanel............................................................................................................. 3-14

Verifying storage system information (summary) for the tiering policy group whenusing the ISPF panel....................................................................................... 3-15Checking SMS storage groups belonging to a tiering policy group when using theISPF panel......................................................................................................3-16

Verifying volume information for the tiering policy group when using the ISPF panel.....................................................................................................................3-17

Verifying pool information for the tiering policy group when using the ISPF panel3-19Frequently used checking methods when using the ISPF panel.................................3-22

Checking whether the tiering policies are applied to the storage system when usingthe ISPF panel................................................................................................3-22Checking the tier relocation status for volumes when using the ISPF panel......... 3-25Checking whether the usage of any pool equals or exceeds the threshold when usingthe ISPF panel................................................................................................3-26

About changing tiering policy groups when using the ISPF panel.............................. 3-28Changing a tiering policy when using the ISPF panel......................................... 3-28

Adding a volume to a tiering policy group when using the ISPF panel.................3-29Deleting a specific volume from a tiering policy group when using the ISPF panel3-30Modifying the tiering policy information CSV file when using the ISPF panel........3-31

Convenient use of list panels..................................................................................3-31Sorting items..................................................................................................3-32Filtering displayed information.........................................................................3-32Searching character strings............................................................................. 3-33

Positioning the cursor at a specific line in a sorted field..................................... 3-33Setting an action in multiple AC fields...............................................................3-34

Customizing the ISPF panels..................................................................................3-35Setting the command line location................................................................... 3-35Setting the number of displayed function keys.................................................. 3-35Highlighting available point-and-shoot fields..................................................... 3-35

4 Tiered Storage Manager for Mainframe operations when using the CLI.....4-1Defining and verifying a tiering policy group when using the CLI commands............... 4-2Defining tiering policy groups when using the CLI commands.................................... 4-3

Checking volume information when using the CLI commands.............................. 4-3

Scanning the storage system when using the CLI commands...............................4-5Creating a tiering policy information CSV file when using the CLI commands........ 4-7Defining tiering policy groups when using the CLI commands.............................. 4-7

Applying tiering policies when using the CLI commands...................................... 4-9 Verification after defining a tiering policy group when using the CLI commands.........4-11

Verifying tiering policies when using the CLI commands.................................... 4-11Checking the progress of tier relocation when using the CLI commands..............4-12Checking volume I/O performance...................................................................4-14

v




About changing tiering policy groups when using the CLI commands........................4-15Changing a tiering policy when using the CLI commands................................... 4-15

Adding a volume to a tiering policy group when using the CLI commands...........4-15Deleting a specific volume from a tiering policy group when using the CLI commands..................................................................................................................... 4-17

5 ISPF panels .........................................................................................5-1Panel relationships of Tiered Storage Manager for Mainframe.................................... 5-3Common items in the panel..................................................................................... 5-4

About the layout of the panels...........................................................................5-4 About the action bar......................................................................................... 5-4 About the AC and COMMAND fields....................................................................5-5 About point-and-shoot field............................................................................... 5-7 About the display unit..................................................................................... 5-12

Device Scan Scope panel ...................................................................................... 5-12Edit Def aults panel ...............................................................................................5-13Error Code Help panel .......................................................................................... 5-14Exception Message List panel ................................................................................5-15Main panel............................................................................................................5-16

Main panel (common)..................................................................................... 5-16

Installation Management area..........................................................................5-17Set Defaults area ...........................................................................................5-18Storage System List area.................................................................................5-19Policy CSV List area.........................................................................................5-20Tiering Policy Group List area.......................................................................... 5-21

Manage Licenses panel .........................................................................................5-22Policy ID Entry panel ............................................................................................5-22Pool Selection List panel ....................................................................................... 5-23Pool Status Detail panel ........................................................................................5-24Setting Information panel...................................................................................... 5-25Tiering Policy Group Definition panel...................................................................... 5-26Tiering Policy Group Pool List panel........................................................................5-27

Tiering Policy Group Pool Status Detail panel.......................................................... 5-28Tiering Policy Group Storage Group List panel.........................................................5-30Tiering Policy Group Summary panel...................................................................... 5-31Tiering Policy Group Volume List panel................................................................... 5-33Tiering Policy Group Volume Status Detail panel......................................................5-35

Volume Selection List panel................................................................................... 5-36 Volume Status Detail panel.................................................................................... 5-37

6 CLI commands..................................................................................... 6-1List of CLI Commands............................................................................................. 6-2CLI command coding format....................................................................................6-3

REXX external routine coding format..................................................................6-4TSO/E command coding format......................................................................... 6-4OS console command coding format.................................................................. 6-5

REXX external routine details...................................................................................6-5KTACTTPG....................................................................................................... 6-5KTDCTDEV.......................................................................................................6-6KTDCTTPG.......................................................................................................6-8KTGETHDA.......................................................................................................6-9

vi




KTIMPORT..................................................................................................... 6-12KTLOAD.........................................................................................................6-14KTQRYDEV.....................................................................................................6-17KTQRYRLC..................................................................................................... 6-19KTQRYTPG.....................................................................................................6-21KTQSTATS..................................................................................................... 6-23KTSCAN......................................................................................................... 6-25KTSTORE....................................................................................................... 6-28

KTWTOMSG................................................................................................... 6-32TSO/E command details........................................................................................ 6-34KTCONMSG.................................................................................................... 6-34KTENV........................................................................................................... 6-36KTERCODE.....................................................................................................6-37KTINSCHK......................................................................................................6-39KTSLEEP........................................................................................................ 6-41

OS console command details................................................................................. 6-42KTALCSVC......................................................................................................6-42KTDSPENV..................................................................................................... 6-43KTSETENV......................................................................................................6-45

7 Files used by Tiered Storage Manager for Mainframe...............................7-1File naming conventions used by Tiered Storage Manager for Mainframe....................7-2Format of datasets used by Tiered Storage Manager for Mainframe............................7-3Disk space requirements of configuration files...........................................................7-3Format of tiering policy information CSV files............................................................7-4

Descriptive conventions of tiering policy information CSV files..............................7-4Syntax of tiering policy information CSV files...................................................... 7-4Configuration example of tiering policy groups and example of specifications in thecorresponding tiering policy information CSV file.................................................7-8Examples of changing a tiering policy information CSV file...................................7-9

8 REXX variable structures....................................................................... 8-1List of REXX variable structures................................................................................8-2Message structure...................................................................................................8-2Host-discovered array index structure...................................................................... 8-3Host-discovered array structure............................................................................... 8-4Tiering policy group structure.................................................................................. 8-9Device information structure..................................................................................8-10

9 Collecting trace information and logs......................................................9-1Information that can be used for troubleshooting......................................................9-2Collecting trace information.....................................................................................9-2

Collecting trace information when using scripts...................................................9-2

Collecting trace information when using TSO/E...................................................9-2Log types for Tiered Storage Manager for Mainframe................................................ 9-3Collecting event logs............................................................................................... 9-4

How to collect event logs.................................................................................. 9-4 About event log output datasets........................................................................ 9-4

Collecting event logs by using the system logger service............................................9-5Settings for collecting event logs when using the system logger service................9-5

vii




Setting LOGR couple data sets...........................................................................9-6Defining the SMS for the system logger service...................................................9-6Defining a log stream........................................................................................9-6Setting access privileges for system logger resources.......................................... 9-7Starting the system logger service..................................................................... 9-7Parameters specified when a log stream is defined............................................. 9-8JCL example for confirming a log stream.......................................................... 9-10JCL example for deleting a log stream..............................................................9-10

Preventing the event log from becoming full when the system logger service is used..................................................................................................................... 9-10Re-defining the log stream when the event log is full........................................ 9-11Restarting the system logger service and re-defining the log stream when the eventlog is full........................................................................................................9-11Disk space requirements for the event log when the system logger service is used.....................................................................................................................9-12Overview of the event log data output tool.......................................................9-13Outputting logs by using the event log data output tool.....................................9-13Control statements for the event log data output tool........................................9-14Output format of the event log data output tool................................................9-15

Collecting event logs without using the system logger service.................................. 9-16 Allocating log datasets without using the system logger service......................... 9-16Writing to a log dataset without using the system logger service........................9-17Disk space requirements for the event log when the system logger service is notused.............................................................................................................. 9-18

Collecting ISPF logs...............................................................................................9-19Checking ISPF logs......................................................................................... 9-19Preventing the ISPF log dataset from becoming full...........................................9-19

Collecting the CLI command-execution log..............................................................9-20Extracting CLI command-execution logs by using an ISPF editor........................ 9-20Extracting CLI command-execution logs by using an extraction script................. 9-21

A XML document type definitions for configuration files..............................A-1

Elements common to configuration files................................................................... A-2 APIInfo element...............................................................................................A-2DiskDevice element.......................................................................................... A-2

Elements in the disk configuration definition file........................................................A-3HostDiscoveredArray element............................................................................A-3SoftwareKeys element...................................................................................... A-3POOL element..................................................................................................A-4PoolTier element.............................................................................................. A-4HostAddressedDisk element.............................................................................. A-5

Elements in the tiering policy group definition file..................................................... A-5TieringPolicyGroup element...............................................................................A-5TieringPolicy element........................................................................................A-6

Example of files used by Tiered Storage Manager for Mainframe................................A-6Example of the specifications in a tiering policy information CSV file.....................A-7Example of a disk configuration definition file that is generated........................... A-7Example of a tiering policy group definition file that is generated.........................A-8

B Commands that can be used in the ISPF panels......................................B-1ERRCODE...............................................................................................................B-2

viii




FILTER...................................................................................................................B-2FIND......................................................................................................................B-3LOCATE................................................................................................................. B-3RFIND....................................................................................................................B-4SELECT..................................................................................................................B-4SORT.....................................................................................................................B-5How to specify the search or filter conditions in ISPF panels...................................... B-6

C Sample scripts......................................................................................C-1List of sample scripts.............................................................................................. C-2Details about sample scripts....................................................................................C-3

KTDEMO00 (Create a disk configuration definition file)........................................C-3KTDEMO01 (Display the contents of the disk configuration definition file).............C-5KTDEMO02 (Create a tiering policy group definition file)......................................C-8KTDEMO03 (Display the contents of the tiering policy group definition file).........C-10KTDEMO04 (Display the volume information)....................................................C-11KTDEMO05 (Change the tiering policy of a volume back to the default)..............C-14KTDEMO10 (Apply the tiering policy)................................................................C-15KTDEMO11 (Check the tiering policy)...............................................................C-16KTDEMO12 (Check the page relocation status)................................................. C-18

KTDEMO13 (Check the relocation progress)......................................................C-20KTDEMO14 (Check I/O performance information)............................................. C-26

D Upgrading Tiered Storage Manager for Mainframe..................................D-1Workflow for upgrading Tiered Storage Manager for Mainframe.................................D-2Preparation for upgrading Tiered Storage Manager for Mainframe..............................D-3

Checking the setting values of the operating environment...................................D-3Creating a back up............................................................................................ D-3Deleting the user SVC by using the KTALCSVC environment setup command........D-4Deleting the user SVC from the IEASVCxx parmlib member.................................D-4Removing the library linkage.............................................................................D-5

Upgrading Tiered Storage Manager for Mainframe.................................................... D-6

E Modifying the sample JCL......................................................................E-1 Values used in the sample JCL modification examples................................................E-2 ALLOUPLD (creating datasets used for transfers)...................................................... E-2RECVUPLD (TSO/E RECEIVE processing).................................................................. E-4HDSKTSIN (performing installation without using SMP/E).......................................... E-5SMPALLOC (allocating SMP/E datasets).................................................................... E-7HDSKT1AL (allocating the distribution library and target library).................................E-9HDSKT2DF (defining the distribution library and target library).................................E-11HDSKT3RC (SMP/E RECEIVE processing)................................................................ E-15HDSKT4AP (creating target libraries)...................................................................... E-16

HDSKT5AC (creating distribution libraries).............................................................. E-18

F Command syntax descriptions................................................................F-1Command syntax descriptions..................................................................................F-2

Acronyms and abbreviations

ix




Glossary

Index

x




Preface

This document describes how to install, configure, and use the Hitachi TieredStorage Manager for Mainframe.

Hereafter, the above product is simply called Tiered Storage Manager for Mainframe. In figures, the product is indicated as HTSM for MF.

This preface includes the following information:

□ Intended audience

□ Product version

□ Release notes

□ Document revision level

□ Document organization

□ Related documents

□ Document conventions

□ Conventions for storage capacity values

□ Accessing product documentation

□Getting help

□ Comments

Preface xi




Intended audience

This document is intended for those who:

• Want to create a storage system that uses Tiered Storage Manager forMainframe, and to operate the system at high performance.

This document is intended for readers who are familiar with the following:

• z/OS functionality• Hitachi Virtual Storage Platform and Hitachi Dynamic Tiering for

Mainframe

Product version

This document revision applies to Hitachi Tiered Storage Manager forMainframe version 8.0.0 or later.

Release notes

Read the release notes before installing and using this product. They maycontain requirements or restrictions that are not fully described in thisdocument or updates or corrections to this document.

Document revision level

Revision Date Description

MK-92HC207-00 July 2013 Initial Release

MK-92HC207-01 April 2014 Revision 1, supersedes and replaces

MK-92HC207-00

Document organization

The following table provides an overview of the contents and organization of this document. Click the chapter title in the left column to go to that chapter.The first page of each chapter provides links to the sections in that chapter.

Chapter/Appendix Description

Chapter 1, Overview of Hitachi Tiered Storage

Manager for Mainframe on page 1-1

Provides an overview of Tiered

Storage Manager for Mainframe.

Chapter 2, Installation and setup on page 2-1 Describes how to install and set upTiered Storage Manager forMainframe.

xii Preface




Chapter/Appendix Description

Chapter 3, Tiered Storage Manager forMainframe operations when using the ISPF panelon page 3-1

Describes how to use the ISPF panelsto operate Tiered Storage Manager forMainframe.

Chapter 4, Tiered Storage Manager forMainframe operations when using the CLI onpage 4-1

Describes how to use CLI commandsto operate Tiered Storage Manager forMainframe.

Chapter 5, ISPF panels on page 5-1 Describes transition, operationmethods, and displayed items of theISPF panel in Tiered Storage Managerfor Mainframe.

Chapter 6, CLI commands on page 6-1 Describes the functionality of thecommands that can be used from theCLI of Tiered Storage Manager forMainframe.

Chapter 7, Files used by Tiered Storage Managerfor Mainframe on page 7-1

Describes the formats of files that areused for Tiered Storage Manager forMainframe.

Chapter 8, REXX variable structures on page8-1

Describes the REXX variable structuresused by Tiered Storage Manager forMainframe.

Chapter 9, Collecting trace information and logson page 9-1

Describes the trace information andlogging of Tiered Storage Manager forMainframe.

Appendix A, XML document type definitions forconfiguration files on page A-1

Describes the structure of configuration files of Tiered StorageManager for Mainframe.

Appendix B, Commands that can be used in theISPF panels on page B-1

Describes the commands that can beused in the ISPF panels of TieredStorage Manager for Mainframe.

Appendix C, Sample scripts on page C-1 Describes the sample scripts of TieredStorage Manager for Mainframe.

Appendix D, Upgrading Tiered Storage Managerfor Mainframe on page D-1

Describes how to update the versionof Tiered Storage Manager forMainframe.

Appendix E, Modifying the sample JCL on pageE-1

Provides examples of modifying thesample job control language (JCL) of Tiered Storage Manager forMainframe.

Appendix F, Command syntax descriptions onpage F-1

Describes the symbols used in syntaxexplanations and the syntax elementsthat are used.

Acronyms and abbreviations on page Acronyms-1 Defines the acronyms andabbreviations used in this document.

Glossary on page Glossary-1 Defines the special terms used in thisdocument.

Index Lists the topics in this document inalphabetical order.

Preface xiii




Related documents

• A manual and document related to Tiered Storage Manager forMainframe:

¢ Hitachi Command Suite Tiered Storage Manager for MainframeMessages, MK-92HC210

¢ Hitachi Tiered Storage Manager for Mainframe Release Notes,

RN-92HC208• Manuals related to Business Continuity Manager:

¢ Hitachi Business Continuity Manager User Guide, MK-94RD247

¢ Hitachi Business Continuity Manager Messages, MK-94RD262

¢ Hitachi Business Continuity Manager Installation Guide, MK-95HC104

¢ Hitachi Business Continuity Manager Reference Guide, MK-96HC135

• A manual related to Hitachi Command Suite products:

¢ Hitachi Command Suite Software User Guide, MK-90HC172

• Manuals related to storage systems:

¢ Hitachi Command Control Interface User Guide, MK-90RD7010

¢ Hitachi Virtual Storage Platform Provisioning Guide for Mainframe,MK-90RD7021

¢ Hitachi Virtual Storage Platform Hitachi Storage Navigator User Guide,MK-90RD7027

• Manuals related to z/OS:

¢ MVS Initialization and Tuning Reference, SA22-7592

¢ MVS Programming: Assembler Services Reference, SA22-7606,SA22-7607

¢

MVS Setting Up a Sysplex , SA22-7625¢ MVS System Codes, SA22-7626

¢ MVS System Commands, SA22-7627

¢ Security Server RACF Security Administrator's Guide, SA22-7683

¢ Security Server RACROUTE Macro Reference, SA88-8621

¢ TSO/E Customization, SA22-7783

¢ TSO/E Messages, SA22-7786

¢ TSO/E Programming Services, SA22-7789

¢ TSO/E REXX Reference, SA22-7790

¢

TSO/E System Programming Command Reference, SA22-7793¢ MVS Programming: Assembler Services Guide, SA88-8577

¢ DFSMS: Using Data Sets, SC26-7410

¢ DFSMSdfp Utilities, SC26-7414

¢ ISPF User's Guide Volume I , SC34-4822

¢ DFSMS Advanced Copy Services, SC35-0428

xiv Preface




Document conventions

This document uses the following typographic conventions:

Convention Description

Bold Indicates text on a window, including menus, menu options, buttons,fields, and labels. Example: Click OK.

Italic Indicates a variable, which is a placeholder for actual text providedby the user or system. Example: copy source-file target-file

Note: Angled brackets (< >) are also used to indicate variables.

Monospace Indicates text that is displayed on screen or entered by the user.Example: # pairdisplay -g oradb

< > angledbrackets

Indicates a variable, which is a placeholder for actual text providedby the user or system. Example: # pairdisplay -g <group>

Note: Italic font is also used to indicate variables.

[ ] squarebrackets

Indicates optional values. Example: [ a | b ] indicates that you canchoose a, b, or nothing.

{ } braces Indicates required or expected values. Example: { a | b } indicates

that you must choose either a or b.

| vertical bar Indicates that you have a choice between two or more options orarguments. Examples: [ a | b ] indicates that you can choose a, b, ornothing. { a | b } indicates that you must choose either a or b.

This document uses the following icons to draw attention to information:

Icon Label Description

Note Calls attention to important and/or additional information.

Tip Provides helpful information, guidelines, or suggestions forperforming tasks more effectively.

Caution Warns the user of adverse conditions and/or consequences(e.g., disruptive operations).

WARNING Warns the user of severe conditions and/or consequences(e.g., destructive operations).

Conventions for storage capacity values

Physical storage capacity values (for example, disk drive capacity) arecalculated based on the following values:

Physical capacity unit Value

1 kilobyte (KB) 1,000 (103) bytes

Preface xv




Physical capacity unit Value

1 megabyte (MB) 1,000 KB or 1,0002 bytes

1 gigabyte (GB) 1,000 MB or 1,0003 bytes

1 terabyte (TB) 1,000 GB or 1,0004 bytes

1 petabyte (PB) 1,000 TB or 1,0005 bytes

1 exabyte (EB) 1,000 PB or 1,0006 bytes

Logical storage capacity values (for example, logical device capacity) arecalculated based on the following values:

Logical capacity unit Value

1 block 512 bytes

1 KB 1,024 (210) bytes

1 MB 1,024 KB or 1,0242 bytes

1 GB 1,024 MB or 1,0243 bytes

1 TB 1,024 GB or 1,0244 bytes

1 PB 1,024 TB or 1,0245 bytes

1 EB 1,024 PB or 1,0246 bytes

Accessing product documentation

The Tiered Storage Manager for Mainframe user documentation is availableon the Hitachi Data Systems Portal: https://portal.hds.com. Check this

site for the most current documentation, including important updates thatmay have been made after the release of the product.

Getting help

Hitachi Data Systems Support Portal is the destination for technical support of your current or previously-sold storage systems, midrange and enterpriseservers, and combined solution offerings. The Hitachi Data Systems customersupport staff is available 24 hours a day, seven days a week. If you needtechnical support, log on to the Hitachi Data Systems Support Portal forcontact information: https://portal.hds.com .

Hitachi Data Systems Community is a new global online community for HDScustomers, partners, independent software vendors, employees, andprospects. It is an open discussion among these groups about the HDSportfolio of products and services. It is the destination to get answers,discover insights, and make connections. The HDS Community complementsour existing Support Portal and support services by providing an area where

xvi Preface






you can get answers to non-critical issues and questions. Join theconversation today! Go to community.hds.com, register, and complete

your profile.

Comments

Please send us your comments on this document: [email protected].

Include the document title and number, including the revision level (forexample, -07), and refer to specific sections and paragraphs wheneverpossible. All comments become the property of Hitachi Data SystemsCorporation.

Thank you!

Preface xvii


http://community.hds.com/



xviii Preface




1

Overview of Hitachi Tiered StorageManager for Mainframe

This chapter provides an overview of Tiered Storage Manager for Mainframe.

□About Tiered Storage Manager for Mainframe

□ Overview of the Tiered Storage Manager for Mainframe functionality

□ Concepts of terms used in Tiered Storage Manager for Mainframe

□ Prerequisites for Tiered Storage Manager for Mainframe

□ System configuration of Tiered Storage Manager for Mainframe

□ About files used by Tiered Storage Manager for Mainframe

□ Workflow for using Tiered Storage Manager for Mainframe

Overview of Hitachi Tiered Storage Manager for Mainframe 1-1




About Tiered Storage Manager for Mainframe

Tiered Storage Manager for Mainframe is software that works together withHitachi Dynamic Tiering for Mainframe to help users manage the data onvolumes tiered to multiple kinds of storage media, such as SSD, SAS, andSATA.

Data saved on tiered volumes can be relocated to the appropriate tier basedon the access frequency by a process called tier relocation. The followingfigure shows an overview of tier relocation. Data that is accessed frequentlyis moved to an upper tier, which consists of higher-speed storage media, anddata that is not so frequently accessed is moved to a lower tier, whichconsists of lower-speed storage media.

Figure 1-1 Automatic data relocation across tiers according to the accessfrequency

After considering the performance requirements for certain data, if you wantto locate the data in a tier appropriate for the requirements, you can directlyspecify the tier in which the data is to be located. For example, you canlocate data that is not accessed frequently but requires quick response in anupper tier.

Figure 1-2 Locating data in a specified tier according to performancerequirements

1-2 Overview of Hitachi Tiered Storage Manager for Mainframe




If only Dynamic Tiering for Mainframe is being used, a storage administratoruses either Storage Navigator or Command Control Interface to managestorage on a pool or volume basis.

If Dynamic Tiering for Mainframe is linked with Tiered Storage Manager forMainframe, the mainframe administrator can directly manage tiers becausethe following operations can be performed:

• Specification of the management target on an SMS storage group basis,

which mainframe administrators can use for storage management.• Specification of the management target on a volume basis by using

device addresses (DEVN or VOLSER) that the host has.

• Creation of a group of SMS storage groups or volumes, and specificationof them all at one time as a single group.

Management from the mainframe administrator's perspective can be used fortiers in which data is to be located. This means that the mainframeadministrator can manage storage according to the operating requirements,thus reducing the storage administrator's work. This allows you to useresources efficiently and maintain SLA, without degrading ROI or OPEX.

The following figure shows an overview of tier management using TieredStorage Manager for Mainframe.





Figure 1-3 Tier management using Tiered Storage Manager for Mainframe

Overview of the Tiered Storage Manager for Mainframefunctionality

The functionality provided by Tiered Storage Manager for Mainframe featurestier management based on tiering policy groups. It also features tiermanagement in conjunction with SMS, and acquisition of configurationinformation of storage systems. The following is a brief overview of thisfunctionality:

• Tier management based on tiering policy groups

¢ Defining tiering policy groups

You can define information related to tier relocation processing, suchas grouping of objects subject to tier management and the new-page





assignment tier. The definitions take effect when a command is usedto apply the definitions to the storage system.

¢ Acquisition of information related to Dynamic Tiering for Mainframe

The access frequency, data location status, and other informationrelated to Dynamic Tiering for Mainframe can be acquired for eachtiering policy group.

• Tier management in conjunction with SMS

The tiers in which data is to be located can be managed, on an SMSstorage group basis, in conjunction with SMS.

• Acquisition of the configuration information of storage systems (scan)

Information about volumes and pools can be acquired by scanning thestorage systems using the SMS storage group name, DEVN, or VOLSER asa key. The acquired information can be used to define tiering policygroups.

Tip: There are two methods of operation for Tiered Storage Manager forMainframe using ISPF panels and using CLI commands. Use the method thatsuits the state of operation.

Related topics

• About tiering policy groups on page 1-5

Concepts of terms used in Tiered Storage Manager forMainframe

This section describes the terms used in Tiered Storage Manager forMainframe.

About tiering policy groups

A tiering policy group is a group of multiple SMS storage groups and volumes.Specification of the tier in which data is to be located, acquisition of information, and other operations can be performed on a tiering policy groupbasis.

The following figure shows the possible grouping patterns of tiering policygroups.





Figure 1-4 Grouping patterns of tiering policy groups

About tiering policiesA tiering policy is information about the tiers in which data will be located andabout the processing of tier relocation.

You can specify a tiering policy prior to defining a tiering policy group. Afteryou define a tiering policy group, you must apply the specified tiering policyto the storage system.

For example, you have applied a tiering policy that locates data in Tier 1(SSD) and Tier 2 (SAS) for a volume. In this case, when tier relocation takesplace, pages are assigned to tiers 1 and 2, and then data is located on thosepages.

The following figure shows an overview of processing related to tieringpolicies.





Figure 1-5 Overview of tiering policies

A tiering policy can be specified by using a tiering policy information CSV file.In a tiering policy information CSV file, the following information can bespecified:

• Where data is to be located (tiering policy level)

• Tier to which new pages are to be assigned (new-page assignment tier)

• Whether to execute tier relocation

Related topics• About tiering policy levels on page 1-8

• About the new-page assignment tier on page 1-9

• Format of tiering policy information CSV files on page 7-4





About tiering policy levels

Tiering policy levels indicate categories of tiers in which data can be located.There are six tiering policy levels, from 0 (default) to 5. If a tiering policylevel is specified, data is located in the tier or tiers with the specified levelwhen tier relocation is performed.

For example, if the tiering policy level of 1 is specified for a volume that hasthree tiers, all pages on the volumes are moved to Tier 1, as shown in the

following figure. Pages that have been moved will not be moved to other tierswhen tier relocation is performed again.

Figure 1-6 When the tiering policy level of 1 is specified for a three-tiervolume

If the tiering policy level of 2 is specified for a volume that has three tiers,pages are moved between tiers 1 and 2 according to the access frequency, asshown in the figure below. After pages are moved, these pages are movedbetween tiers 1 and 2 according to the access frequency each time tierrelocation is performed.

Figure 1-7 When the tiering policy level of 2 is specified for a three-tiervolume

The following shows the relationship between tiering policy levels and the

tiers in which data will be located.





Table 1-1 Relationship between tiering policy levels and tiers in whichdata will be located

Tiering policylevel

Tier in which data will be located

3-tier configuration 2-tier configuration

0 All tiers (tiers 1, 2, and 3) All tiers (tiers 1 and 2)

1 Tier 1 Tier 1

2 Tiers 1 and 2 All tiers (tiers 1 and 2)

3 Tier 2 All tiers (tiers 1 and 2)

4 Tiers 2 and 3 All tiers (tiers 1 and 2)

5 Tier 3 Tier 2

Note:

The smaller the tier number, the higher the tier. For example, if an SSDdevice and an SAS device make up a tiered volume, the SSD device isTier 1, and the SAS device is Tier 2.

About the new-page assignment tier

The new-page assignment tier is the tier to which new pages are assigned thefirst time the host writes data to the volume.

For the tiers with a specified tiering policy level, the priority assigned to newpages is determined by the combination of the values specified for the tieringpolicy level and new-page assignment tier.

For example, if 0 is specified as the tiering policy level and MIDDLE is specified

as the new-page assignment tier for a three-tier volume, the priority of three

tiers is as follows: Tier 2 > Tier 3 > Tier 1. The figure below shows how pagesare assigned in this case. First, pages are assigned to Tier 2, which is thehighest priority. If Tier 2 becomes full, pages are assigned to Tier 3. If Tier 3becomes full, pages are assigned to Tier 1.

Figure 1-8 Overview of assigning new pages to tiers

The following table describes the values that can be used to specify the new-page assignment tier.





Table 1-2 Values that can be used to specify the new-page assignment tier

Value Description

HIGH The new page is assigned from the higher tier of tiers set in the tiering policy.

MIDDLE The new page is assigned from the middle tier of tiers set in the tiering policy.

LOW The new page is assigned from the lower tier of tiers set in the tiering policy.

For example, if newer data is accessed more frequently and older data isaccessed less frequently, you can specify HIGH for the new-page assignment

tier because new pages are then assigned in order starting from the uppertier.

Related topics

• About tiering policy levels on page 1-8

Prerequisites for Tiered Storage Manager for MainframeThis section describes the prerequisites for Tiered Storage Manager forMainframe.

Prerequisite OS

z/OS from V1R10 through V2R1

Caution: VM environments are not supported by Tiered Storage Manager forMainframe.

Prerequisite hardwareVSP Dynamic Tiering for Mainframe volumes

Caution: The following volumes are not supported:

• Volumes of a remote storage system

• Volumes without a host device number assigned

Prerequisite programs

• DFSMS (standard OS component)

• ISPF (standard OS component)• TSO/E REXX (standard OS component)

• TSO/E (standard OS component)

• Security Server (RACF) (standard OS component)

• Alternate Library for REXX (standard OS component) or IBM Library forREXX on zSeries Release 4 (FMID HWJ9140)





• Hitachi Dynamic Provisioning for Mainframe

• Hitachi Dynamic Tiering for Mainframe

System configuration of Tiered Storage Manager forMainframe

The following figure shows the system configuration of Tiered StorageManager for Mainframe.

Figure 1-9 System configuration of Tiered Storage Manager for Mainframe

Caution: The storage system must be connected to the z/OS host.





About files used by Tiered Storage Manager for Mainframe

This section describes the files used by Tiered Storage Manager forMainframe.

Overview of files used by Tiered Storage Manager for Mainframe

Tiered Storage Manager for Mainframe manages disk configurations and

tiering policy groups by using information defined in files.

Tiered Storage Manager for Mainframe uses the following three types of files:

• Tiering policy information CSV file

A user-created CSV file that contains information about volumes or anSMS storage group to be defined as a tiering policy group.

• Disk configuration definition file

A file that defines storage system configuration information. This file iscreated by scanning a storage system.

• Tiering policy group definition file

A file that defines a tiering policy group. This file is created by importing atiering policy information CSV file and a disk configuration definition file.

The disk configuration definition file and tiering policy group definition file aregenerically called configuration files.

Workflow for files used in Tiered Storage Manager for Mainframe

The following describes the workflow for files used in Tiered Storage Managerfor Mainframe.

The numbers in the figure correspond to the steps.





Figure 1-10 Workflow for files used in Tiered Storage Manager forMainframe

1. Scan the storage system.

A disk configuration definition file is created.

2. Create a tiering policy information CSV file.

In the CSV file, the user specifies the information for the volumes or SMSstorage groups to be defined in a tiering policy group.

3. Import a disk configuration definition file and a tiering policy informationCSV file to define a tiering policy group.

A tiering policy group definition file is created.

4. Apply the tiering policies of the defined tiering policy group to the storagesystem.

The pages will be relocated according to the defined tiering policies whentier relocation is performed the next time.

Workflow for using Tiered Storage Manager for Mainframe

The following figure shows the workflow for using Tiered Storage Manager forMainframe.





Figure 1-11 workflow for using Tiered Storage Manager for Mainframe

Related topics

• Workflow for when defining and checking tiering policy groups when using

the ISPF panel on page 3-2• Defining and verifying a tiering policy group when using the CLI

commands on page 4-2





2

Installation and setup

This chapter describes procedures for installing and setting up Tiered StorageManager for Mainframe.

□ Overview of installation and setup

□ Installing Tiered Storage Manager for Mainframe

□ Settings required for using CLI commands (registration for

authentication)

□ Setting RACF security for CLI commands

□ Settings for using environment configuration commands

□ Registering a user SVC

□ Setting the operating environment for Tiered Storage Manager for

Mainframe (setting environment variables or system symbols)

□ Settings required to use Tiered Storage Manager for Mainframe on the

ISPF panel

□ Registering licenses

□ Verifying the setup information

□ Preparing to use Tiered Storage Manager for Mainframe

□ Notes on setting up Tiered Storage Manager for Mainframe when Business

Continuity Manager is already installed

Installation and setup 2-1




□ Prerequisite user SVC versions for Tiered Storage Manager for Mainframe

□ Notes for when multiple versions of Tiered Storage Manager for

Mainframe coexist

2-2 Installation and setup




Overview of installation and setup

The following figure provides an overview of how to install and set up TieredStorage Manager for Mainframe.

Figure 2-1 Overview of installation and setup

#1A user SVC, environment variables, and system symbols of TieredStorage Manager for Mainframe are shared with Business ContinuityManager. Therefore, special care is needed in an environment whereBusiness Continuity Manager is installed.

#2





If you are not using SMP/E for the installation, you do not need to createa backup in the distribution library.

Related topics

• Installing Tiered Storage Manager for Mainframe on page 2-4

• Settings required for using CLI commands (registration for

authentication) on page 2-11• Setting RACF security for CLI commands on page 2-13

• Settings for using environment configuration commands on page 2-14

• Registering a user SVC on page 2-15

• Setting the operating environment for Tiered Storage Manager forMainframe (setting environment variables or system symbols) on page2-18

• Settings required to use Tiered Storage Manager for Mainframe on theISPF panel on page 2-22

• Registering licenses on page 2-25

• Verifying the setup information on page 2-31• Calculating required memory on page 2-32

• Settings required for collecting event logs on page 2-32

• Backing up Tiered Storage Manager for Mainframe to the distributionlibrary on page 2-33

• Notes on setting up Tiered Storage Manager for Mainframe when BusinessContinuity Manager is already installed on page 2-34

Installing Tiered Storage Manager for Mainframe

This section provides an overview and the procedure for installing TieredStorage Manager for Mainframe.

Workflow for during installation

After transferring the load module for Tiered Storage Manager for Mainframeto a host machine, you can install Tiered Storage Manager f or Mainframeusing SMP/E. Alternatively, you can install it directly in the target librarywithout using SMP/E.

The following figure illustrates the workflow when installing Tiered StorageManager for Mainframe.





Figure 2-2 Workflow for during installation of Tiered Storage Manager forMainframe

Related topics

• Transferring the load module to a host machine on page 2-5

• Performing an installation using SMP/E on page 2-8

• Installing directly from the provided datasets in the target library on page2-9

Transferring the load module to a host machine

Transfer the load module for Tiered Storage Manager for Mainframe providedon the installation media to a host machine. During the transfer procedure,use the JCLs provided on the installation media to create datasets used fortransfers and to extract the provided datasets.

The procedure for transferring the load module for Tiered Storage Managerfor Mainframe, which is provided on the installation media, to a host machineis illustrated in the following figure.





Figure 2-3 Procedure for transferring the load module for Tiered StorageManager for Mainframe to a host machine

The numbers in the figure correspond to the steps below.

Procedure

1. Copy the following files provided on the installation media to a PC:

¢ ALLOUPLD (JCL for creating datasets used for transfers)

¢ RECVUPLD (JCL for extracting the provided datasets (TSO/E RECEIVE))

¢ Tiered Storage Manager for Mainframe object archives

2. Transfer the following JCLs from the PC to a mainframe host in ASCIImode:

¢ ALLOUPLD

¢ RECVUPLD





3. Edit the JCLs transferred in accordance with your installationenvironment.

Details are provided at the beginning of each JCL.

4. Create datasets used for transfers.

Execute the ALLOUPLD job that was edited in step 3. This job defines the

datasets on the mainframe host that the Tiered Storage Manager forMainframe files will be transferred into in the next step.

5. Transfer the Tiered Storage Manager for Mainframe object archives fromthe PC to the mainframe host.

In binary mode, transfer the Tiered Storage Manager for Mainframeobject archives from the PC to the sequential datasets (created in step 4)on the mainframe host.

6. Extract (execute the TSO/E RECEIVE command) the provided datasetsfrom the object archives that were transferred.

Execute the RECVUPLD job that was edited in step 3. This job extracts the

product datasets from the object archives transferred in step 5.

The files provided on the installation media are shown in the following table.

Table 2-1 Files provided on the installation media

No. File name Description

1 HITACHI.CHKTnnn.SMPMCS.XMIT The SMP/E control statement for Tiered StorageManager for Mainframe used for SYSMODpackaging (information to be referred to bySMP/E RECEIVE processing (sample JCL:HDSKT3RC))

2 HITACHI.CHKTnnn.F1.XMIT • Sample JCL used for installation

• Sample script for CLI commands

3 HITACHI.CHKTnnn.F2.XMIT Load library for LINKLIB

4 HITACHI.CHKTnnn.F3.XMIT Load library for LPALIB

5 HITACHI.CHKTnnn.F4.XMIT Cataloged procedure library

6 HITACHI.CHKTnnn.F5.XMIT REXX Exec library

7 HITACHI.CHKTnnn.F6.XMIT REXX Exec library

8 HITACHI.CHKTnnn.F7.XMIT ISPF panel library

9 HITACHI.CHKTnnn.F8.XMIT ISPF message library

10 HITACHI.CHKTnnn.F9.XMIT ISPF table library

11 ALLOUPLD JCL for creating datasets used for transfer

12 RECVUPLD JCL for extracting (TSO/E RECEIVE) theprovided datasets

Note:

¢ Items 1 to 10 are Tiered Storage Manager for Mainframe objectarchives.





¢ The nnn part of CHKTnnn in the table varies depending on the version.

Postrequisites

Perform either of the following:

• Performing an installation using SMP/E

• Installing directly from the provided datasets in the target library

Related topics


• Installing directly from the provided datasets in the target library on page2-9

• Appendix E, Modifying the sample JCL on page E-1

Performing an installation using SMP/E

Use sample JCLs to perform an installation with SMP/E.

Procedure

1. Edit the following sample JCLs that will be used for installation inaccordance with the user installation environment.

¢ SMPALLOC (allocates the SMP/E dataset)

¢ HDSKT1AL (allocates the target libraries and distribution libraries)

¢ HDSKT2DF (defines the target libraries and distribution libraries)

¢ HDSKT3RC (performs SMP/E RECEIVE processing)

¢ HDSKT4AP (creates a target library)

Details are provided at the beginning of each sample JCL.

The sample JCLs are stored in the HITACHI.CHKTnnn.F1 dataset (the nnn

part varies depending on the version). If you edited the RECVUPLD job to

change the output destination dataset name for the TSO/E RECEIVE

command, the sample JCLs are stored in the dataset defined by thechange.

2. Execute SMPALLOC.

Allocate the SMP/E control dataset as necessary. If an existing SMP/Econtrol dataset is to be used, skip this step.

3. Execute HDSKT1AL.

The target library and distribution library (DLIB) are allocated.

4. Execute HDSKT2DF.

SMP/E DDDEF is executed, and the target library and distribution library(DLIB) are defined.

5. Execute HDSKT3RC.





SMP/E RECEIVE is executed, and the provided datasets are obtained andstored in the global zone.

6. Execute HDSKT4AP.

Perform the check operation for installing the provided datasets in thetarget library. (The CHECK operand has been specified for the APPLY

command of the sample JCL.) If no errors occur (the execution completeswith a return code of 0), go on to the next step.

7. Delete the CHECK operand from HDSKT4AP.

8. Re-execute HDSKT4AP after the CHECK operand is deleted.

SMP/E APPLY is executed and the provided datasets are installed in thetarget library.

Run the Tiered Storage Manager for Mainframe instance that was installed inthe target library. If no errors occur, back up Tiered Storage Manager forMainframe to the distribution library.

The following table shows the keyword (FMID) that is required for installing

with SMP/E.

Table 2-2 FMID for Tiered Storage Manager for Mainframe components

FMID Function name

CHKTnnn Hitachi Tiered Storage Manager for Mainframe

Note:

The nnn part of CHKTnnn varies depending on the version.

Postrequisites


authentication)

Related topics

• Settings required for using CLI commands (registration forauthentication) on page 2-11

• Backing up Tiered Storage Manager for Mainframe to the distributionlibrary on page 2-33


Installing directly from the provided datasets in the target library

Perform an installation directly from the provided datasets in the targetlibrary, without using SMP/E.

Procedure

1. Edit the sample JCL HDSKTSIN for installation in accordance with the user

installation environment.





Details are provided at the beginning of the sample JCL.

The sample JCL is stored in the HITACHI.CHKTnnn.F1 dataset (the nnn



command, the sample JCL is stored in the dataset after the change.

2. Execute HDSKTSIN.

The contents of the provided datasets are registered in the target library.

Postrequisites

• Settings required for using CLI commands (registration forauthentication)

Related topics

• Settings required for using CLI commands (registration forauthentication) on page 2-11


Library datasets to be registered after the installation

This section describes the attributes of the library datasets (target libraries)to be registered after the installation.

Attributes of the target libraries are shown in the following table.

Table 2-3 Attributes of the target libraries

Library type (DD name#) DSORG RECFMLRECL(bytes)

BLKSIZE(bytes)

Sample library

(HDSKSAMT)

PO FB 80 6,160

Load library for LINKLIB

(HDSKLNKT)

PO U - 6,144

Load library for LPALIB

(HDSKLPAT)

PO U - 6,144

Cataloged procedure library

(HDSKPRCT)

PO FB 80 6,160

REXX Exec library, fixed lengthformat

(HDSKEXET)

PO FB 80 6,160

REXX Exec library, variablelength format

(HDSKEXVT)

PO VB 255 6,120

ISPF panel library PO FB 80 6,160






BLKSIZE(bytes)

(HDSKPNLT)

ISPF message library

(HDSKMSGT)

PO FB 80 6,160

ISPF table library

(HDSKTABT)

PO FB 80 6,160

#

The DD name specified with the HDSKT1AL sample JCL (allocates the

distribution and target libraries) that was used when installing withSMP/E. The dataset name is the one specified in each DD statement.

Settings required for using CLI commands (registration forauthentication)

To use CLI commands, you need to register the load library for LINKLIB andthe KTQRYSMS command for authentication.

Registering the load library for LINKLIB and the KTQRYSMScommand for authentication

To register the load library for LINKLIB and the KTQRYSMS command for

authentication to enable the use of CLI commands:

Procedure

1. Concatenate the load library for LINKLIB HDSKLNKT to LNKLST.You can concatenate by using either of the following methods:

¢ Static method: Specify the load library for LINKLIB HDSKLNKT in the

PROG xx parmlib member as a dataset concatenated to the LNKLST.

To enable concatenation, you must perform an IPL again.

¢ Dynamic method: Use the SETPROG LNKLST command to concatenate

the load library for LINKLIB HDSKLNKT to the LNKLST.

If you cannot perform an IPL because the system is running, use thismethod to concatenate the load library. However, because performingan IPL will invalidate concatenation, modify parmlib as defined in the

static method, above so the change will continue across an IPL.2. Register the load library for LINKLIB HDSKLNKT for APF authorization.

You can register by using either of the following methods:

¢ Static method: Add the load library for LINKLIB HDSKLNKT to the

PROGxx parmlib member as a dataset to be authorized as APF.

To enable registration, you must perform an IPL again.





¢ Dynamic method: Use the SETPROG APF,ADD command to register the

load library as APF authentication.

If you cannot perform an IPL because the system is running, use thismethod to perform registration. However, because performing an IPLwill invalidate registration, modify parmlib as described above in thestatic method so the change will be available across an IPL.

Tip: LNKLST has APF authorization by default, so you do not have to

perform step 2, if the load library for LINKLIB HDSKLNKT was concatenatedwith LNKLST in step 1. Note that there are exceptions to this rule. For

details about APF authorization related to LNKLST, see the manual MVS

Initialization and Tuning Reference.

3. Register the KTQRYSMS command as a TSO/E authorized command.

Add the command name KTQRYSMS to the AUTHCMD section in the

IKJTSOxx parmlib member.

To enable registration, you must perform an IPL again. If you use thePARMLIB CHECK (nn) command and the PARMLIB UPDATE (nn)

command, registration can be enabled without performing an IPL again.For details about the PARMLIB command, see the TSO/E System

Programming Command Reference.

The KTQRYSMS command is a CLI command that is used internally by

Tiered Storage Manager for Mainframe to acquire SMS storage groupinformation.

For details about the SETPROG command, see the manual MVS System

Commands.

Postrequisites

• Setting RACF security for CLI commands

Related topics

• Example of dynamically linking the LINKLIB load library to LNKLST onpage 2-12

• Setting RACF security for CLI commands on page 2-13

Example of dynamically linking the LINKLIB load library to LNKLST

This section explains an example of dynamically linking the LINKLIB loadlibrary to LNKLST.

In this example, the currently-active LNKLST is switched from the originalLNKLST to a temporary LNKLST, and during this time, the original LNKLST is

connected to the LINKLIB load library. Dynamic changing of LNKLST affects

the jobs that are currently being executed. Before carrying out thisprocedure, see the IBM manual relating to LNKLST, and check the required

notes on dynamically changing LNKLST.





Procedure

1. Determine the active LNKLST by issuing the following command.

D PROG,LNKLST

The currently-active LNKLST (original LNKLST) is assumed to be LNKLST00.

2. Copy LNKLST00, and then define a temporary LNKLST (LNKLST99).

SETPROG LNKLST,DEFINE,NAME=LNKLST99,COPYFROM=LNKLST00

3. Activate temporary LNKLST (LNKLST99).SETPROG LNKLST,ACTIVATE,NAME=LNKLST99

4. Apply all jobs that are being executed to the temporary LNKLST

(LNKLST99).

SETPROG LNKLST,UPDATE,JOB=*

5. Add the LINKLIB load library to the original LNKLST (LNKLST00).

SETPROG LNKLST,ADD,NAME=LNKLST00,DSN=loadlib_dataset_name

6. Reactivate original LNKLST (LNKLST00).

SETPROG LNKLST,ACTIVATE,NAME=LNKLST00

7. Re-apply all jobs that are being executed to the original LNKLST

(LNKLST00).SETPROG LNKLST,UPDATE,JOB=*

8. Remove the temporary LNKLST (LNKLST99).

SETPROG LNKLST,UNDEFINE,NAME=LNKLST99

For details on the SETPROG command, see the manual MVS System

Commands.

Setting RACF security for CLI commands

To use Tiered Storage Manager for Mainframe CLI commands, you must set

up RACF security. Assign user permissions to use CLI operation commands orCLI reference commands.

Procedure

1. Define profiles for the RACF FACILITY class.

The correspondence between profiles defined for the FACILITY class andthe available CLI commands are shown in the following table.

Table 2-4 Correspondence between profiles defined for the FACILITY class and the available CLI commands

Profile defined for the FACILITY class Available CLI commandSTGADMIN.YKA.DKT.COMMANDS

(Operation profile)

KTACTTPG

KTDCTDEV

KTDCTTPG

KTIMPORT





Profile defined for the FACILITY class Available CLI command

KTQRYDEV

KTQRYRLC

KTQRYTPG

KTQSTATS

KTSCAN

STGADMIN.YKA.DKT.KTQUERY

(Reference profile)

KTIMPORT

KTQRYDEV

KTQRYRLC

KTQRYTPG

KTQSTATS

KTSCAN

2. Give users permission to view the operation profile or the reference

profile.

For details about how to define RACF profiles and how to assign userpermissions to access the profiles, see the Security Server RACF Security Administrator's Guide.

Tip: Users can use the following commands without access permissions:KTCONMSG, KTENV, KTERCODE, KTGETHDA, KTINSCHK, KTLOAD, KTSLEEP,

KTSTORE, KTWTOMSG

Postrequisites

• Settings for using environment configuration commands

Related topics


Settings for using environment configuration commands

Environment configuration commands (KTALCSVC, KTSETENV, and KTDSPENV)

are used for setting up Tiered Storage Manager for Mainframe. Set upenvironment configuration commands so that they can be used.

Prerequisites

• Settings required for using CLI commands (registration forauthentication)





Procedure

1. Perform either of the following:

¢ Concatenate the HDSKPRCT cataloged procedure library to the IEFPDSI

DD name in the MSTJCLxx parmlib member.

¢ Copy the KTALCSVC member, KTSETENV member, and KTDSPENV

member from the HDSKPRCT cataloged procedure library to a user's

PROCLIB.

Caution: To concatenate the cataloged procedure library to a dataset,make sure that the attributes of the cataloged procedure library are thesame as those of the dataset. For details, see the DFSMS: Using DataSets. For details about how to change the dataset attributes, see thedescription of IEBGENER and IEBCOPY in the DFSMSdfp Utilities.

2. Restrict user access for the KTALCSVC and KTSETENV commands.

Use the RACF program control function to assign permissions to accessthe KTALCSVC and KTSETENV commands only to the system administrator

who will execute the commands. If you do not restrict user access andthe KTALCSVC or KTSETENV command is used by a regular user by

mistake, Tiered Storage Manager for Mainframe might not operateproperly. You do not need to restrict user access for the KTDSPENV

command. For details about the RACF program control function, see theSecurity Server RACF Securit y Administrator's Guide.

Postrequisites

• Registering a user SVC

Related topics


authentication) on page 2-11


Registering a user SVC

You can dynamically register a user SVC by using the KTALCSVC environment

configuration command, or statically register a user SVC by using theIEASVCxx parmlib member.

If you use the IEASVCxx parmlib member to register a user SVC, you must

perform an IPL again. If you cannot perform an IPL again because the systemis running, use the KTALCSVC command to perform registration.

Registering a user SVC using the KTALCSVC command

Use the KTALCSVC environment configuration command to dynamically

register a user SVC.





Prerequisites


Procedure

1. Choose an unused SVC number between 200 and 255 to assign to theuser SVC.

2. Execute the following KTALCSVC command.START KTALCSVC, PARM='SVC-number '

Tip: The user SVC registered with the KTALCSVC command is invalidated if an

IPL is performed again. Perform either of the following in case you need toperform an IPL again the next time:

• Add the KTALCSVC command to the COMMNDxx parmlib member, so that

the user SVC is automatically registered when an IPL is performed again.

• Define the user SVC in the IEASVCxx parmlib member, and use the

statically-registered user SVC from the next time an IPL is performedagain.

Specification examplesSTART KTALCSVC

By omitting the PARM parameter when executing this command, an unused

SVC number between 200 and 255 is assigned.

Caution:

• If you used the KTALCSVC command to register a user SVC while Tiered

Storage Manager for Mainframe was running, the execution of the CLIcommand continues to use the user SVC defined by the IEASVCxx parmlib

member. The registered user SVC will take effect the next time a CLIcommand is executed.

• User SVCs are shared between Tiered Storage Manager for Mainframe,and Business Continuity Manager. Therefore, you must be careful whenregistering a user SVC if you install Tiered Storage Manager forMainframe for the first time in an environment where Business ContinuityManager is installed.

Postrequisites

• Setting the operating environment for Tiered Storage Manager forMainframe (setting environment variables or system symbols)

Related topics


• Registering a user SVC using the IEASVCxx parmlib member on page2-17






• Notes on registering a user SVC if Business Continuity Manager isinstalled on page 2-35

• KTALCSVC on page 6-42

Registering a user SVC using the IEASVCxx parmlib member

Statically register a user SVC by defining a user SVC number in the IEASVCxx

parmlib member.

Procedure

1. Choose an unused number between 200 and 255 to be assigned for theuser SVC.

2. Define the following SYMDEF statement (&YKSVCNO system symbol) in the

IEASYMxx parmlib member:

SYMDEF(&YKSVCNO='SVC-number ')

For details, see the manual MVS Initialization and Tuning Reference.

3. To concatenate the load library for LPALIB HDSKLPAT to LPALST, perform

either of the following:

¢ Define the load library for LPALIB HDSKLPAT in the LPALSTxx parmlib

member. For details, see the manual MVS Initialization and TuningReference.

¢ Use the SETPROG LPA command to dynamically concatenate the load

library for LPALIB HDSKLPAT to LPALST. For details, see the manual

MVS System Commands.

4. Define the following SVCPARM statement in the IEASVCxx parmlib member:

SVCPARM SVC-number ,REPLACE,TYPE(3),EPNAME(JYUASVC),APF(NO),NPRMPT(NO),AR(NO)

For details, see the manual MVS Initialization and Tuning Reference.

To enable registration, you must perform an IPL again with the CLPA

parameter specified.

Caution: User SVCs are shared between Tiered Storage Manager forMainframe, and Business Continuity Manager. Therefore, you must be carefulwhen registering a user SVC if you install Tiered Storage Manager for

Mainframe for the first time in an environment where Business ContinuityManager is installed.

Postrequisites

• Setting the operating environment for Tiered Storage Manager forMainframe (setting environment variables or system symbols)





Related topics


• Notes on registering a user SVC if Business Continuity Manager isinstalled on page 2-35

Setting the operating environment for Tiered StorageManager for Mainframe (setting environment variables orsystem symbols)

This section explains how to set the operating environment for Tiered StorageManager for Mainframe.

About the operating environment for Tiered Storage Manager forMainframe

The operating environment settings for Tiered Storage Manager forMainframe include the following:

• The prefix of the license information dataset that registers the license key

• Whether the system logger service is used to collect event logs

• Whether CLI command execution logs are output to SYSLOG or theconsole

Set the operating environment settings for Tiered Storage Manager forMainframe by using either of the following methods:

• Use the environment variable (set by using the KTSETENV environment

configuration command).Use this method if you cannot perform an IPL again because the system isrunning. However, this setting is invalidated if an IPL is performed again.

• Use the system symbol (set for the IEASYMxx parmlib member).

To enable this setting, you must perform an IPL again. The statically-registered settings can be used the next time an IPL is performed again.

Related topics

• Setting the operating environment by using environment variables onpage 2-19

• Setting the operating environment by using system symbols on page2-21





List of operating environment setting items for Tiered StorageManager for Mainframe

The following table lists operating environment setting items for TieredStorage Manager for Mainframe.

Table 2-5 Operating environment settings items for Tiered StorageManager for Mainframe

Setting itemsEnvironm

entvariable

Systemsymbols

Specifiedvalues

Defaultvalues

Specifiesprefixes for thelicenseinformation

dataset.#

prefix-1 YKLCNSE &YKLCNSE 8 or feweralphanumericcharacters

HITACHI

prefix-2 YKLCNS2 &YKLCNS2 None

Specifies whether the systemlogger service is used to collectevent logs.

LOGPUT &YKLOGPT LOGR: Used

SAM: Not used

LOGR

Specifies whether to output CLIcommand execution logs toSYSLOG or the console.

SYSLOG &YKSYSLG YES: Output

to SYSLOG

CONSOLE:

Output to theconsole

NO: Not

output

YES

#:

The name of a license information dataset is decided as follows:

prefix-1. prefix-2.CCENTRAL.LICENSE

prefix-2 can be omitted. prefix-2 is enabled if prefix-1 is specified.

If you set both the environment variables and the system symbols, thepriority is as follows:

1. Values of the environment variables

2. Values specified for the system symbols

3. Default values

Setting the operating environment by using environment variables

To dynamically set the following operating environments by usingenvironment variables, use the environment setting command KTSETENV.



• Whether CLI command logs are output to SYSLOG or the console





Prerequisites


Procedure

1. Execute the following KTSETENV command.

START KTSETENV,PARM=' parameter = parameter-value'

2. Use the KTDSPENV command as follows to confirm that the environmentvariables have been specified correctly:

START KTDSPENV,PARM='DETAIL'

Example of executing the KTSETENV command

• When setting the name of the license information dataset toHTC1.HTC2.CCENTRAL.LICENSE

START KTSETENV,PARM='YKLCNSE=HTC1'START KTSETENV,PARM='YKLCNS2=HTC2'

• When specifying whether to use the system logger service to collect eventlogs

START KTSETENV,PARM='LOGPUT=LOGR' (if using the system logger

service)

START KTSETENV,PARM='LOGPUT=SAM' (if not using the system logger

service)

• When specifying whether to output CLI command execution logs toSYSLOG or the console

START KTSETENV,PARM='SYSLOG=YES' (if outputting to SYSLOG)

START KTSETENV,PARM='SYSLOG=CONSOLE' (if outputting to the console)

START KTSETENV,PARM='SYSLOG=NO' (if not outputting)

Caution: If you use the KTSETENV command to set SYSLOG=CONSOLE,Tiered Storage Manager for Mainframe version 7.5 is treated as if SYSLOG=YES is set. Be careful in an environment in which multiple

versions coexist or when upgrading.

Tip: This setting is invalidated if an IPL is performed again. Perform either of the following in case you need to perform an IPL again the next time:

• Add the KTSETENV command to the COMMNDxx parmlib member to

automatically set the environment variables when an IPL is performedagain.

• For the IEASYMxx parmlib member, specify the system symbols so that

the statically-registered settings will be used the next time an IPL isperformed.

Tip: Use either the environment variables or the system symbols to specifyboth prefix-1 and prefix-2. If you use the environment variable to specify prefix-1 and use the system symbol to specify prefix-2, the process of determining the prefixes will be complicated.





Tip: The license (name of the license information dataset) for Tiered StorageManager for Mainframe takes effect when the KTLOAD command is first

executed after the license is registered. Even if you used the KTSETENV

command to modify a prefix of the license information dataset name whileCLI commands were being executed, the corresponding license takes effectafter the KTLOAD command is executed the next time.

Caution: Environment variables are shared by Tiered Storage Manager for

Mainframe and Business Continuity Manager. Therefore, you must be carefulwhen setting the environment variables in an environment where BusinessContinuity Manager is installed.

Postrequisites

• Settings required to use Tiered Storage Manager for Mainframe on theISPF panel

Related topics


• Setting the operating environment by using system symbols on page2-21


• Notes on setting environment variables or system symbols if BusinessContinuity Manager is installed on page 2-35

• KTDSPENV on page 6-43

• KTSETENV on page 6-45

• Collecting event logs on page 9-4

• Collecting the CLI command-execution log on page 9-20

Setting the operating environment by using system symbols

To statically set the following operating environments by using systemsymbols, define the IEASYMxx parmlib member.



• Whether CLI command execution logs are output to SYSLOG or theconsole

Procedure

1. Define the following line in the IEASYMxx parmlib member.

SYMDEF(system-symbol='system-symbol-value')

2. After an IPL is performed again, use the KTDSPENV command to confirm

that the system symbols have been specified correctly.






Example of defining the IEASYM xx parmlib member

• When setting the name of the license information dataset toHTC1.HTC2.CCENTRAL.LICENSE

SYMDEF(&YKLCNSE='HTC1')SYMDEF(&YKLCNS2='HTC2')

• When specifying whether to use the system logger service to collect eventlogs

SYMDEF(&YKLOGPT='LOGR') (if using the system logger service)SYMDEF(&YKLOGPT='SAM') (if not using the system logger service)

• When specifying whether to output CLI command execution logs toSYSLOG or the console

SYMDEF(&YKSYSLG='YES') (if outputting to SYSLOG)

SYMDEF(&YKSYSLG='CONSOLE') (if outputting to the console)

SYMDEF(&YKSYSLG='NO') (if not outputting)

Tip: Use either the environment variables or the system symbols to specifyboth prefix-1 and prefix-2. If you use the environment variables to specify prefix-1, and use the system symbols to specify prefix-2, the process of

determining the prefixes will be complicated.

Caution: System symbols are shared by Tiered Storage Manager forMainframe and Business Continuity Manager. Therefore, you must be carefulwhen setting system symbols in an environment where Business ContinuityManager is installed.

Postrequisites

• Settings required to use Tiered Storage Manager for Mainframe on theISPF panel

Related topics


• Notes on setting environment variables or system symbols if BusinessContinuity Manager is installed on page 2-35




Settings required to use Tiered Storage Manager forMainframe on the ISPF panel

You need to execute the KTSTART command in the ISPF panel to use Tiered

Storage Manager for Mainframe on the ISPF panel. This section describes thesettings required to execute the KTSTART command.





The KTSTART command is a TSO/E command that provides an ISPF panel

interface.

To execute the KTSTART command in the ISPF panel, you need to concatenate

the REXX Exec library, ISPF panel library, ISPF message library, and ISPFtable library by using either of the following methods:

• Using DD names to concatenate

• Using the ALTLIB command and the LIBDEF service to concatenate

Using DD names to concatenate the libraries required for executingthe KTSTART command

Use DD names to concatenate the target libraries (REXX Exec library, ISPFpanel library, ISPF message library, and ISPF table library) required forexecuting the KTSTART command in the ISPF panel. The concatenation takes

effect when you log on to ISPF (if you have already logged on, you must logon again).

Procedure

1. Concatenate the REXX Exec library HDSKEXET or HDSKEXVT to SYSEXEC DD

name.

¢ If the existing library concatenated to SYSEXEC DD name has fixed

length format (RECFM=FB), concatenate the REXX Exec libraryHDSKEXET to SYSEXEC DD name.

¢ If the existing library concatenated to SYSEXEC DD name has variable

length format (RECFM=VB), concatenate the REXX Exec libraryHDSKEXVT to SYSEXEC DD name.

2. Concatenate the ISPF panel library HDSKPNLT to ISPPLIB DD name.

Caution: In an environment in which the DBCS function is enabled, youmust also concatenate the ISPF panel library HDSKPNLT to ISPPALT

(alternate panel library) DD name. For details, see the ISPF User's GuideVolume I .

3. Concatenate the ISPF message library HDSKMSGT to ISPMLIB DD name.

Caution: In an environment in which the DBCS function is enabled, youmust also concatenate the ISPF panel library HDSKMSGT to ISPMALT

(alternate message library) DD name. For details, see the ISPF User'sGuide Volume I .

4. Concatenate the ISPF table library HDSKTABT to ISPTLIB DD name.

When you log on to ISPF (if you have already logged on, you must log onagain), you can start the KTSTART command by selecting option 6 Command

in the ISPF Primary Option Menu panel.

Caution: To concatenate a dataset to libraries, make sure that the attributesof the target libraries are the same as the attributes of the dataset. For





example, if the dataset attributes are DSORG=PO and RECFM=FB, the LRECLsetting must be the same among the datasets. For details, see the DFSMS:Using Data Sets. For details about how to change dataset attributes, see thedescription of IEBGENER and IEBCOPY in the DFSMSdfp Utilities.

Postrequisites

• Registering a licenses

Related topics


Using the ALTLIB command and LIBDEF service to concatenate thelibraries required for executing the KTSTART command

Use the ALTLIB command and LIBDEF service to concatenate the target

libraries (REXX Exec library, ISPF panel library, ISPF message library, andISPF table library) required for executing the KTSTART command in the ISPF

panel. The concatenation is invalidated when the KTSTART commandterminates.

Procedure

• To concatenate the REXX Exec library HDSKEXET or HDSKEXVT, use the

TSO/E ALTLIB command.

¢ If the existing library concatenated to SYSEXEC DD name has fixed

length format (RECFM=FB), concatenate the REXX Exec libraryHDSKEXET.

¢ If the existing library concatenated to SYSEXEC DD name has variable

length format (RECFM=VB), concatenate the REXX Exec libraryHDSKEXVT.

• To concatenate the panel library HDSKPNLT, message library HDSKMSGT,

and table library HDSKTABT, use the LIBDEF service of ISPF.

Caution:

• In an environment in which the DBCS function is enabled, you must alsoconcatenate the ISPF panel library HDSKPNLT to ISPPALT (alternate panel

library) DD name, and concatenate the ISPF message library HDSKMSGT to

ISPMALT (alternate message library) DD name. For details, see the ISPF

User's Guide Volume I .

• To concatenate a dataset to libraries, make sure that the attributes of thetarget libraries are the same as the attributes of the dataset. Forexample, if the dataset attributes are DSORG=PO and RECFM=FB, theLRECL setting must be the same among the datasets. For details, see theDFSMS: Using Data Sets. For details about how to change the datasetattributes, see the description of IEBGENER and IEBCOPY in theDFSMSdfp Utilities.





Sample REXX script

While ISPF is running, you can execute the following REXX script toconcatenate the libraries to the DD names (SYSEXEC, ISPPLIB, ISPMLIB, and

ISPTLIB), and execute the KTSTART command to start the main panel for

Tiered Storage Manager for Mainframe.

/* REXX */

ADDRESS TSO "ALTLIB ACTIVATE APPLICATION(EXEC)", "DATASET('HDSKT.Vnnnnnn.HDSKEXET')";

ADDRESS ISPEXEC; "LIBDEF ISPMLIB DATASET ID('HDSKT.Vnnnnnn.HDSKMSGT') STACK"; "LIBDEF ISPPLIB DATASET ID('HDSKT.Vnnnnnn.HDSKPNLT') STACK"; "LIBDEF ISPTLIB DATASET ID('HDSKT.Vnnnnnn.HDSKTABT') STACK";

"SELECT CMD(KTSTART) ";

"LIBDEF ISPTLIB"; "LIBDEF ISPPLIB"; "LIBDEF ISPMLIB";

ADDRESS TSO "ALTLIB DEACTIVATE APPLICATION(EXEC)";

Return 0;

Postrequisites

• Registering a licenses

Related topics


Registering licenses

To use Tiered Storage Manager for Mainframe, you must register a license forit.

Workflow for registering a license

The following figure shows the workflow when registering a license for TieredStorage Manager for Mainframe.





Figure 2-4 Workflow of registering a license for Tiered Storage Managerfor Mainframe

Related topics

• Creating a license information dataset on page 2-26

• Registering a license by using a license key file on page 2-27

• Registering a license by entering a license key on page 2-29

Creating a license information dataset

Create a license information dataset for installing a license key.

Prerequisites

• Specifying prefixes for the license information dataset using theenvironment variable or system symbol

Procedure

1. Edit the JCL that allocates the license information dataset.

Edit the dataset prefix (%PREFIX ) and the volume serial number (%VSN )in accordance with your installation environment. For the dataset prefix(%PREFIX ), specify the value that was set by using the environmentvariable or system symbol.

//ALLOC JOB job info//*// SET PFX=%PREFIX Data set prefix1// SET VSN=%VSN VOLSER//*//BR14 EXEC PGM=IEFBR14//LICENSE DD DSN=&PFX..CCENTRAL.LICENSE,// UNIT=SYSDA,VOL=SER=&VSN,

// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)

The license information dataset has the following format:

¢ Dataset format: Sequential dataset in fixed-length record format

¢ Record size: 80 bytes





¢ Block size: Multiple of 80 bytes

2. Submit the JCL to allocate the license information dataset.

3. Assign the following access permissions for users who use the licenseinformation dataset.

¢ User who installs the license key: Write permission

¢ Other users who operate Tiered Storage Manager for Mainframe: Read

permission

Note: Do not edit or delete the license information dataset after the licensekey is installed. If you do so, Tiered Storage Manager for Mainframe cannotbe used.

Postrequisites

• Registering a license

Related topics


• Setting the operating environment by using system symbols on page 2-21

• Registering a license by using a license key file on page 2-27

• Registering a license by entering a license key on page 2-29

Registering a license by using a license key file

With this method, transfer the license key file to z/OS, and use the ManageLicenses panel to register the license.

The following figure provides the procedure for registering a license by usinga license key file.





Figure 2-5 Procedure for registering a license by using a license key file

Prerequisites

• Creating a license information dataset

The numbers in the figure correspond to the step numbers below.

Procedure

1. Create a license key dataset for transferring a license key file to z/OS.

Create the license key dataset with the following attributes:

¢ Dataset format: VB or FB sequential dataset

¢ Record length: 200 bytes or greater

¢ Block size: Optional

Do not use hyphens in the name of the license key dataset.

2. Transfer the license key file to the host machine.

Use the following format to transfer the license key file to the license keydataset:

¢ ASCII mode¢ Encoded (to EBCDIC)

Assume that the license key file has been transferred to a license keydataset named LICENSE.KEYS.SAMPLE.

3. In the ISPF Primary Option Menu panel, select option 6 Command.

4. Enter KTSTART.





The main panel for Tiered Storage Manager for Mainframe appears.

When you display the main panel for Tiered Storage Manager forMainframe for the first time, the Edit Defaults panel appears. Use thispanel to specify basic information for the ISPF panels.

5. Select the Installation Management 'Install' point-and-shoot field.

The Installation Management area appears.

6. Select the <Licenses> point-and-shoot field.

The Manage Licenses panel appears.

7. Enter the name of the license key dataset (LICENSE.KEYS.SAMPLE) in theLicense Key Dataset Name field, and then press Enter.

The Licenses Message List panel appears.

The license key is read from the license key dataset and installed in thelicense information dataset. The KTA001I message is output if the license

key is installed correctly.

Tip: If the license key file contains the license key for Business ContinuityManager, the license key for Business Continuity Manager is alsoinstalled.

8. Use the License List in the Manage Licenses panel to confirm that thelicense has been installed correctly.

Postrequisites

• Verifying the setup information

Related topics


• Verifying the setup information on page 2-31

• Edit Defaults panel on page 5-13• Installation Management area on page 5-17

• Manage Licenses panel on page 5-22

Registering a license by entering a license key

Register a license by directly entering a key code into the Manage Licensespanel.

The following figure provides the procedure for registering a license bydirectly entering a license key.





Figure 2-6 Procedure for registering a license by directly entering a licensekey

Prerequisites

• Creating a license information dataset

The numbers in the figure correspond to the steps below.

Procedure

1. In the ISPF Primary Option Menu panel, select option 6 Command.

2. Enter KTSTART.

The main panel for Tiered Storage Manager for Mainframe appears.

When you display the main panel for Tiered Storage Manager forMainframe for the first time, the Edit Defaults panel appears. Use thispanel to specify basic information for the ISPF panels.

3. Select the Installation Management 'Install' point-and-shoot field.

The Installation Management area appears.

4. Select the <Licenses> point-and-shoot field.

The Manage Licenses panel appears.

5. In the Manage Licenses panel, enter the key code in the Key Codefield, and then press Enter.

Tip: If you enter the keycode for Business Continuity Manager in this

panel, the license key for Business Continuity Manager is also installed.The Licenses Message List panel appears.

The KTA001I message is output if the license key is installed correctly.

The key code you entered is installed as the license key in the licenseinformation dataset.





6. Use the License List in the Manage Licenses panel to confirm that thelicense has been installed correctly.

Postrequisites

• Verifying the setup information

Related topics


• Verifying the setup information on page 2-31

• Edit Defaults panel on page 5-13

• Installation Management area on page 5-17


Verifying the setup information

After you have completed the setup of Tiered Storage Manager forMainframe, check the setup.

Overview of verifying the setup information

You can execute the KTINSCHK command to check whether the following

items have been completed.

• View permission required for using CLI commands has been assigned tothe reference and operation profiles.

• A user SVC has been registered correctly.

Verifying the setup informationTo check the setup tasks by executing the KTINSCHK command:

Procedure

1. Execute the KTINSCHK command.

From the command execution results, confirm that the setup tasks havebeen performed correctly.

2. If the return code is 8, perform the task that has not been completed.

If the return code of the KTINSCHK command is 8, there is a problem with

the information specified during setup. Check the command executionresults and perform the task that has not been completed.

JCL example

The following shows an example of a JCL used to output the execution resultsof the KTINSCHK command to SYSTSPRT DD name.





//KTINSCHK JOB//IEFPROC EXEC PGM=IKJEFT01,TIME=1440,REGION=4096K//SYSTSPRT DD SYSOUT=*//SYSABEND DD SYSOUT=A//STEPLIB DD DSN=HTC1.KT.Vvvrr .LINKLIB,DISP=SHR//SYSTSIN DD *KTINSCHK/*//

For details about the example of the command output, see the description of the KTINSCHK command.

Postrequisites

• Preparations to use Tiered Storage Manager for Mainframe

Related topics

• Preparing to use Tiered Storage Manager for Mainframe on page 2-32

• KTINSCHK on page 6-39

Preparing to use Tiered Storage Manager for Mainframe

This section describes the preparations that need to be performed beforeusing Tiered Storage Manager for Mainframe, including calculating therequired memory, specifying the settings for collecting event logs, andbacking up files to the distribution library.

Calculating required memory

Use the following formula to calculate the memory size required for runningTiered Storage Manager for Mainframe.

• For a user region of less than 16 MB: 1,024 KB

• For an extended user region of 16 MB or more: 4,000 KB + (4 number-of-volumes) KB

Settings required for collecting event logs

Specify the settings required for collecting event logs. The specificationmethod varies depending on whether you want to output event logs to thelog stream by using the system logger service or to the Tiered Storage

Manager for Mainframe log dataset without using the system logger service.

Procedure

To output event logs to the log stream by using the system logger service,perform all the sysplex setup procedures for using the DASD-only log streamfor the system logger service described in the MVS Setting Up a Sysplex .





To output event logs to the Tiered Storage Manager for Mainframe logdataset without using the system logger service, create a log dataset beforeexecuting a CLI command.

For details about event logs, see the description about collecting event logs.

Related topics

• Collecting event logs by using the system logger service on page 9-5

• Collecting event logs without using the system logger service on page9-16

Backing up Tiered Storage Manager for Mainframe to the distributionlibrary

If SMP/E was used when installing Tiered Storage Manager for Mainframe inthe target library and no errors occurred in the operation of Tiered StorageManager for Mainframe, use a sample JCL to back up Tiered Storage Managerfor Mainframe to the distribution library. This step is unnecessary if you installit directly in the target library without using SMP/E.

Procedure

1. Modify the following sample JCL in accordance with the user installationenvironment.

¢ HDSKT5AC

Details are shown at the beginning of the sample JCL.

The sample JCL is stored in the HITACHI.CHKTnnn.F1 dataset (the nnn



command, the JCL is stored in the dataset after the change.

2. Execute HDSKT5AC.

Perform the checking that is required for backing up the provideddatasets to the distribution library. (The CHECK operand has been

specified for the ACCEPT command.) If no errors occur (the execution

completes with a return code of 0), go on to the next step.

3. Delete the CHECK operand from HDSKT5AC.

4. Re-execute HDSKT5AC after the CHECK operand is deleted.

SMP/E ACCEPT is executed, and the provided datasets are backed up tothe distribution library.

Attributes of the distribution libraries (DLIB) are shown in the following table.

Table 2-6 Attributes of the distribution libraries (DLIB)


BLKSIZE(bytes)

Sample library PO FB 80 6,160






BLKSIZE(bytes)

(HDSKSAMD)

Load library for LINKLIB

(HDSKLNKD)

PO U - 6,144

Load library for LPALIB

(HDSKLPAD)

PO U - 6,144

Cataloged procedure library

(HDSKPRCD)

PO FB 80 6,160

REXX Exec library, fixed lengthformat

(HDSKEXED)

PO FB 80 6,160

REXX Exec library, variablelength format

(HDSKEXVD)

PO VB 255 6,120

ISPF panel library

(HDSKPNLD)

PO FB 80 6,160

ISPF message library

(HDSKMSGD)

PO FB 80 6,160

ISPF table library

(HDSKTABD)

PO FB 80 6,160

#

The DD name specified with the HDSKT1AL sample JCL (allocates the

distribution and target libraries) that was used when installing withSMP/E. The dataset name is the one specified in each DD statement.

Related topics



Notes on setting up Tiered Storage Manager for Mainframewhen Business Continuity Manager is already installed

This section provides notes on registering a user SVC and setting

environment variables and system symbols when installing Tiered StorageManager for Mainframe in an environment where Business ContinuityManager is installed.





Notes on registering a user SVC if Business Continuity Manager isinstalled

Tiered Storage Manager for Mainframe and Business Continuity Managershare the same user SVC. Therefore, you must compare the version of thecurrently enabled user SVC registered by Business Continuity Manager andthe version of the prerequisite user SVC for Tiered Storage Manager forMainframe, and then you must use the user SVC of the later version.

To confirm the version of the currently enabled user SVC, use the YKINSCHK

command of Business Continuity Manager.

• If the confirmed user SVC version is old and does not satisfy conditionsfor the prerequisite user SVC version requirement of Tiered StorageManager for Mainframe:

Use Business Continuity Manager to delete the user SVC, and then useTiered Storage Manager for Mainframe to register it again.

• If the confirmed user SVC version satisfies conditions for the prerequisiteuser SVC version:

You can use the currently enabled user SVC as it is.

Tip:

• For details on the YKINSCHK command, see the Hitachi Business

Continuity Manager Reference Guide.

• For details on how to delete the user SVC in Business Continuity Manager,see the Hitachi Business Continuity Manager Installation Guide.

• This procedure lets you install Tiered Storage Manager for Mainframe forthe first time. If you need to upgrade Tiered Storage Manager forMainframe, refer to the instructions for preparing for the upgrade.

Related topics


• Prerequisite user SVC versions for Tiered Storage Manager for Mainframeon page 2-36

• Preparation for upgrading Tiered Storage Manager for Mainframe on pageD-3

Notes on setting environment variables or system symbols if Business Continuity Manager is installed

Tiered Storage Manager for Mainframe and Business Continuity Manager use

the same environment variables and system symbols. Do not change thecurrently enabled operating environment setting values (that is, environmentvariables or values set to system symbols), in the system where BusinessContinuity Manager is running. In particular, if you change the prefix of alicense information dataset, you must register the Business ContinuityManager license again because the license information dataset is shared byTiered Storage Manager for Mainframe and Business Continuity Manager.





Change the operating environment setting values very carefully if you need tochange them.

Tip: To check the currently enabled operating environment setting values, dothe following:

• If Tiered Storage Manager for Mainframe has already been installed(when you upgrade it)

Check the operating environment setting values that were obtained whenpreparing for the upgrade.

• If Tiered Storage Manager for Mainframe has not been installed (whenyou install it for the first time)

Use the YKDSPENV command to do the check. For details on the YKDSPENV

command, see the Hitachi Business Continuity Manager Reference Guide.

Related topics


• Preparation for upgrading Tiered Storage Manager for Mainframe on pageD-3

Prerequisite user SVC versions for Tiered Storage Managerfor Mainframe

The following table shows the prerequisite user SVC versions for TieredStorage Manager for Mainframe.

Table 2-7 Prerequisite user SVC versions for Tiered Storage Manager for

Mainframe

Tiered Storage Manager for Mainframe version Prerequisite user SVC version

7.5.0 7.5.0 or later

8.0.0

Notes for when multiple versions of Tiered Storage Managerfor Mainframe coexist

This section provides notes for when multiple versions coexist in the samesystem.

Notes on collection of CLI command execution logs

The CONSOLE setting, which is configured by using the KTSETENV command

with SYSLOG=CONSOLE specified or by using the system symbol &YKSYSLG, is





enabled in Tiered Storage Manager for Mainframe version 8.0 or later.Therefore, in an environment in which instances of Tiered Storage Managerfor Mainframe of versions 7.5 and 8.0 or later coexist, even if you configurethe CONSOLE setting by using the KTSETENV command with SYSLOG=CONSOLE

specified or by using the system symbol &YKSYSLG, CLI command execution

logs are output to SYSLOG in Tiered Storage Manager for Mainframe version7.5.

In addition, the output destination of CLI command execution logs in TieredStorage Manager for Mainframe version 8.0 or later cannot be changed toSYSLOG even if you execute the KTSETENV command with SYSLOG=CONSOLE

specified in Tiered Storage Manager for Mainframe version 8.0 or later, andthen execute the KTSETENV command with SYSLOG=YES specified in Tiered

Storage Manager for Mainframe version 7.5. Use the KTSETENV command in

Tiered Storage Manager for Mainframe version 8.0 to change the outputdestination.





3

Tiered Storage Manager for Mainframeoperations when using the ISPF panel

This chapter describes how to use the ISPF panels to operate Tiered StorageManager for Mainframe.

□ Operation description method for the ISPF panels

□ Workflow for when defining and checking tiering policy groups when using

the ISPF panel

□ Starting Tiered Storage Manager for Mainframe and displaying the main

panel

□ Basic ISPF panel settings of Tiered Storage Manager for Mainframe

□ Defining tiering policy groups when using the ISPF panel

□ Verification after scanning storage systems when using the ISPF panel

□ Verification after defining a tiering policy group when using the ISPF panel

□ Frequently used checking methods when using the ISPF panel

□ About changing tiering policy groups when using the ISPF panel

□ Convenient use of list panels

□ Customizing the ISPF panels

Tiered Storage Manager for Mainframe operations when using the ISPF panel 3-1




Operation description method for the ISPF panels

The following describes how the operation of Tiered Storage Manager forMainframe using the ISPF panels is described.

In operation procedures, for panels containing the AC or COMMAND field,you are instructed to specify a slash (/) in the AC or COMMAND field todisplay the action selection panel and then select an action.

The panel display can also be changed by directly specifying an action in theAC or COMMAND field or by using point-and-shoot operations. Use theappropriate way as required.

The function keys assigned in this product are represented by function keynames (Fnn). The nn in Fnn indicates a standard number. If a user changesthese numbers, the numbers used in this manual will be different from thechanged numbers.

Workflow for when defining and checking tiering policygroups when using the ISPF panel

The following figure shows how to use ISPF panels to define a tiering policygroup and verify the created tiering policy group.

3-2 Tiered Storage Manager for Mainframe operations when using the ISPF panel




Figure 3-1 Procedure for defining and verifying a tiering policy group(ISPF panels)

Related topics

• Overview of files used by Tiered Storage Manager for Mainframe on page1-12

• Basic ISPF panel settings of Tiered Storage Manager for Mainframe onpage 3-4

• Scanning storage systems when using the ISPF panel on page 3-5

• Creating a tiering policy information CSV file when using the ISPF panelon page 3-7





• Defining tiering policy groups when using the ISPF panel on page 3-8

• Applying tiering policies when using the ISPF panel on page 3-8

• Checking volume information for the scanned storage system when usingthe ISPF panel on page 3-9

• Checking pool information for the scanned storage system when using theISPF panel on page 3-11

• Verifying definition information for the tiering policy group when using theISPF panel on page 3-14

• Verifying storage system information (summary) for the tiering policygroup when using the ISPF panel on page 3-15

• Checking SMS storage groups belonging to a tiering policy group whenusing the ISPF panel on page 3-16

• Verifying volume information for the tiering policy group when using theISPF panel on page 3-17

• Verifying pool information for the tiering policy group when using the ISPFpanel on page 3-19

Starting Tiered Storage Manager for Mainframe anddisplaying the main panel

This section describes how to start Tiered Storage Manager for Mainframeand display the main panel.

Procedure

1. In the ISPF Primary Option Menu panel, select 6 Command.

The ISPF Command Shell panel appears.

2.

Enter KTSTART.The main panel for Tiered Storage Manager for Mainframe appears.

Tip: When you display the main panel for the first time, the EditDefaults panel appears. Use this panel to specify the basic informationfor using ISPF panels to operate Tiered Storage Manager for Mainframe.

Related topics


• Main panel (common) on page 5-16

Basic ISPF panel settings of Tiered Storage Manager forMainframe

Use the Edit Defaults panel to specify basic information necessary for usingthe ISPF panels to operate Tiered Storage Manager for Mainframe.





Procedure

1. In the main panel, select the Set Defaults 'Defaults' point-and-shootfield.

The Set Defaults area appears.

2. Select the <Edit> point-and-shoot field.

The Edit Defaults panel appears.

3. Enter values for the items, and then press Enter.

The setting is saved.

Caution: If you want to install and use Tiered Storage Manager forMainframe in the same system as Business Continuity Manager, you must

make sure that the prefix character strings for Business ContinuityManager and Tiered Storage Manager for Mainframe are different. If thesame prefix is used for both Business Continuity Manager and TieredStorage Manager for Mainframe, the product may operate abnormally.

Tip: In each panel, press the DispConf function key (F17) to display thebasic information you specified here for the ISPF panels. As a default,because only 12 function keys are displayed, DispConf is not displayed in thelist of function keys. To display DispConf , set the number of displayedfunction keys to 24.

Related topics

• Setting the number of displayed function keys on page 3-35


• Set Defaults area on page 5-18

Defining tiering policy groups when using the ISPF panel

This section describes how to define a tiering policy group by using the ISPFpanels.

Scanning storage systems when using the ISPF panelTo scan storage systems, specify the scan target in the Device Scan Scopepanel, and then press the Scan function key (F6). By scanning a storagesystem, you can acquire its disk configuration information. The acquired diskconfiguration information is saved in the disk configuration definition file.





Prerequisites

• To specify the scan range by using an SMS storage group or volume serialnumbers, bring the volumes online.

Procedure

1. In the main panel, select the Storage System List 'Storage' point-and-shoot field.

The Storage System List area appears.

2. Select the <Scan> point-and-shoot field.

The Device Scan Scope panel appears.

3. Do either of the following:

¢ To specify an SMS storage group to be scanned:

Enter a slash (/) in the Storage Group field and specify the name of the target SMS storage group. Then press the Scan function key (F6).

Tip: If you perform either of the actions below without entering anSMS storage group name, the Storage Group Selection List panel

appears. You can use it to select the desired SMS storage group fromthe list.

• Press the Scan function key (F6).

• Point the cursor to the entry field for the SMS storage groupname, and then press Enter.

¢ To specify volumes to be scanned:

Enter a slash (/) in the Volser or Device Number field, specify therange of volumes to be scanned in the Start and End fields, and thenpress the Scan function key (F6).

The numbers of detected volumes are displayed in the Device Scan

Scope panel.4. Press the Exit function key.

The Confirm Configuration File Update panel appears. Confirm thatyou want to update the disk configuration definition file.

5. Press Enter.

The scan results are saved in the disk configuration definition file, and alist of scanned storage systems appears in the Storage System Listarea.

Tip: If the disk configuration changes significantly after the scan (forexample, the storage systems are replaced or the device numbers of

volumes change due to changes in I/O definitions), you must delete thedisk configuration definition file. Then rescan the storage systems. If necessary, define the tiering policy group again.

Postrequisites

• Creating a tiering policy information CSV file





Related topics


• Device Scan Scope panel on page 5-12

• Storage System List area on page 5-19

Creating a tiering policy information CSV file when using the ISPFpanel

To create a tiering policy information CSV file, assign the policy ID to the filein the Policy CSV List area in the main panel, and then edit the contents of the file.

Procedure

1. In the main panel, select the Policy CSV List 'Policy' point-and-shootfield.

The Policy CSV List area appears.

2. Select the <Create> point-and-shoot field.

The Policy ID Entry Field panel appears.

3. Specify the policy ID to be assigned to the tiering policy information CSVfile, and then press Enter.

The tiering policy information CSV file is created, and the policy IDappears in the Policy CSV List area.

4. Enter a slash (/) in the AC field for the policy ID.

Enter a slash (/) in the AC field for the tiering policy information CSV fileto which you assigned the policy ID.

The Policy CSV List Actions panel appears.

5. Enter 3 in the entry field or select the Edit 'E' point-and-shoot field.The ISPF edit panel for editing the tiering policy information CSV fileappears.

6. Specify information about a tiering policy group to be defined in a CSVfile.

7. Press the Exit function key.

The specified information is saved, and the Policy CSV List area appearsagain.

Postrequisites

• Defining tiering policy groups

Related topics


• Policy CSV List area on page 5-20

• Policy ID Entry panel on page 5-22





• Chapter 7, Files used by Tiered Storage Manager for Mainframe on page7-1

Defining tiering policy groups when using the ISPF panel

To define a tiering policy group, import the tiering policy information CSV filein the Policy CSV List area in the main panel.

Prerequisites

• Scanning the storage system

• Create a tiering policy information CSV file.

Procedure



2. Enter a slash (/) in the AC field for the tiering policy inf ormation CSV file.


3. Enter 4 in the entry field or select the Import 'I' point-and-shoot field.

The tiering policy information CSV file is imported and the tiering policygroup is defined. The defined information is saved in the tiering policygroup definition file.

Postrequisites

• Applying tiering policies

Related topics



• Applying tiering policies when using the ISPF panel on page 3-8


Applying tiering policies when using the ISPF panel

After you have defined a tiering policy group, you must apply the definedtiering policies to the storage system. To apply tiering policies, in the main

panel, specify the action for the tiering policy group in the Tiering PolicyGroup List area.

Prerequisites

• Defining tiering policy groups.





Procedure

1. In the main panel, select the Tiering Policy Group List 'TPG' point-and-shoot field.

The Tiering Policy Group List area appears.

2. Enter a slash (/) in the COMMAND field for the tiering policy group towhich you want to apply the tiering policies.

The Tiering Policy Group List Actions panel appears.

3. Enter 2 in the entry field or select the Activate 'ACT' point-and-shootfield.

The Confirm TPG Activation panel appears.

4. Enter a slash (/) in the Yes, activate the TPG. field, and then pressEnter.

The tiering policies are applied to the storage system.

Related topics



Verification after scanning storage systems when using theISPF panel

The following describes how to verify information about the volumes andpools after scanning storage systems.

Checking volume information for the scanned storage system whenusing the ISPF panel

To check the volume information for the scanned storage system, in the mainpanel, from the Storage System List area, open the Volume SelectionList panel, and then check details about the selected volumes in the VolumeStatus Detail panel.

Procedure



2. Enter a slash (/) in the AC field for the storage system containing the

volumes whose information you want to view.The Storage System List Actions panel appears.

3. Enter 1 in the entry field or select the Volume Selection 'V' point-and-shoot field.

The Volume Selection List panel displays a list of volumes that belongto the specified storage system.





4. To display details about a specific volume, enter a slash (/) in the ACfield.

The Volume Selection List Actions panel appears.

Tip: In this step, you can select a point-and-shoot device number insteadof entering a slash (/) in the AC field. This will directly change the paneldisplay to the Volume Status Detail panel.

5. Enter 1 in the entry field or select the Volume Status Detail 'V' point-and-shoot field.

The Volume Status Detail panel displays details about the volume.





Related topics


• Volume Selection List panel on page 5-36

• Volume Status Detail panel on page 5-37

Checking pool information for the scanned storage system whenusing the ISPF panel

To check the pool information for the scanned storage system, in the mainpanel, from the Storage System List area, open the Pool Selection Listpanel, and then check details about the selected pools in the Pool StatusDetail panel.

Procedure







2. Enter a slash (/) in the AC field for the storage system containing thepools whose information you want to view.

The Storage System List Actions panel appears.

3. Enter 2 in the entry field or select the Pool Selection 'P' point-and-shootfield.

The Pool Selection List panel displays a list of pools that belong to thespecified storage system.

4. To display details about a specific pool, enter a slash (/) in the AC field.

The Pool Selection List Actions panel appears.

Tip: In this step, you can select a point-and-shoot pool ID instead of

entering a slash (/) in the AC field. This will directly change the paneldisplay to the Pool Status Detail panel.

5. Enter 1 in the entry field or select the Pool Status Detail 'P' point-and-shoot field.

The Pool Status Detail panel displays details about the pool.





Related topics


• Pool Selection List panel on page 5-23

• Pool Status Detail panel on page 5-24

Verification after defining a tiering policy group when usingthe ISPF panel

This section describes how to verify the management targets (volumes,pools, and SMS storage groups) after you have defined a tiering policy group.





Verifying definition information for the tiering policy group whenusing the ISPF panel

To verify definition information for the defined tiering policy group, in themain panel, from the Tiering Policy Group List area, open the TieringPolicy Group Definition panel.

Procedure



2. Enter a slash (/) in the COMMAND field for the tiering policy group whoseinformation you want to view.


3. Enter 7 in the entry field or select the Definition 'D' point-and-shootfield.

The Tiering Policy Group Definition panel displays definitioninformation for the specified tiering policy group.

Related topics

• Tiering Policy Group List area on page 5-21

• Tiering Policy Group Definition panel on page 5-26





Verifying storage system information (summary) for the tieringpolicy group when using the ISPF panel

To verify storage system information (summary) for the defined tiering policygroup, in the main panel, from the Tiering Policy Group List area, open theTiering Policy Group Summary panel.

Procedure



2. Enter a slash (/) in the COMMAND field of the tiering policy group forwhich you want to view information.


3. Enter 1 in the entry field or select the Summary 'S' point-and-shootfield.

The Tiering Policy Group Summary panel displays storage systeminformation for the specified tiering policy group.

Related topics


• Tiering Policy Group Summary panel on page 5-31





Checking SMS storage groups belonging to a tiering policy groupwhen using the ISPF panel

To verify information about the SMS storage groups belonging to the definedtiering policy group, in the main panel, from the Tiering Policy Group Listarea, open the Tiering Policy Group Storage Group List panel.

Procedure





3. Enter 4 in the entry field or select the Storage Groups 'SG' point-and-shoot field.

The Select Storage Group List panel appears.

4. Select 1 to display a list of all SMS storage groups contained in the tieringpolicy group. If you want to filter the SMS storage groups to be displayed,select 2 and then specify the filter condition in the Storage Group Namefield.

The Tiering Policy Group Storage Group List panel displaysinformation about the SMS storage groups.





Related topics


• Tiering Policy Group Storage Group List panel on page 5-30

• How to specify the search or filter conditions in ISPF panels on pageB-6

Verifying volume information for the tiering policy group when usingthe ISPF panel

To verify information about the volumes belonging to the defined tieringpolicy group, in the main panel, f rom the Tiering Policy Group List area,open the Tiering Policy Group Volume List panel, and then check detailsabout the selected volumes in the Tiering Policy Group Volume StatusDetail panel.

Procedure





3. Enter 5 in the entry field or select the Volumes 'V' point-and-shoot field.

The Select Volume List panel appears.





4. Select 1 to display a list of all volumes contained in the tiering policygroup. If you want to filter the volumes to be displayed, select 2 and thenspecify filter conditions in the Volser field.

The Tiering Policy Group Volume List panel displays information aboutthe volumes.

5. To display information about a specific volume, enter a slash (/) in the ACfield.

The Tiering Policy Group Volume List Actions panel appears.

Tip: In this step, you can select a point-and-shoot device number insteadof entering a slash (/) in the AC field. This will directly change the paneldisplay to the Tiering Policy Group Volume Status Detail panel.

6. Enter 1 in the entry field or select the TPG Volume Status Detail 'V'point-and-shoot field.

The Tiering Policy Group Volume Status Detail panel displays thevolume information for the tiering policy group.





Related topics


• Tiering Policy Group Volume List panel on page 5-33

• Tiering Policy Group Volume Status Detail panel on page 5-35


Verifying pool information for the tiering policy group when usingthe ISPF panel

To verify information about the pools belonging to the defined tiering policy

group, in the main panel, from the Tiering Policy Group List area, open theTiering Policy Group Pool List panel, and then check details about theselected pools in the Tiering Policy Group Pool Status Detail panel.





Procedure





3. Enter 6 in the entry field or select the Pools 'P' point-and-shoot field.

The Select Pool List panel appears.

4. Select 1 to display a list of all pools contained in the tiering policy group.If you want to filter the pools to be displayed, select 2 and then specifythe filter conditions in the Pool Name field.

The Tiering Policy Group Pool List panel displays information about thepools.

5. To display information about a specific pool, enter a slash (/) in the ACfield.

The Tiering Policy Group Pool List Actions panel appears.

Tip: In this step, you can select a pool ID point-and-shoot field instead of specifying a slash (/) in the AC field. This will directly change the paneldisplay to the Tiering Policy Group Pool Status Detail.





6. Enter 1 in the entry field or select the TPG Pool Status Detail 'P' point-and-shoot field.

The Tiering Policy Group Pool Status Detail panel displays the poolinformation for the tiering policy group..

Related topics


• Tiering Policy Group Pool List panel on page 5-27

• Tiering Policy Group Pool Status Detail panel on page 5-28

• How to specify the search or filter conditions in ISPF panels on page

B-6





Frequently used checking methods when using the ISPFpanel

This section describes the check methods that are frequently used in theTiered Storage Manager for Mainframe panels.

Checking whether the tiering policies are applied to the storage

system when using the ISPF panel

To check whether the tiering policies are applied to the storage system, usethe Tiering Policy Group Summary panel displayed from the TieringPolicy Group List area in the main panel. Use this panel to find any volumesfor which the definitions of tiering policies differ from the current status.

Procedure



2. Enter a slash (/) in the COMMAND field for the tiering policy group to bechecked for whether tiering policies have been applied.



The Mismatch field in the Tiering Policy Group Summary paneldisplays the number of volumes in which the definitions of tiering policiesdiffer from the current status.





4. To check the volumes that contain inconsistencies, select the Mismatchpoint-and-shoot field.

The Tiering Policy Group Volume List panel displays a list of volumesfor which the definitions of tiering policies differ from the current status.

5. To check the tiering policies for a specific volume, enter a slash (/) in theAC field.

The Tiering Policy Group Volume List Actions panel appears.





Tip: In this step, you can select a point-and-shoot device number insteadof entering a slash (/) in the AC field. This will directly change the paneldisplay to the Tiering Policy Group Volume Status Detail panel.

6. Enter 1 in the entry field or select the TPG Volume Status Detail 'V'point-and-shoot field.

The Tiering Policy Group Volume Status Detail panel appears. Tieringpolicies for which the values in the Definition field differ from the values

in the CurrentState field have not been applied to the storage system.

Related topics









Checking the tier relocation status for volumes when using the ISPFpanel

To check the tier relocation status for volumes, use the Relocation statefield in the Tiering Policy Group Summary panel displayed from theTiering Policy Group List area in the main panel.

Procedure



2. Enter a slash (/) in the COMMAND field for the tiering policy group to bechecked for the tier relocation status for volumes.



The Relocation state field of the Tiering Policy Group Summary paneldisplays the tier relocation status.

If the number of volumes displayed in the Out of range field is 1 ormore, the tiering policy group is being relocated or is waiting for the nextrelocation.

If the number of volumes displayed in the Shortage field is 1 or more,pages in some volumes cannot be assigned to the tiers that belong to thespecified level due to insufficient pool capacity. You must take actions





such as increasing the capacity for the tiers with insufficient pool capacity,or moving data to another pool.

4. To check the volumes for each relocation status, select the In range,Out of range, or Shortage point-and-shoot fields.

The Tiering Policy Group Volume List panel displays a list of volumesin the relocation status you selected above. (The following panel appearsif you selected Shortage).

Use the PoolID field to check the ID of a pool with insufficient capacity.

Related topics




Checking whether the usage of any pool equals or exceeds thethreshold when using the ISPF panel

To check whether the usage of any pool equals or exceeds the threshold setin the Set Defaults area in the main panel, use the Tiering Policy GroupSummary panel displayed from the Tiering Policy Group List area in themain panel. In this panel, check the values shown in the Pools exceedingthreshold field.

Procedure







2. Enter a slash (/) in the COMMAND field for the tiering policy group forwhich you want to find pools whose usage equals or exceeds thethreshold.



In the Tiering Policy Group Summary panel, the number of pools

whose usage equals or exceeds the threshold appears in the Poolsexceeding threshold field.

4. To view the pools whose usage equals or exceeds the threshold, selectthe Pools exceeding threshold point-and-shoot field.

The Tiering Policy Group Pool List panel displays a list of pools whoseusage equals or exceeds the threshold.

Related topics








About changing tiering policy groups when using the ISPFpanel

This section describes how to change tiering policy groups by using the ISPFpanels.

Changing a tiering policy when using the ISPF panel

If you need to change a tiering policy due to lowered I/O performance or achange in the purpose for which volumes are being used, modify the createdtiering policy information CSV file, update the definition, and then apply theupdate to the storage system.

Procedure

1. Change the tiering policy information CSV file.

2. In the main panel, select the Policy CSV List 'Policy' point-and-shootfield to update the definition of the tiering policy group.


3. Enter a slash (/) in the AC field for the modified tiering policy informationCSV file.



The modified tiering policy information CSV file is imported and thedefinition of the tiering policy group is updated.



6. Enter a slash (/) in the COMMAND field for the tiering policy group whose

definition was modified.The Tiering Policy Group List Actions panel appears.




The definition of the modified tiering policy group is applied to the storagesystem.

Related topics

• Modifying the tiering policy information CSV file when using the ISPFpanel on page 3-31








• Examples of changing a tiering policy information CSV file on page 7-9

Adding a volume to a tiering policy group when using the ISPF panel

To add a volume to a tiering policy group, first add the volume to thedefinition of the tiering policy group, and then apply the tiering policies to thestorage system.

Prerequisites

• Maybe say prior to doing a scan by SMS storage group or volume serialnumbers, the volumes must be online.

Procedure


¢ If adding a volume to an SMS storage group in a tiering policy group:

Add the volume to the definition of the SMS storage group. You do notneed to add any records to the tiering policy information CSV file.

¢ If the volume to be added to a tiering policy group does not belong toan SMS storage group:

In the tiering policy information CSV file, add the record for thevolume that you want to add.

2. If the volume to be added has not been scanned, scan that volume toupdate the disk configuration definition file.

Information about the volume to be added is saved in the diskconfiguration definition file.


The Policy CSV List area appears.4. Enter a slash (/) in the AC field for the tiering policy information CSV file.



The tiering policy information CSV file is imported and the volume isadded to the definition of the tiering policy group.



7. Enter a slash (/) in the COMMAND field for the tiering policy group whosedefinition was modified.









The updated definition of the tiering policy group is applied to the storagesystem.

Related topics






• Examples of changing a tiering policy information CSV file on page 7-9

Deleting a specific volume from a tiering policy group when using theISPF panel

To delete a specific volume from a tiering policy group, first change thetiering policy of the volume applied to the storage system back to the default

(if necessary) and then delete the volume from the definition of the tieringpolicy group.

Caution: After you delete a volume from the definition, the tiering policy forthat volume can no longer be changed because Tiered Storage Manager forMainframe does not manipulate that volume.

Tip: You can change the tiering policy of the volume to be deleted back tothe default by changing the panel display from the Storage System Listarea to the Volume Selection List panel, specifying D for the AC field, andthen executing Deactivate Device.

Procedure


¢ If the volume to be deleted belongs to an SMS storage group:

Exclude the volume from the SMS storage group.

¢ If the volume to be deleted does not belong to an SMS storage group:

Delete the record for the volume from the tiering policy informationCSV file.


The Policy CSV List area appears.3. Enter a slash (/) in the AC field for the tiering policy information CSV file.



The tiering policy information CSV file is imported and the definition of thetiering policy group is updated.





Related topics






Modifying the tiering policy information CSV file when using the ISPFpanel

To modify the tiering policy information CSV file, specify an action for thetarget file on the Policy CSV List area in the main panel.

Use the following procedure to modify the tiering policy information CSV file.

Procedure



2. Enter a slash (/) in the AC field for the target tiering policy informationCSV file.


3. Enter 3 in the entry field or select the Edit 'E' point-and-shoot field.

The ISPF edit panel for editing the tiering policy information CSV fileappears.

4. Modify the contents of the tiering policy information CSV file.

5. Press the Exit function key.The modifications are saved, and the Policy CSV List area appearsagain.

Related topics



Convenient use of list panelsThis section describes the convenient use of list panels (panels such as theTiering Policy Group Volume List panels that display a list of volumes,pools, or SMS storage groups).





Sorting items

To sort items displayed in a listing panel, select the point-and-shoot headerof the items.

Procedure

1. Select the header in the listing panel.

The items in the field of the header are sorted.

Tip: Another way to sort the items is to enter SORT in the command line

of the ISPF panel to display the Sort Options panel, and specify the sortconditions.

Filtering displayed information

To filter the displayed information, use the Filter Options panel to specifyfilter conditions, and then press Enter.

Procedure

1. Enter FILTER in the command line of the ISPF panel, and then pressEnter.

The Filter Options panel appears.

2. Specify the filter conditions.

The following is an example specification. The displayed items varydepending on the panel that called this panel.

3. Press Enter.The information is filtered according to the specified filter conditions.

Related topics






Searching character strings

To search a character string in a listing panel, use the Find Options panel tospecify the search string, and then press Enter. To conduct another searchby using the same search string, press the Rfind function key.

Procedure

1. Enter FIND in the command line of the ISPF panel, and then press Enter.The Find Options panel appears.

2. Specify the search string.

The following is an example specification.

3. Press Enter.

The cursor is positioned at a line containing the specified search string.4. To conduct another search by using the same search string, press the

Rfind function key.

The cursor is positioned at another line containing the specified searchstring.

Related topics


Positioning the cursor at a specific line in a sorted fieldTo position the cursor at a specific line in a sorted field, use the LocateOptions panel to specify the search string, and then press Enter.

Prerequisites

• Data in the field in which the cursor is to be positioned has been sorted.

Procedure

1. Enter LOCATE in the command line of the ISPF panel, and then press

Enter.The Locate Options panel appears.

2. Specify the search string.

The following is an example specification. The displayed items varydepending on the panel that called this panel.





3. Press Enter.The cursor is positioned at a line containing the specified search string.

Related topics


Setting an action in multiple AC fields

To set or cancel an action in multiple AC fields in a list panel, use the SelectOptions panel to specify the target field, the condition character string for

the field, and the action, and then press Enter.

Procedure

1. Enter SELECT in the command line of the ISPF panel, and then pressEnter.

The Select Options panel appears.

2. Specify the AC fields for which the action is to be set or canceled byspecifying the target fields, the condition character string for the fields,and an action.

The following is an example specification. The displayed items vary

depending on the panel that called this panel.

3. Press Enter.

The action is set or canceled for multiple AC fields.





Note: The action is not set or canceled for the lines that are not displayed bythe filter.

Related topics


Customizing the ISPF panels

This section describes the settings needed to customize the ISPF panels.

Setting the command line location

Use the ISPF Settings panel to position the command line (Command line)at the top or bottom of the panel.

Procedure

1. Enter SETTINGS in the command line of the ISPF panel.

The ISPF Settings panel appears.

2. Clear the Command line at bottom check box to display the commandline at the top of the panel. Select this check box to display the commandline at the bottom of the panel.

Setting the number of displayed function keys

Use the ISPF Settings panel to set 12 or 24 as the number of displayedfunction keys.

Procedure

1. Enter PFSHOW TAILOR in the command line of the ISPF panel.


2. Enter 1 (12) or 2 (24) in the Number of keys field.

If you entered 2 (24), enter 3 (All - display all keys) in the Display setfield.

Highlighting available point-and-shoot fields

Use the ISPF Settings panel to specify the setting to highlight the availablepoint-and-shoot fields.

Procedure

1. Enter PSCOLOR in the command line of the ISPF panel.






2. Set REVERSE in the Highlight column of the Point-and-Shoot row.





4

Tiered Storage Manager for Mainframeoperations when using the CLI

This chapter describes how to use CLI commands to operate Tiered StorageManager for Mainframe.

□ Defining and verifying a tiering policy group when using the CLI

commands

□ Defining tiering policy groups when using the CLI commands

□ Verification after defining a tiering policy group when using the CLI

commands

□ About changing tiering policy groups when using the CLI commands

Tiered Storage Manager for Mainframe operations when using the CLI 4-1




Defining and verifying a tiering policy group when using theCLI commands

The figure below shows the workflow for defining and verifying a tiering policygroup by using the CLI commands.

This figure explains the steps of the procedure, along with the commands andsample scripts to be executed in the procedure.

Figure 4-1 Workflow for defining and verifying a tiering policy group (CLIcommands)

4-2 Tiered Storage Manager for Mainframe operations when using the CLI




Related topics

• Overview of files used by Tiered Storage Manager for Mainframe on page1-12

• Checking volume information when using the CLI commands on page4-3

• Scanning the storage system when using the CLI commands on page4-5

• Creating a tiering policy information CSV file when using the CLIcommands on page 4-7

• Defining tiering policy groups when using the CLI commands on page4-7

• Applying tiering policies when using the CLI commands on page 4-9

• Verifying tiering policies when using the CLI commands on page 4-11

• Checking the progress of tier relocation when using the CLI commands onpage 4-12

• Checking volume I/O performance on page 4-14

Defining tiering policy groups when using the CLIcommands

This section describes how to define a tiering policy group by using the CLIcommands.

Checking volume information when using the CLI commands

Before defining a tiering policy group, acquire volume information from thestorage system by executing the KTQRYDEV command for the volumes to be

defined, and then check the volume information.

Based on the acquired information for volumes, consider how they are usedfor tasks and examine the tiering policy group to be defined.





Figure 4-2 Checking volume information (CLI commands)

Procedure

1. Specify a volume for which you want to acquire information, and thenexecute the KTQRYDEV command.

The acquired volume information is stored in the host-discovered arraystructure and the device information structure.

Reference scripts

For details about how to create the script, see sample script KTDEMO04.

Example

The following shows an example of volume information acquired by executingsample script KTDEMO04 (KTQRYDEV command).

DKC SN:14001,Model:VSP,Microcode:xxxxxxxx ,IFType:1414

Pool ID, Type,Pool Name ,Media(Tier1,Tier2,Tier3) 1, DT,POOLID1 ,"SSD","SAS 15K","SATA 7.2K"

Volume Devn,Volser,CU,SSID,CCA,POOLID,TLv, Entry,Reloc 1101,VOL001,00,0000, 00, 1, 1, HIGH, Y

Postrequisites


Related topics

• Scanning the storage system when using the CLI commands on page4-5





• KTQRYDEV on page 6-17

• KTDEMO04 (Display the volume information) on page C-11

Scanning the storage system when using the CLI commands

To scan the storage system, first execute the KTSCAN command, and then

execute the KTSTORE command to save the scan results.

Figure 4-3 Scanning the storage system (CLI commands)

Prerequisites

• To define a tiering policy group by specifying an SMS storage group orvolume serial numbers, place the volumes online to allow the volumeserial numbers to be detected.

Procedure

1. Specify the scan range, and then execute the KTSCAN command.

The command acquires disk configuration information, and stores it in thehost-discovered array structure and host-discovered array indexstructure.

2. Execute the KTSTORE command.

The data in the host-discovered array structure is saved in the diskconfiguration definition file.

Tip: To view the contents of the disk configuration definition file, execute theKTGETHDA command.

Tip: If the disk configuration changes significantly after the scan (forexample, because the storage system is replaced or device numbers of volumes change due to changes in I/O definitions), you must delete the diskconfiguration definition file. Then rescan the storage system. If necessary,change the definition of the tiering policy group.





Reference scripts

For details about how to create the script, see the following sample scripts.

• Creating a disk configuration definition file: KTDEMO00

• Checking the contents of the created disk configuration definition file:KTDEMO01

Example 1:The code in this example scans devices 0000 through 00FF and volumes FF00through FFFF, and saves the scan results in the disk configuration definitionfile.

CALL KTSCAN "STEM(stem1.) MSG(msgstem.) FROM(0000) TO(00FF)";CALL KTSCAN "STEM(stem1.) MSG(msgstem.) FROM(FF00) TO(FFFF)";CALL KTSTORE "STEM(stem1.) MSG(msgstem.) PREFIX(PREFIX1)";

Example 2:

The code in this example scans the volumes with volume serial numbers fromVOL001 through VOL999, and saves the scan results in the disk configuration

definition file.CALL KTSCAN "STEM(stem1.) MSG(msgstem.) FROMVSN(VOL001)", "TOVSN(VOL999)";CALL KTSTORE "STEM(stem1.) MSG(msgstem.) PREFIX(PREFIX1)";

Example 3:

The code in this example scans the volumes that belong to SMS storagegroup SG1, and saves the scan results in the disk configuration definition file.

CALL KTSCAN "STEM(stem1.) MSG(msgstem.) STORGRP(SG1)";CALL KTSTORE "STEM(stem1.) MSG(msgstem.) PREFIX(PREFIX1)";

Postrequisites


Related topics

• Creating a tiering policy information CSV file when using the CLIcommands on page 4-7

• KTGETHDA on page 6-9

• KTSCAN on page 6-25

• KTSTORE on page 6-28

• KTDEMO00 (Create a disk configuration definition file) on page C-3

• KTDEMO01 (Display the contents of the disk configuration definition file)on page C-5





Creating a tiering policy information CSV file when using the CLIcommands

Specify information about the SMS storage groups or volumes to be definedas a policy group in a CSV file.

For the tiering policy information CSV file, assign a name in the followingformat: prefix .POLICY. policy-ID . prefix is the character string to be

specified in Configuration file prefix on the Edit Defaults panel, or thecharacter string to be specified in the PREFIX parameter of CLI commands.

Make sure that you specify a character string common to the three types of files used by Tiered Storage Manager for Mainframe.

Procedure

1. Determine the configuration of tiering policy groups, and the tieringpolicies to be set for the tiering policy groups.

Specify values for the tiering policy level and the new-page assignmenttier, and whether to execute tier relocation.

2. Create a tiering policy information CSV file.

For details on information that should be written in the CSV file, refer tothe information about tiering policy information CSV files.

Postrequisites

• Defining tiering policy groups

Related topics

• Defining tiering policy groups when using the CLI commands on page4-7


Defining tiering policy groups when using the CLI commands

To define a tiering policy group, execute the KTIMPORT command to import

the tiering policy information CSV file and the disk configuration definitionfile.

If the volumes to be defined have not been scanned yet, you can execute theKTIMPORT command with the SCAN parameter specified to scan the volumes

and create a tiering policy group definition file simultaneously.





Figure 4-4 Defining tiering policy groups (CLI commands)

Prerequisites



• Varying the volumes online if the record type of the tiering policyinformation CSV file is specified as STORGRP or VOLSER.

Procedure

1. Execute the KTIMPORT command.The command reads the data in the tiering policy information CSV file anddisk configuration definition file, and creates a tiering policy groupdefinition file.

Tip: If the SCAN parameter is specified, the command scans the range of

the storage system specified in the tiering policy information CSV file, andcreates a disk configuration definition file and a tiering policy groupdefinition file.

Reference scripts


• Creating a tiering policy group definition file: KTDEMO02

• Checking the contents of the created tiering policy group definition file:KTDEMO03





Example 1:

The code in this example imports a disk configuration definition file whoseprefix is PREFIX1 and a tiering policy information CSV file whose policy ID isPOLICY1, and creates a tiering policy group definition file.

CALL KTIMPORT "MSG(msgstem.) PREFIX(PREFIX1) POLICY(POLICY1)";

Example 2:

The code in this example imports a tiering policy information CSV file whosepolicy ID is POLICY1, and creates a disk configuration definition file whoseprefix is PREFIX1 and a tiering policy group definition file simultaneously.

CALL KTIMPORT "MSG(msgstem.) PREFIX(PREFIX1) POLICY(POLICY1) SCAN";

Postrequisites

• Applying tiering policies

Related topics

• Scanning the storage system when using the CLI commands on page 4-5• Creating a tiering policy information CSV file when using the CLI

commands on page 4-7

• Applying tiering policies when using the CLI commands on page 4-9

• KTIMPORT on page 6-12

• KTDEMO02 (Create a tiering policy group definition file) on page C-8

• KTDEMO03 (Display the contents of the tiering policy group definition file)on page C-10

Applying tiering policies when using the CLI commands

After you have defined a tiering policy group, you must apply the definedtiering policies to the storage system. To apply tiering policies, use theKTLOAD command to load the configuration files to the REXX variable

structure, and then execute the KTACTTPG command.





Figure 4-5 Applying tiering policies (CLI commands)

Prerequisites

• Defining tiering policy groups.

Procedure

1. Execute the KTLOAD command.

Target volume information and information about the tiering policiesdefined in configuration files is loaded from the configuration files to theREXX variable structure.

2. Execute the KTACTTPG command.

The data set in the REXX variable structures is applied to the storagesystem.

Reference scripts


Example:

The code in this example applies the tiering policies of tiering policy groupsTPG1 and TPG2 to the storage system.

CALL KTLOAD "STEM(stem1.) MSG(msgstem.) PREFIX(PREFIX1) TPG(TPG1)";CALL KTACTTPG "STEM(stem1.) MSG(msgstem.)";CALL KTLOAD "STEM(stem2.) MSG(msgstem.) PREFIX(PREFIX1) TPG(TPG2)";CALL KTACTTPG "STEM(stem2.) MSG(msgstem.)";





Postrequisites

• Verification after defining a tiering policy group

Related topics

• Defining tiering policy groups when using the CLI commands on page 4-7

• Verification after defining a tiering policy group when using the CLI

commands on page 4-11• KTACTTPG on page 6-5

• KTLOAD on page 6-14

• KTDEMO10 (Apply the tiering policy) on page C-15

Verification after defining a tiering policy group when usingthe CLI commands

This section describes how to use CLI commands to verify information afteryou have defined a tiering policy group.

Verifying tiering policies when using the CLI commands

By executing the KTQRYTPG command for each tiering policy group, you can

acquire from the storage system the tiering policy information that is set toeach volume. You can view the acquired information to verify tiering policiesapplied to the storage system.

If you want to acquire the tiering policy information for a volume, execute theKTQRYDEV command.

Procedure1. Perform either of the following operations to acquire information about

the tiering policies from the storage system.

¢ To acquire information for each tiering policy group, execute theKTLOAD command, and then the KTQRYTPG command.

¢ To acquire information for each volume, execute the KTQRYDEV

command.

2. View the acquired information, and confirm whether the tiering policieshave been applied.

Reference scripts


• To verify the tiering policies of a tiering policy group: KTDEMO11

• To verify the tiering policies of a volume: KTDEMO04





Example :

The following shows an example of the tiering policy information specified foreach volume in tiering policy group TPG1 acquired by executing sample scriptKTDEMO11 (KTLOAD and KTQRYTPG commands).

Tiering Policy Group Name: TPG1

Volumes Devn,Volser,STORGRP ,SN ,CU,SSID,CCA,POOLID,TLv, Entry,Reloc 0000,VOL001,SG1 ,14001,00,0000, 00, 1, 1,MIDDLE, Y

:

Related topics



• KTQRYTPG on page 6-21


• KTDEMO11 (Check the tiering policy) on page C-16

Checking the progress of tier relocation when using the CLIcommands

By executing the KTQRYTPG command or the KTQRYRLC command, you can

acquire the page relocation status of each volume in the tiering policy groupsor information about Dynamic Tiering for Mainframe pools. You can view theacquired information to check the progress of tier relocation.

Procedure

1. Execute theKTLOAD

command.

The contents of the configuration files are loaded into REXX variablestructures.

2. Execute either of the following commands.

¢ To acquire the page relocation status of each volume:

Execute the KTQRYTPG command.

¢ To acquire the progress information about tier relocation for eachDynamic Tiering for Mainframe pool:

Execute the KTQRYRLC command.

3. View the acquired information and check the progress of tier relocation.

Reference scripts


• To acquire the page relocation status of each volume: KTDEMO12





• To acquire progress information about tier relocation for each DynamicTiering for Mainframe pool: KTDEMO13

Example 1:

The following shows an example of the data allocation information for eachtier of the volume acquired by executing sample script KTDEMO12 (KTLOAD

and KTQRYTPG commands).


Volumes Tier Status POOL Devn,Volser,SN ,CU,CCA, ID,TLv, Cylinders, Tier1Page, Tier2Page, Tier3Page 412D, ,14001,02, 2D, 2, 3, 3339, 0, 1, 0 412E, ,14001,02, 2E, 2, 3, 3339, 0, 1, 0

Example 2:

The following shows an example of information acquired by executing samplescript KTDEMO13 (the KTLOAD, KTQRYTPG, and KTQRYRLC commands). This

information shows the page relocation status of each volume in the tieringpolicy group TPG1 and the tier relocation progress for each Dynamic Tieringfor Mainframe pool.


Volumes POOL Devn,Volser,SN ,CU,CCA, ID,TLv,RelocateStatus ,LocatedPage/ TotalPage 0000,VOL001,14001,00, 00, 1, 3,done , 1/ 1 :

PoolsRelocate RelocateTime MigrationPageSN , ID, Type,Monitor,active %,Start, End,ExpectedCt,MigratedCt

14001, 1, DT, auto,Y 100%,00:00,01:00, 0, 0 :Pools tier status SN , ID,Tier, Used/ Capacity,EntryBuf%,RelocBuf%,Media 14001, 1, 1, 1/ 26 0%, 2%,"SSD" 14001, 1, 2, 263/ 2631 8%, 2%,"SAS 15K" 14001, 1, 3, 1036/ 131578 8%, 2%,"SATA 7.2K" 14001, 2, 1, 2/ 26 0%, 2%,"SSD" 14001, 2, 2, 263/ 2631 8%, 2%,"SAS 15K" 14001, 2, 3, 1036/ 131578 8%, 2%,"EXTERNAL H" :

Related topics

• KTLOAD on page 6-14• KTQRYRLC on page 6-19


• KTDEMO12 (Check the page relocation status) on page C-18

• KTDEMO13 (Check the relocation progress) on page C-20





Checking volume I/O performance

By executing the KTQSTATS command, you can acquire I/O performance

information (number of I/O operations for the drive media) for each volumein a tiering policy group. You can view the acquired information to check if there is any problem with the I/O performance of volumes.

Procedure



2. Execute the KTQSTATS command.

The volume I/O performance information is acquired.

Reference scripts


Example:The following shows an example of the volume I/O performance informationfor tiering policy group TPG1 acquired by executing sample script KTDEMO14(KTLOAD and KTQSTATS commands).

Tiering Policy Group Name : TPG1Monitor Interval Time(sec): 600

Volume I/O statistics ------------------------------------------------------- 11:23:00 - 11:33:00 ------------------------------------------------------- DEVN,Volser,STORGRP,SN ,CU,CCA,Tier1 IOPS,Tier2 IOPS,Tier3 IOPS 1101,VOL001,SG1 ,14001,00, 01, 100, 253, 1486

1201,VOL002,SG1 ,14001,00, 01, 20, 0, 0 ------------------------------------------------------- 11:33:00 - 11:43:00 ------------------------------------------------------- DEVN,Volser,STORGRP,SN ,CU,CCA,Tier1 IOPS,Tier2 IOPS,Tier3 IOPS 1101,VOL001,SG1 ,14001,00, 01, 60, 0, 0 1201,VOL002,SG1 ,14001,00, 01, 4, 0, 0 :

Related topics


• KTQSTATS on page 6-23

• KTDEMO14 (Check I/O performance information) on page C-26





About changing tiering policy groups when using the CLIcommands

This section describes how to change tiering policy groups by using CLIcommands.

Changing a tiering policy when using the CLI commands

If you need to change a tiering policy due to lowered I/O performance or achange in the purpose for which volumes are being used, modify the createdtiering policy information CSV file, update the definition, and then apply theupdate to the storage system.

Procedure

1. Change the tiering policy information CSV file.

2. Execute the KTIMPORT command.

The definition of the tiering policy group is updated with the contents of the modified tiering policy inf ormation CSV file.




Information about the modified tiering policy is applied to the storagesystem.

5. Execute the KTQRYTPG command to check the tiering policy.

Confirm that the tiering policy has been applied to the storage system.

Related topics

• KTACTTPG on page 6-5






Adding a volume to a tiering policy group when using the CLIcommands

To add a volume to a tiering policy group, add a volume to the definition of the tiering policy group, and then apply the tiering policies to the storagesystem.





Prerequisites

• To specify the scan range by SMS storage group or volume serial number,place the volume online.

Procedure

1. Perform either of the following operations:

¢ If adding a volume to an SMS storage group in a tiering policy group:Add the volume to the definition of the SMS storage group. You do notneed to add any records to the tiering policy information CSV file.

¢ If the volume to be added to a tiering policy group does not belong toan SMS storage group:

In the tiering policy information CSV file, add the record for thevolume that you want to add.

2. If the volume information to be added has not been scanned, you need toexecute the KTSCAN command with the volumes specified in the scan

range to update the disk configuration definition file.

The disk information of the volume to be added is stored in the host-

discovered array structure and host-discovered array index structure.

3. Execute the KTSTORE command.

The disk configuration definition file is updated.

4. Execute the KTIMPORT command to update the definition of the tiering

policy group.

The tiering policy group definition file is updated, and the volume isadded.


The contents of the updated configuration files are loaded into REXXvariable structures.


The contents of the updated configuration files set in the REXX variablestructures is applied to the storage system.

7. Execute the KTQRYTPG command.

Confirm whether the tiering policy has been applied to the added volume.

Tip: You can also update the disk configuration definition file by executingthe KTIMPORT command with the SCAN parameter specified, instead of

executing the KTSCAN and KTSTORE commands.

Related topics• KTACTTPG on page 6-5









• KTSCAN on page 6-25

• KTSTORE on page 6-28


Deleting a specific volume from a tiering policy group when using theCLI commands

To delete a specific volume from a tiering policy group, first change thetiering policy of the volume applied to the storage system back to the default(if necessary), and then delete the volume from the definition of the tieringpolicy group.

Caution: After you delete a volume from the definition, the tiering policy forthat volume can no longer be changed because Tiered Storage Manager forMainframe does not manipulate that volume.

Tip: You can use the KTDCTDEV command to change the tiering policy of the

volume to be deleted back to the default.

Procedure

1. Execute the KTQRYDEV command to view information about the volume to

be deleted.

2. Perform either of the following operations:

¢ If the volume to be deleted belongs to an SMS storage group:

Exclude the volume from the SMS storage group.

¢ If the volume to be deleted does not belong to an SMS storage group:

Delete the record for the volume from the tiering policy informationCSV file.

3. Execute the KTIMPORT command.

The volume is deleted from the definition of the tiering policy group.Tiered Storage Manager for Mainframe does not manipulate the volume.

Reference scripts

Refer to the sample script KTDEMO05 for details on how to create scripts forchanging the tiering policy of volumes back to the default by using theKTDCTDEV command.

Related topics

• KTDCTDEV on page 6-6








• KTDEMO05 (Change the tiering policy of a volume back to the default) onpage C-14





5

ISPF panels

This chapter describes transition, operation methods, and displayed items of the ISPF panel in Tiered Storage Manager for Mainframe.

□ Panel relationships of Tiered Storage Manager for Mainframe

□ Common items in the panel

□ Device Scan Scope panel

□ Edit Defaults panel

□ Error Code Help panel

□ Exception Message List panel

□ Main panel

□ Manage Licenses panel

□ Policy ID Entry panel

□ Pool Selection List panel

□ Pool Status Detail panel

□ Setting Information panel

□ Tiering Policy Group Definition panel

□ Tiering Policy Group Pool List panel

ISPF panels 5-1




□ Tiering Policy Group Pool Status Detail panel

□ Tiering Policy Group Storage Group List panel

□ Tiering Policy Group Summary panel

□ Tiering Policy Group Volume List panel

□ Tiering Policy Group Volume Status Detail panel

□ Volume Selection List panel

□ Volume Status Detail panel

5-2 ISPF panels




Panel relationships of Tiered Storage Manager forMainframe

The main panel is the panel that appears when Tiered Storage Manager forMainframe is started, and has five areas that are the gateways to eachoperation. Select the area according to the operation you want to perform.Select a point-and-shoot field or specify the action to move to the next panel.

The following figure shows the panel relationships of Tiered Storage Managerfor Mainframe.

Figure 5-1 Panel relationships of Tiered Storage Manager for Mainframe

ISPF panels 5-3




Common items in the panel

This section describes the common items between the panels for TieredStorage Manager for Mainframe.

About the layout of the panels

This section describes the layout of the panels for Tiered Storage Manager for

Mainframe.

The following figure indicates the layout of the Tiering Policy Group PoolList panel.

About the action bar

The action bar of the Tiered Storage Manager for Mainframe panel containsthe Goto, Commands, and Help menus.

Goto

The Goto pull-down menu displays the name of the panels that you canmove to from the current panel.

5-4 ISPF panels




Figure 5-2 Goto pull-down menu (Tiering Policy Group Pool List panel)

Tip: When you select and move to a panel from the Goto pull-down menu,and then press Exit function key or Cancel function key in the panel thatappears, you will return to the main panel, not to the original panel.

Commands

The Commands pull-down menu displays the command that can be executedin the current panel.

Figure 5-3 Commands pull-down menu (Tiering Policy Group Pool Listpanel)

Help

The Help pull-down menu displays the name of the Help panels that can be

referenced from the current panel.

Figure 5-4 Help pull-down menu (Main panel)

Related topics

• Commands that can be used in the command line

About the AC and COMMAND fields

These are fields for specifying the action of the target.

ISPF panels 5-5




The following are some example of values that can be specified for the AC orCOMMAND field. For other specifiable values, see the explanation for eachpanel.

Specifiable value for AC or COMMAND field

Action

V Displays the list or detailed information of the volumes.

P Displays the list or detailed information of the pools.

SG Displays the list of SMS storage groups.

ACT Applies the tiering policy to the storage system.

DCT Changes the tiering policy to default status.

/ Displays the list of actions (actions panels) that can bespecified for each panel.

Tip: If you position the cursor in the AC or COMMAND field and then pressthe Enter key, the system operates the same as when / is specified.

The following figure show an example of actions panels when / is specified toAC or COMMAND field.

5-6 ISPF panels




About point-and-shoot field

When you place the cursor on a selectable point-and-shoot field and then

press the Enter key, the action set to that field can be executed.

In this manual, selectable point-and-shoot fields are indicated in light-bluetext. In order to check which point-and-shoot fields are selectable in theactual panel, enable the highlighting settings.

ISPF panels 5-7




Tip: Depending on the settings of the terminal emulator, you can selectpoint-and-shoot fields by using the mouse, instead of by pressing the Enterkey. For details on this setting, see the documentation for the terminalemulator that you are using.

The following explains the actions that are executed when you select a point-and-shoot field.

Table 5-1 Actions that are executed when you select a point-and-shootfield

Location Executed action

Header of thelist

Sorts the rows based on the field value under the correspondingheader.

Field Displays a panel that displays a list or detailed information for thecorresponding field.

Tip: If the list you are displaying has PoolID and SN as the header and youselect the PoolID point-and-shoot field, SN and PoolID will be sorted in a

multi-column sort. If the list you are displaying has CU and CCA as theheader and you select the CCA point-and-shoot field, CU and CCA will besorted in a multi-column sort.

Example of point-and-shoot actions

• Header of the list

When you select the State header point-and-shoot field, the rows aresorted based on the values in the State header.

5-8 ISPF panels




• Field

The following is a representative example of an action executed byselecting a point-and-shoot field.

Point-and-shoot fields Action that is executed

Volume statuses such as In range,Mismatch, and Pools exceedingthreshold

Displays the list of volumes of the selectedstatus.

ISPF panels 5-9




Point-and-shoot fields Action that is executed

Volumes, pools Displays the details of the selected volumesor pools.

The following example show the list of volumes when the volume status isselected as the point and shoot field.

5-10 ISPF panels




Related topics

• Highlighting available point-and-shoot fields on page 3-35

ISPF panels 5-11




About the display unit

For the panels that have a capacity or used capacity displayed, Unit: unit isdisplayed on the top right-corner in the panel. The display unit is either Pageor GB.

If the list is displayed in units of GB, the number after the decimal point istruncated and displayed for the capacity and used capacity. However, if thevalue is less than 1, the displayed value is rounded up.

If you select the Unit point-and-shoot field, the following Switch the Unitpanel appears, and you can change the unit to be displayed.

Device Scan Scope panel

In this panel, you can scan a storage system volumes that are connected to ahost. Specify a scan target with an SMS storage group name, volume serialnumber, or device number, and then press the Scan function key (F6).

5-12 ISPF panels




Item Description

Storage Group To specify the target by SMS storage group, specify /,and then in the input field, enter an SMS storagegroup name to be scanned.

Specify /, and then without entering an SMS storagegroup name, press the Enter key with the cursor onthe input field or press the Scan function key (F6) todisplay the Storage Group Selection List pop-upwindow. A list of selectable SMS storage groups isdisplayed.

Volser To specify the target by volume serial number,specify /, and then specify the range of volume serialnumbers to be scanned in Start and End (order of EBCDIC codes).

To scan only one volume, specify the same value forStart and End.

Device Number To specify the target by device number, specify /, andthen specify the range of device numbers to bescanned in Start and End (ascending hexadecimalnumber order).

To scan only one volume, specify the same value forStart and End.

When scanning finishes, the panel displays the unit used for the scan, thescope of the scan, and the number of detected volumes.

After scanning, press the Exit function key to create or update diskconfiguration definition files with the following name, and save theconfiguration information of the detected volumes:

• prefix .DSK.SNnnnnn.LOCAL

prefix : The prefix value specified to Configuration file prefix in the Set

Defaults areannnnn: The serial number of the storage system

Press the Cancel function key to discard the changes and exit.

Related topics

• Set Defaults area on page 5-18

Edit Defaults panel

In this pop-up window, you can edit basic settings for operating TieredStorage Manager for Mainframe from the ISPF panel.

ISPF panels 5-13




Item Description

ISPF log max Specifies the upper limit for the number of messagesthat are output to the ISPF log when one command isexecuted. The value for this option should be aninteger that is either 0 or between 10 and 5000,inclusive. The recommended value is 100. If no valueis specified, 0 will be set, and the number of messageswill not be limited.

• 0: The number of messages is not limited (allmessages are output).

• 10 to 5000: The specified number (integer) of messages are output.

Pool usage threshold Specifies the threshold for the pool usage ratebetween 0 and 100. The number of pools whose usagerate equals or exceeds the threshold specified by thisitem is displayed in Pool Summary in the TieringPolicy Group Summary panel. If no value isspecified, 80 will be set.

Capacity unit The capacity unit for volumes, pools, SMS storagegroups, and tiering policy groups. Specify either Page(pages) or GB (gigabytes). If no value is specified,Page will be set.

Related topics


Error Code Help panel

You can specify an error code to display the error code details.

5-14 ISPF panels




Item Description

Type of error Displays the type of errors.

Exception Message List panel

This pop-up window displays warnings and error messages of a requestedoperation in chronological order. Operations and output messages are storedin the ISPF log. If there are multiple messages, you can scroll across thepanel.

At the top of the line, the results of the executed command are displayed.

ISPF panels 5-15




Item Description

Message If the message shows an error code, the error codedetails are displayed in the Error Code Help panel byplacing the cursor on the displayed error code andthen pressing the ErrCode function key (F4).

Operations and output messages are stored in the ISPF log.

Press the Cancel function key to close the panel.

Related topics

• Error Code Help panel on page 5-14

Main panel

This section explains the Main panel and the areas in the panel.

Main panel (common)

The panel appears when Tiered Storage Manager for Mainframe is started. Inthe main panel, you can list each target object. There are some object linesin the middle of the panel. Select the line point-and-shoot field to expand theaccordion menu of the target object. To contract the accordian menu, selectthe point-and-shoot field on the line again.

Item Description

Installation Management Displays operation menus related to the installation of Tiered Storage Manager for Mainframe.

5-16 ISPF panels




Item Description

Set Defaults Displays basic setting for using Tiered StorageManager for Mainframe on ISPF panel.

Storage System List Display a list of storage systems for storage systemactions.

Policy CSV List Display a list of tiering policy information CSV fileactions.

Tiering Policy Group List Display a list of tiering policy group actions.

Tip: In the upper part of the panel, items in the accordion menu areabbreviated as a shortcut bar. The accordion menu is also expanded byselecting a shortcut bar item that is a point-and-shoot field. Short cut baritem is also executed from the command line by entering the item name.

Related topics

• Installation Management area on page 5-17

• Set Defaults area on page 5-18• Storage System List area on page 5-19



Installation Management area

This area displays operation menus related to the installation of TieredStorage Manager for Mainframe.

ISPF panels 5-17




Item Description

<Licenses> Select the <Licenses> point-and-shoot field to go tothe Manage Licenses panel for registering ordisplaying license information.

Related topics


Set Defaults area

This area displays basic settings for operating Tiered Storage Manager forMainframe from the ISPF panel.

Item Description

<Edit> Select the <Edit> point-and-shoot field to display theEdit Defaults pop-up window where you can editbasic settings.

ISPF log max Displays the upper limit for the number of messagesthat can be output to the ISPF log when one commandis executed.

• 0: The number of messages is not limited (allmessages are output).

• 10 to 5000: The specified number (integer) of messages are output.

Pool usage threshold Displays the threshold for pool usage rate. Thenumber of pools whose usage rate equals or exceedsthis value is displayed in Pool Summary in theTiering Policy Group Summary panel.

5-18 ISPF panels




Item Description

Capacity unit Displays the unit for capacity and usage on volumes,pools, SMS storage groups, and tiering policy groups.

Related topics

• Edit Defaults panel on page 5-13• Tiering Policy Group Summary panel on page 5-31

Storage System List area

In this area you can perform actions for storage systems.

Item Description

<Scan> Select the <Scan> point-and-shoot field to go to the Device ScanScope panel to scan storage systems.

AC The action to be executed for the selected storage system.

You can specify the following actions:

• V: Goes to the Volume Selection List panel.

• P: Goes to the Pool Selection List panel.

• D: Deletes the disk configuration definition file for the selected

storage system.

Related topics

• Device Scan Scope panel on page 5-12

• Pool Selection List panel on page 5-23

ISPF panels 5-19





Policy CSV List area

In this area, you can perform actions for tiering policy information CSV files.

Item Description

<Create> Select the <Create> point-and-shoot field to displaythe Policy ID Entry pop-up window for creatingtiering policy information CSV files.

AC The action to be executed for the selected tieringpolicy information CSV file.


• V: Displays the contents of the selected tieringpolicy information CSV file.

• C: Copies the selected tiering policy informationCSV file. The Policy ID Entry panel for enteringthe policy ID of the tiering policy information CSVfile at the copy destination appears.

• E: Displays the panel for editing the contents of the selected tiering policy information CSV file.

• I: Imports the selected tiering policy informationCSV file, to create creates a tiering policy groupdefinition file.

• D: Deletes the selected tiering policy informationCSV file.

Related topics

• Policy ID Entry panel on page 5-22

5-20 ISPF panels




Tiering Policy Group List area

In this area, you can perform actions for tiering policy groups.

Item Description

COMMAND The action to be executed for the selected tiering policy group.


• S: Goes to the Tiering Policy Group Summary panel.

• ACT: Applies the tiering policy to the storage systems.

• DCT: Changes the tiering policy back to the default.

• SG: Goes to the Tiering Policy Group Storage Group Listpanel.

• V: Goes to the Tiering Policy Group Volume List panel.

• P: Goes to the Tiering Policy Group Pool List panel.

• D: Goes to the Tiering Policy Group Definition panel.

• DEL: Deletes the tiering policy group definition file.

In addition to the action characters, the TSO/E command, REXXexec and CLIST can be specified on the COMMAND field. Prefix andtiering policy group ID character strings are passed to the specifiedcommand in this order as parameters.

Related topics

• Tiering Policy Group Definition panel on page 5-26


• Tiering Policy Group Storage Group List panel on page 5-30



ISPF panels 5-21




Manage Licenses panel

In this panel, you can register a license or display the license information forTiered Storage Manager for Mainframe.

Item Description

PP Name Displays the license name.

• HTSM for MF: Tiered Storage Manager forMainframe license

If a license key for Business Continuity Manager isinstalled in the license information dataset, theBusiness Continuity Manager license is also displayed.

Model Displays the model code for the storage system. Forthe displayed values, see Help.

Type Displays the license type.

• Perm.: Permanent license

• Temp.: Temporary license

• Emer.: Emergency license

Capacity Displays the licensed capacity (unit: TB). If Unlimitedis displayed, the capacity is unlimited.

Policy ID Entry panel

In this panel, you can specify a policy ID for creating or copying tiering policyinformation CSV files.

5-22 ISPF panels




Item Description

Policy ID The policy ID for a tiering policy information CSV file.

• To create a file: Specify a policy ID for the file tobe created.

• To copy a file: Specify the policy ID of the copydestination file.Specify a valid value as a symbolicname because the policy ID is used as a qualifierof a data set name.

Pool Selection List panel

This panel displays a list of pools in a storage system.

Item Description

AC Specify the action to be executed for the selected

pool.You can specify the following actions:

• V: Goes to the Volume Selection List panel.This panel displays the list of volumes that belongto the selected pool.

• P: Goes to the Pool Status Detail panel. Thispanel displays details of the selected pool.

ISPF panels 5-23




Item Description

PoolName Displays the pool name up to 16 characters. You canview pool names that exceed 16 characters in theTiering Policy Group Pool Status Detail panel.

Related topics

• Pool Status Detail panel on page 5-24



Pool Status Detail panel

This panel displays detail information of the selected pool.

5-24 ISPF panels




Current Relocation Information

Displays the current relocation status and capacity and usage information foreach tier.

Item Description

Relocation mode Displays the monitoring mode.

• Auto: Automatic execution mode (tier relocation is performed

automatically)• Manual: Manual execution mode

Relocation status Displays the relocating status.

• In progress: Relocation is in progress

• Finished or stopped: Relocation has finished or stopped

Progress rate Displays the relocation progress (%).

If relocation has never been performed, no value is displayed.

Buffer for Entry(%) Displays the free-area-ratio for new-page assignment (%).

Reloc(%) Displays the ratio (%) of the relocation buffer area.

Previous Relocation Information

Displays the information about the result of the tier relocation that wasexecuted in the previous cycle. If tier relocation has never been performed,the item will be blank.

Item Description

Expected Displays the expected number of migrated pages.

Migrated Displays the migrated pages.

Basic Information

Displays the basic information of the pool.

Setting Information panel

This pop-up window displays basic information for operating Tiered StorageManager for Mainframe from the ISPF panel.

ISPF panels 5-25




Item Description

ISPF Log Max Displays the upper limit of the number of messages that are output tothe ISPF log when one command is executed.

Pool usage threshold Displays the threshold for the pool usage rate. The number of poolswhose usage rate equals or exceeds this value is displayed in PoolSummary in the Tiering Policy Group Summary panel.

Capacity UnitDisplays the unit for capacity and usage on volumes, pools, SMS storagegroups, and tiering policy groups.

Related topics


Tiering Policy Group Definition panel

This panel displays the contents of the tiering policy group definition.

Item Description

AC Specify the action to be executed for the selected volume.


• V: Goes to the Tiering Policy Group Volume Status Detail panel.• P: Goes to the Tiering Policy Group Pool Status Detail panel.

TLv Displays the tiering policy level. The tier to which pages are assigned isshown in the Tiering Policy Group Volume Status Detail panel.

Entry Displays the tier to which new pages are assigned.

• HIGH: New pages are assigned to the higher tier.

5-26 ISPF panels




Item Description

• MIDDLE: New pages are assigned to the middle tier.

• LOW: New pages are assigned to the lower tier.

Reloc Displays whether tier relocation is executed.

• Y: Tier relocation is enabled.

• N : Tier relocation is disabled.

Related topics



Tiering Policy Group Pool List panel

This panel displays a list of pools in a tiering policy group. To display eachtier's capacity information in the right-hand panel, either press the Next

function key or select the Next ---> point-and-shoot field. To return to theleft-hand panel, either press the Prev function key or select the <--- Prevpoint-and-shoot field.

The following figure shows the left-hand panel of the Tiering Policy GroupPool List panel:

The following figure shows the right-hand panel of the Tiering Policy GroupPool List panel:

ISPF panels 5-27




Item DescriptionAC Specify the action to be executed for the selected pool.


• P: Goes to the Tiering Policy Group Pool Status Detail panel.

PoolName Displays the pool name up to 16 characters. You can view pool names thatexceed 16 characters in the Tiering Policy Group Pool Status Detail panel.

Related topics


Tiering Policy Group Pool Status Detail panel

This panel displays detailed information of the selected pool that belongs tothe tiering policy group.

5-28 ISPF panels




Current Relocation Information

Displays the current relocation status and the capacity and usage informationfor each tier.

Item Description

Relocationmode

Displays the monitoring mode.

• Auto: Automatic execution mode (tier relocation is performed automatically)

• Manual: Manual execution mode

Relocationstatus

Displays the relocation status.

• In progress: Relocation is in progress• Finished or stopped: Relocation is finished or stopped

Progress rate Displays the relocation progress (%).

If relocation has never been performed, no value is displayed.

Bufferfor

Entry(%)

Displays the free-area-ratio for new-page assignment (%).

ISPF panels 5-29




Item Description

Reloc(%)

Displays the ratio (%) of the relocation buffer area.

Previous Relocation Information

Displays the information about the result of the tier relocation that wasexecuted in the previous cycle. If relocation has never been performed, thisitem is blank.

Item Description

Expected Displays the expected number of migrated pages.

Migrated Displays the migrated pages.

Basic Information

Displays the basic information of the pool.

Tiering Policy Group Storage Group List panel

This panel displays a list of SMS storage groups to which the volumes in thetiering policy group belong, and information about the capacity of thosestorage groups.

Item Description

AC Specify the action to be executed for the selected storage group.

5-30 ISPF panels




Item Description

• V: Goes to the Tiering Policy Group Volume List panel.

Tier1, Tier2, Tier3 Displays the amount of space used on each tier by all the volumes thatbelong to the SMS storage group.

%T1, %T2, %T3 Displays the distribution ratio (%) of the usage of each tier by all thevolumes that belong to the SMS storage group.

Total Displays the total amount of space used by all the volumes that belong tothe SMS storage group.

Related topics


Tiering Policy Group Summary panel

This panel displays the following information about a tiering policy group:capacity information, page relocation status, pools whose usage rate equalsor exceeds the threshold, and whether the tiering policy is correctly applied tothe storage system. In this panel, you can check the summary statusinformation of the tiering policy group. To go to the detailed informationpanel, select a field name point-and-shoot field.

ISPF panels 5-31




TPG Summary - Capacity and usage information

Item Description

Tier1, Tier2, Tier3 Displays the amount of space used on each tier by all volumes that belongto tiering policy group.

%T1, %T2, %T3 Displays the distribution ratio (%) of the usage of each tier by all volumesthat belong to the tiering policy group.

Total Displays the total amount of space used by all volumes that belong to thetiering policy group.

Capacity Displays the total capacity of all volumes in the tiering policy group.

Volume Summary - Relocation state

Item Description

In range Displays the number of volumes for which all pages in the volume areassigned to the tiers specified by tiering policy level. Select the In rangepoint-and-shoot filed to display the volumes whose statuses are In range in

the Tiering Policy Group Volume List panel.

Out of range Displays the number of volumes for which some pages in the volume are notassigned to the tiers specified by tiering policy level. Select the Out of range point-and-shoot filed to display the volumes whose statuses are Out

of range in the Tiering Policy Group Volume List panel.

Shortage Displays the number of volumes for which some pages in the volume are notassigned to the tiers specified by tiering policy level due to insufficient poolcapacity. Select the Shortage point-and-shoot filed to display the volumeswhose statuses are Shortage in the Tiering Policy Group Volume List

panel.

Tip: When a volume is in the Shortage status, you need to take measures

such as adding capacity to the pool or moving data to other pools.

Volume Summary - TPG definition and active policy comparison

Item Description

Mismatch Displays the number of volumes for which the tiering policy defined for thetiering policy group is different from the tiering policy set for the storagesystem. Select the Mismatch point-and-shoot filed to display thevolumeswhose statuses are Mismatch in the Tiering Policy Group Volume

List panel.

Pool Summary - Pool usage threshold

Item Description

Pools exceedingthreshold

Displays the number of pools whose usage rate equals or exceeds thethreshold specified for Pool usage threshold in the Edit Defaults panel.Select the Pools exceeding threshold point-and-shoot filed to display the

5-32 ISPF panels




Item Description

volumes whose usage rate equals or exceeds the threshold in the TieringPolicy Group Pool List panel.

Tip: When a pool is in the Pools exceeding threshold status, you need to

take measures such as adding capacity to the pool or moving data to otherpools.

Related topics




Tiering Policy Group Volume List panel

This panel displays a list of volumes in a tiering policy group and the status of

those volumes. To display each tier's capacity information in the right-handpanel, either press the Next function key or select the Next ---> point-and-shoot field. To return to the left-hand panel, either press the Prev functionkey or select the <--- Prev point-and-shoot field.

The following figure shows the left-hand panel of the Tiering Policy GroupVolume List panel:

The following figure shows the right-hand panel of the Tiering Policy GroupVolume List panel:

ISPF panels 5-33




Item DescriptionAC Specify the action to be executed for the selected volume.

• V: Goes to the Tiering Policy Group Volume Status Detailpanel.

• P: Goes to the Tiering Policy Group Pool Status Detailpanel.

Diff If the tiering policy defined in the tiering policy group definition fileis different from the tiering policy set for the storage system, * isdisplayed. If these tiering policies are the same, nothing isdisplayed.

TLv Displays the tiering policy level set for the storage system. TheTiering Policy Group Volume Status Detail panel shows whichpages are assigned to which tier.

State Displays the volume relocation status.

• In range: All pages are assigned to the tiers specified bytiering policy level.

• Out of range: Some pages are not assigned to the tiersspecified by tiering policy level.

• Shortage: Some pages are not assigned to the tiers specifiedby tiering policy level due to insufficient pool capacity.

Tier1, Tier2, Tier3 Displays the amount of space used on each tier by the volume.

%T1, %T2, %T3 Displays the distribution ratio (%) of the usage of each tier by thevolume.

Total Displays the total amount of space used by the volume.

Capacity Displays the total capacity of the volume.

5-34 ISPF panels




Related topics



Tiering Policy Group Volume Status Detail panel

This panel displays detailed information of the selected volume that belongsto the tiering policy group.

Tiering Policy Information

Displays the tiering policy of the definition and of the current status in thestorage system.

Item Description

Relocation state Displays the relocation status of the volume.

• In range: All pages are assigned to the tiers specified by tiering policylevel.

ISPF panels 5-35




Item Description

• Out of range: Some pages are not assigned to the tiers specified bytiering policy level.

• Shortage: Some pages are not assigned to the tiers specified bytiering policy level due to insufficient pool capacity.

Tier level# Displays the tiering policy level.

Entry#

Displays the tier to which new pages are assigned.• HIGH: New pages are assigned to the higher tier.



Relocation# Displays whether tier relocation is executed.

Note:

The Definition column shows the value defined in the tiering policy groupdefinition file, and the CurrentState column shows the value set for thestorage system.

Information Per Tier

Displays information about the tiers of the volume.

Basic Information

Displays basic information about the volume.

Volume Selection List panel

This panel displays a list of volumes in the storage system.

5-36 ISPF panels




Item Description

AC Specify the action to be executed for the selected volume.


• V: Goes to the Volume Status Detail panel. This panel displays detailedinformation about the selected volume.

• P: Goes to the Pool Status Detail panel. This panel displays detailedinformation about the selected pool.

• D: Restores the default tiering policy for the volume (tiering policy level: 0,tier to which new pages are assigned: MIDDLE, whether to execute tierrelocation: Y).

CCA The following information, which indicates whether the volume is an externalvolume, is displayed to the right-hand side of the command control addressnumber.

• +: The volume is an external volume.

• -: The volume is not an external volume.

• Blank: Whether the volume is an external volume is unknown.

Related topics• Pool Status Detail panel on page 5-24

• Volume Status Detail panel on page 5-37

Volume Status Detail panel

This panel displays detail information of the selected volume.

ISPF panels 5-37




Tiering Policy Information

Displays the tiering policy of the current status in the storage system.

Item Description

Relocation state Displays the relocation status of the volume.

• In range: All pages are assigned to the tiers specified by tiering policylevel.

• Out of range: Some pages are not assigned to the tiers specified bytiering policy level.

• Shortage: Some pages are not assigned to the tiers specified by tieringpolicy level due to insufficient pool capacity.

Tier level Displays the tiering policy level specified on the storage system.

Entry Displays the tier to which new pages are assigned that is specified on thestorage system.

• HIGH: New pages are assigned to the higher tier.



Relocation Displays whether tier relocation is executed on the storage system.

5-38 ISPF panels




Information Per Tier

Displays the information about the tiers of the volume.

Basic Information

Displays basic information about the volume.

ISPF panels 5-39




5-40 ISPF panels




6

CLI commands

This chapter describes the command functions that can be used in the TieredStorage Manager for Mainframe CLI.

□ List of CLI Commands

□ CLI command coding format

□ REXX external routine details

□ TSO/E command details

□ OS console command details

CLI commands 6-1




List of CLI Commands

The CLI commands provided by Tiered Storage Manager for Mainframe arecategorized into the following command types.

• REXX external routines

• TSO/E commands

• OS console commands

The following tables describe each of the CLI command types.

Table 6-1 REXX external routines

Commandname

Description

KTACTTPG Applies the tiering policy for a tiering policy group.

KTDCTDEV Changes the tiering policy of the specified volume back to the default.

KTDCTTPG Changes the tiering policy of a tiering policy group back to the default.

KTGETHDA Loads the disk configuration definition file to the REXX variable structure.

KTIMPORT Reads the tiering policy information CSV file and the disk configurationdefinition file, and then defines a tiering policy group (creates a tieringpolicy group definition file).

KTLOAD • Loads the tiering policy group definition file to the REXX variablestructure.

• Loads the disk configuration definition file to the REXX variablestructure.

KTQRYDEV Acquires information about the tiering policy for the specified volume andinformation about the pool to which the volume belongs, and then storesthe information in the REXX variable.

KTQRYRLC Acquires information such as the progress of page tier relocation for each

Dynamic Tiering for Mainframe pool to which the tiering policy groupbelongs from the storage system, and then stores the information in theREXX variable structure.

KTQRYTPG Acquires tiering policy information and page tier location status for atiering policy group from the storage system, and then stores theinformation in the REXX variable structure.

KTQSTATS Acquires I/O performance information for a tiering policy group from thestorage system, and then stores the information in the REXX variablestructure.

KTSCAN Scans the operation-target volumes for Tiered Storage Manager forMainframe to acquire the information necessary to identify the volumes,and then sets the information to the REXX variable structure.

KTSTORE • Saves the values of the host-discovered array structure generated bythe KTSCAN or KTLOAD command in the disk configuration definition

file.

• Saves the values of the tiering policy group structure generated bythe KTLOAD command in the tiering policy group definition file.

KTWTOMSG Outputs the specified message ID and message text to the console.

6-2 CLI commands




Table 6-2 TSO/E commands

Commandname

Description

KTCONMSG Monitors the messages output to the console.

KTENV Outputs the following information to the TSO/E terminal:

• Program product name

• Prefix of the license information dataset

• Output method of event logs

• Whether CLI command-execution logs are output to SYSLOG or theconsole

KTERCODE Outputs the information for the specified error code and the cause of theerror to the TSO/E terminal.

KTINSCHK Checks the setting items required for setup for incomplete or incorrectinformation, and outputs the check results and settings to the TSO/Eterminal.

KTSLEEP Suspends the execution of the script for the specified period of time.

Table 6-3 OS console commands

Commandname

Description

KTALCSVC Registers or deletes a user SVC.

KTDSPENV Displays the following information on the console.

• Program product name

• Prefix of the license information dataset



KTSETENV Sets the following values using environment variables:

• Prefixes of the license information dataset



CLI command coding format

This section describes the CLI command coding format for each commandtype.

CLI commands 6-3




REXX external routine coding format

REXX external routines provided by Tiered Storage Manager for Mainframemust be called as subroutines. Therefore, write a REXX script as shownbelow, and then execute the script.

REXX script coding format

CALL 1command-name 1" parameter "

Script coding method

• Use the RESULT variable to acquire the return code of a CLI command.

• When a CLI command is executed, values are set or updated in the REXXvariable structure. To check the command execution results, code a REXXscript to output the REXX variables in the REXX variable structure.

• When a CLI command is executed, a message is generated by thecommand. That message is stored in the REXX variable messagestructure. The message structure is initialized each time a CLI commandwith the same message structure name specified is called.

• Before executing any one of the CLI commands listed below, you mustexecute the KTLOAD command. The KTLOAD command loads the

information necessary for executing the CLI command from theconfiguration file to the REXX variable structure.

¢ KTACTTPG

¢ KTDCTTPG

¢ KTQRYRLC

¢ KTQRYTPG

¢ KTQSTATS

• Multiple REXX variable structures are expanded for a single CLI command.If only some of the REXX variable structures are deleted, subsequentlyissued commands might not operate normally. To delete REXX variablestructures, you need to delete all the related REXX variable structures.

Related topics

• Chapter 8, REXX variable structures on page 8-1

TSO/E command coding format

To execute a CLI command categorized as a TSO/E command from a REXX

script, code the script as follows.

REXX script coding format

ADDRESS 1TSO 1"command-name 1 parameter "

Use the RC variable to acquire the return code of a TSO/E command in the

REXX script.

6-4 CLI commands




OS console command coding format

To execute a CLI command categorized as an OS console command, enterthe command preceded by the START command from the console.

OS console command coding format

START 1 command-name[,PARM=' parameter ']

REXX external routine details

This section describes details about CLI commands categorized as REXXexternal routines. The commands are explained in alphabetic order.

KTACTTPG

Function

Applies the tiering policy for a tiering policy group.

Command type

REXX external routines

FormatKTACTTPG

1STEM(stem-name-1)

1MSG(stem-name-2)

Parameters

STEM(stem-name-1)~<REXX prefix consisting of 64 or fewer characters>

Specify the prefix of the tiering policy group structure to which the targettiering policy group was loaded. This is the character string specified forthe STEM parameter of the KTLOAD command that was previously

executed. This value must end with a period.

MSG(stem-name-2)~<REXX prefix consisting of 64 or fewer characters>

Specify the prefix (any value) of the message structure that storesmessages generated by this command. This value must end with aperiod.

Return codes

The following table lists and describes the codes returned when the KTACTTPG

command terminates. If the commands do not terminate normally, refer tothe resulting error messages for details.

CLI commands 6-5




Table 6-4 Return codes generated by the KTACTTPG command

Return code Meaning

0 The command ended normally.

12 An unsupported device was skipped.

32 An I/O error occurred.

36 The command ended due to an invalid REXX variablestructure.

40 An error occurred during writing of the REXX variables.

44 The command ended due to invalid processing.

48 The command ended due to an invalid parameter. Thepossible causes are as follows:

• The parameters were specified incorrectly.

• The KTLOAD command was not executed, or the value

specified for the STEM parameter is different from the

value of the STEM parameter of the KTLOAD command.

52 The command ended due to an incorrect execution method.The possible causes are as follows:

• The MSG parameter was specified incorrectly.

• Installation was not performed correctly.

REXX variables that are updated by the KTACTTPG command

• All REXX variables in the message structure

• The following REXX variables in the host-discovered array structure

A REXX variable name is preceded by the value specified for the STEM

parameter.¢ LOCAL.SNnnnnn.CUxx .CCAxx .TierLevel

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Entry

¢ LOCAL.SNnnnnn.CUxx .CCAxx .TierRelocation

Related topics

• Message structure on page 8-2

• Host-discovered array structure on page 8-4

• KTDEMO10 (Apply the tiering policy) on page C-15

KTDCTDEV

Function

Changes the tiering policy for a volume back to the following default values.

6-6 CLI commands




• Tiering policy level: 0

• New-page assignment tier: MIDDLE

• Whether to execute tier relocation: Y

Command type

REXX external routine

FormatKTDCTDEV

1MSG(stem-name-1)

1DEVN(nnnn)

Parameters


Specify the prefix (any value) of the message structure that storesmessages generated by this command. This value must end with a

period.

DEVN(nnnn)~<four hexadecimal characters string>

Specify the device number of the volume for which the tiering policy willbe changed back to the default.

Return codes

The following table lists and describes the codes returned when the KTDCTDEV


Table 6-5 Return codes generated by the KTDCTDEV command

Return code Meaning






48 The command ended due to an invalid parameter. Thepossible cause is as follows:





CLI commands 6-7




REXX variables that are updated by the KTDCTDEV command

• All variables in the message structure

Related topics


• KTDEMO05 (Change the tiering policy of a volume back to the default) on

page C-14

KTDCTTPG

Function

Changes the tiering policy for a tiering policy group back to the followingdefault values.




Command type


FormatKTDCTTPG

1STEM(stem-name-1)

1MSG(stem-name-2)

Parameters


Specify the prefix of the tiering policy group structure to which the targettiering policy group was loaded. This is the character string specified forthe STEM parameter of the KTLOAD command that was previously

executed. This value must end with a period.


Specify the prefix (any value) of the name of the message structure thatstores messages generated by this command. This value must end with aperiod.

Return codes

The following table lists and describes the codes returned when the KTDCTTPG


6-8 CLI commands




Table 6-6 Return codes generated by the KTDCTTPG command

Return code Meaning















REXX variables that are updated by the KTDCTTPG command


• The following variables in the host-discovered array structure


parameter.¢ LOCAL.SNnnnnn.CUxx .CCAxx .TierLevel



Related topics



KTGETHDA

Function

Loads the information from the disk configuration definition file to the host-discovered array structure and host-discovered array index structure.

CLI commands 6-9




Command type


FormatKTGETHDA

1STEM(stem-name-1)

1MSG(stem-name-2)

1PREFIX( prefix )

1SN(serial-number )

Parameters


Specify the prefix (any value) of the host-discovered array structure towhich the information will be loaded from the disk configuration definitionfile. This value must end with a period.



PREFIX( prefix )~<prefix character string of 25 or fewer characters>

Specify the prefix of the disk configuration definition file to be read.

SN(storage-system-serial-number )~<5-12 alphanumeric characters>

Specify the serial number of the storage system from which informationwill be read.

Reference note

If the KTGETHDA command with the same value specified for the STEM

parameter is executed multiple times, all execution results are valid as longas the SN parameter, which specifies a storage system, has a unique value. If

a host-discovered array structure has already been set by executing anotherCLI command, information for the same REXX variable name will beoverwritten.

Return codes

The following table lists and describes the codes returned when the KTGETHDA

command terminates. If the commands do not terminate normally, refer to

the resulting error messages for details.

Table 6-7 Return codes generated by the KTGETHDA command

Return code Meaning


6-10 CLI commands




Return code Meaning

4 An unknown XML attribute or element is found in the inputfile.

36 XML data in the input file ends with an invalid structure.

40 • An error occurred during reading of the file.

• An error occurred during writing of the REXX variables.







REXX variables that are updated by the KTGETHDA command• All variables in the message structure

• All variables in the host-discovered array index structure

The prefix of the host-discovered array index structure is "HCC.HDAKT.".



parameter.

¢ LOCAL.SNnnnnn.SerialNum

¢ LOCAL.SNnnnnn.Microcode

¢

LOCAL.SNnnnnn.IFType¢ LOCAL.SNnnnnn.PhysicalSerialNum

¢ LOCAL.SNnnnnn.LDKCNum

¢ LOCAL.SNnnnnn.CUxx .SSID

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Devn

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Volser

¢ LOCAL.SNnnnnn.CUxx .CCAxx .STORGRP

¢ LOCAL.SNnnnnn.CUxx .CCAxx .SSID

¢ LOCAL.SNnnnnn.CUxx .CCAxx .POOLID

¢

LOCAL.SNnnnnn.CUxx .CCAxx .Cyls¢ LOCAL.SNnnnnn.CUxx .CCAxx .External

¢ LOCAL.SNnnnnn.POOLxx .NAME

¢ LOCAL.SNnnnnn.POOLxx .Type

¢ LOCAL.SNnnnnn.POOLxx .PageSize

¢ LOCAL.SNnnnnn.POOLxx .Tier.0

CLI commands 6-11




¢ LOCAL.SNnnnnn.POOLxx .Tier.n.Media

Related topics


• Host-discovered array index structure on page 8-3


• KTDEMO01 (Display the contents of the disk configuration definition file)on page C-5

KTIMPORT

Function

Reads the configuration information from the tiering policy information CSVfile and volume information from the disk configuration definition file, andthen creates a tiering policy group definition file.

Command type


Prerequisites

• If the SCAN parameter is not specified, volumes to be defined as a tiering

policy group must be defined in the disk configuration definition file inadvance by using the KTSCAN and KTSTORE commands.

• If the record type of the tiering policy information CSV file is STORGRP or

VOLSER, the volumes must be placed online.

FormatKTIMPORT

1MSG(stem-name-1)

1PREFIX( prefix )

1POLICY( policy-ID )

[ 1SCAN]

Parameters




Specify the prefix of the disk configuration definition file, tiering policygroup definition file, and tiering policy information CSV file.

6-12 CLI commands




POLICY( policy-ID )~<symbol name consisting of 8 or fewer characters>

Specify the policy-ID that identifies the tiering policy information CSV fileto be read. The tiering policy information CSV file whose name is PREFIX-

parameter-value.POLICY. policy-ID will be read.

SCAN

The volumes or the volumes belonging to the SMS storage group, which

are specified in the tiering policy information CSV file, will be scanned inthe same way as for the KTSCAN command. Then the detected volume

information will be output to the disk configuration definition file.

Tip: When you execute the KTIMPORT command, the following number of data

sets are allocated at the same time:

• If you specify the SCAN parameter: The number of disk configuration

definition files to be updated# + 2

#: The number of disk configuration definition files to be updated is thenumber of storage systems to be scanned.

• If you do not specify the SCAN parameter: 2

Therefore, ensure that the number of datasets allocated at the same timedoes not exceed the value of the DYNAMNBR parameter of the TSO/E logon

procedure or JCL.

Return codes

The following table lists and describes the codes returned when the KTIMPORT


Table 6-8 Return codes generated by the KTIMPORT command

Return codes Meaning

0 The command ended normally. REXX variables were created.

4 No records were defined in the tiering policy information CSVfile. Writing to the tiering policy group definition file was notperformed.

32 The specified CSV file had an error.

36 • An attempt to read SMS storage group information failed.

• An error occurred during internal command processing.

40 • An error occurred during CSV file input processing.






CLI commands 6-13




Return codes Meaning



20000 to 20099 An error occurred, possibly due to insufficient memory (thelast two digits are the REXX error number). For details aboutthe error, see the explanation of the IRX00nnI message

(replace nn with the last two digits of the return code) in the

manual TSO/E Messages.

REXX variables that are updated by the KTIMPORT command


Related topics


• KTDEMO02 (Create a tiering policy group definition file) on page C-8

KTLOAD

Function

Loads the information necessary for Tiered Storage Manager for Mainframeoperation from the following configuration files to the REXX variablestructures.

• Loads the tiering policy group definition file to the tiering policy groupstructure.

• Loads the disk configuration definition file to the host-discovered array

structure and host-discovered array index structure.

Command type


FormatKTLOAD

1STEM(stem-name-1)

1MSG(stem-name-2)

1PREFIX( prefix )

1TPG(tiering-policy-group-ID )

Parameters


6-14 CLI commands




Specify the prefix (any value) of the REXX variable structure to which theinformation will be loaded from the configuration file. This value must endwith a period.

If the KTLOAD command with the same value specified for the STEM

parameter is executed multiple times, the REXX variable will beoverwritten. To specify operations for multiple tiering policy groups in thesame script, specify a unique value of the STEM parameter for each tiering

policy group.MSG(stem-name-2)~<REXX prefix consisting of 64 or fewer characters>



Specify the prefix of the configuration file from which information will beloaded.

TPG(tiering-policy-group-ID )~<prefix character string>

Specify the tiering policy group ID.

This is the tiering policy group definition file name with prefix .TPG.

removed.

Return codes

The following table lists and describes the codes returned when the KTLOAD


Table 6-9 Return codes generated by the KTLOAD command

Return code Meaning


4 An unknown XML attribute or element was found in the inputfile.

36 XML data in the input file ends with an invalid structure.

40 • An error occurred during reading of the configuration file.








CLI commands 6-15




REXX variables that are updated by the KTLOAD command



The prefix of the host-discovered array index structure is "HCC.HDAKT.".



parameter.¢ LOCAL.SNnnnnn.SerialNum


¢ LOCAL.SNnnnnn.IFType

¢ LOCAL.SNnnnnn.PhysicalSerialNum





¢ LOCAL.SNnnnnn.CUxx .CCAxx .STORGRP¢ LOCAL.SNnnnnn.CUxx .CCAxx .SSID


¢ LOCAL.SNnnnnn.CUxx .CCAxx .Cyls

¢ LOCAL.SNnnnnn.CUxx .CCAxx .External





¢

LOCAL.SNnnnnn.POOLxx .Tier.n.Media• The following variables in the tiering policy group structure


parameter.

¢ TPG.ID

¢ TPG.VOL.0

¢ TPG.VOL.n.SerialNum

¢ TPG.VOL.n.CUNum

¢ TPG.VOL.n.CCA

¢

TPG.VOL.n.POOLID¢ TPG.VOL.n.SSID

¢ TPG.VOL.n.TierLevel

¢ TPG.VOL.n.TierRelocation

6-16 CLI commands




Related topics




• Tiering policy group structure on page 8-9

• KTDEMO03 (Display the contents of the tiering policy group definition file)

on page C-10

KTQRYDEV

Function

Acquires the following information about the specified volume from thestorage system, and then stores the information in the REXX variablestructure.

• Tiering policy configuration information

• Page tier location status

• I/O performance information

• Configuration information for the pool to which the volume belongs

Command type


FormatKTQRYDEV

1STEM(stem-name-1)

1MSG(stem-name-2)1DEVN(nnnn)

Parameters


Specify the prefix (any value) of the host-discovered array structure anddevice information structure that store the acquired information. Thisvalue must end with a period.


Specify the prefix (any value) of the message structure that stores

messages generated by this command. This value must end with aperiod.

DEVN(nnnn)~<four hexadecimal characters string>

Specify the device number of the volume for which information will beacquired.

CLI commands 6-17




Return codes

The following table lists and describes the codes returned when the KTQRYDEV


Table 6-10 Return codes generated by the KTQRYDEV command

Return code Meaning


4 A storage system of unknown model was detected. REXXvariables of the specified volume were not created.






52 The command ended due to an invalid execution method. Thepossible causes are as follows:



REXX variables that are updated by the KTQRYDEV command




parameter.








¢ LOCAL.SNnnnnn.CUxx .CCAxx .VOLSER





¢ LOCAL.SNnnnnn.CUxx .CCAxx .TierLevel

6-18 CLI commands






¢ LOCAL.SNnnnnn.CUxx .CCAxx .Used

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.0

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.n.Used

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.n.IO.Ct






¢ LOCAL.SNnnnnn.POOLxx .Tier.n.Capacity

¢ LOCAL.SNnnnnn.POOLxx .Tier.n.Used

¢ LOCAL.SNnnnnn.POOLxx .Tier.n.Unit

¢ LOCAL.SNnnnnn.POOLxx .Tier.n.EntryBufferPerCent

¢ LOCAL.SNnnnnn.POOLxx .Tier.n.RelocateBufferPerCent¢ LOCAL.SNnnnnn.POOLxx .Tier.n.m.ExpectedMigrationPageCt

¢ LOCAL.SNnnnnn.POOLxx .Tier.n.m.MigratedPageCt

¢ LOCAL.SNnnnnn.POOLxx .Auto

¢ LOCAL.SNnnnnn.POOLxx .RelocateStartTime

¢ LOCAL.SNnnnnn.POOLxx .RelocateEndTime

¢ LOCAL.SNnnnnn.POOLxx .Relocating

¢ LOCAL.SNnnnnn.POOLxx .RelocatePerCent

¢ LOCAL.SNnnnnn.POOLxx .ExpectedMigrationPageCt

¢ LOCAL.SNnnnnn.POOLxx .MigratedPageCt• All variables in the device information structure

Related topics



• Device information structure on page 8-10


KTQRYRLC

Function

Acquires the following information about the Dynamic Tiering for Mainframepool from the storage system, and then stores the information in the REXXvariable structure.

CLI commands 6-19




• Progress of page relocation (moving pages between tiers) for theDynamic Tiering for Mainframe pool to which the volumes in the tieringpolicy group belong

• Configuration of the Dynamic Tiering for Mainframe pool to which thevolumes in the tiering policy group belong

Command type


FormatKTQRYRLC

1STEM(stem-name-1)

1MSG(stem-name-2)

Parameters


Specify the prefix of the tiering policy group structure to which the targettiering policy group information was loaded. This is the character stringspecified for the STEM parameter of the KTLOAD command that was

previously executed. This value must end with a period.



Return codes

The following table lists and describes the codes returned when the KTQRYRLC


Table 6-11 Return codes generated by the KTQRYRLC command

Return code Meaning




36 The command ended due to an invalid REXX variable

structure.





6-20 CLI commands




Return code Meaning







REXX variables that are updated by the KTQRYRLC command


• In the host-discovered array structure, the following variables related tothe Dynamic Tiering for Mainframe pool to which the volumes in thespecified tiering policy group belong


parameter.

¢ All variables beginning with LOCAL.SNnnnnn.POOLxx

Related topics




KTQRYTPG

Function

Acquires the following information about the volumes that belong to a tieringpolicy group from the storage system, and then stores the information in theREXX variable structure.

• Tiering policy configuration information

• Page tier location status

Command type


FormatKTQRYTPG

1STEM(stem-name-1)

1MSG(stem-name-2)

CLI commands 6-21




Parameters


Specify the prefix of the tiering policy group structure to which the targettiering policy group information was loaded. This is the character stringspecified for the STEM parameter of the KTLOAD command that was

previously executed.



Return codes

The following table lists and describes the codes returned when the KTQRYTPG


Table 6-12 Return codes generated by the KTQRYTPG command

Return code Meaning











value of the STEM parameter or the KTLOAD command.




REXX variables that are updated by the KTQRYTPG command




parameter.

6-22 CLI commands




¢ LOCAL.SNnnnnn.CUxx .CCAxx .TierLevel



¢ LOCAL.SNnnnnn.CUxx .CCAxx .Used

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.0

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.n.Used

Related topics



• KTDEMO11 (Check the tiering policy) on page C-16

• KTDEMO12 (Check the page relocation status) on page C-18


KTQSTATS

Function

Acquires I/O performance information for a tiering policy group from thestorage system, and then stores the information in the REXX variablestructure. The I/O performance information to be acquired is the number of I/O operations at the back end (number of I/O operations for the drivemedia).

Command type


FormatKTQSTATS

1STEM(stem-name-1)

1MSG(stem-name-2)

Parameters


Specify the prefix of the tiering policy group structure to which the targettiering policy group information was loaded. This is the character string

specified for the STEM parameter of the KTLOAD command that waspreviously executed.



CLI commands 6-23




Return codes

The following table lists and describes the codes returned when the KTQSTATS


Table 6-13 Return codes generated by the KTQSTATS command

Return code Meaning















REXX variables that are updated by the KTQSTATS command




parameter.

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.n.0

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.n.IO.Ct

¢ LOCAL.SNnnnnn.CUxx .CCAxx .Tier.n.IO.diff

• The following variable in the tiering policy group structure


parameter.

¢ TPG.VOL.IO.Interval

Related topics


6-24 CLI commands






• KTDEMO14 (Check I/O performance information) on page C-26

KTSCAN

FunctionAcquires the following information by scanning volumes, and then stores theinformation in the REXX variable structure.

• Detected volume information

• Information about the Dynamic Tiering for Mainframe pool to which thevolumes belong

• Information about the storage system

The range of volumes to be scanned is specified by using one of thefollowing:

• Range specification by using the device numbers• Range specification by using the volume serial numbers

• Specification of an SMS storage group name

Command type


Prerequisites

• To scan the volumes specified by an SMS storage group name or byvolume serial numbers, you must first place the volumes online (onlyonline volumes can be detected).

FormatKTSCAN

1STEM(stem-name-1)

1MSG(stem-name-2)

1{FROM(nnnn) 1TO(nnnn)

|FROMVSN(volser ) 1TOVSN(volser )

|STORGRP(SMS-storage-group-name)}

[1ARRAYS(stem-name-3)]

Parameters


Specify the prefix (any value) of the host-discovered array structure thatstores the scan results. This value must end with a period.

CLI commands 6-25






FROM(nnnn)~<four hexadecimal characters string>

To filter the range of volume detection by device numbers, specify thedevice number of the start volume.

TO(nnnn)~<four hexadecimal characters string>

To filter the range of volume detection by device numbers, specify thedevice number of the end volume.

FROMVSN(volser )~<six or fewer alphanumeric characters>

To filter the range of volume detection by volume serial numbers, specifythe volume serial number of the start volume.

TOVSN(volser )~<six or fewer alphanumeric characters>

To filter the range of volume detection by volume serial numbers, specifythe volume serial number of the end volume.

Information in the range specified by the FROMVSN parameter and TOVSN

parameter is compared in ascending EBCDIC code order.

STORGRP(SMS-storage-group-name)~<symbol name consisting of 8 or fewer

characters>

To restrict the range of volume detection to one SMS storage group,specify the SMS storage group name.

All volumes belonging to the SMS storage group specified by thisparameter will be scanned.

ARRAYS(stem-name-3)~<REXX prefix consisting of 64 or fewer characters>

<<HCC.KTSCAN.>>

Specify the prefix (any value) of the host-discovered array index structurethat stores the scan results. This value must end with a period. Do notspecify "HCC.HDAKT.".

Notes

If you change any function or information for the storage system, such as amicrocode number, execute the KTSCAN command and the KTSTORE command

to acquire the storage system information again and update the definition. Inthis case, you only have to scan one volume to acquire the storage systeminformation.

Reference note

• If you want to define offline volumes in a tiering policy group, specify thedevice numbers for those volumes when executing the KTSCAN and

KTIMPORT commands.

6-26 CLI commands




• If information about the volumes in the detection range already exists inthe host-discovered array structure specified for the STEM parameter, the

existing information is overwritten by the detected information.

Return codes

The following table lists and describes the codes returned when the KTSCAN

command terminates. If the commands do not terminate normally, refer to

the resulting error messages for details.

Table 6-14 Return codes generated by the KTSCAN command

Return code Meaning

0 The command ended normally. The REXX variables for thedetected volumes were created.

4 The volumes for which I/O paths could not be used or thevolumes of unknown storage systems were skipped. The REXXvariables for the successfully detected volumes were created.

8 No volumes were found in the volume detection range

specified by the parameters.12 An I/O error occurred. Some REXX variables could not be

created.

36 An attempt to read SMS storage group information failed.





52 The command ended due to an incorrect execution method.

The possible causes are as follows:



REXX variables that are updated by the KTSCAN command



The prefix of the structure name is the value specified for the ARRAYS

parameter.

• The following variables in the host-discovered array structureA REXX variable name is preceded by the value specified for the STEM

parameter.




CLI commands 6-27









¢ LOCAL.SNnnnnn.CUxx .CCAxx .STORGRP (set only when the STORGRP

parameter is specified)¢ LOCAL.SNnnnnn.CUxx .CCAxx .SSID








¢

LOCAL.SNnnnnn.POOLxx .Tier.n.Media

Related topics





KTSTORE

Function

Saves the values of either of the following REXX variable structures in aconfiguration file.

• Saves the values of the host-discovered array structure generated by theKTSCAN or KTLOAD command in the disk configuration definition file for

each storage system.

• Saves the values of the tiering policy group structure generated by theKTLOAD command in the tiering policy group definition file.

Command typeREXX external routine

FormatKTSTORE

1STEM(stem-name-1)

6-28 CLI commands




1MSG(stem-name-2)

1PREFIX( prefix )

[ 1ARRAYS(stem-name-3)]

[ 1{DSK|TPG}]

[ 1VOLUME(volser )]

[ 1SPACE(quantity ,increment)]

Parameters


Specify the prefix of the target REXX variable structure. If the host-discovered array structure has been created by executing the KTSCAN

command, specify the character string specified for the STEM parameter of

the KTSCAN command. If the REXX variable structure has been created by

executing the KTLOAD command, specify the character string specified for

the STEM parameter of the KTLOAD command. This value must end with a

period.




Specify the prefix of the name of the configuration file that savesinformation.

Caution: If you want to install and use Tiered Storage Manager forMainframe in the same system as Business Continuity Manager, you mustmake sure that the prefix character strings for Business ContinuityManager and Tiered Storage Manager for Mainframe are different. If the

same prefix is used for both Business Continuity Manager and TieredStorage Manager for Mainframe, the product may operate abnormally.

ARRAYS(stem-name-3)~<REXX prefix consisting of 64 or fewer characters>

<<HCC.KTSCAN.>>

Specify the prefix of the host-discovered array index structure that storesthe scan results. Specify the character string that was specified for theARRAYS parameter of the KTSCAN command only if in the disk

configuration file, you save the values of the host-discovered arraystructure acquired by using the KTSCAN command with the ARRAYS

parameter specified. This value must end with a period.

{DSK|TPG}~<<DSK>>Specify the configuration file to save the values of the REXX variables in.

¢ DSK

The values of the host-discovered array structure are saved in thedisk configuration definition file.

¢ TPG

CLI commands 6-29




The values of the tiering policy group structure are saved in thetiering policy group definition file.

VOLUME(volser )~<character string with 6 or fewer alphanumeric

characters>

To allocate the configuration file to a specific volume, specify the serialnumber of the volume to be allocated to. This parameter is enabled whenthe configuration file is not managed by SMS.

SPACE(quantity ,increment) ~<number>((from 1 to 16777215))

On a block basis, specify the primary quantity and secondary quantitywhen allocating the configuration file. One block is 4,096 bytes. Specifythis parameter when you want to limit the primary quantity and add theinsufficient portion to the secondary quantity. If you do not specify thisparameter, the capacity of the configuration file is automaticallycalculated and allocated as the primary quantity.

Tip: If the configuration file already exists when you execute the KTSTORE

command, the existing configuration file information and the informationstored in the REXX variable structure are merged. The merged information is

then saved to a newly allocated dataset. Therefore, the VOLUME parameterand the SPACE parameter are enabled when the configuration file is updated.

Tip: When you execute the KTSTORE command, a number of datasets, equal

to the number of disk configuration definition files to be updated# + 1, areallocated at the same time. Therefore, ensure that the number of datasetsthat are allocated at the same time does not exceed the value of theDYNAMNBR parameter of the TSO/E logon procedure or JCL.

#: The number of disk configuration definition files to be updated is thenumber of storage systems that contain information in their host-discoveredarray structure.

Return codes

The following table lists and describes the codes returned when the KTSTORE


Table 6-15 Return codes generated by the KTSTORE command

Return code Meaning


36 The command ended due to an invalid REXX variable

structure.

40 An error occurred while a configuration file was being createdor updated.



6-30 CLI commands




Return code Meaning





20000 to 20099 An error occurred, possibly due to insufficient memory (thelast two digits are the REXX error number). For details aboutthe error, see the explanation of the IRX00nnI message

(replace nn with the last two digits of the return code) in themanual TSO/E Messages.

REXX variables that are updated by the KTSTORE command

All variables in the message structure

REXX variables saved in the configuration file by the KTSTORE

command• If the disk configuration definition file is specified for saving the REXX

variables, the following REXX variables in the host-discovered arraystructure are saved in the disk configuration definition file.


parameter.


¢ LOCAL.SNnnnnn.Model







¢ LOCAL.SNnnnnn.CUxx .CCAxx .STORGRP









CLI commands 6-31




• If the tiering policy group definition file is specified for saving the REXXvariables, the following REXX variables in the tiering policy groupstructure are saved in the tiering policy group definition file.


parameter.

¢ TPG.ID

¢ TPG.VOL.n.SerialNum

¢ TPG.VOL.n.CUNum

¢ TPG.VOL.n.CCA

¢ TPG.VOL.n.POOLID

¢ TPG.VOL.n.SSID

¢ TPG.VOL.n.TierLevel

¢ TPG.VOL.n.Entry

¢ TPG.VOL.n.TierRelocation

Related topics





KTWTOMSG

Function

Outputs the specified message ID and message text to the console.

Command type


Format

To output a single-line message:

KTWTOMSG 1type,text

To output a multi-line message:

KTWTOMSG1type,text-1,text-2[,text-3][,text-4][,text-5]

[,text-6 ][,text-7 ][,text-8][,text-9][,text-10]

Parameters

type

6-32 CLI commands




Specify one of the values shown below as the type of the message to beoutput. The message will be output with the routing code appropriate forthe specified type.

¢ I

Specify this for a message that reports information. The message willbe output with routing code 11.

¢ W

Specify this for a warning message. The message will be output withrouting code 6.

¢ E

Specify this for an error message. The message will be output withrouting code 6.

text ~<125 or fewer characters>

Specify this parameter to output a single-line message. Specify themessage ID and message text to be output.

text-1~<34 or fewer characters>

Specify this parameter to output a multi-line message. Specify themessage ID and the first line of the message text to be output.

text-2~<70 or fewer characters>

Specify this parameter to output a multi-line message. Specify the secondline of the message text to be output.

text-3 to text-10~<70 or fewer characters>

Specify this parameter to output a message consisting of three or morelines. The specification method is the same as for the text-2 parameter.

Note

A maximum of ten lines can be output in a multi-line message text.

Return codes

The following table lists and describes the codes returned when the KTWTOMSG

command terminates.

Table 6-16 Return codes generated by the KTWTOMSG command

Return code Meaning


1004 The type is not specified.

1008 The specified type is invalid.

1012 No text is specified.

1016 The specified text is invalid.

2000 A system error occurred.

CLI commands 6-33




Return code Meaning

Other than theabove

See the return codes of the WTO macro. For details, see the MVS

Programming: Assembler Services Guide.

TSO/E command details

This section describes details about the TSO/E type CLI commands. Thecommands are explained in alphabetic order.

KTCONMSG

Function

Monitors the messages output to the console.

Command type

TSO/E command

FormatKTCONMSG

1{OP(OPEN)[ 1MSGID(message-ID )] [ 1TIMEOUT(timeout-value)]

|OP(GET) 1HANDLE(X'handle-value')

|OP(CLOSE) 1HANDLE(X'handle-value')

}

Parameters

OP({OPEN|GET|CLOSE})

Specify the processing type.

¢ OPEN

Establish an EMCS console interface for monitoring messages. Whenthe command with the OPEN parameter specified ends normally, the

YKA098I message containing the handle value to be specified for the

OP(GET) and OP(CLOSE) parameters is returned.

¢ GET

Messages acquired after the EMCS console interface was establishedare returned in order in which they arrived.

If no messages have been acquired, either of the following operationsis performed.

If a value other than 0 is specified for the TIMEOUT parameter: If no

messages arrived when the number of seconds specified for theTIMEOUT parameter has elapsed, the YKA096I message is output and

the command ends with return code 2.

6-34 CLI commands




If 0 is specified for the TIMEOUT parameter: The YKA096I message is

output and the command ends with return code 2.

¢ CLOSE

Close the EMCS console interface for monitoring messages.

MSGID(message-ID ) ~<6-10 alphanumeric characters> <<IEA494>>

Specify the message ID of the message to be monitored.

TIMEOUT(timeout-value)~<number>((0-60))<<15>>

Specify the timeout value in seconds.

HANDLE(X'handle-value')~<eight hexadecimal characters string>

Specify the handle value to be associated with the EMCS console interfacethat has already been established. Specify the value in the YKA098I

message that was returned when the KTCONMSG OP(OPEN) command

ended.

Return codes

The following table lists and describes the codes returned when the KTCONMSGcommand terminates.

Table 6-17 Return codes generated by the KTCONMSG command

Return code Meaning

-3 The module cannot be loaded. The possible causes are as follows:

• The necessary library datasets are not concatenated.

• The load library for LINKLIB has not been registered for APFauthentication.

• The module is protected by the RACF program control function.

-1 An interrupt occurred during command execution.

0 Open processing ended normally.

1 The message specified by the MSGID parameter was returned.

2 The number of seconds specified for the TIMEOUT parameter has

elapsed, but no messages arrived.

4 An attempt to acquire a message failed. A possible cause is that themessage was deleted because a long time has passed since theEMCS console interface was established.

6 Close processing ended normally.

8 An invalid parameter was specified.

9 A system error occurred.

CLI commands 6-35




KTENV

Function

Outputs the program product name and the operating environment settingsfor Tiered Storage Manager for Mainframe to the TSO/E terminal.

Command type

TSO/E command

FormatKTENV

Return codes

The following table lists and describes the codes returned when the KTENV

command terminates.

Table 6-18 Return codes generated by the KTENV command

Return code Meaning

-3 The module cannot be loaded. The possible causes are asfollows:


• The module is protected by the RACF program controlfunction.

-1 An interrupt occurred during command execution.


Output items

The following table lists and describes the items output when the KTENV

command is executed, in order in which they are output.

Table 6-19 Output items of the KTENV command

Output item Description

Hitachi Tiered Storage

Manager for MainframeProgram product name

Environment variables

(v.r.m-nn(zz))

v.r.m-nn( zz ): Version number and build number

License info DSN prefix Prefix of the license information dataset

Event log output method • LOGR: Event logs are output by using the system

logger service.

• SAM: Event logs are output without using the

system logger service.

6-36 CLI commands





CLI log output settings • YES: CLI command-execution logs are output to

SYSLOG.

• CONSOLE: CLI command-execution logs are output

to the console.

• NO: CLI command-execution logs are not output.

YKLCNSE Value of the YKLCNSE environment variable specifiedby the KTSETENV command#

&YKLCNSE Value of the &YKLCNSE system symbol#

YKLCNS2 Value of the YKLCNS2 environment variable specified

by the KTSETENV#

&YKLCNS2 Value of the system symbol &YKLCNS2#

LOGPUT Value of the LOGPUT environment variable specified by

the KTSETENV command#

&YKLOGPT Value of the &YKLOGPT system symbol#

SYSLOG Value of the SYSLOG environment variable specified by

the KTSETENV command#

&YKSYSLG Value of the &YKSYSLG system symbol#

#

If the value has not been specified, N/A is output.

Example

The following shows an example of executing the KTENV command.

READYKTENV Hitachi Tiered Storage Manager for MainframeEnvironment variables (v .r .m-nn(zz))License info DSN prefix: HITACHIEvent log output method: LOGRCLI log output settings: NOYKLCNSE = N/A (&YKLCNSE = "HITACHI" )YKLCNS2 = N/A (&YKLCNS2 = N/A )LOGPUT = LOGR (&YKLOGPT = N/A )SYSLOG = N/A (&YKSYSLG = N/A )YKZ371I KTENV command return code=0.

KTERCODE

Function

Outputs the information for the specified error code and the cause of theerror to the TSO/E terminal.

CLI commands 6-37




Command type

TSO/E command

FormatKTERCODE

1error-code

Parameters

error-code ~<four hexadecimal characters string>

Specify the sense byte information (error code) for the storage systemcontained in messages output by Tiered Storage Manager for Mainframe.For details about error codes, see the description of storage system sensebyte information in the Hitachi Tiered Storage Manager for MainframeMessages.

Return codes

The following table lists and describes the codes returned when the KTERCODE

command terminates.

Table 6-20 Return codes generated by the KTERCODE command

Return code Meaning


8 The description of the specified error code was not found.

16 The command ended due to an invalid parameter.

64 The module cannot be loaded. The possible causes are asfollows:


• The module is protected by the RACF program controlfunction.

Example

The following shows an example of executing the KTERCODE command.

READYKTERCODE 6A13 Error details: The command could not be executed because a remote command was executed

while the command device was not defined.

Type of error: Others.

6-38 CLI commands




KTINSCHK

Function

Checks the setting items required for setup for incomplete or incorrectinformation, and then outputs a message showing the check results and thesettings.

Command type

TSO/E command

FormatKTINSCHK

Return codes

The following table lists and describes the codes returned when the KTINSCHK

command terminates.

Table 6-21 Return codes generated by the KTINSCHK command

Return code Meaning

0 There were no problems with the settings.

8 There were problems with the settings.

32 A processing error occurred during command execution.

Output items

The following table lists and describes the items output when the KTINSCHK

command is executed, in the order in which they are output.

Table 6-22 Output items of the KTINSCHK command


Security Settings • OK: View permission required for using CLI

commands is assigned to the reference profile orthe operation profile.

• FAULTY: View permission required for using CLI

commands is assigned to neither the referenceprofile nor the operation profile.

User SVC Routine • OK: There are no problems with registration of theuser SVC.

• FAULTY: There are problems with registration of

the user SVC.

Facility Class ProfilesQuery

Name of the currently defined reference profile#1

CLI commands 6-39





Facility Class ProfilesCommands

Name of the currently defined operation profile#1

Directions Description about permissions required for using theoperation and reference CLI commands

Version of User SVC forthis program

Prerequisite user SVC version for the running TieredStorage Manager for Mainframe program.

Current User

SVC

SVC Number User SVC number that is currently enabled in the

system#2

Version Version of the user SVC that is currently enabled in

the system#2

Dynamic

registeredUser SVC

SVC Number User SVC number that was dynamically registered by

using the KTALCSVC command#2

Version Version of the user SVC that was dynamically

registered by using the KTALCSVC command#2

Static

installedUser SVC

SVC Number User SVC number that was statically registered by

defining the IEASYM xx parmlib member#2

Version Version of the user SVC that was statically registered

by defining the IEASVC xx parmlib member.#2

Directions Description about the relationship between a user SVCthat was dynamically or statically registered and theuser SVC enabled in the system.

#1

If the value has not been specified, N/A is output.

#2

If the information cannot be acquired, N/A is output.

Example

The following shows an example of executing the KTINSCHK command.

READYKTINSCHK

Security Settings .........: OK User SVC Routine ..........: OK

Facility Class Profiles Query : STGADMIN.YKA.DKT.KTQUERY Facility Class Profiles Commands : STGADMIN.YKA.DKT.COMMANDS

Directions The current setup is listed above. An unregistered profile is listed as N/A. The RACF settings are necessary in order to use CLI commands. After a profile is defined in the RACF FACILITY class, a user can use CLI commands by being given the access rights of the profile. There are the following two kinds of profiles: - Facility Class Profiles Query

6-40 CLI commands




- Facility Class Profiles Commands To give a user the permissions necessary to use all of the CLI commands: 1. Make the RACF FACILITY class active. 2. Define the STGADMIN.YKA.DKT.COMMANDS profile in the FACILITY class. 3. Give the user the access rights of the profile. To give a user the permissions necessary to use some of the CLI commands

(the reference commands): 4. Make the RACF FACILITY class active. 5. Define the STGADMIN.YKA.DKT.KTQUERY profile in the FACILITY class. 6. Give the user the access rights of the profile.

Version of User SVC for this program .............: v .r .m-nn(zz) or later Current User SVC : SVC Number 200 Version v .r .m-nn(zz) Dynamic registered User SVC : SVC Number 200 Version v .r .m-nn(zz) Static installed User SVC : SVC Number 251 Version v .r .m-nn(zz)

Directions The current users SVC routine registration number and version are listed above. User SVC numbers and versions that have not been acquired are listed as N/A. If a Dynamic registered User SVC exists, the Dynamic registered User SVC will become the Current User SVC. If a Dynamic registered User SVC does not exist and a Static installed User SVC exists, the Static installed User SVC will become the Current User SVC. If the Current User SVC is smaller than the Version of User SVC for this

program, then the program will not run properly.

If this is the case, use the KTALCSVC command to dynamically register the latest User SVC. Also, register the latest User SVC if a Dynamic registered User SVC is deleted. The following is an example of deleting a registered User SVC: +--------------------------------------------------------------------+ : START KTALCSVC,PARM=DELETE : +--------------------------------------------------------------------+ The following is an example of registering a User SVC: +--------------------------------------------------------------------+ : START KTALCSVC : +--------------------------------------------------------------------+

Note:

A User SVC registered by using the KTALCSVC command will become invalid during a re-IPL. As a result, we recommend performing either of the following settings in order to prepare for the next re-IPL: - Add the KTALCSVC command to the COMMNDxx parmlib member, and then have the User SVC automatically re-registered during a re-IPL. - Define a User SVC in the IEASVCxx parmlib member, and then use the User SVC that was statically installed from the next IPL.

YKK001I KTINSCHK completed. RC=00,V/R=v .r .m-nn(zz),2013/04/15 09:56:30

KTSLEEP

Function

Suspends the execution of the script for the specified period of time.

Command type

TSO/E command

CLI commands 6-41




FormatKTSLEEP

1{SEC(timeout-value)|MIN(timeout-value)}

Parameters

SEC(timeout-value)~<number>((1-9999))

Specify the period of time in seconds during which the script issuspended.

MIN(timeout-value)~<number>((1-9999))

Specify the period of time in minutes during which the script issuspended.

Note

Depending on the priority and operating status of other tasks, the scriptsuspended by the KTSLEEP command might not operate immediately after the

specified time has elapsed.

Return codes

The following table lists and describes the codes returned when the KTSLEEP

command terminates.

Table 6-23 Return codes generated by the KTSLEEP command

Return code Meaning


8 Suspension status was canceled due to an interrupt.

16 The command ended due to an invalid parameter.

OS console command details

This section describes details about the OS console command type CLIcommands. The commands are explained in alphabetic order.

KTALCSVC

Function

Use this command to register or delete a user SVC.

Command type

OS console command

6-42 CLI commands




Format

START 1KTALCSVC[,PARM='{SVC-number |DELETE}']

Parameters

If you omitted the PARM part of the command, an unused SVC number

between 200 and 255 is assigned.

SVC-number to <number> ~ ((from 200 to 255))Specify a SVC number to be assigned for the user SVC.

DELETE

Specify this parameter to delete a user SVC.

Notes

If you used the KTALCSVC command to delete a user SVC while Tiered

Storage Manager for Mainframe was running, CLI commands that are beingexecuted might terminate abnormally.

Return codes

The following table shows the return codes when the execution of theKTALCSVC command ends.

Table 6-24 Return codes generated by the KTALCSVC command

Return code Meaning

0 Successfully completed.

4 The user SVC is already registered.

16 Registration or deletion of the user SVC failed.

20 Processing stopped due to an error (the specified value orexecution environment is invalid).

KTDSPENV

Function

Displays the program product name and the Tiered Storage Manager forMainframe operating environment setting values in the console.

Command type

OS console command

Format

START 1KTDSPENV

[,PARM='[{SUMMARY|DETAIL}]']

CLI commands 6-43




Parameters

SUMMARY is assumed if the PARM part of the command was omitted or specified

as PARM=''.

SUMMARY

Displays the program product name, the prefix of the license informationdataset, the information about whether to use the system logger service,and the information about whether to output CLI command-executionlogs to SYSLOG or the console.

DETAIL

Displays the content displayed when the SUMMARY parameter is specified,

and also displays the environment variables that are set dynamically byusing the KTSETENV command and the system symbol values that are set

statically.

Return codes

The following table shows return codes when the execution of the KTDSPENV

command ends.

Table 6-25 Return codes generated by the KTDSPENV command

Return code Meaning


4 There is an error in the specified value. The command wasexecuted assuming that SUMMARY is specified.

Execution examples

Execution example without the DETAIL parameter

START KTDSPENVKTA403I Hitachi Tiered Storage Manager for MainframeKTA400I Environment variables (v .r .m-nn(zz))KTA401I License info DSN prefix: HitachiKTA401I Event log output method: LOGRKTA401I CLI log output settings: YES

Execution example with the DETAIL parameter

START KTDSPENV,PARM='DETAIL'KTA403I Hitachi Tiered Storage Manager for MainframeKTA400I Environment variables (v .r .m-nn(zz))KTA401I License info DSN prefix: HTC1.HTC2

KTA401I Event log output method: SAMKTA401I CLI log output settings: NOKTA402I YKLCNSE = HTC1 (&YKLCNSE = N/A )KTA402I YKLCNS2 = HTC2 (&YKLCNS2 = N/A )KTA402I LOGPUT = SAM (&YKLOGPT = "LOGR" )KTA402I SYSLOG = NO (&YKSYSLG = "YES" )

6-44 CLI commands




KTSETENV

Function

Use this command to set the following values using environment variables.

• Prefixes of the license information dataset



Command type

OS console command

Format

START 1KTSETENV,

PARM='{YKLCNSE=[ prefix-1]|YKLCNS2=[ prefix-2]|

LOGPUT=[{LOGR|SAM}]|SYSLOG=[{YES|NO|CONSOLE}]}[,...]'

Parameters

Multiple parameters can be specified for the maximum length that can bespecified in the PARM parameter of the START command. If the same

parameter is specified more than once, the instance specified last takeseffect.

YKLCNSE=[ prefix-1] ~ <8 or fewer alphanumeric characters>

Specify prefix-1 for the license information dataset so that the name of the dataset is unique. To remove the value of the environment variableYKLCNSE, specify PARM='YKLCNSE='.

YKLCNS2=[ prefix-2]: ~ <8 for few alphanumeric characters>

Specify prefix-2 for the license information dataset so that the name of the dataset is unique. To remove the value of the environment variableYKLCNS2, specify PARM='YKLCNS2='.

LOGPUT=[LOGR|SAM]

Specify whether the system logger service is to be used when outputtingevent logs.

¢ LOGR

Event logs are output using the system logger service.¢ SAM

Event logs are output to a sequential dataset without using thesystem logger service.

To remove the value of the environment variable LOGPUT, specify

PARM='LOGPUT='.

CLI commands 6-45




SYSLOG=[YES|NO|CONSOLE]

Specify whether CLI command-execution logs are output to SYSLOG orthe console.

¢ YES

CLI command-execution logs are output to SYSLOG.

¢ CONSOLE

CLI command-execution logs are output to the console.¢ NO

CLI command-execution logs are not output.

To remove the value of the environment variable SYSLOG, specify

PARM='SYSLOG='.

Return codes

The following table shows the return codes when execution of the KTSETENV

command ends.

Table 6-26 Return codes generated by the KTSETENV command

Return code Meaning


4 The specified value is invalid. Another value was used forexecution.

8 The specified value is invalid. Processing was canceled.

12 Processing was canceled due to a system error (such as aGETMAIN error).

16 An internal error occurred.

6-46 CLI commands




7

Files used by Tiered Storage Managerfor Mainframe

This chapter describes the files used by Tiered Storage Manager forMainframe.

□ File naming conventions used by Tiered Storage Manager for Mainframe

□ Format of datasets used by Tiered Storage Manager for Mainframe

□ Disk space requirements of configuration files

□ Format of tiering policy information CSV files

Files used by Tiered Storage Manager for Mainframe 7-1




File naming conventions used by Tiered Storage Manager forMainframe

The following table describes the file naming conventions for files used byTiered Storage Manager for Mainframe.

Table 7-1 File naming conventions used by Tiered Storage Manager forMainframe

File type File name

Tiering policy information CSV file prefix .POLICY. policy-ID

Disk configuration definition file prefix .DSK.SNnnnnn.LOCAL

Tiering policy group definition file prefix .TPG.tiering-policy-group-ID

• prefix is the character string to be specified in Configuration file prefixon the Edit Defaults panel, or the character string to be specified in thePREFIX parameter of CLI commands. Make sure that you specify the

same character string for all three types of files used by Tiered Storage

Manager for Mainframe.

Caution: If you want to install and use Tiered Storage Manager forMainframe in the same system as Business Continuity Manager, you mustmake sure that the prefix character strings for Business ContinuityManager and Tiered Storage Manager for Mainframe are different. If thesame prefix is used for both Business Continuity Manager and TieredStorage Manager for Mainframe, the product may operate abnormally.

• policy-ID is the identifier of a tiering policy information CSV file. This isthe value to be specified in the POLICY parameter of the KTIMPORT

command.

• nnnnn is the serial number of the storage system.

• tiering-policy-group-ID is the identifier of a tiering policy group. This isspecified in a tiering policy CSV file as the name of a tiering policy group.

Caution: Use the disk configuration definition file and tiering policy groupdefinition file as a reference only. They might not function properly if youchange the file contents.

The following table shows the maximum length and the permitted charactersfor items in the filenames used by Tiered Storage Manager for Mainframe.

Table 7-2 Maximum length and permitted characters for items infilenames used by Tiered Storage Manager for Mainframe

ItemMaximum

lengthPermitted characters

Prefix 25 A string consisting of one or more parts, joined byperiods. Each part can contain from one to eightcharacters, and consist of uppercase alphabetic andnumeric characters. Note that the first character of

7-2 Files used by Tiered Storage Manager for Mainframe




ItemMaximum

lengthPermitted characters

each part must be an uppercase alphabeticcharacter.

Policy ID 8 One to eight uppercase alphabetic character ornumbers. This must start with an uppercasealphabetic character.

Tiering policygroup ID

44 - (5 + prefix )

A string consisting of one or more parts, joined byperiods. Each part can contain from one to eightcharacters, and consist of uppercase alphabetic andnumeric characters. Note that the first character of each part must be an uppercase alphabeticcharacter.

Format of datasets used by Tiered Storage Manager forMainframe

The following table explains the format of datasets used by Tiered StorageManager for Mainframe.

Table 7-3 Format of datasets used by Tiered Storage Manager forMainframe

File name DSORG RECFM LRECL BLKSIZE

Tiering policy information CSV file PS VB 128 or more Any

Disk configuration definition file PS VB 256 4,096

Tiering policy group definition file PS VB 256 4,096

Disk space requirements of configuration files

The following table explains how to calculate the disk space required forconfiguration files.

Table 7-4 Disk space requirements of configuration files

Configuration file Size (unit: bytes)

Disk configuration definition file 700+ A 400+B 230

Tiering policy group definition file 200+C 100+D 100

Legend:

A: Number of volumes specified in the disk configuration definition file

B: Number of pools specified in the disk configuration definition file

C: Number of volumes specified in the tiering policy group definition file

D: Number of records specified in the tiering policy group definition file





Format of tiering policy information CSV files

This section describes the format of tiering policy CSV files.

Descriptive conventions of tiering policy information CSV files

This subsection describes the descriptive conventions for tiering policyinformation CSV files.

• A record (row) with a hash mark (#) in the first column, as shown below,

is a comment.

# character-string

• Any double quotation marks (") specified for a parameter are ignored.

• If values after a parameter are omitted, commas (,) that are used as

separators of the values can also be omitted. In the following example,the specification of the new-page assignment tier of the SGI storagegroup and whether to execute tier relocation are omitted includingcommas (,).

#TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc

STORGRP,SG1 ,TPG1 ,2

Syntax of tiering policy information CSV files

This subsection describes the syntax of tiering policy information CSV files.

Syntaxrecord-type,device,tiering-policy-group-ID [,[tiering-policy-level][,[new-page-assignment-tier ][,[tier-relocation]]]]

Parameters

record-type, device

Specifies the volume or volumes for which a tiering policy is to be set.Use one of the following patterns:

¢ STORGRP,SMS-storage-group-name ~ <symbol name consisting of 8

or fewer characters>

Use this pattern when you specify the name of the SMS storage groupthat the target volumes belong to. The tiering policy is set for allvolumes that belong to the specified SMS storage group.

¢ DEVN,device-number ~ <4-digit hexadecimal number>

Use this pattern when you specify the device number of the target

volume.¢ VOLSER,volume-serial-number ~ <6 or fewer alphanumeric

characters>

Use this pattern when you specify the volume serial number of thetarget volume.

tiering-policy-group-ID ~ <prefix character string>





Specifies the name of the tiering policy group to be defined. An operationcan be performed in batch on all objects that belong to the tiering policygroup specified by this parameter.

prefix .TPG.tiering-policy-group-ID is used as the name of a tiering

policy group definition file. The maximum length of a tiering policy groupID that can be specified is 44 - (5 + length-of-character-string-specified-for-prefix ).

tiering-policy-level ~ <numeric characters> ((0|1|2|3|4|5)) <<0>>

Specifies a numeric characters as the tiering policy level (that determinesthe tiers in which data is to be located) to be set for the specified volume.The following table describes the relationships between tiering policylevels and tiers in which data will be located.

The smaller the tier number, the higher the tier. For example, if an SSDdevice and an SAS device make up a tiered volume, the SSD device isTier 1, and the SAS device is Tier 2.

Table 7-5 Relationship between tiering policy levels and tiers in whichdata will be located

Tiering policylevel

Tier in which data will be located

3-tier configuration 2-tier configuration

0 All tiers (Tiers 1, 2, and 3) All tiers (Tiers 1 and 2)

1 Tier 1 Tier 1

2 Tiers 1 and 2 All tiers (Tiers 1 and 2)

3 Tier 2 All tiers (Tiers 1 and 2)

4 Tiers 2 and 3 All tiers (Tiers 1 and 2)

5 Tier 3 Tier 2

new-page-assignment-tier ~ <alphabetic characters> ((HIGH|MIDDLE|LOW))

<<MIDDLE>>

Specifies the order of tiers to which new pages will be assigned first if there are multiple tiers in the specified tiering policy level. The meaningsof the values that can be specified are as follows:

¢ HIGH: The new page is assigned from the higher tier of tiers set in the

tiering policy.

¢ MIDDLE: The new page is assigned from the middle tier of tiers set in

the tiering policy.

¢

LOW: The new page is assigned from the lower tier of tiers set in thetiering policy.

The following tables describe in detail the values set for the new-pageassignment tier in a 3-tier and a 2-tier configuration. how the order of tiers to which new pages will be assigned is determined by the tieringpolicy level and new-page assignment tier settings. In the table, 1>2indicates that pages will first be assigned to Tier 1 (higher tier), and if Tier 1 becomes full, pages will then be assigned to Tier 2 (lower tier). The





smaller the tier number, the higher the tier. For example, if an SSDdevice and an SAS device make up a tiered volume, the SSD device isTier 1, and the SAS device is Tier 2.

Table 7-6 New-page assignment description (3-tier configuration)

Tieringpolicy

level

Value of the new-page assignment tier setting

HIGH MIDDLE LOW Description

0 1>2>3 2>3>1 3>2>1 The order changes according to thevalue that is set. This is a case inwhich setting a value is effective.

1 1>2>3 1>2>3 1>2>3 Because only one tier applies to thislevel, the order does not changeaccording to the value that is set.

2 1>2>3 1>2>3 2>1>3 If LOW is set, Tier 2 is given higherpriority than Tier 1.

3 2>3>1 2>3>1 2>3>1 Because only one tier applies to thislevel, the order does not change

according to the value that is set.

4 2>3>1 2>3>1 3>2>1 If LOW is set, Tier 3 is given higherpriority than Tier 2.

5 3>2>1 3>2>1 3>2>1 Because only one tier applies to thislevel, the order does not changeaccording to the value that is set.

Table 7-7 New-page assignment description (2-tier configuration)

Tieringpolicy level

Value of the new-page assignment tier setting

HIGH MIDDLE LOW Description

0 1>2 1>2 2>1 If LOW is set, Tier 2 is given higherpriority than Tier 1.

1 1>2 1>2 1>2 Because only one tier applies to thislevel, the order does not changeaccording to the value that is set.

2 1>2 1>2 2>1 If LOW is set, Tier 2 is given higherpriority than Tier 1.

3 1>2 1>2 2>1

4 1>2 1>2 2>1

5 2>1 2>1 2>1 Because only one tier applies to thislevel, the order does not change

according to the value that is set.

tier-relocation ~ <alphabetic character> ((Y|N)) <<Y>>

Specifies whether to execute tier relocation for the volume or volumes.

¢ Y: Executes tier relocation.

¢ N: Does not execute tier relocation.





Record priority

The priority of records in one tiering policy group is as follows.

• If you specified the same SMS storage group name, device number, orvolume serial number for multiple records, the record specified last isvalid.

• If you specified the same volume with both the record for the devicenumber and the record for the volume serial number, the record specifiedlast is valid.

• If one record specifies a volume, and another record specifies an SMSstorage group that contains the same volume, the volume specification inthe former record takes priority.

Examples

• Example of defining multiple volumes for different tiering policies

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocDEVN ,1101 ,TPG1 ,1DEVN ,1102 ,TPG1 ,5

• Example of defining an SMS storage group and a volume belonging tothat SMS storage group

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2 ,HIGHDEVN ,1101 ,TPG1 ,1 ,LOW

The record that specifies a specific volume takes priority.

For example, if a volume with device number 1101 belongs to SMSstorage group SG1 in the above coding, the tiering policy of the volumewith device number 1101 is as follows: the tiering policy level is 1 (not 2),and the new-page assignment tier is LOW (not HIGH).

• Example of defining the same volume for multiple tiering policy groups

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,1STORGRP,SG1 ,TPG2 ,5

Both definitions are valid. By using the KTACTTPG command to switch the

definition applied to the storage system, you can switch the definitionbased on the time zone.

• Example of defining the same volume more than once for a single tieringpolicy group

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocDEVN ,1101 ,TPG1 ,1DEVN ,1101 ,TPG1 ,5

The last record is valid. For example, in the above coding, tiering policy

level 5 is assigned to the volume with device number 1101.





Configuration example of tiering policy groups and example of specifications in the corresponding tiering policy information CSV file

The following shows an example of configuring tiering policy groups and anexample of specifications in the corresponding tiering policy information CSVfile.

Figure 7-1 Configuration example of tiering policy groups

The following provides details about the tiering policy groups in the

configuration example.

Tiering policy group TPG1:





Target volumeTiering

policy level

New-pageassignment

tier

Whether toexecute tierrelocation

Volumes belonging to SMSstorage group SG1

2 HIGH Not specified

Volume of device number 1101 1 Not specified Not specified

Volume of device number 1202 2 HIGH Not specified

Tiering policy group TPG2:

Target volumeTiering

policy level

New-pageassignment

tier

Whether toexecute tierrelocation

Volumes belonging to SMSstorage groups SG2 and SG3

5 Not specified Not specified

Specify as follows to define the sample configuration shown above:

Specification in the tiering policy information CSV file

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2 ,HIGHDEVN ,1101 ,TPG1 ,1DEVN ,1202 ,TPG1 ,2 ,HIGHSTORGRP,SG2 ,TPG2 ,5STORGRP,SG3 ,TPG2 ,5

Values that must be specified for the prefix, policy ID, and tiering policygroup ID

¢ Prefix: PREFIX1

This value will be used as the file name prefix for configuration filesand tiering policy information CSV files.

¢ Policy ID: POLICY1

This value will be used as the file name suffix for tiering policyinformation CSV files.

¢ Tiering policy group IDs: TPG1 and TPG2

These values will be used as the file name suffixes for tiering policygroup definition files.

Examples of changing a tiering policy information CSV file

The following provides examples of changing a tiering policy information CSVfile.





When changing the tiering policy

Modify the tiering policy parameters in the record.

Before the change:

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2 ,HIGHDEVN ,1101 ,TPG1 ,1DEVN ,1202 ,TPG1 ,2 ,HIGH

After the change:

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2 ,HIGHDEVN ,1101 ,TPG1 ,1DEVN ,1202 ,TPG1 ,5 ,LOW

When changing the tiering policy back to the default

Keep the record, but delete the tiering policy parameters.

Before the change:

#TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc

STORGRP,SG1 ,TPG1 ,2 ,HIGHDEVN ,1202 ,TPG1 ,2 ,HIGH

After the change:

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1DEVN ,1202 ,TPG1 ,2 ,HIGH





The above example changes the tiering policy of volumes in the storagesystem in the SMS storage group SG1 back to the default.

Tip: After you change the tiering policy back to the default, the status of thevolume to delete is as follows:




Caution: If the record (not the tiering policy parameters) is deleted, thevolume is deleted from the tiering policy group while the tiering policyremains. Consequently, Tiered Storage Manager for Mainframe cannotmanipulate the volume.

When deleting tiering policies assigned individually to volumes inthe SMS storage group so that they match the settings on the SMSstorage group

This example deletes the record of the volume from the tiering policyinformation CSV file. After the record is deleted, the tiering policies assignedindividually are deleted. The tiering policies that are set to the SMS storagegroup where the volume belongs are applied.

Before the change:

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2 ,HIGHDEVN ,1101 ,TPG1 ,1DEVN ,1202 ,TPG1 ,2 ,HIGH

After the change:

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2 ,HIGHDEVN ,1202 ,TPG1 ,2 ,HIGH

In the above example, the tiering policy level of the volume of device number1101 in the SMS storage group SG1 is 2. The new-page assignment tier isHIGH.





When adding a volume to the SMS storage group

#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2 ,HIGH

Add a volume to the SMS storage group. You do not need to modify thetiering policy information CSV file.

When adding a volume that does not belong to the SMS storagegroup

Add the record of the volume to be added to the tiering policy information

CSV file.

Before the change:


After the change:






When deleting a volume that belongs to the SMS storage group


Remove the volume from the SMS storage group. You do not need to modifythe tiering policy information CSV file.

When deleting a volume that does not belong to the SMS storage

group

Delete the record of the volume from the tiering policy information CSV file.

Before the change:


After the change:






8

REXX variable structures

This chapter describes the REXX variable structures used by Tiered StorageManager for Mainframe.

□ List of REXX variable structures

□ Message structure

□ Host-discovered array index structure

□ Host-discovered array structure

□ Tiering policy group structure

□ Device information structure

REXX variable structures 8-1




List of REXX variable structures

REXX variable structures are variables expanded by executing a CLIcommand. REXX variable structures store the values loaded from TieredStorage Manager for Mainframe configuration files, information acquired fromthe storage system, and the results of CLI commands. These structures arealso used for passing information between CLI commands. Some values of REXX variable structures are saved in configuration files.

The following table lists the REXX variable structures.

Table 8-1 REXX variable structures

REXX variablestructure name

ContentsConfiguration file that

stores REXX variable values

Message structure Messages generated by CLIcommands

None (Information is not savedin a configuration file.)

Host-discoveredarray indexstructure

Information about theconfiguration of a storage systemand volumes in the storage system

None (Information is not savedin a configuration file.)

Host-discoveredarray structure

Values set for the storage systemand volumes in the storage system

Disk configuration definitionfile

Tiering policy groupstructure

Values related to tiering policiesthat are to be set in the storagesystem for the volumes belongingto a tiering policy group

Tiering policy group definitionfile

Device informationstructure

Address information for volumes None (Information is not savedin a configuration file.)

Message structure

Messages generated by CLI commands are stored in the message structure.

When the structure is created

When a CLI command is executed

Prefix of the structure name

The prefix of the message structure name is the value specified for the MSG

parameter of each command.

REXX variable names and contents

The following table lists and describes the REXX variables in the messagestructure. A REXX variable name is preceded by the prefix of the structurename.

8-2 REXX variable structures




Table 8-2 Message structure

REXX variable name Description

0 Number of messages output by one command (n)

n. Information for each message is stored in the lower-level REXX variables.

SeveritySeverity

TextMessage ID and message text

Value Additional information

Host-discovered array index structure

The host-discovered array index structure stores information values thatindicate the configuration of a storage system and volumes in the storagesystem.


The structure is created when one of the following occurs:

• The KTLOAD command is executed (the structure is created by loading

information from the disk configuration definition file).

• The KTGETHDA command is executed (the structure is created by loading


• The KTSCAN command is executed.

Prefix of the structure nameThe prefix of the host-discovered array index structure name is either of thefollowing:

• If the structure is created by the KTLOAD command or KTGETHDA

command: HCC.HDAKT.

• If the structure is created by the KTSCAN command: Value specified for

the ARRAYS parameter (if the ARRAYS parameter is omitted, HCC.KTSCAN.)


The following table lists and describes the REXX variables in the host-discovered array index structure. A REXX variable name is preceded by theprefix of the structure name.





Table 8-3 Host-discovered array index structure

REXX variablename

Description

0 Number of storage systems (n)

n. Information for each storage system is stored in lower-level REXX variables.

SerialNum Serial number of the scanned storage system

DADIDFixed character string LOCAL is stored.

PrefixPrefix of the host-discovered array structure from which the last period is removed

POOLMapMap information obtained from the pool IDs

1 is set for the position corresponding to the pool ID. The first value indicates pool ID

00. If this value is 1 1, the defined pool IDs will be 01 and 03.

CUMapMap information obtained from the control unit numbers

1 is set to the position corresponding to the control unit numbers. The first value

indicates control unit number 00. If this value is 11 1 1, the defined control unitnumbers will be 00, 01, 03, and 05.

CUxx . Information for each control unit is stored in lower-level REXX variables. xx indicatesa control unit number (hexadecimal).

No information for undefined control unit numbers is stored in REXX variables. Checkthe defined control unit numbers from the map information.

CCAMap Map information obtained from the command control address

1 is set to the position corresponding to the command control address numbers. The

first value indicates command control address number 00. If this value is 1 11, the

defined command control address numbers are 00, 03, and 04.

Note:

in the table indicates a space.

Host-discovered array structure

The host-discovered array structure stores the settings for a storage systemand volumes in the storage system.


The host-discovered array structure is created when one of the followingoccurs:

• The KTLOAD command is executed (the structure is created by loading


• The KTGETHDA command is executed (the structure is created by loading






• The KTQRYDEV command is executed.

• The KTSCAN command is executed.


The prefix of the host-discovered array structure name is the value specifiedfor the STEM parameter of each command.


The following table lists and describes the REXX variables in the host-discovered array structure. A REXX variable name is preceded by the prefix of the structure name.

Table 8-4 Host-discovered array structure


LOCAL.SNnnnnn. Information for each storage system is stored in lower-level REXX variables. nnnnn indicates the storagesystem serial number.

SerialNumStorage system serial number

ModelStorage system model (USP|USPV|VSP)

MicrocodeMicrocode number

IFTypeInterface version

PhysicalSerialNumPhysical DKC serial number

LDKCNum

Logical DKC number

CUxx .

(followed by lower-level REXX variables)

Information for each control unit is stored in lower-level REXX variables. xx indicates a control unitnumber (hexadecimal).

No information for undefined control unit numbers isstored in REXX variables. Check the defined controlunit numbers from the map information stored in thehost-discovered array index structure.

POOLxx .

(followed by lower-level REXX variables)

Information for each Dynamic Tiering for Mainframepool is stored in lower-level REXX variables. xx indicates a pool ID ( xx is hexadecimal). No informationis stored in REXX variables for undefined pool IDs.Check the defined pool IDs from the map informationstored in the host-discovered array index structure.

Lower-level REXX variables for LOCAL.SNnnnnn.CUxx .






LOCAL.SNnnnnn.CUxx . Upper-variable name

SSIDOne of the storage system IDs of the control unit

CCAxx . Information for each command control address is stored in lower-level REXX variables. xx indicates a command control addressnumber (hexadecimal). No information for undefined command

control address numbers is stored in REXX variables. Check thedefined command control address numbers from the mapinformation stored in the host-discovered array index structure.

DevnDevice number

VolserVolume serial number

STORGRPSMS storage group name

SSIDStorage system ID

POOLIDPool ID (decimal number)

CylsVolume capacity (number of cylinders)

ExternalExternal volume information

• Y: External volume

• N: Not an external volume

N is always specified for Dynamic Tiering for Mainframe volumes or

Dynamic Provisioning for Mainframe volumes.

TierLevelTiering policy level

Entry New-page assignment tier• HIGH: The new page is assigned from the higher tier of tiers

set in the tiering policy.

• MIDDLE: The new page is assigned from the middle tier of tiers


• LOW: The new page is assigned from the lower tier of tiers set

in the tiering policy.

TierRelocationWhether to execute tier relocation

• Y: Executes tier relocation.

• N (other than Y): Does not execute tier relocation.

Used

Total number of pages allocated to the volume

Tier. --

0Number of tiers (n)

n. Information for each tier is stored in lower-level REXX variables. nindicates a tier number.






UsedNumber of pages assigned to each tier

IO. --

CtNumber of I/Os for the target volume (integrated value)

Only the number of I/O operations at the back end are counted as

I/O operations (number of I/O operations for the drive media).

diff Number of I/Os for the target volume after the previous KTQSTATS

command was issued

This value is invalid if the prefix TPG.n.IO.Interval in the tiering

policy group structure is set to 0.

Note:

Some REXX variables take effect only for Dynamic Tiering for Mainframevolumes or Dynamic Provisioning for Mainframe volumes. If the value isnot valid, 0 or a NULL is set.

Lower-level REXX variables for LOCAL.SNnnnnn.POOLxx .


LOCAL.SNnnnnn.POOLxx . Upper-variable name

NAMEPool name

TypePool type

• DT: Dynamic Tiering for Mainframe pool

• DP: Dynamic Provisioning for Mainframe pool

• OTHER: Other pools

PageSize Page size (unit: TRK)

AutoMonitoring mode

• Y: Automatic execution mode (tier relocation is

performed automatically)

• N: Manual execution mode

RelocateStartTime#Tier relocation start time (hh:mm)

RelocateEndTime#Tier relocation end time (hh:mm)

RelocatingRelocation status

• Y: Relocation in progress• N: Relocation finished or stopped

RelocatePerCentRelocation progress (%)

ExpectedMigrationPageCt#Expected number of migrated pages for the entirepool






MigratedPageCt#Number of migrated pages for the entire pool

Tier. --

0Number of tiers (n)

n. Information for each tier is stored in lower-levelREXX variables. n indicates a tier number.

MediaAttribute of the drive media in the pool(hexadecimal)

• 0000: SSD (SSD) or Native Flash (NF)

• 0001: SAS 15K RPM (SAS 15K)

• 0002: SAS 10K RPM (SAS 10K)

• 0003: SATA 7.2K RPM (SATA 7.2K)

• 0004: External connection (Mid) (EXTERNAL M)

• 0005: SAS 7.2K RPM (SAS 7.2K)

• 0006: Mixed• 0007: External connection (High) (EXTERNAL H)

• 0008: External connection (Low) (EXTERNAL L)

CapacityTotal tier capacity

UsedUsed tier capacity

UnitUnit of the total tier capacity and used tier capacity

EntryBufferPerCentFree area ratio for new-page assignment (%). This isthe percentage of free area allocated for each tier towhich new pages can be assigned during relocation.

RelocateBufferPerCentPercentage of the buffer area used for relocation(%)

m. m indicates the migration-source tier number.

ExpectedMigrationPageCt#Expected number of pages to be migrated from tierm to tier n.

MigratedPageCt# Number of pages migrated from tier m to tier n.

Note:

Some REXX variables take effect only for Dynamic Tiering for Mainframe

pools. If the value is not valid, 0 or a NULL is set.

#:

This does not display information about the relocation that is currentlybeing executed. This displays information about the relocation that wasperformed in the previous cycle.





How to obtain the variable parts (nnnn and xx) in REXX variablenames

To view volume and pool information from the host-discovered arraystructure, you need the following information for the storage system toidentify the volume or pool: serial number (nnnnn in SNnnnnn), control unit

number (xx in CUxx ), command control address (xx in CCAxx ), and pool ID

(xx in POOLxx ). You can obtain these values from the REXX variable values in

the tiering policy group structure, host-discovered array index structure, ordevice information structure. Use the obtained values to create a REXXvariable name for the host-discovered array structure, and then view theinformation. For details, see the sample scripts in which the correspondingcommands are used.

Example of the KTQRYDEV command

This example shows how to obtain the storage system's serial number(SN), CU number, and command control address from the deviceinformation structure, create the REXX variable name for the host-discovered array structure, and then view the tiering policy level of thevolume. In this example, the prefix of the host-discovered array structure

is assumed to be DEMO_STEM.sym_SN = 'SN' || DEMO_STEM.SerialNumsym_CU = 'CU' || DEMO_STEM.CUNumsym_CCA = 'CCA' || DEMO_STEM.CCATierLevel = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierLevel

Related topics

• Appendix C, Sample scripts on page C-1

Tiering policy group structure

The values to be set for the storage system for the volumes belonging to atiering policy group are stored in the tiering policy group structure.


The KTLOAD command is executed (the structure is created by loading

information from the tiering policy group definition file).


The prefix of the tiering policy group structure name is the value specified forthe STEM parameter of each command.


The following table lists and describes the REXX variables in the tiering policygroup structure. A REXX variable name is preceded by the prefix of thestructure name.





Table 8-5 Tiering policy group structure


TPG. --

IDTiering policy group name

VOL.--

0Number of volumes (n)

n.Information for each volume is stored in lower-level REXXvariables.

SerialNumStorage system serial number

CUNumCommand unit number

CCACommand control address

POOLID Pool ID (decimal number)

SSIDStorage system ID

TierLevelTiering policy level

EntryNew-page assignment tier

• HIGH: New pages are assigned to a high-level tier first.

• MIDDLE: New pages are assigned to a middle-level tier first.

• LOW: New pages are assigned to a low-level tier first.

TierRelocation

Whether to execute tier relocation

• Y: Executes tier relocation.

• N (other than Y): Does not execute tier relocation.

IO. --

Interval Interval since issuing the KTQSTATS command (in seconds). This is

the elapsed time since the previous KTQSTATS command was

issued. If the command has not been issued yet or has beenissued only one time, 0 is set.

Device information structure

The address and the pool ID of the volumes subject to the KTQRYDEV

command is stored in the device information structure.


When the KTQRYDEV command is executed






The prefix of the device information structure name is the value specified forthe STEM parameter of the KTQRYDEV command.


The following table lists and describes the REXX variables in the device

information structure. A REXX variable name is preceded by the prefix of thestructure name.

Table 8-6 Device information structure

REXX variable

nameDescription

SerialNum Storage system serial number

CUNum Command unit number

CCA Command control address

POOLID Pool ID (decimal number)A NULL is set if the volume subject to the KTQRYDEV command is not a Dynamic

Provisioning for Mainframe volume or a Dynamic Tiering for Mainframe volume.





9

Collecting trace information and logs

This chapter describes collecting trace information and logs for Tiered StorageManager for Mainframe.

□ Information that can be used for troubleshooting

□ Collecting trace information

□ Log types for Tiered Storage Manager for Mainframe

□ Collecting event logs

□ Collecting event logs by using the system logger service

□ Collecting event logs without using the system logger service

□ Collecting ISPF logs

□ Collecting the CLI command-execution log

Collecting trace information and logs 9-1




Information that can be used for troubleshooting

If an error occurs, trace information and logs can be used for troubleshooting.

The following table shows the information that can be used fortroubleshooting.

Table 9-1 Information that can be used for troubleshooting

Information that canbe used for

troubleshootingDescription

Trace information Trace information includes user operations and macros issued to the storagesystem. It is saved in memory and can be used to help analyze the causes of errors. In Tiered Storage Manager for Mainframe, trace information saved inmemory is output to an ABEND dump if a CLI command terminates abnormally.

Logs • Error messages and trace information (event log) are collected in logdatasets.

• Log data for the CLI commands executed in the ISPF panel are collected inISPF log dataset.

• CLI command-execution logs are collected in SYSLOG.

Related topics

• Collecting trace information on page 9-2

• Log types for Tiered Storage Manager for Mainframe on page 9-3

Collecting trace information

Trace information about user operations and macros issued to hardware is

saved in memory. To help analyze the causes of errors, the trace informationcan be specified to be output to an ABEND dump if a CLI commandterminates abnormally.

If GTF is started with the GTF parameter specified to acquire an USR trace(TRACE=USR), trace information will be acquired as a GTF trace with anevent code from X'300' to X'30F'.

Collecting trace information when using scripts

To output ABEND dumps when using scripts to operate Tiered StorageManager for Mainframe, specify SYSABEND for a JCL DD statement.

Collecting trace information when using TSO/E

The following describes how to output ABEND dumps when using TSO/E tooperate Tiered Storage Manager for Mainframe.

9-2 Collecting trace information and logs




Procedure

1. Log on to the TSO/E terminal.

2. Enter the following commands.

¢ To output an ABEND dump to the spool:

ALLOC DD(SYSABEND) SYSOUT(SYSOUT-class)

¢ To output an ABEND dump to a dataset:

ALLOC DD(SYSABEND) DS(dataset-name)

3. Execute a CLI command.

4. If the CLI command terminated abnormally and the system returned tothe READY mode, press the Enter key.

If you enter a TSO/E command without pressing the Enter key, ABENDdumps might not be output.

Log types for Tiered Storage Manager for Mainframe

Of the acquired trace information, only the information that must be

presented to the user is output to a log.

The following table shows the log types for Tiered Storage Manager forMainframe, the collected information, and the output destinations.

Table 9-2 Log types for Tiered Storage Manager for Mainframe

Log type Collected information Output destination

Event log • Messages

• Only in the case of an I/O error,parameter information, returninformation, and sense byteinformation for that I/O

• Time-stamps

• Command parameter information

• When the system logger service isused:

DASD-only log stream for the systemlogger service

• When the system logger service isnot used:

Log dataset for Tiered StorageManager for Mainframe

ISPF log • Transaction logs in the ISPF panel

• Messages that were output duringcommand execution

ISPF log dataset

CLI command-execution log

• CLI command name

• Parameters

• Execution results

SYSLOG

Related topics


• Collecting ISPF logs on page 9-19






Collecting event logs

This section describes how to collect event logs.

How to collect event logs

Two methods are available for collecting event logs. Use the LOGPUT

environment variable or the &YKLOGPT system symbol to select the method.

The methods for collecting event logs are as follows.

• Use the system logger service to output event logs to a log stream, andthen use the Tiered Storage Manager for Mainframe tool to output theevent logs from the log stream to a dataset.

• Output event logs to a Tiered Storage Manager for Mainframe log datasetwithout using the system logger service.

The system logger service provides the MVS-standard functionality forwriting, displaying, and deleting log data.

The system logger service has the following features. Use them as the

guideline for determining whether to use the system logger service.

• Provides mechanisms for capacity management (functions forautomatically migrating log data and automatically allocating logdatasets) and troubleshooting (log duplication function).

• Allows the users to extract only necessary information later andcustomize it.

• Allows the users to view logs in the middle of a program.

Related topics

• Setting the operating environment by using environment variables on

page 2-19




About event log output datasets

Event log data can be output to two types of datasets.

When the system logger service is used, log data is output to the DASD-only

log stream for the system logger service. Use the event log output tool(KTLOGCP) to output the log data from the log stream to a dataset.

If the system logger service is not used, log data is output to a TieredStorage Manager for Mainframe log dataset for each job.

The following figure provides an overview of event log output.





Figure 9-1 Overview of event log output

For details about log streams, see the manual MVS Programming: Assembler

Services Reference.

Related topics



Collecting event logs by using the system logger service

This section describes how to collect event logs when the system loggerservice is used.

Settings for collecting event logs when using the system loggerservice

This subsection describes the settings for collecting event logs by using thesystem logger service.

To collect event logs by using the system logger service, the settings forusing the system logger service must be specified.

To use the DASD-only log stream for the system logger service, perform allsysplex setup procedures described in the manual MVS Setting Up a Sysplex to set up the sysplex.

Care must be taken with the items shown in the following table during setupof the system logger service.





Table 9-3 Items that require care during setup of the system loggerservice

ItemRequired/optional

Remarks

Setting LOGR couple data sets Required --

Defining the SMS for the system

logger service

Optional Set this item when allocating

staging datasets or log datasets tothe SMS management volume.

Defining a log stream Required --

Setting access privileges forsystem logger resources

Optional Set this item when using theSystem Authorization Facility (SAF).

Starting the system loggerservice

Required --

Related topics

• Setting LOGR couple data sets on page 9-6• Defining the SMS for the system logger service on page 9-6

• Defining a log stream on page 9-6

• Setting access privileges for system logger resources on page 9-7

• Starting the system logger service on page 9-7

Setting LOGR couple data sets

In a sysplex environment, format the LOGR couple datasets and then definethem for the sysplex.

Defining the SMS for the system logger service

To allocate staging datasets and log datasets used by the system loggerservice to an SMS management volume, you must define the SMS for theTiered Storage Manager for Mainframe system logger service.

You need to define the following items.

• SMS storage group

• Management class

• Storage class

• Data class• ACS routine

Defining a log stream

Use the IXCMIAPU utility to define a log stream.





Allocate one Tiered Storage Manager for Mainframe log stream to a system.In the sysplex environment, allocate one log stream to each system in whichTiered Storage Manager for Mainframe is started.

Procedure

1. Correct the parameters including the log stream name(log_stream_name) for the IXCMIAPU utility shown below according to

the environment.The following is an example of parameters when an SMS definition is notused.

//DEFINE1 EXEC PGM=IXCMIAPU//SYSPRINT DD SYSOUT=*//SYSIN DD *DATA TYPE(LOGR) REPORT(YES)DEFINE LOGSTREAM NAME(log_stream_name)DASDONLY(YES)MAXBUFSIZE(64000)STG_SIZE(800)LS_SIZE(5000)

HLQ(CCENTRAL)/*

2. Execute the IXCMIAPU utility.

Related topics

• Parameters specified when a log stream is defined on page 9-8

Setting access privileges for system logger resources

If the System Authorization Facility (SAF) can be used, grant accessprivileges to users who execute Tiered Storage Manager for Mainframe

commands because the system performs SAF checks for each request.

The following access privileges must be granted.

• CLASS: FACILITY

RESOURCE: MVSADMIN.LOGR

Permission: ALTER permission or READ permission

• CLASS: LOGSTRM

RESOURCE: Log stream name

Permission: ALTER permission

Starting the system logger serviceThis subsection describes how to start the system logger service.

To start the system logger service, activate the subsystem (system loggeraddress space). If the subsystem is not active, an error will occur in theconnection request macro (IXGCONN).





Procedure

1. Use either of the following methods to activate the subsystem.

¢ Add SUBSYS SUBNAME(LOGR) INITRTN(IXGSSINT) to the IEFSSNxx

parmlib member.

To activate the subsystem with this method, you must perform an IPLagain.

¢

Use the SETSSI ADD,SUBNAME=LOGR,INITRTN=IXGSSINT command todynamically add the subsystem.

Tip: To stop the system logger service, execute the FORCE IXGLOGR,ARM

command. To restart the system logger service that was stopped by theFORCE IXGLOGR,ARM command, use the S IXGLOGRS command.

Parameters specified when a log stream is defined

This subsection describes the parameters that are specified when theIXCMIAPU utility is used to define a log stream.

For details about parameters, see the manual MVS Setting Up a Sysplex .NAME(log_stream_name)

The log stream name is CCENTRAL.LOG.system-name. For a system-name,

specify the system name of the system symbol (&SYSNAME). If a system

name starts with a number, Tiered Storage Manager for Mainframeextracts the last five characters of the system name and adds prefixedYKS to them to form the log stream name. If a system name starts with a

number, the last five characters used for the log stream name must beunique within the sysplex.

The following shows examples of how a system name starting with anumber is converted to the system name in a log stream name.

¢ For the system name 1SYS starting with a number and consisting of

less than five characters:

YKS is added to the system name to create YKS1SYS.

¢ For the system name 1SYSTEM starting with a number and consisting

of more than five characters:

YKS is added to the last five characters YSTEM to create YKSYSTEM.

¢ For the system names 1SYSTEM and 2SYSTEM, both of which start with

numbers and consist of more than five characters:

YKS is added to the last five characters YSTEM to create YKSYSTEM,

which results in two identical system names. In this case, the system

name (&SYSNAME) specified for the IEASYSxx parmlib member must bechanged.

For details about system names, see the manual MVS Initialization and Tuning Reference.

DASDONLY(YES)

Specify YES to make the log stream a DASD-only log stream.





MAXBUFSIZE(maxbufsize)

Maximum block size of a log. Specify 64000 (bytes).

STG_SIZE(stg_size)

Specify the size of the staging dataset. Specify a value in the range from100 (400KB) to 1000 (4MB).

Do not specify this parameter when using an SMS definition.

STG_DATACLAS(stg_dataclas)

Specify the name of the SMS data class used for allocating the DASDstaging dataset for this log stream. Specify this parameter when using anSMS definition.

STG_MGMTCLAS(stg_mgmtclas)

Specify the name of the SMS management class used for allocating theDASD staging dataset for this log stream. Specify this parameter whenusing an SMS definition.

STG_STORCLAS(stg_storclas)

Specify the name of the SMS storage class used for allocating the DASD

staging dataset for this log stream. Specify this parameter when using anSMS definition.

LS_SIZE(ls_size)

Specify the size of the DASD log dataset. Specify any size.

The required size depends on the frequency of the output of event logdata from the log stream to a dataset and how event log data is deleted.Specify an appropriate value to prevent the dataset from being full.

Do not specify this parameter when using an SMS definition.

LS_DATACLAS(ls_dataclas)

Specify the name of the SMS data class used for allocating a log dataset.

Specify this parameter when using an SMS definition.

LS_MGMTCLAS(ls_mgmtclas)

Specify the name of the SMS management class used for allocating a logdataset. Specify this parameter when using an SMS definition.

LS_STORCLAS(ls_storclas)

Specify the name of the SMS storage class used for allocating a logdataset. Specify this parameter when using an SMS definition.

AUTODELETE(YES)

Specify this parameter when automatically deleting event log data.

RETPD(retpd )Specify this parameter when automatically deleting event log data.Specify the number of days to retain event log data in the log stream.

HLQ(CCENTRAL)

This parameter specifies that CCENTRAL is the high level qualifier used as

a part of the log dataset name. This parameter is optional. If this





parameter is not specified, the default high level qualifier IXGLOGR will be

a part of the log dataset name.

The specification of the following parameters is optional.

• HIGHOFFLOAD

• LOWOFFLOAD

• LIKE

• MODEL

• DIAG

JCL example for confirming a log stream

The following shows an example of JCL for confirming the definition of a logstream and the allocation of a log dataset.

//LIST1 EXEC PGM=IXCMIAPU//SYSPRINT DD SYSOUT=*//SYSIN DD *

DATA TYPE(LOGR) REPORT(YES)LIST LOGSTREAM NAME(log_stream_name) DETAIL(YES)/*

JCL example for deleting a log stream

The following shows a JCL example used for deleting the log stream when thelog dataset is full.

//DEL1 EXEC PGM=IXCMIAPU//SYSPRINT DD SYSOUT=*//SYSIN DD *DATA TYPE(LOGR)

DELETE LOGSTREAM NAME(log_stream_name)/*

Preventing the event log from becoming full when the system loggerservice is used

This subsection describes how to prevent the event log from becoming fullwhen the system logger service is used.

Procedure

1.

If a log dataset is full, execution of a CLI command will continue, butevent log data will no longer be output. Use either of the followingmanagement methods to prevent the log dataset from becoming full.

¢ Automatically delete event log data (specify the AUTODELETE(YES)

parameter when defining the log stream).

¢ Periodically delete and re-define the log stream.





Use the IXCMIAPU utility with the DELETE LOGSTREAM

NAME(log_stream_name) parameter specified to delete the log

stream. The log dataset is deleted when the log stream is deleted. Fordetails, see the manual MVS Setting Up a Sysplex .

Related topics


• JCL example for deleting a log stream on page 9-10

Re-defining the log stream when the event log is full

If a log dataset is full, execution of CLI commands will continue, but event logdata will no longer be output. To resume the output of event log data,suspend the CLI command, and then delete and re-define the log stream.

Procedure

1. Suspend the CLI command.

2. Use the event log data output tool (KTLOGCP) to output all log data fromthe log stream to a dataset.

3. Use the IXCMIAPU utility with the DELETE LOGSTREAM

NAME(log_stream_name) parameter specified to delete the log stream.

The log dataset is deleted when the log stream is deleted. For details, seethe manual MVS Setting Up a Sysplex .

4. Re-define the log stream.

5. Log on to TSO/E again and then execute the CLI command.

Related topics


• Outputting logs by using the event log data output tool on page 9-13


Restarting the system logger service and re-defining the log streamwhen the event log is full

If a log dataset is full, execution of CLI commands will continue, but event logdata will no longer be output. The log stream cannot be deleted duringexecution of a CLI command. Therefore, if the CLI command cannot be

stopped when a log dataset is full, you can restart the system logger serviceand then delete and re-define the log stream to resume the output of eventlog data.

Procedure

1. Enter the FORCE IXGLOGR,ARM command to stop the system logger

service.





2. Enter the S IXGLOGRS command to restart the system logger service.

3. Use the IXCMIAPU utility with the DELETE LOGSTREAM

NAME(log_stream_name) parameter specified to delete the log stream.

The log dataset is deleted when the log stream is deleted. For details, seethe manual MVS Setting Up a Sysplex .

4. Re-define the log stream.

Related topics

• Starting the system logger service on page 9-7



Disk space requirements for the event log when the system loggerservice is used

The following table shows the amount of log data when the system loggerservice is used to output the event log.

Table 9-4 Amount of event log data when the system logger service isused

Types of event log data Size#1 Number percommand

Messages (excluding messages outputfrom the ISPF panel and scripts)

68 + message

length#2

Number of outputmessages

Only in the case of an I/O error,parameter information for the CCW forthat I/O

68 + CCW length#2 Number of I/O errors

Only in the case of an I/O error, returninformation for that I/O

224 Number of I/O errors

Only in the case of an I/O error, sensebyte information for that I/O


Time-stamps 96 2

Command parameter information 224 1

#1

The size is rounded up to a multiple of 32 before being output.

#2

The maximum length is 256 bytes.

Estimating the staging dataset

Estimate the disk capacity based on the amount of event log data.





Estimating the log stream dataset

Estimate the disk capacity based on the amount of offloaded event log dataand the retention period.

Estimating the dataset (OUTLOG) to which logs are output from thelog stream

Estimate the disk capacity based on the amount of offloaded event log dataand the retention period.

Overview of the event log data output tool

The event log data output tool (KTLOGCP) outputs the event log data

accumulated in the log stream to a dataset. The output log data will not bedeleted from the log stream.

KTLOGCP allows you to output only the necessary event log data by specifying

conditions for output data.

The maximum length of a record that can be output is 8,192 bytes. Log data

longer than 8,192 bytes will be divided before being output. The maximumblock length is 32,760 bytes.

Tip: To merge event log data activated by multiple OSs in a sysplexenvironment, output the log for each OS from the log stream to a dataset,transfer files to a PC, and then sort the files in chronological order.

Outputting logs by using the event log data output tool

From the event log output by the system logger service to the data stream,you can output the required log data to a dataset by using the event log dataoutput tool (KTLOGCP).

Procedure

1. Determine the conditions for event log data to be output (start time, endtime, and job name).

2. Create a control statement for KTLOGCP.

The following shows the format of the SYSIN dataset for specifying a

control statement.

¢ Dataset format: Sequential dataset in the fixed-length record format

¢ Record length: 80 bytes

¢ Block length: Any value (multiple of 80)

3. Create a JCL for KTLOGCP.

Use the following example to create a JCL for KTLOGCP.

//YUKON01 JOB// EXEC PGM=KTLOGCP//OUTLOG DD DSN=YUKON.LOG.DATA,DISP=(NEW,KEEP),





// RECFM=VB,LRECL=8192,BLKSIZE=32760,// SPACE=(CYL,(100,10)),VOL=SER=WKVL01,UNIT=DASD//SYSPRINT DD SYSOUT=A//SYSIN DD *RANGE STARTTIME(2013/03/24,00:00:00) ENDTIME(2013/03/24,23:59:59)SELECT COND(JOBNAME,EQ,'USER01T')SELECT COND(JOBNAME,EQ,'USER01')/*

4. Execute KTLOGCP.

Related topics

• Control statements for the event log data output tool on page 9-14

• Output format of the event log data output tool on page 9-15

Control statements for the event log data output tool

A control statement specified in the DD statement SYSIN for the log data

output tool (KTLOGCP) contains a RANGE control statement, which specifies

the time, and SELECT control statements, which specify the job names.

If the DD statement SYSIN is not specified or if no control statement exists,

all log data for the system logger service will be output from the log streamto a dataset.

Format of the RANGE control statementRANGE{

1STARTTIME(yyyy /mm/dd [,hh:mm:ss]) 1ENDTIME(yyyy /mm/dd [,hh:mm:ss])|

1STARTTIME(yyyy /mm/dd [,hh:mm:ss])|

1ENDTIME(yyyy /mm/dd [,hh:mm:ss])}

RANGE control statement operands

STARTTIME(yyyy /mm/dd [,hh:mm:ss]) ~ <<1900/01/01,00:00:00>> <<if

hh:mm:ss is omitted, 00:00:00>>

Use the local time to specify the start date and time of the log data to beoutput.

ENDTIME(yyyy /mm/dd [,hh:mm:ss]) ~ <<2042/09/17,23:53:47>> <<if

hh:mm:ss is omitted, 23:59:59>>

Use the local time to specify the end date and time of the log data to beoutput.

The RANGE control statement can be specified only once at the beginning of the first control statement line.

Format of the SELECT control statement

SELECT 1COND(JOBNAME,EQ,value)





SELECT control statement operands

COND(JOBNAME,EQ,value) ~ <string of 8 or fewer characters>

Specify the job name as a condition of the log data to be output from thelog stream to a dataset. Enclose the specified value in quotation marks(').

You can specify a maximum of 100 lines of SELECT control statements. If multiple lines are specified, all log data that matches the control statements

will be output from the log stream to a dataset.

Coding of the RANGE and SELECT control statements

• A line beginning with an asterisk (*) is treated as a comment line.

• Columns after the 73rd column in a control statement line are ignored.

• Each control statement must be completely specified on one line. Acontrol statement cannot extend over two or more lines.

Control statement examples

To output the log data with acquisition dates in the range from 2013/03/2400:00 to 2013/03/24 23:59, specify as follows.

RANGE STARTTIME(2013/03/24,00:00:00) ENDTIME(2013/03/24,23:59:59)

To output the log data with acquisition dates in the range from 2013/03/2400:00 to 2013/03/24 23:59 and with the job names USER01T or USER01,specify as follows.

RANGE STARTTIME(2013/03/24,00:00:00) ENDTIME(2013/03/24,23:59:59)SELECT COND(JOBNAME,EQ,'USER01T')SELECT COND(JOBNAME,EQ,'USER01')

Output format of the event log data output tool

The following table shows the output format of the event log data output tool.

Table 9-5 Output format of the event log data output tool

OffsetLengt

hOutput contents Description

+X'00' 2 Output data length Output data length = 32 + log data length (n)

+X'02' 2 Reserved '0000'X

+X'04' 1 Division flag 1 For the first record: '01'X

For records other than the first record: '00'X

+X'05' 1 Division flag 2 For the last record: '01'X

For records other than the last record: '00'X

+X'06' 8 GMT time-stamp (TODformat)

The time-stamp specified by the system loggerservice when the log data is output

+X'0E' 8 Local time-stamp (TODformat)

The time-stamp specified by the system loggerservice when the log data is output





OffsetLengt

hOutput contents Description

+X'16' 10 Reserved '00 ... 00'X

+X'20' n Log data --

Collecting event logs without using the system loggerservice

If the system logger service is not used, log data is output to a TieredStorage Manager for Mainframe log dataset.

Allocating log datasets without using the system logger service

Allocate two sequential datasets (log datasets) to each job to collect logs.

Procedure

1. Estimate the log dataset capacity.

Estimate the amount of log data based on the frequency at which CLIcommands are issued and the frequency of errors. Allocate enough spaceto ensure that log data can be output until a backup of the log dataset iscreated in one sequential dataset.

2. Create log datasets.

For the log dataset, specify the amount of the initial allocation only. Thespecification of any additional allocation is ignored.

The following shows the format of the log dataset.

¢ RECFM: VB

¢ LRECL: 8196

¢ BLKSIZE: 8200

The following shows an example of creating log datasets in TSO/E.

ALLOC DS('USER01.YKLOG01') VOL(WKVL01) NEW SP(100) CYL DSORG(PS)RECFM(V,B) LRECL(8196) BLKSIZE(8200)ALLOC DS('USER01.YKLOG02') VOL(WKVL01) NEW SP(100) CYL DSORG(PS)RECFM(V,B) LRECL(8196) BLKSIZE(8200)

3. Allocate the log datasets.

¢ For TSO/E, use the ALLOC command to allocate DD name YKLOG01 and

DD name YKLOG02 to log datasets.¢ When using JCL, specify DD statement YKLOG01 and DD statement

YKLOG02 in the JCL.

The following shows a specification example in TSO/E.

ALLOC DD(YKLOG01) DS('USER01.YKLOG01') OLDALLOC DD(YKLOG02) DS('USER01.YKLOG02') OLD





The following shows a JCL specification example.

//YKLOG01 DD DSN='USER01.YKLOG01',DISP=OLD,VOL=SER=WKVL01,UNIT=DASD//YKLOG02 DD DSN='USER01.YKLOG02',DISP=OLD,VOL=SER=WKVL01,UNIT=DASD

Allocate a log dataset for each job. When the job terminates, another job canreuse that log dataset. In this case, logs are added to the end of the previouslog output.

Note, however, that you need to reallocate a new log dataset rather thanusing the existing one in the following cases:

• An I/O error occurred in the log dataset.

• The OS went down.

Related topics

• Disk space requirements for the event log when the system logger serviceis not used on page 9-18

Writing to a log dataset without using the system logger serviceThis subsection describes how to write data to a log dataset without using thesystem logger service. How the data is written depends on the number of allocated log datasets.

When both YKLOG01 and YKLOG02 are specified

1. Logs are written to YKLOG01. If the log dataset is reused, logs are added

to the end of the previous log output.

2. If YKLOG01 is full, logs are written to YKLOG02.

3. If YKLOG02 is also full, logs are written to YKLOG01. In this case, the

existing logs in YKLOG01 are overwritten.

4. Steps 2 and 3 are repeated.

If a log dataset is full and the log output destination is switched, the KTG291I

message (the log dataset is full) and the KTG292I message (the log dataset is

switched) are output to the console. At this time, the KTG291I message

indicates the name of the log dataset that became full. The KTG292I message

indicates the job name and the DD names of log datasets before and afterswitching (YKLOG01 or YKLOG02).

Tip: When a log dataset becomes full (KTG291I and KTG292I messages are

output), you can suspend execution of the script and back up the log datasetindicated in the KTG291I message. However, the log dataset cannot be

backed up if the KTG292I message indicates the same log dataset before and

after switching. This is because an error might have occurred in either logdataset and the log dataset before switching has been overwritten.





If neither YKLOG01 nor YKLOG02 is specified

The KTG261E message is output and processing continues without acquiring

logs. To acquire logs, you need to log on to TSO/E again and then specify theYKLOG01 and YKLOG02 DD statements.

If either YKLOG01 or YKLOG02 is specified

The KTG261E message is output and logs are output only to the log datasetfor which the DD statement is specified. In this case, if the log datasetbecomes full, it will be overwritten from the beginning.

If an I/O error occurs in YKLOG01 or YKLOG02

The messages from KTG262E to KTG264E are output, and logs will be output

only to the log dataset in which an I/O error has not occurred. If the logdataset becomes full, it will be overwritten from the beginning. If an I/O erroroccurs in both log datasets, processing continues without acquiring logs.

Tip: You cannot view log datasets during execution of a CLI command. Wait

until the executing script terminates and then view the log dataset.

Disk space requirements for the event log when the system loggerservice is not used

The following table shows the amount of log data when the event log isoutput without using the system logger service.

Table 9-6 Amount of event log data when the system logger service is notused

Types of event log data Size#1 Number per

command

Messages (excluding messages outputfrom the ISPF panel and scripts)

100 + message

length#2

Number of outputmessages

Only in the case of an I/O error,parameter information for the CCW forthat I/O

100 + CCW length#2 Number of I/O errors

Only in the case of an I/O error, returninformation for that I/O


Only in the case of an I/O error, sensebyte information for that I/O


Time-stamps 128 2

Command parameter information 256 1

#1

The size is rounded up to a multiple of 32 before being output.

#2





The maximum length is 256 bytes.

Collecting ISPF logs

When a CLI command is executed in the ISPF panel, ISPF log data isautomatically collected to an ISPF log dataset.

Checking ISPF logs

Check the ISPF log showing the operation history for the ISPF panel.

Procedure

1. In the ISPF Primary Option Menu panel, select 7 (Dialog Test).

The Primary Option panel appears.

2. Select 5 (Log).

The Browse log panel appears, displaying the contents of the ISPF log.

Preventing the ISPF log dataset from becoming full

If you use the ISPF panel for CLI command operations for a long time, theISPF log dataset might become full. This could cause a CLI command toterminate abnormally. To prevent such a problem, perform the following if you want to use the ISPF panel for a long time for CLI command operations.

Procedure

1. When you start using ISPF, delete the ISPF log information from the ISPFlog dataset.

2. When you perform an operation in the Tiered Storage Manager forMainframe panel, enter LOG in the Command line.

The Specify Disposition of Log Data Set panel appears.

3. Select 3 (Keep existing data set and continue with new data set ).

The ISPF log dataset is switched to another dataset.

You must periodically switch the ISPF log dataset to another dataset toprevent the ISPF log dataset from becoming full.

Tip: If the CLI command terminated abnormally because the ISPF log datasetwas full, in the ISPF end menu ( Specify Disposition of Log Data Setpanel), select 4 (Keep data set - New (allocate new data set in next session))

to save the current ISPF log dataset, and then allocate another dataset.





Collecting the CLI command-execution log

You can use the environment variable SYSLOG to specify the command-

execution log (that is, the command name, parameters, and executionresults) to be output to either SYSLOG or the console.

The execution log for the following CLI commands is output. If you specifythat the log is to be output to SYSLOG, the KTC310I and KTC311I message

containing the log is output. If you specify that the log is to be output to theconsole, the KTC910I and KTC911I message containing the log is output.

KTACTTPG, KTCONMSG, KTDCTDEV, KTDCTTPG, KTGETHDA, KTIMPORT, KTLOAD,

KTQRYDEV, KTQRYRLC, KTQRYTPG, KTQSTATS, KTSCAN, KTSTORE, KTCONMSG

The log for the KTCONMSG command will be output only when OPEN or CLOSE is

specified in the OP parameter.

There are two methods for extracting output CLI command-execution logs:

• Use an ISPF editor.

• Use an output script.

Related topics



• Extracting CLI command-execution logs by using an ISPF editor on page9-20

• Extracting CLI command-execution logs by using an extraction script onpage 9-21

Extracting CLI command-execution logs by using an ISPF editorTo use an ISPF editor to extract CLI command-execution logs from SYSLOGto a sequential dataset:

Procedure

1. Create a dataset to which log data will be extracted from SYSLOG.

YUKON.KTLOG is assumed as the name of the allocated sequential dataset.

2. Display SYSLOG in the SDSF panel.

3. In the panel showing SYSLOG, enter the SDSF command to extract

SYSLOG data for the desired period to the dataset you created in step 1.To extract information from 13:00 to 14:00, enter as follows.

PRINT ODSN 'YUKON.KTLOG'PRINT 13:00:00 14:00:00PRINT CLOSE





4. Use the ISPF editor to display a panel for editing the dataset created instep 3.

5. In the ISPF editor panel, enter the following command to delete the linesother than the CLI command-execution logs.

If the CLI command-execution logs are specified to be output to SYSLOG(SYSLOG=YES):

exclude p'KTC31#I' alldelete all nxresetsave

If the CLI command-execution logs are specified to be output to theconsole (SYSLOG=CONSOLE):

exclude p'KTC91#I' alldelete all nxresetsave

Caution: If the KTC910I message extends to two lines, the second line is

not extracted.

6. Terminate the ISPF editor.

Extracting CLI command-execution logs by using an extraction script

You can extract CLI command-execution logs to a sequential dataset by usingan extraction script.

Procedure

1. Create a dataset to which SYSLOG data will be extracted.

YUKON.SYSLOG is assumed as the name of the allocated sequentialdataset.

2. Create a dataset to which only CLI command-execution logs will beextracted.

YUKON.KTLOG is assumed as the name of the allocated sequential dataset.

3. Display SYSLOG in the SDSF panel.

4. In the panel showing SYSLOG, enter the SDSF command to extract

SYSLOG data for the desired period to the dataset you created in step 1.

To extract the information from 13:00 to 14:00, enter as follows.

PRINT ODSN 'YUKON.SYSLOG'PRINT 13:00:00 14:00:00PRINT CLOSE

5. Execute the CLI command-execution log output procedure to extract theCLI command-execution log to the dataset you created in step 2.

If the procedure is stored in the sequential dataset YUKON.EXTCMD,

execute as follows.





If the CLI command-execution logs are specified to be output to SYSLOG(SYSLOG=YES):

EXEC 'YUKON.EXTCMD' 'KTC31 YUKON.SYSLOG YUKON.KTLOG'

If the CLI command-execution logs are specified to be output to theconsole (SYSLOG=CONSOLE):

EXEC 'YUKON.EXTCMD' 'KTC91 YUKON.SYSLOG YUKON.KTLOG'

Example of a CLI command-execution log output procedure

/* REXX ***/Parse Upper Arg Mystrg Myinds Myoutds;"ALLOCATE DA('"Myinds"') F(INDD) SHR REUSE""ALLOCATE DA('"Myoutds"') F(OUTDD) OLD REUSE""EXECIO 0 DISKR INDD (OPEN)"eof='NO'DO WHILE eof = 'NO' "EXECIO 1 DISKR INDD (STEM LINE.)" IF RC = 2 THEN eof='YES' ELSE DO IF INDEX(LINE.1,Mystrg) <> 0 THEN DO "EXECIO 1 DISKW OUTDD (STEM LINE.)" END ENDEND"EXECIO 0 DISKR INDD (FINIS)""EXECIO 0 DISKW OUTDD (FINIS)""FREE F(INDD)""FREE F(OUTDD)"EXIT 0

Caution: If the KTC910I message extends to two lines, the second line is not

extracted.

Caution: Care must be taken when executing many CLI commands becauseoutput to SYSLOG increases.





A

XML document type definitions forconfiguration files

This appendix describes the XML document type definitions for configurationfiles used by Tiered Storage Manager for Mainframe.

□ Elements common to configuration files

□ Elements in the disk configuration definition file

□ Elements in the tiering policy group definition file

□ Example of files used by Tiered Storage Manager for Mainframe

XML document type definitions for configuration files A-1




Elements common to configuration files

The following describes the elements common to all types of configurationfiles.

Note that element names, attribute names, and attribute values are casesensitive.

APIInfo elementThe APIInfo element contains information about the configuration file.

Structure<!ELEMENT APIInfo(ANY)><!ATTLIST APIInfo Level (7.5.0)#REQUIRED UpdateID CDATA#IMPLIED>

The following lists and describes the attributes of this element.

Attribute name Description

Level A character string that indicates the API level (XML interfaceversion of Tiered Storage Manager for Mainframe) is set.

UpdateID Last update ID

DiskDevice element

Information about the volumes of the storage system is stored in theDiskDevice element.

Structure<!ELEMENT DiskDevice(EMPTY)><!ATTLIST DiskDevice SerialNum CDATA#REQUIRED CUNum CDATA#REQUIRED SSID CDATA#REQUIRED CCA CDATA#REQUIRED POOLID CDATA#IMPLIED Cyls CDATA#IMPLIED External (Y|N)#IMPLIED>



SerialNum Serial number of the storage system

CUNum Control unit (CU) number

SSID Storage system ID (SSID)

A-2 XML document type definitions for configuration files





CCA Command control address (CCA)

POOLID Pool ID

Cyls Volume capacity

External External volume information

Elements in the disk configuration definition file

The following describes the elements in the disk configuration definition file.

HostDiscoveredArray element

Information about the storage system is stored in the HostDiscoveredArray

element.

Structure<!ELEMENT HostDiscoveredArray(SoftwareKeys, POOL*,HostAddressedDisk*)><!ATTLIST HostDiscoveredArray Description CDATA#REQUIRED DADID ID#REQUIRED NGDADIDEnable (0|1)#IMPLIED SerialNum CDATA#REQUIRED Model (7700E|9900|9900V|USP|USPV|VSP)#REQUIRED Microcode CDATA#REQUIRED IFType CDATA#REQUIRED PhysicalSerialNum CDATA#IMPLIED>



Description Used by the system.

DADID Used by the system.

NGDADIDEnable Used by the system.

SerialNum Serial number of the scanned storage system

Model Model of the storage system

Microcode Microcode number

IFType Interface version

PhysicalSerialNum Physical DKC (disk controller) serial number of the storage system

SoftwareKeys element

The SoftwareKeys element is used by the system.





Structure<!ELEMENT SoftwareKeys(EMPTY)><!ATTLIST SoftwareKeys TC (0|1)#REQUIRED SI (0|1)#REQUIRED TCA (0|1)#REQUIRED UR (0|1)#REQUIRED>

POOL element

Information about pools is stored in the POOL element.

Structure<!ELEMENT POOL(PoolTier*)><!ATTLIST POOL POOLID CDATA#REQUIRED NAME CDATA#IMPLIED Type CDATA#REQUIRED PageSize CDATA#IMPLIED>



POOLID Pool ID

NAME Pool name

Type Pool type information:

DT: Dynamic Tiering for Mainframe pool

DP: Dynamic Provisioning for Mainframe pool

OTHER: Other pools

PageSize Page size

PoolTier element

Information about tiers is stored in the PoolTier element.

Structure<!ELEMENT PoolTier(ENPTY)><!ATTLIST PoolTier Tier CDATA#REQUIRED Media CDATA#IMPLIED

>



Tier Tier number






Media Attribute of the media that constitutes the pool

The numerical values (hexadecimal) have the following meanings:

• 0000: SSD (solid state drive) or Native Flash (NF)

• 0001: SAS 15K RPM (SAS 15K)

• 0002: SAS 10K RPM (SAS 10K)

• 0003: SATA 7.2K RPM (SATA 7.2K)• 0004: External media (Mid) (EXTERNAL M)

• 0005: SAS 7.2K RPM (SAS 7.2K)

• 0006: Mixed

• 0007: External media (High) (EXTERNAL H)

• 0008: External media (Low) (EXTERNAL L)

HostAddressedDisk element

Information about the volumes managed by the host is stored in the

HostAddressedDisk element.

Structure<!ELEMENT HostAddressedDisk(DiskDevice)><!ATTLIST HostAddressedDisk Devn CDATA#IMPLIED Volser CDATA#IMPLIED STORGRP CDATA#IMPLIED>



Devn Device number

Volser Volume serial number

STORGRP Name of the SMS storage group that the volume belongs to

Elements in the tiering policy group definition file

The following describes the elements in the tiering policy group definition file.

TieringPolicyGroup elementInformation about tiering policy groups is stored in the TieringPolicyGroup

element.





Structure<!ELEMENT TieringPolicyGroup(TieringPolicy*)><!ATTLIST TieringPolicyGroup ID CDATA#REQUIRED>



ID Tiering policy group name

TieringPolicy element

Information about tiering policies is stored in the TieringPolicy element.

Structure<!ELEMENT TieringPolicy (DiskDevice *)><!ATTLIST TieringPolicy Level (0|1|2|3|4|5)#IMPLIED

Entry (HIGH|MIDDLE|LOW)#IMPLIED TierRelocation (Y|N)#IMPLIED>



Level Tiering policy level

Entry New-page assignment tier

• HIGH: The new page is assigned from the higher tier of tiers


• MIDDLE: The new page is assigned from the middle tier of

tiers set in the tiering policy.

• LOW: The new page is assigned from the lower tier of tiers set

in the tiering policy.

TierRelocation Tier relocation

• Y: Executes tier relocation for the volume.

• N: Does not execute tier relocation for the volume.

Example of files used by Tiered Storage Manager forMainframe

The following figure shows a configuration example of files used by TieredStorage Manager for Mainframe.





Figure A-1 Configuration example of files used by Tiered Storage Managerfor Mainframe

Example of the specifications in a tiering policy information CSV file#TYPE ,DEVICE,TPGID,TierLvl,Entry,RelocSTORGRP,SG1 ,TPG1 ,2DEVN ,1101 ,TPG1 ,1STORGRP,SG2 ,TPG1 ,5

Example of a disk configuration definition file that is generated<?xml version="1.0" encoding="ebcdic-cp-us"?><APIInfo Level="7.5.0"><HostDiscoveredArray SerialNum="14001" Model="VSP"Microcode="700000FF" IFType="3131" PhysicalSerialNum="14002"><POOL POOLID="1" NAME="POOL1" Type="DT" PageSize="672"><PoolTier Tier="1" Media ="0000" /><PoolTier Tier="2" Media ="0001" /><PoolTier Tier="3" Media ="0004" />

</POOL><POOL POOLID="2" NAME="POOL2" Type="DT" PageSize="672"><PoolTier Tier="1" Media ="0000" /><PoolTier Tier="2" Media ="0001" /><PoolTier Tier="3" Media ="0005" /></POOL><HostAddressedDisk Devn="1101" Volser="VOL010" STORGRP="SG1" ><DiskDevice SerialNum="14001" CUNum="01" SSID="2340" CCA="12"POOLID="1" />





</HostAddressedDisk><HostAddressedDisk Devn="1201" Volser="VOL011" STORGRP="SG1"><DiskDevice SerialNum="14001" CUNum="01" SSID="2340" CCA="01"POOLID="1" /></HostAddressedDisk><HostAddressedDisk Devn="1202" Volser="VOL012" STORGRP="SG1"><DiskDevice SerialNum="14001" CUNum="01" SSID="2340" CCA="02"POOLID="1" /></HostAddressedDisk><HostAddressedDisk Devn="2501" Volser="VOL021" STORGRP="SG2"><DiskDevice SerialNum="14001" CUNum="02" SSID="2340" CCA="01"POOLID="2" /></HostAddressedDisk><HostAddressedDisk Devn="2502" Volser="VOL022" STORGRP="SG2"><DiskDevice SerialNum="14001" CUNum="02" SSID="2340" CCA="02"POOLID="2" /></HostAddressedDisk></HostDiscoveredArray></APIInfo>

Example of a tiering policy group definition file that is generated<?xml version="1.0" encoding="ebcdic-cp-us"?>

<APIInfo Level="7.5.0"><TieringPolicyGroup ID="TPG1" ><TieringPolicy Level="1" Entry="MIDDLE" TierRelocation="Y"><DiskDevice SerialNum="14001" CUNum="01" SSID="2340" CCA="12" /></TieringPolicy><TieringPolicy Level="2" Entry="HIGH" TierRelocation="Y"><DiskDevice SerialNum="14001" CUNum="01" SSID="2340" CCA="01" /><DiskDevice SerialNum="14001" CUNum="01" SSID="2340" CCA="02" /></TieringPolicy><TieringPolicy Level="5" Entry="MIDDLE" TierRelocation="Y"><DiskDevice SerialNum="14001" CUNum="02" SSID="2340" CCA="01" /><DiskDevice SerialNum="14001" CUNum="02" SSID="2340" CCA="02" /></TieringPolicy></TieringPolicyGroup>

</APIInfo>





B

Commands that can be used in the ISPFpanels

This appendix describes the commands that can be used in the ISPF panels of Tiered Storage Manager for Mainframe.

□ ERRCODE

□ FILTER

□ FIND

□ LOCATE

□ RFIND

□ SELECT

□ SORT

□ How to specify the search or filter conditions in ISPF panels

Commands that can be used in the ISPF panels B-1




ERRCODE

Function

Displays the Error Code Help panel that shows error code details.

Syntax

ERRCODE

Related topics

• Error Code Help panel on page 5-14

FILTER

Function

Filters a list according to the specified condition.

SyntaxFILTER[{field-name Filter-condition|RESET}]

The abbreviation of FILTER is FIL.

Parameters

If you omit the parameters, the Filter Options panel appears to allow you toenter parameter values.

field-name

Specifies the name of the field for which the filter condition is specified.

Filter-condition

Specifies the condition character string.

RESET

Cancels the filter.

Tip: The filtered results will be sorted in ascending order.

Specification examples

• Character string specification

Specify as follows to filter the list by the SMS storage group namedSTORGRP1.

FIL STORGRP STORGRP1

B-2 Commands that can be used in the ISPF panels




• Generic name specification

Specify as follows to filter the list by volumes having a volume serialnumber beginning with V#704.

FIL Volser V#704*

• Range specification

Specify as follows to filter the list by volumes having device numbers from

703B to 7050.

FIL Devn 703B:7050

Related topics


FIND

Function

Searches for a specified character string.

SyntaxFIND[ search-string ]

The abbreviation of FIND is F.

Parameters

If you omit the parameter, the Find Options panel appears to allow you toenter parameter values.

search-string

Specifies the search string.

Related topics


LOCATE

Function

Searches for the specified character string for a sorted field, and positions thecursor at the line that matches the specified condition. If the specified





character string is not found, the cursor is positioned at the line that has thevalue nearest to the specified condition.

SyntaxLOCATE[ locate-string ]

The abbreviation of LOCATE is L.

Parameters

If you omit the parameter, the Locate Options panelappears to allow you toenter parameter values.

locate-string


Related topics


RFIND

Function

Conducts a search again for the character string specified for the FIND

command that was executed immediately before.

SyntaxRFIND

The abbreviation of RFIND is RF.

Tip: If the FIND command has not been executed, the Find Options panel

appears.

SELECT

Function

Sets or cancels an action in the AC field of a line that satisfies the specified

condition.

SyntaxSELECT[ field-name Select-condition[ {action|RESET}]]

The abbreviation of SELECT is SEL.





Parameters

If you omit the parameters, the Select Options panel appears to allow youto enter parameter values.

field-name

Specifies the name of the field for which the condition is specified.

Select-condition


action

Specifies the action to be set in the AC field. If you do not specify anyaction, a slash (/) will be set in the AC field. If the panel has only oneaction, that action will be set.

RESET

Cancels the action set in the AC field.

Specification examples

• Character string specificationSpecify as follows to set V (displaying the Volume Status Detail panel)in the AC fields for the volumes that belong to the pool with pool ID 120.

SEL PooLID 120 V


Specify as follows to set D (changing the tiering policy to the default) inthe AC fields for the volumes having a volume serial number beginningwith VOL.

SEL Volser VOL* D


Specify as follows to cancel the actions set in the AC fields for thevolumes having device numbers from 0F10 to 0F15.

SEL Devn 0F10:0F15 RESET

Related topics


SORT

Function

Sorts information in a displayed list.





SyntaxSORT[ field-name [{A|D}]]

The abbreviation of SORT is SO.

Parameters

If you omit the parameters, the Sort Options panelappears to allow you to

enter parameter values.field-name

Specifies the field name as a sort key.

{A|D}

Specifies the sort order.

¢ A: Ascending order

¢ D: Descending order

If you omit this parameter, items in the list will be sorted in ascendingorder. If they have already been sorted in ascending order, they will besorted in descending order.

Tip: If the list has the PoolID and SN headers and you specify PoolID forfield-name, the information will be sorted by using multiple columns, SN andPoolID. If the list has the CU and CCA headers and you specify CCA forfield-name, the information will be sorted by using multiple columns, CU andCCA.

Tip: If you execute the SORT command when the list is filtered, the unfiltered

information is sorted.

How to specify the search or filter conditions in ISPF panelsThe following describes how to specify conditions for searching for a line orfiltering in the ISPF panel.

You can specify one of the following ways to specify the search or filtercondition:

• Character string specification


Use the following syntax:

¢ character-string*: Targets all values beginning with character-string.

¢ *: Targets all lines.


Use one of the following syntaxes:

¢ minimum-value:maximum-value

Targets values in the range from minimum-value to maximum-value.





¢ minimum-value:

Targets values that are equal to or greater than minimum-value.

¢ :maximum-value

Targets values that are less than or equal to maximum-value.

Note:

• Entries are case-sensitive. However, entries are not case-sensitive in the

Find Options panel (FIND command).

• If you want to specify an asterisk as a character (not as a marker for ageneric character) at the end of the character string, specify two asteriskstogether (**).

The following table lists the panels (commands) and the specificationmethods that can be used.

Panel name (commandname)

Characterstring

specification

Generic namespecification

Range specificationcharacter-

string **

• Filter Options panel

(FILTER command#)

• Select Options panel

(SELECT command#)

Yes Yes Yes Yes

• Find Options panel (FIND

command#)

• Locate Options panel

(LOCATE command#)

Yes -- -- --

• Select Pool List panel

• Select Storage GroupList panel

• Select Volume List panel

Yes Yes -- --

Legend:

Yes: Can be specified

--: Cannot be specified

#

If you want to specify a string in the command line, specify it as follows:

¢ To specify a string that contains non-alphanumeric characters, enclose

the entire string in apostrophes (').¢ To specify a string that contains an apostrophe, specify two

apostrophes in succession ('').





C

Sample scripts

This appendix provides sample scripts for Tiered Storage Manager forMainframe.

□ List of sample scripts

□ Details about sample scripts

Sample scripts C-1




List of sample scripts

Sample scripts for each CLI command are stored in the sample library. Thefollowing table provides an overview of each sample script.

Table C-1 Overview of sample scripts

Samplescript name

PurposeCommand tobe executed

DD name specification orparameter

Relevant REXX variable structure

KTDEMO00 Create a diskconfigurationdefinition file.

KTSCAN

KTSTORE

DD name: KTINDD scan range

list #1

PREFIX( prefix )

--

KTDEMO01 Display thecontents of the diskconfigurationdefinition file.

KTGETHDA DD name: KTDSKDD disk-

configuration-definition-file

Host-discovered arrayindex structure

Host-discovered arraystructure

KTDEMO02 Create atiering policygroup

definition file.

KTIMPORT PREFIX( prefix )

POLICY( policy-ID )

--

KTDEMO03 Display thecontents of the tieringpolicy groupdefinition file.

KTLOAD DD name: KTTPGDD tiering-

policy-group-definition-file



KTDEMO04 Display thevolumeinformation.

KTQRYDEV DEVN(device-number ) Host-discovered arraystructure

Device informationstructure

KTDEMO05 Change thetiering policyof a volumeback to thedefault.

KTDCTDEV DEVN(device-number ) --

KTDEMO10 Apply thetiering policy.

KTLOAD

KTACTTPG

PREFIX( prefix )

TPG(tiering-policy-group-

ID )

--

KTDEMO11 Check thetiering policy.

KTLOAD

KTQRYTPG

PREFIX( prefix )

TPG(tiering-policy-group-

ID )



KTDEMO12 Check the

pagerelocationstatus of volumes.

KTLOAD

KTQRYTPG

PREFIX( prefix )

TPG(tiering-policy-group-ID )

Host-discovered array

structure


KTDEMO13 Check therelocationprogress.

KTLOAD

KTQRYTPG

PREFIX( prefix )


Host-discovered arrayindex structure

C-2 Sample scripts




Samplescript name

PurposeCommand tobe executed

DD name specification orparameter

Relevant REXX variable structure

KTQRYRLC Host-discovered arraystructure


KTDEMO14 Check I/O

performanceinformation.

KTLOAD

KTQSTATS

PREFIX( prefix )


INTERVAL(display-

interval)#2

Host-discovered array

structureTiering policy groupstructure

#1

Specify the values of the FROM and TO parameters, the FROMVSN and TOVSN

parameters, or the STORGRP parameter of the KTSCAN command for scan

range list . The following shows an example of a record:

DEVN 0000 00FFVOLSER VOL001 VOL009

STORGRP GRPNAME

#2

Processing is performed repeatedly at the intervals (seconds) specified forINTERVAL until the processing is canceled.

Details about sample scripts

Details about the sample scripts are provided below.

KTDEMO00 (Create a disk configuration definition file)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO00 - A sample demonstration script that *//* generates DSK configuration dataset. *//* *//* This sample script uses the following CLI commands. *//* - KTSCAN *//* - KTSTORE *//* *//* This sample script assumes the following settings. */

/* 1) Dataset which is allocated by ddname KTINDD has records *//* of scan range list of volume or sms storage group. *//* Record examples are: *//* DEVN 0000 00FF *//* VOLSER VOL001 VOL009 *//* STORGRP GRPNAME *//* 2) The definition files are stored in the dataset with the *//* prefix specified in PREFIX() option value */

Sample scripts C-3




/* in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO00.";

/** Parse argument specified in the EXEC command*/

PARSE UPPER ARG @optionsPARSE UPPER VALUE @options 'PREFIX()' with 'PREFIX('opt_prefix')';

/* Check option values. */IF opt_prefix = '' THEN DO

SAY "Please specify PREFIX() value in the argument.";EXIT 8;

END;

/** Read all records from DD(KTINDD) dataset.*/

ADDRESS TSO "EXECIO * DISKR KTINDD (FINIS STEM scan_range.";IF RC /= 0 THEN DO

SAY 'Dataset(KTINDD) read error occurred. rc='RC;EXIT 8;

END;

/** Parse each record of DD(KTINDD) dataset.*/

ScannedVolumeIsFound='N';ScanFailed='N';DO i=1 to scan_range.0;

/** Parse scan range list record.*/recordStr = SUBSTR(scan_range.i,1,72);PARSE VAR recordStr scan_type scan_from scan_to .

/** Scan volumes by DEVN or VOLSER or STORGRP range,* and add volume information* to REXX variables of the STEM() operand specified.

*/IF scan_type='DEVN' THEN DOSAY 'Executing KTSCAN DEVN= 'scan_from' - 'scan_to;CALL KTSCAN "STEM(DEMO_STEM.) MSG(DEMO_MSG.) ARRAYS(DEMO_SCAN.)",

" FROM("scan_from") TO("scan_to")";END;ELSE IF scan_type='VOLSER' THEN DOSAY 'Executing KTSCAN VOLSER= 'scan_from' - 'scan_to;CALL KTSCAN "STEM(DEMO_STEM.) MSG(DEMO_MSG.) ARRAYS(DEMO_SCAN.)",

" FROMVSN("scan_from") TOVSN("scan_to")";END;ELSE IF scan_type='STORGRP' THEN DOSAY 'Executing KTSCAN STORGRP= 'scan_from;CALL KTSCAN "STEM(DEMO_STEM.) MSG(DEMO_MSG.) ARRAYS(DEMO_SCAN.)",

" STORGRP("scan_from")";END;ELSE DOSAY 'Ignore KTINDD LINE='recordStrITERATE;

END;/** Check the return code to see if it is 0 or not.*/IF RESULT > 8 THENScanFailed='Y';

ELSE IF RESULT < 8 THEN

C-4 Sample scripts




ScannedVolumeIsFound='Y';IF RESULT > 0 THENCALL printErrorMessage "KTSCAN" RESULT;

END;

IF ScanFailed='Y' THEN DOSAY 'KTSCAN error occurred.';EXIT 8;

END;IF ScannedVolumeIsFound /='Y' THEN DOSAY 'Scanned volume is nothing.';EXIT 4;

END;

/** Store scanned volumes information to the DSK configuration dataset.**/CALL KTSTORE "STEM(DEMO_STEM.) MSG(DEMO_MSG.) ARRAYS(DEMO_SCAN.)",

" PREFIX("opt_prefix") DSK";/** Check the return code to see if it is 0 or not.*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTSTORE" RESULT;EXIT 8;

END;

SAY "#-- END KTDEMO00." /* The sample script completed. */EXIT 0;

/** printErrorMessage: This procedure prints all of the error messages* in the Message structure when a CLI command failed.*/printErrorMessage: procedure expose DEMO_MSG.ARG cli_name cli_result;SAY "Command name=" || cli_name || ",result=" || cli_result;IF DATATYPE(DEMO_MSG.0) = 'NUM' THENDO x = 1 to DEMO_MSG.0;SAY "Severity = " || DEMO_MSG.x.Severity;SAY "Text = " || DEMO_MSG.x.Text;SAY "Value = " || DEMO_MSG.x.Value;

END;RETURN 0;

KTDEMO01 (Display the contents of the disk configuration definitionfile)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* */

/* KTDEMO01 - A sample demonstration script that *//* displays information in the DSK configuration dataset. *//* *//* This sample script uses the following CLI commands. *//* - KTGETHDA *//* *//* This sample script assumes the following settings. *//* 1) DSK configuration dataset is already created. *//* 2) DSK configuration dataset is allocated to ddname KTDSKDD. */

Sample scripts C-5




/* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO01.";

/** Get dataset name of ddname KTDSKDD.*/

fc = LISTDSI("KTDSKDD" "FILE");IF fc > 4 THEN DO

SAY 'DD(KTDSKDD) is not allocated or invalid.';EXIT 8;

END;

/** Get prefix and serialNum from dataset name.*/

PARSE VAR sysdsname val_prefix'.DSK.SN'val_SN'.'val_dadid;

/** Read DSK configuration file and set pool/volume information* to REXX variables.*/

CALL KTGETHDA "STEM(DEMO_STEM.) MSG(DEMO_MSG.)"," PREFIX("val_prefix") SN("val_SN")";

/** Check the return code to see if it is 0 or not.

*/IF RESULT /= 0 THEN DO

CALL printErrorMessage "KTGETHDA" RESULT;EXIT 8;

END;

/** Display values in the DSK configuration file.*/

DO k=1 to HCC.HDAKT.0;val_SN = HCC.HDAKT.k.SerialNum;sym_SN = 'SN'||val_SN;

/* Display storage system information. */SAY '';SAY 'DKC';

SAY ' SN:' ||DEMO_STEM.LOCAL.sym_SN.SerialNum||,',Model:' ||DEMO_STEM.LOCAL.sym_SN.Model||,',Microcode:' ||DEMO_STEM.LOCAL.sym_SN.Microcode||,',IFType:' ||DEMO_STEM.LOCAL.sym_SN.IFType;

/* Find first pool from POOLMap. */val_POOLMap = VALUE("HCC.HDAKT."||k||".POOLMap");pos_POOLID = POS('1',val_POOLMap, 1);

/** Display pool values in the DSK configuration file.*/SAY '';SAY 'Pools';SAY ' ID, Type,Pool Name ,Tier1,Tier2,Tier3';DO WHILE(pos_POOLID /= 0);val_POOLID = pos_POOLID - 1;sym_POOLID = 'POOL'||D2X(val_POOLID, 2);/** Get information values about the pool* from DSK structure REXX variables.*/val_Name = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.NAME;val_Type = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Type;val_PageSize = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.PageSize;

C-6 Sample scripts




val_Media = '';TierCt = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.0;IF DATATYPE(TierCt) /= 'NUM' THENTierCt = 0;

DO t=1 to TierCt;/* Get pool's drive media information */IF val_Media = '' THENval_Media = convertMediaType(,

DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Media);ELSEval_Media = val_Media','convertMediaType(,

DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Media);END;

/* Display pool information. */SAY ' 'RIGHT(val_POOLID,3)','RIGHT(val_Type,5)||,

','LEFT(val_Name,32)','val_Media;

/* Find next pool from POOLMap. */pos_POOLID = POS('1', val_POOLMap, pos_POOLID+1);

END;

SAY '';SAY 'Volumes';SAY ' Devn,Volser,STORGRP ,CU,SSID,CCA,POOLID, Cylinders,Ext';

/* Find first cu from CUMap. */

val_CUMap = VALUE("HCC.HDAKT."||k||".CUMap");pos_CU = POS('1',val_CUMap, 1);

DO WHILE(pos_CU /= 0);hex_CU = D2X(pos_CU-1, 2);sym_CU = 'CU'||hex_CU;

/* Find first CCA from CCAMap. */val_CCAMap = VALUE("HCC.HDAKT."||k||"."||sym_CU||".CCAMAP");pos_CCA = POS('1',val_CCAMap, 1); /* Find mapped CCA. */DO WHILE(pos_CCA /= 0);hex_CCA = D2X(pos_CCA-1, 2);sym_CCA = 'CCA'||hex_CCA;

/** Get information values about the volume

* from DSK structure REXX variables.*/val_devn = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn;val_Volser = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser;val_STORGRP = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.STORGRP;val_SSID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.SSID;val_POOLID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.POOLID;val_Cyls = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Cyls;val_External = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.External;

/* Display volume information. */SAY ' 'RIGHT(val_devn,4)','LEFT(val_Volser,6)||,

','LEFT(val_STORGRP,8)||,','hex_CU','val_SSID', 'hex_CCA','RIGHT(val_POOLID,6)||,','RIGHT(val_Cyls,10)','RIGHT(val_External,3);

/* Find next CCA from CCAMap. */pos_CCA = POS('1',val_CCAMap, pos_CCA+1);

END;/* Find next CU from CUMap. */pos_CU = POS('1',val_CUMap, pos_CU+1);

END;END;

SAY "#-- END KTDEMO01."; /* The sample script completed. */EXIT 0;

Sample scripts C-7




/** printErrorMessage: This procedure prints all of the error messages* in the Message structure when a CLI command failed.*/

printErrorMessage: procedure expose DEMO_MSG.ARG cli_name cli_result;SAY "Command name=" || cli_name || ",result=" || cli_result;IF DATATYPE(DEMO_MSG.0) = 'NUM' THENDO x = 1 to DEMO_MSG.0;SAY "Severity = " || DEMO_MSG.x.Severity;SAY "Text = " || DEMO_MSG.x.Text;SAY "Value = " || DEMO_MSG.x.Value;

END;RETURN 0;

/** convertMediaType: This procedure converts from media type value* (<stem>LOCAL.SNnnnnn.POOLxx.Tier.n.Media in the DSK structure)* to media type description string.*/

convertMediaType: procedureARG mediaTypeValue;

IF mediaTypeValue = '0000' THENmediaTypeStr = 'SSD';

ELSE IF mediaTypeValue = '0001' THENmediaTypeStr = 'SAS 15K';


ELSE IF mediaTypeValue = '0003' THENmediaTypeStr = 'SATA 7.2K';

ELSE IF mediaTypeValue = '0004' THENmediaTypeStr = 'EXTERNAL M';

ELSE IF mediaTypeValue = '0005' THENmediaTypeStr = 'SAS 7.2K';

ELSE IF mediaTypeValue = '0006' THENmediaTypeStr = 'MIXED MEDIA';

ELSE IF mediaTypeValue = '0007' THENmediaTypeStr = 'EXTERNAL H';

ELSE IF mediaTypeValue = '0008' THENmediaTypeStr = 'EXTERNAL L';

ELSEmediaTypeStr = '';

mediaTypeStr = '"'mediaTypeStr'"';RETURN mediaTypeStr;

KTDEMO02 (Create a tiering policy group definition file)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO02 - A sample demonstration script that *//* generates TPG configuration dataset. */

/* *//* This sample script uses the following CLI commands. *//* - KTIMPORT *//* *//* This sample script assumes the following settings. *//* 1) DSK configuration dataset is already created. *//* 2) Tiering policy information CSV dataset is already created. *//* 3) Policy ID of tiering policy information CSV dataset is *//* specified in POLICY() option value in the script's argument. */

C-8 Sample scripts




/* 4) The CSV and DSK dataset name's prefix is PREFIX() option *//* value in the script's argument. *//* If argument is "PREFIX(KT.DEMO) POLICY(POLICY1)", *//* CSV dataset name is : KT.DEMO.POLICY.POLICY1 *//* DSK dataset name is : KT.DEMO.DSK.SNnnnnn.LOCAL *//* nnnnn is serial number *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO02.";

/** Parse argument specified in the EXEC command.*/PARSE UPPER ARG @optionsPARSE UPPER VALUE @options 'POLICY()' with 'POLICY('opt_policyid')';PARSE UPPER VALUE @options 'PREFIX()' with 'PREFIX('opt_prefix')';

/** Check option values in the argument.*/IF opt_policyid = '' THEN DOSAY "Please specify POLICY() value in the argument.";EXIT 8;

END;IF opt_prefix = '' THEN DOSAY "Please specify PREFIX() value in the argument.";

EXIT 8;END;

/** Parse tiering policy information CSV file* and create TPG configuration file(s).*/CALL KTIMPORT "MSG(DEMO_MSG.)",

" PREFIX("opt_prefix") POLICY("opt_policyid")";/** Check the return code to see if it is 0 or not.*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTIMPORT" RESULT;EXIT 8;

END;



END;RETURN 0;

Sample scripts C-9




KTDEMO03 (Display the contents of the tiering policy groupdefinition file)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO03 - A sample demonstration script that *//* displays information in the TPG configuration dataset. *//* *//* This sample script uses the following CLI commands. *//* - KTLOAD *//* *//* This sample script assumes the following settings. *//* 1) TPG configuration dataset is already created. *//* 2) TPG configuration dataset is allocated to ddname KTTPGDD. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO03.";

/** Get dataset name of ddname KTTPGDD.

*/fc = LISTDSI("KTTPGDD" "FILE");IF fc > 4 THEN DO;

SAY 'DD(KTTPGDD) is not allocated or invalid.';EXIT 8;

END;

/** Get prefix and serialNum from dataset name.*/

PARSE VAR sysdsname val_prefix'.TPG.'val_tpgid;

/** Load TPG configuration file and set information to REXX variables.*/

CALL KTLOAD "STEM(DEMO_STEM.) MSG(DEMO_MSG.)",

" PREFIX("val_prefix") TPG("val_tpgid")";/** Check the return code to see if it is 0 or not.*/

IF RESULT /= 0 THEN DOCALL printErrorMessage "KTLOAD" RESULT;EXIT 8;

END;

/** Display values in the TPG configuration file.*/

SAY 'Tiering Policy Group Name: '||DEMO_STEM.TPG.ID;SAY '';SAY 'Volumes';SAY ' Devn,Volser,STORGRP ,SN ,CU,SSID,CCA,POOLID,'||,

'TLv, Entry,Reloc, Cylinders'DO i=1 to DEMO_STEM.TPG.VOL.0;

/** Get information values about the volume* from TPG structure REXX variables.*/val_SN = DEMO_STEM.TPG.VOL.i.SerialNum;val_CU = DEMO_STEM.TPG.VOL.i.CUNum;val_CCA = DEMO_STEM.TPG.VOL.i.CCA;val_TierLevel = DEMO_STEM.TPG.VOL.i.TierLevel;

C-10 Sample scripts




val_Entry = DEMO_STEM.TPG.VOL.i.Entry;val_TierRelocation= DEMO_STEM.TPG.VOL.i.TierRelocation;

/** Generate symbol which is part of the DSK structure REXX variable* name.*/sym_SN = 'SN' ||val_SN;sym_CU = 'CU' ||val_CU;sym_CCA = 'CCA'||val_CCA;

/** Get information values about the volume* from DSK structure REXX variables.*/val_Devn = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn;val_Volser = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser;val_STORGRP= DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.STORGRP;val_SSID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.SSID;val_POOLID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.POOLID;val_Cyls = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Cyls;

/** Display volume information in the TPG.*/SAY ' 'RIGHT(val_Devn,4)','LEFT(val_Volser,6)||,

','LEFT(val_STORGRP,8)','val_SN','val_CU||,

','val_SSID', 'val_CCA','RIGHT(val_POOLID,6)||,','RIGHT(val_TierLevel,3)','RIGHT(val_Entry,6)||,','RIGHT(val_TierRelocation,5)||,','RIGHT(val_Cyls,10);

END;


/** printErrorMessage: This procedure prints all of the error messages* in the Message structure when a CLI command failed.*/printErrorMessage: procedure expose DEMO_MSG.ARG cli_name cli_result;SAY "Command name=" || cli_name || ",result=" || cli_result;

IF DATATYPE(DEMO_MSG.0) = 'NUM' THENDO x = 1 to DEMO_MSG.0;SAY "Severity = " || DEMO_MSG.x.Severity;SAY "Text = " || DEMO_MSG.x.Text;SAY "Value = " || DEMO_MSG.x.Value;

END;RETURN 0;

KTDEMO04 (Display the volume information)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. */

/* *//**********************************************************************//* *//* KTDEMO04 - A sample demonstration script that *//* displays storage information of the target volume's DKC.*//* *//* This sample script uses the following CLI commands. *//* - KTQRYDEV *//* */

Sample scripts C-11




/* This sample script assumes the following settings. *//* 1) Device number of target (want to get storage information) *//* volume is specified in the DEVN() option value *//* in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO04.";

/** Parse argument specified in the EXEC command.*/

PARSE UPPER ARG @optionsPARSE UPPER VALUE @options 'DEVN()' with 'DEVN('opt_devn')';

/** Check option values in the argument.*/

IF opt_devn = '' THEN DOSAY "Please specify DEVN() value in the argument.";EXIT 8;

END;

/** Query tiering policy to the target volume.*/

CALL KTQRYDEV "STEM(DEMO_STEM.) MSG(DEMO_MSG.) DEVN("opt_devn")";

/** Check the return code to see if it is 0 or not.*/

IF RESULT /= 0 THEN DOCALL printErrorMessage "KTQRYDEV" RESULT;EXIT 8;

END;

val_SN = DEMO_STEM.SerialNum;val_CU = DEMO_STEM.CUNum;val_CCA = DEMO_STEM.CCA;val_POOLID = DEMO_STEM.POOLID;

sym_SN = 'SN' ||val_SN;sym_CU = 'CU' ||val_CU;sym_CCA = 'CCA' ||val_CCA;

SAY 'DKC';SAY ' SN:' ||DEMO_STEM.LOCAL.sym_SN.SerialNum||,

',Model:' ||DEMO_STEM.LOCAL.sym_SN.Model||,',Microcode:' ||DEMO_STEM.LOCAL.sym_SN.Microcode||,',IFType:' ||DEMO_STEM.LOCAL.sym_SN.IFType;

IF DATATYPE(val_POOLID)='NUM' THEN DO/** Display Pool values in the volume specified in the DEVN().*/SAY '';SAY 'Pool';SAY ' ID, Type,Pool Name ,'||,

'Media(Tier1,Tier2,Tier3)';

/* Get pool information. */sym_POOLID = 'POOL'||D2X(val_POOLID,2);val_Name = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.NAME;val_Type = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Type;val_PageSize = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.PageSize;

val_Media = '';TierCt = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.0;IF DATATYPE(TierCt) /= 'NUM' THENTierCt = 0;

C-12 Sample scripts




DO t=1 to TierCt;/* Get pool's drive media information. */IF val_Media = '' THENval_Media = convertMediaType(,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Media);

ELSEval_Media = val_Media','convertMediaType(,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Media);

END;

/* Display pool information. */SAY ' 'RIGHT(val_POOLID,3)','RIGHT(val_Type,5)||,

','LEFT(val_Name,32)','val_Media;END;

SAY '';SAY 'Volume';SAY ' Devn,Volser,CU,SSID,CCA,POOLID,TLv, Entry,Reloc';

/** Get information values about the volume* from DSK structure REXX variables.*/val_Devn = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn;val_Volser = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser;val_SSID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.SSID;val_POOLID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.POOLID;

val_TierLevel = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierLevel;val_Entry = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Entry;val_TierRelocation = ,

DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierRelocation;


','val_CU','val_SSID', 'val_CCA','RIGHT(val_POOLID,6)||,','RIGHT(val_TierLevel,3)||,','RIGHT(val_Entry,6)','RIGHT(val_TierRelocation,5);



END;RETURN 0;

/** convertMediaType: This procedure converts from media type value* (<stem>LOCAL.SNnnnnn.POOLxx.Tier.n.Media in the DSK structure)* to media type description string.*/convertMediaType: procedureARG mediaTypeValue;IF mediaTypeValue = '0000' THENmediaTypeStr = 'SSD';


Sample scripts C-13










ELSE IF mediaTypeValue = '0008' THENmediaTypeStr = 'EXTERNAL L';

ELSEmediaTypeStr = '';


KTDEMO05 (Change the tiering policy of a volume back to thedefault)

/* REXX */

/**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO05 - A sample demonstration script that *//* resets tiering policy of the target volume. *//* *//* This sample script uses the following CLI commands. *//* - KTDCTDEV *//* *//* This sample script assumes the following settings. *//* 1) Device number of target (want to reset tiering policy to *//* default) volume is specified in the DEVN() option value *//* in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO05.";

/** Parse argument specified in the EXEC command.*/

PARSE UPPER ARG @optionsPARSE UPPER VALUE @options 'DEVN()' with 'DEVN('opt_devn')';

/** Check option values in the argument.*/

IF opt_devn = '' THEN DOSAY "Please specify DEVN() value in the argument.";EXIT 8;

END;

/** Reset tiering policy of the target volume.*/

CALL KTDCTDEV "MSG(DEMO_MSG.) DEVN("opt_devn")";/** Check the return code to see if it is 0 or not.*/

C-14 Sample scripts




IF RESULT /= 0 THEN DOCALL printErrorMessage "KTDCTDEV" RESULT;EXIT 8;

END;



END;RETURN 0;

KTDEMO10 (Apply the tiering policy)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO10 - A sample demonstration script that *//* sets tiering policy to volumes in the TPG. *//* *//* This sample script uses the following CLI commands. *//* - KTLOAD *//* - KTACTTPG *//* *//* This sample script assumes the following settings. */

/* 1) TPG and DSK configuration dataset is already created. *//* 2) The TPG and DSK dataset name's prefix is PREFIX() option *//* value in the script's argument. *//* 3) Tiering Policy Group ID of the TPG configuration dataset is *//* specified in TPG() option value in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO10.";

/** Parse argument specified in the EXEC command.*/PARSE UPPER ARG @optionsPARSE UPPER VALUE @options 'TPG()' with 'TPG('opt_tpgid')';PARSE UPPER VALUE @options 'PREFIX()' with 'PREFIX('opt_prefix')';

/** Check option values in the argument.*/IF opt_tpgid = '' THEN DOSAY "Please specify TPG() value in the argument.";EXIT 8;

END;IF opt_prefix = '' THEN DOSAY "Please specify PREFIX() value in the argument.";

Sample scripts C-15




EXIT 8;END;

/** Load TPG configuration file and set information to REXX variables.*/

CALL KTLOAD "STEM(DEMO_STEM.) MSG(DEMO_MSG.)"," PREFIX("opt_prefix") TPG("opt_tpgid")";

/** Check the return code to see if it is 0 or not.*/

IF RESULT /= 0 THEN DOCALL printErrorMessage "KTLOAD" RESULT;EXIT 8;

END;

/** Set tiering policy to each volume in the TPG.*/

CALL KTACTTPG "STEM(DEMO_STEM.) MSG(DEMO_MSG.)";/** Check the return code to see if it is 0 or not.*/

IF RESULT /= 0 THEN DOCALL printErrorMessage "KTACTTPG" RESULT;EXIT 8;

END;




END;RETURN 0;

KTDEMO11 (Check the tiering policy)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO11 - A sample demonstration script that *//* displays tiering policy setting values of volume */

/* in the TPG. *//* *//* This sample script uses the following CLI commands. *//* - KTLOAD *//* - KTQRYTPG *//* *//* This sample script assumes the following settings. *//* 1) TPG and DSK configuration dataset is already created. *//* 2) The TPG and DSK dataset name's prefix is PREFIX() option */

C-16 Sample scripts




/* value in the script's argument. *//* 3) Tiering Policy Group ID of the TPG configuration dataset is *//* specified in TPG() option value in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO11.";



END;IF opt_prefix = '' THEN DOSAY "Please specify PREFIX() value in the argument.";EXIT 8;

END;

/** Load TPG configuration file and set information to REXX variables.*/CALL KTLOAD "STEM(DEMO_STEM.) MSG(DEMO_MSG.)",

" PREFIX("opt_prefix") TPG("opt_tpgid")";/** Check the return code to see if it is 0 or not.*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTLOAD" RESULT;EXIT 8;

END;

/** Get tiering policy setting values of volume in the TPG and* tier status of volumes and pools in the TPG to REXX variables.

*/CALL KTQRYTPG "STEM(DEMO_STEM.) MSG(DEMO_MSG.)";/** Check the return code to see if it is 0 or not.*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTQRYTPG" RESULT;EXIT 8;

END;

/** Display values in the TPG configuration file.*/SAY 'Tiering Policy Group Name: '||DEMO_STEM.TPG.ID;SAY '';SAY 'Volumes';SAY ' Devn,Volser,STORGRP ,SN ,CU,SSID,CCA,POOLID'||,

',TLv, Entry,Reloc'DO i=1 to DEMO_STEM.TPG.VOL.0;/** Generate symbol which is part of the DSK structure REXX variable* name.*/val_SN = DEMO_STEM.TPG.VOL.i.SerialNum;val_CU = DEMO_STEM.TPG.VOL.i.CUNum;

Sample scripts C-17




val_CCA = DEMO_STEM.TPG.VOL.i.CCA;sym_SN = 'SN' ||val_SN;sym_CU = 'CU' ||val_CU;sym_CCA = 'CCA'||val_CCA;

/** Get information values about the volume* from DSK structure REXX variables.*/val_Devn = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn;val_Volser = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser;val_STORGRP = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.STORGRP;val_SSID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.SSID;val_POOLID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.POOLID;val_TierLevel = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierLevel;val_Entry = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Entry;val_TierRelocation = ,DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierRelocation;


','LEFT(val_STORGRP,8)','val_SN','val_CU||,','val_SSID', 'val_CCA','RIGHT(val_POOLID,6)||,','RIGHT(val_TierLevel,3)||,','RIGHT(val_Entry,6)','RIGHT(val_TierRelocation,5);

END;



printErrorMessage: procedure expose DEMO_MSG.ARG cli_name cli_result;SAY "Command name=" || cli_name || ",result=" || cli_result;IF DATATYPE(DEMO_MSG.0) = 'NUM' THENDO x = 1 to DEMO_MSG.0;SAY "Severity = " || DEMO_MSG.x.Severity;SAY "Text = " || DEMO_MSG.x.Text;

SAY "Value = " || DEMO_MSG.x.Value;END;RETURN 0;

KTDEMO12 (Check the page relocation status)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO12 - A sample demonstration script that */

/* displays tier status of volume and pool in the TPG. *//* *//* This sample script uses the following CLI commands. *//* - KTLOAD *//* - KTQRYTPG *//* *//* This sample script assumes the following settings. *//* 1) TPG and DSK configuration dataset is already created. *//* 2) The TPG and DSK dataset name's prefix is PREFIX() option */

C-18 Sample scripts




/* value in the script's argument. *//* 3) Tiering Policy Group ID of the TPG configuration dataset is *//* specified in TPG() option value in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO12.";NUMERIC DIGITS 10




END;



END;

/** Get tiering policy setting values of volume in the TPG and

* tier status of volumes and pools in the TPG to REXX variables.*/CALL KTQRYTPG "STEM(DEMO_STEM.) MSG(DEMO_MSG.)";/** Check the return code to see if it is 0 or not.*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTQRYTPG" RESULT;EXIT 8;

END;

SAY 'Tiering Policy Group Name: '||DEMO_STEM.TPG.ID;SAY '';

SAY 'Volumes Tier Status';SAY ' POOL';SAY ' Devn,Volser,SN ,CU,CCA, ID,TLv,Cylinders,'||,

'Tier1Page,Tier2Page,Tier3Page';DO i=1 to DEMO_STEM.TPG.VOL.0;/** Generate symbol which is part of the DSK structure REXX variable* name.*/val_SN = DEMO_STEM.TPG.VOL.i.SerialNum;val_CU = DEMO_STEM.TPG.VOL.i.CUNum;val_CCA = DEMO_STEM.TPG.VOL.i.CCA;

Sample scripts C-19




sym_SN = 'SN' ||val_SN;sym_CU = 'CU' ||val_CU;sym_CCA = 'CCA'||val_CCA;

/** Get information values about the volume* from DSK structure REXX variables.*/val_Devn = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn;val_Volser = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser;val_Cyls = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Cyls;val_POOLID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.POOLID;val_TierLevel = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierLevel;

/* Display only multi tier volume. */val_TierCt = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Tier.0;IF DATATYPE(val_TierCt) /= 'NUM' THENITERATE;

DO t=1 to val_TierCt;val_pageCt.t = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Tier.t.Used;

END;DO t=val_TierCt+1 to 3;val_pageCt.t = 0;

END;

/*

* Display volume's tier information in the TPG.*/SAY ' 'RIGHT(val_Devn,4)','LEFT(val_Volser,6)||,

','val_SN','val_CU', 'val_CCA','RIGHT(val_POOLID,3)||,','RIGHT(val_TierLevel,3)||,','RIGHT( val_Cyls,10)||,','RIGHT(val_pageCt.1,10)||,','RIGHT(val_pageCt.2,10)||,','RIGHT(val_pageCt.3,10);

END;


/** printErrorMessage: This procedure prints all of the error messages

* in the Message structure when a CLI command failed.*/printErrorMessage: procedure expose DEMO_MSG.

ARG cli_name cli_result;SAY "Command name=" || cli_name || ",result=" || cli_result;IF DATATYPE(DEMO_MSG.0) = 'NUM' THENDO x = 1 to DEMO_MSG.0;SAY "Severity = " || DEMO_MSG.x.Severity;SAY "Text = " || DEMO_MSG.x.Text;SAY "Value = " || DEMO_MSG.x.Value;

END;RETURN 0;

KTDEMO13 (Check the relocation progress)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. *//* *//**********************************************************************//* *//* KTDEMO13 - A sample demonstration script that */

C-20 Sample scripts




/* displays tier page placement status and *//* relocate progress in the TPG. *//* *//* This sample script uses the following CLI commands. *//* - KTLOAD *//* - KTQRYTPG *//* - KTQRYRLC *//* *//* This sample script assumes the following settings. *//* 1) TPG and DSK configuration dataset is already created. *//* 2) The TPG and DSK dataset name's prefix is PREFIX() option *//* value in the script's argument. *//* 3) Tiering Policy Group ID of the TPG configuration dataset is *//* specified in TPG() option value in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO13.";NUMERIC DIGITS 11 /* Some rexx value exceed 9digits. */




END;



END;

/** Get tiering policy setting values of volume in the TPG and* tier status of volumes and pools in the TPG.*/CALL KTQRYTPG "STEM(DEMO_STEM.) MSG(DEMO_MSG.)";/** Check the return code to see if it is 0 or not.*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTQRYTPG" RESULT;EXIT 8;

END;/** Get volume/pool relocation progress status in the TPG.*/CALL KTQRYRLC "STEM(DEMO_STEM.) MSG(DEMO_MSG.)";/*

Sample scripts C-21




* Check the return code to see if it is 0 or not.*/

IF RESULT /= 0 THEN DOCALL printErrorMessage "KTQRYRLC" RESULT;EXIT 8;

END;

/** Display relocation progress status per volume.*/

SAY 'Tiering Policy Group Name: '||DEMO_STEM.TPG.ID;SAY '';

SAY 'Volumes';SAY ' POOL';SAY ' Devn,Volser,SN ,CU,CCA, ID,TLv,'||,

'RelocateStatus ,LocatedPage/ TotalPage';DO i=1 to DEMO_STEM.TPG.VOL.0;

/** Generate symbol which is part of the DSK structure REXX variable* name.*/val_SN = DEMO_STEM.TPG.VOL.i.SerialNum;val_CU = DEMO_STEM.TPG.VOL.i.CUNum;val_CCA = DEMO_STEM.TPG.VOL.i.CCA;sym_SN = 'SN' ||val_SN;sym_CU = 'CU' ||val_CU;

sym_CCA = 'CCA'||val_CCA;

/** Get information values about the volume* from DSK structure REXX variables.*/val_Devn = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn;val_Volser = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser;val_POOLID = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.POOLID;val_TLv = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierLevel;val_pageCt = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Used;

volTierCt = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Tier.0;IF (volTierCt /=2)&(volTierCt /=3) THEN DOSAY ' 'RIGHT(val_Devn,4)','LEFT(val_Volser,6)||,

','val_SN','val_CU', 'val_CCA||,

','RIGHT(val_POOLID,3)','RIGHT(val_TLv,3);ITERATE;END;

sym_POOLID = 'POOL'||D2X(val_POOLID, 2);val_RelocatePerCent = ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.RelocatePerCent;

poolTierCt = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.0;IF DATATYPE(poolTierCt) /= 'NUM' THENpoolTierCt = 0;

/* TierLevel TierRange MultiTier* 3Tier 2Tier 3Tier 2Tier* 0 1/2/3 1/2 Y Y* 1 1 1 N N* 2 1/2 1/2 Y Y* 3 2 1/2 N Y* 4 2/3 1/2 Y Y* 5 3 2 N N*/TierRange.1 = '';TierRange.2 = '';TierRange.3 = '';MultiTier = 'Y';IF volTierCt=3 THEN DO /* 3tier? */IF val_TLv/=3 & val_TLv/=4 & val_TLv/=5 THEN

C-22 Sample scripts




TierRange.1 = 'Y';IF val_TLv/=1 & val_TLv/=5 THENTierRange.2 = 'Y';

IF val_TLv/=1 & val_TLv/=2 & val_TLv/=3 THENTierRange.3 = 'Y';

IF val_TLv=1 | val_TLv=3 | val_TLv=5 THENMultiTier = 'N';

END;ELSE IF volTierCt=2 THEN DO /* 2tier? */IF val_TLv /= 5 THENTierRange.1 = 'Y';

IF val_TLv /= 1 THENTierRange.2 = 'Y';

IF val_TLv=1 | val_TLv=5 THENMultiTier = 'N';

END;

/** Calculate page in the tier range for relocate status recognition.*/TierRangePageCt = 0;DO t=1 to volTierCt;IF TierRange.t = 'Y' THEN DOTierRangePageCt = TierRangePageCt ,+ DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Tier.t.Used;

END;END;

/** Calculate capacity and used in the tier range.*/TierRangeCapacity = 0; /* total page count */TierRangeUsed = 0; /* used pages count */TierRangeReserved = 0; /* reserved page count for new & reallocate */DO t=1 to poolTierCt;IF TierRange.t = 'Y' THEN DOReservedPerCent = 0;IF DATATYPE(,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.EntryBufferPerCent,) = 'NUM' THEN DO;ReservedPerCent = ReservedPerCent + ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.EntryBufferPerCent;

END;

IF DATATYPE(,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.RelocateBufferPerCent,) = 'NUM' THEN DO;ReservedPerCent = ReservedPerCent + ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.RelocateBufferPerCent;

END;TierRangeReserved = TierRangeReserved + TRUNC(,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Capacity,* ReservedPerCent/100);

TierRangeCapacity = TierRangeCapacity ,+ DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Capacity;

TierRangeUsed = TierRangeUsed ,+ DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Used;

END;END;

/** Identify relocate status as shown below.* ALL: Y=All pages are in the expected Tier(s) of the range* capacity: expected Tier(s) capacity* Relocate%: Pool's RelocatePerCent** ALL Capacity Relocate% MultiTier relocateStatus* Y any any N -> done* Y any 100 Y -> done* Y any >100 Y -> done or relocating

Sample scripts C-23




* N full any any -> capacity shortage* N not full 100 any -> relocate waiting* N not full >100 any -> relocating*/IF TierRangePageCt = val_pageCt THEN DO/* All pages are in the tier. */IF MultiTier ='N' THEN /* Tier level is not multi tier? */relocateStatus = 'done ';

ELSE IF val_RelocatePerCent = 100 THENrelocateStatus = 'done ';

ELSErelocateStatus = 'done or relocating';

END;ELSE DO;IF TierRangeUsed >= TierRangeCapacity - TierRangeReserved THENrelocateStatus = 'capacity shortage ';

ELSE IF val_RelocatePerCent = 100 THENrelocateStatus = 'relocate waiting ';

ELSErelocateStatus = 'relocating ';

END;

SAY ' 'RIGHT(val_Devn,4)','LEFT(val_Volser,6)||,','val_SN','val_CU', 'val_CCA||,','RIGHT(val_POOLID,3)','RIGHT(val_TLv,3)||,','relocateStatus','RIGHT(TierRangePageCt,11)||,'/'RIGHT(val_pageCt,10);

END;

/** Display pool information.*/

SAY '';SAY 'Pools';SAY ' Relocate'||,

' RelocateTime MigrationPage';SAY ' SN , ID, Type,Monitor,active %,'||,

'Start, End,ExpectedCt,MigratedCt';DO k=1 to HCC.HDAKT.0;

val_SN = HCC.HDAKT.k.SerialNum;sym_SN = 'SN'||val_SN;

val_POOLMap = VALUE("HCC.HDAKT."||k||".POOLMap");

pos_POOLID = POS('1',val_POOLMap, 1);

DO WHILE(pos_POOLID /= 0);val_POOLID = pos_POOLID - 1;sym_POOLID = 'POOL'||D2X(val_POOLID, 2);

/** Get information values about the pool* from DSK structure REXX variables.*/val_Type = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Type;IF val_Type='DT' THEN DO;val_Auto = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Auto;val_RelocatePerCent = ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.RelocatePerCent;

val_RelocateStartTime = ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.RelocateStartTime;

val_RelocateEndTime = ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.RelocateEndTime;

val_Relocating = ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Relocating;

val_MigratedPageCt = ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.MigratedPageCt;

val_ExpectedMigrationPageCt = ,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.ExpectedMigrationPageCt;

C-24 Sample scripts




IF val_Auto = 'Y' THENmonitorMode = 'auto';

ELSEmonitorMode = 'manual';

/** Display pool tier information.*/

SAY ' 'val_SN','RIGHT(val_POOLID,3)','RIGHT(val_Type,5)||,','RIGHT(monitorMode,7)||,','val_Relocating' 'RIGHT(val_RelocatePerCent,3)'%'||,','RIGHT(val_RelocateStartTime,5)||,','RIGHT(val_RelocateEndTime,5)||,','RIGHT(val_ExpectedMigrationPageCt,10)||,','RIGHT(val_MigratedPageCt,10);

END;


END;END;

/** Display relocation progress status per tier of the pool.*/SAY '';SAY 'Pools tier status';

SAY ' SN , ID,Tier, Used/ Capacity,EntryBuf%,RelocBuf%,Media';DO k=1 to HCC.HDAKT.0;val_SN = HCC.HDAKT.k.SerialNum;sym_SN = 'SN'||val_SN;

val_POOLMap = VALUE("HCC.HDAKT."||k||".POOLMap");pos_POOLID = POS('1',val_POOLMap, 1);

DO WHILE(pos_POOLID /= 0);val_POOLID = pos_POOLID - 1;sym_POOLID = 'POOL'||D2X(val_POOLID, 2);

/* get pool's tier information */poolTierCt = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.0;IF DATATYPE(poolTierCt) /= 'NUM' THEN DO;pos_POOLID = POS('1', val_POOLMap, pos_POOLID+1);

ITERATE;END;

DO t=1 to poolTierCt;val_Capacity = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Capacity;val_Used = DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Used;val_EntryBufferPerCent =,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.EntryBufferPerCent;

val_RelocateBufferPerCent =,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.RelocateBufferPerCent;

val_Media = convertMediaType(,DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.Media);

/** Display pool's tier information.*/

SAY ' 'val_SN','RIGHT(val_POOLID,3)', 't||,','RIGHT(val_Used,10)'/'RIGHT(val_Capacity,10)||,','RIGHT(val_EntryBufferPerCent,8)||,'%,'RIGHT(val_RelocateBufferPerCent,8)'%,'val_Media;

END;


END;END;

Sample scripts C-25







END;RETURN 0;

/** convertMediaType: This procedure converts from media type value* (<stem>LOCAL.SNnnnnn.POOLxx.Tier.n.Media in the DSK structure)* to media type description string.*/

convertMediaType: procedureARG mediaTypeValue;

IF mediaTypeValue = '0000' THEN

mediaTypeStr = 'SSD';ELSE IF mediaTypeValue = '0001' THENmediaTypeStr = 'SAS 15K';







ELSE IF mediaTypeValue = '0008' THEN

mediaTypeStr = 'EXTERNAL L';ELSEmediaTypeStr = '';


KTDEMO14 (Check I/O performance information)

/* REXX *//**********************************************************************//* *//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd. *//* */

/**********************************************************************//* *//* KTDEMO14 - A sample demonstration script that *//* displays volume I/O statistics. *//* *//* This sample script uses the following CLI commands. *//* - KTLOAD *//* - KTQSTATS *//* */

C-26 Sample scripts




/* This sample script assumes the following settings. *//* 1) TPG and DSK configuration dataset is already created. *//* 2) The TPG and DSK dataset name's prefix is PREFIX() option *//* value in the script's argument. *//* 3) Tiering Policy Group ID of the TPG configuration dataset is *//* specified in TPG() option value in the script's argument. *//* 4) KTQSTATS command interval time is specified in the *//* INTERVAL() option value in the script's argument. *//* *//**********************************************************************//* Sample script begins. */SAY "#-- BEGIN KTDEMO14.";NUMERIC DIGITS 10 /* Some rexx value exceed 9digits. */

/** Parse argument specified in the EXEC command.*/PARSE UPPER ARG @optionsPARSE UPPER VALUE @options 'TPG()' with 'TPG('opt_tpgid')';PARSE UPPER VALUE @options 'PREFIX()' with 'PREFIX('opt_prefix')';PARSE UPPER VALUE @options 'INTERVAL()' with 'INTERVAL('opt_interval')';

/** Check option values in the argument.*/IF opt_tpgid = '' THEN DOSAY "Please specify TPG() value in the argument.";

EXIT 8;END;IF opt_prefix = '' THEN DOSAY "Please specify PREFIX() value in the argument.";EXIT 8;

END;IF DATATYPE(opt_interval) /= 'NUM' THENopt_interval = 600;


" PREFIX("opt_prefix") TPG("opt_tpgid")";/** Check the return code to see if it is 0 or not.

*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTLOAD" RESULT;EXIT 8;

END;

/** Display header information.*/SAY 'Tiering Policy Group Name : '||DEMO_STEM.TPG.ID;SAY 'Monitor Interval Time(sec): '||opt_interval;SAY '';SAY 'Volume I/O statistics';

/** Get I/O statistics each interval time,* and display I/O statistics values of all volumes in the TPG.*/getmsgrc = 0;EndTime=TIME();DO WHILE getmsgrc=0;/** Get tiering policy setting values of volume in the TPG and* tier status of volumes and pools in the TPG to REXX variables.*/CALL KTQSTATS "STEM(DEMO_STEM.) MSG(DEMO_MSG.)";

Sample scripts C-27




/** Check the return code to see if it is 0 or not.*/IF RESULT /= 0 THEN DOCALL printErrorMessage "KTQSTATS" RESULT;EXIT 8;

END;

IF DEMO_STEM.TPG.VOL.IO.Interval > 0 THEN DO;StartTime = EndTime;EndTime = TIME();SAY ' -------------------------------------------------------';SAY ' 'StartTime' - 'EndTime;SAY ' -------------------------------------------------------';SAY ' Devn,Volser,STORGRP ,SN ,CU,CCA'||,

',Tier1 IOPS,Tier2 IOPS,Tier3 IOPS';

DO i=1 to DEMO_STEM.TPG.VOL.0;val_SN = DEMO_STEM.TPG.VOL.i.SerialNum;val_CU = DEMO_STEM.TPG.VOL.i.CUNum;val_CCA = DEMO_STEM.TPG.VOL.i.CCA;sym_SN = 'SN' ||val_SN;sym_CU = 'CU' ||val_CU;sym_CCA = 'CCA'||val_CCA;

val_Devn = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn;

val_Volser = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser;val_STORGRP = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.STORGRP;

/** If KTQSTATS is not first call,* IO.diff has I/O count from last call.*/

DO j=1 to 3;val_iops.j=0;

END;DO j=1 to DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Tier.0;val_iops.j=DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Tier.j.IO.diff,

/DEMO_STEM.TPG.VOL.IO.Interval;IF TRUNC(val_iops.j) /= val_iops.j THEN DO;IF val_iops.j < 100 THENval_iops.j = TRUNC(val_iops.j,3);

ELSEval_iops.j = TRUNC(val_iops.j,0);END;

END;

/** Display this volume's I/O statistics.*/

SAY ' 'RIGHT(val_Devn,4)','LEFT(val_Volser,6)||,','LEFT(val_STORGRP,8)','val_SN','val_CU||,', 'val_CCA||','RIGHT(val_iops.1,10)||,','RIGHT(val_iops.2,10)','RIGHT(val_iops.3,10);

END;END;

/** Wait for interval.*/ADDRESS TSO "KTSLEEP SEC("opt_interval")";

END;


/** printErrorMessage: This procedure prints all of the error messages

C-28 Sample scripts




* in the Message structure when a CLI command failed.*/printErrorMessage: procedure expose DEMO_MSG.ARG cli_name cli_result;SAY "Command name=" || cli_name || ",result=" || cli_result;IF DATATYPE(DEMO_MSG.0) = 'NUM' THENDO x = 1 to DEMO_MSG.0;SAY "Severity = " || DEMO_MSG.x.Severity;SAY "Text = " || DEMO_MSG.x.Text;SAY "Value = " || DEMO_MSG.x.Value;

END;RETURN

0;

Sample scripts C-29




C-30 Sample scripts




D

Upgrading Tiered Storage Manager forMainframe

This appendix describes how to upgrade Tiered Storage Manager forMainframe.

□ Workflow for upgrading Tiered Storage Manager for Mainframe

□ Preparation for upgrading Tiered Storage Manager for Mainframe

□ Upgrading Tiered Storage Manager for Mainframe

Upgrading Tiered Storage Manager for Mainframe D-1




Workflow for upgrading Tiered Storage Manager forMainframe

The following figure shows the Workflow for upgrading Tiered StorageManager for Mainframe.

Figure D-1 Workflow for upgrading

#

You do not need to delete and register a user SVC if the currently enabled

user SVC version satisfies the conditions for the user SVC that areprerequisites for Tiered Storage Manager for Mainframe after upgrading.

Related topics

• Checking the setting values of the operating environment on page D-3

• Creating a backup on page D-3

• Deleting the user SVC by using the KTALCSVC environment setupcommand on page D-4

• Deleting the user SVC from the IEASVCxx parmlib member on pageD-4

• Removing the library linkage on page D-5

• Upgrading Tiered Storage Manager for Mainframe on page D-6

D-2 Upgrading Tiered Storage Manager for Mainframe




Preparation for upgrading Tiered Storage Manager forMainframe

The following describes the tasks that must be performed before upgradingTiered Storage Manager for Mainframe.

Checking the setting values of the operating environment

Check the setting values of the operating environment that will be used foran installation of the new version.

Procedure

1. Execute the KTDSPENV command as shown below:


The values set for the environment variables and system symbolic nameslisted in the following table are displayed.

Table D-1 Setting values of the operating environment to be checked

before upgrading

Environment variable System symbolic names Description

YKLCNSE &YKLCNSE Prefix of a license informationdataset

YKLCNS2 &YKLCNS2

LOGPUT &YKLOGPT Event log output mode

SYSLOG &YKSYSLG Whether to output the log data of CLI command execution toSYSLOG or the console

Related topics


Creating a backup

Back up the following files:

• Tiering policy group definition file

File name: prefix .TPG.tiering-policy-group-ID

• Disk configuration definition file

File name: prefix .DSK.SNnnnnn.LOCAL• Tiering policy information CSV file

File name: prefix .POLICY. policy-ID

• Library dataset registered when the current version of Tiered StorageManager for Mainframe was installed





Tip: When you back up and rename files, make sure that you change onlythe prefix of the file names. Because a file name contains information such astiering policy group IDs, changing a file name might cause file consistenciesto be lost, preventing Tiered Storage Manager for Mainframe from operating.

Related topics

• Library datasets to be registered after the installation on page 2-10

Deleting the user SVC by using the KTALCSVC environment setupcommand

You must delete a user SVC before upgrading and assign the same SVCnumber after upgrading if the currently enabled user SVC version is olderthan the prerequisite user SVC version of Tiered Storage Manager forMainframe after upgrading.

If a dynamic user SVC has been registered by using the KTALCSVC

environment setup command, use the KTALCSVC command to delete the user

SVC.

Procedure

1. Execute the KTINSCHK command to confirm the currently enabled user

SVC version.

2. If this version is older than the prerequisite user SVC version of TieredStorage Manager for Mainframe after upgrading, execute the KTALCSVC

command as shown below.

START KTALCSVC,PARM='DELETE'

Caution: A user SVC is shared by Tiered Storage Manager for Mainframe and

Business Continuity Manager. Therefore, in a system where BusinessContinuity Manager is installed, make sure that Business Continuity Manageris not running before deleting the user SVC.

Related topics



• KTALCSVC on page 6-42

Deleting the user SVC from the IEASVCxx parmlib memberYou must delete the user SVC before upgrading, and then re-assign the sameSVC number after version updating if the currently enabled user SVC versionis older than the prerequisite user SVC version of Tiered Storage Manager forMainframe after version updating. If the static user SVC has been registered





by using the IEASVCxx parmlib member, delete the user SVC from the

IEASVCxx parmlib member.

Procedure

1. Execute the KTINSCHK command to confirm the currently enabled user

SVC version.

2. If this version is older than the prerequisite user SVC version of Tiered

Storage Manager for Mainframe after upgrading, disable (comment out)the SYMDEF statement that contains the &YKSVCNO system symbolic name

in the IEASYMxx parmlib member, as shown below:

/* SYMDEF(&YKSVCNO='SVC-number ') */

3. Disable (comment out) the SVCPARM statement that specifies the JYUASVC

module of the IEASVCxx parmlib member, as shown below:

/* SVCPARM SVC-number ,REPLACE,TYPE(3),EPNAME(JYUASVC),APF(NO),NPRMPT(NO),AR(NO) */

To apply the deletion of the user SVC, perform re-IPL by specifying the CLPA

parameter. Perform re-IPL at the end of the preparation for upgrading.

Caution: A user SVC is shared by Tiered Storage Manager for Mainframe andBusiness Continuity Manager. Therefore, in a system where BusinessContinuity Manager is installed, make sure that Business Continuity Manageris not running before deleting the user SVC.

Related topics



Removing the library linkage

Remove all the links to libraries that were established during setup.

Procedure

1. Remove the linkage of the HDSYPRCT cataloged procedure library.

¢ If the cataloged procedure library has been statically linked to theIEFPDSI DD name in the MSTJCLxx parmlib member, remove the

linkage.

¢ If the KTALCSVC, KTSETENV, and KTDSPENV members have been copied

from the cataloged procedure library to the user's PROCLIB, deletethose members.

2. Remove the linkage of the HDSYLNKT load library for LINKLIB.





¢ If the load library for LINKLIB has been statically linked by adding it tothe PROGxx parmlib member, delete the load library from the member.

¢ If the load library for LINKLIB has been dynamically linked to LNKLST

by using the SETPROG LNKLST command, use the SETPROG LNKLST

command to remove the linkage.

3. If the user SVC has been registered by using the IEASVCxx parmlib

member, remove the linkage of the HDSYLPAT load library for LPALIB.

(This step is unnecessary if the user SVC was registered by using theYKALCSVC command.)

¢ If the load library for LPALIB has been statically linked by defining it inthe LPALSTxx parmlib member, delete the definition.

¢ If the load library for LPALIB has been dynamically linked to LPALSTby using the SETPROG LPA command, use the SETPROG LPA command

to remove the linkage.

To apply the removal of static linkages, you must perform re-IPL specifyingthe CLPA parameter. Perform re-IPL at the end of the preparation for

upgrading.

Upgrading Tiered Storage Manager for Mainframe

The procedure for upgrading Tiered Storage Manager for Mainframe is thesame as for a new installation except the following.

When upgrading Tiered Storage Manager for Mainframe:

• You do not need to register a user SVC if the currently enabled user SVCversion satisfies the conditions for the user SVC that are prerequisites forTiered Storage Manager for Mainframe.

• If the license of the version before migration can be used and there are

no licenses to be added, you do not need to register a license for TieredStorage Manager for Mainframe.

Note:

• If a task requiring re-IPL was performed during preparation for upgrading,always perform re-IPL before starting the procedure for upgrading.

• If sample JCL HDSKT2DF, which defines the distribution library and target

library, terminated abnormally during installation using SMP/E andGIM35601E ** DATASET SUBENTRY WAS NOT ADDED BECAUSE IT ALREADY

EXISTS. was output, change the ADD command in HDSKT2DF to the REP

command, and then execute HDSKT2DF again.

Related topics

• Chapter 2, Installation and setup on page 2-1





E

Modifying the sample JCL

This appendix provides examples of how to modify the sample JCL.

□ Values used in the sample JCL modification examples

□ ALLOUPLD (creating datasets used for transfers)

□ RECVUPLD (TSO/E RECEIVE processing)

□ HDSKTSIN (performing installation without using SMP/E)

□ SMPALLOC (allocating SMP/E datasets)

□ HDSKT1AL (allocating the distribution library and target library)

□ HDSKT2DF (defining the distribution library and target library)

□ HDSKT3RC (SMP/E RECEIVE processing)

□ HDSKT4AP (creating target libraries)

□ HDSKT5AC (creating distribution libraries)

Modifying the sample JCL E-1




Values used in the sample JCL modification examples

Prefixes for the dataset names and volumes allocated to the datasets used inthe sample JCL modification examples are shown in the following table.

Dataset use Prefix for dataset name Volume allocated

to the dataset

Dataset used for transfers TSO/E user ID TSOW00

For TSO/E RECEIVE TSO/E user ID TSOW00

SMP/E dataset HTC1.KT. SMP001

Target library HTC1.KT. KTT000

Distribution library HTC1.KT. KTD000

Global zone

(SMPTLIB)

HTC1.KT. SMP001

In the sample JCL, the nnn part of CHKTnnn and the nnnnnn part of Vnnnnnn

vary depending on the version.

ALLOUPLD (creating datasets used for transfers)

The method for modifying ALLOUPLD, which creates datasets used for

transfers, is described below.

The following numbers correspond to the numbers appearing on the right sideof the sample JCL.

(1) to (3)

Modify the JOB statement in accordance with the installationenvironment.

(4) to (14)

Change the prefix for the name of the dataset transfer destination fromHITACHI to the TSO/E user ID.

(15)

Change VOLSER from #tso01 to TSOW00.

//ALLOUPLD JOB (ACCT#),'ALLO UPLD FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL allocates data sets in preparation for storing//* the data files for installation of HTSM for MF from the//* distribution CD.//*//* Instructions:

E-2 Modifying the sample JCL




//* 1. Change ' HITACHI' to the current USERID.//* 2. Change '#tso01' to VOLSER of your device.//* 3. Submit this JCL to allocate the data sets for storing//* the data files.//* 4. Transfer the unzipped .XMIT files to the allocated data sets//* via FTP in "BINARY" mode.//* 5. See RECVUPLD for further procedures.//*//*//* Remove all HTSM for MF files.//*//CLEAN EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD * DELETE HITACHI.CHKTnnn.SMPMCS.XMIT -----(4) DELETE HITACHI.CHKTnnn.F1.XMIT -----(5) DELETE HITACHI.CHKTnnn.F2.XMIT -----(6) DELETE HITACHI.CHKTnnn.F3.XMIT -----(7) DELETE HITACHI.CHKTnnn.F4.XMIT -----(8) DELETE HITACHI.CHKTnnn.F5.XMIT -----(9) DELETE HITACHI.CHKTnnn.F6.XMIT -----(10) DELETE HITACHI.CHKTnnn.F7.XMIT -----(11) DELETE HITACHI.CHKTnnn.F8.XMIT -----(12) DELETE HITACHI.CHKTnnn.F9.XMIT -----(13) SET MAXCC = 0/*//*

//* Allocate the data sets for storing the data files.//*//* Value Description//* -------- --------------------------------// SET PFX=HITACHI Data set prefix -----(14)// SET VRM=CHKTnnn Version of HTSM For MF// SET VSN=#tso01 VOLSER -----(15)//*//BR14 EXEC PGM=IEFBR14//SMPMCS DD DSN=&PFX..&VRM..SMPMCS.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F1 DD DSN=&PFX..&VRM..F1.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,

// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F2 DD DSN=&PFX..&VRM..F2.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(60)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F3 DD DSN=&PFX..&VRM..F3.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F4 DD DSN=&PFX..&VRM..F4.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(15)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F5 DD DSN=&PFX..&VRM..F5.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F6 DD DSN=&PFX..&VRM..F6.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),





// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F7 DD DSN=&PFX..&VRM..F7.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F8 DD DSN=&PFX..&VRM..F8.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)//F9 DD DSN=&PFX..&VRM..F9.XMIT,// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(TRK,(45)),// DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120),// DISP=(,CATLG,DELETE)

RECVUPLD (TSO/E RECEIVE processing)

The changes in RECVUPLD, which performs TSO/E RECEIVE processing, are

explained below.


(1) to (3)


(4) to (14), (16), (18), (20), (22), (24), (26), (28), (30), and (32)

Change the prefix for the dataset name from HITACHI to the TSO/E user

ID.

(15), (17), (19), (21), (23), (25), (27), (29), (31), and (33)

Change VOLSER from #tso01 to TSOW00.

//RECVUPLD JOB (ACCT#),'TSO RECEIVE', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JOB uses TSO RECEIVE command to receive the data sets//* that were allocated by ALLOUPLD JCL and contain the unzipped//* .XMIT files that were uploaded via binary FTP transfer.//*

//* Instructions://* 1. Logon with the same USERID used for ALLOUPLD job.//* 2. Change 'HITACHI.' prefixes to suit your naming convention.//* 3. Change '#tso01' to VOLSER of your device.//* 4. Submit this JCL.//* 5. See this product's documentation for SMP/E instructions.//* Modify the .SMPMCS file so that the chosen file prefix//* is indicated in the RFDSNPFX() parameter of the//* FUNCTION() statement.//* Allocate the .SMPMCS file directly to the SMP/E





//* SMPPTFIN DD statement on the receive step. SMP/E will//* locate the other files via the catalog.//*//*//* Remove all HTSM for MF files.//*//CLEAN EXEC PGM=IDCAMS//SYSPRINT DD SYSOUT=*//SYSIN DD * DELETE HITACHI.CHKTnnn.SMPMCS -----(4) DELETE HITACHI.CHKTnnn.F1 -----(5) DELETE HITACHI.CHKTnnn.F2 -----(6) DELETE HITACHI.CHKTnnn.F3 -----(7) DELETE HITACHI.CHKTnnn.F4 -----(8) DELETE HITACHI.CHKTnnn.F5 -----(9) DELETE HITACHI.CHKTnnn.F6 -----(10) DELETE HITACHI.CHKTnnn.F7 -----(11) DELETE HITACHI.CHKTnnn.F8 -----(12) DELETE HITACHI.CHKTnnn.F9 -----(13) SET MAXCC = 0/*//*********************************************************************//* TSO receive to restore portable PDS from BINARY FTP//*********************************************************************//S1 EXEC PGM=IKJEFT01//SYSTSPRT DD SYSOUT=*//SYSTSIN DD *

RECEIVE INDSN(CHKTnnn.SMPMCS.XMIT) DSNAME('HITACHI.CHKTnnn.SMPMCS') + -----(14) VOLUME(#tso01) -----(15) RECEIVE INDSN(CHKTnnn.F1.XMIT) DSNAME('HITACHI.CHKTnnn.F1') + -----(16) VOLUME(#tso01) -----(17) RECEIVE INDSN(CHKTnnn.F2.XMIT) DSNAME('HITACHI.CHKTnnn.F2') + -----(18) VOLUME(#tso01) -----(19) RECEIVE INDSN(CHKTnnn.F3.XMIT) DSNAME('HITACHI.CHKTnnn.F3') + -----(20) VOLUME(#tso01) -----(21) RECEIVE INDSN(CHKTnnn.F4.XMIT) DSNAME('HITACHI.CHKTnnn.F4') + -----(22) VOLUME(#tso01) -----(23) RECEIVE INDSN(CHKTnnn.F5.XMIT)

DSNAME('HITACHI.CHKTnnn.F5') + -----(24) VOLUME(#tso01) -----(25) RECEIVE INDSN(CHKTnnn.F6.XMIT) DSNAME('HITACHI.CHKTnnn.F6') + -----(26) VOLUME(#tso01) -----(27) RECEIVE INDSN(CHKTnnn.F7.XMIT) DSNAME('HITACHI.CHKTnnn.F7') + -----(28) VOLUME(#tso01) -----(29) RECEIVE INDSN(CHKTnnn.F8.XMIT) DSNAME('HITACHI.CHKTnnn.F8') + -----(30) VOLUME(#tso01) -----(31) RECEIVE INDSN(CHKTnnn.F9.XMIT) DSNAME('HITACHI.CHKTnnn.F9') + -----(32) VOLUME(#tso01) -----(33)END/*

HDSKTSIN (performing installation without using SMP/E)

The method for modifying HDSKTSIN, which performs installation without

using SMP/E, is explained below.






(1) to (3)


(4)

Change the prefix for the input dataset name from HITACHI to the TSO/E

user ID.

(5)

Change the prefix for the target library name from HITACHI to HTC1.KT.

(6)

Change the volume allocated to the target library from #KT001 to KTT000.

//HDSKTSIN JOB (ACCT#),'SAMPLE COPY', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* JCL template for simplified installation of HTSM for MF.//*//* This sample shows an installation method that copies//* distribution data sets directly to the target libraries,//* without using SMP/E.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- ----------------------------------

// SET IPFX=HITACHI Prefix of distribution data sets -----(4)// SET IVRM=CHKTnnn Version of distribution data sets// SET TPFX=HITACHI Prefix of target libraries -----(5)// SET TVRM=Vnnnnnn Version of target libraries// SET TVSN=#KT001 VOLSER of target libraries -----(6)//*//* 3) Submit the JCL.//*//*********************************************************************//COPY EXEC PGM=IEBCOPY//SYSPRINT DD SYSOUT=*//* Input data sets//INF1 DD DSN=&IPFX..&IVRM..F1,DISP=SHR SAMPLIB data set//INF2 DD DSN=&IPFX..&IVRM..F2,DISP=SHR LINKLIB data set//INF3 DD DSN=&IPFX..&IVRM..F3,DISP=SHR LPALIB data set//INF4 DD DSN=&IPFX..&IVRM..F4,DISP=SHR PROCLIB data set

//INF5 DD DSN=&IPFX..&IVRM..F5,DISP=SHR EXEC(F) data set//INF6 DD DSN=&IPFX..&IVRM..F6,DISP=SHR EXEC(V) data set//INF7 DD DSN=&IPFX..&IVRM..F7,DISP=SHR PANEL data set//INF8 DD DSN=&IPFX..&IVRM..F8,DISP=SHR MESSAGE data set//INF9 DD DSN=&IPFX..&IVRM..F9,DISP=SHR TABLE data set//* Output libraries//OUTF1 DD DSN=&TPFX..&TVRM..HDSKSAMT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), SAMPLIB// SPACE=(TRK,(15,1,5)),DCB=*.INF1 Target library





//OUTF2 DD DSN=&TPFX..&TVRM..HDSKLNKT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), LINKLIB// SPACE=(TRK,(75,1,20)),DCB=*.INF2 Target library//OUTF3 DD DSN=&TPFX..&TVRM..HDSKLPAT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), LPALIB// SPACE=(TRK,(1,1,1)),DCB=*.INF3 Target library//OUTF4 DD DSN=&TPFX..&TVRM..HDSKPRCT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), PROCLIB// SPACE=(TRK,(5,1,10)),DCB=*.INF4 Target library//OUTF5 DD DSN=&TPFX..&TVRM..HDSKEXET,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), EXECLIB(F)// SPACE=(TRK,(45,1,10)),DCB=*.INF5 Target library//OUTF6 DD DSN=&TPFX..&TVRM..HDSKEXVT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), EXECLIB(V)// SPACE=(TRK,(45,1,10)),DCB=*.INF6 Target library//OUTF7 DD DSN=&TPFX..&TVRM..HDSKPNLT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), PANEL// SPACE=(TRK,(60,1,200)),DCB=*.INF7 Target library//OUTF8 DD DSN=&TPFX..&TVRM..HDSKMSGT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), MESSAGE

// SPACE=(TRK,(5,1,5)),DCB=*.INF8 Target library//OUTF9 DD DSN=&TPFX..&TVRM..HDSKTABT,// UNIT=3390,VOL=SER=&TVSN,// DISP=(NEW,CATLG,DELETE), TABLE// SPACE=(TRK,(5,1,5)),DCB=*.INF9 Target library//SYSIN DD * COPY OUTDD=OUTF1,INDD=INF1 COPYMOD OUTDD=OUTF2,INDD=INF2 COPYMOD OUTDD=OUTF3,INDD=INF3 COPY OUTDD=OUTF4,INDD=INF4 COPY OUTDD=OUTF5,INDD=INF5 COPY OUTDD=OUTF6,INDD=INF6 COPY OUTDD=OUTF7,INDD=INF7 COPY OUTDD=OUTF8,INDD=INF8 COPY OUTDD=OUTF9,INDD=INF9/*

SMPALLOC (allocating SMP/E datasets)

The method for modifying SMPALLOC, which allocates SMP/E datasets, is

described below.


(1) to (3)

Modify the JOB statement in accordance with the installation

environment.

(4)

Change the prefix for the SMP/E dataset name from HDSKT to HTC1.KT.

(5) and (8)





Change the volume allocated to the SMP/E dataset from #smp01 to

SMP001.

(6), (7), (9), and (10)

Modify the prefix for the dataset name from HDSKT to HTC1.KT.

//SMPALLOC JOB (ACCT#),'ALLO SMP FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL allocates a CSI data set.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------// SET PFX=HDSKT Prefix of SMP files -----(4)

// SET VSN=#smp01 DASD volume serial for SMP files -----(5)//*//* 3) Submit the JCL.//*//*********************************************************************//STEP01 EXEC PGM=IDCAMS//CSIVOL DD UNIT=SYSDA,VOL=SER=&VSN,DISP=SHR//SYSPRINT DD SYSOUT=*//SYSIN DD * DELETE HDSKT.SMPCSI.CSI -----(6) SET MAXCC=0 DEFINE CLUSTER( - NAME(HDSKT.SMPCSI.CSI) - -----(7) FREESPACE(10 5) - KEYS(24 0) - RECORDSIZE(24 143) -

SHAREOPTIONS(2 3) - UNIQUE - VOLUMES(#smp01) - -----(8) ) - DATA( - NAME(HDSKT.SMPCSI.CSI.DATA) - -----(9) CONTROLINTERVALSIZE(4096) - CYLINDERS(1 1) - ) - INDEX( - NAME(HDSKT.SMPCSI.CSI.INDEX)- -----(10) CYLINDERS(1 1) - )/*//*//* Initialize a CSI data set. Refer to p.28 of SMP/E User's Guide.//*//STEP02 EXEC PGM=IDCAMS//SMPCSI DD DISP=OLD,DSN=&PFX..SMPCSI.CSI//ZPOOL DD DISP=SHR,DSN=SYS1.MACLIB(GIMZPOOL)//SYSPRINT DD SYSOUT=*//SYSIN DD * REPRO OUTFILE(SMPCSI) - INFILE(ZPOOL)/*//*





//* Allocate data sets for SMP installation of NC//*//STEP03 EXEC PGM=IEFBR14//* Data sets required by SMP//SMPPTS DD DSN=&PFX..SMPPTS,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,10)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920)//SMPSCDS DD DSN=&PFX..SMPSCDS,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,15)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920)//SMPMTS DD DSN=&PFX..SMPMTS,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,5)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920)//SMPSTS DD DSN=&PFX..SMPSTS,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5,5)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=27920)//SMPLOG DD DSN=&PFX..SMPLOG,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,

// SPACE=(CYL,(1,5)),// DCB=(RECFM=VB,LRECL=510,BLKSIZE=27998)//SMPLOGA DD DSN=&PFX..SMPLOGA,// DISP=(NEW,CATLG,DELETE),// UNIT=SYSDA,VOL=SER=&VSN,// SPACE=(CYL,(1,5)),// DCB=(RECFM=VB,LRECL=510,BLKSIZE=27998)

HDSKT1AL (allocating the distribution library and targetlibrary)

The method for modifying HDSKT1AL, which allocates the distribution library

and target library, is described below.


(1) to (3)


(4)

Change the prefix for the dataset name from HDSKT to HTC1.KT.

(5)

Change the volume allocated to the target library from #KT001 to KTT000.

(6)

Change the volume allocated to the distribution library from #KT002 to

KTD000.





//HDSKT1AL JOB (ACCT#),'ALLO UPLD FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*

//* This JCL allocates the data sets for SMP/E installation of//* HTSM for MF.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------// SET PFX=HDSKT Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET TVSN=#KT001 Target library VOLSER -----(5)// SET DVSN=#KT002 Distribution library VOLSER -----(6)//*//* 3) Submit the JCL.//*//*********************************************************************//ALLOCATE EXEC PGM=IEFBR14//* Allocate target libraries//HDSKSAMT DD DSN=&PFX..&VRM..HDSKSAMT, SAMPLES LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(15,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKLNKT DD DSN=&PFX..&VRM..HDSKLNKT, LOAD LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(75,1,20)),// DCB=(BLKSIZE=6144,RECFM=U)//HDSKLPAT DD DSN=&PFX..&VRM..HDSKLPAT, LPA LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(1,1,1)),

// DCB=(BLKSIZE=6144,RECFM=U)//HDSKPRCT DD DSN=&PFX..&VRM..HDSKPRCT, PROC LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(5,1,10)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKEXET DD DSN=&PFX..&VRM..HDSKEXET, EXEC(F) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKEXVT DD DSN=&PFX..&VRM..HDSKEXVT, EXEC(V) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6120,LRECL=255,RECFM=VB)

//HDSKPNLT DD DSN=&PFX..&VRM..HDSKPNLT, PANEL LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(60,1,200)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKMSGT DD DSN=&PFX..&VRM..HDSKMSGT, MESSAGE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,





// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKTABT DD DSN=&PFX..&VRM..HDSKTABT, TABLE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&TVSN,// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//* Allocate distribution libraries//HDSKSAMD DD DSN=&PFX..&VRM..HDSKSAMD, SAMPLES LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(15,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKLNKD DD DSN=&PFX..&VRM..HDSKLNKD, LOAD LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(75,1,20)),// DCB=(BLKSIZE=6144,RECFM=U)//HDSKLPAD DD DSN=&PFX..&VRM..HDSKLPAD, LPA LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(1,1,1)),// DCB=(BLKSIZE=6144,RECFM=U)//HDSKPRCD DD DSN=&PFX..&VRM..HDSKPRCD, PROC LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(5,1,10)),

// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKEXED DD DSN=&PFX..&VRM..HDSKEXED, EXEC(F) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKEXVD DD DSN=&PFX..&VRM..HDSKEXVD, EXEC(V) LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(45,1,10)),// DCB=(BLKSIZE=6120,LRECL=255,RECFM=VB)//HDSKPNLD DD DSN=&PFX..&VRM..HDSKPNLD, PANEL LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(60,1,200)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)

//HDSKMSGD DD DSN=&PFX..&VRM..HDSKMSGD, MESSAGE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)//HDSKTABD DD DSN=&PFX..&VRM..HDSKTABD, TABLE LIBRARY// DISP=(NEW,CATLG,DELETE),// UNIT=3390,VOL=SER=&DVSN,// SPACE=(TRK,(5,1,5)),// DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB)

HDSKT2DF (defining the distribution library and target

library)The method for modifying HDSKT2DF, which defines the distribution library

and the target library, is described below.






(1) to (3)


(4)

Change the prefix for the SMP/E dataset name, target library name, anddistribution library name from HDSKT to HTC1.KT.

(5) to (10)Change the prefix for the SMP/E dataset name from HDSKT to HTC1.KT.

(11)

Change the volume allocated to SMPTLIB from #smp01 to SMP001.

(12) to (29)

Change the prefix for the target library name from HDSKT to HTC1.KT.

(30) to (38)

Change the prefix of the distribution library name from HDSKT to HTC1.KT.

//HDSKT2DF JOB (ACCT#),'DO THE DDDEFS', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E DDDEF for the distribution libraries and//* the target libraries.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*

//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSKT Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)//* #smp01 DASD volume serial for SMPTLIB//*//* 3) Submit the JCL to begin execution of SMP/E DDDEF.//*//*********************************************************************//S1 EXEC PGM=GIMSMP//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*

//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),





// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//* SMP/E control record input//SMPCNTL DD *SET BDY(GLOBAL).UCLIN.ADD GLOBALZONE ZONEINDEX( (DLIB1,HDSKT.SMPCSI.CSI,DLIB), -----(5)

(TGT1,HDSKT.SMPCSI.CSI,TARGET)) -----(6) SREL(Z038).ADD DDDEF(SMPPTS) DA(HDSKT.SMPPTS) -----(7) OLD.ADD DDDEF(SMPLOG) DA(HDSKT.SMPLOG) -----(8) MOD.ADD DDDEF(SMPLOGA) DA(HDSKT.SMPLOGA) -----(9) MOD.ADD DDDEF(SMPTLIB) DSPREFIX(HDSKT.TM) -----(10) VOLUME(#smp01) -----(11) UNIT(3390) CYL

SPACE(5,5) DIR(200) DSNTYPE(PDS).ADD DDDEF(HDSKSAMT) DA(HDSKT.Vnnnnnn.HDSKSAMT) -----(12) OLD.ADD DDDEF(HDSKLNKT) DA(HDSKT.Vnnnnnn.HDSKLNKT) -----(13) OLD.ADD DDDEF(HDSKLPAT) DA(HDSKT.Vnnnnnn.HDSKLPAT) -----(14) OLD.ADD DDDEF(HDSKPRCT) DA(HDSKT.Vnnnnnn.HDSKPRCT) -----(15) OLD.ADD DDDEF(HDSKEXET) DA(HDSKT.Vnnnnnn.HDSKEXET) -----(16) OLD.ADD DDDEF(HDSKEXVT) DA(HDSKT.Vnnnnnn.HDSKEXVT) -----(17) OLD.ADD DDDEF(HDSKPNLT) DA(HDSKT.Vnnnnnn.HDSKPNLT) -----(18) OLD.ADD DDDEF(HDSHDSKMSGT) DA(HDSKT.Vnnnnnn.HDSKMSGT) -----(19)





OLD.ADD DDDEF(HDSKTABT) DA(HDSKT.Vnnnnnn.HDSKTABT) -----(20) OLD.ENDUCL.SET BDY(TGT1).UCLIN.ADD TARGETZONE(TGT1) RELATED(DLIB1) SREL(Z038).ADD DDDEF(HDSKSAMT) DA(HDSKT.Vnnnnnn.HDSKSAMT) -----(21) OLD.ADD DDDEF(HDSKLNKT) DA(HDSKT.Vnnnnnn.HDSKLNKT) -----(22) OLD.ADD DDDEF(HDSKLPAT) DA(HDSKT.Vnnnnnn.HDSKLPAT) -----(23) OLD.ADD DDDEF(HDSKPRCT) DA(HDSKT.Vnnnnnn.HDSKPRCT) -----(24) OLD.ADD DDDEF(HDSKEXET) DA(HDSKT.Vnnnnnn.HDSKEXET) -----(25) OLD.ADD DDDEF(HDSKEXVT) DA(HDSKT.Vnnnnnn.HDSKEXVT) -----(26)

OLD.ADD DDDEF(HDSKPNLT) DA(HDSKT.Vnnnnnn.HDSKPNLT) -----(27) OLD.ADD DDDEF(HDSKMSGT) DA(HDSKT.Vnnnnnn.HDSKMSGT) -----(28) OLD.ADD DDDEF(HDSKTABT) DA(HDSKT.Vnnnnnn.HDSKTABT) -----(29) OLD.ENDUCL.SET BDY(DLIB1).UCLIN.ADD DLIBZONE(DLIB1) RELATED(TGT1) SREL(Z038).

ADD DDDEF(HDSKSAMD) DA(HDSKT.Vnnnnnn.HDSKSAMD) -----(30) OLD.ADD DDDEF(HDSKLNKD) DA(HDSKT.Vnnnnnn.HDSKLNKD) -----(31) OLD.ADD DDDEF(HDSKLPAD) DA(HDSKT.Vnnnnnn.HDSKLPAD) -----(32) OLD.ADD DDDEF(HDSKPRCD) DA(HDSKT.Vnnnnnn.HDSKPRCD) -----(33) OLD.ADD DDDEF(HDSKEXED) DA(HDSKT.Vnnnnnn.HDSKEXED) -----(34) OLD.ADD DDDEF(HDSKEXVD) DA(HDSKT.Vnnnnnn.HDSKEXVD) -----(35) OLD.ADD DDDEF(HDSKPNLD) DA(HDSKT.Vnnnnnn.HDSKPNLD) -----(36) OLD.ADD DDDEF(HDSKMSGD) DA(HDSKT.Vnnnnnn.HDSKMSGD) -----(37) OLD.ADD DDDEF(HDSKTABD) DA(HDSKT.Vnnnnnn.HDSKTABD) -----(38)





OLD.ENDUCL.SET BDY(GLOBAL).LIST ALLZONES DDDEF./*

HDSKT3RC (SMP/E RECEIVE processing)The method for modifying HDSKT3RC, which performs SMP/E RECEIVE

processing, is explained below.


(1) to (3)


(4)


(5)


SMP001.

(6)

Change RFPREFIX from HITACHI to HTC1.KT.

//HDSKT3RC JOB (ACCT#),'RECEIVE HTSM FOR MF', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************

//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E RECEIVE to uncompress .XMIT files.//*//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSKT Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)

// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//* HITACHI Refer to 4) for detail.//*//* 3) Select form of SMPPTFIN DD statement depending upon whether//* installing from tape or uploaded .XMIT file.//*//* 4) Modify the value of RFPREFIX to match the prefix of the data set//* that you created with the JCL 'RECVUPLD'. Refer to the comment//* (refer to 3.) in 'RECVUPLD' for more detail.//*





//* 5) Submit the JCL.//*//*********************************************************************//RECEIVE EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),

// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPHOLD DD DUMMY//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//* Use DASD files if installing from .XMIT distribution//SMPPTFIN DD DSN=&PFX..CHKTnnn.SMPMCS,DISP=SHR//* Use tape files if installing from cartridge tape//*SMPPTFIN DD DSN=SMPMCS,DISP=OLD,

//* VOL=SER=HDSKT,UNIT=3480,LABEL=(1,SL)//SMPCNTL DD *SET BDY(GLOBAL).RECEIVE SELECT(CHKTnnn) RFPREFIX(HITACHI) -----(6) LIST./*

HDSKT4AP (creating target libraries)

The method for modifying HDSKT4AP, which creates the target library, is

explained below.


(1) to (3)






(4)


(5)


SMP001.

(6)

After SMP/E ACCEPT is completed, delete CHECK (or comment it out), and

then perform the job again.

//HDSKT4AP JOB (ACCT#),'APPLY HTSM FOR MF', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E APPLY to create the target libraries.//*

//* Instructions://* 1) Modify the JOB statement to match your environment.//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSKT Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//*//* 3) Submit the JCL and make sure that no error occurs.//* 4) Remove CHECK operand from APPLY and re-submit the JCL to//* complete.//*//*********************************************************************

//APPLY EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)

//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a





//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//SMPHOLD DD DUMMY//SMPSCDS DD DISP=SHR,DSN=&PFX..SMPSCDS//SMPMTS DD DISP=SHR,DSN=&PFX..SMPMTS//SMPSTS DD DISP=SHR,DSN=&PFX..SMPSTS//SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB// DD DISP=SHR,DSN=&PFX..SMPMTS//SMPCNTL DD *SET BDY(TGT1).APPLY SELECT(CHKTnnn) CHECK -----(6) ./*

HDSKT5AC (creating distribution libraries)

The method for modifying HDSKT5AC, which creates the distribution library, is

explained below.


(1) to (3)


(4)


(5)


SMP001.

(6)

After SMP/E ACCEPT is completed, delete CHECK (or comment it out), and

then perform the job again.

//HDSKT5AC JOB (ACCT#),'ALLO UPLD FILES', -----(1)// REGION=0M,CLASS=A, -----(2)// MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3)//*********************************************************************

//*//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd.//*//*********************************************************************//*//* This JCL executes SMP/E ACCEPT to create the distribution libraries.//*//* Instructions://* 1) Modify the JOB statement to match your environment.





//* 2) Modify the following values to match your environment://*//* Value Description//* -------- --------------------------------//* GIMSMP Installation SMP/E program// SET PFX=HDSKT Prefix of SMP files -----(4)// SET VRM=Vnnnnnn Second level name (VER REL MOD)// SET VSN=#smp01 DASD volume serial for SMPTLIB -----(5)//*//* 3) Submit the JCL and make sure that no error occurs.//* 4) Remove CHECK operand from ACCEPT and re-submit the JCL to//* complete.//*//*********************************************************************//ACCEPT EXEC PGM=GIMSMP//SMPOUT DD SYSOUT=*//SMPRPT DD SYSOUT=*//SMPLIST DD SYSOUT=*//SYSPRINT DD SYSOUT=*//SMPWRK1 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK2 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK3 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),

// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK4 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,LRECL=80,BLKSIZE=3120)//SMPWRK6 DD UNIT=SYSDA,// SPACE=(3120,(0364,0380,500)),// DCB=(RECFM=FB,BLKSIZE=3120)//SYSUT1 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT2 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT3 DD UNIT=SYSDA,SPACE=(3120,(0380,0760))//SYSUT4 DD UNIT=SYSDA,SPACE=(3120,(0038,0100)),// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB)//* The following data sets would likely be specified in a//* cataloged procedure customized for a particular customer.//SMPPTS DD DISP=SHR,DSN=&PFX..SMPPTS//SMPLOG DD DISP=MOD,DSN=&PFX..SMPLOG

//SMPLOGA DD DISP=MOD,DSN=&PFX..SMPLOGA//SMPCSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//GLOBAL DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//TGT1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//DLIB1 DD DISP=SHR,DSN=&PFX..SMPCSI.CSI//SMPTLIB DD DISP=SHR,UNIT=3390,VOL=SER=&VSN//SMPHOLD DD DUMMY//SMPSCDS DD DISP=SHR,DSN=&PFX..SMPSCDS//SMPMTS DD DISP=SHR,DSN=&PFX..SMPMTS//SMPSTS DD DISP=SHR,DSN=&PFX..SMPSTS//SYSLIB DD DISP=SHR,DSN=SYS1.MACLIB// DD DISP=SHR,DSN=&PFX..SMPMTS//SMPCNTL DD *SET BDY(DLIB1).ACCEPT SELECT(CHKTnnn)

CHECK -----(6) ./*





F

Command syntax descriptions

This chapter describes the command syntax conventions used in thisdocument.

□ Command syntax descriptions

Command syntax descriptions F-1




Command syntax descriptions

The following table describes the command syntax conventions used in thisdocument.

Table F-1 Command syntax descriptions

Symbol Convention

| Vertical bars are delimiters between multiple items and represent the word"or".

Example:

A|B|C means "A, B, or C".

[ ] Items enclosed by brackets can be omitted.

If multiple items are described, all the items are omitted or only one of themis selected.

Example:

[A] means "do not specify anything " or "only specify A".

{ } One item must be selected from among the items enclosed by curly brackets.Items are delimited by vertical bars (|).

Example:

{A|B|C} means "you must specify A, B, or C".

... or + The item that immediately precedes an ellipsis symbol can be specifiedrepeatedly.

Example:

A, ... means "you can specify item A as many times as necessary".

{A|B}+ means "you must specify item A or B as many times as necessary inany order".

* The item that immediately precedes this symbol can be omitted or can bespecified repeatedly.

Example:{A|B}* means "do not specify anything" or "specify A or B as many times asnecessary in any order".

_ Indicates that the item is a value assumed by the system if one of the itemsenclosed by the selection symbols is omitted.

0Indicates that there can be a space or tab.

Indicates that one or more spaces or tabs are necessary.

nIndicates that n or more spaces or tabs are necessary.

~ The items that immediately precede this symbol must follow the conventionfor < >, << >>, or (( )).

< > Indicates a syntax element that must be used when specifying the item.

<< >> Indicates a default value used by the system if the item is omitted.

(( )) Indicates the range of valid values.

The following table shows the syntax elements used in this document.

F-2 Command syntax descriptions




Table F-2 Syntax elements

Syntaxelement

Valid value Example

<Numericcharacter>

0-9 --

<Alphabetic

character>

A-Z, a-z, at marks (@), hash marks (#), and dollar signs

($)

--

<Uppercasealphabeticcharacter>

A-Z, at marks (@), hash marks (#), and dollar signs ($) --

<Alphanumericcharacter>

<Alphabetic character> or <numeric character> A123

<Alphanumericcharacterstring>

<Alphanumeric character>+ A123

<Alphabeticcharacter

string>

<Alphabetic character>+ A@C

<Hexadecimalcharacter>

<Numeric character>, A-F, and a-f --

<Hexadecimalcharacterstring>

<Hexadecimal character>+

This setting is not case sensitive.

--

<REXX symbolheadingcharacter>

<Alphabetic characters>, exclamation marks (!), questionmarks (?), and underscores (_)


--

<REXX simplesymbol>

<REXX symbol heading character>{<REXX symbolheading character> | <numeric character>}*


--

<REXX prefix> <REXX simple symbol>[.<REXX simple symbol>]*.


A?.A123.!12.

<Symbolicname>

<Uppercase alphabetic character>{<uppercasealphabetic character>|<numeric character>}*

Note: A symbolic name can contain eight or fewercharacters.

A1234567

<Prefixcharacterstring>

<Symbolic name>[.<symbolic name>]* A12.B34.CDE

Command syntax descriptions F-3




F-4 Command syntax descriptions




Acronyms and abbreviations

The following acronyms and abbreviations might be used in this guide.

A

APFauthorized program facility

ASCIIamerican standard code for information interchange

B

Business Continuity Manager

Hitachi Business Continuity Manager

C

CCAcommand control address

CCWchannel command word

CLIcommand line interface

Command Control InterfaceHitachi Command Control Interface

# A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Acronyms-1




CSVcomma-separated values

CUcontroller unit

DDASD

direct access storage device

DEVNdevice number

DFSMSData Facility Storage Management Subsystem

DKC

disk controller

DLIBdistribution library

DSORGdata set organization

Dynamic Provisioning for MainframeHitachi Dynamic Provisioning Software for Mainframe

Dynamic Tiering for MainframeHitachi Dynamic Tiering Software for Mainframe

E

EBCDICextended binary coded decimal interchange code

F

FMIDfunction modification identifier


Acronyms-2




FTPfile transfer protocol

G

GTF

generalized trace facility

I

I/Oinput/output

IDIdentifier

IPLinitial program load

ISPFinteractive system productivity facility

J

JCL job control language

L

LDEVlogical device

LRECLlogical record length

O

OPEXoperating expense


Acronyms-3




OSoperating system

R

RACF

resource access control facility

RECFMrecord format

REXXrestructured extended executor

ROIreturn on investment

S

SAFsystem authorization facility

SASserial attached SCSI

SATAserial advanced technology attachment

SCSIsmall computer system interface

SLAservice level agreement

SMP/Esystem modification program extended

SMSUnits of the storage pool managed by the DFSMS

SSDsolid state drive


Acronyms-4




SSIDstorage system ID

SVCsupervisor call

SVPservice processor

SYSMODSYStem MODification

T

Tiered Storage Manager for MainframeHitachi Tiered Storage Manager for Mainframe

TSO/E

Time Sharing Option/Extensions

V

VMvirtual machine

VSPHitachi Virtual Storage Platform

X

XMLextensible markup language


Acronyms-5





Acronyms-6




Glossary

This glossary describes the terms used in this manual.

A

AC fieldAn entry field used to specify an action in an ISPF panel. The action specified in the ACfield is executed for the corresponding line when Enter is pressed.

B

Business Continuity ManagerA program used for building a highly reliable backup system in which multiple datacenters are linked together. In the event of a disaster, this program enables operations

to continue by using the copy functions of the storage systems, and also enables you tominimize the restoration time or data loss from a disaster.

C

CLI commandA command that can be used from the command line interface (CLI) of Tiered StorageManager for Mainframe.

CLI command-execution log

The log in which log data for executed CLI commands is recorded.

Command Control InterfaceA program that allows users to operate a storage system from the command interface.


Glossary-1




COMMAND fieldAn entry field used to specify an action in an ISPF panel. The action specified in theCOMMAND field is executed for the corresponding line when Enter is pressed.

Configuration fileA generic name for the tiering policy group definition file and disk configurationdefinition f ile.

D

device addressA numbering system for devices that a storage system can use to manage volumes. Adevice address is represented by a combination of a CU and a CCA.

device information structureA REXX variable structure in which device information for volumes is stored.

DEVN

A device number used by a mainframe host to manage storage volumes.

disk configuration definition fileA file that defines the storage system's configuration information.

Dynamic Provisioning for MainframeSoftware that allocates a virtual volume to a host so that the required amount of physical space can be used according to the data write request.

Dynamic Tiering for MainframeSoftware providing functionality that relocates data according to the access frequency,in addition to the functionality equivalent to Dynamic Provisioning for Mainframe. Inprinciple, data areas that are accessed frequently are relocated to a higher-speedhardware tier, and data areas that are accessed not so frequently are relocated to alower-speed hardware tier. This functionality can both improve volume performance andreduce costs.

E

environment setup commandCommands that are used to set up a Tiered Storage Manager for Mainframe operatingenvironment. These commands are started by using the START OS command. The

following commands are environment setup commands: KTALCSVC, KTSETENV, andKTDSPENV


Glossary-2




environment variablesVariables which are set by using the KTSETENV command to set up the Tiered Storage

Manager for Mainframe operating environment. Environment variables can be used tospecify the prefixes of license information dataset, whether to use the system loggerservice, and whether to output the CLI command-execution log data to SYSLOG or theconsole.

event log

The log in which operations of Tiered Storage Manager for Mainframe are logged. Thelogged data includes messages, information about parameters used when I/O errorsoccurred, and command parameter information.

H

host-discovered array index structureA REXX variable structure storing information that indicates the storage system andvolume configurations.

host-discovered array structureA REXX variable structure that stores the values set for a storage system or volume.The data in host-discovered array structures is saved in the disk configuration definitionfile.

L

log streamAn aggregate of log data written by the system logger service.

logical DKCAn aggregate of volumes whose CU numbers are from 00 through FE that can behandled by VSP. Tiered Storage Manager for Mainframe recognizes a logical DKC as astorage system. A number assigned to each logical DKC (logical DKC serial number) iscalled a storage system's serial number.

logical DKC numberA number (0 or 1) assigned to each logical DKC in the storage system.

logical DKC serial numberA number assigned to each logical disk controller (DKC).


Glossary-3




M

message structureA REXX variable structure that stores messages generated by CLI commands that areexecuted.

N

new-page assignment tierThe tier to which new pages are assigned when a host writes data to a volume for thefirst time.

P

physical DKC serial numberA number assigned to each storage system.

point-and-shootThe act of positioning the cursor on an item in a panel and pressing Enter to select it. If an action has been set for the point-and-shoot item, selecting that item triggers theaction to be executed.

R

REXXOne of the structure programming languages developed by IBM. Mainly used on the IBM

mainframe operating system and used as the macro language for calling applicationsand operating system functions.

REXX variable structureA variable whose value is passed when a CLI command is executed.

S

SMP/EAn IBM installer.

SMS storage groupAn aggregate of the volumes that constitute the storage pool managed by DFSMS(storage management environment in IBM MVS).


Glossary-4




SNThe serial number of a storage system.

Storage NavigatorA program product that is connected to a service processor (SVP) to allow users tooperate a storage system remotely.For details, see the Storage N avigator U ser Guide.

storage system serial numberA number assigned to each logical disk controller (DKC). This is also called a logical DKCserial number.

SVP (service processor)An internal computer in a storage system. Maintenance personnel use it when analyzingmaintenance information or diagnosing devices.

system logger serviceMVS series standard functionality for writing, displaying, and deleting log data.

T

tierMedia in a pool grouped by drive type and performance. A maximum of three tiers canbe defined for one pool based on the performance of the media.

tier relocationA function of Dynamic Tiering for Mainframe. This function automatically allocates datato appropriate media according to the access frequency, based on the informationcollected by performance monitoring. Frequently accessed data is allocated to an uppertier, which consists of faster media, and infrequently accessed data is allocated to a

lower tier, which consists of lower media.

tiering policyInformation about which tiers data is to be located in, and how data is to be relocated.

tiering policy groupA group of multiple SMS storage groups or volumes. A tiering policy specification oroperation can be performed for each tiering policy group.

tiering policy group definition fileA file that defines tiering policy groups.

tiering policy group structureA REXX variable structure that stores tiering policy values. Information about the tieringpolicy group structure is saved in the tiering policy group definition file.


Glossary-5




tiering policy information CSV fileA CSV file that specifies information about the volumes or an SMS storage group, whichare to be defined in the tiering policy group.

tiering policy levelA level of tiers in which data can be relocated. There are six levels, from 0 (default)

through 5. If a tiering policy level is specified, pages are assigned to the tiers that

belong to the specified level, and data is saved on the pages.

V

VOLSER A volume serial number used by a mainframe host to manage storage volumes.


Glossary-6




Index

A

AC field Glossary-1

ALLOUPLD (sample JCL) E-2

ARRAYS parameter [KTSCAN command] 6-26

ARRAYS parameter [KTSTORE command] 6-29attributes of the distribution libraries (DLIB) 2-33

attributes of the target libraries 2-10

B

Business Continuity Manager Glossary-1

C

calculating required memory 2-32

CLI command 6-1, Glossary-1

CLI command coding format 6-3

CLI command-execution log 9-3, Glossary-1

collecting trace information 9-2

collecting trace information and logs 9-1

Command Control Interface Glossary-1

COMMAND field Glossary-2

command syntax descriptions F-1

commands that can be used in ISPF panels B-1

common items in the panel 5-4

configuration file Glossary-2

configuration file, disk space requirements of 7-3

D

defining log stream 9-6

defining SMS for system logger service 9-6

device address Glossary-2

device information structure 8-10, Glossary-2

Device Scan Scope panel 5-12

DEVN Glossary-2

DEVN parameter [KTDCTDEV command] 6-7

DEVN parameter [KTQRYDEV command] 6-17

disk configuration definition file 1-12, Glossary-2

disk space requirements for event log 9-12, 9-18

DSK parameter [KTSTORE command] 6-29

Dynamic Provisioning for Mainframe Glossary-2

Dynamic Tiering for Mainframe Glossary-2

E

Edit Defaults panel 5-13

environment variable 2-18, Glossary-3

ERRCODE B-2

Error Code Help panel 5-14

error-code parameter [KTERCODE command] 6-38

estimating log stream dataset 9-13

estimating OUTLOG 9-13

estimating staging dataset 9-12

event log 9-3, Glossary-3

event log data output tool 9-13

Exception Message List panel 5-15

F

file provided on the installation media 2-7

files used by Tiered Storage Manager for

Mainframe 7-1


Mainframe and their configuration 1-12

Index-1





Mainframe, dataset format of 7-3


Mainframe, names of 7-2

FILTER B-2

Filter Options panel B-2

filtering displayed information 3-32

FIND B-3

Find Options panel B-3

FMID 2-9

FROM parameter [KTSCAN command] 6-26

FROMVSN parameter [KTSCAN command] 6-26

H

HANDLE parameter [KTCONMSG command] 6-35

HDSKT1AL [sample JCL] E-9

HDSKT2DF [sample JCL] E-11

HDSKT3RC [sample JCL] E-15

HDSKT4AP [sample JCL] E-16

HDSKT5AC [sample JCL] E-18

HDSKTSIN [sample JCL] E-5

highlighting available point-and-shoot fields 3-35

host-discovered array index structure 8-3,

Glossary-3

host-discovered array structure 8-4, Glossary-3

how to specify filter conditions in ISPF paneIs B-6

how to specify search conditions in ISPF paneIs B-6

Iinstallation and setup 2-1

overview 2-3

Installation Management area 5-17

installation using SMP/E 2-8

ISPF panels 5-1

K

KTACTTPG command 6-5

KTALCSVC command 6-42

KTCONMSG command 6-34

KTDCTDEV command 6-6

KTDCTTPG command 6-8

KTDSPENV command 6-43

KTENV command 6-36

KTERCODE command 6-37

KTGETHDA command 6-9

KTIMPORT command 6-12

KTINSCHK command 6-39

KTLOAD command 6-14

KTLOGCP 9-13

KTQRYDEV command 6-17

KTQRYRLC command 6-19

KTQRYTPG command 6-21

KTQSTATS command 6-23

KTSCAN command 6-25

KTSETENV command 6-45

KTSLEEP command 6-41

KTSTORE command 6-28

KTWTOMSG command 6-32

L

layout of the panel 5-4

library datasets to be registered after the

installation 2-10

license information dataset

creating 2-26

list of CLI commands 6-2

LOCATE B-3

Locate Options panel B-4

log stream Glossary-3

log types 9-3

logical DKC Glossary-3

logical DKC number Glossary-3

logical DKC serial number Glossary-3

M

Main panel 5-16

Main panel (common) 5-16

Manage Licenses panel 5-22

message structure 8-2, Glossary-4

MIN parameter [KTSLEEP command] 6-42

MSG parameter [KTACTTPG command] 6-5

MSG parameter [KTDCTDEV command] 6-7

MSG parameter [KTDCTTPG command] 6-8

MSG parameter [KTGETHDA command] 6-10

MSG parameter [KTIMPORT command] 6-12MSG parameter [KTLOAD command] 6-15

MSG parameter [KTQRYDEV command] 6-17

MSG parameter [KTQRYRLC command] 6-20

MSG parameter [KTQRYTPG command] 6-22

MSG parameter [KTQSTATS command] 6-23

MSG parameter [KTSCAN command] 6-26

Index-2




MSG parameter [KTSTORE command] 6-29

MSGID parameter [KTCONMSG command] 6-35

N

New-page assignment description (2-tier

configuration) 7-6

New-page assignment description (3-tier

configuration) 7-6

new-page assignment tier Glossary-4

new-page assignment tier, about 1-9

new-page assignment tier, values 1-10

O

OP parameter [KTCONMSG command] 6-34

OS console command 6-42

OS console command coding format 6-5

coding format 6-5

Overview of assigning new pages to tiers 1-9

overview of Hitachi Tiered Storage Manager for

Mainframe 1-1

P

parameters specified when log stream is defined

9-8

physical DKC serial number Glossary-4

point-and-shoot Glossary-4

Policy ID Entry panel 5-22

Policy CSV List area 5-20

POLICY parameter [KTIMPORT command] 6-13

Pool Selection List panel 5-23

Pool Status Detail panel 5-24

positioning cursor at specific line in sorted field

3-33

PREFIX parameter [KTGETHDA command] 6-10

PREFIX parameter [KTIMPORT command] 6-12

PREFIX parameter [KTLOAD command] 6-15

PREFIX parameter [KTSTORE command] 6-29

Preparing to use Tiered Storage Manager for

Mainframe 2-32

prerequisites for Tiered Storage Manager for

Mainframe 1-10

progress of tier relocation

checking (CLI commands) 4-12

R

RECVUPLD (sample JCL) E-4

registering a license by entering a license key 2-29

registering a license by using a license key file2-27

registering a user SVC 2-15

registering licenses 2-25

RESET parameter (FILTER command) B-2

RESET parameter (SELECT command) B-5REXX Glossary-4

REXX external routine 6-5

REXX external routine coding f ormat 6-4

REXX script coding format (REXX external routine)

6-4

REXX script coding format (TSO/E command) 6-4

REXX variable structure 8-1, Glossary-4

RFIND B-4

S

sample JCL E-1

SCAN parameter [KTIMPORT command] 6-13

script coding method 6-4

searching character strings 3-33

SEC parameter [KTSLEEP command] 6-42

SELECT B-4

Select Options panel B-5

Set Defaults area 5-18

setting access privileges for system logger

resources 9-7

setting actions in multiple AC fields 3-34

setting command line location 3-35

Setting Information panel 5-25

setting LOGR couple data sets 9-6

setting number of displayed function keys 3-35

setting operating environment by using

environment variables 2-19

settings required to use Tiered Storage Manager

for Mainframe on the ISPF panel 2-22

SMP/E Glossary-4

SMPALLOC [sample JCL] E-7

SMS storage group Glossary-4

SN Glossary-5

SN parameter [KTGETHDA command] 6-10

SORT B-5

Sort Options panel B-6

sorting items 3-32

SPACE parameter [KTSTORE command] 6-30

specific volume

Index-3




deleting from tiering policy group (CLI

commands) 4-17

deleting from tiering policy group (ISPF panels)

3-30

starting system logger service 9-7

STEM parameter [KTACTTPG command] 6-5

STEM parameter [KTDCTTPG command] 6-8

STEM parameter [KTGETHDA command] 6-10

STEM parameter [KTLOAD command] 6-14

STEM parameter [KTQRYDEV command] 6-17

STEM parameter [KTQRYRLC command] 6-20

STEM parameter [KTQRYTPG command] 6-22

STEM parameter [KTQSTATS command] 6-23

STEM parameter [KTSCAN command] 6-25

STEM parameter [KTSTORE command] 6-29

stopping the system logger service 9-8

Storage Navigator Glossary-5

storage system

scanning (CLI commands) 4-5

scanning (ISPF panels) 3-5Storage System List area 5-19

storage system serial number Glossary-5

STORGRP parameter [KTSCAN command] 6-26

SVP (service processor) Glossary-5

Switch the Unit panel 5-12

syntax element F-3

system configuration of Tiered Storage Manager

for Mainframe 1-11

system logger service Glossary-5

system symbol 2-18

T

terms used in Tiered Storage Manager for

Mainframe 1-5

text parameter [KTWTOMSG command] 6-33

text-1 parameter [KTWTOMSG command] 6-33

text-2 parameter [KTWTOMSG command] 6-33

tier Glossary-5

tier relocation Glossary-5

Tiered Storage Manager for Mainframe

functionality

overview 1-4

Tiered Storage Manager for Mainframe operations

ISPF panels 3-1

Tiered Storage Manager for Mainframe operations

when using the CLI

CLI commands 4-1

tiering policy Glossary-5

applying (CLI commands) 4-9

applying (ISPF panels) 3-8

changing (CLI commands) 4-15

changing (ISPF panels) 3-28

verifying (CLI commands) 4-11

tiering policy group Glossary-5

adding volume (CLI commands) 4-15

adding volume (ISPF panels) 3-29

changing (ISPF panels) 3-28

defining (CLI commands) 4-7

defining (ISPF panels) 3-3, 3-5, 3-8

defining and verifying (CLI commands) 4-2

verifying (ISPF panels) 3-3

tiering policy group definition file 1-12, Glossary-5

Tiering Policy Group Definition panel 5-26

Tiering Policy Group List area 5-21

Tiering Policy Group Pool List panel 5-27

Tiering Policy Group Pool Status Detail panel 5-28

Tiering Policy Group Storage Group List panel 5-30tiering policy group structure 8-9, Glossary-5

Tiering Policy Group Summary panel 5-31

Tiering Policy Group Volume List panel 5-33

Tiering Policy Group Volume Status Detail panel

5-35

tiering policy group, about 1-5

tiering policy group, configuration example of 7-8

tiering policy group, grouping patterns of 1-6

tiering policy information CSV file 1-12, Glossary-6

creating (CLI commands) 4-7

creating (ISPF panels) 3-7

example of changing 7-9

modifying (ISPF panels) 3-31

tiering policy information CSV file, format of 7-4

tiering policy level Glossary-6

tiering policy level, about 1-8

tiering policy, about 1-6

tiering policy, overview of 1-7

TIMEOUT parameter [KTCONMSG command] 6-35

TO parameter [KTSCAN command] 6-26

TOVSN parameter [KTSCAN command] 6-26

TPG parameter [KTLOAD command] 6-15

TPG parameter [KTSTORE command] 6-29

TSO/E command 6-34

TSO/E command coding format

coding format 6-4

type parameter [KTWTOMSG command] 6-32

Index-4




U

Upgrading Tiered Storage Manager for Mainframe

D-1

upgrading, preparation for D-3

V

verification after defining tiering policy group 3-13verification after scanning storage systems (ISPF

panels) 3-9

Verifying the setup information 2-31

VOLSER Glossary-6

volume I/O performance, checking 4-14

volume information

checking (CLI commands) 4-3

VOLUME parameter [KTSTORE command] 6-30

Volume Selection List panel 5-36

Volume Status Detail panel 5-37

W

Workflow for upgrading Tiered Storage Manager

for Mainframe D-2

workflow for using Tiered Storage Manager for

Mainframe 1-14

writing to log dataset (without using system logger

service) 9-17

Index-5




Index-6


Hitachi Tiered Storage Manager for Mainframe User Guide

Documents

Transcript of Hitachi Tiered Storage Manager for Mainframe User Guide