Ref: Your note of Sun, 14 Apr 2019 17:06:00 -0400 The SYNADAF information returned by the access method is all HLASM knows about the error. To produce a more "intelligent" message HLASM would have to parse the SYNADAF information itself, which would be complex and error-prone yet provide very limited value.
The SYNADAF message format has hardly changed for decades, and compatibility considerations mean that any enhancement is likely to require changes to the calling code to enable and exploit it. For coding errors associated with a particular input record, HLASM is usually able to issue an ASMA435I message identifying the record affected, including more details about the data set and member. However, I/O errors are rare and unexpected and cause HLASM to abort, so the I/O error routine is common for all types of file (input, output and work files) and is as simple and robust as possible. I agree that the documentation of ASMA999U could be more helpful in pointing to the documentation of the SYNAD message. I guess that in the past the term SYNAD would have been more familiar to Assembler programmers. I also see that the documentation says that a dump is produced, but I'm fairly sure that has never been true for HLASM. So I've noted that we should look into improving the documentation of that message. Jonathan Scott, HLASM IBM Hursley, UK
