Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Work data set space usage
BMC AMI Utilities allocate work space as needed. These datasets have the high-level qualifier you provide with configuration parameter +WORKPREFIX and their low-level qualifier is WK0000n where n starts with 1 and is incremented as additional datasets are needed.
During processing, the size required for the WK00001 data set vary by product and mostly depend on whether sorting is required. Below are details about WK00001 file usage by product. The WK00001 work space is similar to the typical sort work space with two advantages:
- Allocation is handled outside the JCL to simplify that JCL and prevent allocation errors.
- If WK00001 fills up WK00002 is allocated.
- VSAM is used to facilitate multiple servers sharing the files and information therein.
(Recommended) Use the BMC AMI Utilities defaults for work-file allocations and to use Extended Attribute (EA) enabled DASD for these large VSAM work datasets.
BMC AMI Load
- Keys are sorted to build indexes.
- The data is sorted if sorting is requested with +SORT or ORDER YES.
BMC AMI Reorg
- Space to back up the RID translation table, approx. 8 bytes per key.
- For very non-unique indexes, the RID list for the key is sorted.
- In rare cases the WK work space is used for sorting the data. BMC AMI Reorg generally does not sort the data.
BMC AMI Unload
The data is sorted if sorting is requested with ORDER BY or ORDER YES.