Posted on https://blogs.sas.com/content/sascom: Our friends at Zencos also offered a few predictions and recommendations, including: Increasing efficiencies: Companies will be reallocating resources effectively to succeed (or at least stay in business). Focused industries: Follow the new administration’s priorities to see which industries will bounce back first – government infrastructure, healthcare
Author
We recently confirmed (via http://support.sas.com/forums/forum.jspa?forumID=10&start;=0) that SAS Enterprise Guide does not support proxy servers between itself and SAS servers (metadata, workspace, stored process, etc). However, if the proxy server can be transparent then EG can work through it. While implementing SAS BI at a customer site we needed to access
Don't forget to register for the SAS Global Forum 2009! http://support.sas.com/events/sasglobalforum/index.html March 22-25, 2009 Washington, DC And check out my submitted paper on Monday afternoon - Supporting a SAS Server Architecture Included topics: Documenting the routine tasks (such as restarting services in the correct order and adding users)
SAS Enterprise Guide allows users to access files on the SAS server environment. Only one of the three options can be set - either to point to the designated user folder 'SAS User Root', set to the root 'System Root', or define a shared location/directory 'path'. The SAS Administrator sets
The output delivery system (ODS) provides some wonderful out-of-the-sas-box custom style sheets (CSS) for use in SAS web output. My personal favorite is 'sasweb'. However, many organizations wish to modify these and deploy new style sheets to the enterprise. The best approach I have found is to utilize the Enterprise
Right-click on any SAS file and several options could appear, including but not limited to 'Open in SAS Enterprise Guide', 'Open in SAS 9.1', 'Submit in SAS 9.1', etc. In silent installs, multiple SAS version environments, or other registry impacting issues - these options could be rendered useless or simply
Over the last couple days, there have been some posts in SAS-L as well as those new fangled twitters, on whether 'R' open sourced software is a threat (ignoring the SAS Sales team's response) and on whether SAS could move to Open Source. Highlights from these discussions: New York Times
"The cube has too few dimensions." - is related to Metadata Permissions on the cubes. When completing a refresh of the cube with full PROC OLAP syntax, the metadata permissions get removed on the individual cube. If this is the common practice (to run full PROC OLAP Syntax), it is
Using the proc metalib process to update specific elements would generate errors related to the base SAS Library conflicting with the Metalib referenced library. You can run a libname _all_ list; statement to review all the libraries available to the process. Also, the reference material utilized to improve the process
Within SAS Run the following code (the purple text is the password you would like to encode): proc pwencode in='myn3wpwd4u'; run; After submitting this code (F3), the resulting encoded password in available only in the log file. The results from this example are below, the highlighted line is the encrypted