In reply to Chris Hemedinger.

I have found that inserting "data _null_; run;" ahead of a new macro definition will eliminate the above issue.