Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Tom Marchant
On Mon, 13 Apr 2015 10:22:40 -0700, Sam Siegel wrote: Agreed. There are good and bad on both sides of that line. This reminded me of something that Phil Payne wrote several years ago. Hope you find it amusing. Tom Marchant Subject: Re: (OTR) Fixing the user From: Phil Payne

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Scott Ford
It's like one of the hardware networking guys telling me that the router tables can't be corrupted. This happened right after they applied a router firmware/software fix, my reply 'say what' On Monday, April 13, 2015, Shmuel Metz (Seymour J.) shmuel+ibm-m...@patriot.net wrote: In

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Shmuel Metz (Seymour J.)
In 985915eee6984740ae93f8495c624c6c2368d57...@jscpcwexmaa1.bsg.ad.adp.com, on 04/13/2015 at 09:21 AM, Farley, Peter x23353 peter.far...@broadridge.com said: Please get off that ridiculously high systems programmer horse of yours and join us here in the 21st century. You almost had me their,

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Shmuel Metz (Seymour J.)
In 552bc59e.1010...@vse2pdf.com, on 04/13/2015 at 09:33 AM, Tony Thigpen t...@vse2pdf.com said: Ed must work for the government, or a union shop. No place I ever worked would have allowed such programmers to continue to be employed. I've seen them in commercial, educational and government

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Farley, Peter x23353
: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shmuel Metz (Seymour J.) Sent: Monday, April 13, 2015 10:28 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC In 985915eee6984740ae93f8495c624c6c2368d57

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Ed Gould
On Apr 13, 2015, at 4:16 PM, Shmuel Metz (Seymour J.) wrote: In 552bc59e.1010...@vse2pdf.com, on 04/13/2015 at 09:33 AM, Tony Thigpen t...@vse2pdf.com said: Ed must work for the government, or a union shop. No place I ever worked would have allowed such programmers to continue to be

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Ed Gould
On Apr 13, 2015, at 6:01 PM, Farley, Peter x23353 wrote: I may not have stated that as I meant it - I did try to indicate my meaning by using that . . . horse *of yours* . . ., intending to mean just him and not all. Not well written, mea culpa, but it was a rant. I have encountered

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Sam Siegel
Enterprise COBOL Service to convert ASCII to EBCDIC Ze'ev: Because in most cases programmers are less than lets say bright. If you bring up ASCII you will only confuse them. I suspect they will try and use it in some sort of horrendous fashion, like convert to ASCII and then back. To give you

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Bernd Oppolzer
Somehow strange discussion, IMHO. I´'m sure that there are many bright people in the COBOL community. But: COBOL could well be some sort of biotope for not so well teached programmers. And: most significant software packages on the mainframe that do complicated algorithms and computations (math,

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread John McKown
On Sun, Apr 12, 2015 at 10:46 PM, Ed Gould edgould1...@comcast.net wrote: Ze'ev: Because in most cases programmers are less than lets say bright. If you bring up ASCII you will only confuse them. I suspect they will try and use it in some sort of horrendous fashion, like convert to ASCII and

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Elardus Engelbrecht
Ze'ev Atlas wrote: Why is getting an ASCII piece of information so scary? And why would handling it using proper programming, any scary? Simply, if you receive data, say x'0A0B0CF1F2F3', then how would you see, programmatically, it is ASCII or EBCDIC? With TRT or friends? I had to avoid a

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Shmuel Metz (Seymour J.)
In 2355787451595524.wa.elardus.engelbrechtsita.co...@listserv.ua.edu, on 04/13/2015 at 04:41 AM, Elardus Engelbrecht elardus.engelbre...@sita.co.za said: Simply, if you receive data, say x'0A0B0CF1F2F3', then how would you see, programmatically, it is ASCII or EBCDIC? That isn't an ASCII

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Farley, Peter x23353
of yours and join us here in the 21st century. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: Sunday, April 12, 2015 11:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Standard IBM Enterprise COBOL Service

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Tony Thigpen
: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC Ze'ev: Because in most cases programmers are less than lets say bright. If you bring up ASCII you will only confuse them. I suspect they will try and use it in some sort of horrendous fashion, like convert to ASCII and then back

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Graham Hobbs
[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ed Gould Sent: Sunday, April 12, 2015 11:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC Ze'ev: Because in most cases programmers are less than lets say bright. If you bring up ASCII you

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-13 Thread Ed Gould
On Apr 13, 2015, at 8:33 AM, Tony Thigpen wrote: amen, Peter. Ed must work for the government, or a union shop. No place I ever worked would have allowed such programmers to continue to be employed. Of course, on second thought, I have seen some really, really bad stuff coming out of the

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-12 Thread Ed Gould
Ze'ev: Because in most cases programmers are less than lets say bright. If you bring up ASCII you will only confuse them. I suspect they will try and use it in some sort of horrendous fashion, like convert to ASCII and then back. To give you an idea how stupid programmers can be a S0C7

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-12 Thread Ze'ev Atlas
Because in most cases programmers are less than lets say bright. Oh, I see... I guess that this is why my rate when I program in lowly Access VBA is higher then anything COBOL programmers could get. I am not even trying to compare that to my rate when I write Perl, T-SQL, PL/SQL, etc. They

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-12 Thread Ze'ev Atlas
to summarize the conversation: I don't know what is scarer letting ASCII loose in the environment or letting programmers know about it. Not to alarm you further, but I believe it's already endemic. Not in any company I have ever worked. Why is getting an ASCII piece of information so scary?

Re: Standard IBM Enterprise COBOL Service to convert ASCII to EBCDIC

2015-04-12 Thread Ze'ev Atlas
Thank you all to those who've pointed me to NATIONAL-OF and DISPLAY-OF intrinsic functions. For some reason I missed them when looking at the list of intrinsic functions. While calling the C runtime library is an interesting exercise, using native COBOL functionality when in COBOL is superior.