Thank you. We opened one 2 weeks ago , but still not finding a way to solve this. ... View more

we tried to distinguish whether the error occurred because of the code, using only /**/ as STP code.The answer is no. Is there any other way to test or solve this issue? ... View more

@AllanBowe     Using a graphical interface to create a new STP . After pressing "Finish" button in the wizard, the STP will be run.   ... View more

when calling it for testing   ... View more

Hi @AnandVyas    Thank you for your prompt reply. we have checked the identity YYY in source server and target server are the same, just the login info is different .  Will the following cases hit the same error ? By the way, We are in the case of 1. case 1 Source server: identity YYY  login domain\aaa Target server: identity YYY login missing (registered before)   case 2   Source server:identity YYY login domain\aaa Target server: identity YYY login domain\AAA   ... View more

Thanks @FredrikE !   It's a simple way to export properties of data sets.(I think it is the same data as those in dictionary.tables and dictionary.columns) However, I'm afraid that those data are not enough to help me tell which data set is in use or not.   ... View more

Thanks @Kurt_Bremser !   May I understand it like that the information in dictionary.tables and dictionary.columns is all the visible property data of data sets to the sas workspace server?  ... View more

@ybolduc  Thank you for your reply.   I mean the association between library and registered table.   In generally, after we registering a dataset stored in a library with a SAS folder, we can find that registered table displaying in the SAS folder. What happen if the registered table lost its association with its original library, for instance, its physical table or library has been deleted ? The registered table will leave in SAS folder as trash, because users will not be able to open and use it anymore. To classify and manage the registered tables, I am trying to list up all the registered tables and find out their original libraries. At present, I am facing the following 2 problems that really need your help. 1, how to detect the existence of registered tables in enterprise guide   Be based on my knowledge, I found that   If a registered table had a connection with a library(even if lost the connection in recently),   then it still can be found in a SAS folder in EG.   If a registered table had never ever been assigned to a library, then it will not appear in EG. 2, If the registered table appeared in enterprise guide, then look up its library.   Is there any methods can solve my problems. BTW, if my explanation makes you confused, please let me know.     ... View more

Thank you for your post. That’s a solution when there is only one table name required to search for its library name. However, I am still seeking a more efficient way to help me to read out all the library names for a long list of registered tables. I tried to write a loop macro(please check the attachment), basically using the macro that described in  http://support.sas.com/kb/37/386.html , but it doesn’t work. Further more, I found another problem that some registered tables are not appearing in the SAS folder, but displayed in the Management Console. Is there any solutions or suggestions? ... View more

@Patrick   Sorry for my unclear expression. The missing data is the original location(library) of the metadata tables before they are registered. For example: Suppose a table named【Demo】, stored in a pre-assigned sas library【LIB】, were registered in a sas folder【Shared folder】. Although %mdsec macro can give me a location of the sas folder【Shared folder 】, what I need is the original location【LIB】 of the table. Is there any sas code to extract that kind of data?     ... View more