Your DATACLAS and STORCALS routines have the unusual (at least to me) feature
of removing those attributes if the DSN is not one of the expected ones. That
means that if a unexpected data set needs to be managed, the user cannot
include the DATACLAS and STORCLAS parameters on the DD statement but must wait
until someone has updated the ACS. We use ACS to enforce standards but if the
user went to the trouble to include SMS data in his allocation we try to honor
it (and let RACF fail the allocation if he uses parameters he is not authorized
to.) We also store the default SMS parameters in the RACF DFP fields since it
is easier to change those than the ACS routines.
Robert Pelletier <[EMAIL PROTECTED]> wrote:
Hi All. I have been asked to make a file SMS managed and to add 2 volumes to
the SMS pool. This is uncharted waters for me. I have found our ACS routines
and they are as follows:
PROC STORCLAS
FILTLIST OEDSN INCLUDE(OMVS.**,POSIX.**,OMVSV210.**,CAI.*.HFS.**)
FILTLIST BACKS INCLUDE('SERVP.SLFVNOTE')
SELECT
snip
OTHERWISE
SET &STORCLAS EQ ''
END
END
I need to add SERVP.MONTHLY.SLFVNOTE some where.
snip
PROC DATACLAS
FILTLIST HELMS INCLUDE('SERVP.SLFVNOTE')
SELECT
snip
OTHERWISE
SET &DATACLAS EQ ''
END
END
---------------------------------
Yahoo! FareChase - Search multiple travel sites in one click.
----------------------------------------------------------------------
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
