It's as much as I can do just to spell CoBOL but, as far as I can tell, it's
not ready for prime time. Even its most avid proponent signs off thus:
TomR >> COBOL is the Language of the Future! <<
We are trapped in the present. We cannot get to the future. The nearest we
can get to the future is the latest, most recent, current instance of the
present. Ergo, CoBOL is not for us.
'Nuff said!
;-)
===
> Date: Thu, 16 Oct 2014 10:17:56 -0400
> From: 00000006f84450fa-dmarc-requ...@listserv.ua.edu
> Subject: 64bit
> To: IBM-MAIN@LISTSERV.UA.EDU
>
> 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 ?
>
> Thanks as always,
>
> Regards,
>
> Scott ford
> www.identityforge.com - www.idmworks.com
> from my IPAD
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
