Tim Hare wrote: >As mentioned before, I've created a SHARE requirement and an RFE to have the >system record the information from the IFC001I (cataloged procedure was >expanded from... msg) and IFC002I (INCLUDE was expanded from... msg) message >in an SMF record. If this would be important or useful to your shop, you >should vote this up. I know we've wanted to find a way for years to determine >what cataloged procedures are in use, and eliminate the ones no one uses from >the non-IBM libraries. This will also help determine if someone is using >JCLLIB to run their own version of a procedure.
While you're waiting for that RFE to be accepted (?), please consider RACF command altdsd <whatever dsn profile> audit(all(READ)) for ALL your dataset profiles except the catalogs where you can perhaps use audit(all(ALTER)) for them. This will ensure that all and every type of access attempts are logged. Of course, you will have to weed out the non proc dsn from your RACF reports to see what you want. You wrote in that RFE: "Organizations of long standing often have thousands of cataloged procedures. Often a large percentage of these are obsolete or never used (FORTRAN Code-and-Go procedures, anyone?) " Thousands? Wow! That is four-letter word bad. Just migrate them and see when they're recalled by HSM upon usage. Put them in WARNING or (better) clear out the access list in RACF and see who holws at you at 03:00. You can use CSI to search for anciend and unused procs, but I agree in all, a nice SMF record would be handy dandy. Of course JCLLIB is very tricky to check and track. Perhaps a JES2 exit can help you to eliminate all JCLLIB statement, but ... >Here's the RFE link: >http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=133491 I have Voted for that cool RFE under grave danger... ;-D Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
