Sorry for unclear requirements. I mean that our team had developed some small tools and needs to testing on several different environments.
We have no ideas on conduct testing environment. So i can not give you the detailed description about our requirement.
If you could send me uesful materials or references on Mainframe environment setting. I am looking forward to your feedback.
I think that we need to break the tools so that get the designment and development completely. Testing is done for detecting the errors as completely as possible. i gained another way of consider the requirement from your points. thanks expat.
I wish you could send me materials that related to management of MF system or how to initial new environment. i am appreciate for your response coming soon.
Joined: 14 Mar 2007 Posts: 8593 Location: Back in jolly old England
Unfortunately I do not have material to send.
When you talk of an environment what exactly do you mean ? A mirror image of production as was used for our acceptance test environment.
We used to take full application dumps of production and restore to acceptance over a weekend to ensure that the acceptance environment was as close as possible to production. Obviously these days you have SNAPSHOT / FLASHCOPY / TDMF / SRDF / PPRC ad infinitum to replicate DASD.
Joined: 06 Jun 2008 Posts: 8165 Location: East Dubuque, Illinois, USA
There is no such thing in general terms as "mainframe environment". There can be testing in batch, testing in online (CICS, IMS, or other), testing in TSO, testing in Unix System Services, but you cannot just state you want to test in a mainframe environment. Hence there is no way we can provide you with any assistance.
Strictly speaking, I just want a tesing environment used to testing small tools in batch. Due to lack of environment knowledges, I am still in learning of MVS, the site i worked is conducted for development. I am not sure the different between development environment and tesing evn, and so on. firstly, i need gain clear understanding of different environment.
Many thanks for your help. I am glad to exchange with you all.
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
I am not sure the different between development environment and tesing evn, and so on.
These are labels that are created/defined locally. They are completely site-specific.
In some organizations the "test" environment is where programmers work, in others it is where system (rather than unit) testing is done. In some, it is where new releases of software products are initially installed for verification/validation.
At each site you join, you will need to learn the local terminology.
I haven't been anywhere yet that allows individuals to define an entire lpar for their testing of "small tools in batch". People run these tests from "their own" or custom product libraries.
Keep in mind that the mainframe is a far more collaborative effort than spending a couple of hundred dollars for an Intel box and installing the operating system from shrink-wrapped Microsoft software
It all depends on what your tools need to access and how you need that configured. For example, do you need a database? If so, there are many choices; DB2, Oracle, MySQL, a home grown system, a set of data sets, etc.
Do you need a transaction processing system? There is CICS, IMS, Application servers and several more IBM and non-IBM systems.
Do you need a runtime environment for the language you are using? There is Language Environment (LE), Java virtual machines, Unix services, TSO services, Rexx libraries, CICS libraries, etc
And there is Security: ACF/2, RACF, Top Secret...
And performance configuration: WLM
And communications: TCP/IP, Terminal emulation, etc
Resetting all of these in a test environment for reproducable results can be as simple as emptying some data sets or as difficult as reinitializing set of network attached load balanced application servers with predefined test data, configurations, security, tuning, error recovery, etc, etc, etc.
There are literally thousands of combinations of software that your tools might need. Or the tools may need only Rexx and a PDS or two.
I've made it sound much more complicated than it really is, but only to say that you need to understand specifically what the system you are testing need to run.