Scribd
Upload
18 views5 pages

COBOL Class 01 - Introduction To COBOL6

Class 6

Uploaded by

nows108
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
18 views5 pages

COBOL Class 01 - Introduction To COBOL6

Class 6

Uploaded by

nows108
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 5

COBOL (Common Business Oriented Language) – 12-15 sessions

-----
Intro COBOL Program Structure - Division, Section & Paragraph

Variable Declarations - Level Numbers, PIC clause,


Data types & Size
Input-Output & Arithmetic - VALUE CLAUSE, Accept &
Display - Compute
Data Movement Verbs - Simple Move, Move with Of
clause, Group Move & CORR
Conditional Statements - IF & Evaluate Statement –
Continue & Next Sentence
Control Sequence Verbs - Perform ,STOP RUN, GOBACK,
EXIT, EXIT PROGRAM, GOTO
File Handling - OPEN, READ, WRITE, REWRITE,
DELETE & CLOSE
Memory Saving - Usage Clause, 88 Level
Number, Redefines & Renames 66 LEVEL
Array-Occurs table - Search & Search All - PERFORM
VARYING
Sub-Program - CALL Statement
(Static & Dynamic Call)
String Handling Verbs - String, Unstring, Inspect &
Referential
===================================================================================
==========================
Introduction to COBOL
-----------------
MAINFRAME --> IT IS A BIG COMPUTER -> USED FOR DATA 1. STORE & 2. PROCESSING

PROCESSING -> 1. BATCH PROCESS 2. ONLINE PROCESSING

1. BUSINESS LOGIC -> COBOL.

COBOL -> WE CANNOT DEVELOPER ANY SOFTWARE


-> WE CAN CODE BUSINESS LOGIC -> TO MAINTAIN THE APPLICATION

COBOL -> VERY EASY


-> MOSTLY ENGLISH

--> PGM ARE LENGTHY -> SMALL LOGIC PGM --> 300 LINES OF CODE

==> IF AM INTO MAINFRAME -APPLICATION

2 THINGS -> 1. AS A DEVELOPER -> WE NEED TO KNOW HOW TO CODE THE


PGM -> FALL INTO A DEVELOPER PROJECT
2. AS A ANALSYST/SUPT ROLE --> 1. ALONG WITH THE
CODING THE PGM 2. HOW TO ANALYSIS OF THE PGM
==>
HOW TO CODE A COBOL PGM** :-

PGM FORMAT: DIVISION.


SECTION.
PARAGRAPHS
STATEMENT. --> COMMAND/INSTRUTION TO
SYSTEM -HOW TO PROCESS THE DATA.

DIVISION -> 4 DIVISION


1. IDENTIFICATION DIVISION. (ID DIVISION)
2. ENVIRONMENT DIVISION
--OPTIONAL
3. DATA DIVISION.
--OPTIONAL
4. PROCEDURE DIVISION.

>> ID DIVISION: USED TO PROVIDE THE IN-PROG DOCUMENTATION DETAILS.


-> WE HAVE ONLY PARAGRAPHS..
-> OUT OF THESE 6 PARA -> ONLY PROGRAM-ID IS
REQUIRED.
-> PROJECT PROG -> PROGRAM-ID - AUTHOR & DATE-
WRITTEN.

ID DIVISION.
PROGRAM-ID. NAME-OF-PGM.
AUTHOR. UR NAME.
DATE-WRITTEN. TODAY-DATE.
DATE-COMPILED. TODAY-DATE.
INSTALLTION. APPLICATION-NAME.
SECURITY. WARNING MESSAGE.

PGM NAME -> 8 CHAR (ALP-NUM) --> EX: ANILPGM1 ANILPGM2 , TESTPGM1 , TESTPGM2
--> VALID NAME?? NOT VALID..

PROJECT => APPLICATION -A --> Z1YE* -> Z1YE0001 - Z1YE9999


-> NEW PROJECT PROGRAM -> Z1YE**
APPLICATION -B --> Z1YN* -> Z1YN0001 - Z1YN9999

>> ENVIRONMENT DIVISION:- USED TO DEFINE THE REQUIRED FILE IN THE PGM** OF
BATCH APPLICATION (FOR ONLINE - NO NEED)

DATA-STORE-.FILE/TABLE -> PROCESS-GET THE DATA (COBOL - LOGIC +CAL -SEND) ->
FILE/TABLE.

ENVIRONMENT DIVISION.
INPUT-OUTPUT SECTION.
FILE-CONTROL.
DEFINE THE ALL FILE (INPUT - OUTPUT)

== COBOL PGM TYPES == == IS ENV DIVISION


REQUIRED.? (YES/NO)
===
1. ONLY COBOL
NO
2. COBOL + FILE
YES
3. COBOL + DB2
NO
4. COBOL + DB2 + FILE
YES
-----------------------------------------------------------------
---------------------ONLINE PGM - NO ENV REQUIRED.
5. COBOL + CICS
NO
6. COBOL + CICS +FILE
NO -- NOT REQUIRED --> FCT - FILE CONTROL TABLE
7. COBOL + CICS + DB2
NO
8. COBOL + CICS + FILE + DB2
NO -- NOT REQUIRED

>> DATA DIVISION:- => USED TO DEFINE ALL VARIABLE REQUIRED IN THE PGM
----

VARIABLE:- TEMP MEMORY SPACE ALLOCATED IN THE PGM - TO STORE AND PROCESS
THE DATA
-> SCOPE/LIFE OF A VAIBRALE -> TILL THE END OF PGM.
=> UR PGM COMPLETED -> VARIABLE MEMORY -
> DELETED.
-> WHY I NEED A VAIABLE??

DATA (FILE/DB2) -> GET DATA INTO PGM (COBOL - MEMORY?? HOLD THAT -> DEFINE
MEMORY -VARIABLE + PROCESS ) -> SEND -> FILE/TABLE
--
A1111,ANIL,5000 < DEPOSIT -2000 ACCT-NUM,CUST-NAME,ACCT-BAL,
DEP-AMT << VARIABLE

ACCT-BAL + DEP-AMT << PROCESS ==> A1111,ANIL,7000

==== SHOPPING IN SUPER MARKET


====

SUPER MARKET
HOME
ITEM -HERE STORED ===> BAG'S / COVER / -CARD BOX ===========>
ITEM (FREE/CONT/USE)

DATA DIVISION.
FILE SECTION. -> FILE VARIBALE.
WORKING-STORAGE SECTION. -> DEVELOPER VARIBALE ->
USE FOR BUILDING LOGIC + DB2
LINKAGE SECTION. -> DIFF STYLE -> LINKING
VARIABLE

>> PROCEDURE DIVISION:


>> USED TO CODE ALL BUSINESS LOGIC
>> WE DONT HAVE PRE- DEFINED SECTION / PARAGRAPHS.
>> WE AS DEVELOPER WE CAN CODE OUR OWN SECTION/PARAGRAPHS
>> 80% OF UR WORK WILL BE HERE.

>> WE CODE THE STATEMENT -> COMMAND TO SYSTEM TELLING - HOW TO PROCESS THE
DATA

=> STOP RUN -> COBOL STATEMENT ->COME OUT OF THE PGM ( END OF THE
COBOL PGM)

8TH COL
ID DIVISION.
PROGRAM-ID. CBLPGM01.
AUTHOR. NAME.
DATE-WRITTEN. TODAYS.

ENVIRONMENT DIVISION.
INPUT-OUTPUT SECTION.
FILE-CONTROL.

DATA DIVISION.
FILE SECTION.
WORKING-STORAGE SECTION.
LINKAGE SECTION.

PROCEDURE DIVISION.
000-MAIN-PARA. COMMON.
12 COL
DISPLAY ' HELLO ALL'.
DISPLAY ' WELCOME TO MAINFRAME TRAINING'.

STOP RUN.

COBOL -> COBOL CODE SHEET** -> PGM LINE -> 1-80 COL LENGTH

1-6 -> LINE NUMBER -> SYSTEM AUTO..

7TH COL -> USED FOR CODE A COMMENT (COMMENT -> SYSTEM WILL
IGNORE THOSE LINES)

8-11 -> AREA-A > HEADER > DIVISION , SECTION , PARAG , 01 LEVEL
-> BUT WE ALWAYS -START 8TH ONLY

12-72 -> AREA-B -> STATEMENT (DISPLAY -STOP RUN)

73-80 --> CHANGE TAG -> I WILL SHOW U IN PROJECT.

--> 7-72 -> COMMENT + HEADER + STATEMENT


7 8 12

--> ASKED ME TO CODE A COBOL PGM: 1. WHAT ARE MY IN/OUTPUT ARE 1. FILE -
> OKAY -STYLE-1

2. TABLE -> OKAY -STYLE-2


2. ID - FINISH IT
3. ENVIRONMENT -> CHECK
POINT-1
4. DATA DIVISION (COMPLET IT
PARTITALY) - UNTIL THE LOGIC IS COMPLETED..
5. PROCEDURE DIVISION
(COMPLETE IT )
6. COMPILE + TEST + RETEST..

PGM vs DATA -> CHOOSE 1 -> DATA**

--> ANALYS THE PGM: -> FULL PGM - CHECK AND TELL ME -WHAT THE PGM DOING??

BIG PGM: 1. CHECK THE COMMENT OF THE PGM**


2. ENVIRONMENT DIVISION
--. INPUT?? IS IT FILE A PGM YES -> STYLE 1 , DB2 PGM -STYLE-2
3. PROCEDURE DIVISION.
4. IF REQUIRED -> CHECK THE DATA
DIVISION. (THIS IS ONLY IF REQUIRED)

---

You might also like