> Kind of irrelevant, because in z/OS BSAM/BPAM detects the problem and HLASM > never sees it.
Of course HLASM sees it; where do you think the ASMA999U message comes from? The issue is what other information HLASM should provide to establish context and whether (IMHO, no) HLASM should interpret the SYNADAF text instead of displaying it. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Monday, April 15, 2019 1:27 PM To: [email protected] Subject: Re: Lousy error from HLASM in USS On 2019-04-15, at 10:28:03, John McKown wrote: > Hope I'm not too off-topic on this discussion, but now I'm curious what > Dignus' Assembler, DASM, would report in this instance. > They provide a web-based trial, http://secure-web.cisco.com/14l4apiijJ5GoM2Nb7GavQ-2WJwOC-IVOMWvPrBshnWYd5ujCB0EtMjXr6q6nxGB6qMzegHo_teoMG3wL5oRga-9gUxKKHztmVNZMBQ5ryRDF5UcQEdRGuMM_SUpt9clINtFLJvUJIE79kDAnjtMYeHab4Cw4S6sWpOC19nbICcdVDLakmFSU_tFHQGWHHMK3Hd3J6O8GG5xRERmCuoA3FGGnPq3qhn8snQsYNnd5eSD0anMlGBzb5f8du_WmAKn-cUKx5lrLN7PM9AZRL9Bs6vBjDGWrC_jAucRxgKAfd9MxmjW7sz0_18wwWZkci4J6exw5wZu4WT_cDycxKXjQlsE2XCLy6u02wIHgNCWwJ_FomImx1BDJVo7DYtuQRrOt/http%3A%2F%2Fwww.dignus.com%2Fcgi-bin%2Fassemble.cgi which for: START DC C'..|....+....|....+....|....+....|....+....|....+....' ...+....|junk END ... reports: Assembler command & output (error/warning messages): dasm -flisting=/tmp/1265.lst /tmp/t1265.asm DASM Dignus Systems/ASM - version 1.95.11 (c) Copyright Dignus, LLC 1994-2019 All rights reserved. DASM is licensed to Dignus,LLC (Linux). dasm: /tmp/t1265.asm line 2:DASM900W Input line too long, truncated dasm: /tmp/t1265.asm line 2:DASM144E Begin-to-continue columns not blank dasm: /tmp/t1265.asm line 2:DASM435I Record 2 in /tmp/t1265.asm dasm: /tmp/t1265.asm line 2:DASM140W END record missing dasm: /tmp/t1265.asm line 2:DASM435I Record 2 in /tmp/t1265.asm DASM Return code 8, 2 Warnings, 1 Error, elapsed time 0.00 seconds, object code size X'34'. Kind of irrelevant, because in z/OS BSAM/BPAM detects the problem and HLASM never sees it. What does HLASM under Linux for z do? -- gil
