🚀 go-pugleaf

I have read a number of replies to this note in both comp.lang.cobol and
IBM-MAIN.  Let me summarize *my* personal suggestions on the steps that you
should follow:

1) Read all 3 Migration Guides at the following locations:
 For COBOL:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IGY3MG00/CCONTENT
S

For PL/I:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IBM3MG00/CCONTENT
S

For LE:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CEEA6130/CCONTENT
S

2) Review the ILC (InterLanguage Communications) Manual at:

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/CEEA4110/CCONTENT
S

3)  Look into the Edge Portfolio Analyzer (or other products if you can find
them).  See:
 http://edge-information.com/epa-00.htm

4) Make certain that you verify that all your "development tools"
(debuggers, dump analyzers, etc) are at the appropriate levels to support
current levels of LE and an compilers.  Then make certain that the same is
true for any "outside" provided applications run in your shop.

 ... After this preparatory work - I have a few suggestions:

A) *Never* override the link-edit attributes for COBOL programs.   If you
set the compiler options correctly (for what you want), then "take" the
linkage editor (or binder) options that are produced.

B) Move to an environment where LE is the *only* run-time library in use
(Linklist, Steplib, etc)

C) *After* you have killed off all older run-time libraries, then make
certain that you move to LE as the only link-edit library in use.

D) *AFTER* you have moved to LE as the only run-time and link-edit library,
then use RACF or similar facility to insure that only the "newer" compilers
are used for maintenance and development.


--
Bill Klein
 wmklein <at> ix.netcom.com
"joseluis" <jos@generali.es> wrote in message
news:b16bk2$5nm$1@nsnmrro2-gest.nuria.telefonica-data.net...
> Hi all,
>
>  This year we're planning to migrate our high level languages. Now we're
> running
>
>         on a OS/390 V 2.10,
>         LE runtime environment in Linklist,
>         OS PL/I 2.3 and
>         COBOL II V 1.3.2
>         CICS Transaction Server V 1.3.0
>         DB2 V 5.1.0
>
>  Our online environment is all in AMODE 31 but in batch we're runnig
mainly
> in AMODE 24. This change is dificult
>  for as because is a integrate and dinamyc environment and is very
dificult
> to establish trcability of programs calls and
>  we've understand that we've to migrate in a particular order in order to
> avoid AMODE31 call to AMODE24 rutines.
>
>  we would like to migrate to OS/390 Enterprise PL/I and COBOL and some
that
> we discus are
>
>     - Can we linkedite our actuals programs with LE (only linkedite) ? Is
it
> a good idea?
>     - Is it necesary to migrate our batch environment to AMODE 31 (or ANY)
?
> and if is not
>       a mandatory, is it better?
>     - Is there strong compatibilities within pl/I and COBOL verssions
runnig
> together ?
>     - Someone has experienced a similar (ordered and global) migration?
>
>   Any sugestions?
>
>   Thank you very much
>
>   Josep Lluis
>
>
>
>
>
>
>
>
>