|
COBOL Report Generator |
|
Print graphics in COBOL reports with the reporting tool
RPV Reports.
Insert graphics (images, photos, logos, charts, graphs, etc.) in your plain text file COBOL
reports to improve the quality of your reports.
See how the report generator RPV Reports can be used to print graphics in your plain text COBOL reports. |
 |
|
Mainframe Training |
|
The
Mainframe COBOL Training Boot Camp is an intensive 10-day training course that allows
you to function as a COBOL programmer in an IBM Enterprise mainframe environment.
A comprehensive offering of instructor led online and onsite
mainframe training courses are provided including COBOL, CICS, DB2,
Easytrieve, FileAid, ISPF, JCL, VSAM, IMS, JES2, REXX, SysPlex, SMP/E,
Xpeditor and z/OS, giving you the foundation to function as a mainframe programmer. |
|
|
|
COBOL Analysis Tools |
Analyze, debug and understand your COBOL applications with our quality set of
COBOL Analysis Tools.
Analyze your COBOL applications with our Error Checker tool which checks for
logic errors that are not detected by COBOL compilers.
Analyze the IF ELSE structure of your COBOL programs with our Nested If Analysis tool.
Understand the logic of your COBOL programs from top to bottom and bottom to top with our comprehensive Top Down Logic Progression and Bottom Up Logic Regression tool.
Generate an easy to understand database cross reference listing with our ADABAS and DB2 File References tools. |
|
|
|
COBOL Email List Rental |
|
You can reach a highly targeted, qualified, opt-in audience of
COBOL users by renting the COBUG email list.
Contact us today advertise@cobug.com for details about our email list and rental rates.
|
|
|
|
Website Advertisement |
|
Advertise on the
COBUG website and reach tens of thousands of COBOL users. Increase
your sales leads.
Contact COBUG at advertise@cobug.com for advertising rates.
|
|
|
|
Support COBUG |
|
|
|
|
|
|
|
| |
Contributed by: Hugo Vandamme, Functioneel Analist, Ops&IT Banking/ING Belgium
A problem arising very often is the mess created by nested IF's.
Forgetting 1 ELSE or END-IF has cost many man-years.
Everybody tries to avoid this problem by aligning IF, ELSE and END-IF as far as possible.
Nevertheless, this system fails very often.
My suggestion, (I use it in pseudo-code) :
NUMBER the IF, ELSE and END-IF statements as follows :
e.g.
IF1 condition
statement
IF2 condition
statement
ELSE2
statement
END-IF2
statement
ELSE1
statement
END-IF1
This numbering helps to understand the structure of nested IF's and makes it easy to discover errors.
COBOL-compiler should accept this structure and create an error (or only a warning?) if numbering is not coherent.
Just a suggestion of an old programmer - if ever accepted, it will not be useful for me anymore.
--------------------------
|
|
[ Go to Top of Page ]
|
|
|
|
COBOL Job Seekers |
Looking for a COBOL job? Submit your resume here and have it viewed by employers and recruiters hiring for COBOL positions.
|
|
|
Employers & Recruiters |
Do you need to fill a COBOL position? Post your COBOL jobs here and find the most qualified COBOL candidates to fill your COBOL position.
|
|
|
Call for Articles |
Articles are being sought for the COBUG newsletters.
Will you help us in our efforts to provide newsletters for the COBOL community at large?
Contribute to the COBUG newsletters! Answer this call for COBOL and related legacy articles. |
|
|
Join COBUG! |
Become a part of COBUG and the global COBOL community today.
Join Now ...
|
|
|
COBOL Forums |
Try our COBOL forums for help!
Let the COBUG members help you.
Post your issues!
|
|
|
