Owner manual

ManualsBrandsHP ManualsStorageXP P9500 Storage

HP XP P9000 Smart Manager for Mainframe

User Guide

Part number: TB589-96001

First edition: July 2013

Summary of content (240 pages)

PAGE 1
HP XP P9000 Smart Manager for Mainframe User Guide Part number: TB589-96001 First edition: July 2013
PAGE 2
Legal and notice information © Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
PAGE 3
Contents Preface .............................................................................................. 11 1 Overview of Smart Manager for Mainframe ........................................ 13 About Smart Manager for Mainframe ......................................................................................... Overview of the Smart Manager for Mainframe functionality .......................................................... Terms used in Smart Manager for Mainframe ............................
PAGE 4
Registering a license by entering a license key ....................................................................... Checking the setup ................................................................................................................... Overview of checking the setup ............................................................................................ How to check the setup .......................................................................................................
PAGE 5
KTQRYRLC ........................................................................................................................ 99 KTQRYTPG ...................................................................................................................... 101 KTQSTATS ....................................................................................................................... 102 KTSCAN ...........................................................................................................
PAGE 6
Re-defining the log stream when the event log is full .............................................................. Restarting the system logger service and re-defining the log stream when the event log is full ...... Disk space requirements for the event log when the system logger service is used ..................... Overview of the event log data output tool ........................................................................... Outputting logs by using the event log data output tool ...............
PAGE 7
KTDEMO10 KTDEMO11 KTDEMO12 KTDEMO13 KTDEMO14 (Apply the tiering policy) ................................................................................. (Check the tiering policy) ................................................................................ (Check the page relocation status) .................................................................... (Check the relocation progress) ........................................................................ (Check I/O performance information) ....
PAGE 8
Figures 1 Automatic data relocation across tiers according to the access frequency ....................... 13 2 Locating data in a specified tier according to performance requirements ........................ 14 3 Tier management using Smart Manager for Mainframe ............................................... 15 4 Grouping patterns of tiering policy groups ................................................................. 16 5 Overview of tiering policies ....................................................
PAGE 9
Tables 1 Relationship between tiering policy levels and tiers in which data will be located ............ 18 2 Values that can be used to specify the new-page assignment tier ................................... 19 3 Files provided on the installation media ..................................................................... 26 4 FMID for Smart Manager for Mainframe components .................................................. 28 5 Attributes of the target libraries ..........................................
PAGE 10
32 Output items of the KTINSCHK command ................................................................. 117 33 Return codes generated by the KTSLEEP command .................................................... 120 34 Return codes generated by the KTALCSVC command ................................................. 121 35 Return codes generated by the KTDSPENV command ................................................ 122 36 Return codes generated by the KTSETENV command .......................................
PAGE 11
Preface This document describes how to use the following program product: - HP XP P9000 for Smart Manager for Mainframe Hereafter, the above product is simply called Smart Manager for Mainframe. In figures, the product is indicated as Smart Manager for MF.
PAGE 12
Preface
PAGE 13
1 Overview of Smart Manager for Mainframe This chapter provides an overview of Smart Manager for Mainframe. About Smart Manager for Mainframe Smart Manager for Mainframe is software that works together with Smart Tiers Z to help users manage the data on volumes tiered to multiple kinds of storage media, such as SSD, SAS, and SATA. Data saved on tiered volumes can be relocated to the appropriate tier based on the access frequency by a process called tier relocation.
PAGE 14
Figure 2 Locating data in a specified tier according to performance requirements If only Smart Tiers Z is being used, a storage administrator uses either Remote Web Console or RAID Manager to manage storage on a pool or volume basis.
PAGE 15
Figure 3 Tier management using Smart Manager for Mainframe Overview of the Smart Manager for Mainframe functionality The functionality provided by Smart Manager for Mainframe features tier management based on tiering policy groups. It also features tier management in conjunction with SMS, and acquisition of configuration information of storage systems.
PAGE 16
Related topics • About tiering policy groups, page 16 Terms used in Smart Manager for Mainframe This section describes the terms used in Smart Manager for Mainframe. 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 group basis.
PAGE 17
Figure 5 Overview of tiering policies A tiering policy can be specified by using a tiering policy information CSV file.
PAGE 18
Figure 6 When the tiering policy level of 1 is specified for a three-tier volume 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, as shown in the figure below. After pages are moved, these pages are moved between tiers 1 and 2 according to the access frequency each time tier relocation is performed.
PAGE 19
For the tiers with a specified tiering policy level, the priority assigned to new pages is determined by the combination of the values specified for the tiering policy 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 pages are assigned in this case.
PAGE 20
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 for REXX on zSeries Release 4 (FMID HWJ9140) • Thin Provisioning Z • Smart Tiers Z System configuration
PAGE 21
Figure 9 System configuration of Smart Manager for Mainframe CAUTION: The storage system must be connected to the z/OS host. Flow of operations The following figure shows the flow of operations for using Smart Manager for Mainframe.
PAGE 22
Figure 10 Flow of operations for using Smart Manager for Mainframe Related topics • Procedure for defining and verifying a tiering policy group, page 60 22 Overview of Smart Manager for Mainframe
PAGE 23
2 Installation and Setup This chapter describes procedures for installing and setting up Smart Manager for Mainframe. Overview of installation and setup The following figure provides an overview of how to install and set up Smart Manager for Mainframe. Figure 11 Overview of installation and setup #1 A user SVC, environment variables, and system symbols of Smart Manager for Mainframe are shared with Business Continuity Manager.
PAGE 24
If you are not using SMP/E for the installation, you do not need to create a backup in the distribution library.
PAGE 25
Transferring the load module to a host machine Transfer the load module for Smart Manager for Mainframe provided on the installation media to a host machine. During the transfer procedure, use the JCLs provided on the installation media to create datasets used for transfers and to extract the provided datasets. The procedure for transferring the load module for Smart Manager for Mainframe, which is provided on the installation media, to a host machine is illustrated in the following figure.
PAGE 26
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 Smart Manager for Mainframe files will be transferred into in the next step. 5. Transfer the Smart Manager for Mainframe object archives from the PC to the mainframe host. In binary mode, transfer the Smart Manager for Mainframe object archives from the PC to the sequential datasets (created in step 4) on the mainframe host. 6.
PAGE 27
• Installing directly from the provided datasets in the target library Related topics • Performing an installation using SMP/E, page 27 • Installing directly from the provided datasets in the target library, page 28 • Appendix D, page 211 Performing an installation using SMP/E Use sample JCLs to perform an installation with SMP/E. 1. Edit the following sample JCLs that will be used for installation in accordance with the user installation environment.
PAGE 28
The following table shows the keyword (FMID) that is required for installing with SMP/E. Table 4 FMID for Smart Manager for Mainframe components FMID Function name CHKLnnn Smart Manager for Mainframe Note The nnn part of CHKLnnn varies depending on the version.
PAGE 29
Attributes of the target libraries are shown in the following table.
PAGE 30
1. Concatenate the load library for LINKLIB HPQKLNKT to LNKLST. You can concatenate by using either of the following methods: • Static method: Specify the load library for LINKLIB HPQKLNKT in the PROGxx 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 HPQKLNKT to the LNKLST.
PAGE 31
• Example of dynamically linking the LINKLIB load library to LNKLST, page 31 Example of dynamically linking the LINKLIB load library to LNKLST This section explains an example of dynamically linking the LINKLIB load library to LNKLST. In this example, the currently-active LNKLST is switched from the original LNKLST 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.
PAGE 32
1. Define profiles for the RACF FACILITY class. The correspondence between profiles defined for the FACILITY class and the available CLI commands are shown in the following table. Table 6 Correspondence between profiles defined for the FACILITY class and the available CLI commands Profile defined for the FACILITY class Available CLI command KTACTTPG KTDCTDEV KTDCTTPG KTIMPORT STGADMIN.YKA.DKT.COMMANDS (Operation profile) KTQRYDEV KTQRYRLC KTQRYTPG KTQSTATS KTSCAN KTIMPORT KTQRYDEV STGADMIN.YKA.DKT.
PAGE 33
Related topics • Settings for using environment configuration commands, page 33 Settings for using environment configuration commands Environment configuration commands (KTALCSVC, KTSETENV, and KTDSPENV) are used for setting up Smart Manager for Mainframe. Set up environment configuration commands so that they can be used. Prerequisites • Settings required for using CLI commands (registration for authentication) To specify the settings required for using environment configuration commands: 1.
PAGE 34
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 system is 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 • Settings for using environment configuration commands To register a use SVC: 1.
PAGE 35
Operations to be performed in the next step • Setting the operating environment for Smart Manager for Mainframe (setting environment variables or system symbols) Related topics • Settings for using environment configuration commands, page 33 • Registering a user SVC using the IEASVCxx parmlib member, page 35 • Setting the operating environment for Smart Manager for Mainframe (setting environment variables or system symbols), page 36 • Notes on when registering a user SVC if Business Continuity Manager is i
PAGE 36
Operations to be performed in the next step • Setting the operating environment for Smart Manager for Mainframe (setting environment variables or system symbols) Related topics • Setting the operating environment for Smart Manager for Mainframe (setting environment variables or system symbols), page 36 • Notes on when registering a user SVC if Business Continuity Manager is installed, page 54 Setting the operating environment for Smart Manager for Mainframe (setting environment variables or system symbols
PAGE 37
Setting items Environment variable System symbols Specifies whether the system logger service is used to collect event logs. LOGPUT &YKLOGPT Specifies whether to output CLI command execution logs to SYSLOG. SYSLOG &YKSYSLG Specified values Default values LOGR: Used SAM: Not used LOGR YES: Output 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.
PAGE 38
START KTSETENV,PARM='YKLCNSE=HPQ1' START KTSETENV,PARM='YKLCNS2=HPQ2' • When specifying whether to use the system logger service to collect event logs 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 to SYSLOG START KTSETENV,PARM='SYSLOG=YES' (if outputting to SYSLOG) START KTSETENV,PARM='SYSLOG=NO' (if not outputting to SYSLOG) TIP: This setting is
PAGE 39
Related topics • • • • • • • • Settings for using environment configuration commands, page 33 Setting the operating environment by using system symbols, page 39 Settings required for registering a license in the ISPF panel, page 40 Notes on setting environment variables or system symbols if Business Continuity Manager is installed, page 55 KTDSPENV, page 121 KTSETENV, page 123 Collecting event logs, page 142 Collecting the CLI command-execution log, page 157 Setting the operating environment by using syst
PAGE 40
CAUTION: System symbols are shared by Smart Manager for Mainframe and Business Continuity Manager. Therefore, you must be careful when setting system symbols in an environment where Business Continuity Manager is installed.
PAGE 41
2. Concatenate the ISPF panel library HPQKPNLT to ISPPLIB DD name. CAUTION: In an environment in which the DBCS function is enabled, you must also concatenate the ISPF panel library HPQKPNLT to ISPPALT (alternate panel library) DD name. For details, see the ISPF User's Guide Volume I. 3. Concatenate the ISPF message library HPQKMSGT to ISPMLIB DD name.
PAGE 42
• To concatenate the panel library HPQKPNLT, message library HPQKMSGT, and table library HPQKTABT, use the LIBDEF service of ISPF. CAUTION: • In an environment in which the DBCS function is enabled, you must also concatenate the ISPF panel library HPQKPNLT to ISPPALT (alternate panel library) DD name, and concatenate the ISPF message library HPQKMSGT to ISPMALT (alternate message library) DD name. For details, see the ISPF User's Guide Volume I.
PAGE 43
Flow of operations for registering a license The following figure shows an flow of operations when registering a license for Smart Manager for Mainframe.
PAGE 44
To create a license information dataset: 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 environment variable 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.
PAGE 45
The following figure provides the procedure for registering a license by using a license key file. Figure 15 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. To register a license by using a license key file 1. Create a license key dataset for transferring a license key file to z/OS.
PAGE 46
4. Enter KTSTART. The Main Menu panel appears. Main Menu Option ===> _________________________________________________________________ HP XP P9000 Smart Manager for Mainframe V.R ----------------------------Enter a selection choice 0 Manage Licenses 1 Exit All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. Copyright (C)2013 Hitachi Data Systems Corporation. All rights reserved. Version v.r.n-mm F1=Help 5. F3=Exit Select option 0 Manage Licenses. The Manage Licenses panel appears.
PAGE 47
6. Enter the name of the license key dataset (LICENSE.KEYS.SAMPLE) in the License Key Dataset Name field, and then press Enter. Manage Licenses Row 1 to 2 of 2 Command ===> _______________________________________________ Scroll ===> PAGE 2013/03/11 19:44:14 Enter the license key information below and press ENTER to install. License Key Dataset Name LICENSE.KEYS.
PAGE 48
TIP: If the license key file contains the license key for Business Continuity Manager, the license key for Business Continuity Manager is also installed. 7. Use the License List in the Manage Licenses panel to confirm that the license has been installed correctly. Manage Licenses Row 1 to 2 of 2 Command ===> _______________________________________________ Scroll ===> PAGE 2013/03/11 19:45:54 Enter the license key information below and press ENTER to install.
PAGE 49
Figure 16 Procedure for registering a license by directly entering a license key Prerequisites • Creating a license information dataset The numbers in the figure correspond to the steps below. To register a license by directly entering a license key: 1. In the ISPF Primary Option Menu panel, select option 6 Command. 2. Enter KTSTART. The Main Menu panel appears. Main Menu Option ===> _________________________________________________________________ HP XP P9000 Smart Manager for Mainframe V.
PAGE 50
4. In the Manage Licenses panel, enter the key code in the Key Code field, and then press Enter. Manage Licenses Row 1 to 2 of 2 Command ===> _______________________________________________ Scroll ===> PAGE 2013/03/11 19:44:14 Enter the license key information below and press ENTER to install.
PAGE 51
The key code you entered is installed as the license key in the license information dataset. 5. Use the License List in the Manage Licenses panel to confirm that the license has been installed correctly. Manage Licenses Row 1 to 2 of 2 Command ===> _______________________________________________ Scroll ===> PAGE 2013/03/11 19:44:14 Enter the license key information below and press ENTER to install.
PAGE 52
1. Execute the KTINSCHK command. From the command execution results, confirm that the setup tasks have been 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 execution results and perform the task that has not been completed.
PAGE 53
Settings required for collecting event logs Specify the settings required for collecting event logs. The specification method varies depending on whether you want to output event logs to the log stream by using the system logger service or to the Smart Manager for Mainframe log dataset without using the system logger service.
PAGE 54
Library type (DD name#) Load library for LINKLIB (HPQKLNKD) Load library for LPALIB (HPQKLPAD) Cataloged procedure library (HPQKPRCD) REXX Exec library, fixed length format (HPQKEXED) REXX Exec library, variable length format (HPQKEXVD) ISPF panel library (HPQKPNLD) ISPF message library (HPQKMSGD) ISPF table library (HPQKTABD) DSORG RECFM LRECL (bytes) BLKSIZE (bytes) PO U - 6,144 PO U - 6,144 PO FB 80 6,160 PO FB 80 6,160 PO VB 255 6,120 PO FB 80 6,160 PO FB 80 6,160 PO FB
PAGE 55
• If the confirmed user SVC version is old and does not satisfy conditions for the prerequisite user SVC version requirement of Smart Manager for Mainframe: Use Business Continuity Manager to delete the user SVC, and then use Smart Manager for Mainframe to register it again. • If the confirmed user SVC version satisfies conditions for the prerequisite user SVC version: You can use the currently enabled user SVC as it is.
PAGE 56
• Preparation for version updating, page 205 Prerequisite user SVC versions for Smart Manager for Mainframe The following table shows the prerequisite user SVC versions for Smart Manager for Mainframe. Table 9 Prerequisite user SVC versions for Smart Manager for Mainframe Smart Manager for Mainframe version Prerequisite user SVC version 7.5.0 7.5.
PAGE 57
3 Smart Manager for Mainframe operation This chapter describes operation of Smart Manager for Mainframe. About files used by Smart Manager for Mainframe This section describes the files used by Smart Manager for Mainframe. Overview of files used by Smart Manager for Mainframe Smart Manager for Mainframe manages disk configurations and tiering policy groups by using information defined in files.
PAGE 58
Figure 17 Relationship between files and commands used in Smart Manager for Mainframe operation 1. Execute the KTSCAN command. Disk configuration information is acquired from the storage system and then stored in a REXX variable structure such as a host-discovered array structure. 2. Execute the KTSTORE command. The disk configuration information stored in the REXX variable structure is saved, and a disk configuration definition file is created. 3. Create a tiering policy information CSV file.
PAGE 59
Figure 18 Configuration example of tiering policy groups Specify the following values when defining this example configuration: • Prefix: PREFIX1 This value will be used as the file name prefix for configuration files and tiering policy information CSV files. • Policy CSV ID: POLICY1 This value will be used as the file name suffix for tiering policy information CSV files. • Tiering policy group IDs: TPG1 and TPG2 These values will be used as the file name suffixes for tiering policy group definition files.
PAGE 60
Defining and verifying tiering policy groups This section describes how to define a tiering policy group and how to verify the tiering policy group that is created. Procedure for defining and verifying a tiering policy group The figure below shows a general procedure for defining a tiering policy group and verifying the tiering policy group that is created. This figure explains the steps of the procedure, along with the commands and sample scripts to be executed in the procedure.
PAGE 61
• • • • • Creating a tiering policy group definition file, page 65 Applying tiering policies, page 67 Verifying tiering policies, page 68 Checking the progress of tier relocation, page 69 Checking volume I/O performance, page 70 Checking volume information Before defining a tiering policy group, acquire volume information from the storage system by executing the KTQRYDEV command for the volumes to be defined, and then check the volume information.
PAGE 62
DKC SN:14001,Model:VSP,Microcode:xxxxxxxx,IFType:1414 Pool ID, Type,Pool Name 1, DT,POOLID1 ,Media(Tier1,Tier2,Tier3) ,"SSD","SAS 15K","SATA 7.
PAGE 63
2. Execute the KTSTORE command. The data in the host-discovered array structure is saved in the disk configuration definition file. TIP: To view the contents of the disk configuration definition file, execute the KTGETHDA command. Reference scripts For details about how to create the script, see the following sample scripts.
PAGE 64
• KTDEMO00 (Create a disk configuration definition file), page 174 • KTDEMO01 (Display the contents of the disk configuration definition file), page 177 Creating a tiering policy information CSV file Specify information about the SMS storage groups or volumes to be defined as a policy group in a CSV file. For the tiering policy information CSV file, assign a name in the following format: prefix.POLICY.policy-CSV-ID. prefix is a character string specified in the PREFIX parameter of a CLI command.
PAGE 65
Operations to be performed in the next step • Creating a tiering policy group definition file Related topics • Creating a tiering policy group definition file, page 65 • Chapter 5, page 125 Creating a tiering policy group definition file To create a tiering policy group definition file, execute the KTIMPORT command to import the tiering policy information CSV file and disk configuration definition file.
PAGE 66
To create a tiering policy group definition file: • Execute the KTIMPORT command. The command reads the data in the tiering policy information CSV file and disk configuration definition file, and creates a tiering policy group definition 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, and creates a disk configuration definition file and a tiering policy group definition file.
PAGE 67
Applying tiering policies After you have defined a tiering policy group, you must apply the defined tiering policies to the storage system. To apply tiering policies, use the KTLOAD command to load the configuration files to the REXX variable structure, and then execute the KTACTTPG command. Figure 23 Applying tiering policies Prerequisites • Creating a tiering policy group definition file To apply tiering policies: 1. Execute the KTLOAD command.
PAGE 68
Operations to be performed in the next step • Verifying tiering policies Related topics • Creating a tiering policy group definition file, page 65 • Verifying tiering policies, page 68 • KTACTTPG, page 86 • KTLOAD, page 94 • KTDEMO10 (Apply the tiering policy), page 187 Verifying tiering policies By executing the KTQRYTPG command for each tiering policy group, you can acquire from the storage system the tiering policy information that is set to each volume.
PAGE 69
Related topics • • • • • • Creating a tiering policy group definition file, page 65 KTLOAD, page 94 KTQRYDEV, page 97 KTQRYTPG, page 101 KTDEMO04 (Display the volume information), page 183 KTDEMO11 (Check the tiering policy), page 189 Checking the progress of tier relocation By executing the KTQRYTPG command or the KTQRYRLC command, you can acquire the page relocation status of each volume in the tiering policy groups or information about Smart Tiers Z pools.
PAGE 70
Example 2: The following shows an example of information acquired by executing sample script KTDEMO13 (the KTLOAD, KTQRYTPG, and KTQRYRLC commands). This information shows the page relocation status of each volume in the tiering policy group TPG1 and the tier relocation progress for each Smart Tiers Z pool.
PAGE 71
2. Execute the KTQSTATS command. The volume I/O performance information is acquired. Reference scripts For details about how to create the script, see sample script KTDEMO14. Example: The following shows an example of the volume I/O performance information for tiering policy group TPG1 acquired by executing sample script KTDEMO14 (KTLOAD and KTQSTATS commands).
PAGE 72
3. Execute the KTLOAD command. The contents of the configuration files are loaded into REXX variable structures. 4. Execute the KTACTTPG command. Information about the modified tiering policy is applied to the storage system. 5. Execute the KTQRYTPG command to check the tiering policy. Confirm that the tiering policy has been applied to the storage system.
PAGE 73
6. Execute the KTACTTPG command. The contents of the updated configuration files set in the REXX variable structures 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 executing the KTIMPORT command with the SCAN parameter specified, instead of executing the KTSCAN and KTSTORE commands.
PAGE 74
TIP: You can use the KTDCTDEV command to change the tiering policy of volumes applied back to the storage system to the default before deleting the volume from the tiering policy group definition file.
PAGE 75
5. Execute the KTIMPORT command. The command reads the data in the tiering policy information CSV file and disk configuration definition file, and creates a tiering policy group definition file that defines the new disk configuration information.
PAGE 76
Keep the record, but delete the tiering policy parameters. Before the change: #TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc STORGRP,SG1 ,TPG1 ,2 ,HIGH DEVN ,1202 ,TPG1 ,2 ,HIGH After the change: #TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc STORGRP,SG1 ,TPG1 DEVN ,1202 ,TPG1 ,2 ,HIGH The above example changes the tiering policy of volumes in the storage system in the SMS storage group SG1 back to the default.
PAGE 77
This example deletes the record of the volume from the tiering policy information CSV file. After the record is deleted, the tiering policies assigned individually are deleted. The tiering policies that are set to the SMS storage group where the volume belongs are applied.
PAGE 78
Example of adding a volume to the tiering policy group definition The following describes how to add a volume to the tiering policy group definition. 1. Do either of the following: When adding a volume to the SMS storage group #TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc STORGRP,SG1 ,TPG1 ,2 ,HIGH Add a volume to the SMS storage group. You do not need to modify the tiering policy information CSV file.
PAGE 79
Scan the volume where the record is added. CALL KTSCAN CALL KTSTORE 3. "STEM(stem1.) MSG(msgstem.) FROM(1202)", "TO(1202)"; "STEM(stem1.) MSG(msgstem.) PREFIX(PREFIX1)"; Update the tiering policy group definition file to the new definition. CALL KTIMPORT "MSG(msgstem.) PREFIX(PREFIX1) POLICY(POLICY1)"; 4. Apply the updates to the storage system. CALL KTLOAD "STEM(stem1.) MSG(msgstem.) PREFIX(PREFIX1)", "TPG(TPG1)"; CALL KTACTTPG "STEM(stem1.) MSG(msgstem.)"; 5.
PAGE 80
#TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc STORGRP,SG1 ,TPG1 ,2 ,HIGH DEVN ,1202 ,TPG1 ,2 ,HIGH Remove the volume from the SMS storage group. You do not need to modify the tiering policy information CSV file. If the volume to be deleted does not belong to the SMS storage group Delete the record of the volume from the tiering policy information CSV file.
PAGE 81
The above example applies the tiering policy of the SMS storage group SG1 to the volume of device number 1101 (the tiering policy level is 2). Related topics • KTDCTDEV, page 87 • KTIMPORT, page 92 • KTQRYDEV, page 97 • Format of tiering policy information CSV files, page 127 Example of changing a device number The following describes how to change the device number of a volume that belongs to tiering policy group TPG1. 1. 2. Delete the disk configuration definition file.
PAGE 82
• • • • 82 KTLOAD, page 94 KTSCAN, page 104 KTSTORE, page 107 Format of tiering policy information CSV files, page 127 Smart Manager for Mainframe operation
PAGE 83
4 CLI Commands This chapter describes the command functions that can be used in the Smart Manager for Mainframe CLI. List of CLI Commands The CLI commands provided by Smart Manager for Mainframe are categorized 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 11 REXX external routines Command name Description KTACTTPG Applies the tiering policy for a tiering policy group.
PAGE 84
Command name Description KTSCAN Scans the operation-target volumes for Smart Manager for Mainframe to acquire the information necessary to identify the volumes, and then sets the information to the REXX variable structure. • Saves the values of the host-discovered array structure generated by the KTSCAN or KTLOAD command in the disk configuration definition file. KTSTORE • Saves the values of the tiering policy group structure generated by the KTLOAD command in the tiering policy group definition file.
PAGE 85
CLI command coding format This section describes the CLI command coding format for each command type. REXX external routine coding format REXX external routines provided by Smart Manager for Mainframe must be called as subroutines. Therefore, write a REXX script as shown below, 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.
PAGE 86
Use the RC variable to acquire the return code of a TSO/E command in the REXX script. OS console command coding format To execute a CLI command categorized as an OS console command, enter the 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 REXX external routines. The commands are explained in alphabetic order.
PAGE 87
Return codes The following table lists and describes the codes returned when the KTACTTPG command terminates. If the commands do not terminate normally, refer to the resulting error messages for details. Table 14 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 variable structure. 40 An error occurred during writing of the REXX variables.
PAGE 88
• Tiering policy level: 0 • New-page assignment tier: MIDDLE • Whether to execute tier relocation: Y Command type REXX external routine Format KTDCTDEV 1MSG(stem-name-1) 1DEVN(nnnn) Parameters MSG(stem-name-1)~ Specify the prefix (any value) of the message structure that stores messages generated by this command. This value must end with a period.
PAGE 89
REXX variables that are updated by the KTDCTDEV command • All variables in the message structure Related topics • Message structure, page 131 • KTDEMO05 (Change the tiering policy of a volume back to the default), page 186 KTDCTTPG Function Changes the tiering policy for a tiering policy group back to the following default values.
PAGE 90
Return code Meaning 36 The command ended due to an invalid REXX variable structure. 40 An error occurred during writing of the REXX variables. 44 The command ended due to invalid processing. The command ended due to an invalid parameter. The possible causes are as follows: • The parameters were specified incorrectly. 48 • 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.
PAGE 91
1PREFIX(prefix) 1SN(serial-number) Parameters STEM(stem-name-1)~ Specify the prefix (any value) of the host-discovered array structure to which the information will be loaded from the disk configuration definition file. This value must end with a period. MSG(stem-name-2)~ Specify the prefix (any value) of the message structure that stores messages generated by this command. This value must end with a period.
PAGE 92
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.". • The following variables in the host-discovered array structure A REXX variable name is preceded by the value specified for the STEM parameter. • LOCAL.SNnnnnn.SerialNum • LOCAL.SNnnnnn.Microcode • LOCAL.SNnnnnn.IFType • LOCAL.SNnnnnn.PhysicalSerialNum • LOCAL.SNnnnnn.
PAGE 93
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 in advance 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.
PAGE 94
Return codes The following table lists and describes the codes returned when the KTIMPORT command terminates. If the commands do not terminate normally, refer to the resulting error messages for details. Table 18 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 CSV file. Writing to the tiering policy group definition file was not performed.
PAGE 95
• Loads the disk configuration definition file to the host-discovered array structure and host-discovered array index structure. Command type REXX external routine Format KTLOAD 1STEM(stem-name-1) 1MSG(stem-name-2) 1PREFIX(prefix) 1TPG(tiering-policy-group-ID) Parameters STEM(stem-name-1)~ Specify the prefix (any value) of the REXX variable structure to which the information will be loaded from the configuration file. This value must end with a period.
PAGE 96
Return code Meaning 48 The command ended due to an invalid parameter. The possible cause is as follows: • The parameters were specified incorrectly. The command ended due to an incorrect execution method. The possible causes are as follows: 52 • The MSG parameter was specified incorrectly. • Installation was not performed correctly.
PAGE 97
• TPG.VOL.n.SSID • TPG.VOL.n.TierLevel • TPG.VOL.n.TierRelocation Related topics • • • • • Message structure, page 131 Host-discovered array index structure, page 132 Host-discovered array structure, page 133 Tiering policy group structure, page 138 KTDEMO03 (Display the contents of the tiering policy group definition file), page 181 KTQRYDEV Function Acquires the following information about the specified volume from the storage system, and then stores the information in the REXX variable structure.
PAGE 98
Return codes The following table lists and describes the codes returned when the KTQRYDEV command terminates. If the commands do not terminate normally, refer to the resulting error messages for details. Table 20 Return codes generated by the KTQRYDEV command Return code Meaning 0 The command ended normally. 32 An I/O error occurred. 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.
PAGE 99
• LOCAL.SNnnnnn.POOLxx.NAME • LOCAL.SNnnnnn.POOLxx.Type • LOCAL.SNnnnnn.POOLxx.PageSize • LOCAL.SNnnnnn.POOLxx.Tier.0 • LOCAL.SNnnnnn.POOLxx.Tier.n.Media • 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.
PAGE 100
Format KTQRYRLC 1STEM(stem-name-1) 1MSG(stem-name-2) Parameters STEM(stem-name-1)~ Specify the prefix of the tiering policy group structure to which the target tiering policy group information was loaded. This is the character string specified for the STEM parameter of the KTLOAD command that was previously executed. This value must end with a period.
PAGE 101
• In the host-discovered array structure, the following variables related to the Smart Tiers Z pool to which the volumes in the specified tiering policy group belong A REXX variable name is preceded by the value specified for the STEM parameter. • All variables beginning with LOCAL.SNnnnnn.
PAGE 102
Return code Meaning 12 An unsupported device was skipped. 32 An I/O error occurred. 36 The command ended due to an invalid REXX variable structure. 40 An error occurred during writing of the REXX variables. 44 The command ended due to invalid processing. The command ended due to an invalid parameter. The possible causes are as follows: • The parameters were specified incorrectly.
PAGE 103
Command type REXX external routine Format KTQSTATS 1STEM(stem-name-1) 1MSG(stem-name-2) Parameters STEM(stem-name-1)~ Specify the prefix of the tiering policy group structure to which the target tiering policy group information was loaded. This is the character string specified for the STEM parameter of the KTLOAD command that was previously executed.
PAGE 104
REXX variables that are updated by the KTQSTATS command • All variables in the message structure • The following 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.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 A REXX variable name is preceded by the value specified for the STEM parameter. • TPG.
PAGE 105
1{FROM(nnnn) 1TO(nnnn) |FROMVSN(volser) 1TOVSN(volser) |STORGRP(SMS-storage-group-name) } [ 1ARRAYS(stem-name-3)] Parameters STEM(stem-name-1)~ Specify the prefix (any value) of the host-discovered array structure that stores the scan results. This value must end with a period. MSG(stem-name-2)~ Specify the prefix (any value) of the message structure that stores messages generated by this command.
PAGE 106
• If information about the volumes in the detection range already exists in the 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.
PAGE 107
• LOCAL.SNnnnnn.CUxx.CCAxx.Volser • LOCAL.SNnnnnn.CUxx.CCAxx.STORGRP (set only when the STORGRP parameter is specified) • 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 • LOCAL.SNnnnnn.POOLxx.Tier.n.
PAGE 108
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.
PAGE 109
TIP: If the configuration file already exists when you execute the KTSTORE command, the existing configuration file information and the information stored in the REXX variable structure are merged. The merged information is then saved to a newly allocated dataset. Therefore, the VOLUME parameter and the SPACE parameter are enabled when the configuration file is updated.
PAGE 110
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 array structure are saved in the disk configuration definition file. A REXX variable name is preceded by the value specified for the STEM parameter. • LOCAL.SNnnnnn.SerialNum • LOCAL.SNnnnnn.Model • LOCAL.SNnnnnn.Microcode • LOCAL.SNnnnnn.IFType • LOCAL.SNnnnnn.PhysicalSerialNum • LOCAL.SNnnnnn.CUxx.
PAGE 111
KTWTOMSG Function Outputs the specified message ID and message text to the console. Command type REXX external routine Format To output a single-line message: KTWTOMSG 1type,text To output a multi-line message: KTWTOMSG 1type,text-1,text-2[,text-3][,text-4][,text-5] [,text-6][,text-7][,text-8][,text-9][,text-10] Parameters type Specify one of the values shown below as the type of the message to be output. The message will be output with the routing code appropriate for the specified type.
PAGE 112
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 26 Return codes generated by the KTWTOMSG command Return code Meaning 0 The command ended normally. 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.
PAGE 113
Specify the processing type. • OPEN Establish an EMCS console interface for monitoring messages. When the 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 established are returned in order in which they arrived. If no messages have been acquired, either of the following operations is performed.
PAGE 114
Return code Meaning 6 Close processing ended normally. 8 An invalid parameter was specified. 9 A system error occurred. KTENV Function Outputs the program product name and the operating environment settings for Smart Manager for Mainframe to the TSO/E terminal. Command type TSO/E command Format KTENV Return codes The following table lists and describes the codes returned when the KTENV command terminates.
PAGE 115
Output item Description License info DSN prefix Prefix of the license information dataset • LOGR: Event logs are output by using the system logger service. Event log output method • SAM: Event logs are output without using the system logger service. • YES: CLI command-execution logs are output. CLI log output settings • NO: CLI command-execution logs are not output.
PAGE 116
KTERCODE Function Outputs the information for the specified error code and the cause of the error to the TSO/E terminal. Command type TSO/E command Format KTERCODE 1error-code Parameters error-code ~ Specify the sense byte information (error code) for the storage system contained in messages output by Smart Manager for Mainframe. For details about error codes, see the description of storage system sense byte information in the Smart Manager for Mainframe Messages.
PAGE 117
READY KTERCODE 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. KTINSCHK Function Checks the setting items required for setup for incomplete or incorrect information, and then outputs a message showing the check results and the settings. Command type TSO/E command Format KTINSCHK Return codes The following table lists and describes the codes returned when the KTINSCHK command terminates.
PAGE 118
Output item Description • OK: There are no problems with registration of the user SVC. User SVC Routine • FAULTY: There are problems with registration of the user SVC.
PAGE 119
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 - 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.
PAGE 120
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 Format KTSLEEP 1{SEC(timeout-value)|MIN(timeout-value)} Parameters SEC(timeout-value)~((1-9999)) Specify the period of time in seconds during which the script is suspended. MIN(timeout-value)~((1-9999)) Specify the period of time in minutes during which the script is suspended.
PAGE 121
KTALCSVC Function Use this command to register or delete a user SVC. Command type OS console command 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 ~ ((from 200 to 255)) Specify a SVC number to be assigned for the user SVC. DELETE Specify this parameter to delete a user SVC.
PAGE 122
Command type OS console command Format START 1KTDSPENV [,PARM='[{SUMMARY|DETAIL}]'] 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 information dataset, the information about whether to use the system logger service, and the information about whether to output CLI command-execution logs to SYSLOG.
PAGE 123
START KTDSPENV,PARM='DETAIL' KTA403I HP XP P9000 Smart Manager for Mainframe KTA400I Environment variables (v.r.m-nn(zz)) KTA401I License info DSN prefix: HPQ1.HPQ2 KTA401I Event log output method: SAM KTA401I CLI log output settings: NO KTA402I YKLCNSE = HPQ1 (&YKLCNSE = N/A KTA402I YKLCNS2 = HPQ2 (&YKLCNS2 = N/A KTA402I LOGPUT = SAM (&YKLOGPT = "LOGR" KTA402I SYSLOG = NO (&YKSYSLG = "YES" ) ) ) ) KTSETENV Function Use this command to set the following values using environment variables.
PAGE 124
• SAM Event logs are output to a sequential dataset without using the system logger service. To remove the value of the environment variable LOGPUT, specify PARM='LOGPUT='. SYSLOG=[YES|NO] Specify whether CLI command-execution logs are output to SYSLOG. • YES CLI command-execution logs are output to SYSLOG. • NO CLI command-execution logs are not output to SYSLOG. To remove the value of the environment variable SYSLOG, specify PARM='SYSLOG='.
PAGE 125
5 Files used by Smart Manager for Mainframe This chapter describes the files used by Smart Manager for Mainframe. File naming conventions used by Smart Manager for Mainframe The following table describes the file naming conventions for files used by Smart Manager for Mainframe. Table 37 File naming conventions used by Smart Manager for Mainframe File type File name Tiering policy information CSV file prefix.POLICY.policy-CSV-ID Disk configuration definition file prefix.DSK.SNnnnnn.
PAGE 126
The following table shows the maximum length and the permitted characters for items in the filenames used by Smart Manager for Mainframe. Table 38 Maximum length and permitted characters for items in filenames used by Smart Manager for Mainframe Item Maximum length Permitted characters Prefix 25 A string consisting of one or more parts, joined by periods. Each part can contain from one to eight characters, and consist of uppercase alphabetic and numeric characters.
PAGE 127
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 policy information 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.
PAGE 128
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 group ID that can be specified is 44 - (5 + length-of-character-string-specified-for-prefix). tiering-policy-level ~ ((0|1|2|3|4|5)) <<0>> Specifies a numeric characters as the tiering policy level (that determines the tiers in which data is to be located) to be set for the specified volume.
PAGE 129
Tiering policy level Value of the new-page assignment tier setting HIGH MIDDLE LOW Description 2 1>2>3 1>2>3 2>1>3 If LOW is set, Tier 2 is given higher priority than Tier 1. 3 2>3>1 2>3>1 2>3>1 Because only one tier applies to this level, 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 higher priority than Tier 2.
PAGE 130
Examples • Example of defining multiple volumes for different tiering policies #TYPE DEVN DEVN ,DEVICE,TPGID,TierLvl,Entry,Reloc ,1101 ,TPG1 ,1 ,1102 ,TPG1 ,5 • Example of defining an SMS storage group and a volume belonging to that SMS storage group #TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc STORGRP,SG1 ,TPG1 ,2 ,HIGH DEVN ,1101 ,TPG1 ,1 ,LOW The record that specifies a specific volume takes priority.
PAGE 131
6 REXX Variable Structures This chapter describes the REXX variable structures used by Smart Manager for Mainframe. List of REXX variable structures REXX variable structures are variables expanded by executing a CLI command. REXX variable structures store the values loaded from Smart Manager for Mainframe configuration files, information acquired from the storage system, and the results of CLI commands. These structures are also used for passing information between CLI commands.
PAGE 132
REXX variable names and contents The following table lists and describes the REXX variables in the message structure. A REXX variable name is preceded by the prefix of the structure name. Table 45 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.
PAGE 133
REXX variable name Description n. Information for each storage system is stored in lower-level REXX variables. SerialNum Serial number of the scanned storage system DADID Fixed character string LOCAL is stored. Prefix Prefix of the host-discovered array structure from which the last period is removed Map information obtained from the pool IDs POOLMap 1 is set for the position corresponding to the pool ID. The first value indicates pool ID 00.
PAGE 134
REXX variable names and contents 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 47 Host-discovered array structure REXX variable name Description LOCAL.SNnnnnn. Information for each storage system is stored in lower-level REXX variables. nnnnn indicates the storage system serial number.
PAGE 135
REXX variable name Description SSID Storage system ID POOLID Pool ID (decimal number) Cyls Volume capacity (number of cylinders) External volume information • Y: External volume External • N: Not an external volume N is always specified for Smart Tiers Z volumes or Thin Provisioning Z volumes. Tiering policy level TierLevel New-page assignment tier • HIGH: The new page is assigned from the higher tier of tiers set in the tiering policy.
PAGE 136
REXX variable name Description LOCAL.SNnnnnn.POOLxx.
PAGE 137
REXX variable name Description Used Used tier capacity Unit Unit of the total tier capacity and used tier capacity EntryBufferPerCent Free area ratio for new-page assignment (%). This is the percentage of free area allocated for each tier to which new pages can be assigned during relocation. RelocateBufferPerCent MigratedPageCtPercentage of the buffer area used for relocation (%) m. m indicates the migration-source tier number.
PAGE 138
Tiering policy group structure The values to be set for the storage system for the volumes belonging to a tiering policy group are stored in the tiering policy group structure. When the structure is created The KTLOAD command is executed (the structure is created by loading information from the tiering policy group definition file). Prefix of the structure name The prefix of the tiering policy group structure name is the value specified for the STEM parameter of each command.
PAGE 139
REXX variable name Description Whether to execute tier relocation TierRelocation • 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 been issued only one time, 0 is set.
PAGE 140
REXX Variable Structures
PAGE 141
7 Collecting trace information and logs This chapter describes collecting trace information and logs for Smart Manager for Mainframe. 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 for troubleshooting.
PAGE 142
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 to the READY mode, press the Enter key. If you enter a TSO/E command without pressing the Enter key, ABEND dumps might not be output.
PAGE 143
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, and then use the Smart Manager for Mainframe tool to output the event logs from the log stream to a dataset. • Output event logs to a Smart Manager for Mainframe log dataset without using the system logger service.
PAGE 144
Figure 24 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, page 144 • Collecting event logs without using the system logger service, page 153 Collecting event logs by using the system logger service This section describes how to collect event logs when the system logger service is used.
PAGE 145
Related topics • • • • • Setting LOGR couple data sets, page 145 Defining the SMS for the system logger service, page 145 Defining a log stream, page 145 Setting access privileges for system logger resources, page 146 Starting the system logger service, page 146 Setting LOGR couple data sets In a sysplex environment, format the LOGR couple datasets and then define them for the sysplex.
PAGE 146
Setting access privileges for system logger resources If the System Authorization Facility (SAF) can be used, grant access privileges to users who execute Smart Manager for Mainframe commands because the system performs SAF checks for each request. The following access privileges must be granted. • CLASS: FACILITY RESOURCE: MVSADMIN.
PAGE 147
• 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 be changed.
PAGE 148
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.
PAGE 149
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, see the manual MVS Setting Up a Sysplex.
PAGE 150
Related topics • Starting the system logger service, page 146 • Parameters specified when a log stream is defined, page 146 • JCL example for deleting a log stream, page 148 Disk space requirements for the event log when the system logger service is used The following table shows the amount of log data when the system logger service is used to output the event log.
PAGE 151
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 maximum block length is 32,760 bytes. TIP: To merge event log data activated by multiple OSs in a sysplex environment, 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.
PAGE 152
Format of the RANGE control statement RANGE{ 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>> <> Use the local time to specify the start date and time of the log data to be output.
PAGE 153
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.
PAGE 154
2. Create log datasets. For the log dataset, specify the amount of the initial allocation only. The specification 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.
PAGE 155
When both YKLOG01 and YKLOG02 are specified 1. 2. 3. 4. Logs are written to YKLOG01. If the log dataset is reused, logs are added to the end of the previous log output. If YKLOG01 is full, logs are written to YKLOG02. If YKLOG02 is also full, logs are written to YKLOG01. In this case, the existing logs in YKLOG01 are overwritten. Steps 2 and 3 are repeated.
PAGE 156
Disk space requirements for the event log when the system logger service is not used The following table shows the amount of log data when the event log is output without using the system logger service.
PAGE 157
2. When you perform an operation in the Smart Manager for Mainframe 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 to prevent the ISPF log dataset from becoming full.
PAGE 158
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:00 PRINT CLOSE 4. Use the ISPF editor to display a panel for editing the dataset created in step 3. 5. In the ISPF editor panel, enter the following command to delete the lines other than the CLI command-execution logs.
PAGE 159
5. Execute the CLI command-execution log output procedure to extract the CLI 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. EXEC 'YUKON.EXTCMD' 'KTC31 YUKON.SYSLOG YUKON.
PAGE 160
Collecting trace information and logs
PAGE 161
8 Support and other resources Numerous support options are available. Contacting HP HP technical support For worldwide technical support information, see the HP support website: http://www.hp.
PAGE 162
Conventions This guide follows the conventions shown in Table 56 to refer to HP P9000 products.
PAGE 163
Product reference Full name or meaning JCL Job Control Language LDEV Logical DEVice LRECL Logical RECord Length MIH Missing Interrupt Handler OS Operating System RACF Resource Access Control Facility RAID Redundant Array of Independent Disks RECFM RECord ForMat REXX REstructured eXtended eXecutor ROI Return On Investment SAF System Authorization Facility SAS Serial Attached SCSI SATA Serial Advanced Technology Attachment SCSI Small Computer System Interface SLA Service Level A
PAGE 164
Support and other resources
PAGE 165
A XML document type definitions for configuration files This appendix describes the XML document type definitions for configuration files used by Smart Manager. Elements common to configuration files The following describes the elements common to all types of configuration files. Note that element names, attribute names, and attribute values are case sensitive. APIInfo element The APIInfo element contains information about the configuration file.
PAGE 166
SSID CCA POOLID Cyls External CDATA#REQUIRED CDATA#REQUIRED CDATA#IMPLIED CDATA#IMPLIED (Y|N)#IMPLIED > The following lists and describes the attributes of this element.
PAGE 167
Attribute name Description 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.
PAGE 168
Attribute name Description Pool type information: DT: Smart Tiers Z pool Type DP: Thin Provisioning Z pool OTHER: Other pools PageSize Page size PoolTier element Information about tiers is stored in the PoolTier element. Structure The following lists and describes the attributes of this element.
PAGE 169
Volser STORGRP CDATA#IMPLIED CDATA#IMPLIED > The following lists and describes the attributes of this element. Attribute name Description 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 element Information about tiering policy groups is stored in the TieringPolicyGroup element.
PAGE 170
Attribute name Description Level Tiering policy level New-page assignment tier • HIGH: The new page is assigned from the higher tier of tiers set in the tiering policy. Entry • 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. Tier relocation TierRelocation • Y: Executes tier relocation for the volume. • N: Does not execute tier relocation for the volume.
PAGE 171
Example of a disk configuration definition file that is generated PAGE 172
XML document type definitions for configuration files
PAGE 173
B Sample scripts This appendix provides sample scripts for Smart Manager for Mainframe. List of sample scripts Sample scripts for each CLI command are stored in the sample library. The following table provides an overview of each sample script. Table 57 Overview of sample scripts Sample script name Purpose KTDEMO00 Create a disk configuration definition file.
PAGE 174
Sample script name Purpose KTDEMO12 Check the page relocation status of volumes. Command to be executed DD name specification or parameter Relevant REXX variable structure KTLOAD PREFIX(prefix) Host-discovered array structure KTQRYTPG TPG(tiering-policy-group-ID) Tiering policy group structure PREFIX(prefix) Host-discovered array index structure TPG(tiering-policy-group-ID) Host-discovered array structure KTLOAD Check the relocation progress. KTDEMO13 Check I/O performance information.
PAGE 175
/* 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 */ /* in the script's argument. */ /* */ /**********************************************************************/ /* Sample script begins. */ SAY "#-- BEGIN KTDEMO00.
PAGE 176
SAY 'Executing KTSCAN STORGRP= 'scan_from; CALL KTSCAN "STEM(DEMO_STEM.) MSG(DEMO_MSG.) ARRAYS(DEMO_SCAN.)", " STORGRP("scan_from")"; END; ELSE DO SAY 'Ignore KTINDD LINE='recordStr ITERATE; END; /* * Check the return code to see if it is 0 or not. */ IF RESULT > 8 THEN ScanFailed='Y'; ELSE IF RESULT < 8 THEN ScannedVolumeIsFound='Y'; IF RESULT > 0 THEN CALL printErrorMessage "KTSCAN" RESULT; END; IF ScanFailed='Y' THEN DO SAY 'KTSCAN error occurred.
PAGE 177
KTDEMO01 (Display the contents of the disk configuration definition file) /* 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.
PAGE 178
/* 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.
PAGE 179
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.
PAGE 180
ARG mediaTypeValue; IF mediaTypeValue = '0000' THEN mediaTypeStr = 'SSD'; ELSE IF mediaTypeValue = '0001' THEN mediaTypeStr = 'SAS 15K'; ELSE IF mediaTypeValue = '0002' THEN mediaTypeStr = 'SAS 10K'; ELSE IF mediaTypeValue = '0003' THEN mediaTypeStr = 'SATA 7.2K'; ELSE IF mediaTypeValue = '0004' THEN mediaTypeStr = 'EXTERNAL M'; ELSE IF mediaTypeValue = '0005' THEN mediaTypeStr = 'SAS 7.
PAGE 181
PARSE UPPER ARG @options PARSE UPPER VALUE @options 'POLICY()' PARSE UPPER VALUE @options 'PREFIX()' with 'POLICY('opt_policyid')'; with 'PREFIX('opt_prefix')'; /* * Check option values in the argument. */ IF opt_policyid = '' THEN DO SAY "Please specify POLICY() value in the argument."; EXIT 8; END; IF opt_prefix = '' THEN DO SAY "Please specify PREFIX() value in the argument."; EXIT 8; END; /* * Parse tiering policy information CSV file * and create TPG configuration file(s).
PAGE 182
/* 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.
PAGE 183
/* * 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.
PAGE 184
/* displays storage information of the target volume's DKC.*/ /* */ /* This sample script uses the following CLI commands. */ /* - KTQRYDEV */ /* */ /* 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.
PAGE 185
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' THEN TierCt = 0; DO t=1 to TierCt; /* Get pool's drive media information.
PAGE 186
*/ printErrorMessage: procedure expose DEMO_MSG. ARG cli_name cli_result; SAY "Command name=" || cli_name || ",result=" || cli_result; IF DATATYPE(DEMO_MSG.0) = 'NUM' THEN DO 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 * (LOCAL.SNnnnnn.POOLxx.Tier.n.Media in the DSK structure) * to media type description string.
PAGE 187
/* 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 @options PARSE UPPER VALUE @options 'DEVN()' with 'DEVN('opt_devn')'; /* * Check option values in the argument.
PAGE 188
/* */ /**********************************************************************/ /* */ /* 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.
PAGE 189
IF RESULT /= 0 THEN DO CALL printErrorMessage "KTACTTPG" RESULT; EXIT 8; END; SAY "#-- END KTDEMO10."; /* 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' THEN DO x = 1 to DEMO_MSG.0; SAY "Severity = " || DEMO_MSG.x.
PAGE 190
/* * Check option values in the argument. */ IF opt_tpgid = '' THEN DO SAY "Please specify TPG() value in the argument."; EXIT 8; END; IF opt_prefix = '' THEN DO SAY "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.
PAGE 191
* 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.
PAGE 192
/* 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 KTDEMO12.
PAGE 193
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; 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.
PAGE 194
DO 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.
PAGE 195
*/ 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 DO CALL 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. */ CALL KTQRYTPG "STEM(DEMO_STEM.) MSG(DEMO_MSG.)"; /* * Check the return code to see if it is 0 or not.
PAGE 196
*/ val_Devn val_Volser val_POOLID val_TLv val_pageCt = = = = = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Devn; DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Volser; DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.POOLID; DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.TierLevel; DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Used; volTierCt = DEMO_STEM.LOCAL.sym_SN.sym_CU.sym_CCA.Tier.
PAGE 197
TierRangePageCt = 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 DO ReservedPerCent = 0; IF DATATYPE(, DEMO_STEM.LOCAL.sym_SN.sym_POOLID.Tier.t.
PAGE 198
IF TierRangeUsed >= TierRangeCapacity - TierRangeReserved THEN relocateStatus = 'capacity shortage '; ELSE IF val_RelocatePerCent = 100 THEN relocateStatus = 'relocate waiting '; ELSE relocateStatus = '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.
PAGE 199
/* * 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; /* Find next pool from POOLMap. */ pos_POOLID = POS('1', val_POOLMap, pos_POOLID+1); END; END; /* * Display relocation progress status per tier of the pool.
PAGE 200
/* Find next pool from POOLMap. */ pos_POOLID = POS('1', val_POOLMap, pos_POOLID+1); END; END; SAY "#-- END KTDEMO13."; /* 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' THEN DO x = 1 to DEMO_MSG.
PAGE 201
/* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. */ /* */ /**********************************************************************/ /* */ /* KTDEMO14 - A sample demonstration script that */ /* displays volume I/O statistics. */ /* */ /* This sample script uses the following CLI commands. */ /* - KTLOAD */ /* - KTQSTATS */ /* */ /* This sample script assumes the following settings. */ /* 1) TPG and DSK configuration dataset is already created.
PAGE 202
/* * 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.
PAGE 203
/DEMO_STEM.TPG.VOL.IO.Interval; IF TRUNC(val_iops.j) /= val_iops.j THEN DO; IF val_iops.j < 100 THEN val_iops.j = TRUNC(val_iops.j,3); ELSE val_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 syscall "sleep" opt_interval END; SAY "#-- END KTDEMO14.
PAGE 204
Sample scripts
PAGE 205
C Version Updating This appendix describes how to update the version of Smart Manager for Mainframe. Overview of version updating The following figure shows an overview of updating the version of Smart Manager for Mainframe. Figure 26 Overview of version updating # 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 are prerequisites for Smart Manager for Mainframe after version updating.
PAGE 206
Checking the setting values of the operating environment Check the setting values of the operating environment that will be used for an installation of the new version. • Execute the KTDSPENV command as shown below: START KTDSPENV,PARM='DETAIL' The values set for the environment variables and system symbolic names listed in the following table are displayed.
PAGE 207
Deleting the user SVC by using the KTALCSVC environment setup command You must delete a user SVC before version updating and assign the same SVC number after version updating if the currently enabled user SVC version is older than the prerequisite user SVC version of Smart Manager for Mainframe after version updating. If a dynamic user SVC has been registered by using the KTALCSVC environment setup command, use the KTALCSVC command to delete the user SVC. 1.
PAGE 208
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 version updating. CAUTION: A user SVC is shared by Smart Manager for Mainframe and Business Continuity Manager. Therefore, in a system where Business Continuity Manager is installed, make sure that Business Continuity Manager is not running before deleting the user SVC.
PAGE 209
NOTE: • If a task requiring re-IPL was performed during preparation for version updating, always perform re-IPL before starting the procedure for updating the version. • If sample JCL HPQKT2DF, which defines the distribution library and target library, terminated abnormally during installation using SMP/E and GIM35601E ** DATASET SUBENTRY WAS NOT ADDED BECAUSE IT ALREADY EXISTS. was output, change the ADD command in HPQKT2DF to the REP command, and then execute HPQKT2DF again.
PAGE 210
Version Updating
PAGE 211
D Modifying the sample JCL This appendix provides examples of how to modify the sample JCL. Values used in the sample JCL modification examples Prefixes for the dataset names and volumes allocated to the datasets used in the 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 HPQ1.KT. SMP001 Target library HPQ1.
PAGE 212
//********************************************************************* //* //* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. //* //********************************************************************* //* //* This JCL allocates data sets in preparation for storing //* the data files for installation of Smart Manager for MF from the //* distribution CD. //* //* Instructions: //* 1. Change 'HP' to the current USERID. //* 2. Change '#tso01' to VOLSER of your device. //* 3.
PAGE 213
// // //F3 // // // // //F4 // // // // //F5 // // // // //F6 // // // // //F7 // // // // //F8 // // // // //F9 // // // // DD DD DD DD DD DD DD DCB=(DSORG=PS,RECFM=FB,LRECL=80,BLKSIZE=3120), DISP=(,CATLG,DELETE) 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) 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) DSN=&PFX..&VRM..
PAGE 214
//* //* All Rights Reserved. Copyright (C) 2013, 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 'HP.' prefixes to suit your naming convention. //* 3.
PAGE 215
VOLUME(#tso01) RECEIVE INDSN(CHKLnnn.F5.XMIT) DSNAME('HP.CHKLnnn.F5') + VOLUME(#tso01) RECEIVE INDSN(CHKLnnn.F6.XMIT) DSNAME('HP.CHKLnnn.F6') + VOLUME(#tso01) RECEIVE INDSN(CHKLnnn.F7.XMIT) DSNAME('HP.CHKLnnn.F7') + VOLUME(#tso01) RECEIVE INDSN(CHKLnnn.F8.XMIT) DSNAME('HP.CHKLnnn.F8') + VOLUME(#tso01) RECEIVE INDSN(CHKLnnn.F9.XMIT) DSNAME('HP.CHKLnnn.
PAGE 216
//* ----------------------------------------// SET IPFX=HP Prefix of distribution data sets -----(4) // SET IVRM=CHKLnnn Version of distribution data sets // SET TPFX=HP 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 datasets //INF1 DD DSN=&IPFX..&IVRM..
PAGE 217
COPY COPYMOD COPYMOD COPY COPY COPY COPY COPY COPY OUTDD=OUTF1,INDD=INF1 OUTDD=OUTF2,INDD=INF2 OUTDD=OUTF3,INDD=INF3 OUTDD=OUTF4,INDD=INF4 OUTDD=OUTF5,INDD=INF5 OUTDD=OUTF6,INDD=INF6 OUTDD=OUTF7,INDD=INF7 OUTDD=OUTF8,INDD=INF8 OUTDD=OUTF9,INDD=INF9 /* SMPALLOC (allocating SMP/E datasets) The method for modifying SMPALLOC, which allocates SMP/E datasets, is described below. The following numbers correspond to the numbers appearing on the right side of the sample JCL.
PAGE 218
DEFINE CLUSTER( NAME(HPQKT.SMPCSI.CSI) FREESPACE(10 5) KEYS(24 0) RECORDSIZE(24 143) SHAREOPTIONS(2 3) UNIQUE VOLUMES(#smp01) - -----(7) - NAME(HPQKT.SMPCSI.CSI.DATA) CONTROLINTERVALSIZE(4096) CYLINDERS(1 1) ) INDEX( NAME(HPQKT.SMPCSI.CSI.INDEX)CYLINDERS(1 1) ) -----(8) ) DATA( -----(9) -----(10) /* //* //* 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.
PAGE 219
//SMPLOGA // // // // DD DSN=&PFX..SMPLOGA, DISP=(NEW,CATLG,DELETE), UNIT=SYSDA,VOL=SER=&VSN, SPACE=(CYL,(1,5)), DCB=(BLKSIZE=32720,LRECL=80,RECFM=FB) HPQKT1AL (allocating the distribution library and target library) The method for modifying HPQKT1AL, which allocates the distribution library and target library, is described below. The following numbers correspond to the numbers appearing on the right side of the sample JCL.
PAGE 220
//HPQKLNKT DD DSN=&PFX..&VRM..HPQKLNKT, LOAD LIBRARY // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=&TVSN, // SPACE=(TRK,(75,1,20)), // DCB=(BLKSIZE=6144,RECFM=U) //HPQKLPAT DD DSN=&PFX..&VRM..HPQKLPAT, LPA LIBRARY // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=&TVSN, // SPACE=(TRK,(1,1,1)), // DCB=(BLKSIZE=6144,RECFM=U) //HPQKPRCT DD DSN=&PFX..&VRM..
PAGE 221
// //HPQKEXED // // // // //HPQKEXVD // // // // //HPQKPNLD // // // // //HPQKMSGD // // // // //HPQKTABD // // // // DD DD DD DD DD DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) DSN=&PFX..&VRM..HPQKEXED, EXEC(F) LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER=&DVSN, SPACE=(TRK,(45,1,10)), DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) DSN=&PFX..&VRM..HPQKEXVD, EXEC(V) LIBRARY DISP=(NEW,CATLG,DELETE), UNIT=3390,VOL=SER=&DVSN, SPACE=(TRK,(45,1,10)), DCB=(BLKSIZE=6120,LRECL=255,RECFM=VB) DSN=&PFX..&VRM..
PAGE 222
//* All Rights Reserved. Copyright (C) 2013, 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.
PAGE 223
ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL. SET UCLIN. ADD ADD ADD GLOBALZONE ZONEINDEX( (DLIB1,HPQKT.SMPCSI.CSI,DLIB), (TGT1,HPQKT.SMPCSI.CSI,TARGET)) SREL(Z038). DDDEF(SMPPTS) DA(HPQKT.SMPPTS) OLD. DDDEF(SMPLOG) DA(HPQKT.SMPLOG) MOD. DDDEF(SMPLOGA) DA(HPQKT.SMPLOGA) MOD. DDDEF(SMPTLIB) DSPREFIX(HPQKT.TM) VOLUME(#smp01) UNIT(3390) CYL SPACE(5,5) DIR(200) DSNTYPE(PDS). DDDEF(HPQKSAMT) DA(HPQKT.Vnnnnnn.HPQKSAMT) OLD. DDDEF(HPQKLNKT) DA(HPQKT.Vnnnnnn.HPQKLNKT) OLD.
PAGE 224
ADD DDDEF(HPQKLPAT) DA(HPQKT.Vnnnnnn.HPQKLPAT) OLD. DDDEF(HPQKPRCT) DA(HPQKT.Vnnnnnn.HPQKPRCT) OLD. DDDEF(HPQKEXET) DA(HPQKT.Vnnnnnn.HPQKEXET) OLD. DDDEF(HPQKEXVT) DA(HPQKT.Vnnnnnn.HPQKEXVT) OLD. DDDEF(HPQKPNLT) DA(HPQKT.Vnnnnnn.HPQKPNLT) OLD. DDDEF(HPQKMSGT) DA(HPQKT.Vnnnnnn.HPQKMSGT) OLD. DDDEF(HPQKTABT) DA(HPQKT.Vnnnnnn.HPQKTABT) OLD. ADD ADD ADD ADD ADD ADD ENDUCL. SET UCLIN. ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL.
PAGE 225
HPQKT3RC (SMP/E RECEIVE processing) The method for modifying HPQKT3RC, which performs SMP/E RECEIVE processing, is explained below. The following numbers correspond to the numbers appearing on the right side of the sample JCL. (1) to (3) Modify the JOB statement in accordance with the installation environment. (4) Change the prefix for the dataset name from HPQKT to HPQ1.KT. (5) Change the volume allocated to the SMP/E dataset from #smp01 to SMP001. (6) Change RFPREFIX from HP to HPQ1.KT.
PAGE 226
// 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
PAGE 227
//HPQKT4AP JOB (ACCT#),'APPLY SMART MGR Z', -----(1) // REGION=0M,CLASS=A, -----(2) // MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID -----(3) //********************************************************************* //* //* All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd. //* //********************************************************************* //* //* This JCL executes SMP/E APPLY to create the target libraries. //* //* Instructions: //* 1) Modify the JOB statement to match your environment.
PAGE 228
//GLOBAL //TGT1 //DLIB1 //SMPTLIB //SMPHOLD //SMPSCDS //SMPMTS //SMPSTS //SYSLIB // //SMPCNTL SET APPLY DD DISP=SHR,DSN=&PFX..SMPCSI.CSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI DD DISP=SHR,DSN=&PFX..SMPCSI.CSI DD DISP=SHR,UNIT=3390,VOL=SER=&VSN DD DUMMY DD DISP=SHR,DSN=&PFX..SMPSCDS DD DISP=SHR,DSN=&PFX..SMPMTS DD DISP=SHR,DSN=&PFX..SMPSTS DD DISP=SHR,DSN=SYS1.MACLIB DD DISP=SHR,DSN=&PFX..SMPMTS DD * BDY(TGT1). SELECT(CHKLnnn) CHECK .
PAGE 229
//* //* 3) Submit the JCL and make sure that no error occurs. //* 4) Remove CHECK operand from ACCEPT and re-submit the JCL to //* complete.
PAGE 230
Modifying the sample JCL
PAGE 231
E Command syntax descriptions This chapter describes the command syntax conventions used in this document. Command syntax descriptions The following table describes the command syntax conventions used in this document. Table 59 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.
PAGE 232
Symbol Convention ~ The items that immediately precede this symbol must follow the convention for < >, << >>, 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.
PAGE 233
Glossary This glossary describes the terms used in this manual. Business Continuity Manager A program used for building a highly reliable backup system in which multiple data centers 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 to minimize the restoration time or data loss from a disaster.
PAGE 234
host-discovered array structure A 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 definition file. log stream An aggregate of log data written by the system logger service. logical DKC An aggregate of volumes whose CU numbers are from 00 through FE that can be handled by HP P9500. Smart Manager for Mainframe recognizes a logical DKC as a storage system.
PAGE 235
system logger service MVS series standard functionality for writing, displaying, and deleting log data. Thin Provisioning Z Software that allocates a virtual volume to a host so that a necessary amount of physical space can be used according to the data write request. tier Media in a pool grouped by drive type and performance. A maximum of three tiers can be defined for one pool based on the performance of the media. tier relocation A function of Smart Tiers Z.
PAGE 236
Glossary
PAGE 237
Index Business Continuity Manager, 233 error-code parameter [KTERCODE command], 116 estimating log stream dataset, 150 estimating OUTLOG, 150 estimating staging dataset, 150 event log, 142, 233 event log data output tool, 150 example of adding a volume, 78 example of changing a device number, 81 example of changing the tiering policy, 75 example of deleting a volume, 79 C F A ALLOUPLD (sample JCL), 211 ARRAYS parameter [KTSCAN command], 105 ARRAYS parameter [KTSTORE command], 108 attributes of the dist
PAGE 238
K N KTACTTPG command, 86 KTALCSVC command, 121 KTCONMSG command, 112 KTDCTDEV command, 87 KTDCTTPG command, 89 KTDSPENV command, 121 KTENV command, 114 KTERCODE command, 116 KTGETHDA command, 90 KTIMPORT command, 92 KTINSCHK command, 117 KTLOAD command, 94 KTLOGCP, 150 KTQRYDEV command, 97 KTQRYRLC command, 99 KTQRYTPG command, 101 KTQSTATS command, 102 KTSCAN command, 104 KTSETENV command, 123 KTSLEEP command, 120 KTSTORE command, 107 KTWTOMSG command, 111 New-page assignment description (2-tier configu
PAGE 239
REXX script coding format (REXX external routine), 85 REXX script coding format (TSO/E command), 85 REXX variable structure, 131, 234 S sample JCL modification example, 211 SCAN parameter [KTIMPORT command], 93 script coding method, 85 SEC parameter [KTSLEEP command], 120 setting access privileges for system logger resources, 146 setting LOGR couple data sets, 145 setting operating environment by using environment variables, 37 settings required for registering license in ISPF panel, 40 Smart Manager for M
PAGE 240