Whosack you proved the SAS environment is running on both used id's. Very nice because this eliminates that possible parts. As all is working at SAS do not expect miracles being solved by upgrading. Although every support will tell you this. "The next version will solve every problem, just wait" .... (humbug)  One of te last possibilities is something strange/weird in the batch scheduling you do and your manual actions as difference. This beyond the scope of SAS and yet the should know. (google at microsoft for this type of questions) Some examples: - Run Powershell script as Scheduled task, that uses Excel COM object - http://social.technet.microsoft.com/Forums/de-DE/d47d116e-10b9-44f0-9a30-7406c86c2fbe/scheduled-task-wont-run-bat-file What could be the issue is the running key when started as scheduled job does not have the needed rights or resources. - the scheduler is running by a key, probably "local server".   + This key can not elevate rights.   + some reources may have other settings  (com is an example may be more) - When running scheduled it is missing the keybord / screen resources. These do exist when used directly.   + when some program is expecting those resources (call for them) then ... (wait/dump) Why should SAS support know? Anser: It is common for Windows. http://technet.microsoft.com/en-us/library/hh125927(v=ws.10).aspx It is the same reason you have to change some rights (logn as batch job etc.)    ... View more

The Object spawner is the master on servicing every request initial and following for WS and SP on all users. Users can start more processes on their own by using Mp-connect that is bypassing the objectspawner or by using multiple Eguide sessions. Going a way of denial service will end up in unhappy users.   http://support.sas.com/documentation/cdl/en/biasag/62612/HTML/default/viewer.htm#n12027intelplatform00srvradm.htm Windows server usage, it is not my favorite. I know to objectspawner is mostly running as "Local server" SAS(R) 9.3 Intelligence Platform: Application Server Administration Guide Local server has many privileges but is missing: domain admin rights Thinking of lowering priority Windows OS processes..... Priority setting in Windows is also possible. Scheduling Priorities (Windows) and How to Alter a Program's Base Priority at a Command Prompt, The idle is used for stand-by detection, setting it that low could prevent stanby. Manual intervention using taskmanager is usual advice. The start command could give something.  ... View more

The evolvments are in the direction of multithreading (high performance) and parallel processing. I do not think you can stop that. Qustions like I have often seen as an ad-hoc approach when suddenly running out of resources suffering performance issues. Eguide (latest versions) an Eminer are explicitly designed to spawn multiple sessions if possible. The goal is better service to users. Server performance management is the classic performance & Tuning question. - How much human effort you would like to spent in optimization vs the hardware cost/usage?  What you could do is: - Getting better hardware. your users are expecting unlimited speed by unlimited sizing. There will be always a limit. - Getting your users to know and what they are doing.   Possible is eduction of you users to choose/desing more effective coding solutions - Invest in analyzing and monitoring the usage in a more longer time intervals.  (apm pacakge ITRM etc)   Spreading the load to other hours using batch/scheduling could be an option. - Tuning at the OS-level.    Classic z/OS was very good at wiht the options of isolating workload types so the most critical ones would alwasy run (WLM).   Windows is has less designed for that as it easier to put more machines in.   Unix has te options of:   + segregation of SASwork (utilloc). You can define many of them   + Nice/renice  http://en.wikipedia.org/wiki/Nice_(Unix) SAS is using a fork from the sasauth (spawner) module. Do not expect the user setttings be effective set of the common user OS  administration. I have noticed all forked processes are inheriting the settings of the key running the spawner. The same is true for ulimits umask etc.  You can only see that by running the services by different keys. Using a dedicated key for the spawners.     You will probably need a plan wich appservers SP-server WS servers are needing at wich priority. The settings (eg nice) to be scripted in the levx/SASapp subfolders in the user-mode files.   ... View more

For iml (not ims) SAS/IML(R) 12.3 User's Guide ( Multiplication Operator, Elementwise:   # ) a sample working with vectors For the datastep SAS(R) 9.4 Language Reference: Concepts (Syntax for Defining and Referencing an Array) The major problem looks not to be technical, but getting the syntax and words aligned from one product to another. ... View more

wkossack  your header is mentioning 9.3 but in the descritption it is 9.3. Wich one is true? wkossack your telling the SAS programming and DDE works with one user, true?   The problem is this doesn't work when you run that with an other user as batch processes in your technical setup, true? This kind of issues are quite common to be an issue. I personal have seen them many many year. We can give you only tips you can do to do research for that issue as it is related to your possible unique technical environment.   True? ... View more

You could have hit something strange witin the OS like: 41863 - DATA step does not run completely when you use the PIPE engine in Vista, Windows 7 and Windows 2003 and 2008 server operating environments ... View more

The missing of any logfile saying something is dissappointing. You are saying using a different user and DDE excel. Some addtional checkpoints: - Is SAS and Excel both working with the other user? - The DDE interface is actually connecting to an interactive Excel session   It this possible wiht that type of batch-processing? is there some check Excel has been started?    Is it communicating with the correct Excel session ? (only the first I can imagine). ... View more

Fot the tecnical part on SAS/Access to oracle there are a lot of tuning options. For simple read retrieve is should commonly be acceptable. Teh buffsize can help to improve, some functions are causing ... (heavy network load)  http://support.sas.com/resources/papers/proceedings13/081-2013.pdf ... View more

The code is error free. The question is about performance. By happy, the machine is still not smart enough to transform the unstructerd  question in answer on his own. You have something to do and think about it.  Some advices: - Break up your research into smaller parts. Eg extract the missings to a smaller table to do more research on.  The pre-req is this number and size must fit in your environment.  The smaller the dataset to work on the easier it becomes.  (Same as fugues) - Understand the physical effects of your request   Indeed Check with you ORA DBA (as LinusH) already stated. If there are views (disadvantage), indexes(advantage) you could imagine what the DBMS internally wil do. - Sequential/Random  Normally invisible as hidden behind the SQL. When the effect wil be an access to the whole database touching every record. Try to have it done just once and sequential. When the effect will be accessing more than (rule of thumb) as 10% still do it sequential once, is it less random (indexed) would be faster. Getting some answers, iterate this as new questions will need to solved.     ... View more

Download the depot. ... View more

SAS(R) 9.4 Companion for Windows (Performance tools) ... View more

As you stated: Without having set the Memcache Memlib options the program is running fine. The problem you posted may be caused by one or both (combination) of these options. As the they are tuning options to move io/data to memory you could find other solutions to do that. The root cause of this type of errors can be a result of OS (Windows) behavior and/or settings. I had some bad experiences with SGIO option, never solved just switched off. When you need to analyze and solve that part you should go for the TS support approach.  It would be interesting to see some feedback of that. Although you have small datasets (0,5Mb) you could have run out of memory. I am missing the analyses part on that. The error is indicating a locking problem on an internal processed file. That is weird. Soemtimes this happens by very advanced tuning ideas to assume have delayed processing and holding files open (opportunistic locking). It is at the edge of OS level internals and  SAS.   You have found the Work location. the _TDxxxx (xx are random assigned processnumbers) you will find work files as you could see by the SASwork. In the current SAS-session these locations must be the same. The SAS_utill ....  Your error-message  is indicating is using WORK, SASwork to be at that physical location. File processing is often cached at OS level. Juust at some synchronisation points it will write some information out. By that you can expect not seeing anything happening and  .... at the same time the OS is very busy working on that. The more advanced trace/debug and monitor tools should be able to help and debug that kind of activity.      ... View more

Agree with ballardw, it is about configuring Eguide. Would be an option to redirect this discussion in the Eguide discussions. ChrisH is following that one. ... View more