LIBNAME <libref> list;%*list path associated with specific libref; LIBNAME _ALL_ list;%*list all assigned and sys-allocated librefs; FILENAME <fileref> list; FILENAME _ALL_ list;%*list all user-assigned filerefs;

I usually assign all libnames and filerefs in my autoexec(s).

for those lost in space, whilst debugging and head-scratching one could insert, -- and consider deleting later! :-) -- these statements as a Reality? Check!

Ron Fehd the macro maven CDC Atlanta GA USA RJF2@cdc.gov

-----Original Message----- From: PBourdages@IAG.QC.CA [mailto:PBourdages@IAG.QC.CA] In fact, when writing SAS Standards for my corporation, I specificaly wrote about the subject. Work, SasUser and Srever Libraries... What a mess. But what a joy when people write down exactly the lib reference. Easier to maintain code. -----Message d'origine----- De : Nicholson Warman [mailto:newarman@OFFICE.UNCG.EDU] This is the same religious argument as whether you should use library-free SAS dataset references vs. qualifying with WORK. Example:

DATA MY_DATASET; ...

versus

DATA WORK.MY_DATASET; ...

Having had to go through (what felt like miles of) production code to find where the library reference was wrong, and having to make allowances for code where SASUSER was mixed with WORK BECAUSE THE ... LIBRARIES WERE THE SAME!!!! I really recommend the qualification of libraries for SAS datasets. At least that way, you can use utility programs and/or FILEFIND tools to look at all references to a SAS dataset, so that you have SOME hope (say at 2AM with a user screaming in the telephone) of finding what is broken.

Can you tell that both are pet peeves of mine? ==================== Marcus of B5: "I've found that a kind word and a 2x4 are more effective than a kind word alone."