Re: Mainframe Testing
>> Can anybody tell me about Mainframe testing Our QA uses Rational Functional Tester. See: http://www-03.ibm.com/software/products/en/functional -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Mainframe Testing
Thanks David, I know you folks use it extensively, I'm trying work out what the wider world demand is for training. Would be good to incorporate a reference site or some case studies though if the course eventuates. I'll ping Alan.. On Wed, Jul 13, 2016 at 3:38 PM, David Crayford wrote: > On 13/07/2016 1:29 PM, Wayne Bickerdike wrote: > >> Does anyone on the list use Workload Simulator for testing, load testing, >> regression testing? >> > > Wayne, > > You might want to ping your old landlord Alan offline. He's our expert on > the floor. He's globe trotting around Europe with > his family at the mo. > > > I've been asked to possibly run a course and develop coursework on WSIM. >> >> Since IBM outsourced all their training, it appears that this one isn't >> covered. >> >> Was there ever a formal training course for this product? >> >> On Tue, Feb 7, 2012 at 11:10 AM, Mitch wrote: >> >> Folks: >>> >>> What you want is an automated tool that can modify the batch executables >>> "on the fly" for each environment. If you have a change control tool >>> like >>> ISPW, SYSChange, Endevor or ChangeMan, it is pretty straightforward to >>> set >>> up rules through an automated JCL management tool such as J-Man from >>> Visiant Arcares (www.visiantarcares.com). Through an easy to define set >>> of rules, the user can cause the batch processes (even the automated >>> updating of the scheduling nets when moving to production) to mirror the >>> appropriate libraries, naming conventions, test environments, etc. And, >>> as >>> Chris says, "what ever runs in production, you're going to need a copy of >>> it in testing." This can also be automated if you have one of the change >>> tools described above and the appropriate JCL management solutions, such >>> as >>> J-Man. >>> >>> Chris, this could be a way to multiply yourself!:o) >>> >>> >>> Mitch >>> >>> >>> >>> -Original Message- >>> From: Cris Hernandez #9 >>> To: IBM-MAIN >>> Sent: Mon, Feb 6, 2012 2:29 pm >>> Subject: Re: Mainframe Testing >>> >>> >>> well, whatever runs in production, you're going to need a copy of it in >>> esting. >>> sually means a lot of batch and then testing the onlines/applications' >>> user >>> ccess. >>> found it always helped to keep a testbed of data for batch/db's, then >>> write an >>> utomated batch job scheduler that edits all the JCL and control cards so >>> that >>> hey point to testing libraries/files instead of production, plus remove >>> all the >>> roc steps that you don't want to run (emails, data xfers, etc.). >>> adly, there aren't enough of me to go around... >>> >>> -- On Sun, 2/5/12, Mohd Rizwan wrote: >>> From: Mohd Rizwan >>> ubject: Mainframe Testing >>> o: ibm-m...@bama.ua.edu >>> ate: Sunday, February 5, 2012, 11:47 PM >>> Hi Friends, >>> Can anybody tell me about Mainframe testing, what are the tools are used >>> or Mainframe system testing >>> -- >>> Mohd Rizwan >>> 538451750* >>> -- >>> or IBM-MAIN subscribe / signoff / archive access instructions, >>> end email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >>> -- >>> or IBM-MAIN subscribe / signoff / archive access instructions, >>> end email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >>> >>> >>> -- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN >>> >>> >> >> > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Mainframe Testing
On 13/07/2016 1:29 PM, Wayne Bickerdike wrote: Does anyone on the list use Workload Simulator for testing, load testing, regression testing? Wayne, You might want to ping your old landlord Alan offline. He's our expert on the floor. He's globe trotting around Europe with his family at the mo. I've been asked to possibly run a course and develop coursework on WSIM. Since IBM outsourced all their training, it appears that this one isn't covered. Was there ever a formal training course for this product? On Tue, Feb 7, 2012 at 11:10 AM, Mitch wrote: Folks: What you want is an automated tool that can modify the batch executables "on the fly" for each environment. If you have a change control tool like ISPW, SYSChange, Endevor or ChangeMan, it is pretty straightforward to set up rules through an automated JCL management tool such as J-Man from Visiant Arcares (www.visiantarcares.com). Through an easy to define set of rules, the user can cause the batch processes (even the automated updating of the scheduling nets when moving to production) to mirror the appropriate libraries, naming conventions, test environments, etc. And, as Chris says, "what ever runs in production, you're going to need a copy of it in testing." This can also be automated if you have one of the change tools described above and the appropriate JCL management solutions, such as J-Man. Chris, this could be a way to multiply yourself!:o) Mitch -Original Message- From: Cris Hernandez #9 To: IBM-MAIN Sent: Mon, Feb 6, 2012 2:29 pm Subject: Re: Mainframe Testing well, whatever runs in production, you're going to need a copy of it in esting. sually means a lot of batch and then testing the onlines/applications' user ccess. found it always helped to keep a testbed of data for batch/db's, then write an utomated batch job scheduler that edits all the JCL and control cards so that hey point to testing libraries/files instead of production, plus remove all the roc steps that you don't want to run (emails, data xfers, etc.). adly, there aren't enough of me to go around... -- On Sun, 2/5/12, Mohd Rizwan wrote: From: Mohd Rizwan ubject: Mainframe Testing o: ibm-m...@bama.ua.edu ate: Sunday, February 5, 2012, 11:47 PM Hi Friends, Can anybody tell me about Mainframe testing, what are the tools are used or Mainframe system testing -- Mohd Rizwan 538451750* -- or IBM-MAIN subscribe / signoff / archive access instructions, end email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- or IBM-MAIN subscribe / signoff / archive access instructions, end email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Mainframe Testing
Does anyone on the list use Workload Simulator for testing, load testing, regression testing? I've been asked to possibly run a course and develop coursework on WSIM. Since IBM outsourced all their training, it appears that this one isn't covered. Was there ever a formal training course for this product? On Tue, Feb 7, 2012 at 11:10 AM, Mitch wrote: > Folks: > > What you want is an automated tool that can modify the batch executables > "on the fly" for each environment. If you have a change control tool like > ISPW, SYSChange, Endevor or ChangeMan, it is pretty straightforward to set > up rules through an automated JCL management tool such as J-Man from > Visiant Arcares (www.visiantarcares.com). Through an easy to define set > of rules, the user can cause the batch processes (even the automated > updating of the scheduling nets when moving to production) to mirror the > appropriate libraries, naming conventions, test environments, etc. And, as > Chris says, "what ever runs in production, you're going to need a copy of > it in testing." This can also be automated if you have one of the change > tools described above and the appropriate JCL management solutions, such as > J-Man. > > Chris, this could be a way to multiply yourself!:o) > > > Mitch > > > > -Original Message----- > From: Cris Hernandez #9 > To: IBM-MAIN > Sent: Mon, Feb 6, 2012 2:29 pm > Subject: Re: Mainframe Testing > > > well, whatever runs in production, you're going to need a copy of it in > esting. > sually means a lot of batch and then testing the onlines/applications' user > ccess. > found it always helped to keep a testbed of data for batch/db's, then > write an > utomated batch job scheduler that edits all the JCL and control cards so > that > hey point to testing libraries/files instead of production, plus remove > all the > roc steps that you don't want to run (emails, data xfers, etc.). > adly, there aren't enough of me to go around... > > -- On Sun, 2/5/12, Mohd Rizwan wrote: > From: Mohd Rizwan > ubject: Mainframe Testing > o: ibm-m...@bama.ua.edu > ate: Sunday, February 5, 2012, 11:47 PM > Hi Friends, > Can anybody tell me about Mainframe testing, what are the tools are used > or Mainframe system testing > -- > Mohd Rizwan > 538451750* > -- > or IBM-MAIN subscribe / signoff / archive access instructions, > end email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > -- > or IBM-MAIN subscribe / signoff / archive access instructions, > end email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
