Ronan, That are good additions.  I could add the following on sassrv and the StoredProcess Part. The need to avoid using a generic sassrv is mostly a result of the business requirement to have a well secured enviroment. Running everything by sassrv is a possible backdoor for hackers intended and unintended. The bisecag (and others) is filled with cautions to have your hostlayer controls (security) well defined. The SP-s are running by a dedicated key that is needing host acces. It is following: Category:Principle - OWASP This key for the SP must be defined as login at the "general servers" group. Sounds strange, it is how it works. You can login with a group.    SAS(R) 9.3 Intelligence Platform: Security Administration Guide (How Logins Are Used)  Knowing that corrections afterwards are more easy to do and test for the SP functionality. ... View more

One possible approach is: SAS(R) 9.4 Statements: Reference (by processing) The notsorted is indicating it should be grouped. Order is not relevant. first.-- and last.-- processing can give you control over the group begin/end.   The retain statement (and lag) over values of previous record as ordered in the dataset. Be carefull to use obs as name, it also used as an automatic variabele with same value as _n_.       ... View more

Ebele, I am reading "copyobjects.rexx", I position the environment as z/OS (hopefully 64-bit). It will mean RACF, HFS, BPXAS, bound libraries (z/OS classic 3390) DB2 etc. A lot of users must be there,  as there are 10 levels and 15 appservers. Knowing you I could have a idea...  With this sizing it makes a lot sense to have all kind of procedures for maintenance, configuration and support being scripted. The advantages: - avoiding manual errors . - the scripting can be use as the documentation of the change process. - in case of migrations the scripting can serve as central point to rebuild to a new design. (yes: NO SMU usage) We agree about that. That means: - leaving aside (not using) the SMC and SDW for that kind of work and replace that with scritps as applicable. - better conformation to normal IT "best practices" and Standard of Good Practice - Wikipedia, the free encyclopedia - It is not conform the approach that people of SAS institute are commonly claiming it should be implemented. What do we have: - You must have implemented a version of user-import and synchronisation macros.   SAS(R) 9.4 Intelligence Platform: Security Administration Guide (User Import Macros)   That is User-identity management without SMC - With 9.3 copying more with metadata became possible, yes the -subprop file.   SAS(R) 9.4 Intelligence Platform: System Administration Guide (Using the Batch Import Tool)   With this promotion and ship and also parts of configuration can be automated. - With own build programs in Java .Net and SAS it is possible to update the metadatabase.   This part is documented but not extensively. It is sayin you can build your own SMC functionality as you like.      SAS(R) 9.4 Open Metadata Interface: Reference and Usage New in 9.4 - more batch interfaces are coming,   SAS(R) 9.4 Intelligence Platform: Security Administration Guide (About the Batch Tools for Metadata Authorization) I tried to automated some configurations steps as you wanted, it stopped for political issues. As a schema for ports is needed I have put that with applicationnames in a table like registration. (macro-list like) From that point I generated a lot of neede code for interactive called processes or for bach like ones or configfiles to be uploaded to a operational location (segregated in dtap/changeproces). Your proposal of -subpro file usage. I could think of one generating all variations of -subprop filecontents. Than by calling a batch-script referencing a named combination to a -subpropfile will do the job. Jaap ... View more

SAS(R) 9.4 Language Reference: Concepts (About Date and Time Intervals) is containing a lot. IS8601 is giving a standard to the weeknumbers. With  INTCK and INTNX functions you should be able to do all type of calculations. Remember that week 53 and the 29 february are not occuring every year. You have to deal with that. Before quering a DBMS it should be handy to have setup common used week/date indications/intervals.  (last week last month etc) using the normal date, date-time conventions as macro-vars.  last week, last month are well defined related to you (simulated) date. When it comes to calculating working-days  it is possible to add a user customized table for that. (not all holidays are equal). This is all part of date/time calculations. In reality a very dificult enviroment altough it has the feeling of being simple. ... View more

Hi ebele, Copying Application Server Contexts will probably technical working as copy option, only..   You are introducing a lot of possible issues if you want to add additonal appservers this way. That are: - Missing OS files (they will be created with the Deployment wizzard. - Conflicting port number issues. - Possible broken missing associations to .....   When needing a new appserver context it would be better to use the deployment wizard and plan ports. For the SASwork question, this day, I have put all references in. As expecting the need for additional app-servers. Copy SP definition with  related SP processes can be copied to an other location and set up with a different App-server context with the copy. ... View more

Is there a reason to not wanting handing over te code? Is the release/change process missing? That would an issue to solve, This is meaning you develop have let it tested and someone else after an user-acceptance will test it. In this kind of processes the handing over is done with all kind of agreements on responsabilities. Do you want to have your code run while you are not present. No releasemanagement involved, than the question is: can your program being scheduled.  Answer: There are a lot of schedule options. It depends on the technical enviroment versions tools and the support that is delivered to you.     By the way versioning is something quite different as release management.    ... View more

Beto, The pop-up behavior is quit normal with Windows. The goal is help in preventing spamming/botnets. Get into the microsoft questions: Avoiding Excessive Security Warnings when Sending Automated E-mail Messages  When you configure an other mail-server. ... SMTP has by default no security setup/layer most of it solved by the mail server and routers/firewalls. At home it rather easy to receive mails from every mail-provider (pop3 mapi) sending mails however is mostly blocked. Using SMTP poort 25 is often filtered by their routers. Having a mailprovider offering secured sending mail you could use that. The required configuration settings may be slightly different (mapi and mapiport). An in house mailserver is able to configure to allow mail. Often it is called "bulkmail". Why this all? Same reason preventing spamming/botnets.      ... View more

Hi Abhijt, Ahmed is right to mention the utilloc option. It will isolate the IO caused by utilities like Proc SQL , Proc Sort using temporary data. That utilloc option has things like roundrobin selection, The configuration is changing fast with a growing lot of instances and variations. As Sun/solaris is an old name (oracle) now I assume a lot of historical grown practices. Your environment is C/S but can be of BI/DI style (use of Eguide Amo DI Miner etc) or the classic one,  SAS/Connect with SAS on desktops and Batch with eg LSF. BI/DI style. (The structure is almost the same with 9.3)   SAS(R) 9.4 Intelligence Platform: System Administration Guide (Overview of Configuration Files) These are the basic ones. See the remarks to not change the old well known names but the _usermod versions of them. The sasv9_local is a site specific one for all SAS processes on the machine including the metadata server and Object spawner server. It is better to use this one with that goal and not for user-segregation.       SAS(R) 9.4 Intelligence Platform: System Administration Guide (Reference: Configuration Files for SAS Servers) These are the one for the APPlications-servers defined in the SASMETA dataserver. You need to do the variations in the /Lev_/...._usermod....  files to segregate the users. You are needing several app-servers for that. It is configuration step. The challenge is adding appservers and a Portnumbering scheme SAS(R) 9.4 Intelligence Platform: Application Server Administration Guide (Defining Multiple Application Servers) The deployment wizzard  will also aad the directories on the OS level. Adding servers with SMC is possible but those directories are not created. There is no convention mentioned for the needed additional portnumbers. It depends on the complexity. Just one convention: You can have a Multiple level environment. By this convention the last numer is the same as the used level. SAS(R) 9.3 Intelligence Platform: System Administration Guide, Second Edition Port Numbering in a Multiple-Level Environment Classic   With batch and some of the SAS/Connect options you need to make it scritped. (export etc... see Ahmed remark) The most easy way is a Unix script (wrapper) with parameters and then the correct settings/config etc. hmmmm .... 1000 users and Sun Solaris (single machine). I get the feeling you have some performance issues. ... View more

Abhijit, The other reply was pointing in the dierction of the irrespectivity of tools. Therefore I made the reference. Aside the version (9.3) It is very important to know the OS environment (windows/Unix) and the way of working (Desktop/ Client-Server - Server). Within a Windows desktop environment it makes not much sense to think about segregated workfiles. More Ram and faster IO (SSD) is easier and more profitable to incerase speed. You are the only user on the machine. Do you want to have more workfiles the hardware (more dasd units) should be present and capable to get some profits, mostly that is the botteleneck..The -work options at a script to start or a own config-file will do. Pointing to a local dasd and not a remote fileshare is very advicable.  Iit normally part of "Mydocuments) user based. Within a Windows or Unix Server environment a lot more users are being expected. They can interfere each other and also possible get into blocking issue by running out of resources. So monitoring and tuning the system should get attention. As in most modern installations like SAS 9.3 are using the BI/DI server I mentioned the segregation in that environment. All the modern tools like Eguide AMO (Connect) are running with a registration / configuration in the App-server-context defined in the SAS metadata. Basically the _usermod files are te same as the old autoexec/config approach on the OS level. It has become a nested approach now. The SAS metadata hes been designed for grouping users according the Enterprise organization. That is conform your question. There are some samples causing the misundertanding as it would be designed with tools in mind.. wrong...wrong ... The education samples of SAS are using "Orion Star" fully based on grouping users according the organization. It is named Enterprise Intelligence Platform (EIP) for that. Some exceptions with EIP could be there, as: - Classic SAS (is bypassing SAS metadata) direct via the DMS approach or by batch executing (including the LSF based start) - Classic SAS/connect as with 9.3 it still not controlled by SAS-metadatastrcutures In those cases the old approach of dedicated autoexec and config as usermod setting can be solved within shell scripting. It will deliver the same functionality as the appserver (metadata) approach by that.    Within Unix the mountpoints are meant for isolation of files/data. You can define a lost of them with all their  own performance properties. Having the mapping names you can also group them to users (type of usage) as you like/want.  The best hardware and connection would be advisable (performance troughput). Within Windows(server) the IO approach is different as the split and rearrange of data is less architected on this point. With the virtualization level a part a lot should be made possible..   ... View more

see: Different work area for different tools in SAS  in SAS Deployment (kusuma) ... View more

reeza, As I read the note, it is intended functionality avoiding the naming conventions with Excel usage. It is happening in proc export. In that case it will always be problematic. (No bug/error). Maybe it is caused by an interface limitation and manually in Excel it is bypassed.   ... View more