You, like the name for the Sun, are SOL. We actually had something like this happen to us. A vendor supplied a CICS system level product to us. It worked fine in Test and Model Office. When I installed it in Production, it consistently brought the region down. This was due to the fact that our production CICS was significantly more active and DSA was always nearly 100% allocated. They couldn't reproduce. I reproduced the problem and even wrote a patch to fix it (they gave us source). It was a random 4 byte memory overlay due to a race condition. My work with their developer resolved the problem and got us a year's free maintenance.
On Wed, Jan 30, 2013 at 1:14 PM, Joel C. Ewing <[email protected]> wrote: <snip> > From the RD&T reference cited: > 'The Program may not be used to run production workloads of any kind, nor > more robust development workloads including without limitation production > module builds, pre-production testing, stress testing, or performance > testing." > > So neither zPDT nor RD&T may be used for any production workload, or even a > workload that attempts to emulate a production workload. Sounds too > restrictive to me - how could you legally debug and fix application > problems that only show up under stress if you are a developer and this is > your only z/OS machine? > > -- > Joel C. Ewing, Bentonville, AR [email protected] > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN -- Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
