Re: COBOL/ILE sample?

There are several things you will need to look for. 
Select statement will be different. 
Comp fields will be treated differently based on the compiler directive. 
STOP RUN. Can cause issues with the CL job stream, I change those to GOBACK.

Some printing issues will occur depending on printer control characters in
COBOL. 
Data issues between systems are one of the biggest issues I face when
migrating from VSE to iSeries. 


There are a lot of little issues that I could go on about, but this is what
I do for a living day in and day out. I would be more than happy to discuss
off-list. 

I currently have two projects going right now taking VSE to iSeries. My
company has been doing these types of conversions for some time now. 

Thanks,


Jerry M Thomas
Cothern Computer Systems, Inc.
1640 Lelia Drive 
Jackson, MS 39216
phone : 601-718-0811
email : jerryt@xxxxxxxxxxx 

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On
Behalf Of Michael Rosinger
Sent: Tuesday, August 22, 2006 10:06 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] COBOL/ILE sample?

Thank you to all who responded with ideas and suggestions both on and 
off-list concerning getting started with WDSC.

Within the next year, we will be migrating COBOL/VSE programs from the 
VSE/ESA environment to iSeries COBOL/ILE. Is there anyone out there that has

done this and can identify the significant differences between the two 
formats of COBOL? If we can identify these differences I could probably 
write a filter program that would change the sources automatically so that 
those issues are dealt with.

Also, a small sample COBOL/ILE program that opens and reads a "file" and 
prints a report along with the accompanying CL would be very helpful. Anyone

game? TIA.