-- snip -- Even with a large FILTLIST, I don't think that the overhead needs to be worried about. The ACS routines are driven mainly during dataset allocation, so unless your site allocates an extraordinary number of datasets per day, the overhead is probably not noticable. Compared to the rest of the code for allocation (volume selection, DADSM, catalog, etc.) I doubt if even a large filtlist will be a significant part. You could put tests up front in the ACS rtns to identify datasets that definitely don't match the filtlists and bypass that search for many datasets. -- snip --
A very different approach is to use RACF to contain information that you can then check in your ACS routines. It may be a better approach, since you will not have to maintain very large filter lists. John ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
