× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You should have no trouble going from CBL to CBLLE if there are no GO TO's that 
branch to a prior paragraph name. A program that had code like the following 
compiled as COBOL/400 but failed to compile as ILE COBOL.

STEP-2.
    READ INPUT-FILE
        AT END
            GO TO STEP-3.
    IF  CUSTOMER-NAME = SPACES
        GO TO STEP-2.
    IF  EXPIRATION-DATE < TODAYS-DATE
        GO TO STEP-2.
    ...

Also, you will get a lot of warning errors if your I-O statements lack phrases 
like "INVALID KEY" where that would be an appropriate phrase. That may not be 
important to you; I prefer all my SEV's to be no higher than 0.

Cheers -- Jay
 
-----Original Message-----
From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] 
On Behalf Of Finucci Domenico
Sent: Friday, January 14, 2005 8:09 AM
To: COBOL Programming on the iSeries/AS400
Subject: R: [COBOL400-L] COBOL400 TO COBOL LE

 1. Is there any tools availaible (Necessary?) to migrate COBOL/400 TO COBOL LE.
No tools are needed, at least to compile in ILE. Simply rename CBL to CBLLE and 
recompile

 2.Whether they are compatible,Please give me the diffrences between these two.
Too difficult to resume in a short mail.  Take a look at "ILE Concept" manual. 
Are you experienced in C or C++ ? A few concepts are common. 

 3.What  will be the migration startegy.
Minimal migration strategy is first to convert to CBLLE and recompile. In a 
near future you may try to introduce some ILE - tipical characteristics (date 
calculation, return-code, DLL, and so on...)


Sincerely

        Domenico Finucci
         Tel. + 39 02-43.01.2494, cell. 348 - 59.53.279
        E-mail: domenico.finucci@xxxxxxxxxxxx 
 


-----Messaggio originale-----
Da: natarajan pillai [mailto:natrajan_msc@xxxxxxxxx]
Inviato: venerdì 14 gennaio 2005 14.01
A: cobol400-l@xxxxxxxxxxxx
Oggetto: [COBOL400-L] COBOL400 TO COBOL LE


Hi All,
  I am a software professional working for an mnc in India.I have few doubts 
regarding 
COBOL LE ansd COBOL/400.
 1. Is there any tools availaible (Necessary?) to migrate COBOL/400 TO COBOL LE.
 2.Whether they are compatible,Please give me the diffrences between these two.
 3.What  will be the migration startegy.
 
It will be great to have answers for all the questions,Even if you know for the 
first two 
it will be fine.
 
Thanks a Lot and Really you people are doign good work
 
 
 
Best Regards
Natarajan
 
 
 
 
 
 

                
---------------------------------
Do you Yahoo!?
 Yahoo! Mail - now with 250MB free storage. Learn more.
_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.


_______________________________________________
This is the COBOL Programming on the iSeries/AS400 (COBOL400-L) mailing list
To post a message email: COBOL400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/cobol400-l
or email: COBOL400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/cobol400-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.