>Not only that, but CICS is developed--and I assume tested--in Hursley. I >suspect they, as well as Bvblingen, San Jose, Rochester, Perth, Raleigh, >Rome and other labs play from a different "rule book" than do the folks >in POK.
Not really different in this regard. The word about dirty getmain was propagated to every system test organization within IBM z, and it is expected that they use it (sometimes they'll use it periodically -- it is a fact that dirty getmain has on occasion hidden a problem that running without dirty getmain would have encountered). Our standard position with respect to ISVs is that if they encounter an IBM problem due to their use of dirty getmain, we will try to fix it. The CICS situation that Jim Mulder mentioned is, I hope, more the exception than the rule. Clearly if problems do not get fixed, then you will be turning off dirty getmain as you can't do your own work if on an unstable system, and thus not getting any of the testing benefit that dirty getmain can provide. Please note also that dirty getmain does not try to be omniscient. It is a fact (but not a documented promise) that the first getmain done under a job for a user-region subpool will get 0's, simply because of the "free region" done between jobs. Dirty getmain may not note that and may "dirty it". A program that relied on that behavior would technically be "correct" but would not work with dirty getmain active. We tend to try to remove that reliance just so that other programs can use dirty getmain, We want the system to be usable with dirty getmain active, we just cannot guarantee it. If there were the notion of "here is something for your sandbox system, please let us know if you find some problem, but we cannot promise to take an APAR to fix it", is that something that would work for you? Many of the DIAGxx traps would fall into that categorization. This notion is, sort of, the "agreement" we have with the ISVs. I'm not speaking legal-ese because I don't know how. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
