tag:blogger.com,1999:blog-18371456.post6268629166254937887..comments2024-03-26T00:07:20.400-05:00Comments on The Db2 Portal Blog: Consider Cross-Compiling COBOL to Java to Reduce CostsCraig S. Mullinshttp://www.blogger.com/profile/17077237739217901780noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-18371456.post-42372742938241931062023-07-06T08:16:24.334-05:002023-07-06T08:16:24.334-05:00Keep sharing such kind of useful post with us! Get...Keep sharing such kind of useful post with us! Get error-free <a href="https://www.taskade.com/templates/ai" rel="nofollow"><strong>AI Productivity Templates</strong></a> by deeming Taskade.Creative Webhttps://www.blogger.com/profile/03810996335791522391noreply@blogger.comtag:blogger.com,1999:blog-18371456.post-85365514257810513972022-11-18T04:14:14.273-06:002022-11-18T04:14:14.273-06:00You have written an excellent blog. I learned some...You have written an excellent blog. I learned something new from your Blog. Keep sharing valuable information. <a href="https://www.wdptechnologies.com/" rel="nofollow">WDP Technologies</a>WDP Technologieshttps://www.blogger.com/profile/12307301003867466267noreply@blogger.comtag:blogger.com,1999:blog-18371456.post-31650912573915922192022-09-29T05:02:02.572-05:002022-09-29T05:02:02.572-05:00I appreciate you sharing this kind of information....I appreciate you sharing this kind of information. It was a pleasure to read your article and to be informed of the most recent trends and changes. I like the information on this site because it was helpful to me in my research on <a href="https://www.mnscredit.com/blog/identifying-and-mitigating-risks-associated-with-doing-business-in-india/" rel="nofollow">conducting business in india</a>. Keep sharing.Credit Solution To Businesseshttps://www.blogger.com/profile/11752498693845496664noreply@blogger.comtag:blogger.com,1999:blog-18371456.post-53442509078375013442021-04-18T01:45:22.147-05:002021-04-18T01:45:22.147-05:00Good Post. Application ModernizationGood Post. <a href="https://www.comakeit.com/application-modernization/" rel="nofollow">Application Modernization</a>coMakeIThttps://www.comakeit.com/application-modernization/noreply@blogger.comtag:blogger.com,1999:blog-18371456.post-26204367317336949462020-08-05T14:44:05.807-05:002020-08-05T14:44:05.807-05:00Thangaraj... the above reply was from the vendor, ...Thangaraj... the above reply was from the vendor, CloudframeCraig S. Mullinshttps://www.blogger.com/profile/17077237739217901780noreply@blogger.comtag:blogger.com,1999:blog-18371456.post-74516217964094544962020-08-05T14:07:45.436-05:002020-08-05T14:07:45.436-05:00It’s 2020, the phones in our pockets have more mem...It’s 2020, the phones in our pockets have more memory than was available to most mainframe applications in the 70’s, 80’s, and 90’s. Wisely, the inventors of Java recognized that the constraints resulting in the need for COBOL redefines, or C unions, were no longer constraints, and omitted the similar language feature in Java. COBOL procedure pointers, however, are a long-standing construct in all YACLs, which COBOL (is not and) was late to adopt. When rewriting legacy COBOL or C applications in Java, these are examples of the interesting problems to solve by crafting a solution that is intuitive and normal in the Java language, lest the solution carries forward design patterns in Java that are unnatural, unnecessary, confusing, and difficult to maintain.<br /><br /> <br />To address COBOL redefines or C unions, one approach might be to create unique classes for each of the COBOL or C data structures, then encapsulate replication of changes in state amongst the classes with getter and setter functions. While in principle this is simple, in practice this is quite complex due to the extent COBOL redefines are in use. The result also can be brittle unmaintainable code, and one must question what was gained by abandoning COBOL? This is an example where CloudFrame adds considerable value by encapsulating the complexity, eliminating dead code and data structures, and generating highly maintainable and performant code. With CloudFrame, Java developers are not required to understand 60 years of COBOL’s history to maintain a brand-new Java system.<br /><br />Background. The COBOL redefines statement was critically important 30 – 60 years ago, due to physical memory constraints. The C language has a similar construct, known as union. The COBOL and C language solution use the same memory locations for different data structures, contextually based upon data values and application logic. Though only one data structure is valid at any one instance. For example, a 1K input record may be a header, transaction, or footer record, all uniquely identified by byte 10 of a data structure common to all records. Using COBOL redefines enables the program to need only 1K of memory to process any of the records. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-18371456.post-90389727542905835982020-08-04T14:34:14.474-05:002020-08-04T14:34:14.474-05:00Great explanation and very interesting. I have bee...Great explanation and very interesting. I have been working on a large scale COBOL to Java project. Would like to you how does COBOL pointers are handled in the converted Java? And How are the crazy redefinitions possible in COBOL are handled in Java?Thangarajhttps://www.blogger.com/profile/11118596109099810970noreply@blogger.com