5 Things To Know About z/OS V2.1 DFSMS
MaryL. 110000D677 Visits (1731)
DFSMS is the standard methodology worldwide for managing enterprise data and storage on the z/OS platform. It provides an automated, centralized, policy-based solution for z/OS storage management. While there are many new enhancements in z/OS V2.1 DFSMS – the following are 5 of my favorite.
This DFSMS release introduces RLS usage for ICF catalogs in a parallel sysplex environment. The purpose of the enhancement is to meet requirements for better performance and availability on catalogs. Using RLS will improve performance by providing locking at a record level, replacing catalog level sharing. Catalogs using RLS will not need to access the VVR in cache. For Catalogs in RLS mode the catalog records are placed in RLS local buffer pools or CF cache structures.
RLS support for catalogs is optional and not supported for Master Catalogs at this time.
The new Storage Tier function in DFSMShsm will support moving data from the DFSMShsm managed Primary volumes to the most optimum hardware tier. Prior to DFSMS V2.1, there was no way to automatically move less active data between disk technologies, from the fastest and more expensive, to the slowest and cheaper. These disk technologies are solid state drives (SSD), hard disk drives (HDD), and
Serial Advanced Technology Attachment (SATA) drives. The data will ultimately move to tape. Data movement will occur as a Class Transition as part of the Primary Space Management.
z/OS V2.1 through DFSMS V2.1 provides Version 2 of PDSE data sets that can provide for improved performance, reduced path lengths, and improved index searches. New data sets can be allocated in Version 2 format by specifying the new version on the DSNTYPE keyword on the JCL DD statement or on the TSO/E ALLOCATE statement, or through an option in the ISPF 3.2 panel.
These enhancements are intended to provide additional scalability and usability benefits of using PDSEs in place of PDSs, make it feasible to use PDSEs instead of multiple large sequential data sets, and help reduce the space required for PDSEs.
In DFSMS V2.1, when SMS receives a request for space information, it compares the information in the DCE with the information inside the SMS address space. It automatically refreshes the space information inside the active configuration data set (ACDS) of SMS, returning accurate space statistics to the caller that requested this information.
This is by far my favorite! I am working with a team of storage experts from around the world who are hard at work producing an IBM Redbooks publication that provides a summary of the functions and enhancements integrated into z/OS V2.1 DFSMS. The information in the publication provides you with the information you need to understand and evaluate the content of this DFSMS release, along with practical implementation hints and tips. The information will allow you to start prioritizing the implementation of new functions and evaluating their applicability in your DFSMS environment.