try the getattr() metadata function. Feed in the &transformID variable to return the name of the object. http://support.sas.com/documentation/cdl/en/lrmeta/60739/HTML/default/viewer.htm#getattr.htm ... View more

If you are using Platform Process Manager you can also parse the logs from this. It will include the job and flow, return code, metadata id of the job, start and end times and cpu time. ... View more

Custom code stored in Metadata is in the TextStore of the Metadata server. Use GetMetadata to view it and choose SourceCode. ... View more

Not that I can remember. I think you have to write your own. I remember that SAS had a java example on the DI site for 3.4 some time back. You could possibly check that out. ... View more

Have you tried highlighting each node in the process and copying? I'm pretty sure that used to work ... View more

If your using 4.x version check out the reports built into DI. There is a report that will output job, table, transform information. Otherwise I had success in the older version using Doxygen and placing doxy friendly tags in metadata notes. Hope that helps. Cam ... View more

Are they SAS datasets in the same library? If so, then the following may work; Run Proc Datasets to rename the file to a filename that is consistent all the time run proc metalib before beginning the job to register the sas dataset in metadata. Particulary if the dataset is new or has changed columns. Execute your job using the new dataset name as your source If you need to keep the original name of the dataset, run proc datasets again at the end to name it back The same logic can be applied with text files but instead, you just need to rename the date-stamped text file to something consistent with either a filename pipe, systask command or an x command. Hope that helps. ... View more

The metadata server is a fresh configuration. We have literally had 9.2 for a week. I'll definitely look at the logging feature however. Thanks for the advice ... View more

We did something similar in the appserver autoexec with 9.1. We recorded the Process ID, Work Path and User ID etc. Basically whenever a user initiated a session with SAS from any client application that used the autoexec you got a record. The dataset grew really fast and we had some issues with causing DI jobs running in parallel to fail. It was fun to see the people who like to open 10 sessions of EGuide at once though 🙂 ... View more

Thanks for the advice Chris. All of our users are running XP however they all have hardware acceleration. I tested the turning off of tabs and changing to open type fonts and found at least on my machine an improvement. I'll keep researching and hopefully come up with some answers. Thanks again. ... View more

Hi, We have just installed the 9.2 environment so I will have a look at the new custom transformations. Thanks for the reply. ... View more