Re: Lousy error from HLASM in USS

2019-04-12 Thread Paul Gilmartin
On Fri, 12 Apr 2019 09:23:40 -0400, Steve Smith wrote: >I think the grumpiness and sarcasm might be a bit over the top. The error >does have roots going back to the middle ages, > IBM should operate a booth at Renaissance Faire. Or Comic Con. > ... that when combined with >modern functionality

Re: Lousy error from HLASM in USS

2019-04-12 Thread Steve Smith
I think the grumpiness and sarcasm might be a bit over the top. The error does have roots going back to the middle ages, that when combined with modern functionality, causes some odd results. Anyway it's something that doesn't happen very often. If IBM thinks it's worthwhile, they'll improve it.

Re: Lousy error from HLASM in USS

2019-04-11 Thread Paul Gilmartin
That should have been cross-posted to ASSEMBLER-LIST and MVS-OE. On Thu, 11 Apr 2019 19:47:56 -0400, Phil Smith III wrote: >Easy to reproduce. Create an assembler input deck with a line longer than 80 >bytes; it can even be a single line: >*

Re: Lousy error from HLASM in USS

2019-04-11 Thread Charles Mills
Post to the  HLASM list which the development lead monitors. He is very responsive. CharlesSent from a mobile; please excuse the brevity. Original message From: Phil Smith III Date: 4/11/19 4:47 PM (GMT-08:00) To: IBM-MAIN@LISTSERV.UA.EDU Subject: Lousy error from HLASM in

Lousy error from HLASM in USS

2019-04-11 Thread Phil Smith III
Easy to reproduce. Create an assembler input deck with a line longer than 80 bytes; it can even be a single line: * x (that x is in column 81) Put it in a USS directory as, say, bad.asm. Now cd to that directory in a sh