Hello,
When I transport a job from one environment to the other in DI Studio the SPD Server Table Loader Transformation in the environment I imported the job into autogenerates a libname statement which is just wrong and throws an ERROR - I could of course comment the statement out but there seems to be an option set in one environment which enables this autogeneration of the libname statement - anybody an idea which option I have to set?
Kind Regards
Criptic
First step is to compare how the libnames are defined in respective environment.
Also, be sure when you import the job that librefs are mapped to the correct one in the target environment.
Put the generated libname statemnts side by side, determine the difference, and find the setting in metadata.
Or is it even that you don't get a libame in the source environment (pre-assigned)?
First step is to compare how the libnames are defined in respective environment.
Also, be sure when you import the job that librefs are mapped to the correct one in the target environment.
Put the generated libname statemnts side by side, determine the difference, and find the setting in metadata.
Or is it even that you don't get a libame in the source environment (pre-assigned)?
Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9.
Lock in the best rate now before the price increases on April 1.
Need to connect to databases in SAS Viya? SAS’ David Ghan shows you two methods – via SAS/ACCESS LIBNAME and SAS Data Connector SASLIBS – in this video.
Find more tutorials on the SAS Users YouTube channel.