BMC AMI Load +ALLO
USED | (default) Specifies that BMC AMI Utilities should use the space amount from the existing data set as the primary quantity for the new data set This value is obtained from the high-used RBA in the VSAM catalog. |
|---|---|
ALLO | Specifies that BMC AMI Utilities should use the currently allocated space amount from the existing data set as the primary quantity for the new data set The value is obtained from the high-allocated RBA in the VSAM catalog. |
Db2 | Specifies that BMC AMI Utilities should use primary quantity and secondary quantities from the Db2 catalog as the values for the new data set If the object is not Db2-managed or if the PQTY value is less than the high-used RBA for the data set, BMC AMI Utilities use the high-allocated value. |
KEEPDB2 | Specifies that BMC AMI Utilities should use values from the (PQTY) Db2 catalog for the primary quantity of the new data set This keyword is different from +ALLO(DB2) in that +ALLO(DB2) is a conditional switch, whereas the KEEPDB2 parameter forces BMC AMI Utilities to use the Db2 values. If the data set is user-managed, BMC AMI Utilities use the values in use for primary quantity as it is defined to AMS for the new data set. If a value of -1 is set for any object in the catalog for either PRIQTY or SECQTY, BMC AMI Utilities correctly keep the Db2 primary and secondary allocations. |
MXIG | Has a similar meaning to the MVS JCL SPACE parameter MXIG requests that space allocated to the data set be the smaller of the PQTY needed or the space available on the volume. This parameter affects only primary space allocation. Secondary extents should be available when you use this parameter. |
REUSE | Specifies that BMC AMI Utilities should write the newly loaded data set over the original data set +ALLO(REUSE) can be honored only if the VSAM cluster has the REUSE attribute and the existing size is at least large enough for the data set to be loaded. |