 |
UV Software has a complete solution for conversion of mainframe
MVS or VSE JCL, COBOL, & DATA batch systems to Unix, Linux, or Windows/SFU.
Over 50 successful conversions including global corporations & government agencies.
Please see demo conversions & detailed explanations at:
www.uvsoftware.ca
You may send samples of your files for conversion & return by email.
You may download 1 free utility from:
www.uvsoftware.ca/ libuvhd.htm
'uvhd' displays data files with packed/binary fields in 'vertical hexadecimal',
and includes many interactive functions (browse, search, select, update, print, etc).
|
 |
COBOL Report Generator |
|
Print graphical COBOL reports in Windows with
RPV Reports.
Insert graphics (images, photos, logos, charts, etc.) into your COBOL reports
to improve the print quality of your COBOL reports.
See how RPV Reports can be used to preview or print graphical COBOL reports in Windows. |
|
|
COBOL Documentation |
|
Are your mainframe COBOL applications properly documented?
DCD III
is a comprehensive COBOL documentation and application
understanding tool that will allow you to reduce COBOL maintenance,
development, and mainframe migration costs.
Learn more about how you can document and understand your mainframe COBOL
applications with DCD III. |
|
|
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 our email list rental rates.
|
|
|
Website Advertisement |
|
Advertise on the
COBUG website and reach tens of thousands of COBOL users. Increase
your COBOL sales leads.
Contact COBUG at advertise@cobug.com for advertising rates.
|
|
|
|
|
|
|
| |
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. |
|
|
Local COBOL User Groups |
Check out the list of local COBOL user groups from around the world and join a user group near you.
|
|
|
Call for User Group Leaders! |
Get Involved! We are looking for user group
leaders to help organize and coordinate a local COBOL user group.
|
|
|
Join COBUG! |
Become a part of the COBUG community today.
Join Now ...
|
|
|
COBOL Forums |
Try our forums for help!
Let the COBUG members help you.
Post your issues!
|
|
|
