2009/5/11 Tom Marchant <[email protected]>: > On Sat, 9 May 2009 16:35:58 -0400, Tony Harminc wrote:
>>.... Keep in mind that in many cases the attributes can change >>between the time you check, and the time you (or some service or >>program you call) actually uses the storage. > > And Binyamin made a similar comment. > > What do you mean by this? If you determine that an address is in CSA, it > will continue to be a CSA address. Of course, that location could no longer > be allocated to the same address space, or indeed any address space. In > addition, the location could have been converted to SQA, I suppose, or have > been used to hold a dynamic LPA module. Is that what you are talking about? Those, and quite probably other things that neither of us has thought about. I made my comment with respect to security checking. In his initial post, Joe Reichman said he wanted "to determine its nature e.g. CSA SQA etc.....", and so clearly the CSA vs SQA difference was just an example. There are various reasons why a program might want to know this sort of thing about an address, and one of them is a usually ill considered attempt to base some sort of security checking on it. I just reissued a standard warning that's been around since IBM's first Statement of MVS System Integrity in 1974 or so. Tony H. ---------------------------------------------------------------------- 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
