End of support

   

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Databases and collection data sets in version 7.9

The structure of the Storage Guard Perform (SGP), Space collection, and Capacity Planning databases have changed in version 7.9. The structure of the VTOC Scan (VSCAN) data set has also changed. The version 7.8 and prior databases and VSCAN files cannot be used in version 7.9 and the version 7.9 databases cannot be used in any prior releases.

New SGP databases must be created and initialized for version 7.9 of MainView SRM along with the creation of a new SGP started task. 

Warnings

  • Review the following documentation and take great care in following the instructions. Using a version 7.8 database in version 7.9 will corrupt the database and make it useless for version 7.8 or 7.9 of the MainView SRM products.
  • Ensure that the most recent maintenance is applied to the MainView SRM products prior to creating, initializing, and converting any of the databases.

To create and initialize the SGP databases

  1. Create new SGP databases.
    1. Review the CALCPERF member in SAMPLIB to determine space allocations for the new databases.
    2. Customize and execute the SGPALCDB member in SAMPLIB to create and initialize new SGP database files.
  2. Create and customize a new SGP PROC.
    1. Using the SGPPROC in SAMPLIB create and customize a new SGP procedure.
    2. Ensure the STEPLIB in the new SGP PROC is using  the new version 7.9 LOADLIBs.
    3. Ensure the database DD statements SGPHDBxx in your new SGP PROC have been set to the new database files.
  3. Update the version 7.9 SVOS PARMLIB.

    Ensure that the “PERFRM_PRC=” in the SMMSYSxx member in the PARMLIB used in your version 7.9 SVOS started task has been set to the new SGP started task name.

To convert the Space and Capacity Planning databases

The Space and Capacity Planning databases have been altered in version 7.9 of MainView SRM and therefore cannot be carried forward without first converting them. The conversion process does not alter the version 7.8 databases, allowing you to run the conversion multiple times (if necessary) and keeps the version 7.8 databases available for any SVOS started tasks that are still running version 7.8.  The conversion members supplied in SAMPLIB contain the instructions for the conversion; however, you should review and familiarize yourself with the following steps before proceeding:

  1. Create new Space and Capacity Planning databases.
    1. Review the CALCSPAC member in SAMPLIB to determine the space allocations for the new databases.
    2. Customize and execute the SGDACPDB member in SAMPLIB to create the Capacity Planning databases.
    3. Customize and execute the SGDALCDB member in SAMPLIB to create the Space databases.
  2. Run the conversion.
    1. Prior to running the conversion jobs, stop the space collector (SVSGD) that is using the version 7.8 databases.
    2. Customize and execute the SGDCONVC member in SAMPLIB to convert the version 7.8 Capacity Planning databases into the new version 7.9 databases.
    3. Customize and execute the SGDCONVS member in SAMPLIB to convert the version 7.8 Space databases into the new version 7.9 databases.
  3. Update the version 7.9 SVOS SMDBASxx PARMLIB member.

    The SMDBASxx member contains the definition for the CP and SP databases. Ensure your new version 7.9 SVOS PROC has the correct PARMLIB defined and the correct SMDBASxx member defined in SMMSYSxx. The SMDBASxx member should have the correct (new) version 7.9 CP and SP databases defined.

Note

The conversion process alters the character director number of the Physical Disk ID of EMC devices to the actual hexadecimal representation of the number to better match displays using EMC commands. For example, the ABCDE-55-C1 ID is converted to ABCDE-37-C1.


To create a new VSCAN data set

The VSCAN data set has been altered in version V7.9 of MainView SRM and therefore a new data set must be created. The following process should be executed prior to running any VSCANs:

  1. Edit the active SMMSYSxx member (or what will be your active SMMSYSxx member) of your version 7.9 SVOS started task.
  2. Update the VSCAN_OINDX= parameter using a different data set name prefix than you have for the prior release of MainView SRM.
  3. Save the SMMSYSxx member.  
  4. If your SVOS started task is 
    1. Active, issue the refresh command against the member.  
    2. Not active the change will take affect when you start SVOS.

Do not use the version 7.9 VSCAN data set in prior versions of MainView SRM.

Was this page helpful? Yes No Submitting... Thank you

Comments