|
Michael, I would recommend joining that site so that you can gain access to the forums - its costs nothing to post/search the forums, so its really a no brainer. You may find some examples in the forums and the downloadable code section. If you need more examples I might be able to scrape up a couple of older programs...as long as you don't mind seeing a GO TO here and there ;-) Terry Winchester Programmer/Analyst ________________________________ The Raymond Corporation terry.winchester@xxxxxxxxxxxxxxx
-----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Rosinger Sent: Tuesday, August 22, 2006 2:00 PM To: cobol400-l@xxxxxxxxxxxx Subject: Re: [COBOL400-L] COBOL/ILE questions Terry, Thanks. I will look at the link. We won't be porting any CICS applications. We have very few left. Most of them have been re-engineered as MS Visual C++ accessing our UDB/iSeries database remotely via TCP/IP. The remaining few CICS applications are slated to go that route as well (but maybe VB instead of Visual C++). -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com "Winchester Terry" <terry.winchester@xxxxxxxxxxxxxxx> wrote in message news:mailman.509.1156268924.5750.cobol400-l@xxxxxxxxxxxxxxxMichael, In my experience, the biggest thing to adapt to was screen/workstation I/O. We converted from a homegrown VSE environment to an AS/400 purchased package over a decade ago. We had to convert a few of our CICS programs to interactive Cobol with display files - this is a PITA. If you have any CICS interactive programs I hope your buying the CICS environment for the iSeries otherwise you'll spend a long time converting/rewriting code! As far as batch programs, those that stick within the Cobol Standards will require much less time to convert - probably your SELECT statements will need modification, etc. Here's a short discussion from the one of the other iSeries sites that may give a little more info:http://www.systeminetwork.com/isnetforums/showthread.php?t=304 1&highlight=VSE Terry Winchester Programmer/Analyst ________________________________ The Raymond Corporation terry.winchester@xxxxxxxxxxxxxxx-----Original Message----- From: cobol400-l-bounces@xxxxxxxxxxxx [mailto:cobol400-l-bounces@xxxxxxxxxxxx] On Behalf OfMichael RosingerSent: Tuesday, August 22, 2006 12:44 PM To: cobol400-l@xxxxxxxxxxxx Subject: [COBOL400-L] COBOL/ILE questions Cross-posted to WDSCI-l. Within the next year, we will be migrating COBOL/VSEprograms from theVSE/ESA environment to iSeries COBOL/ILE. Is there anyone out there that has done this and would be willing to share 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 required to execute the program would be very helpful. Anyone game? TIA. -- Regards, Michael Rosinger Systems Programmer / DBA Computer Credit, Inc. 640 West Fourth Street Winston-Salem, NC 27101 336-761-1524 m rosinger at cciws dot com
Confidentiality Notice: The preceding e-mail message (including any attachments) contains information that may be confidential, protected by applicable legal privileges, or constitute non-public information. It is intended to be conveyed only to the designated recipient(s). If you are not an intended recipient of this message, please notify the sender by replying to this message and then delete it from your system. Use, dissemination, distribution or reproduction of this message by unintended recipients is not authorized and may be unlawful.
As an Amazon Associate we earn from qualifying purchases.
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.