• Issue 38357 – SAS stored process might fail to run when the language is set to Norwegian
• Issue 40130 – Errors might occur running a project after migration in SAS Enterprise Guide

You can obtain more details at the SAS Enterprise Guide 4.22 Hot Fix Downloads page at http://ftp.sas.com/techsup/download/hotfix/HF2/A53.html#A53007.

I had been using SAS Enterprise Guide 4.22 for months without any crashes, but in May I installed the SAS Hot Fix A53005 primarily because it was available.  After installation of the Hot Fix, whenever I attempted to run the Create Format task, even in a brand new project, I received the following error:

SAS Enterprise Guide has encountered a problem.  We recommend that you save your work and restart SAS Enterprise Guide.

I submitted a ticket to SAS Tech Support, and for SAS, it took a relatively long time to get resolved.  Tech Support had to forward the issue on to the Development Team, who determined that the hot fix (and A53003 before it) relied on a patched version of the Microsoft Visual C++ runtime.  The patched version of the runtime was used because it fixed a security hole in ATL (Active Template Library).

Tech Support sent me the link for the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update (http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en), and when I applied the update to my system, the Create Format task worked fine.

http://support.sas.com/documentation/cdl/en/biwaag/63536/PDF/default/biwaag.pdf

The information in the Key User Action Log can be imported into SAS data sets and presented in reports. To report the data, follow these steps:

1. Import the WebReportStudio_KeyActions.log data into a SAS data set. Here are the main steps:
   1. Assign a libref to an XML file that contains log data, and specify the XML engine.  In the following example, MyFile.xml is a copy of a Key User Action Log file:
      

      libname myxml xml ’C:\My Files\XML\MyFile.xml’;

   2. Use the SAS data sets procedure to import the XML file into a SAS data set.
      Here is an example:
      

      proc data sets library=myxml;

      This code creates a data set named EVENT in the MYXML library. For more information, see SAS online Help and documentation.

2. In SAS Information Map Studio, create an information map based on the data set that you created in the preceding step. For the information map, you might want to provide the ability to filter based on the event code (<code> tag), the user name (<user> tag), the report name (<report> tag), or the date (<date> tag). For information about using SAS Information Map Studio, see the product Help.
3. 3 In SAS Web Report Studio, define a report based on the information map that you created in the previous step. You can define the report to be refreshed manually, and then schedule the report to run at regular intervals.

The issue described in SAS Note 36601: Cannot undo changes in Microsoft Excel when the SAS® Add-In for Microsoft Office is installed can be fixed by applying the second maintenance release for SAS 9.2 (TS2M2).

However, after you apply the maintenance release, you must also select the option Always Prompt for Data Source. This option can be found under SAS –> Options on the Tasks page. See Usage Note 37701: Additional SAS® Add-In for Microsoft Office configuration is required to restore functionality of the Undo button in Microsoft Excel.

from Chris Hemendinger, senior software manager in SAS R&D and author of

Supported Versions and Combinations:

• You can use EG 4.1 with local SAS 9.2 (no metadata server).  Everything local on your Windows machine; it should just work.
• You can have both EG 4.1 and EG 4.2 on your local machine, along with local SAS 9.2, and all should work together.
• You can have SAS 9.1.3 and SAS 9.2 on your local machine, but EG (either version) will use only the version of SAS that is registered for local use, which is usually the version that was installed last.  You can run "sas /regserver" to register a particular version of SAS.
• You can have SAS 9.1.3 and SAS 9.2 side-by-side on a server machine with two metadata servers (one 9.1.3 and one 9.2) and object spawner instances, as long as you assign unique ports for the metadata server and workspace servers.  So in this way, you could point EG 4.1 at the SAS 9.1.3 instance, and EG 4.2 at the SAS 9.2 instance.  This approach might be helpful for transitioning.

Unsupported Versions and Combinations:

• You cannot use EG 4.1 with remote SAS 9.2, nor can you connect to a SAS 9.2 metadata server.  The SAS 9.2 metadata server has a different API that EG 4.1 doesn’t speak.
• You cannot use EG 4.2 with SAS 9.1.3 at all: EG 4.2 relies on some new features within SAS 9.2 that aren’t compatible with SAS 9.1.3 (ODS Graphics and some new APIs).

One data set that we were working with included a date variable which was stored as a DATE9. format.  A user complained that every time she exported the data it ended up in DATETIME format, and all of the zeroes from the time complicated her project.  I tried to replicate her problem many times by exporting the same data set into Excel and I ended up with DATE9. every time.  I finally asked her to send screen shots of what she was doing, and noticed what she called “export” was actually using “Send To –> Microsoft Excel”.  I explained that to get the results she wanted, she needed to use the “real” export technique.  After I solved this problem, I browsed to support.sas.com and sure enough, SAS had already identified this issue in Microsoft Excel might not maintain date formats in SAS Enterprise Guide.  Apparently this issue is fixed in Enterprise Guide 4.2 but I have not tested it yet.

• context sensitive keyword completion (syntax suggestion)
• relative file addressing
• code reverse engineering (see what old code is doing)
• an autoexec process flow for projects (runs automatically when project is opened)
• code analyzer (reads a program and turns it into a process flow)

I also had the opportunity to preview some of the new features in the upcoming version of Web Report Studio (4.3).  SAS is expanding drag and drop capabilities, which makes creation of report even easier.  The biggest news though is the ability to use more than one data source in a report section!

• Problem Note 39149: The SAS Enterprise Guide editor’s width of caret position panel within the status bar does not accommodate for large row and column number schemes
• Problem Note 38003: Unable to edit existing parameter in SAS® Enterprise Guide®

Enterprise Guide 4.1 Hot Fix 41EG14 (66)

from support.sas.com:

Configure a Group Content Administrator

A group content administrator is a user who has WriteMetadata permission for the respective group, and the group’s Portal permission tree. A group content administrator can share personal content with the group, and can edit or remove content that has been shared with the group. (The SAS administrator and the SAS Trusted User has WriteMetadata permission for all group permission trees that are defined in metadata.)

Prerequisites: Before you can assign a content administrator for a group, all of the following must be true:

• The person who will be a content administrator must have a user identity that is defined in SAS metadata.
• This user identity must be a member of the group that the person will administer.
• A group permission tree folder must exist in metadata for the group. To verify that a permission tree folder exists, or to create one, see Overview of Permission Tree Folders.

To configure a group content administrator for the Portal Application Permissions tree, follow these steps:

1. Log on to SAS Management Console as the SAS Administrator (sasadm).
2. On the Plug-ins tab in SAS Management Console, navigate to Environment Management –> Authorization Manager –> Resource Management –> By Type –> Tree.
3. Right-click on the permissions tree for the group and select Properties.
4. In the permissions tree properties dialog box, select the Authorization tab.
5. Select the Add button to display the Add Users and Groups dialog box.
6. In the Add Users and Groups dialog box, select and move the group content administrator under Available Identities to Selected Identities. Note that the group content administrator must be a person, and not a group.
7. Click OK to exit the dialog box.
8. When you return to the Authorization tab, make sure the appropriate user is selected in the Users and Groups list box.
9. To modify the permissions for the selected user, in the permissions list row for the WriteMetadata permission, select Grant.
   Important Note: Ensure that the permission is explicit. The check box for a permission that comes from a directly assigned access control entry (ACE) has no added background color. If the check box for a permission has a background color, to remove the background color and designate the permission as a directly assigned permission, click the check box again.
10. In the properties dialog box, click OK to save your changes.

The user that was configured as a group content administrator can now log on to the portal and share personal content with that group.

Working with files

Moving around in the file

Inserting and overwriting text

Deleting text

Undo and redo

There are obviously many more Vim commands out there.  Typically if I find myself in a situation where extensive modifications need to be made with a text editor, I will use Crimson Editor on Windows.

The list of commands above are a subset of The Vim commands cheat sheet – 1.2.