we found the answer but it seems that something is still wrong. apparently, the file was under a SMS management class which checks for 'unreferenced' datasets older then 999 days and in the brief period that the started task using it was down (right before an ipl which is the only time it comes down), HSM decided to delete the file.
But the question is what does SMS consider to be 'unreferenced' - clearly the file is getting allocated but I am not sure if it is actually opened (this is a vendor product and the file usage may be optional). SMS claimed that the last time the file was 'referenced' was about the time I think that it was created. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ted MacNEIL Sent: Monday, April 20, 2009 2:16 PM To: [email protected] Subject: Re: can SMS managed VSAM file be deleted while allocated >that is what i thought - the job would have had to be down at the time the file was deleted. >Unless there is some weird bug in the system. > thanks Ted You're welcome. Get DAF from the CBT, and run it against the SMF data for the time period in question. That should tell who/when. If it does match up with the job running at the same time, then not only do you have a weird bug, but you have a data integrity problem. But, I strongly doubt it! You should find the culprit, then you can use your favourite form of persuasion to stop them from doing again. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
