Space Cube Modernization Guide

Space Cube analyzes disk and tape sequential dataset activity on z/OS systems. It stores this activity in an internal database, providing reports on dataset size, usage, and reference patterns over time. This allows organizations to understand how their storage resources are being used and identify potential inefficiencies.

Space Cube is a tool set designed for analyzing and reporting on storage activity. It is not a complete system or a general-purpose application, but rather a specialized tool that focuses on providing insights into dataset usage patterns.

Organizations that rely heavily on z/OS mainframe systems and need to manage large volumes of data on disk and tape are the best fit for Space Cube. This includes enterprises in industries such as banking, insurance, and government, where data storage and management are critical.

A company should consider using Space Cube when they need to gain better visibility into their dataset usage patterns on z/OS. This could be driven by concerns about storage costs, performance bottlenecks, or the need to optimize data placement and retention policies.

Alternatives to Space Cube include BMC AMI Storage solutions such as FDRPAS and COMPAKTOR, as well as other z/OS storage management tools. These products offer overlapping but not identical functionality, with differences in features, reporting capabilities, and integration with other systems.

Space Cube runs on the z/OS platform and is dependent on the z/OS operating system and its associated subsystems. It typically runs within an LPAR (Logical Partition) on the mainframe.

Space Cube requires access to z/OS system data to collect information about dataset activity. It likely uses standard z/OS interfaces and APIs to gather this data. Specific subsystems required may include SMS (Storage Management Subsystem).

Space Cube stores its collected data in an internal database. The specific type of database is not publicly documented, but it is likely a VSAM (Virtual Storage Access Method) or similar z/OS-native data storage mechanism.

Space Cube likely uses configuration files to define parameters such as data collection intervals, report definitions, and database settings. The exact format and location of these files are specific to the product.

Space Cube provides business value by enabling organizations to optimize their storage utilization, reduce storage costs, and improve system performance. By providing insights into dataset usage patterns, it helps identify underutilized or obsolete data, allowing for more efficient storage management.

Without Space Cube, organizations may lack visibility into their dataset usage patterns, leading to inefficient storage utilization, increased storage costs, and potential performance bottlenecks. They may also struggle to comply with data retention policies and regulatory requirements.

Space Cube integrates with the z/OS environment and can provide data to other systems management tools. It helps to understand the storage usage and can be used to improve the efficiency of other tools such as backup and recovery software.

Space Cube leverages the security features of the z/OS operating system to control access to its functions and data. It likely integrates with z/OS security systems such as RACF, ACF2, or Top Secret to authenticate users and authorize access to resources.

Space Cube likely uses an access control model based on roles and permissions, where users are assigned roles that grant them specific privileges to access data and perform functions within the system. This could be implemented using RBAC (Role-Based Access Control).

Space Cube generates audit logs that track user activity and system events. These logs can be used to monitor security, detect unauthorized access, and investigate security incidents. The logs likely include information such as user IDs, timestamps, and actions performed.

Space Cube is typically deployed on-premise within the z/OS environment. It requires technical expertise to install, configure, and maintain. Ongoing operational requirements include monitoring system performance, managing the internal database, and generating reports.

Implementing Space Cube requires a good understanding of z/OS systems, storage management concepts, and the organization's data storage environment. Common implementation challenges include configuring the system to collect the right data, tuning performance, and integrating with existing security systems.

Ongoing operational requirements for Space Cube include monitoring the system for performance issues, managing the internal database to ensure data integrity, and scheduling regular report generation to provide insights into storage utilization.