Based on information I have found on other sites and a SUGI paper written by Paul Sherman it appears that ERROR messages like "NOTE: Invalid second argument to function SUBSTR at line nnnnn column nnn" are actually indicating macro BLOCK and COLUMN rather than open code LINE and COLUMN.  My question is, if I turn on MACRO options like MPRINT or MGEN or MLOGIC how can I determine the block numbers in the output.  Is there some undocumented automatic macro variable like &SYSMACBLOCK that I could %PUT to the log to identify more closely which of my generated statements is generating the note when I have lots of SUBSTR calls?  ... View more

I am trying to add a TARGET= to a URL generated in a PROC REPORT with CALL DEFINE so that the generated hyperlink works correctly in a framed environment.  There does not appear to be documented way to do this that I have found.  I have seen some references to modifying the style template but have not found any working examples.  I tried fooling the system by including double quotes in my CALL DEFINE to extend the generated HREF which almost worked, but the actual html converted the buried double quotes to &quot; which did not work when displaying the page.   compute link;   href=cat("&htmlbody..html#",trim(scan(path,-1,'\')),'" target="body');   call define(_col_,'URL',href); endcomp;   Results in this HTML:   <tr> <td class="l data" style=" border-width: 0px;"><a href="BODY.html#Report#16&quot; target=&quot;body">Messages by Severity</a> </td> </tr>   which does not work properly.  Any suggestions on how I can generate a proper target="body" with CALL DEFINE? ... View more