Testing in DB2

Michael Bancale

Testing in DB2
We have been a mostly VSAM shop for a really long time. We have moved some
small and medium systems to DB2 by rewriting them. We recently put what I
am considering a large application to DB2. This application now shares some
data with two other applications. In the testing environment the two areas
were having some difficulties testing because the common table was needed on
way for one team and another way for the other team. We are now beginning
work on a large system which will share data between even more systems. In
the past if a programmer wanted to test all they had to do is create their
own VSAM files and begin their testing. We have several CICS test regions
which would allow multiple programmers to test with different data. I think
the old way of doing things is gone now but I need to come up with a viable
options for allowing multiple teams to test with their own data when needed.
At this time the main way I would do this is to have several copies of the
database with different DB, TS and owner names.

Any comments or suggestions?

Thanks,


Michael Bancale
[login to unmask email]
Texas Farm Bureau Insurance Company
www.txfb-ins.com
Waco, Texas



[login to unmask email]

Re: Testing in DB2
(in response to Michael Bancale)
Hi,

One suggestion to consider is to add a column to the tables
(like 'OPER_ID') and create views on the tables as SELECT *
FROM tab WHERE OPER_ID=USER WITH CHECK OPTION. As data is
added to the tables you can populate the OPER_ID field as
necessary. Programmers would then only see and manipulate
their own data and not step on others. LOADs would still
have to be coordinated.

Regards,

Michael Levine
Premier Data Services, Inc.


>We have been a mostly VSAM shop for a really long time. We have moved some
>small and medium systems to DB2 by rewriting them. We recently put what I
>am considering a large application to DB2. This application now shares some
>data with two other applications. In the testing environment the two areas
>were having some difficulties testing because the common table was needed on
>way for one team and another way for the other team. We are now beginning
>work on a large system which will share data between even more systems. In
>the past if a programmer wanted to test all they had to do is create their
>own VSAM files and begin their testing. We have several CICS test regions
>which would allow multiple programmers to test with different data. I think
>the old way of doing things is gone now but I need to come up with a viable
>options for allowing multiple teams to test with their own data when needed.
>At this time the main way I would do this is to have several copies of the
>database with different DB, TS and owner names.
>
>Any comments or suggestions?
>
>Thanks,
>
>
>Michael Bancale
>[login to unmask email]
>Texas Farm Bureau Insurance Company
>www.txfb-ins.com
>Waco, Texas
>
>
>


>
>