Academic Tutorials



English | French | Portugese | German | Italian
Home Advertise Payments Recommended Websites Interview Questions FAQs
News Source Codes E-Books Downloads Jobs Web Hosting
Chats

Cobol
Introduction to Cobol Programming
Cobol Basics
Cobol Divisions
The Identification Division
The Environment Division
Data Division
Procedure Division
Defining Data Part 1
Number Formats
Moving and Editing Data
Initializing Data
Defining Data Part 2
Printing and Writing Data
Tables
Boolean Data
HIGH-VALUES and LOW-VALUES
Commands and Logics
Accept and Display
Move
Perform
Cobol IF... THEN...ELSE...
Conditions
Cobol Evaluate
Cobol Strings
Cobol Write
Scope Terminators
File Handling
Reading and Writing
REWRITE, DELETE, and EXTEND
SORT and MERGE
Input and Output Procedure
FILE STATUS (error handling)
Debugging COBOL Code

HTML Tutorials
HTML Tutorial
XHTML Tutorial
CSS Tutorial
TCP/IP Tutorial
CSS 1.0
CSS 2.0
HLML
XML Tutorials
XML Tutorial
XSL Tutorial
XSLT Tutorial
DTD Tutorial
Schema Tutorial
XForms Tutorial
XSL-FO Tutorial
XML DOM Tutorial
XLink Tutorial
XQuery Tutorial
XPath Tutorial
XPointer Tutorial
RDF Tutorial
SOAP Tutorial
WSDL Tutorial
RSS Tutorial
WAP Tutorial
Web Services Tutorial
Browser Scripting
JavaScript Tutorial
VBScript Tutorial
DHTML Tutorial
HTML DOM Tutorial
WMLScript Tutorial
E4X Tutorial
Server Scripting
ASP Tutorial
PERL Tutorial
SQL Tutorial
ADO Tutorial
CVS
Python
Apple Script
PL/SQL Tutorial
SQL Server
PHP
.NET (dotnet)
Microsoft.Net
ASP.Net
.Net Mobile
C# : C Sharp
ADO.NET
VB.NET
VC++
Multimedia
SVG Tutorial
Flash Tutorial
Media Tutorial
SMIL Tutorial
Photoshop Tutorial
Gimp Tutorial
Matlab
Gnuplot Programming
GIF Animation Tutorial
Scientific Visualization Tutorial
Graphics
Web Building
Web Browsers
Web Hosting
W3C Tutorial
Web Building
Web Quality
Web Semantic
Web Careers
Weblogic Tutorial
SEO
Web Site Hosting
Domain Name
Java Tutorials
Java Tutorial
JSP Tutorial
Servlets Tutorial
Struts Tutorial
EJB Tutorial
JMS Tutorial
JMX Tutorial
Eclipse
J2ME
JBOSS
Programming Langauges
C Tutorial
C++ Tutorial
Visual Basic Tutorial
Data Structures Using C
Cobol
Assembly Language
Mainframe
Forth Programming
Lisp Programming
Pascal
Delphi
Fortran
OOPs
Data Warehousing
CGI Programming
Emacs Tutorial
Gnome
ILU
Soft Skills
Communication Skills
Time Management
Project Management
Team Work
Leadership Skills
Corporate Communication
Negotiation Skills
Database Tutorials
Oracle
MySQL
Operating System
BSD
Symbian
Unix
Internet
IP-Masquerading
IPC
MIDI
Software Testing
Testing
Firewalls
SAP Module
ERP
ABAP
Business Warehousing
SAP Basis
Material Management
Sales & Distribution
Human Resource
Netweaver
Customer Relationship Management
Production and Planning
Networking Programming
Corba Tutorial
Networking Tutorial
Microsoft Office
Microsoft Word
Microsoft Outlook
Microsoft PowerPoint
Microsoft Publisher
Microsoft Excel
Microsoft Front Page
Microsoft InfoPath
Microsoft Access
Accounting
Financial Accounting
Managerial Accounting
Network Sites


Debugging COBOL Code


Previoushome






Debugging COBOL code

So you've written your program, finally got it to compile after sorting out all those syntax errors and undefined variables and the rest.

A D V E R T I S E M E N T
So you execute the program and Hey Presto! ... nothing happens, you get a runtime error, or worst of all, your computer locks up and you're reaching for CTRL+ALT+DEL. So what went wrong?

Don't worry. The next thing to do after writing your wonderfully crafted program is to fix all the bugs, that is, all the errors in the code that lie hidden in the logic beyond the reach of the compiler. Here are a few personal hints and tips of mine to set about debugging your program (and avoiding errors in the first place), or at least how I go about getting my code to do what I want it to do.

 

  1. Before a line of code is written...preparation
  2. Commenting
  3. Variable names
  4. Break it up
  5. "Stubs"
  6. Watching variables
  7. Debugging tools

 
 

(i) Before a line of code is written...preparation

The best way to avoid spending hours trying to untangle a mass of complex code (that you brilliantly typed into the computer straight from the top of your head) is PREPARATION. By that I mean: (1) be absolutely clear about what you want the program to do - know what the inputs and outputs are, (2) write a very broad algorithm and gradually refine as far as you can using pseudo-code, (3) draw a flow chart or structure chart that matches the pseudo-code, and (4) translate the flow chart into actual COBOL.

One issue is: Do I write the PROCEDURE DIVISION first and then go back and write the DATA DIVISION? This would seem a fairly sensible thing to do except that in practise you find you will forget to declare a whole slew of variables. A further point is that a good deal of COBOL involves doing things to the data that rely on what's been declared in the DATA DIVISION. Again, I would suggest preparing a fair proportion of the data definitions on paper first. When I write a program I write as much DATA DIVISION as possible before starting on the PROCEDURE DIVISION. Then, as I proceed through the code I keep going back to the DATA DIVISION to update it as soon as possible.

 (ii) Commenting
 

Liberally sprinkle you code with comments that explain exactly what each fragment of code is meant to do. This really helps when trying figure out what's going on.

 (iii) Variable names
 

Use variable names that are meaningful and stick to a standard format. For example, some people use a prefix before variable names to indicated the general function of the variable, such as printing variables:

 

01 PRINT-OUTPUT.
03 P-NAME PIC X(20).
03 P-ADDRESS PIC X(50).
03 P-CUS-CODE PIC 9(6).
03 P-PAGE-COUNT PIC 999.

This example uses "P-" before each name to indicate a member of the print output group. Sometimes the prefix "WS-" is used to indicate WORKING-STORAGE, "L-" for LINKAGE SECTION variables. Notice that the names are also meaningful. While you may spend longer typing out longer names you'll thank youself when it comes to fixing bugs.  

Care should be taken when deciding names that you spell them correctly (PAGE-COUNTRE) and/or consistantly (RECORD-NUM and RECORD-NO) and that you don't try to use singular and plural names (CUSTOMER-TOTAL and CUSTOMER-TOTALS).

 
 

(iv) Break it up
 

Breaking your code into smaller procedures (i.e. paragraphs) not only makes the program easier to read, but easier spot where problems are arising.

 
 

(v) "Stubs"
 

One way to monitor what is going on when you run your program is to place "stubs" at important points in the logic. By stubs I mean a DISPLAY statement that tells you the that certain position in the logic has been executed:

 

MAIN-PARAGRAPH.
DISPLAY 'IN MAIN PARAGRAPH'
PERFORM INIT-PARAGRAPH.
PERFORM RECORD-READ-PARAGRAPH
UNTIL NO-MORE-RECORDS
PEFORM TERMINATE-RUN
DISPLAY 'PROGRAM ENDING'
STOP RUN.

If you have a DISPLAY at the beginning of each paragraph then the console window might look something like this:
 
IN MAIN PARAGRAPH
IN INIT-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN RECORD-READ-PARAGRAPH
IN TERMINATE-PARAGRAPH
PROGRAM ENDING

You must remember to remove all of the stubs when the program is fully debugged.

 

 
 

(vi) Watching variables
Of course, just putting little flags say "IN PARAGRAPH XYZ" can be extended further to display the value of certain important variables:
 

DISPLAY "P-COUNTER = " P-COUNTER

Again, don't forget to remove them (or comment them out) when your done.  

 
 

(vii) Debugging tools
Both the Fujitsu COBOL85 and Microfocus Personal COBOL compilers (and presumably other too) have debugging utilities. Most significant are the ability to animate the program and set breakpoints throughout your code. Animating your code allows you to view each line of code as the debugger steps through the program. You can pause the run at any point and check the value of variables. During this process you can specify variables that you want to watch throughout the run. Animating a program run can prove a bit tedious if large amounts of iterations are involved.

An alternative is to set breakpoints. By doing so the program run will pause at defined breakpoints (wherever you want them) to allow you to check the value of variables.

You should check your compiler documentation to find out how to use debugging utilites: for large programs they are well worth the effort.

 

*       *       *

When it comes to actually fixing errors try to avoid "hacks", that is, adding bits of code to correct erroneous data values rather than trying to find out why the data was wrong in the first place. You may find yourself getting bound up in ever more complex arrays of Boolean flags to allow certain conditions: e.g.
 

IF (X = Y) AND (Z >= W) AND ((A = B) OR (A <> C)) AND (D < F) THEN...scream..?

This being the case, see if your logic couldn't be better designed. Sometimes going back to the drawing board (more than once) is the best strategy in the long run. Like a famous chess grandmaster once said (I don't know who) "If you see a good move, look for a better one" : if you think of a good way of coding something, look for a better alternative (not as snappy ?!).  

Something to keep in mind at all times is that one day someone other than yourself may have to read and understand (and perhaps modify) your code. Whether this is true or not it is a good habit to get into because it makes you write better code. And, as a software professional, this will almost certainly be the case.



Be the first one to comment on this page.




  Cobol eBooks
More Links » »
 
 Cobol FAQs
More Links » »
 
 Cobol Interview Questions
More Links » »
 
 Cobol Articles
More Links » »
 
 Cobol News
More Links » »
 
 Cobol Jobs
More Links » »

Share And Enjoy:These icons link to social bookmarking sites where readers can share and discover new web pages.
  • blinkbits
  • BlinkList
  • blogmarks
  • co.mments
  • connotea
  • del.icio.us
  • De.lirio.us
  • digg
  • Fark
  • feedmelinks
  • Furl
  • LinkaGoGo
  • Ma.gnolia
  • NewsVine
  • Netvouz
  • RawSugar
  • Reddit
  • scuttle
  • Shadows
  • Simpy
  • Smarking
  • Spurl
  • TailRank
  • Wists
  • YahooMyWeb

Previoushome

Keywords: Cobol Basics, cobol programming language, cobol language programming tutorial pdf, history of cobol programming, basic cobol programming, syntax use in cobol programming, cobol programming software download, cobol programming code, learn cobol programming, cobol performs syntax, cobol 2008

HTML Quizzes
HTML Quiz
XHTML Quiz
CSS Quiz
TCP/IP Quiz
CSS 1.0 Quiz
CSS 2.0 Quiz
HLML Quiz
XML Quizzes
XML Quiz
XSL Quiz
XSLT Quiz
DTD Quiz
Schema Quiz
XForms Quiz
XSL-FO Quiz
XML DOM Quiz
XLink Quiz
XQuery Quiz
XPath Quiz
XPointer Quiz
RDF Quiz
SOAP Quiz
WSDL Quiz
RSS Quiz
WAP Quiz
Web Services Quiz
Browser Scripting Quizzes
JavaScript Quiz
VBScript Quiz
DHTML Quiz
HTML DOM Quiz
WMLScript Quiz
E4X Quiz
Server Scripting Quizzes
ASP Quiz
PERL Quiz
SQL Quiz
ADO Quiz
CVS Quiz
Python Quiz
Apple Script Quiz
PL/SQL Quiz
SQL Server Quiz
PHP Quiz
.NET (dotnet) Quizzes
Microsoft.Net Quiz
ASP.Net Quiz
.Net Mobile Quiz
C# : C Sharp Quiz
ADO.NET Quiz
VB.NET Quiz
VC++ Quiz
Multimedia Quizzes
SVG Quiz
Flash Quiz
Media Quiz
SMIL Quiz
Photoshop Quiz
Gimp Quiz
Matlab Quiz
Gnuplot Programming Quiz
GIF Animation Quiz
Scientific Visualization Quiz
Graphics Quiz
Web Building Quizzes
Web Browsers Quiz
Web Hosting Quiz
W3C Quiz
Web Building Quiz
Web Quality Quiz
Web Semantic Quiz
Web Careers Quiz
Weblogic Quiz
SEO Quiz
Web Site Hosting Quiz
Domain Name Quiz
Java Quizzes
Java Quiz
JSP Quiz
Servlets Quiz
Struts Quiz
EJB Quiz
JMS Quiz
JMX Quiz
Eclipse Quiz
J2ME Quiz
JBOSS Quiz
Programming Langauges Quizzes
C Quiz
C++ Quiz
Visual Basic Quiz
Data Structures Using C Quiz
Cobol Quiz
Assembly Language Quiz
Mainframe Quiz
Forth Programming Quiz
Lisp Programming Quiz
Pascal Quiz
Delphi Quiz
Fortran Quiz
OOPs Quiz
Data Warehousing Quiz
CGI Programming Quiz
Emacs Quiz
Gnome Quiz
ILU Quiz
Soft Skills Quizzes
Communication Skills Quiz
Time Management Quiz
Project Management Quiz
Team Work Quiz
Leadership Skills Quiz
Corporate Communication Quiz
Negotiation Skills Quiz
Database Quizzes
Oracle Quiz
MySQL Quiz
Operating System Quizzes
BSD Quiz
Symbian Quiz
Unix Quiz
Internet Quiz
IP-Masquerading Quiz
IPC Quiz
MIDI Quiz
Software Testing Quizzes
Testing Quiz
Firewalls Quiz
SAP Module Quizzes
ERP Quiz
ABAP Quiz
Business Warehousing Quiz
SAP Basis Quiz
Material Management Quiz
Sales & Distribution Quiz
Human Resource Quiz
Netweaver Quiz
Customer Relationship Management Quiz
Production and Planning Quiz
Networking Programming Quizzes
Corba Quiz
Networking Quiz
Microsoft Office Quizzes
Microsoft Word Quiz
Microsoft Outlook Quiz
Microsoft PowerPoint Quiz
Microsoft Publisher Quiz
Microsoft Excel Quiz
Microsoft Front Page Quiz
Microsoft InfoPath Quiz
Microsoft Access Quiz
Accounting Quizzes
Financial Accounting Quiz
Managerial Accounting Quiz
Testimonials | Contact Us | Link to Us | Site Map
Copyright 2008. Academic Tutorials.com. All rights reserved Privacy Policies | About Us
Our Portals : Academic Tutorials | Best eBooksworld | Beyond Stats | City Details | Interview Questions | Discussions World | Excellent Mobiles | Free Bangalore | Give Me The Code | Gog Logo | Indian Free Ads | Jobs Assist | New Interview Questions | One Stop FAQs | One Stop GATE | One Stop GRE | One Stop IAS | One Stop MBA | One Stop SAP | One Stop Testing | Webhosting in India | Dedicated Server in India | Sirf Dosti | Source Codes World | Tasty Food | Tech Archive | Testing Interview Questions | Tests World | The Galz | Top Masala | Vyom | Vyom eBooks | Vyom International | Vyom Links | Vyoms | Vyom World
Copyright 2003-2018 Vyom Technosoft Pvt. Ltd., All Rights Reserved.