Can you add this to the list of links you get when click your login name (upper right corner)? ... View more

You can use the Migration Wizard (MigrationWizard.exe in the EG application directory) to update your EG projects to have the correct library reference when names/libnames change. I'm not sure what DI Studio does, but I doubt that it references the metadata ID of the library.  That value is "volatile" and can change when you migrate content from one metadata environment to another, and that's why EG doesn't use it.  Then again, DI jobs are stored in metadata and thus participate in metadata migration, so perhaps it can reference the ID safely.  EG projects are not metadata objects -- they are external files -- and that's why you must use the MigrationWizard to fix them up when a library name or server name changes in your environment. It's almost a philosophical question. Which is the more "definitive" name: the library object name or the libref?  SAS programs rely on the libref, traditionally (aside from the META engine, which uses the library name).  But clients such as SAS Management Console, Information Map Studio, and even EG show you the library name first, and you must dig to find the libref if it's important to you. Here's what I do.  These are my general practices as an amateur SAS admin.  Others may have experiences/requirements that conflict with these guidelines. - if possible, make the library name and libref the same.  But you sacrifice human readability of the library name. - if they must be different, try to make the libref a derivative of the library name (so that you can guess one given the other).  Example: "Human Resources" (name) -> "HR" (libref).  In many cases, the libref is legacy: you already have production programs that use it.  So your only discretion is in how you provide a "friendly name" on the object. - do not define the same libref in two different library objects.  Sometimes people do rely on this trick though, partitioning the metadata permissions so that one segment of users sees one definition, while a different segment sees the other.  That's valid, but you must recognize the potential conflict when users overlap these segments. - likewise, do not use the same library name in two different library objects.  Ideally the management console would make this difficult to do, but I think it is possible to get in this situation.  Because the name (not libref) takes precedence for most metadata-centric operations, having duplicate names can cause confusion, if not serious problems. Chris ... View more

try this.... filename test "c:\test_file.txt"; data _null_; set your_sas_dataset; file test dlm="|"; put var1 var2 var3 var10; run; ... View more

Hi Scott, you can modify most of those location in SMC under “Foundation  Services Manager” Example for Remote Services Some of the ones you had listed may work and other may not. The ones that don’t you have to modify the <SAS_CONFIG> \Lev1\Web\Common\LogConfig files Take care, Sunshine ... View more

Hi All, Thanks for all the replies, much appreciated. However, they all addressed *how* SAS works with respect to data step views, which I had already deduced.  I was more interested in people's opinions of *how* they thought SAS should work. I must admit I don't recall ever creating a data step view using a variable list but, as Howles said, the variable list in the data step view is static as defined at compile time.  And the same behaviour holds for data set lists. I know the data step view is a compiled object where the definition is compiled, but the data is dynamic and derived at run time.  I guess the question is, should variable lists and data set lists in a data step view be dynamic as well?  After all, it's just software; SAS could have created this to work in either way. IMO, dynamic variable lists and data set lists would be very useful, but I admit it could also cause confusion / problems if the data set structure changed after the view was created.  But, if I had to choose, I would make the variable lists and data set lists dynamic, where the data step view derives the list at runtime.  I suspect the current functionality was just "easier" when data step views were first developed. In any case, I find the "describe view" functionality to be misleading; I believe it should return the expanded lists as they were defined at compile time. Regarding the various replies, I could either just redefine the view each time, rather than defining a permanent view, or use the dictionary tables.  As suggested, I did choose to use the dictionary tables, as I found the generated code to be clearer.  But the results are the same in both approaches. Thanks Scott ... View more

Scott surely it is not a good idea to code like      where put(monthStart,yyq.)='2011Q1' when  it demands that a PUT() function be applied, especially as there is an equivalent without that function      where monthStart between '1-jan-2011'd and "31-Mar-2011"d These date constants can be generated as easily as 2011Q1. The alternative filtering  for months and years are as easy. ... View more

See if an old sas-l posting of mine helps. ... View more

Disagree is a strong word... it seemed in your description that only processes that might lock table were other ETL-processes. In this case, a proper scheduling will be enough to avoid locking. I can see that there can be other cases when on-line ad-hoc jobs are locking tables i.e. in Enterprise Guide. These kind of problems might need some other techniques, such as shutting down workspace servers, kill servers processes etc. These situations are probably easier handled if the data store resides in a data server environment, such as SPD Server, or other external RDBMS. /Linus ... View more

in 9.2 + Rather than impersonating you can (as an unrestricted account) look at explore authorisations on the objects Authorisation Tab, advanced button. You can see the effective permission of a group or defined user, similar to Effective permisison tab on the Windows OS. Barry ... View more

A warning with the copy, and then deleting the old objects.  The copy creates new object ID's so any thing using those old tables objects will break. Another example of where the interfaces are different between the SAS Clients, why isn't there a Move to folder in SMC like there is in DIS. Barry ... View more

Maybe I'm oversimplistic in my thinking  - but it seems like you could collect the prompt value and then just use a something like a CAT function to build the Where statement.  How you build the code to support the prompt may require some fancy footwork if it has a lot of options. *Note this coding is not exact - just communicating the idea. data _null_; TEMP_STMT=cats("Where ", " product=","&ProdPromptValue", " and ", "count >", "&CountPromptValue"); call symput ("where_stmt", temp_stmt); run; %your_macro(&where_stmt.)                Curious to know if this will work and if not what you did figure out. Tricia Blog: Notes for SAS BI Users ... View more