| Michael Mattias 2005-06-01, 8:55 pm |
| Just noticed...
"Roby66" <NOSPAM@libero.it> wrote in message
news:d7kco0$pl$1@newsreader.mailgate.org...
> Hi, I'm roby...
> I'm trying to porting vb array management (redim preserve) to cobol
....
[anither message.]..
>Anyway I have to port this vb application on mainframe..
....
>I only know new application has to be developed
>using cobol II, I think cobol 85.
>Customer sent me a source code is running on
>their system and I suppose is standard ansi85
???
Not sure I understand your situation entirely, but let me hazard a guess:
Customer sent you COBOL source code of ..what, what they use now? And you
need to integrate some capability currently available in a VB program into
that software?
Not ever having seen any of this, or even sure if I understand the situation
correctly, two things come to mind...
1. There is such a thing as "Mainframe BASIC". IIRC, it's not terribly
popular or powerful, but it's out there somewhere.
2. Instead of screwing around with a port, might be easier and surely will
be more maintainable long-term to forget about 'porting,' bite the bullet
and just write the required logic in COBOL from scratch. (Disclaimer: I am a
notorious critic of 'verb-for-verb' port/translation efforts).
FWIW, if your BASIC is well written, your COBOL code - if equally
well-written - will look a lot like the BASIC code with which you
start.(I've often said "Well-written BASIC looks a lot like well-written
COBOL. Badly-written BASIC looks a lot like, well, badly-written BASIC".
(Also FWIW: dynamic memory allocation and pointer variables ARE available
with IBM mainrame COBOL).
MCM
|