z/OS DFSMS Implementing System-Managed Storage
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Planning Your Migration

z/OS DFSMS Implementing System-Managed Storage
SC23-6849-00

There are several major tasks for migrating database data to system management:
  • Designing the storage classes and ACS routine
  • Designing the management classes and ACS routine
  • Designing the storage groups and ACS routine
  • Testing your SMS configuration
  • Activating the new SMS configuration
  • Migrating the end-user databases and related database data sets
  • Testing migrate/recall performance for end-user databases
  • Migrating the production databases and related database data sets

For CICS®, IMS™, and DB2®, you must ensure that any database data sets you plan to system-manage are cataloged using the standard search order. In particular, check image copies and logs to ensure that they are cataloged.

CICS data can benefit from compression, extended format, extended addressability, secondary volume space amount, and dynamic cache management enhancements when the data sets are KSDSs. Batch programs accessing this data can benefit from system-managed buffering.

For IMS data, consider converting any OSAM data sets to VSAM. By converting to VSAM, you can benefit from enhanced dynamic cache management. IMS Version 5 supports enhanced dynamic cache management for OSAM data sets. KSDSs being used by IMS can be extended format but cannot be compressed because IMS uses its own form of compression and cannot tolerate compression performed by DFSMS.

For DB2 data, complete the following tasks:
  • Verify consistency between DB2 STOGROUPs and SMS storage groups. See Relating DB2 STOGROUPs to SMS Storage Groups for more information.
  • Ensure that SMS management class expiration attributes are synchronized with DB2's expiration information:
    • Expiration of logs must be consistent with the value of ARCRETN. You should update the BSDS with the DB2 change log inventory utility.
    • Expiration of any DB2 index spaces or table spaces requires a proper SQL DROP.
    • Expiration of any DB2 image copies requires running the MODIFY utility to update SYSCOPY.
  • Set DSNZPARM to have DFSMShsm automatically recall DB2 data sets during DB2 access. Set RECALL to Y. Set RECALLD, the maximum wait for DFSMShsm to complete re-creation of data sets on primary storage, based on testing with typical end-user database data sets.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014