We are creating intraday Image Copy jobs that may contain a mix of small and large tables. We use Templates and Include/Exclude to determine which objects should go to TAPE and which should go to DASD. The threshold for what determines large or small is currently an agreed upon number within the group. For any one database we have a two-step job with one step for DASD and one for TAPE. Ideally we would want everything to go to DASD but we are limiting the size of our DASD pools at the moment. We would like this process to be self-managing to recognize the addition/removal of tablespaces/indexes as well as when the threshold for any given object is exceeded. Today determining which step a table should go in is a manual process
|Who would benefit from this IDEA?||DBAs who need to make decisions of which media to place COPY output on based on table size.|
How should it work?
1) Add syntax to the COPY utility that allows any specific object qualifying to be copied to use one of two template DDs/DSNs - one which will support TAPE output and one which will support DASD output
2) Add syntax to the COPY utility that will allow a threshold to be specified to the utility to decide which template DD/DSN to use
3) The threshold should be compared against the TOTALROWS value in RTS for the object