> SYNADAF provides the DDname, which is sufficient Not when the dataset is dynamically allocated. I would not expect the OP to have a clue what dataset SYS00001 is. That said, I consider this to be a case of missing information rather than an issue with the data in the message; what needs clarification is the referent of "WRNG.LNTH.RECRD"; IMHO changing the text to "Wrong Length Record" would serve no purpose.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List <[email protected]> on behalf of Steve Smith <[email protected]> Sent: Sunday, April 14, 2019 5:06 PM To: [email protected] Subject: Re: Lousy error from HLASM in USS SYNADAF provides the DDname, which is sufficient. I see no good reason to complicate code that runs so rarely. Adding features to ancient interfaces would need to show a significant payback potential in my book, and I'd bet IBM's book is tougher than mine. The HLASM team is responsive (to a fault - e.g. ILMA), and they can fix this themselves (i.e. with a better error for WRNG.LNTH.RECRD). Seems to me that would be the way to go. sas On Sun, Apr 14, 2019 at 4:00 PM Seymour J Metz <[email protected]> wrote: > If IBM accepts an RFE for SYNADAF to provide dsname, member and path, > they will need to do so in a fashion that does not break existing code. > That means that the callers will still need new code to exploit it. > > Long messages don't bother me. > > No, a one line primary and an optional one line secondary is all the > SYNADAF currently provides. > > > -- > Shmuel (Seymour J.) Metz > http://mason.gmu.edu/~smetz3 > > ________________________________________ > From: IBM Mainframe Assembler List <[email protected]> on > behalf of Paul Gilmartin <[email protected]> > Sent: Sunday, April 14, 2019 3:52 PM > To: [email protected] > Subject: Re: Lousy error from HLASM in USS > > On 2019-04-14, at 12:52:27, Seymour J Metz wrote: > > > I approve of using the message text from SYNADAF, but Shirley it would > be reasonable to include dsname, member and path > > > SYNADAF should do that, not its caller. > > Various IBM docs specify PATH_MAX as 1023. That could result in long > messages. > > > ..., when relevant. Also, does ASMA999U include the secondary message > from SYNADAF when the primary message buffer ends in "S"? > > > If the message should be so long, can the secondary message end > in "S" to indicate a tertiary message, etc. > > > 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. > > > Thanks. Lots for the OP to RTFM. > > -- gil > -- sas
