Please give as much as possible information what you have checked and verified. Just admin access is no solution in contrary. Having that you must be capable of doing all admin work or getting a fresh installation and start over again. When that is not your task you will lose a lot of time. ... View more

Thanks Steve, the numbers are getting into a binary way not decimal digits. You are getting the same isuues as the accuracy of 1/3 and than adding it. The real maths will get some fractions to miss the real value as a result 0《》0 . There are many notes on that fuzz factor and more. The first calculators where als showing that. As people got confused they made an automatic rounding to the result. Now people get confused on binary arithmetic. As the rounding got standardized that rounding could become introduced in SAS. I have seen some notes about that. ... View more

Did you read all those things about numeric orecision? As soon as you are going into not whole numbers or having more than 12 digits you are in the area that 1 might not be equal to 1 due to that precision. Remember the slider. It is not a SAS problem it is numeric binary global one. ... View more

Tammy, it makes sense to have one metadata server serving the VA work the BI classic one and the data-mining.That brings you at the same level of an AD security administration with Windows and RBAC. The VA work (end users) are accessed by lasr-servers. You can define many of those. The simple bi work for less advanced users you can organize by SAS APP users on some compute servers. Putting that data and users  there. You can define many SAS APP servers as they are meant as applications data and code by SAS. Those data miners can have their own SAS APP servers on dedicated compute servers. By that segregation you are needing groups to assign the users to all of these data segregated appservers. This approach is quite common. There is a problem with special roles like a person doing bi work and administration. In that case a dual account is normally mandatory. That solves also the part of data administration with VA. Windows  admins are using that approach theirself but seeing SAS as something like excel do not make the association to do it similar with SAS. I am wondering how you would go on to protect system resource usage and data security by trying to prohibit excel. ... View more

There is no need to reboot the Windows machines. You can have them running for a long period. Problems are often within the "apolications" like sas.  The cause can be memory problems or synchronisation issues. The real solution is a developers question, in this case sas TS and the developers of the SAS system. Needing to bypass issues in SAS you could plan to restart all SAS servers better word services. Eg the metadata server. In that case your batch processes will not be affected. Needing a planned outage of the os you can plan that so cancelling running jobs is an expected event ... View more

To add: - Check the current dir of the batch server it is not the home dir as normally expected - the log file notation is 12hr based one , you would 24hr as normal - when apm is active spaces in source names are not allowed anymore. I think this issue already exists in the batch server script. Using the foundation entry directly allows spaces when proper quoted. Why this way to publish and not with TS fir a fix or kb note? ... View more

The compression or the encryption is needed as you could see all data accessing the file as an text file. Linus the aes encryption is added with 9.4 and is not available with 9.3. It is a good argument to follow the latest releases and not getting to far behind. A major requirement for that is an IT implementation not too different from common IT government policies. Yep that is one I keep to state as that alignment is a root cause problem. As the binding of the Sas dataset is made to a metadata ever.  That is giving the question on DR and BR requirements. Who what when where why with the how. ... View more

Your execution time and data-sizing doe not match to normal behavior. A common pitfall is the Cartesian product as it blows up the data. When this happens, there should be a warning-note of that. There is something strange in you SQL that is your new dataset (work.event) and an input dataset (event a left join) are the same. This is logical not possible in a RDBMS approach. During the processing those should be segregated. With classic SAS that is solved by using an intermediate file. I have also seen warnings SAS is not  happy with that anymore as of multithreading within their PRoc SQL.   ... View more

Merritr I do not know how to recover that forgotten password. The same as you researching advantages/disadvantages. I stopped with this as was being a lonely guy and not seeing any way to get this covered. More complicating as the results (PDF/HTML Excel) and code (sas) were needing the same kind of level of security requirements (same info).   ... View more

@hnsj  get confident with the dependicies between servers. At that point the SAS docs are good. There are also the notes to take care off Metadata and compute servers: SAS(R) 9.4 Intelligence Platform: System Administration Guide, Third Edition some of those can be restarted from the SMC (objectspawner) Midtier: SAS(R) 9.4 Intelligence Platform: Middle-Tier Administration Guide, Second Edition VA: SAS(R) LASR(TM) Analytic Server 2.2: Reference Guide Just having a "sas.servers start" will try to start all of them in the correct order on the current machine. It can not solve stuck/blocked services. You have the be sure that is not the case. A sas.servers stop (all) and verifying those are stopped is a more secure approach.   ... View more

That is going into the hell by inventing out, trying to get these processes aligned into security policies as of regulations and the in-house IT policies. Those machines should be able to be operated by common support staff. That is not Ronan/Jaap or any other platform admin personally. The big problem is that SAS is violating those guidelines and doing different things. The SAS documentation can tell a lot but when its wrong it is wrong. You didn't follow my advice and do the research on the way the status is solved in those scripts. I did had problems with a reliable weekly restart of the services using the adviced SAS approach. So I did debug those scripts and analyzed  them. There was no help from SAS TS as not understanding or willing to understand the issues. What I have found is:  - The metadataserver is started (detached background). The object spawner is started after some planned time (sleep function) not really checking the availability of the metadataserver. That was problem 1/ It could happen the objectspawner did start but could not retrieve the needed metadata. Only by seeing missing content (comparing) that problem could be recognized. It can be checked fully trustworthy by using a proc metaoperate doing a real login. Seeing the start en status check being coded, that is the pid-number check. If you are convinced the pinging of a server is the proof the server runs, than there is long way to go for some learning.       - The same issue was recently seen with the connectspawner as also changed to retrieve information from metadata. It failed and customers complained. - With Eminer there is a Rmi service needed hardly to recognize. Customers complained they could not login. Than found the service was corrupted started by validating the test-url as documented. Not it is not in the servers.sas. script. While reviewing those scripts  Than seeing another coding problem. You need some background on C-language.  The coding issue: the $*  is giving the string unchanged to another script (the whole string as is) would you code $1 $2 $3 than the string is first evaluated and than composed to an array of strings (arg argcount C functions) the effect is that the original string gets broken.  The difference looks not that big but when you quoted arguments and spaces you get into trouble. Do you have a batch-script (batchserver) with logging configured than try to use sas code with spaces in the name. It will dump with all kind of messages where the first troublesome one is the wrong default directory setting (sas note  can be given). Some more issues? - sasauth did not check the normal Unix root conventions (locked users after x-attempts) There is change on that. - having tested that locking of the account (working now) finding sas did add unmentioned actions on top of that. Locking out 5 minutes at the same moment you can do a login with putty. There is no need to put something on top of that . The Unix policies are set and accepted by business policies. - The restart of the services (complete system) was planned because every wrong login added 5 additional seconds for all users (somewhere internal). It could happen the metadataserver did not react for some some 1or 2 hours and  than processing again. Where on earth did you learn that SAS institute delivers failure free software and you can trust them for everything on that. Please get critical and do the research and the validation of what is there and than react accordingly.  I mentioned the experiences by solving issues, that is going beyond what is documented and expected. ... View more

ronan the sas.servers scritp are made for interactive usage. The question is aiming to solve this by in house monitoring tools that are not aligned with SAS proposals. Normally there is a dedicated department (the bridge) that is delivering that kind over services of availability and continuity. At that department a dedicated sas platform admin for a unique solution is not wanted.    Quite simple. Those script with the sas.servers do not offer a check on operationally availability. Just go and analyze those and you will have to admit that. It is not a good situation that services can be non-operational expecting customers to complain on that. The goal is recognizing that and repair before they complain. (see ITIL)   ... View more