IBM Tivoli Advanced Allocation Management for z/OS User ...publib.boulder.ibm.com/tividd/td/ITAAMfzOS/SC23... · configuring and using IBM Tivoli Advanced Allocation Management and

IBM Tivoli Advanced Allocation Management for z/OS

User's GuideVersion 3 Release 1

SC23-9817-01

��

IBM Tivoli Advanced Allocation Management for z/OS

User's GuideVersion 3 Release 1

SC23-9817-01

��

Note:Before using this information and the product it supports, read the information in “Notices” on page 369.

This edition applies to Version 3 Release 1 of IBM Tivoli Advanced Allocation Management for z/OS (productnumber 5697-P35) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright Rocket Software Inc., 2003 - 2010. All Rights Reserved.

Contents

About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiIntended audience for this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiPublications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Accessing publications online . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiOrdering publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Accessing terminology online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiTivoli technical training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiSupport information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiConventions used in this publication . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Typeface conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiiHow to read syntax diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv

Chapter 1. Advanced Allocation Management overview . . . . . . . . . . . . . . . 1What does Advanced Allocation Management do?. . . . . . . . . . . . . . . . . . . . . . . 1Features and benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Advanced Allocation Management components. . . . . . . . . . . . . . . . . . . . . . . . 4Advanced Allocation Management architecture and processing . . . . . . . . . . . . . . . . . . 6

Started task and subsystem definition . . . . . . . . . . . . . . . . . . . . . . . . . . 6Compatibility with other products . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2. Installation and security considerations. . . . . . . . . . . . . . . . . 13Hardware and software prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Installing and implementing Advanced Allocation Management . . . . . . . . . . . . . . . . . . 13Migration considerations and requirements . . . . . . . . . . . . . . . . . . . . . . . . . 14Migration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Step 1: Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Step 2: Install Advanced Allocation Management in a test environment . . . . . . . . . . . . . . 15Step 3: Convert product definitions and test . . . . . . . . . . . . . . . . . . . . . . . 15Step 4: Migrate to production . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Migration and installation documentation . . . . . . . . . . . . . . . . . . . . . . . . . 16Security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Securing the control data set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Securing user interface update functions. . . . . . . . . . . . . . . . . . . . . . . . . 16How Advanced Allocation Management uses RACF to determine access to update functions . . . . . . . 17Security and internal work data sets . . . . . . . . . . . . . . . . . . . . . . . . . . 18Security and definition management . . . . . . . . . . . . . . . . . . . . . . . . . . 18Authorizing the started task for selected NOTCAT2 functions . . . . . . . . . . . . . . . . . 18

Chapter 3. Configuring Advanced Allocation Management . . . . . . . . . . . . . 19Configuration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Configuration steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Step 1: APF-authorize the load libraries . . . . . . . . . . . . . . . . . . . . . . . . . 19Step 2: Configure the started task JCL . . . . . . . . . . . . . . . . . . . . . . . . . 20Step 3: Allocate the control data set . . . . . . . . . . . . . . . . . . . . . . . . . . 21Step 4: Specify subsystem options . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Step 5: Secure the user interface update functions . . . . . . . . . . . . . . . . . . . . . 22Step 6: Configure the CLISTs and start the Advanced Allocation Management user interface . . . . . . . 23Step 7: Start the started task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Step 8: Verify the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 4. Advanced Allocation Management definition management. . . . . . . . . 31The control data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Control data set requirements and guidelines . . . . . . . . . . . . . . . . . . . . . . . 31

iii

Modifying control data set members . . . . . . . . . . . . . . . . . . . . . . . . . . 32Activating rule and volume group member definitions . . . . . . . . . . . . . . . . . . . . 32

Implementing multiple instances of Advanced Allocation Management . . . . . . . . . . . . . . . 32Using separate control data sets for multiple instances . . . . . . . . . . . . . . . . . . . . 33Using a shared control data set for multiple instances . . . . . . . . . . . . . . . . . . . . 34

Guidelines and recommendations for implementing Advanced Allocation Management . . . . . . . . . . 34

Chapter 5. Using the Advanced Allocation Management user interface . . . . . . . . 37Accessing the Tivoli Advanced Allocation Management Primary Option Menu . . . . . . . . . . . . . 37Tivoli Advanced Allocation Management Primary Option Menu options . . . . . . . . . . . . . . . 37Accessing online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Managing control data set members . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Specifying a control data set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Specifying a control data set by selecting the subsystem ID from a list of active subsystems . . . . . . . 39Selecting control data set members . . . . . . . . . . . . . . . . . . . . . . . . . . 39Control member management options . . . . . . . . . . . . . . . . . . . . . . . . . 40Creating a new control data set member using the Edit option . . . . . . . . . . . . . . . . . 41

Viewing and updating subsystem options . . . . . . . . . . . . . . . . . . . . . . . . . 41Fixed Subsystem Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Modifiable Subsystem Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Modifiable Product-Level Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Displaying Advanced Allocation Management recovery statistics . . . . . . . . . . . . . . . . . 43Advanced Allocation Management Recovery Statistics . . . . . . . . . . . . . . . . . . . . 44

Viewing event history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Input Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Report Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Output Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 6. Using rule definitions to define processing . . . . . . . . . . . . . . . 51How rule definitions work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Rule definition syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Syntax precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Rule definition evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Creating and modifying rule definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 52Rule definition member requirements. . . . . . . . . . . . . . . . . . . . . . . . . . 52Determining the functions to include in rule definitions . . . . . . . . . . . . . . . . . . . 53Establishing rule definition default processing . . . . . . . . . . . . . . . . . . . . . . . 55Including or excluding items from processing . . . . . . . . . . . . . . . . . . . . . . . 55Specifying multiple functions or selection criteria . . . . . . . . . . . . . . . . . . . . . . 55Activating rule definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Displaying active rule definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Recommendations and guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Function and rule definition examples . . . . . . . . . . . . . . . . . . . . . . . . . . 58Advanced Volume Selection (AVS). . . . . . . . . . . . . . . . . . . . . . . . . . . 58Continue RULEDEF processing (CONTINUE) . . . . . . . . . . . . . . . . . . . . . . . 58Initialize a newly allocated data set (DATASET_INIT) . . . . . . . . . . . . . . . . . . . . 60Process NOT CATLGD 2 errors (NOTCAT2) . . . . . . . . . . . . . . . . . . . . . . . 60Dynamic PDS directory increase (PDS_DIR_INC) . . . . . . . . . . . . . . . . . . . . . . 63Controlled reduction of primary space (PRIM_REDUCE) . . . . . . . . . . . . . . . . . . . 65Test a rule definition (RULEDEF_TEST) . . . . . . . . . . . . . . . . . . . . . . . . . 66Add a secondary allocation (SEC_ALLOC) . . . . . . . . . . . . . . . . . . . . . . . . 67Reduce secondary allocation to largest available free extent (SEC_BEST) . . . . . . . . . . . . . . 68Increase the size of secondary allocation (SEC_INC) . . . . . . . . . . . . . . . . . . . . . 69Recover from secondary allocation space failures (SEC_REDUCE) . . . . . . . . . . . . . . . . 70Recover unused disk space (SPACE_RELEASE) . . . . . . . . . . . . . . . . . . . . . . 72Terminate an allocation (TERM_ALLOC) . . . . . . . . . . . . . . . . . . . . . . . . 73Dynamically add volumes (VOL_ADD) . . . . . . . . . . . . . . . . . . . . . . . . . 73Using comparison operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Setting allocation attributes using Enhanced Allocation Management functions . . . . . . . . . . . . 75

iv IBM Tivoli Advanced Allocation Management for z/OS User's Guide

Specifying $NULL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Data class override ($DCOC and $DCOU) . . . . . . . . . . . . . . . . . . . . . . . . 75

Space recovery strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Chapter 7. Defining volume groups . . . . . . . . . . . . . . . . . . . . . . . 79Sample volume group definition member . . . . . . . . . . . . . . . . . . . . . . . . . 79Volume group definition syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Creating and modifying volume group definitions . . . . . . . . . . . . . . . . . . . . . . 79

Volume group definition member requirements . . . . . . . . . . . . . . . . . . . . . . 80Activating volume group definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 80Displaying volume group definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Single volume group list example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Multiple volume group lists example . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Chapter 8. Specifying Advanced Allocation Management syntax . . . . . . . . . . . 83Specifying multiple operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Specifying lists of items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Including comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Using wildcard characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Chapter 9. Rule definition syntax . . . . . . . . . . . . . . . . . . . . . . . . 87Main keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

DEFAULTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87INCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88EXCLUDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Enhanced Allocation Management functions . . . . . . . . . . . . . . . . . . . . . . . . 89Selection criteria keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Comparison operands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

String comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Numeric comparisons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Null or unspecified values ($NULL) . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Character string values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Numeric suffixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Data class override . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

$DCOU (unconditional override) . . . . . . . . . . . . . . . . . . . . . . . . . . . 91$DCOC (conditional override) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

ACS environment considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Space parameter considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92How allocation attributes are used during selection criteria processing . . . . . . . . . . . . . . . 94Function and selection criteria environment compatibility . . . . . . . . . . . . . . . . . . . . 94

Chapter 10. Function keywords. . . . . . . . . . . . . . . . . . . . . . . . . 101AVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101AVS_ALGORITHM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102AVS_MOUNT_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104AVS_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105AVS_VGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106AVS_VGRP_SEARCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106AVS_VSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107CONTINUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108DATASET_INIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109DIAG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109ENVIRONMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111MSG_DESTINATION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112MSG_LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113NOTCAT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115NOTCAT2_CHECK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117NOTCAT2_DYNAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Contents v

||

NOTCAT2_QUALIFIER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119NOTCAT2_QUALIFIER_POSITION . . . . . . . . . . . . . . . . . . . . . . . . . . . 120NOTCAT2_SUFFIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120PDS_DIR_INC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121PRIM_REDUCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122PRIM_REDUCE_INC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124PRIM_REDUCE_LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125RULEDEF_TEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126SEC_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127SEC_ALLOC_AMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128SEC_BEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129SEC_BEST_LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129SEC_INC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130SEC_INC_AMT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131SEC_INC_VOLNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132SEC_INC_XTNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133SEC_REDUCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133SEC_REDUCE_INC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134SEC_REDUCE_LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135SPACE_RELEASE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136TERM_ALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137VOL_ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138VOL_ADD_ALGORITHM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141VOL_ADD_LIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143VOL_ADD_MOUNT_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143VOL_ADD_PROMPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145VOL_ADD_SGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146VOL_ADD_UNIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147VOL_ADD_VGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148VOL_ADD_VGRP_SEARCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149VOL_ADD_VSER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150WRITE_MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

Chapter 11. Enhanced Allocation Management function keywords. . . . . . . . . . 155$DCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155SET_ACCBIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157SET_ADISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158SET_BLKSIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159SET_BUFSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160SET_CISZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160SET_CISZ_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161SET_CISZ_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162SET_CONTIGUOUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163SET_DATACLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163SET_DEFERMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164SET_DIRBLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165SET_DSNAME_TYPE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166SET_DSORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167SET_EXPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168SET_EXTADDR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169SET_FILESEQNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170SET_FRLOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171SET_FSPC_CA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172SET_FSPC_CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SET_ILOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173SET_KEY_LEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174SET_KEY_OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175SET_LOGSTREAM_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176SET_LRECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177SET_MGMTCLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178SET_NDISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

vi IBM Tivoli Advanced Allocation Management for z/OS User's Guide

SET_NUMVOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180SET_NUMVOLS_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181SET_NUMVOLS_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182SET_PQTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182SET_PQTY_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183SET_PQTY_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184SET_RECFM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185SET_RETPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189SET_REUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190SET_SHROPT_XRGN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191SET_SHROPT_XSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192SET_SPACEUNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193SET_SPACEUNITS_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194SET_SPACEUNITS_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195SET_SPANNED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196SET_SQTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197SET_SQTY_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198SET_SQTY_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199SET_STORCLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200SET_STORGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201SET_TAPE_COMP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202SET_TAPE_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203SET_UNIT_AFFINITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204SET_UNIT_COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205SET_UNIT_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205SET_VOLCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206SET_VSAM_SEPARATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

Chapter 12. Selection criteria . . . . . . . . . . . . . . . . . . . . . . . . . 209ACCBIAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209ADISP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210BLKSIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211BUFSPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212CISZ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213CISZ_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213CISZ_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214CONTIGUOUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215DATACLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215DDNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216DEFERMOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217DEVICECLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217DIRBLKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218DSNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219DSNAME_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220DSNAME_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220DSNAME_LASTNODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221DSNAME_QUALIFIER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222DSNAME_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222DSORG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224EXPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225EXTADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226FILESEQNO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227FRLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228FSPC_CA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229FSPC_CI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229GROUPID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230GUARSPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231ILOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231JOBACCTn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232JOBCLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233JOBNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

Contents vii

JOBTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234KEY_LEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235KEY_OFF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235LOGGING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236LOGSTREAM_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237LRECL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238MAXSPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239MGMTCLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240MOUNT_USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240NDISP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242NUMVOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243NUMVOLS_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244NUMVOLS_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244OWNERID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245PROCSTEPNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245PROGRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246PQTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247PQTY_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248PQTY_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248PSPACE_KB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249PSPACE_MB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250RECFM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251RELEASESPACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255RETPD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256REUSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257SDISP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258SHROPT_XRGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259SHROPT_XSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259SMS_MANAGED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260SPACEUNITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261SPACEUNITS_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262SPACEUNITS_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263SPANNED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264SQTY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265SQTY_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266SQTY_INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267STEPACCTn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268STEPNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268STORCLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269STORGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270SUBSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271SYSID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271SYSPLEXNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272TAPE_COMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272TAPE_LABEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273TEMPDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274UNIT_AFFINITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275UNIT_COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275UNIT_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276UNIT_TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277USERID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278VOLCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279VOLSER_ANY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280VOLSER_CURRENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281VOLSER_FIRST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282VSAM_SEPARATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Chapter 13. Volume group definition syntax . . . . . . . . . . . . . . . . . . . 285Syntax diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Main keywords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

GROUP_NAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

viii IBM Tivoli Advanced Allocation Management for z/OS User's Guide

VOLUMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

Chapter 14. Event recording and reporting . . . . . . . . . . . . . . . . . . . . 287Enabling event recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Disabling event recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Report filter criteria and filtersets. . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Specifying multiple filtersets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Filter criteria formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Report options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Report option combinations and results . . . . . . . . . . . . . . . . . . . . . . . . . 289Batch reporting utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Configuring the batch reporting utility JCL . . . . . . . . . . . . . . . . . . . . . . . 290Sample execution report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Sample formatted basic detail and extended detail record reports . . . . . . . . . . . . . . . . 293Sample formatted summary record report . . . . . . . . . . . . . . . . . . . . . . . . 295

Creating a custom report utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297GLOSSMFR (DSECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297GLOSSMFR (detail record map) . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Event recording and reporting filter criteria and sort field descriptions . . . . . . . . . . . . . . . 299Filter criteria descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299Sort fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

Chapter 15. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Chapter 16. Frequently asked questions . . . . . . . . . . . . . . . . . . . . . 307

Chapter 17. Subsystem options . . . . . . . . . . . . . . . . . . . . . . . . 309Subsystem options modification and display reference. . . . . . . . . . . . . . . . . . . . . 309

Chapter 18. Operator commands . . . . . . . . . . . . . . . . . . . . . . . . 311Issuing commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Display commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Enable and disable commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Dynamic configuration commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Appendix A. Advanced Allocation Management message format . . . . . . . . . . 313

Appendix B. Dialog messages . . . . . . . . . . . . . . . . . . . . . . . . . 315

Appendix C. Subsystem and started task messages . . . . . . . . . . . . . . . 319

Appendix D. Function messages (non-VSAM) . . . . . . . . . . . . . . . . . . 335

Appendix E. Function messages (VSAM) . . . . . . . . . . . . . . . . . . . . 347

Appendix F. Syntax-check messages . . . . . . . . . . . . . . . . . . . . . . 351

Appendix G. Event recording and reporting messages . . . . . . . . . . . . . . 359

Support information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Using IBM Support Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Obtaining fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365Contacting IBM Software Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Determining the business impact . . . . . . . . . . . . . . . . . . . . . . . . . . . 367Describing problems and gathering information . . . . . . . . . . . . . . . . . . . . . . 367Submitting problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Contents ix

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

Bibliography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

x IBM Tivoli Advanced Allocation Management for z/OS User's Guide

About this guide

This information provides instructions for configuring and using IBM® Tivoli®

Advanced Allocation Management for z/OS® and is designed to help systemprogrammers and production control personnel perform these tasks:v Install Advanced Allocation Managementv Configure Advanced Allocation Managementv Operate Advanced Allocation Management

Intended audience for this guideThis information is intended for those persons responsible for installing,configuring and using IBM Tivoli Advanced Allocation Management and assumesa working knowledge of:v The OS/390® or z/OS operating systemv SMP/Ev RACF®

v ISPF

PublicationsThe following publications are included in the Advanced Allocation Managementproduct library:v IBM Tivoli Advanced Allocation Management for z/OS Program Directory, GI11-9207

Provides hardware and software prerequisites and instructions for the AdvancedAllocation Management SMP/E installation.

v IBM Tivoli Advanced Allocation Management for z/OS User's Guide, SC23-9817Provides instructions for using Advanced Allocation Management.

v IBM Tivoli Advanced Allocation Management for z/OS Monitoring Agent Planningand Configuration Guide, SC23-9821Provides instructions for planning, installing, and configuring AdvancedAllocation Management. This publication includes the following types ofinformation:– 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'sGuide, SC23-9819Provides instructions for using Advanced Allocation Management to monitorz/OS system and sysplex resources, and product-specific monitoring scenarios.

xi

Accessing publications onlineIBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Information Center Website at http://www.ibm.com/software/tivoli/library/.

In the Tivoli Information Center window, click Tivoli product manuals. Click theletter that matches the first letter of your product name to access your productlibrary. For example, click M to access the IBM Tivoli Monitoring library or click Oto access the IBM Tivoli OMEGAMON® library.

Note: If you print PDF documents on other than letter-sized paper, set the optionin the File > Print window that allows Adobe® Reader to print letter-sizedpages on your local paper.

Reading CCR2 onlineIBM publishes CCR2, a useful monthly e-newsletter for the System z® and zSeries®

software community. You can find the latest issue of CCR2 at http://www-306.ibm.com/software/tivoli/features/ccr2/info.html.

Ordering publicationsYou can order many Tivoli publications online at the following Web site:

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi.

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:1. Go to http://www.elink.ibmlink.ibm.com/public/applications/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 onlineThe Tivoli Software Glossary includes definitions for many of the technical termsrelated to Tivoli software. The Tivoli Software Glossary is available at the followingTivoli software library Web site:

http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

The IBM Terminology Web site consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology Web site at thefollowing Web address:

http://www-306.ibm.com/software/globalization/terminology

xii IBM Tivoli Advanced Allocation Management for z/OS User's Guide

http://www.ibm.com/software/tivoli/library/

http://www-306.ibm.com/software/tivoli/features/ccr2/info.html

http://www-306.ibm.com/software/tivoli/features/ccr2/info.html

http://www.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi




http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm

http://www-306.ibm.com/software/globalization/terminology

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM TivoliEducation Web site:

http://www.ibm.com/software/tivoli/education

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:v IBM Support Assistant: You can search across a large collection of known

problems and workarounds, Technotes, and other information athttp://www.ibm.com/software/support/isa.

v Obtaining fixes: You can locate the latest fixes that are already available for yourproduct.

v Contacting IBM Software Support: If you still cannot solve your problem, andyou need to work with someone from IBM, you can use a variety of ways tocontact IBM Software Support.

For more information about resolving problems, see “Support information” onpage 365.

Conventions used in this publicationThis guide uses several conventions for special terms and actions and for operatingsystem-dependent commands and paths.

Typeface conventionsThis guide uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip: and Operating system considerations)

v Keywords and parameters in text

Italic

v Words defined in textv 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 Examples and code examplesv File names, programming keywords, and other elements that are difficult

to distinguish from surrounding textv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

About this guide xiii

http://www.ibm.com/software/tivoli/education

http://www-306.ibm.com/software/support/isa

How to read syntax diagramsThe following rules apply to the syntax diagrams that are used in this information:v Read the syntax diagrams from left to right, from top to bottom, following the

path of the line. The following conventions are used:– The >>--- symbol indicates the beginning of a syntax diagram.– The ---> symbol indicates that the syntax diagram is continued on the next

line.– The >--- symbol indicates that a syntax diagram is continued from the

previous line.– The --->< symbol indicates the end of a syntax diagram.

v Required items appear on the horizontal line (the main path).

�� required_item ��

v Optional items appear below the main path.

�� required_itemoptional_item

��

If an optional item appears above the main path, that item has no effect on theexecution of the syntax element and is used only for readability.

��optional_item

required_item ��

v If you can choose from two or more items, they appear vertically, in a stack.If you must choose one of the items, one item of the stack appears on the mainpath.

�� required_item required_choice1required_choice2

��

If choosing one of the items is optional, the entire stack appears below the mainpath.

�� required_itemoptional_choice1optional_choice2

��

If one of the items is the default, it appears above the main path, and theremaining choices are shown below.

�� required_itemdefault_choice

optional_choiceoptional_choice

��

v An arrow returning to the left, above the main line, indicates an item that can berepeated.

xiv IBM Tivoli Advanced Allocation Management for z/OS User's Guide

�� required_item � repeatable_item ��

If the repeat arrow contains a comma, you must separate repeated items with acomma.

�� required_item �

,

repeatable_item ��

A repeat arrow above a stack indicates that you can repeat the items in thestack.

v Keywords, and their minimum abbreviations if applicable, appear in uppercase.They must be spelled exactly as shown. Variables appear in all lowercase italicletters (for example, column-name). They represent user-supplied names orvalues.

v Separate keywords and parameters by at least one space if no interveningpunctuation is shown in the diagram.

v Enter punctuation marks, parentheses, arithmetic operators, and other symbols,exactly as shown in the diagram.

v Footnotes are shown by a number in parentheses, for example (1).

About this guide xv

xvi IBM Tivoli Advanced Allocation Management for z/OS User's Guide

Chapter 1. Advanced Allocation Management overview

Advanced Allocation Management for z/OS is a tool that helps prevent and reduceprocessing delays and interruptions that can result from x37 abends and errors thatoccur due to insufficient disk space during new allocations. Using AdvancedAllocation Management to help prevent and recover from these situations can helpyour installation significantly increase productivity and data availability, andminimize the downtime that can occur as a result of these conditions.

Advanced Allocation Management runs as a started task with a user-designatedsubsystem. Definition management (defining where and how Advanced AllocationManagement operates) is performed using a control data set which contains PDSmembers that govern specific aspects of Advanced Allocation Managementprocessing. Users can access Advanced Allocation Management through an onlineuser interface and authorized users can issue operator commands to performselected operations.

What does Advanced Allocation Management do?Advanced Allocation Management helps you to avoid and recover from x37 (B37,D37, and E37) type abends. These types of abends involve storage managementissues such as insufficient disk space allocations and unavailable DASD extents.

Advanced Allocation Management also helps prevent JOB FAILED JCL errors thatoccur due to insufficient disk space during new allocations. Preventing andreducing the processing delays and interruptions that can result from these abendsand errors is important because they can negatively impact productivity andimpede data availability.

In addition, Advanced Allocation Management provides:v Volume group support that enables you to define DASD groups from which to

select additional volumes as neededv Advanced volume selection capabilities that provide the capability of having

Advanced Allocation Management select the volumes for a non-SMS manageddata set at initial allocation time

v Enhanced allocation management features which permit centralized control ofallocation attribute usage

v Extensive event recording and reporting to help you evaluate product benefits,specific events Advanced Allocation Management encountered, and subsequentactions taken for a particular job, or time frame, and so on

v Online reporting that provides a statistical summary of both proactive andreactive product actions

Features and benefitsAdvanced Allocation Management offers a variety of features to help you get themost out of your z/OS environment.

1

x37 abend recovery

Advanced Allocation Management helps to recover from x37 type abends in theseways.v Controls reduction of primary space to satisfy allocationv Dynamically adds volumes at end of volume processing as requiredv Recovers from secondary allocation space failures by reducing the allocation

amount to a value that is consistent with the current free space on the volumev Dynamically increases PDS directory size if exhausted

x37 abend prevention and avoidance

Advanced Allocation Management helps prevent and avoid x37 type abends inthese ways.v Automatically adds a secondary allocation if none is specifiedv Reduces secondary allocation to largest available free extentv Increases the size of the secondary allocation as data set extends occur after a

particular extent— and at a particular volume numberv 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 featurespermit centralized control of allocation attribute usage by offering the ability to:v Set allocation attributes that are not specified — or override allocation attributes

that do not meet your standardsv Control a wide variety of allocation attributes such as: SMS-managed,

non-SMS-managed, UNITNAME, UNITTYPE, VOLSER, DATACLAS,STORCLAS, MGMTCLAS, RECFM, LRECL, BLKSIZE (including forcingsystem-determined blksize) DISPOSITION (allows forcing catalog control),SPACE parameters, expiration date, and retention period values

v Fail jobs that specify installation-restricted allocation valuesv 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 selectadditional volumes as needed.

Supported data set types

Advanced Allocation Management supports these data sets types.v VSAM and non-VSAM data setsv SMS and non-SMS-managed data setsv Physical sequentialv Partitionedv Striped data setsv Dynamically allocated data sets

2 IBM Tivoli Advanced Allocation Management for z/OS User's Guide

Note:

v Only DASD data sets are supported. Advanced Allocation Managementdoes not support hierarchical file system (HFS) or zSeries file system(ZFS) data sets.

v Advanced Allocation Management does not process space abends for VIOdata sets.

Advanced Allocation Management supports the LARGE data set format whichallows the specification of more than 65535 tracks for the primary and secondaryallocation 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 indexesv 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 ExtendedAddressing Space (Cylinder-managed space) is based upon the size of theallocation as compared to the Breakpoint Value (BPV) defined either at the systemlevel or within an SMS Storage Group. When determining the eligibility of acandidate volume for Advanced Allocation Management AVS or VOL_ADDprocessing, this preference, based on the BPV, is used within each of the selectionalgorithms as appropriate. Similarly, this preference is considered when reducing asecondary allocation as part of SEC_REDUCE, SEC_BEST, PRIM_REDUCE onnon-first volumes.

Note: As defined by IBM, VSAM data sets that contain a control area size of otherthan 1, 3, 5, 7, 9, or 15 are not eligible for allocation in the cylinder-managedspace of an EAV volume. Also excluded are data sets with IMBED orKEYRANGE attributes defined.

Event recording and reporting

Advanced Allocation Management provides an extensive event recording andreporting facility to help you evaluate product benefits, specific events AdvancedAllocation Management encountered, and subsequent actions taken for a particularjob or time frame, and so on.

Event history can be viewed using the online dialog or by using the batchreporting utility. Additionally, record layouts are provided so that users can createtheir 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 deliversseamless integration with related storage management capability, and helps youeasily monitor the impact of allocation abends managed by Advanced Allocation

Chapter 1. Advanced Allocation Management overview 3

||

Management. Users can view information and be alerted to situations from a singleGUI through integration with TEP.

Extensive and flexible rule definitions

Extensive, easy to understand rule definitions give you the flexibility to choose thecombination of selection criteria and functions that best suit your specific needs.

Online user interface

The Advanced Allocation Management online user interface allows you to easilybuild and manipulate rule definitions as well as view and update the status of theproduct and its processing options.

Operator commands

Operator commands enable authorized users to view and update AdvancedAllocation Management subsystem information, activate rule and volume groupdefinitions, and enable or disable specific product functions, such as product-levelintercepts, from an operator console.

User-specified messaging

Advanced Allocation Management provides user-specified messaging for specificactions taken. You also have the ability to specify where product messages shouldbe directed: JES SYSMSG data set, the operator console, or both.

Advanced Allocation Management componentsAdvanced Allocation Management runs as a started task with a user-designatedsubsystem. Definition management (defining where and how Advanced AllocationManagement operates) is performed using a control data set which contains PDSmembers that govern specific aspects of Advanced Allocation Managementprocessing.

Control data set

To determine how to handle a potential x37 abend or other similar error condition,Advanced Allocation Management employs user-defined processing definitionswhich reside in the Advanced Allocation Management control data set. Each PDSmember in the control data set contains a specific set of definitions that determinehow Advanced Allocation Management performs a particular type of processing.

The Advanced Allocation Management control data set contains these membertypes:v Subsystem optionsv Rule definitionsv Volume group definitions

Note: Sample control data set members are generated during the installationprocess. You can modify these members according to your installation'sneeds using the options that are available on the Tivoli Advanced AllocationManagement Control Member Management screen (recommended method)or by using ISPF EDIT.


Subsystem options

This member contains global definitions and general operation options (includingthe unique four character subsystem ID that is associated with a specific instanceof Advanced Allocation Management) that determine how Advanced AllocationManagement functions.

Rule definitions

This member contains rule definitions that determine the items you wantAdvanced Allocation Management to include or exclude from processing (selectioncriteria) and the functions you want Advanced Allocation Management to performusing the items specified by the selection criteria.

Advanced Allocation Management uses rule definitions to determine whether ornot it should take action in the event that an x37 type abend, or other out-of-spacecondition, is about to occur. Rule definition syntax consist of keywords andkeyword 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 includeor exclude from Advanced Allocation Management processing. Functions specifythe actions (controlling reduction of primary space, adding a secondary allocation,and so on) that you want Advanced Allocation Management to perform using theselection criteria.

Note: By default, Advanced Allocation Management only includes items in itsprocessing when specifically directed to do so.

Volume group definitions

This member contains the volume group list that defines a group of volumes fromwhich additional volumes can be selected as needed (volume group definitions areused in conjunction with the volume addition function that is available within therule definitions).

Note: Volume groups are only used for non-SMS data sets. For SMS data sets, SMSis used to select a volume based on SMS constructs.

The dynamic volume addition function, provided with the Advanced AllocationManagement rule definition syntax, helps avoid out-of-space conditions that occurduring end-of-volume processing. During end-of-volume processing, this functiondynamically adds another volume, from user-specified volume groups, when thesecondary allocation space request cannot be satisfied on the current volume.

Volume group definitions enable you to specify the volume groups from whichAdvanced Allocation Management selects these additional volumes. You define thevolume serial numbers either specifically, or generically, using a pattern maskingfacility. The volume addition function enables you to specify in any combination: avolume group, an esoteric name, or generic names.

Started task

The Advanced Allocation Management started task JCL points to the subsystemoptions member in the Advanced Allocation Management control data set which


contains the unique subsystem ID that is associated with a specific AdvancedAllocation Management subsystem.

Advanced Allocation Management subsystem

Each instance of Advanced Allocation Management is considered to be a separateAdvanced Allocation Management subsystem and must have a unique subsystemID and started task JCL to differentiate it from other Advanced AllocationManagement subsystems.

User interface

The Advanced Allocation Management user interface consists of a series of ISPFpanels that enable you to easily manage Advanced Allocation Management controldata set members, view and update Advanced Allocation Management subsystemsettings, or view recovery statistics for an active Advanced Allocation Managementsubsystem.

Advanced Allocation Management architecture and processingAdvanced Allocation Management operates at the system level to intercept x37type 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, determinewhat 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 particularerror condition involving the selected items. The extensive and flexible ruledefinitions enable you to specify many possible combinations of selection criteria(the items you want Advanced Allocation Management to include or exclude fromprocessing) and functions (the actions you want Advanced Allocation Managementto 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 andvolume group support enable you to define specific volume groups from whichAdvanced Allocation Management selects additional volumes, as needed.

After you initiate the Advanced Allocation Management started task, andcustomize and activate the appropriate definitions, no additional user interventionis required. When Advanced Allocation Management is running, it interacts withyour operating system to determine when an x37 type abend, or other similarerror, is about to occur and manages the situation according to your specifications.

Note: Advanced Allocation Management does not attempt to prevent and recoverfrom all situations—only those that you have specified using AdvancedAllocation Management definitions.

Started task and subsystem definitionAdvanced Allocation Management is designed so that multiple instances can runconcurrently on a single z/OS image. Each instance of the product is considered aseparate Advanced Allocation Management subsystem and must have a uniquesubsystem ID and started task JCL to differentiate it from other AdvancedAllocation Management subsystems that might be running on the same image.


When the started task is initiated, it references the data in the subsystem optionsmember to establish global settings, including the subsystem identifier for thisspecific instance of the product. The started task then starts the AdvancedAllocation Management subsystem and the product begins the initializationprocess during which time the control blocks are built, the product modules areloaded, and other product files are read and processed.

The following figure shows an example of a single instance of AdvancedAllocation Management on a single image:

Job A

Advanced AllocationManagement

Started Task andSubsystem

AdvancedAllocation Management

Control Data Set

User initiates the AdvancedAllocation Management started

task

The Advanced Allocation Management startedtask references the Advanced Allocation

Management control data set to obtain theunique subsystem identifier (SSID) for this

instance of Advanced AllocationManagement

Data SetProcessing

Job B

Data SetProcessing

(z/OS Allocation)

(z/OS End-Of-VolumeProcessing)

Advanced Allocation ManagementAllocation Intercepts

(subsystem options member) (DD statement)

Advanced Allocation ManagementEOV Intercepts

Once Advanced Allocation Management is running, its product-level intercepts(allocation and end-of-volume processing intercepts) interact with your operatingsystem to determine when an x37 type abend, or other similar error, is about tooccur. When Advanced Allocation Management detects a potential error condition,it manages the situation according to the product definitions specified in thecontrol data set.

Note: An Advanced Allocation Management subsystem can be active or inactive.An Advanced Allocation Management subsystem is considered active whenthe Advanced Allocation Management started task associated with thatsubsystem ID is currently running and the product-level intercepts areenabled.

Figure 1. Advanced Allocation Management (single instance)


Advanced Allocation Management subsystem identificationWhen configuring Advanced Allocation Management, you must specify a uniquefour character subsystem ID to identify the Advanced Allocation Managementsubsystem for each instance of Advanced Allocation Management that you want torun.

The Advanced Allocation Management subsystem ID identifies a specific instanceof Advanced Allocation Management within your environment and appears onproduct panels and in messages.

Running multiple instances of Advanced Allocation ManagementRunning multiple instances of Advanced Allocation Management is useful in thosesituations where you want to reserve one Advanced Allocation Managementsubsystem for testing purposes and another subsystem for production purposes.

Note: A maximum of four concurrently active subsystems on a single z/OS systemare allowed.

Multiple instances of Advanced Allocation Management can run concurrently onthe same image, or on different images: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 donot need to specify a unique subsystem identifier and started task name for eachinstance because each instance resides on a different image. For example, if youwant to run two instances of Advanced Allocation Management (one instance onimage "A" and one instance on image "B"), each subsystem identifier could bedefined as "OPT1" and each started task could be named "ALLOCPT1."

v To run multiple instances of Advanced Allocation Management on the samez/OS image, each instance must have a unique subsystem identifier and startedtask name (because there can only be one occurrence of a specific AdvancedAllocation Management subsystem running on a single image at any giventime). 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 Managementon image "B", you must specify a different subsystem ID and started task (forexample, subsystem ID "OPT2" and started task "ALLOCPT2").

Note: If you run multiple Advanced Allocation Management subsystems on thesame z/OS image, at the same time, the subsystem that was initiated last isthe subsystem whose processing takes precedence. For example, if twoAdvanced Allocation Management subsystems (OPT1 and OPT2) arerunning on image "A" and the OPT2 subsystem was initiated last—itsprocessing takes precedence over any OPT1 subsystem processing on image"A".

The following figure shows examples of multiple Advanced AllocationManagement instances that illustrate both of these scenarios.


Job B

Advanced Allocation ManagementAllocation Intercepts

Advanced AllocationManagementStarted Task(ALLOCPT1)

and Subsystem(OPT1)

Advanced AllocationManagementStarted Task

(ALLOCPT2) andSubsystem

(OPT2)


(ALLOCPT1) andSubsystem

(OPT1)

Image A

Image B


Processing

Job A

Data Set Data Set

Processing)(z/OS End-Of-Volume

(z/OS Allocation)

ProcessingData Set

Job B

ProcessingData Set

Job A

Processing)(z/OS End-Of-Volume

(z/OS Allocation)

Processing


Allocation InterceptsAdvanced Allocation Management

Note:v The Advanced Allocation Management subsystem "OPT1" that is running on

image "A" is a different subsystem than the Advanced Allocation Managementsubsystem "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 productsIt is recommended that you do not operate products that are similar to AdvancedAllocation Management in function because these products might have featuresthat are the same, or similar, to Advanced Allocation Management andunpredictable results could occur.

Figure 2. Advanced Allocation Management (multiple instances)


Summary of changesThis information summarizes the significant improvements or enhancements forAdvanced Allocation Management. New and changed information is indicated bya vertical bar (|) to the left of a change. Editorial changes that have no technicalsignificance are not noted.

SC23-9819-01v The NOTCAT2_DYNAL keyword has been added to allow selective enablement

of processing of dynamically allocated data sets for the NOTCAT2 function. See“NOTCAT2_DYNAL” on page 118 for more information.

v The NOTCAT2 function has been updated. See “Process NOT CATLGD 2 errors(NOTCAT2)” on page 60 and “NOTCAT2” on page 115 for details.

v Information about Advanced Allocation Management processing has been addedto the VOL_ADD function. See “VOL_ADD” on page 138 and “Dynamically addvolumes (VOL_ADD)” on page 73.

v The SPACE_RELEASE function description has been clarified. For moreinformation, see “SPACE_RELEASE” on page 136.

v The TERM_ALLOC function description has been updated. For moreinformation, see “TERM_ALLOC” on page 137.

v The MOUNT_USAGE function description has been clarified. For moreinformation, see “MOUNT_USAGE” on page 240.

v The description of the PRIM_REDUCE function has been updated. For moreinformation, see “Controlled reduction of primary space (PRIM_REDUCE)” onpage 65 and “PRIM_REDUCE” on page 122.

v Important information has been added to the following Enhanced AllocationManagement function keyword descriptions:– SET_DATACLAS– SET_MGMTCLAS– SET_STORCLAS– SET_STORGRPFor more information, see Chapter 11, “Enhanced Allocation Managementfunction keywords,” on page 155.

v Important information has been added to the following selection criteriakeyword descriptions:– DEVICECLASS– GUARSPACE– MOUNT_USAGE– RELEASESPACE– UNIT_TYPEFor more information, see Chapter 12, “Selection criteria,” on page 209.

v Information has been added to describe the order of processing of the SEC_*functions. See “Add a secondary allocation (SEC_ALLOC)” on page 67, “Increasethe size of secondary allocation (SEC_INC)” on page 69, “Recover fromsecondary allocation space failures (SEC_REDUCE)” on page 70, and “Reducesecondary allocation to largest available free extent (SEC_BEST)” on page 68.

v Default information has been added for the following function keywords:– AVS_UNIT– AVS_VGRP– AVS_VSER


– NOTCAT2_QUALIFIER– NOTCAT2_SUFFIX– SPACE_RELEASE– VOL_ADD_UNIT– VOL_ADD_VGRP– VOL_ADD_VSERFor details, see Chapter 10, “Function keywords,” on page 101.

v Additional examples have been added to the MSG_LEVEL keyword description.For more information, see “MSG_LEVEL” on page 113.

v Additional examples have been added to the topic “Using wildcard characters”on page 84.

v The descriptions for the SEC_ALLOC and SEC_INC function keywords havebeen clarified. For more information, see “SEC_ALLOC” on page 127 and“SEC_INC” on page 130.

v The descriptions for the VOLCT, SET_VOLCT, NUMVOLS, and SET_NUMVOLSkeywords have been updated. For more information, see Chapter 10, “Functionkeywords,” on page 101 and Chapter 12, “Selection criteria,” on page 209.

v A new message, GLO2197E, has been added. See Appendix D, “Functionmessages (non-VSAM),” on page 335 for details.

v The message number for message GLO2150I (GLO2150I VOLSER(S): VVVVVV) hasbeen changed to GLO2156I and message number GLO3150I has been changed toGLO3156I.

SC23-9819-00v 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 13.v Selection criteria keywords have been added and updated. See Chapter 12,

“Selection criteria,” on page 209 for more information.v Support for Enhanced Allocation Management has been added. See Chapter 11,

“Enhanced Allocation Management function keywords,” on page 155 for moreinformation.

v Advanced volume selection capabilities have been added. See “AdvancedVolume Selection (AVS)” on page 58 for more information.

v Additional information has been added to the GLO1036E message. SeeAppendix C, “Subsystem and started task messages,” on page 319 for moreinformation.

v The GLOJIVP1 member steps and example output have been updated. See “Step8: Verify the installation” on page 24 and Table 5 on page 25 for moreinformation.



Chapter 2. Installation and security considerations

There are several factors you need to consider when installing and securingAdvanced Allocation Management.

Hardware and software prerequisitesMake sure that you have these minimum hardware and software requirements inplace before you install Advanced Allocation Management.

Hardware prerequisites

Advanced Allocation Management runs on a mainframe system. The system mustbe 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.8and higher. No additional software is required for Advanced AllocationManagement to operate properly.

Installing and implementing Advanced Allocation ManagementThis topic provides general information about installing and implementingAdvanced Allocation Management. For specific installation instructions, see theProgram Directory for Advanced Allocation Management for z/OS.

If this is a new installation of Advanced Allocation Management, or if AdvancedAllocation Management is replacing a similar product, it is strongly recommendedthat you install and run Advanced Allocation Management in a test environmentprior to implementing it in your production environment. Doing so ensures thatthe product is configured according to your needs without impacting your currentproduction data.

After you install Advanced Allocation Management in a test environment, it isrecommended that you run a series of initial tests, followed by more extensivetesting as you gain experience with the product. After successful testing in a testenvironment, a gradual, incremental implementation of the product in yourproduction environment is recommended. For example, you might begin bycreating a series of test jobs that you can use to become familiar with AdvancedAllocation Management features and functions. Use Advanced AllocationManagement selection criteria to specify that only these test jobs should beincluded in Advanced Allocation Management processing.

Important: If Advanced Allocation Management is replacing a similar product atyour installation:v Be sure to fully test it in a test environment prior to installing it in

your production environment.v Perform an IPL prior to starting Advanced Allocation Management.

(Advanced Allocation Management cannot run concurrently withother products that perform similar functionality.)

13

|||

Coexistence with prior versions

Follow these guidelines if you have a prior version of Advanced AllocationManagement (the IBM Tivoli Allocation Optimizer for z/OS product) and you arealso installing Advanced Allocation Management 3.1.1. If you start Allocation Optimizer 2.1 first, after an IPL, you can start Advanced

Allocation Management 3.1 without having to perform an IPL. To ensure theproper functioning of Advanced Allocation Management 3.1, be sure not tostart it until after Allocation Optimizer 2.1 has finished initializing.

2. You must perform an IPL before starting Advanced Allocation Management 3.1if you have first started any other version of Allocation Optimizer besidesversion 2.1.

3. If you start Advanced Allocation Management 3.1 first, after an IPL, you cannotrun any other release of Advanced Allocation Management (AllocationOptimizer) without first performing an IPL.

Migration considerations and requirementsWhen migrating to Advanced Allocation Management, follow these considerationsand requirements.

If Advanced Allocation Management is replacing a similar product at yourinstallation, it is recommended that you perform the migration process in a testenvironment prior to performing the migration in your production environment toensure that the migration will work as expected. After you have successfullyperformed the migration in the test environment, you can begin the process ofmigrating from your previous product to Advanced Allocation Management inyour production environment.

During the migration process it is not necessary to uninstall any similar productyou might have, however it is important to note that Advanced AllocationManagement cannot run concurrently with other products that perform similarfunctionality. This is because Advanced Allocation Management and similarproducts operate by intercepting events at low levels within the operating systemand Advanced Allocation Management cannot determine with any certainty howanother product might have established itself within the operating system.

Therefore, to avoid potential conflicts and help ensure trouble-free operation:v Do not run Advanced Allocation Management concurrently with a similar

product.v It is strongly recommended that you perform an IPL prior to starting Advanced

Allocation Management if a similar product has been running on the system(and vice-versa).

Migration stepsComplete these steps when migrating to Advanced Allocation Management.

Step 1: PlanningComplete these steps when planning a migration to Advanced AllocationManagement.1. Review all installation and migration documentation including prerequisites.2. Collect existing product data from the current production environment.


|||

||||

3. Determine the test system on which you want to initially install AdvancedAllocation Management.

Step 2: Install Advanced Allocation Management in a testenvironment

Complete these steps to install Advanced Allocation Management in a testenvironment.1. Install Advanced Allocation Management on the test system using the supplied

sample rule definitions (RULEDEFS) and volume group definitions(VGRPDEFs) members generated during the installation process.

2. Install any required and recommended Advanced Allocation Managementmaintenance on the test system.

3. Start Advanced Allocation Management.4. Run the IVP job supplied in the sample library data set to verify the installation

of Advanced Allocation Management on the test system.

Step 3: Convert product definitions and testComplete these steps to convert product definitions.1. If, after running the IVP job, you want to run additional test jobs, create a copy

of the RULEDEFS and VGRPDEFS members and modify them to include thetest jobs for Advanced Allocation Management processing.When changing the RULEDEFS and VGRPDEFS members to specify your testjobs, the RULEDEF_TEST keyword can be added and set to ENABLE. This willallow you verify that the selection criteria you have specified will match theentities (jobs, data sets, and so on) that you intended.After you have successfully tested your RULEDEFS, you can setRULEDEF_TEST to DISABLE (or remove it entirely) and allow AdvancedAllocation Management to perform processing. To accomplish this, modify thespace value in your test application.During testing, you can modify the space values in your test application JCL toforce out-of-space conditions to occur (simply adjust the primary andsecondary quantities in your test application JCL as needed).

Note: In order for the definitions to take effect, you must activate them usingthe online dialog or the appropriate z/OS command.

2. Run the test jobs to ensure that Advanced Allocation Management is workingas you intended.

3. Manually convert your existing product processing definitions to AdvancedAllocation Management rule and volume group definitions.

4. Run Advanced Allocation Management with the converted production controlmembers in the test environment with copies of the production jobs.

Step 4: Migrate to productionAfter testing is complete and any issues have been resolved (control members havebeen updated, and so on) run Advanced Allocation Management in place of yourexisting product on the production system.

Note: An IPL is required if the existing product was previously running on thez/OS image since the last IPL.

Chapter 2. Installation and security considerations 15

Migration and installation documentationIn addition to the installation information provided in the Program Directory forAdvanced Allocation Management for z/OS, you might find these topics helpful whenperforming the migration process.

Table 1. Migration topics

For information about: See:

Security v “Security considerations”

v “Step 5: Secure the user interface update functions”on page 22

Installation and configuration v Chapter 3, “Configuring Advanced AllocationManagement,” on page 19

Definition management v Chapter 4, “Advanced Allocation Managementdefinition management,” on page 31

v Chapter 6, “Using rule definitions to defineprocessing,” on page 51

v Chapter 7, “Defining volume groups,” on page 79

Security considerationsAdvanced Allocation Management provides data availability benefits to all users ofthe system. To help ensure product security and processing integrity, it isrecommended that Advanced Allocation Management product definitions becreated, modified, and maintained by select users (such as system programmersand production control personnel).

The Advanced Allocation Management user interface provides users with theability to view and update selected subsystem options. To enable you to control auser's ability to modify these settings, Advanced Allocation Management leveragesRACF and RACF profiles and access authorities to determine whether or not aspecific user can perform Advanced Allocation Management update functions.

Note: While RACF is specifically cited, other SAF-based security products can beused to secure the Advanced Allocation Management user interface updatefunctions.

Securing the control data setBecause the control data set contains options that define Advanced AllocationManagement processing, it is recommended that you secure the control data set asyou would any other system data set in your shop.

Securing user interface update functionsBy default, the Tivoli Advanced Allocation Management Subsystem Settings screenprovides users with the ability to view and update selected subsystem options. Toenable you to control a user's ability to modify these settings, Advanced AllocationManagement leverages RACF and RACF profiles and access authorities.

Note: While this discussion refers specifically to RACF, it applies equally to otherSAF-based security products.


Advanced Allocation Management uses these RACF profiles to determine whetheror not a specific user can perform Advanced Allocation Management updatefunctions:v GLO.ADMIN.ssid (where ssid is a specific four-character Advanced Allocation

Management subsystem—for example, "AOP1")v GLO.ADMIN.* (where * indicates all subsystems)

These profiles must exist in the RACF FACILITY class. If the FACILITY class doesnot exist, then the user interface update functions are not secure.

Note: "GLO " is the product prefix for Advanced Allocation Management and isused to identify the product in product messages, data set members, and soon.

To perform update functions, a user's record must exist in the one of these GLO.*profiles within the FACILITY class, and their access authority must be UPDATE. Ifthe user's access authority is not UPDATE, then the user can only view informationon the Tivoli Advanced Allocation Management Subsystem Settings screen (noupdating is permitted).

Note: The access authority for a specific subsystem profile (GLO.ADMIN.ssid)takes precedence over the more generic "all subsystems" profile(GLO.ADMIN.*). For example, if a user has UPDATE authority for allsubsystems, but for a specific subsystem profile, has only viewing privileges,the user will only be able to view subsystem settings for that particularsubsystem.

How Advanced Allocation Management uses RACF todetermine access to update functions

If you are using RACF to secure the update functions, these actions occur when auser selects an update option from the Tivoli Advanced Allocation ManagementSubsystem Settings screen:1. Advanced Allocation Management instructs RACF to verify whether or not the

resource (the update options on the Tivoli Advanced Allocation ManagementSubsystem Settings screen) is protected.

2. If the resource is protected, as in the case of the update functions on the TivoliAdvanced Allocation Management Subsystem Settings screen, RACF uses theresource name to search for the profile GLO.ADMIN.ssid. If RACF does notfind the profile, it searches for more generic profiles in this order:GLO.ADMIN.*, GLO.*, and finally, **.

3. When a profile is found, RACF determines if the user is on the profile's accesslist.v If the user is on the profile's access list — RACF compares the user's access

intent to the access authority; if the access intent and access authority permit,the user is allowed to perform the update option.

v If the user is not on the profile's access list — RACF compares the user'saccess intent to the universal access (UACC) of the profile and the user ispermitted (or not permitted) to perform the update option.

For information about RACF, RACF profiles and access authorities, see RACFGeneral Information.

Chapter 2. Installation and security considerations 17

Security and internal work data setsSome Advanced Allocation Management internal work data sets are created usinga high-level qualifier consisting of the value of the TSO PROFILE PREFIX, ifpresent. (If the TSO PROFILE is set to NOPREFIX the high-level qualifier will beset to the TSO USERID.)

Therefore, you should define your security profiles accordingly to allow creationand deletion of these internal data sets.

Security and definition managementTo help ensure product security and processing integrity, Advanced AllocationManagement product definitions should be created, modified, and maintained byselect users, such as system programmers and production control personnel.

Authorizing the started task for selected NOTCAT2 functionsThe Advanced Allocation Management started task must be authorized using yoursecurity authorization product to allow the uncataloging, deletion, and renaming ofdata sets if the NOTCAT2 functions of UNCATALOG, SCRATCH, and RENAMEwill be used.


Chapter 3. Configuring Advanced Allocation Management

To install Advanced Allocation Management, follow the installation instructionsprovided in the Program Directory for Advanced Allocation Management for z/OSincluded with Advanced Allocation Management. After you install AdvancedAllocation Management, perform these steps to configure Advanced AllocationManagement for your environment.

Configuration summaryThis table summarizes the steps you need to complete to successfully configureAdvanced Allocation Management for your environment.

Table 2. Summary of Advanced Allocation Management configuration steps

Step Description Member name

1 Authorize the required load libraries (not applicable)

2 Configure the started task JCL GLOJSTC

3 Allocate the Advanced Allocation Managementcontrol data set

GLOJCNTL

4 Specify the Advanced Allocation Managementsubsystem options

OPTIONS

5 Secure user interface update functions (not applicable)

6 Configure the CLISTS GLO, GLOCLIST

7 Initiate the Advanced Allocation Managementstarted task

(not applicable)

8 Verify the installation GLOJIVP1

Configuration stepsPerform these steps to configure Advanced Allocation Management.

It is strongly recommended that before you begin the process of configuringAdvanced Allocation Management, you copy your SMP/E target libraries to yourruntime libraries and then configure the runtime libraries. Doing so allows you to:v apply maintenance without being in contention with the Advanced Allocation

Management started task and with anyone using the ISPF interfacev take greater control of maintenance rolloutsv avoid overlaying any changes made during the configuration process

Note: You will need to refresh your runtime libraries and re-specify yourconfiguration values for any elements altered when maintenance is applied.

Step 1: APF-authorize the load librariesThe load library containing Advanced Allocation Management (HILEVEL.SGLOLOAD)must be APF authorized.

19

To ensure that the Advanced Allocation Management (HILEVEL.SGLOLOAD) library isAPF-authorized, include this library as part of your system APF-authorized list.For more information about APF authorization, see the MVS Programming:Authorized Assembler Services Guide.

Step 2: Configure the started task JCLThe Advanced Allocation Management started task JCL is located in the GLOJSTCmember of the Advanced Allocation Management sample library (SGLOSAMP).

To configure the started task JCL, complete these steps:1. Copy the Advanced Allocation Management started task JCL to your system

PROCLIB.

Tip: It is recommended that you name the Advanced Allocation Managementstarted task member "ALLOCOPT" because this name is easily identifiablewith the Advanced Allocation Management product.

2. Verify that the statement: //ALLOCOPT PROC OPTSMBR=OPTIONS points to themember name "OPTIONS."

Note: "OPTIONS" is the default member name of the subsystem optionsmember of the Advanced Allocation Management control data setallocated in “Step 3: Allocate the control data set” on page 21.

3. Configure the started task JCL that you copied to your system PROCLIB byreplacing GLO.V3R1 with the high-level qualifier of the installed AdvancedAllocation Management load libraries.

Note:

v A DD statement with a DDNAME of OPTIONS must be presentwithin the Advanced Allocation Management started task. This DDstatement points to the subsystem options member of the AdvancedAllocation Management control data set (OPTIONS) which containsthe global settings for the product. When the started task is initiated, itreferences the data in the subsystem options member to establishglobal settings, including the subsystem identifier for this specificinstance of Advanced Allocation Management.

v A DD statement with a DDNAME of CONTROL must be presentwithin the Advanced Allocation Management started task. Forexample://CONTROL DD DSN=GLO.V3R1.CONTROL,DISP=SHR

This DD statement points to the Advanced Allocation Managementcontrol data set that contains the rule definitions (RULEDEFS) andvolume group definitions (VGRPDEFS).

v To ensure proper installation and operation, the high-level qualifieryou specify for the control data set JCL in “Step 3: Allocate the controldata set” on page 21 must match the high-level qualifier you specifyin the started task JCL.

v The started task must have the authority to read the AdvancedAllocation Management control data set and load library.

v The Advanced Allocation Management started task must beauthorized using your security authorization product to allow theuncataloging, deletion and renaming of data sets if the NOTCAT2functions of UNCATALOG, SCRATCH, and RENAME will be used.


After you configure the started task JCL, add it to z/OS for started task initiation.

Note: Do not attempt to initiate the started task until you have finishedconfiguring Advanced Allocation Management. Attempting to initiate thestarted task prior to completing configuration could cause the started task tofail.

Step 3: Allocate the control data setThe options and definitions that determine how Advanced Allocation Managementperforms processing in your environment reside in the Advanced AllocationManagement control data set. The JCL to create the control data set is located inthe GLOJCNTL member of the SGLOSAMP library.

To allocate the Advanced Allocation Management control data set and generate thesample PDS members, complete these steps:1. Configure the GLOJCNTL member by replacing GLO.V3R1 with the high-level

qualifier of the installed Advanced Allocation Management load libraries.

Note: The high-level qualifier that you specify must match the high-levelqualifier you specified in “Step 2: Configure the started task JCL” onpage 20.

2. Submit the JCL to create the control data set. The JCL creates the control dataset and populates the data set with these sample members: subsystem options(OPTIONS), rule definition (RULEDEFS), and volume group definition(VGRPDEFS).

Step 4: Specify subsystem optionsTo configure Advanced Allocation Management, you must specify a four-characterAdvanced Allocation Management subsystem ID (for example: AOPT) to associatewith this particular instance of Advanced Allocation Management. The AdvancedAllocation Management SSID identifies the Advanced Allocation Managementsubsystem on product panels and in messages generated by the product.

The Advanced Allocation Management subsystem options reside in the OPTIONSmember of the Advanced Allocation Management control data set generated by theGLOJCNTL member JCL. These options are the global definitions and generaloperation options that determine where and how Advanced AllocationManagement performs its functions.

To specify Advanced Allocation Management subsystem options, modify thecontents of the OPTIONS member as described in Table 3.

Table 3. Specifying subsystem options

Subsystem option Description

SSID Specify the four-character alphanumeric Advanced AllocationManagement subsystem ID that identifies this particular instanceof Advanced Allocation Management. For example, "AOP1","AOP2", and so on. The default subsystem ID is "AOPT."

INITIAL_RULEDEF Specify the name of the rule definitions member to use uponstartup. The default rule definitions member name is RULEDEFS.

INITIAL_VGRPDEF Specify the name of the volume group definitions member to useupon startup. The default volume group definitions member nameis VGRPDEFS.

Chapter 3. Configuring Advanced Allocation Management 21

Table 3. Specifying subsystem options (continued)

Subsystem option Description

SMF_RECORD_ID Specify the SMF record type to use for Advanced AllocationManagement.Notes:

1. If you do not specify the SMF record type, AdvancedAllocation Management will not write any SMF records.

2. If you are recording SMF data for an existing product andwant to also record SMF data for Advanced AllocationManagement, select a new, previously unused record type.(Once SMF data has been generated for a given record type,SMF data from a different source and in a different formatshould not be written using that same record type.)

For information about how Advanced Allocation Managementuses the SMF record type you specify, see Chapter 14, “Eventrecording and reporting,” on page 287.

Step 5: Secure the user interface update functionsAdvanced Allocation Management uses RACF profiles and access authorities todetermine a user's ability to perform update functions from the Tivoli AdvancedAllocation Management Subsystem Settings screen.

These profiles and access authorities are summarized in the table below.

Table 4. RACF profiles and access authorities used to secure update functions

If a user's recordexists in the profile:

and their accessauthority is: then the user can:

GLO.ADMIN.ssid UPDATE Perform update functions for the AdvancedAllocation Management subsystem specified byssid

GLO.ADMIN.* UPDATE Perform update functions for all AdvancedAllocation Management subsystems

GLO.ADMIN.ssid (not UPDATE) Perform view functions for the AdvancedAllocation Management subsystem specified byssid (no update functions are permitted)

GLO.ADMIN.* (not UPDATE) Perform view functions for all AdvancedAllocation Management subsystems (no updatefunctions are permitted)

Note: The profiles described in this table must exist in the RACF FACILITY class.If the FACILITY class does not exist, then the update functions are notsecure.

To secure the Tivoli Advanced Allocation Management Subsystem Settings screenupdate functions, complete these steps:1. Use RACF to create the GLO.ADMIN.ssid and GLO.ADMIN.* profiles.2. Add user records to the appropriate profiles giving each user access authority

according to your installation's security requirements.v To give a user the ability to perform update options for all Advanced

Allocation Management subsystems, ensure that their user record exists inthe GLO.ADMIN.* profile with an access authority of UPDATE.


v To give a user the ability to perform update options for a specific AdvancedAllocation Management subsystem, ensure that their user record exists in theGLO.ADMIN.ssid profile (where ssid denotes a specific Advanced AllocationManagement subsystem, for example: AOPT) with an access authority ofUPDATE.

For information about RACF profiles and access authorities, see RACF GeneralInformation.

Step 6: Configure the CLISTs and start the AdvancedAllocation Management user interface

To start the Advanced Allocation Management user interface, run the AdvancedAllocation Management CLIST. However, before doing so, you must first configuretwo CLISTs (GLO and GLOCLIST) located in the SGLOSAMP sample library, towork in your environment.

The statements within the GLO member allow you to start the AdvancedAllocation Management user interface CLIST (GLOCLIST) as a separateapplication, therefore enabling you to continue your ISPF session should youencounter a problem with this particular instance of Advanced AllocationManagement.

To configure the CLISTS and start the Advanced Allocation Management userinterface user interface, complete these steps.1. To configure the GLO member, complete these steps:

a. Copy the GLO member to your system CLIST library.

Note: You must copy the GLO member to your system CLIST library to runthe GLO CLIST using a TSO command.

b. In the PROC 0 CLISTLIB () statement, specify the name of the data setwhere the GLOCLIST member was copied. For example:PROC 0 CLISTLIB(ABCD.USER.CLIST)

2. The GLOCLIST starts the Advanced Allocation Management user interface. Toconfigure the GLOCLIST, specify the high-level qualifier between theparentheses using the format:PROC 0 HILEVEL(HILEVEL)

Where HILEVEL is the high-level qualifier. For example: PROC 0 HLQ(GLO.V3R1)

3. To start the user interface and access the Tivoli Advanced AllocationManagement Primary Option Menu, type the TSO command: TSO GLO

When you run the CLIST, the Tivoli Advanced Allocation Management PrimaryOption Menu menu appears. (Press Enter to remove the copyright statement.)

Step 7: Start the started taskThis information describes how to start and stop the Advanced AllocationManagement started task.

To start and stop the Advanced Allocation Management started task, do thefollowing:v Initiate the Advanced Allocation Management started task by issuing the START

command from the operator console. For example:START ALLOCOPT


v Stop the Advanced Allocation Management started task by issuing the STOPcommand from the operator console. For example:STOP ALLOCOPT

Note: It is recommended that you configure the Advanced AllocationManagement started task to start automatically when z/OS is IPLed. Toaccomplish this, add the appropriate command to the COMMNDxxmember in SYS1.PARMLIB. (If needed, consult your support personnel toimplement this automatic startup.)

Step 8: Verify the installationAfter you install and configure Advanced Allocation Management, verify thatAdvanced Allocation Management is properly installed using the JCL provided inthe GLOJIVP1 member of the SGLOSAMP Advanced Allocation Managementsample library. The JCL provided in this member is designed to be used inconjunction with the sample rule definitions (RULEDEFS) and volume groupdefinitions (VGRPDEFS) members to verify the basic operation of the AdvancedAllocation Management functions. Each portion of the GLOJIVP1 member isdescribed, including the results you should obtain during a successful verificationprocess.

Notes:

v You can run the JCL provided in the GLOJIVP1 member on any z/OSimage where you want to verify the installation of Advanced AllocationManagement.

v Any SMS data class to which an IVP test data set is assigned shouldhave the SMS ADD'L VOLUME AMOUNT attribute option set to (P)Primary.

v After you successfully run the GLOJIVP1 JCL, you can performadditional tests to ensure that Advanced Allocation Management is setup and working for the types of production applications in use at yourinstallation.

To verify the Advanced Allocation Management installation, complete these steps:1. Modify the installation verification JCL in the GLOJIVP1 member by changing

all occurrences of the high-level qualifier ?GLOHLQ? to GLO.V3R1 (or to thehigh-level qualifier of the installed Advanced Allocation Management libraries).

2. Modify the VGRPDEFS member to add valid volume serial numbers for theinitial test volume group.

Note: You do not need to modify the RULEDEFS member. This member hasbeen predefined to work with the installation verification JCL providedin member GLOJIVP1.

3. Start the Advanced Allocation Management started task if you have not alreadydone so.

4. Submit the modified JCL that resides in the GLOJIVP1 member.

For each step in the job, compare your results with the expected results describedin Table 5 on page 25.


Table 5. GLOJIVP1 summary and expected results

Step Description Expected results

DELETE1-DELETE9,DELETEA-DELETED

These steps delete the testdata sets that are usedduring the installationverification process.Performing these stepsensures that you do nothave any previously usedtest data sets that mightalter your results.

Return code 0

ALLOC1 The ALLOC1 step allocatesthe test data set. This stepof the installationverification job allocates thetest data set in preparationfor the next series of tests.

Return code 0.

AVS The AVS step tests the AVSfunction for non-VSAMdata sets.Note: The data set beingcreated in this step must bea non SMS-managed dataset.

Return code 0 and the messages:

GLO2148I AVS HAS SUCCESSFULLY SELECTED ALLVOLUMES

GLO2156I VOLSER(S): VVVVVV

GLO2123I GLOJIVP1,AVS,,SYSUT2,DSNAME

Where DSNAME is the name of the data setand VVVVVV is the volser chosen.

DIRINC The DIRINC step tests thePDS_DIR_INC function bydynamically adding asecond directory block to aPDS that has a fulldirectory.


GLO2150I INCREASING PDS DIRECTORY SIZE

GLO2123I GLOJIVP1,DIRINC,,DD21,DSNAME

Where DSNAME is the name of the data set.

DSINIT The DSINIT step tests theDATASET_INIT function.


GLO2080I INITIALIZING DATA SET

GLO2123I GLOJIVP1,DSINIT,,DD1,DSNAME

Where DSNAME is the name of the data set.Note: These results will only be obtained ifAdvanced Allocation Management has beeninitialized with Z1_INTERCEPT=ENABLEspecified in the OPTIONS member. Otherwisethe step will end with RC=0 but the data setwill not be initialized and the messages willnot be issued.

NCATCRE The NCATCRE step createsthe test data set forNOTCAT2=SCRATCH.Thisstep of the installationverification job allocates atest data set in preparationfor the next test.

Return code 0


|

Table 5. GLOJIVP1 summary and expected results (continued)


NCATSCR The NCATSCR step teststhe NOTCAT2 function.This step tests theNOTCAT2=SCRATCHfunction using a test dataset which is deleted whenthe test is completed.


GLO2084I DATA SET ON VOLSER VVVVVVSCRATCHED AT ALLOCATION TIME

GLO2123I GLOJIVP1,NCATSCR,,SYSUT2,DSNAME

Where DSNAME is the name of the data setand VVVVVV is the volser of the volume onwhich the old data set was cataloged.

NOTCAT2 The NOTCAT2 step teststhe NOTCAT2 function.Note: You must manuallydelete both the SYSUT4AND SYSUT5 data sets assuccessful verification ofthe NOTCAT2 step willresult in termination of thejob. The data sets youspecify for this step mustnot be SMS-managed datasets.


GLO2051I JOB SET TO FAIL DUE TO NOT CATLGD2 ON VOLSER VVVVVV

GLO2123I GLOJIVP1,NOTCAT2,,SYSUT5,DSNAME

Where DSNAME is the name of the data setand VVVVVV is the volser of the volume onwhich the NOT CATLGD 2 error occurred.Note: You must manually delete the SYSUT4and SYSUT5 data sets as successful verificationof the NOTCAT2 step will result in terminationof the job. The data sets used in this step mustnot be SMS-managed data sets.

PRIMRED The PRIMRED step teststhe PRIM_REDUCEfunction by reducing a highprimary allocation quantityfor the test data set untilthe allocation is successful.


GLO2118I REDUCING PRIMARY ALLOCATION TONNNNN TRACKS

GLO2123I GLOJIVP1,PRIMRED,,SYSUT2,DSNAME

Where NNNNN is the new allocation quantityand DSNAME is the name of the data set.Note: There might be multiple sets of the firsttwo messages depending upon the amount ofavailable space on the volume.

SECALLOC The SECALLOC step teststhe SEC_ALLOC functionby adding a secondaryallocation amount whenthe test data set expands toits second extent.


GLO2100I SETTING SECONDARY ALLOCATION TO 1TRKS

GLO2123I GLOJIVP1,SECALLOC,,SYSUT2,DSNAME


SECBEST The SECBEST step tests theSEC_BEST function bylowering a large secondaryallocation quantity for thetest data set to a value thatwill fit on the volume.


GLO2103I EXTENT-MATCHING SECONDARYALLOCATION TO NNNNN TRKS

GLO2123I GLOJIVP1,SECBEST,,SYSUT2,DSNAME

Where NNNNN is the new allocation quantitythat reflects the largest available extent andDSNAME is the name of the data set.




SECINC The SECINC step tests theSEC_INC function bystarting at the third extentof the test data set andthen increasing thesecondary allocationamount by 100% of theprevious amount.


GLO2106I INCREASING SECONDARY ALLOCATION TO2 TRKS

GLO2123I GLOJIVP1,SECINC,,SYSUT2,DSNAME

GLO2106I INCREASING SECONDARY ALLOCATION TO4 TRKS



SECRED The SECRED step tests theSEC_REDUCE function byreducing the secondaryallocation amount for thetest data set to the largestavailable extent (after asecondary allocation failureoccurs).


GLO2109I REDUCING SECONDARY ALLOCATION TONNNNN TRKS



SECREL The SECREL step tests theSEC_RELEASE function byallocating several tracks forthe test data set —however, only one of thetracks is used (a partialrelease truncates theunused tracks leaving onlyone for the primaryallocation).


GLO2125I SPACE RELEASE RECOVERED NNNNNNNNNTRACKS

GLO2123I GLOJIVP1,SECREL,,SYSUT2,DSNAME

Where NNNNNNNNN is the number of tracksreleased and DSNAME is the name of the dataset.

SETCLASS The SETCLASS step teststhe SET_DATACLASReturn code 0 and themessages: function. Thedata set will be assigned aninvalid data class in theJCL which will be removedby the SET_DATACLASfunction.


GLO2194I SET PROCESSING COMPLETE;DATACLAS=(NULL) (OLD VALUE=DDDDDDDD)

GLO2123I GLOJIVP1,,,SYSUT9,DSNAME

Where DSNAME is the name of the data setand DDDDDDDD is the name of the dataclass.

SETUNITNT The SETUNITNT step teststhe SET_UNITNAMEfunction. The data set willbe assigned an invalid unitname in the JCL which willbe changed to SYSALLDAby the SET_UNIT_NAMEfunction.


GLO2194I SET PROCESSING COMPLETE;UNIT_NAME=SYSALLDA (OLD VALUE=ABCDEFGH)

GLO2123I GLOJIVP1,SETUNITN,,DD1,DSNAME





VAVS The VAVS step tests theAVS function for VSAMdata sets.Note: The data set beingcreated in this step must bea non SMS-managed dataset.


GLO3148I AVS HAS SUCCESSFULLY SELECTED ALLVOLUMES-DATA


GLO3123I GLOJIVP1,VAVS,,,DSNAME

GLO3148I AVS HAS SUCCESSFULLY SELECTED ALLVOLUMES-INDEX


GLO3123I GLOJIVP1,VAVS,,,DSNAME

Where DSNAME is the name of the data setand VVVVVV is the volser chosen.

VOLADD The VOLADD step teststhe VOL_ADD function bytesting the need to extendto an additional volume.


GLO2128I DATA SET SUCCESSFULLY EXTENDED TOVOLUME VVVVVV

GLO2123I GLOJIVP1,VOLADD,,SYSUT4,DSNAME

Where DSNAME is the name of the data setand VVVVVV is the volser of the volume towhich the data set was extended.

VPRIMRED The VPRIMRED step teststhe PRIM_REDUCEfunction by defining aVSAM data set with a highprimary allocation quantity.


GLO3118I REDUCING PRIMARY ALLOCATION TONNNNN CYLINDERS

GLO3123I GLOJIVP1,VPRIMRED,,,DSNAME

Where NNNNN is the new allocation quantityand DSNAME is the name of the data set.Note: There might be multiple sets of the firsttwo messages depending upon the amount ofavailable space on the volume.

VSECALC The VSECALC step teststhe SEC_ALLOC functionby defining a VSAM dataset with a zero secondaryallocation quantity andcopying data into it.


GLO3100I SETTING SECONDARY ALLOCATION TO 1CYLS

GLO3123I GLOJIVP1,VSECALC,,SYS0002,DSNAME


VSECBEST The VSECBEST step teststhe SEC_BEST function bydefining a VSAM data setwith a high secondaryallocation quantity andcopying data into it.


GLO3103I EXTENT-MATCHING DATA SECONDARYALLOCATION TO NNNNN CYLS

GLO3123I GLOJIVP1,VSECBST,,SYS0004,DSNAME



|

|



VSECRED The VSECRED step teststhe SEC_REDUCE functionby defining a VSAM dataset with a high secondaryallocation quantity andcopying data into it.


GLO3109I REDUCING DATA SECONDARY ALLOCATIONTO NNNNN CYLS

GLO3123I GLOJIVP1,VSECRED,,SYS0006,DSNAME


VVOLADD The VVOLADD step teststhe VOL_ADD function bydefining a VSAM data setwith a zero secondaryallocation quantity andcopying data into it.


GLO3128I DATA SUCCESSFULLY EXTENDED TOVOLUME VVVVVV - SSSS

GLO3123I GLOJIVP1,VVOLADD,,SYS0008,DSNAME

Where DSNAME is the name of the data set,VVVVVV is the volser of the volume to whichthe data set was extended, and SSSS is thesubsystem.

After you have finished verifying the installation, the next step is to defineAdvanced Allocation Management processing in your environment by creating ruledefinitions and volume group definitions according to your installation'srequirements.

Successful GLOJIVP1 resultsThis information shows an example of the results you should see after yousuccessfully run the GLOJIVP1 JCL.


||

||||

IRR010I USERID PDABC1 IS ASSIGNED TO THIS JOB.GLO2194I SET PROCESSING COMPLETE; DATACLAS=(NULL) (OLD VALUE=TEST)GLO2123I GLOJIVP1,,,SYSUT9,NSMS.GLO.TEST.DATAICH70001I PDABC1 LAST ACCESS AT 11:54:14 ON TUESDAY, JUNE 30, 2009$HASP373 GLOJIVP1 STARTED - INIT 1 - CLASS A - SYS RL13RKTSW01I ------------- Timings (HH:MM:SS.hh) --------------RKTSW01I JOBNAME STEPNAME PROCSTEP STEP RC CPU (Total) CPU (TCB) CPU (SRB) CPU (Other)RKTSW01I GLOJIVP1 DELETE1 1 00 00:00:00.47 00:00:00.06 00:00:00.00 00:00:00.41RKTSW01I PRIMRED 2 00 00:00:00.10 00:00:00.08 00:00:00.00 00:00:00.02RKTSW01I DELETE2 3 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2100I SETTING SECONDARY ALLOCATION TO 1 TRKS -J310GLO2123I GLOJIVP1,SECALLOC,,SYSUT2,NSMS.GLO.TEST.DATA -J310RKTSW01I SECALLOC 4 00 00:00:00.10 00:00:00.08 00:00:00.00 00:00:00.02RKTSW01I DELETE3 5 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2103I EXTENT-MATCHING SECONDARY ALLOCATION TO 3930 TRKS -J310GLO2123I GLOJIVP1,SECBEST,,SYSUT2,NSMS.GLO.TEST.DATA -J310RKTSW01I SECBEST 6 00 00:00:00.10 00:00:00.08 00:00:00.00 00:00:00.02RKTSW01I DELETE4 7 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2106I INCREASING SECONDARY ALLOCATION TO 2 TRKS -J310GLO2123I GLOJIVP1,SECINC,,SYSUT2,NSMS.GLO.TEST.DATA -J310GLO2106I INCREASING SECONDARY ALLOCATION TO 4 TRKS -J310GLO2123I GLOJIVP1,SECINC,,SYSUT2,NSMS.GLO.TEST.DATA -J310RKTSW01I SECINC 8 00 00:00:00.12 00:00:00.09 00:00:00.00 00:00:00.03RKTSW01I DELETE5 9 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2109I REDUCING SECONDARY ALLOCATION TO 65534 TRKS -J310GLO2123I GLOJIVP1,SECRED,,SYSUT3,NSMS.GLO.TEST.DATA -J310RKTSW01I SECRED 10 00 00:00:00.10 00:00:00.08 00:00:00.00 00:00:00.02RKTSW01I DELETE6 11 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2125I SPACE RELEASE RECOVERED 9 TRACKS -J310GLO2123I GLOJIVP1,SECREL,,SYSUT2,NSMS.GLO.TEST.DATA -J310RKTSW01I SECREL 12 00 00:00:00.10 00:00:00.08 00:00:00.00 00:00:00.02RKTSW01I DELETE7 13 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2128I DATA SET SUCCESSFULLY EXTENDED TO VOLUME NSL204 -J310GLO2123I GLOJIVP1,VOLADD,,SYSUT4,NSMS.GLO.TEST.DATA -J310RKTSW01I VOLADD 14 00 00:00:00.21 00:00:00.16 00:00:00.02 00:00:00.03RKTSW01I DELETE8 15 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02RKTSW01I ALLOC1 16 00 00:00:00.07 00:00:00.06 00:00:00.00 00:00:00.01GLO2150I INCREASING PDS DIRECTORY SIZE -J310GLO2123I GLOJIVP1,DIRINC,,DD21,NSMS.GLO.TEST.DATA -J310RKTSW01I DIRINC 17 00 00:00:00.40 00:00:00.27 00:00:00.02 00:00:00.11RKTSW01I DELETE9 18 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2080I INITIALIZING DATA SET -J310GLO2123I GLOJIVP1,DSINIT,,DD1,NSMS.GLO.TEST.DATA -J310RKTSW01I DSINIT 19 00 00:00:00.09 00:00:00.07 00:00:00.00 00:00:00.02RKTSW01I DELETEA 20 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02RKTSW01I SETCLASS 21 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02RKTSW01I DELETEB 22 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2194I SET PROCESSING COMPLETE; UNIT_NAME=SYSALLDA (OLD VALUE=ABCDEFGH) -J310GLO2123I GLOJIVP1,SETUNITN,,DD1,NSMS.GLO.TEST.DATA -J310RKTSW01I SETUNITN 23 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02RKTSW01I DELETEC 24 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02GLO2148I AVS HAS SUCCESSFULLY SELECTED ALL VOLUMES -J310GLO2156I VOLSER(S): NSL204 -J310GLO2123I GLOJIVP1,AVS,,SYSUT2,NSMS.GLO.TEST.DATA -J310RKTSW01I AVS 25 00 00:00:00.09 00:00:00.07 00:00:00.00 00:00:00.02RKTSW01I DELETED 26 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02RKTSW01I VPRIMRED 27 00 00:00:00.25 00:00:00.25 00:00:00.00 00:00:00.00GLO3100I SETTING SECONDARY ALLOCATION TO 1 CYLS -J310GLO3123I GLOJIVP1,VSECALC,,SYS00005,RSTEST.VSAM.TEST -J310RKTSW01I VSECALC 28 00 00:00:00.32 00:00:00.31 00:00:00.00 00:00:00.01GLO3103I EXTENT-MATCHING DATA SECONDARY ALLOCATION TO 291 CYLS -J310GLO3123I GLOJIVP1,VSECBST,,SYS00007,RSTEST.VSAM.TEST -J310RKTSW01I VSECBST 29 00 00:00:00.31 00:00:00.30 00:00:00.00 00:00:00.01GLO3109I REDUCING DATA SECONDARY ALLOCATION TO 291 CYLS -J310GLO3123I GLOJIVP1,VSECRED,,SYS00009,RSTEST.VSAM.TEST -J310RKTSW01I VSECRED 30 00 00:00:00.30 00:00:00.30 00:00:00.00 00:00:00.00GLO3128I DATA SUCCESSFULLY EXTENDED TO VOLUME NSL204 -J310GLO3123I GLOJIVP1,VVOLADD,,SYS00013,NSMS.VSAM.TEST -J310RKTSW01I VVOLADD 31 00 00:00:00.23 00:00:00.23 00:00:00.00 00:00:00.00GLO3148I AVS HAS SUCCESSFULLY SELECTED ALL VOLUMES-DATA -J310GLO3156I VOLSER(S): NSL204 -J310GLO3123I GLOJIVP1,VAVS,,,NSMS.VSAM.TEST -J310GLO3148I AVS HAS SUCCESSFULLY SELECTED ALL VOLUMES-INDEX -J310GLO3156I VOLSER(S): NSL204 -J310GLO3123I GLOJIVP1,VAVS,,,NSMS.VSAM.TEST -J310RKTSW01I VAVS 32 00 00:00:00.17 00:00:00.17 00:00:00.00 00:00:00.00RKTSW01I NCATCRE 33 00 00:00:00.07 00:00:00.06 00:00:00.00 00:00:00.01GLO2084I DATA SET ON VOLSER NSL201 SCRATCHED AT ALLOCATION TIME -J310GLO2123I GLOJIVP1,NCATSCR,,SYSUT7,NSMS.GLO.TEST.DATA -J310RKTSW01I NCATSCR 34 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02RKTSW01I DELETE10 35 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02IEF377I GLOJIVP1 NOTCAT2 980

NSMS.GLO.TEST.DATA NOT CATLGD 2GLO2051I JOB SET TO FAIL DUE TO NOT CATLGD 2 ON VOLSER NSL200 -J310GLO2123I GLOJIVP1,NOTCAT2,,SYSUT5,NSMS.GLO.TEST.DATA -J310RKTSW01I NOTCAT2 36 00 00:00:00.08 00:00:00.06 00:00:00.00 00:00:00.02IEF378I GLOJIVP1 NOTCAT2 - JOB FAILED 984

CATALOG DISPOSITION ERRORRKTSW01I GLOJIVP1 JOB TOTALS: 00:00:04.96 00:00:03.82 00:00:00.04 00:00:01.10$HASP395 GLOJIVP1 ENDED

Figure 3. Example of successful GLOJIVP1 results


Chapter 4. Advanced Allocation Management definitionmanagement

After you install and configure Advanced Allocation Management, the next step isto define Advanced Allocation Management processing.

Advanced Allocation Management processing is determined by the contents of thecontrol data set. Definition management is the process of defining where and howAdvanced Allocation Management performs processing using the contents of thecontrol data set.

The control data setThe control data set contains product definitions that determine where and howAdvanced Allocation Management operates.

The Advanced Allocation Management control data set and default members aregenerated by the installation and configuration process. Each member type(OPTIONS, RULEDEFS, VGRPDEFS) contains a specific set of definitions thatdetermine a particular aspect of Advanced Allocation Management processing:v The OPTIONS member contains global definitions and general operation options

(including the subsystem ID that is associated with a specific instance ofAdvanced Allocation Management) that determine how Advanced AllocationManagement functions.

v The RULEDEFS member contains selection criteria and functions. Selection criteriaenable you to specify the items to include or exclude from Advanced AllocationManagement processing. Functions enable you to specify the actions that youwant Advanced Allocation Management to perform using the selection criteria.

v The VGRPDEFS member contains the volume group list that defines a group ofvolumes from which additional volumes can be selected as needed (volumegroup definitions are used in conjunction with the volume addition function thatis available within the rule definition syntax).

Control data set requirements and guidelinesNote these control data set requirements and guidelines.v The control data set must be a partitioned data set with fixed format records

that have a record length of 80 bytes.v The control data set can exist for an active or inactive Advanced Allocation

Management subsystem. (An Advanced Allocation Management subsystem isconsidered active when the Advanced Allocation Management started taskassociated with the subsystem ID is running and the subsystem and theproduct-level intercepts have not been disabled.)

v Multiple control data sets are permitted.v Members can be renamed to suit your needs. All control data set member names

must adhere to standard PDS member name conventions.v Each control data set member requires the first line in the member to be a

comment which contains a string that denotes the member type (for example,"RULE DEFINITION" or VOLUME GROUP LIST"). Including this commentfacilitates the identification of the member type when viewing multiple controldata set members using the Advanced Allocation Management user interface.

31

Modifying control data set membersYou perform definition management when you first implement AdvancedAllocation Management in your environment by specifying the subsystem optionsduring the configuration process and then by specifying the rule and volumegroup definitions. However, you might need to modify the contents of the controldata set as your installation's needs grow and change.

Subsystem options member (OPTIONS)

Initially, you define subsystem options when you customize a specific instance ofAdvanced Allocation Management. Some subsystem options, such as the currentlyactive rule definitions or volume group member, can be modified by authorizedusers by using options that are available on the Tivoli Advanced AllocationManagement Subsystem Settings screen, or by using operator commands.

Note: Once set, subsystem options rarely need to modified unless you are addingor removing an Advanced Allocation Management subsystem.

Rule definitions member (RULEDEFS)

Rule definitions can be modified as needed by using the options that are availableon the Tivoli Advanced Allocation Management Control Member Managementscreen (recommended) or by using the ISPF EDIT function.

Volume group definitions member (VGRPDEFS)

Volume group definitions can be modified as needed by using the options that areavailable on the Tivoli Advanced Allocation Management Control MemberManagement screen (recommended) or by using the ISPF EDIT function.

Activating rule and volume group member definitionsOnce modified, you must activate rule and volume group definitions in order fortheir settings to take effect.

Note: Subsystem options do not need to be activated—their settings take effectwhen the Advanced Allocation Management started task associated with thespecific subsystem options member is started.

To activate the rule or volume group definitions, you issue an Advanced AllocationManagement operator command (ACTIVATE) from a z/OS console. Operatorcommands can be issued whenever the Advanced Allocation Management startedtask is running. This feature enables dynamic modification of selection criteria andactions at any time without requiring a shutdown or quiesce of the product.

Note: Rule definitions (RULEDEFS) and volume group list (VGRPDEFS) membernames are one to eight-byte names because these are names of PDSmembers. The names of these members can be specified as parameters onoperator commands (for example: ACTIVATE RULEDEFS RULESET1 orACTIVATE VGRPDEFS VOLGRP2). The subsystem options member namecannot be specified as parameter on a command.

Implementing multiple instances of Advanced Allocation ManagementAdvanced Allocation Management is designed so that multiple instances can runconcurrently on a single z/OS image.


Implementing multiple instances of Advanced Allocation Management in test andproduction environments is useful when you are first installing the product orwhen you want to reserve one subsystem for testing purposes and another one forproduction purposes.

In these situations, an Advanced Allocation Management control data set can existfor each Advanced Allocation Management subsystem — or one control data setcan be shared among subsystems.

Using separate control data sets for multiple instancesYou can use separate control data sets for multiple instances. This configuration isrecommended for those installations that require users to have separateauthorizations for each Advanced Allocation Management subsystem. For example,you might want some users to be able to work with a specific Advanced AllocationManagement subsystem, but limit their access to other Advanced AllocationManagement subsystems.

Figure 4 shows an example where two separate control data sets exist for twoseparate Advanced Allocation Management subsystems (one control data set persubsystem).


Control Data Set

User initiates the AdvancedAllocation Management

started task

(subsystem optionsmember:"OPTIONS1")

SSID=AOP1


(ALLOCOP2) andSubsystem (AOP2)


Control Data Set


started task


SSID=AOP2

(DD statement points to"OPTIONS2" member)




AOP1

AOP2

Image A

In Figure 4, each control data set is associated with a specific Advanced AllocationManagement subsystem (AOP1 or AOP2) and each control data set contains asubsystem options member, a rule definitions member, and a volume groupdefinitions member for the specific subsystem.

Figure 4. Multiple instances of Advanced Allocation Management (separate control data sets)

Chapter 4. Advanced Allocation Management definition management 33

Using a shared control data set for multiple instancesYou can use a shared control data set for multiple instances. This configuration isrecommended for those installations that do not require users to have separateauthorization for individual Advanced Allocation Management subsystems. Forexample, in those cases where you want all users to be able to work with allAdvanced Allocation Management subsystems in your environment.

Figure 5 shows an example where a single control data sets exists for two separateAdvanced Allocation Management subsystems.

AOP2


Allocation Managementstarted task

Control Data Set

User initiates the Advanced


SSID=AOP1




started task


SSID=AOP2





AOP1

Image A

In Figure 5, one control data set is associated with two Advanced AllocationManagement subsystems (AOP1 and AOP2). The control data set contains asubsystem options member for each Advanced Allocation Management subsystem(the OPTIONS1 member specifies the subsystem options for subsystem AOP1 andthe OPTIONS2 member specifies the subsystem options for subsystem AOP2). Ruledefinitions and a volume group definitions members can be defined for eachsubsystem—or be shared between both subsystems.

Guidelines and recommendations for implementing AdvancedAllocation Management

Refer to these guidelines and recommendations for methods you can use toimplement Advanced Allocation Management in your environment.

Figure 5. Multiple instances of Advanced Allocation Management (shared control data set)


v Initially implement Advanced Allocation Management only for test jobs. Forexample, you might want to create a series of test jobs that you can use tobecome familiar with Advanced Allocation Management features and functions.Use Advanced Allocation Management selection criteria to specify that onlythese jobs should be included in Advanced Allocation Management processing.

v As new RULEDEF DEFINEs are added, the RULEDEF_TEST keyword can beadded and set to ENABLE. This allows you to verify that the selection criteriayou have specified will match the entities (jobs, data sets, and so on) that youintended. After you have successfully tested the rule definitions, you can setRULEDEF_TEST to DISABLE, or remove it entirely, and allow AdvancedAllocation Management to perform processing.

v Start with specific applications that can be easily identified by the first fewcharacters of a jobname. For example, you might have a series of jobs that havejobnames beginning with the characters "ABC." Use the Advanced AllocationManagement selection criteria keyword JOBNAME, in conjunction with theINCLUDE keyword, to specify that only these jobs should be included inAdvanced Allocation Management processing.

v Specify a select set of data set name high-level qualifiers and then gradually addmore selection criteria as needed. For example, you might have a group of datasets that have high-level qualifiers of "SS22" and "SS23. " Use the AdvancedAllocation Management selection criteria keyword DSNAME, in conjunctionwith the INCLUDE keyword, to specify that only these data sets should beincluded in Advanced Allocation Management processing. Additional selectioncriteria can be added as you become more familiar with Advanced AllocationManagement.

Chapter 4. Advanced Allocation Management definition management 35


Chapter 5. Using the Advanced Allocation Management userinterface

Advanced Allocation Management provides an online user interface that enablesyou to easily manage control data set members, view and update subsystemoptions, display subsystem statistics, and review Advanced AllocationManagement event history.

Accessing the Tivoli Advanced Allocation Management Primary OptionMenu

You access the Tivoli Advanced Allocation Management Primary Option Menu byrunning the Advanced Allocation Management dialog CLIST.

To access the Tivoli Advanced Allocation Management Primary Option Menu,complete these steps:1. Run the Advanced Allocation Management dialog CLIST using a TSO

command (for example: TSO GLO).The Tivoli Advanced Allocation Management Primary Option Menu appears.

2. Press Enter to remove the copyright statement.

Tivoli Advanced Allocation Management Primary Option Menu optionsThese options are available from the Tivoli Advanced Allocation ManagementPrimary Option Menu.

Manage Control MembersType 1 to view, edit, rename, delete, or syntax-check control data setmembers.

View/Update OptionsType 2 to view or update active Advanced Allocation Managementsubsystem settings.

Display StatisticsType 3 to display Advanced Allocation Management subsystem statistics(the conditions detected and the actions taken by the product).

View Event HistoryType 4 to review Advanced Allocation Management event history.

About Tivoli Advanced Allocation ManagementType A to view Advanced Allocation Management copyright information.

Exit Tivoli Advanced Allocation ManagementType X (or press PF3) to exit the Advanced Allocation Management userinterface.

Accessing online helpTo access the Advanced Allocation Management online help facility, press PF1.

37

Managing control data set membersFrom the Tivoli Advanced Allocation Management Control Member Managementscreen, you can manage the contents of any Advanced Allocation Managementcontrol data set.

To view and modify Advanced Allocation Management control data set members,type 1 (Manage Control Members) from the Tivoli Advanced AllocationManagement Primary Option Menu. The Tivoli Advanced Allocation ManagementControl Member Management screen appears. For example:

Note: An Advanced Allocation Management subsystem does not need to be activeto view and modify control data sets using the options available on thisscreen.

Specifying a control data setTo use the V (View), E (Edit), R (Rename), D (Delete), or S (Syntax-check)options, you must specify the control data set that contains the member (ormembers) that you want to view, edit, rename, delete, or syntax-check.

Choose one of these methods to specify the control data set:v Type the name of a control data set in the Data set name field.

Note: You must enclose the data set name in single quotes.v Type the four character subsystem ID of an active Advanced Allocation

Management subsystem in the Active Subsystem ID field and press Enter toretrieve the selected subsystem control data set name.

v If multiple Advanced Allocation Management subsystems are active, leave theControl data set and Control member fields blank to display a list of activesubsystem IDs from which you can select a subsystem (and retrieve thecorresponding data set name).

Tivoli Advanced Allocation Management Control Member Management

Option ===>

blank Display list R Rename control memberV View control member D Delete control memberE Edit control member S Syntax-check control member

Enter a control data set name below or specify an active subsystemID to retrieve the control data set name for that subsystem. Leaveboth fields blank to obtain a list of active subsystems.

Control data set:Data set name . . . . 'ABCD.GLO.CONTROL’__________________________Active Subsystem ID . ____ (Select control data set by subsystem)

Control member:Member name . . . . . RULESET1 (If V, E, R, D, S selected)New member name . . . (If E, R selected)

Figure 6. Tivoli Advanced Allocation Management Control Member Management screen


Specifying a control data set by selecting the subsystem IDfrom a list of active subsystems

When multiple Advanced Allocation Management subsystems are active, you candisplay a list of active subsystems from which you can select an active subsystemID (and retrieve the associated control data set name).

To select an Advanced Allocation Management subsystem, complete these steps:v Leave the Data set name and Active Subsystem ID fields on the Tivoli

Advanced Allocation Management Control Member Management screen blankand then press Enter. The Tivoli Advanced Allocation Management SubsystemSelection screen appears. For example:

Note: If only one Advanced Allocation Management subsystem is active andyou do not specify a control data set, or member, in the Data set nameand member name fields and you press Enter, the name of the controldata set that is associated with the currently active Advanced AllocationManagement subsystem appears in the Data set name field.

v To specify a subsystem from the Tivoli Advanced Allocation ManagementSubsystem Selection screen, select one of these options:– To specify a subsystem, type an Advanced Allocation Management subsystem

ID in the Subsystem ID field and then press Enter. Advanced AllocationManagement retrieves the name of the control data set associated with theselected subsystem.

– To select from a list of currently active Advanced Allocation Managementsubsystems, leave the Subsystem ID field blank and press Enter. The TivoliAdvanced Allocation Management Active Subsystems screen appears, listingthe currently active subsystems. For example:

v To select a subsystem, type S in the field to the left of the active subsystem thatyou want select and then press Enter. Advanced Allocation Managementretrieves the name of the control data set associated with the selected subsystem.

Selecting control data set membersAfter you specify a control data set, there are two methods you can use to workwith specific control data set members.

Choose either of these methods to select control data set members:v Type the name of the specific member you want to work with in the Member

name field.

Tivoli Advanced Allocation Management Subsystem Selection

Specify the ID of an active subsystem:

Subsystem ID . . . (blank for a list of active subsystems)

Figure 7. Tivoli Advanced Allocation Management Subsystem Selection screen

Tivoli Advanced Allocation Management Active Subsystems

Select one of the active subsystems below.__ AOP1___AOPT

Figure 8. Tivoli Advanced Allocation Management Active Subsystems screen

Chapter 5. Using the Advanced Allocation Management user interface 39

v Leave the Member name field blank and press Enter to display a list ofmembers from which you can perform view, edit, rename, delete, orsyntax-check operations.

Specifying a specific control data set memberSpecify a particular member of the control data set to view, edit, or syntax-check,specify a member name.

To specify a specific control data set member, do the following:

In the Member name field, type the name of the control data set member that youwant to view, edit, rename, delete, or syntax-check.

Note: If you do not specify a member name and you specify one of the theseoptions: V, E, R, D, or S, you will be prompted to specify a member name.

Displaying a list of control data set membersTo display a list of members from which you can perform view, edit, rename,delete, or syntax-check operations, press Enter (do not specify a member name).

To display a list of members, complete these steps:v Press Enter (do not specify a member name). A list of members from the selected

control data set appear. For example:

v Type one of these options: V (View), E (Edit), R (Rename), D (Delete), or S(Syntax-check) in the field to the left of a member to perform the actionassociated with the particular option.

Control member management optionsAfter you select a control data set and member, or after you display a list ofcontrol data set members, you can select from these options.

V View a control data set member. When you select this option, the ISPFVIEW function is invoked to allow you to view the selected control dataset member.

E Edit a control data set member. When you select this option, the ISPF EDITfunction is invoked to allow you to modify the selected member.

Tip: You can also use the Edit option to create a new member.

MEMBER LIST ABCD.GLO.CONTROL Row 00001 of 00014Name Prompt Size Created Changed ID

. AOPTOPTS 5 2008/08/14 2008/08/14 21:00:28 PDUSER

. AOP1OPTS 5 2008/08/14 2008/08/14 21:00:33 PDUSER

. AOP2OPTS 5 2008/08/14 2008/08/14 21:00:36 PDUSER

. ERRORS 160 2008/07/15 2008/07/15 02:35:23 PDUSER

. JJHDEF 138 2008/08/24 2008/08/24 19:34:02 PDUSER

. JJHOPTS 5 2008/08/22 2008/08/22 16:06:34 PDUSER

. JJHSET01 8 2008/08/22 2008/08/22 16:06:16 PDUSER

. RULESET1 41 2008/04/04 2008/08/24 18:44:39 PDUSER

. RULESET3 43 2008/08/19 2008/09/02 16:05:46 PDUSER

. ABCDGRP1 4 2008/07/18 2008/07/18 16:17:50 PDUSER

. SAMPLE 160 2008/05/01 2008/08/26 14:35:40 PDUSER

. SAMPLE2 89 2008/08/13 2008/08/13 00:10:00 PDUSER

. STRTCMDS 3 2008/04/04 2008/07/18 16:27:42 PDUSER

. ZTRTCMDS 4 2008/04/10 2008/04/10 10:05:18 PDUSER**End**

Figure 9. Displaying a list of control data set members


R Rename a control data set member. When you select this option, theMember Rename dialog is displayed to enable you to rename the selectedmember. The current member name appears in the Old Name field. Torename the member, type the new (1 to 8 character) member name in theNew member name field and press Enter. The selected member isrenamed.

Note: To cancel the rename operation, press PF3.

D Delete a control data set member. When you select this option, you areprompted to confirm the deletion of the member. After you confirm thedeletion, the member is deleted when you press Enter.

S Syntax-check a control data set member (RULEDEFS or VGRPDEFSmembers only). When you select this option, Advanced AllocationManagement checks the selected control data set member for syntax errors.The ISPF BROWSE function is invoked to allow you to view the resultsreturned by syntax check routine. If no errors are detected, the message NOSYNTAX ERRORS FOUND appears at the end of the data listing.

Notes:

1. The results of the syntax check are listed in a temporary filewhose name is the concatenation of the user ID, the startedtask, and a final qualifier of "SYNTAX."

2. You cannot syntax-check an OPTIONS member.

When you are finished working with the selected member, press PF3 to exit andreturn to the Tivoli Advanced Allocation Management Control MemberManagement screen.

Creating a new control data set member using the Edit optionThis information describes how to use the Edit option create a new control data setmember.

To create a new control data set member, complete these steps:1. From the Tivoli Advanced Allocation Management Control Member

Management screen, type the name of the new control data set member in theNew member name field.

2. Type E in the Option line and press Enter. The new member is created andISPF EDIT is invoked to enable you to edit the new member.

Note: If a member with the same name already exists, you will be prompted toprovide a different (unique) member name.

Viewing and updating subsystem optionsThe Tivoli Advanced Allocation Management Subsystem Settings screen enablesyou to view and modify (if authorized) selected subsystem settings.

Notes:

v An Advanced Allocation Management subsystem must be active toaccess the Tivoli Advanced Allocation Management Subsystem Settingsscreen.

v Only authorized users can update modifiable settings.


To view and modify (if authorized) selected subsystem settings, complete thesesteps:1. To view or update subsystem options, type 2 (View/Update Options) from the

Tivoli Advanced Allocation Management Primary Option Menu. The TivoliAdvanced Allocation Management Subsystem Settings screen appears. Forexample:

Tivoli Advanced Allocation Management Subsystem Settings

Fixed Subsystem Settings:Subsystem ID. . . . . . . AOP1Started Task Name . . . . ALLOCP1Control Data Set Name . . ABCD.GLO.CONTROL

Modifiable Subsystem Settings:Subsystem Status. . . . . .E (Enable or Disable)Active Rule Definition. . .RULESET1_(name of member to be activated)

("*" to re-activate same member)Active VGRP Definition. . .________ (name of member to be activated)

("*" to re-activate same member)

Status Information:Rule Definition last activated . . . 07/15/2003 13:06:50VGRP Definition last activated . . . 07/15/2003 13:07:12

Modifiable Product-level Settings:Intercepts Status . . . . E (Enable or Disable) (** see note)

**- intercepts apply to ALL active Advanced Allocation Management subsystems

2. When you are finished, press PF3 to exit the Tivoli Advanced AllocationManagement Subsystem Settings screen.

Fixed Subsystem SettingsFixed Subsystem Settings fields are display-only.

Subsystem IDThe active Advanced Allocation Management subsystem ID.

Started Task NameThe name of the Advanced Allocation Management started task that isassociated with the subsystem ID.

Control Data Set NameThe name of the control data set for the active Advanced AllocationManagement subsystem.

Modifiable Subsystem SettingsModifiable Subsystem Settings can be modified by authorized users.

Subsystem statusThe current subsystem status: enabled (E) or disabled (D). To change thestatus, type E (Enable the subsystem so that Advanced AllocationManagement processing occurs) or D (Disable the subsystem so that noAdvanced Allocation Management processing occurs).

Active rule definitionThe name of the currently active rule definitions member of the controldata set displayed in the Control Data Set Name field. To activate a ruledefinitions member, type the name of the rule definition member that youwant to activate in this field and press Enter. To reactivate the samemember, type an asterisk (*) in this field.


Note: Rule definitions must be activated for their definitions to take effect.

Active VGRP definitionThe name of the currently active volume group definitions member of thecontrol data set displayed in the Control Data Set Name field. To activatea volume group definitions member, type the name of the volume groupdefinition member that you want to activate in this field and press Enter.To reactivate the same member, type an asterisk (*) in this field.

Note: Volume group definitions must be activated for their definitions totake effect.

Status InformationStatus Information fields are display only.

Rule definition last activatedThe date in the format MM/DD/YYYY (month, day, and year) and time inthe format HH:MM:SS (hours, minutes, and seconds) that the ruledefinition member was last activated.

VGRP definition last activatedThe date in the format MM/DD/YYYY (month, day, and year) and time inthe format HH:MM:SS (hours, minutes, and seconds) that the volumegroup definition member was last activated.

Modifiable Product-Level SettingsModifiable Product-level Settings fields can only be modified by authorizedusers.

Intercepts Status:The current intercept status: enabled (E) or disabled (D). To change thestatus, type E (Enable product-level intercepts) or D (Disable product-levelintercepts) as follows:v Enabling the intercepts allows Advanced Allocation Management to

perform processing.v Disabling the intercepts allows the Advanced Allocation Management

started task to remain active without performing any processing.Disabling the product-level intercepts can be useful in those situationswhen you do not want to shut down Advanced Allocation Managementcompletely (for example, for debugging purposes).

Note: This option enables (or disables) product-level intercepts for allactive Advanced Allocation Management subsystems. Enabling ordisabling the product-level intercepts does not start or stop theAdvanced Allocation Management started task.

Displaying Advanced Allocation Management recovery statisticsThe Tivoli Advanced Allocation Management Recovery Statistics screen showstatistics for the currently selected active Advanced Allocation Managementsubsystem. The information on this panel is updated each time you press Enter.

Note: An Advanced Allocation Management subsystem must be active to accessthe Tivoli Advanced Allocation Management Recovery Statistics screen.


To view Advanced Allocation Management recovery statistics, complete thesesteps:1. Type 3 (Display Statistics) from the Tivoli Advanced Allocation Management

Primary Option Menu. The Tivoli Advanced Allocation Management RecoveryStatistics screen appears.For example:

Tivoli Advanced Allocation Management Recovery Statistics

Statistics recording started at 11/24/2009 07:01:45 Subsystem ID AOP1

Initial volume primary space allocation failures recovered........ 3Subsequent volume primary space allocation failures recovered..... 14Undefined secondary allocation space abends avoided (D37)......... 6Unavailable secondary allocation space abends avoided (B37/E37)... 0Unavailable secondary allocation space abends recovered (B37/E37) 450Insufficient volumes defined abends recovered (B37/E37)........... 225Possible insufficient space abends avoided (B37/E37).............. 0Space release option added to primary or secondary allocation..... 0Insufficient PDS directory space for member save errors recovered. 0NOT CATLGD 2 errors processed..................................... 0Data sets initialized..............................................0

******************************************************************************* ** Total number of abends and errors either avoided or recovered 698 ** Number of tracks recovered from adding space release 0 ** Number of Allocation parms set by Enhanced Allocation Management 0 ** Non-SMS Volume(s) selected by Advanced Volume Selection 0 ** Number of data set allocations failed by TERM_ALLOC 0 ** Total data sets processed by RULEDEF_TEST mode 0 ** *******************************************************************************

2. When you are finished viewing the statistics, press PF3 to exit the TivoliAdvanced Allocation Management Recovery Statistics screen.

Advanced Allocation Management Recovery StatisticsThese fields display the statistics collected by Advanced Allocation Management.

Statistics recording started atThe date in the format MM:DD:YY (month, day, and year) and time in theformat HH:MM:SS (hours, minutes, and seconds) Advanced AllocationManagement began recording statistics for the selected subsystem.

Initial volume primary space allocation failures recoveredThe number of times primary space was reduced by the PRIM_REDUCEfunction.

Subsequent volume primary space allocation failures recoveredThe number of times Advanced Allocation Management reduced theprimary allocation on a volume which was added.

Undefined secondary allocation space abends avoided (D37)The number of times the SEC_ALLOC function added a secondaryallocation during D37 processing when no secondary space value wasspecified (or, it was specified as zero).

Unavailable secondary allocation space abends avoided (B37/E37)The number of times the SEC_BEST function decreased the secondaryallocation to fit in the largest single extent on the volume duringend-of-volume processing.


||||||||||||||||||||||||||

Unavailable secondary allocation space abends recovered (B37/E37)The number of times the SEC_REDUCE function recovered from secondaryallocation space failures by reducing the allocation amount to a value thatwas consistent with the free space on the volume.

Insufficient volumes defined abends recovered (B37/E37)The number of times that the VOL_ADD function dynamically addedvolumes during end-of volume processing.

Possible insufficient space abends avoided (B37/E37)The number of times the SEC_INC function increased the size of thesecondary allocation as data set extends occurred after a particular extent,and at a particular volume number.

Space release option added to primary or secondary allocationThe number of times Advanced Allocation Management added theSPACE_RELEASE option to an allocation.

Insufficient PDS directory space for member save errors recoveredThe total number of PDS directory space errors recovered as a result of theAdvanced Allocation Management PDS_DIR_INC function.

NOT CATLGD 2 errors processedDisplays the total number of NOT CATLGD 2 related errors processed byAdvanced Allocation Management since the started task was initialized.

Data sets initializedDisplays the number of data sets that have been initialized by AdvancedAllocation Management.

Total number of abends and errors either avoided or recoveredThe total number of abends and errors that were either avoided orrecovered by Advanced Allocation Management.

Number of tracks recovered from adding space releaseThe total number of tracks that were freed as a result of the AdvancedAllocation Management SPACE_RELEASE function.

Number of Allocation parms set by Enhanced Allocation ManagementThe number of data set parameters that were added, changed, or deletedby Enhanced Allocation Management.

Non-SMS Volume(s) selected by Advanced Volume SelectionThe number of non-SMS data sets for which volumes were selected atallocation time by Advanced Volume Selection.

Number of data set allocations failed by TERM_ALLOCThe number of data set allocations that were forced to fail as a result of theTERM_ALLOC function.

Total data sets processed by RULEDEF_TEST modeThe number of data sets that went through primary or secondaryallocation and matched a RULEDEF with RULEDEF_TEST set to ENABLE.

Viewing event historyThe Advanced Allocation Management event recording and reporting facilityenables you to create reports online or by using a batch reporting utility. Theoptions on the Tivoli Advanced Allocation Management View Event History screenenable you to customize and generate Advanced Allocation Management eventhistory reports.


Note: Advanced Allocation Management will not record event data unless youspecifically configure it to do so.

To create reports online, complete these steps:1. Type 4 (View Event History) from the Tivoli Advanced Allocation Management

Primary Option Menu. The Tivoli Advanced Allocation Management ViewEvent History screen appears.For example:

Tivoli Advanced Allocation Management View Event History

Input Options:SMF Source File (**).SMF Record ID . . . .Filter Set Criteria .

Enter "/" to select optionSpecify additional SMF source filesSpecify additional filter set criteria

Report Options:Sort-By Field . . . .Detail Report . . . . (Basic, All, or No)Summary Report. . . . (Yes or No)Format. . . . . . . . (Report or List)

Output Options:Listing Data Set (**)Output Mode . . . . . (View or Browse)

**- data set names must be fully qualified, without quotes

2. When you are finished specifying input, report, and output options, press PF3to exit the Tivoli Advanced Allocation Management View Event History screen.

Input OptionsSpecify these input options.

SMF Source File(Required.) Type the name of the SMF data set to be searched forAdvanced Allocation Management event records.

Note: The SMF data set you specify must be a non-VSAM data set.

SMF Record ID(Required.) The specific SMF record type that has been designated for useby Advanced Allocation Management. This is the three character numericvalue specified by SMF_RECORD_ID in the Advanced AllocationManagement control data set OPTIONS member generated during theinstallation and configuration process.

Filter Set CriteriaSpecify a filter set criteria.

Specify additional SMF source filesType a slash (/) to display the Tivoli Advanced Allocation ManagementSMF Source Files screen and specify an additional nine SMF source files.

Specify additional filter set criteriaType a slash (/) to display the Tivoli Advanced Allocation ManagementFilter Set Criteria screen and specify an additional nine filter set criteria.


Specifying additional SMF source filesFrom the Tivoli Advanced Allocation Management SMF Source Files screen youcan specify up to nine additional SMF source files.

To specify additional SMF source files, complete these steps:1. Type a slash (/) in the Specify additional SMF source files field. The Tivoli

Advanced Allocation Management SMF Source Files screen appears.For example:

Tivoli Advanced Allocation Management SMF Source Files

Specify 1 or more SMF Source Files below:

==>==>==>==>==>==>==>==>==>==>

Press ENTER to process or F3 to cancel.

Note: The SMF data sets you specify must be non-VSAM data sets.2. Specify up to nine additional SMF source files.3. Press Enter to process the additional files or press PF3 to cancel.

Specifying additional filter set criteriaFrom the Filter Set Criteria screen, you can specify up to nine additional filter setcriteria. If you need to specify more than ten filter criteria, use the batch reportingutility.

To specify additional filter set criteria, complete these steps:1. Type a slash (/) in the Specify additional filter set criteria field. The Tivoli

Advanced Allocation Management Filter Set Criteria screen appears.For example:

Tivoli Advanced Allocation Management Filter Set Criteria

Specify 1 or more Filter Set Criteria below:

==>==>==>==>==>==>==>==>==>==>

Press ENTER to process or F3 to cancel.

2. Specify up to nine additional filter set criteria.3. Press Enter to process the additional criteria or press PF3 to cancel.


Report OptionsThe View Even History report options (Detail Report, Summary Report, andFormat) are designed to work in combination with each other to produce a desiredoutput. These report options are available.

Sort-By Field(Optional) Specify the field that should be used to sort the report.

Note: If you do not provide a sort field, the records will be reported in theorder in which they are read.

Detail ReportDetail records provide a detailed description of each entity that encountersan event that is recorded.

Specify one of these options:v Y — (Default) Include detail records in the report.v N — Do not include detail records in the report.v A — (ALL) Generate an expanded report with additional values.v B — (BASIC) Include detail records in the report. (Specifying this option

is the same as specifying Y.)

Note: If Format=R (Report) is also specified, the detail records areformatted. If Format=L (List) is also specified, the detail records arecomposed of raw data, in a format suitable for input into anotherreport-writing utility.

Summary ReportSpecify whether or not a summary of the records processed should begenerated. Type Y (default) to generate a summary of the recordsprocessed; otherwise type N (do not generate a summary of the recordsprocessed).

Note: Because the summary report is always formatted, SummaryReport=Y is valid only when Format=R (Report) is also specified.

FormatSpecify the type of output to generate. Type R (Report) to generate aformatted report, or type L (List) to generate raw data records in a formatsuitable for input into other report-writing utilities.

Output OptionsSpecify these output options.

Listing Data SetSpecify the name of the listing data set as follows:v To retain the output specify a data set name in this field. If the data set

you specify does not exist, it will be created. If the data set you specifyexists, the contents will be overwritten.

v If you do not specify a data set name, a temporary data set will beallocated which will be deleted after you are finished browsing orviewing the output.

Output ModeSpecify the ISPF facility that should be used to display the resulting report.


v Type V (View) to specify ISPF VIEW which allows for greatermanipulation of displayed data (such as record sorting and various linemanipulations), but is limited by the size of the report that it candisplay.

v Or, type B (Browse) to specify ISPF BROWSE which is unlimited in thesize of the report it can display, but is much more limited in the way thedata can be manipulated.



Chapter 6. Using rule definitions to define processing

The rule definitions member of the control data set enables you to define howAdvanced Allocation Management performs processing in your environment.

How rule definitions workAdvanced Allocation Management uses rule definitions to determine whether ornot it should take action in the event that an x37 type abend, or other out-of-spacecondition, is about to occur.

Within the rule definitions member, you specify the items that you want AdvancedAllocation Management to include or exclude from processing, and how AdvancedAllocation Management should perform processing when it encounters the selecteditems.

Once defined, you must activate the rule definitions for their settings to take effect.To activate the rule definitions, you can use the Active Rule Definition optionavailable on the Tivoli Advanced Allocation Management Subsystem Settingsscreen, or you can use an operator command that can be issued whenever theAdvanced Allocation Management started task is running.

Rule definition syntaxRule definition syntax consists of keywords and keyword values grouped intoselection criteria (items to include or exclude from processing) and functions(actions that you want Advanced Allocation Management to perform using theselection criteria) by the DEFAULTS, INCLUDE, and EXCLUDE main keywords.

Syntax precedenceAdvanced Allocation Management processes rule definition syntax in top-downorder. Therefore, once Advanced Allocation Management finds an item thatmatches a selection criteria, it exits and does not process the remaining statementsin the rule definition member.

Consider the rule definition syntax:* RULE DEFINITIONSDEFAULTS PRIM_REDUCE=ENABLE * Default settingsPRIM_REDUCE_LIM=50PRIM_REDUCE_INC=10*EXCLUDE JOBNAME=ABCJOB2 * Item to exclude from processingINCLUDE JOBNAME=ABCJOB* * Item to include in processing

Advanced Allocation Management will process the syntax as follows:v The DEFAULTS main keyword specifies the default processing for Advanced

Allocation Management. In the example, the PRIM_REDUCE function has beenspecified as the default function. This means that Advanced AllocationManagement will perform the PRIM_REDUCE function for any items that it hasbeen instructed to include in its processing.

v The EXCLUDE main keyword specifies the items that Advanced AllocationManagement should exclude from its processing. In the example, the EXCLUDEstatement specifies that jobs that have a job name of ABCJOB2 should not be

51

included in Advanced Allocation Management processing. Therefore, ifAdvanced Allocation Management encounters a job with a job name ofABCJOB2, it will exit at this point and not perform any processing.

v The INCLUDE main keyword specifies the items that Advanced AllocationManagement should include in its processing. In the example, the INCLUDEstatement specifies that any job with a job name that starts with the characters"ABCJOB" should be included in Advanced Allocation Management processing.Therefore, if Advanced Allocation Management does not encounter a job with ajob name of ABCJOB2, but instead encounters a job with a job name ofABCJOB1 or ABCJOBA, and so on — it will perform processing.

Rule definition evaluationRule definitions are evaluated separately at each of these points in allocationprocessing, primarily to provide for volume-based selection criteria.1. At the initial allocation of a data set on the first volume. This allows for the fact

that volume-based selection criteria cannot be performed at this point inallocation because the volume is not known unless explicitly defined.

2. At the first secondary allocation of a data set at which time volume-basedinformation is known.

3. At the first allocation on a new volume to account for volume-based selectioncriteria for the new volume.

Creating and modifying rule definitionsWhen creating a rule definitions member, you must first determine how you wantAdvanced Allocation Management to perform processing (that is, the functions andselection criteria that you want to use). For example, you might want AdvancedAllocation Management to perform processing only for jobs that reference certaindata, or that have specific job name characteristics.

Note: It is recommended that you start by implementing simple rule definitionsand then gradually add more selection criteria and functions as you needthem.

To create a rule definition member for your installation, complete these steps:1. Copy the sample rule definition member (RULEDEFS) provided in the

Advanced Allocation Management control data set generated during theinstallation and configuration process.

2. Modify the new (copied) member for your installation. To modify the member,use the options that are available on the Tivoli Advanced AllocationManagement Control Member Management screen (recommended), or use theISPF EDIT function to modify the member directly.

3. Save the member you modified using a valid one to eight-character membername. (All control data set member names must adhere to standard PDSmember name conventions.)

Rule definition member requirementsEach control data set member requires the first line in the member to be acomment which contains a string that denotes the member type.

The first line of the rule definition member must be a comment which contains thetext "RULE DEFINITIONS"


For example:* RULE DEFINITIONS

This comment identifies the member as a rule definitions member.

Note: If you have multiple rule definition members, each member must containthis same comment as the first line in the member.

Determining the functions to include in rule definitionsUse these tables to help you determine the functions to include in your ruledefinitions.

Table 6 shows some common issues, the corresponding abends, and the functionsto use to avoid the abends.

Table 6. Selecting a function based on issue and abend type

Type of issue and abend Function

During end-of-volume processing, no more space wasavailable on the volume, the data set reached 16 extents, orthe VTOC was full. (IEC030I, B37 abend.)

Increase, reduce, or adjustsecondary to best fit;dynamically add volumes

A data set opened for output used all the primary spaceand no secondary space was requested. IEC031I, D37abend.

Add secondary allocation

A data set opened for output used all space available onthe current volume and no more volumes were available.(IEC032I, E37 abend.)

Dynamically add volumes,reduce secondary or adjust it tobest fit

In a DD statement, the SPACE parameter requested moretracks than were available on the requested direct accessvolume. (IEF257I, JOB FAILED - JCL ERROR.)

Reduce primary

Ineffective use of existing storage resources; poor planning;arbitrary use of existing JCL.

Adjust secondary to best fit,release unused space

An attempt is made to store directory information for anew member in a PDS (using MVS's STOW service) andall of the directory blocks are full.

Dynamically increase thedirectory space within thepartitioned data set

An attempt is made to catalog a new data set, but the dataset is currently cataloged on another volume.

Detect the attempt to catalogthe duplicate data set andperform processing to preventthe potential use of the wrongdata set.

Control initial allocation of non-SMS volumes Use the various AdvancedVolume Selection keywords toselect volumes fromuser-defined pools

Modify data set attributes to enforce standards Use the various SET_ functionsof Enhanced AllocationManagement

Terminate allocation upon matching selection criteria Use the TERM_ALLOCfunction after matching onvarious selection criteria

Tune volume selection Specify volume selectionalgorithm for both initial andsubsequent volume allocation

Chapter 6. Using rule definitions to define processing 53

Table 7 shows Advanced Allocation Management abend recovery functions andtheir corresponding keywords.

Table 7. x37 Abend recovery functions - keyword reference

Function Keywords

Controlled reduction of primary space to satisfyallocation.

PRIM_REDUCE PRIM_REDUCE_LIMPRIM_REDUCE_INC

Dynamically add volumes at end-of-volumeprocessing.

VOL_ADD VOL_ADD_LIMVOL_ADD_PROMPTVOL_ADD_SGRP VOL_ADD_UNITVOL_ADD_VGRP VOL_ADD_VSERVOL_ADD_MOUNT_USAGE

Recover from secondary allocation space failures byreducing the allocation amount to a value consistentwith the current free space on the volume.

SEC_REDUCE SEC_REDUCE_INCSEC_REDUCE_LIM

Detect and dynamically recover from DIRECTORYFULL conditions.

PDS_DIR_INC

Table 8 shows the Advanced Allocation Management abend prevention andavoidance functions and their corresponding keywords.

Note: Using abend prevention functions can result in improved processing timebecause, in general, abend prevention functions incur less processingoverhead.

Table 8. x37 Abend prevention and avoidance functions - keyword reference

Function Keywords

Automatically add a secondary allocation ifnone is specified.

SEC_ALLOC SEC_ALLOC_AMT

Reduce secondary allocation to largestavailable free extent.

SEC_BEST SEC_BEST_LIM

Increase the size of the secondary allocationas data set extends occur at a particularextent and at a particular volume number.

SEC_INC SEC_INC_AMT SEC_INC_VOLNOSEC_INC_XTNT

Recover unused disk space by automaticallyreleasing allocated, unused data set space atdata set close.

SPACE_RELEASE

Detect the attempt to catalog a newly createddata set that is already cataloged on anothervolume.

NOTCAT2 NOTCAT2_CHECKNOTCAT2_DYNAL NOTCAT2_QUALIFIERNOTCAT2_QUALIFIER _POSITIONNOTCAT2_SUFFIX

Initialize a newly allocated, but not opened,non-VSAM data set by performing anOPEN/CLOSE sequence on it during steptermination.

DATASET_INIT

Table 9 on page 55 shows Advanced Allocation Management allocate managementfunctions and their corresponding keywords.


||

||

|||

|||

|||

||

|||

|

|||

||||

||||

|

|

Table 9. Allocate management functions and corresponding keywords

Function Corresponding keywords

Advanced volume selection AVS, AVS_VGRP, AVS_UNIT, AVS_VSER,AVS_MOUNT_USAGE, AVS_ALGORITHM,and AVS_VGRP_SEARCH

Enhanced allocation management Enhanced Allocation Management functionkeywords (these keywords begin with theprefix "SET_")

Standards enforcement TERM_ALLOC

Establishing rule definition default processingThe DEFAULTS main keyword establishes the default settings for the AdvancedAllocation Management functions.

The settings you specify using the DEFAULT keyword remain active until youoverride them with a DISABLE specification using a subsequent INCLUDE mainkeyword. For example, if you set PRIM_REDUCE=ENABLE using the DEFAULTSmain keyword, the PRIM_REDUCE function will remain enabled until you specifyPRIM_REDUCE=DISABLE using an INCLUDE main keyword.

Note: The first keyword in the rule definitions member must be the DEFAULTSkeyword.

Including or excluding items from processingThe INCLUDE main keyword specifies the items to be selected for processing andthe functions to invoke for the selected items.

The EXCLUDE main keyword specifies the items to be excluded from AdvancedAllocation Management processing.

Note: EXCLUDE keywords must precede INCLUDE keywords because AdvancedAllocation Management processes rule definitions in top-down order.

Specifying multiple functions or selection criteriaThis information provides examples of how to specify multiple functions orselection criteria.

Example: Specifying multiple selection criteria

When you include multiple functions or selection criteria, you must specify eachitem you want to include in Advanced Allocation Management processing on aseparate INCLUDE statement. For example:INCLUDE DSNAME=DISK*INCLUDE DSNAME=DSKABC*INCLUDE DSNAME=WORK*INCLUDE DSNAME=WRKABC*INCLUDE DSNAME=PABC.CDEF.*

In the example, Advanced Allocation Management will process all of the specifieddata sets.


Example: Specifying multiple data sets with additional selectioncriteria

To specify multiple data sets with additional selection criteria, you could specifythe selection criteria on each INCLUDE statement. For example:INCLUDE USER=LT*

DSNAME=DISK*TEMPDS=NO

INCLUDE USER=LT*DSNAME=DSKABC*TEMPDS=NO

INCLUDE USER=LT*DSNAME=WORK*TEMPDS=NO

INCLUDE USER=LT*DSNAME=WRKABC*TEMPDS=NO

INCLUDE USER=LT*DSNAME=PABC.CDEF.*TEMPDS=NO

In the example, Advanced Allocation Management will process the specified datasets where the user ID assigned to the job name begins with "LT" and the data setis not a temporary data set.

Example: Specifying multiple selection criteria on one INCLUDEstatement

If you do not specify each data set name on a separate INCLUDE statement, onlythe last instance of a keyword will be processed. For example:INCLUDE USER=LT*

DSNAME=DISK*DSNAME=DSKABC*DSNAME=WORK*DSNAME=WRKABC*DSNAME=PABC.CDEF.*TEMPDS=NO

In the example, data sets that match the DSNAME PABC.CDEF.* selection criteriawill be the only data sets that are processed (provided the user ID assigned to thejob name begins with "LT" and the data sets are not a temporary data sets). Theother DSNAME specifications (DSNAME=DISK*, DSNAME=DSKABC*,DSNAME=WORK*, DSNAME=WRKABC*) will be ignored.

Activating rule definitionsAfter you modify the rule definitions, you must activate the definitions in order forthe settings to take effect.

There are two ways to activate the rule definitions: you can use the Active RuleDefinition option available on the Tivoli Advanced Allocation ManagementSubsystem Settings screen, or you can issue the ACTIVATE operator commandfrom the operator console. The ACTIVATE command causes the contents of thespecified member to become the active set of definitions Advanced AllocationManagement uses during processing.

Issue the ACTIVATE operator command using the format:MODIFY stcname,ACTIVATE RULEDEFS member


||

Where stcname is the name of the started task and member is the name of the ruledefinitions member.

Note: Specifying a member name on the ACTIVATE command is optional. If youdo not specify a member name, the member name RULEDEFS is used.

This example shows the result of a successful activation of a rule definitionmember as it appears in the JES SYSMSG output:GLO4199I 1 * RULE DEFINITIONSGLO4199I 2 DEFAULTS PRIM_REDUCE=ENABLEGLO4199I 3 PRIM_REDUCE_LIM=50GLO4199I 4 PRIM_REDUCE_INC=10GLO4199I 5GLO4199I 6 INCLUDE JOBNAME=ABCJOB2GLO4199I 7 INCLUDE JOBNAME=ABCJOB3GLO4199I 8 PRIM_REDUCE_INC=05GLO4199I 9 INCLUDE JOBNAME=ABCJOB1GLO4105I RULE DEFINITIONS SUCCESSFULLY ACTIVATED -AOPT

Note: The message RULE DEFINITIONS SUCCESSFULLY ACTIVATED appears when therule definitions have been successfully activated. If an error occurs duringthe activation process, review the messages provided in the JES SYSMSGoutput to help determine the cause of the error.

Displaying active rule definitionsThe DISPLAY command displays a message on the operator console that providesinformation about the active set of rule definitions, including the member namefrom which they were activated, as well as the date and time of activation.

To display the currently active rule definitions, issue the DISPLAY command fromthe operator console using the format:

MODIFY stcname,DISPLAY RULEDEFSWhere stcname is the name of the started task.

Note: A rule definitions member can only be displayed if it has been activated. Ifthe member has not been activated, a message notifies you that the memberhas not been activated.

Recommendations and guidelinesAs you create and modify rule definitions, note these guidelines.v Advanced Allocation Management will not perform any processing unless you

specify at least one INCLUDE keyword in the rule definitions.v In general, all EXCLUDE statements should be placed before any INCLUDE

statements. For example, to always exclude SYS1.* data sets from processing,placing the EXCLUDE statements prior to all of the INCLUDE statements willprevent Advanced Allocation Management from processing a SYS1.* data setwhen it is accessed by something for which there is an INCLUDE statement (forexample: PGM=IKJ*).

v In general, INCLUDE statements should be ordered from most specific to leastspecific. For example, consider this series of statements:DEFAULTS VOL_ADD=ENABLEINCLUDE JOBNAME=HSMPDO*INCLUDE DDNAME=SORTWK*VOL_ADD=DISABLE


Because the INCLUDE JOBNAME=HSMPDO* statement appears before theINCLUDE DDNAME=SORTWK* statement, it is possible that AdvancedAllocation Management could process the VOL_ADD statement for a SORTWK*DD if it is written to by a job that has a JOBNAME where the first six charactersof the job are "HSMPDO." This situation can occur because there are potentiallymany ddnames for jobs beginning with HSMPDO* (less specific).To correct this situation, place the INCLUDE for SORTWK* (more specific)before the INCLUDE for HSMPDO* (less specific) to ensure that all processingfor any sortwork DD has VOL_ADD=DISABLE applied to it regardless of thejobname.

Function and rule definition examplesRefer to these examples to help you create rule definitions for your installation.

Advanced Volume Selection (AVS)Advanced Volume Selection enables Advanced Allocation Management to selectthe volumes for a non-SMS managed data set at initial allocation time.

At initial allocation time, the AVS function enables you to select the volumes for anon-SMS managed data set.

ExampleINCLUDE JOBNAME=JJHTEST01AVS=ENABLEAVS_VGRP=GROUP01AVS_MOUNT_USAGE=STORAGE

In the example, when an AVS is performed for a non-SMS-managed data set forjob JJHTEST01, the volumes that Advanced Allocation Management will considerwill be all of the volumes with a mount usage attribute of STORAGE in thevolume group named GROUP01.

Usage and processing considerations

Note these VSAM considerations:v AVS is performed at the component level for VSAM data sets using the specified

algorithm. For the BESTFIT, FIRST and PERFORMANCE algorithms the size ofthe extent to locate is determined as follows:– With the space parameters defined at the CLUSTER level, the primary

allocation quantity is used for both the data and index components to searchfor space.

– With the space parameters defined separately at the DATA and INDEX levels,each component's respective primary quantity is used to search for space.

v When the cluster definition contains volume serial numbers, AVS will overlayany user-specified values and either truncate or extend the volume list asnecessary.

v If no volumes are able to be located using the requested AVS algorithm, thevolume list will be emptied and the cluster definition will fail.

Continue RULEDEF processing (CONTINUE)The CONTINUE function provides the ability to direct Advanced AllocationManagement to perform any applicable actions for a matched rule definition andthen continue to look for additional matching rule definitions.


ExampleRULE DEFINITIONS

DEFAULTS*INCLUDE

UNIT_NAME=VIOSET_UNIT_NAME=SYSDA

INCLUDEUNIT_NAME=VIOSET_UNIT_NAME=SYSDACONTINUE=ENABLE

INCLUDEPROGRAM=ADRDSSUPRIM_REDUCE=(DISABLE,DISABLE)

Note the following in the example:v If the first rule definition appears near the top of the RULEDEF member, when a

request for VIO is encountered, it will match the rule definition and change theunitname to SYSDA and stop processing any subsequent rule definitions. In thiscase, you might not want to stop processing at this point because this is a globalchange and more specific changes might follow this definition.

v CONTINUE=ENABLE directs Advanced Allocation Management to make thechange when unitname=VIO is specified, but then to continue checking andacting on other matching rule definitions.

v If you code a DFDSS step (ADRDSSU) and SYSPRINT is being directed to VIO,Advanced Allocation Management will change that specification to SYSDA, butwill then also disable PRIM_REDUCE for any and all allocations within this jobstep.

Example: Accumulating RULEDEF informationINCLUDE DDNAME=SYSUT1

PRIM_REDUCE=ENABLEMSG_LEVEL=RULEDEFCONTINUE=ENABLE

INCLUDE JOBNAME=JJHTEST1SEC_ALLOC=ENABLEMSG_LEVEL=EXCEPTIONS

The RULEDEF behavior in the example will be as follows:1. For a data set with a DDNAME of SYSUT1 in a job with a jobname of

JJHTEST2, the options set will be PRIM_REDUCE=ENABLE andMSG_LEVEL=RULEDEF. This is because only the first RULEDEF matches.

2. For a data set with a DDNAME of SYSUT2 in a job with a jobname ofJJHTEST1, the options set will be SEC_ALLOC=ENABLE andMSG_LEVEL=EXCEPTIONS. This is because only the second RULEDEFmatches.

3. For a data set with a DDNAME of SYSUT1 in a job with a jobname ofJJHTEST1, the options set will be PRIM_REDUCE=ENABLE,SEC_ALLOC=ENABLE and MSG_LEVEL=EXCEPTIONS. This is because bothRULEDEFS match. In the case of MSG_LEVEL, because it is specified on bothRULEDEFS, the last MSG_LEVEL specification will override the firstMSG_LEVEL specification.


Initialize a newly allocated data set (DATASET_INIT)The DATASET_INIT function initializes a newly allocated, but not opened,non-VSAM data set by performing an OPEN/CLOSE sequence on it during steptermination. The initialization causes a valid end-of-file mark to be written to thedata set, eliminating the possibility of I/O errors or invalid data being read by anyprogram trying to read the empty data set. This initialization process also causesspace release, if coded in the JCL, to be driven for the new data set (which can bedesirable for some applications).

Note: If a step is terminating abnormally, MVS will not release space at data setclose.

For a data set to be eligible for initialization, these criteria must be met:v The data set must be non-VSAM.v The DSORG, if coded in the JCL, must be set to PS or PSU.v The data set must have had a volume assigned to it during allocation.v The data set cannot be allocated to VIO.v If the step is terminating normally, the normal disposition in the JCL cannot be

DELETE - DISP=(x,DELETE,x).v If the step is terminating abnormally, the abnormal disposition in the JCL cannot

be DELETE - DISP=(x,x,DELETE).

What it does

The DATASET_INIT function initializes a newly allocated, but not openednon-VSAM data set by performing an OPEN/CLOSE sequence on it during steptermination.


DEFAULTS*INCLUDE JOBNAME=ABC

DATASET_INIT=ENABLE

In the example, all newly allocated, un-opened data sets that match the requiredcriteria, and are allocated by job ABC, will be initialized.


The DATASET_INIT function requires that an additional parameter be added tothe Advanced Allocation Management OPTIONS member followed by an IPL andsubsequent restart of the product.

Process NOT CATLGD 2 errors (NOTCAT2)The NOTCAT2 function detects and handles NOT CATLGD 2 errors. A NOTCATLGD 2 error is reported by the system message IEF287I at step terminationwhen an attempt is made to catalog a newly created data set (but it is determinedthat the data set name is already cataloged to another volume or volumes).

If the system default is set such that these errors do not cause job termination,allowing subsequent steps to continue could result in the usage of an incorrect


data set. This could cause any number of processing errors costing significantlosses in employee and processing time recovering from the ensuing problems.

What it does

The NOTCAT2 keyword specifies how to handle NOT CATLGD 2 errors asreported by the IEF287I message. Several keywords are related to the NOTCAT2function:v The NOTCAT2_CHECK keyword specifies when the detection of the duplicate

data set name occurs (either during the initial allocation of the data set beforethe step is performed — or at step termination time during data set dispositionprocessing and after detection of the IEF287I NOT CATLGD 2 message for thedata set).

v The NOTCAT2_QUALIFIER, NOTCAT2_QUALIFIER_POSITION, andNOTCAT2_SUFFIX keywords are used in conjunction with the NOTCAT2RENAME option to indicate that the currently cataloged data set with theduplicate data set name should be renamed so that the newly created data setcan be successfully cataloged.

Example: NOTCAT2* RULE DEFINITIONS

DEFAULTS

*INCLUDE JOBNAME=ABCDJOB * Item to include in processing

DDNAME=DD1 * Item to include in processingNOTCAT2=JCLFAIL * Function to invoke

The INCLUDE main keyword specifies the selection criteria:v JOBNAME=ABCDJOB specifies that jobs with have a job name of "ABCDJOB

"should be included in Advanced Allocation Management processing.v DDNAME=DD1 specifies that jobs with a DDNAME of "DD1" should be

included in Advanced Allocation Management processing.

NOTCAT2=JCLFAIL specifies that Advanced Allocation Management should failthe remainder of the job upon encountering an IEF287I NOT CATLGD 2 reportederror.

Therefore, if Advanced Allocation Management encounters a job with a job nameof ABCDJOB and with a DDNAME of "DD1" that has received a NOT CATLGD 2error it will cause the remainder of the job to fail as reported by system messageIEF378I.

Any job with a job name that does not match the job name selection criteria of"ABCDJOB" with the DDNAME selection criteria of "DD1" will not process NOTCATLGD 2 errors in this manner.

Example: NOTCAT2_CHECK* RULE DEFINITIONS

DEFAULTS NOTCAT2=JCLFAIL * Default settingsNOTCAT2_CHECK=STEPTERM

*INCLUDE SMS_MANAGED=YES * Item to include in processing

NOTCAT2=SCRATCH * Exception to default processing


NOTCAT2=JCLFAIL specifies that any job that encounters a NOT CATLGD 2 errorshould fail at the step where the error is encountered and that all subsequent stepsshould not be processed.

NOTCAT2_CHECK=STEPTERM specifies that the NOTCAT2 processing occurs atthe end of the job step.

The INCLUDE main keyword specifies selection criteria and any desiredexceptions to default processing. In the example, SMS_MANAGED=YES specifiesthat any SMS-managed data sets should be included in Advanced AllocationManagement processing and NOTCAT2=SCRATCH specifies that the existing dataset should be deleted.

Therefore, if Advanced Allocation Management encounters a job whose attempt toallocate a new SMS-managed data set would have failed because a data set withthe same name is already cataloged on another volume, Advanced AllocationManagement will delete the old data set, thus allowing the new data set to beallocated and cataloged.


Note these considerations:v NOTCAT2 is only applicable to newly created non-VSAM data sets.v NOTCAT2 does not process dynamically allocated data sets. If you need to

process dynamically allocated data sets, use the NOTCAT2_DYNAL function.The NOTCAT2_DYNAL function allows you to selectively enable, or disable,processing of dynamically allocated data sets.

v When NOTCAT2 causes failure of the remainder of a job, the system messageIEF378I will be issued.

v The Advanced Allocation Management started task must be authorized usingyour security authorization product to allow the uncataloging, deletion, andrenaming of data sets if the NOTCAT2 functions of UNCATALOG, SCRATCH,and RENAME will be used.

v The NOTCAT2_CHECK STEPTERM option is ignored for SMS-managed datasets because SMS detects duplicate data set names during allocation and issuesthe IGD17101I message upon detection of the duplicate data set name whichcauses the current and subsequent steps to be flushed.

v Advanced Allocation Management only handles NOT CATLGD 2 errors whenthe data set in question is currently cataloged.

As shown in Table 10, all values of NOTCAT2 except DISABLE will causeAdvanced Allocation Management to intervene in NOTCAT2 situations fornon-SMS-managed, non-VSAM data sets. (NOTCAT2 processing does not apply toVSAM data sets.)

For SMS-managed data sets, SMS will cause the equivalent of NOTCAT2=JCLFAILto occur without the assistance of Advanced Allocation Management —unlessNOTCAT2_CHECK=ALLOCATE while NOTCAT2 specifies either SCRATCH orRENAME.

Table 10. Effect of Advanced Allocation Management NOTCAT2 values on SMS- andnon-SMS-managed data sets

NOTCAT2 value NOTCAT2_CHECK (ALLOCATE) NOTCAT2_CHECK (STEPTERM)

DISABLE neither neither


||||

Table 10. Effect of Advanced Allocation Management NOTCAT2 values on SMS- andnon-SMS-managed data sets (continued)

NOTCAT2 value NOTCAT2_CHECK (ALLOCATE) NOTCAT2_CHECK (STEPTERM)

JCLFAIL non-SMS* non-SMS*

UNCATALOG non-SMS non-SMS

SCRATCH both non-SMS

RENAME both non-SMS

Note: * SMS will cause the equivalent of NOTCAT2=JCLFAIL processing duringallocation for SMS-managed data sets, without the assistance of AdvancedAllocation Management.

Dynamic PDS directory increase (PDS_DIR_INC)The PDS_DIR_INC function detects and recovers DIRECTORY FULL conditions bydynamically increasing the directory space within a partitioned data set when aDIRECTORY FULL condition occurs.

What it does

DIRECTORY FULL conditions occur when an attempt is made to store directoryinformation for a new member in a PDS (using the MVS STOW service) and all ofthe directory blocks are full. Currently, when an attempt is made to store directoryinformation for a new member in a partitioned data set and there is no spaceavailable in the directory, the STOW service is terminated. (If the STOW servicewas invoked from CLOSE processing, the system issues a B14-0C abend.)

When this situation occurs, the only way to add the new member is to:1. Copy the current member data to a temporary location.2. Allocate a new data set with more directory blocks.3. Copy the old data set to the new data set.4. Copy the current member data from the temporary location to the new data

set.5. Delete the old data set.6. Rename the new data set using the original data set name.

This can be a time-consuming process that is prone to error.

Using the Advanced Allocation Management PDS_DIR_INC function, theDIRECTORY FULL condition can be detected and dynamically recovered. When aDIRECTORY FULL condition is detected, Advanced Allocation Managementdetermines whether it is possible to add another block to the directory. If so, thefunction adds a single directory block to the directory. This provides the additionaldirectory space needed to allow the current STOW operation to completesuccessfully. It also allows for the future addition of 6 to 20 members to the dataset, depending on the type of information being stored in the directory entries (forexample, ISPF statistics, and so on).


Example* RULE DEFINITIONSDEFAULTS PDS_DIR_INC=ENABLE * Default settings*INCLUDE JOBNAME=ABCJOB1 * item to include in processingPDS_DIR_INC=DISABLE

Note these items in the example:v PDS_DIR_INC=ENABLE indicates that the PDS_DIR_INC function should be

enabled.v The INCLUDE main keyword specifies selection criteria to which the function

applies. In the example, JOBNAME=ABCJOB1 specifies that those jobs thatspecify a job name of ABCJOB1 should be included in Advanced AllocationManagement processing.

v PDS_DIR_INC=DISABLED indicates that the PDS_DIR_INC function should bedisabled.

Therefore, if Advanced Allocation Management encounters a job where the jobname matches "ABCJOB1" and a DIRECTORY FULL condition occurs, AdvancedAllocation Management will not increase the directory space as defined by thesubsequent PDS_DIR_INC statement.

If Advanced Allocation Management encounters a job where the job name does notmatch "ABCJOB1"and a DIRECTORY FULL condition occurs, Advanced AllocationManagement will increase the directory space as defined by the PDS_DIR_INCkeyword in the DEFAULTS statement. In other words, the PDS_DIR_INC functionwill apply and be processed for all jobs except for those whose job name is“ABCJOB1".


MVS requires that all directory blocks in a PDS directory be contiguous and theentire directory must reside in the first extent of the data set. When thePDS_DIR_INC function detects a DIRECTORY FULL condition, it verifies that adirectory block can be added without violating these MVS requirements. Therefore,if the current directory completely occupies the first extent of the data set, it willnot be possible for Advanced Allocation Management to add a directory block. Inaddition, if member data follows the last directory block on the track, AdvancedAllocation Management will attempt to move any necessary members to free theremaining space on the track for the new directory block. If there is not enoughspace in the data set to move the required members, Advanced AllocationManagement cannot complete the recovery.

Notes:

1. PDS/Es do not have the same restrictions regarding the fixed size of thedirectory and therefore do not encounter DIRECTORY FULL conditions.For this reason, the PDS_DIR_INC function will not attempt to operateon PDS/Es.

2. Advanced Allocation Management obtains control during the MVSSTOW service to determine when it is necessary to perform recoveryprocessing for DIRECTORY FULL conditions. Therefore, any processthat re-writes the PDS directory without using STOW processing is noteligible for dynamic PDS directory increase processing.Depending upon the specific type of operation being performed and thetype of data sets being processed, IEBCOPY sometimes uses STOW and


sometimes does not. One example is the case where one or moremembers of a PDS or PDS/E are being copied to another data set,which is a standard PDS. If the input data set is a standard PDS,IEBCOPY does not use STOW to update the output PDS. However, ifthe input data set is a PDS/E, then IEBCOPY does use STOW to updatethe output PDS.Advanced Allocation Management will only attempt to performdynamic PDS directory increase for IEBCOPY in those cases where ituses STOW to add member information to the directory of a PDS.

Controlled reduction of primary space (PRIM_REDUCE)The PRIM_REDUCE function helps avoid JOB FAILED-JCL errors that occur due toinsufficient space for a primary allocation.

What it does

Out-of-space conditions can occur for primary allocations when a job requestsallocation for a new data set and the primary space is not available on therequested volume. When an out-of-space condition occurs for a primary allocation,the PRIM_REDUCE function reduces the original allocation by a user-specifiedamount, up to a maximum value, until the allocation is successful.

Example* RULE DEFINITIONSDEFAULTS PRIM_REDUCE=ENABLE * Default settings

PRIM_REDUCE_LIM=50PRIM_REDUCE_INC=10

*INCLUDE JOBNAME=ABCJOB2 * Item to include in processingINCLUDE JOBNAME=ABCJOB3 * Item to include in processing

PRIM_REDUCE_INC=05 * Function to invoke

Note these items in the example:v PRIM_REDUCE=ENABLE specifies that the PRIM_REDUCE function should be

enabled.v PRIM_REDUCE_LIM=50 specifies that the primary allocation amount should not

be reduced below 50 percent of the original allocation amount.v PRIM_REDUCE_INC=10 specifies that the original allocation value should be

reduced by 10 percent of the original allocation amount (on each allocationattempt) until the allocation is successful.

The INCLUDE main keywords that follow the PRIM_REDUCE keywords specifythe selection criteria:v The first INCLUDE keyword specifies that jobs that have a job name of

ABCJOB2 should be included in Advanced Allocation Management processing.v The second INCLUDE keyword specifies that jobs that have a job name of

ABCJOB3 should be included in Advanced Allocation Management processing.In addition, the PRIM_REDUCE_INC keyword that follows specifies that forthese jobs, the original allocation should be reduced by 5 percent of the originalallocation amount (instead of 10 percent).

Therefore, if Advanced Allocation Management encounters a job with a job nameof ABCJOB2 and an out-of-space condition occurs for a primary allocation,


Advanced Allocation Management will reduce the original allocation by 10 percentof the original allocation amount, not to exceed 50 percent of the original allocationamount, until the allocation is successful.

If Advanced Allocation Management encounters a job with a job name of ABCJOB3and an out-of-space condition occurs for a primary allocation, Advanced AllocationManagement will reduce the original allocation by 5 percent of the originalallocation amount, not to exceed 50 percent of the original allocation amount, untilthe allocation is successful.

Jobs that do not have job names of ABCJOB2 or ABCJOB3 will not be included inAdvanced Allocation Management processing. When an out-of-space conditionoccurs for these jobs, these jobs will abend.


Note these considerations:v For the PRIM_REDUCE function initial allocation (the first set of operands for

PRIM_REDUCE), Advanced Allocation Management uses thePRIM_REDUCE_INC amount to continue reducing the allocation until it is eithersuccessful or the limit specified by PRIM_REDUCE_LIM is reached.For PRIM_REDUCE non-initial allocations (the second set of operands forPRIM_REDUCE), Advanced Allocation Management evaluates the amount ofavailable freespace and reduces the allocation to that value, or thePRIM_REDUCE_LIM value, whichever is greater.

v The PRIM_REDUCE, PRIM_REDUCE_INC, and PRIM_REDUCE_LIM keywordsare supported for VSAM and non-VSAM data sets. The PRIM_REDUCE functionand related keywords work in the same manner for both types of data sets.

v When specifying explicit volsers for a data set and one of the non-first volumescontains no free space when an extend to a new volume occurs, end of volumeprocessing normally produces an E37 abend. If you want Advanced AllocationManagement to skip the volume with no free space and continue processing bytrying the next explicitly specified volume or by adding a new volume using theVOL_ADD function, you must specify PRIM_REDUCE=(,ENABLE).

v If you specify more than 65535 tracks of data for a primary allocation fornon-VSAM, non-LARGE format, non-extended format data sets, AdvancedAllocation Management will reduce the specified value to 65535 tracks, or less,as part of PRIM_REDUCE processing.

v PRIM_REDUCE will not be performed for DFDSS dynamically allocated datasets.

Test a rule definition (RULEDEF_TEST)The RULEDEF_TEST function allows you to verify that selection criteria specifiedon a RULEDEF INCLUDE or EXCLUDE statement are set up properly to matchintended data set allocations.

What it does

When RULEDEF_TEST is set to ENABLE on a given INCLUDE or EXCLUDEstatement and a data set allocation or extend is performed that matches theselection criteria on that INCLUDE or EXCLUDE statement, no preventative orrecovery action is actually taken, but rather a message is written to indicate thatthe match occurred. An SMF record indicating RULEDEF_TEST processing for thedata set is also generated (if SMF recording for Advanced Allocation Management


||

is active). This allows you to test one or more RULEDEF INCLUDE or EXCLUDEstatements prior to using them in processing.

The RULEDEF_TEST function generates information indicating whether AdvancedAllocation Management considers selection criteria specified on a RULEDEFINCLUDE or EXCLUDE statement to match a given data set that is being allocatedor extended.


DEFAULTS*INCLUDE JOBNAME=ABC

PRIM_REDUCE=ENABLESEC_REDUCE=ENABLERULEDEF_TEST=ENABLE

In the example, when jobs that have a jobname of "ABC" pass though allocation orend-of-volume processing, test messages will be generated indicating thatAdvanced Allocation Management recognizes them as matches for this RULEDEFINCLUDE or EXCLUDE statement. After the job ABC is run, and the test messagesare received indicating that the RULEDEF INCLUDE or EXCLUDE statementmatches the intended data set processing, you can remove the RULEDEF_TESTkeyword or set it to DISABLE and you can be confident that this RULEDEF willperform the indicated processing (PRIM_REDUCE and SEC_REDUCE) for jobs thathave a jobname of "ABC".

Add a secondary allocation (SEC_ALLOC)The SEC_ALLOC function helps avoid job failures that are caused by D37 abends.

What it does

The SEC_ALLOC function adds a secondary allocation during D37 processing if nosecondary space value has been specified. (Data sets that are created with only aprimary allocation are not extended when the primary allocation is full —therefore a D37 abend occurs.) During D37 processing, this function obtains controland adds a secondary space value based on a percentage of the original primaryallocation amount (if no secondary allocation has been specified).




STEPNAME=CREATE * Item to include in processingSEC_ALLOC=ENABLE * Function to invokeSEC_ALLOC_AMT=50

Note these items in the example:

The PRIM_REDUCE=ENABLE function is specified within the default settings.

The INCLUDE main keyword that follows the PRIM_REDUCE function keywordsspecify the selection criteria:


v JOBNAME=ABCDJOB specifies that only those jobs that have a job name of"ABCDJOB " should be included in Advanced Allocation Managementprocessing.

v STEPNAME=CREATE specifies that only those jobs that have a step name of"CREATE" should be included in Advanced Allocation Management processing.

The SEC_ALLOC function keywords that follow the INCLUDE keyword andselection criteria, specify that Advanced Allocation Management should add asecondary allocation if an out-of-space condition occurs as follows:v SEC_ALLOC=ENABLE specifies that the SEC_ALLOC function should be

enabled.v SEC_ALLOC_AMT= 50, so the secondary allocation amount will be 50 percent

of the original primary allocation amount.

Therefore, if Advanced Allocation Management encounters an out-of-spacecondition for a job that has a job name of "ABCDJOB " and a STEPNAME ofCREATE, it will add a secondary allocation. Because SEC_ALLOC_AMT is set to50, the secondary allocation amount will be 50 percent of the original primaryallocation amount. (If Advanced Allocation Management encounters a job that doesnot match all of the specified selection criteria and an out-of-space conditionoccurs, the job will be allowed to abend.)


The SEC_ALLOC and SEC_ALLOC_AMT keywords are supported for VSAM andnon-VSAM data sets. The SEC_ALLOC function and related keyword work in thesame manner for both types of data sets.

The order of processing of the SEC_* functions is:1. SEC_ALLOC2. SEC_INC3. SEC_BEST4. SEC_REDUCE

Reduce secondary allocation to largest available free extent(SEC_BEST)

The SEC_BEST function helps to increase the chances for successful job completionwhen the operating system fails to acquire the secondary allocation amount neededto successfully complete a job.

What it does

When the operating system fails to acquire the secondary allocation amountneeded to successfully complete a job, a B37 abend can result. This function occursprior to the attempt to allocate space to prevent the abend from occurring. Itdecreases the secondary allocation to fit in the largest single extent on the volumeand then re-drives the space acquisition processing.




|

|

|

|

|


SEC_BEST=ENABLE * Function to invoke


The PRIM_REDUCE=ENABLE function is specified within the default settings.

The INCLUDE main keyword that follows the PRIM_REDUCE function keywordsspecify the selection criteria. JOBNAME=ABCDJOB specifies that only those jobsthat have a job name of "ABCDJOB" should be included in Advanced AllocationManagement processing.

The SEC_BEST function keyword that follows the INCLUDE keyword andselection criteria, specify that Advanced Allocation Management should reduce thesecondary allocation to fit in the largest single extent on the volume.


The purpose of the SEC_BEST function is to prevent volume fragmentation byreducing, if needed, a secondary allocation quantity to the size of the largest freeextent. Without this function active, an extent that is too large to fit into the largestsingle extent on the volume would be split into a maximum of five extents whichcan cause fragmentation on the volume. Using SEC_REDUCE in place of, or incombination with the SEC_BEST function, allows you to adjust the size of theextents and the amount of distribution of extents on the volume.

The SEC_BEST and SEC_BEST_LIM keywords are supported for VSAM andnon-VSAM data sets. The SEC_BEST function and related keyword work in thesame manner for both types of data sets.


(The SEC_BEST function always occurs prior to a secondary allocation attempt andSEC_REDUCE only occurs when the secondary allocation attempt fails.)

Increase the size of secondary allocation (SEC_INC)The SEC_INC function helps avoid abends that can occur due to insufficientsecondary allocations. This function helps prevent x37 abends for those data setsthat unexpectedly increase in size, or do so at infrequent intervals, by increasingthe size of each successive secondary allocation at a specified point.

What it does

The SEC_INC function increases the size of the secondary allocation as data setextends occur after a particular extent, and at a particular volume number.

Example* RULE DEFINITIONSDEFAULTS SEC_INC=ENABLE * Default settings

SEC_INC_AMT=100


|

|

|

|

|

||

SEC_INC_XTNT=1*INCLUDE JOBNAME=ABCDJOB * Item to include in processing

Note these items in the example:v SEC_INC=ENABLE specifies that the SEC_INC function should be enabled.v SEC_INC_AMT=100 specifies, as a percentage of the previous allocation amount,

the amount by which secondary allocations should be increased. BecauseSEC_INC_AMT is set to 100, Advanced Allocation Management will increasesecondary allocations by 100 percent of the previous allocation amount.

v SEC_INC_XTNT=1 specifies the extent number at which secondary allocationsshould be increased as defined by the SEC_INC and SEC_INC_AMT keywords.

The INCLUDE main keyword that follows the SEC_INC keywords specify theselection criteria. JOBNAME=ABCDJOB specifies that only those jobs that have ajob name of "ABCDJOB " should be included in Advanced Allocation Managementprocessing.

Therefore, if Advanced Allocation Management encounters a situation where thespecified extent (extent 1) has been reached, for a job with a job name ofABCDJOB, it will increase the secondary allocations by 100 percent of the previousallocation amount, at extent 1.

Any job with a job name that does not match the job name selection criteria of"ABCDJOB" will be allowed to abend if there is an insufficient secondaryallocation.


Note these considerations:v If the newly increased size will not fit in a single extent, you can reduce the size

by also specifying the SEC_BEST function, or recover from it failing by using theSEC_REDUCE function.

v The SEC_INC function supports non-VSAM data sets.


Recover from secondary allocation space failures(SEC_REDUCE)

The SEC_REDUCE function recovers from secondary allocation space failures.

What it does

The SEC_REDUCE function reduces the allocation amount to a value that isconsistent with the current free space on the volume.


|

|

|

|

|

Note: When using SEC_REDUCE in conjunction with multi-striped SMS data sets,the secondary allocation amount is reduced by a user-specified percentage(specified using the SEC_REDUCE_INC keyword) until the allocation issuccessful.

Example* RULE DEFINITIONSDEFAULTS SEC_REDUCE=ENABLE * Default settings

SEC_REDUCE_LIM=20SEC_REDUCE_INC=5

*INCLUDE JOBNAME=ABCJOB* * Item to include in processing

STEPNAME=CREATE * Item to include in processingDDNAME=DD1 * Item to include in processing

Note these items in the example:v SEC_REDUCE=ENABLE specifies that the SEC_REDUCE function should be

enabled.v SEC_REDUCE_INC= 5 specifies that Advanced Allocation Management should

reduce a secondary allocation by 5 percent of the original secondary allocationamount.

v SEC_REDUCE_LIM=20 specifies the limit that Advanced Allocation Managementshould not exceed (20 percent of the original secondary allocation amount)during the reduction process.

The INCLUDE main keyword specify the selection criteria:v JOBNAME=ABCJOB* specifies that only those jobs that have a job name

beginning with "ABCJOB" should be included in Advanced AllocationManagement processing.

v STEPNAME=CREATE specifies that only those jobs that have a step name of"CREATE" should be included in Advanced Allocation Management processing.

v DDNAME=DD1 specifies that only those jobs that have a ddname of "DD1"should be included in Advanced Allocation Management processing.

Therefore, if Advanced Allocation Management encounters an out-of-spacecondition for a data set where the job has a job name that begins with "ABCJOB"(for example, ABCJOB5) with a STEPNAME of CREATE and a DDNAME of DD1,it will reduce the secondary allocation by 5 percent of the original secondaryallocation amount, not to exceed 20 percent of the original secondary allocationamount. (If Advanced Allocation Management encounters a job that does notmatch all of the specified selection criteria and an out-of-space condition occurs,the job will be allowed to abend.)


Note these considerations:v The SEC_REDUCE_INC keyword only applies to SMS multi-striped data sets.

Therefore, the 5 percent specified by the SEC_REDUCE_INC keyword in theexample only applies to SMS data sets. (For non-SMS data sets, the allocation isreduced to the largest available extent not below the SEC_REDUCE_LIM value.)

v The SEC_REDUCE, SEC_REDUCE_INC, and SEC_REDUCE_LIM keywords aresupported for VSAM and non-VSAM data sets. The SEC_REDUCE function andrelated keywords work in the same manner for both types of data sets. ForVSAM data sets, Advanced Allocation Management will not reduce thesecondary space below the size of a CA (Control Area).



(The SEC_BEST function always occurs prior to a secondary allocation attempt andSEC_REDUCE only occurs when the secondary allocation attempt fails.)

Recover unused disk space (SPACE_RELEASE)The SPACE_RELEASE function increases available space for other tasks in thesystem.

What it does

The SPACE_RELEASE function automatically releases unused space when a dataset is closed.

Note: SPACE_RELEASE is only applicable to new or existing physical sequentialdata sets.

Example* RULE DEFINITIONSDEFAULTS*INCLUDE JOBNAME=ABCDJOB * Item to include in processing

DDNAME=DD1 * Item to include in processingSPACE_RELEASE=ENABLE * Function to invoke


The INCLUDE main keyword specifies the selection criteria:v JOBNAME=ABCDJOB specifies that jobs with have a job name of "ABCDJOB "

should be included in Advanced Allocation Management processing.v DDNAME=DD1 specifies that jobs with a DDNAME of "DD1" should be

included in Advanced Allocation Management processing.

SPACE_RELEASE=ENABLE specifies that Advanced Allocation Managementshould automatically release unused space when a data set is closed.

Therefore, if Advanced Allocation Management encounters a job with a job nameof ABCDJOB and with a DDNAME of "DD1" it will automatically releases unusedspace when a data set is closed.

Any job with a job name that does not match the job name selection criteria of"ABCDJOB" will not have space released in this manner.


Note these considerations:v The SPACE_RELEASE function is independent of the RLSE subparameter. That

is, it does not matter if you specify RLSE in the JCL. Advanced AllocationManagement performs the SPACE_RELEASE function, if specified to do so,within the rule definitions.


|

|

|

|

|

||

v Because Advanced Allocation Management causes space release to occur, anyOS/390 or z/OS restrictions apply.

v The SPACE_RELEASE function supports non-VSAM data sets.

Terminate an allocation (TERM_ALLOC)The TERM_ALLOC function can be used to enforce site installation standards byforcing an allocation to fail when the selection criteria in a RULEDEF have beenmet.

What it does

When set to ENABLE, Advanced Allocation Management fails the allocation bysimulating an authorization failure which varies based upon the SMS managementstatus of the data set as well as whether or not it is a VSAM data set.


DEFAULTS*INCLUDE JOBNAME=PRODJOB

DATACLAS=TESTTERM_ALLOC=ENABLE

In the example, if the jobname is PRODJOB and the SMS Data Class is specified asTEST, the allocation will fail.

Dynamically add volumes (VOL_ADD)The VOL_ADD function helps avoid out-of-space conditions that occur duringend-of-volume processing.

What it does

During end-of-volume processing, the VOL_ADD function dynamically addsanother volume when the secondary allocation space request cannot be satisfied onthe current volume, and properly handles any requisite catalog updates.

Example* RULE DEFINITIONS*EXCLUDE JOBNAME=ABCJOB1 * Item to exclude from processingINCLUDE JOBNAME=ABCJOB* * Item to include in processing

VOL_ADD=ENABLE * Default settingsVOL_ADD_LIM=10VOL_ADD_VSER=(DASD01,DASD02,DASD03,DASD04)

Note these items in the example:v VOL_ADD=ENABLE specifies that the VOL_ADD function should be enabled.v VOL_ADD_LIM =10 specifies that Advanced Allocation Management should

add a maximum of 10 volumes (if needed).v The VOL_ADD_VSER keyword lists the volume serial numbers Advanced

Allocation Management should use to determine where it should obtain theadditional volumes.


The EXCLUDE main keyword specifies the selection criteria that should be excludedfrom Advanced Allocation Management processing. In the example, jobs that havea job name of ABCJOB1 will be excluded from Advanced Allocation Managementprocessing. Therefore, if Advanced Allocation Management encounters a job with ajob name of ABCJOB1, and a secondary allocation space request cannot be satisfiedon the current volume, it will not add any additional volumes.

However, if Advanced Allocation Management encounters a job with a job nameother than ABCJOB1, it will add additional volumes as directed by the VOL_ADDkeywords because the INCLUDE statement specifies that jobs with job names thatbegin with "ABCJOB" should be included in Advanced Allocation Managementprocessing.


Note these considerations:v For SMS data sets (non-VSAM and VSAM), SMS selects the additional volume

based on the SMS constructs that apply for the data set. Therefore, volumegroups are not used and the VOL_ADD_SGRP, VOL_ADD_VGRP,VOL_ADD_UNIT, VOL_ADD_VSER, VOL_ADD_MOUNT_USAGE, andVOL_ADD_PROMPT function keywords are ignored.

v Advanced Allocation Management will not attempt to perform the VOL_ADDfunction for PDSes because MVS data management does not supportmulti-volume PDSes (including partitioned data set extended).

v The VOL_ADD, VOL_ADD_LIM, VOL_ADD_PROMPT, VOL_ADD_SGRP,VOL_ADD_UNIT, VOL_ADD_VGRP and VOL_ADD_VSER keywords aresupported for VSAM and non-VSAM data sets. The VOL_ADD function andrelated keywords work in the same manner for both types of data sets.

v When SMS extends a VSAM data set which has in its associated data class theADD'L VOLUME AMOUNT attribute set to (S) Secondary, the initial allocationon the new volume is set to the value of the secondary allocation quantity. If thesecondary allocation quantity is zero, the extend will not occur even if theVOL_ADD function is enabled and (or) candidate volumes exist. For such anextend to be successful, enable the Advanced Allocation ManagementSEC_ALLOC function or set the SMS ADD'L VOLUME AMOUNT attribute to(P) Primary.

v When specifying explicit volsers for a data set and one of the non-first volumescontains no free space when an extend to a new volume occurs, end of volumeprocessing normally produces an E37 abend. If you want Advanced AllocationManagement to skip the volume with no free space and continue processing bytrying the next explicitly specified volume or by adding a new volume using theVOL_ADD function, you must specify PRIM_REDUCE=(,ENABLE).

v When Advanced Allocation Management processes a VSAM cluster, all AIXeswithin the upgrade set for the cluster will also be handled when end-of-volumeis reached for the AIX®.

Using comparison operatorsMany selection criteria keywords allow you to specify optional comparisonoperands (EQ, NE, GE, LE, GT, LT).

This example shows how the greater than (GT) comparison operator can be usedto specify a retention period that is greater than a specific number of days.INCLUDE

RETPD=(5,GT)


|||

In the example, when the specified retention period is greater than five days, thedefinition is considered a match.

Setting allocation attributes using Enhanced AllocationManagement functions

The Enhanced Allocation Management function keywords allow you to setallocation attributes to specific values.

This example shows how the SET_UNIT_NAME keyword can be used to specify aunit name.INCLUDE

RETPD=(5,LT)SET_UNIT_NAME=TEMPTAPE

In the example, when the specified retention period is less than five days, the unitname will be set to TEMPTAPE.

Specifying $NULLFor selection criteria processing, $NULL indicates that an allocation attribute wasnot specified for a JCL, DYNALLOC, or DEFINE statement.

Specifying $NULL allows you to set a value if no value was specified. Forexample:INCLUDE

DEVICECLASS=TAPERETPD=$NULLSET_RETPD=1

In the example, when an allocation is directed to tape, if no retention period isspecified, then set it to one day.

Data class override ($DCOC and $DCOU)For Enhanced Allocation Management processing, the data class override featureallows you to indicate that if a value is specified both in the DATACLAS and inthe JCL or DEFINE statement, the DATACLAS value takes precedence. $DCOCindicates that the override is to take place only if the DATACLAS value is valid(not null).

For example:INCLUDE

DEVICECLASS=TAPESET_EXPDATE=$DCOC

In the example, when an allocation is directed to tape, if the DATACLAS specifiesan expiration date, it will override any value that is specified using a JCL orDEFINE statement. (If the DATACLAS does not specify an expiration date, nooverride will be performed.)

$DCOU indicates that the override is to take place regardless of whether theDATACLAS value is null or not (unconditional override).

For example:INCLUDE

DEVICECLASS=TAPESET_EXPDATE=$DCOU


In the example, when an allocation is directed to tape, if the DATACLAS is null orif it specifies an expiration date, it will override any value that is specified using aJCL or DEFINE statement.

Space recovery strategiesAdvanced Allocation Management enables you to choose from many differentspace recovery strategies when insufficient space exists to allocate a data set.Through the use of individual keywords, or combinations of keywords, you caninfluence the distribution and size of extents for a data set. These topics describethe various keywords and their influence on extent distribution in situations whereinsufficient space exists to accommodate the original allocation amount.

PRIM_REDUCE

The PRIM_REDUCE function allows the initial allocation on the first andsubsequent volumes of a data set to succeed when insufficient space exists toallocate the original amount requested. If you use PRIM_REDUCE withoutspecifying any of the Advanced Allocation Management secondary allocationfunctions and assuming that many, if not all, of the requests for secondaryallocations fail, a data set will tend to spread out with a single extent acrossmultiple volumes as shown in Figure 10.

(1 extent per volume)

This scenario also presumes one of the following:v Sufficient volumes were originally specified.v The Advanced Allocation Management VOL_ADD function has been used to

add volumes.

Note: When specifying explicit volsers for a data set and one of the non-firstvolumes contains no free space when an extend to a new volume occurs,end of volume processing normally produces an E37 abend. If you wantAdvanced Allocation Management to skip the volume with no free spaceand continue processing by trying the next explicitly specified volume or byadding a new volume using the VOL_ADD function, you must specifyPRIM_REDUCE=(,ENABLE).

Figure 10. Space recovery strategy (PRIM_REDUCE)


SEC_REDUCE

SEC_REDUCE processing occurs after the failure of an attempt to allocate thesecondary quantity for a data set. The secondary quantity is reduced so thatallocation will be successful. Therefore, when you specify SEC_REDUCE and avolume has little space or is fragmented, the data set will tend to use as manyextents as allowed for the data set type (up to the maximum amount). If the dataset extends to other volumes, the same processing occurs again. This causes thedistribution of extents for the data set to consist of many potentially smallerextents across fewer volumes (as shown in Figure 11) as compared to using thePRIM_REDUCE function by itself.

(Many extents per volume)

SEC_BEST

The SEC_BEST function is similar to the SEC_REDUCE function in that it reducesa secondary quantity to a size that can be successfully allocated. The difference isthat the size reduction occurs prior to the allocation attempt which can result infewer extents across fewer volumes and a reduction in data set fragmentation.

(Larger and fewer extents per volume)

In attempting to allocate a secondary quantity of a specific size, if a contiguousarea of space is not available, the system will attempt to satisfy the allocation usingup to five extents. This can result in many small extents and can cause the

Figure 11. Space recovery strategy (SEC_REDUCE)

Figure 12. Space recovery strategy (SEC_BEST)


maximum extent limit for the volume to be reached sooner, as well cause the dataset to extend to another volume. Use of the SEC_BEST function ensures that eachsecondary allocation quantity attempt consists of only a single extent of themaximum size space available up to the original quantity requested. Much betteruse of the available space on the volume is made reducing fragmentation and dataset extends. As compared to use of the PRIM_REDUCE function, extents arepotentially many, but spread across fewer volumes. Because Advanced AllocationManagement reduces the size of the extent prior to the system's attempt atallocation, the number of extents are typically larger in size and fewer in numberthan can occur when using the SEC_REDUCE function.

SEC_INC

The SEC_INC function is designed to accommodate unforeseen changes inworkload by increasing the secondary allocation quantity at a specific point.However, this does have some implications on the number of extents and extentdistribution. If a data set unexpectedly grows much larger than normal it can endup creating many extents on the original volume (and possibly onto additionalvolumes). The SEC_INC function increases the secondary allocation resulting infewer extents and possibly fewer volumes.

You can combine the various Advanced Allocation Management functions todesign an extent distribution scheme that best suits your needs. For example, usingPRIM_REDUCE and SEC_REDUCE in combination with the VOL_ADD functionensures that allocations will be successful regardless of your present state offragmentation on your disk volumes.


Chapter 7. Defining volume groups

Use Advanced Allocation Management volume group definitions to define groupsof volumes from which Advanced Allocation Management can select additionalvolumes as directed by the VOL_ADD keyword.

The volume group definitions member in the Advanced Allocation Managementcontrol data set contains the list of volume serial numbers that are associated witha particular volume group name. You can use the volume group name inconjunction with the rule definition VOL_ADD_VGRP keyword to define a groupof volumes that Advanced Allocation Management uses to satisfy a volumeaddition as directed by the VOL_ADD keyword.

Note: This functionality only applies to non-SMS volume extends.

Once defined, you must activate the volume group definitions in order for thedefinitions to take effect. To activate the volume group definitions, you use anoperator command that can be issued whenever the Advanced AllocationManagement started task is running.

Sample volume group definition memberThis information describes the sample volume group definitions member(VGRPDEFS).

Figure 13 shows the volume group definitions provided in the VGRPDEFS samplemember generated by the GLOJCNTL member JCL during the installation andconfiguration process. In the sample, the member has been modified to include avolume group (JJHGRP01) and a list of volumes (VOL000-VOL005).

Volume group definition syntaxVolume definition syntax is comprised of two main keywords: GROUP_NAME(which defines the name of the volume group) and VOLUMES (which defines thelist the volumes in the group).

Creating and modifying volume group definitionsWhen creating a volume group definition member for your installation, use thesample member (VGRPDEFS) provided in the Advanced Allocation Managementcontrol data set.

To create a volume group definition member for your installation, complete thesesteps:

* VGRP DEFINITIONS

GROUP_NAME=JJHGRP01 * NAME OF THE VOLUME GROUP

VOLUMES=(VOL000,VOL001,VOL002,VOL003, * <--- CHANGE TO APPROPRIATEVOL004,VOL005) * VOLUME SERIAL NUMBERS

Figure 13. Sample volume group definitions member (VGRPDEFS)

79

1. Copy the sample volume group definition member (VGRPDEFS) provided inthe Advanced Allocation Management control data set generated by theinstallation and configuration process.

2. Modify the new (copied) member for your installation. To modify volumegroup definitions, use the options that are available on the Tivoli AdvancedAllocation Management Control Member Management screen (recommended),or use the ISPF EDIT function to modify the member directly.

3. Save the member using a valid one to eight-character member name. Allcontrol data set member names must adhere to standard PDS member nameconventions.

Note: When using the Advanced Allocation Management dynamic volumeaddition feature, specifying specific volumes as compared to genericvolumes can result in improved processing speed.

Volume group definition member requirementsEach control data set member requires the first line in the member to be acomment which contains a string that denotes the member type.

The first line of the volume definition member must be a comment which containsthe text "VGRP DEFINITIONS" For example:

* VGRP DEFINITIONS

This comment identifies the member as a volume group definitions member.

Note: If you have multiple volume group definition members, each member mustcontain this same comment as the first line in the member.

Activating volume group definitionsAfter you create and modify volume group definitions for your installation, youmust activate them in order for the settings to take effect.

To activate the volume group definitions, issue the ACTIVATE operator commandfrom the operator console:

Issue the ACTIVATE operator command using the format:MODIFY stcname,ACTIVATE VGRPDEFS member

Where stcname is the name of the started task and member is the name of thevolume group definitions member. The ACTIVATE command causes the contentsof the specified member to become the active set of definitions used by AdvancedAllocation Management during processing.

Note: The member name is optional on the ACTIVATE command. If you do notspecify a member name, the member name VGRPDEFS is used.

The following messages show the result of a successful activation of a volumegroup definition member as it appears in the JES SYSMSG output.For example:GLO4199I 1 * VGRP DEFINITIONSGLO4199I 2 GROUP_NAME=JJHGRP01GLO4199I 3 VOLUMES=(VOL000,VOL001,VOL002,VOL003,VOL004,VOL005)GLO4109I VGRP DEFINITIONS SUCCESSFULLY ACTIVATED -AOPT


Note: The message VGRP DEFINITIONS SUCCESSFULLY ACTIVATED appears when thedefinitions have been successfully activated. If an error occurs during theactivation, messages are provided in the JES SYSMSG output to help youdetermine the cause of the error.

Displaying volume group definitionsThe DISPLAY command displays a message on the operator console that providesinformation about the active set of volume group definitions including the membername from which they were activated, as well as the date and time the memberwas activated.

To display the currently active volume group definitions, issue the DISPLAYoperator command from the operator console as follows:MODIFY stcname,DISPLAY VGRPDEFS

Where stcname is the name of the started task.

Note: A volume group list member can only be displayed if it has been activated.If the member has not been activated, a message notifies you that themember has not been activated.

Single volume group list exampleIn this example, a single volume group (GROUP01) list contains volumesVOL001-VOL004, and volumes that begin with the letter "D".* VGRP DEFINITIONSGROUP_NAME=GROUP01VOLUMES=(VOL001,VOL002,VOL003,VOL004,

D*)

Note: When you list multiple values for an operand (such as a volume list) youmust enclose the list in parentheses. If the list exceeds the limit of a singlerecord, you can continue the list on subsequent records by ending the list ona record at a comma and then continuing the list on the next record.

Multiple volume group lists exampleThis example shows three volume groups (GROUP01, GROUP02, and GROUP03)that are specified.* VGRP DEFINITIONS

GROUP_NAME=GROUP01

VOLUMES=(VOL00A,VOL00B,VOL00C,VOL00D,VOL00E,VOL00F,VOL00G,VOL00H,VOL00I,VOL00J,VOL00K,VOL00L)

GROUP_NAME=GROUP02

VOLUMES=(VOL00M,VOL00N,VOL00O,VOL00P,VOL00Q,VOL00R,VOL00S,VOL00T,VOL00U,VOL00V,VOL00W,VOL00X)

GROUP_NAME=GROUP03

VOLUMES=(VOL01A,VOL02B,VOL03C,VOL04D,VOL05E,VOL06F,VOL07G,VOL08H,VOL09I,VOL10J,VOL11K,VOL12L)

Chapter 7. Defining volume groups 81


Chapter 8. Specifying Advanced Allocation Managementsyntax

These topics provide general guidelines for using Advanced AllocationManagement syntax.

For both rule definitions and volume group definition syntax, keywords can bespecified in columns 1-72 inclusive (the maximum record length for the AdvancedAllocation Management control data set is 80 bytes). Except for lists of items, akeyword and its operands must be contained within a single record.

Specifying multiple operandsFor keywords that have multiple operands, enclose the operands in parentheses.

Multiple operands for a keyword should be separated by a comma. (Spacesbetween operands separated by commas are ignored.) Do not include spacessurrounding the equal sign that associates a keyword with its operands. If you donot need to specify all of the operands for a keyword, use a comma to denote themissing operands. For example:DEFAULTS PRIM_REDUCE=ENABLE

PRIM_REDUCE_LIM=(50,50)PRIM_REDUCE_INC=(10,20)

Note: If you specify only the first operand and no other subsequent operands, youdo not need to enclose the operand in parentheses — or include any trailingcommas to denote the missing operands.

Blanks between fields separated by commas are ignored. Therefore, theseRULEDEFS specifications are equivalent:PRIM_REDUCE=(ENABLE, ENABLE)PRIM_REDUCE=(ENABLE,ENABLE)

Specifying lists of itemsAny operands that require a list of multiple items (such as a volume list) mustenclose the list in parentheses.

If the list exceeds the limit of a single record, you can continue the list onsubsequent records by ending the list on a record at a comma and then continuingthe list on the next record. For example:VOLSER=(DASD01,DASD02,DASD03,

DASD04,DASD05,DASD06)

Any set of keywords included within parentheses and separated by commas canbe continued onto the next line. For example:PRIM_REDUCE=(ENABLE,

ENABLE)

Including commentsYou can include comments with your syntax in two ways.

83

If an asterisk is coded in column 1, the entire record is considered a comment. Ifan asterisk located in any other column is preceded and followed by a blank, thearea of the record from the asterisk to the end of the record is considered acomment. For example:DEFAULTS PRIM_REDUCE=ENABLE


* Here is the first type of commentINCLUDE JOBNAME=ABCJOB2INCLUDE JOBNAME=ABCJOB3

PRIM_REDUCE_INC=05INCLUDE JOBNAME=ABCJOB * Here is the second type of comment

Using wildcard charactersWildcard characters are supported where indicated in the syntax descriptions.Where supported, an asterisk (*) can be used to indicate zero or more characters. Apercent sign (%) can be used to indicate a single matching character.

Example: Using wildcard characters to specify jobnames

For example:DEFAULTS PRIM_REDUCE=ENABLE


*INCLUDE JOBNAME=ABC%%%%2INCLUDE JOBNAME=JHH*INCLUDE JOBNAME=JOB1*TST

PRIM_REDUCE_INC=05

In this example, INCLUDE JOBNAME=ABC%%%%2 indicates that all jobnamesthat begin with "ABC" followed by any four characters and ending with "2" (forexample, ABCTEST2 or ABC12342) should be included in processing.

The INCLUDE JOBNAME=JHH* statement, indicates that all jobnames that startwith "JHH" such as JHHTEST, JHHABC, JHH1, and so on, should be included.

The INCLUDE JOBNAME=JOB1*TST statement indicates that all jobnames thatstart with "JOB1" and end with "TST", such as JOB1ATST or JOB15TST should beincluded.

Example: Using wildcard characters to specify data set names

For example:INCLUDE DSNAME=WRKABC*INCLUDE DSNAME=WORK.ABC*.IJKINCLUDE DSNAME=PABC.CDEF.*INCLUDE DSNAME=NODE1.NO*E4

In this example, INCLUDE DSNAME=WRKABC* indicates that all data sets withnames that begin with "WRKABC" (such as WRKABCTS, WRKABC1.TEST,WRKABC2.TST.DSK1, and so on) should be included in processing.

The INCLUDE DSNAME=WORK.ABC*.IJK statement indicates that all data setswith names that begin with "WORK.ABC" and end with ".IJK" (such asWORK.ABC123.IJK or WORK.ABCTST1.DSK1.IJK) should be included inprocessing.


||||||||

|||

|

|

||||

|||

||||

The INCLUDE DSNAME=PABC.CDEF.* statement indicates that all data sets withnames that begin with "PABC.CDEF." (such as PABC.CDEF.TST orPABC.CDEF.TEST.WRK1) should be included in processing.

The INCLUDE DSNAME=NODE1.NO*E4 statement indicates that all data setswith names that begin with "NODE1.NO" and end with "E4" (such asNODE1.NOABC.NODE4, or NODE1.NODE2.NODE3.NODE4) should be includedin processing.

Example: Using wildcard characters with string comparisons

You can also use wildcard characters in conjunction with string comparisons.

For example:INCLUDE DSNAME=(WORK.ABC*.IJK,EQ)

In this example, the INCLUDE DSNAME=WORK.ABC*.IJK statement indicatesthat all data sets with names that begin with "WORK.ABC" and end with ".IJK"(such as WORK.ABC123.IJK or WORK.ABCTST1.DSK1.IJK) should be included inprocessing.

However, if a comparison other than EQ or NE is made against a string containinggeneric characters ('*' or '%'), the comparison is made only against the characterstring up to, and including, the character immediately preceding the genericcharacter.

For example, consider the following statement:INCLUDE DSNAME=(WORK.*.IJK,GT)

In this example, any data set name string with a value greater than “WORK.”would be included in processing.

See “String comparisons” on page 90 and “Comparison operands” on page 89 formore information about comparing strings.

Chapter 8. Specifying Advanced Allocation Management syntax 85

|||

||||

|

|

|

|

||||

||||

|

|

||

||


Chapter 9. Rule definition syntax

Rule definition syntax consist of keywords and keyword values grouped intofunctions and selection criteria by the DEFAULTS, INCLUDE, and EXCLUDE mainkeywords.

Main keywordsMain keywords define the three types of rules that control Advanced AllocationManagement processing.

Note: The underlined portion of the keyword indicates the minimally acceptableabbreviation.

DEFAULTSThe first keyword in the rule definitions member, after the required comment thatidentifies the member type, must be the DEFAULTS keyword.

The DEFAULTS keyword establishes the default settings for the AdvancedAllocation Management functions and selection criteria. The settings you specifyusing the DEFAULTS keyword remain active until you override them with anequivalent specification using a subsequent INCLUDE keyword.

For example, if you set PRIM_REDUCE=ENABLE using the DEFAULTS keyword,the function will remain enabled until you specify PRIM_REDUCE=DISABLEusing an INCLUDE keyword. The DEFAULTS keyword and its keywords can befollowed by any number of INCLUDE or EXCLUDE keywords.

Note: Any selection or function keyword that is not specified on an INCLUDE orEXCLUDE statement will inherit the value, if any, specified on theDEFAULTS statement.

Syntax

DEFAULTS

�� DEFAULTS FunctionsSelection Criteria

� INCLUDE FunctionsSelection Criteria

�

� � EXCLUDEFunctionsSelection Criteria

��

Figure 14. Rule definition syntax

87

Example: Establishing default settings for functionsDEFAULTS PRIM_REDUCE=ENABLE


In this example, the DEFAULTS keyword establishes the default settings for thePRIM_REDUCE, PRIM_REDUCE_LIM, and PRIM_REDUCE_INC functionkeywords.

Example: Establishing default settings for a function andselection criteriaDEFAULTS MESSAGES=ENABLE

MSG_LEVEL=ALLMSG_DEST=JESSEC_BEST=DISABLEJOBTYPE=JOB

In this example, the DEFAULTS keyword establishes the default settings for theMESSAGES, MSG_LEVEL, and MSG_DEST function keywords and JOBTYPEselection criteria to help ensure no started task or TSO user was processed byAdvanced Allocation Management.

INCLUDEThe INCLUDE keyword specifies the items to be selected for processing and thefunctions to invoke for the selected items.

Note: Advanced Allocation Management will not perform any processing unlessyou specify at least one INCLUDE statement in the rule definitions.

Syntax

INCLUDE

ExampleDEFAULTS PRIM_REDUCE=ENABLE


*INCLUDE JOBNAME=ABCDJOB2INCLUDE JOBNAME=ABCDJOB3INCLUDE JOBNAME=ABCDJOB1

In this example, the DEFAULTS keyword establishes the default settings for thePRIM_REDUCE, PRIM_REDUCE_LIM, and PRIM_REDUCE_INC functionkeywords. The INCLUDE statements indicate that Advanced AllocationManagement should include jobs that have the a job name of ABCDJOB2,ABCDJOB3, or ABCDJOB1, in its processing.

EXCLUDEThe EXCLUDE keyword specifies the items to be excluded from AdvancedAllocation Management processing and should generally precede INCLUDEstatements because rule definitions are processed in top-down order.


Note: Function-specific keywords are permitted for the EXCLUDE keyword, butare ignored. This feature enables you to easily switch a rule definitionbetween an INCLUDE and an EXCLUDE without requiring you tore-specify the function keywords.

Syntax

EXCLUDE

ExampleDEFAULTS PRIM_REDUCE=ENABLE


*EXCLUDE JOBNAME=ABCDJOB2EXCLUDE JOBNAME=ABCDJOB3INCLUDE JOBNAME=ABCDJOB*

In this example, the DEFAULTS keyword establishes the default settings for thePRIM_REDUCE, PRIM_REDUCE_LIM, and PRIM_REDUCE_INC functionkeywords. The EXCLUDE statements that follow indicate that Advanced AllocationManagement should exclude jobs that have the a job name of "ABCDJOB2" or"ABCDJOB3" from processing. Any other jobs that have a job name beginning with"ABCDJOB " will be included in processing because the INCLUDE statementspecifies that Advanced Allocation Management should include any job that has ajob name that begins with "ABCDJOB."

FunctionsFunction keywords define the functions that Advanced Allocation Managementperforms, and the values it should use for those functions when it finds a matchusing the associated selection criteria.

Enhanced Allocation Management functionsEnhanced Allocation Management function keywords enable you to set allocationattributes to specific values. These keywords have a prefix of "SET_"

Note: When specifying Enhanced Allocation Management function keywords,ensure that the Enhanced Allocation Management function values you useare consistent and valid to your operating system.

Selection criteria keywordsUse selection criteria keywords in conjunction with the INCLUDE or EXCLUDEmain keywords to specify the items to include or exclude from AdvancedAllocation Management processing.

Comparison operandsMany selection criteria keywords allow you to specify these optional comparisonoperands.v EQ — (Default.) Equal.v NE — Not equal.v GE — Greater than or equal.

Chapter 9. Rule definition syntax 89

v LE — Less than or equal.v GT— Greater than.v LT— Less than.

For example, in the statement:JOBNAME=(PAYROLL3,GT)

a match will occur if the JOBNAME is greater than the string "PAYROLL3".

Note: If you do not specify a comparison operand for a keyword that allowscomparison operands, an equal comparison (EQ) is assumed.

String comparisonsAdvanced Allocation Management performs string comparisons using the EBCDICcharacter set. Strings of unequal length are assumed to be padded with blanks.

If a comparison other than EQ or NE is made against a string containing genericcharacters ('*' or '%'), the comparison is made only against the character string upto, and including, the character immediately preceding the generic character.

Numeric comparisonsComparisons can be performed for numeric values.

For example:BLKSIZE=(4096,GT)

will be considered a match if the BLKSIZE is greater than 4096. With numericvalues, a numeric comparison is performed. Therefore, any leading zeroes areignored. For example, 4096, 04096, and 00004096 are all considered to be equal.

Null or unspecified values ($NULL)For some selection criteria and Enhanced Allocation Management functionkeywords, the reserved string ($NULL) designates that a null or unspecified valueexists for the particular item.

For example, in the DD statement://DD1 DD DSNAME=PAY.FILE,DISP=(,CATLG)

a selection criteria of ADISP=$NULL would be considered a match because theabnormal disposition was not specified using the JCL DD DISP keyword.

Note: For selection criteria keywords, the only comparison operators that shouldbe used with $NULL are the EQ and NE comparison operators. Using anyother comparison operators, while they will not be flagged as errors, will beignored.

Character string valuesAll character string values can contain generic characters unless otherwisespecified.


Numeric suffixesSelection criteria and function numeric values can have a suffix appended to themto designate a scale.

The allowed suffixes are:v K = Kilobytes (value * 1024)v M = Megabytes (value * 1048576)v G = Gigabytes (value * 1073741824)v T = Terabytes (value * 1099511627776)

For example, 4K represents the numeric value 4096. The suffix counts toward themaximum allowed length of the field. Therefore, when you specify 4K as the valuefor a keyword, it is considered to have a length of 2.

Data class overrideTypically, when an attribute value is assigned in both the data class and in the JCLor DEFINE statement for a data set, the JCL value will override the value specifiedin the data class. The Data Class Override feature allows you to specify that thevalue specified in the data class should override the JCL or DEFINE specificationinstead.

You can choose to have all Advanced Allocation Management supported valuesoverride JCL or DEFINE values as a whole— or you can selectively chooseindividual attribute values which should be overridden by the equivalent dataclass values.

The Enhanced Allocation Management $DCO function specifies whether the dataclass override feature should be active for all Advanced Allocation Managementsupported data class variables. Two keywords ($DCOU and $DCOC) providedwith the Enhanced Allocation Management functions enable the data class valuesto unconditionally, or conditionally, override the individual attributes.

$DCOU (unconditional override)$DCOU indicates that the JCL or DEFINE value should be overridden by the dataclass value unconditionally.

When you specify $DCOU in cases where a variable value is specified in both thedata class and in the allocation specification (either in JCL, dynamic allocationrequests or IDCAMS DEFINE statements), the value specified in the data class willunconditionally override the specification from the other source. That is, if there isno value specified in the data class or the value specified in the data class is null,the specification from the other source (the equivalent JCL or DEFINE attribute)will also be nullified, or removed, so that it appears as if it had never beenspecified.

$DCOC (conditional override)$DCOC indicates that the JCL or DEFINE value should be overridden by the dataclass value only if the data class has a value defined.

When you specify $DCOC in the cases where a variable value is specified in boththe data class and in the allocation specification from some other source, onlywhen the value specified in the data class is not null will it override the value


from the other source. That is, if the data class does not have a particular valuedefined, the equivalent JCL or DEFINE attribute value will be left as is and willnot be replaced with a null value.

ACS environment considerationsThe ACS environment considerations described in this topic are applicable to theDATACLAS, MGMTCLAS, STORCLAS, and STORGRP selection criteria and theSET_DATACLAS, SET_MGMTCLAS, SET_STORCLAS, and SET_STORGRPfunctions.

SMS can make multiple calls to the ACS environment to determine the four SMSconstructs of the data, storage and management classes and the storage group. Forexample, SMS might make an initial call to determine the data, storage andmanagement classes and then make a second call to establish the storage group.When you use an SMS construct as a selection criterion, it will only be considereda match if the particular selection criterion was requested in the call to the ACSenvironment.

For example, if ACS makes a call to determine the data class and a rule definitioncontains selection criteria for both data and storage classes, even if the data classmatches the rule definition selection criterion, because a storage class selectioncriterion was specified, but the storage class was not requested in the ACS call, therule definition will be considered a non-match.

Note: SMS makes a single ACS call for all JCL-defined data sets prior to the startof the first step of the job. Consequently, any messages associated withchanges to the Data Class, Storage Class, Management Class and StorageGroup using the SET_DATACLAS, SET_STORCLAS, SET_MGMTCLAS andSET_STORGRP Enhanced Allocation Management functions respectively,will be displayed at the very beginning of the job ahead of the execution ofthe first step.

Similarly, after a match is made on the selection criteria in a rule definition, theonly SMS constructs which can be set with Advanced Allocation Management arethe constructs originally requested in the call to the ACS environment. Forexample, if only the data class is requested in the call to the ACS environment,only the SET_DATACLAS Enhanced Allocation Management function will behonored. Any specified SET_STORCLAS, SET_MGMTCLAS or SET_STORGRPfunction will be ignored.

Space parameter considerationsThe same rules that apply during normal z/OS and SMS processing also applywhen you use Advanced Allocation Management to change an allocation variable.

For example, IDCAMS does not allow for space parameters to be specifiedconcurrently at both the cluster and data or index levels. Therefore, if you want toset space parameters at the cluster level, then you should also add SET statements(Enhanced Allocation Management function keywords) to nullify them at the dataand index levels (and vice-versa).

For example, if you specify:SET_SPACEUNITS_DATA=CYLSET_PQTY_DATA=2SET_SQTY_DATA=2


SET_SPACEUNITS_INDEX=CYLSET_PQTY_INDEX=1SET_SQTY_INDEX=1

you should also include these SET statements:SET_SPACEUNITS=$NULLSET_PQTY=$NULLSET_SQTY=$NULL

Note: To nullify space parameters for a given level, you must set all of thevariables (SET_SPACEUNITS, SET_PQTY, and SET_SQTY) to null.

Consistency rules for space parameters (batch or dynamicallocation)

Follow these consistency rules for space parameters for batch or dynamic allocation(VSAM and non-VSAM data sets):v If SPACEUNITS, PQTY, or SQTY are either implicitly or explicitly set to be

overridden by the dataclas ($DCO), then, either:– all of those parameters must be set to be overridden by the dataclas.– AVGREC and average-record-length (a sub-parameter of the SPACE keyword)

must have originally been specified for the allocation.For example, if SPACE=(TRK,1000) is coded in the JCL and you specifySET_SPACEUNITS=$DCOC in the RULEDEFS, a consistency check failuremessage will be issued and the SET operation will not be performed. This isbecause a dataclas can only specify space parameters in AVGREC units and ifAVGREC=M is specified in the dataclas, an invalid allocation of(average_record_length * 1000 * 1000000) would result.However, if SPACE=(TRK,1000) is coded in the JCL and you specifySET_SPACEUNITS=$DCOC in the RULEDEFS, and also specifySET_PQTY=$DCOC and SET_SQTY=$DCOC, then space quantities consistentwith AVGREC from the dataclas will be used, resulting in a meaningfulallocation.

v If SPACEUNITS, PQTY, or SQTY are either implicitly or explicitly set to beoverridden by the dataclas (dataclas-override (DCO)), then AVGVALUE, PQTY,and SQTY must be defined in the dataclas, or none must be defined in thedataclas.

v If SPACEUNITS, PQTY, or SQTY are set to $NULL, then all of those parametersmust be set to $NULL.

v If SPACEUNITS is explicitly changed to a non-$DCO ($DCOU or $DCOC),non-$NULL value, then a new corresponding PQTY value must also be specified(unless the original PQTY value was zero).

v If SPACEUNITS is explicitly changed to a non-$DCO ($DCOU or $DCOC),non-$NULL value, then a new corresponding SQTY value must also be specified(unless the original SQTY value was zero).

v If SPACEUNITS is either implicitly or explicitly set to AVGRECU, AVGRECK, orAVGRECM, the record-size must also be specified.

Consistency rules for space parameters (VSAM DEFINEs)

Follow these consistency rules for space parameters for VSAM defines:


v If SPACEUNITS, PQTY, or SQTY are either implicitly or explicitly set to beoverridden by the dataclas ($DCO), then all of those parameters must be set tobe overridden by the dataclas.

v If SPACEUNITS, PQTY, or SQTY are either implicitly or explicitly set to beoverridden by the dataclas (dataclas-override (DCO)), then AVGVALUE, PQTY,and SQTY must be defined in the dataclas, or none must be defined in thedataclas.

v If SPACEUNITS, PQTY, or SQTY are set to $NULL, then all of those parametersmust be set to $NULL.

v If SPACEUNITS is explicitly changed to a non-$DCO ($DCOU or $DCOC),non-$NULL value, then a new corresponding PQTY value must also be specified(unless the original PQTY value was zero).

v If SPACEUNITS is explicitly changed to a non-$DCO ($DCOU or $DCOC),non-$NULL value, then a new corresponding SQTY value must also be specified(unless the original SQTY value was zero).

v If SPACEUNITS is either implicitly or explicitly set to AVGRECU, AVGRECK, orAVGRECM, the average record size must also be specified.

How allocation attributes are used during selection criteria processingSome values can be specified in the SMS data class as well as in the JCL. When theselection criteria are processed, Advanced Allocation Management uses the valueas it is used by the system (following rules of precedence).

For example, if an allocation attribute is specified in both the SMS data class andin the JCL or IDCAMS equivalent, the system will use the JCL value (unless inz/OS 1.10 the SMS data class Override Space value is specified, in which case thedata class space-related values, data control interval size, and CI and CA freespacevalues will be used).

For more information about the Override Space parameter, see the z/OS V1R10.0DFSMS Storage Administration Reference (for DFSMSdfp, DFSMSdss, DFSMShsm).

Function and selection criteria environment compatibilityThis table shows the function and selection criteria permitted in each environment.

Table 11. Function and selection criteria environment compatibility

Keyword ACS ALLOCATE EXTEND UNALLOCATE STOW CATCHECK

ACCBIAS x x x

ADISP x x x x x

AVS x

AVS_ALGORITHM x

AVS_MOUNT_USAGE x

AVS_UNIT x

AVS_VGRP x

AVS_VGRP_SEARCH x

AVS_VSER x

BLKSIZE x x x x x

BUFSPC x x x

CISZ x x x

CISZ_DATA x x x


Table 11. Function and selection criteria environment compatibility (continued)


CISZ_INDEX x x x

CONTIGUOUS x x x x x

CONTINUE x x x x x x

DATACLAS x x x x x x

DATASET_INIT x

DDNAME *3 *3 x x x x

DEFERMOUNT x x x x

DEVICECLAS x x x x x

DIAG x x x x x x

DIRBLKS x x x x x

DSNAME x x x x x x

DSNAME_DATA x x x

DSNAME_INDEX x x x

DSNAME_LASTNODE x x x x x x

DSNAME_QUALIFIER x x x x x x

DSNAME_TYPE x x x x x x

DSORG x x x x x x

ENVIRONMENT x x x x x x

EXPDATE x x x x x x

EXTADDR x x x

FILESEQNO x x x x

FRLOG x x x

FSPC_CA x x x

FSPC_CI x x x

GROUPID x x x x x x

GUARSPACE x x x x x x

ILOAD x x x

JOBACCTn x x x x x x

JOBCLASS *1 x x x x x

JOBNAME x x x x x x

JOBTYPE x x x x x x

KEY_LEN x x x

KEY_OFF x x x

LOGGING x x x

LOGSTREAM_ID x x x

LRECL x x x

MAXSPACE x x x x x x

MESSAGES x x x x x x

MGMTCLAS x x x x x x

MOUNT_USAGE x x x x x

MSG_DESTINATION x x x x x x

MSG_LEVEL x x x x x x

NDISP x x x x x

NOTCAT2 x

NOTCAT2_CHECK x




NOTCAT2_DYNAL x

NOTCAT2_QUALIFIER x

NOTCAT2_QUALIFIER_POSITION x

NOTCAT2_SUFFIX x

NUMVOLS x x x

NUMVOLS_DATA x x x

NUMVOLS_INDEX x x x

OWNERID x x x x x

PDS_DIR_INC x

PRIM_REDUCE x x

PRIM_REDUCE_INC x x

PRIM_REDUCE_LIM x x

PROCSTEPNAME *2 x x x x x

PROGRAM x x x x x x

PQTY x x x x x x

PQTY_DATA x x x

PQTY_INDEX x x x

PSPACE_KB x x x x x x

PSPACE_MB x x x x x x

RECFM x x x x x

RELEASESPACE x x x x x

RETPD x x x x x x

REUSE x x x

RULEDEF_TEST x x x x x x

SDISP x x x x x

SEC_ALLOC x

SEC_ALLOC_AMT x

SEC_BEST x

SEC_BEST_LIM x

SEC_INC x

SEC_INC_AMT x

SEC_INC_VOLNO x

SEC_INC_XTNT x

SEC_REDUCE x

SEC_REDUCE_INC x

SEC_REDUCE_LIM x

SET_ACCBIAS x

SET_ADISP x

SET_BLKSIZE x

SET_BUFSPC x

SET_CISZ x

SET_CISZ_DATA x

SET_CISZ_INDEX x

SET_CONTIGUOUS x

SET_DATACLAS x




SET_DEFERMOUNT x

SET_DIRBLKS x

SET_DSNAME_TYPE x

SET_DSORG x

SET_EXPDATE x

SET_EXTADDR x

SET_FILESEQNO x

SET_FRLOG x

SET_FSPC_CA x

SET_FSPC_CI x

SET_ILOAD x

SET_KEY_LEN x

SET_KEY_OFF x

SET_LOGSTREAM_ID x

SET_LRECL x

SET_MGMTCLAS x

SET_NDISP x

SET_NUMVOLS x

SET_NUMVOLS_DATA x

SET_NUMVOLS_INDEX x

SET_PQTY x

SET_PQTY_DATA x

SET_PQTY_INDEX x

SET_RECFM x

SET_RETPD x

SET_REUSE x

SET_SHROPT_XRGN x

SET_SHROPT_XSYS x

SET_SPACEUNITS x

SET_SPACEUNITS_DATA x

SET_SPACEUNITS_INDEX x

SET_SPANNED x

SET_SQTY x

SET_SQTY_DATA x

SET_SQTY_INDEX x

SET_STORCLAS x

SET_STORGRP x

SET_TAPE_COMP x

SET_TAPE_LABEL x

SET_UNIT_AFFINITY x

SET_UNIT_COUNT x

SET_UNIT_NAME x

SET_VOLCT x

SET_VSAM_SEPARATE x

SHROPT_XRGN x x x




SHROPT_XSYS x x x

SMS_MANAGED x x x x x x

SPACE_RELEASE x

SPACEUNITS x x x x x x

SPACEUNITS_DATA x x x

SPACEUNITS_INDEX x x x

SPANNED x x x

SQTY x x x x x x

SQTY_DATA x x x

SQTY_INDEX x x x

STEPACCTn x x x x x x

STEPNAME *2 x x x x x

STORCLAS x x x x x x

STORGRP x x x x x x

SUBSYS x x x x x x

SYSID x x x x x x

SYSPLEXNAME x x x x x x

TAPE_COMP x x x

TAPE_LABEL x x x x

TEMPDS x x x x x

TERM_ALLOC x x x x x

UNIT_AFFINITY x x x x x

UNIT_COUNT x x x x x x

UNIT_NAME x x x x x x

UNIT_TYPE x x x x x

USERID x x x x x x

VOL_ADD x

VOL_ADD_ALGORITHM x

VOL_ADD_LIM x

VOL_ADD_MOUNT_USAGE x

VOL_ADD_PROMPT x

VOL_ADD_SGRP x

VOL_ADD_UNIT x

VOL_ADD_VGRP x

VOL_ADD_VGRP_SEARCH x

VOL_ADD_VSER x

VOLCT x x x x x

VOLSER_ANY x x x x x x

VOLSER_CURRENT x x x x x

VOLSER_FIRST x x x x x

VSAM_SEPARATE x x

WRITE_MSG x x x x x x

Notes:


1. JOBCLASS is set to x'D0', the "}" character, when ACS is called duringinitial batch JCL processing.

2. PROCESTEPNAME and STEPNAME are not available during ACSprocessing when called during initial batch JCL processing.

3. DDNAME is not available during IDCAMS DEFINE processing.



Chapter 10. Function keywords

Function keywords specify the functions Advanced Allocation Managementperforms and the values it should use for those functions, when it finds a matchusing the associated selection criteria.

Note:

1. In the keyword descriptions, the underlined portion of the keywordindicates the minimally acceptable abbreviation.

2. All functions that have an ENABLE or DISABLE option default toDISABLE if no DEFAULT value is set (or if the function is not explicitlyspecified).

For more information about function keywords, including examples, see “Functionand rule definition examples” on page 58.

AVSThe AVS keyword specifies whether Advanced Volume Selection is enabled ordisabled. Advanced Volume Selection enables Advanced Allocation Management toselect the volumes for a non-SMS managed data set at initial allocation time.

Syntax

��DISABLE

AVS= ENABLE

��

AVS=ENABLE | DISABLE

Operands

ENABLEEnable Advanced Volume Selection.

DISABLEDisable Advanced Volume Selection.

Note: The AVS keyword requires at least one of the AVS_VGRP, AVS_UNIT orAVS_VSER keywords in order to specify the volsers to search for a suitablevolume.

VSAM notes:

AVS is performed at the component level for VSAM data sets using the specifiedalgorithm. For the BESTFIT, FIRST, and PERFORMANCE algorithms the size of theextent to locate is determined as follows:v With the space parameters defined at the CLUSTER level, the primary allocation

quantity is used for both the data and index components to search for space.v With the space parameters defined separately at the DATA and INDEX levels,

each component's respective primary quantity is used to search for space.

101

||

|

When the cluster definition contains volume serial numbers, AVS will overlay anyuser-specified values and either truncate or extend the volume list as necessary.

If no volumes are able to be located using the requested AVS algorithm, thevolume list will be emptied and the cluster definition will fail.

Default

DISABLE.

Environments

ALLOCATE.

Related keywords

AVS_ALGORITHM, AVS_MOUNT_USAGE, AVS_UNIT, AVS_VGRP,AVS_VGRP_SEARCH, and AVS_VSER.

ExampleAVS=ENABLE

In this example, AVS is set to ENABLE, therefore, Advanced Volume Selection willbe enabled.

AVS_ALGORITHMThe AVS_ALGORITHM keyword specifies a volume selection algorithm to usewhen performing Advanced Volume Selection.

Syntax

��LARGESTSINGLE

AVS_ALGORITHM= BESTFITFIRSTMOSTFREESPACEPERFORMANCE

��

AVS_ALGORITHM=BESTFIT | FIRST | LARGESTSINGLE | MOSTFREESPACE |PERFORMANCE

Operands

BESTFITSelect the volume(s) with a single extent in which the requested amount isclosest to the requested primary allocation quantity (without being less thanthe requested primary allocation quantity).

FIRSTSelect the first volume(s) with enough total freespace to satisfy the requestedallocation amount.

Note: The allocation amount might not be able to be satisfied because thefreespace needed might be spread out across more than five extents


|

|

|

(which is the normal limit within allocation for satisfying a spacerequest). Therefore, you might need to specify PRIM_REDUCE to assistin making the allocation successful.

LARGESTSINGLESelect the volume(s) with the largest single free extent.

Note: Advanced Allocation Management selects a volume with the largestsingle extent. This does not mean that the volume has enough space tosatisfy the requested amount — it simply indicates it is the volume withthe largest single extent. Therefore, you might need to use thePRIM_REDUCE function to handle those situations where the selectedvolume does not have adequate space available.

MOSTFREESPACESelect the volume with the most available freespace. The most availablefreespace is defined as the total amount of free cylinders or tracks on thevolume (depending upon the allocation unit used). If you specify cylinderallocation, the total number of free cylinders is considered. Otherwise, the totalnumber of free tracks is considered.

PERFORMANCESelect the volume with the lowest fragmentation index.

Notes:

1. If more than one volume is to be selected as specified in the volumecount, Advanced Allocation Management will choose multiple volumesstarting with the best candidate as defined by the algorithm chosen —down to the least eligible candidate.

2. For the BESTFIT and FIRST algorithm, as the size of the extent must atleast contain the requested primary quantity, it could be possible thatAdvanced Allocation Management will not find enough volumes basedon the algorithm to satisfy the volume count specified. In that case, theremaining volumes, up to the volume count specified, will be chosenusing the MOSTFREESPACE algorithm.

3. When Advanced Allocation Management chooses initial volumes usingAVS, the allocation request is converted to a specific volume request.

Tips:

v If you want to fill volumes in sequence, leaving other volumes mostly empty forlarge allocations, consider specifying FIRST or BESTFIT. (Specifying FIRST tendsto fill volumes in order of specification in the various volume groups.)

v If you want to distribute allocations evenly among all volumes in a volumegroup, consider specifying MOSTFREESPACE and LARGESTSINGLE. (In mostcases, specifying MOSTFREESPACE followed by LARGESTSINGLE tends toevenly distribute the allocations across the volumes listed in the volume groups.)

These suggestions are dependent upon sizes and patterns of data set creation anddeletion and your results could vary.

Default

LARGESTSINGLE.

Chapter 10. Function keywords 103

|||

||||

Environments

ALLOCATE.

Related keywords

AVS, AVS_MOUNT_USAGE, AVS_UNIT, AVS_VGRP, AVS_VGRP_SEARCH, andAVS_VSER.

ExampleAVS_ALGORITHM=MOSTFREESPACE

In the example, the volume with most available freespace will be selected.

AVS_MOUNT_USAGEThe AVS_MOUNT_USAGE keyword limits volume selection to those volumes thatmatch the requested mount usage attributes.

Syntax

��ANY

AVS_MOUNT_USAGE= ALLPRIVATEPUBLICSTORAGE

��

AVS_MOUNT_USAGE=ALL | ANY | PRIVATE | PUBLIC | STORAGE

Operands

Specify one of these operands.

ALLSpecifies that all mount usage attributes are acceptable (specifying ALL is thesame as specifying ANY).

ANYSpecifies that any mount usage attribute is acceptable.

PRIVATE, PUBLIC, and STORAGEThe PRIVATE, PUBLIC, and STORAGE operands are equivalent to the mountusage attribute for a volume as defined in the Unit Control Block for a device— and as defined by z/OS.

Only one operand can be specified. For example:

Valid: AVS_MOUNT_USAGE=STORAGE

Not valid: AVS_ADD_MOUNT_USAGE=STORAGE,PUBLIC

Default

ANY.


|

Environments

ALLOCATE.

Related keywords

AVS, AVS_ALGORITHM, AVS_UNIT, AVS_VGRP, AVS_VGRP_SEARCH, andAVS_VSER.

ExampleINCLUDE JOBNAME=JJHTEST01

AVS=ENABLEAVS_VGRP=GROUP01AVS_MOUNT_USAGE=STORAGE

In the example, when an AVS is performed for a non-SMS-managed data set forjob JJHTEST01, the volumes that Advanced Allocation Management will considerwill be all of the volumes with a mount usage attribute of STORAGE in thevolume group named GROUP01.

AVS_UNITThe AVS_UNIT keyword specifies the units to search for eligible volumes whenperforming Advanced Volume Selection.

Syntax

��

�

,

AVS_UNIT=( unitname )

��

AVS_UNIT=(unitname,unitname,....)

Where:

unitnameSpecifies a unit to search for eligible volumes. Each unit name can be amaximum of eight characters in length.

Default

None.

Environments

ALLOCATE.

Related keywords

AVS, AVS_ALGORITHM, AVS_MOUNT_USAGE, AVS_VGRP,AVS_VGRP_SEARCH, and AVS_VSER.

ExampleAVS_UNIT=(DISKBIG,DISKALT)


||

|

|

In the example, Advanced Allocation Management will search the esoteric groupswith the unit names of DISKBIG and DISKALT for eligible volumes.

AVS_VGRPThe AVS_VGRP keyword specifies volume groups to search for eligible volumeswhen performing Advanced Volume Selection.

Syntax

��

�

,

AVS_VGRP=( vgrp )

��

AVS_VGRP=(vgrp,vgrp,....)

Where:

vgrpSpecifies a volume group to search. Each volume group name can be amaximum of eight characters in length.

Default

None.

Environments

ALLOCATE.

Related keywords

AVS, AVS_ALGORITHM, AVS_MOUNT_USAGE, AVS_UNIT,AVS_VGRP_SEARCH, and AVS_VSER.

ExampleAVS_VGRP=(GROUP01,GROUP02,GROUP03)

In the example, Advanced Allocation Management will search the GROUP01,GROUP02, and GROUP03 volume groups for eligible volumes.

AVS_VGRP_SEARCHThe AVS_VGRP_SEARCH keyword specifies the volume selection volume groupsearch method to use when performing Advanced Volume Selection.

Syntax

��ALL

AVS_VGRP_SEARCH= FIRST

��

AVS_VGRP_SEARCH=ALL | FIRST


||

|

|

|

Operands

ALLSearch all volume groups for a suitable volume.

FIRSTStop searching for volumes after the volume group that was just searched hasa volume in it that meets the criterion established by the AVS_ALGORITHMkeyword.

Note: Other than BESTFIT (when all volumes requested are able to be satisfiedusing the BESTFIT algorithm) there is no guarantee that the spacerequested will be available.

For example, if you specify AVS_ALGORITHM= LARGESTSINGLE andAdvanced Allocation Management selects a volume with the largestsingle extent in a volume group, that does not mean that the volume hasenough space to satisfy the requested amount, it simply means it is thevolume with the largest single extent. Therefore, you might need to usethe PRIM_REDUCE function to handle those situations where theselected volume does not have adequate space available.

Default

ALL.

Environments

ALLOCATE.

Related keywords

AVS, AVS_ALGORITHM, AVS_MOUNT_USAGE, AVS_UNIT, AVS_VGRP, andAVS_VSER.

ExampleAVS_VGRP_SEARCH=FIRST

In the example, Advanced Allocation Management will stop searching for volumesif a suitable volume exists in the volume group in which it is currently searching.

AVS_VSERThe AVS_VSER keyword specifies the volsers Advanced Allocation Managementshould search for eligible volumes when performing Advanced Volume Selection.

Syntax

��

�

,

AVS_VSER=( volser )

��

AVS_VSER=(volser,volser,....)

Where:


volserSpecifies the 1-6 character volume serial number(s) to search for eligiblevolumes

Default

None.

Environments

ALLOCATE.

Related keywords

AVS, AVS_ALGORITHM, AVS_MOUNT_USAGE, AVS_UNIT, AVS_VGRP, andAVS_VGRP_SEARCH.

ExampleAVS_VSER=(V0L100,VOL200,VOL300)

In the example, Advanced Allocation Management will search theVOL100,VOL200, and VOL300 volsers for eligible volumes.

CONTINUEThe CONTINUE keyword specifies that RULEDEFS processing should continueeven if the current RULEDEF encounters a match.

Syntax

��DISABLE

CONTINUE= ENABLE

��

CONTINUE=ENABLE | DISABLE

Operands

ENABLEEnable CONTINUE processing.

DISABLEDisable CONTINUE processing.

Default

DISABLE.

Environments

ACS, ALLOCATE, CATCHECK, EXTEND, STOW, and UNALLOCATE.

ExampleCONTINUE=ENABLE


|

|

|

|

|

In the example, RULEDEFS processing will continue when Advanced AllocationManagement encounters a match on the current rule definition.

DATASET_INITThe DATASET_INIT keyword specifies whether the data set in question should beinitialized.

Syntax

��DISABLE

DATASET_INIT= ENABLE

��

DATASET_INIT=ENABLE | DISABLE

Operands

ENABLEPerform data set initialization.

DISABLEDo not perform data set initialization.

Default

DISABLE.

Environments

UNALLOCATE.

ExampleINCLUDE JOBNAME=ABC

DATASET_INIT=ENABLE

In the example, all newly allocated, un-opened data sets that match the requiredcriteria and are allocated by job ABC will be initialized.

DIAGThe DIAG keyword specifies whether or not to display diagnostic information.

Syntax

��DISABLE

DIAG= ENABLE

��

DIAG=ENABLE | DISABLE

Note: This keyword should only be used at the direction of IBM personnel.


|

|

|

|

Operands

ENABLEDisplay diagnostic information.

DISABLEDo not display diagnostic information.

Default

DISABLE.

Environments


ExampleDIAG=DISABLE

In the example, DIAG is set to DISABLE, therefore, no diagnostic information willbe displayed.

ENVIRONMENTWithin Advanced Allocation Management, the term environment describes aparticular phase in the processing of a data set during which Advanced AllocationManagement is capable of performing function and selection processing.

The ENVIRONMENT keyword limits the operation of a RULEDEF to a specificenvironment, or environments. You can specify the ENVIRONMENT keyword onDEFAULTS, INCLUDE, or EXCLUDE statements.

Syntax

��

�

,ALL

ENVIRONMENT=( ACS )ALLOCATECATCHECKEXTENDSTOWUNALLOCATE

��

ENVIRONMENT=(ACS, ALL, ALLOCATE, CATCHECK, EXTEND, STOW,UNALLOCATE)

Tip: While not required, the ENVIRONMENT keyword can be helpful whenspecifying and converting to rule definitions.

Operands

ACSThe point in SMS processing directly following the assignment of one or moreof the SMS constructs of Data Class, Storage Class, Management Class, orStorage Group.


|

|

|

||||||||||||||||||||||||||||||||||||||||||

|

||

||

ALLAll points where Advanced Allocation Management intercepts processing.Specifying ALL is the same as specifying all of the previous six options.

ALLOCATEThe point in processing where a new data set is allocated (including VSAMand non-VSAM, SMS and non-SMS data sets).

CATCHECKThe point in allocation processing where the determination of the priorexistence of a data set is made. For SMS data sets, this point is just prior to theallocation of a data set. For non-SMS data sets, this point can be just prior tothe allocation of a data set — or at unallocation processing time during catalogdisposition processing.

EXTENDThe point in processing where a new extent is added to a data set, either onthe current volume or on a new volume (including volume addition).

STOWThe point in PDS processing when a new member is being added to a data setand the directory is being updated.

UNALLOCATEThe point in processing where a data set is unallocated.

Note: You can specify one or more of the specified options.

Default

ALL.

Environments


ExampleENVIRONMENT=(EXT)

In the example, the specified environment is EXTEND.

MESSAGESThe MESSAGES keyword specifies whether or not to display messages.

Syntax

��DISABLE

MESSAGES= ENABLE

��

MESSAGES=ENABLE | DISABLE

Operands

ENABLEDisplay messages.


|

DISABLEDo not display messages.

Default

DISABLE.

Environments


Related keywords

MSG_DESTINATION and MSG_LEVEL.

ExampleMESSAGES=DISABLE

In the example, MESSAGES is set to DISABLE, therefore, no messages will bedisplayed.

MSG_DESTINATIONThe MSG_DESTINATION keyword specifies where messages should be directed.

Syntax

��JES

MSG_DESTINATION= BOTHCONSOLE

��

MSG_DESTINATION=BOTH | CONSOLE | JES

Operands

BOTHJES SYSMSG data set and operator console.

CONSOLEOperator console.

JESJES SYSMSG data set.

Note: The MSG_DESTINATION keyword is associated with the MESSAGESkeyword. You must specify MESSAGES=ENABLE to implement thisfunction.

Default

JES.

Environments



|

|

|

Related keywords

MESSAGES and MSG_LEVEL.

ExampleMSG_DESTINATION=CONSOLE

In the example, MSG_DESTINATION is set to CONSOLE, therefore, messages willbe directed to the operator console.

MSG_LEVELThe MSG_LEVEL keyword specifies whether to display only exception messages,display messages concerning a RULEDEF match, or display all messages.

Syntax

��

�

,(1) EXCEPTIONS

MSG_LEVEL=( ALL )RULEDEF

��

Notes:

1 Although you can specify both ALL and EXCEPTIONS, the two optionscontradict one another. Only the EXCEPTIONS option will be honored if bothare specified.

MSG_LEVEL=(EXCEPTIONS, ALL, RULEDEF)

Operands

ALLSpecifying MSG_LEVEL=ALL displays both exception messages andinformational messages related to successful completion of certain functions byAdvanced Allocation Management.

Note: MSG_LEVEL=ALL does not include the RULEDEF option. (RULEDEFmatch messages will not be displayed when only MSGLEVEL=ALL isspecified.)

EXCEPTIONSDisplay only exception messages.

RULEDEFWhen you specify MSG_LEVEL=RULEDEF Advanced Allocation Managementdisplays a message concerning a RULEDEF match each time it checks for amatching RULEDEF and finds a match. (Advanced Allocation Managementdoes not display a message if it does not find a RULEDEF match.)

Note: Checks for a matching RULEDEF can occur many times during theprocessing of a data set and therefore can increase the number ofmessages output to the message destination.

Note: The MSG_LEVEL keyword is associated with the MESSAGES keyword. Youmust specify MESSAGES=ENABLE to implement this function.


|||||||||||||||||||||||||||||||

|

|||

|||||

|||

Default

EXCEPTIONS.

Environments


Related keywords

MESSAGES and MSG_DESTINATION.

Example

In this example, MSG_LEVEL is set to RULEDEF:INCLUDE JOBNAME=MSGLEVEL

STEPNAME=CREATE0MSG_LEVEL=RULEDEF

The resulting joblog shows the line number of the matching RULEDEF statements:GLO2188I MATCHING INCLUDE RULEDEF LINE NUMBER = 17 - Q31VGLO2188I MATCHING INCLUDE RULEDEF LINE NUMBER = 17 - Q31VIEF236I ALLOC. FOR MSGLEVEL CRESTEP CREATE0IGD100I 2105 ALLOCATED TO DDNAME DD1 DATACLAS ( )GLO2188I MATCHING INCLUDE RULEDEF LINE NUMBER = 17 - Q31V

Next, MSG_LEVEL is set to EXCEPTIONS. When an attempt is made to allocate adata set with the duplicate data set name (STEP CREATE2) and use the NOTCATfunction to resolve the situation:INCLUDE JOBNAME=MSGLEVEL

STEPNAME=CREATE2MSG_LEVEL=EXCEPTIONSNOTCAT2=RENOTCAT2_C=ANOTCAT2_Q=NSMSNOTCAT2_QUALIFIER_P=1

There are no RULEDEF messages present in the joblog.

Finally, when MSG_LEVEL=ALL is specified:INCLUDE JOBNAME=MSGLEVEL

STEPNAME=CREATE4MSG_LEVEL=ALLNOTCAT2=RENOTCAT2_C=ANOTCAT2_Q=NSMSNOTCAT2_QUALIFIER_P=1

The resulting joblog shows these messages:GLO2087I DATA SET ON VOLSER NSL200 RENAMED AT ALLOCATION TIME -Q31VGLO2086I NEW NAME: NSMS.NSMS.RSTEST.GLO.ORL12.MSGALL -Q31VGLO2123I MSGLEVEL,CREATE4,CRESTEP,DD1,NSMS.RSTEST.GLO.ORL12.MSGALL -Q31V

Note that when MSG_LEVEL=ALL is specified, no MSG_LEVEL messages appearin the joblog (as they do when MSG_LEVEL=RULEDEF is specified).

Example: MSG_LEVEL=ALLMSG_LEVEL=ALL


|

|

|||

|

|||||

|||

|||||||

|

|

|||||||

|

|||

||

In the example, MSG_LEVEL is set to ALL, therefore, both exception messages andinformational messages related to successful completion of certain functions byAdvanced Allocation Management will be displayed.

Example: MSG_LEVEL=(ALL, RULEDEF)INCLUDE JOBNAME=AAMTEST1

MSG_LEVEL=(ALL,RULEDEF)SPACE_RELEASE=ENABLE

In this example, MSG_LEVEL=(ALL,RULEDEF). The resulting joblog shows thesemessages:GLO2188I MATCHING INCLUDE RULEDEF LINE NUMBER = 17 - Q31VGLO2188I MATCHING INCLUDE RULEDEF LINE NUMBER = 17 - Q31VIEF236I ALLOC. FOR AAMTEST1 CRESTEP CREATE0IGD100I 2105 ALLOCATED TO DDNAME SYSUT2 DATACLAS ( )GLO2188I MATCHING INCLUDE RULEDEF LINE NUMBER = 17 – Q31VGLO2125I SPACE RELEASE RECOVERED 9 TRACKS -Q31VGLO2123I AAMTEST1,CREATE0,CRESTEP,SYSUT2,RSQA.AAMTEST1.GLO.TEST.DATA –Q31V

NOTCAT2The NOTCAT2 keyword specifies how to handle NOT CATLGD 2 errors asreported by the system message IEF287I. Advanced Allocation Management onlyhandles NOT CATLGD 2 errors when the data set in question is currentlycataloged.

Notes:

1. The Advanced Allocation Management started task must be authorizedusing your security authorization product to allow the uncataloging,deletion, and renaming of data sets if the NOTCAT2 functions ofUNCATALOG, SCRATCH and RENAME will be used.

2. The NOTCAT2 function does not process dynamically allocated datasets. If you need to process dynamically allocated data sets, use theNOTCAT2_DYNAL function. The NOTCAT2_DYNAL function allowsyou to selectively enable, or disable, processing of dynamically allocateddata sets.

Syntax

��DISABLE

NOTCAT2= JCLFAILRENAMESCRATCHUNCATALOG

��

NOTCAT2=DISABLE | JCLFAIL | RENAME | SCRATCH | UNCATALOG

Operands


DISABLEThe NOTCAT2 function should not be performed.


|||

|

|||

||

|||||||

|||||

|

JCLFAILNOT CATLGD 2 errors should be processed and the jobstream should be set tofail with the system message:

IEF378I jobname jjjjjjjj - JOB FAILED - CATALOG DISPOSITION ERROR

upon detecting the IEF287I NOT CATLGD 2 message for a data set.

Note: JCLFAIL does not apply to SMS-managed data sets because SMS alreadyperforms the equivalent checking and failing of a job upon encounteringa duplicate data set name at allocation time.

RENAMEThe currently cataloged data set with the duplicate data set name should berenamed so that the newly created data set can be successfully cataloged.

SCRATCHThe currently cataloged data set with the duplicate data set name should beuncataloged and deleted so that the newly created data set can be successfullycataloged.

Note: This option is valid for both SMS and non-SMS-managed data sets withthe NOTCAT2_CHECK=ALLOCATION option.

UNCATALOGThe currently cataloged data set with the duplicate data set name should beuncataloged so that the newly created data set can be successfully cataloged.

Notes:

1. This option is ignored for SMS-managed data sets as SMS-manageddata sets cannot be validly uncataloged.

2. This option is valid with both NOTCAT2_CHECK=ALLOCATIONand NOTCAT2_CHECK=STEPTERM.

Notes:

1. This option is valid for both SMS and non-SMS-managed data sets withthe NOTCAT2_CHECK=ALLOCATION options.

2. If you use the NOTCAT2_QUALIFIER option, make sure that thehigh-level qualifier chosen maintains the status of the data set as eitherSMS or non-SMS-managed. Either NOTCAT2_QUALIFIER orNOTCAT2_SUFFIX (or both) must be specified for this option to beeffective.

3. If either, or both, of the NOTCAT2_QUALIFIER or NOTCAT2_SUFFIXoptions causes the length of the data set name to exceed 44 charactersin length, the data set name is truncated. The NOTCAT2_QUALIFIERvalue is applied first (if present) followed by the NOTCAT2_SUFFIX (ifpresent).

4. NOTCAT2 does not process dynamically allocated data sets. If you needto process dynamically allocated data sets, use the NOTCAT2_DYNALfunction. The NOTCAT2_DYNAL function allows you to selectivelyenable, or disable, processing of dynamically allocated data sets.

Default

DISABLE.


||||

Environments

CATCHECK.

Related keywords

NOTCAT2_CHECK, NOTCAT2_DYNAL, NOTCAT2_QUALIFIER,NOTCAT2_QUALIFIER_POSITION, and NOTCAT2_SUFFIX.

ExampleNOTCAT2=JCLFAIL

In the example, upon detecting the IEF287I NOT CATLGD 2 message for a dataset, NOT CATLGD 2 errors will be processed and the jobstream will be set to fail.

NOTCAT2_CHECKThe NOTCAT2_CHECK keyword specifies when the detection of the duplicatedata set name occurs.

Syntax

��STEPTERM

NOTCAT2_CHECK= ALLOCATION

��

NOTCAT2_CHECK=ALLOCATION | STEPTERM

Operands


ALLOCATIONThe detection of the duplicate data set name occurs during the initial allocationof the data set (before the step is performed).

Note: This option is available for both SMS and non-SMS-managed data sets.

STEPTERMThe detection of the duplicate data set name occurs at step termination (duringdata set disposition processing and after detection of the IEF287I NOTCATLGD 2 message for the data set).

Notes:

1. This option is ignored for SMS-managed data sets as SMS detectsduplicate data set names during allocation. (SMS issues theIGD17101I message upon detection of the duplicate data set namewhich causes the current and subsequent steps to be flushed.)

2. If you use NOTCAT2 at step termination time, you will see theIEF253I and (or) the IGD17001I duplicate data set name messages ifthe new data set is allocated to the same volser as the old data set.This occurs because you cannot have two data sets with the samename in a single VTOC. Therefore, the step will never reach thestep termination phase as it will fail during allocation. Thissituation should only occur if you use an explicit volser for a non


|

||

|

SMS-managed data set. If you let the system choose a volser, it willtry to choose a volume that does not already have the data set on it.

Default

STEPTERM.

Environments

CATCHECK.

Related keywords

NOTCAT2, NOTCAT2_DYNAL, NOTCAT2_QUALIFIER,NOTCAT2_QUALIFIER_POSITION, and NOTCAT2_SUFFIX.

ExampleNOTCAT2_CHECK=ALLOCATION

In the example, the detection of the duplicate data set name occurs during theinitial allocation of the data set before the step is performed.

NOTCAT2_DYNALIn some cases, NOTCAT2 failures for dynamic allocations are intercepted andprocessed by the calling program (for example: TSO). However, there are someapplications that do not automatically handle such situations and for whichNOTCAT2 processing could be beneficial. In these cases, the NOTCAT2_DYNALfunction allows you to selectively enable, or disable, processing of dynamicallyallocated data sets.

Syntax

Note: Advanced Allocation Management does not automatically handle NOTCAT2for dynamically allocated data sets. (The default for the NOTCAT2_DYNALkeyword is DISABLE.) Without knowledge of the specific actions performedby a calling program, unexpected problems could occur.

��DISABLE

NOTCAT2_DYNAL= ENABLE

��

NOTCAT2_DYNAL=ENABLE | DISABLE

Operands

ENABLEAllow NOTCAT2 processing for dynamically allocated data sets.

DISABLEBypass NOTCAT2 processing for dynamically allocated data sets.

Default

DISABLE.


|

||

|

||||||

|

||||

|||||||||||||||||||

|

|

|

||

||

|

|

Environments

CATCHECK.

Related keywords

NOTCAT2, NOTCAT2_CHECK, NOTCAT2_QUALIFIER,NOTCAT2_QUALIFIER_POSITION, and NOTCAT2_SUFFIX.

ExampleNOTCAT2_DYNAL=ENABLE

In the example, dynamically allocated data sets will be eligible for NOTCAT2processing.

NOTCAT2_QUALIFIERThe NOTCAT2_QUALIFIER keyword specifies a high-level qualifier.

Syntax

��NOTCAT2_QUALIFIER= qualifier

��

NOTCAT2_QUALIFIER=qualifier

Where:

qualifierSpecifies a qualifier (up to eight characters in length) to be added to thecurrently existing data set name in the position specified by theNOTCAT2_QUALIFIER_POSITION keyword. The value you specify must meetnormal data set naming conventions for valid characters.

If needed, a period (.) is automatically added to the end of this value whenforming the new data set name. If the addition of this value to the data setname causes it to exceed 44 characters in length, the data set name is truncatedat 44 characters. If you specify both NOTCAT2_QUALIFIER andNOTCAT2_SUFFIX, NOTCAT2_QUALIFIER is applied first.

Note: For the NOTCAT2_QUALIFIER keyword to be effective, theNOTCAT2_QUALIFIER_POSITION keyword must have a non-zerovalue.

Default

None.

Environments

CATCHECK.

Related keywords

NOTCAT2, NOTCAT2_CHECK, NOTCAT2_DYNAL,NOTCAT2_QUALIFIER_POSITION, and NOTCAT2_SUFFIX.


|

|

|

||

|

|

||

|

|

|

||

ExampleNOTCAT2_QUALIFIER=abcNOTCAT2_QUALIFIER_POSITION=2

In the example, the resulting data set name will have qualifier of "abc" as thesecond qualifier in the data set name (for example: tst.abc.data).

NOTCAT2_QUALIFIER_POSITIONThe NOTCAT2_QUALIFIER_POSITION keyword specifies the position of the dataset name qualifier defined by the NOTCAT2_QUALIFIER keyword.

Syntax

��NOTCAT2_QUALIFIER_POSITION= position

��

NOTCAT2_QUALIFIER_POSITION=position

Where:

positionIs a numeric value that specifies the position of the data set name qualifier. Themaximum value allowed is 22. A value of one (1) indicates that the qualifierwill be the highest level qualifier in the data set name. A value that exceeds thecurrent number of qualifiers in the data set name will result in the qualifierbeing added to the end of the data set name.

Default

The default is zero (0) which is the same as not specifying this keyword.

Environments

CATCHECK.

Related keywords

NOTCAT2, NOTCAT2_CHECK, NOTCAT2_DYNAL, NOTCAT2_QUALIFIER, andNOTCAT2_SUFFIX.

ExampleNOTCAT2_QUALIFIER=abcNOTCAT2_QUALIFIER_POSITION=1

In the example, the resulting data set name will begin with "abc" (for example:abc.test.data).

NOTCAT2_SUFFIXThe NOTCAT2_SUFFIX keyword specifies a low-level qualifier.


|

|

|

||

Syntax

��NOTCAT2_SUFFIX= suffix

��

NOTCAT2_SUFFIX=suffix

Where:

suffixSpecifies a low-level qualifier (up to eight characters in length) to be added tothe end of currently existing data set name. This value must meet normal dataset naming conventions for valid characters. If the addition of this value to theend of the data set name causes it to exceed 44 characters in length, the dataset name is truncated at 44 characters. If both NOTCAT2_QUALIFIER andNOTCAT2_SUFFIX are specified, NOTCAT2_SUFFIX is applied last.

Default

None.

Environments

CATCHECK.

Related keywords

NOTCAT2, NOTCAT2_CHECK, NOTCAT2_DYNAL, NOTCAT2_QUALIFIER, andNOTCAT2_QUALIFIER_POSITION.

ExampleNOTCAT2_SUFFIX=myjcl

In the example, the resulting data set name will end with "myjcl" (for example:abc.test.myjcl).

PDS_DIR_INCThe PDS_DIR_INC keyword specifies whether or not to automatically increase thedirectory space within a partitioned data set when a DIRECTORY FULL conditionoccurs.

Syntax

��DISABLE

PDS_DIR_INC= ENABLE

��

PDS_DIR_INC=ENABLE | DISABLE

Operands

ENABLEAutomatically increase the directory space.


|

|

|

||

|

DISABLEDo not increase the directory space.

Default

DISABLE.

Environments

STOW.

ExamplePDS_DIR_INC=DISABLE

In the example, PDS_DIR_INC is set to DISABLE, therefore, Advanced AllocationManagement will not increase the directory space within a partitioned data setwhen a DIRECTORY FULL condition occurs.

PRIM_REDUCEThe PRIM_REDUCE keyword specifies whether or not to reduce the primaryallocation when an out-of-space condition occurs.

Syntax

��(DISABLE,DISABLE)

PRIM_REDUCE= (ENABLE,ENABLE)(ENABLE,DISABLE)(DISABLE,ENABLE)

��

PRIM_REDUCE=(ENABLE | DISABLE, ENABLE | DISABLE)

Operands

The PRIM_REDUCE keyword has two operands:v The first operand applies to the primary allocation on the first volume. Valid

values are ENABLE (reduce the primary allocation when an out-of-spacecondition occurs) and DISABLE (do not reduce the primary allocation when anout-of-space condition occurs).

v The second operand applies to the primary allocation on the second andsubsequent volumes. Valid values are ENABLE (reduce the primary allocationwhen an out-of-space condition occurs) and DISABLE (do not reduce theprimary allocation when an out-of-space condition occurs).

Notes:

1. You must set PRIM_REDUCE_INC to a non-zero value to implementthis function.

2. For non-VSAM data sets, the first allocation on volumes other than thefirst volume, is not technically a primary allocation. The allocationquantity value used to extend non-VSAM volumes to additionalvolumes is actually the secondary quantity.

3. When specifying explicit volsers for a data set and one of the non-firstvolumes contains no free space when an extend to a new volume


|

|

|

||

occurs, end of volume processing normally produces an E37 abend. Ifyou want Advanced Allocation Management to skip the volume withno free space and continue processing by trying the next explicitlyspecified volume or by adding a new volume using the VOL_ADDfunction, you must specify PRIM_REDUCE=(,ENABLE).

4. If you specify more than 65535 tracks of data for a primary allocationfor non-VSAM, non-LARGE format, non-extended format data sets,Advanced Allocation Management will reduce the specified value to65535 tracks, or less, as part of PRIM_REDUCE processing.

5. For SMS VSAM and non-VSAM data sets, since the volume serialnumber is not yet chosen by the system at PRIM_REDUCE time, ifVOLSER_CURRENT is specified in the selection criteria with a valueother than $NULL , the RULEDEF statement is considered not to matchfor the PRIM_REDUCE function on the first volume.

6. PRIM_REDUCE will not be performed for DFDSS dynamically allocateddata sets.

Default

DISABLE, DISABLE.

Environments

ALLOCATE, EXTEND.

Related keywords

PRIM_REDUCE_INC and PRIM_REDUCE_LIM.

The PRIM_REDUCE keyword is associated with the PRIM_REDUCE_INC andPRIM_REDUCE_LIM keywords. PRIM_REDUCE_INC specifies the increment touse when reducing the primary allocation on the first volume andPRIM_REDUCE_LIM specifies the reduction limit.

When the PRIM_REDUCE_LIM value for the initial volume of a non VSAM dataset is set to zero, the primary quantity for a data set will be set to zero, ifnecessary, by the PRIM_REDUCE function. This will allow the secondary quantity,if specified, to be used to allocate space on any explicitly specified volumes or onvolumes added by Advanced Allocation Management through the VOL_ADDfunction. If the PRIM_REDUCE_LIM value is non-zero, the lowest value to whichthe primary quantity will be reduced is one (1). For VSAM data sets the lowestpossible primary quantity value is one allocation unit regardless of the setting ofPRIM_REDUCE_LIM.

ExamplePRIM_REDUCE=(ENABLE, DISABLE)

In the example, when an out-of-space condition occurs, the primary allocation willbe reduced on the first volume, but not on the second, or subsequent volumes.


||

|

|

PRIM_REDUCE_INCThe PRIM_REDUCE_INC keyword specifies the increment to use (a percentagevalue of the current allocation amount) when reducing the primary allocation asenabled by the PRIM_REDUCE keyword.

Syntax

��PRIM_REDUCE_INC= xx,yy

��

PRIM_REDUCE_INC=xx,yy

Where:

xx Applies to the primary allocation on the first volume. Valid values are 0-99.

yy Applies to the primary allocation on the second and subsequent volumes.Valid values are 0-99.

Note: Specifying 0 (zero) disables PRIM_REDUCE.

When an out-of-space condition occurs for a primary allocation, the originalallocation is reduced by the amount specified by PRIM_REDUCE_INC, up to thevalue specified for the PRIM_REDUCE_LIM keyword, until the allocation issuccessful.

For example, if enabled by the PRIM_REDUCE keyword, when an out-of-spacecondition occurs for a primary allocation on the first volume, Advanced AllocationManagement will reduce the original allocation by the amount specified byPRIM_REDUCE_INC until the allocation is successful—or the limit specified by thePRIM_REDUCE_LIM keyword is reached.

First volume (the primaryallocation will be reduced).

Second, and subsequent volumes (theprimary allocation will not be reduced).

PRIM_REDUCE (ENABLE, DISABLE). PRIM_REDUCE (ENABLE, DISABLE).

Figure 15. PRIM_REDUCE (ENABLE, DISABLE)


For example, if PRIM_REDUCE_INC=5 and PRIM_REDUCE_LIM=80 AdvancedAllocation Management will reduce the allocation amount in 5 percent increments(not to exceed 80 percent of the original allocation amount).

100

95

91

87

83

79

76

73

PRIM_REDUCE_LIM=80(The amount will not be

reduced below 80% of theoriginal allocation amount)

PRIM_REDUCE_INC=5(The allocation amount will be

reduced in 5% increments)

Note: The PRIM_REDUCE_INC keyword is associated with the PRIM_REDUCEand PRIM_REDUCE_LIM keywords. You must specifyPRIM_REDUCE=ENABLE to implement this function andPRIM_REDUCE_LIM to specify the reduction limit.

Default

The default is 0,0.

Environments

ALLOCATE and EXTEND.

Related keywords

PRIM_REDUCE and PRIM_REDUCE_LIM.

ExamplePRIM_REDUCE_INC=(40,40)

In the example, when an out-of-space condition occurs for a primary allocation onthe first volume, the original allocation will be reduced by 40 percent of the currentallocation amount, up to the value specified for the PRIM_REDUCE_LIM keyword,until the allocation is successful.

When an out-of-space condition occurs for a primary allocation on the second andsubsequent volumes, the original allocation will also be reduced by 40 percent ofthe current allocation amount, up to the value specified for thePRIM_REDUCE_LIM keyword, until the allocation is successful.

PRIM_REDUCE_LIMThe PRIM_REDUCE_LIM keyword specifies the reduction limit as a percentagevalue of the original allocation amount.

Figure 16. PRIM_REDUCE_INC (primary allocation on the first volume)


|

|

Syntax

��PRIM_REDUCE_LIM= (xx,yy)

��

PRIM_REDUCE_LIM=(xx,yy)

Where:

xx Applies to the primary allocation on the first volume. Valid values are 0-99.

yy Applies to the primary allocation on the second and subsequent volumes.Valid values are 0-99.

Note: The PRIM_REDUCE_LIM keyword is associated with the PRIM_REDUCEkeyword and only has an effect when the corresponding PRIM_REDUCEoperand is set to ENABLE. When an out-of-space condition occurs, the sizeof the primary allocation will not be reduced below the amount specified bythe PRIM_REDUCE_LIM keyword.

Default

The default is 0,0.

Environments

ALLOCATE and EXTEND.

Related keywords

PRIM_REDUCE_INC and PRIM_REDUCE.

ExamplePRIM_REDUCE_LIM=(20,40)

In the example, when an out-of-space condition occurs for a primary allocation onthe first volume, Advanced Allocation Management will reduce the originalallocation by the amount specified by PRIM_REDUCE_INC until the allocation issuccessful—or the limit specified by the PRIM_REDUCE_LIM keyword (20 percentof the original allocation amount) is reached.

When an out-of-space condition occurs for a primary allocation on the second andsubsequent volumes, Advanced Allocation Management will evaluate the amount offreespace and reduce the allocation to that value, or to the value specified byPRIM_REDUCE_LIM (40 percent of the original allocation amount) — whichever isgreater.

RULEDEF_TESTThe RULEDEF_TEST keyword specifies whether entities that match this RULEDEFare to be tested or processed.

Syntax


|

|

��DISABLE

RULEDEF_TEST= ENABLE

��

RULEDEF_TEST=ENABLE | DISABLE

Operands

ENABLEEnable testing for rule definitions.

DISABLEDisable testing for rule definitions (perform processing).

Default

DISABLE.

Environments


ExampleINCLUDE JOBNAME=ABC

PRIM_REDUCE=ENABLESEC_REDUCE=ENABLERULEDEF_TEST=ENABLE

In the example, when jobs that have a jobname of "ABC" pass though allocation orend-of-volume processing, test messages will be generated indicating thatAdvanced Allocation Management recognizes them as matches for this RULEDEF.

After the job ABC is run and the test messages are observed, this indicates thatRULEDEF_TEST can then be removed or set it to DISABLE and you can beconfident that this RULEDEF will perform the indicated processing(PRIM_REDUCE and SEC_REDUCE) for jobs whose names are "ABC."

SEC_ALLOCThe SEC_ALLOC keyword specifies whether or not to add a secondary allocationwhen one does not exist in order to prevent an out-of-space condition.

Syntax

��DISABLE

SEC_ALLOC= ENABLE

��

SEC_ALLOC=ENABLE | DISABLE

Operands

ENABLEAdd a secondary allocation.


|

|

|

|

|

DISABLEDo not add a secondary allocation.

Note: The SEC_ALLOC keyword is associated with the SEC_ALLOC_AMTkeyword. You must set SEC_ALLOC_AMT to a non-zero value to implementthis function.

Default

DISABLE.

Environments

EXTEND.

Related keywords

SEC_ALLOC_AMT.

ExampleSEC_ALLOC=ENABLE

In the example, SEC_ALLOC is set to ENABLE, therefore, Advanced AllocationManagement will add a secondary allocation in order to prevent an out-of-spacecondition.

SEC_ALLOC_AMTThe SEC_ALLOC_AMT keyword specifies the secondary allocation amount as apercentage of the original primary allocation amount.

Syntax

��SEC_ALLOC_AMT=xxxx

��

SEC_ALLOC_AMT=xxxx

Where:

xxxxIs an amount specified as a percentage of the original primary allocationamount. The valid range is 0-1000. Specifying 0 (zero) disables SEC_ALLOC.

Default

The default is 0 (zero).

Environments

EXTEND.

Related keywords

SEC_ALLOC.


|||

|

|

|

|

Note: The SEC_ALLOC_AMT keyword is associated with the SEC_ALLOCkeyword. You must specify SEC_ALLOC=ENABLE to implement thisfunction.

ExampleSEC_ALLOC_AMT=10

In the example, SEC_ALLOC_AMT is set to 10, therefore, the secondary allocationamount will be 10 percent of the original primary allocation amount.

SEC_BESTThe SEC_BEST keyword specifies whether or not to reduce the secondaryallocation amount to the largest extent available on a volume when enough spacedoes not exist to allocate the original secondary allocation amount.

Syntax

��DISABLE

SEC_BEST= ENABLE

��

SEC_BEST=ENABLE | DISABLE

Operands

ENABLEReduce the secondary extent.

DISABLEDo not reduce the secondary extent.

Default

DISABLE.

Environments

EXTEND.

Related keywords

SEC_BEST_LIM.

ExampleSEC_BEST=ENABLE

In the example, SEC_BEST is set to ENABLE, therefore, Advanced AllocationManagement will reduce the secondary allocation amount.

SEC_BEST_LIMThe SEC_BEST_LIM keyword specifies a limit (as a percentage of the originalallocation amount) below which the SEC_BEST function will not reduce theoriginal allocation.


|

|

|

Syntax

��SEC_BEST_LIM=xx

��

SEC_BEST_LIM=xx

Where:

xx Is a limit (specified as a percentage of the original allocation amount) belowwhich the SEC_BEST function will not reduce the original allocation. The validrange is 0-99.

Note: The SEC_BEST_LIM keyword is associated with the SEC_BEST keyword.You must specify SEC_BEST=ENABLE to implement this function.

Default


Environments

EXTEND.

Related keywords

SEC_BEST.

ExampleSEC_BEST_LIM=50

In the example, SEC_BEST_LIM is set to 50. Advanced Allocation Management willevaluate the amount of freespace and reduce the allocation to that value, or to thevalue specified by SEC_BEST_LIM (50 percent of the original allocation amount) —whichever is greater.

SEC_INCThe SEC_INC keyword specifies whether or not to increase secondary allocationsafter a specific extent number is reached as defined by the SEC_INC_XTNTkeyword.

Syntax

��DISABLE

SEC_INC= ENABLE

��

SEC_INC=ENABLE | DISABLE

Operands

ENABLEIncrease secondary allocations.


|

|

|

DISABLEDo not increase secondary allocations.

Note: The SEC_INC keyword is associated with the SEC_INC_AMT keyword. Youmust set SEC_INC_AMT to a non-zero value to implement this function.

Default

DISABLE.

Environments

EXTEND.

Related keywords

SEC_INC_AMT, SEC_INC_VOLNO, and SEC_INC_XTNT.

ExampleSEC_INC=DISABLE

In the example, SEC_INC is set to DISABLE, therefore, Advanced AllocationManagement will not increase secondary allocations.

SEC_INC_AMTThe SEC_INC_AMT keyword specifies, as a percentage of the original or previousallocation amount, the amount by which secondary allocations should beincreased.

Syntax

��SEC_INC_AMT=xxxx

��

SEC_INC_AMT=xxxx

Where:

xxxxIs a percentage of the original or previous allocation amount, the amount bywhich secondary allocations should be increased. The valid range is 0-1000.Specifying 0 (zero) disables SEC_INC.

Note: The SEC_INC_AMT keyword is associated with the SEC_INC keyword. Youmust specify SEC_INC=ENABLE to implement this function.

Default


Environments

EXTEND.


||

|

|

|

|

Related keywords

SEC_INC, SEC_INC_VOLNO, and SEC_INC_XTNT.

ExampleSEC_INC_AMT=20

In the example, SEC_INC_AMT is set to 20, therefore, Advanced AllocationManagement will increase secondary allocations by 20 percent of the original orprevious allocation amount.

SEC_INC_VOLNOThe SEC_INC_VOLNO keyword specifies the volume sequence number at whichsecondary allocations should be increased as defined by the SEC_INC,SEC_INC_AMT and SEC_INC_XTNT keywords.

Syntax

��SEC_INC_VOLNO=xxx

��

SEC_INC_VOLNO=xxx

Where:

xxxIs the volume sequence number at which secondary allocations should beincreased as defined by the SEC_INC, SEC_INC_AMT and SEC_INC_XTNTkeywords. The valid range is 0-255. If you specify 0 (zero) anySEC_INC_XTNT value is assumed to apply to the first volume of a data set.

Note: The SEC_INC_VOLNO keyword is associated with the SEC_INC keyword.You must specify SEC_INC=ENABLE to implement this function.

Default


Environments

EXTEND.

Related keywords

SEC_INC_AMT, SEC_INC, and SEC_INC_XTNT.

ExampleSEC_INC_VOLNO=5

In the example, SEC_INC_VOLNO is set to 5, therefore, at volume sequencenumber 5, Advanced Allocation Management will increase secondary allocations asdefined by the SEC_INC, SEC_INC_AMT and SEC_INC_XTNT keywords.


|

|

SEC_INC_XTNTThe SEC_INC_XTNT keyword specifies the extent number on the volume specifiedby the SEC_INC_VOLNO keyword or if SEC_INC_VOLNO is not specified, thefirst volume which secondary allocations should be increased as defined by theSEC_INC and SEC_INC_AMT keywords.

Syntax

��SEC_INC_XTNT=xxx

��

SEC_INC_XTNT=xxx

Where:

xxxIs the extent number on the volume specified by the SEC_INC_VOLNOkeyword or if SEC_INC_VOLNO is not specified, the first volume whichsecondary allocations should be increased as defined by the SEC_INC andSEC_INC_AMT keywords. The valid range is 0-255.

Note: The SEC_INC_XTNT keyword is associated with the SEC_INC keyword.You must specify SEC_INC=ENABLE to implement this function.

Default


Environments

EXTEND.

Related keywords

SEC_INC, SEC_INC_AMT, and SEC_INC_VOLNO.

ExampleSEC_INC_XTNT=9

In the example, SEC_INC_XTNT is set to 9, therefore, at extent 9, AdvancedAllocation Management will increase secondary allocations as defined by theSEC_INC and SEC_INC_AMT keywords.

SEC_REDUCEThe SEC_REDUCE keyword specifies whether or not to reduce a secondaryallocation on the current volume in response to an out-of-space condition.

Syntax

��DISABLE

SEC_REDUCE= ENABLE

��


|

|

|

SEC_REDUCE=ENABLE | DISABLE

Operands

ENABLEReduce the secondary allocation.

DISABLEDo not reduce the secondary allocation.

Note: The SEC_REDUCE keyword is associated with the SEC_REDUCE_INCkeyword. You must set SEC_REDUCE_INC to a non-zero value toimplement this function.

Default

DISABLE.

Environments

EXTEND.

Related keywords

SEC_REDUCE_INC and SEC_REDUCE_LIM.

ExampleSEC_REDUCE=DISABLE

In the example, SEC_REDUCE is set to DISABLE, therefore, Advanced AllocationManagement will not reduce the secondary allocation on the current volume inresponse to an out-of-space condition.

SEC_REDUCE_INCThe SEC_REDUCE_INC keyword specifies a percentage of the original secondaryallocation amount by which a secondary allocation should be reduced inconjunction with the SEC_REDUCE keyword.

Syntax

��SEC_REDUCE_INC=xx

��

SEC_REDUCE_INC=xx

Where:

xx A percentage of the original secondary allocation amount by which asecondary allocation should be reduced in conjunction with the SEC_REDUCEkeyword. The valid range is 0-99. Specifying 0 (zero) disables SEC_REDUCE.

Notes:


|||

|

|

1. The SEC_REDUCE_INC keyword is associated with the SEC_REDUCEkeyword. You must specify SEC_REDUCE=ENABLE to implement thisfunction. Secondary reduction is limited by the SEC_REDUCE_LIMkeyword.

2. The SEC_REDUCE_INC value is only used for:a. SMS multi-striped data sets, both VSAM and non-VSAM, when

performing a secondary space reduction.b. SMS non-VSAM data sets when the secondary allocation quantity is

used while extending to a new volume.

Default


Environments

EXTEND.

Related keywords

SEC_REDUCE and SEC_REDUCE_LIM.

ExampleSEC_REDUCE_INC=20

In the example, SEC_REDUCE_INC is set to 20, therefore, for multi-striped datasets defined by SMS, Advanced Allocation Management will reduce a secondaryallocation by 20 percent of the original secondary allocation amount.

SEC_REDUCE_LIMThe SEC_REDUCE_LIM keyword specifies the secondary allocation reduction limitas a percentage of the original secondary allocation amount below which thesecondary allocation should not be reduced.

Syntax

��SEC_REDUCE_LIM=xx

��

SEC_REDUCE_LIM=xx

Where:

xx The secondary allocation reduction limit as a percentage of the originalsecondary allocation amount below which the secondary allocation should notbe reduced. The valid range is 0-99.

Note: The SEC_REDUCE_LIM keyword is associated with the SEC_REDUCEkeyword. You must specify SEC_REDUCE=ENABLE to implement thisfunction.


|

|

Default


Environments

EXTEND.

Related keywords

SEC_REDUCE and SEC_REDUCE_INC.

ExampleSEC_REDUCE_LIM=10

In the example, SEC_REDUCE_LIM is set to 10, therefore, Advanced AllocationManagement will evaluate the amount of freespace and reduce the allocation tothat value, or to the value specified by SEC_REDUCE_LIM (10 percent of theoriginal allocation amount) — whichever is greater.

SPACE_RELEASE

The SPACE_RELEASE keyword specifies whether or not to release a data set'sunused space during unallocation and, if so, whether to release it only after asecondary extent has been allocated. This keyword applies to new or existingphysical sequential data sets.

Syntax

��DISABLE

SPACE_RELEASE= ENABLESECONDARY

��

SPACE_RELEASE=ENABLE | DISABLE | SECONDARY

Operands

ENABLERelease any unused space.

DISABLEDo not release unused space.

SECONDARYRelease any unused space only if a secondary extent has been allocated. (Spacewill be released if a secondary extent exists.)

Note: SPACE_RELEASE is only applicable to new or existing physical sequentialdata sets.

Default

DISABLE.


|

|

||||

|

|

||

||

|||

||

|

|

Environments

UNALLOCATE.

ExampleSPACE_RELEASE=DISABLE

In the example, SPACE_RELEASE is set to DISABLE, therefore, AdvancedAllocation Management will not release any space.

TERM_ALLOCThe TERM_ALLOC keyword specifies that an allocation should be forced to failwhen the selection criteria in a RULEDEF have been met.

Syntax

��DISABLE

TERM_ALLOC= ENABLE

��

TERM_ALLOC=ENABLE | DISABLE

Operands

ENABLEThe current allocation should be forced to fail.

DISABLEThe current allocation should be processed normally.

Note: When set to ENABLE, Advanced Allocation Management fails the allocationby simulating an authorization failure which varies based upon the SMSmanagement status of the data set as well as whether or not it is a VSAMdata set:v For a non-SMS, non-VSAM data set, the allocation will be failed with the

message: IEF720I JJHTESTZ ALLOCATE ddname - USER NOT AUTHORIZED TODEFINE THIS DATA SET

For a batch job this will result in a JCL error and the failure of the job.v For a non-SMS, VSAM data set, the DEFINE will be failed with the

messages:IDC3036I DATA SET COULD NOT BE DEFINED TO SECURITY SUBSYSTEM

IDC3007I ** VSAM CATALOG RETURN CODE IS 118

v For an SMS, non-VSAM data set, the allocation will be failed with themessage:IEF344I JJHTESTZ ALLOCATE ddname - ALLOCATION FAILED DUE TO DATAFACILITY SYSTEM ERROR

v For an SMS, VSAM data set, the allocation will be failed with themessage:IDC3932I STORAGE MANAGEMENT SUBSYSTEM CALL FAILED. REASON CODE WAS17061


|

In all cases, regardless of the setting of the MSG_LEVEL option, AdvancedAllocation Management always displays the following message when anallocation is failed:

GLO2999I ALLOCATION TERMINATED AS REQUESTED BY RULEDEF LINE nnnnn -ssid

where nnnnn is the RULEDEF line number associated with theTERM_ALLOC function and ssid is the Advanced Allocation ManagementSubsystem Identification. This message will be followed by messageGLO2123I which fully identifies the data set. In addition, if SMF recording isenabled, an SMF record will be created documenting the failure.

Default

DISABLE.

Environments

ACS, ALLOCATE, CATCHECK, STOW, and UNALLOCATE.

ExampleTERM_ALLOC=ENABLE

In the example, the current allocation will be forced to fail.

VOL_ADDThe VOL_ADD keyword specifies whether or not to add additional volumes whenan out-of-space condition occurs and no more volumes are available as specified inthe original allocation.

Syntax

��DISABLE

VOL_ADD= ENABLE

��

VOL_ADD=ENABLE | DISABLE

Operands

ENABLEAdd additional volumes.

DISABLEDo not add additional volumes.

To locate a suitable volume, Advanced Allocation Management searches thevolume groups specified using the VOL_ADD_UNIT, VOL_ADD_VSER,VOL_ADD_VGRP, and VOL_ADD_SGRP keywords. Advanced AllocationManagement searches all of these volume groups until it finds the best candidate.

VOL_ADD will search for a default volume group when:v you explicitly specify a volume group, or


|

|

|

|

v you specify VOL_ADD and you do not specify values for the VOL_ADD_UNIT,VOL_ADD_VSER and VOL_ADD_VGRP keywords.

VOL_ADD will find a default volume group based upon either the first, or current,volser.

Note: When specifying explicit volsers for a data set and one of the non-firstvolumes contains no free space when an extend to a new volume occurs,end of volume processing normally produces an E37 abend. If you wantAdvanced Allocation Management to skip the volume with no free spaceand continue processing by trying the next explicitly specified volume or byadding a new volume using the VOL_ADD function, you must specifyPRIM_REDUCE=(,ENABLE).

Figure 17 on page 140 shows the processing logic Advanced AllocationManagement uses to determine the best candidate:


Advanced Allocation Management searches volume groups specified

by VOL_ADD_UNIT, VOL_ADD_VSER, VOL_ADD_VGRP, and

VOL_ADD_SGRP keywords

Is the free extent >=

desired size?YES

NO

*Does the second

operand of

PRIM_REDUCE =

ENABLE? YES

NO

Does

VOL_ADD_PROMPT=

ENABLE?

YES

NO

Advanced Allocation

Management prompts

the operator to specify

a volume

Does the volume have

sufficient free space?

Advanced Allocation

Management uses the

best free extent

located

The largest extent is

used (limited by the

PRIM_REDUCE_LIM

value)

*Or, if Advanced

Allocation Management

has not found a free

extent...

YES

NO

Advanced Allocation Management prompts

the operator to specify a suitable volume

(or waits for the operator to cancel the

operation).

Use the specified

volume

The allocation is

allowed to fail

Did the operator reply

"CANCEL"?

YES NO

Advanced Allocation

Management will use

the SEC_REDUCE

function (if enabled)

Notes:

1. MVS data management does not support multiple volumes for:v PDSes (PDS and PDS/E)v Sequential (non-VSAM) multi-striped data sets

Figure 17. VOL_ADD keyword and associated processing logic


v VSAM temporary data setsv VIO data setsTherefore, the VOL_ADD function is not supported for these data sets.

2. For SMS data sets, SMS chooses the volume based on its own internalconstructs (Advanced Allocation Management has no influence orchoice in the volumes used). Therefore, volume groups are not usedand the VOL_ADD_LIM, VOL_ADD_PROMPT, VOL_ADD_SGRP,VOL_ADD_UNIT, VOL_ADD_VGRP, VOL_ADD_VSER,VOL_ADD_ALGORITHM, VOL_ADD_MOUNT_USAGE, andVOL_ADD_VGRP_SEARCH. keywords do not apply.

3. Due to integrity considerations, Advanced Allocation Management willnot perform a VOL_ADD if more than one DCB is opened against aDDNAME — or if more than one DDNAME is assigned to the samedata set name.

4. When Advanced Allocation Management processes a VSAM cluster, allAIXes within the upgrade set for the cluster will also be handled whenend-of-volume is reached for the AIX.

Default

DISABLE.

Environments

EXTEND.

Related keywords

VOL_ADD_ALGORITHM, VOL_ADD_LIM, VOL_ADD_MOUNT_USAGE,VOL_ADD_PROMPT, VOL_ADD_SGRP, VOL_ADD_UNIT, VOL_ADD_VGRP,VOL_ADD_VSER, and VOL_ADD_VGRP_SEARCH.

ExampleVOL_ADD=ENABLE

In the example, VOL_ADD is set to ENABLE, therefore, Advanced AllocationManagement will add additional volumes when an out-of-space condition occursand no more volumes are available as specified in the original allocation.

VOL_ADD_ALGORITHMThe VOL_ADD_ALGORITHM keyword specifies a volume selection algorithm touse when extending to a new volume.

Syntax

��LARGESTSINGLE

VOL_ADD_ALGORITHM= BESTFITFIRSTMOSTFREESPACEPERFORMANCE

��


|||

|

|

|

VOL_ADD_ALGORITHM=BESTFIT | FIRST | LARGESTSINGLE |MOSTFREESPACE | PERFORMANCE

Operands

BESTFITSelect the volume(s) with a single extent in which the requested amount isclosest to the requested primary allocation quantity (for VSAM data sets) orthe secondary allocation quantity (for non-VSAM data sets) without being lessthan the requested primary allocation quantity or secondary allocation quantity(as appropriate).

FIRSTSelect the first volume(s) with enough total freespace to satisfy the requestedallocation amount.

Note: The allocation amount might not be able to be satisfied because thefreespace needed might be spread out across more than five extents(which is the normal limit within allocation for satisfying a spacerequest). Therefore, you might need to specify PRIM_REDUCE to assistin making the allocation successful.

LARGESTSINGLESelect the volume(s) with the largest single free extent.

Note: Advanced Allocation Management selects a volume with the largestsingle extent. This does not mean that the volume has enough space tosatisfy the requested amount — it simply indicates it is the volume withthe largest single extent. Therefore, you might need to use thePRIM_REDUCE function to handle those situations where the selectedvolume does not have adequate space available.

MOSTFREESPACESelect the volume with the most available freespace. The most freespace isdefined as the total amount of free cylinders or tracks on the volumedepending upon the allocation unit used. If cylinder allocation is specified, thetotal number of free cylinders is considered. Otherwise, the total number offree tracks is considered.

PERFORMANCESelect the volume with the lowest fragmentation index.

Default

LARGESTSINGLE.

Environments

EXTEND.

Related keywords

VOL_ADD, VOL_ADD_LIM, VOL_ADD_MOUNT_USAGE, VOL_ADD_PROMPT,VOL_ADD_SGRP, VOL_ADD_UNIT, VOL_ADD_VGRP,VOL_ADD_VGRP_SEARCH, and VOL_ADD_VSER.


ExampleVOL_ADD_ALGORITHM=MOSTFREESPACE

In the example, the volume with most available freespace will be selected.

VOL_ADD_LIMThe VOL_ADD_LIM keyword specifies the maximum number of volumes a dataset is allowed to have when the VOL_ADD function is enabled.

Syntax

��VOL_ADD_LIM=xxx

��

VOL_ADD_LIM=xxx

Where:

xxxIs the maximum number of volumes a data set is allowed to have when theVOL_ADD function is enabled. The valid range is 0-255.

Note: The VOL_ADD_LIM keyword is associated with the VOL_ADD keyword.You must specify VOL_ADD=ENABLE to implement this function.

Default

The default value is 0 (zero), which means there is no limit to the maximumnumber of volumes except those implemented by z/OS.

Environments

EXTEND.

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_MOUNT_USAGE,VOL_ADD_PROMPT, VOL_ADD_SGRP, VOL_ADD_UNIT, VOL_ADD_VGRP,VOL_ADD_VGRP_SEARCH, and VOL_ADD_VSER.

ExampleVOL_ADD_LIM=10

In the example, VOL_ADD_LIM is set to 10, therefore, Advanced AllocationManagement will not allow the data set to exist on more than 10 volumes. Thus,when VOL_ADD_LIM is set to 10, the data set can only have 10 volumes (total)which means you can only extend to an additional 9 volumes before AdvancedAllocation Management allows the job to abend.

VOL_ADD_MOUNT_USAGEThe VOL_ADD_MOUNT_USAGE keyword acts as a filter for the volumes selectedas part of the normal volume selection process used by Advanced AllocationManagement.


|

||

That is, Advanced Allocation Management selects a group of candidate volumesbased upon the VOL_ADD_VGRP, VOL_ADD_UNIT, VOL_ADD_VSER keywordsettings and default volume group. The VOL_ADD_MOUNT_USAGE keywordvalue is then applied to that set of volumes to create a subset of eligible candidatevolumes for the VOL_ADD function.

Syntax

��ANY

VOL_ADD_MOUNT_USAGE= CURRENTPRIVATEPUBLICSTORAGE

��

VOL_ADD_MOUNT_USAGE=ANY | CURRENT | PRIVATE | PUBLIC |STORAGE

Operands

ANYSpecifies that any mount usage attribute is acceptable.

CURRENTSpecifies that the mount usage attribute of the selected volume should be thesame as the mount usage attribute of the current volume of the data set. Thecurrent volume of a data set is the volume which has just causedend-of-volume processing to occur resulting in the invocation of theVOL_ADD function.

PRIVATE, PUBLIC, and STORAGEThe PRIVATE, PUBLIC, and STORAGE keyword values are equivalent to themount usage attribute for a volume as defined in the Unit Control Block for adevice — and as defined by z/OS.

Only one keyword value can be specified. For example:

Valid: VOL_ADD_MOUNT_USAGE=STORAGE

Not valid: VOL_ADD_MOUNT_USAGE=STORAGE,PUBLIC

Default

ANY.

Environments

EXTEND.

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_LIM, VOL_ADD_PROMPT,VOL_ADD_SGRP, VOL_ADD_UNIT, VOL_ADD_VGRP,VOL_ADD_VGRP_SEARCH, and VOL_ADD_VSER.


|

ExampleINCLUDE JOBNAME=JJHTEST01

VOL_ADD=ENABLEVOL_ADD_VGRP=GROUP01VOL_ADD_MOUNT_USAGE=STORAGE

In the example, when a VOL_ADD is to be performed for a non-SMS-manageddata set for job JJHTEST01, the volumes that will be considered by AdvancedAllocation Management will be all of the volumes with a mount usage attribute ofSTORAGE in both the volume group named GROUP01 and the default volumegroup.

VOL_ADD_PROMPTThe VOL_ADD_PROMPT keyword specifies whether or not to prompt theoperator by means of a WTOR (message GLO2137A) when a volume cannot befound to satisfy the VOL_ADD function.

Syntax

��DISABLE

VOL_ADD_PROMPT= ENABLE

��

VOL_ADD_PROMPT=ENABLE | DISABLE

Operands

ENABLEPrompt the operator.

DISABLEDo not prompt the operator.

Notes:

1. The VOL_ADD_PROMPT keyword is associated with the VOL_ADDkeyword. You must specify VOL_ADD=ENABLE to implement thisfunction.

2. This keyword does not apply to SMS data sets.

Default

DISABLE.

Environments

EXTEND.

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_LIM,VOL_ADD_MOUNT_USAGE, VOL_ADD_SGRP, VOL_ADD_UNIT,VOL_ADD_VGRP, VOL_ADD_VGRP_SEARCH, and VOL_ADD_VSER.

ExampleVOL_ADD_PROMPT=ENABLE


|

|

|

In the example, VOL_ADD_PROMPT is set to ENABLE, therefore, a WTOR willprompt the operator when a volume cannot be found to satisfy the VOL_ADDfunction.

VOL_ADD_SGRPThe VOL_ADD_SGRP keyword determines the default volume group AdvancedAllocation Management should use for VOL_ADD.

Syntax

��FIRST

VOL_ADD_SGRP= CURRENT

��

VOL_ADD_SGRP=FIRST | CURRENT

Operands


CURRENTSpecifies Advanced Allocation Management should use the volume groupassociated with the current (last) volume.

If you specify VOL_ADD_SGRP=CURRENT, Advanced AllocationManagement uses the current volume of the data set (which might be differentthan the first volume if the data set has more than one volume) to perform thesearch for the default volume group.

When you specify VOL_ADD_SGRP=CURRENT you do not to have to definea volume group using the VOL_ADD_VGRP keyword on the INCLUDEstatement.

FIRSTSpecifies Advanced Allocation Management should use the first volumeassigned to the data set to search the VGRPDEFS to locate a volume group touse. The first volume group found (which includes the first volume of the dataset) is used as the default volume group.

When searching for a volume for VOL_ADD, Advanced Allocation Managementconsiders all volumes in the default volume group as well as any other volumesthat are explicitly specified on the INCLUDE statement by the VOL_ADD_VGRP,VOL_ADD_UNIT and VOL_ADD_VSER keywords — before selecting a volume.Advanced Allocation Management uses the volume with the largest amount offreespace for the VOL_ADD. Advanced Allocation Management does not stopsearching volume groups when it locates a volume with a suitable amount of space(it continues to search all volumes from all volume groups and other sources forthe volume with the largest amount of freespace).

Notes:

1. The VOL_ADD_SGRP keyword is associated with the VOL_ADDkeyword. You must specify VOL_ADD=ENABLE to implement thisfunction.

2. The VOL_ADD_SGRP keyword does not apply to SMS data sets.


|

Default

FIRST.

Environments

EXTEND.

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_LIM,VOL_ADD_MOUNT_USAGE, VOL_ADD_PROMPT, VOL_ADD_UNIT,VOL_ADD_VGRP, VOL_ADD_VGRP_SEARCH, and VOL_ADD_VSER.

ExampleVOL_ADD_SGRP=CURRENT

In the example, the volume group associated with the current (last) volume will beused.

VOL_ADD_UNITThe VOL_ADD_UNIT keyword specifies esoteric unit names or generic nameswhich will be used in conjunction with the VOL_ADD keyword.

Syntax

��

�

,

VOL_ADD_UNIT=( uuuuuuuu )

��

VOL_ADD_UNIT=(uuuuuuuu,uuuuuuuu,.......)

Where:

uuuuuuuuIs a unit name. Each name (uuuuuuuu) can be a maximum of eight charactersin length.

Notes:

1. This keyword is associated with the VOL_ADD keyword. You mustspecify VOL_ADD=ENABLE to implement this function.


Default

None.

Environments

EXTEND.


|

|

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_LIM,VOL_ADD_MOUNT_USAGE, VOL_ADD_PROMPT, VOL_ADD_SGRP,VOL_ADD_VGRP, VOL_ADD_VGRP_SEARCH, and VOL_ADD_VSER.

ExampleVOL_ADD_UNIT=RDVOLS

In the example, VOL_ADD_UNIT is set to RDVOLS, therefore, AdvancedAllocation Management will use the unit name RDVOLS in conjunction with theVOL_ADD keyword to determine where Advanced Allocation Management shouldobtain additional volumes.

VOL_ADD_VGRPThe VOL_ADD_VGRP keyword specifies a name of a volume group (or groups)which will be used in conjunction with the VOL_ADD keyword.

Syntax

��

�

,

VOL_ADD_VGRP=( pppppppp )

��

VOL_ADD_VGRP=(pppppppp,pppppppp,......)

Where:

ppppppppIs a name of a volume group. Each volume group name (pppppppp) can be amaximum of eight characters in length.

Notes:



Default

None.

Note: When no volume group is defined, Advanced Allocation Management usesa default volume group. The default volume group is chosen using eitherthe first or current volser for a data set as specified (or defaulted in theVOL_ADD_SGRP keyword). Advanced Allocation Management will use theparticular volume to search the volume group definitions in order (from firstto last) looking for a volume group which contains the volser. That volumegroup will be used as the default volume group from which a volume willbe selected for volume addition based upon the selected or defaultedVOL_ADD_ALGORITHM.


|

|

|||||||||

Environments

EXTEND.

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_LIM,VOL_ADD_MOUNT_USAGE, VOL_ADD_PROMPT, VOL_ADD_SGRP,VOL_ADD_UNIT, VOL_ADD_VGRP_SEARCH, and VOL_ADD_VSER.

ExampleVOL_ADD_VGRP=(VGRP0001,VGRP0002)

In the example, VOL_ADD_VGRP lists the volume groups VGRP0001 andVGRP0002, therefore, these volume group will be used in conjunction with theVOL_ADD keyword to determine which volume groups Advanced AllocationManagement should use to obtain additional volumes.

VOL_ADD_VGRP_SEARCHThe VOL__ADD_VGRP_SEARCH keyword specifies the volume selection volumegroup search method when extending to a new volume.

Syntax

��ALL

VOL_ADD_VGRP_SEARCH= FIRST

��

VOL__ADD_VGRP_SEARCH=ALL | FIRST

Operands


ALLSearch all volume groups for a suitable volume.

FIRSTStop searching for volumes after the volume group that was just searched hasa volume in it that meets the criterion established by theVOL_ADD_VGRP_ALGORITHM keyword.

Note: Other than BESTFIT (when all volumes requested are able to be satisfiedusing the BESTFIT algorithm) there is no guarantee that the spacerequested will be available. For example, if you specifyVOL_ADD_VGRP_ALGORITHM= LARGESTSINGLE and AdvancedAllocation Management selects a volume with the largest single extentin a volume group, that does not mean that the volume has enoughspace to satisfy the requested amount, it simply means it is the volumewith the largest single extent. Therefore, you might need to use thePRIM_REDUCE function to handle those situations where the selectedvolume does not have adequate space available.


|

Default

ALL.

Environments

EXTEND.

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_LIM,VOL_ADD_MOUNT_USAGE, VOL_ADD_PROMPT, VOL_ADD_SGRP,VOL_ADD_UNIT, VOL_ADD_VGRP, and VOL_ADD_VSER.

ExampleVOL__ADD_VGRP_SEARCH=FIRST

In the example, Advanced Allocation Management will stop searching for volumesif a suitable volume exists in the volume group in which it is currently searching.

VOL_ADD_VSERThe VOL_ADD_VSER keyword specifies the volume serial number (or numbers)that are used in conjunction with the VOL_ADD keyword.

Syntax

��

�

,

VOL_ADD_VSER=( vvvvvv )

��

VOL_ADD_VSER=(vvvvvv,vvvvvv,.......)

Where:

vvvvvvIs a serial number. Each serial number (vvvvvv) can be a maximum of sixcharacters in length.

Notes:



Default

None.

Environments

EXTEND.


|

|

|

|

Related keywords

VOL_ADD, VOL_ADD_ALGORITHM, VOL_ADD_LIM,VOL_ADD_MOUNT_USAGE, VOL_ADD_PROMPT, VOL_ADD_SGRP,VOL_ADD_UNIT, VOL_ADD_VGRP, and VOL_ADD_VGRP_SEARCH.

ExampleVOL_ADD_VSER=(DASD01, DASD02)

In the example, VOL_ADD_VSER lists the volume serial numbers DASD01,DASD02, therefore, Advanced Allocation Management will use these volume serialnumbers in conjunction with the VOL_ADD keyword to determine whereAdvanced Allocation Management should obtain additional volumes.

Note: The order in which you specify the volume serial numbers does not affectprocessing.

WRITE_MSGThe WRITE_MSG keyword enables you to output a message upon execution of theactions for a RULEDEF.

Syntax

��

�

,

WRITE_MSG = ( msgtext )env

��

WRITE_MSG=(msgtext,env...)

Where:

msgtextSpecifies the message to be written to the destination specified in theMSG_DESTINATION function. If blanks are included in the message, themessage text must be surrounded by double quotes. The maximum length ofthe message, including any quotes, is 120 characters.

env(Optional.) Specifies the environments within which the message should bedisplayed. You can specify 0–7 environment keywords. Valid options are:

ACSThe point in SMS processing directly following the assignment of one ormore of the SMS constructs of Data Class, Storage Class, ManagementClass, or Storage Group.

ALL(Default.) All points where Advanced Allocation Management interceptsprocessing.

ALLOCATEThe point in processing where a new data set is allocated (including VSAMand non-VSAM, SMS and non-SMS data sets).


|

CATCHECKThe point in allocation processing where the determination of the priorexistence of a data set is made. For SMS data sets, this point is just prior tothe allocation of a data set. For non-SMS data sets, this point can be justprior to the allocation of a data set — or at unallocation processing timeduring catalog disposition processing.

EXTENDThe point in processing where a new extent is added to a data set, eitheron the current volume or on a new volume (including volume addition).

STOWThe point in PDS processing when a new member is being added to a dataset and the directory is being updated.

UNALLOCATEThe point in processing where a data set is unallocated.

Note:

v The message text can contain certain symbolic variables which arereplaced at message generation time with the appropriate text. The totallength of the message, after the symbolic variables have been expanded,cannot exceed 120 characters. Any text exceeding the maximum lengthwill be truncated. Valid symbolic variables are:– &JB — Jobname.– &ST — Stepname.– &PS — Procedure stepname.– &DS — Data set name.– &DD — DDNAME.– &EV — Environment (displays the same values for Environment as

described above for env).– &LN — The RULEDEF line number associated with the RULEDEF

containing the WRITE_MSG keyword for which the selection criteriamatched.

– &SS — The Advanced Allocation Management SubsystemIdentification.

When the symbolic variables are replaced with actual values, any trailingblanks will be removed. If a symbolic variable does not have anassociated value (for example, Procedure Stepname), a single asterisk willbe displayed.If you want to include the "&" character in the message coding twoampersands in a row will result in the display of a single ampersand inthe output message.

v The specification of the first eight characters can take advantage of thesame rules used for other Advanced Allocation Management messages. Ifthe first three characters are "GLO" and the next four characters arenumeric characters, the eighth character can be used to define thecircumstances under which the message will be displayed:– If the eighth character is an "E", the message will always be displayed.– If the eighth character is an "I", the message will only be displayed if

the MSG_LEVEL function is set to ALL.– If the eighth character is set to "S", the message will always be

displayed and the "S" will be replaced with an "I".


If the first three characters are not "GLO" and the next four characters arenot numeric, the message will always be displayed.

v The message text can be continued from one line to another. To continuethe message text to another line, the text must be surrounded by quotes.Continue the text to (and including) column 72. On the next line, continuethe message text starting at column one.For example:12345678901234567890123456789012345678901234567890123456789012345678901234567890--------------------------------------------------------------------------------

INCLUDE JOBNAME=JJHTEST1WRITE_MSG="THIS VERY LONG SAMPLE MESSAGE TEXT IS GOING TO BE CONTINUED ON

THE NEXT LINE"

Default

ALL.

Environments


ExampleWRITE_MSG=("Do not allocate TEST data sets in VGRP=PROD")

In the example, the message: Do not allocate TEST data sets in VGRP=PROD willbe generated.


|

|


Chapter 11. Enhanced Allocation Management functionkeywords

Use Advanced Allocation Management Enhanced Allocation Management functionkeywords to set allocation attributes.

Note:

1. The underlined portion of the keyword indicates the minimallyacceptable abbreviation.

2. $NULL indicates that a particular attribute value should be set such thatit appears that it was not specified by the user.

3. The default listed is the default for the Advanced AllocationManagement keyword, not the default assigned to the attribute by theoperating system (unless otherwise specifically noted).

4. Where applicable, the JCL, IDCAMS, data, management and storageclass equivalents are provided. For the data, management, or storageclass equivalents— the field name from the appropriate ISMF panel thatis used to define the class is listed.

5. The use of numeric suffixes is permitted.6. When using the Enhanced Allocation Management functions, it is your

responsibility to ensure that the values are consistent and valid to theoperating system.

$DCOThe $DCO keyword specifies whether the data class override feature should beactive for all Advanced Allocation Management supported data class variables.$DCO specifies whether the data class values for various attributes should overrideany specified JCL or DEFINE specified values.

Syntax

��$DCO= CONDITIONAL

DISABLEUNCONDITIONAL

��

$DCO=CONDITIONAL | DISABLE | UNCONDITIONAL

Operands


CONDITIONALOnly override JCL or DEFINE values if the corresponding data class value isnot null.

DISABLETurn off data class override unless explicitly specified at the individual variablelevel.

155

UNCONDITIONALOverride the JCL or DEFINE values even if the corresponding data class valueis null (in which case the variable in the JCL or DEFINE will also be set as if ithad not been specified).

$DCO supports these values within the data class:v Access Biasv Data Control Interval Sizev Tape Compactionv Directory Blocksv DSNTYPEv Data Set Organizationv Record Organizationv Extended Addressabilityv Expiration Datev Control Interval Freespacev Control Area Freespacev FRLOGv Key Lengthv Key Offsetv Logstream IDv Record Lengthv Record Formatv Retention Periodv Reusev Xrgn Shareoptionv Xsys Shareoptionv Primary Quantityv Secondary Quantityv Space Allocation Units (AVGREC)v Spannedv Speed or Recoveryv Volume Count

Default

None.

Environments

ALLOCATE.

JCL equivalent

(Refer to each individual attribute supported by Advanced AllocationManagement.)

Example$DC0=C


In the example, only JCL or DEFINE values will be overridden if thecorresponding data class value is not null.

SET_ACCBIAS(VSAM only.) The SET_ACCBIAS keyword specifies the assigned VSAM SystemManaged Buffering specification.

Syntax

��SET_ACCBIAS= DO

DWSOSWSYSTEMUSER$DCOC$DCOU

��

SET_ACCBIAS=DO | DW | SO | SW | | SYSTEM | USER | $DCOC | $DCOU

Operands


DOSystem-managed buffering with direct optimization.

DWSystem managed buffering weighted for direct processing.

SOSystem-managed buffering with sequential optimization.

SWSystem-managed buffering weighted for sequential processing.

SYSTEMSystem managed buffering chooses the buffering technique.

USERSystem-managed buffering is not used.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD AMP=(’ACCBIAS=USER’)

Data class equivalent

Record Access Bias.

Chapter 11. Enhanced Allocation Management function keywords 157

Related selection criteria

ACCBIAS.

ExampleSET_ACCBIAS=DW

In the example, system managed buffering weighted for direct processing isspecified.

SET_ADISPThe SET_ADISP keyword specifies the abnormal termination disposition for a dataset.

Syntax

��SET_ADISP= CATLG

DELETEKEEPUNCATLG

��

SET_ADISP=CATLG | DELETE | KEEP | UNCATLG

Operands


CATLGThe specified abnormal disposition is DISP=(,,CATLG).

DELETEThe specified abnormal disposition is DISP=(,,DELETE).

KEEPThe specified abnormal disposition is DISP=(,,KEEP).

UNCATLGThe specified abnormal disposition is DISP=(,,UNCATLG).

Note:

1. Wildcard characters are not permitted.2. This keyword is not applicable to VSAM IDCAMS DEFINE statements.3. The system takes these defaults with the abnormal termination

disposition parameter:v If you omit the abnormal termination disposition, the default is the

disposition specified, or defaulted to, by the normal terminationdisposition. If the normal termination disposition is PASS, the defaultabnormal termination disposition is DELETE for a NEW data set (orKEEP for an existing data set).

v If you omit the DISP parameter, the default disposition is DELETE forthe abnormal termination disposition.


Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD DISP=(,,DELETE)


ADISP.

ExampleSET_ADISP=DELETE

In the example, the specified abnormal disposition is DISP=(,,DELETE).

SET_BLKSIZE(Non-VSAM only.) The SET_BLKSIZE keyword specifies the block size for a dataset.

Syntax

��SET_BLKSIZE= nnnnnnnnnn

��

SET_BLKSIZE=nnnnnnnnnn

Where:

nnnnnnnnnn is an integer (0-2147483647).

Note: If you set the this value to zero (0) you can cause the system to calculate thesystem-determined blocksize as determined under the circumstances.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD DD01 BLKSIZE=256000


BLKSIZE.


ExampleSET_BLKSIZE=256000

In the example, the specified blocksize is 256000.

SET_BUFSPC(VSAM only.) The SET_BUFSPC keyword specifies the buffer space specificationfor a data set.

Syntax

��SET_BUFSPC= nnnnnnnnnn

��

SET_BUFSPC=nnnnnnnnnn

Where:


Default

None.

Environments

ALLOCATE.

JCL equivalentDD DD01 AMP=(’BUFSP=128000’)

IDCAMS equivalentDEFINE CLUSTER(BUFFERSPACE(256000) ...)


BUFSPC.

ExampleSET_BUFSPC=256000

In the example, the buffer space specification is 256000.

SET_CISZ(VSAM only.) The SET_CISZ keyword specifies the control interval size for aVSAM cluster.

Syntax

��SET_CISZ= nnnnn

��


SET_CISZ=nnnnn

Where:

nnnnn is an integer (0-32768).

Default

None.

Environments

ALLOCATE.

AMS equivalentDEFINE CLUSTER (CONTROLINTERVALSIZE(8192) ....)


CISZ.

ExampleSET_CISZ=8192

In the example, the specified control interval size is 8192.

SET_CISZ_DATA(VSAM only.) The SET_CISZ_DATA keyword specifies the control interval size forthe data component of a VSAM cluster.

Syntax

��SET_CISZ_DATA= nnnnn

$DCOC$DCOU

��

SET_CISZ_DATA=nnnnn | $DCOC | $DCOU

Where:


Default

None.

Environments

ALLOCATE.

AMS equivalentDEFINE CLUSTER (....) DATA (CONTROLINTERVALSIZE(8192) ....)



CIsize Data.


CISZ_DATA.

ExampleSET_CISZ_DATA=8192

In the example, the specified control interval size for the data component is 8192.

SET_CISZ_INDEX(VSAM only.) The SET_CISZ_INDEX keyword specifies the control interval size forthe index component of a VSAM cluster.

Syntax

��SET_CISZ_INDEX= nnnnn

��

SET_CISZ_INDEX=nnnnn

Where:


Default

None.

Environments

ALLOCATE.

AMS equivalentDEFINE CLUSTER (....) DATA(....) INDEX(CONTROLINTERVALSIZE(8192) ....)


CIsize Data.


CISZ_DATA.

ExampleSET_CISZ_INDEX=8192

In the example, the specified control interval size for the index component is 8192.


SET_CONTIGUOUS(Non-VSAM disk data sets only.) The SET_CONTIGUOUS keyword specifieswhether the CONTIG option should be specified when allocating a new data set.

Syntax

��SET_CONTIGUOUS= YES

NO

��

SET_CONTIGUOUS=YES | NO

Operands

YESCONTIG should be specified.

NOCONTIG should not be specified.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD SPACE=(CYL,(1,1),,CONTIG)


CONTIGUOUS.

ExampleSET_CONTIG=Y

In the example, CONTIG should be specified when allocating a new data set.

SET_DATACLASThe SET_DATACLAS keyword specifies the SMS data class to be assigned to adata set.

Syntax

��SET_DATACLAS= dataclas

$NULL

��

SET_DATACLAS=dataclas | $NULL

Where:


dataclas is the 1-8 character SMS data class name. Wildcard characters are notpermitted.

Note:

v As permitted in SMS, you can assign a data class to a non-SMS data set.v This keyword requires additional calls to SMS Configuration Services and

its presence anywhere in the RULEDEFS member can cause a measurableincrease in CPU time for all tasks in the system, especially thoseperforming large numbers of allocations. Therefore, consideration shouldbe used when specifying this keyword in your rule definition member.

Default

None.

Environments

ACS.

JCL equivalentDD01 DD DATACLAS=SMALL

IDCAMS equivalentDEFINE CLUSTER (NAME(...) DATACLASS(SMALL) ...)


DATACLAS.

ExampleSET_DATACLAS=SMALL

In the example, "SMALL" is the SMS data class name to be assigned to the dataset.

SET_DEFERMOUNTThe SET_DEFERMOUNT keyword specifies whether the DEFER option should bespecified for the UNIT keyword.

Syntax

��SET_DEFERMOUNT= YES

NO

��

SET_DEFERMOUNT=YES | NO

Operands

YESDEFER should be specified.

NODEFER should not be specified.


|

|||||

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD UNIT=(3490,,DEFER)


DEFERMOUNT.

ExampleSET_DEFER=Y

In the example, the DEFER option should be specified for the UNIT keyword.

SET_DIRBLKS(PDS and PDS/E data sets only.) The SET_DIRBLKS keyword specifies the numberof directory blocks assigned to a PDS or PDS/E data set.

Syntax

��SET_DIRBLKS= nnnnn

$DCOC$DCOU

��

SET_DIRBLKS=nnnnn | $DCOC | $DCOU

Where:

nnnnn is an integer (0-65535) that specifies the number of directory blocks.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD SPACE=(,(,,120))


Space Directory.



DIRBLKS.

ExampleSET_DIRBLKS=120

In the example, the number of directory blocks assigned is 120.

SET_DSNAME_TYPEThe SET_DSNAME_TYPE keyword specifies the type of data set.

Syntax

��SET_DSNAME_TYPE= BASIC

EXTPREFEXTREQHFSLARGELIBPDS$DCOC$DCOU

��

SET_DSNAME_TYPE=BASIC | EXTPREF | EXTREQ | HFS | LARGE | LIB |PDS | $DCOC | $DCOU

Operands


BASICAllows the specification of less than 65535 tracks for the primary andsecondary allocation for non-VSAM data sets.

EXTPREFAn extended format is preferred if the data set is VSAM, sequential, or ifDSORG is omitted from all sources.

EXTREQExtended format is required if the data set is VSAM, sequential, or if DSORGis omitted from all sources.

HFSHierarchical file system data set (HFS data set).

LARGEAllows the specification of more than 65535 tracks for the primary andsecondary allocation for non-VSAM data sets.

LIBPDSE data set.

PDSPartitioned data set (PDS).


Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD DSNTYPE=HFS


Data Set Name Type and If Ext parameters.


DSNAME_TYPE.

ExampleSET_DSNAME_TYPE=LIB

In the example, the data set type is PDSE.

SET_DSORGThe SET_DSORG keyword specifies the data set organization for non-VSAM datasets and the record organization for VSAM data sets.

Syntax

��SET_DSORG= DA

ESDSKSDSLDSPOPSRRDS$DCOC$DCOU

��

SET_DSORG=DA | ESDS | KSDS | LDS || PO | PS | RRDS | $DCOC | $DCOU

Operands


DADirect access.

ESDSVSAM entry-sequenced data set.

KSDSVSAM key-sequenced data set.


|

||||||||||||||||||||||||||||||||||||||||

|

|

|

|

||

||

||

LDSVSAM linear data set.

POPartitioned organized.

PS Physical sequential.

RRDSEither a VSAM variable-length or fixed-length relative-record data set.

Notes:

1. Wildcard characters are not permitted.2. The $DCOU and $DCOC keywords are only valid for KSDS, ESDS,

RRDS, and LDS VSAM data sets.3. The Enhanced Allocation Management function keywords pertaining to

VSAM record organization (KSDS, ESDS, RRDS, LDS) do not apply toVSAM IDCAMS DEFINEs, however, they are applicable to VSAM datasets being created through JCL.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD DSORG=PSDD01 DD RECORG=KS


Recorg.


DSORG.

ExampleSET_DSORG=PS

In the example, the specified organization is physical sequential.

SET_EXPDATEThe SET_EXPDATE keyword specifies an expiration date for a data set.

Syntax

��SET_EXPDATE= yyyyddd

$DCOC$DCOU

��


||

||

||

||

|

|

||

||||

|

SET_EXPDATE=yyyyddd | $DCOC | $DCOU

Where:

yyyyddd is a Julian date and yyyy is a four digit year and ddd is a three digit day.

Note: If you specify SET_EXPDATE and SET_RETPD, SET_EXPDATE takesprecedence.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD EXPDT=2009/003

IDCAMS equivalentDEFINE CLUSTER(TO(2009003) ..)


Retpd or Expdt.


EXPDATE.

ExampleSET_EXPDATE=2009003

In the example, the expiration date is the third day of 2009.

SET_EXTADDR(VSAM data sets only.) The SET_EXTADDR keyword specifies the ExtendedAddressability attribute for a VSAM cluster.

Syntax

��SET_EXTADDR= YES

NO$DCOC$DCOU

��

SET_EXTADDR=YES | NO | $DCOC | $DCOU

Note: For this VSAM option, the ISMF Data Class Define panel always defaultsthe value for this field to "N" if a blank is specified. Therefore, because avalue is always defined, the $DCOC option acts the same as the $DCOUoption.


Operands

YESExtended addressability should be defined for the data set.

NOExtended addressability should not be defined for the data set.

Note: The system will only honor EXTADDR=YES if the cluster is also defined asan extended format data set.

Default

SMS defaults to NO for Extended Addressability.

Environments

ALLOCATE.


Extended Addressability.


EXTADDR.

ExampleSET_EXTADDR=N

In the example, extended addressability should not be defined for the data set.

SET_FILESEQNO(Tape data sets only.) The SET_FILESEQNO keyword specifies a file sequencenumber of a data set.

Syntax

��SET_FILESEQNO= nnn

��

SET_FILESEQNO=nnn

Where:

nnn is the sequence number (0-255) of the data set on the tape.

Default

None.

Environments

ALLOCATE.


JCL equivalentDD01 DD LABEL=(4,)


FILESEQNO.

ExampleSET_FILESEQNO=4

In the example, the file sequence number is 4.

SET_FRLOG(VSAM data sets only.) The SET_FRLOG keyword specifies whether VSAM batchlogging should be specified for a VSAM data set.

Syntax

��SET_FRLOG= ALL

NONEREDOUNDO$DCOC$DCOU

��

SET_FRLOG=ALL | NONE | REDO | UNDO | $DCOC | $DCOU

Operands


ALLBoth backward and forward recovery should be enabled.

NONEThe VSAM batch logging option should not be performed.

REDOForward recovery should be enabled.

UNDOBackward recovery should be enabled.

Default

None. (This keyword has no default.)

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CL (FRLOG(REDO) ...)



FRlog.


FRLOG.

ExampleSET_FRLOG=REDO

In the example, forward recovery should be enabled.

SET_FSPC_CA(VSAM data sets only.) The SET_FSPC_CA keyword specifies the freespacepercentage for the control area of a VSAM data set.

Syntax

��SET_FSPC_CA= nnn

$DCOC$DCOU

��

SET_FSPC_CA=nnn | $DCOC | $DCOU

Where:

nnn is an integer that specifies the free space percentage (0-100).

Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CL (FREESPACE(0 10) ...)


% Freespace CA.


FSPC_CA.

ExampleSET_FSPC_CA=10

In the example, the specified free space percentage is 10 (10%).


SET_FSPC_CI(VSAM data sets only.) The SET_FSPC_CI keyword specifies the freespacepercentage for the control interval of a VSAM data set.

Syntax

��SET_FSPC_CI= nnn

$DCOC$DCOU

��

SET_FSPC_CI=nnn | $DCOC | $DCOU

Where:

nnn is an integer that specifies the free space percentage (0-100).

Default

None.

Environments

ALLOCATE.



% Freespace CI.


FSPC_CI.

ExampleSET_FSPC_CI=10

In the example, the specified free space percentage is 10 (10%).

SET_ILOAD(VSAM data sets only.) The SET_ILOAD keyword specifies the initial load optionto be specified for a VSAM data set.

Syntax

��SET_ILOAD= RECOVERY

SPEED$DCOC$DCOU

��


SET_ILOAD=SPEED | RECOVERY | $DCOC | $DCOU

Note: For this VSAM option, the ISMF Data Class Define panel always defaultsthe value for this field to "R" (Recovery) if a blank is specified. Therefore,because a value is always defined, the $DCOC option acts the same as the$DCOU option.

Operands


RECOVERYThe RECOVERY option should be specified.

SPEEDThe SPEED option should be specified.

Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CLUSTER (RECOVERY ...)DEFINE CLUSTER (SPEED ...)


Initial Load.


ILOAD.

ExampleSET_ILOAD=S

In the example, the initial load option to be specified is the SPEED option.

SET_KEY_LEN(Key sequenced VSAM data sets only.) The SET_KEY_LEN keyword specifies thekey length of a key sequenced VSAM data set.

Syntax

��SET_KEY_LEN= nnn

$DCOC$DCOU

��

SET_KEY_LEN=nnn | $DCOC | $DCOU


Where:

nnn is the length of a key in the range of 1-255.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD KEYLEN=6,...

IDCAMS equivalentDEFINE CLUSTER(KEYS(8 ..) ...)


Keylen.


KEY_LEN.

ExampleSET_KEY_L=8

In the example, the specified key length is 8.

SET_KEY_OFF(Key sequenced VSAM data sets only.) The SET_KEY_OFF keyword specifies theoffset of the key in a key sequenced VSAM data set.

Syntax

��SET_KEY_OFF= nnn

$DCOC$DCOU

��

SET_KEY_OFF=nnnnn | $DCOC | $DCOU

Where:

nnnnn is the offset of the key (0-32767) within a data record.

Default

None.


Environments

ALLOCATE.

JCL equivalentDD01 DD KEYOFF=0,...

IDCAMS equivalentDEFINE CLUSTER(KEYS(... 12) ...)


Keyoff.


KEY_OFF.

ExampleSET_KEY_OFF=12

In the example, the specified offset of the key is 12.

SET_LOGSTREAM_ID(SMS-managed VSAM data sets only.) The SET_LOGSTREAM_ID keywordspecifies the name of a logstream data set for an SMS-managed VSAM data set.

Syntax

��SET_LOGSTREAM_ID= logstream_id

$DCOC$DCOU

��

SET_LOGSTREAM_ID=logstream_id | $DCOC | $DCOU

Where:

logstream_id is a string of 1-26 characters naming the logstream. Wildcardcharacters are not permitted.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD LGSTREAM=PAY.STREAM


IDCAMS equivalentDEFINE CLUSTER(LOGSTREAMID(PAY.STREAM) ...)


Logstream ID.


LOGSTREAM_ID.

ExampleSET_LOGSTREAM_ID=PAY.STREAM

In the example, the name of the logstream data set is PAY.STREAM.

SET_LRECLThe SET_LRECL keyword specifies the record length of a data set.

Syntax

��SET_LRECL=( nnnnn )

$DCOC , nnnnn$DCOU

��

SET_LRECL=(nnnnn | $DCOC | $DCOU,nnnnn)

Where:

nnnnn is an integer (1-32767) that defines the length of a non-VSAM record or theaverage and maximum record sizes of a VSAM data set.

Note the following:v For non-VSAM data sets the second length is ignored.v When using the SET_LRECL keyword to set both average and maximum

LRECLs for a VSAM data set and the values are not the same, the values thatare stored in the catalog (and those reported if a LISTCAT is subsequentlyperformed), will each be two greater than the values specified. This is normaland is the same as if the RECORDSIZE parameter were coded on a VSAMDEFINE with two differing values (and Advanced Allocation Management wasnot processing the data set).

v The second LRECL set of parameters in the SET_LRECL function only pertain toIDCAMS-based VSAM DEFINEs. So they are ignored for JCL-based definition ofVSAM data sets.

Default

None.

Environments

ALLOCATE.


JCL equivalentDD01 DD LRECL=80,....

IDCAMS equivalentDEFINE CL (RECORDSIZE(80 120) ...)


Lrecl.


LRECL.

ExampleSET_LRECL=(80,,120)

SET_MGMTCLAS(SMS-managed data sets only.) The SET_MGMTCLAS keyword specifies the SMSmanagement class to be assigned to an SMS data set.

Syntax

��SET_MGMTCLAS= mgmtclas

$NULL

��

SET_MGMTCLAS=mgmtclas | $NULL

Where:

mgmtclas is the 1-8 character name assigned to the SMS management class.Wildcard characters are not permitted.

Note: This keyword requires additional calls to SMS Configuration Services and itspresence anywhere in the RULEDEFS member can cause a measurableincrease in CPU time for all tasks in the system, especially those performinglarge numbers of allocations. Therefore, consideration should be used whenspecifying this keyword in your rule definition member.

Default

None.

Environments

ACS.

JCL equivalentDD01 DD MGMTCLAS=STANDARD

IDCAMS equivalentDEFINE CLUSTER(MANAGEMENTCLASS(LONGTERM) ...)


|||||


MGMTCLAS.

ExampleSET_MGMTCLAS=TSO

In the example, the SMS management class to be assigned is TSO.

SET_NDISPThe SET_NDISP keyword specifies the normal termination disposition for a dataset.

Syntax

��SET_NDISP= CATLG

DELETEKEEPPASSUNCATLG

��

SET_NDISP=CATLG | DELETE | KEEP | PASS | UNCATLG

Operands


CATLGThe specified or defaulted normal disposition is DISP=(,CATLG).

DELETEThe specified or defaulted normal disposition is DISP=(,DELETE).

KEEPThe specified or defaulted normal disposition is DISP=(,KEEP).

PASSThe specified or defaulted normal disposition is DISP=(,PASS).

UNCATLGThe specified or defaulted normal disposition is DISP=(,UNCATLG).

Notes:

1. The SET_NDISP keyword does not apply to VSAM IDCAMS DEFINEstatements.

2. The system takes the following defaults with the normal terminationdisposition parameter:v If you omit the normal termination disposition, the default is

DELETE for a NEW data set and KEEP for an existing data set.v If you omit the DISP parameter, the default disposition is DELETE for

the normal termination disposition.

Default

None.


|

Environments

ALLOCATE.

JCL equivalentDD01 DD DISP=(,DELETE,)


NDISP.

ExampleSET_NDISP=CATLG

In the example, the specified or defaulted normal disposition is DISP=(,CATLG).

SET_NUMVOLS(Only applies to VSAM DEFINES.) The SET_NUMVOLS keyword specifies thenumber of volumes to be defined at the cluster level for a VSAM DEFINE.

Syntax

��SET_NUMVOLS= nn

$DCOC$DCOU

��

SET_NUMVOLS=nn | $DCOC | $DCOU

Where:

nnn is an integer (0-59) that specifies the number of volumes.

Note:

v If you specify SET_NUMVOLS=$DCOU and the DATACLAS VolumeCount value is null, the override will not be performed.

v For non-SMS managed data sets, SET_NUMVOLS is only effective if AVSis set to ENABLE.

v For non-SMS managed data sets, IDCAMS requires the specification of theVOLUMES parameter when defining a data set. When usingSET_NUMVOLS this parameter must still be defined, but any VOLSERcan be specified since it will be overridden by AVS processing.

Default

None.

Environments

ALLOCATE


IDCAMS equivalentDEFINE CLUSTER(VOLUMES(VOL001 VOL002) ...)DEFINE CLUSTER(VOLUMES(* * * *) ...)


Volume Count.


NUMVOLS.

ExampleSET_NUMVOLS=2

In the example, the number of volumes to be defined is 2.

SET_NUMVOLS_DATA(Only applies to VSAM DEFINES.) The SET_NUMVOLS_DATA keyword specifiesthe number of volumes to be defined for the data component of a VSAM cluster.

Syntax

��SET_NUMVOLS_DATA=nn

��

SET_NUMVOLS_DATA=nn

Where:

nn is an integer (0-59) that specifies the number of volumes.

Default

None.

Environments

ALLOCATE

IDCAMS equivalentDEFINE CLUSTER(...) DATA(VOLUMES(VOL001 VOL002) ...)DEFINE CLUSTER(...) DATA(VOLUMES(* * * *) ...)


NUMVOLS_DATA.

ExampleSET_NUMVOLS_DATA=2



SET_NUMVOLS_INDEX(VSAM DEFINES only.) The SET_NUMVOLS_INDEX keyword specifies thenumber of volumes to be defined for the index component of a VSAM cluster. (Forinstances other than VSAM DEFINES use SET_VOLCT instead.)

Syntax

��SET_NUMVOLS_INDEX=nn

��

SET_NUMVOLS_INDEX=nn

Where:


Default

None.

Environments

ALLOCATE

IDCAMS equivalentDEFINE CLUSTER(...) INDEX(VOLUMES(VOL001 VOL002) ...)DEFINE CLUSTER(...) INDEX(VOLUMES(* * * *) ...)


NUMVOLS_INDEX.

ExampleSET_NUMVOLS_INDEX=2


SET_PQTYThe SET_PQTY keyword specifies the primary quantity value assigned to the dataset. For VSAM data sets this defines the primary quantity at the cluster level.

Syntax

��SET_PQTY= nnnnnnnn

$DCOC$DCOU$NULL

��

SET_PQTY=nnnnnnnn | $DCOC | $DCOU | $NULL

Where:


nnnnnnnn is an integer (0-16777215) that specifies the primary quantity for a dataset. For non-VSAM new data sets, nnnnnnnn is the actual amount requested. ForVSAM data sets nnnnnnnn is the requested primary quantity (the value isrepresented in space allocation units).

Note: The $DCOC and $DCOU keywords are only valid for a SPACEUNITS valueof RECU, RECK, or RECM.

See “Space parameter considerations” on page 92 for information about specifyingspace related keywords.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD SPACE=(...,(1))

IDCAMS equivalentDEFINE CLUSTER(CYLINDERS(1) ....)DEFINE CLUSTER(TRACKS(1) ....)DEFINE CLUSTER(RECORDS(1000) ....)DEFINE CLUSTER(MEGABYTES(2) ....)DEFINE CLUSTER(KILOBYTES(2048) ...)


Space Primary.


PQTY.

ExampleSET_PQTY=2048

In the example, the primary quantity value is 2048.

SET_PQTY_DATA(VSAM data sets only.) The SET_PQTY_DATA keyword specifies the primaryquantity value to be assigned to the data component of a VSAM data set.

Syntax

��SET_PQTY_DATA= nnnnnnnn

$NULL

��

SET_PQTY_DATA=nnnnnnnn | $NULL


Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested primary allocationquantity for the data component in the requested allocation units.

Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CLUSTER(...) DATA(CYLINDERS(1) ....)DEFINE CLUSTER(...) DATA(TRACKS(1) ....)DEFINE CLUSTER(...) DATA(RECORDS(1000) ....)DEFINE CLUSTER(...) DATA(MEGABYTES(2) ....)DEFINE CLUSTER(...) DATA(KILOBYTES(2048) ...)


PQTY_DATA.

ExampleSET_PQTY_DATA=2048


SET_PQTY_INDEX(VSAM data sets only.) The SET_PQTY_INDEX keyword specifies the primaryquantity value to be assigned to the index component of a VSAM data set.

Syntax

��SET_PQTY_INDEX= nnnnnnnn

$NULL

��

SET_PQTY_INDEX=nnnnnnnn | $NULL

Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested primary allocationquantity for the index component in the requested allocation units.

Default

None.

Environments

ALLOCATE.


JCL equivalentDEFINE CLUSTER(...) INDEX(CYLINDERS(1) ....)DEFINE CLUSTER(...) INDEX(TRACKS(1) ....)DEFINE CLUSTER(...) INDEX(RECORDS(1000) ....)DEFINE CLUSTER(...) INDEX(MEGABYTES(2) ....)DEFINE CLUSTER(...) INDEX(KILOBYTES(2048) ...)


PQTY_INDEX.

ExampleSET_PQTY_INDEX=2048


SET_RECFM(Non-VSAM data sets only.) The SET_RECFM keyword specifies the record formatfor a non-VSAM data set.

Syntax


��SET_RECFM= D

DADBDBADBSDBSADSDSAFFAFBFBAFBMFBSFBSAFBSMFBTFBTAFBTMFMFSFSAFSMFTFTAFTMUUAUMUTUTAUTMVVAVBVBAVBMVBSVBSAVBSMVBTVBTAVBTMVBSTVBSTAVBSTMVMVSVSAVSMVTVTAVTM$DCOC$DCOU

��

SET_RECFM=D | DA | DB | DBA | DBS | DBSA | DS | DSA | F | FA | FB |FBA | FBM | FBS | FBSA | FBSM | FBT | FBTA | FBTM | FM| FT | FTA |FTM | FS | FSA | FSM | U | UA | UM | UT | UTA | UTM | V | VA | VB |


VBA | VBM | VM | VBS | VBSA| VBSM | VBT | VBTA | VBTM | VBST |VBSTA | VBSTM | VS | VSA | VSM | VT | VTA| VTM | $DCOC | $DCOU

Operands

D ASCII variable-length.

DAASCII variable-length (ANSI format).

DBASCII variable-length (blocked).

DBAASCII variable-length (blocked, ANSI format).

DBSASCII variable-length (blocked, spanned).

DBSAASCII variable-length (blocked, spanned, ANSI format).

DSASCII variable-length (spanned).

DSAASCII variable-length (spanned, ANSI format).

F Fixed length.

FAFixed length (ANSI format).

FB Fixed length (blocked).

FBAFixed length (blocked, ANSI format).

FBMFixed length (blocked, machine code format).

FBSFixed length (blocked, standard blocks).

FBSAFixed length (blocked, standard blocks, ANSI format).

FBSMFixed length (blocked, standard blocks, machine code format).

FBTFixed length (blocked, track overflow).

FBTAFixed length (blocked, track overflow, ANSI format).

FBTMFixed length (blocked, track overflow, machine code format).

FMMachine code format.

FS Fixed length (standard blocks).

FSAFixed length (standard blocks, ANSI format).


FSMFixed length (standard blocks, machine code format).

FT Fixed length (track overflow).

FTAFixed length (track overflow, ANSI format).

FTMFixed length (track overflow, machine code format).

U Undefined-length.

UAUndefined-length (ANSI format).

UMUndefined-length (machine code format).

UTUndefined-length (track overflow).

UTAUndefined-length (track overflow, ANSI format).

UTMUndefined-length (track overflow, machine code format).

V Variable length.

VAVariable length (ANSI format).

VBVariable length (blocked).

VBAVariable length (blocked, ANSI format).

VBMVariable length (blocked, machine code format).

VBSVariable length (blocked, spanned).

VBSAVariable length (blocked, spanned, ANSI format).

VBSMVariable length (blocked, spanned, machine code format).

VBSTVariable length (blocked, spanned, track overflow).

VBSTAVariable length (blocked, spanned, track overflow, ANSI format).

VBSTMVariable length (blocked, spanned, track overflow, machine code format).

VBTVariable length (blocked, track overflow).

VBTAVariable length (blocked, track overflow, ANSI format).


VBTMVariable length (blocked, track overflow, machine code format).

VMVariable length (machine code format).

VSVariable length (spanned).

VSAVariable length (spanned, ANSI format).

VSMVariable length (spanned, machine code format).

VTVariable length (track overflow).

VTAVariable length (track overflow, ANSI format).

VTMVariable length (track overflow, machine code format).

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD RECFM=FB


Recfm.


RECFM.

ExampleSET_RECFM=FB

In the example, the record format is fixed length (blocked).

SET_RETPDThe SET_RETPD keyword specifies the retention period for a data set.

Syntax

��SET_RETPD= nnnn

$DCOC$DCOU

��


SET_RETPD=nnnn |$DCOC |$DCOU

Where:

nnnn is an integer (0-9999) that specifies the number of days to retain the data set.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD RETPD=100

IDCAMS equivalentDEFINE CLUSTER(FOR(200) ...)


Retpd or Expdt.


RETPD.

ExampleSET_RETPD=100

In the example, the retention period is 100 days.

SET_REUSE(VSAM data sets only.) The SET_REUSE keyword specifies whether the VSAMREUSE or NOREUSE option should be specified.

Syntax

��SET_REUSE= YES

NO$DCOC$DCOU

��

SET_REUSE=YES |NO |$DCOC |$DCOU

Note: For this VSAM option, the ISMF Data Class Define panel always requires avalue of either "Y' or "N". Therefore, because a value is always defined, the$DCOC option acts the same as the $DCOU option.


Operands

YESREUSE should be specified.

NONOREUSE should be specified.

Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CL (REUSE ....)DEFINE CL (NORUSE....)


Reuse.


REUSE.

ExampleSET_REUSE=YES

In the example, the VSAM REUSE option should be specified.

SET_SHROPT_XRGN(VSAM data sets only.) The SET_SHROPT_XGRN keyword specifies theshareoptions for cross-region sharing.

Syntax

��SET_SHROPT_XRGN= n

$DCOC$DCOU

��

SET_SHROPT_XRGN=n | $DCOC | $DCOU

Where:

n is an integer (1-4) that specifies the VSAM cross-region shareoption.

Default

None.


Environments

ALLOCATE.

IDCAMS equivalentDEFINE CL (SHAREOPTIONS(1) ...)


Shareoptions Xregion.


SHROPT_XRGN.

ExampleSET_SHROPT_XRGN=1

In the example, 1 is the specified VSAM cross-region shareoption.

SET_SHROPT_XSYS(VSAM data sets only.) The SET_SHROPT_XSYS keyword specifies theshareoptions for cross-system sharing.

Syntax

��SET_SHROPT_XSYS= n

$DCOC$DCOU

��

SET_SHROPT_XSYS=n | $DCOC | $DCOU

Where:

n is an integer (3 or 4) that specifies the VSAM cross-system shareoption.

Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CL (SHAREOPTIONS(. 3) ...)


Shareoptions Xsystem.



SHROPT_XSYS.

ExampleSET_SHROPT_XSYS=3

In the example, 3 is the specified VSAM cross-system shareoption.

SET_SPACEUNITSThe SET_SPACEUNITS keyword specifies the allocation unit type for a data set.

Syntax

��SET_SPACEUNITS=( AVGRECU , nnnnn )

AVGRECK , nnnnnAVGRECM , nnnnnBLK , nnnnnCYLKBMBRECORDSTRK$DCOC$DCOU$NULL

��

SET_SPACEUNITS=(AVGRECU | AVGRECK | AVGRECM | BLK | CYL | KB |MB | TRK | RECORDS | $DCOC | $DCOU | $NULL, nnnnn)

Operands

AVGRECUSpace is allocated in records with AVGREC=U specified.

AVGRECKSpace is allocated in records with AVGREC=K specified.

AVGRECMSpace is allocated in records with AVGREC=M specified.

Note: You can use the AVGRECU, AVGRECK, and AVGRECM operands witha VSAM DEFINE and it will function in an identical manner as theprocessing that occurs when AVGREC is specified in the Data Class.

BLKSpace is allocated in blocks.

nnnnnAn integer (0-65535) that specifies either the block size or record size whenallocations are made with the allocation space units of BLK or AVGRECU,AVGRECK, or AVGRECM respectively.

CYLSpace is allocated in cylinders.


KBSpace is allocated in kilobytes.

Note: This value only applies to IDCAMS DEFINEs.

MBSpace is allocated in megabytes.

Note: This value only applies to IDCAMS DEFINEs.

RECORDSSpace is allocated using the IDCAMS DEFINE CLUSTER RECORDS keyword.

TRKSpace is allocated in tracks.


Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD SPACE=(8000,(2000,200))

IDCAMS equivalentDEFINE CLUSTER(CYLINDERS(...) ....)DEFINE CLUSTER(TRACKS(...) ....)DEFINE CLUSTER(RECORDS(...) ....)DEFINE CLUSTER(MEGABYTES(...) ....)DEFINE CLUSTER(KILOBYTES(...) ...)


Space Avgrec.


SPACEUNITS.

ExampleSET_SPACEU=CYL

In the example, space is allocated in cylinders.

SET_SPACEUNITS_DATA(VSAM data sets only.) The SET_SPACEUNITS_DATA keyword specifies theallocation units for the data component of a VSAM data set.


Syntax

��SET_SPACEUNITS_DATA= CYL

KBMBRECORDSTRK$NULL

��

SET_SPACEUNITS_DATA=CYL | KB | MB | RECORDS | TRK | $NULL

Operands




RECORDSSpace is allocated in records.


Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CLUSTER(...) DATA(CYLINDERS(...) ....)DEFINE CLUSTER(...) DATA(TRACKS(...) ....)DEFINE CLUSTER(...) DATA(RECORDS(...) ....)DEFINE CLUSTER(...) DATA(MEGABYTES(...) ....)DEFINE CLUSTER(...) DATA(KILOBYTES(...) ...)


SPACEUNITS_DATA.

ExampleSET_SPACEUNITS_D=KB

In the example, space is allocated in kilobytes.

SET_SPACEUNITS_INDEX(VSAM data sets only.) The SET_SPACEUNITS_INDEX keyword specifies theallocation units for the index component of a VSAM data set.


Syntax

��SET_SPACEUNITS_INDEX= CYL

KBMBRECORDSTRK$NULL

��

SET_SPACEUNITS_INDEX=CYL | KB | MB | RECORDS | TRK | $NULL

Operands






Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CLUSTER(...) INDEX(CYLINDERS(...) ....)DEFINE CLUSTER(...) INDEX(TRACKS(...) ....)DEFINE CLUSTER(...) INDEX(RECORDS(...) ....)DEFINE CLUSTER(...) INDEX(MEGABYTES(...) ....)DEFINE CLUSTER(...) INDEX(KILOBYTES(...) ...)


SPACEUNITS_INDEX.

ExampleSET_SPACEUNITS_INDEX=TRK

In the example, space is allocated in tracks.

SET_SPANNED(VSAM data sets only.) The SET_SPANNED keyword specifies whether theSPANNED option should be defined for a VSAM data set.


Syntax

��SET_SPANNED= YES

NO$DCOC$DCOU

��

SET_SPANNED=YES | NO | $DCOC | $DCOU

Operands

YESThe SPANNED option should be defined.

NOThe NOSPANNED option should be defined.

Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CLUSTER (SPANNED ...)DEFINE CLUSTER (NOSPANNED ...)


Spanned / Nonspanned.


SPANNED.

ExampleSET_SPAN=Y

In the example, the SPANNED option should be defined.

SET_SQTYThe SET_SQTY keyword specifies the secondary quantity value to be assigned tothe data set. For VSAM data sets this keyword specifies the secondary quantity atthe cluster level.


Syntax

��SET_SQTY= nnnnnnnn

$DCOC$DCOU$NULL

��

SET_SQTY=nnnnnnnn | $DCOC | $DCOU | $NULL

Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested secondary quantityfor a data set in the requested allocation units.


Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD SPACE=(...,(,2))

IDCAMS equivalentDEFINE CLUSTER(CYLINDERS(... 1) ....)DEFINE CLUSTER(TRACKS(... 1) ....)DEFINE CLUSTER(RECORDS(... 1000) ....)DEFINE CLUSTER(MEGABYTES(... 2) ....)DEFINE CLUSTER(KILOBYTES(... 2048) ...)


Space Secondary.


SQTY.

ExampleSET_SQTY=2048

In the example, the secondary quantity value to be assigned is 2048.

SET_SQTY_DATA(VSAM data sets only.) The SET_SQTY_DATA keyword specifies the secondaryquantity value to be assigned to the data component of a VSAM data set.


Syntax

��SET_SQTY_DATA= nnnnnnnn

$NULL

��

SET_SQTY_DATA=nnnnnnnn | $NULL

Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested secondaryallocation quantity for the data component in the requested allocation units.

Default

None.

Environments

ALLOCATE.

IDCAMS equivalentDEFINE CLUSTER(...) DATA(CYLINDERS(... 1) ....)DEFINE CLUSTER(...) DATA(TRACKS(... 1) ....)DEFINE CLUSTER(...) DATA(RECORDS(... 1000) ....)DEFINE CLUSTER(...) DATA(MEGABYTES(... 2) ....)DEFINE CLUSTER(...) DATA(KILOBYTES(... 2048) ...)


SQTY_DATA.

ExampleSET_SQTY_DATA=2048


SET_SQTY_INDEX(VSAM data sets only.) The SET_SQTY_INDEX keyword specifies the secondaryquantity value to be assigned to the index component of a VSAM data set.

Syntax

��SET_SQTY_INDEX= nnnnnnnn

$NULL

��

SET_SQTY_INDEX=nnnnnnnn | $NULL

Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested secondaryallocation quantity for the index component in the requested allocation units.


Default

None.

Environments

ALLOCATE.

JCL equivalentDEFINE CL ... INDEX(TRACKS(1) ...)

IDCAMS equivalentDEFINE CLUSTER(...) INDEX(CYLINDERS(... 1) ....)DEFINE CLUSTER(...) INDEX(TRACKS(... 1) ....)DEFINE CLUSTER(...) INDEX(RECORDS(... 1000) ....)DEFINE CLUSTER(...) INDEX(MEGABYTES(... 2) ....)DEFINE CLUSTER(...) INDEX(KILOBYTES(... 2048) ...)


SQTY_INDEX.

ExampleSET_SQTY_INDEX=2048


SET_STORCLASThe SET_STORCLAS keyword specifies an SMS storage class to be assigned to anSMS data set.

Syntax

��SET_STORCLAS= storclas

$NULL

��

SET_STORCLAS=storclas | $NULL

Where:

storclas is the 1-8 character string that specifies the SMS storage class. Wildcardcharacters are not permitted.

Notes:

1. If you remove the storage class you effectively make the data set nonSMS-managed. (You can remove the storage class assigned to a data setby an SMS ACS routine by specifying SET_STORCLAS=$NULL.)

2. If you add a storage class to a data set that originally did not have oneassigned to it, you will cause the data set to become SMS-managed.

3. This keyword requires additional calls to SMS Configuration Servicesand its presence anywhere in the RULEDEFS member can cause ameasurable increase in CPU time for all tasks in the system, especially


|||

those performing large numbers of allocations. Therefore, considerationshould be used when specifying this keyword in your rule definitionmember.

Default

None.

Environments

ACS.

JCL equivalentDD01 DD STORCLAS=PAYRCLAS

IDCAMS equivalentDEFINE CLUSTER(STORAGECLASS(PAYRCLAS) ...)


STORCLAS.

ExampleSET_STORCLAS=PAYRCLAS

In the example, the SMS storage class to be assigned is PAYRCLAS.

SET_STORGRPThe SET_STORGRP keyword specifies an SMS storage group assigned to the dataset.

Syntax

��SET_STORGRP= storgrp

$NULL

��

SET_STORGRP=storgrp | $NULL

Where:

storgrp is a 1-8 character string that specifies the SMS storage group.


Default

None.


|||

|||||

Environments

ACS.


STORGRP.

ExampleSET_STORGRP=STGLARGE

In the example, the SMS storage group is STGLARGE.

SET_TAPE_COMP(Tape data sets only.) The SET_TAPE_COMP keyword specifies the datacompaction setting for a tape data set.

Syntax

��SET_TAPE_COMP= YES

NO$DCOC$DCOU

��

SET_TAPE_COMP=YES | NO | $DCOC | $DCOU

Operands

YESTRTCH=COMP should be specified.

NOTRTCH=NOCOMP should not be specified.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD DCB=(’TRTCH=COMP’)


Compaction.


TAPE_COMP.


ExampleSET_TAPE_C=Y

In the example, TRTCH=COMP should be specified.

SET_TAPE_LABEL(Tape data sets only.) The SET_TAPE_LABEL keyword specifies the type of tapelabel used for a data set.

Syntax

��SET_TAPE_LABEL= AL

AULBLPLTMNLNSLSLSUL

��

SET_TAPE_LABEL=AL | AUL | BLP | LTM | NL | NSL | SL | SUL

Operands

ALISO/ANSI Version 1 or ISO/ANSI/FIPS Version 3 labels.

AULUser labels and ISO/ANSI Version 1 or ISO/ANSI/FIPS Version 3 labels.

BLPBypass label processing.

LTMLeading tapemarks.

NLUnlabeled tapes.

NSLNon-standard labels.

SL Standard labels.

SULStandard and user labels.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD LABEL=(,SL),...



TAPE_LABEL.

ExampleSET_TAPE_L=SL

In the example, standard labels will be used.

SET_UNIT_AFFINITYThe SET_UNIT_AFFINITY keyword specifies whether UNIT affinity should bedefined for a data set.

Syntax

��SET_UNIT_AFFINITY= YES

NO

��

SET_UNIT_AFFINTY=YES | NO

Operands

YESUNIT affinity should be specified (allow unit affinity if it is specified).

NOUNIT affinity should not be specified (remove unit affinity if it is specified).

Note: This keyword does not apply to VSAM DEFINEs or SMS data sets.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD UNIT=AFF=DD02


UNIT_AFFINITY.

ExampleSET_UNIT_A=Y

In the example, UNIT affinity should be specified.


SET_UNIT_COUNTThe SET_UNIT_COUNT keyword specifies the number of units assigned to thedata set.

Syntax

��SET_UNIT_COUNT= nn

��

SET_UNIT_COUNT=nn

Where:

nn specifies the number of units (1-59) assigned to the data set.

Note: UNIT_COUNT should not be used for VSAM DEFINEs. UNIT_COUNT isvalid for JCL or dynamically allocated data sets (including SMS andnon-SMS VSAM and non-VSAM data sets). For IDCAMS DEFINEs, theSET_NUMVOLS keyword should be used instead.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD UNIT=(SYSDA,3)


UNIT_COUNT.

ExampleSET_UNIT_C=3

In the example, the number of units assigned to the data set is 3.

SET_UNIT_NAMEThe SET_UNIT_NAME keyword specifies the generic or esoteric unit name to beassigned.

Syntax

��SET_UNIT_NAME= uuuuuuuu

$NULL

��

SET_UNIT_NAME=uuuuuuuu |$NULL


Note: UNIT_NAME is only applicable to non-SMS data sets. This keyword doesnot apply to VSAM DEFINEs or SMS data sets.

Where:

uuuuuuuu is the 1-8 character unit name. Wildcard characters are not permitted.

Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD UNIT=SYSALLDA


UNIT_NAME.

ExampleSET_UNIT_NAME=SYSALLDA

In the example, the unit name to be assigned is SYSALLDA.

SET_VOLCTThe SET_VOLCT keyword specifies the number of volumes defined to the data set.

Syntax

��SET_VOLCT= nnn

$DCOC$DCOU

��

SET_VOLCT=nnn | $DCOC | $DCOU

Notes:

v For DASD data sets the maximum number of volumes is limited to 59.For tape data sets the maximum number of volumes is limited to 255.

v SET_VOLCT should not be used for VSAM DEFINEs. SET_VOLCT isvalid for JCL or dynamically allocated data sets (including SMS andnon-SMS VSAM and non-VSAM data sets). For IDCAMS DEFINEs theSET_NUMVOLS keyword should be used instead.

Where:

nnn is an integer (0-255) that specifies the volume count.


Default

None.

Environments

ALLOCATE.

JCL equivalentDD01 DD VOL=(,,,4,SER=VOL001)


Volume Count.


VOLCT.

ExampleSET_VOLCT=4

In the example, the number of volumes defined is 4.

SET_VSAM_SEPARATE(VSAM data sets only.) SET_VSAM_SEPARATE specifies whether the index anddata components of a VSAM data set should be on separate volumes.

Syntax

��SET_VSAM_SEPARATE= YES

NO

��

SET_VSAM_SEPARATE=YES | NO

Operands

YESIndex and data components should be on separate volumes.

NOIndex and data components should not be on separate volumes.

Note: For non-SMS VSAM data sets, in order to separate the index and the datacomponents, Advanced Allocation Management must have a potential list ofvolumes to choose from. Therefore, you can only specifySET_VSAM_SEPARATE if you are also using the advanced volume selection(AVS) function.

Default

None.


Environments

ALLOCATE.

IDCAMS equivalentDEFINE CL (...) DATA(VOL(VOL001) ...) INDEX(VOL(VOL002) ...)


VSAM_SEPARATE.

ExampleSET_VSAM_SEP=Y

In the example, index and data components should be on separate volumes.


Chapter 12. Selection criteria

Use selection criteria keywords in conjunction with the INCLUDE or EXCLUDEmain keywords to specify the items to include or exclude from AdvancedAllocation Management processing.

Note these items in the syntax descriptions:1. The underlined portion of the keyword indicates the minimally acceptable

abbreviation.2. $NULL indicates that the particular selection criterion was not specified.3. op represents the comparison operator (EQ,NE,LT,GT,LE,GE).4. The default listed is the default for the Advanced Allocation Management

keyword, not the default assigned to the particular attribute by the operatingsystem (unless otherwise specifically noted).

5. Where applicable, the JCL, IDCAMS, and Data, Management, and Storage Classequivalents are listed. For the Data, Management, or Storage Class equivalents,the field name from the appropriate ISMF panel that is used to define the classis listed.

6. The use of numeric suffixes is permitted.

ACCBIAS(VSAM only.) The ACCBIAS keyword specifies the assigned VSAM SystemManaged Buffering specification.

Syntax

��ACCBIAS= USER

SYSTEMDWDOSWSO

��

ACCBIAS=USER | SYSTEM | DW | DO | SO | SW

Operands


USERBypass system-managed buffering.

SYSTEMSystem managed buffering.

DWDirect weighted.

DOSequential optimized.

209

SOSequential optimized.

SWSequential weighted.

Default

None.

Environments

ALLOCATE, EXTEND, and UNALLOCATE.

JCL equivalentDD01 DD AMP=(’ACCBIAS=USER’)


Record Access Bias.

Related Enhanced Allocation Management function

SET_ACCBIAS.

ExampleACCBIAS=DO

ADISPThe ADISP keyword specifies the abnormal termination disposition for a data set.

Syntax

��ADISP= KEEP

CATLGUNCATLGDELETE$NULL

��

ADISP=KEEP | CATLG | UNCATLG | DELETE | $NULL

Operands


KEEPThe specified abnormal disposition is DISP=(,,KEEP).

CATLGThe specified abnormal disposition is DISP=(,,CATLG).

UNCATLGThe specified abnormal disposition is DISP=(,,UNCATLG).


DELETEThe specified abnormal disposition is DISP=(,,DELETE).

Note:

1. Wildcard characters are not permitted.2. This keyword is not applicable to VSAM IDCAMS DEFINE statements.3. The system takes these defaults with the abnormal termination

disposition parameter:v If you omit the abnormal termination disposition, the default is the

disposition specified, or defaulted to, by the normal terminationdisposition. If the normal termination disposition is PASS, the defaultabnormal termination disposition is DELETE for a NEW data set (orKEEP for an existing data set).

v If you omit the DISP parameter, the default disposition is DELETE forthe abnormal termination disposition.

Default

None.

Environments

ALLOCATE, EXTEND, UNALLOCATE, STOW, and CATCHECK.

JCL equivalentDD01 DD DISP=(,,DELETE)


SET_ADISP.

ExampleADISP=KEEP

BLKSIZE(Non-VSAM only.) The BLKSIZE keyword specifies the defined block size for adata set.

Syntax

��BLKSIZE= (nnnnnnnnnn, )

op

��

BLKSIZE=(nnnnnnnnnn,op)

Where:


Chapter 12. Selection criteria 211

Default

None.

Environments


JCL equivalentDD DD01 BLKSIZE=256000


SET_BLKSIZE.

ExampleBLKSIZE=256000

BUFSPC(VSAM only.) The BUFSPC keyword specifies the defined buffer space specificationfor a data set.

Syntax

��BUFSPC= (nnnnnnnnnn, )

op

��

BUFSPC=(nnnnnnnnnn,op)

Where:


Default

None.

Environments


JCL equivalentDD DD01 AMP=(’BUFSP=128000’)

IDCAMS equivalentDEFINE CLUSTER(BUFFERSPACE(256000) ...)


SET_BUFSPC.


ExampleBUFSPC=128000

CISZ(VSAM only.) The CISZ keyword specifies the defined control interval size for aVSAM cluster.

Syntax

��CISZ= (nnnnn, )

op

��

CISZ=(nnnnn,op)

Where:


Default

None.

Environments


AMS equivalentDEFINE CLUSTER (CONTROLINTERVALSIZE(8192) ....)


SET_CISZ.

ExampleCISZ=8192

CISZ_DATA(VSAM only.) The CISZ_DATA keyword specifies the defined control interval sizefor the data component of a VSAM cluster.

Syntax

��CISZ_DATA= (nnnnn, )

op

��

CISZ_DATA=(nnnnn,op)

Where:



Default

None.

Environments


AMS equivalentDEFINE CLUSTER (....) DATA (CONTROLINTERVALSIZE(8192) ....)


SET_CISZ_DATA.

ExampleCISZ_DATA=8192

CISZ_INDEX(VSAM only.) The CISZ_INDEX keyword specifies the defined control interval size.

Syntax

��CISZ_INDEX= (nnnnn, )

op

��

CISZ_INDEX=(nnnnn,op)

Where:


Default

None.

Environments


AMS equivalentDEFINE CLUSTER (....) DATA(....) INDEX(CONTROLINTERVALSIZE(8192) ....)


SET_CISZ_INDEX.

ExampleCISZ_INDEX=8192


CONTIGUOUS(Non-VSAM disk data sets only.) The CONTIGUOUS keyword specifies whetherthe CONTIG option was specified when allocating a new data set.

Syntax

��CONTIGUOUS= YES

NO

��

CONTIGUOUS=YES | NO

Operands

YESCONTIG was specified.

NOCONTIG was not specified.

Default

None.

Environments


JCL equivalentDD01 DD SPACE=(CYL,(1,1),,CONTIG)


SET_CONTIGUOUS.

ExampleCONTIG=Y

DATACLASThe DATACLAS keyword specifies the SMS data class assigned to a data set.

Syntax

��DATACLAS= ( dataclas , )

$NULL op

��

DATACLAS=(dataclas | $NULL,op)

Where:

dataclas is the 1-8 character SMS data class name. Wildcard characters arepermitted.


Default

None.

Environments

ACS, ALLOCATE, EXTEND, UNALLOCATE, STOW, and CATCHECK.

Note: During ACS processing, the value that is used is the value assigned by theuser (or the system) prior to Advanced Allocation Management processing.In the other environments, the value that is used is the value assigned byAdvanced Allocation Management (if specified); otherwise, it is the valueassigned by the user or by the system.

JCL equivalentDD01 DD DATACLAS=SMALL

IDCAMS equivalentDEFINE CLUSTER (NAME(...) DATACLASS(SMALL) ...)


SET_DATACLAS.

ExampleDATACLAS=LISTDATA

DDNAMEThe DDNAME keyword specifies a ddname assigned to a data set.

Syntax

��DDNAME= (ddname, )

op

��

DDNAME=(ddname,op)

Where:

ddname is a 1-8 character ddname. Wildcard characters are permitted.

Note: VSAM clusters defined through IDCAMS do not have a defined DDNAME.

Default

None.

Environments



JCL equivalentDD01 DD ......

ExampleDDNAME=SYSUT1

DEFERMOUNT(Tape devices only.) The DEFERMOUNT keyword specifies whether the DEFERoption was specified for the UNIT keyword.

Syntax

��DEFERMOUNT= YES

NO

��

DEFERMOUNT=YES | NO

Operands

YESDEFER was specified.

NODEFER was not specified.

Default

None.

Environments

ALLOCATE, EXTEND, UNALLOCATE, and CATCHECK.

JCL equivalentDD01 DD UNIT=(3490,,DEFER)


SET_DEFERMOUNT.

ExampleDEFER=Y

DEVICECLASSThe DEVICECLASS keyword specifies the type of device assigned to the data set.


Syntax

��DEVICECLASS= DISK

TAPEVIO

��

DEVICECLASS=DISK | TAPE | VIO

Operands


DISKThe data set is assigned to a disk device.

TAPEThe data set is assigned to a magnetic tape device.

VIOThe data set is defined to a VIO device.

Note: For new SMS data set allocations that have no UNIT and no VOLSERspecification either in the JCL or dynamic allocation request, DEVICECLASScannot be determined. If DEVICECLASS is not known, any DEVICECLASSselection criterion specified in a RULEDEF will be considered a non-matchand the RULEDEF will not be selected. Consequently, DEVICECLASSshould not be used as a sole selection criterion in environments where newSMS data sets are allocated with neither a UNIT nor VOLSER specification.

Default

None.

Environments


JCL equivalent

None (although the UNIT assigned to the device indirectly defines the deviceclass).

ExampleDEVICEC=D

DIRBLKS(PDS and PDS/E data sets only.) The DIRBLKS keyword specifies the number ofdirectory blocks assigned to a PDS or PDS/E data set.


|||||||

Syntax

��DIRBLKS= (nnnnn, )

op

��

DIRBLKS=(nnnnn,op)

Where:


Default

None.

Environments

ALLOCATE, EXTEND, UNALLOCATE, CATCHECK, and STOW.

JCL equivalentDD01 DD SPACE=(,(,,120))


SET_DIRBLKS.

ExampleDIRBLKS=120

DSNAMEThe DSNAME keyword specifies a data set name.

Syntax

��DSNAME= (dsname, )

op

��

DSNAME=(dsname,op)

Note: For VSAM the DSNAME keyword defines the cluster name.

Where:

dsname is a 1-44 character data set name. Wildcard characters are permitted.

Default

None.


Environments


JCL equivalentDD01 DD DSN=PAY01.FILE

IDCAMS equivalentDEFINE CLUSTER (NAME(PAY01.FILE) ...)

ExampleDSNAME=PDGLO.TEST.DATA.SET

DSNAME_DATA(VSAM data sets only.) The DSNAME_DATA keyword specifies the data set nameof the data component of a VSAM cluster.

Syntax

��DSNAME_DATA= (dsname, )

op

��

DSNAME_DATA=(dsname,op)

Where:


Default

None.

Environments


IDCAMS equivalentDEFINE CL (...) DATA(NAME(PAY01.FILE))

ExampleDSNAME_DATA=PAY01.FILE

DSNAME_INDEX(VSAM data sets only.) The DSNAME_INDEX keyword specifies the data set nameof the index component of a VSAM cluster.


Syntax

��DSNAME_INDEX= (dsname, )

op

��

DSNAME_INDEX=(dsname,op)

Where:


Default

None.

Environments


IDCAMS equivalentDEFINE CL (...) INDEX(NAME(PAY01.FILE))

ExampleDSNAME_INDEX=PAY01.FILE

DSNAME_LASTNODEThe DSNAME_LASTNODE keyword specifies the last qualifier of a data set name.

Syntax

��DSNAME_LASTNODE= (lastnode, )

op

��

DSNAME_LASTNODE=(lastnode,op)

Where:

lastnode is a 1-8 character data set name qualifier. Wildcard characters arepermitted.

Note: For VSAM the DSNAME_LASTNODE keyword pertains to the cluster name.

Default

None.

Environments

ACS, ALLOCATE, EXTEND, UNALLOCATE, CATCHECK, and STOW.


JCL equivalentDD01 DD DSN=QUAL1.QUAL2.QUAL3.QUALLAST

IDCAMS equivalentDEFINE CLUSTER (NAME(QUAL1.QUAL2.QUAL3.QUALLAST) ...)

ExampleDSNAME_LASTNODE=QUALLAST

DSNAME_QUALIFIERThe DSNAME_QUALIFIER keyword specifies one of the qualifiers of a data setname.

Syntax

��DSNAME_QUALIFIER= ( qualifier ,qualifier_num )

$NULL ,op

��

DSNAME_QUALIFIER=(qualifier | $NULL, qualifier_num,op)

Note: For VSAM, the DSNAME_QUALIFIER pertains to the cluster name. If youdo not specify a qualifier number, the DSNAME_QUALIFIER keyword isignored.

Where:v qualifier — Is an 1-8 character data set name qualifier. Wildcard characters are

permitted.v qualifier_num — The position (1-22) of the qualifier in the data set name.

Default

None.

Environments


JCL equivalentDD01 DD DSN=QUAL1.QUAL2.QUAL3.QUAL4

IDCAMS equivalentDEFINE CLUSTER (NAME(QUAL1.QUAL2.QUAL3.QUAL4) ...)

ExampleDSNAME_QUALIFIER=(QUAL2, 2)

DSNAME_TYPEThe DSNAME_TYPE keyword specifies the type of data set.


|

||||||||||||||||||||||||||||||

|

|

Syntax

��DSNAME_TYPE= LIB

PDSHFSEXTREQEXTPREFLARGEBASIC

��

DSNAME_TYPE=LIB | PDS | HFS | EXTREQ | EXTPREF | LARGE | BASIC

Operands


LIBA PDSE data set.

PDSPartitioned data set (PDS).

HFSHierarchical file system data set (HFS data set).

EXTREQExtended format data set if the data set is VSAM, sequential, or if DSORG isomitted from all sources.

EXTPREFPrefer extended format data set if the data set is VSAM, sequential, or ifDSORG is omitted from all sources.

LARGEAllows the specification of more than 65535 tracks for the primary andsecondary allocation for non-VSAM data sets.

BASICAllows the specification of less than 65535 tracks for the primary andsecondary allocation for non-VSAM data sets.

Default

None.

Environments


JCL equivalentDD01 DD DSNTYPE=HFS


Data Set Name Type and If Ext parameters.



SET_DSNAME_TYPE.

ExampleDSNAME_TYPE=HFS

DSORGThe DSORG keyword specifies the data set organization for non-VSAM data setsand the record organization for VSAM data sets.

Syntax

��DSORG= PS

PODAVSNVKSDSRRDSESDSLDS

��

DSORG=PS | PO | DA | VS | NV | KSDS | RRDS | ESDS | LDS

Operands


PS Physical sequential.

POPartitioned organized.

DADirect access.

VSVSAM.

NVNon-VSAM.

KSDSVSAM key-sequenced data set.

RRDSEither a VSAM variable-length or fixed-length relative-record data set.

ESDSVSAM entry-sequenced data set.

LDSVSAM linear data set.

Note: Wildcard characters are not permitted.


Default

None.

Environments


Note: The CATCHECK environment does not apply to VSAM data sets.

JCL equivalentDD01 DD DSORG=PSDD01 DD RECORG=KS

IDCAMS equivalentDEFINE CLUSTER(INDEXED ...)DEFINE CLUSTER(NONINDEXED ...)DEFINE CLUSTER(LINEAR ...)DEFINE CLUSTER(NUMBERED ...)


Recorg.


SET_DSORG.

ExampleDSORG=PS

EXPDATEThe EXPDATE keyword specifies an expiration date for a data set.

Syntax

��EXPDATE= ( yyyyddd , )

$NULL op

��

EXPDATE=(yyyyddd | $NULL,op)

Where:

yyyyddd is a Julian date (yyyy is a four digit year and ddd is a three digit day).

Note: If you specify EXPDATE and RETPD, EXPDATE takes precedence.

Because the system uses the same internal field to store the EXPDATE andRETPD value, if one or the other is specified in the JCL or DEFINEstatement, either the EXPDATE or RETPD selection criteria keyword can beused as a selection criterion provided the proper date format is specified.


For example, if you specify a RETPD of 1 and the creation date was 2008001as expressed in EXPDATE format, the value of the field as stored internallyby the system would be 2008002. Therefore, either of these two selectioncriteria would match:RETPD=1EXPDATE=2008002

Default

None.

Environments


JCL equivalentDD01 DD EXPDT=2009/003

IDCAMS equivalentDEFINE CLUSTER(TO(2009003) ..)


Retpd or Expdt.


SET_EXPDATE.

ExampleEXPDATE=2009003

EXTADDR(VSAM data sets only.) The EXTADDR keyword specifies the ExtendedAddressability attribute for a VSAM cluster.

Syntax

��EXTADDR= YES

NO

��

EXTADDR=YES | NO

Operands

YESExtended addressability was defined for the data set.

NOExtended addressability was not defined for the data set.


Default

SMS defaults to NO for Extended Addressability.

Environments



Extended Addressability.


SET_EXTADDR.

ExampleEXTADDR=N

FILESEQNO(Tape data sets only.) The FILESEQNO keyword specifies a file sequence numberof a data set.

Syntax

��FILESEQNO= (nnn, )

op

��

FILESEQNO=(nnn,op)

Where:

nnn is the sequence number (0-255).

Default

None.

Environments


JCL equivalentDD01 DD LABEL=(4,)


SET_FILESEQNO.

ExampleFILESEQNO=4


FRLOG(VSAM data sets only.) The FRLOG keyword specifies whether VSAM batchlogging was specified for a VSAM data set.

Syntax

��FRLOG= REDO

NONEUNDOALL$NULL

��

FRLOG=REDO | NONE | ALL | UNDO | $NULL

Operands


REDOForward recovery was requested.

NONEThe VSAM batch logging option was not requested.

ALLBoth backward and forward recovery was requested.

UNDOBackward recovery was requested.

Default


Environments


IDCAMS equivalentDEFINE CL (FRLOG(REDO) ...)


FRlog.


SET_FRLOG.

ExampleFRLOG=REDO


FSPC_CA(VSAM data sets only.) The FSPC_CA keyword specifies the freespace percentagefor the control area of a VSAM data set.

Syntax

��FSPC_CA= (nnn, )

op

��

FSPC_CA=(nnn,op)

Where:

nnn is an integer (0-100).

Default

None.

Environments




% Freespace CA.


SET_FSPC_CA.

ExampleFSPC_CA=10

FSPC_CI(VSAM data sets only.) The FSPC_CI keyword specifies the freespace percentagefor the control interval of a VSAM data set.

Syntax

��FSPC_CI= (nnn, )

op

��

FSPC_CI=(nnn,op)

Where:


nnn is an integer (0-100).

Default

None.

Environments




% Freespace CI.


SET_FSPC_CI.

ExampleFSPC_CI=10

GROUPIDThe GROUPID keyword specifies a security group (such as a RACF or equivalentsecurity product) identifier.

Syntax

��GROUPID= (group_id, )

op

��

GROUPID=(group_id,op)

Where:

group_id is a 1-8 character group ID. Wildcard characters are permitted.

Default

None.

Environments


JCL equivalentJJHTEST01 JOB ,,GROUP=DEVELOPR

ExampleGROUPID=DEVELOPR


GUARSPACEThe GUARSPACE keyword specifies the Guaranteed Space attribute for the dataset as defined in the SMS storage class.

Syntax

��GUARSPACE= YES

NO

��

GUARSPACE=YES | NO

Operands

YESGuaranteed Space was specified.

NOGuaranteed Space was not specified.

Note:

v Guaranteed Space is defined in the SMS storage class.v This keyword requires additional calls to SMS Configuration Services and

its presence anywhere in the RULEDEFS member can cause a measurableincrease in CPU time for all tasks in the system, especially thoseperforming large numbers of allocations. Therefore, consideration shouldbe used when specifying this keyword in your rule definition member.

Default

None.

Environments


Storage class equivalent

Guaranteed Space.

ExampleGUARSPACE=YES

ILOAD(VSAM data sets only.) The ILOAD keyword specifies the initial load optionspecified for a VSAM data set.

Syntax

��ILOAD= SPEED

RECOVERY

��


|

|||||

ILOAD=SPEED | RECOVERY

Operands

SPEEDThe SPEED option was specified.

RECOVERYThe RECOVERY option was specified.

Default

None.

Environments


IDCAMS equivalentDEFINE CLUSTER (RECOVERY ...)DEFINE CLUSTER (SPEED ...)


Initial Load.


SET_ILOAD.

ExampleILOAD=S

JOBACCTn(VSAM and non-VSAM.) The JOBACCTn keyword specifies one of the first fifteenJob Accounting field specifications.

Syntax

��JOBACCTn= ( value , )

$NULL op

��

JOBACCTn=(value | $NULL,op)

Where:v n — is an integer (1-15).v value — is a character string value with a maximum length of 144. If the string

contains special characters or blanks, enclose the string with double quotes.Wildcard characters are permitted.

Default

None.


|

|

Environments


JCL equivalentJOB ,’accounting information’

ExampleJOBACCTn= "Department 5 - Room 5A"

JOBCLASSThe JOBCLASS keyword specifies a single character JES job class.

Syntax

��JOBCLASS= (class, )

op

��

JOBCLASS=(class,op)

Where:

class is one character that specifies the job class. Wildcard characters are permitted.

Default

None.

JCL equivalentJJHTEST01 JOB ,,CLASS=A

Environments


ExampleJOBCLASS=A

JOBNAMEThe JOBNAME keyword specifies the name of the job, started task, or TSO user IDassociated with the task that is processing a data set.

Syntax

��JOBNAME= (jobname, )

op

��

JOBNAME=(jobname,op)


Where:

jobname is the 1-8 character name of the job, started task, or TSO user ID. Wildcardcharacters are permitted.

Default

None.

Environments


JCL equivalentJJHTEST1 JOB ...

ExampleJOBNAME=JJHTEST

JOBTYPEThe JOBTYPE keyword specifies the type of address space.

Syntax

��JOBTYPE= JOB

STCTSUAPPC

��

JOBTYPE=JOB | STC | TSU | APPC

Operands


JOBNormal job address space.

STCStarted task.

TSUTime-sharing user.

APPCAPPC address space.

Note: Wildcard characters are not permitted.

Default

None.


Environments


ExampleJOBTYPE=JOB

KEY_LEN(Key sequenced VSAM data sets only.) The KEY_LEN keyword specifies the keylength of a key sequenced VSAM data set.

Syntax

��KEY_LEN= (nnn, )

op

��

KEY_LEN=(nnn,op)

Where:

nnn is the length of a key in the range of 1-255.

Default

None.

Environments


JCL equivalentDD01 DD KEYLEN=6,...

IDCAMS equivalentDEFINE CLUSTER(KEYS(8 ..) ...)


Keylen.


SET_KEY_LEN.

ExampleKEY_L=12

KEY_OFF(Key sequenced VSAM data sets only.) The KEY_OFF keyword specifies the offsetof the key in a key sequenced VSAM data set.


Syntax

��KEY_OFF= (nnnnn, )

op

��

KEY_OFF=(nnnnn,op)

Where:

nnnnn is the offset of the key (0-32767) with a data record.

Default

None.

Environments


JCL equivalentDD01 DD KEYOFF=0,...

IDCAMS equivalentDEFINE CLUSTER(KEYS(... 12) ...)


Keyoff.


SET_KEY_OFF.

ExampleKEY_O=12

LOGGING(VSAM RLS data sets only.) The LOGGING keyword specifies the type of loggingperformed for the sphere of a VSAM RLS data set.

Syntax

��LOGGING= BACK

BOTHNONE$NULL

��

LOGGING=BACK | BOTH | NONE | $NULL


Operands


BACKBackward recovery.

BOTHBackward and forward recovery.

NONENeither forward or backward recovery.

Default


Environments


IDCAMS equivalentDEFINE CL(LOG(UNDO))


Log.

ExampleLOGGING=BOTH

LOGSTREAM_ID(SMS-managed VSAM data sets only.) The LOGSTREAM_ID keyword specifies thename of a logstream data set for an SMS-managed VSAM data set.

Syntax

��LOGSTREAM_ID= ( logstream_id , )

$NULL op

��

LOGSTREAM_ID=(logstream_id | $NULL,op)

Where:

logstream_id is a string of 1-26 characters naming the logstream. Wildcardcharacters are permitted.

Default

None.

Environments



JCL equivalentDD01 DD LGSTREAM=PAY.STREAM

IDCAMS equivalentDEFINE CLUSTER(LOGSTREAMID(PAY.STREAM) ...)


Logstream ID.


SET_LOGSTREAM_ID.

ExampleLOGSTREAM_ID=PAY.STREAM

LRECLThe LRECL keyword specifies the record length of a data set.

Syntax

��

�

,

LRECL=( nnnnn , )op

��

LRECL=(nnnnn,op,nnnnn,op)

Where:

Where nnnnn is an integer (1-32767) that defines the length of a non-VSAM recordor the average and maximum record sizes of a VSAM data set.

Note: For non-VSAM data sets the second length and comparison operator areignored.

Default

None.

Environments


JCL equivalentDD01 DD LRECL=80,....

IDCAMS equivalentDEFINE CL (RECORDSIZE(80 120) ...)



Lrecl.


SET_LRECL.

ExampleLRECL=(80,,120)

MAXSPACEThe MAXSPACE keyword specifies the maximum potential space on the firstvolume of a data set.

Syntax

��MAXSPACE= (nnnnnnnn, )

op

��

MAXSPACE=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) that specifies the maximum potential space inallocation units a data set can occupy on the first volume.

Note:

v For non-VSAM data sets, MAXSPACE is calculated by adding the spacerequired for the primary allocation to the space required for 15 extentsworth of the secondary allocation. The Advanced Allocation ManagementMAXSPACE value is expressed in the specified units of allocation (CYL,TRK, and so on), not as the equivalent number of bytes.

v For VSAM data sets, MAXSPACE is calculated by adding the spacerequired for the primary allocation to the space required for 254 extentsworth of secondary allocation.

Default

None.

Environments


JCL equivalentDD01 DD SPACE=(CYL,(1,1)),...

ExampleMAXSP=16577225


MGMTCLAS(SMS-managed data sets only.) The MGMTCLAS keyword specifies the SMSmanagement class assigned to an SMS data set.

Syntax

��MGMTCLAS= ( mgmtclas , )

$NULL op

��

MGMTCLAS=(mgmtclas | $NULL,op)

Where:

mgmtclas is the 1-8 character name assigned to the SMS management class.Wildcard characters are permitted.

Default

None.

Environments


Note: During ACS processing, the value that is used is the value assigned by theuser or the system prior to Advanced Allocation Management processing. Inthe other environments, the value that is used is the value assigned byAdvanced Allocation Management (if specified); otherwise, it is the valueassigned by the user or by the system.

JCL equivalentDD01 DD MGMTCLAS=STANDARD

IDCAMS equivalentDEFINE CLUSTER(MANAGEMENTCLASS(LONGTERM) ...)


SET_MGMTCLAS.

ExampleMGMTCLAS=TSO

MOUNT_USAGE(Non-SMS, non-VSAM data sets only.) The MOUNT_USAGE keyword specifies themount usage type of the current volume at the time an Advanced AllocationManagement function is being performed.


Syntax

��

�

,ALL

MOUNT_USAGE=( PUBLIC )PRIVATESTORAGE

��

MOUNT_USAGE=(PUBLIC | PRIVATE | STORAGE | ALL)

Operands

PUBLICThe volume is mounted PUBLIC.

PRIVATEThe volume is mounted PRIVATE.

STORAGEThe volume is mounted STORAGE.

ALLThe volume can be mounted with any status.

Notes:

1. Wildcard characters are not permitted.2. You can specify more than one keyword value. For example:

MOUNT_USAGE=(PRIVATE,PUBLIC,STORAGE,ALL)3. For the PRIM_REDUCE function, and all SET functions, for the initial

allocation on the first volume of supported data sets, the mount usagetype is only known where the VOLSER is specifically identified eitherin the JCL or dynamic allocation request.If the mount usage type is not known, any MOUNT_USAGE selectioncriterion specified in a RULEDEF will be considered a non-match andthe RULEDEF will not be selected. Consequently, the PRIM_REDUCEfunction and all SET functions for the initial allocation on the firstvolume of a data set should not be used along with theMOUNT_USAGE keyword.

Default

ALL.

Environments


Note: For any function pertinent to the ACS or ALLOCATION environments, themount usage type is only known where the VOLSER is specificallyidentified either in the JCL or dynamic allocation request.

ExampleMOUNT_USAGE=PRIVATE


|||||||||||||||||||||||||||||||||

|

||

||||

||||||

|

|

NDISPThe NDISP keyword specifies the normal termination disposition for a data set.

Syntax

��NDISP= PASS

KEEPCATLGUNCATLGDELETE$NULL

��

NDISP=PASS | KEEP | CATLG | UNCATLG | DELETE | $NULL

Operands


PASSThe specified or defaulted normal disposition is DISP=(,PASS).

KEEPThe specified or defaulted normal disposition is DISP=(,KEEP).

CATLGThe specified or defaulted normal disposition is DISP=(,CATLG).

UNCATLGThe specified or defaulted normal disposition is DISP=(,UNCATLG).

DELETEThe specified or defaulted normal disposition is DISP=(,DELETE).

Notes:

1. The NDISP keyword does not apply to VSAM IDCAMS DEFINEstatements.

2. The system takes the following defaults with the normal terminationdisposition parameter:v If you omit the normal termination disposition, the default is

DELETE for a NEW data set and KEEP for an existing data set.v If you omit the DISP parameter, the default disposition is DELETE for

the normal termination disposition.

Default

None.

Environments


JCL equivalentDD01 DD DISP=(,DELETE,)



SET_NDISP.

ExampleNDISP=CATLG

NUMVOLSThe NUMVOLS keyword specifies the number of volumes defined to a VSAMcluster.

Syntax

��NUMVOLS= (nn, )

op

��

NUMVOLS=(nn,op)

Where:


Note: The volume count is determined by the number of unique, specific, volsersfor the data and index components (duplicate volsers are counted once).When non-specific volser entries denoted by an asterisk (*) are specified, thelarger of the number of non-specific volsers specified for the data and indexcomponents will be added to the number of unique specific volsers, if any.

Default

None.

Environments

ALLOCATE, EXTEND, UNALLOCATE.

IDCAMS equivalentDEFINE CLUSTER(VOLUMES(VOL001 VOL002) ...)DEFINE CLUSTER(VOLUMES(* * * *) ...)


Volume Count.


SET_NUMVOLS.

ExampleNUMVOLS=5


NUMVOLS_DATAThe NUMVOLS_DATA keyword specifies the number of volumes to be defined forthe data component of a VSAM cluster.

Syntax

��NUMVOLS_DATA= (nn, )

op

��

NUMVOLS_DATA=(nn,op)

Where:


Default

None.

Environments


IDCAMS equivalentDEFINE CLUSTER(...) DATA(VOLUMES(VOL001 VOL002) ...)DEFINE CLUSTER(...) DATA(VOLUMES(* * * *) ...)


SET_NUMVOLS_DATA.

ExampleNUMVOLS_DATA=5

NUMVOLS_INDEXThe NUMVOLS_INDEX keyword specifies the number of volumes to be definedfor the index component of a VSAM cluster.

Syntax

��NUMVOLS_INDEX= (nn, )

op

��

NUMVOLS_INDEX=(nn,op)

Where:



Default

None.

Environments


IDCAMS equivalentDEFINE CLUSTER(...) INDEX(VOLUMES(VOL001 VOL002) ...)DEFINE CLUSTER(...) INDEX(VOLUMES(* * * *) ...)


SET_NUMVOLS_INDEX.

ExampleSET_NUMVOLS_INDEX=5

OWNERIDThe OWNERID keyword specifies the owner identification for the data set asstored in the catalog.

Syntax

��OWNERID= (owner_id, )

op

��

OWNERID=(owner_id,op)

Where:

owner_id is a 1-8 character owner identification. Wildcard characters are permitted.

Default

None.

Environments

ALLOCATE, EXTEND, UNALLOCATE, STOW, and CATCHECK

IDCAMS equivalentDEFINE CL (OWNER(PLEXAA) ...)

ExampleOWN=PLEXAA

PROCSTEPNAMEThe PROCSTEPNAME keyword specifies a procedure step name.


Syntax

��PROCSTEPNAME= (procstepname, )

op

��

PROCSTEPNAME=(procstepname,op)

Where:

procstepname is the 1-8 character procedure step name. Wildcard characters arepermitted.

Default

None.

Environments

ALLOCATE, EXTEND, UNALLOCATE, STOW, and CATCHECK

JCL equivalentPSTEP01 EXEC PROC01

ExamplePROCSTEPNAME=JJHPROC

PROGRAMThe PROGRAM keyword specifies the job step program name active when aparticular Advanced Allocation Management function is performed.

Syntax

��PROGRAM= (program, )

op

��

PROGRAM=(program,op)

Where:

program is the 1-8 character program name. Wildcard characters are permitted.

Default

None.

Environments


JCL equivalentSTEP01 EXEC PGM=HUMRSR01


ExamplePROGRAM=RDEFDRVR

PQTYThe PQTY keyword specifies the primary quantity value assigned to the data set.

Syntax

��PQTY= (nnnnnnnn, )

op

��

PQTY=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) that specifies the primary quantity for a dataset. For new non-VSAM data sets, this is the actual amount requested. Fornon-VSAM new data sets this is the amount of space allocated to the first extent.For VSAM data sets this is the requested primary quantity; the value isrepresented in space allocation units. For example SPACE=(TRK,(5,2)) would havea PQTY value of 5 as would SPACE=(CYL,(5,2)).

Note: When a DEFINE is performed for a VSAM data set and space is specifiedusing the RECORDS, KILOBYTES, or MEGABYTES parameters, IDCAMSconverts these specifications to either tracks or cylinders and saves theconverted specification in the catalog. Therefore, if a rule definition is codedthat checks spaceunits for performing a function that occurs during VSAMend-of-volume (such as SEC_ALLOC), SPACEUNITS=RECU, KB, or MB willnot generate a match. This can affect PQTY (primary quantity) matching. Forexample, if a DEFINE specifies MB(1), that specification will be converted totwo cylinders and saved and that value will be saved in the catalog.Therefore attempting to check PQTY=1 for a function that is performedduring VSAM end-of-volume will cause a non-match to occur as well.

Default

None.

Environments


JCL equivalentDD01 DD SPACE=(...,(1))

IDCAMS equivalentDEFINE CLUSTER(CYLINDERS(1) ....)DEFINE CLUSTER(TRACKS(1) ....)DEFINE CLUSTER(RECORDS(1000) ....)DEFINE CLUSTER(MEGABYTES(2) ....)DEFINE CLUSTER(KILOBYTES(2048) ...)



SET_PQTY.

ExamplePQTY=2048

PQTY_DATA(VSAM data sets only.) The PQTY_DATA keyword specifies the primary quantityvalue assigned to the data component of a VSAM data set.

Syntax

��PQTY_DATA= (nnnnnnnn, )

op

��

PQTY_DATA=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) specifying the requested primary allocationquantity for the data component in the requested allocation units.

Default

None.

Environments


IDCAMS equivalentDEFINE CLUSTER(...) DATA(CYLINDERS(1) ....)DEFINE CLUSTER(...) DATA(TRACKS(1) ....)DEFINE CLUSTER(...) DATA(RECORDS(1000) ....)DEFINE CLUSTER(...) DATA(MEGABYTES(2) ....)DEFINE CLUSTER(...) DATA(KILOBYTES(2048) ...)


SET_PQTY_DATA.

ExamplePQTY_DATA=2048

PQTY_INDEX(VSAM data sets only.) The PQTY_INDEX keyword specifies the primary quantityvalue assigned to the index component of a VSAM data set.


Syntax

��PQTY_INDEX= (nnnnnnnn, )

op

��

PQTY_INDEX=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) specifying the requested primary allocationquantity for the index component in the requested allocation units.

Default

None.

Environments


JCL equivalentDEFINE CLUSTER(...) INDEX(CYLINDERS(1) ....)

DEFINE CLUSTER(...) INDEX(TRACKS(1) ....)DEFINE CLUSTER(...) INDEX(RECORDS(1000) ....)DEFINE CLUSTER(...) INDEX(MEGABYTES(2) ....)DEFINE CLUSTER(...) INDEX(KILOBYTES(2048) ...)


SET_PQTY_INDEX.

ExamplePQTY_INDEX=1000

PSPACE_KBThe PSPACE_KB keyword specifies the requested or actual primary space allocatedto a data set in kilobytes.

Syntax

��PSPACE_KB= (nnnnnnnn, )

op

��

PSPACE_KB=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) that specifies the number of kilobytes for theprimary allocation quantity of a data set. For a new non-VSAM data set this is therequested primary allocation quantity. For an existing non-VSAM data set this is


the actual space allocated to the first extent of a data set. For VSAM data sets thisis the requested primary allocation quantity.

Default

None.

Environments


Note: For the ACS environment this value is obtained from the SMS ACS variable&SIZE.

JCL equivalentDD01 DD SPACE=(TRK,(1,1))

ExamplePSPACE_KB=16577200

PSPACE_MBThe PSPACE_MB keyword specifies the requested, or actual, primary spaceallocated to a data set in megabytes.

Syntax

��PSPACE_MB= (nnnnnnnn, )

op

��

PSPACE_MB=(nnnnnnnnn,op)

Where:

nnnnnnnnn is an integer (0-16777215) that specifies the number of megabytes forthe primary allocation quantity of a data set. For a new non-VSAM data set this isthe requested primary allocation quantity. For an existing non-VSAM data set thisis the actual space allocated to the first extent of a data set. For VSAM data setsthis is the requested primary allocation quantity.

Default

None.

Environments


Note: For the ACS environment this value is calculated from the ACS variable&SIZE.

JCL equivalentDD01 DD SPACE-(1,(5,1)),AVGREC=M


ExamplePSPACE_MB=5

RECFM(Non-VSAM data sets only.) The RECFM keyword specifies the record format for anon-VSAM data set.

Syntax


��RECFM= U

UAUMUTUTAUTMVVAVMVBVBAVBMVSVSAVSMVTVTAVTMVBSVBSAVBSMVBTVBTAVBTMVBSTVBSTAVBSTMFFAFMFBFBAFBMFTFTAFTMFBTFBTAFBTMFSFSAFSMFBSFBSAFBSMDDADBDBADSDSADBSDBSA

��

RECFM=U | UA | UM | UT | UTA | UTM | V | VA | VM | VB | VBA | VBM| VS | VSA | VSM | VT | VTA| VTM | VBS | VBSA| VBSM | VBT | VBTA |VBTM | VBST | VBSTA | VBSTM | F | FA | FM | FB | FBA | FBM | FT | FTA| FTM | FBT | FBTA | FBTM | FS | FSA | FSM | FBS | FBSA | FBSM | D |


DA | DB | DBA | DS | DSA | DBS | DBSA

Operands

D ASCII variable-length.

DAASCII variable-length (ANSI format).

DBASCII variable-length (blocked).

DBAASCII variable-length (blocked, ANSI format).

DBSASCII variable-length (blocked, spanned).

DBSAASCII variable-length (blocked, spanned, ANSI format).

DSASCII variable-length (spanned).

DSAASCII variable-length (spanned, ANSI format).

F Fixed length.

FAFixed length (ANSI format).

FB Fixed length (blocked).

FBAFixed length (blocked, ANSI format).

FBMFixed length (blocked, machine code format).

FBSFixed length (blocked, standard blocks).

FBSAFixed length (blocked, standard blocks, ANSI format).

FBSMFixed length (blocked, standard blocks, machine code format).

FBTFixed length (blocked, track overflow).

FBTAFixed length (blocked, track overflow, ANSI format)

FBTMFixed length (blocked, track overflow, machine code format).

FMMachine code format.

FS Fixed length (standard blocks).

FSAFixed length (standard blocks, ANSI format).


FSMFixed length (standard blocks, machine code format).

FT Fixed length (track overflow).

FTAFixed length (track overflow, ANSI format).

FTMFixed length (track overflow, machine code format).

U Undefined-length.

UAUndefined-length (ANSI format).

UMUndefined-length (machine code format).

UTUndefined-length (track overflow).

UTAUndefined-length (track overflow, ANSI format).

UTMUndefined-length (track overflow, machine code format).

V Variable length.

VAVariable length (ANSI format).

VBVariable length (blocked).

VBAVariable length (blocked, ANSI format).

VBMVariable length (blocked, machine code format).

VBSVariable length (blocked, spanned).

VBSAVariable length (blocked, spanned, ANSI format).

VBSMVariable length (blocked, spanned, machine code format).

VBSTVariable length (blocked, spanned, track overflow).

VBSTAVariable length (blocked, spanned, track overflow, ANSI format).

VBSTMVariable length (blocked, spanned, track overflow, machine code format).

VBTVariable length (blocked, track overflow).

VBTAVariable length (blocked, track overflow, ANSI format).


VBTMVariable length (blocked, track overflow, machine code format).

VMVariable length (machine code format).

VSVariable length (spanned).

VSAVariable length (spanned, ANSI format).

VSMVariable length (spanned, machine code format).

VTVariable length (track overflow).

VTAVariable length (track overflow, ANSI format).

VTMVariable length (track overflow, machine code format).

Default

None.

Environments


JCL equivalentDD01 DD RECFM=FB


Recfm.


SET_RECFM.

ExampleRECFM=V

RELEASESPACE(Non-VSAM data sets.) The RELEASESPACE keyword specifies whether spacerelease was specified.

Syntax

��RELEASESPACE= YES

NO

��

RELEASESPACE=YES | NO


Operands

YESSpace release was specified.

NOSpace release was not specified.


Default

None.

Environments


JCL equivalentDD01 DD SPACE=(TRK,(1,1),,RLSE))

Management class equivalent

Partial Release.

ExampleRELEASESPACE=Y

RETPDThe RETPD keyword specifies the retention period for a data set.

Syntax

��RETPD= ( nnnn , )

$NULL op

��

RETPD=(nnnn | $NULL,op)

Where:

nnnn is an integer (0-9999) that specifies the number of days to retain the data set.

Note: If you specify EXPDATE and RETPD, the EXPDATE keyword takesprecedence.

Because the same internal field is used by the system to store the EXPDATEand RETPD value, if one or the other is specified in the JCL or DEFINE,either the EXPDATE or RETPD selection keyword can be used as a selectioncriterion provided the proper date format is specified. For example, if youspecify a RETPD of 1 and the creation date was 2008001 as expressed in


|||||

EXPDATE format, the value of the field as stored internally by the systemwould be 2008002. Therefore, either of these two selection criteria wouldmatch:RETPD=1EXPDATE=2008002

Default

None.

Environments


JCL equivalentDD01 DD RETPD=100

IDCAMS equivalentDEFINE CLUSTER(FOR(200) ...)


Retpd or Expdt.


SET_RETPD.

ExampleRETPD=365

REUSE(VSAM data sets only.) The REUSE keyword specifies whether the VSAM REUSEoption was specified.

Syntax

��REUSE= YES

NO

��

REUSE=YES | NO

Operands

YESREUSE was specified.

NONOREUSE was specified.

Default

None.


Environments


IDCAMS equivalentDEFINE CL (REUSE ....)


Reuse.


SET_REUSE.

ExampleREUSE=YES

SDISPThe SDISP keyword specifies the status disposition for a data set.

Syntax

��SDISP= NEW

SHROLDMOD

��

SDISP=NEW | SHR | OLD | MOD

Operands

NEWThe specified or defaulted status disposition is DISP=(NEW).

SHRThe specified or defaulted status disposition is DISP=(SHR).

OLDThe specified or defaulted status disposition is DISP=(OLD).

MODThe specified or defaulted status disposition is DISP=(MOD).

Notes:

1. The SDISP keyword does not apply to a VSAM IDCAMS DEFINEstatement.

2. The system takes the following defaults with the status dispositionparameter: If you omit the DISP parameter, the default disposition isNEW for the status disposition.

Default

None.


Environments


JCL equivalentDD01 DD DISP=(NEW,,)

ExampleSDISP=NEW

SHROPT_XRGN(VSAM data sets only.) The SHROPT_XGRN keyword specifies theSHAREOPTIONS for cross-region sharing.

Syntax

��SHROPT_XRGN= (n, )

op

��

SHROPT_XRGN=(n,op)

Where:

n is an integer (1-4) that specifies the VSAM cross-region shareoption.

Default

None.

Environments


IDCAMS equivalentDEFINE CL (SHAREOPTIONS(1) ...)


Shareoptions Xregion.


SET_SHROPT_XRGN.

ExampleSHROPT_XRGN=1

SHROPT_XSYS(VSAM data sets only.) The SHROPT_XSYS keyword specifies theSHAREOPTIONS for cross-system sharing.


Syntax

��SHROPT_XSYS= (n, )

op

��

SHROPT_XSYS=(n,op)

Where:

n is an integer (3 or 4) that specifies the VSAM cross-system shareoption.

Default

None.

Environments


IDCAMS equivalentDEFINE CL (SHAREOPTIONS(. 3) ...)


Shareoptions Xsystem.


SET_SHROPT_XSYS.

ExampleSHROPT_XSYS=3

SMS_MANAGEDThe SMS_MANAGED keyword specifies whether or not the data set is under SMScontrol.

Syntax

��SMS_MANAGED= YES

NO

��

SMS_MANAGED=YES | NO

Operands

YESThe data set is SMS-managed.

NOThe data set is not SMS-managed.


Note: If an SMS storage class is assigned to the data set prior to any modificationby Advanced Allocation Management, the data set is considered to beSMS-managed. If the SMS storage class is added or removed by AdvancedAllocation Management in the ACS environment, subsequent environmentswill reflect an SMS management status of NO if the storage class wasremoved or YES if a storage class was added.

Default

None.

Environments


ExampleSMS_MANAGED=YES

SPACEUNITSThe SPACEUNITS keyword specifies the allocation unit type for a data set.

Syntax

��SPACEUNITS=( AVGRECU , nnnnn , )

AVGRECK , nnnnn opAVGRECM , nnnnnBLK , nnnnnCYLKBMBRECORDSTRK

��

SPACEUNITS=(BLK | CYL | TRK | KB | MB | RECORDS | AVGRECU |AVGRECK | AVGRECM,nnnnn,op)

Operands

BLKSpace is allocated in blocks.





RECORDSSpace is allocated using the IDCAMS DEFINE CLUSTER RECORDS keyword.


AVGRECUSpace is allocated in records with AVGREC=U specified.

AVGRECKSpace is allocated in records with AVGREC=K specified.

AVGRECMSpace is allocated in records with AVGREC=M specified.

nnnnnis an integer (0-65535) that specifies either the block size or record size whenallocations are made with the allocation space units of BLK or AVGRECU,AVGRECK, or AVGRECM respectively. This value does not apply to VSAMdata sets.

Note: When a DEFINE is performed for a VSAM data set and space is specifiedusing the RECORDS, KILOBYTES, or MEGABYTES parameters, IDCAMSconverts these specifications to either tracks or cylinders and saves theconverted specification in the catalog. Therefore, if a rule definition is codedthat checks spaceunits for performing a function that occurs during VSAMend-of-volume (such as SEC_ALLOC), SPACEUNITS=AVGRECU, KB, or MBwill not generate a match. This can affect PQTY (primary quantity)matching. For example, if a DEFINE specifies MB(1), that specification willbe converted to two cylinders and saved and that value will be saved in thecatalog. Therefore attempting to check PQTY=1 for a function that isperformed during VSAM end-of-volume will cause a non-match to occur aswell.

Default

None.

Environments


JCL equivalentDD01 DD SPACE=(8000,(2000,200))

IDCAMS equivalentDEFINE CLUSTER(CYLINDERS(...) ....)DEFINE CLUSTER(TRACKS(...) ....)DEFINE CLUSTER(RECORDS(...) ....)DEFINE CLUSTER(MEGABYTES(...) ....)DEFINE CLUSTER(KILOBYTES(...) ...)


SET_SPACEUNITS.

ExampleSPACEU=CYL

SPACEUNITS_DATA(VSAM data sets only.) The SPACEUNITS_DATA keyword specifies the allocationunits for the data component of a VSAM data set.


Syntax

��SPACEUNITS_DATA= CYL

TRKKBMBRECORDS

��

SPACEUNITS_DATA=(CYL | TRK | RECORDS | KB | MB)

Operands






Default

None.

Environments


IDCAMS equivalentDEFINE CLUSTER(...) DATA(CYLINDERS(...) ....)DEFINE CLUSTER(...) DATA(TRACKS(...) ....)DEFINE CLUSTER(...) DATA(RECORDS(...) ....)DEFINE CLUSTER(...) DATA(MEGABYTES(...) ....)DEFINE CLUSTER(...) DATA(KILOBYTES(...) ...)


SET_SPACEUNITS_DATA.

ExampleSPACEUNITS_D=REC

SPACEUNITS_INDEX(VSAM data sets only.) The SPACEUNITS_INDEX keyword specifies the allocationunits for the index component of a VSAM data set.


Syntax

��SPACEUNITS_INDEX= CYL

TRKKBMBRECORDS

��

SPACEUNITS_INDEX=(CYL | TRK | RECORDS | KB | MB)

Operands






Default

None.

Environments


IDCAMS equivalentDEFINE CLUSTER(...) INDEX(CYLINDERS(...) ....)DEFINE CLUSTER(...) INDEX(TRACKS(...) ....)DEFINE CLUSTER(...) INDEX(RECORDS(...) ....)DEFINE CLUSTER(...) INDEX(MEGABYTES(...) ....)DEFINE CLUSTER(...) INDEX(KILOBYTES(...) ...)


SET_SPACEUNITS_INDEX.

ExampleSPACEUNITS_INDEX=REC

SPANNED(VSAM data sets only.) The SPANNED keyword specifies whether the SPANNEDoption is defined for a VSAM data set.


Syntax

��SPANNED= YES

NO

��

SPANNED=YES | NO

Operands

YESThe SPANNED option was defined.

NOThe NOSPANNED option was defined.

Default

None.

Environments


IDCAMS equivalentDEFINE CLUSTER (SPANNED ...)DEFINE CLUSTER (NOSPANNED ...)


Spanned / Nonspanned.


SET_SPANNED.

ExampleSPAN=Y

SQTYThe SQTY keyword specifies the secondary quantity value assigned to the data set.

Syntax

��SQTY= (nnnnnnnn, )

op

��

SQTY=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested secondaryquantity.


Default

None.

Environments


JCL equivalentDD01 DD SPACE=(...,(,2))

IDCAMS equivalentDEFINE CLUSTER(CYLINDERS(... 1) ....)DEFINE CLUSTER(TRACKS(... 1) ....)DEFINE CLUSTER(RECORDS(... 1000) ....)DEFINE CLUSTER(MEGABYTES(... 2) ....)DEFINE CLUSTER(KILOBYTES(... 2048) ...)


SET_SQTY.

ExampleSQTY=2048

SQTY_DATA(VSAM data sets only.) The SQTY_DATA keyword specifies the secondary quantityvalue assigned to the data component of a VSAM data set.

Syntax

��SQTY_DATA= (nnnnnnnn, )

op

��

SQTY_DATA=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested secondaryallocation quantity for the data component in the requested allocation units.

Default

None.

Environments



IDCAMS equivalentDEFINE CLUSTER(...) DATA(CYLINDERS(... 1) ....)DEFINE CLUSTER(...) DATA(TRACKS(... 1) ....)DEFINE CLUSTER(...) DATA(RECORDS(... 1000) ....)DEFINE CLUSTER(...) DATA(MEGABYTES(... 2) ....)DEFINE CLUSTER(...) DATA(KILOBYTES(... 2048) ...)


SET_SQTY_DATA.

ExampleSQTY_DATA=1000

SQTY_INDEX(VSAM data sets only.) The SQTY_INDEX keyword specifies the secondaryquantity value assigned to the index component of a VSAM data set.

Syntax

��SQTY_INDEX= (nnnnnnnn, )

op

��

SQTY_INDEX=(nnnnnnnn,op)

Where:

nnnnnnnn is an integer (0-16777215) that specifies the requested secondaryallocation quantity for the index component in the requested allocation units.

Default

None.

Environments


JCL equivalentDEFINE CL ... INDEX(TRACKS(1) ...)

IDCAMS equivalentDEFINE CLUSTER(...) INDEX(CYLINDERS(... 1) ....)DEFINE CLUSTER(...) INDEX(TRACKS(... 1) ....)DEFINE CLUSTER(...) INDEX(RECORDS(... 1000) ....)DEFINE CLUSTER(...) INDEX(MEGABYTES(... 2) ....)DEFINE CLUSTER(...) INDEX(KILOBYTES(... 2048) ...)


SET_SQTY_INDEX.


ExampleSQTY_INDEX=1000

STEPACCTn(VSAM and non-VSAM data sets.) The STEPACCTn keyword specifies one of thefirst fifteen Step Accounting field specifications.

Syntax

��STEPACCTn= ( value , )

$NULL op

��

STEPACCTn=(value | $NULL,op)

Where:v n— is an integer (1-15).v value — is a character string with a maximum length of 144. If the string

contains special characters or blanks it should be surrounded by double quotes.Wildcard characters are permitted.

Default

None.

Environments


JCL equivalentSTEP01 EXEC PGM=PAY01,ACCT=(’accounting information’)

ExampleSTEPACCTn="Department 950"

STEPNAMEThe STEPNAME keyword specifies the stepname assigned to a job step.

Syntax

��STEPNAME= (stepname, )

op

��

STEPNAME=(stepname,op)

Where:

stepname is the 1-8 character step name. Wildcard characters are permitted.


Default

None.

Environments


JCL equivalentSTEP01 EXEC PGM=PAYR01

ExampleSTEPNAME=JJHSTEP

STORCLASThe STORCLAS keyword specifies an SMS storage class assigned to an SMS dataset.

Syntax

��STORCLAS= ( storclas , )

$NULL op

��

STORCLAS=(storclas | $NULL,op)

Where:

storclas is the 1-8 character string that specifies the SMS storage class. Wildcardcharacters are permitted.

Default

None.

Environments

ACS, ALLOCATE, EXTEND, UNALLOCATE, STOW, and CATCHECK

Note: During ACS processing, the value that is used is the value assigned by theuser or the system prior to Advanced Allocation Management processing. Inthe other environments, the value that is used is the value assigned byAdvanced Allocation Management (if specified); otherwise, it is the valueassigned by the user or by the system.

JCL equivalentDD01 DD STORCLAS=PAYRCLAS

IDCAMS equivalentDEFINE CLUSTER(STORAGECLASS(PAYRCLAS) ...)



SET_STORCLAS.

ExampleSTORCLAS=TSO

STORGRPThe STORGRP keyword specifies an SMS storage group assigned to an SMS dataset.

Syntax

��STORGRP= ( storgrp , )

$NULL op

��

STORGRP=(storgrp | $NULL,op)

Where:

storgrp is a 1-8 character string specifying the SMS storage group. Wildcardcharacters are permitted.

Note: With SMS, it is possible to define more than one eligible storage group for anew data set allocation. In this situation, if the Advanced AllocationManagement STORGRP filter parameter is used, the specified storage groupname will be checked against all eligible storage groups for the allocation. Ifthe specified name matches any of the eligible storage groups, thenAdvanced Allocation Management will consider that portion of theRULEDEF a match. Once a specific storage group has been assigned to thedata set however, only that assigned storage group will be checked againstthe storage group name specified by the STORGRP filter parameter.

Default

None.

Environments


Note: During ACS processing, the value that is used is the value assigned by theuser or the system prior to Advanced Allocation Management processing. Inthe other environments, the value that is used is the value assigned byAdvanced Allocation Management (if specified) otherwise, it is the valueassigned by the user or by the system.


SET_STORGRP.

ExampleSTORGRP=STGLARGE


SUBSYSThe SUBSYS keyword specifies a subsystem name assigned to an AdvancedAllocation Management address space.

Syntax

��SUBSYS= (subsys_id, )

op

��

SUBSYS=(subsys_id,op)

Where:

subsys_id is a 1-4 character value specifying the Advanced Allocation Managementsubsystem ID. (This is the value assigned in the OPTIONS member for the SSIDstart-up parameter.) Wildcard characters are permitted.

Default

None.

Environments


ExampleSUBSYS=GLO1

SYSIDThe SYSID keyword specifies an OS/390 or z/OS system ID.

Syntax

��SYSID= (sys_id, )

op

��

SYSID=(sys_id,op)

Where:

sys_id is 1-4 character string that specifies the OS/390 or z/OS system ID. Wildcardcharacters are permitted.

Default

None.

Environments



JCL equivalent/*JOBPARM SYSAFF=ABCD

ExampleSYSID=RS16

SYSPLEXNAMEThe SYSPLEXNAME keyword specifies the z/OS name assigned to the sysplex.

Syntax

��SYSPLEXNAME= (plexname, )

op

��

SYSPLEXNAME=(plexname,op)

Where:

plexname is a 1-8 character string specifying the OS/390 or z/OS sysplex name.Wildcard characters are permitted.

Default

None.

Environments


ExampleSYSPLEXNAME=PLEX001

TAPE_COMP(Tape data sets only.) The TAPE_COMP keyword specifies the defined datacompaction setting for a tape data set.

Syntax

��TAPE_COMP= YES

NO

��

TAPE_COMP=YES | NO

Operands

YESTRTCH=COMP was specified.

NOTRTCH=NOCOMP was specified.


Default

None.

Environments

ALLOCATE, UNALLOCATE, and CATCHECK.

JCL equivalentDD01 DD DCB=(’TRTCH=COMP’)


Compaction.


SET_TAPE_COMP.

ExampleTAPE_C=Y

TAPE_LABEL(Non-VSAM tape data sets only.) The TAPE_LABEL keyword specifies the type oftape label used for a data set.

Syntax

��TAPE_LABEL= SL

SULALAULNSLNLBLPLTM

��

TAPE_LABEL=SL | SUL | AL | AUL | NSL | NL | BLP | LTM

Operands

ALISO/ANSI Version 1 or ISO/ANSI/FIPS Version 3 labels.

AULUser labels and ISO/ANSI Version 1 or ISO/ANSI/FIPS Version 3 labels.

BLPBypass label processing.

LTMLeading tapemarks.

NLUnlabeled tapes.


NSLNon-standard labels.

SL Standard labels.

SULStandard and user labels.

Default

None.

Environments


JCL equivalentDD01 DD LABEL=(,SL),...


SET_TAPE_LABEL.

ExampleTAPE_L=SL

TEMPDSThe TEMPDS keyword specifies whether the data set is temporary.

Syntax

��TEMPDS= YES

NO

��

TEMPDS=YES | NO

Operands

Specify one of these operands to indicate whether data set permanence should beevaluated.

YESThe data set must be a temporary data set for this rule definition to match.

NOThe data set must not be a temporary data set for this rule definition to match.

Default

None.

Environments



ExampleTEMPDS=YES

UNIT_AFFINITYThe UNIT_AFFINITY keyword specifies whether UNIT affinity is defined for adata set.

Syntax

��UNIT_AFFINITY= YES

NO

��

UNIT_AFFINTY=YES | NO

Operands

YESUNIT affinity was specified.

NOUNIT affinity was not specified.

Note: This keyword does not apply to VSAM DEFINEs or SMS data sets.

Default

None.

Environments


JCL equivalentDD01 DD UNIT=AFF=DD02


SET_UNIT_AFFINITY.

ExampleUNIT_A=YES

UNIT_COUNTThe UNIT_COUNT keyword specifies the number of units assigned to the data set.

Syntax

��UNIT_COUNT= (nn, )

op

��


UNIT_COUNT=(nn,op)

Where:

nn specifies the number of units (1-59) assigned to the data set.

Note: UNIT_COUNT should not be used for VSAM DEFINEs. UNIT_COUNT isvalid for JCL or dynamically allocated data sets (including SMS andnon-SMS VSAM and non-VSAM data sets). For IDCAMS DEFINEs, theNUMVOLS keyword should be used instead.

Default

None.

Environments

ACS, ALLOCATE, EXTEND, UNALLOCATE, STOW, CATCHECK.

JCL equivalentDD01 DD UNIT=(SYSDA,3)


SET_UNIT_COUNT.

ExampleUNIT_C=24

UNIT_NAMEThe UNIT_NAME keyword specifies the generic or esoteric unit name or unitnames.

Syntax

��

�UNIT_NAME=( uuuuuuuu ,)$NULL

��

UNIT_NAME=(uuuuuuuu | $NULL,uuuuuuuu | $NULL,....)

Note: UNIT_NAME is only applicable to non-SMS, non-VSAM data sets. (It doesnot apply to VSAM DEFINEs or SMS data sets.) When a data set is allocatedas DISP=NEW, the unit name used for matching is either the one explicitlyidentified in the UNIT= JCL keyword or equivalent dynamic allocation textunit, or the one defaulted by the system. For non-DISP=NEW allocations,the unit name is the generic unit name as identified in the catalog.

Where:

uuuuuuuu is the 1-8 character unit name. Wildcard characters are permitted.


Default

None.

Environments


JCL equivalentDD01 DD UNIT=SYSALLDA


SET_UNIT_NAME.

ExampleUNIT_NAME=SYSALLDA

UNIT_TYPEThe UNIT_TYPE keyword specifies the type of unit on which a data set isallocated.

Syntax

��UNIT_TYPE= OTHER

ANY3390338093453420348034903590

��

UNIT_TYPE=(OTHER | 3390 | 3380 | 9345 | 3420 | 3480 | 3490 | 3590 | ANY)

Notes:

1. For non-SMS data sets, the volume serial number must be specified inthe JCL or IDCAMS DEFINE in order to determine the unit type forfunctions in the ACS and ALLOCATION environments. A non-matchwill occur if UNIT_TYPE is specified under such circumstances.

2. For SMS VSAM and non-VSAM data sets, since the volume serialnumber is not yet chosen by the system in the ACS and ALLOCATIONenvironments, the unit type is not known, therefore if UNIT_TYPE isspecified in the selection criteria, the RULEDEF statement is considerednot to match.

3. For new SMS data set allocations that have no UNIT and no VOLSERspecification either in the JCL or dynamic allocation request,UNIT_TYPE cannot be determined. If UNIT_TYPE is not known, anyUNIT_TYPE selection criterion specified in a RULEDEF will beconsidered a non-match and the RULEDEF will not be selected.Consequently, UNIT_TYPE should not be used as a sole selection


|

||||||

criterion in environments where new SMS data sets are allocated withneither a UNIT nor VOLSER specification.

Operands

OTHERA unit type other than 3390, 3380, 9345, 3420, 3480, 3490, or 3590.

33903390 device.

33803380 device.

93459345 device.

34203420 device.

34803480 device.

34903490 device.

35903590 device.

ANYAny unit type.

Default

None.

Environments


ExampleUNIT_TYPE=3380

USERIDThe USERID keyword specifies a user ID (such as a RACF or equivalent securityproduct user ID).

Syntax

��USERID= (user_id, )

op

��

USERID=(user_id,op)

Where:

user_id is 1-7 character user ID. Wildcard characters are permitted.


||

Default

None.

Environments


JCL equivalentJJHTEST01 JOB ,,USER=DVLPJJH

ExampleUSERID=PDSMITH

VOLCTThe VOLCT keyword specifies the number of volumes defined to the data set.

Syntax

��VOLCT= (nnn, )

op

��

VOLCT=(nnn,op)

Where:

nnn is an integer (0-255) that specifies the volume count.

Notes:

v For preexisting data sets, this value is considered to be the number ofunique prime and candidate volumes for both the index and datacomponents of a cluster.

v For DASD data sets the maximum number of volumes is limited to 59.v VOLCT should not be used for VSAM DEFINEs. VOLCT is valid for JCL

or dynamically allocated data sets (including SMS and non-SMS VSAMand non-VSAM data sets). For IDCAMS DEFINEs the NUMVOLSkeyword should be used instead.

Default

None.

Environments


JCL equivalentDD01 DD VOL=(,,,4,SER=VOL001)


Volume Count.



SET_VOLCT.

ExampleVOLCT=124

VOLSER_ANYThe VOLSER_ANY keyword specifies any volume serial number.

Syntax

��

�

,

VOLSER_ANY=( volser )$NULL

��

VOLSER_ANY=(volser | $NULL,volser | $NULL,....)

Where:

volser is the 1-6 character volume serial number. Wildcard characters are permitted.

Notes:

1. For non-SMS non-VSAM data sets, the volume serial number must bespecified in the JCL (or dynamic allocation) for the VOLSER_ANYselection criterion to match for the PRIM_REDUCE function on the firstvolume.

2. For SMS VSAM and non-VSAM data sets, since the volume serialnumber is not yet chosen by the system at PRIM_REDUCE time, ifVOLSER_ANY is specified in the selection criteria, the RULEDEFstatement is considered not to match for the PRIM_REDUCE functionon the first volume.

Default

None.

Environments


JCL equivalentDD01 DD VOL=SER=(BIG001,BIG002,...)

IDCAMS equivalentDEFINE CLUSTER(VOLUMES(BIG001 BIG002 ...) ...)

ExampleVOLSER_ANY=SMS001


|

|||||||||||||||||||||||||||

|

|

VOLSER_CURRENTThe VOLSER_CURRENT keyword specifies a volume serial number of the currentvolume being processed when a particular function is being performed.

Syntax

��

�

,

VOLSER_CURRENT=( volser )$NULL

��

VOLSER_CURRENT=(volser | $NULL,volser | $NULL,....)

Where:


Notes:

1. For non-SMS non-VSAM data sets, the volume serial number must bespecified in the JCL (or dynamic allocation) for the VOLSER_CURRENTselection criterion to match for the PRIM_REDUCE function on the firstvolume.

2. For non-SMS VSAM data sets, the first volume serial number in theDEFINE for the data set (in either the index or data component) is usedfor matching purposes for the PRIM_REDUCE function on the firstvolume.

3. For SMS VSAM and non-VSAM data sets, since the volume serialnumber is not yet chosen by the system at PRIM_REDUCE time, ifVOLSER_CURRENT is specified in the selection criteria with a valueother than $NULL, the RULEDEF statement is considered not to matchfor the PRIM_REDUCE function on the first volume.

Default

None.

Environments


JCL equivalentDD01 DD VOL=SER=(BIG001,BIG002,...)

IDCAMS equivalentDEFINE CLUSTER(VOLUMES(BIG001 BIG002 ...) ...)

ExampleVOLSER_CURRENT=SMS001


|

|||||||||||||||||||||||||||

|

|

VOLSER_FIRSTThe VOLSER_FIRST keyword specifies a volume serial number of the first volumeof the data set.

Syntax

��

�

,

VOLSER_FIRST=( volser )$NULL

��

VOLSER_FIRST=(volser | $NULL,volser | $NULL,....)

Where:


Notes:

1. For non-SMS non-VSAM data sets, the volume serial number must bespecified in the JCL (or dynamic allocation) for the VOLSER_FIRSTselection criterion to match for the PRIM_REDUCE function on the firstvolume.

2. For non-SMS VSAM data sets, the first volume serial number in theDEFINE for the data set (in either the index or data component) is usedfor matching purposes for the PRIM_REDUCE function on the firstvolume.

3. For SMS VSAM and non-VSAM data sets, since the volume serialnumber is not yet chosen by the system at PRIM_REDUCE time, ifVOLSER_FIRST is specified in the selection criteria, the RULEDEFstatement is considered not to match for the PRIM_REDUCE functionon the first volume.

Default

None.

Environments


JCL equivalentDD01 DD VOL=SER=BIG001

IDCAMS equivalentDEFINE CLUSTER(VOLUMES(BIG001 ...) ...)

ExampleVOLSER_FIRST=SMS001


|

|||||||||||||||||||||||||||

|

|

VSAM_SEPARATE(VSAM data sets only.) VSAM_SEPARATE specifies whether the index and datacomponents of a VSAM data set are on separate volumes.

Syntax

��VSAM_SEPARATE= YES

NO

��

VSAM_SEPARATE=YES | NO

Operands

YESIndex and data components are on separate volumes.

NOIndex and data components are not on separate volumes.

Default

None.

Environments

EXTEND and UNALLOCATE.

IDCAMS equivalentDEFINE CL (...) DATA(VOL(VOL001) ...) INDEX(VOL(VOL002) ...)


SET_VSAM_SEPARATE.

ExampleVSAM_SEP=Y



Chapter 13. Volume group definition syntax

Use volume group definition syntax to define volume groups.

Note: Volume group definitions do not apply to SMS data sets.

Syntax diagramThis information shows the Advanced Allocation Management volume groupdefinition syntax.

�� GROUP_NAME nnnnnnnn �

,

VOLUMES=( vvvvvv ) ��

Main keywordsThe volume group definition syntax consists of two keywords: GROUP_NAMEand VOLUMES. The main keyword used to define a volume group is theGROUP_NAME keyword.

In the descriptions, the underlined portion of the keyword indicates the minimallyacceptable abbreviation.

GROUP_NAMEThe GROUP_NAME keyword defines a volume group.

Syntax

GROUP_NAME=nnnnnnnn

Where nnnnnnnn is a maximum of eight characters (alphanumeric) to define avolume group.

Example

GROUP_NAME=JJHGRP01

VOLUMESThe VOLUMES keyword defines the list of volumes in the volume group.

Syntax

VOLUMES=(vvvvvv,vvvvvv,......)

Where vvvvvv is a six character volume serial number. Multiple volumes can belisted Wildcard characters are permitted.

Example

VOLUMES=(VOL001,VOL002,VOL003)

285


Chapter 14. Event recording and reporting

Advanced Allocation Management provides an extensive event recording andreporting facility to help you evaluate product benefits, specific events AdvancedAllocation Management encountered, and subsequent actions taken for a particularjob or time frame, and so on.

Advanced Allocation Management utilizes the z/OS System Management Facility(SMF) to record and retain historical information that can be later archived,retrieved, and reported upon. A report utility is also provided which extracts theSMF records Advanced Allocation Management has created and reports them in avariety of formats. Data can be viewed using the View Event History dialog facility(the View Event History option available from the Tivoli Advanced AllocationManagement Primary Option Menu) or by using the batch reporting utility. ADSECT of the record layout is provided so that you can write your own programsto report on the SMF data, processing it in any manner you choose.

Note: Advanced Allocation Management event data recording is optional.Advanced Allocation Management will not write event data to SMF unlessyou configure it to do so. For information about how Advanced AllocationManagement uses the SMF record type you specify, see “Step 4: Specifysubsystem options” on page 21.

Enabling event recordingTo enable the event recording facility to record data, complete these steps.1. Select a user SMF record type that is not currently in use at your installation.

The record type must be within the range of 128-255.

Note: If you are recording SMF data for an existing product and also want torecord SMF data for Advanced Allocation Management, select a new,previously unused record type. (Once SMF data has been generated for agiven record type, SMF data from a different source and in a differentformat should not be written using that same record type.)

2. Add the selected record type to the list of record types that SMF is to record.The list of record types resides in the MVS SMFPRMxx PARMLIB member.

3. Activate the updated SMFPRMxx member using either the MVS SET commandor by performing an IPL.

4. Update the SMF_RECORD_ID parameter in Advanced Allocation ManagementOPTIONS member to specify the selected record type to be recorded.

5. If Advanced Allocation Management is running, shut it down and restart it toregister the OPTION member change.For more information about SMF and updating the MVS SMFPRMxx PARMLIBmember, see z/OS MVS System Management Facilities (SMF).After you have enabled event data recording, Advanced AllocationManagement will automatically begin recording event data to SMF and you canuse either the View Event History dialog facility or the batch reporting facilityto obtain reports on the data.

287

Disabling event recordingTo stop event data recording, complete these steps.1. Remove the record type from the MVS SMFPRMxx PARMLIB member.2. Remove the record type (specified by the SMF_RECORD_ID parameter) from

the OPTIONS member in the Advanced Allocation Management control dataset.

3. If Advanced Allocation Management is running, shut it down and restart it toregister the OPTION member change.

Report filter criteria and filtersetsFilter criteria provide a way to select only records matching certain specificationsto be reported.

Filter criteria are specified as elements of filtersets. A filterset represents one ormore filter criteria that are to be AND'ed together to determine whether or not arecord matches. For example:FILTER_SET=(JOBNAME=ABC,DDNAME=XYZ)

indicates only those records where the jobname is "ABC" AND the ddname is "XYZ"are to be reported.

Notes:

1. FILTER_SET= must precede the criteria.2. Filterset criteria must be separated by commas (even if they are on

separate lines). The last filterset criteria you specify does not require acomma after it.

Specifying multiple filtersetsYou can specify more than one filterset. Each filterset you specify is OR'ed with theothers.

For example:FILTER_SET=(JOBNAME=ABC)FILTER_SET=(JOBNAME=DEF)

indicates only those records where the jobname is "ABC" OR "DEF" are to bereported.

Note: If you are using the View Event History dialog facility, you can specify amaximum of 10 filtersets and a maximum of 10 filter criteria per filterset. Ifyou are using the batch reporting utility, a maximum of 32 filtersets can bespecified and a maximum of 32 filter criteria per filterset can be specified.

Filter criteria formatsEach of the following FILTER_SET= specifications are valid formats for specifyingfilter criteria.FILTER_SET=JOBNAME=ABC

FILTER_SET=(JOBNAME=ABC)

FILTER_SET=(JOBNAME=ABC,DDNAME=XYZ)




Report optionsThe report options Detail Report, Summary Report, and Format are designed towork in combination with each other to produce a desired output.

The following rules apply when specifying these report options:v DETAIL=N and SUMMARY=N are not valid togetherv FORMAT=L and SUMMARY=Y are not valid together

(If SUMMARY=Y, FORMAT must be R)v FORMAT=L and DETAIL=N are not valid together

(If FORMAT=L, DETAIL must be Y)

Report option combinations and resultsThis information shows report option combinations and corresponding results.

Table 12. Report options and results

If you specify: The result is:

FORMAT=LIST DETAIL=N SUMMARY=N invalid combination; error condition returned

FORMAT=LIST DETAIL=N SUMMARY=Y invalid combination; error condition returned

FORMAT=LIST DETAIL=(A or B)SUMMARY=N

generates unformatted records in a list; nosummary report is generated

FORMAT=LIST DETAIL=(A or B)SUMMARY=Y

invalid combination; error condition returned

FORMAT=REPORT DETAIL=NSUMMARY=N

invalid combination; error condition returned

FORMAT=REPORT DETAIL=NSUMMARY=Y

generates a summary report

FORMAT=REPORT DETAIL=(A or B)SUMMARY=N

generates detail records in a formatted report;no summary report is generated

FORMAT=REPORT DETAIL=(A or B)SUMMARY=Y

generates detail records in a formatted report;a summary report is generated at the end

Batch reporting utilityThe Advanced Allocation Management batch reporting utility provides a methodfor generating event history reports in batch.

In some situations, the batch reporting utility can provide greater flexibility andcontrol over the data to be reported and the output destination (as compared tousing the View Event History dialog facility).

Chapter 14. Event recording and reporting 289

Configuring the batch reporting utility JCLTo use the batch reporting utility, you must configure the batch reporting utilityJCL.

Note: The sample JCL for the utility is generated during the installation processand is located in the GLOJLOGR member of the Advanced AllocationManagement sample library.

The contents of the GLOJLOGR member are shown in Figure 18.

To configure the batch reporting utility JCL, complete these steps:1. Replace GLO.V3R1 with the high-level qualifier of the installed Advanced

Allocation Management load libraries.2. Specify the names of the SMF data sets to be searched for Advanced Allocation

Management event records. In Figure 18, the SMF data set specified isSMF.DATA.SET1.

3. Specify the SMF record type that has been designated for use by AdvancedAllocation Management.

4. Modify the required DD statement.5. Specify input control statements.

Modifying required DD statementsThese DD statements in the batch reporting utility JCL are required and should bemodified as follows:v HISTOUT specifies where the resulting report output is written. It is

recommended that you allow the utility to place file attributes on the data set atthe time it is written, however, you can specify the following:– If Format=R is specified, HISTOUT must have a record format of fixed (F) or

fixed block (FB) and a record length (LRECL) of 80.– If Format=L is specified, HISTOUT must have a record format of variable (V)

or variable blocked (VB) and a record length (LRECL) of 1024.

//********************************************************************//* *//* DESCRIPTION: THIS JOB EXECUTES THE BATCH REPORT UTILITY. *//* *//* CAUTION: YOU WILL NEED TO MODIFY THIS JCL BEFORE USING IT. *//* *//* SMF.DATA.SET1 MUST BE CHANGED TO A VALID SMF DATA SET NAME *//* ??? MUST BE CHANGED TO A VALID SMF RECORD TYPE *//* *//* NOTES: *//* 1) ’GLO.V3R1’ IS THE SUGGESTED HIGH-LEVEL QUALIFIER. *//* 2) "*" HAS BEEN SPECIFIED FOR THE SYSOUT PARAMETER. *//* *//********************************************************************//*//GLOLOGRP EXEC PGM=GLOLOGRP//STEPLIB DD DSN=GLO.V3R1.SGLOLOAD,DISP=SHR//HISTOUT DD SYSOUT=*//CNTLOUT DD SYSOUT=*//CNTLIN DD *SMFIN=SMF.DATA.SET1SMF_RECORD_ID=???/*

Figure 18. Batch reporting utility JCL (GLOJLOGR)


v CNTLOUT specifies where execution statistics and diagnostics are to be written,It must have a record format of fixed (F) or fixed block (FB) and a record length(LRECL) of 80.

v CNTLIN specifies the location of the input control statements. It must have arecord format of fixed (F) or fixed block (FB) and a record length (LRECL) of 80.

Input control statementsThese control statements are valid input to the batch reporting utility.

Note: All control statements that you add to the JCL must start in card columnone. This restriction does not apply to continuation statements.

SMFIN(Required.) Specifies the names of the SMF data sets to be searched forAdvanced Allocation Management event records. A maximum of 32 dataset names can be specified.

Each of the following SMFIN= specifications are valid formats forspecifying data set names using SMFIN:SMFIN=SMF.data.set1

SMFIN=(SMF.data.set1)

SMFIN=(SMF.data.set1,SMF.data.set2)



Notes:

1. The SMF data set you specify must be a non-VSAM data set.2. Multiple dsnames specified on a SMFIN statement must be

separated by commas (even if they are specified on separatelines). The last dsname you specify does not require a commaafter it.

SMF_RECORD_ID=xxx(Required.) Specifies the SMF record type that has been designated for useby Advanced Allocation Management where xxx is a 1 to 3 digit recordidentifier with a value between 128 and 255.

Note: This is the numeric value specified in the Advanced AllocationManagement control data set OPTIONS member generated duringthe installation and configuration process.

FILTER_SETSpecifies a set of filter criteria to select only records matching certainspecifications for reporting. Each filterset is composed of one or morefiltersets. A maximum of 32 filtersets can be specified and a maximum of32 filter criteria per filterset can be specified.

SORT_BYSpecifies the field that the selected records are to be sorted by.

Note: This value is optional and if not specified, the records will bereported in the order in which they are read.


DETAIL_REPORTDetail records provide a detailed description of each entity that encountersan event that is recorded. Valid values are:v A (or ALL) — Include extended detail records in the report.v B (or BASIC) — Include basic detail records in the report.v Y (or YES) — Include detail records in the report.

Note: Specifying Y is the same as specifying B and is supported fordownward compatibility.

v N (or NO) — Do not include detail records in the report.v If Format=R (Report) is also specified, the detail records are formatted.v If Format=L (List) is also specified, the detail records are composed of

raw data, in a format suitable for input into another report-writingutility.

SUMMARY_REPORTSpecifies whether a summary of the records processed should begenerated. Valid values are:v Y (or YES) — Generate a summary of the records processed.v N (or NO) — Do not generate a summary.

Note: Because the summary report is always formatted, SummaryReport=Y is valid only when Format=R (Report) is also specified.

FORMATFORMAT specifies the type of output to generate. Valid values are:v R (or REPORT) — Generate a formatted report.v L (or LIST) — Generate raw data records in a format suitable for input

into other report-writing utilities.

Running the batch reporting utilityWhen you are finished modifying the batch reporting utility JCL, submit the JCL togenerate the report.

Sample execution reportThe reports you generate can vary depending upon the options and filters youselect. This information provides an example of an execution report generated bythe batch reporting utility JCL.

Figure 19 on page 293 shows a sample execution report.


These statistics are summarized in the sample execution report:

Number of SMF records readDisplays the number of SMF records read by Advanced AllocationManagement.

Number of processing activity records readDisplays the number of processing activity records read by AdvancedAllocation Management.

Number of records that passed filteringDisplays the number of records that passed filtering.

Sample formatted basic detail and extended detail recordreports

The reports you generate can vary depending upon the options and filters youselect. This information provides an example of a formatted basic detail andformatted extended detail record reports generated by batch reporting utility JCL.

Figure 20 shows an example of a formatted basic detail record report.

* * * TIVOLI Advanced Allocation Management EVENT HISTORY REPORT * * *

VALIDATING CONTROL STATEMENTS-

SMFIN=PDABCD.SMF.OUTSMF_RECORD_ID=128

END OF CONTROL STATEMENT INPUT

THE FOLLOWING REPORTING OPTIONS ARE IN EFFECT-FORMAT=REPORTDETAIL_REPORT=BASICSUMMARY_REPORT=YES

STATISTICS SUMMARY:

NUMBER OF SMF RECORDS READ.......................0000013NUMBER OF PROCESSING ACTIVITY RECORDS READ.......0000013NUMBER OF RECORDS THAT PASSED FILTERING..........0000013

PROCESSING IS COMPLETE; RETURN CODE IS 0000000

Figure 19. Sample execution report

* * * TIVOLI Advanced Allocation Management PROCESSING ACTIVITY DETAIL REPORT * * *

DATE: 2007/02/07 JOBNAME: GLOJIVP1 STEPNAME: PRIMREDTIME: 14:22:26 JOBTYPE: JOB PROCSTEP:SYSTEM ID: ABC1 PROGRAM: IEBDG DDNAME: SYSUT2SUBSYS: APRD RDEF_LINE: 00002986 DSORG: PSDSNAME: PDABCD.GLO.TEST.DATAACTIVITY: INITIAL VOLUME PRIMARY SPACE ALLOCATION FAILURE RECOVERED

DATE: 2007/02/07 JOBNAME: GLOJIVP1 STEPNAME: SECALLOCTIME: 14:22:26 JOBTYPE: JOB PROCSTEP:SYSTEM ID: ABC1 PROGRAM: IEBDG DDNAME: SYSUT2SUBSYS: APRD RDEF_LINE: 00002990 DSORG: PSDSNAME: PDABCD.GLO.TEST.DATAACTIVITY: UNDEFINED SECONDARY ALLOCATION SPACE ABEND AVOIDED (D37)

Figure 20. Sample formatted basic detail record report


Figure 21 shows an example of a formatted extended detail record report.

The basic detail record report provides fundamental information about AdvancedAllocation Management processing activity. The extended detail record reportincludes SMS details, such as storage class and storage group information inaddition to the information provided in the basic detail record report.

A formatted basic or extended detail record report can include these Activity fielddetails for the NOTCAT2 function.

NOT CATLGD 2 ERR PROCESSED WITH JCLFAIL ON VOLSER VVVVVV ATTTTTT

The number of NOTCAT2 errors processed with a JCLFAIL action. Where:v VVVVVV — If the error was detected at allocation time, VVVVVV is the

first volser of the newly created data set. If the error was detected atstep termination time, VVVVVV is the first volser of the currentlycataloged old data set.

v TTTT — Is set to "ALLOC" if the error was detected at allocation time.Otherwise TTTT is set to "TERM" if the error was detected at steptermination time.

NOT CATLGD 2 ERR PROCESSED WITH SCRATCH ON VOLSER VVVVVVAT TTTTT

The number of NOTCAT2 errors processed with a SCRATCH (uncatalogand delete) action. Where:v VVVVVV — Is the first volser of the current existing data set that was

deleted.v TTTT — Is set to "ALLOC" if the error was detected at allocation time.

Otherwise TTTT is set to "TERM" if the error was detected at steptermination time.

NOT CATLGD 2 ERR PROCESSED WITH RENAME ON VOLSER VVVVVVAT TTTTT

The number of NOTCAT2 errors processed with a RENAME action.Where:v VVVVVV — Is the first volser of the current existing data set that was

renamed.v TTTT — Is set to "ALLOC" if the error was detected at allocation time.


If the Activity field indicates that the NOT CATLGD 2 error was processedwith the RENAME action, the following line is included:NEW NAME: dsname

* * * TIVOLI Advanced Allocation Management PROCESSING ACTIVITY DETAIL REPORT * * *

DATE: 2007/02/07 JOBNAME: GLOJIVP1 STEPNAME: SECALLOCTIME: 14:22:26 JOBTYPE: JOB PROCSTEP:SYSTEM ID: ABC1 PROGRAM: IEBDG DDNAME: SYSUT2SUBSYS: APRD RDEF_LINE: 00000097 DSORG: PSDSNAME: PDABCD.GLO.TEST.DATAACTIVITY: UNDEFINED SECONDARY ALLOCATION SPACE ABEND AVOIDED (D37)TEMPDS: NO SMS-MGD: YES DATACLAS: TSODCSTORCLAS: TSOSC MGMTCLAS: STANDARD STORGRP: SGSG2SDISP: NEW NDISP: CATLG ADISP: DELETE

Figure 21. Sample formatted extended detail record report


where dsname is the new name assigned to the current existing data setthat was renamed.

NOT CATLGD 2 ERR PROCESSED WITH UNCATLG ON VOLSER VVVVVVAT TTTTT

The number of NOTCAT2 errors processed with an UNCATALOG action.Where:v VVVVVV — Is the first volser of the current existing data set that was

uncataloged.v TTTT — Is set to "ALLOC" if the error was detected at allocation time.


A formatted basic or extended detail record report can include these Activity fielddetails for the Enhanced Allocation Management, Advanced Volume Selection andTERM_ALLOC functions.

DATA SET ALLOCATION FAILED BY THE TERM_ALLOC FUNCTIONData set allocations that were forced to fail as a result of theTERM_ALLOC function.

ALLOCATION PARAMETER SET BY ENHANCED ALLOCATIONMANAGEMENT

Data set parameters that were added, changed or deleted by EnhancedAllocation Management.

NON-SMS VOLUME(S) SELECTED BY ADVANCED VOLUME SELECTIONThe number of non-SMS data sets for which volumes were selected atallocation time by Advanced Volume Selection.

Sample formatted summary record reportThe reports you generate can vary depending upon the options and filters youselect. This information provides an example of a formatted summary recordreport generated by the batch reporting utility JCL.

Figure 22 shows a sample formatted summary record report.

The following activity summary information is shown in the sample summaryrecord report:

* TIVOLI Advanced Allocation Management PROCESSING ACTIVITY SUMMARY REPORT *

INITIAL VOLUME PRIMARY SPACE ALLOCATION FAILURES RECOVERED....... 000001SUBSEQUENT VOLUME PRIMARY SPACE ALLOCATION FAILURES RECOVERED.... 000000UNDEFINED SECONDARY ALLOCATION SPACE ABENDS AVOIDED (D37)........ 000000UNAVAILABLE SECONDARY ALLOCATION SPACE ABENDS AVOIDED (B37/E37).. 000000UNAVAILABLE SECONDARY ALLOCATION SPACE ABENDS RECOVERED (B37/E37) 000000INSUFFICIENT VOLUMES DEFINED ABENDS RECOVERED (B37/E37).......... 000023POSSIBLE INSUFFICIENT SPACE ABENDS AVOIDED (B37/E37)............. 000023SPACE RELEASE OPTION ADDED TO PRIMARY OR SECONDARY ALLOCATION.... 000000INSUFFICIENT PDS DIRECTORY SPACE ERRORS RECOVERED................ 000000NOT CATLGD 2 ERRORS PROCESSED.................................... 000002DATA SETS INITIALIZED............................................ 000000DATA SETS PROCESSED BY RULEDEF_TEST MODE......................... 000000ALLOCATION PARMS SET BY ENHANCED ALLOCATION MANAGEMENT........... 000000NON-SMS VOLUME(S) SELECTED BY ADVANCED VOLUME SELECTION.......... 000000NUMBER OF DATA SET ALLOCATIONS FAILED BY TERM_ALLOC.............. 000000

Figure 22. Sample formatted summary record report


|||||||||||||||||

Initial volume primary space allocation failures recoveredThe number of times primary space was reduced by the PRIM_REDUCEfunction.

Subsequent volume primary space allocation failures recoveredThe number of times Advanced Allocation Management reduced theprimary allocation on a volume which was added.

Undefined secondary allocation space abends avoided (D37)The number of times the SEC_ALLOC function added a secondaryallocation during D37 processing when no secondary space value wasspecified (or, it was specified as zero).

Unavailable secondary allocation space abends avoided (B37/E37)The number of times the SEC_BEST function decreased the secondaryallocation to fit in the largest single extent on the volume duringend-of-volume processing.

Unavailable secondary allocation space abends recovered (B37/E37)The number of times the SEC_REDUCE function recovered from secondaryallocation space failures by reducing the allocation amount to a value thatwas consistent with the free space on the volume.

Insufficient volumes defined abends recovered (B37/E37)The number of times that the VOL_ADD function dynamically addedvolumes during end-of volume processing.

Possible insufficient space abends avoided (B37/E37)The number of times the SEC_INC function increased the size of thesecondary allocation as data set extends occurred after a particular extent,and at a particular volume number.

Space release option added to primary or secondary allocationThe number of times Advanced Allocation Management added theSPACE_RELEASE option to an allocation.

Insufficient PDS directory space for member save errors recoveredThe total number of PDS directory space errors recovered as a result of theAdvanced Allocation Management PDS_DIR_INC function.

NOT CATLGD 2 errors processedDisplays the total number of NOT CATLGD 2 related errors processed byAdvanced Allocation Management since the started task was initialized.

Data sets initializedDisplays the number of data sets that have been initialized by AdvancedAllocation Management.

Data sets processed by RULEDEF_TEST modeThe total number data allocations or extends that matched a RULEDEFINCLUDE or EXCLUDE statement which had RULEDEF_TEST set toENABLE.

Allocation parms set by Enhanced Allocation ManagementThe number of data set parameters that were added, changed or deletedby Enhanced Allocation Management.

Non-SMS Volume(s) selected by Advanced Volume SelectionThe number of non-SMS data sets for which volumes were selected atallocation time by Advanced Volume Selection.


Number of data set allocations failed by TERM_ALLOCThe number of data set allocations that were forced to fail as a result of theTERM_ALLOC function.

Creating a custom report utilityIn addition to View Event History dialog facility and the batch reporting utility,Advanced Allocation Management provides record maps to allow users to write acustom reporting utility in the language of their choosing.

These record maps are provided:v A DSECT to be used by assembler programs to directly map the SMF records.v A record description of the raw records generated when DETAIL=(A or B) and

FORMAT=L are specified.

Although the latter record description is also in DSECT format, it can be tailored toany programming or report language syntax. Both record maps are generatedduring installation process and reside in the GLOSSMFR member of the AdvancedAllocation Management sample library.

Note: The SMF record is composed of triplets that define multiple record sections.If you are unfamiliar with the use of triplets in SMF record processing, seez/OS MVS System Management Facilities (SMF) for more information.

GLOSSMFR (DSECT)This topic shows an excerpt from the GLOSSMFR member.

Figure 23 on page 298 shows an excerpt from the GLOSSMFR member whichshows a portion of the SMFREC DSECT.


GLOSSMFR (detail record map)This topic shows the supplied FORMAT=L detail record map.

***********************************************************************SMFREC DSECT** SMF RECORD HEADER SEGMENT*

DS 0DSMFRECRPS DS 0CL72 FIXED LENGTH HEADERSMFRECRHD DS 0CL24 RECORD HEADER SECTIONSMFRECLEN DC FL2’0’ RECORD LENGTHSMFRECSEG DC BL2’0’ SEGMENT DESCRIPTORSMFRECFLG DC BL1’0’ HEADER FLAG BYTE -* SYSTEM INDICATOR* BIT 0 - SUBSYSTEM IDENTIFICATION* FOLLOWS SYSTEM* IDENTIFICATION* BIT 1 - SUBTYPES USED* BIT 2 RESERVED* BIT 3-6 VERSION INDICATORS* BIT 7 - RESERVED* SEE ’STANDARD SMF RECORD* HEADER’ FOR DETAILS.SMFRECRTY DC XL1’0’ RECORD TYPESMFRECTME DC FL4’0’ TIME RECORD WAS MOVED* TO SMF BUFFER, IN HUNDREDTHS* OF A SECOND.SMFRECDTE DC PL4’0000’ DATE THAT THE RECORD* WAS MOVED TO THE SMF BUFFER,* IN THE FORM OCYYDDDF(WHERE F IS THE* SIGN). FOR A TSO SESSION, THE DATE* IS THE LOGOFF DATE.SMFRECSID DC CL4’ ’ SYSTEM IDENTIFICATIONSMFRECWID DC CL4’0’ SUBSYSTEM IDENTIFIERSMFRECSTP DC FL2’0’ RECORD SUBTYPESMFRECSAR EQU 1 1 = SUBSYSTEM ACTIVITYSMFRECPAR EQU 3 3 = PROCESSING ACTIVITY** SELF DEFINING SECTION*SMFRECSDS DS 0CL48 SELF DEFINING SECTION*SMFRECSOF DC F’0’ OFFSET TO SUBSYSTEM ID SECTION* FROM START OF RECORD, INCLUDING* THE RDWSMFRECSLN DC FL2’0’ LENGTH OF SUBSYSTEM ID SECTIONSMFRECSON DC FL2’0’ NUMBER OF SUBSYSTEM ID SECTIONS*SMFRECAOF DC F’0’ OFFSET TO SUBSYSTEM ACTIVITY* SECTION FROM START OF RECORD,* INCLUDING THE RDWSMFRECALN DC FL2’0’ LENGTH OF SUBSYSTEM ACTIVITY* SECTIONSMFRECAON DC FL2’0’ NUMBER OF SUBSYSTEM ACTIVITY* SECTIONS*SMFRECJOF DC F’0’ OFFSET TO JOB IDENTIFICATION* SECTION FROM START OF RECORD,* INCLUDING THE RDWSMFRECJLN DC FL2’0’ LENGTH OF JOB IDENTIFICATION* SECTIONSMFRECJON DC FL2’0’ NUMBER OF JOB IDENTIFICATION* SECTIONS*

Figure 23. GLOSSMFR (SMFREC DSECT excerpt)


Event recording and reporting filter criteria and sort field descriptionsUse filter criteria and sort fields with Advanced Allocation Management eventrecording and reporting.

Filter criteria descriptionsUse filter criteria and sort fields with Advanced Allocation Management eventrecording and reporting.

************************************************************************ AOD1 RECORD DSECT *************************************************************************AODATA1 DSECT*AOD1RDW DC AL2(0,0) RDWAOD1RVER DC CL2’03’ RECORD VERSIONAOD1DATE DC CL10’ ’ DATE (YYYY/MM/DD FORMAT)AOD1TIME DC CL8’ ’ TIME (HH:MM:SS) FORMAT

DC CL4’ ’ RESERVEDAOD1SID DC CL4’ ’ MVS SYSTEM ID

DC CL8’ ’ RESERVEDAOD1SSID DC CL4’ ’ ADVANCED ALLOCATION MGMT SUBSYS IDAOD1ATYP DC CL4’ ’ ADDRESS SPACE TYPE(JOB/STC/TSU/APPC)AOD1JOBN DC CL8’ ’ JOBNAME

DC CL8’ ’ RESERVEDAOD1STPN DC CL8’ ’ STEPNAMEAOD1PSTP DC CL8’ ’ PROCSTEPNAMEAOD1PGMN DC CL8’ ’ PROGRAMAOD1DSN DC CL44’ ’ DSNAMEAOD1DDN DC CL8’ ’ DDNAMEAOD1DSRG DC CL2’ ’ DSORG (PS/PO/DA/VS)AOD1PACT DC CL65’ ’ PROCESSING ACTIVITY

DC CL15’00’ RESERVEDAOD1TRKR DC CL7’0000000’ IF SPACE RELEASE; NUMBER OF TRACKS* RELEASED

DC CL1’ ’ RESERVED*AOD1NCTV DC CL6’ ’ IF NOT CATLGD 2, FIRST* VOLSER OF DATA SET IN ERROR*AOD1NCTO DC CL6’ ’ IF NOT CATLGD 2, FIRST* VOLSER OF OLD DATA SET*AOD1NCCD DC CL4’ ’ ABEND CODE FOR NOTCAT2*AOD1NCNM DC CL44’ ’ FOR NOTCAT2=RENAME, THE NEW* DATA SET NAME*AOD1SDSP DC CL3’ ’ STATUS DISPOSITION -* (NEW/SHR/OLD/MOD)AOD1NDSP DC CL7’ ’ NORMAL DISPOSITION - (PASS/* KEEP/DELETE/CATLG/UNCATLG)AOD1ADSP DC CL7’ ’ ABNORMAL DISPOSITION -* (KEEP/DELETE/CATLG/UNCATLG)AOD1SMSM DC CL1’ ’ SMS-MANAGED DATA SET (Y/N)AOD1TEMP DC CL1’ ’ TEMPORARY DATA SET (Y/N)AOD1SMDC DC CL8’ ’ SMS DATA CLASSAOD1SMSC DC CL8’ ’ SMS STORAGE CLASSAOD1SMMC DC CL8’ ’ SMS MANAGEMENT CLASSAOD1SMSG DC CL8’ ’ SMS 1ST OR ONLY STORGRP NAMEAOD1LINE DC CL8’ ’ MATCHING RULEDEF LINE NUMBER*AODATA1L EQU *-AODATA1 LENGTH OF RECORD** END OF AODATA MAPPING ....*

Figure 24. FORMAT=L detail record map


These filter criteria are available for use with Advanced Allocation Managementevent recording and reporting. Value prefixes are allowed for the criteria asindicated. A value prefix is one or more characters followed by an asterisk "*" thatallows matching to occur on a portion of the value. For example, specifyingFILTER_SET=JOBNAME=AB* or, FILTER_SET=JOBNAME=(AB*) will allow all jobswhose names begin with "AB" to pass filtering.

ADISP=valueAbnormal termination disposition. Valid values are:v KEEPv DELETEv CATLGv UNCATLG

DATACLAS=valueSMS data class (1 to 8 characters). Value prefix allowed.

DDNAME=valueddname (1 to 8 characters). Value prefix is allowed.

DSNAME=valuedata set name (1 to 44 characters). Value prefix is allowed.

DSORG=valueData set organization (2 characters). Valid values are:v PS (physical sequential)v PO (partitioned organization)v DA (direct access)v VS (VSAM)v KS —VSAM key-sequenced data setv RR—Either a VSAM variable-length or fixed-length relative-record data

setv ES—VSAM entry-sequenced data setv LD—VSAM linear data setv NV—Non-VSAM data set

Note: If you specify DSORG=VS, all records with a DSORG value of eitherKS, ES, RR or LD will also be selected in addition to those with thegeneric value of VS. Likewise, if you specify a DSORG of NV, allrecords with a DSORG value of PS, PO, or DA will also be selectedin addition to those with the generic value of NV.

ENDTIME=valueAn end time value specified in yyyy/mm/dd-hh:mm:ss format (where:yyyy = year, mm = month, dd = day, hh = hour, mm = minutes, and ss =seconds). ENDTIME used in conjunction with STARTTIME can be used tospecify a time frame.

Note: You must specify a hyphen (-) in between the date and time values.For example: 2004/09/02-10:25:00. Embedded spaces between thedate and time values are not permitted.

JOBNAME=valuejobname (1 to 8 characters). Value prefix is allowed.

JOBTYPE=valuejobtype. Valid values are:


v JOB (a normal job address space)v STC (started task)v TSU (time-sharing user)v APPC (APPC address space)

MGMTCLAS=valueSMS management class (1 to 8 characters). Value prefix allowed.

NDISP=valueNormal termination disposition. Valid values are:v PASSv KEEPv DELETEv CATLGv UNCATLG

PROGRAM=valueprogram name (1 to 8 characters). Value prefix is allowed.

PROCSTEPNAME=valueprocstepname (1 to 8 characters). Value prefix is allowed.

SDISP=valueStatus disposition. Valid values are:v NEWv SHRv OLDv MOD

SMS-MANAGED=valueSMS-management. Valid values are:v (Y)ESv (N)O

STARTTIME=valueA start time value specified in yyyy/mm/dd hh:mm:ss format (where:yyyy = year, mm = month, dd = day, hh = hour, mm = minutes, and ss =seconds). STARTTIME used in conjunction with ENDTIME can be used tospecify a time frame.

Note: You must specify a hyphen (-) between the date and time values.For example: 2004/09/02-10:25:00. Embedded spaces between thedate and time values are not permitted.

SUBSYS=valueAdvanced Allocation Management subsystem ID (1 to 4 characters). Valueprefix is allowed.

STEPNAME=valuestepname (1 to 8 characters). Value prefix is allowed.

STORCLAS=valueSMS storage class (1 to 8 characters). Value prefix allowed.

STORGRP=valueSMS first or only storage group (1 to 8 characters). Value prefix allowed.


SYSID=valueMVS system ID (1 to 4 characters). Value prefix is allowed.

TEMPDS=valueTemporary data set. Valid values are:v (Y)ESv (N)O

Sort fieldsThese sort fields are available for use with event recording and reporting.

ACTIVITYSpecify ACTIVITY to sort the report by Advanced Allocation Managementprocessing action.

ADISPSpecify ADISP to sort the report by abnormal termination disposition.

DATACLASSpecify DATACLAS to sort the report by SMS data class.

DATETIMESpecify DATETIME to sort the report by time frame.

DDNAMESpecify DDNAME to sort the report by ddname.

DSNAMESpecify DSNAME to sort the report by data set name.

DSORGSpecify DSORG to sort the report by data set organization.

JOBNAMESpecify JOBNAME to sort the report by job name.

JOBTYPESpecify JOBTYPE to sort the report by job type.

MGMTCLASSpecify MGMTCLAS to sort the report by SMS management class.

NDISPSpecify NDISP to sort the report by normal termination disposition.

PROGRAMSpecify PROGRAM to sort the report by program name.

PROCSTEPNAMESpecify PROCSTEPNAME to sort the report by procstepname.

SDISPSpecify SDISP to sort the report by status disposition.

SMS-MANAGEDSpecify SMS-MANAGED to sort the report by SMS-managementspecification.

STEPNAMESpecify STEPNAME to sort the report by step name.

STORCLASSpecify STORCLAS to sort the report by SMS storage class.


STORGRPSpecify STORGRP to sort the report by SMS storage group.

SUBSYSSpecify SUBSYS to sort the report by Advanced Allocation Managementsubsystem ID.

SYSIDSpecify SYSID to sort the report by MVS system ID.

TEMPDSSpecify TEMPDS to sort the report by temporary data set specification.



Chapter 15. Troubleshooting

Consult these troubleshooting topics to help you diagnose and resolve anyproblems you might encounter.

Disabling product-level intercepts

When the product-level intercepts are enabled, Advanced Allocation Managementperforms processing. When you disable the intercepts, you allow the AdvancedAllocation Management started task to remain active without performing anyprocessing. Disabling the intercepts can be helpful in certain situations when youdo not want to shut down Advanced Allocation Management completely. Forexample, if Advanced Allocation Management is running and processing is notoccurring as expected, you can disable the intercepts to help isolate the cause ofthe problem and collect any information (such as dumping the address space) thatyou can use to troubleshoot the problem.

Note: Disabling (or enabling) the product-level intercepts disables (or enables) theintercepts for all active Advanced Allocation Management subsystems.

Bypassing specific processing

When Advanced Allocation Management does not operate as expected for aparticular job or started task, and the process is critical to production processing,you can force Advanced Allocation Management to bypass the area of processingin question without shutting down the product entirely for all other processing. Toaccomplish this, you can add a bypass ddname to any jobstep JCL to forceAdvanced Allocation Management to bypass processing for all data sets accessedby the step. The ddname is AOBYPASS and the format of the DD statement is:

//AOBYPASS DD DUMMY

This statement can be added anywhere after a step's EXEC statement and beforethe next step's EXEC statement or "// " (end of job). For example://PDUSER#2 JOB (ACCT#),’PDUSER’,// MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID//*//JOBLIB DD DISP=SHR,// DSN=DSN.V710.SDSNLOAD//*//DSNTEP2 EXEC PGM=IKJEFT01,DYNAMNBR=20//AOBYPASS DD DUMMY//SYSTSPRT DD SYSOUT=*.-- PROCESSING TO BYPASS -----.//DSNTEP3 EXEC PGM=IKJEFT01,DYNAMNBR=20

Using the bypass ddname enables you to avoid the processing in question withoutrequiring extensive time-consuming modifications to the rule definitions.

Note: You can also use the bypass ddname to systematically isolate specific areasof processing in order to locate the cause of a particular problem.

305

Generating trace data

When Advanced Allocation Management does not operate as expected for aparticular job or started task, you can add a trace ddname to any jobstep JCL togenerate trace data for diagnostic purposes. The ddname is AOTRACE and theformat of the DD statement is://AOTRACE DD DUMMY

This statement can be added anywhere after a step's EXEC statement and beforethe next step's EXEC statement or "// " (end of job).

For example://PDUSER#2 JOB (ACCT#),’PDUSER’,// MSGCLASS=X,CLASS=A,NOTIFY=&SYSUID//*//JOBLIB DD DISP=SHR,// DSN=DSN.V710.SDSNLOAD//*//DSNTEP2 EXEC PGM=IKJEFT01,DYNAMNBR=20//AOTRACE DD DUMMY//SYSTSPRT DD SYSOUT=*..//DSNTEP3 EXEC PGM=IKJEFT01,DYNAMNBR=20

Note: The AOTRACE DD should only be used at the direction of technicalsupport.


Chapter 16. Frequently asked questions

Consult these questions and answers to help you understand more about usingAdvanced Allocation Management.

Installation and configuration

Question: Are there any special sizing considerations for the Advanced AllocationManagement control data set?

Answer: Because the Advanced Allocation Management control data set containsrelatively little data, there are no special sizing considerations. The space valuessupplied with the installation JCL are sufficient.

Definition management

Question: Is it true that an INCLUDE JOBNAME=xxxxxxx definition by itself willallow processing for that jobname with all of the defaults specified at thebeginning of the parameter member?

Answer: Yes. The only time you need to specify function keywords and valuesafter selection criteria is when you want to specify a value other than the defaultvalues. Otherwise, all defaults will be applied.

Question: Rule definitions are processed in a top-down order. Does this means thatas soon as a match is found, the process exits and does not process the remainingparameters?

Answer: Yes. The only exception is when you specify the CONTINUE keyword.The CONTINUE keyword specifies that RULEDEFS processing should continueeven if the current RULEDEF encounters a match. (Because all of the AdvancedAllocation Management definitions are specified together with the selectioncriteria, there is no multiple-member evaluation.)

Question: If you have multiple programs or jobnames that you want to include orexclude from Advanced Allocation Management processing, do you need separateINCLUDE and EXCLUDE statements for each one? In other words, you cannotcombine more than one program in an INCLUDE or EXCLUDE statement.

Answer: Yes, that is correct (one selection of a given type per INCLUDE orEXCLUDE statement). However, you can put jobname and program selectioncriteria together on a single INCLUDE or EXCLUDE definition.

Using Advanced Allocation Management

Question: What would be the benefit (or need) of running multiple AdvancedAllocation Management subsystems in a single system environment? Under whatkind of circumstances is the use of multiple Advanced Allocation Managementsubsystems recommended?

Answer: The most common reason is to run production and test versionsconcurrently.

307

Question: The SMS data class has a 'Space Constraint Relief' attribute which I canuse to reduce space up to a specific percentage. This definition enables me toreduce primary allocation of the data sets. However, if I use the AdvancedAllocation Management PRIM_REDUCE function for an SMS-managed data set,which definition is given priority—the SMS definition or the Advanced AllocationManagement definition?

Answer: Advanced Allocation Management handles both SMS andnon-SMS-managed data sets. When using SMS, think of Advanced AllocationManagement an extension to DFSMS. In other words, when SMS definitions havebeen defined, those definitions are implemented first and then any AdvancedAllocation Management definitions will take effect.


Chapter 17. Subsystem options

Advanced Allocation Management subsystem options are the global definitionsand general operation options that determine how Advanced AllocationManagement functions.

S1_INTERCEPTSpecifies whether initialization of S1 (STOW) intercept is to be enabled ordisabled at product startup. The default is ENABLE. Specify DISABLE onlywhen conflicts are occurring with other software that intercept STOWprocessing.

Note: Each time you modify this parameter setting within the OPTIONSmember, you must IPL the system and then restart AdvancedAllocation Management in order for the new setting to take effect.

SSID The unique four character alphanumeric Advanced Allocation Managementsubsystem identifier that identifies a specific instance of AdvancedAllocation Management. For example: AOP1, AOP2, AOAA, and so on.The default is AOPT.

SECURITY_CLASSThe default is FACILITY.

INITIAL_RULEDEFThe name of the rule definitions member to use upon startup. For example:RULESABC, RULESET2, and so on. The default is RULEDEFS.

INITIAL_VGRPDEFThe name of the volume group definitions member to use upon startup.For example: VGRPFST, VGRPD002. The default is VGRPDEFS.

Z1_INTERCEPTSpecifies whether initialization of the Z1 (step termination) intercept is tobe enabled or disabled at product start-up. The default is DISABLE.Specify ENABLE only if you would like to use the DATASET_INITfunction. Valid values are:v ENABLE—Z1 intercept is to be initialized at product start-up.v DISABLE— Z1 intercept is not to be initialized at product start-up.

Note: Each time you modify this parameter setting within the OPTIONSmember, you must IPL the system and then restart AdvancedAllocation Management in order for the new setting to take effect.

Subsystem options modification and display referenceAdvanced Allocation Management subsystem options can be modified anddisplayed in a variety of ways.

Table 13 on page 310 provides a reference that shows how the options can bemodified and where the options appear (on the dialog or console).

309

Table 13. Subsystem options modification and display reference

Option

Modifyfromdialog?

Modify usingoperatorcmd?

Specify inOPTIONSmember?

Specify in startparameters?

Display indialog?

Display onconsole?

S1_INTERCEPT No No Yes No No No

SSID No No Yes No Yes Yes

SECURITY_CLASS No No Yes No No No

(Name of activeRULEDEFS)

Yes Yes Yes No Yes Yes

(Name of activeVGRPDEFS)

Yes Yes Yes No Yes Yes


Chapter 18. Operator commands

Advanced Allocation Management operator commands enable authorized users toperform selected operations.

Advanced Allocation Management offers several different types of operatorcommands that can be used to display the status of Advanced AllocationManagement, to enable and disable certain functions, and to dynamically alterprocessing without requiring a shutdown or quiesce of the product.

Issuing commandsOperator commands are issued using the MVS™ MODIFY command therefore, thecommands should be prefixed with "MODIFY stcname," (where stcname is the nameof the started task) followed immediately by the command.

Note: Operator commands must be entered from an MVS operator console orusing a facility that issues MVS commands, such as SDSF.

The following are examples of operator commands:MODIFY stcname,ACTIVATE RULEDEFS member

orF stcname,ACTIVATE RULEDEFS member

Display commandsDisplay commands provide information about Advanced Allocation Management,such as the current subsystem and whether or not the product intercepts areenabled on the issuing operator's console.

Note: Commands in this category do not affect Advanced Allocation Managementconfiguration.

DIAGNOSEDisplays diagnostic information.

Note: This command should only be used at the direction of technicalsupport.

DISPLAY SUBSYSTEMDisplays information about the current Advanced Allocation Managementsubsystem.

DISPLAY SUBSYSTEM ALLDisplays information about all Advanced Allocation Managementsubsystems on the current z/OS image.

DISPLAY RULEDEFSDisplays information (the rule definitions member name that is currentlyactive and the date and time it was activated) about the rule definitions forthe current Advanced Allocation Management subsystem.

DISPLAY VGRPDEFSDisplays information (the volume group definitions member name that is

311

currently active and the date and time it was activated) about the volumegroup definitions for the current Advanced Allocation Managementsubsystem.

DISPLAY INTERCEPTSDisplays whether or not the product-level intercepts are enabled ordisabled.

Note: There are one set of intercepts for any and all subsystems on a z/OSimage.

DISPLAY ALLPerforms the equivalent actions of the following operator commands:v DISPLAY INTERCEPTSv DISPLAY SUBSYSTEMv DISPLAY RULEDEFSv DISPLAY VGRPDEFS

Enable and disable commandsEnable and disable commands enable or disable specific Advanced AllocationManagement functions.

ENABLE INTERCEPTSEnables the product-level intercepts.

ENABLE SUBSYSTEMEnables the subsystem for processing.

DISABLE INTERCEPTSDisables the product-level intercepts.

DISABLE SUBSYSTEMDisables the subsystem for processing. Disabling the subsystem willprevent it from participating in any new events such as out-of-spaceconditions.

Dynamic configuration commandsDynamic configuration commands enable you to dynamically modify AdvancedAllocation Management rule or volume group definitions at any time withoutrequiring you to shutdown or perform a quiesce of the product.

ACTIVATE RULEDEFS memberActivates a new or updated rule definitions member. Advanced AllocationManagement reads the contents of the specified rule definitions memberand then creates the appropriate control blocks.

ACTIVATE VGRPDEFS memberActivates a new or updated volume group definitions member. AdvancedAllocation Management reads the contents of the specified volume groupdefinitions member and then creates the appropriate control blocks.


Appendix A. Advanced Allocation Management messageformat

Advanced Allocation Management messages adhere to the following format.

Message format descriptionGLOinnnnx

Where:

GLO Indicates that the message was issued by Advanced AllocationManagement

i Indicates the message identifier

nnn Indicates the message identification number

x Indicates the severity of the message:

A Information message. User action required.

E Error message. Some errors might be user-correctable, read theUser Response text to determine the appropriate course of action.

F Fatal error message. Read the User Response text to determine theappropriate course of action.

I Information message. No user action required.

W Warning message. Results might not be as expected.

Each message also includes the following information:

Explanation:The Explanation section explains what the message text means, why itoccurred, and what its variables represent.

User response:The User response section describes whether a response is necessary, whatthe appropriate response is, and how the response will affect the system orprogram.

313


Appendix B. Dialog messages

These messages are related to issues with ISPF or with entries made on theAdvanced Allocation Management screens.

GLO002E INVALID SELECTION - PLEASEENTER A VALID OPTION OR X TOEXIT

Explanation: An invalid selection was entered.

User response: Please choose a valid selection.

GLO003E INVALID DATASET NAME

Explanation: The data set name provided is not valid.

User response: Please provide a valid data set name.

GLO004E DATASET DOESN’T EXIST. ENTERTHE CORRECT DATASET OR USESSID

Explanation: The specified data set does not exist.

User response: Please specify the correct data set, oran Advanced Allocation Management subsystem ID.

GLO005E INVALID VALUE - VALID VALUESARE (V,E,R,D,S, BLANK)

Explanation: An invalid value was entered.

User response: Please input a valid value V (View), E(Edit), R (Rename), D (Delete), S (Syntax-check), orblank (display list).

GLO006E INVALID MEMBER. ENTER THECORRECT MEMBER NAME

Explanation: An invalid member name was entered.

User response: Please specify a valid member name.

GLO007E ISPF ERROR: ZERRLM

Explanation: An ISPF error has occurred.

User response: Please contact IBM Support.

GLO008E MEMBER ALREADY EXISTS IN THISDATASET

Explanation: The specified member already exists inthe data set.

User response: Please specify another member name.

GLO009I OPERATION COMPLETEDSUCCESSFULLY

Explanation: This message indicates that the operationhas completed without error.

User response: No action is required.

GLO010E NO ACTIVE SUBSYSTEMS FOUND

Explanation: This message indicates that AdvancedAllocation Management could not locate any activesubsystems.

User response: An Advanced Allocation Managementsubsystem must be active. An Advanced AllocationManagement subsystem is considered active when theAdvanced Allocation Management started taskassociated with that subsystem ID is currently runningand the product-level intercepts are enabled.

GLO011E ACTIVE SUBSYSTEM ssid NOTFOUND

Explanation: This message indicates that AdvancedAllocation Management could not locate the specifiedsubsystem.

User response: Verify the subsystem ID and re-specifythe subsystem ID if needed.

GLO012E LOG DATASET DOESN’T EXIST FORTHE ACTIVE SUBSYSTEM

Explanation: The log data set you specified does notexist for the Advanced Allocation Managementsubsystem.


GLO013E INVALID VALUE - PLEASE USE "S" TOSELECT AN ACTIVE SUBSYSTEM

Explanation: An invalid value was entered to select anactive subsystem.

User response: Please type S to select a subsystem.

GLO014E INVALID VALUE - PLEASE ENTER "E"OR "D" VALUE

Explanation: An invalid value was entered.

315

User response: Please select either E (ENABLE) or D(DISABLE).

GLO015E INVALID VALUE - PLEASE USEFORMAT "MM:SS".

Explanation: The value entered for the time intervalwas not provided in the correct format.

User response: Please enter the time interval in theformat mm:ss (minutes:seconds).

GLO016E GLOQUERY FAILED - RETURN CODE:RCREG15

Explanation: This message indicates that a queryoperation has failed. The return code (RCREG15) isprovided.


GLO017E GLOUPDATE FAILED - RETURNCODE: RCREG15

Explanation: This message indicates that an updateoperation has failed. The return code (RCREG15) isprovided. Valid return codes are:

v 0 — The request was successful. The request updateswere made.

v 4 — A request to activate a RULEDEF or VGRPDEFmember failed. See the Advanced AllocationManagement job log for a description of the errors.

v 8 — Sufficient storage is not available for the updaterequest. Try logging on with a larger region size.

v 12 — Advanced Allocation Management has notbeen started on the system. No updates are possible.

User response: If the return code is greater than 1000please contact IBM Support.

GLO018E GLOSCHECK FAILED - RETURNCODE: RCREG15

Explanation: This message indicates that a checkoperation has failed. The return code (RCREG15) isprovided.


GLO019E ALLOCATION ERROR - AN ERRORWAS ENCOUNTERED ALLOCATINGTHE SYNTAX DD - PROCESS NOTCOMPLETED

Explanation: This message indicates that an erroroccurred during allocation.


GLO020E TRUNCATION ERROR DISPLAYINGPANEL IN &PNLNAME - RC16

Explanation: This message indicates that a truncationerror occurred when displaying the specified panel(&PNLNAME). The return code is provided.


GLO021E SEVERE ERROR DISPLAYING PANELIN &PNLNAME - RC20

Explanation: This message indicates that a severeerror occurred when displaying the specified panel(&PNLNAME). The return code (RC20) is provided.


GLO022E UNEXPECTED RETURN CODE FROMPANEL IN &PNLNAME

Explanation: This message indicates that AdvancedAllocation Management encountered an unexpectedreturn code from the specified panel (&PNLNAME).


GLO023I LOG DATA SET &LOGDSN IS EMPTY.

Explanation: The specified log data set is empty.

User response: None required.

GLO024E MEMBER IS NOT IN RULEDEFINITION FORMAT. PLEASEVERIFY THE FORMAT.

Explanation: The specified member is not in thecorrect format.

User response: Verify that the Rule Definition memberhas a comment card in the required format.

GLO025E MEMBER IS NOT IN VGRPDEFINITION FORMAT. PLEASEVERIFY THE FORMAT.

Explanation: The specified member is not in thecorrect format.

User response: Verify that the VGRP member has acomment card in the required format.

GLO026E MEMBER IS NOT IN RULE OR VGRPDEFINTION FORMAT. SYNTAXCHECK WASN’T COMPLETED.

Explanation: This message indicates that an invalidmember type was specified. The syntax-check option isonly valid for Rule Definition and VGRP Definitionmember types.

User response: Please specify a valid member type.

GLO015E • GLO026E


GLO027E SMF SOURCE FILE MUST NOT BEBLANK.

Explanation: The SMF Source File field must not beblank.

User response: Please specify the SMF source file tobe searched for Advanced Allocation Managementevent records.

GLO028E ADDITIONAL SMF SOURCE FILESCAN ONLY BE BLANK OR "/".

Explanation: An invalid option was entered.

User response: To specify additional SMF source files,type "/" to display the Tivoli Advanced AllocationManagement SMF Source Files screen.

GLO029E ADDITIONAL FILTER CRITERIA CANONLY BE BLANK OR "/".


User response: To specify additional filter set criteria,type "/" to display the Tivoli Advanced AllocationManagement Filter Set Criteria screen.

GLO030E DETAIL REPORT CAN ONLY BE "Y","N", "B", OR "A".


User response: Specify Y to include detail records;otherwise, specify N (do not include detail records).

GLO031E SUMMARY REPORT CAN ONLY BE"Y" OR "N".


User response: Specify Y to generate a summary ofthe records that were processed; otherwise, specify N(do not generate a summary).

GLO032E FORMAT CAN ONLY BE "R" OR "L".


User response: Specify R (report output) or L (listoutput).

GLO033E OUTPUT MODE CAN ONLY BE "V"OR "B"


User response: Specify V (View) or B (browse).

GLO034E ALLOCATION ERROR - AN ERRORWAS ENCOUNTERED ALLOCATINGTHE CNTLIN DD - PROCESS NOTCOMPLETED

Explanation: An error was encountered allocatingCNTLIN DD.

User response: Make sure at least 10 cylinders areavailable on at least one user-accessible DASD volume.Look for any related allocation failure messagescontaining additional information regarding the natureof the error. Log off and log back on, then retry thefailing dialog function. If the problem persists, contactIBM Support.

GLO035E ALLOCATION ERROR - AN ERRORWAS ENCOUNTERED ALLOCATINGTHE CNTLOUT DD - PROCESS NOTCOMPLETED

Explanation: An error was encountered allocatingCNTLOUT DD.


GLO036E ALLOCATION ERROR - AN ERRORWAS ENCOUNTERED ALLOCATINGTHE HISTOUT DD - PROCESS NOTCOMPLETED

Explanation: An error was encountered allocatingHISTOUT DD.


GLO037E CAN'T OPEN CNTLOUT DD.

Explanation: Advanced Allocation Management wasunable to open CNTLOUT DD.

User response: Log off and log back on, then retry thefailing dialog function. If the problem persists, contactIBM Support.

GLO038E CAN'T OPEN HISTOUT DD.

Explanation: Advanced Allocation Management wasunable to open HISTOUT DD.

User response: Log off and log back on, then retry the

GLO027E • GLO038E

Appendix B. Dialog messages 317

failing dialog function. If the problem persists, contactIBM Support.

GLO039E SMF RECORD ID CAN ONLY BENUMERIC.

Explanation: A numeric SMF Record ID is required.

User response: Please specify a numeric SMF RecordID.

GLO040E SMF RECORD ID MUST NOT BEBLANK.

Explanation: The SMF Record ID is required.

User response: Please specify a valid SMF record ID.

GLO039E • GLO040E


Appendix C. Subsystem and started task messages

These messages are related to issues with the Advanced Allocation Managementsubsystem or started task.

GLO1000E INSUFFICIENT OPERATING SYSTEMLEVEL; OS/390 R2.10 (SP6.10) ORHIGHER REQUIRED

Explanation: Product initialization has determinedthat the level of the operating system is not at a levelhigh enough to support the product.

User response: Run the product on a system withOS/390 at the 2.10 level or above.

GLO1001E PRODUCT IS NOT RUNNINGAPF-AUTHORIZED

Explanation: Product initialization has determinedthat the libraries from which the product is beingloaded are not APF-authorized.

User response: Run the product from APF-authorizedlibraries.

GLO1001I RULEDEFS ACTIVATIONSUCCESSFUL –ssss

Explanation: This message is issued to the operatorconsole following successful activation of ruledefinitions using the ACTIVATE RULEDEFS operatorcommand.


GLO1002E INSUFFICIENT VIRTUAL STORAGEFOR PRODUCT PROCESSING

Explanation: Product initialization was unable toobtain the required above-the-line storage.

User response: Increase the amount of availableabove-the-line storage and attempt to restart theproduct. If this is not successful, contact IBM Support.


Explanation: Product initialization was unable toobtain the required below-the-line storage.

User response: Increase the amount of availablebelow-the-line storage and attempt to restart theproduct. If this is not successful, contact IBM Support.

GLO1004E UNABLE TO LOCATE REQUIREDDDNAME - CONTROL

Explanation: During product initialization, theCONTROL DD statement was unable to be located inthe product started task procedure.

User response: The CONTROL DD statement isrequired. Add the CONTROL DD statement to theAdvanced Allocation Management started taskprocedure and retry.

GLO1004I VGRPDEFS ACTIVATIONSUCCESSFUL –ssss

Explanation: This message is issued to the operatorconsole following successful activation of volumegroup definitions using the ACTIVATE VGRPDEFSoperator command.


GLO1005E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JFCBFOR DDNAME CONTROL, RC=rrrrrrrr

Explanation: An internal error (rrrrrrrr) occurredwhile processing the CONTROL DD statement duringproduct initialization.

User response: Make sure that the CONTROL DDstatement points to a valid partitioned data set andretry. If the error persists, contact IBM Support.

GLO1006E UNABLE TO LOCATE REQUIREDDDNAME - OPTIONS

Explanation: During product initialization, theOPTIONS DD statement was unable to be located inthe product started task procedure.

User response: The OPTIONS DD statement isrequired. Add the OPTIONS DD statement to theAdvanced Allocation Management started taskprocedure and retry.

GLO1007E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JFCBFOR DDNAME OPTIONS, RC=rrrrrrrr

Explanation: An internal error (rrrrrrrr) occurredwhile processing the OPTIONS DD statement duringproduct initialization.

User response: Make sure that the OPTIONS DDstatement points to a valid data set and retry. If theerror persists, contact IBM Support.

319

GLO1007I RULEDEFS ACTIVATED ONmm/dd/yyyy at hh:mm:ss FROM MEMBERmember -ssss

Explanation: This message is issued in response to theDISPLAY RULEDEFS operator command. In themessage text mm/dd/yyyy indicates the month, day andyear on which the rule definitions were activated,hh:mm:ss is the time in hours, minute and seconds atwhich the rule definitions were activated, and memberis the member name from the control data set fromwhich the rule definitions were processed.


GLO1008I RULEDEFS NOT ACTIVATED –ssss

Explanation: This message is issued in response to theDISPLAY RULEDEFS operator command when no ruledefinitions have been activated.


GLO1009E OPEN FAILED FOR PROCESSINGOPTIONS MEMBER; DEFAULTOPTIONS USED

Explanation: Open processing was unsuccessful forthe OPTIONS member so the default options wereused.

User response: Make sure that the OPTIONS DDstatement points to a valid data set and retry. If theerror continues, contact IBM Support.

GLO1009I VGRPDEFS ACTIVATED ONmm/dd/yyyy at hh:mm:ss FROM MEMBERmember -ssss

Explanation: This message is issued in response to theDISPLAY VGRPDEFS operator command. In themessage text, mm/dd/yyyy indicates the month, day andyear on which the volume group definitions wereactivated and hh:mm:ss indicates the time in hours,minutes and seconds, at which the volume groupdefinitions were activated, and member is the membername from the control data set from which the volumegroup definitions were processed.


GLO1010I PRODUCT INTERCEPTS HAVE BEENENABLED

Explanation: This message is issued during productinitialization and indicates successful installation ofproduct intercepts.


GLO1012E ATTACH FOR GLOMAIN FAILED,RC=rrrrrrrr

Explanation: During product initialization, the startupof an internal task failed. The value rrrrrrrr identifiesthe internal error code.

User response: Examine other error messages thatmight have occurred at the same time as this messageto aid in determining the cause of the failure. If nocause can be determined, contact IBM Support.

GLO1013I PRODUCT TERMINATION ISCOMPLETE

Explanation: This message is issued in response to theproduct shutdown command at completion oftermination processing.


GLO1021E INVALID OPTION SPECIFIED -pppppppp

Explanation: During product initialization, an invalidkeyword was encountered when processing thesubsystem options in the OPTIONS member. The valuepppppppp is the invalid option encountered — or thevalue "(NONE)" if blank options were specified.

User response: Correct the specified option keywordand restart the product.

GLO1022E REQUIRED DELIMETER "=" ISMISSING - pppppppp

Explanation: During product initialization, whileprocessing the subsystem options in the OPTIONSmember, a keyword was encountered which requiredan equal sign (=) but it was found to be missing. Thevalue pppppppp indicates the associated keyword.


GLO1023E INVALID VALUE SPECIFIED FOROPTION - pppppppp

Explanation: During product initialization, whileprocessing the subsystem options in the OPTIONSmember, a keyword was encountered with an invalidvalue. The value pppppppp indicates the option with theincorrect value.


GLO1024I PROCESSING OPTION SET -SSID=ssss

Explanation: This message is issued during productinitialization to display the value (ssss) set for the SSIDkeyword in the OPTIONS member.

GLO1007I • GLO1024I



GLO1025E INVALID VALUE SPECIFIED FOROPTION - SSID=ssss

Explanation: During product initialization, whileprocessing the subsystem options in the OPTIONSmember, an incorrect value was encountered for theSSID option. The value ssss indicates the invalid value.


GLO1026I PROCESSING OPTION SET -INITIAL_RULEDEF=rrrrrrrr

Explanation: This message is issued during productinitialization to display the value (rrrrrrrr) specified forthe INITIAL_RULEDEF keyword in the OPTIONSmember.


GLO1027E INVALID VALUE SPECIFIED FOROPTION -INITIAL_RULEDEF=rrrrrrrr

Explanation: During product initialization, whileprocessing the subsystem options in the OPTIONSmember, an incorrect value was encountered for theINITIAL_RULEDEF option. The value rrrrrrrr indicatesthe invalid value.


GLO1028I PROCESSING OPTION SET -INITIAL_VGRPDEF=vvvvvvvv

Explanation: This message is issued during productinitialization to display the value (vvvvvvvv) specifiedfor the INITIAL_VGRPDEF keyword in the OPTIONSmember.


GLO1029E INVALID VALUE SPECIFIED FOROPTION -INITIAL_VGRPDEF=vvvvvvvv

Explanation: During product initialization, whileprocessing the subsystem options in the OPTIONSmember, an incorrect value was encountered for theINITIAL_VGRPDEF option. The value vvvvvvvvindicates the invalid value.


GLO1034E ERROR IN NAME/TOKEN RETRIEVALPROCESSING, RC=rrrrrrrr

Explanation: During product initialization, an internalsystem error (rrrrrrrr) was encountered in establishingthe product.


GLO1035E NAME/TOKEN ALREADY EXISTS,BUT TOKEN IS ZERO

Explanation: During product initialization, an internalsystem error was encountered in establishing theproduct.


GLO1036E NAME/TOKEN ALREADY EXISTS,BUT TOKEN DOES NOT POINT TO AVALID PRODUCT BLOCK

Explanation: During product initialization, an internalsystem error was encountered in establishing theproduct. Although there are other possible reasons forreceiving this message, the most likely cause is thatafter the current IPL, a version of Advanced AllocationManagement that is incompatible with AdvancedAllocation Management 3.1 was started prior to startingAdvanced Allocation Management 3.1.

User response: IPL the system before startingAdvanced Allocation Management 3.1. If this does notresolve the problem, contact IBM Support.

GLO1038E UNABLE TO OBTAIN STORAGE FORPRODUCT CONTROL BLOCK,RC=rrrrrrrr

Explanation: During product initialization,above-the-line CSA storage was unable to be obtained aproduct control block as indicated by the internalreturn code rrrrrrrr.

User response: Investigate and correct the shortage ofabove-the-line CSA storage and restart the product. Ifthe problem persists, contact IBM Support.

GLO1040E ERROR IN NAME/TOKEN CREATEPROCESSING, RC=rrrrrrrr

Explanation: During product initialization, an internalsystem error (rrrrrrrr) was encountered in establishingthe product.


GLO1041I PRODUCT INTERCEPTS HAVE BEENESTABLISHED

Explanation: This message is issued when allintercepts have been successfully established.

GLO1025E • GLO1041I

Appendix C. Subsystem and started task messages 321


GLO1042E UNABLE TO OBTAIN STORAGE FORCOMMON AREA ROUTINE,RC=rrrrrrrr

Explanation: During product initialization,above-the-line CSA storage was unable to be obtainedfor loading a required product routine as detailed bythe internal return code rrrrrrrr.

User response: Investigate and correct the shortage ofabove-the-line CSA storage and restart the product. Ifthe problem persists, contact IBM Support.

GLO1043E BLDL FAILED FOR mmmmmmmm,RC=rrrrrrrr

Explanation: During product initialization, a requiredload module was unable to be successfully located. Thevalue mmmmmmmm identifies the load module and thevalue rrrrrrrr specifies the internal return code in error.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task, or in the system LINKLISTconcatenation and then restart the product.

GLO1044E UNABLE TO DETERMINE ORIGIN OFmmmmmmmm

Explanation: During product initialization whileprocessing the product load module mmmmmmmm anerror was encountered.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task or in the system LINKLISTconcatenation and restart the product.

GLO1046E PRIVATE LOAD FAILED FORmmmmmmmm

Explanation: During product initialization, theprocessing of a product load module (mmmmmmm) tobe located in above-the-line private storage failed.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task, or in the system LINKLISTconcatenation and then restart the product. In addition,check the available amount of above-the-line privatestorage available for the Advanced AllocationManagement started task. After correcting the problem,restart the product. If the error cannot be determined,contact IBM Support.

GLO1047E COMMON LOAD FAILED FORmmmmmmmm

Explanation: During product initialization, theprocessing of a product load module (mmmmmmm) to

be located in above-the-line common storage, failed.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task, or in the system LINKLISTconcatenation and then restart the product. In addition,check the available amount of above-the-line commonstorage available for the Advanced AllocationManagement started task. After correcting the problem,restart the product. If the error cannot be determined,contact IBM Support.

GLO1048E UNABLE TO OBTAIN STORAGE FORA1 INTERCEPT, RC=rrrrrrrr

Explanation: During product initialization an error(rrrrrrrr) was encountered while attempting to obtainabove-the-line common storage for a product controlblock.

User response: Investigate a potential shortage ofabove-the-line common storage and restart the product.If the problem continues, contact IBM Support.

GLO1050E UNABLE TO LOCATE LPDE FORIEFW21SD

Explanation: During product initialization, a requiredpointer to an operating system module was unable tobe located.


GLO1052E UNABLE TO LOCATE IEFAB434

Explanation: During product initialization, a requiredoperating system module was unable to be located.


GLO1055E PAGE SERVICE LIST EXHAUSTEDFOR A1 INTERCEPT

Explanation: During product initialization, whileattempting to establish a product intercept, anunexpected internal error was encountered.


GLO1056E UNABLE TO OBTAIN STORAGE FORE1 INTERCEPT, RC=rrrrrrrr

Explanation: During product initialization, an error(rrrrrrrr) was encountered while attempting to obtainbelow-the-line common storage for a product controlblock.

User response: Investigate a potential shortage ofbelow-the-line common storage and restart the product.If the problem continues, contact IBM Support.

GLO1042E • GLO1056E


GLO1058E UNABLE TO LOCATE LPDE FORIGC0005E



GLO1060E UNABLE TO LOCATE IFG0554P



GLO1063E PAGE SERVICE LIST EXHAUSTEDFOR E1 INTERCEPT



GLO1064E UNABLE TO LOCATE LPDE FORIGC0002A



GLO1065W ENTRY POINT IN IGC0002A’S LPDEDOES NOT MATCH VCONREFERENCES



GLO1066E UNABLE TO OBTAIN STORAGE FORS1 INTERCEPT, RC=rrrrrrrr


User response: Investigate a potential shortage ofabove-the-line common storage and restart the product.If the problem persists, contact IBM Support.




GLO1070E UNABLE TO LOCATE IGG021AB



GLO1072E UNABLE TO LOCATE IGC0002F



GLO1073E PAGE SERVICE LIST EXHAUSTEDFOR S1 INTERCEPT



GLO1073W MAXIMUM ACTIVE SUBSYSTEMSEXCEEDED (4)

Explanation: The current iteration of AdvancedAllocation Management being started would exceed thelimit of four concurrently active subsystems on a singlez/OS system. Startup for the current iteration isterminated.

User response: If the current iteration of AdvancedAllocation Management is needed, shut down one ofthe already active Advanced Allocation Managementsubsystems and then restart the current iteration. Todisplay all currently active Advanced AllocationManagement subsystems use the"display,subsystems,all" command or select option 2from the Advanced Allocation Management onlinedialog.

GLO1074E DUPLICATE SUBSYSTEM FOUNDFOR SSID=ssss

Explanation: During product initialization, a duplicateproduct control block was encountered for thesubsystem ID ssss.







GLO1079E UNABLE TO LOCATE LPDE FORIEFW21SD

Explanation: During product initialization a requiredpointer to an operating system module was unable tobe located.


GLO1081E UNABLE TO LOCATE IEFAB4A0






GLO1085E UNABLE TO LOCATE LPDE FORIEFAB4A0



GLO1086E ENTRY POINT IN IEFAB4A0"S LPDEDOES NOT MATCH VCONREFERENCES




Explanation: During product initialization, an error(rrrrrrrr) was encountered while attempting to obtainabove-the-line common storage for a product controlblock.


GLO1089E UNABLE TO LOCATE LPDE FORIGDZILLA



GLO1091E UNABLE TO LOCATE IGDSSIRT






GLO1095E UNABLE TO LOCATE SSCT FOR SMS

Explanation: The process that sets the AdvancedAllocation Management intercepts was not able tolocate the subsystem control table for SMS.


GLO1096E FUNCTION IS NOT VALID FORSUBSYSTEM

Explanation: The process that sets the AdvancedAllocation Management intercepts found that thefunction code for SMS was not valid in the subsystemvector table.


GLO1097E UNABLE TO LOCATE LPDE FORIGDSSIRT



GLO1098E ENTRY POINT IN IGDSSIRT'S LPDEDOES NOT MATCH VCONREFERENCES





GLO1100E ACRONYM CHECK FAILED FORGSSB

Explanation: An internal error occurred within theproduct during product initialization.



Explanation: Main task startup was unable to obtainenough above-the-line private storage to initialize.

User response: Increase the amount of above-the-lineprivate storage. If the problem persists, contact IBMSupport.

GLO1102E ERROR OCCURRED INCROSS-MEMORY INITIALIZATION

Explanation: An internal error occurred during maintask start-up.


GLO1103E ATTACH FOR GLOLSRP FAILED,RC=rrrrrrrr -ssss

Explanation: An internal error (rrrrrrrr) wasencountered within the main product task whileattempting to attach a service subtask for subsystem IDssss.


GLO1105E ATTACH FOR GLODSRP FAILED,RC=rrrrrrrr -ssss

Explanation: An internal error (rrrrrrrr) wasencountered within the main product task whileattempting to attach a service subtask for subsystem IDssss.


GLO1105I SUBSYSTEM IS ACTIVE ANDENABLED

Explanation: This message indicates that the mainproduct task has successfully started and is now active.


GLO1106I SUBSYSTEM INITIALIZATION ISCOMPLETE

Explanation: This message is issued when the mainproduct task has successfully completed initializationprocessing.


GLO1107I PRODUCT TERMINATION HAS BEENREQUESTED

Explanation: A command to terminate the productwas successfully received.


GLO1111E UNABLE TO OBTAIN STORAGE FORCOMMON AREA ROUTINE,RC=rrrrrrrr

Explanation: Product subsystem initialization wasunable to obtain a sufficient amount of storage to loada required module.

User response: Check and increase the amountavailable above- and below-the-line storage and restartthe product. If the error persists, contact IBM Support.

GLO1112E BLDL FAILED FOR mmmmmmmm,RC=rrrrrrrr

Explanation: During product subsystem initialization,a required load module was unable to be successfullylocated. The value mmmmmmmm identifies the loadmodule and the value rrrrrrrr specifies the internalreturn code in error.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task or in the system LINKLISTconcatenation and then restart the product.

GLO1113E UNABLE TO DETERMINE ORIGIN OFmmmmmmmm

Explanation: An error was encountered duringproduct subsystem initialization while processing theproduct load module mmmmmmmm.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task or in the system LINKLISTconcatenation and then restart the product

GLO1115E INITIAL LOAD FAILED FORmmmmmmmm

Explanation: During product subsystem initialization,a required load module (mmmmmmmm) did not loadsuccessfully.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task or in the system LINKLISTconcatenation and then restart the product. In addition,check the available amount of above-the-line privatestorage available for the product started task. Aftercorrecting the problem restart the product. If the errorcannot be determined, contact IBM Support.



GLO1116E DIRECTED LOAD FAILED FORmmmmmmmm

Explanation: During product subsystem initialization,a required load module (mmmmmmmm) did not loadsuccessfully.

User response: Verify that the load modules for theproduct are accessible either in a STEPLIB in theproduct started task or in the system LINKLISTconcatenation and then restart the product.

GLO1117E NON-ZERO RETURN CODE FROMSYSEVENT, RC=rrrrrrrr -ssss

Explanation: During product subsystem initialization,an error (rrrrrrrr) was encountered when attempting tomake the product started task address spacenon-swappable for subsystem ssss.


GLO1118E ATTACH FOR GLOVIRP FAILED,RC=rrrrrrrr -ssss

Explanation: An internal error (rrrrrrrr) occurredwithin the main product task while attempting toattach a service subtask for subsystem ID ssss.


GLO1122E INVALID COMMAND SPECIFIED -cccccccc -ssss

Explanation: The product subsystem command parserreceived an error while processing the command(cccccccc) issued to the started task for subsystem IDssss.

User response: Correct and re-issue the command.

GLO1123E INVALID COMMAND SPECIFIED -cccccccc -ssss

Explanation: An invalid or null product subsystemcommand (cccccccc) was issued to the started task forsubsystem ID ssss.

User response: Correct and re-issue the command.

GLO1124E EXCESSIVE OPERANDS SPECIFIEDFOR COMMAND - cccccccc -ssss

Explanation: More operands than are allowed werespecified for the DISPLAY command issued (cccccccc) tothe product started task for subsystem ID ssss.

User response: Re-issue the command using thecorrect number of operands.

GLO1125E INSUFFICIENT OPERANDSSPECIFIED FOR COMMAND - cccccccc-ssss

Explanation: The command entered contains feweroperands than the minimum required. The commandentered is cccccccc. The subsystem ID is ssss.


GLO1126E INVALID OPERAND SPECIFIED FORCOMMAND - cccccccc -ssss

Explanation: The command entered contains aninvalid operand. The command entered is cccccccc. Thesubsystem ID is ssss.

User response: Correct the invalid operand andre-issue the command.

GLO1127I SUBSYSTEM IS ACTIVE | INACTIVEAND ENABLED | DISABLED -ssss

Explanation: This message is issued in response to theDISPLAY SUBSYSTEM or DISPLAY ALL operatorcommand and shows the ACTIVE or INACTIVE statusof the product subsystem and whether or not thesubsystem is ENABLED or DISABLED for thesubsystem ssss.


GLO1129I THERE ARE CURRENTLY NOSUBSYSTEMS -ssss

Explanation: This message is issued in response to theproduct operator command DISPLAY SUBSYSTEM ALLwhen no subsystems are located.


GLO1130I SUBSYSTEM xxxx IS ACTIVE |INACTIVE AND ENABLED |DISABLED -ssss

Explanation: This message is issued in response to theDISPLAY SUBSYSTEM ALL operator command issuedto subsystem ssss and shows the ACTIVE or INACTIVEstatus of each product subsystem as identified by xxxxand whether or not the subsystem is ENABLED orDISABLED.


GLO1131I RULEDEFS ACTIVATED ONmm/dd/yyyy AT hh:mm:ss FROMMEMBER mmmmmmmm -ssss

Explanation: This message is issued in response to theDISPLAY RULEDEFS operator command to subsystemID ssss and shows the date mm/dd/yyyy and timehh:mm:ss at which the active set of RULEDEFS was last



activated as well as the member name (mmmmmmmm)from which they were activated.


GLO1132I RULEDEFS NOT ACTIVATED -ssss

Explanation: This message is issued in response to theDISPLAY RULEDEFS operator command to subsystemID ssss when no RULEDEFS were found to have beenactivated.


GLO1133I VGRPDEFS ACTIVATED ONmm/dd/yyyy AT hh:mm:ss FROMMEMBER mmmmmmmm -ssss

Explanation: This message is issued in response to theDISPLAY VGRPDEFS operator command to subsystemID ssss and shows the date mm/dd/yyyy and timehh:mm:ss at which the active set of VGRPDEFS was lastactivated as well as the member name (mmmmmmmm)from which they were activated.


GLO1134I VGRPDEFS NOT ACTIVATED -ssss

Explanation: This message is issued in response to theDISPLAY VGRPDEFS operator command to subsystemID ssss when no VGRPDEFS were found to have beenactivated.


GLO1135I PRODUCT INTERCEPTS AREENABLED | DISABLED -ssss

Explanation: This message is issued in response to theDISPLAY INTERCEPTS operator command tosubsystem ID ssss and shows whether or not theintercepts are ENABLED or DISABLED.


GLO1136I PRODUCT-LEVEL TRACING ISENABLED | DISABLED -ssss

Explanation: This message is issued in response to theDISPLAY TRACING operator command to subsystemID ssss and shows whether or not the product tracingfacility is ENABLED or DISABLED.


GLO1137I SUBSYSTEM-LEVEL TRACING ISENABLED | DISABLED -ssss

Explanation: This message is issued in response to theDISPLAY TRACING operator command to subsystemID ssss and shows whether or not the subsystemtracing facility is ENABLED or DISABLED.



Explanation: More operands than are allowed werespecified for the ENABLE command issued (cccccccc) tothe Advanced Allocation Management started task forsubsystem ID ssss.


GLO1141I SUBSYSTEM IS NOW ENABLED -ssss

Explanation: This message is issued in response to theENABLE SUBSYSTEM operator command andindicates that the subsystem ssss was successfullyenabled.


GLO1142I PRODUCT INTERCEPTS ARE NOWENABLED -ssss

Explanation: This message is issued in response to theENABLE INTERCEPTS operator command andindicates that the intercepts for subsystem ssss weresuccessfully enabled.


GLO1144I TRACING FOR PRODUCT IS NOWENABLED -ssss

Explanation: This message is issued in response to theENABLE TRACING or ENABLE TRACING ALLoperator command for subsystem ID ssss and indicatesthat product level tracing is now enabled.


GLO1145I TRACING FOR SUBSYSTEM IS NOWENABLED -ssss

Explanation: This message is issued in response to theENABLE TRACING ALL operator command forsubsystem ID ssss and indicates that subsystem leveltracing is now enabled.



Explanation: More operands than are allowed werespecified for the DISABLE command issued (cccccccc) tothe product started task for subsystem ID ssss.


GLO1132I • GLO1146E


GLO1149I SUBSYSTEM IS NOW DISABLED -ssss

Explanation: This message is issued in response to theDISABLE SUBSYSTEM operator command andindicates that the subsystem ssss was successfullydisabled.


GLO1150I PRODUCT INTERCEPTS ARE NOWDISABLED -ssss

Explanation: This message is issued in response to theDISABLE INTERCEPTS operator command andindicates that the intercepts for subsystem ssss weresuccessfully disabled.


GLO1152I TRACING FOR PRODUCT IS NOWDISABLED -ssss

Explanation: This message is issued in response to theDISABLE TRACING or DISABLE TRACING ALLoperator command for subsystem ID ssss and indicatesthat product level tracing is now disabled.


GLO1153I TRACING FOR SUBSYSTEM IS NOWDISABLED -ssss

Explanation: This message is issued in response to theDISABLE TRACING ALL operator command forsubsystem ID ssss and indicates that subsystem leveltracing is now disabled.



Explanation: More operands than are allowed werespecified for the ACTIVATE command issued (cccccccc)to the Advanced Allocation Management started taskfor subsystem ID ssss.


GLO1175I RULEDEFS | VGRPDEFS MEMBERmmmmmmmm ACTIVATIONSUCCESSFUL -ssss

Explanation: This message is issued in response to theACTIVATE RULEDEFS operator command or the initialRULEDEFS activation (as indicated from the OPTIONSmember for subsystem ID ssss) to show that theRULEDEFS or VGRPDEFS from member mmmmmmmmwas successfully activated.


GLO1176I dddddddd MEMBER mmmmmmmmACTIVATION FAILED - SEEJESYSMSG FOR DETAILS -ssss

Explanation: This message is issued in response to theACTIVATE RULEDEFS operator command or the initialRULEDEFS activation (as indicated from the OPTIONSmember for subsystem ID ssss) to show that theRULEDEFS or VGRPDEFS from member mmmmmmmmwas not successful due to syntax errors.

User response: Review the error messages in the JESSYSMSG output for the Advanced AllocationManagement started task, and then correct the errorsand re-activate the RULEDEFS or VGRPDEFS.

GLO1177I dddddddd MEMBER mmmmmmmmACTIVATION FAILED - FAILURECODE cccc -ssss

Explanation: This message is issued in response to theACTIVATE RULEDEFS operator command, or theinitial RULEDEFS activation (as indicated from theOPTIONS member for subsystem ID ssss) to show thatthe RULEDEFS or VGRPDEFS from membermmmmmmmm was not successful due to an internalerror as denoted by cccc.

User response: Review any error messages in the JESSYSMSG output or the console log for the AdvancedAllocation Management started task to determine thepossible cause of the error, then correct the errors andre-activate the RULEDEFS or VGRPDEFS. If theproblem persists, contact IBM Support.

GLO1179I ORIGINAL VCON LOCATED ATlocation, VIA INSTRUCTIONSEQUENCE MATCHING- ssss

Explanation: During product initialization, AdvancedAllocation Management determined that a pointer to anoperating system module had been altered. This mostcommonly occurs when another software product hasset a hook for the module. Advanced AllocationManagement continues to try and locate the operatingsystem module by matching instruction sequences inthe calling module.

User response: None required.

GLO1180E UNABLE TO LOCATE IGC0002F VCONVIA INSTRUCTION SEQUENCEMATCHING- ssss

Explanation: During product initialization, AdvancedAllocation Management determined that a pointer to anoperating system module had been altered. This mostcommonly occurs when another software product hasset a hook for the module. Advanced AllocationManagement attempted to locate the operating systemmodule by matching instruction sequences in thecalling module, but was unsuccessful.




GLO1181I PROCESSING OPTION SET -S1_INTERCEPT=ENABLE|DISABLE

Explanation: This message is issued during productinitialization to display the value set for theS1_INTERCEPT parameter in the OPTIONS member.


GLO1182E INVALID VALUE SPECIFIED FOROPTION - S1_INTERCEPT=xxxxxxx

Explanation: During product initialization, whileprocessing the subsystem options in the OPTIONSmember, an incorrect value was encountered for theS1_INTERCEPT parameter. The value xxxxxxx indicatesthe invalid value.

User response: Valid values are "ENABLE" and"DISABLE". Correct the specified option keyword andrestart the product.

GLO1183W S1 INTERCEPT INITIALIZATION HASBEEN DISABLED DYNAMIC PDSDIRECTORY INCREASE FUNCTION ISNOT AVAILABLE

Explanation: The S1_INTERCEPT parameter in theOPTIONS member has been set to DISABLE. TheDynamic PDS Directory Increase function whichrequires the S1 intercept will not be available.

User response: To re-ENABLE the function, theS1_INTERCEPT parameter must be removed from theOPTIONS member, or changed to ENABLE, and thenyou must IPL the system and restart AdvancedAllocation Management.

GLO1184E COMMAND VERB NOT UNIQUE -cccccccc -ssss

Explanation: More than one command exists thatmatches the abbreviation specified (cccccccc) for thecommand verb. The Advanced Allocation Managementsubsystem processing the command was ssss.

User response: Re-issue the command, using acommand verb abbreviation that more uniquelyspecifies the intended command.

GLO1185E INVALID COMMAND SYNTAXSPECIFIED - ssss

Explanation: The command entered contains invalidsyntax. The Advanced Allocation Managementsubsystem processing the command was ssss.

User response: Review the command entered andcorrect the syntax.

GLO1189E 2.1 NAME/TOKEN EXISTS, BUTTOKEN DOES NOT POINT TO AVALID PRODUCT BLOCK

Explanation: Advanced Allocation Managementversion 3.1 (or higher) detected that a previous versionis present on the system, but the required productblocks are not valid. In this situation, version 3.1 (orhigher) initialization is not possible.

User response: To start version 3.1 (or higher), an IPLmust first be performed.

GLO1190E PREVIOUS VERSION GPB LOCATED,BUT VERSION IS NOT 2.1

Explanation: Advanced Allocation Managementversion 3.1 (or higher) detected that a previous versionis present on the system, but the version is not 2.1 orhigher. Version 3.1 (or higher) cannot be initialized onceany Advanced Allocation Management version prior to2.1 has been started on the system.

User response: To start version 3.1 (or higher), an IPLmust first be performed to remove the older version.

GLO1191E INVALID MODULE NAME SPECIFIED- cccccccc

Explanation: The command entered specifies aninvalid module name. The command entered is cccccccc.

User response: Re-issue the command with a correctmodule name.

GLO1192I MODULE mmmmmmmm vvvv ffffffffdddddddd ttttt

Explanation: Module header information is displayed,where mmmmmmmm is the name of the module, vvvv isthe version, ffffffff is the FMID dddddddd is the assemblydate and ttttt is the assembly time.

User response: None.

GLO1193I MODULE mmmmmmmm LOCATED ATaaaaaaaa (stgloc)

Explanation: The module address (with offset ifspecified) is displayed, where mmmmmmmm is thename of the module, aaaaaaaa is the virtual storageaddress, and stgloc is the storage location ("PRIVATE"or "COMMON").

User response: None.

GLO1194E ERROR IN NAME/TOKEN DELETEPROCESSING, RC=rrrrrrrr

Explanation: During initialization, AdvancedAllocation Management encountered an error anddetermined that termination was necessary. As part oftermination, an attempt was made to delete the



product's NAME/TOKEN, but the NAME/TOKENDELETE service encountered an error. rrrrrrrr containsthe value returned in register 15. Product terminationcontinues.


GLO1195E ERROR OCCURRED DURINGFREEMAIN FOR GPB, RC=rrrrrrrr

Explanation: During initialization, AdvancedAllocation Management encountered an error anddetermined that termination was necessary. As part oftermination, an attempt was made to freemain theproduct control block, but the FREEMAIN serviceencountered an error. rrrrrrrr contains the valuereturned in register 15. Product termination continues.


GLO1196E UNEXPECTED VCON COUNT FOR iiINTERCEPT; EXPECTED=eee,FOUND=fff

Explanation: While setting product intercept ii,Advanced Allocation Management encountered anunexpected VCON count for a particular csect. Theexpected VCON count is eee and the actual VCONcount is fff. While this does not necessarily indicate aproblem, it indicates the possibility of one. An SVCdump is taken. Depending upon the particularintercept, product initialization might continue orterminate.


GLO1200E UNABLE TO OBTAIN VIRTUALSTORAGE FOR WORKAREA

Explanation: A service task of the main productstarted task was unable to obtain the required amountof above-the-line storage.

User response: Increase the amount of above-the-linestorage for the Advanced Allocation Management task.If the problem persists, contact IBM Support.










GLO1366E UNABLE TO OBTAIN STORAGE FORZ1 INTERCEPT, RC=rrrrrrrr



GLO1370E UNABLE TO LOCATE LPDE FORIDA0192A



GLO1372E UNABLE TO LOCATE IDAOCTBL



GLO1373E UNABLE TO LOCATE IDAO557B





User response: Investigate a potential shortage of



above-the-line common storage and restart the product.If the problem persists, contact IBM Support.

GLO1382E UNABLE TO LOCATE ISTRING

Explanation: During product initialization, an internalcontrol block was unable to be located.








GLO1385E UNABLE TO LOCATE IDAO557F






GLO1391E INTERNAL ERROR IN GIRWB000,RC=rrrrrrrr

Explanation: An internal error occurred in routineGIRWB000 with a return code of rrrrrrrr.


GLO1393E UNABLE TO DETERMINE ILEVEL

Explanation: During product initialization, an internalcontrol block level was unable to be determined.


GLO1396W Z1 INTERCEPT INITIALIZATION HASBEEN DISABLED

Explanation: To enable the function, theZ1_INTERCEPT parameter must be set to ENABLE andthen the system must be IPLed and AdvancedAllocation Management must be restarted.


GLO1397W DATA SET INITIALIZATIONFUNCTION IS NOT AVAILABLE

Explanation: This message accompanies GLO1396W.See the explanation provided for that message.

User response: This message accompanies GLO1396W.See the user response provided for that message.

GLO1398I PROCESSING OPTION SET -Z1_INTERCEPT=ooooooo

Explanation: This message is issued during productinitialization to display the value (ooooooo) specified forthe Z1_INTERCEPT keyword in the OPTIONS member.


GLO1399E INVALID VALUE SPECIFIED FOROPTION - Z1_INTERCEPT=ooooooo

Explanation: During product initialization whileprocessing the subsystem options in the OPTIONSmember, an incorrect value was encountered for theZ1_INTERCEPT option. The value ooooooo indicates theinvalid value.





GLO1402E UNABLE TO LOCATE LPDE FORIGC00020



GLO1403E UNABLE TO LOCATE IFG0202J





||||
















GLO1415E UNABLE TO LOCATE IFG0202J



GLO1416E UNABLE TO LOCATE IFG0202I









GLO1423E UNABLE TO LOCATE IFG055ZZ CALL

Explanation: An internal error was encounteredduring initialization of Advanced AllocationManagement. Initialization will not continue.


GLO1424E UNABLE TO LOCATE IFG055ZZRETURN



GLO1425E UNABLE TO LOCATE IFG055ZZCOMPARE



GLO1426E UNABLE TO LOCATE IFG055ZZBRANCH





GLO1427E UNABLE TO LOCATE IFG055ZZSTRING



GLO1428E INVALID IFG055ZZ BRANCH OFFSET



GLO1450E UNEXPECTED RETURN CODE FROMENQUEUE TEST FUNCTION, R15=rc

Explanation: During the dynamic PDS directoryincrease function, an unexpected error code wasreturned when testing the ownership of the data setresource. Recovery was unable to continue.

User response: Note the return code as indicated by“rc” and contact technical support with the diagnosticinformation.

GLO1451W UNABLE TO OBTAIN STORAGE FORGQSCAN WORKAREA

Explanation: During the dynamic PDS directoryincrease function, Advanced Allocation Managementwas unable to obtain necessary storage for an MVSservice. Recovery was unable to continue.

User response: Increase the region size and attempt torerun the process. If the error still occurs, contacttechnical support.

GLO1452W DIRECTORY INCREASE REQUIRESEXCLUSIVE CONTROL, BUT THEDATA SET IS BEING SHARED

Explanation: During the dynamic PDS directoryincrease function, Advanced Allocation Managementrequired exclusive control of the data set to maintainthe integrity of the PDS directory, but was unable toobtain it. Recovery was unable to continue.

User response: If the directory increase is still desired,terminate any processes that have shared ownership ofthe data set and rerun the process.

GLO1453W DIRECTORY INCREASE REQUIRESEXCLUSIVE CONTROL, BUTELEVATION FAILED; R15=rc

Explanation: During the dynamic PDS directoryincrease function, Advanced Allocation Managementhad shared ownership of the data set, but requiredexclusive control to maintain integrity of the PDS

directory. An attempt to elevate the ownership toexclusive was unsuccessful. Recovery was unable tocontinue.

User response: If the directory increase is still desired,terminate any processes that have ownership of thedata set and rerun the process.

GLO1454W DIRECTORY INCREASE REQUIRESEXCLUSIVE CONTROL, BUT DATASET IS SHARED BY ONE OR MOREOTHER TASKS (1)



GLO1455W DIRECTORY INCREASE REQUIRESEXCLUSIVE CONTROL, BUT WASUNABLE TO DETERMINE THEOWNING TCB

Explanation: During the dynamic PDS directoryincrease function, Advanced Allocation Managementrequired exclusive control of the data set to maintainthe integrity of the PDS directory, but was unable todetermine data set ownership. Recovery was unable tocontinue.


GLO1456W DIRECTORY INCREASE REQUIRESEXCLUSIVE CONTROL, BUT DATASET IS SHARED BY ONE OR MOREOTHER TASKS (2)



GLO1457E NON-ZERO RETURN FROM GQSCANSERVICE, R15=rc

Explanation: During the dynamic PDS directoryincrease function, an unexpected error code wasreturned when determining the ownership of the dataset resource. Recovery was unable to continue.

User response: Note the return code as indicated by rcand contact technical support with the diagnosticinformation.



GLO1458W ERROR DURING GQSCANTERMINATION PROCESSING, R15=rc

Explanation: During the dynamic PDS directoryincrease function, an unexpected error code wasreturned when determining the ownership of the dataset resource. Recovery was unable to continue.


GLO1459W DIRECTORY INCREASE REQUIRESEXCLUSIVE CONTROL, BUT THEDATA SET IS BEING SHARED



GLO1460E DIRECTORY INCREASE REQUIRESEXCLUSIVE CONTROL, BUT WASUNABLE TO OBTAIN IT; R15=rc

Explanation: During the dynamic PDS directoryincrease function, Advanced Allocation Managementrequired exclusive control of the data set to maintainthe integrity of the PDS directory, but an attempt toobtain it failed. Recovery was unable to continue.











GLO1485E UNABLE TO LOCATE IDAO557X






GLO1458W • GLO1488E


Appendix D. Function messages (non-VSAM)

These messages are related to the Advanced Allocation Management functions thatsupport non-VSAM data sets.


Explanation: During an attempt to intercept anallocation request, Advanced Allocation Managementwas unable to obtain enough above-the-line orbelow-the-line storage to perform processing.

User response: Increase the amount of above-the-lineand below-the-line storage for the job encountering theerror. If the error persists, contact IBM Support.

GLO2001E STORAGE OBTAIN FAILURE xxxxxxxx- FUNCTION BYPASSED -ssss

Explanation: In support of the NOTCAT2 function,the product was unable to obtain the required amountof below-the-line storage for the Advanced AllocationManagement subsystem ssss The field xxxxxxxxcontains diagnostic information.

User response: Increase the amount of below-the-linestorage for the job step. If the problem persists, contactIBM Support.

GLO2002E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR SCT,RC=rrrrrrrr

Explanation: During interception of a primaryallocation request, an internal error (rrrrrrrr) wasencountered while attempting to access a systemcontrol block.


GLO2008E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR SIOT,RC=rrrrrrrr

Explanation: During interception of a secondaryallocation request, an internal error (rrrrrrrr) wasencountered while attempting to access a systemcontrol block.



Explanation: During interception of a secondaryallocation request, an internal error (rrrrrrrr) was

encountered while attempting to access a systemcontrol block.



Explanation: During interception of a directory STOWrequest an internal error (rrrrrrrr) was encounteredwhile attempting to access a system control block.


GLO2019E UNABLE TO LOCATE IRWB INQUEUE - ssss

Explanation: During processing an allocation request,the product encountered an internal error forsubsystem ID ssss.


GLO2023E ERROR IN NAME/TOKEN DELETEPROCESSING, RC=rrrrrrrr

Explanation: An internal system error (rrrrrrrr) wasencountered during processing of an allocation request.


GLO2025E ERROR IN NAME/TOKEN CREATEPROCESSING, RC=rrrrrrrr

Explanation: An internal system error (rrrrrrrr) wasencountered during processing of an allocation request.


GLO2031E INTERNAL ERROR IN GIRWB000,RC=rcrcrcrc

Explanation: An internal error occurred in routineGIRWB000 with a return code of rcrcrcrc.



Explanation: During interception of a primaryallocation request, an internal error (rrrrrrrr) was

335

encountered while attempting to access a systemcontrol block.


GLO2038E INTERNAL ERROR IN GIRWB000,RC=rcrcrcrc

Explanation: An internal error occurred in routineGIRWB000 with a return code of rcrcrcrc.


GLO2040E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JCT,RC=rrrrrrrr

Explanation: During interception of an allocationrequest, an internal error (rrrrrrrr) was encounteredwhile attempting to access a system control block.


GLO2041E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JMR,RC=rrrrrrrr









GLO2049I DUPLICATE DATA SET BUT DSORGIS VSAM - NOTCAT2 FUNCTIONSKIPPED -ssss

Explanation: For the NOTCAT2 function forAdvanced Allocation Management subsystem ssss, aduplicate data set name was found, but the data setwas VSAM so the NOTCAT2 function was skipped.


GLO2051I JOB SET TO FAIL DUE TO NOTCATLGD 2 ON VOLSER vvvvvv -ssss

Explanation: The current job step and subsequentsteps were failed for Advanced Allocation Managementsubsystem ssss in support of the NOTCAT2=JCFAILfunction upon detecting a NOT CATLGD 2 error atstep termination when attempting to catalog the dataset identified by message GLO2123I with its first volserof vvvvvv.


GLO2061I JOB SET TO FAIL DUE TODUPLICATE DATA SET NAME ONvvvvvv AT ALLOCATION -ssss

Explanation: The current job step and subsequentsteps were failed for Advanced Allocation Managementsubsystem ssss in support of the NOTCAT2=JCLFAILfunction upon detecting a duplicate data set name atallocation time for the data set identified by messageGLO2123I with its first volser of vvvvvv.





GLO2074E DDPB QUEUE ERROR xxxxxxxx-SDUMP TAKEN - QUEUE RECOVERYSUCCESSFUL

Explanation: During processing, Advanced AllocationManagement detected a problem with an internalcontrol block queue where xxxxxxxx represents aninternal error code which only has meaning to IBMSupport.

User response: An SVCDUMP will be taken withinthe address space that detected the error. The title ofthe dump will be "DDPB QUEUE ERROR". After thedump is taken, Advanced Allocation Management willcorrect the queue problem and continue processing.Please save the SVCDUMP and contact IBM Support.


Explanation: During interception of step termination,an internal error (rrrrrrrr) was encountered whileattempting to access a system control block.




GLO2076E ERROR OCCURRED DURINGRESMGR ADD PROCESSING,RC=rrrrrrrr

Explanation: An attempt to add a resource managerwas unsuccessful. (rrrrrrrr) indicates the return codepassed back from the RESMGR invocation.


GLO2077I WAITING FOR RESMGR DELETE

Explanation: When attempting to delete a resourcemanager, it is possible that the system will require theissuing program (Advanced Allocation Management )to wait before the deletion is complete. The amount oftime of the wait should be relatively short. This is aninformational message issued to aid in diagnosis in theevent that the wait becomes excessive.

User response: If Advanced Allocation Managementreturns from the wait relatively quickly, no action isrequired. If the wait appears excessive, please contactIBM Support.

GLO2078E ERROR OCCURRED DURINGRESMGR DELETE PROCESSING,RC=rrrrrrrr

Explanation: An attempt to delete a resource managerwas unsuccessful. (rrrrrrrr) indicates the return codepassed back from the RESMGR invocation.





GLO2080E INITIALIZING DATA SET

Explanation: Through RULEDEF statements,Advanced Allocation Management was instructed toinitialize a newly allocated data set. The data setinitialization was successfully performed. MessageGLO2123I accompanies this message and indicates thejobname, ddname, data set name, and so on. for thedata set being initialized.


GLO2081E ERROR OCCURRED DURING OPENPROCESSING FORDDNAME=dddddddd, RC=rrrrrrrr

Explanation: A request was made to initialize the dataset represented by ddname dddddddd. During the openportion of initialization, an error occurred. The returncode from OPEN is rrrrrrrr.


GLO2082E OPEN UNSUCCESSFUL FORDDNAME=dddddddd

Explanation: A request was made to initialize the dataset represented by ddname dddddddd. While the openportion of initialization ended with a return code ofzero, the open was not successful.


GLO2083E ERROR OCCURRED DURING CLOSEPROCESSING FORDDNAME=dddddddd, RC=rrrrrrrr

Explanation: A request was made to initialize the dataset represented by ddname dddddddd. During the closeportion of initialization, an error occurred. The returncode from CLOSE is rrrrrrrr.


GLO2083I DATA SET ON VOLSER ooooooSCRATCHED DUE TO NOT CATLGD 2ON VOLSER vvvvvv -ssss

Explanation: The data set named in messageGLO2123I with its first volser on volume oooooo wasdeleted in support of the NOTCAT2=SCRATCHfunction at step termination time for the new data setwith its first volser located on volume vvvvvv on behalfof the Advanced Allocation Management subsystemssss.


GLO2084E ERROR OCCURRED DURINGOBTAIN PROCESSING FORDDNAME=dddddddd, RC=rrrrrrrr

Explanation: A request was made to initialize the dataset represented by ddname dddddddd. During OBTAINprocessing for the data set, an error occurred. Thereturn code from OBTAIN is rrrrrrrr.


GLO2084I DATA SET ON VOLSER ooooooSCRATCHED AT ALLOCATION TIME-ssss

Explanation: The data set named in messageGLO2123I with its first volser on volume oooooo wasdeleted in support of the NOTCAT2=SCRATCHfunction at allocation time on behalf of the AdvancedAllocation Management subsystem ssss.



Appendix D. Function messages (non-VSAM) 337

GLO2085E ABEND OCCURRED DURINGDATASET_INIT PROCESSING FORDDNAME=dddddddd (ccccc)

Explanation: A request was made to initialize the dataset represented by ddname dddddddd. Duringinitialization processing an abend occurred. (ccccc)contains the abend type and code.


GLO2085I DATA SET ON VOLSER ooooooRENAMED DUE TO NOT CATLGD 2ON VOLSER vvvvvv -ssss

Explanation: The data set named in messageGLO2123I with its first volser on volume oooooo wasrenamed in support of the NOTCAT2=RENAMEfunction at step termination time for the new data setwith its first volser located on volume vvvvvv on behalfof the Advanced Allocation Management subsystemssss. The new name of the renamed data set is specifiedin message GLO2086I.


GLO2086I NEW NAME: datasetname -ssss

Explanation: Specifies the new name (datasetname) of adata set renamed as a result of theNOTCAT2=RENAME function.


GLO2087I DATA SET ON VOLSER ooooooRENAMED AT ALLOCATION TIME-ssss

Explanation: The data set named in messageGLO2123I with its first volser on volume oooooo wasrenamed in support of the NOTCAT2=RENAMEfunction at allocation time on behalf of the AdvancedAllocation Management subsystem ssss. The new nameof the renamed data set is specified in messageGLO2086I.


GLO2088I DATA SET ON VOLSER ooooooUNCATALOGED DUE TO NOTCATLGD 2 ON VOLSER vvvvvv -ssss

Explanation: The data set named in messageGLO2123I with its first volser on volume oooooo wasuncataloged in support of theNOTCAT2=UNCATALOG function at step terminationtime for the new data set with its first volser located onvolume vvvvvv on behalf of the Advanced AllocationManagement subsystem ssss.


GLO2089I DATA SET ON VOLSER ooooooUNCATALOGED AT ALLOCATIONTIME -ssss

Explanation: The data set named in messageGLO2123I with its first volser on volume oooooo wasuncataloged in support of theNOTCAT2=UNCATALOG function at allocation timeon behalf of the Advanced Allocation Managementsubsystem ssss.


GLO2090E NOTCAT2 fffffffff FAILURE IN SERVICEROUTINE, RC=rcrcrcrc -ssss

Explanation: An unexpected failure occurred insupport of the NOTCAT2 function identified by fffffffffwith the return code specified in rcrcrcrc for AdvancedAllocation Management subsystem ssss.


GLO2091E NOTCAT2 ffffffff FAILURE ININVOKED SERVICE - RC=rcrcrcrc,R15=aaaaaaaa, R0=bbbbbbbb,OFFSET=oooooooo -ssss

Explanation: An unexpected failure occurred insupport of the NOTCAT2 function identified by fffffffffwith the return code specified in rcrcrcrc for AdvancedAllocation Management subsystem ssss. The fieldsaaaaaaaa, bbbbbbbb and oooooooo contain diagnosticinformation meaningful only to IBM Support.


GLO2092E VOLUME LIST RETRIEVAL ERROReeeeeeee - NOTCAT2 PROCESSINGSKIPPED -ssss

Explanation: An unexpected failure identified by thefailure code in eeeeeeee occurred in support of theNOTCAT2 function when attempting to perform acatalog LOCATE on behalf of Advanced AllocationManagement subsystem ssss.


GLO2100I SETTING SECONDARY ALLOCATIONTO nnnnnq uuuu -ssss

Explanation: This message indicates that AdvancedAllocation Management is setting the secondaryallocation to the value nnnnn for the DDNAMEreferenced in message in GLO2123I on behalf ofsubsystem ssss. The value q corresponds to the JCLparameter AVGREC and indicates either K (kilobytes)or M (megabytes) respectively and is only presentwhen SMS managed data sets are used and when theallocation unit is RCDS. The value uuuu indicates eitherCYL, TRKS, BLKS, or RCDS. This message is issued in



response to the SEC_ALLOC function and is followedby message GLO2123I.


GLO2101E SBST0500 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc – ssss

Explanation: An internal error (rcrcrcrc) wasencountered while performing the SEC_BEST functionon behalf of subsystem ssss.


GLO2102E SBST0600 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc, R0=rsrsrsrs, ATOFFSET oooooooo – ssss

Explanation: An internal error identified by the returncode rcrcrcrc, reason code rsrsrsrs, and offset oooooooo,was encountered while performing the SEC_BESTfunction on behalf of subsystem ssss.


GLO2103I EXTENT-MATCHING SECONDARYALLOCATION TO nnnnnq uuuu -ssss

Explanation: This message indicates that AdvancedAllocation Management is setting the secondaryallocation to the value nnnnn for the DDNAMEreferenced in message in GLO2123I on behalf ofsubsystem ssss. The value q corresponds to the JCLparameter AVGREC and indicates either K (kilobytes)or M (megabytes) respectively and is only presentwhen SMS managed data sets are used and when theallocation unit is RCDS. The value uuuu indicates eitherCYL, TRKS, BLKS, or RCDS. This message is issued inresponse to the SEC_BEST function and is followed bymessage GLO2123I.


GLO2104E SINC0500 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc – ssss

Explanation: An internal error (rcrcrcrc) wasencountered while performing the SEC_INC functionon behalf of subsystem ssss.


GLO2105E SINC0600 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc, R0=rsrsrsrs, ATOFFSET oooooooo – ssss

Explanation: An internal error identified by the returncode rcrcrcrc, reason code rsrsrsrs, and offset oooooooo,was encountered while performing the SEC_INCfunction on behalf of subsystem ssss.


GLO2106I INCREASING SECONDARYALLOCATION TO nnnnnq uuuu - ssss

Explanation: This message indicates that AdvancedAllocation Management is setting the secondaryallocation to the value nnnnn for the DDNAMEreferenced in message in GLO2123I on behalf ofsubsystem ssss. The value q corresponds to the JCLparameter AVGREC and indicates either K (kilobytes)or M (megabytes) respectively and is only presentwhen SMS managed data sets are used and when theallocation unit is RCDS. The value uuuu indicates eitherCYL, TRKS, BLKS, or RCDS. This message is issued inresponse to the SEC_INC function and is followed bymessage GLO2123I.


GLO2107E SRED0500 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc – ssss

Explanation: An internal error (rcrcrcrc) wasencountered while performing the SEC_REDUCEfunction on behalf of subsystem ssss.


GLO2108E SRED0600 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc, R0=rsrsrsrs, ATOFFSET oooooooo – ssss

Explanation: An internal error identified by the returncode rcrcrcrc, reason code rsrsrsrs, and offset oooooooo,was encountered while performing the SEC_REDUCEfunction on behalf of subsystem ssss.


GLO2109I REDUCING SECONDARYALLOCATION TO nnnnnq uuuu -ssss

Explanation: This message indicates that AdvancedAllocation Management is setting the secondaryallocation to the value nnnnn for the DDNAMEreferenced in message in GLO2123I on behalf ofsubsystem ssss. The value q corresponds to the JCLparameter AVGREC and indicates either K (kilobytes)or M (megabytes) respectively and is only presentwhen SMS managed data sets are used and when theallocation unit is RCDS. The value uuu indicates eitherCYL, TRKS, BLKS, or RCDS. This message is issued inresponse to the SEC_REDUCE function and is followedby message GLO2123I.


GLO2112I ALLOCATION SUCCESSFULLYRECOVERED FOR DSN=dsname – ssss

Explanation: The primary allocation for data setdsname was successfully reduced on behalf ofsubsystem ssss. This message is issued in response tothe PRIM_REDUCE function.




GLO2113E SPCHK010 NON-ZERO RETURNFROM BVIRB000, RC=rrrrrrrr – ssss

Explanation: Advanced Allocation Managementencountered an internal error (rrrrrrrr) while processingthe primary reduction function on behalf of subsystemssss.


GLO2114E SPCHK060 NON-ZERO RETURNFROM VAE, R15=rcrcrcrc – ssss

Explanation: An internal error (rcrcrcrc) wasencountered while performing the PRIM_REDUCEfunction on behalf of subsystem ssss.


GLO2115E SPCHK070 NON-ZERO RETURNFROM VAE, R15=rcrcrcrc, R0=rsrsrsrs, ATOFFSET oooooooo – ssss

Explanation: An internal error identified by the returncode rcrcrcrc, reason code rsrsrsrs, and offset oooooooo,was encountered while performing the PRIM_REDUCEfunction on behalf of subsystem ssss.


GLO2116I UNABLE TO REDUCE PRIMARYSPACE QUANTITY; CURRENT VALUEIS 0 OR 1 ssss

Explanation: While performing the PRIM_REDUCEfunction on behalf of subsystem ssss, AdvancedAllocation Management could reduce the primaryquantity no further because the current value is 0(zero). Message GLO2123I follows this message andidentifies the DDNAME that encountered the error.


GLO2117I SPACE REDUCTION OF ppp% WOULDREDUCE PRIMARY QUANTITYBEYOND MINIMUM LIMIT ssss

Explanation: Indicates that Advanced AllocationManagement could not reduce the primary quantityany further by the percentage value ppp as requestedby the PRIM_REDUCE function on behalf of subsystemssss as doing so would lower the primary quantitybelow the limit value defined by thePRIM_REDUCE_LIM option. Message GLO2123Ifollows this message and identified the DDNAME thatencountered the situation.


GLO2118I REDUCING PRIMARY ALLOCATIONTO nnnnn uuuuuuuuu -ssss

Explanation: This message indicates that AdvancedAllocation Management is reducing the primaryallocation quantity to the value nnnnn on behalf ofsubsystem ssss (where uuuuuuuu indicates eitherTRACKS, CYLINDERS, or BLKS/RCDS). This messageis issued in response to the PRIM_REDUCE function.Message GLO2123I follows this message and identifiedthe DDNAME for which reduction is being performed.


GLO2119E JFCB VALIDATION FAILED ssss

Explanation: This message indicates that an internalerror occurred while performing the PRIM_REDUCEfunction on behalf of subsystem ssss. MessageGLO2123I follows this message and identified theDDNAME that encountered the error.


GLO2123I jjjjjjjj,ssssssss,pppppppp,dddddddd,dsn ssss

Explanation: This message identifies the jobname(jjjjjjjj), stepname (ssssssss), procedure stepname(pppppppp), ddname (dddddddd), and data set name (dsn)associated with the preceding message associated withsubsystem ssss.


GLO2124E UNRECOGNIZED INTERCEPT IDENCOUNTERED (nn) -ssss

Explanation: This message indicates unrecognizablecontrol information (nn) was passed from an interceptpoint to the intercept handling routine for subsystemssss.


GLO2125I SPACE RELEASE RECOVEREDnnnnnnnnn TRACKS -ssss

Explanation: This message indicates that the spacerelease option (which is equivalent to the RLSE optionof the SPACE keyword of the DD statement) has beenset for the data set identified by the message GLO2123Ion behalf of subsystem ssss. The value nnnnnnnnnindicates the number of tracks recovered and isassociated with the SPACE_RELEASE function ofAdvanced Allocation Management.




GLO2127E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR SIOT,RC=rrrrrrrr - ssss

Explanation: During the VOL_ADD function, aninternal error (rrrrrrrr) was encountered whileattempting to access a system control block forsubsystem ssss.


GLO2128I DATA SET SUCCESSFULLYEXTENDED TO VOLUME vvvvvv -ssss

Explanation: The data set identified by the messageGLO2123I successfully processed the VOL_ADDfunction and extended the data set to the volume serialnumber vvvvvv on behalf of subsystem ssss.


GLO2129E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR AMPX,RC=rrrrrrrr -ssss

Explanation: During SELECTION processing, aninternal error (rrrrrrrr) was encountered whileattempting to access a system control block.


GLO2130E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JFCBX,RC=rrrrrrrr -ssss



GLO2130E UNRECOGNIZED INTERCEPT IDENCOUNTERED (nn)

Explanation: Unrecognizable control information nnwas passed from an intercept point to the intercepthandling routine.


GLO2131E VOLUME NOT ADDED DUE TOVOLUME ADD LIMIT REACHED -ssss

Explanation: A volume addition could not beperformed because either the operating system limit of59 volumes or the volume limit specified by theVOL_ADD_LIM keyword was reached. The GLO2123Imessage identifies the data set.

User response: Increase the size of each extent or raisethe limit specified by the VOL_ADD_LIM keyword.

GLO2133E UNEXPECTED RETURN FROM VAE,R15=rcrcrcrc - ssss

Explanation: An internal error identified by the returncode rcrcrcrc was encountered while performing theVOL_ADD function on behalf of subsystem ssss.


GLO2134E NON-ZERO RETURN FROM VAE,R15=rcrcrcrc, R0=rsrsrsrs, AT OFFSEToooooooo - ssss

Explanation: An internal error identified by the returncode rcrcrcrc, reason code rsrsrsrs and offset oooooooowas encountered while performing the VOL_ADDfunction on behalf of subsystem ssss.


GLO2135E SVOL2240 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc - ssss

Explanation: An internal error identified by the returncode rcrcrcrc was encountered while performing theVOL_ADD function on behalf of subsystem ssss.


GLO2136E NON-ZERO RETURN FROM VAE,R15=rcrcrcrc, R0=rsrsrsrs, AT OFFSEToooooooo - ssss

Explanation: An internal error identified by the returncode rcrcrcrc, reason code rsrsrsrs, and offset oooooooo,was encountered while performing the VOL_ADDfunction on behalf of subsystem ssss.


GLO2137A SPECIFY VOLSER FOR jobname,stepname, procstepname, ddname OR REPLYCANCEL -ssss

Explanation: In support of the VOL_ADD_PROMPTkeyword, the operator is prompted for a volume serialnumber to use to extend the data set associated withthe job specified by jobname, the step specified bystepname, the procedure stepname specified byprocstepname and the DDNAME specified by ddname forsubsystem ssss.

User response: Specify a six character volume serialnumber to use to extend the data set, or reply with thecommand CANCEL to fail the allocation.

GLO2138I OPERATOR RESPONDED TOVOLUME REQUEST WITH vvvvvv -ssss

Explanation: In response to message GLO2137A thatis associated with the VOL_ADD_PROMPT function,the operator responded with volume serial numbervvvvvvv for subsystem ssss.




GLO2139E VOLUME ADD NOT PERFORMED -UNABLE TO LOCATE SUITABLECANDIDATE VOLUME -ssss

Explanation: After searching all of the volumesspecified by the user to be used for locating a newvolume, no volumes with adequate space were foundto extend the data set to another volume. The value ssssidentifies the Advanced Allocation Managementsubsystem ID. Message GLO2123I identifies the dataset.

User response: Either add more volumes to besearched, free up space on the existing volumes, orinclude the VOL_ADD_PROMPT keyword and supplya volume to be used with adequate space.

GLO2141E UNEXPECTED ERROR rcrcrcrcDURING VOLUME ADD -sss

Explanation: An internal error (rcrcrcrc) occurredduring processing of the VOL_ADD function forsubsystem ssss.


GLO2142E PRED0700 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc - ssss

Explanation: An internal error identified by the returncode rcrcrcrc was encountered while performing thePRIM_REDUCE function for a secondary volume onbehalf of subsystem ssss.


GLO2143E PRED4000 NON-ZERO RETURN FROMVAE, R15=rcrcrcrc, R0=rsrsrsrs, ATOFFSET oooooooo - ssss

Explanation: An internal error identified by the returncode rcrcrcrc, reason code rsrsrsrs, and offset oooooooo,was encountered while performing the PRIM_REDUCEfunction for a secondary volume on behalf ofsubsystem ssss.


GLO2144I SETTING INITIAL ALLOCATION ONVOLUME vvvvvv TO nnnnnq uuuu -ssss

Explanation: In response to successful completion ofthe PRIM_REDUCE function on a secondary volumeidentified by vvvvvv for subsystem ssss, the initialallocation was set to nnnnn. The value q corresponds tothe JCL parameter AVGREC and indicates either K(kilobytes) or M (megabytes) respectively and is onlypresent when SMS managed data sets are used andwhen the allocation unit is RCDS. The value uuuuindicates either CYL, TRKS, BLKS, or RCDS. This

message is followed by message GLO2123I whichidentifies the data set.


GLO2146E AVS NOT PERFORMED - UNABLE TOLOCATE SUITABLE CANDIDATEVOLUME(S)-xxxxx -ssys

Explanation: While performing AVS processing for anon-VSAM non-SMS data set, Advanced AllocationManagement was unable to locate any candidatevolumes to fulfill the requested number of volumes forthe data set based upon the AVS algorithm chosen.Normal system allocation will be used to allocate thedata set. The variable ssys is the Advanced AllocationManagement subsystem identifier.

User response: Verify that a volume group or groups,unit name list or volser list has been specified in therule definition for this allocation. Verify that anyvolume groups specified are defined in a volume groupdefinition. Verify that enough space exists in thevolumes specified based on the chosen AVS algorithm.

GLO2148I AVS HAS SUCCESSFULLY SELECTEDALL VOLUMES-xxxxx -ssys

Explanation: AVS was able to locate all requestedvolumes for the non-VSAM non-SMS data set asrequested using the specified AVS algorithm. Thefollowing GLO2156I message displays the volumesselected.


GLO2149E AVS UNABLE TO FULFILL VOLUMECOUNT REQUEST DUE TOINSUFFICIENT VOLUMES-xxxxx -ssys

Explanation: AVS was unable to locate the requestednumber of volumes requested for a non-VSAMnon-SMS data set as requested using the specified AVSalgorithm. The volume list for the component will betruncated to the number of volumes located. Thevariable ssys is the Advanced Allocation Managementsubsystem identifier. The following GLO2156I messagedisplays the volumes selected.


GLO2150I INCREASING PDS DIRECTORY SIZE-ssss

Explanation: Advanced Allocation Managementdetected and successfully recovered a DIRECTORYFULL condition. The directory size was dynamicallyincreased so that STOW processing for the current



|||||

||||||||

member could be successfully completed.


GLO2151W INSUFFICIENT SPACE IN PRIMARYEXTENT TO INCREASE PDSDIRECTORY SIZE -ssss

Explanation: During an attempt to recover from aDIRECTORY FULL condition, Advanced AllocationManagement determined that there was insufficientspace in the data set's primary extent to increase thesize of the directory. The recovery was unsuccessfuland system error processing was allowed to terminatethe process.

User response: The data set must be re-allocated andthe directory's size must be manually increased. Theprocess that originally attempted to add the member tothe data set must then be re-run.

GLO2152W INSUFFICIENT SPACE IN DATA SETTO INCREASE PDS DIRECTORY SIZE-ssss

Explanation: During an attempt to recover from aDIRECTORY FULL condition, Advanced AllocationManagement determined that member data had to bemoved to make space for the new directory block, butthere was insufficient space in the data set to move themember data to. The recovery was unsuccessful andsystem error processing was allowed to terminate theprocess.

User response: Compressing the data set could freeenough space to allow the member data to be moved.If this is the case, compress the data set and then re-runthe process that originally attempted to add themember to the data set. Advanced AllocationManagement will detect the DIRECTORY FULLcondition, move the necessary members, and thendynamically increase the directory size. If compressingthe data set does not free enough space for the memberdata to be moved, the data set must be re-allocatedwith more primary and (or) secondary space. If this isthe case, the number of directory blocks should beincreased at the same time. The process that originallyattempted to add the member to the data set must thenbe re-run.

GLO2153W DATA SET NOT SUPPORTED FORPDS DIRECTORY INCREASE DUE TO(reason) -ssss

Explanation: Where reason is one of the following:

v TTR LIST IN USER DATA

v TEXT IN USER DATA

v NOTE LIST IN USER DATA

v OVERLAY USAGE

v ALIAS USAGE

During an attempt to recover from a DIRECTORYFULL condition, Advanced Allocation Managementdetected one of the unsupported conditions listedabove. The recovery process is stopped and systemerror processing is allowed to terminate the process.

User response: The PDS directory increase function isnot supported with this type of PDS usage. To preventthis message from appearing in the future, an exclusionfor the entity being processed can be added to theAdvanced Allocation Management RULEDEFS member.

GLO2154E I/O ERROR DETECTED DURING PDSDIRECTORY INCREASE FUNCTION-ssss

Explanation: During an attempt to recover from aDIRECTORY FULL condition, Advanced AllocationManagement determined that member data had to bemoved to make space for the new directory block.While moving the member data, an I/O error occurredpreventing the process from successfully completing.The recovery process was stopped and system errorprocessing was allowed to terminate the process.Message GLO2155E accompanies this message todescribe the nature of the I/O error.

User response: Verify that the data in the existingmembers is valid. If so, re-allocate the data set,increasing the size of the directory. If the data in theexisting members is not valid, the data set must berestored from a backup. The data set must then bere-allocated, increasing the size of the directory. Aftercompleting the above action(s), re-run the process thatoriginally attempted to add the member to the data set.

GLO2155E (text from the system SYNAD routine)-ssss nnnn -ssss

Explanation: This message accompanies messageGLO2154E and provides details about the I/O errorthat was encountered.

User response: Perform the actions described in theUser Response for message GLO2154E, record thecontents of this message, and contact IBM Support.

GLO2156I VOLSER(S): vvvvvv vvvvvvv vvvvvvvvvvvvvv vvvvvvv vvvvvvv vvvvvvv -ssys

Explanation: This message lists up to seven volumeserial numbers as chosen by AVS processing for anon-VSAM data set. If more than seven volumes wereallocated, multiple GLO2156I messages will bedisplayed.


GLO2151W • GLO2156I


|||

|||||

|

GLO2160E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JCT,RC=rrrrrrrr



GLO2161E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JMR,RC=rrrrrrrr












GLO2188I MATCHING xxxxxxx RULEDEF LINENUMBER = nnnnn -ssys

Explanation: In response to theMSG_LEVEL=RULEDEF option, this message isdisplayed upon a RULEDEF match during variouspoints during non-VSAM processing by AdvancedAllocation Management. The variable xxxxxxx is eitherthe word INCLUDE or EXCLUDE denoting a match onan INCLUDE or EXCLUDE RULEDEF respectively,nnnnn is the RULEDEF line number and ssys is theAdvanced Allocation Management subsystem identifier.


GLO2189I WAITING ON RESOURCES FOR 15MINUTES - RETRYING -ssss

Explanation: This message is an informationalmessage that indicates that a resource required byAdvanced Allocation Management to perform a volumeadd has not been available for fifteen minutes. ssssindicates the Advanced Allocation Managementsubsystem ID. No action is required as AdvancedAllocation Management will continue to try to acquirethe resource.


GLO2190I ENTITY PROCESSED BYRULEDEF_TEST MODE; RULEDEFLINE NUMBER nnnnn -ssss

Explanation: This informational message indicates thatthe data set being processed matches a RULEDEFstatement that designates simulate mode and identifiesthe line number of the matching statement in thecurrently active RULEDEFS definition. No recoveryaction is actually performed for the data set. Thismessage can appear more than once during the life ofan allocation through unallocation for a data set.Message GLO2123I follows this message to identify thedata set involved. This message applies to non-VSAMdata sets only.


GLO2195E FAILURE DURING CONSISTENCYCHECK FOR SET PROCESSING;REASON CODE xxx

Explanation: During SET processing, a consistencycheck failed with reason code xx, where xx is one of thefollowing codes. Message GLO2123I accompanies thismessage.

01 One or more of the following parameters wereeither implicitly or explicitly set todataclas-override (DCO), but not all of themwere set to DCO and the original allocationdid not specify AVGREC andaverage-record-length.

v SPACEUNITS

v PQTY

v SQTY

User response: Change the SET values forSPACEUNITS, PQTY, and (or) SQTY so thatDCO is used for all of the parameters (or noneof them,) or change the original allocation touse AVGREC and average-record-length.

02 SPACEUNITS, PQTY, and SQTY were eitherimplicitly, or explicitly, set to dataclas-override(DCO), but AVGVALUE, PQTY, and (or) SQTYwas not defined in the dataclas.



User response: Add values to the dataclas forAVGVALUE, PQTY, and (or) SQTY, or changethe SET statements so that DCO is not usedfor SPACEUNITS, PQTY, or SQTY.

03 One or more of the following parameters wereset to $NULL, but not all of them were set to$NULL.

v SPACEUNITS

v PQTY

v SQTY

User response: Change the SET values forSPACEUNITS, PQTY, and(or) SQTY, so that$NULL is used for all of them (or none ofthem).

04 SPACEUNITS is being either implicitly orexplicitly changed, but no correspondingPQTY change was specified.

User response: Add a SET statement forPQTY.

05 SPACEUNITS is being either implicitly orexplicitly changed, but no correspondingSQTY change was specified.

User response: Add a SET statement for SQTY.

06 SPACEUNITS is being either implicitly orexplicitly set to AVGRECU, AVGRECK, orAVGRECM, but the record-size was notspecified.

User response: Specify the record-sizesubparameter on the SET_SPACEUNITSstatement.

GLO2197E ERROR RETURNED FROMUCBPIN/UNPIN FOR UCB ATuuuuuuuu, RC=rrrrrrrr, OFFSET=oooooooo-ssss

Explanation: An unexpected failure occurred inUCBPIN/UNPIN processing for the UCB at virtualstorage location uuuuuuuu. The return code is rrrrrrrrand the internal error offset is oooooooo (for internaldiagnostic use only). The Advanced AllocationManagement subsystem is ssss.


GLO2200E UNABLE TO PERFORM UPDATE FORxxxxxxxx - ssss

Explanation: During SET processing for allocationvariable xxxxxxxx, a system service did not completesuccessfully. SET processing was not performed.


GLO2201E UNABLE TO CREATE JFCBX(S)DURING SET_VOLCT PROCESSING,RC=cccccccc, RS=ssssssss -ssss

Explanation: During SET processing for VOLCT, anerror was returned by the SWAREQ ASSIGN systemservice. The return code is cccccccc and the reason codeis ssssssss.


GLO2202E NON-ZERO RETURN FROM SJFREQRETRIEVE, RC=cccccccc, RS=ssssssss -ssss

Explanation: During SELECTION processing, an errorwas returned by the SJFREQ RETRIEVE system service.The return code is cccccccc and the reason code isssssssss.


GLO2203E NON-ZERO RETURN FROM SJFREQUPDATE, RC=cccccccc, RS=ssssssss -ssss

Explanation: During SET processing, an error wasreturned by the SJFREQ UPDATE system service. Thereturn code is cccccccc and the reason code is ssssssss.


GLO2204E NON-ZERO RETURN FROM SJFREQERASE, RC=cccccccc, RS=ssssssss -ssss

Explanation: During SET processing, an error wasreturned by the SJFREQ ERASE system service. Thereturn code is cccccccc and the reason code is ssssssss.


GLO2900E INVALID STORAGE REQUEST FORCONTROL BLOCK nnnn -ssss

Explanation: An internal error occurred whileattempting to obtain a control block identified by nnnnsubsystem ID ssss.


GLO2901E INSUFFICIENT VIRTUAL STORAGEFOR CONTROL BLOCK nnnn -ssss

Explanation: Sufficient storage was not available toobtain a required control block identified by nnnnsubsystem ID ssss.

User response: Attempt to increase above-the-line orbelow-the-line storage for the job receiving the errormessage. If the error persists, contact IBM Support.



|||||

||||||

|

GLO2902E ACRONYM CHECK FAILED WHILEATTEMPTING TO FREE nnnn,DATA=dddd -ssss

Explanation: An internal error occurred whileattempting to free a control block identified by nnnnwith the invalid data identified by dddd for subsystemID ssss.


GLO2903E FAILURE OCCURRED DURINGFREEMAIN FOR nnnn -ssss

Explanation: An internal error occurred whileattempting to free a control block identified by nnnnsubsystem ID ssss.



Explanation: During interception of a secondaryallocation request, an internal error (rrrrrrrr) wasencountered while attempting to access a systemcontrol block.


GLO2999I ALLOCATION TERMINATED ASREQUESTED BY RULEDEF LINE nnnnn- ssid

Explanation: Where nnnnn is the RULEDEF linenumber associated with the TERM_ALLOC function,ssid is the Advanced Allocation Management subsystemidentification. In accordance with the TERM_ALLOCfunction, the data set allocation was terminated asrequested by RULEDEF line number nnnnn for theAdvanced Allocation Management subsystem with thesubsystem ID ssid.




Appendix E. Function messages (VSAM)

These messages are related to the Advanced Allocation Management functions thatsupport VSAM data sets.

GLO3100I SETTING SECONDARY ALLOCATIONTO nnnnn uuuu

Explanation: This message indicates that AdvancedAllocation Management is setting the secondaryallocation to the value nnnnn for the DDNAMEreferenced in message in GLO3123I on behalf ofsubsystem ssss. The value uuuu indicates either CYL Sor TRKS. This message is issued in response to theSEC_ALLOC function for VSAM and is followed bymessage GLO3123I.


GLO3103I EXTENT-MATCHING tttttSECONDARY ALLOCATION TO nnnnnuuuuu -ssss

Explanation: This message indicates that AdvancedAllocation Management is setting the secondaryallocation to the value nnnnn for the DDNAMEreferenced in message in GLO3123I on behalf ofsubsystem ssss. The value uuuu indicates either CYL Sor TRKS while the value ttttt indicates either INDEX orDATA referring to the component for which the actionwas performed. This message is issued in response tothe SEC_BEST function for VSAM and is followed bymessage GLO3123I.


GLO3109I REDUCING ttttt SECONDARYALLOCATION TO nnnnn uuuu -ssss

Explanation: This message indicates that AdvancedAllocation Management is setting the secondaryallocation to the value nnnnn for the DDNAMEreferenced in message in GLO3123I on behalf ofsubsystem ssss. The value uuuu indicates either CYL Sor TRKS while the value ttttt indicates either INDEX orDATA referring to the component for which the actionwas performed. This message is issued in response tothe SEC_BEST function for VSAM and is followed bymessage GLO3123I.


GLO3116I UNABLE TO REDUCE PRIMARYSPACE QUANTITY; CURRENT VALUEIS 0 OR 1 -ssss

Explanation: While performing the PRIM_REDUCEfunction for a VSAM data set on behalf of subsystem

ssss, Advanced Allocation Management could reducethe primary quantity no further because the currentvalue is 0 (zero). Message GLO3123I follows thismessage and identifies the DDNAME that encounteredthe error.


GLO3117I SPACE REDUCTION OF ppp% WOULDREDUCE PRIMARY QUANTITYBEYOND MINIMUM LIMIT -ssss

Explanation: This message indicates that AdvancedAllocation Management could not reduce the primaryquantity for a VSAM data set any further by thepercentage value ppp as requested by thePRIM_REDUCE function on behalf of subsystem ssss asdoing so would lower the primary quantity below thelimit value defined by the PRIM_REDUCE_LIM option.Message GLO3123I follows this message and identifiesthe DDNAME that encountered the situation.


GLO3118I REDUCING PRIMARY ALLOCATIONTO nnnnn uuuuuuuuuu -ssss

Explanation: This message indicates that AdvancedAllocation Management is reducing the primaryallocation quantity for a VSAM data set to the valuennnnn on behalf of subsystem ssss (where uuuuuuuuindicates either TRACKS, CYLINDERS, RECORDS,MEGABYTES or KILOBYTES). This message is issuedin response to the PRIM_REDUCE function. MessageGLO3123I follows this message and identifies theDDNAME for which reduction is being performed.


GLO3123I jobname, stepname, pstepname, ddname,dsname, -ssss

Explanation: This message identifies the jobname(jobname), stepname (stepname), procedure stepname(pstepname), ddname (ddname), and data set name(dsname) associated with the preceding message that isassociated with subsystem -ssss for a VSAM data set.

User response: No action is required

GLO3124E UNRECOGNIZED INTERCEPT IDENCOUNTERED (xx)

Explanation: Unrecognizable control information xx

347

was passed from an intercept point to the intercepthandling routine.


GLO3126E VADD1260 NON-ZERO RETURNFROM SVC99, R15=rrrrrrrr -ssss

Explanation: An internal error (rrrrrrrr) occurredduring processing of the VOL_ADD function for aVSAM data set on behalf of subsystem ssss.


GLO3127E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR SIOT,RC=rrrrrrrr -ssss

Explanation: During interception of a VSAMallocation request, an internal error (rrrrrrrr) wasencountered while attempting to access a systemcontrol block.


GLO3128I ttttt SUCCESSFULLY EXTENDED TOVOLUME vvvvvv -ssss

Explanation:

ttttt, identified by the message GLO3123I, wassuccessfully extended to volume serial number vvvvvvon behalf of subsystem ssss in response to theVOL_ADD function.

Where: ttttt is either DATA, INDEX, AIX-D (an AIX forthe data component was processed), AIX-I (an AIX forthe index component was processed), BAS-D or BAS-I(which indicates that the VOL_ADD was performed forthe base cluster data or index component due to anadd through an UPDATE path).


GLO3131E VOLUME NOT ADDED DUE TOVOLUME ADD LIMIT REACHED -ssss

Explanation: A volume addition could not beperformed for the VSAM data set because either theoperating system limit of 59 volumes or the volumelimit specified by the VOL_ADD_LIM keyword wasreached. The GLO3123I message identifies the data set.

User response: Increase the size of each extent or raisethe limit specified by the VOL_ADD_LIM keyword.

GLO3135E SVOL2240 NON-ZERO RETURN FROMVAE, R15=rrrrrrrr -ssss

Explanation: An internal error (rrrrrrrr) wasencountered while performing the VOL_ADD functionfor a VSAM data set on behalf of subsystem ssss.


GLO3136E NON-ZERO RETURN FROM VAE,R15=rrrrrrrr, R0=ssssssss -ssss

Explanation: An internal error identified by the returncode rrrrrrrr and the reason code ssssssss wasencountered while performing the VOL_ADD functionfor a VSAM data set on behalf of subsystem ssss.


GLO3137A SPECIFY VOLSER FORjobname,stepname,pstepname,ddname ORREPLY CANCEL -ssss

Explanation: In support of the VOL_ADD_PROMPTkeyword for a VSAM data set, the operator isprompted for a volume serial number to use to extendthe data set associated with the job specified byjobname, the step specified by stepname, the procedurestepname specified by procstepname and the DDNAMEspecified by ddname for subsystem ssss.

User response: Specify a six character volume serialnumber to use to extend the data set, or reply with thecommand CANCEL to fail the allocation.

GLO3138I OPERATOR RESPONDED TOVOLUME REQUEST WITH vvvvvvv-ssss

Explanation: In response to message GLO3137A thatis associated with the VOL_ADD_PROMPT function fora VSAM data set, the operator responded with volumeserial number vvvvvvv for subsystem ssss.


GLO3139E VOLUME ADD NOT PERFORMED -UNABLE TO LOCATE SUITABLECANDIDATE VOLUME -ssss

Explanation: After searching all of the volumesspecified by the user to be used for locating a newvolume for a VSAM data set, no volumes withadequate space were found to extend the data set toanother volume. The value ssss identifies the AdvancedAllocation Management subsystem ID. MessageGLO3123I identifies the data set.

User response: Either add more volumes to besearched, free up space on the existing volumes, orinclude the VOL_ADD_PROMPT keyword and supplya volume to be used with adequate space.

GLO3141E UNEXPECTED ERROR rrrrrrrrDURING VOLUME ADD -ssss

Explanation: An internal error (rrrrrrrr) occurredduring processing of the VOL_ADD function for aVSAM data set on behalf of subsystem ssss.




|

||||

||||||

GLO3144I SETTING INITIAL ALLOCATION ONNEW VOLUME TO nnnnn uuuu -sssss

Explanation: In response to successful completion ofthe PRIM_REDUCE function on a secondary volumefor a VSAM data set identified by vvvvvv for subsystemssss, the initial allocation was set to nnnnn. The valueuuuu indicates either CYL S or TRKS. This message isfollowed by message GLO3123I which identifies thedata set.


GLO3146E AVS NOT PERFORMED - UNABLE TOLOCATE SUITABLE CANDIDATEVOLUME(S)-xxxxx -ssys

Explanation: While performing AVS processing for anon-SMS VSAM cluster component, AdvancedAllocation Management was unable to locate anycandidate volumes to fulfill the requested number ofvolumes for the data set based upon the AVS algorithmchosen. The volume list for the component will beemptied which will result in an IDCAMS DEFINEfailure in order to prevent the allocation of the data set.The xxxxx variable is the VSAM cluster componenttype - either DATA or INDEX while ssys is theAdvanced Allocation Management subsystem identifier.


GLO3148I AVS HAS SUCCESSFULLY SELECTEDALL VOLUMES-xxxxx -ssys

Explanation: AVS was able to locate all requestedvolumes for the non-SMS VSAM cluster component asidentified by the variable xxxxx as either DATA orINDEX as requested using the specified AVS algorithm.The following GLO3156I message displays the volumesselected.


GLO3149E AVS UNABLE TO FULFILL VOLUMECOUNT REQUEST DUE TOINSUFFICIENT VOLUMES-xxxxx -ssys

Explanation: AVS was unable to locate the requestednumber of volumes requested for a non-SMS VSAMcluster component as identified by the variable xxxxx aseither DATA or INDEX as requested using the specifiedAVS algorithm. The volume list for the component willbe truncated to the number of volumes located. Thevariable ssys is the Advanced Allocation Managementsubsystem identifier. The following GLO3156I messagedisplays the volumes selected.

User response: Verify that a volume group or groups,

unit name list or volser list has been specified in therule definition for this allocation. Verify that anyvolume groups specified are defined in a volume groupdefinition. Verify that enough space exists in thevolumes specified based on the chosen AVS algorithm.

GLO3156I VOLSER(S): vvvvvv vvvvvvv vvvvvvvvvvvvvv vvvvvvv vvvvvvv vvvvvvv -ssys

Explanation: Lists up to seven volume serial numbersas chosen by AVS processing for a non-SMS VSAMcluster component. If more than seven volumes wereallocated, multiple GLO3156I messages will bedisplayed.


GLO3186I MAXIMUM EXTENTS OF 255 PERCLUSTER REACHED -ssss

Explanation: This message indicates that maximumallowable number of extents was reached for the VSAMcluster and no further extends can be performed.


GLO3187I MAXIMUM EXTENTS OF 123 PERVOLUME REACHED -ssss

Explanation: This message indicates that maximumallowable number of extents for a VSAM componentwas reached and no further extends can be performed.


GLO3188I MATCHING RULEDEF LINE NUMBER= nnnnn - ssss

Explanation: This informational message identifies theline number of the statement in the currently activeRULEDEFS to be used for subsequent functions. Theline number is listed in the Advanced AllocationManagement started task listing in the JES SYSMSGdata set. This message can appear more than onceduring the life of an allocation through unallocation fora data set. Message GLO2123I follows this message toidentify the data set involved.

Note: This message only appears when tracing is on.


GLO3188S MATCHING xxxxxxx RULEDEF LINENUMBER = nnnnn -ssys

Explanation: In response to theMSG_LEVEL=RULEDEF option, this message isdisplayed upon a RULEDEF match during variouspoints during VSAM processing by AdvancedAllocation Management. The variable xxxxxxx is eitherthe word INCLUDE or EXCLUDE denoting a match onan INCLUDE or EXCLUDE RULEDEF respectively,

GLO3144I • GLO3188S

Appendix E. Function messages (VSAM) 349

||||||

|||||||||

|||

|||||

|

nnnnn is the RULEDEF line number and ssys is theAdvanced Allocation Management subsystem identifier.


GLO3190I ENTITY PROCESSED BYRULEDEF_TEST MODE; RULEDEFLINE NUMBER nnnnn -ssss

Explanation: This informational message indicates thatthe data set being processed matches a RULEDEFstatement that designates simulate mode and identifiesthe line number of the matching statement in thecurrently active RULEDEFS definition. No recoveryaction is actually performed for the data set. Thismessage can appear more than once during the life ofan allocation through unallocation for a data set.Message GLO2123I follows this message to identify thedata set involved. This message applies to VSAM datasets only.


GLO3195E FAILURE DURING CONSISTENCYCHECK FOR SET PROCESSING;REASON CODE xxx

Explanation: During SET processing, a consistencycheck failed with reason code xx, where xx is one of thefollowing codes. Message GLO3123I accompanies thismessage.

01 One or more of the following parameters wereeither implicitly or explicitly set todataclas-override (DCO), but not all of themwere set to DCO.

v SPACEUNITS

v PQTY

v SQTY

User response: Change the SET values forSPACEUNITS, PQTY, and (or) SQTY, so thatDCO is used for all of the parameters (or noneof them).

02 SPACEUNITS, PQTY, and SQTY were eitherimplicitly or explicitly set to dataclas-override(DCO), but AVGVALUE, PQTY, and (or) SQTYwas not defined in the dataclas.

User response: Add values to the dataclas forAVGVALUE, PQTY, and (or) SQTY, or changethe SET statements so that DCO is not usedfor SPACEUNITS, PQTY, or SQTY.

03 One or more of the following parameters wereset to $NULL, but not all of them were set to$NULL.

v SPACEUNITS

v PQTY

v SQTY

User response: Change the SET values forSPACEUNITS, PQTY, and (or) SQTY, so that$NULL is used for all of them (or none ofthem).

04 SPACEUNITS is being either implicitly orexplicitly changed, but no correspondingPQTY change was specified.

User response: Add a SET statement forPQTY.

05 SPACEUNITS is being either implicitly orexplicitly changed, but no correspondingSQTY change was specified.

User response: Add a SET statement for SQTY.

06 SPACEUNITS is being either implicitly orexplicitly set to AVGRECU, AVGRECK, orAVGRECM, but the record-size was notspecified.

User response: Specify the record-sizesubparameter on the SET_SPACEUNITSstatement.

GLO3199E ERROR OCCURRED DURINGSWAREQ PROCESSING FOR JFCBX,RC=rrrrrrrr -ssss



GLO3200E UNABLE TO CHAIN CONTROLBLOCK FOR FIELD LIST - xxxxxxxx-ssss

Explanation: During SET processing for an IDCAMSDEFINE, an internal error occurred while processing acatalog field list for allocation variable xxxxxxxx.


GLO3201E UNABLE TO ACQUIRE SPACE TOBUILD FIELD LIST - xxxxxxxx -ssss



GLO3202E UNABLE TO CHAIN CONTROLBLOCK FOR FIELD LIST -xxxxxxx -ssss





Appendix F. Syntax-check messages

These messages are related to issues with the Advanced Allocation Managementsyntax-checking feature.

GLO4001W END-OF-DATA ENCOUNTERED ssid

Explanation: This message indicates that an internalerror has occurred during rule or volume groupdefinition activation or syntax checking. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.


GLO4002E STRING ADDRESS IS ZERO ssid



GLO4003E PROCESSING MODE NOT SPECIFIEDssid



GLO4004E READ ROUTINE ADDRESS MISSINGssid



GLO4006E RECORD AREA ADDRESS MISSINGssid



GLO4007E OUTPUT AREA ADDRESS MISSINGssid



GLO4008E PARSE TABLE ADDRESS MISSINGssid



GLO4009E INTERNAL ERROR - RKDFTYPEINVALID ssid



GLO4010E KEYWORD SHOULD NOT HAVEPARAMETERS keyword ssid

Explanation: The specified keyword (keyword) wasspecified with parameters when it should have noparameters. The ssid is the subsystem ID assigned toAdvanced Allocation Management.

User response: Remove the parameters from thekeyword and then use the Advanced AllocationManagement syntax-check option to verify the syntax.

GLO4011E ILLEGAL PLACEMENT OF EQUALSIGN keyword ssid

Explanation: The specified keyword (keyword) has anequal sign specified in an incorrect location. This erroris usually caused by one or more spaces before, orafter, the equal sign.

User response: Correct the syntax and then use the

351

Advanced Allocation Management syntax-check optionto verify the syntax.

GLO4012E EXCESSIVE NUMBER OF KEYWORDPARMS SPECIFIED keyword ssid

Explanation: The specified keyword (keyword) hasmore parameters specified than are allowed. The ssid isthe subsystem ID assigned to Advanced AllocationManagement.

User response: Use the Advanced AllocationManagement syntax-check option to verify the syntaxfor the appropriate number of parameters and thenremove or add parameters as required.

GLO4013E UNBALANCED PARENTHESES keywordssid

Explanation: The specified keyword (keyword) doesnot contain an equal number of matching left and rightparentheses. The ssid is the subsystem ID assigned toAdvanced Allocation Management.

User response: Use the Advanced AllocationManagement syntax-check option to verify the syntaxand to determine if you need to add a right or leftparentheses to enclose the operands.

GLO4014E MISPLACED COMMA keyword ssid

Explanation: The specified keyword (keyword) has acomma specified in an illegal location. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.

User response: Correct the syntax and use theAdvanced Allocation Management syntax-check optionto verify the syntax.

GLO4015E MISPLACED EQUAL SIGN keyword ssid

Explanation: The specified keyword (keyword) has anequal sign in an incorrect location. This message isissued when two equal signs are adjacent to each other.The ssid is the subsystem ID assigned to AdvancedAllocation Management.

User response: Correct the syntax and then use theAdvanced Allocation Management syntax-check optionto verify the syntax.

GLO4016E KEYWORD LENGTH EXCEEDS 256BYTE INTERNAL LIMIT ssid



GLO4017E KEYWORD VALUE NOT VALIDkeyword ssid

Explanation: The specified keyword (keyword) hasspecified an operand which is not one of the allowablevalues. The ssid is the is the subsystem ID assigned toAdvanced Allocation Management.

User response: Use the Advanced AllocationManagement syntax-check option to verify the syntax.

GLO4018E KEYWORD VALUE NOT ALPHABETICkeyword ssid

Explanation: The specified keyword (keyword) has avalue which is not all alphabetic as required. The ssid isthe subsystem ID assigned to Advanced AllocationManagement.


GLO4019E KEYWORD VALUE NOT NUMERICkeyword ssid

Explanation: The specified keyword (keyword) has avalue which is not numeric as required. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.


GLO4020E KEYWORD VALUE DOES NOT BEGINWITH ALPHABETIC keyword ssid

Explanation: The specified keyword (keyword) has avalue which does not begin with an alphabeticcharacter as required. The ssid is the subsystem IDassigned to Advanced Allocation Management.


GLO4021E KEYWORD VALUE EXCEEDSMAXIMUM ALLOWED LENGTHkeyword ssid

Explanation: The value for the specified keyword(keyword) has a length which is longer than themaximum length allowed. The ssid is the subsystem IDassigned to Advanced Allocation Management.




GLO4022E KEYWORD VALUE DOES NOT MEETMINIMUM LENGTH keyword ssid

Explanation: The value for the specified keyword(keyword) has a length which is shorter than theminimum length allowed. The ssid is the subsystem IDassigned to Advanced Allocation Management.


GLO4023E UNABLE TO EXPAND VARIABLEAREA keyword ssid

Explanation: While processing the specified keyword(keyword) an internal storage-related error occurred. Thessid is the subsystem ID assigned to AdvancedAllocation Management.

User response: Increase the above-the-line region sizefor the Advanced Allocation Management started task.If this does not resolve the error, please contact IBMSupport.

GLO4024E NUMERIC VALUE EXCEEDSINTERNAL LIMIT OF999,999,999,999,999 keyword ssid

Explanation: The value for the specified keyword(keyword) is greater than the maximum allowednumeric value of 999,999,999,999,999. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.


GLO4025E NUMERIC VALUE IS BELOWMINIMUM ALLOWED keyword ssid

Explanation: The value for the specified keyword(keyword) is less than the minimum value allowed. Thessid is the subsystem ID assigned to AdvancedAllocation Management. Correct the syntax and use theAdvanced Allocation Management syntax-check optionto verify the syntax.

GLO4026E NUMERIC VALUE EXCEEDSMAXIMUM ALLOWED keyword ssid

Explanation: The value for the specified keyword(keyword) is greater than the maximum value allowed.The ssid is the subsystem ID assigned to AdvancedAllocation Management.


GLO4027E MISSING LEFT PARENTHESIS keywordssid

Explanation: More than one parameter value has beenspecified for the indicated keyword (keyword), but therequired left parenthesis was not found. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.


GLO4028E MISPLACED LEFT PARENTHESISkeyword ssid

Explanation: A left parenthesis was specified in aninappropriate location for the specified keyword(keyword). The ssid is the subsystem ID assigned toAdvanced Allocation Management.


GLO4029E MISSING ADDRESS OF VARIABLEAREA ssid



GLO4030E INVALID KEYWORD keyword ssid

Explanation: The specified keyword (keyword) is not arecognized keyword. The ssid is the subsystem IDassigned to Advanced Allocation Management.


GLO4031E SECONDARY KEYWORD NOTPRECEDED BY PRIMARY KEYWORDkeyword ssid

Explanation: The specified keyword (keyword) wasfound without a preceding DEFAULTS, INCLUDE orEXCLUDE keyword. The ssid is the subsystem IDassigned to Advanced Allocation Management.



Appendix F. Syntax-check messages 353

GLO4032E UNEXPECTED END OF DATA keywordssid

Explanation: This message indicates that an internalerror has occurred during rule or volume groupdefinition activation or syntax checking whileprocessing the specified keyword (keyword). The ssid isthe subsystem ID assigned to Advanced AllocationManagement.


GLO4033E EXPECTED AN EQUAL SIGN keywordssid

Explanation: This message indicates that an internalerror has occurred during rule or volume groupdefinition activation or syntax checking whileprocessing the specified keyword (keyword). The ssid isthe subsystem ID assigned to Advanced AllocationManagement.


GLO4100F FATAL ERROR ENCOUNTERED -PARSING TERMINATED ssid

Explanation: This message indicates that an internalerror has occurred during rule or volume groupdefinition activation or syntax checking. The ssidindicates the subsystem ID assigned to AdvancedAllocation Management.


GLO4101F UNABLE TO GETMAIN CDSB -PARSING TERMINATED ssid

Explanation: This message indicates that an internalerror has occurred. Advanced Allocation Managementwas unable to obtain enough storage in the ExtendedCSA for a required control block. The ssid indicates thesubsystem ID assigned to Advanced AllocationManagement.

User response: Check for available space in the ECSAand increase the region size above-the-line for theAdvanced Allocation Management started task. If thisdoes not resolve the situation, please contact IBMSupport.

GLO41021E CONTROL DATA RECFM ERROR -PROCESSING TERMINATED ssid

Explanation: The CONTROL DD must point to apartitioned data set with fixed format records with arecord length of 80 bytes. The ssid is the subsystem IDassigned to Advanced Allocation Management.

User response: Review the contents of the started taskJCL to ensure that it includes a DD statement with aDDNAME of CONTROL that points to a valid

partitioned data set with fixed format records with arecord length of 80 bytes.

GLO4102F UNABLE TO GETMAIN GCDB -PARSING TERMINATED ssid

Explanation: This message indicates that an internalerror has occurred. Advanced Allocation Managementwas unable to obtain enough storage in the ExtendedCSA for a required control block. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.

User response: Please check available space in theECSA and increase the region size above-the-line forthe Advanced Allocation Management started task. Ifthis does not resolve the situation, please contact IBMSupport.

GLO4103W NO DATA PROCESSED - PARSINGTERMINATED ssid

Explanation: The Advanced Allocation Managementcontrol data set member did not contain any validkeywords. The ssid is the subsystem ID assigned toAdvanced Allocation Management.

User response: Ensure that the control data setmember contains valid syntax. Use the AdvancedAllocation Management syntax-check option to verifythe syntax.

GLO4104E ERRORS ENCOUNTERED - RULE(S)NOT ACTIVATED ssid

Explanation: Errors were encountered whileprocessing the control data set member. The ruledefinitions were not activated. The ssid is the subsystemID assigned to Advanced Allocation Management.

User response: See the JES SYSMSG list data set for adetailed list of the errors.

GLO4105I RULE DEFINITIONS SUCCESSFULLYACTIVATED ssid

Explanation: No errors were encountered duringactivation and the rule definitions were successfullyactivated. The ssid is the subsystem ID assigned toAdvanced Allocation Management.


GLO4106E DEFAULTS DEFINITION MISSINGFROM MEMBER – PROCESSINGTERMINATED ssid

Explanation: The DEFAULTS main keyword was notfound before encountering an INCLUDE or EXCLUDEkeyword. The DEFAULTS keyword and its operands (ifany) must precede any INCLUDE or EXCLUDEkeywords. The ssid is the subsystem ID assigned to



Advanced Allocation Management.

User response: Make sure that the DEFAULTSkeyword precedes any INCLUDE or EXCLUDEkeywords. Use the Advanced Allocation Managementsyntax-check option to verify the syntax.

GLO4107E EXCESSIVE NUMBER OF DEFAULTSDEFINITIONS - PROCESSINGTERMINATED ssid

Explanation: Only one DEFAULTS keyword ispermitted in the rules definition control data setmember. The ssid is the subsystem ID assigned toAdvanced Allocation Management.

User response: Remove the unneeded DEFAULTSkeyword (or keywords) and then use the AdvancedAllocation Management syntax-check option to verifythe syntax.

GLO4108E ERRORS ENCOUNTERED - VGRP(S)NOT ACTIVATED ssid

Explanation: Errors were encountered whileprocessing the control data set member. The volumegroup definitions were not activated. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.

User response: See the JES SYSMSG list data set for adetailed list of the errors.

GLO4109I VGRP DEFINITIONS SUCCESSFULLYACTIVATED ssid

Explanation: No errors were encountered duringactivation and the volume group definitions weresuccessfully activated. The ssid is the subsystem IDassigned to Advanced Allocation Management.


GLO4110E UNABLE TO GETMAIN < 16MWORKAREA – PROCESSINGTERMINATED ssid


User response: Increase the region size below-the-linefor the Advanced Allocation Management started task.If this does not resolve the situation, please contact IBMSupport.

GLO4111E UNABLE TO ESTABLISH ESTAE -PROCESSING TERMINATED ssid

Explanation: This message indicates that an internalerror has occurred. The ssid is the subsystem IDassigned to Advanced Allocation Management.


GLO4112E INVALID PARM BLOCK (TYPE) -PROCESSING TERMINATED ssid



GLO4113E INVALID PARM BLOCK (SRCE) -PROCESSING TERMINATED ssid



GLO4114E INVALID PARM BLOCK (DEFN) -PROCESSING TERMINATED ssid



GLO4115E UNABLE TO LOCATE CONTROL DD -PROCESSING TERMINATED ssid

Explanation: A DD statement with a DDNAME ofCONTROL must be present within the AdvancedAllocation Management started task. This DD statementmust point to a partitioned data set with fixed formatrecords that have a record length of 80 bytes. Thecontrol data set contains various members whichprovide parameters that control the processing ofAdvanced Allocation Management. The ssid is thesubsystem ID assigned to Advanced AllocationManagement.

User response: Review the contents of the started taskJCL to ensure that it includes a DD statement with aDDNAME of CONTROL that points to a partitioneddata set with fixed format records with a record lengthof 80 bytes.



GLO4116E SWAREQ FAILURE - PROCESSINGTERMINATED ssid



GLO4117E DYNALLOC FAILURE - PROCESSINGTERMINATED ssid

Explanation: This message indicates that an internalerror has occurred during rule definition or volumegroup definition activation or syntax checking. The ssidis the subsystem ID assigned to Advanced AllocationManagement.


GLO4118E CONTROL DATA SET MUST BEDSORG OF PO – PROCESSINGTERMINATED ssid

Explanation: The CONTROL DD must point to apartitioned data set with fixed format records that havea record length of 80 bytes. The ssid is the subsystemID assigned to Advanced Allocation Management.

User response: Review the contents of the AdvancedAllocation Management started task JCL to ensure thatit includes a DD statement with a DDNAME ofCONTROL that points to a partitioned data set withfixed format records with a record length of 80 bytes.

GLO4119E CONTROL DATA OPEN ERROR -PROCESSING TERMINATED ssid

Explanation: An error was encountered during OPENprocessing for the data set referenced by theCONTROL DD statement. The ssid is the subsystem IDassigned to Advanced Allocation Management.

User response: Review the contents of the started taskJCL to ensure that it includes a DD statement with aDDNAME of CONTROL that points to a partitioneddata set. Ensure that the data set is a valid partitioneddata set with fixed format records with a record lengthof 80 bytes.

GLO4120E CONTROL DATA LRECL ERROR -PROCESSING TERMINATED ssid

Explanation: The CONTROL DD must point to apartitioned data set with fixed format records with arecord length of 80 bytes. The ssid is the subsystem IDassigned to Advanced Allocation Management.

User response: Review the contents of the started taskJCL to ensure that it includes a DD statement with aDDNAME of CONTROL that points to a valid

partitioned data set with fixed format records with arecord length of 80 bytes.

GLO4122E UNABLE TO LOCATE CONTROLMEMBER – PROCESSINGTERMINATED ssid

Explanation: The member name specified on, ordefaulted to in an ACTIVATE RULEDEFS orACTIVATE VGRPDEFS command, could not be located.The ssid is the subsystem ID assigned to AdvancedAllocation Management.

User response: Ensure that the specified memberexists in the data set pointed to by the CONTROL DDstatement in the Advanced Allocation Managementstarted task procedure.

GLO4123E UNABLE TO GETMAIN BUFFER AREA- PROCESSING TERMINATED ssid


User response: Increase the region size above-the-linefor the Advanced Allocation Management started task.If this does not resolve the situation, please contact IBMSupport.

GLO4124E INVALID PARM BLOCK (STRA) -PROCESSING TERMINATED ssid



GLO4125E INVALID PARM BLOCK (STRD) -PROCESSING TERMINATED ssid



GLO4126E UNABLE TO GETMAIN VARIABLEAREA – PROCESSING TERMINATEDssid


User response: Increase the region size above-the-line



for the Advanced Allocation Management started task.If this does not resolve the situation, please contact IBMSupport.

GLO4127E READ ROUTINE ADDRESS MISSING- PROCESSING TERMINATED

Explanation: This message indicates an internal errorin processing during rule or volume group definitionactivation or syntax checking.


GLO4128E WRITE ROUTINE ADDRESS MISSING- PROCESSING TERMINATED

Explanation: This message indicates an internal errorin processing during rule or volume group definitionactivation or syntax checking.


GLO4129E FIRST RECORD MUST BE COMMENTCARD

Explanation: This message indicates that the firstlogical record in a rule or volume group definition wasnot a comment card.

User response: Add a comment card as the firstrecord of the rule or volume group definitionscontaining within the comment the characters "RULEDEFINITION" or "VGRP DEFINITION" as appropriate.

GLO4130I NO SYNTAX ERRORS FOUND

Explanation: This informational message is issued atthe end of the syntax check processing that wasinvoked using Option S of the Tivoli AdvancedAllocation Management Control Member Managementscreen. The message indicates that syntax checking wassuccessful and no errors were found.


GLO4131E SYNTAX ERRORS ENCOUNTERED

Explanation: This message is issued at the end of thesyntax check processing invoked using Option S of theTivoli Advanced Allocation Management ControlMember Management screen. This message indicatessome errors were found while checking the syntax forthe associated rule or volume group definitions.

User response: Check the listing for other errormessages which provide additional details about theerrors and correct the errors.

GLO4132E UNABLE TO GETMAIN VARIABLEAREA 2 - PROCESSING TERMINATEDssid

Explanation: This message indicates that an internalerror has occurred during rule group definitionactivation or syntax checking. The ssid is the subsystemID assigned to Advanced Allocation Management.

User response: Increase the region size above-the-linefor the Advanced Allocation Management started task.If this does not resolve the situation, please contact IBMSupport.

GLO4199I linenum linedata – ssid

Explanation: This line displays each record read fromthe control data set member where linenum is therecord number and linedata is the actual record image.The ssid is the subsystem ID assigned to AdvancedAllocation Management.





Appendix G. Event recording and reporting messages

These messages are related issues with the Advanced Allocation Managementevent recording and reporting utility.

GLO7000E INSUFFICIENT ABOVE-THE-LINEVIRTUAL STORAGE AVAILABLE

Explanation: During event reporting processing,Advanced Allocation Management was unable toobtain the required storage above the 16 MB line.

User response: Increase the region size for the reportutility and re-run it. If the problem persists, contactIBM Support.

GLO7001E INSUFFICIENT BELOW-THE-LINEVIRTUAL STORAGE AVAILABLE

Explanation: During event reporting processing,Advanced Allocation Management was unable toobtain the required storage below the 16 MB line.


GLO7002E OPEN FAILED FOR CNTLOUT FILE

Explanation: Open processing was unsuccessful forthe CNTLOUT file.

User response: Make sure that the CNTLOUT DDstatement is present in the JCL and that it points to avalid data set. Look in the joblog for any datamanagement (IECxxx) messages containing additionalinformation regarding the nature of the error. If theproblem persists, contact IBM Support.

GLO7010E OPEN FAILED FOR CNTLIN FILE

Explanation: Open processing was unsuccessful forthe CNTLIN file.

User response: Make sure that the CNTLIN DDstatement is present in the JCL and that it points to avalid data set. Look in the joblog for any datamanagement (IECxxx) messages containing additionalinformation regarding the nature of the error. If theproblem persists, contact IBM Support.

GLO7011E MAXIMUM OF ONE SMFINSTATEMENT HAS BEEN EXCEEDED

Explanation: More than one SMFIN control statementhas been specified.

User response: Only one SMFIN control statement ispermitted. Please specify one SMFIN control statement.

GLO7012W ONE OR MORE SMF RECORDS WEREENCOUNTERED OF AN UNKNOWNVERSION

Explanation: Advanced Allocation Managementencountered one or more SMF records whose recordtype matched that specified, but it did not recognizethe version value within it.

User response: Verify that the version of the reportutility is the same as the version of the product thatrecorded the records to SMF. If problems persist, pleasecontact IBM Support.

GLO7013E ERROR(S) ENCOUNTERED DURINGCONTROL STATEMENT PROCESSING

Explanation: Errors were encountered whileprocessing the report utility control statements.

User response: Review the control statementsprovided and verify that the syntax is correct.

GLO7014E ERROR OCCURRED DURINGALLOCATION OF TEMPORARYWORK FILE

Explanation: An error occurred during the allocationof the temporary work file used during event reportingprocessing. Message GLO7049E accompanies thismessage and provides diagnostic information regardingthe error.

User response: Please contact IBM support.

GLO7015E OPEN FAILED FOR TEMPFILE FOROUTPUT PROCESSING

Explanation: Open processing was unsuccessful forthe temporary work file used during event reportingoutput processing.

User response: Look in the joblog for any datamanagement (IECxxx) messages containing additionalinformation regarding the nature of the error. If theproblem persists, contact IBM Support.

GLO7016E ERROR OCCURRED DURINGALLOCATION OF SMF DATA SET -

Explanation: An error occurred during the allocationof the SMF data set specified using the SMFIN controlstatement. Messages GLO7018E and GLO7049Eaccompany this message and indicate the SMF data set

359

name in error and provide diagnostic informationregarding the error.

User response: Verify that the specified data set nameexists and is cataloged.

GLO7017E OPEN FAILED FOR SMF DATA SET -

Explanation: Open processing was unsuccessful forthe specified SMF data set. Message GLO7018Eaccompanies this message and indicates the SMF dataset name in error.


GLO7018E data set name

Explanation: This message accompanies GLO7016E orGLO7017E and indicates the name of the SMF data setfor which the error occurred.

User response: Refer the accompanying message forinstructions on how to respond.

GLO7019E NO SMF RECORDS WERE FOUND INANY INPUT FILE

Explanation: No SMF records were found in anyspecified SMF data set(s) to be searched for AdvancedAllocation Management event records.

User response: Ensure that the data set(s) specified bythe SMFIN control statement contain valid SMF data.

GLO7020E NO SMF RECORDS OF THESPECIFIED TYPE WERE FOUND INANY INPUT FILE

Explanation: No SMF records of the type specified bythe SMF_RECORD_ID parameter were found in theSMF data set(s) to be searched for Advanced AllocationManagement event records.

User response: Ensure that the proper set-up steps forevent recording have been performed and thatAdvanced Allocation Management is active. Alsoensure that the RULEDEFS are set up properly so thatAdvanced Allocation Management is activelypreventing and recovering space-related conditions onyour system. Finally, ensure that the value specified onthe SMF_RECORD_ID control statement for the reportutility matches the value specified on theSMF_RECORD_ID control statement in the OPTIONSmember of the Advanced Allocation Managementcontrol data set.

GLO7021E NO SMF RECORDS OF THESPECIFIED TYPE PASSED FILTERING

Explanation: No SMF records in the specified SMFdata set(s) passed filtering as specified by theFILTER_SET control statement(s).

User response: Ensure that the filter criteria value(s)were specified properly and that the entities specifiedin the filter criteria actually had Advanced AllocationManagement processing performed on their behalf.

GLO7022E OPEN FAILED FOR HISTOUT DCB

Explanation: Open processing was unsuccessful forthe HISTOUT DCB.

User response: Make sure that the HISTOUT DDstatement is present in the JCL and that it points to avalid data set. Look in the joblog for any datamanagement (IECxxx) messages containing additionalinformation regarding the nature of the error. If theproblem persists, contact IBM Support.

GLO7023E DETAIL=NO AND SUMMARY=NOARE NOT VALID TOGETHER

Explanation: The report option combinationDETAIL=NO AND SUMMARY=NO is not valid.

User response: Specify a valid combination of reportoptions.

GLO7024E SUMMARY=YES AND FORMAT=LISTARE NOT VALID TOGETHER

Explanation: The report option combinationSUMMARY=YES AND FORMAT=LIST is not valid.


GLO7025E ABOVE CONTROL STATEMENTCONTAINS ONE OR MORE ERRORS

Explanation: A control statement specified as input tothe report utility contains an error.

User response: Review the specified control statementand verify that the keyword, value, and syntax is valid.

GLO7026E NO DATA SET NAMES WERESPECIFIED FOR SMFIN

Explanation: A data set name was not specified forthe SMFIN parameter in the report utility JCL. Aminimum of one data set must be specified in order forevent data reporting to take place.

User response: Specify one or more names of SMFdata set(s) to be searched for Advanced AllocationManagement event records. A maximum of 32 data setscan be specified.



GLO7027E SMF_RECORD_ID IS REQUIRED, BUTWAS NOT SPECIFIED

Explanation: The Advanced Allocation Managementreport utility requires a SMF record ID in order toknow which SMF records to process.

User response: Add a SMF_RECORD_ID controlstatement to the report utility input, specifying thevalue that Advanced Allocation Management was setup to use for event recording. This value is defined inthe OPTIONS member of the Advanced AllocationManagement control data set.

GLO7028I PARENTHESIS UNMATCHED BEFOREEND-OF-FILE ON CNTLIN DATA SET

Explanation: While processing the CNTLIN data set, arequired matching parenthesis was found to bemissing.

User response: Review the input control statements,add the required parenthesis to the appropriate controlstatement and re-run the report utility.

GLO7030E FORMAT=LIST AND DETAIL=NO ARENOT VALID TOGETHER

Explanation: The report option combinationFORMAT=LIST AND DETAIL=NO is not valid.


GLO7031E MAXIMUM NUMBER OF SMFINFILES (32) EXCEEDED

Explanation: The number of SMF data sets specifiedvia the SMFIN control statement is greater than themaximum number allowed.

User response: Modify the SMFIN control statementto specify no more than 32 SMF data sets and re-runthe report utility.

GLO7032E MAXIMUM NUMBER OF FILTERCRITERIA FOR A FILTERSET (32)EXCEEDED

Explanation: The number of filter criteria specified isgreater than the maximum number of allowed filtercriteria allowed for a single filterset.

User response: Modify the FILTER_SET controlstatement to specify no more than 32 filter criteria andre-run the report utility.

GLO7033E MAXIMUM NUMBER OF FILTERSETS(32) EXCEEDED

Explanation: The number of FILTER_SET controlstatements specified is greater than the maximumnumber allowed.

User response: Change the control statements tospecify no more than 32 FILTER_SETs and re-run thereport utility.

GLO7034E UNABLE TO OBTAIN STORAGE FORFCCA

Explanation: During event reporting processing,insufficient storage above the 16 MB line was availablefor an internal product control block.


GLO7035E ERROR OCCURRED IN CONVTODSERVICE

Explanation: A non-zero return code was returnedfrom the system time-of-day conversion routine. Thisroutine is required for the report utility to workproperly.


GLO7036E ERROR OCCURRED IN STCKCONVSERVICE

Explanation: A non-zero return code was returnedfrom the system store-clock conversion routine. Thisroutine is required for the report utility to workproperly.


GLO7037E REQUIRED DELIMETER "=" ISMISSING IN ABOVE CONTROLSTATEMENT

Explanation: While processing the control statementsfor the report utility, a control statement wasencountered which requires an equal sign (=) but it wasfound to be missing.

User response: Add the required delimiter to theappropriate control statement and re-run the reportutility.

GLO7038E DATA SET SPECIFIED BY SMFIN ISNOT CATALOGED -

Explanation: One or more of the data sets specified bythe SMFIN parameter is not cataloged. MessageGLO7018E accompanies this message and indicates theSMF data set name that was not found in the catalog.

User response: Check the data set(s) specified by theSMFIN parameter and ensure that all of them arecataloged.


Appendix G. Event recording and reporting messages 361

GLO7039E OPEN FAILED FOR TEMPFILE FILEFOR INPUT PROCESSING

Explanation: Open processing was unsuccessful forthe TEMPFILE file required for input processing.


GLO7040E UNABLE TO LOCATE REQUIREDDDNAME - SMFIN -

Explanation: During event reporting processing,Advanced Allocation Management was unable to locateit the SMF input data set ddname (SMFIN) in the TIOT.Message GLO7018E accompanies this message andindicates the SMF data set name that being processedat the time of the error.

User response: This is an internal error. Contact IBMSupport.

GLO7041E IERROR OCCURRED DURINGSWAREQ JFCB RETRIEVAL FORSMFIN, RC=rrrrrrrr,

Explanation: During event reporting processing,Advanced Allocation Management issued a SWAREQto retrieve the JFCB for the SMF input data set ddname(SMFIN). The SWAREQ request was unsuccessful,returning with return code rrrrrrrr. Message GLO7018Eaccompanies this message and indicates the SMF dataset name that being processed at the time of the error.


GLO7042E INVALID FILTER CRITERIASPECIFIED IN FILTERSET-

Explanation: An invalid filter criteria was encounteredon a FILTER_SET control statement. MessageGLO7043E accompanies this message and indicates theinvalid filter criteria.

User response: Review the specified filter criteria andverify that the keyword, value, and syntax is valid. Ifthe problem persists, contact IBM Support.

GLO7044E INVALID DSORG (VSAM) FOR DATASET SPECIFIED BY SMFIN -

Explanation: One or more of the data sets specified bythe SMFIN parameter does not have a valid DSORG(PS). Message GLO7018E accompanies this messageand indicates the SMF data set name that has theinvalid DSORG.

User response: The Advanced Allocation Managementevent reporting utility only works with SMF data thathas been previously unloaded from the system SMF

(MAN) data sets. Ensure that all SMF data setsspecified by the SMFIN parameter have a DSORG ofPS.

GLO7049E DYNALLOC RETURN CODE=retcode,ERROR CODE=errcode, INFOCODE=infocode

Explanation: During event reporting processing, adynamic allocation request failed. This messageaccompanies a previous message and providesdiagnostic information regarding the nature of theerror. retcode is the value returned in register 15 by thedynamic allocation service. errcode and infocode are theerror and info code values returned in fields S99ERRORand S99INFO in the dynamic allocation request block.These values are documented in the MVS Programming:Authorized Assembler Services Guide.

User response: The retcode, errcode, and infocode valuescan be found in the MVS Programming: AuthorizedAssembler Services Guide which can help to determinethe exact nature of the problem. If additional assistanceis required, contact IBM Support.

GLO7050E UNABLE TO LOAD SORT ROUTINE

Explanation: During event reporting processing, theSORT_BY parameter was specified. This causedAdvanced Allocation Management to attempt to load amodule with the name of "SORT", but the load wasunsuccessful.

User response: If module SORT does not reside inlinklist or lpalib on your system, add a DD to theSTEPLIB concatenation of the report utility step,specifying the name of the loadlib in which SORTresides. If module SORT does reside in linklist or lpalibon your system, or you add a DD to the STEPLIBconcatenation of the report utility step and theproblems persists, contact IBM Support.

GLO7051E UNABLE TO LOCATE REQUIREDDDNAME - TEMPFILE

Explanation: During event reporting processing, theSORT_BY parameter was specified. While attempting toperform sort processing, Advanced AllocationManagement was unable to locate its temporaryprocessing DD (TEMPFILE) in the TIOT.


GLO7052E ERROR OCCURRED DURING SWAREQJFCB RETRIEVAL FOR TEMPFILE,RC=rrrrrrrr

Explanation: During event reporting processing, theSORT_BY parameter was specified. While attempting toperform sort processing, Advanced AllocationManagement issued a SWAREQ to retrieve the JFCB for



its temporary processing DD (TEMPFILE). TheSWAREQ request was unsuccessful, returning withreturn code rrrrrrrr.


GLO7053E DDNAME SYSIN UNAVAILABLE;ALREADY ALLOCATED

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustallocate ddname SYSIN to communicate with the sortroutine, but discovered that the ddname was alreadyallocated.

User response: If you are invoking the report utility inTSO using the dialog, perform the following steps:

1. Exit the Advanced Allocation Management dialog.

2. From the TSO command line, issue "TSO FREEF(SYSIN)."

3. Re-invoke the Advanced Allocation Managementdialog.

4. Re-invoke the report utility from the dialog.

If the problem persists, contact IBM Support.

GLO7054E DDNAME SYSOUT UNAVAILABLE;ALREADY ALLOCATED

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustallocate ddname SYSOUT to communicate with the sortroutine, but discovered that the ddname was alreadyallocated.

User response: If you are invoking the report utility inTSO using the dialog, perform the following steps:

1. Exit the Advanced Allocation Management dialog.

2. From the TSO command line, issue "TSO FREEF(SYSOUT)."

3. Re-invoke the Advanced Allocation Managementdialog.

4. Re-invoke the report utility from the dialog.

If the problem persists, contact IBM Support.

GLO7055E ERROR OCCURRED DURINGALLOCATION FOR SORTIN

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustallocate ddname SORTIN to communicate with the sortroutine, but the allocation was unsuccessful.


GLO7056E ERROR OCCURRED DURINGALLOCATION FOR SORTOUT

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustallocate ddname SORTOUT to communicate with thesort routine, but the allocation was unsuccessful.Message GLO7049E accompanies this message andprovides diagnostic information regarding the error.


GLO7057E ERROR OCCURRED DURINGALLOCATION FOR SYSOUT

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustallocate ddname SYSOUT to communicate with the sortroutine, but the allocation was unsuccessful. MessageGLO7049E accompanies this message and providesdiagnostic information regarding the error.


GLO7058E ERROR OCCURRED DURINGALLOCATION FOR SYSIN

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustallocate ddname SYSIN to communicate with the sortroutine, but the allocation was unsuccessful. MessageGLO7049E accompanies this message and providesdiagnostic information regarding the error.


GLO7059E OPEN FAILED FOR SYSIN FILE

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustopen ddname SYSIN to communicate with the sortroutine, but the open was unsuccessful.


GLO7060E OPEN FAILED FOR SYSOUT FILE

Explanation: During event reporting processing, theSORT_BY parameter was specified. To perform sortprocessing, Advanced Allocation Management mustopen ddname SYSOUT to communicate with the sortroutine, but the open was unsuccessful.

User response: Look in the joblog for any datamanagement (IECxxx) messages containing additionalinformation regarding the nature of the error. If the


Appendix G. Event recording and reporting messages 363

problem persists, contact IBM Support.

GLO7061E ERROR OCCURRED DURING SORTPROCESSING; SORT MESSAGESFOLLOW-

Explanation: During event reporting processing, theSORT_BY parameter was specified. AdvancedAllocation Management invoked the sort routine, butthe sort was unsuccessful. Advanced AllocationManagement copies the messages from sort to theCNTLOUT file following this message.

User response: Evaluate the sort messages that followand attempt to correct the problem. If you are unable tocorrect the problem or if the problem persists, contactIBM Support.

GLO7080E INVALID VALUE SPECIFIED FORKEYWORD STARTTIME

Explanation: The value specified for the STARTTIMEfilter criteria is not valid. The value must be in theformat yyyy/mm/dd-hh:mm:ss.

User response: Check the value specified for theSTARTTIME filter criteria and ensure it meets therequired format.

GLO7081E INVALID VALUE SPECIFIED FORKEYWORD ENDTIME

Explanation: The value specified for the ENDTIMEfilter criteria is not valid. The value must be in theformat yyyy/mm/dd-hh:mm:ss.

User response: Check the value specified for theENDTIME filter criteria and ensure it meets therequired format.

GLO7082E INVALID VALUE SPECIFIED FORKEYWORD JOBTYPE-

Explanation: The value specified for the JOBTYPEfilter criteria is not valid.

User response: Check the value specified for theJOBTYPE filter criteria and ensure it specifies one ofthe valid values.

GLO7083E INVALID VALUE SPECIFIED FORKEYWORD DSORG

Explanation: The value specified for the DSORG filtercriteria is not valid.

User response: Check the value specified for theDSORG filter criteria and ensure it specifies one of thevalid values. “DSORG” on page 224 for a list of validvalues.

GLO7084E WILDCARD PREFIX NOT ALLOWEDFOR SPECIFIED FILTER CRITERIA

Explanation: A filter criteria was specified with awildcard prefix indicator ("*") in the value, butspecified filter criteria does not allow wildcardprefixing.

User response: Re-specify the value in the offendingfilter criteria, removing the wildcard prefix indicator.



Support information

If you have a problem with your IBM software, you want to resolve it quickly. Thissection describes the following options for obtaining support for IBM softwareproducts:v “Using IBM Support Assistant”v “Obtaining fixes”v “Contacting IBM Software Support” on page 366

Using IBM Support AssistantThe IBM Support Assistant is a free, stand-alone application that you can install onany workstation. You can then enhance the application by installingproduct-specific plug-in modules for the IBM products you use.

The IBM Support Assistant saves you time searching product, support, andeducational resources. The IBM Support Assistant helps you gather supportinformation when you need to open a problem management record (PMR) orElectronic Tracking Record (ETR), which you can then use to track the problem.

TipThe Log and Trace Analyzer tool can help you prepare logs to submit with aPMR.

The product-specific plug-in modules of the IBM Support Assistant provide youwith the following resources:v Support linksv Education linksv Ability to submit problem management reports

For more information and to download the IBM Support Assistant, seehttp://www.ibm.com/software/support/isa/.

Obtaining fixesA product fix might be available to resolve your problem. To determine whichfixes are available for your Tivoli software product, follow these steps:1. Go to the IBM Software Support Web site at http://www.ibm.com/software/

support.2. Under Select a brand and/or product, select Tivoli.3. Under Select a product, select a product and click Go.4. Under Download, click the name of a fix to read its description and, optionally,

to download it.If there is no Download heading for your product, supply a search term, errorcode, or APAR number in the field provided under Search Support (thisproduct), and click Search.

365

http://www-306.ibm.com/software/support/isa

http://www.ibm.com/software/support

http://www.ibm.com/software/support

For more information about the types of fixes that are available, see the IBMSoftware Support Handbook at http://techsupport.services.ibm.com/guides/handbook.html.

Contacting IBM Software SupportIBM Software Support provides assistance with product defects. The easiest way toobtain that assistance is to open a PMR or ETR directly from the IBM SupportAssistant (see “Using IBM Support Assistant” on page 365), and attach the logsyou prepare with the help of the Log and Trace Analyzer Tool.

Before contacting IBM Software Support, your company must have an active IBMsoftware maintenance contract, and you must be authorized to submit problems toIBM. The type of software maintenance contract that you need depends on thetype of product you have:v For IBM distributed software products (including, but not limited to, Tivoli,

Lotus®, and Rational® products, as well as DB2® and WebSphere® products thatrun on Windows®, or UNIX® operating systems), enroll in Passport Advantage®

in one of the following ways:

OnlineGo to the Passport Advantage Web site at http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm and clickHow to Enroll.

By phoneFor the phone number to call in your country, go to the IBM SoftwareSupport Web site at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

v For customers with Subscription and Support (S & S) contracts, go to theSoftware Service Request Web site at https://techsupport.services.ibm.com/ssr/login.

v For customers with IBMLink, CATIA, Linux®, S/390®, iSeries®, pSeries®, zSeries,and other support agreements, go to the IBM Support Line Web site athttp://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006.

v For IBM eServer™ software products (including, but not limited to, DB2 andWebSphere products that run in zSeries, pSeries, and iSeries environments), youcan purchase a software maintenance agreement by working directly with anIBM sales representative or an IBM Business Partner. For more informationabout support for eServer software products, go to the IBM Technical SupportAdvantage Web site at http://www.ibm.com/servers/eserver/techsupport.html.

If you are not sure what type of software maintenance contract you need, call1-800-IBMSERV (1-800-426-7378) in the United States. From other countries, go tothe contacts page of the IBM Software Support Handbook on the Web athttp://techsupport.services.ibm.com/guides/contacts.html and click the name ofyour geographic region for phone numbers of people who provide support foryour location.


http://techsupport.services.ibm.com/guides/handbook.html

http://techsupport.services.ibm.com/guides/handbook.html

http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

http://www-306.ibm.com/software/howtobuy/passportadvantage/pao_customers.htm

http://techsupport.services.ibm.com/guides/contacts.html


https://techsupport.services.ibm.com/ssr/login

https://techsupport.services.ibm.com/ssr/login

http://www.ibm.com/services/us/index.wss/so/its/a1000030/dt006

http://www.ibm.com/servers/eserver/techsupport.html


If you prefer to contact IBM Software support without the help of the IBM SupportAssistant, complete the following steps:1. “Determining the business impact”2. “Describing problems and gathering information”3. “Submitting problems”

Determining the business impactWhen you report a problem to IBM, you are asked to supply a severity level.Therefore, you need to understand and assess the business impact of the problemthat you are reporting. Use the following criteria:

Severity 1The problem has a critical business impact. You are unable to use theprogram, resulting in a critical impact on operations. This conditionrequires an immediate solution.

Severity 2The problem has a significant business impact. The program is usable, butit is severely limited.

Severity 3The problem has some business impact. The program is usable, but lesssignificant features (not critical to operations) are unavailable.

Severity 4The problem has minimal business impact. The problem causes little impacton operations, or a reasonable circumvention to the problem wasimplemented.

Describing problems and gathering informationWhen describing a problem to IBM, be as specific as possible. Include all relevantbackground information so that IBM Software Support specialists can help yousolve the problem efficiently. To save time, know the answers to these questions:v What software versions were you running when the problem occurred?v Do you have logs, traces, and messages that are related to the problem

symptoms? IBM Software Support is likely to ask for this information.v Can you re-create the problem? If so, what steps were performed to re-create the

problem?v Did you make any changes to the system? For example, did you make changes

to the hardware, operating system, networking software, and so on.v Are you currently using a workaround for the problem? If so, be prepared to

explain the workaround when you report the problem.

Submitting problemsYou can submit your problem to IBM Software Support in one of two ways:

OnlineClick Submit and track problems on the IBM Software Support site athttp://www.ibm.com/software/support/probsub.html. Type yourinformation into the appropriate problem submission form.

By phoneFor the phone number to call in your country, go to the contacts page ofthe IBM Software Support Handbook at http://techsupport.services.ibm.com/guides/contacts.html and click the name of your geographic region.

Support information 367

http://www.ibm.com/software/support/probsub.html



If the problem you submit is for a software defect or for missing or inaccuratedocumentation, IBM Software Support creates an Authorized Program AnalysisReport (APAR). The APAR describes the problem in detail. Whenever possible,IBM Software Support provides a workaround that you can implement until theAPAR is resolved and a fix is delivered. IBM publishes resolved APARs on theSoftware Support Web site daily, so that other users who experience the sameproblem can benefit from the same resolution.


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

369

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM CorporationJ46A/G4555 Bailey AvenueSan Jose, CA 95141-1003U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have notbeen thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM's application programming interfaces.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.


TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, other countries,or both. These and other IBM trademarked terms are marked on their firstoccurrence in this information with the appropriate symbol (® or ™), indicating USregistered or common law trademarks owned by IBM at the time this informationwas published. Such trademarks may also be registered or common lawtrademarks in other countries. A complete and current list of IBM trademarks isavailable on the Web at http://www.ibm.com/legal/copytrade.shtml.

Microsoft®, Windows, Windows NT®, and the Windows logo are trademarks ofMicrosoft Corporation in the Unites States, other countries, or both.

Other company, product, and service names may be trademarks or service marksof others.

Notices 371

http://www.ibm.com/legal/copytrade.shtml


Bibliography

You might need to refer to other sources of information when you are using Advanced AllocationManagement.

This section lists the documentation that supports Advanced Allocation Management.

Tip: To quickly locate a specific book, use the IBM Publications Center, which is located atwww.elink.ibmlink.ibm.com/public/applications/publications/cgibin/pbi.cgi. After you enter yourcountry information, click Search for publications , and enter the publication number (xxxx-xxxx) of thebook that you want.

Titles cited in this bookv RACF General Information, GC28-0722-19v MVS Programming: Authorized Assembler Services Guide, SA22-7605-08v z/OS MVS System Management Facilities (SMF), SA22-7630-15v z/OS V1R10.0 DFSMS Storage Administration Reference (for DFSMSdfp, DFSMSdss, DFSMShsm),

SC26-7402-10

373



Index

Special characters$DCO 91, 155$DCOC 75, 91$DCOU 75, 91$NULL 75, 90

Aabend

B37 1D37 1E37 1prevention 1recovery 1

ACCBIAS keywordsyntax 209

ACS environment considerations 92ACTIVATE

command 80ACTIVATE RULEDEFS command 312ACTIVATE VGRPDEFS command 312activating

rule definitions 56volume group definitions 80

Active rule definitionModifiable Subsystem Settings 42

Active VGRP definitionModifiable Subsystem Settings 42

ADISP keywordsyntax 210

Advanced Allocation Managementaudience, intended xicompatibility with other products 10event recording and reporting 2operator commands 2, 311overview 1single instance 7started task 23subsystem ID 8, 21supported data set types 2VSAM support 2

Advanced Allocation ManagementSubsystem Settings

status information 43Advanced Allocation Manager

configuring 19allocation attributes 94

setting 75AOBYPASS 305APF-authorizing

load library 20architecture and processing 6automatic started task 23AVS

description 58keyword 101

AVS_ALGORITHMkeyword 102, 141

AVS_ALGORITHM keywordsyntax 102, 141

AVS_MOUNT_USAGEkeyword 104

example 104AVS_MOUNT_USAGE keyword

syntax 104AVS_UNIT

keyword 105AVS_UNIT keyword

syntax 105AVS_VGRP

keyword 106AVS_VGRP keyword

example 106syntax 106

AVS_VGRP_SEARCHkeyword 106

AVS_VGRP_SEARCH keywordexample 106syntax 106

AVS_VSERkeyword 107

AVS_VSER keywordexample 107syntax 107

BB37 68batch reporting utility 289

sample reports 292, 293, 295batch reporting utility JCL

configuring 290BLKSIZE keyword

syntax 211books

see publications xi, xiiBUFSPC keyword

syntax 212bypassing

specific processing 305

Ccharacter string values 91CISZ keyword

syntax 213CISZ_DATA keyword

syntax 213CISZ_INDEX keyword

syntax 214CLISTs

customizing 23GLO 23GLOCLIST 23

commandsACTIVATE 56, 80

command 56DISPLAY 81

comment cardrule definitions 52

commentsincluding in syntax 84

comparison operators 74, 89components 4configuration steps 19

configuring the started task JCL 20summary of 19

CONTIGUOUS keywordsyntax 215

CONTINUEkeyword 108

CONTINUE keywordexample 108syntax 108

Continue RULEDEF processing 59control data set 7

allocating 21and definition management 31member types 4OPTIONS member 21overview of 4security considerations 16shared 34specifying 38, 39

control data set membercreating 41specifying 40

control data set membersdisplaying 40managing 38modifying 32selecting 39

Control Data Set NameFixed Subsystem Settings 42

control data set requirements 31control data sets

separate 33Control member management

options 40conventions

abbreviations xiiitypeface xiii

creatingrule definitions 52volume group definitions 79

customer supportSee Software Support

customization stepsallocating the control data set 21APF-authorizing load libraries 20customizing the CLISTs 23initiating the started task 23securing user interface 22specifying subsystem options 21verifying the installation 24

DD37 67data class override 75, 91

375

data set namesand wildcard characters 84

DATACLAS keywordsyntax 215

DATASET_INITdescription 60keyword 109

DATASET_INIT keywordexample 109

DDNAME keywordsyntax 216

default processingrule definitions 55

DEFAULTSkeyword 87

DEFAULTS keywordexample 87syntax 87

DEFERMOUNT keywordsyntax 217

definition management 31and multiple instances 33and the control data set 31

definitionsvolume group 79

Detail Reportreport option 48

DEVICECLASS keywordsyntax 218

DIAGkeyword 109

DIAG keywordexample 109syntax 109

DIAGNOSE command 311dialog

messages 315DIRBLKS keyword

syntax 219DIRECTORY FULL conditions

and PDS_DIR_INC function 63DISABLE INTERCEPTS command 312DISABLE SUBSYSTEM command 312DISPLAY

command 81DISPLAY ALL command 311display commands 311DISPLAY INTERCEPTS command 311DISPLAY RULEDEFS command 311Display Statistics

Primary Option Menu 37DISPLAY SUBSYSTEM ALL

command 311DISPLAY SUBSYSTEM command 311displaying

active rule definitions 57volume group definitions 81

DSECTs 297DSNAME keyword

syntax 219DSNAME_DATA keyword

syntax 220DSNAME_INDEX keyword

syntax 221DSNAME_LASTNODE keyword

syntax 221

DSNAME_QUALIFIER keywordsyntax 222

DSNAME_TYPE keywordsyntax 223

DSORG keywordsyntax 224

dynamic configuration operatorcommands 312

Eeducation 365

see Tivoli technical training xiiienable and disable

operator commands 312ENABLE INTERCEPTS command 312ENABLE SUBSYSTEM command 312end-of-volume intercepts 7end-of-volume processing 4Enhanced Allocation Management

functions 89, 91keywords 155processing 75SET_ACCBIAS 157SET_ADISP 158SET_BLKSIZE 159SET_BUFSPC 160SET_CISZ 160SET_CISZ_DATA 161SET_CISZ_INDEX 162SET_CONTIGUOUS 163SET_DATACLAS 163SET_DEFERMOUNT 164SET_DIRBLKS 165SET_DSNAME_TYPE 166SET_DSORG 167SET_EXPDATE 168SET_EXTADDR 169SET_FILESEQNO 170SET_FRLOG 171SET_FSPC_CA 172SET_FSPC_CI 173SET_ILOAD 173SET_KEY_LEN 174SET_KEY_OFF 175SET_LOGSTREAM_ID 176SET_LRECL 177SET_MGMTCLAS 178SET_NDISP 179SET_NUMVOLS 180SET_NUMVOLS_DATA 181SET_NUMVOLS_INDEX 182SET_PQTY 182SET_PQTY_DATA 183SET_PQTY_INDEX 184SET_RECFM 185SET_REPTD 189SET_REUSE 190SET_SHROPT_XRGN 191SET_SHROPT_XSYS 192SET_SPACEUNITS 193SET_SPACEUNITS_DATA 195SET_SPACEUNITS_INDEX 196SET_SPANNED 197SET_SQTY 198SET_SQTY_DATA 199SET_SQTY_INDEX 199

Enhanced Allocation Management(continued)

SET_STORCLAS 200SET_STORGRP 201SET_TAPE_COMP 202SET_TAPE_LABEL 203SET_UNIT_AFFINITY 204SET_UNIT_COUNT 205SET_UNIT_NAME 205SET_VOLCT 206SET_VSAM_SEPARATE 207

Enhanced Allocation Managementfunctions

using 75evaluation

rule definition 52event history 46event recording

disabling 288enabling 287

event recording and reporting 287batch reporting utility 289filter criteria 288messages 359

exampleAVS function 58CONTINUE function 59DATASET_INIT function 60NOTCAT2 function 60PDS_DIR_INC function 63PRIM_REDUCE function 65RULEDEF_TEST function 66SEC_ALLOC function 67SEC_BEST function 68SEC_INC function 69SEC_REDUCE function 70SPACE_RELEASE function 72TERM_ALLOC function 73VOL_ADD function 73volume group list 81

examplesrule definitions 58

EXCLUDEkeyword 87

EXCLUDE keywordexample 89syntax 89

excluding items from processing 55EXPDATE keyword


EXTADDR keywordsyntax 226

FFACILITY class 22FILESEQNO keyword

syntax 227filter criteria 288

value prefixes 300filter criteria formats 288filter set criteria

specifying 47filtersets 288fix packs 365Fixed Subsystem Settings 42


Formatreport option 48

FORMAT=L detail record map 298formatted basic detail record report 293formatted extended detail record

report 293frequently asked questions 307FRLOG keyword

syntax 228FSPC_CA keyword

syntax 229FSPC_CI keyword

syntax 229function

AVS 101AVS_ALGORITHM 102, 141AVS_MOUNT_USAGE 104AVS_UNIT 105AVS_VGRP 106AVS_VGRP_SEARCH 106AVS_VSER 107CONTINUE 108DATASET_INIT 109DIAG 109keywords 101MESSAGES 111MSG_DESTINATION 112MSG_LEVEL 113NOTCAT2 115NOTCAT2_CHECK 117NOTCAT2_DYNAL 118NOTCAT2_QUALIFIER 119NOTCAT2_QUALIFIER_

POSITION 120NOTCAT2_SUFFIX 121PDS_DIR_INC 121PRIM_REDUCE 122PRIM_REDUCE_INC 124PRIM_REDUCE_LIM 126RULEDEF_TEST 126SEC_ALLOC 127SEC_ALLOC_AMT 128SEC_BEST 129SEC_BEST_LIM 130SEC_INC 130SEC_INC_AMT 131SEC_INC_VOLNO 132SEC_INC_XTNT 133SEC_REDUCE 133SEC_REDUCE_INC 134SEC_REDUCE_LIM 135SPACE_RELEASE 136TERM_ALLOC 137VOL_ADD 138VOL_ADD_LIM 143VOL_ADD_MOUNT_USAGE 144VOL_ADD_PROMPT 145VOL_ADD_SGRP 146VOL_ADD_UNIT 147VOL_ADD_VGRP 148VOL_ADD_VGRP_SEARCH 149VOL_ADD_VSER 150WRITE_MSG 151

function and selection criteriaenvironments 94

functions 89determining which to include 53

functions (continued)Enhanced Allocation

Management 89, 91keyword reference 53multiple 55

GGLO.ADMIN.* profile 22GLO.ADMIN.ssid profile 22GLOCLIST

customizing 23GLOJCNTL member 21GLOJIVP1 member

descriptions 24modifying 24successful results 29

GLOJLOGR member 290GLOJSTC member 20glossary, accessing online xiiGLOSSMFR 297, 298GLOSSMFR member 297GROUP_NAME

keyword 79GROUP_NAME keyword


GROUPID keywordsyntax 230

GUARSPACE keywordsyntax 231

guidelinesrule definitions 57syntax 83

Hhardware requirements 13

IIBM Redbooks 365IBM Support Assistant 365IEF287I

system message 60ILOAD keyword

syntax 231INCLUDE

keyword 87INCLUDE keyword

example 88syntax 88

including items in processing 55INITIAL_RULEDEF subsystem

option 21, 309INITIAL_VGRPDEF subsystem

option 21, 309input control statements 291Input Options 46installation 16

verifying 24installing

Advanced AllocationManagement 13

instancesmultiple 8

intercepts 7enabling and disabling 305

Intercepts StatusModifiable Product-level Setting 43

IPLsand the started task 23

JJCL

started task 20JOBACCTn keyword

syntax 232JOBCLASS keyword

syntax 233JOBNAME keyword

syntax 233jobnames

and wildcard characters 84JOBTYPE keyword

syntax 234

KKEY_LEN keyword

syntax 235KEY_OFF keyword

syntax 236keyword reference

functions 53keywords

ACCBIAS 209ADISP 210AVS 101AVS_ALGORITHM 102, 141AVS_MOUNT_USAGE 104AVS_UNIT 105AVS_VGRP 106AVS_VGRP_SEARCH 106AVS_VSER 107BLKSIZE 211BUFSPC 212CISZ 213CISZ_DATA 213CISZ_INDEX 214CONTIGUOUS 215CONTINUE 108DATACLAS 215DATASET_INIT 109DDNAME 216DEFAULTS 87DEFERMOUNT 217DEVICECLASS 218DIAG 109DIRBLKS 219DSNAME 219DSNAME_DATA 220DSNAME_INDEX 221DSNAME_LASTNODE 221DSNAME_QUALIFIER 222DSNAME_TYPE 223DSORG 224Enhanced Allocation

Management 155ENVIRONMENT 110EXCLUDE 87, 89

Index 377

keywords (continued)EXPDATE 225EXTADDR 226FILESEQNO 227FRLOG 228FSPC_CA 229FSPC_CI 229function 89, 101GROUP_NAME 79, 285GROUPID 230GUARSPACE 231ILOAD 231INCLUDE 87, 88JOBACCTn 232JOBCLASS 233JOBNAME 233JOBTYPE 234KEY_LEN 235KEY_OFF 236LOGGING 236LOGSTREM_ID 237LRECL 238MAXSPACE 239MESSAGES 111MGMTCLAS 240MOUNT_USAGE 241MSG_DESTINATION 112MSG_LEVEL 113NDISP 242NOTCAT2 60, 115NOTCAT2_CHECK 60, 117NOTCAT2_DYNAL 118NOTCAT2_QUALIFIER 60, 119NOTCAT2_QUALIFIER_

POSITION 120NOTCAT2_SUFFIX 60, 121NUMVOLS 243NUMVOLS_DATA 244NUMVOLS_INDEX 244OWNERID 245PDS_DIR_INC 121PQTY 247PQTY_DATA 248PQTY_INDEX 249PRIM_REDUCE 122PRIM_REDUCE_INC 124PRIM_REDUCE_LIM 126PROCSTEPNAME 246PROGRAM 246PSPACE_KB 249PSPACE_MB 250RECFM 251RELEASESPACE 255RETPD 256REUSE 257RULEDEF_TEST 35, 126SDISP 258SEC_ALLOC 127SEC_ALLOC_AMT 128SEC_BEST 129SEC_BEST_LIM 130SEC_INC 130SEC_INC_AMT 131SEC_INC_VOLNO 132SEC_INC_XTNT 133SEC_REDUCE 133SEC_REDUCE_INC 134

keywords (continued)SEC_REDUCE_LIM 135selection criteria 89SET_ACCBIAS 157SET_ADISP 158SET_BLKSIZE 159SET_BUFSPC 160SET_CISZ 160SET_CISZ_DATA 161SET_CISZ_INDEX 162SET_CONTIGUOUS 163SET_DATACLAS 163SET_DEFERMOUNT 164SET_DIRBLKS 165SET_DSNAME_TYPE 166SET_DSORG 167SET_EXPDATE 168SET_EXTADDR 169SET_FILESEQNO 170SET_FRLOG 171SET_FSPC_CA 172SET_FSPC_CI 173SET_ILOAD 173SET_KEY_LEN 174SET_KEY_OFF 175SET_LOGSTREM_ID 176SET_LRECL 177SET_MGMTCLAS 178SET_NDISP 179SET_NUMVOLS 180SET_NUMVOLS_DATA 181SET_NUMVOLS_INDEX 182SET_PQTY 182SET_PQTY_DATA 183SET_PQTY_INDEX 184SET_RECFM 185SET_RETPD 189SET_REUSE 190SET_SHROPT_XGRN 191SET_SHROPT_XSYS 192SET_SPACEUNITS 193SET_SPACEUNITS_DATA 195SET_SPACEUNITS_INDEX 196SET_SPANNED 197SET_SQTY 198SET_SQTY_DATA 199SET_SQTY_INDEX 199SET_STORCLAS 200SET_STORGRP 201SET_TAPE_COMP 202SET_TAPE_LABEL 203SET_UNIT_AFFINITY 204SET_UNIT_COUNT 205SET_UNIT_NAME 205SET_VOLCT 206SET_VSAM_SEPARATE 207SHROPT_XGRN 259SHROPT_XSYS 260SMS_MANAGED 260SPACE_RELEASE 136SPACEUNITS 261SPACEUNITS_DATA 263SPACEUNITS_INDEX 264SPANNED 265SQTY 265SQTY_DATA 266SQTY_INDEX 267

keywords (continued)STEPACCTn 268STEPNAME 268STORCLAS 269STORGRP 270SUBSYS 271SYSID 271SYSPLEXNAME 272TAPE_COMP 272TAPE_LABEL 273TEMPDS 274TERM_ALLOC 137UNIT_AFFINITY 275UNIT_COUNT 275UNIT_NAME 276UNIT_TYPE 277USERID 278VOL_ADD 138VOL_ADD_LIM 143VOL_ADD_MOUNT_USAGE 144VOL_ADD_PROMPT 145VOL_ADD_SGRP 146VOL_ADD_UNIT 147VOL_ADD_VGRP 148VOL_ADD_VGRP_SEARCH 149VOL_ADD_VSER 150VOLCT 279VOLSER_ANY 280VOLSER_CURRENT 281VOLSER_FIRST 282VOLUMES 79, 285VSAM_SEPARATE 283WRITE_MSG 151

Llist of multiple items

in syntax 83Listing Data Set

output option 48load library

APF-authorizing 20LOGGING keyword

syntax 236LOGSTREAM_ID keyword

syntax 237LRECL keyword

syntax 238

Mmain keywords


Manage Control MembersPrimary Option Menu 37

manualssee publications xi, xii

MAXSPACE keywordsyntax 239

member typesin control data set 4

messagesdialog 315event recording and reporting 359format 313


messages (continued)non-VSAM function 335subsystem and started task 319syntax-check 351VSAM function 347

MESSAGESkeyword 111

MESSAGES keywordexample 111syntax 111

MGMTCLAS keywordsyntax 240

migration 16planning for 14

migration considerations 14Modifiable Product-level Settings 43Modifiable Subsystem Settings 42modifying


MOUNT_USAGE keywordsyntax 241

MSG_DESTINATIONkeyword 112

MSG_DESTINATION keywordexample 112syntax 112

MSG_LEVELkeyword 113

MSG_LEVEL keywordMSG_LEVEL keyword


multiple filtersetsspecifying 288

multiple functionsspecifying 55

multiple instancesand definition management 33overview 8

multiple operandsspecifying 83

multiple selection criteriaspecifying 55

MVSSTOW service 63

NNDISP keyword

syntax 242non-VSAM function

messages 335NOTCAT2


NOTCAT2 keywordexample 60, 115syntax 60, 115

NOTCAT2 security considerations 19NOTCAT2_CHECK

keyword 117NOTCAT2_CHECK keyword


NOTCAT2_CHECK_QUALIFIERkeyword

example 119NOTCAT2_CHECK_QUALIFIER_

POSITION keywordexample 120

NOTCAT2_DYNALkeyword 118

NOTCAT2_QUALIFIERkeyword 119

NOTCAT2_QUALIFIER keywordsyntax 119

NOTCAT2_QUALIFIER_ POSITIONkeyword 120

NOTCAT2_QUALIFIER_ POSITIONkeyword

syntax 120NOTCAT2_SUFFIX

keyword 121NOTCAT2_SUFFIX keyword


notices 369numeric comparisons 90numeric suffixes 91NUMVOLS keyword

syntax 243NUMVOLS_DATA keyword

syntax 244NUMVOLS_INDEX keyword

syntax 244

Oonline help

accessing 38online publications xiioperands

multiple 83operating commands

issuing 311operator commands 311

ACTIVATE RULEDEFS 312ACTIVATE VGRPDEFS 312DIAGNOSE 311DISABLE INTERCEPTS 312DISABLE SUBSYSTEM 312DISPLAY ALL 311display commands 311DISPLAY INTERCEPTS 311DISPLAY RULEDEFS 311DISPLAY SUBSYSTEM 311DISPLAY SUBSYSTEM ALL 311dynamic configuration 312enable and disable 312ENABLE INTERCEPTS 312ENABLE SUBSYSTEM 312

optionsOutput 48Report 48

OPTIONS member 21out-of-space

conditions 65Output Mode

output option 48Output Options 48

OWNERID keywordsyntax 245

PPDS_DIR_INC


PDS_DIR_INC keywordexample 121syntax 121

PQTY keywordsyntax 247

PQTY_DATA keywordsyntax 248

PQTY_INDEX keywordsyntax 249

prerequisitesexperience xiknowledge xi

PRIM_REDUCEdescription 65keyword 122

PRIM_REDUCE functionand space recovery strategies 76

PRIM_REDUCE keywordexample 122syntax 122

PRIM_REDUCE_INCkeyword 124

PRIM_REDUCE_INC keywordexample 124syntax 124

PRIM_REDUCE_LIMkeyword 126

PRIM_REDUCE_LIM keywordexample 126syntax 126

problem determinationdescribing problems 367determining business impact 367submitting problems 367

problem resolution 365processing

end-of-volume 4Enhanced Allocation Management 75including or excluding items 55SEC_ALLOC 67SEC_BEST 68SEC_INC 69SEC_REDUCE 70SPACE_RELEASE 72TERM_ALLOC 73using rule definitions to define 51VOL_ADD 73

PROCSTEPNAME keywordsyntax 246

product compatibilityconsiderations 10

product definitionsconverting 15

product panels 16Tivoli Advanced Allocation

Management Control MemberManagement 38

Index 379

product panels (continued)Tivoli Advanced Allocation

Management Primary OptionMenu 37

Tivoli Advanced AllocationManagement Recovery Statistics 43

Tivoli Advanced AllocationManagement SubsystemSettings 41, 56

Tivoli Advanced AllocationManagement View EventHistory 46

product-level intercepts 7, 43PROGRAM keyword

syntax 246PSPACE_KB keyword

syntax 249PSPACE_MB keyword

syntax 250publications xi

accessing online xiiordering xii

RRACF 17

FACILITY class 22RACF profiles 16

descriptions of 22RECFM keyword

syntax 251recovery statistics 43, 44Redbooks, IBM 365RELEASESPACE keyword

syntax 255Report option combinations and

results 289report options 289Report Options 48required DD statements

modifying 290requirements

hardware 13rule definition member 52software 13volume definition member 80

RETPD keywordsyntax 256

REUSE keywordsyntax 257

rule definitionevaluation 52guidelines 57syntax 51

Rule definition last activatedStatus Information 43

rule definition membercomment card 52requirements 52

rule definitions 32, 51activating 56creating and modifying 52default processing 55determining functions to include 53displaying active 57examples 58main keywords 87

rule definitions (continued)overview 4syntax precedence 51understanding 51

RULEDEF_TESTkeyword 126

RULEDEF_TEST description 66RULEDEF_TEST keyword 35

example 126

Ssample

VGRPDEFS 79sample library 20

GLOCLIST member 23GLOJCNTL member 21GLOJIVP1 member 24GLOJLOGR member 290GLOJSTC member 20GLOSSMFR member 297

sample reportsbatch reporting utility 292, 293, 295

SDISP keywordsyntax 258

SEC_ALLOCdescription 67keyword 127processing 67

SEC_ALLOC keywordexample 127syntax 127

SEC_ALLOC_AMTkeyword 128

SEC_ALLOC_AMT keywordexample 128syntax 128

SEC_BESTdescription 68keyword 129processing 68

SEC_BEST functionand space recovery strategies 76

SEC_BEST keywordexample 129syntax 129

SEC_BEST_LIMkeyword 130

SEC_BEST_LIM keywordexample 130syntax 130

SEC_INCdescription 69keyword 130processing 69

SEC_INC keywordexample 130syntax 130

SEC_INC_AMTkeyword 131

SEC_INC_AMT keywordexample 131syntax 131

SEC_INC_VOLNOkeyword 132

SEC_INC_VOLNO keywordexample 132

SEC_INC_VOLNO keyword (continued)syntax 132

SEC_INC_XTNTkeyword 133

SEC_INC_XTNT keywordexample 133syntax 133

SEC_REDUCEdescription 70keyword 133processing 70

SEC_REDUCE functionand space recovery strategies 76

SEC_REDUCE keywordexample 133syntax 133

SEC_REDUCE_INCkeyword 134

SEC_REDUCE_INC keywordexample 134syntax 134

SEC_REDUCE_LIMkeyword 135

SEC_REDUCE_LIM keywordexample 135syntax 135

securinguser interface update functions 22

security considerations 16, 18and the control data set 16NOTCAT2 19Tivoli Advanced Allocation

Management Subsystem Settingsscreen 16

selection criteria 209ACCBIAS 209ADISP 210BLKSIZE 211BUFSPC 212CISZ 213CISZ_DATA 213CISZ_INDEX 214CONTIGUOUS 215DATACLAS 215DDNAME 216DEFERMOUNT 217DEVICECLASS 218DIRBLKS 219DSNAME 219DSNAME_DATA 220DSNAME_INDEX 221DSNAME_LASTNODE 221DSNAME_QUALIFIER 222DSNAME_TYPE 223DSORG 224EXTADDR 226FILESEQNO 227FRLOG 228FSPC_CA 229FSPC_CI 229GROUPID 230GUARSPACE 231ILOAD 231JOBACCTn 232JOBCLASS 233JOBNAME 233JOBTYPE 234


selection criteria (continued)KEY_LEN 235KEY_OFF 236keywords 89LOGGING 236LOGSTREAM_ID 237LRECL 238MAXSPACE 239MGMTCLAS 240MOUNT_USAGE 241multiple 55NDISP 242NUMVOLS 243NUMVOLS_DATA 244NUMVOLS_INDEX 244OWNERID 245PQTY 247PQTY_DATA 248PQTY_INDEX 249PROCSTEPNAME 246PROGRAM 246PSPACE_KB 249PSPACE_MB 250RECFM 251RELEASESPACE 255REPTD 256REUSE 257SDISP 258SHROPT_XRGN 259SHROPT_XSYS 260SMS_MANAGED 260SPACEUNITS 261SPACEUNITS_DATA 263SPACEUNITS_INDEX 264SPANNED 265SQTY 265SQTY_DATA 266SQTY_INDEX 267STEPACCTn 268STEPNAME 268STORCLAS 269STORGRP 270SUBSYS 271SYSID 271SYSPLEXNAME 272TAPE_COMP 272TAPE_LABEL 273TEMPDS 274UNIT_AFFINITY 275UNIT_COUNT 275UNIT_NAME 276UNIT_TYPE 277USERID 278VOLCT 279VOLSER_ANY 280VOLSER_CURRENT 281VOLSER_FIRST 282VSAM_SEPARATE 283

selection criteria processing 94SET_ACCBIAS keyword

syntax 157SET_ADISP keyword

syntax 158SET_BLKSIZE keyword

syntax 159SET_BUFSPC keyword

syntax 160

SET_CISZ keywordsyntax 160

SET_CISZ_DATA keywordsyntax 161

SET_CISZ_INDEX keywordsyntax 162

SET_CONTIGUOUS keywordsyntax 163

SET_DATACLAS keywordsyntax 163

SET_DEFERMOUNT keywordsyntax 164

SET_DIRBLKS keywordsyntax 165

SET_DSNAME_TYPE keywordsyntax 166

SET_DSORG keywordsyntax 167

SET_EXPDATE keywordexample 168syntax 168

SET_EXTADDR keywordsyntax 169

SET_FILESEQNO keywordsyntax 170

SET_FRLOG keywordsyntax 171

SET_FSPC_CA keywordsyntax 172

SET_FSPC_CI keywordsyntax 173

SET_ILOAD keywordsyntax 173

SET_KEY_LEN keywordsyntax 174

SET_KEY_OFF keywordsyntax 175

SET_LOGSTREAM_ID keywordsyntax 176

SET_LRECL keywordsyntax 177

SET_MGMTCLAS keywordsyntax 178

SET_NDISP keywordsyntax 179

SET_NUMVOLS keywordsyntax 180

SET_NUMVOLS_DATA keywordsyntax 181

SET_NUMVOLS_INDEX keywordsyntax 182

SET_PQTY keywordsyntax 182

SET_PQTY_DATA keywordsyntax 183

SET_PQTY_INDEX keywordsyntax 184

SET_RECFM keywordsyntax 185

SET_RETPD keywordsyntax 189

SET_REUSE keywordsyntax 190

SET_SHROPT_XGRN keywordsyntax 191

SET_SHROPT_XSYS keywordsyntax 192

SET_SPACEUNITS keywordsyntax 193

SET_SPACEUNITS_DATA keywordsyntax 195

SET_SPACEUNITS_INDEX keywordsyntax 196

SET_SPANNED keywordsyntax 197

SET_SQTY keywordsyntax 198

SET_SQTY_DATA keywordsyntax 199

SET_SQTY_INDEX keywordsyntax 199

SET_STORCLAS keywordsyntax 200

SET_STORGRP keywordsyntax 201

SET_TAPE_COMP keywordsyntax 202

SET_TAPE_LABEL keywordsyntax 203

SET_UNIT_AFFINITY keywordsyntax 204

SET_UNIT_COUNT keywordsyntax 205

SET_UNIT_NAME keywordsyntax 205

SET_VOLCT keywordsyntax 206

SET_VSAM_SEPARATE keywordsyntax 207

SGLOSAMP 24SHROPT_XGRN keyword

syntax 259SHROPT_XSYS keyword

syntax 260SMF source files

specifying 47SMF_RECORD_ID subsystem option 21SMS_MANAGED keyword

syntax 260software

requirements 13Software Support 365

contacting 366describing problems 367determining business impact 367submitting problems 367

sort fields 302Sort-By Field

report option 48space parameter

considerations 92space recovery strategies

PRIM_REDUCE function 76SEC_BEST function 76SEC_REDUCE function 76

SPACE_RELEASEdescription 72keyword 136processing 72

SPACE_RELEASE keywordexample 136syntax 136

SPACEUNITS keywordsyntax 261

Index 381

SPACEUNITS_DATA keywordsyntax 263

SPACEUNITS_INDEX keywordsyntax 264

SPANNED keywordsyntax 265

SQTY keywordsyntax 265

SQTY_DATA keywordsyntax 266

SQTY_INDEX keywordsyntax 267

SSID subsystem option 21, 309started task

and IPLs 23automatic 23initiating 23stopping 23

started task JCLconfiguring 20

Started Task NameFixed Subsystem Settings 42

started task processing 7statistics 44STEPACCTn keyword

syntax 268STEPNAME keyword

syntax 268stopping

started task 23STORCLAS keyword

syntax 269STORGRP keyword

syntax 270string comparisons 90SUBSYS keyword

syntax 271subsystem and started task

messages 319subsystem definition 7subsystem ID 21

Advanced Allocation Management 8specifying 21

Subsystem IDFixed Subsystem Settings 42

subsystem optionsdescriptions 309INITIAL_RULEDEF 21, 309INITIAL_VGRPDEF 21, 309modification and display 309SSID 21, 309Z1_INTERCEPT 309

subsystem OPTIONS member 21Subsystem status

Modifiable Subsystem Settings 42suffixes

numeric 91Summary Report

report option 48support 365support assistant 365syntax

continuation 83guidelines 83including comments in 84lists of multiple items 83rule definition 51

syntax (continued)specifying multiple operands 83volume group definition 79wildcard characters 84

syntax diagramvolume group definitions 285

syntax diagramshow to read xiv

syntax precedencerule definitions 51

syntax-checkmessages 351

SYS1.PARMLIBand the automatic started task 23

SYSID keywordsyntax 271

SYSPLEXNAME keywordsyntax 272

TTAPE_COMP keyword

syntax 272TAPE_LABEL keyword

syntax 273TEMPDS keyword

syntax 274TERM_ALLOC

description 73keyword 137processing 73

terminology xiitest environment

installing in 15Tivoli Advanced Allocation Management

Primary Option Menu 37accessing 23, 37

Tivoli Advanced Allocation ManagementRecovery Statistics 43

Tivoli Advanced Allocation ManagementSubsystem Settings

Modifiable Subsystem Settings 42screen 41, 42, 43

Tivoli Advanced Allocation ManagementSubsystem Settings screen

security considerations 16Tivoli Advanced Allocation Management

View Event Historyscreen 46

Tivoli Software Information Center xiiTivoli technical training xiiitraining, Tivoli technical xiiitroubleshooting 305typeface conventions xiii

UUNIT_AFFINITY keyword

syntax 275UNIT_COUNT keyword

syntax 275UNIT_NAME keyword

syntax 276UNIT_TYPE keyword

syntax 277unspecified values ($NULL) 90

update functions 17user interface 4, 37

starting 23USERID keyword

syntax 278

Vvalue prefixes 300verifying

installation 24VGRP definition last activated

Status Information 43VGRPDEFS 79, 80View Event History

Primary Option Menu 37View/Update Options

Primary Option Menu 37VOL_ADD 79

description 73keyword 138processing 73

VOL_ADD keywordexample 138syntax 138

VOL_ADD_ALGORITHM keywordexample 141

VOL_ADD_LIMkeyword 143

VOL_ADD_LIM keywordexample 143syntax 143

VOL_ADD_MOUNT_USAGEkeyword 144


VOL_ADD_PROMPTkeyword 145

VOL_ADD_PROMPT keywordexample 145syntax 145

VOL_ADD_SGRPkeyword 146

VOL_ADD_SGRP keywordexample 146

VOL_ADD_UNIT keyword 147example 147syntax 147

VOL_ADD_VGRPkeyword 148

VOL_ADD_VGRP keywordexample 148syntax 148

VOL_ADD_VGRP_SEARCHkeyword 149

VOL_ADD_VGRP_SEARCH keywordexample 149syntax 149

VOL_ADD_VSERkeyword 150

VOL_ADD_VSER keywordexample 150syntax 150

VOLCT keywordsyntax 279

VOLSER_ANY keywordsyntax 280


VOLSER_CURRENT keywordsyntax 281

VOLSER_FIRST keywordsyntax 282

volume definition memberrequirements 80

volume group definition syntax 79volume group definitions 4

activating 80creating and modifying 79displaying 81main keywords 285overview 4syntax diagram 285

volume group definitions membersample 79

volume group listexample 81

volume group member definitions 32volume groups

defining 79VOLUMES

keyword 79VOLUMES keyword


VSAM functionmessages 347

VSAM_SEPARATE keywordsyntax 283

Wwildcard characters

and data set names 84and jobnames 84in syntax 84

work data sets 18WRITE_MSG

keyword 151WRITE_MSG keyword


ZZ1_INTERCEPT

subsystem option 309

Index 383


��

Program Number: 5697-P35

Printed in USA

SC23-9817-01

Documents

IBM Tivoli Advanced Allocation Management for z/OS User ...publib.boulder.ibm.com/tividd/td/ITAAMfzOS/SC23... · configuring and using IBM Tivoli Advanced Allocation Management and