@s_lassen, yes, you are essentially correct in your surmise that dll's are what is listed in an RTRACE log, but it's just a bit more complicated than that.
The RTRACE log lists every file reference. For example, whenever a dynamic load library, a dll, is referenced, an entry is placed in the log. When I analyze the RTRACE log, I:
- Get the name of the .dll by parsing the text in the log.
- Use the name of the dll (sans extension) with the data step function TSLVL. TSLVL returns the SAS product code, an alphanumeric string 3 to 12 characters long. The product code is however in many cases not particularly helpful. For example, "dtdrodbcmssq." To me, it's not exactly intuitive which product the code "dtdrodbcmssq" represents. As it happens, "dtdrodbcmssq" represents DataDirect ODBC Driver for Microsoft SQL Server.
- So, after one has the product code, one has to translate the product code to the product name. I don't know of a function for this. 😞 What I do is I run sas.tools.viewregistry.jar which produces an html report that lists the product codes for one's installation -- and their corresponding product names. I then use the names in the html report to create a SELECT-WHEN block of code in a data step, an unfortunately manual process, and, to make matters just a bit worse, not every product code is listed, hence my original question regarding a master list of product codes and their corresponding product names.
One good thing here is that one can see from the RTRACE log which folder each dll is in, giving one at least a general sense of what category a given dll is in. If one is using SAS Enterprise Guide, one can also look at WORK._ProdsAvail which has more information about installed products, their names, and their codes.
Based on the folder structure(s) and the information in WORK._ProdsAvail, I agree with you that cbase and basecom are part of the base product (they are both in the "Core" folder) and that rlink is part of SAS/Connect. Still, it would be nice if there were a master list somewhere, or, even better, a SAS function that returns the product name based on the product code. There may be such a function; I'm just not familiar with it if there is.
Lastly, your idea regarding using RTRACE without an RTRACELOC is a really good one. One can see exactly what is called in the chain of events if the RTRACE is stored in the same log as everything else. I hesitate to set this up as part of a Production configuration because it could make the regular SAS log quite lengthy and difficult to interpret for the average person. However, if one sets up RTRACE as part of a command line instantiation, it should be a good and useful technique, so I thank you for that.
Jim
