Some ideas: 1) Code something in REXX that wraps itself around your INIT JCL process and updates a file accordingly 2) Allocate a special one track dataset with volser and timestamp info in the dataset name. Periodically LISTC to see them. If re-initing, make sure there is a JCL step to delete the special dataset.
3) If you are talking about massive amounts of DASD, write a JCL generator that, in addition to building the JCL, updates an audit file. Lots of us have REXX that generates DASD INIT JCL. Although I haven't used mine in years, I can send it to you if you like. Bob --------------------------------------------------------- Robert B. Richards (Bob) US Office of Personnel Management 1900 E Street NW Room: BH04L Washington, D.C. 20415 Phone: (202) 606-1195 Email: robert.richa...@opm.gov --------------------------------------------------------- -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Jennifer Currell Sent: Thursday, July 02, 2009 5:48 AM To: IBM-MAIN@bama.ua.edu Subject: VTOC audit trail - init of new dasd volumes Hello Does anyone know how I could track dasd volumes being initialised? This would be for audit purposes. I can look at DCOLLECT info and see live SYS1.VTOCIX.volser datasets. This only looks at dasd available when the job was run. This shows when they were created but not what they were called before. I can look at SMF data to show when the ICKDSF program was run. This gives a job name but not the userid. And doesn't show any volser details. I would like to find out when the ICKDSF program was run and the volser name before and afterwards. I could scan the syslogs but this only show the UCB address not the volsers. Does anyone have any ideas? Thanks ---------------------------------------------------------------------- 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
