<<<We had an issue a couple of years ago where OEMs were using the services (I believe IGWASMS) to determine if a data set is SMS-managed.>>>
Thanks for the reply Mark. I don't think that is the case. I've been running the Module Fetch Montitor (Peter Relson's utility) all day and I've only seen one LOAD of IGWASMS, and that seemed to coincide with an SB37 abend. <<<They are not temporary data sets. They are real data sets, with names deliberately chosen to merely *look* like temporary data sets. As permanent data sets, MVS processing deals with them just like any other permanent data set. I cannot remember exactly why at the moment, but that's how CA-Endevor works.>>> Thanks Brian for that reply. I hope that is not the case, otherwise I won't be able to change those *temporary data sets* to use VIO if they are only temporary in name. I now don't understand the SVC 26 request unless it is simply a query, altough the PLIST looked to me as if it was trying a DEFINE. Also, if it was trying to catalog the dataset I would have expected security violations for update attempts to the master catalog which I'm not seeing. Additionally, it is an SMS requirement for permanent datasets that they be catalogued, so I'm not able to put all the pieces of the puzzle together yet. Tom ---------------------------------------------------------------------- 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
