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
