Though this is a z/VM mailing list, I hope someone will be able to shed some light on this bizarre problem that I have difficulty explaining.
We defined a dataset that I think (!) we perhaps created as a HFS dataset. We did not do anything else (no read or update) with it. We had not set up any ACF2 rules for it. But somehow we are getting ACF2 violations on accesses from USS. When the violations exceeded the limit, USS id was cancelled by ACF2 causing all TCP/IP and USS dependent tasks to abend. We had to re-IPL the LPAR. We had to delete the dataset before re-IPLing for fear of another incident! I am guessing that because we set it up as a HFS (unintentionally), any access by backup jobs or via ISPF was considered as coming from USS. Since the ACF2 rules were not set up, it caused violations and the consequent results. We do not remember if we set it up as a normal or HFS dataset. That evidence is gone. But my theory is that it was set up as HFS with no ACF2 rules and any access to it was considered as coming from USS. This is bizarre. We are splitting hair to find out why and how it happened. Any clues welcome :-) __________________________________________ Ranga Nathan / CSG Systems Programmer - Specialist; Technical Services; BAX Global Inc. Irvine-California Tel: 714-442-7591 Fax: 714-442-2840 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
