Basic Framework of JCL

/name	JOB	parameters...
//name	EXEC	parameters...
//name	DD	parameters...

Each of this JCL Statements have a label – a symbolic name assigned to them. Its like naming kids. Well, there could be so many boys in your area, but how do distinguish them? Of course, by their names.

In the same way, a JCL may contain a bunch of DD Statements, one for Input file, one for the output file, one for the error file. How do you tell them apart, by naming them. As a good practice, we always give names to all our JCL Statements. Names kinda help you to refer back to these statements in the future. You want to point out a particular JCL Statement to your friend, just spell out its name.

But, notice carefully, each label(name) is preceded with two slashes //. The two slashes are a JCL Statement’s signature. They indicate that the statement is a JCL Statement(one of JOB, EXEC, DD). Every JCL Statement wear the two slashes //. A naked statement without // won’t be treated as a JCL Statement.

Now, every JOB, EXEC and DD Statement has got these whole lot of parameters. What you’ll be learning throughout these tutorials is mostly the parameters. Parameters add stuff and meaning to the JCL Statement. 

Now, let me give you a booster, that’s going to help you organise the way you think about this JCL.

- JCL is made up of mainly JOB, EXEC and DD.
- JOB is easy to learn and use.
- EXEC is easy and fun to use.
- DD Statements take three forms
   1. DD Statements to read a file.(easy)
   2. DD Statements to write to the logs.(easy)
   3. DD Statements to create a new file(hard!); you’d have to learn parameters such as DISP, UNIT, DCB, SPACE and several others to code this.

Have a good look at this chart :

IBM Mainframe Tutorials - JCL DB2 COBOL CICS

Here you can find

• Links to JCL Tutorials, DB2 tutorials, SQL tutorials, COBOL tutorials, VSAM tutorials, XPEDITER tutorials, FILE-AID tutorials.
• Links to DB2 Inteview Questions, COBOL Interview questions, JCL interview questions, CICS interview questions, VSAM interview questions.
• You can also find links to IBMMAINFRAME Forums, COBOL forums, DB2 forums, CICS forums, VSAM forums, REXX forums, JCL forums, DFSORT forums, ICETOOL forums, EASYTRIEVE forums, IMS DB forums, IMS DC forums, XML forums, Mainframe Jobs forums, Interview questions forums.

IBM Mainframes Certification

To achieve challenging position in Software field, where my analytical and problem solving skills can put in for the successful completion of the project and the growth of the organization, which is in turn my growth and development.
Personal traits: Dedicated, Consistent positive notions, ability to work in groups, analytical and innovative skills. Good communication skill, Reasoning ability and smart working.

Software Exposure
IBM Mainframes : JCL, VSAM, COBOL, DB2, CICS, IMS
Languages : C, C++, HTML
Operating System : MS-DOS, Windows 9x, 2000, XP, UNIX
Package : MS –Office XP

Certification:
IBM Mainframes Certification from Hinduja TMT Ltd, Bangalore.

Project Profile:
ATM Transaction Management System
Module handled : Account information provider
Software : IBM Mainframes
Operating System : MVS, Z/OS - 390
Host Language : COBOL
Compiler : JCL
RDBMS/Backend : DB2
Description: This module will access the master database and generate the respective account information for those accounts with correctly entered passwords. It will generate various screens relevant to each transaction .Screens involved in this module designed using CICS and COBOL is used as host language. The database consists accounting information of customer like name, address, account number, password, amount deposited, retrieved. Once the password entered matches, this module will display account information.If, not the necessary instructions containing screen to proceed will comes into picture.

Basic Framework of Job Control Language-JCL

My head’s spinning around the 3 JCL Statements : JOB, EXEC and DD. Could you tell me something more about them?
So, you’ve got the gist of the concept behind JCL, all the JCL that you going to write from hereon, maybe for the next 10-20 years, would be composed of three main statements :

//name	JOB	parameters...
//name	EXEC	parameters...
//name	DD	parameters..

Each of this JCL Statements have a label – a symbolic name assigned to them. Its like naming kids. Well, there could be so many boys in your area, but how do distinguish them? Of course, by their names.


In the same way, a JCL may contain a bunch of DD Statements, one for Input file, one for the output file, one for the error file. How do you tell them apart, by naming them. As a good practice, we always give names to all our JCL Statements. Names kinda help you to refer back to these statements in the future. You want to point out a particular JCL Statement to your friend, just spell out its name.

But, notice carefully, each label(name) is preceded with two slashes //. The two slashes are a JCL Statement’s signature. They indicate that the statement is a JCL Statement(one of JOB, EXEC, DD). Every JCL Statement wear the two slashes //. A naked statement without // won’t be treated as a JCL Statement.

Now, every JOB, EXEC and DD Statement has got these whole lot of parameters. What you’ll be learning throughout these tutorials is mostly the parameters. Parameters add stuff and meaning to the JCL Statement.

Now, let me give you a booster, that’s going to help you organise the way you think about this JCL.

JCL is made up of mainly JOB, EXEC and DD.
- JOB is easy to learn and use.
- EXEC is easy and fun to use.
- DD Statements take three forms
   1. DD Statements to read a file.(easy)
   2. DD Statements to write to the logs.(easy)
   3. DD Statements to create a new file(hard!); you’d have to learn parameters such as DISP, UNIT, DCB, SPACE and several others to code this.

Have a good look at this chart :

How can you pass values from COBOL program to non-COBOL programs

If u want to pass values from jcl to cobol use "parm" parameter in the exec statement and in the cobol program declare the linkage section for the values to be passed.If u want to pass values from cobol to other non-cobol programs this can be done by call by reference or call by value.ex: call pgma using ws-name, ws-sex.