Why is UDM necessary?

 Management of z/OS storage is becoming more of a challenge due to the ever-increasing size of Data Storage farms and the decrease in the manpower to TeraByte ratio to manage this Storage. The net result is critical management processes, such as Audits of the Catalog environment, are being ignored while other tasks, such as the initializing of volumes, are performed without the time to ensure the required checks have been actioned, thereby increasing the possibility of user errors.

UDM solves these issues by simplifying and automating most of the tasks involved in managing your data.

Distributed with UDM are a series of processes which collectively provide an out of the box solution:

Additionally, UDM provides the ability to define and test your Service Level Agreements on a single system and then via a single mouse click provides the ability to propagate the processes to manage these service levels to all your Systems.

Who is UDM designed for?

UDM fits seamlessly into any Data Center thanks to its flexible architecture. Customers with existing third party products can easily tailor UDM to interface with these existing products.

Irrespective of the Data Center size, UDM provides immediate benefits:

Storages managers, operations support, systems programmers and capacity planners can all benefit from the UDM features:

When should UDM be used?

UDM can be used to proactively monitor your Systems, or it can be used to perform adhoc tasks on request.

By activating UDM on a System, simply by starting the Started task, UDM will be automatically monitoring and maintaining your Systems as well as collecting historical information on your System for further analysis.

Once active, UDM provides a comprehensive set of processes which allow you to perform common tasks, such as the following:

2-Defrag JCL_21
Identify volumes with a high Fragmentation Index and then build and submit DFDSS DEFRAG control cards.

3-JCL Decks_21
Generate and submit IDCAMS DEFINE ALIAS control cards on all Sysplexes to define a new Userid.

4-Report decks_21
List all datasets associated to specific mask across all Systems and Sysplexes and generate control cards to delete them. Identify who is filling up the spool by running the Spool report, grouping by Ownerid and Summarizing by Record count

5-HSM swaplog_21
Trap message IGD008I (DFSMS configuration activated), locate the active SCDS and ACS routines, and create a date timed backup of the datasets. Automatically issue a DFHSM SWAPLOG command on all systems at midnight.