IBM Tivoli Advanced Allocation Management for z/os. User's Guide. Version 3 Release 1 SC

Transcription

1 IBM Tivoli Advanced Allocation Management for z/os User's Guide Version 3 Release 1 SC

2

3 IBM Tivoli Advanced Allocation Management for z/os User's Guide Version 3 Release 1 SC

4 Note: Before using this information and the product it supports, read the information in Notices on page 353. This edition applies to Version 3 Release 1 of IBM Tivoli Advanced Allocation Management for z/os (product number 5697-P35) and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright Rocket Software Inc., 2003, 2009

5 Contents About this guide xi Intended audience for this guide xi Publications xi Accessing publications online xii Ordering publications xii Accessing terminology online xii Tivoli technical training xiii Support information xiii Conventions used in this publication xiii Typeface conventions xiii Chapter 1. Advanced Allocation Management overview What does Advanced Allocation Management do? Features and benefits Advanced Allocation Management components Advanced Allocation Management architecture and processing Started task and subsystem definition Compatibility with other products Summary of changes Chapter 2. Installation and security considerations Hardware and software prerequisites Installing and implementing Advanced Allocation Management Migration considerations and requirements Migration steps Step 1: Planning Step 2: Install Advanced Allocation Management in a test environment Step 3: Convert product definitions and test Step 4: Migrate to production Migration and installation documentation Security considerations Securing the control data set Securing user interface update functions How Advanced Allocation Management uses RACF to determine access to update functions Security and internal work data sets Security and definition management Authorizing the started task for selected NOTCAT2 functions Chapter 3. Configuring Advanced Allocation Management Configuration summary Configuration steps Step 1: APF-authorize the load libraries Step 2: Configure the started task JCL Step 3: Allocate the control data set Step 4: Specify subsystem options Step 5: Secure the user interface update functions Step 6: Configure the CLISTs and start the Advanced Allocation Management user interface Step 7: Start the started task Step 8: Verify the installation Chapter 4. Advanced Allocation Management definition management iii

6 The control data set Control data set requirements and guidelines Modifying control data set members Activating rule and volume group member definitions Implementing multiple instances of Advanced Allocation Management Using separate control data sets for multiple instances Using a shared control data set for multiple instances Guidelines and recommendations for implementing Advanced Allocation Management Chapter 5. Using the Advanced Allocation Management user interface Accessing the Tivoli Advanced Allocation Management Primary Option Menu 35 Tivoli Advanced Allocation Management Primary Option Menu options Accessing online help Managing control data set members Specifying a control data set Specifying a control data set by selecting the subsystem ID from a list of active subsystems Selecting control data set members Control member management options Creating a new control data set member using the Edit option Viewing and updating subsystem options Fixed Subsystem Settings Modifiable Subsystem Settings Status Information Modifiable Product-Level Settings Displaying Advanced Allocation Management recovery statistics Advanced Allocation Management Recovery Statistics Viewing event history Input Options Report Options Output Options Chapter 6. Using rule definitions to define processing How rule definitions work Rule definition syntax Syntax precedence Rule definition evaluation Creating and modifying rule definitions Rule definition member requirements Determining the functions to include in rule definitions Establishing rule definition default processing Including or excluding items from processing Specifying multiple functions or selection criteria Activating rule definitions Displaying active rule definitions Recommendations and guidelines Function and rule definition examples Advanced Volume Selection (AVS) Continue RULEDEF processing (CONTINUE) Initialize a newly allocated data set (DATASET_INIT) Process NOT CATLGD 2 errors (NOTCAT2) Dynamic PDS directory increase (PDS_DIR_INC) Controlled reduction of primary space (PRIM_REDUCE) Test a rule definition (RULEDEF_TEST) Add a secondary allocation (SEC_ALLOC) iv IBM Tivoli Advanced Allocation Management for z/os : User's Guide

7 Reduce secondary allocation to largest available free extent (SEC_BEST) 66 Increase the size of secondary allocation (SEC_INC) Recover from secondary allocation space failures (SEC_REDUCE) Recover unused disk space (SPACE_RELEASE) Terminate an allocation (TERM_ALLOC) Dynamically add volumes (VOL_ADD) Using comparison operators Setting allocation attributes using Enhanced Allocation Management functions 72 Specifying $NULL Data class override ($DCOC and $DCOU) Space recovery strategies Chapter 7. Defining volume groups Sample volume group definition member Volume group definition syntax Creating and modifying volume group definitions Volume group definition member requirements Activating volume group definitions Displaying volume group definitions Single volume group list example Multiple volume group lists example Chapter 8. Specifying Advanced Allocation Management syntax Specifying multiple operands Specifying lists of items Including comments Using wildcard characters Chapter 9. Rule definition syntax Main keywords DEFAULTS INCLUDE EXCLUDE Functions Enhanced Allocation Management functions Selection criteria keywords Comparison operands String comparisons Numeric comparisons Null or unspecified values ($NULL) Character string values Numeric suffixes Data class override $DCOU (unconditional override) $DCOC (conditional override) ACS environment considerations Space parameter considerations How allocation attributes are used during selection criteria processing Function and selection criteria environment compatibility Chapter 10. Function keywords AVS AVS_ALGORITHM AVS_MOUNT_USAGE AVS_UNIT AVS_VGRP Contents v

8 AVS_VGRP_SEARCH AVS_VSER CONTINUE DATASET_INIT DIAG ENVIRONMENT MESSAGES MSG_DESTINATION MSG_LEVEL NOTCAT NOTCAT2_CHECK NOTCAT2_QUALIFIER NOTCAT2_QUALIFIER_POSITION NOTCAT2_SUFFIX PDS_DIR_INC PRIM_REDUCE PRIM_REDUCE_INC PRIM_REDUCE_LIM RULEDEF_TEST SEC_ALLOC SEC_ALLOC_AMT SEC_BEST SEC_BEST_LIM SEC_INC SEC_INC_AMT SEC_INC_VOLNO SEC_INC_XTNT SEC_REDUCE SEC_REDUCE_INC SEC_REDUCE_LIM SPACE_RELEASE TERM_ALLOC VOL_ADD VOL_ADD_ALGORITHM VOL_ADD_LIM VOL_ADD_MOUNT_USAGE VOL_ADD_PROMPT VOL_ADD_SGRP VOL_ADD_UNIT VOL_ADD_VGRP VOL_ADD_VGRP_SEARCH VOL_ADD_VSER WRITE_MSG Chapter 11. Enhanced Allocation Management function keywords $DCO SET_ACCBIAS SET_ADISP SET_BLKSIZE SET_BUFSPC SET_CISZ SET_CISZ_DATA SET_CISZ_INDEX SET_CONTIGUOUS SET_DATACLAS SET_DEFERMOUNT vi IBM Tivoli Advanced Allocation Management for z/os : User's Guide

9 SET_DIRBLKS SET_DSNAME_TYPE SET_DSORG SET_EXPDATE SET_EXTADDR SET_FILESEQNO SET_FRLOG SET_FSPC_CA SET_FSPC_CI SET_ILOAD SET_KEY_LEN SET_KEY_OFF SET_LOGSTREAM_ID SET_LRECL SET_MGMTCLAS SET_NDISP SET_NUMVOLS SET_NUMVOLS_DATA SET_NUMVOLS_INDEX SET_PQTY SET_PQTY_DATA SET_PQTY_INDEX SET_RECFM SET_RETPD SET_REUSE SET_SHROPT_XRGN SET_SHROPT_XSYS SET_SPACEUNITS SET_SPACEUNITS_DATA SET_SPACEUNITS_INDEX SET_SPANNED SET_SQTY SET_SQTY_DATA SET_SQTY_INDEX SET_STORCLAS SET_STORGRP SET_TAPE_COMP SET_TAPE_LABEL SET_UNIT_AFFINITY SET_UNIT_COUNT SET_UNIT_NAME SET_VOLCT SET_VSAM_SEPARATE Chapter 12. Selection criteria ACCBIAS ADISP BLKSIZE BUFSPC CISZ CISZ_DATA CISZ_INDEX CONTIGUOUS DATACLAS DDNAME DEFERMOUNT Contents vii

10 DEVICECLASS DIRBLKS DSNAME DSNAME_DATA DSNAME_INDEX DSNAME_LASTNODE DSNAME_QUALIFIER DSNAME_TYPE DSORG EXPDATE EXTADDR FILESEQNO FRLOG FSPC_CA FSPC_CI GROUPID GUARSPACE ILOAD JOBACCTn JOBCLASS JOBNAME JOBTYPE KEY_LEN KEY_OFF LOGGING LOGSTREAM_ID LRECL MAXSPACE MGMTCLAS MOUNT_USAGE NDISP NUMVOLS NUMVOLS_DATA NUMVOLS_INDEX OWNERID PROCSTEPNAME PROGRAM PQTY PQTY_DATA PQTY_INDEX PSPACE_KB PSPACE_MB RECFM RELEASESPACE RETPD REUSE SDISP SHROPT_XRGN SHROPT_XSYS SMS_MANAGED SPACEUNITS SPACEUNITS_DATA SPACEUNITS_INDEX SPANNED SQTY SQTY_DATA viii IBM Tivoli Advanced Allocation Management for z/os : User's Guide

11 SQTY_INDEX STEPACCTn STEPNAME STORCLAS STORGRP SUBSYS SYSID SYSPLEXNAME TAPE_COMP TAPE_LABEL TEMPDS UNIT_AFFINITY UNIT_COUNT UNIT_NAME UNIT_TYPE USERID VOLCT VOLSER_ANY VOLSER_CURRENT VOLSER_FIRST VSAM_SEPARATE Chapter 13. Volume group definition syntax Syntax diagram Main keywords GROUP_NAME VOLUMES Chapter 14. Event recording and reporting Enabling event recording Disabling event recording Report filter criteria and filtersets Specifying multiple filtersets Filter criteria formats Report options Report option combinations and results Batch reporting utility Configuring the batch reporting utility JCL Sample execution report Sample formatted basic detail and extended detail record reports Sample formatted summary record report Creating a custom report utility GLOSSMFR (DSECT) GLOSSMFR (detail record map) Event recording and reporting filter criteria and sort field descriptions Filter criteria descriptions Sort fields Chapter 15. Troubleshooting Chapter 16. Frequently asked questions Chapter 17. Subsystem options Subsystem options modification and display reference Chapter 18. Operator commands Contents ix

12 Issuing commands Display commands Enable and disable commands Dynamic configuration commands Appendix A. Advanced Allocation Management message format Appendix B. Dialog messages Appendix C. Subsystem and started task messages Appendix D. Function messages (non-vsam) Appendix E. Function messages (VSAM) Appendix F. Syntax-check messages Appendix G. Event recording and reporting messages Support information Using IBM Support Assistant Obtaining fixes Contacting IBM Software Support Determining the business impact Describing problems and gathering information Submitting problems Notices Trademarks Bibliography Index x IBM Tivoli Advanced Allocation Management for z/os : User's Guide

13 About this guide This information provides instructions for configuring and using IBM Tivoli Advanced Allocation Management for z/os and is designed to help system programmers and production control personnel perform these tasks: v Install Advanced Allocation Management v Configure Advanced Allocation Management v Operate Advanced Allocation Management Intended audience for this guide Publications This information is intended for those persons responsible for installing, configuring and using IBM Tivoli Advanced Allocation Management and assumes a working knowledge of: v The OS/390 or z/os operating system v SMP/E v RACF v ISPF The following publications are included in the Advanced Allocation Management product library: v IBM Tivoli Advanced Allocation Management for z/os Program Directory, GI Provides hardware and software prerequisites and instructions for the Advanced Allocation Management SMP/E installation. v IBM Tivoli Advanced Allocation Management for z/os User's Guide, SC Provides instructions for using Advanced Allocation Management. v IBM Tivoli Advanced Allocation Management for z/os Monitoring Agent Planning and Configuration Guide, SC Provides instructions for planning, installing, and configuring Advanced Allocation Management. This publication includes the following types of information: Information and worksheets to help you plan your configuration A list of prerequisite steps to complete before configuring the product Instructions for configuring the monitoring server and monitoring agent on a z/os system Instructions for installing and setting up the distributed components of the product Information about using system variables and batch processing to expand a configuration across the enterprise Security considerations and advice v IBM Tivoli Advanced Allocation Management for z/os Monitoring Agent User's Guide, SC Provides instructions for using Advanced Allocation Management to monitor z/os system and sysplex resources, and product-specific monitoring scenarios. xi

14 Accessing publications online IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Information Center Web site at In the Tivoli Information Center window, click Tivoli product manuals. Click the letter that matches the first letter of your product name to access your product library. For example, click M to access the IBM Tivoli Monitoring library or click O to access the IBM Tivoli OMEGAMON library. Note: If you print PDF documents on other than letter-sized paper, set the option in the File > Print window that allows Adobe Reader to print letter-sized pages on your local paper. Reading CCR2 online IBM publishes CCR2, a useful monthly e-newsletter for the System z and zseries software community. You can find the latest issue of CCR2 at Ordering publications You can order many Tivoli publications online at the following Web site: publications/cgibin/pbi.cgi. You can also order by telephone by calling one of these numbers: v In the United States: v In Canada: In other countries, contact your software account representative to order Tivoli publications. To locate the telephone number of your local representative, perform the following steps: 1. Go to publications/cgibin/ pbi.cgi. 2. Select your country from the list and click Go. 3. Click About this site in the main panel to see an information page that includes the telephone number of your local representative. Accessing terminology online The Tivoli Software Glossary includes definitions for many of the technical terms related to Tivoli software. The Tivoli Software Glossary is available at the following Tivoli software library Web site: The IBM Terminology Web site consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology Web site at the following Web address: xii IBM Tivoli Advanced Allocation Management for z/os : User's Guide

15 Tivoli technical training Support information For Tivoli technical training information, refer to the following IBM Tivoli Education Web site: If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: v v v IBM Support Assistant: You can search across a large collection of known problems and workarounds, Technotes, and other information at Obtaining fixes: You can locate the latest fixes that are already available for your product. Contacting IBM Software Support: If you still cannot solve your problem, and you need to work with someone from IBM, you can use a variety of ways to contact IBM Software Support. For more information about resolving problems, see Support information on page 349. Conventions used in this publication This guide uses several conventions for special terms and actions and for operating system-dependent commands and paths. Typeface conventions This guide uses the following typeface conventions: Bold v v v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu names, tabs, property sheets), labels (such as Tip: and Operating system considerations) Keywords and parameters in text Italic v Words defined in text v Emphasis of words (words as words) v New terms in text (except in a definition list) v Variables and values you must provide Monospace v s and code examples v File names, programming keywords, and other elements that are difficult to distinguish from surrounding text v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options About this guide xiii

16 xiv IBM Tivoli Advanced Allocation Management for z/os : User's Guide

17 Chapter 1. Advanced Allocation Management overview Advanced Allocation Management for z/os is a tool that helps prevent and reduce processing delays and interruptions that can result from x37 abends and errors that occur due to insufficient disk space during new allocations. Using Advanced Allocation Management to prevent and recover from these situations can help your installation significantly increase productivity and data availability, and minimize the downtime that can occur as a result of these conditions. Advanced Allocation Management runs as a started task with a user-designated subsystem. Definition management (defining where and how Advanced Allocation Management operates) is performed using a control data set which contains PDS members that govern specific aspects of Advanced Allocation Management processing. Users can access Advanced Allocation Management through an online user interface and authorized users can issue operator commands to perform selected operations. What does Advanced Allocation Management do? Advanced Allocation Management enables you to avoid and recover from x37 (B37, D37, and E37) type abends. These types of abends involve storage management issues such as insufficient disk space allocations and unavailable DASD extents. Advanced Allocation Management also helps prevent JOB FAILED JCL errors that occur due to insufficient disk space during new allocations. Preventing and reducing the processing delays and interruptions that can result from these abends and errors is important because they can negatively impact productivity and impede data availability. In addition to abend recovery and prevention, Advanced Allocation Management provides: v v v v v Volume group support that enables you to define DASD groups from which to select additional volumes as needed Advanced volume selection capabilities that provides the capability of having Advanced Allocation Management select the volumes for a non-sms managed data set at initial allocation time Enhanced allocation management features to provide centralized control of allocation attribute usage Extensive event recording and reporting to help you evaluate product benefits, specific events Advanced Allocation Management encountered, and subsequent actions taken for a particular job, or time frame, and so on Online reporting that provides a statistical summary of both proactive and reactive product actions Features and benefits Advanced Allocation Management offers a variety of features to help you get the most out of your z/os environment. x37 abend recovery Advanced Allocation Management recovers from x37 type abends in these ways. v Controls reduction of primary space to satisfy allocation 1

18 v v v Dynamically adds volumes at end of volume processing as required Recovers from secondary allocation space failures by reducing the allocation amount to a value that is consistent with the current free space on the volume Dynamically increases PDS directory size if exhausted x37 abend prevention and avoidance Advanced Allocation Management prevents and avoids x37 type abends in these ways. v Automatically adds a secondary allocation if none is specified v Reduces secondary allocation to largest available free extent v v Increases the size of the secondary allocation as data set extends occur after a particular extent and at a particular volume number Recovers unused disk space by automatically releasing allocated, unused, data set space at data set close Enhanced Allocation Management Advanced Allocation Management Enhanced Allocation Management features provide centralized control of allocation attribute usage by offering the ability to: v v v v Set allocation attributes that are not specified or override allocation attributes that do not meet your standards Control a wide variety of allocation attributes such as: SMS-managed, non-sms-managed, UNITNAME, UNITTYPE, VOLSER, DATACLAS, STORCLAS, MGMTCLAS, RECFM, LRECL, BLKSIZE (including forcing system-determined blksize) DISPOSITION (allows forcing catalog control), SPACE parameters, expiration date, and retention period values Fail jobs that specify installation-restricted allocation values Make SMS DATACLAS values override values specified using JCL, DEFINE statements, or dynamic allocation Volume group support Volume group support enables you to define DASD groups from which to select additional volumes as needed. Supported data set types Advanced Allocation Management supports these data sets types. v VSAM and non-vsam data sets v SMS and non-sms-managed data sets v Physical sequential v Partitioned v Striped data sets v Dynamically allocated data sets Note: Only DASD data sets are supported. Advanced Allocation Management does not support hierarchical file system (HFS) or zseries file system (ZFS) data sets. Advanced Allocation Management supports the LARGE data set format which allows the specification of more than tracks for the primary and secondary 2 IBM Tivoli Advanced Allocation Management for z/os : User's Guide

19 allocation for non-vsam data sets specified with a DSNTYPE of LARGE. VSAM support Advanced Allocation Management VSAM support includes: v VSAM (KSDS, ESDS, RRDS, VRRDS, and LDS) v Alternate indexes v Index and data components of clusters where applicable Note: Only integrated catalog facility (ICF) data sets (SMS and non-sms managed) are supported. Extended Address Volume support Advanced Allocation Management supports z/os 1.10 Extended Address Volume (EAV) functionality for VSAM data sets. Preference for allocation in the Extended Addressing Space (Cylinder-managed space) is based upon the size of the allocation as compared to the Breakpoint Value (BPV) defined either at the system level or within an SMS Storage Group. When determining the eligibility of a candidate volume for Advanced Allocation Management AVS or VOL_ADD processing, this preference, based on the BPV, is used within each of the selection algorithms as appropriate. Similarly, this preference is considered when reducing a secondary allocation as part of SEC_REDUCE, SEC_BEST, PRIM_REDUCE on non-first volumes. Note: As defined by IBM, VSAM data sets that contain a control area size of other than 1, 3, 5, 7, 9, or 15 are not eligible for allocation in the cylinder-managed space of an EAV volume. Also excluded are data sets with IMBED or KEYRANGE attributes defined. Event recording and reporting Advanced Allocation Management provides an extensive event recording and reporting facility to help you evaluate product benefits, specific events Advanced Allocation Management encountered, and subsequent actions taken for a particular job or time frame, and so on. Event history can be viewed using the online dialog or by using the batch reporting utility. Additionally, record layouts are provided so that users can create their own reporting programs, customized to suit their specific needs. Integration with the Tivoli Enterprise Portal (TEP) Integration with IBM Tivoli OMEGAMON XE for Storage through TEP delivers seamless integration with related storage management capability, and helps you easily monitor the impact of allocation abends prevented by Advanced Allocation Management. Users can view information and be alerted to situations from a single GUI through integration with TEP. Extensive and flexible rule definitions Extensive, easy to understand rule definitions give you the flexibility to choose the combination of selection criteria and functions that best suit your specific needs. Chapter 1. Advanced Allocation Management overview 3

20 Online user interface The Advanced Allocation Management online user interface allows you to easily build and manipulate rule definitions as well as view and update the status of the product and its processing options. Operator commands Operator commands enable authorized users to view and update Advanced Allocation Management subsystem information, activate rule and volume group definitions, and enable or disable specific product functions, such as product-level intercepts, from an operator console. User-specified messaging Advanced Allocation Management provides user-specified messaging for specific actions taken. You also have the ability to specify where product messages should be directed: JES SYSMSG data set, the operator console, or both. Advanced Allocation Management components Advanced Allocation Management runs as a started task with a user-designated subsystem. Definition management (defining where and how Advanced Allocation Management operates) is performed using a control data set which contains PDS members that govern specific aspects of Advanced Allocation Management processing. Control data set To determine how to handle a potential x37 abend or other similar error condition, Advanced Allocation Management employs user-defined processing definitions which reside in the Advanced Allocation Management control data set. Each PDS member in the control data set contains a specific set of definitions that determine how Advanced Allocation Management performs a particular type of processing. The Advanced Allocation Management control data set contains these member types: v Subsystem options v Rule definitions v Volume group definitions Note: Sample control data set members are generated during the installation process. You can modify these members according to your installation s needs using the options that are available on the Tivoli Advanced Allocation Management Control Member Management screen (recommended method) or by using ISPF EDIT. Subsystem options This member contains global definitions and general operation options (including the unique four character subsystem ID that is associated with a specific instance of Advanced Allocation Management) that determine how Advanced Allocation Management functions. 4 IBM Tivoli Advanced Allocation Management for z/os : User's Guide

21 Rule definitions This member contains rule definitions that determine the items you want Advanced Allocation Management to include or exclude from processing (selection criteria) and the functions you want Advanced Allocation Management to perform using the items specified by the selection criteria. Advanced Allocation Management uses rule definitions to determine whether or not it should take action in the event that an x37 type abend, or other out-of-space condition, is about to occur. Rule definition syntax consist of keywords and keyword values grouped into selection criteria and functions by the DEFAULTS, INCLUDE and EXCLUDE main keywords. Selection criteria specify the items (job name, data set name, and so on) to include or exclude from Advanced Allocation Management processing. Functions specify the actions (controlling reduction of primary space, adding a secondary allocation, and so on) that you want Advanced Allocation Management to perform using the selection criteria. Note: By default, Advanced Allocation Management only includes items in its processing when specifically directed to do so. Volume group definitions This member contains the volume group list that defines a group of volumes from which additional volumes can be selected as needed (volume group definitions are used in conjunction with the volume addition function that is available within the rule definitions). Note: Volume groups are only used for non-sms data sets. For SMS data sets, SMS is used to select a volume based on SMS constructs. The dynamic volume addition function, provided with the Advanced Allocation Management rule definition syntax, helps avoid out-of-space conditions that occur during end-of-volume processing. During end-of-volume processing, this function dynamically adds another volume, from user-specified volume groups, when the secondary allocation space request cannot be satisfied on the current volume. Volume group definitions enable you to specify the volume groups from which Advanced Allocation Management selects these additional volumes. You define the volume serial numbers either specifically, or generically, using a pattern masking facility. The volume addition function enables you to specify in any combination: a volume group, an esoteric name, or generic names. Started task The Advanced Allocation Management started task JCL points to the subsystem options member in the Advanced Allocation Management control data set which contains the unique subsystem ID that is associated with a specific Advanced Allocation Management subsystem. Advanced Allocation Management subsystem Each instance of Advanced Allocation Management is considered to be a separate Advanced Allocation Management subsystem and must have a unique subsystem Chapter 1. Advanced Allocation Management overview 5

22 ID and started task JCL to differentiate it from other Advanced Allocation Management subsystems. User interface The Advanced Allocation Management user interface consists of a series of ISPF panels that enable you to easily manage Advanced Allocation Management control data set members, view and update Advanced Allocation Management subsystem settings, or view recovery statistics for an active Advanced Allocation Management subsystem. Advanced Allocation Management architecture and processing Advanced Allocation Management operates at the system level to intercept x37 type abends and other errors that are caused by insufficient disk space allocations, unavailable DASD extents, and out-of-space conditions. After you install and customize Advanced Allocation Management, determine what you want to recover in the event of an x37 type abend, or other similar error, and what Advanced Allocation Management should do if it encounters a particular error condition involving the selected items. The extensive and flexible rule definitions enable you to specify many possible combinations of selection criteria (the items you want Advanced Allocation Management to include or exclude from processing) and functions (the actions you want Advanced Allocation Management to perform when it detects an item specified by the selection criteria). In addition, to help avoid out-of-space conditions that occur during end-of-volume processing, Advanced Allocation Management s dynamic volume addition function and volume group support enable you to define specific volume groups from which Advanced Allocation Management selects additional volumes, as needed. After you initiate the Advanced Allocation Management started task, and customize and activate the appropriate definitions, no additional user intervention is required. When Advanced Allocation Management is running, it interacts with your operating system to determine when an x37 type abend, or other similar error, is about to occur and manages the situation according to your specifications. Note: Advanced Allocation Management does not attempt to prevent and recover from all situations only those that you have specified using Advanced Allocation Management definitions. Started task and subsystem definition Advanced Allocation Management is designed so that multiple instances can run concurrently on a single z/os image. Each instance of the product is considered a separate Advanced Allocation Management subsystem and must have a unique subsystem ID and started task JCL to differentiate it from other Advanced Allocation Management subsystems that might be running on the same image. When the started task is initiated, it references the data in the subsystem options member to establish global settings, including the subsystem identifier for this specific instance of the product. The started task then starts the Advanced Allocation Management subsystem and the product begins the initialization process during which time the control blocks are built, the product modules are loaded, and other product files are read and processed. 6 IBM Tivoli Advanced Allocation Management for z/os : User's Guide

23 Figure 1 shows an example of a single instance of Advanced Allocation Management on a single image: Advanced Allocation Management Control Data Set (subsystem options member) The Advanced Allocation Management started task references the Advanced Allocation Management control data set to obtain the unique subsystem identifier (SSID) for this instance of Advanced Allocation Management User initiates the Advanced Allocation Management started task Advanced Allocation Management Started Task and Subsystem (DD statement) Job A Data Set Processing Job B Data Set Processing (z/os Allocation) (z/os End-Of-Volume Processing) Advanced Allocation Management Allocation Intercepts Advanced Allocation Management EOV Intercepts Figure 1. Advanced Allocation Management (single instance) Once Advanced Allocation Management is running, its product-level intercepts (allocation and end-of-volume processing intercepts) interact with your operating system to determine when an x37 type abend, or other similar error, is about to occur. When Advanced Allocation Management detects a potential error condition, it manages the situation according to the product definitions specified in the control data set. Note: An Advanced Allocation Management subsystem can be active or inactive. An Advanced Allocation Management subsystem is considered active when the Advanced Allocation Management started task associated with that subsystem ID is currently running and the product-level intercepts are enabled. Advanced Allocation Management subsystem identification When configuring Advanced Allocation Management, you must specify a unique four character subsystem ID to identify the Advanced Allocation Management subsystem for each instance of Advanced Allocation Management that you want to run. The Advanced Allocation Management subsystem ID identifies a specific instance of Advanced Allocation Management within your environment and appears on product panels and in messages. Chapter 1. Advanced Allocation Management overview 7

24 Running multiple instances of Advanced Allocation Management Running multiple instances of Advanced Allocation Management is useful in those situations where you want to reserve one Advanced Allocation Management subsystem for testing purposes and another subsystem for production purposes. Note: A maximum of four concurrently active subsystems on a single z/os system are allowed. Multiple instances of Advanced Allocation Management can run concurrently on the same image, or on different images: v v To run multiple instances of Advanced Allocation Management on separate z/os images (one instance per image) you can specify the same, or different, subsystem IDs and started task names for each instance of the product. You do no need to specify a unique subsystem identifier and started task name for each instance because each instance resides on a different image. For example, if you want to run two instances of Advanced Allocation Management (one instance on image A and one instance on image B ), each subsystem identifier could be defined as OPT1 and each started task could be named ALLOCPT1. To run multiple instances of Advanced Allocation Management on the same z/os image, each instance must have a unique subsystem identifier and started task name (because there can only be one occurrence of a specific Advanced Allocation Management subsystem running on a single image at any given time). For example, if the Advanced Allocation Management subsystem OPT1 is running on image B, and it was initiated from the started task named ALLOCPT1, to initiate a second instance of Advanced Allocation Management on image B, you must specify a different subsystem ID and started task (for example, subsystem ID OPT2 and started task ALLOCPT2 ). Note: If you run multiple Advanced Allocation Management subsystems on the same z/os image, at the same time, the subsystem that was initiated last is the subsystem whose processing takes precedence. For example, if two Advanced Allocation Management subsystems (OPT1 and OPT2) are running on image A and the OPT2 subsystem was initiated last its processing takes precedence over any OPT1 subsystem processing on image A. Figure 2 on page 9 shows examples of multiple Advanced Allocation Management instances that illustrate both of these scenarios. 8 IBM Tivoli Advanced Allocation Management for z/os : User's Guide

25 Image A Job A Data Set Processing Job B Data Set Processing Advanced Allocation Management Started Task (ALLOCPT1) and Subsystem (OPT1) (z/os Allocation) (z/os End-Of-Volume Processing) Advanced Allocation Management Allocation Intercepts Advanced Allocation Management EOV Intercepts Image B Job A Data Set Processing Job B Data Set Processing Advanced Allocation Management Started Task (ALLOCPT1) and Subsystem (OPT1) Advanced Allocation Management Started Task (ALLOCPT2) and Subsystem (OPT2) (z/os Allocation) (z/os End-Of-Volume Processing) Advanced Allocation Management Allocation Intercepts Advanced Allocation Management EOV Intercepts Figure 2. Advanced Allocation Management (multiple instances) Note these items in Figure 2: v The Advanced Allocation Management subsystem OPT1 that is running on image A is a different subsystem than the Advanced Allocation Management subsystem OPT1 that is running on image B. v Each Advanced Allocation Management subsystem that is running on image B has a unique subsystem identifier and started task name. Compatibility with other products It is recommended that you do not operate products that are similar to Advanced Allocation Management in function because these products might have features that are the same, or similar, to Advanced Allocation Management and unpredictable results could occur. Chapter 1. Advanced Allocation Management overview 9

26 Summary of changes This topic summarizes the significant improvements or enhancements for Advanced Allocation Management. New and changed information is indicated by a vertical bar () to the left of a change. Editorial changes that have no technical significance are not noted. SC v As of version 3.1 IBM Tivoli Allocation Optimizer for z/os has been renamed to IBM Tivoli Advanced Allocation Management for z/os. v Advanced Allocation Management must be installed on a system with z/os 1.8 and higher. See Hardware and software prerequisites on page 11. v Selection criteria keywords have been added and updated. See Chapter 12, Selection criteria, on page 195 for more information. v Support for Enhanced Allocation Management has been added. See Chapter 11, Enhanced Allocation Management function keywords, on page 141 for more information. v Advanced volume selection capabilities have been added. See Advanced Volume Selection (AVS) on page 56 for more information. v Additional information has been added to the GLO1036E message. See Appendix C, Subsystem and started task messages, on page 303 for more information. v The GLOJIVP1 member steps and example output have been updated. See Step 8: Verify the installation on page 22 and Table 5 on page 23 for more information. 10 IBM Tivoli Advanced Allocation Management for z/os : User's Guide

27 Chapter 2. Installation and security considerations There are several factors you need to consider when installing and securing Advanced Allocation Management. Hardware and software prerequisites Make sure that you have these minimum hardware and software requirements in place before you install Advanced Allocation Management. Hardware prerequisites Advanced Allocation Management runs on a mainframe system. The system must be able to support the ESA instruction set. No special hardware is required. Software prerequisites Advanced Allocation Management must be installed on a system with z/os 1.8 and higher. No additional software is required for Advanced Allocation Management to operate properly. Installing and implementing Advanced Allocation Management This topic provides general information about installing and implementing Advanced Allocation Management. For specific installation instructions, see the Program Directory for Advanced Allocation Management for z/os. If this is a new installation of Advanced Allocation Management, or if Advanced Allocation Management is replacing a similar product, it is strongly recommended that you install and run Advanced Allocation Management in a test environment prior to implementing it in your production environment. Doing so ensures that the product is configured according to your needs without impacting your current production data. After you install Advanced Allocation Management in a test environment, it is recommended that you run a series of initial tests, followed by more extensive testing as you gain experience with the product. After successful testing in a test environment, a gradual, incremental implementation of the product in your production environment is recommended. For example, you might begin by creating a series of test jobs that you can use to become familiar with Advanced Allocation Management features and functions. Use Advanced Allocation Management selection criteria to specify that only these test jobs should be included in Advanced Allocation Management processing. Note: If Advanced Allocation Management is replacing a similar product at your installation, be sure to fully test it in a test environment prior to installing it in your production environment. Advanced Allocation Management 3.1 and prior versions of Advanced Allocation Management Follow these guidelines if you have a prior version of Advanced Allocation Management (Allocation Optimizer) and you are installing Advanced Allocation Management