Part Two
#9 - Disk Storage Management, ISMF

Background:

Physical direct access storage used by z/OS today is provided on hardware such as the IBM DS8880 that can scale from 3 terabytes to more than 3 petabytes of physical storage capacity. A single mainframe, and indeed, even each LPAR on the mainframe can have many physical hardware storage controllers attached, each of which could potentially scale to more than 3 petabytes. Thus, a single mainframe is capable of processing an enormous amount of big data.

IBM provides on z/OS a suite of Data Facility Storage Management Subsystem (DFSMS) products to manage both user-managed storage (NONSMS) and Systems Managed Storage (SMS). Mainframe storage administrators use DFSMS to automate and simplify storage and data management tasks using SMS-managed storage.

SMS managed storage has several benefits. For example, when an application or user wants to allocate new data sets, instead of being required to know ahead of time which volume serial numbers can be used, and finding volumes with enough free space, SMS can do those tasks based on criteria defined by the storage administrator. SMS management also provides tools that help a storage administrator control allocation of storage between hundreds of different applications and users.

A storage administrator uses ISMF to manage DASD, tape and optical storage attached to a z/OS system or collection of z/OS systems called a sysplex. The storage administrator defines SMS constructs which define characteristics associated with or assigned to data sets, objects and volumes. Some of the constructs are:

  1. Data classes - data set properties automatically assigned by DFSMS when a data set is created.
  2. Storage classes - Availability, Accessibility and Performance requirements.
  3. Management classes - Data migration, backup and retention attributes.
  4. Storage Groups - a list of storage volumes with common properties.

The storage class constructs allow you to simply specify a storage class and how much space you need, or the storage administrator can define routines that automatically assign a storage class based on criteria like data set name. The storage administrator also defines associations between storage classes and storage groups.

On TSO/ISPF, both storage administrators and users, such as programmers, can use the Interactive Storage Management Facility (ISMF). ISMF is option (IS) on the contest system. There are two main options provided by ISMF, Storage Administrator Mode and User Mode. The default mode on the contest system is User Mode, and is the mode that will be used for this challenge.

Your challenge:

In this challenge, you will use ISMF as a user of the system. Even though you are not able to directly modify storage groups, you are able to list volumes that are associated with storage groups. First, you will list all the SMS managed volumes on the contest system. Next, you will generate a report of volumes for a storage group, and include details about the amount of free space available.

Then you will list information about your own data sets, allocate a new SMS managed data set on a volume in the storage group set up for the contest, and generate a report with selected information about your new SMS managed data set. Finally, you will store the two reports you created in your P2.OUTPUT library.

Use the F1 (Help) option to navigate the ISMF panels, and to find additional information for this challenge.

z/OS User manuals to help you with this challenge:

STEP 1: Use ISMF option 5 "Storage Class" to generate a list of all the SMS managed volumes on the contest system.

  1. First, submit CC#####.JCL(ISMFALC). This job allocates physical sequential output data sets where you will store reports created by ISMF.
  2. Next, jump to the ISMF panel option 5 (=IS.5), the STORAGE CLASS APPLICATION SELECTION. Enter * nex to Storage Class Name.
    This will generate a list of all SMS storage classes on the contest system. Note the storage classes that start with "DB" are used later in the contest by a DB2 relational database.
  3. Press F3 twice to return to the ISMF Primary Option Menu and select option 2, Volume - Perform Functions Against Volumes.
  4. Select Option 1 - DASD, and press enter. On the VOLUME SELECTION ENTRY PANEL, specify the following options:
          
    Select Source to Generate Volume List . . 2 (1 - Saved list, 2 - New list) 1 Generate from a Saved List Query Name To List Name . . Save or Retrieve 2 Generate a New List from Criteria Below Specify Source of the New List . . 2 (1 - Physical, 2 - SMS) Optionally Specify One or More: Enter "/" to select option Generate Exclusive list Type of Volume List . . . 1 (1-Online,2-Not Online,3-Either) Volume Serial Number . . * (fully or partially specified) Device Type . . . . . . . (fully or partially specified) Device Number . . . . . . (fully specified) To Device Number . . . (for range of devices) Acquire Physical Data . . Y (Y or N) Acquire Space Data . . . Y (Y or N) Storage Group Name . . . (fully or partially specified) CDS Name . . . . . . .
  5. Press the enter key. You will notice DEFAULT PRIMING DONE at the top. The following fields are primed, because you specified option 2 - SMS, as the source of the new list.
           
    Storage Group Name . . . * (fully or partially specified) CDS Name . . . . . . . 'ACTIVE'
  6. Verify that CDS Name says 'Active' and Storage Class Name is *, then press the enter key again.

    Scroll right. Look for STORAGE GRP NAME in column 23 to see how the volumes are subdivided into various storage groups.

    Press F3 to go back to the VOLUME SELECTION ENTRY PANEL. Change the Storage Group Name * to the name of the storage group that was associated with the four MTM* volumes and press enter.

    For more information about ISMF Volume and Data set selection lists, see Understanding format and content of the lists.

STEP 2: Generate a report that would help a user or storage administrator find how much capacity is in a storage group, so they can determine whether additional capacity is needed.

  1. At the top of the VOLUME LIST panel (from the end of step one), position your cursor over the List option and press the enter key. A pull-down list will be shown. Type the number associated with Print, and press the enter key.
  2. On the VOLUME PRINT ENTRY panel specify:
    Select Format Type . . . . . 1 (1 - Standard, 2 - Roster)
    Report Data Set Name . . . .ISMF.REPORT1.OUTPUT
    Replace Report Contents . . . Y (Y or N)
  3. Next, specify the numbers for following tags. Type the tag numbers, separated by spaces in the order that they appear in the list below:

    You will need to scroll forward and backward to locate the tag numbers requested in the list below. However, be careful, it is easy to accidentally overtype the default values.

    • Free Space
    • Free DSCBs
    • Device Number
    • Percent Free Space
    • Storage Group

    Press enter to get to the PRINT JOB SUBMISSION ENTRY PANEL

  4. On the PRINT JOB SUBMISSION ENTRY PANEL, you should see PANEL PRIMING NOT DONE at the top right side of the panel. Change the first option to 1 Submit Job for Background Processing, then press enter. This will open the ISMF DATA SET PRINT EXECUTE STATEMENT ENTRY PANEL. Press enter again and you'll receive a message indicating that a job was just submitted.

    The job will execute and the output of which will be the requested report. This report is written in your ISMF.REPORT1.OUTPUT data set. Press F3 until you area back to the ISPF Primary Option Menu, then jump to =3.4 and view the contents of your ISMF.REPORT1.OUTPUT data set. Confirm that it contains the columns you requested.
Note: You'll find an additional column was added: VOLUME SERIAL. This is expected, and for good reason: the volume serial or "VOLSER" is always relevant information!

STEP 3: Allocate an SMS-managed data set, and generate an ISMF report to list information about it.

A permanent new data set, such as most of your CC##### data sets, can be allocated on a NONSMS volume, without the need to specify a volume serial number if volumes with the "storage" attribute exist. There is no further granularity based on criteria such as data set name.

For system-managed data sets, the device dependent volume serial number (volser) and unit number information is not required, because the volser is assigned within a storage group selected by the Automatic Class Selection (ACS) routines. For more information, see z/OS V2R2 DFSMS Introduction - ACS routines.

For more information about the Data Class, Management Class, Storage Class and Aggregate Group applications of DFSMS, see Using Data Facility Storage Management Subsystem (DFSMS).

  1. Take a look at your CC#####.JCL member ISMFDS. This job allocates an SMS-managed data set, and uses a Data Class named MTMSEQ.

    Often a Data class is automatically assigned according to Automatic Class Selection routines set up by the storage administrator. However, as you see in your ISMFDS job a Data Class set up by the storage administrator can be specified in JCL. A SMS managed data set is not required to have a Data Class.

    Don't submit this job just yet, you'll need to perform some other actions first.

  2. From the ISMF PRIMARY OPTION MENU (=IS), select Option 4 - Data Class.
  3. Keep the defaults listed on the DATA CLASS APPLICATION SELECTION panel and press enter.
  4. From the DATA CLASS LIST panel, type DISPLAY in the LINE OPERATOR column next to MTMSEQ and press enter.
  5. On the first DATA CLASS DISPLAY panel, you will see some of the attributes that would be used during a new data set allocation, if the MTMSEQ Data Class was selected.

                        
    CDS Name . . . : ACTIVE Data Class Name : MTMSEQ Description : SEQUENTIAL DATA SETS Recfm . . . . . . . . . : FB Lrecl . . . . . . . . . : 80 Override Space . . . . . : NO Space Avgrec . . . . . . : K Avg Value . . . . : 1 Primary . . . . . : 1 Secondary . . . . : 1 Directory . . . . : Retpd Or Expdt . . . . . : Volume Count . . . . . . : 1 Add'l Volume Amount . . :

    A Data Class like MTMSEQ may (or may not) describe initial SPACE attributes. If Override Space is set to "YES", then the Data Class will override any SPACE settings specified in JCL. A value of "NO" allows the user to override the Data Class attributes inside JCL.

  6. Open CC#####.JCL(ISMFDS) for editing again.
  7. Update the JCL to specify the storage class name that has the same name as the storage group you specified at the end of STEP 1 on the VOLUME SELECTION ENTRY PANEL. Then submit the JCL.
  8. Look closely at the data set named in JCL DD DD1 definition. Type this data set name into =3.4 and enter an I next to the data set to open the information panel showing the data set attributes.

    You may notice even though MTMSEQ specifies only 1 KB, the data set occupies 54 kilobytes. In case you are wondering why, it's because the minimum allocation for a data set is 1 track.

  9. From the ISMF PRIMARY OPTION MENU (=IS) enter 1 to open the Data Set - Perform Functions Against Data Sets.
  10. Specify the following options on the DATA SET SELECTION ENTRY PANEL:
    		  
    1 Generate from a Saved List Query Name To List Name . . Save or Retrieve 2 Generate a new list from criteria below Data Set Name . . . ** Enter "/" to select option Generate Exclusive list Specify Source of the new list . . 2 (1 - VTOC, 2 - Catalog) 1 Generate list from VTOC Volume Serial Number . . . (fully or partially specified) Storage Group Name . . . . (fully specified) 2 Generate list from Catalog Catalog Name . . . Volume Serial Number . . . (fully or partially specified) Acquire Data from Volume . . . . . . . Y (Y or N) Acquire Data if DFSMShsm Migrated . . Y (Y or N)
  11. Press the enter key.
  12. Scroll right and left to see the information listed for your data sets.
    Note: You may need to set your Scoll option again on this panel.

    Notice the differences between your SMS-managed data set and your other data sets, such as VOLUME SERIAL, LAST BACKUP DATE, STORAGE CLASS NAME and DATA SET ENVIRONMENT.

  13. Use F3 to go back to the DATA SET SELECTION ENTRY PANEL, and specify the following:
              
    1 Generate from a Saved List Query Name To List Name . . Save or Retrieve 2 Generate a new list from criteria below Data Set Name . . . ** Enter "/" to select option Generate Exclusive list Specify Source of the new list . . 1 (1 - VTOC, 2 - Catalog) 1 Generate list from VTOC Volume Serial Number . . . (fully or partially specified) Storage Group Name . . . . MTM (fully specified) 2 Generate list from Catalog Catalog Name . . . Volume Serial Number . . . (fully or partially specified) Acquire Data from Volume . . . . . . . Y (Y or N) Acquire Data if DFSMShsm Migrated . . Y (Y or N)

    Press enter and you will be presented with all of your data sets that part of the MTM storage group.

  14. Generate another report using the List pull down option 9 for Print ....
  15. On the DATA SET PRINT ENTRY panel specify:
    Select Format Type . . . . . 1 (1 - Standard, 2 - Roster)
    Report Data Set Name . . . .ISMF.REPORT2.OUTPUT
    Replace Report Contents . . . Y (Y or N)
  16. Specify Tags to be Printed in this order:
    • DS Organisation
    • Record Format
    • Record Length
    • Volume Serial Number
    • Creation Date
    • Storage Class Name
    • DS Environment
    • Entry Type

Press enter, and just as before, on the PRINT JOB SUBMISSION ENTRY PANEL, change the first option to 1 to submit the job in batch. Then press enter until you get the message about the job being submitted.

Return to ISPF =3.4 and view ISMF.REPORT2.OUTPUT to confirm that it contains the requested information. Just like in the first report, the first column contains extra information here: "DATA SET NAME". This is expected.

STEP 4: Submit JCL(ISMFP2) to copy the two generated reports into your P2.OUTPUT data set.

Note: The sequential report data sets and the SMS managed data set that were created during this challenge are deleted upon successful exectution of ISMFP2.

Take a look at P2.OUTPUT(#09) to see the results and congratulations! You now know how use ISMF to perform SMS and non-SMS data management tasks on z/OS! Feel free to move on to the next challenge now.

Next: Challenge #10