•The number of volumes in the Storage Group satisfies the volume count

•Accessibility requested

•Availability (dual copy or RAMAC) requested

•The volume was explicitly requested and guaranteed space is YES

•Sufficient free space to perform the allocation without exceeding the high threshold

•Volumes fall within a pre-determined range of millisecond response times based on the request

•The volume supports extended format if EXT=PREFERRED or REQUIRED is requested in the data class

Candidates for secondary volumes are primary volumes that, in addition:

•Are at or above high threshold, or exceed high threshold following the allocation.

•Are quiesced, or the Storage Group to which the volume belongs is quiesced.

•Did not meet the requested millisecond response time.

•Did not meet the accessibility request of standard or preferred.

•Did not meet the IART of greater than zero.

•Did not meet the availability request of standard or preferred.

When a Storage Group does not contain enough volumes to satisfy the volume count, all volumes in the Storage Group are flagged tertiary. Tertiary volumes are only selected when there are no primary or secondary volumes and the request is for a non-VSAM non-GUARANTEED SPACE request.

After the system selects the primary allocation volume, that volume's associated Storage Group is used to select any remaining volumes requested.

5.3.4.2 Planning for Implementation

It is important that unique Storage Groups are used for production databases and recovery data sets, because of their critical status. Appropriate groups should be defined by the storage administrator to prevent automatic migration (AUTO MIGRATE), and automatic backup (AUTO BACKUP). However non-production databases should be considered for placement on standard primary volumes (possibility shared with other data types), as their availability is normally not as critical.

DB2 allows the DBA to define a collection of volumes that DB2 uses to find space for new data set allocation, known as STOGROUPs. When converting DB2 databases to SMS, and DB2 STOGROUPs are used to manage DB2 database data, one way is to design the SMS Storage Groups so they are compatible with existing STOGROUP definitions.

Once the conversion is complete, it is recommended that SMS be used, rather than DB2 to allocate databases. To allow SMS control over volume selection, define DB2 STOGROUPs with VOLUMES(*).

44Storage Management with DB2 for OS/390

Page 65 Page 67
Page 66
Image 66
IBM 5655-DB2, 5695-DF1 manual Planning for Implementation
Page 65 Page 67

5695-DF1, 5655-DB2 specifications

IBM 5655-DB2 and 5695-DF1 are significant components within the IBM software ecosystem, predominantly focusing on data management and integration solutions. These offerings cater primarily to enterprise environments that require robust database management systems and associated frameworks to maintain and manipulate data efficiently.

IBM 5655-DB2 is a well-known relational database management system (RDBMS) that excels in managing large volumes of structured data. Its architecture is designed to support high availability, scalability, and performance, crucial for businesses operating in today’s data-driven world. Some of its main features include advanced indexing capabilities, support for complex queries, and dynamic workload management. Additionally, it provides strong concurrency controls, which enable multiple users to access and manipulate data simultaneously without compromising data integrity.

One of the key characteristics of DB2 is its support for various data types, including JSON and XML, making it versatile for modern applications that generate data in diverse formats. It also features robust security mechanisms to protect sensitive data, aligning with compliance standards across industries. Integration with analytics tools further allows businesses to derive insights from their data, enhancing decision-making processes.

On the other hand, IBM 5695-DF1, also known as the InfoSphere DataStage, is a powerful data integration tool that facilitates the extraction, transformation, and loading (ETL) of data from various sources to target systems. It empowers organizations to streamline their data flows, ensuring that clean, consistent information is available for analysis and operational use. Key features of 5695-DF1 include a user-friendly graphical interface that enhances developer productivity and a rich set of connectors for numerous data sources, enabling seamless data integration.

DataStage also supports real-time data integration, allowing businesses to keep their data synchronized across multiple platforms. Its parallel processing capabilities dedicatedly optimize performance, enabling organizations to handle vast datasets efficiently. It incorporates data quality tools that help in validating and cleansing data before it is used for decision-making processes.

Both IBM 5655-DB2 and 5695-DF1 are part of a broader strategy to accommodate the evolving landscape of data management. Businesses leverage these technologies to enhance their data architectures, fostering agility and competitive advantage in their respective markets. Their integration capabilities, along with a focus on security and scalability, position them as vital assets in modern enterprise environments. Whether managing critical data within a database or ensuring seamless data flow across systems, these IBM offerings provide a comprehensive approach to handling complex data challenges.
Top Page Image Contents