all prompts in visible in the whole the branch will pop-up once at the start when you do a run. What is the problem with that?    ... View more

Jason, please explain your question.  For the auth-domains you will find in the sas- docs examples like oracle that is a tool naming not a domain naming. You could possible integrate local managed installations by eg LDAP.  By that all tools will go into one security-domain. -> Avoid the naming associated to tools. When this association by tools happens (made wrong decision) you can get into that several external security providers are sharing the same authdomain. when both are setting policies using the same accounts with different policies you have a confliction situation by the logical flow of information.    The other nasty problem is also a logical one. You can design processes using a shared account to be used (SP WS) at he moment you needing to do some updates at setting OS security or updating some shared files you login (DI Eguide) with that shared "high privileged" account. You will get the security setting as valid for "general servers". The question of Jan is related to release management (vertical line DTAP SDLM ALM) not the be confused with version management (horizontal line development).  Mixing operatios (OracleProdAuth P) and developers (oracleDevAuth D) with test data and production data in the same metadata-database is not a very good approach. Do you know the contents of those ISO 27002:2013 guideline? Starts after 27001  It is about risk-management, an introduction to that could be: Cybersecurity and Managing Risk   The first action is building a simple normal defense ....  (than get to 14.2.2 of 27002).    ... View more

Correct Scott, it is batch processing for enterprise environments. Think at 100+ users.  As Anant is mentioning 10000 that is a fit.  With that number of users have a look at metacoda (Paul / Michelle Homes) Synchronizing SAS Platform Identities - platformadmin.com . These are built around the same macros-s. Extracting the metadata is more easy to start with, just retrieving.  SAS(R) 9.4 Intelligence Platform: Security Administration Guide, Second Edition It shows the tables that are in used and could be modified. The tables are identified by that keys-id SAS(R) 9.4 Intelligence Platform: Security Administration Guide, Second Edition that must be unique.  This one is not commonly filled when doing manual updates with SMC. When left blank they are excluded. As you probably are having an IAM system (central user registration) you could use those convention that are in place (unique keys person-id's)  ... View more

Windows is more easy than Unix, Must us be really SSO or is it allowed to save *hased" keys to simulate that. ... View more

Ballard and the HASH package within DS2. Many procs  that could be seen as packages and yes with IML you could use R packages .  ... View more

The SAS data_step is the only part you are taking into account for comparing SQL/SAS? That is very limited one. SQL was invented for OLTP and it has the limitations and advantages involved for that. SAS was invented for analysis with those limitations and advantages. You can do al lot in the SAS datastep (pointering) that is not possible with SQL due to the fact SAS is processing all the data sequential and SQL is doing it in subsets. The performance behavior is also totally different. ... View more

Ankit, You are right it is a omission. The only  things I know that could be similar are at SAS(R) 9.4 Intelligence Platform: Security Administration Guide, Second Edition. This information should come from SAS-institute with a description not only how to implement but also what are possible risks and what to expect to get aligned to common IT security policies as of regulations. ... View more

http://support.sas.com/documentation/cdl/en/pcfsicg/67728/PDF/default/pcfsicg.pdf see page 42-43  it looks like some settings to enable that authenitication are not done/present.  Without user/password it only can access the account the pcfilesserver is running on. Giving a user/password it should verify and switch user context only possible with very high system privileges. Seems a reasonable explanation. It is not nice just that dump is coming.    ... View more

Alex of course that will be slow as you are causing a lot of IO may be even network related. That can become easily a trashing one. Trashing is the system will become very busy but hardly doing any real work as it mostly trying correcting interrupts for doing work. Imagine you have 20 managers continuously asking for how the work proceeds but giving no room to do any work.  The problem is not the coding but understanding what is happening by that code. Advices: - try to avoid copying. Moving is much faster. Moving and Replacing Files (Windows) there is a move command.  https://technet.microsoft.com/en-us/library/cc772528.aspx   The difference is that is not copying data but instead will try to move the pointer to the data in the filesystem so it will appear within another directory. (renaming) - run the commands in xsync (symchronous mode) to prevent that too many processes are started running at the same time. You could create some lists that could run in parallel (3-4 max)  and start those separately. - those very long names should be no problem using unc names. No need the split those and using drive letters. - Assuming you have sas-datasets than use the sas "proc copy" with move option. - having libraries to new non-existence directories use: "options dlcreatedir"  ;      New directories will be createn as soon being used with those libnames. - Yes, you can mix drectories with different types of data sas specific and non-sas types (eg pdf word text)  at Windows/Unix (no not classic mainframe) . That is often more complicating than simplifying the job. Each SAS version is having a unique structure an version types may not be mixed. Think on placing the SAS specific types in segregated directories.  ... View more