Thanks Doc@Duke for the suggestion! I took your advice and created a SASware Ballot.  I will post a link to the SASware Ballot so anyone who reads this discussion can vote in favor for the idea! ... View more

Signed up and ready to go! Thanks for the info! ... View more

Here is a bit from a link I found on SAS's website:   http://support.sas.com/documentation/cdl/en/hostwin/63285/HTML/default/viewer.htm#winperform.htm Specifying the MEMLIB and MEMCACHE Options in 64-Bit Windows Environments Sixty-four bit processing in Windows operating environments uses 16 terabytes (TB) of virtual address space, so in these environments, extended memory is not needed. SAS uses the conventional memory that is available to support the MEMLIB and MEMCACHE options. CAUTION: It is possible to exhaust system memory, and thus cause system failure. You can use the MEMMAXSZ option to limit the amount of system memory that SAS allocates for the MEMLIB and MEMCACHE options.  To use the MEMLIB and MEMCACHE options, ensure that the operating environment meets the following requirements: Intel or Intel-compatible 64-bit processor (Itanium or later). Any 64-bit version of Windows. 4 GB of RAM or more; you might have better performance if you use more than 8 GB. SAS 9.2 for Windows. Then follow these steps: Set the total amount of memory for memory-based libraries by using the MEMMAXSZ system option. See MEMMAXSZ System Option: Windows. Set the memory block size for memory-based libraries by using the MEMBLKSZ system option. See MEMBLKSZ System Option: Windows. Specifying the Local Security Settings In 32-bit environments starting with Windows XP Professional and above, the Lock pages in memory security setting must be set, so that each user who is running SAS has access to the extended memory. If a user does not have the correct permissions, then SAS will issue a warning message to the log. System administrators can set the local security settings through the Start Menu. To set this value Open the Control Panel. Double click Administrative Tools. Double click Local Security Policy. The Local Security Settings window will open. Double click Local Policies. Double click User Rights Assignment. Double click Lock pages in memory. The Local Security Policy Setting window will open. Click Add. The Select User or Groups window will open. Select the user IDs or name of the group of users who need to run SAS with access to the extended memory. Click OK in the Select User or Groups window. Click OK in the Local Security Policy window. Note:   In the Local Security Policy window, you might see two check boxes: the Local Security Setting check box and the Effective Policy Setting check box. If the Effective Policy Setting check box is not selected for the users that you added, you will need to reboot your computer so that the new security settings will take effect. ... View more

As silly as this may sound, I would check that you have properly installed this SAS/Warehouse feature, and have it properly configured.  If you have the administrative perspective, check out the following link: http://support.sas.com/documentation/cdl/en/waug/59817/PDF/default/waug.pdf (Page 72 mentions some settings) Either it's not installed, or not setup correctly, and therfore it cannot find the catalog SASHELP.DW This is my guess so far ^ 🙂 ... View more

When you say restart the web services, are you speaking of a WebSphere instance ?  Don't list all your details here, but the power behind the machine that is hosting the Mid-tier (web-server) can affect the start up time greatly.  I would also find the log file locations for WebSphere (or whatever platform you are using) and "tail -f" (if in Unix) the log file while the restart is going on.  You can watch as the start up appends logging information to the log file, and you may be able to notice where it's spending most of it's time, and if it is having any major issues or errors. If you are in Unix or Windows would probably make a big difference on your approach to diagnosing the problem here, but I'd advise the log files as a starting point 🙂 ... View more

Have you checked the File Type options for windows?  If you have a window open in explorer, you should be able to go to: Tools > Folder Options > File Types (tab) Did the associated file types get messed up or changed? You can set the extension to the SAS program that opens it, this should fix the issue, if I understand the problem correctly. 🙂 Good luck! ... View more

We have similar issues with creating "builds" for the SAS software in my organization.  9.2 builds seemed to be a lot better than 9.1.3, but there still have been issues with the software builds we have created and distributing them. (The builds are how a part of our IT department manages software installs, so they want SAS to fit into there method of installs)  We created response files following the directions from the link below: http://support.sas.com/documentation/cdl/en/biig/62611/HTML/default/viewer.htm#n05023intelplatform00install.htm Even with this method, which I'm connecting the dots with jasonlosh's response, is that the install has many redistributable's that can affect what is installed.  These pre-reqs vary from machine to machine greatly from my experiance. (Installed on 8 machines, and I think only 2 machines had the same pre-reqs installed, other than that they all had different lists of pre-reqs to install) What would be nice is having a response file built for typical SAS BI installs, but having the pre-install (system checker) run dynamically.  So if you perform the response file install on the 100 machines, and they have different pre requirements (redistributable installs), it can account for them.  All of this under a "silent" isntall would be nice. We are currently working on this matter as well, and will re-post if we find any better methods of performing these installs ... View more

Yea, the gentleman that installed the SAS 9.2 right before I got here mentioned that he had to redo the ports #s for this setup.  It is nice using the Lev1 Lev2 options within the SAS 9.2 install now.  I'm going to add the Connect Server and Spawner this evening or weekend and see if it helps on some performance issues. ... View more

I think we have just about every databses within our orginization.  In regards to SAS, most of them are DB2 or SAS. I am not aware of the METAAUTOINIT option.  Looking into this right now. Thanks ... View more

After checking the DeploymentRegistry.html, I did find that it was installed, or included inthe SID file.  The plan file selected must have been the issue then. To continue on though, most of our SAS users are connecting to this UNIX based machine from PCs.  The saswork directory (where temporary EG projects are being stored) indicates that the jobs are being run on the server correct?  The gathering and manipulation of data is all taking place on the server I'd hope.  Can you think of any issues with setting up the Connect Server and Spawner within metadata in relation to having a 9.1.3 server on the same machine?  I'm sure having different ports than the 9.1.3 would be all that is needed, but figured I'd ask the question anyways. So in a nut shell, I do believe we want users to run jobs on the server (is this considered the backend of the server?) I might play with this more over the weekend and test. Sorry for the elementry questions in advance, I will reiterate that I am in "training" 🙂 ... View more