IBM Tivoli Advanced Allocation Management details
Prevention and avoidance of x37 abends
Automatically add a secondary allocation if one is not specified, and reduce secondary allocation to the largest available free extent. Increase the size of the secondary allocation as data set extends occur after a particular extent and at a particular volume number. You can recover unused disk space by automatically releasing allocated, unused data set space at data set close.
Recovery from x37 abends
Control reduction of primary space to satisfy allocation and add volumes dynamically at end of volume processing. You can recover from secondary allocation space failures by reducing the allocation amount to a value that is consistent with the current free space on the volume. You can also increase PDS directory size dynamically, if exhausted.
Centralized allocation management
Set allocation attributes that are not specified, or override sub-standard attributes. Control allocation attributes such as SMS-managed, non-SMS-managed, UNITNAME, UNITTYPE, VOLSER, DATACLAS, STORCLAS, MGMTCLAS, RECFM, LRECL, BLKSIZE, DISPOSITION, SPACE parameters, expiration date and retention period. You can fail jobs that specify installation-restricted allocation values and cause SMS DATACLAS values to override values specified through JCL, DEFINE statements or dynamic allocation.
Integration with TEP
Connect IBM® Tivoli® Advanced Allocation Management to IBM Tivoli OMEGAMON® XE for Storage through IBM Tivoli Enterprise Portal (TEP) to achieve integration with related storage management capabilities and to monitor the effect of allocation abends. You can view information and be alerted to situations from a single, graphical interface through integration with TEP.
SMF cost-saving reporting utility
Evaluate potential cost savings by generating a projected savings report using a System Management Facility (SMF) reporting utility. The report provides estimates of the costs associated with recoverable space related abends and a projected annual savings summary.
Name filtering and customization
Use BASIC as well as EXTENDED1 and EXTENDED2 options that match two methods of performing pattern matching within Interactive System Productivity System Facility (ISPF). User-defined variables allow further processing customization. User-defined variables are identified in the variables definition member (VARDEFS). Once defined in the variable definition member, the variable can then be specified on select RULEDEF keywords as well as the VGRPDEF keyword VOLUMES.
Extensive selection criteria
Extend your flexibility with support for multiple operands, including DATACLAS, DDNAME, DSNAME, DSNAME_QUALIFIER, JOBNAME, MGMTCLAS, STORCLAS, STORGRP, PROGRAM and USERID. Enhance comparison operator support with expanded selection criteria keyword options, including DSORG (EQ and NE only), VOLSER_ANY, VOLSER_CURRENT and VOLSER_FIRST.
Support VSAM data sets, including KSDS, ESDS, RRDS, VRRDS, and LDS, alternate indexes and index and data components of clusters, where applicable. IBM Tivoli Advanced Allocation Management does not support VSAM record-level-sharing (RLS) access mode.
Volume group and data set support
Define DASD groups from which to select additional volumes as needed. Includes support for: Virtual Storage Access Method (VSAM) and non-VSAM; Storage Management Subsystem (SMS) and non-SMS-managed; physical sequential; partitioned; striped and dynamically allocated data sets. Also includes support for the LARGE data set format, which allows the specification of more than 65535 tracks for the primary and secondary allocation for non-VSAM data sets specified with a DSNTYPE of LARGE.
EAV and IAM support
Support IBM z/OS® V1.10 EAV functionality for VSAM data sets and the EAV functionality added in z/OS V1.11 for Extended Format Sequential data sets as well as EAV functionality added in z/OS 1.12. Gain support for virtually all functions that apply to IAM data sets with VOL_ADD support for IAM data sets.
Access IBM Tivoli Advanced Allocation Management through an online user interface that enables authorized users to issue operator commands to view and update subsystem information, activate rule and volume group definitions, and enable or disable specific product functions, such as product-level intercepts, from an operator console.
Ignore IBM Db2® subsystem allocations
Eliminate the creation of unnecessary control blocks and reduce CPU time associated with allocations done by IBM Db2 subsystems.
To run the base product: IBM z/OS V1.11 or later. To run the workstation interface: IBM Tivoli Monitoring V6.2.
Any machine capable of running IBM z/OS V1.11 or later.