LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (May 1999, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 17 May 1999 10:17:08 GMT
Reply-To:     David Johnson <david_h_johnson@HOTMAIL.COM>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         David Johnson <david_h_johnson@HOTMAIL.COM>
Subject:      Re: Stored Compiled macros, multiple catalogs
Content-type: text/plain; format=flowed;

Thanks to Peter Crawford for his reply to my query on multiple catalogs for stored compiled macros.

Reiterating the problem: in an object oriented environment we wanted to have multiple catalogs containing stored compiled macros according to their subject area.

Conceptually, since SAS supports concatenated library references, you could start a session with the SASMSTORE option pointing to such a reference. It doesn't work, for reasons that should have been obvious when it was first conceived. A stored compiled catalog has the SAS file name of SASMACR. The read process for SAS using concatenated references finds the first occurrence of each SAS file name for each Member type.

Therefore, only the first SASMACR catalog will be found and the SAS System will search only that file for the entry name associated with that macro call. If it is not found it will NOT then search for any more SASMACR catalogs before reporting that the macro reference is not resolved.

There is no immediately obvious solution for catalog concatenation unless a single composite catalog is created. For our site this means even more austere naming since the first character will need to reference a subject area for the source code, and the description include up to 8 characters for a catalog subject name.

Much as I really dislike hanging my hopes on future unseen untested releases, it seems I must wait on version 8 for 40 character entry names.

Thanks again Peter, you've saved me wasting too much time on this.

On a related issue, has anyone found a way to clear the SASMSTORE related library reference? Issuing an OPTIONS statements will let you changed the SASMSTORE library reference from FRED to GINGER. GINGER will then be searched for macros and not FRED, but FRED is still flagged as being in use and can't be cleared or reassigned. Looks like a :feature: to me.

David

/*---------------------------------------------------------+ | David Johnson SAS Contractor, @ client site | | +44 (0)7050 65 6406 | | The content of this email is the personal opinion of the| | writer and does not reflect the policies or opinions of | | the client. | | Please reply to questions posted to SAS/L directly to the| | authors return address. This address is NOT registered | | with any of the SAS/L listservers. | +---------------------------------------------------------*/

______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com


Back to: Top of message | Previous page | Main SAS-L page