Tom,
No problem..I want to head our products toward 64bit ..So changing our existing COBOL code was my first choice. But it looks like I will head us for C or C++ with Assembler called routines. But I appreciate the email for sure. Regards, Scott www.identityforge From: Tom Ross Sent: Monday, October 20, 2014 8:28 PM To: IBM-MAIN@LISTSERV.UA.EDU Part of the reason for going to a new backend (code generator/optimizer) in COBOL V5.1 was that the new backend already supports AMODE 64. This is another step in the direction of AMODE 64 COBOL. The first steps were to get infrastructure in LE, get AMODE 64 support for COBOL into plan for CICS, DB2 and DFSORT, and make sure that all of the players are playin'! AMODE 64 COBOL is already in our plans, but it is not going to be in V5.x. Sorry, we are working on it, but we may be too late to help you Scott! Cheers, TomR >> COBOL is the Language of the Future! << >Scott - I think that only enterprise cobol 5.x support 64 bit natively. > >Sam > >On Thu, Oct 16, 2014 at 7:17 AM, Scott Ford < >00000006f84450fa-dmarc-requ...@listserv.ua.edu> wrote: > >> All, >> I have a generalized design question. First background will help. Our >> products run as Enterprise Cobol STC, no multi-tasking, yet. We call hlasm >> subroutines. I would like to use 64bit storage for some functions from >> Cobol. Is this feasible. I think it is, where I am unclear is the call and >> binder parameters. Do I have to do anything special parameter wise ? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
