Re: COBOL/ILE questions

"Jon Paris" <Jon.Paris@xxxxxxxxxxxxxx> wrote in message 
news:mailman.580.1156276449.5750.cobol400-l@xxxxxxxxxxxxxxx

As I said on WDSC Michael - we need to know more about the type of 
programs
(on-line, batch, etc.) before we can give a you a feel for the scope.

I responded earlier that these are all batch programs.

In terms of data types the biggie is usually that the meaning of COMP is
different on the two platforms.  It means binary on mainframe and packed 
on
System i.  As a result COBOL redefinitions involving such fields can be 
"interesting.

According to the ILE COBOL Reference, COMP is binary if you specify the 
COMPASBIN compiler option, which is what we would absolutely have to do 
coming from the VSE world. Otherwise, it is as you said, assumed to be 
packed decimal.

Hardest thing is creating the external file definitions to match the
internal defs in the current COBOL code.  If you make extensive use of 
COPY
books and the definitions are well done this can be semi-automated.

We do try to make good use of copybooks.

There have been a couple of tools around in the past - don't know if they
still exist.  Google may turn up something.

I will keep looking.

Hardest part of the conversion?  Learning not to waste time looking for 
"how
to do" things that simply don't need to be done on a System i!

You got that right. That's why I am picking the collective brain of the list 
:-)

Thanks for the comments!