You are on page 1of 7

1.how can u track a TICKET? What is the Ticket Tracking mechanism ? 2.What is SCHEDULAR? 3.

How can u copy a particular member ,from production region to test region? 4. What is the option in ISPF menu for TOOLS? 5. What will happen when executing an embedded SQL program, without performing BIND? 6. GDG concatenation for FIXED length and Variable length? 7. Why we should not use GOTO statement? 8.A record which was created before 2 years of period has to be deleted from a database table on by checking each and every month? how u will code that JCL/ while before deleting u have to take a back up copy of that table?

9.What is unit testing? 10. how you will plan a unit testing? how wll finialize that your program has been finished succesfully? 11. what is analysis? Give the description to have? 12. how will place ur program in ENDEVOR? 13.what real time abends that u faced regarding CICS? 14.how will set break point with XPEDITOR? 15. what are the different phases in LIFE CYCLE? 16. how will make work reques plan(WRP) and Quality Reports?

2.What is SCHEDULAR? Schedular organized the batch job flow. /* I can write more about this but there are too many questions */ 3. How can u copy a particular member ,from production region to test region? Using Endevor/ Panvalet ??? 5. What will happen when executing an embedded SQL program, without performing BIND? Job will abend 7. Why we should not use GOTO statement? You can use GO TO statements, if you can keep track of branching 13.what real time abends that u faced regarding CICS? what ?????? 8.A record which was created before 2 years of period has to be deleted from a database table on by checking each and every month? Write a Delete Sql 14.how will set break point with XPEDITOR? Type BR on the line you want a break

http://www.scenariotester.com/st/static/overview.asp http://www.scribd.com/doc/88359621/Mainframe-230 http://motevich.blogspot.in/2008/04/how-to-run-qtp-test-from-command-line.html http://mainframethebigiron.blogspot.in/2011/12/xpeditor-how-to-debug-programs.html

Mainframe Performance Tester Resume Everyone who plans for a job needs to have a plan that works out properly. This mainframe performance tester resume example opens new ideas of framing a unique resume that works positively in the job application procedures. It starts in a formal introduction of personal details with clear statement of career goals, credentials, education, and work experience. If you're just starting to write, this resume example is the perfect example you can start with. It can help you in identifying, structuring, and organizing the information that leads you towards success. You can hope to expand your job search with this sample resume. Feel free to examine and refer the sections provided in this sample. A mainframe performance tester is a software tester who performs of mainframe by using Load Runner and stress testing techniques. The roles and responsibilities of a mainframe performance tester include developing complete life cycle of testing mainframe performance, testing mainframe performance capacity, preparing test plans, executing test plans, analyzing mainframe performance, Load Runner test scripting , and preparing test results. It is mandatory for a mainframe performance tester to have sound knowledge of mainframe performance testing concepts, building automation test scripts, software development life cycle, and mainframe performance testing tools. Mainframe Performance Tester Resume Example Eugene Walter One Washington Square, San Jose, California 95192 Cell: (333)-021-3354 email: walter@example.com Career Goal: Well versed in online transaction processing, batch processing, and Database server with hands on experience in testing mainframe performance by using standard tools. Seeking an opportunity to work as a mainframe performance tester in a renowned organization Summary of Knowledge:

More than three years of professional experience in testing mainframe system application and performance Extensive knowledge of testing mainframe systems, mainframe tools, and mainframe testing environments Comprehensive knowledge of software testing, User Acceptance Testing, and mainframe development In-depth knowledge of system integration, defect tracking, test validation, and test planning

Excellent technical, analytical, troubleshooting and communication skills Ability to work cooperatively in a team environment and in a fast paced and dynamic environment

Professional Work History: Organization: Amgen Technology, California Duration: January 2010 till date Designation: Mainframe Performance Tester

Responsible for developing test plans, strategies, scenarios and perform execution of test cases Handle the tasks of preparing test cases and defect tracking of mainframe systems Perform responsibilities of implementing testing cycles by coordinating with testing leads Responsible for investigating and logging defects and provide solution of the same by consulting with software developers Assigned responsibilities of running Mainframe Schedules to test and record mainframe performance Handle the tasks of developing mainframe performance testing life cycle and formulate test plans

Organization: ABX International Group, California Duration: August 2008 to December 2009 Designation: Junior Mainframe Performance Tester

Handled responsibilities of evaluating test results to determine the defect in performance of mainframe systems Assigned the tasks of performing parallel testing by using Mercury Quality Center tools Performed responsibilities of preparing test cases and test scripts under the guidelines of senior staff Responsible for troubleshooting mainframe performance testing environment issues and participated in test planning Handled the tasks of identifying and extracting data from tables required for test execution Performed responsibilities of preparing and maintaining testing reports

Educational Summary: Achieved Bachelor's degree of Science in Computer Science San Jose State University, California in the year 2008 Reference: Will be pleased to furnish upon request

Job applicants write resume to get an interview. The information presented should match with the requirement of the opening or position. This mainframe performance tester resume example will help you to learn more on the skills sets, educational qualifications, and job responsibilities required for the position. A number of resume sample are provided on line. This one will work in the best way. You can make yourself as the best applicant by reviewing the sample and writing in the same style and pattern. It will help you to understand what effective resume is all about and what advantages you will gain by sending a unique resume. What is a mainframe? Mainframe is a high performance multi user computer system which is most scalable, available,reliable and secured machine in the world capable of performing some Million Instructions per second(upto 569,632 MIPS) with the following characteristics: Reliable single-thread performance, which is essential for reasonable operations against adatabase. Maximum I/O connectivity, which means mainframes excel at providing for huge disk farms. Maximum I/O bandwidth, so connections between drives and processors have few choke points. Reliabilitymainframes often allow for "graceful degradation" and service while the system isrunning. Factors contributing to mainframe use The reasons for mainframe use are many, but most generally fall into one or moreof the following categories: y _ Reliability, availability, and serviceability y _ Security y _ Scalabilty y _ Continuing compatibility y _ Evolving architecture Now we come to our main point of discussion mainframe testing. Mainframe Testing Mainframe Testing is similar to client-server applications testing , but you have to know how tooperate basic TSO and ISPF commands and menus, view

mainframe files, look at and useSDSF or other output tool, log on CICS and transactions, use FTP or another transfer protocol,submit the batch job - it's for QA testing of mainframe applications.And plus, QA testing for another platform, like WEB and/or client-service, since the mainframe is usually back-end.It can be learned pretty quickly, but it needs an access to mainframe .There are various kind of tests : integration tests, performance tests, volume tests, regressiontests, stress tests etcYou can test a all cluster of programs or a whole day or night of production. You need to knowthe expected results, discuss with business analysts, with system team, with Capacity team, . And you will have to know a lot of tools or technic : Strobe, File Aid, Ecomp, CA7, report Excel,Word, DB2, CICS, zOS, Sort, backup, recovery, etc.As part of mainframe testing you could be testing a COBOL application on a DB2 database, or aPeoplesoft application using an Oracle database, or the application could be a CICS applicationusing QA Hyperstation to automate the testing. The QA principles do not change, however theskillsets differ to some extent. You may be required to know JCL, ISPF and TSO and have a basic understanding of COBOL. You should know how to write SQL queries to test anydatabases. There may also be networking issues to consider when testing large systemenvironments. Mainframe applications run on the mainframe and clients access the mainframe through aterminal emulator. The terminal emulator is the only software that needs to sit on the clientmachine. Changes to the software (COBOL, JCL, etc) are made on the mainframe and as amainframe tester you don't need to worry about migrating them to the client. If it works throughone terminal emulator it should work on them all. Client/Server Testing Vs Mainframe Testing Client/server architecture allows some of the processing to be done by the client. However, sincethere is code to ship to the client, you have to worry about the code being installed properly,working on their OS, playing well with the other applications on the desktop, security, and performance. Inside a company, you probably know the number of users, types of environments(OS, RAM, connection speed), so it's not as extensive as web testing, but it has more variablesthan mainframe testing. Also, while usability should not be ignored on mainframe applications, itseems to be more of an issue with client/server applications since they also generally have GUIs. Mainframe Test Tools Some of the tools that are used for mainframe testing are as follows:1. Test Director 2. QTP (Quick Test Professional)3. Claim Repository4. Foundation Testing Tool (FTT)5. TN3270 Plus6. Hiperstation7. Load Runner Skill set specific to mainframe testing 1. COBOL2. DB23. JCL4. CICS

5. Assembler 6. VSAM7. ISPF/TPF

You might also like