View previous topic :: View next topic |
Author |
Message |
vini Intermediate
Joined: 12 Jan 2004 Posts: 240 Topics: 48 Location: Maryland
|
Posted: Thu Jan 22, 2004 11:55 am Post subject: Cobol Appln. Maintenance |
|
|
Hi Friends,
Say I have a complex Cobol program and for ease of its Maintenance I would like to quickly or readily know its Structure or Hierarchy. One tedious and time consuming way is to Dry run the program.
Anyone knows of any common Tool /utility to achieve this ?!! It could be on mainframe or PC-based. Maybe even some Freeware which I could download.
If not , then any other Inputs on making the Task of maintaining a Complex and Huge Cobol Application easier .. apart from following Standards and Documenting the code i.e ? Assuming its someone elses baby and your expected to maintain it.
Thnks!
vini |
|
Back to top |
|
 |
kolusu Site Admin

Joined: 26 Nov 2002 Posts: 12378 Topics: 75 Location: San Jose
|
Posted: Thu Jan 22, 2004 1:02 pm Post subject: |
|
|
Vini,
I can see the enthusiasm of yours to know the system you have taken over to maintain. But remember that the system you want to learn is built over years. so go slow and first try to understand the business logic behind the system and then slowly the technical details will automatically flow in. There aren't any tools to get you what you asked for. Even if there are tools they wouldn't be 100% accurate.
Still if you insist on knowing the program, then you can try these suggestions.
Take a copy of compiler listing of the program(this will have the includes,copy books expanded). This will be big enough to be a pillow so that you can have it even during your sleep Now try to write down a psuedo code by going thru the program. This cannot be achieved in a day or two . so be patient.
Once you have done with that put your psuedo code as a reference sheet and run the program in batch or xpeditor. Now cross check your psuedo code with the results and verify if you understanding of the program is correct. Start with simple test and slowly move on to the most complex tests.
Hope this helps...
Cheers
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
 |
mfjin Beginner
Joined: 26 Apr 2003 Posts: 94 Topics: 17
|
Posted: Thu Jan 22, 2004 3:05 pm Post subject: |
|
|
vini,
microfocus revolve - a pc based tool should give you some idea in the form of flow diagrams and structure charts. |
|
Back to top |
|
 |
vini Intermediate
Joined: 12 Jan 2004 Posts: 240 Topics: 48 Location: Maryland
|
Posted: Thu Jan 22, 2004 4:30 pm Post subject: |
|
|
We do not have Microfocus Revolve here & its not a Freeware.
I guess I'll have to go the traditional route as explained by kolusu
Thnks.
vini |
|
Back to top |
|
 |
Mervyn Moderator

Joined: 02 Dec 2002 Posts: 415 Topics: 6 Location: Hove, England
|
Posted: Thu Jan 22, 2004 6:02 pm Post subject: |
|
|
Vini, I've been doing this job for longer than I care to remember. I still believe there's no substitute for reading the code. Then reading it again. Then again. Then realising there are bits in there you can do better, and proving it.
Enjoy your work. _________________ The day you stop learning the dinosaur becomes extinct |
|
Back to top |
|
 |
kok328 Beginner

Joined: 05 Nov 2003 Posts: 19 Topics: 0 Location: MI, USA
|
Posted: Fri Feb 13, 2004 12:01 pm Post subject: |
|
|
Vini,
Compuware has a PC based product call DEV/Enterprise which will analyze a program and draw flowcharts, maps, etc....
I wouldn't rely on this alone, use it as a road map to read the code. |
|
Back to top |
|
 |
neilxt Beginner
Joined: 01 Mar 2004 Posts: 23 Topics: 1
|
Posted: Wed May 12, 2004 3:05 pm Post subject: |
|
|
Quote: |
Say I have a complex Cobol program and for ease of its Maintenance I would like to quickly or readily know its Structure or Hierarchy. One tedious and time consuming way is to Dry run the program.
|
I have some CLISTS which might help however they have some very strict requirements...
One program analyses the current program and creates a hierarchical (and recursive) list of performed routines like this...
*** ************ MAKECHRT *************************
*** PERFORM STRUCTURE OF PROGRAM CREATED BY MAKECHI
*** ===============================================
*** PROCEDURE DIVISION
*** AA00-CONTROL
*** : BA00-INITIALIZE
*** : : XA00-READ-CHSA UNTIL WI-REC OR WI-EOF
*** : BB00-PROCESS UNTIL WI-EOF
*** : : YA00-WRITE-REPORT
*** : : XA00-READ-CHSA
*** : BC00-FINALIZE
*** ************ END MAKECHRT *********************
HOWEVER it requires that the program use SECTIONS not PERFORM ... THRU (which is better programming practice anyway; but that's a different thread...)
So - I have another CLIST which converts a program from PERFORM ... THRU logic to use SECTIONs.
HOWEVER that requires that good programming standards be followed - specifically no overlapping performs. OTOH - it's pretty good at finding and marking such problem areas which can be very useful in itself so long as you remember to cancel out and not leave the program partially SECTIONized.
And I would like to add that ...
Quote: |
Then realising there are bits in there you can do better, and proving it.
|
... is also one of my favourite tools. It works much better than just reading it. |
|
Back to top |
|
 |
Dibakar Advanced

Joined: 02 Dec 2002 Posts: 700 Topics: 63 Location: USA
|
Posted: Thu May 13, 2004 12:45 am Post subject: |
|
|
Quote: |
So - I have another CLIST which converts a program from PERFORM ... THRU logic to use SECTIONs.
|
I was thinking of developing similar tool but got stuck at PERFORM ... THRU.
Thanks for sahring the idea. |
|
Back to top |
|
 |
Cogito-Ergo-Sum Advanced
Joined: 15 Dec 2002 Posts: 637 Topics: 43 Location: Bengaluru, INDIA
|
Posted: Thu May 13, 2004 2:42 am Post subject: |
|
|
I had done that too; in REXX. 8)
Except, we had some 'shortcuts' that sometimes helped in parsing COBOL code. The most difficult part was, when a VERB with it clauses would span multiple lines. I cannot divulge much.
My code did 2 things. Check program for any standard violations. And, provide a flow of program similar to what neilxt has posted above. It was not as pretty though.  _________________ ALL opinions are welcome.
Debugging tip:
When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
-- Sherlock Holmes. |
|
Back to top |
|
 |
|
|