Sorry I've been away for a while...

Great Cruise. Ate too much, but then what are you supposed to do ... Great weather. We had a wonderful time.

Now back to CICS... and some DB2

We have had some discussions about adding MORE test CICS regions. We have about 60 or so now. They usually come on pairs. Two distinct application directions. One is primarily VSAM and the other is DB2. One has some Web code, the other doesn't.
Virtually NO MRO, a little function shipping and a little File sharing (VSAM). Just a bit 1980's, without the Web code ... This is the 21st century, isn't it?

Trying to get the developers to think a bit more outside the box is like trying to get a COBOL programmer to write code in Fortran or RPG. So thy don't disrupt any other testing that mey be going on, they want a new set of CICS regions. Taking turns is something they haven't learned yet.

We've had the same problem with DB2 subsystems, but a DASD limitation has curbed those requests, until we get more DASD. On the DB2 side, system testing is requiring a production sized subsystem for their testing. If we didn't have many clients, and the system test was for most everything, that would be possible. But, we have 30+ clients, the systems test is for one of those clients, so one would think the set-up for the system test would be for that client's data, a subset of production, but the system test folks seem to have a problem figuring out what data is whose and rather than taking the time ONCE to figure that out, they ask for pretty much everything. And they wonder why their tests run so long ...

Just wondering how others handle the testing problem...