HP XP7 Smart Manager for Mainframe User Guide Part number: TK916-96001 First edition: April 2014
Legal and notice information © Copyright 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Preface .............................................................................................. 13 1 Overview of Smart Manager for Mainframe ........................................ 15 About Smart Manager for Mainframe ......................................................................................... Overview of the Smart Manager for Mainframe functionality .......................................................... Concepts of terms used in Smart Manager for Mainframe ................
Workflow for registering a license ........................................................................................ Creating a license information dataset .................................................................................. Registering a license by using a license key file ...................................................................... Registering a license by entering a license key .......................................................................
Customizing the ISPF panels ....................................................................................................... Setting the command line location ........................................................................................ Setting the number of displayed function keys ........................................................................ Highlighting available point-and-shoot fields ..........................................................................
Volume Status Detail panel ....................................................................................................... 137 6 CLI commands ............................................................................... 139 List of CLI Commands .............................................................................................................. CLI command coding format ....................................................................................................
Information that can be used for troubleshooting ......................................................................... Collecting trace information ..................................................................................................... Collecting trace information when using scripts .................................................................... Collecting trace information when using TSO/E ...................................................................
HostAddressedDisk element ............................................................................................... Elements in the tiering policy group definition file ........................................................................ TieringPolicyGroup element ............................................................................................... TieringPolicy element ........................................................................................................
HPQKT4AP (creating target libraries) ......................................................................................... 296 HPQKT5AC (creating distribution libraries) ................................................................................. 298 F Command syntax descriptions .......................................................... 301 Command syntax descriptions .................................................................................................. 301 Glossary .................
Figures 1 Automatic data relocation across tiers according to the access frequency ....................... 15 2 Locating data in a specified tier according to performance requirements ........................ 16 3 Tier management using Smart Manager for Mainframe ............................................... 17 4 Grouping patterns of tiering policy groups ................................................................. 18 5 Overview of tiering policies ....................................................
Tables 1 Relationship between tiering policy levels and tiers in which data will be located ............ 20 2 Values that can be used to specify the new-page assignment tier ................................... 21 3 Files provided on the installation media ..................................................................... 30 4 FMID for Smart Manager for Mainframe components .................................................. 32 5 Attributes of the target libraries ..........................................
32 Output items of the KTINSCHK command ................................................................. 173 33 Return codes generated by the KTSLEEP command .................................................... 176 34 Return codes generated by the KTALCSVC command ................................................. 177 35 Return codes generated by the KTDSPENV command ................................................ 178 36 Return codes generated by the KTSETENV command .......................................
Preface This document describes how to use the following program product: - HP XP7 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.
Preface
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.
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.
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.
TIP: There are two methods of operation for Smart Manager for Mainframe using ISPF panels and using CLI commands. Use the method that suits the state of operation. Related topics • About tiering policy groups, page 18 Concepts of 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.
Figure 5 Overview of tiering policies A tiering policy can be specified by using a tiering policy information CSV file.
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.
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.
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
Figure 9 System configuration of Smart Manager for Mainframe CAUTION: The storage system must be connected to the z/OS host. 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.
A file that defines a tiering policy group. This file is created by importing a tiering policy information CSV file and a disk configuration definition file. The disk configuration definition file and tiering policy group definition file are generically called configuration files. Workflow for files used in Smart Manager for Mainframe The following describes the workflow for files used in Smart Manager for Mainframe. The numbers in the figure correspond to the steps.
Figure 11 workflow for using Smart Manager for Mainframe Related topics • Workflow for when defining and checking tiering policy groups when using the ISPF panel, page 59 • Defining and verifying a tiering policy group when using the CLI commands, page 91 User Guide 25
Overview of Smart Manager for Mainframe
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 12 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.
If you are not using SMP/E for the installation, you do not need to create a backup in the distribution library.
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.
3. Edit the JCLs transferred in accordance with your installation environment. Details are provided at the beginning of each JCL. 4. Create datasets used for transfers. Execute the ALLOUPLD job that was edited in step 3. This job defines the datasets on the mainframe host that the 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.
Postrequisites Perform either of the following: • Performing an installation using SMP/E • Installing directly from the provided datasets in the target library Related topics • Performing an installation using SMP/E, page 31 • Installing directly from the provided datasets in the target library, page 32 • Appendix E, page 281 Performing an installation using SMP/E Use sample JCLs to perform an installation with SMP/E. Procedure 1.
8. Re-execute HPQKT4AP after the CHECK operand is deleted. SMP/E APPLY is executed and the provided datasets are installed in the target library. Run the Smart Manager for Mainframe instance that was installed in the target library. If no errors occur, back up Smart Manager for Mainframe to the distribution library. The following table shows the keyword (FMID) that is required for installing with SMP/E.
Library datasets to be registered after the installation This section describes the attributes of the library datasets (target libraries) to be registered after the installation. Attributes of the target libraries are shown in the following table.
Registering the load library for LINKLIB and the KTQRYSMS command for authentication To register the load library for LINKLIB and the KTQRYSMS command for authentication to enable the use of CLI commands: Procedure 1. Concatenate the load library for LINKLIB 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.
Postrequisites • Setting RACF security for CLI commands Related topics • Example of dynamically linking the LINKLIB load library to LNKLST, page 35 • Setting RACF security for CLI commands, page 36 Example of dynamically linking the LINKLIB load library to LNKLST This section explains an example of dynamically linking the LINKLIB load library to LNKLST.
SETPROG LNKLST,UNDEFINE,NAME=LNKLST99 For details on the SETPROG command, see the manual MVS System Commands. Setting RACF security for CLI commands To use Smart Manager for Mainframe CLI commands, you must set up RACF security. Assign user permissions to use CLI operation commands or CLI reference commands. Procedure 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.
TIP: Users can use the following commands without access permissions: KTCONMSG, KTENV, KTERCODE, KTGETHDA, KTINSCHK, KTLOAD, KTSLEEP, KTSTORE, KTWTOMSG Postrequisites • Settings for using environment configuration commands Related topics • Settings for using environment configuration commands, page 37 Settings for using environment configuration commands Environment configuration commands (KTALCSVC, KTSETENV, and KTDSPENV) are used for setting up Smart Manager for Mainframe.
Postrequisites • Registering a user SVC Related topics • Settings required for using CLI commands (registration for authentication), page 33 • Registering a user SVC, page 38 Registering a user SVC You can dynamically register a user SVC by using the KTALCSVC environment configuration command, or statically register a user SVC by using the IEASVCxx parmlib member. If you use the IEASVCxx parmlib member to register a user SVC, you must perform an IPL again.
CAUTION: • If you used the KTALCSVC command to register a user SVC while Smart Manager for Mainframe was running, the execution of the CLI command continues to use the user SVC defined by the IEASVCxx parmlib member. The registered user SVC will take effect the next time a CLI command is executed. • User SVCs are shared between Smart Manager for Mainframe, and Business Continuity Manager.
4. Define the following SVCPARM statement in the IEASVCxx parmlib member: SVCPARM SVC-number,REPLACE,TYPE(3),EPNAME(JYUASVC),APF(NO),NPRMPT(NO),AR(NO) For details, see the manual MVS Initialization and Tuning Reference. To enable registration, you must perform an IPL again with the CLPA parameter specified. CAUTION: User SVCs are shared between Smart Manager for Mainframe, and Business Continuity Manager.
Related topics • Setting the operating environment by using environment variables, page 41 • Setting the operating environment by using system symbols, page 43 List of operating environment setting items for Smart Manager for Mainframe The following table lists operating environment setting items for Smart Manager for Mainframe.
Procedure 1. Execute the following KTSETENV command. START KTSETENV,PARM='parameter=parameter-value' 2. Use the KTDSPENV command as follows to confirm that the environment variables have been specified correctly: START KTDSPENV,PARM='DETAIL' Example of executing the KTSETENV command • When setting the name of the license information dataset to HPQ1.HPQ2.CCENTRAL.
TIP: The license (name of the license information dataset) for Smart Manager for Mainframe takes effect when the KTLOAD command is first executed after the license is registered. Even if you used the KTSETENV command to modify a prefix of the license information dataset name while CLI commands were being executed, the corresponding license takes effect after the KTLOAD command is executed the next time.
2. After an IPL is performed again, use the KTDSPENV command to confirm that the system symbols have been specified correctly. START KTDSPENV,PARM='DETAIL' Example of defining the IEASYMxx parmlib member • When setting the name of the license information dataset to HPQ1.HPQ2.CCENTRAL.
Settings required to use Smart Manager for Mainframe on the ISPF panel You need to execute the KTSTART command in the ISPF panel to use Smart Manager for Mainframe on the ISPF panel. This section describes the settings required to execute the KTSTART command. The KTSTART command is an REXX script that provides an ISPF panel interface.
CAUTION: To concatenate a dataset to libraries, make sure that the attributes of the target libraries are the same as the attributes of the dataset. For example, if the dataset attributes are DSORG=PO and RECFM=FB, the LRECL setting must be the same among the datasets. For details, see the DFSMS: Using Data Sets. For details about how to change dataset attributes, see the description of IEBGENR and IEBCOPY in the DFSMSdfp Utilities.
Sample REXX script While ISPF is running, you can execute the following REXX script to concatenate the libraries to the DD names (SYSEXEC, ISPPLIB, ISPMLIB, and ISPTLIB), and execute the KTSTART command to start the main panel for Smart Manager for Mainframe. /* REXX */ ADDRESS TSO "ALTLIB ACTIVATE APPLICATION(EXEC)", "DATASET('HPQKT.Vnnnnnn.HPQKEXET')"; ADDRESS ISPEXEC; "LIBDEF ISPMLIB DATASET ID('HPQKT.Vnnnnnn.HPQKMSGT') STACK"; "LIBDEF ISPPLIB DATASET ID('HPQKT.Vnnnnnn.
• Registering a license by entering a license key, page 50 Creating a license information dataset Create a license information dataset for installing a license key. Prerequisites • Specifying prefixes for the license information dataset using the environment variable or system symbol Procedure 1. Edit the JCL that allocates the license information dataset. Edit the dataset prefix (%PREFIX) and the volume serial number (%VSN) in accordance with your installation environment.
Related topics • • • • Setting the operating environment by using environment variables, page 41 Setting the operating environment by using system symbols, page 43 Registering a license by using a license key file, page 49 Registering a license by entering a license key, page 50 Registering a license by using a license key file With this method, transfer the license key file to z/OS, and use the Manage Licenses panel to register the license.
2. Transfer the license key file to the host machine. Use the following format to transfer the license key file to the license key dataset: • ASCII mode • Encoded (to EBCDIC) Assume that the license key file has been transferred to a license key dataset named LICENSE.KEYS.SAMPLE. 3. In the ISPF Primary Option Menu panel, select option 6 Command. 4. Enter KTSTART. The main panel for Smart Manager for Mainframe appears.
The following figure provides the procedure for registering a license by directly entering a license key. Figure 17 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. Procedure 1. In the ISPF Primary Option Menu panel, select option 6 Command. 2. Enter KTSTART. The main panel for Smart Manager for Mainframe appears.
Postrequisites • Verifying the setup information Related topics • • • • • Creating a license information dataset, page 48 Verifying the setup information, page 52 Edit Defaults panel , page 116 Installation Management area, page 119 Manage Licenses panel , page 123 Verifying the setup information After you have completed the setup of Smart Manager for Mainframe, check the setup.
/* // For details about the example of the command output, see the description of the KTINSCHK command.
Backing up Smart Manager for Mainframe to the distribution library If SMP/E was used when installing Smart Manager for Mainframe in the target library and no Smart Manager for Mainframe, use a sample JCL to back up Smart Manager for Mainframe to the distribution library. This step is unnecessary if you install it directly in the target library without using SMP/E. Procedure 1. Modify the following sample JCL in accordance with the user installation environment.
Library type (DD name#) ISPF message library (HPQKMSGD) ISPF table library (HPQKTABD) DSORG RECFM LRECL (bytes) BLKSIZE (bytes) PO FB 80 6,160 PO FB 80 6,160 # The DD name specified with the HPQKT1AL sample JCL (allocates the distribution and target libraries) that was used when installing with SMP/E. The dataset name is the one specified in each DD statement.
TIP: • For details on the YKINSCHK command, see the HP XP7 for Business Continuity Manager Software Reference Guide. • For details on how to delete the user SVC in Business Continuity Manager, see the HP XP7 for Business Continuity Manager Software Installation Guide. • This procedure lets you install Smart Manager for Mainframe for the first time. If you need to upgrade Smart Manager for Mainframe, refer to the instructions for preparing for the upgrade.
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.0 or later 8.0.
Installation and setup
3 Smart Manager for Mainframe operations when using the ISPF panel This chapter describes how to use the ISPF panels to operate Smart Manager for Mainframe. Operation description method for the ISPF panels The following describes how the operation of Smart Manager for Mainframe using the ISPF panels is described.
Figure 18 Procedure for defining and verifying a tiering policy group (ISPF panels) Related topics • • • • • • • • • • Overview of files used by Smart Manager for Mainframe, page 23 Basic ISPF panel settings of Smart Manager for Mainframe, page 61 Scanning storage systems when using the ISPF panel, page 62 Creating a tiering policy information CSV file when using the ISPF panel, page 63 Defining tiering policy groups when using the ISPF panel, page 64 Applying tiering policies when using the ISPF panel, p
Starting Smart Manager for Mainframe and displaying the main panel This section describes how to start Smart Manager for Mainframe and display the main panel. Procedure 1. In the ISPF Primary Option Menu panel, select 6 Command. The ISPF Command Shell panel appears. 2. Enter KTSTART. The main panel for Smart Manager for Mainframe appears. TIP: When you display the main panel for the first time, the Edit Defaults panel appears.
3. Enter values for the items, and then press Enter. The setting is saved. TIP: In each panel, press the DispConf function key (F17) to display the basic information you specified here for the ISPF panels. As a default, because only 12 function keys are displayed, DispConf is not displayed in the list of function keys. To display DispConf, set the number of displayed function keys to 24.
3. Do either of the following: • To specify an SMS storage group to be scanned: Enter a slash (/) in the Storage Group field and specify the name of the target SMS storage group. Then press the Scan function key (F6). TIP: If you perform either of the actions below without entering an SMS storage group name, the Storage Group Selection List panel appears. You can use it to select the desired SMS storage group from the list. • Press the Scan function key (F6).
Procedure 1. In the main panel, select the Policy CSV List 'Policy' point-and-shoot field. The Policy CSV List area appears. 2. Select the point-and-shoot field. The Policy ID Entry Field panel appears. 3. Specify the policy ID to be assigned to the tiering policy information CSV file, and then press Enter. The tiering policy information CSV file is created, and the policy ID appears in the Policy CSV List area. 4. Enter a slash (/) in the AC field for the policy ID.
2. Enter a slash (/) in the AC field for the tiering policy information CSV file. The Policy CSV List Actions panel appears. 3. Enter 4 in the entry field or select the Import 'I' point-and-shoot field. The tiering policy information CSV file is imported and the tiering policy group is defined. The defined information is saved in the tiering policy group definition file.
Verification after scanning storage systems when using the ISPF panel The following describes how to verify information about the volumes and pools after scanning storage systems. Checking volume information for the scanned storage system when using the ISPF panel To check the volume information for the scanned storage system, in the main panel, from the Storage System List area, open the Volume Selection List panel, and then check details about the selected volumes in the Volume Status Detail panel.
5. Enter 1 in the entry field or select the Volume Status Detail 'V' point-and-shoot field. The Volume Status Detail panel displays details about the volume.
3. Enter 2 in the entry field or select the Pool Selection 'P' point-and-shoot field. The Pool Selection List panel displays a list of pools that belong to the specified storage system. 4. To display details about a specific pool, enter a slash (/) in the AC field. The Pool Selection List Actions panel appears. TIP: In this step, you can select a point-and-shoot pool ID instead of entering a slash (/) in the AC field. This will directly change the panel display to the Pool Status Detail panel.
5. Enter 1 in the entry field or select the Pool Status Detail 'P' point-and-shoot field. The Pool Status Detail panel displays details about the pool. Related topics • Storage System List area, page 120 • Pool Selection List panel , page 125 • Pool Status Detail panel , page 125 Verification after defining a tiering policy group when using the ISPF panel This section describes how to verify the management targets (volumes, pools, and SMS storage groups) after you have defined a tiering policy group.
Procedure 1. In the main panel, select the Tiering Policy Group List 'TPG' point-and-shoot field. The Tiering Policy Group List area appears. 2. Enter a slash (/) in the COMMAND field for the tiering policy group whose information you want to view. The Tiering Policy Group List Actions panel appears. 3. Enter 7 in the entry field or select the Definition 'D' point-and-shoot field. The Tiering Policy Group Definition panel displays definition information for the specified tiering policy group.
3. Enter 1 in the entry field or select the Summary 'S' point-and-shoot field. The Tiering Policy Group Summary panel displays storage system information for the specified tiering policy group.
3. Enter 4 in the entry field or select the Storage Groups 'SG' point-and-shoot field. The Select Storage Group List panel appears. 4. Select 1 to display a list of all SMS storage groups contained in the tiering policy group. If you want to filter the SMS storage groups to be displayed, select 2 and then specify the filter condition in the Storage Group Name field. The Tiering Policy Group Storage Group List panel displays information about the SMS storage groups.
2. Enter a slash (/) in the COMMAND field for the tiering policy group whose information you want to view. The Tiering Policy Group List Actions panel appears. 3. Enter 5 in the entry field or select the Volumes 'V' point-and-shoot field. The Select Volume List panel appears. 4. Select 1 to display a list of all volumes contained in the tiering policy group. If you want to filter the volumes to be displayed, select 2 and then specify filter conditions in the Volser field.
6. Enter 1 in the entry field or select the TPG Volume Status Detail 'V' point-and-shoot field. The Tiering Policy Group Volume Status Detail panel displays the volume information for the tiering policy group.
3. Enter 6 in the entry field or select the Pools 'P' point-and-shoot field. The Select Pool List panel appears. 4. Select 1 to display a list of all pools contained in the tiering policy group. If you want to filter the pools to be displayed, select 2 and then specify the filter conditions in the Pool Name field. The Tiering Policy Group Pool List panel displays information about the pools. 5. To display information about a specific pool, enter a slash (/) in the AC field.
6. Enter 1 in the entry field or select the TPG Pool Status Detail 'P' point-and-shoot field. The Tiering Policy Group Pool Status Detail panel displays the pool information for the tiering policy group..
Procedure 1. In the main panel, select the Tiering Policy Group List 'TPG' point-and-shoot field. The Tiering Policy Group List area appears. 2. Enter a slash (/) in the COMMAND field for the tiering policy group to be checked for whether tiering policies have been applied. The Tiering Policy Group List Actions panel appears. 3. Enter 1 in the entry field or select the Summary 'S' point-and-shoot field.
5. To check the tiering policies for a specific volume, enter a slash (/) in the AC field. The Tiering Policy Group Volume List Actions panel appears. TIP: In this step, you can select a point-and-shoot device number instead of entering a slash (/) in the AC field. This will directly change the panel display to the Tiering Policy Group Volume Status Detail panel. 6. Enter 1 in the entry field or select the TPG Volume Status Detail 'V' point-and-shoot field.
Procedure 1. In the main panel, select the Tiering Policy Group List 'TPG' point-and-shoot field. The Tiering Policy Group List area appears. 2. Enter a slash (/) in the COMMAND field for the tiering policy group to be checked for the tier relocation status for volumes. The Tiering Policy Group List Actions panel appears. 3. Enter 1 in the entry field or select the Summary 'S' point-and-shoot field.
4. To check the volumes for each relocation status, select the In range, Out of range, or Shortage point-and-shoot fields. The Tiering Policy Group Volume List panel displays a list of volumes in the relocation status you selected above. (The following panel appears if you selected Shortage). Use the PoolID field to check the ID of a pool with insufficient capacity.
3. Enter 1 in the entry field or select the Summary 'S' point-and-shoot field. In the Tiering Policy Group Summary panel, the number of pools whose usage exceeds the threshold appears in the Pools exceeding threshold field. 4. To view the pools whose usage exceeds the threshold, select the Pools exceeding threshold point-and-shoot field. The Tiering Policy Group Pool List panel displays a list of pools whose usage exceeds the threshold.
2. In the main panel, select the Policy CSV List 'Policy' point-and-shoot field to update the definition of the tiering policy group. The Policy CSV List area appears. 3. Enter a slash (/) in the AC field for the modified tiering policy information CSV file. The Policy CSV List Actions panel appears. 4. Enter 4 in the entry field or select the Import 'I' point-and-shoot field. The modified tiering policy information CSV file is imported and the definition of the tiering policy group is updated. 5.
2. If the volume to be added has not been scanned, scan that volume to update the disk configuration definition file. Information about the volume to be added is saved in the disk configuration definition file. 3. In the main panel, select the Policy CSV List 'Policy' point-and-shoot field to update the definition of the tiering policy group. The Policy CSV List area appears. 4. Enter a slash (/) in the AC field for the tiering policy information CSV file. The Policy CSV List Actions panel appears. 5.
TIP: You can change the tiering policy of the volume to be deleted back to the default by changing the panel display from the Storage System List area to the Volume Selection List panel, specifying D for the AC field, and then executing Deactivate Device. Procedure 1. Do either of the following: • If the volume to be deleted belongs to an SMS storage group: Exclude the volume from the SMS storage group.
4. Modify the contents of the tiering policy information CSV file. 5. Press the Exit function key. The modifications are saved, and the Policy CSV List area appears again. Related topics • Policy CSV List area, page 121 • Chapter 7, page 181 Convenient use of list panels This section describes the convenient use of list panels (panels such as the Tiering Policy Group Volume List panels that display a list of volumes, pools, or SMS storage groups).
2. Specify the filter conditions. The following is an example specification. The displayed items vary depending on the panel that called this panel. 3. Press Enter. The information is filtered according to the specified filter conditions. Related topics • How to specify the search or filter conditions in ISPF panels, page 240 Searching character strings To search a character string in a listing panel, use the Find Options panel to specify the search string, and then press Enter.
Positioning the cursor at a specific line in a sorted field To position the cursor at a specific line in a sorted field, use the Locate Options panel to specify the search string, and then press Enter. Prerequisites • Data in the field in which the cursor is to be positioned has been sorted. Procedure 1. Enter LOCATE in the command line of the ISPF panel, and then press Enter. The Locate Options panel appears. 2. Specify the search string. The following is an example specification.
2. Specify the AC fields for which the action is to be set or canceled by specifying the target fields, the condition character string for the fields, and an action. The following is an example specification. The displayed items vary depending on the panel that called this panel. 3. Press Enter. The action is set or canceled for multiple AC fields. NOTE: The action is not set or canceled for the lines that are not displayed by the filter.
Procedure 1. Enter PFSHOW TAILOR in the command line of the ISPF panel. The ISPF Settings panel appears. 2. Enter 1 (12) or 2 (24) in the Number of keys field. If you entered 2 (24), enter 3 (All - display all keys) in the Display set field. Highlighting available point-and-shoot fields Use the ISPF Settings panel to specify the setting to highlight the available point-and-shoot fields. Procedure 1. Enter PSCOLOR in the command line of the ISPF panel. The ISPF Settings panel appears. 2.
Smart Manager for Mainframe operations when using the ISPF panel
4 Smart Manager for Mainframe operations when using the CLI This chapter describes how to use CLI commands to operate Smart Manager for Mainframe. Defining and verifying a tiering policy group when using the CLI commands The figure below shows the workflow for defining and verifying a tiering policy group by using the CLI commands. This figure explains the steps of the procedure, along with the commands and sample scripts to be executed in the procedure.
Figure 19 Workflow for defining and verifying a tiering policy group (CLI commands) Related topics • • • • • • • • • Overview of files used by Smart Manager for Mainframe, page 23 Checking volume information when using the CLI commands, page 93 Scanning the storage system when using the CLI commands, page 94 Creating a tiering policy information CSV file when using the CLI commands, page 96 Defining tiering policy groups when using the CLI commands, page 96 Applying tiering policies when using the CLI com
Checking volume information when using the CLI commands 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. Based on the acquired information for volumes, consider how they are used for tasks and examine the tiering policy group to be defined.
Postrequisites • Scanning the storage system Related topics • Scanning the storage system when using the CLI commands, page 94 • KTQRYDEV, page 153 • KTDEMO04 (Display the volume information), page 253 Scanning the storage system when using the CLI commands To scan the storage system, first execute the KTSCAN command, and then execute the KTSTORE command to save the scan results.
TIP: If the disk configuration changes significantly after the scan (for example, because the storage system is replaced or device numbers of volumes change due to changes in I/O definitions), you must delete the disk configuration definition file. Then rescan the storage system. If necessary, change the definition of the tiering policy group. Reference scripts For details about how to create the script, see the following sample scripts.
• KTDEMO00 (Create a disk configuration definition file), page 244 • KTDEMO01 (Display the contents of the disk configuration definition file), page 247 Creating a tiering policy information CSV file when using the CLI commands 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-ID.
Figure 22 Defining tiering policy groups (CLI commands) Prerequisites • Scanning the storage system • Creating a tiering policy information CSV file • Varying the volumes online if the record type of the tiering policy information CSV file is specified as STORGRP or VOLSER. Procedure • 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.
Example 2: The code in this example imports a tiering policy information CSV file whose policy ID is POLICY1, and creates a disk configuration definition file whose prefix is PREFIX1 and a tiering policy group definition file simultaneously. CALL KTIMPORT "MSG(msgstem.
Procedure 1. Execute the KTLOAD command. Target volume information and information about the tiering policies defined in configuration files is loaded from the configuration files to the REXX variable structure. 2. Execute the KTACTTPG command. The data set in the REXX variable structures is applied to the storage system. Reference scripts For details about how to create the script, see sample script KTDEMO10.
Procedure 1. Perform either of the following operations to acquire information about the tiering policies from the storage system. • To acquire information for each tiering policy group, execute the KTLOAD command, and then the KTQRYTPG command. • To acquire information for each volume, execute the KTQRYDEV command. 2. View the acquired information, and confirm whether the tiering policies have been applied. Reference scripts For details about how to create the script, see the following sample scripts.
2. Execute either of the following commands. • To acquire the page relocation status of each volume: Execute the KTQRYTPG command. • To acquire the progress information about tier relocation for each Smart Tiers Z pool: Execute the KTQRYRLC command. 3. View the acquired information and check the progress of tier relocation. Reference scripts For details about how to create the script, see the following sample scripts.
Tiering Policy Group Name: TPG1 Volumes POOL Devn,Volser,SN ,CU,CCA, ID,TLv,RelocateStatus 0000,VOL001,14001,00, 00, 1, 3,done : ,LocatedPage/ TotalPage , 1/ 1 Pools Relocate RelocateTime MigrationPage SN , ID, Type,Monitor,active %,Start, End,ExpectedCt,MigratedCt 14001, 1, DT, auto,Y 100%,00:00,01:00, 0, 0 : Pools tier status SN , ID,Tier, Used/ Capacity,EntryBuf%,RelocBuf%,Media 14001, 1, 1, 1/ 26 0%, 2%,"SSD" 14001, 1, 2, 263/ 2631 8%, 2%,"SAS 15K" 14001, 1, 3, 1036/ 131578 8%, 2%,"SATA 7.
Tiering Policy Group Name : TPG1 Monitor Interval Time(sec): 600 Volume I/O statistics ------------------------------------------------------11:23:00 - 11:33:00 ------------------------------------------------------DEVN,Volser,STORGRP,SN ,CU,CCA,Tier1 IOPS,Tier2 IOPS,Tier3 IOPS 1101,VOL001,SG1 ,14001,00, 01, 100, 253, 1486 1201,VOL002,SG1 ,14001,00, 01, 20, 0, 0 ------------------------------------------------------11:33:00 - 11:43:00 ------------------------------------------------------DEVN,Volser,STORGRP
Related topics • • • • • • KTACTTPG, page 142 KTACTTPG, page 142 KTIMPORT, page 148 KTLOAD, page 150 KTQRYTPG, page 157 Format of tiering policy information CSV files, page 183 Adding a volume to a tiering policy group when using the CLI commands To add a volume to a tiering policy group, add a volume to the definition of the tiering policy group, and then apply the tiering policies to the storage system.
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.
Reference scripts Refer to the sample script KTDEMO05 for details on how to create scripts for changing the tiering policy of volumes back to the default by using the KTDCTDEV command.
5 ISPF panels This chapter describes transition, operation methods, and displayed items of the ISPF panel in Smart Manager for Mainframe. Panel relationships of Smart Manager for Mainframe The main panel is the panel that appears when Smart Manager for Mainframe is started, and has five areas that are the gateways to each operation. Select the area according to the operation you want to perform. Select a point-and-shoot field or specify the action to move to the next panel.
Figure 24 Panel relationships of Smart Manager for Mainframe Common items in the panel This section describes the common items between the panels for Smart Manager for Mainframe. About the layout of the panels This section describes the layout of the panels for Smart Manager for Mainframe. The following figure indicates the layout of the Tiering Policy Group Pool List panel.
About the action bar The action bar of the Smart Manager for Mainframe panel contains the Goto, Commands, and Help menus. Goto The Goto pull-down menu displays the name of the panels that you can move to from the current panel.
Figure 26 Commands pull-down menu (Tiering Policy Group Pool List panel) Help The Help pull-down menu displays the name of the Help panels that can be referenced from the current panel. Figure 27 Help pull-down menu (Main panel) Related topics • Commands that can be used in the command line About the AC and COMMAND fields These are fields for specifying the action of the target. The following are some example of values that can be specified for the AC or COMMAND field.
The following figure show an example of actions panels when / is specified to AC or COMMAND field. About point-and-shoot field When you place the cursor on a selectable point-and-shoot field and then press the Enter key, the action set to that field can be executed. In this manual, selectable point-and-shoot fields are indicated in light-blue text. In order to check which point-and-shoot fields are selectable in the actual panel, enable the highlighting settings.
The following explains the actions that are executed when you select a point-and-shoot field. Table 10 Actions that are executed when you select a point-and-shoot field Location Executed action Header of the list Sorts the rows based on the field value under the corresponding header. Field Displays a panel that displays a list or detailed information for the corresponding field.
• Field The following is a representative example of an action executed by selecting a point-and-shoot field. Point-and-shoot fields Action that is executed Volume statuses such as In range, Mismatch, and Pools exceeding threshold Displays the list of volumes of the selected status. Volumes, pools Displays the details of the selected volumes or pools. The following example show the list of volumes when the volume status is selected as the point and shoot field.
Related topics • Highlighting available point-and-shoot fields, page 89 About the display unit For the panels that have a capacity or used capacity displayed, Unit: unit is displayed on the top right-corner in the panel. The display unit is either Page or GB. If the list is displayed in units of GB, the number after the decimal point is truncated and displayed for the capacity and used capacity. However, if the value is less than 1, the displayed value is rounded up.
Device Scan Scope panel In this panel, you can scan a storage system volumes that are connected to a host. Specify a scan target with an SMS storage group name, volume serial number, or device number, and then press the Scan function key (F6). Item Description To specify the target by SMS storage group, specify /, and then in the input field, enter an SMS storage group name to be scanned.
After scanning, press the Exit function key to create or update disk configuration definition files with the following name, and save the configuration information of the detected volumes: • prefix.DSK.SNnnnnn.LOCAL prefix: The prefix value specified to Configuration file prefix in the Set Defaults area nnnnn: The serial number of the storage system Press the Cancel function key to discard the changes and exit.
Item Description Type of error Displays the type of errors. Exception Message List panel This pop-up window displays warnings and error messages of a requested operation in chronological order. Operations and output messages are stored in the ISPF log. If there are multiple messages, you can scroll across the panel. At the top of the line, the results of the executed command are displayed.
Related topics • Error Code Help panel , page 116 Main panel This section explains the Main panel and the areas in the panel. Main panel (common) The panel appears when Smart Manager for Mainframe is started. In the main panel, you can list each target object. There are some object lines in the middle of the panel. Select the line point-and-shoot field to expand the accordion menu of the target object. To contract the accordian menu, select the point-and-shoot field on the line again.
Related topics • • • • • Installation Management area, page 119 Set Defaults area , page 119 Storage System List area, page 120 Policy CSV List area, page 121 Tiering Policy Group List area, page 122 Installation Management area This area displays operation menus related to the installation of Smart Manager for Mainframe. Item Description Select the point-and-shoot field to go to the Manage Licenses panel for registering or displaying license information.
Item Description Select the point-and-shoot field to display the Edit Defaults popup window where you can edit basic settings. Displays the upper limit for the number of messages that can be output to the ISPF log when one command is executed. ISPF log max • 0: The number of messages is not limited (all messages are output). • 10 to 5000: The specified number (integer) of messages are output. Pool usage threshold Displays the threshold for pool usage rate.
Item Description Select the point-and-shoot field to go to the Device Scan Scope panel to scan storage systems. The action to be executed for the selected storage system. You can specify the following actions: • V: Goes to the Volume Selection List panel. AC • P: Goes to the Pool Selection List panel. • D: Deletes the disk configuration definition file for the selected storage system.
Item Description Select the point-and-shoot field to display the Policy ID Entry pop-up window for creating tiering policy information CSV files. The action to be executed for the selected tiering policy information CSV file. You can specify the following actions: • V: Displays the contents of the selected tiering policy information CSV file. • C: Copies the selected tiering policy information CSV file.
Item Description The action to be executed for the selected tiering policy group. You can specify the following actions: • S: Goes to the Tiering Policy Group Summary panel. • ACT: Applies the tiering policy to the storage systems. • DCT: Changes the tiering policy back to the default. COMMAND • SG: Goes to the Tiering Policy Group Storage Group List panel. • V: Goes to the Tiering Policy Group Volume List panel. • P: Goes to the Tiering Policy Group Pool List panel.
Item Description Displays the license name. • Smart Manager for MF: Smart Manager for Mainframe license PP Name If a license key for Business Continuity Manager is installed in the license information dataset, the Business Continuity Manager license is also displayed. Displays the model code for the storage system. For the displayed values, see Help. Model Displays the license type. • Perm.: Permanent license Type • Temp.: Temporary license • Emer.
Pool Selection List panel This panel displays a list of pools in a storage system. Item Description Specify the action to be executed for the selected pool. You can specify the following actions: • V: Goes to the Volume Selection List panel. This panel displays the list of volumes that belong to the selected pool. AC • P: Goes to the Pool Status Detail panel. This panel displays details of the selected pool. PoolName Displays the pool name up to 16 characters.
Current Relocation Information Displays the current relocation status and capacity and usage information for each tier. Item Description Displays the monitoring mode. • Auto: Automatic execution mode (tier relocation is performed automatically) Relocation mode • Manual: Manual execution mode Displays the relocating status. • In progress: Relocation is in progress Relocation status • Finished or stopped: Relocation has finished or stopped Displays the relocation progress (%).
Item Description Expected Displays the expected number of migrated pages. Migrated Displays the migrated pages. Basic Information Displays the basic information of the pool. Setting Information panel This pop-up window displays basic information for operating Smart Manager for Mainframe from the ISPF panel. Item Description ISPF Log Max Displays the upper limit of the number of messages that are output to the ISPF log when one command is executed.
Item Description Specify the action to be executed for the selected volume. You can specify the following actions: AC • V: Goes to the Tiering Policy Group Volume Status Detail panel. • P: Goes to the Tiering Policy Group Pool Status Detail panel. Displays the tiering policy level. The tier to which pages are assigned is shown in the Tiering Policy Group Volume Status Detail panel. TLv Displays the tier to which new pages are assigned. • HIGH: New pages are assigned to the higher tier.
The following figure shows the right-hand panel of the Tiering Policy Group Pool List panel: Item Description Specify the action to be executed for the selected pool. You can specify the following actions: AC • P: Goes to the Tiering Policy Group Pool Status Detail panel. PoolName Displays the pool name up to 16 characters. You can view pool names that exceed 16 characters in the Tiering Policy Group Pool Status Detail panel.
Current Relocation Information Displays the current relocation status and the capacity and usage information for each tier. Item Description Displays the monitoring mode. • Auto: Automatic execution mode (tier relocation is performed automatically) Relocation mode • Manual: Manual execution mode Displays the relocation status. • In progress: Relocation is in progress Relocation status • Finished or stopped: Relocation is finished or stopped Displays the relocation progress (%).
Item Description Expected Displays the expected number of migrated pages. Migrated Displays the migrated pages. Basic Information Displays the basic information of the pool. Tiering Policy Group Storage Group List panel This panel displays a list of SMS storage groups to which the volumes in the tiering policy group belong, and information about the capacity of those storage groups. Item Description Specify the action to be executed for the selected storage group.
Tiering Policy Group Summary panel This panel displays the following information about a tiering policy group: capacity information, page relocation status, pools whose usage rate exceeds the threshold, and whether the tiering policy is correctly applied to the storage system. In this panel, you can check the summary status information of the tiering policy group. To go to the detailed information panel, select a field name point-and-shoot field.
Item Description Shortage Displays the number of volumes for which some pages in the volume are not assigned to the tiers specified by tiering policy level due to insufficient pool capacity. Select the Shortage point-andshoot filed to display the volumes whose statuses are Shortage in the Tiering Policy Group Volume List panel. TIP: When a volume is in the Shortage status, you need to take measures such as adding capacity to the pool or moving data to other pools.
The following figure shows the right-hand panel of the Tiering Policy Group Volume List panel: Item Description Specify the action to be executed for the selected volume. • V: Goes to the Tiering Policy Group Volume Status Detail panel. AC • P: Goes to the Tiering Policy Group Pool Status Detail panel. Diff If the tiering policy defined in the tiering policy group definition file is different from the tiering policy set for the storage system, * is displayed.
Item Description Tier1, Tier2, Tier3 Displays the amount of space used on each tier by the volume. %T1, %T2, %T3 Displays the distribution ratio (%) of the usage of each tier by the volume. Total Displays the total amount of space used by the volume. Capacity Displays the total capacity of the volume.
Item Description Displays the relocation status of the volume. • In range: All pages are assigned to the tiers specified by tiering policy level. Relocation state • Out of range: Some pages are not assigned to the tiers specified by tiering policy level. • Shortage: Some pages are not assigned to the tiers specified by tiering policy level due to insufficient pool capacity. Tier level# Displays the tiering policy level. Displays the tier to which new pages are assigned.
Item Description Specify the action to be executed for the selected volume. You can specify the following actions: • V: Goes to the Volume Status Detail panel. This panel displays detailed information about the selected volume. AC • P: Goes to the Pool Status Detail panel. This panel displays detailed information about the selected pool. • D: Restores the default tiering policy for the volume (tiering policy level: 0, tier to which new pages are assigned: MIDDLE, whether to execute tier relocation: Y).
Tiering Policy Information Displays the tiering policy of the current status in the storage system. Item Description Displays the relocation status of the volume. • In range: All pages are assigned to the tiers specified by tiering policy level. Relocation state • Out of range: Some pages are not assigned to the tiers specified by tiering policy level. • Shortage: Some pages are not assigned to the tiers specified by tiering policy level due to insufficient pool capacity.
6 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.
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.
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.
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.
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.
• 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.
REXX variables that are updated by the KTDCTDEV command • All variables in the message structure Related topics • Message structure, page 193 • KTDEMO05 (Change the tiering policy of a volume back to the default), page 256 KTDCTTPG Function Changes the tiering policy for a tiering policy group back to the following default values.
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.
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.
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.
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.
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.
• 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.
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.
• TPG.VOL.n.SSID • TPG.VOL.n.TierLevel • TPG.VOL.n.TierRelocation Related topics • • • • • Message structure, page 193 Host-discovered array index structure, page 194 Host-discovered array structure, page 195 Tiering policy group structure, page 200 KTDEMO03 (Display the contents of the tiering policy group definition file), page 251 KTQRYDEV Function Acquires the following information about the specified volume from the storage system, and then stores the information in the REXX variable structure.
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.
• 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.
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.
• 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.
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.
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.
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.
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.
• 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.
• 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.
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.
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.
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.
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.
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.
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.
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.
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 YKLCNSE &YKLCNSE YKLCNS2 &YKLCNS2 LOGPUT &YKLOGPT SYSLOG &YKSYSLG • NO: CLI command-execution logs are not output.
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.
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.
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.
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.
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.
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.
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.
START KTDSPENV,PARM='DETAIL' KTA403I HP XP7 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.
• 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='.
7 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-ID Disk configuration definition file prefix.DSK.SNnnnnn.
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.
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.
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.
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.
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.
Figure 28 Configuration example of tiering policy groups The following provides details about the tiering policy groups in the configuration example.
Specification in the tiering policy information CSV file #TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc STORGRP,SG1 ,TPG1 ,2 ,HIGH DEVN ,1101 ,TPG1 ,1 DEVN ,1202 ,TPG1 ,2 ,HIGH STORGRP,SG2 ,TPG2 ,5 STORGRP,SG3 ,TPG2 ,5 Values that must be specified for the prefix, policy ID, and tiering policy group ID • Prefix: PREFIX1 This value will be used as the file name prefix for configuration files and tiering policy information CSV files.
When changing the tiering policy back to the default Keep the record, but delete the tiering policy parameters. Before the change: #TYPE ,DEVICE,TPGID,TierLvl,Entry,Reloc STORGRP,SG1 ,TPG1 ,2 ,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.
When deleting tiering policies assigned individually to volumes in the SMS storage group so that they match the settings on the SMS storage group 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.
When adding a volume that does not belong to the SMS storage group Add the record of the volume to be added to the tiering policy information CSV file.
Delete the record of the volume from the tiering policy information CSV file.
8 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.
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.
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.
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.
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.
REXX variable name Description LOCAL.SNnnnnn.POOLxx.
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 Percentage of the buffer area used for relocation (%) m. m indicates the migration-source tier number.
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.
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.
REXX variable structures
9 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.
Procedure 1. Log on to the TSO/E terminal. 2. Enter the following commands. • To output an ABEND dump to the spool: ALLOC DD(SYSABEND) SYSOUT(SYSOUT-class) • To output an ABEND dump to a dataset: ALLOC DD(SYSABEND) DS(dataset-name) 3. Execute a CLI command. 4. If the CLI command terminated abnormally and the system returned 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.
Collecting event logs This section describes how to collect event logs. How to collect event logs Two methods are available for collecting event logs. Use the LOGPUT environment variable or the &YKLOGPT system symbol to select the method. The methods for collecting event logs are as follows. • Use the system logger service to output event logs to a log stream, and then use the Smart Manager for Mainframe tool to output the event logs from the log stream to a dataset.
Figure 29 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 206 • Collecting event logs without using the system logger service, page 215 Collecting event logs by using the system logger service This section describes how to collect event logs when the system logger service is used.
Related topics • • • • • Setting LOGR couple data sets, page 207 Defining the SMS for the system logger service, page 207 Defining a log stream, page 207 Setting access privileges for system logger resources, page 208 Starting the system logger service, page 208 Setting LOGR couple data sets In a sysplex environment, format the LOGR couple datasets and then define them for the sysplex.
Related topics • Parameters specified when a log stream is defined, page 208 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.
to form the log stream name. If a system name starts with a number, the last five characters used for the log stream name must be unique within the sysplex. The following shows examples of how a system name starting with a number is converted to the system name in a log stream name. • For the system name 1SYS starting with a number and consisting of less than five characters: YKS is added to the system name to create YKS1SYS.
Specify the name of the SMS storage class used for allocating a log dataset. Specify this parameter when using an SMS definition. AUTODELETE(YES) Specify this parameter when automatically deleting event log data. RETPD(retpd) Specify this parameter when automatically deleting event log data. Specify the number of days to retain event log data in the log stream. HLQ(CCENTRAL) This parameter specifies that CCENTRAL is the high level qualifier used as a part of the log dataset name. This parameter is optional.
Procedure • If a log dataset is full, execution of a CLI command will continue, but event log data will no longer be output. Use either of the following management methods to prevent the log dataset from becoming full. • Automatically delete event log data (specify the AUTODELETE(YES) parameter when defining the log stream). • Periodically delete and re-define the log stream. Use the IXCMIAPU utility with the DELETE LOGSTREAM NAME(log_stream_name) parameter specified to delete the log stream.
Procedure 1. Enter the FORCE IXGLOGR,ARM command to stop the system logger service. 2. Enter the S IXGLOGRS command to restart the system logger service. 3. Use the IXCMIAPU utility with the DELETE LOGSTREAM NAME(log_stream_name) parameter specified to delete the log stream. The log dataset is deleted when the log stream is deleted. For details, see the manual MVS Setting Up a Sysplex. 4. Re-define the log stream.
Estimating the dataset (OUTLOG) to which logs are output from the log stream Estimate the disk capacity based on the amount of offloaded event log data and the retention period. Overview of the event log data output tool The event log data output tool (KTLOGCP) outputs the event log data accumulated in the log stream to a dataset. The output log data will not be deleted from the log stream. KTLOGCP allows you to output only the necessary event log data by specifying conditions for output data.
Related topics • Control statements for the event log data output tool, page 214 • Output format of the event log data output tool, page 215 Control statements for the event log data output tool A control statement specified in the DD statement SYSIN for the log data output tool (KTLOGCP) contains a RANGE control statement, which specifies the time, and SELECT control statements, which specify the job names.
• Each control statement must be completely specified on one line. A control statement cannot extend over two or more lines. Control statement examples To output the log data with acquisition dates in the range from 2013/03/24 00:00 to 2013/03/24 23:59, specify as follows. RANGE STARTTIME(2013/03/24,00:00:00) ENDTIME(2013/03/24,23:59:59) To output the log data with acquisition dates in the range from 2013/03/24 00:00 to 2013/03/24 23:59 and with the job names USER01T or USER01, specify as follows.
Procedure 1. Estimate the log dataset capacity. Estimate the amount of log data based on the frequency at which CLI commands are issued and the frequency of errors. Allocate enough space to ensure that log data can be output until a backup of the log dataset is created in one sequential dataset. 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.
Writing to a log dataset without using the system logger service This subsection describes how to write data to a log dataset without using the system logger service. How the data is written depends on the number of allocated log datasets. 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.
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.
Procedure 1. When you start using ISPF, delete the ISPF log information from the ISPF log dataset. 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.
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.
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.
Collecting trace information and logs
10 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.
Conventions This guide follows the conventions shown in Table 56 to refer to HP XP7 products.
Product reference Full name or meaning 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 Agreement Smart Manager for
Support and other resources
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.
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.
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.
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.
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.
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.
Example of a disk configuration definition file that is generated PAGE 234XML document type definitions for configuration files
B Commands that can be used in the ISPF panels This appendix describes the commands that can be used in the ISPF panels of Smart Manager for Mainframe. ERRCODE Function Displays the Error Code Help panel that shows error code details. Syntax ERRCODE Related topics • Error Code Help panel , page 116 FILTER Function Filters a list according to the specified condition. Syntax FILTER[{field-name Filter-condition|RESET}] The abbreviation of FILTER is FIL.
RESET Cancels the filter. TIP: The filtered results will be sorted in ascending order. Specification examples • Character string specification Specify as follows to filter the list by the SMS storage group named STORGRP1. FIL STORGRP STORGRP1 • Generic name specification Specify as follows to filter the list by volumes having a volume serial number beginning with V#704. FIL Volser V#704* • Range specification Specify as follows to filter the list by volumes having device numbers from 703B to 7050.
Parameters If you omit the parameter, the Find Options panel appears to allow you to enter parameter values. search-string Specifies the search string. Related topics • How to specify the search or filter conditions in ISPF panels, page 240 LOCATE Function Searches for the specified character string for a sorted field, and positions the cursor at the line that matches the specified condition.
TIP: If the FIND command has not been executed, the Find Options panel appears. SELECT Function Sets or cancels an action in the AC field of a line that satisfies the specified condition. Syntax SELECT[ field-name Select-condition[ {action|RESET}]] The abbreviation of SELECT is SEL. Parameters If you omit the parameters, the Select Options panel appears to allow you to enter parameter values. field-name Specifies the name of the field for which the condition is specified.
SEL Volser VOL* D • Range specification Specify as follows to cancel the actions set in the AC fields for the volumes having device numbers from 0F10 to 0F15. SEL Devn 0F10:0F15 RESET Related topics • How to specify the search or filter conditions in ISPF panels, page 240 SORT Function Sorts information in a displayed list. Syntax SORT[ field-name [{A|D}]] The abbreviation of SORT is SO. Parameters If you omit the parameters, the Sort Options panelappears to allow you to enter parameter values.
TIP: If you execute the SORT command when the list is filtered, the filtered information is sorted. How to specify the search or filter conditions in ISPF panels The following describes how to specify conditions for searching for a line or filtering in the ISPF panel.
Yes: Can be specified --: Cannot be specified # If you want to specify a string in the command line, specify it as follows: • To specify a string that contains non-alphanumeric characters, enclose the entire string in apostrophes ('). • To specify a string that contains an apostrophe, specify two apostrophes in succession ('').
Commands that can be used in the ISPF panels
C 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.
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.
/* 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.
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.
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.
/* 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.
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.
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.
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).
/* 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.
/* * 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.
/* 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.
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.
*/ 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.
/* 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.
/* */ /**********************************************************************/ /* */ /* 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.
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.
/* * 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.
* 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.
/* 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.
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.
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.
*/ 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.
*/ 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.
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.
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.
/* * 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.
/* 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.
/* 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.
/* * 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.
/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.
Sample scripts
D Upgrading Smart Manager for Mainframe This appendix describes how to upgrade Smart Manager for Mainframe. Workflow for upgrading Smart Manager for Mainframe The following figure shows the Workflow for upgrading Smart Manager for Mainframe. Figure 31 Workflow for upgrading # You do not need to delete and register a user SVC if the currently enabled user SVC version satisfies the conditions for the user SVC that are prerequisites for Smart Manager for Mainframe after upgrading.
Preparation for upgrading Smart Manager for Mainframe The following describes the tasks that must be performed before upgrading Smart Manager for Mainframe. 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.
TIP: When you back up and rename files, make sure that you change only the prefix of the file names. Because a file name contains information such as tiering policy group IDs, changing a file name might cause file consistencies to be lost, preventing Smart Manager for Mainframe from operating.
2. If this version is older than the prerequisite user SVC version of Smart Manager for Mainframe after upgrading, disable (comment out) the SYMDEF statement that contains the &YKSVCNO system symbolic name in the IEASYMxx parmlib member, as shown below: /* SYMDEF(&YKSVCNO='SVC-number') */ 3.
3. If the user SVC has been registered by using the IEASVCxx parmlib member, remove the linkage of the HPQYLPAT load library for LPALIB. (This step is unnecessary if the user SVC was registered by using the YKALCSVC command.) • If the load library for LPALIB has been statically linked by defining it in the LPALSTxx parmlib member, delete the definition. • If the load library for LPALIB has been dynamically linked to LPALST by using the SETPROG LPA command, use the SETPROG LPA command to remove the linkage.
Upgrading Smart Manager for Mainframe
E 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.
//********************************************************************* //* //* All Rights Reserved. Copyright (C) 2013, 2014, 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.
// // //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..
//* All Rights Reserved. Copyright (C) 2013, 2014, Hitachi, Ltd. //* //********************************************************************* //* //* This JOB uses TSO RECEIVE command to receive the data sets //* that were allocated by ALLOUPLD JCL and contain the unzipped //* .XMIT files that were uploaded via binary FTP transfer. //* //* Instructions: //* 1. Logon with the same USERID used for ALLOUPLD job. //* 2. Change 'HP.' prefixes to suit your naming convention. //* 3.
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.
// 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..F1,DISP=SHR SAMPLIB dataset //INF2 DD DSN=&IPFX..
COPYMOD COPYMOD COPY COPY COPY COPY COPY COPY 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.
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.
// // // // 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. (1) to (3) Modify the JOB statement in accordance with the installation environment.
// 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..HPQKPRCT, PROC LIBRARY // DISP=(NEW,CATLG,DELETE), // UNIT=3390,VOL=SER=&TVSN, // SPACE=(TRK,(5,1,10)), // DCB=(BLKSIZE=6160,LRECL=80,RECFM=FB) //HPQKEXET DD DSN=&PFX..&VRM..
//HPQKEXED // // // // //HPQKEXVD // // // // //HPQKPNLD // // // // //HPQKMSGD // // // // //HPQKTABD // // // // DD DD DD DD DD 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..
//* //********************************************************************* //* //* This JCL executes SMP/E DDDEF for the distribution libraries and //* the target libraries. //* //* Instructions: //* 1) Modify the JOB statement to match your environment.
ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ADD ENDUCL. SET UCLIN. ADD ADD ADD ADD (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. DDDEF(HPQKLPAT) DA(HPQKT.
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.
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.
// 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
//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, 2014, Hitachi, Ltd. //* //********************************************************************* //* //* This JCL executes SMP/E APPLY to create the target libraries. //* //* Instructions: //* 1) Modify the JOB statement to match your environment.
//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 .
//* //* 3) Submit the JCL and make sure that no error occurs. //* 4) Remove CHECK operand from ACCEPT and re-submit the JCL to //* complete.
Modifying the sample JCL
F 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.
Symbol Convention <> 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.
Glossary This glossary describes the terms used in this manual. AC field An entry field used to specify an action in an ISPF panel. The action specified in the AC field is executed for the corresponding line when Enter is pressed. Business Continuity Manager A program used for building a highly reliable backup system in which multiple data centers are linked together.
event log The log in which operations of Smart Manager for Mainframe are logged. The logged data includes messages, information about parameters used when I/O errors occurred, and command parameter information. host-discovered array index structure A REXX variable structure storing information that indicates the storage system and volume configurations. host-discovered array structure A REXX variable structure that stores the values set for a storage system or volume.
SMP/E An IBM installer. SMS storage group An aggregate of the volumes that constitute the storage pool managed by DFSMS (storage management environment in IBM MVS). SN The serial number of a storage system. storage system serial number A number assigned to each logical disk controller (DKC). This is also called a logical DKC serial number. SVP (service processor) An internal computer in a storage system. Maintenance personnel use it when analyzing maintenance information or diagnosing devices.
Glossary
Index A AC field, 303 ALLOUPLD (sample JCL), 281 ARRAYS parameter [KTSCAN command], 161 ARRAYS parameter [KTSTORE command], 164 attributes of the distribution libraries (DLIB), 54 attributes of the target libraries, 33 B Business Continuity Manager, 303 C calculating required memory, 53 CLI command, 303 CLI command coding format, 141 CLI command-execution log, 204, 303 CLI commands, 139 collecting trace information, 203 collecting trace information and logs, 203 COMMAND field, 303 command syntax descripti
HPQKT1AL [sample JCL], 289 HPQKT2DF [sample JCL], 291 HPQKT3RC [sample JCL], 295 HPQKT4AP [sample JCL], 296 HPQKT5AC [sample JCL], 298 I installation and setup, 27 overview, 27 Installation Management area, 119 installation using SMP/E, 31 ISPF panels, 107 K KTACTTPG command, 142 KTALCSVC command, 177 KTCONMSG command, 168 KTDCTDEV command, 143 KTDCTTPG command, 145 KTDSPENV command, 177 KTENV command, 170 KTERCODE command, 172 KTGETHDA command, 146 KTIMPORT command, 148 KTINSCHK command, 173 KTLOAD comma
PREFIX parameter [KTGETHDA command], 147 PREFIX parameter [KTIMPORT command], 149 PREFIX parameter [KTLOAD command], 151 PREFIX parameter [KTSTORE command], 164 Preparing to use Smart Manager for Mainframe, prerequisites for Smart Manager for Mainframe, 21 progress of tier relocation checking (CLI commands), 100 R RAID Manager, 304 RECVUPLD (sample JCL), 283 registering a license by entering a license key, 50 registering a license by using a license key file, 49 registering a user SVC, 38 registering licen
tiering policy, 305 applying (CLI commands), 98 applying (ISPF panels), 65 changing (CLI commands), 103 changing (ISPF panels), 81 verifying (CLI commands), 99 tiering policy group, 305 adding volume (CLI commands), 104 adding volume (ISPF panels), 82 changing (ISPF panels), 81 defining (CLI commands), 96 defining (ISPF panels), 60, 62, 64 defining and verifying (CLI commands), 92 verifying (ISPF panels), 60 tiering policy group definition file, 23, 305 Tiering Policy Group Definition panel, 127 Tiering Pol
