I approve of using the message text from SYNADAF, but Shirley it would be reasonable to include dsname, member and path, when relevant. Also, does ASMA999U include the secondary message from SYNADAF when the primary message buffer ends in "S"?
The HLASM Programmer's Guide should have a reference to, e.g., z/OS DFSMS Macro Instructions for Data Sets for the format of the SYNADAF data. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Peter Relson <[email protected]> Sent: Saturday, April 13, 2019 9:57 AM To: [email protected] Subject: Re: Lousy error from HLASM in USS I'd guess that you get this same error from a lot of places in z/OS, just not with ASMA999U as the prefix. Searching for "WRONG LEN RECRD" gets a lot of hits. Perhaps you ought to focus on the area that is likely to be changed (the documentation) rather than one that isn't (the code). The doc for ASMA999U ought to be improved. It should mention this extra information courtesy of the SYNAD processing (or at least point to a place where the extra information is described, and that description ought to explain what it means and in this case give some of the obvious examples). Peter Relson z/OS Core Technology Design
