On Fri, 6 Feb 2009 10:08:17 -0600, John McKown <joa...@swbell.net> wrote:
>Now this is interesting (to me). APAR OA25205. > >PROBLEM SUMMARY: > **************************************************************** > * USERS AFFECTED: Users of DFSMS that use PDS or PDSE data * > * sets that require an SMF audit trail at * > * the member level. * > **************************************************************** > * PROBLEM DESCRIPTION: Currently, BPAM and DESERV will create * > * an SMF 42 record when a PDS or PDSE * > * directory is initialized and when * > * individual members are deleted. * > * However, BPAM and DESERV does not * > * provide an audit trail at the member * > * level when PDS or PDSE members are * > * added, updated and renamed. SMF type * > * 42 records should be enhanced to * > * provide new subtypes when a PDS or PDSE * > * member for STOW ADD/REPLACE/CHANGE and * > * DESERV PUT/RENAME. * Of course, one can not really depend on getting those records for a PDS, as it does not require very sophisticated programming to rewrite a PDS directory without using STOW. Thus anyone with UPDATE to a PDS could add/delete/rename members of that PDS without any type 42 record being created. -- Walt Farrell, CISSP IBM STSM, z/OS Security Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
