One could have used NATIONAL-OF built-in function in Enterprise COBOL to exploit Unicode Conversion Services: http://www.ibm.com/support/knowledgecenter/SS6SG3_3.4.0/com.ibm.entcobol.doc_3.4/igyc1uni.htm -----Original Message----- From: Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> To: IBM-MAIN <IBM-MAIN@LISTSERV.UA.EDU> Sent: Mon, Dec 19, 2016 4:47 pm Subject: ASCII<->EBCDIC (was: convince programmer something else is better.)
On Mon, 19 Dec 2016 08:35:33 -0600, Peter Vander Woude wrote: > >Our programmers used to use a cobol to read in a file, for ebcdic to ascii >translation, and then this subprogram would be called for each record to >convert from ebcdic to ascii. The job steps calling that routine spent over >90% of their cpu time in that subprogram. > >I re-wrote into hlasm, and eliminated at least 80-90% of the cpu time, just >due to the efficiencies that the assembler code management of the data in a >table, have vs cobol. > And that conversion is built in to the z/OS UNIX kernel if the proper incantations are performed. -- gil ---------------------------------------------------------------------- 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
