Printable View
Hi I am a new member to this group.
I had a question on mainframe testing in my recent interview.
How you submit the batch jobs (Health care claims) in mainframe?
where you check them to see if those are processed with success or failure?
How do you login to Mainframe?(is it through Hyperspace?)
Please provide me the infomation about the batch jobs in Mainframe
Well, since your question sounds basic, i will just explain the most basic answer -
1.Prepare your batch job
2.JEM (utility to check if the job is error free)
3.Once you have zero errors, submit the job using the SUB command
4.Once the job is submitted, use sd;st command to view the spool (shows the status of the jobs) .Verify if each step of the job has been processed as required.
Usually , batch jobs results in file updation , taking backup of files, copying from data files to VSAM files, database updation of certain fields etc. These are carried out by the PROG (program ) which is used in the step of the JCL.You will get a better knowledge of the batch process as you work on an established system
Wow, to answer your question, it would probably take a thesis. I was in a program that took about a year to teach what you want to know.
A batch job begins after you submit it to the internal reader (intrdr). To do this, you can use a TSO SUB, REXEC, FTP, use another job (batch or online) to submit it to the intrdr or trigger some signal that would cause an auto scheduler to submit the job.
Most people simply use SDSF/IOF to check the output of a job. Additionally, the job can download the output to a little PC, send you an email, signal your beeper or text your phone. And these are just a few of the possibilities.
Logging into a mainframe can be done many, many ways. In it's simplest form, you can sign on to a VTAM app using a 3270 green screen.
Other ways include making a java call to REXEC, MQ, CICS, DB2, Websphere, etc. These then interface with RACF to give you a thumbs up or down.
For PC users, think of batch jobs as a BAT/CMD file that runs a series of programs each performing a specific task and passing data to the next program. Given the complexity of your scheduling system, you can kick off other batch jobs as soon as a dataset is created, a certain date/time, an online comes down or a file appears on a little PC.