View previous topic :: View next topic |
Author |
Message |
Dibakar Advanced
Joined: 02 Dec 2002 Posts: 700 Topics: 63 Location: USA
|
Posted: Mon Dec 09, 2002 6:15 am Post subject: Assembler to Cobol conversion |
|
|
I want to know how Address instructions (like LA) and Macros (assuming there expansion depends on parametrs passed) are handled when converting Assember programs to complete Cobol programs.
Thanks,
Dibakar. |
|
Back to top |
|
|
Mervyn Moderator
Joined: 02 Dec 2002 Posts: 415 Topics: 6 Location: Hove, England
|
Posted: Mon Dec 09, 2002 4:17 pm Post subject: |
|
|
Dibakar,
When converting from one language to another, I believe you should concentrate on Function rather than on Method. This is especially important when converting from Assembler.
The LA instruction doesn't necessarily convert directly to anything. It is used for incrementing counters (though it probably shouldn't be); it is also used for array subscripting. You must work out what the program is doing, then write something to achieve the same objective.
Cheers,
Merv |
|
Back to top |
|
|
nxn00 Beginner
Joined: 02 Dec 2002 Posts: 18 Topics: 0 Location: US
|
Posted: Mon Dec 09, 2002 7:00 pm Post subject: |
|
|
The LA instruction was used to "add +1" in the old days (70's).
LA was FAST! Not an issue by then, but "old timers" liked it.
Now, we are the "old timers." _________________ Natalie |
|
Back to top |
|
|
Nikunj Beginner
Joined: 03 Dec 2002 Posts: 6 Topics: 3 Location: Pune, India
|
Posted: Tue Dec 10, 2002 12:07 am Post subject: |
|
|
Dibakar
I believe that some of the macros which can be called by assembler but cannot by cobol, could be matter of concern. For that you might want to use assembler subroutines, which will be called by cobol program |
|
Back to top |
|
|
Dibakar Advanced
Joined: 02 Dec 2002 Posts: 700 Topics: 63 Location: USA
|
Posted: Tue Dec 10, 2002 2:30 am Post subject: |
|
|
Well Merv aptly confirmed my fears, ASSEMBLER to COBOL has to tackled by FUNCTION rather than METHOD.
But I would like to share experience of people who went through such conversion. I was once involved in estimation of a ASSEMBLER to COBOL conversion project where it involved over 200 programs with no supporting documments. To me it looked a very difficult job. Unfortunately we didn't get the project so I am wondering what it would have been like if really do such conversions. |
|
Back to top |
|
|
Mervyn Moderator
Joined: 02 Dec 2002 Posts: 415 Topics: 6 Location: Hove, England
|
Posted: Tue Dec 10, 2002 5:28 pm Post subject: |
|
|
I've never been involved in a conversion project of this type, but I would say you'd be well advised to be on the generous side when quoting for the job, and try very hard to find areas that can be discarded completely (it's quite amazing sometimes how much old stuff really isn't used any more).
Tackle the job steadily, enjoy yourself, and be prepared to learn very quickly!
Cheers,
Merv
|
|
Back to top |
|
|
hari_uss Beginner
Joined: 19 Dec 2002 Posts: 78 Topics: 6 Location: Trivandrum, India
|
Posted: Mon Dec 23, 2002 1:46 am Post subject: |
|
|
Same here Dibakar,
I also have a similar experience with Assembler to Cobol conversion. We had 80 programs to convert. In fact, we did a prototype too.
I also approached in the same way, function by function. I split the 3000+ lines of code of an assembler program into several modules. I created a low level specification on that with different modules conncted mainly with GO TOs. (There is no straight forward method to avoid BR when you convert into Cobol). Then I got rid of GO TOs with some techniques. This may of interest for you.
Rewriting Sphagetti Code.
Eventually, what we figured out was around 40hrs for one program (of size 1000+). To be frank, I don't know whether that figure was correct or not since I moved out of the team by then.
Regards,
Hari. |
|
Back to top |
|
|
|
|