Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
COBOL LE
- Thread starter Dimandja
- Start date
Hi Dimandja,
I think Cobol LE is IBM's latest version of Cobol for OS/390 and VM. The LE bit stands for Language Environment and according to the IBM blurb:
Language Environment, an element of both OS/390 and VM/ESA operating systems creates a single run-time environment for multiple high level languages including:
C/C++
COBOL
PL/I and
Fortran as well as Language Environment enabled assembler programs.
With a single run-time environment, incompatibilities between language specific run-time environments are eliminated. This means that your company's COBOL and C applications, for example, could communicate efficiently and easily together. In addition, your programmers, with various language skills, could work together to build applications with component programs written in a variety of languages.
Well that's what IBM say! There's an IBM overview of migrating from cobol/390 to cobol le at . You'll find an awful lot of info available on the web too. The place I'm at is suipposed to be upgrade to 'zos' shortly which I'm lead to believe will support LE, so maybe we'll be migrating to this soon. I'll let you know.
hth
Marc
I think Cobol LE is IBM's latest version of Cobol for OS/390 and VM. The LE bit stands for Language Environment and according to the IBM blurb:
Language Environment, an element of both OS/390 and VM/ESA operating systems creates a single run-time environment for multiple high level languages including:
C/C++
COBOL
PL/I and
Fortran as well as Language Environment enabled assembler programs.
With a single run-time environment, incompatibilities between language specific run-time environments are eliminated. This means that your company's COBOL and C applications, for example, could communicate efficiently and easily together. In addition, your programmers, with various language skills, could work together to build applications with component programs written in a variety of languages.
Well that's what IBM say! There's an IBM overview of migrating from cobol/390 to cobol le at . You'll find an awful lot of info available on the web too. The place I'm at is suipposed to be upgrade to 'zos' shortly which I'm lead to believe will support LE, so maybe we'll be migrating to this soon. I'll let you know.
hth
Marc
- Thread starter
- #3
Hi Marc,
Nice to hear from you. Thanks for the information.
The Tandem platform uses something that is, I think, similar to LE. It is called the Common Runtime Environment (CRE). When coding outside the CRE, and one of the modules in written in COBOL, the MAIN program must be COBOL. In the CRE, any one of C, COBOL and other supported languages could be declared as MAIN.
One thing that the CRE solves in the mixed languages environment is the sharing of I/O resources. For example, C is notorious for hogging default IO devices through its printf() statements, while COBOL is frivolous with its use of IO resources with DISPLAY statements - each DISPLAY opens, writes than closes the file. In the CRE, each module can use any IO device already opened by another language module, without any initializations or further OPEN statements.
Dimandja
Nice to hear from you. Thanks for the information.
The Tandem platform uses something that is, I think, similar to LE. It is called the Common Runtime Environment (CRE). When coding outside the CRE, and one of the modules in written in COBOL, the MAIN program must be COBOL. In the CRE, any one of C, COBOL and other supported languages could be declared as MAIN.
One thing that the CRE solves in the mixed languages environment is the sharing of I/O resources. For example, C is notorious for hogging default IO devices through its printf() statements, while COBOL is frivolous with its use of IO resources with DISPLAY statements - each DISPLAY opens, writes than closes the file. In the CRE, each module can use any IO device already opened by another language module, without any initializations or further OPEN statements.
Dimandja
Hi,
This is a nice link about LE.
Regards,
Crox
This is a nice link about LE.
Regards,
Crox
- Status
Similar threads
- Locked
- Question