well, whatever runs in production, you're going to need a copy of it in testing. usually means a lot of batch and then testing the onlines/applications' user access. I found it always helped to keep a testbed of data for batch/db's, then write an automated batch job scheduler that edits all the JCL and control cards so that they point to testing libraries/files instead of production, plus remove all the proc steps that you don't want to run (emails, data xfers, etc.). Sadly, there aren't enough of me to go around...
--- On Sun, 2/5/12, Mohd Rizwan <[email protected]> wrote: From: Mohd Rizwan <[email protected]> Subject: Mainframe Testing To: [email protected] Date: Sunday, February 5, 2012, 11:47 PM Hi Friends, Can anybody tell me about Mainframe testing, what are the tools are used for Mainframe system testing -- *Mohd Rizwan 9538451750* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
