Blogging about all things SAS » x – Notes to Self

Mirror Mirror on the wall, where am I running?

Shane Gibson — Wed, 01 Jun 2011 09:29:14 +0000

We have been doing some trouble shooting with the new Grid environment, and one of the guys on the customers site found this great piece fo SAS code:

%put _all_;

Run it in EG and the log will tell you a whole heap about what and where you are running your code on!

Example results from SAS 9.2 (GRID)

GLOBAL _CLIENTUSERID ‘sg’

GLOBAL _SASHOSTNAME ‘sasserver1′

GLOBAL _CLIENTAPP ‘SAS Enterprise Guide’

GLOBAL _CLIENTUSERNAME ‘Shane Gibson’

GLOBAL _CLIENTMACHINE ‘sasclient1′

GLOBAL _CLIENTPROJECTPATH ”

GLOBAL _SASPROGRAMFILE

GLOBAL _CLIENTVERSION ’4.3.0.10354′

GLOBAL SASWORKLOCATION “/opt/sas/work/Lev4/SASWork/”

GLOBAL _CLIENTTASKLABEL ‘Program’

GLOBAL _SASSERVERNAME ‘SASApp’

GLOBAL _CLIENTPROJECTNAME ”

AUTOMATIC AFDSID 0

AUTOMATIC AFDSNAME

AUTOMATIC AFLIB

AUTOMATIC AFSTR1

AUTOMATIC AFSTR2

AUTOMATIC FSPBDV

AUTOMATIC SYSBUFFR

AUTOMATIC SYSCC 0

AUTOMATIC SYSCHARWIDTH 1

AUTOMATIC SYSCMD

AUTOMATIC SYSDATE 01JUN11

AUTOMATIC SYSDATE9 01JUN2011

AUTOMATIC SYSDAY Wednesday

AUTOMATIC SYSDEVIC ACTIVEX

AUTOMATIC SYSDMG 0

AUTOMATIC SYSDSN WORK _PRODSAVAIL

AUTOMATIC SYSENCODING latin1

AUTOMATIC SYSENDIAN LITTLE

AUTOMATIC SYSENV BACK

AUTOMATIC SYSERR 0

AUTOMATIC SYSERRORTEXT

AUTOMATIC SYSFILRC 1

AUTOMATIC SYSHOSTNAME sasserver1

AUTOMATIC SYSINDEX 2

AUTOMATIC SYSINFO 0

AUTOMATIC SYSJOBID 20038

AUTOMATIC SYSLAST WORK._PRODSAVAIL

AUTOMATIC SYSLCKRC 0

AUTOMATIC SYSLIBRC 0

AUTOMATIC SYSLOGAPPLNAME

AUTOMATIC SYSMACRONAME

AUTOMATIC SYSMAXLONG 9007199254740992

AUTOMATIC SYSMENV S

AUTOMATIC SYSMSG

AUTOMATIC SYSNCPU 4

AUTOMATIC SYSODSPATH WORK.TEMPLAT(UPDATE) SASUSER.TEMPLAT(READ) SASHELP.TMPLMST(READ)

AUTOMATIC SYSPARM

AUTOMATIC SYSPBUFF

AUTOMATIC SYSPROCESSID 41D82DA54B2444914018000000000000

AUTOMATIC SYSPROCESSNAME Object Server

AUTOMATIC SYSPROCNAME

AUTOMATIC SYSRC 0

AUTOMATIC SYSSCP LIN X64

AUTOMATIC SYSSCPL Linux

AUTOMATIC SYSSITE 0010004447

AUTOMATIC SYSSIZEOFLONG 8

AUTOMATIC SYSSIZEOFUNICODE 4

AUTOMATIC SYSSTARTID

AUTOMATIC SYSSTARTNAME

AUTOMATIC SYSTCPIPHOSTNAME sasserver1

AUTOMATIC SYSTIME 20:14

AUTOMATIC SYSUSERID sassys

AUTOMATIC SYSVER 9.2

AUTOMATIC SYSVLONG 9.02.02M3P041310

AUTOMATIC SYSVLONG4 9.02.02M3P04132010

AUTOMATIC SYSWARNINGTEXT

Capturing Screenshots on a Mac

Shane Gibson — Sat, 06 Nov 2010 07:27:48 +0000

Because I always forget!

To capture the entire desktop, press Command-Shift-3. The screen shot will be automatically saved as a PNG file on your desktop.

To copy the entire desktop, press Command-Control-Shift-3. The screen shot will be placed on your clipboard for you to paste into another program.

To capture a portion of the desktop, press Command-Shift-4. A cross-hair cursor will appear and you can click and drag to select the area you wish to capture. When you release the mouse button, the screen shot will be automatically saved as a PNG file on your desktop. (The file is saved as PDF in Mac OS 10.3 and earlier.)

To capture a specific application window, press Command-Shift-4, then press the Spacebar. The cursor will change to a camera, and you can move it around the screen. As you move the cursor over an application window, the window will be highlighted. The entire window does not need to be visible for you to capture it. When you have the cursor over a window you want to capture, just click the mouse button and the screen shot will be saved as a PNG file on your desktop. (The file is saved as PDF in Mac OS 10.3 and earlier.)

Add Control to the two shortcuts above to place the screen shot on the clipboard instead of saving it to the desktop.

Another method for capturing screen shots in Mac OS X is by using the bundled Apple utility, Grab, located in the Applications > Utilities folder. Grab is useful if you need to include a cursor or a menu in your screen shot, or if you want to save your screen shot to TIFF format. To include a cursor, first go to Grab Preferences and select the cursor icon you wish to have in your screen shot. To capture the screen with Grab, run Grab, then choose of the capture modes from the “Capture” menu: Selection, Window, Screen, Timed Screen.

When you choose the Selection mode in Grab, you can capture a specific region of the screen by dragging around it. Grab will display a tooltip showing the size of the region you have selected and the screen shot will open in a window when you release the mouse button. The cursor will not be included.

When you choose the Window mode in Grab, an instruction window will appear asking you to select the window you wish to capture, then click the “Choose Window” button. When you click the button, the instructions will disappear and the window you click ill be captured, including the mouse cursor at the position where you click (if a cursor was selected in Preferences).

When you choose the Screen mode in Grab, an instruction window will appear asking you to click the screen when you are ready to capture. The mouse cursor will be included in your screen shot at the position where you click (if a cursor was selected in Preferences).

When you choose the Timed Screen mode in Grab, an instruction window will appear, allowing you to prepare your screen for capture. When you are ready, press the “Start Timer” button and you will have ten seconds before the screen is captured. This allows you to open menus and sub-menus, if necessary. After ten seconds the entire screen will be captured. The mouse cursor will be included in your screen shot if a cursor was selected in Preferences.

SAS 9.2 Third Party Sofwtare Dependencies and Versions

Shane Gibson — Mon, 03 May 2010 00:26:17 +0000

I have been doing a bit more Solution Architecture work around SAS 9.2 lately, and I keep needing to validate what versions of Operating System works with what version of SAS etc.

So here are the links (please note I have only included links to SAS 9.2 TM2Mx, not TM1M0):

Transforming SAS Dates – From here to there, funny things are everywhere

Shane Gibson — Thu, 29 Apr 2010 07:39:25 +0000

Every now and again I get to right some SAS code.

And every know and again I need to transform SAS dates, from Date/Time to Date9 or from Date to Date/Time etc.

Its one thing that I always end up looking at SAS support for the correct syntax. So Im going to post each one I use here so I can find them easily.

SAS Date to Date/Time

To convert a SAS date to a SAS Date/Time, by adding a time of 00:00:00 to it use:

dhms(,0,0,0)

SAS 9.2 Users Connection profiles

Shane Gibson — Mon, 05 Apr 2010 08:41:42 +0000

In SAS 9.2 two different typos of connection profiles are stored for each user, one for windows applications (AMO, EG etc) and the pother for Java applications (DI Studio, Info Map Studio etc).

Java Applications:

Connection profiles are stored on the hosts of the desktop applications at C:\Documents and Settings\user name\Application Data\SAS\MetadataServerProfiles. In the Windows Vista operating environment, the path is C:\Users\user name\AppData\Roaming\SAS\MetadataServerProfiles. The names of the profiles use the file extension.swa.

Windows Applications:

These profiles are stored in the ConfigurationV42.xml file in the users home directory C:\Documents and Settings\user name\Application Data\SAS\MetadataServerProfiles.

And of course recommended good practice is to only change these files via the profile editing capability provided within each of the SAS client applications.

SAS 9.2 Migration – Migrating Formats

Shane Gibson — Fri, 19 Mar 2010 07:22:18 +0000

And following on with the theme of migrating SAS formats …..

SAS Support article here:

http://support.sas.com/kb/22/194.html

Outlines how to migrate formats across SAS systems.

Basically you just:

1) Export the formats to a transport file by using the follwing code:

  libname library 'location-of-existing-formats-catalog';
  libname trans xport 'transport-file-name';
  proc format library=library cntlout=trans.cntlfmt;

2) Import the formats from the transport file using the following code:
  libname library 'output-library-for-format-storage';
  libname trans xport 'transport-file-name-from-sending-site';
  proc format library=library cntlin=trans.cntlfmt;

This is of course assuming you don’t have the code that originally created teh formats, because you could just run that instead. But bet you dont as you have just searched for something that made you find this blog post

A list of SAS 9.2 procedures

Shane Gibson — Wed, 17 Mar 2010 09:13:33 +0000

If you are ever looking for a list of SAS 9.2 procedures or trying to work out what SAS product you need to buy to use a certain procedure, you can find them here on the SAS support site:

SAS Procedures by Name
SAS Procedures by Product

SAS Access – Who plays nicely with who(m)

Shane Gibson — Sat, 06 Mar 2010 08:59:54 +0000

Just saw this post on Chris H’s blog here and I am replicating it so I can find it when I need it. (cause half my posts are there so I can find them when I need them)

If you want to know what version of SAS/Access works with what operating system and what release and what database etc, then look here:

http://support.sas.com/matrix/list?SAS=All&Engine=All&OS=All&googleTrack=on

Summary of SAS 9.2 Migration Course Tweets

Shane Gibson — Wed, 02 Dec 2009 04:17:14 +0000

Well course is over and I passed, so wahoo for me!

I am blogging all my tweets from the course so it is easier for me to search them in the future.

SAS 9.2 Folder tree permissions may remove the requirement to have multiple application server definitions to secure libraries about 2 hours ago from web

You can review the DI Studio migration reports at \Lev1\Logs\Config\ETL~.log about 2 hours ago from web

When migrating you lose all your WRV/WRS report schedules and will need to recreate them about 2 hours ago from web

EG automated migration mappings don’t work (yet) – Last bit on this page http://tinyurl.com/m48bzx about 3 hours ago from web

Users Subscription Profiles (Publish and Subscribe) have to be recreated in SAS 9.2 by an Admin user. about 3 hours ago from web

An error occurs when you exit SAS® Enterprise Guide http://support.sas.com/kb/33/988.html about 3 hours ago from web

Migrating EG 2.x to EG 4.2 http://support.sas.com/kb/35/922.html about 3 hours ago from web

EG migration support note: http://support.sas.com/kb/37/956.html, about 3 hours ago from web

Special Considerations for Customers Upgrading to SAS 9.2 http://tinyurl.com/yc7hlmc about 3 hours ago from web

Remember to clear the WRS Query Cache before doing SMU about 4 hours ago from web

Wonder what this new SAS 9.2 web url does? /SASBIPortlets about 4 hours ago from web

SASMeta has a workspace server to run promotion/replication and backups about 4 hours ago from web

SAS 9.2 SMC now has a metadata analyse and repair utility built in. Metadata Manager > Active Server (right Click) about 4 hours ago from web

You should probably run Proc Metacleanse before the migration: http://support.sas.com/kb/33/577.html about 20 hours ago from web

In 9.2 by default there are now 2 application servers, SASApp and SASMeta. about 20 hours ago from web

SMU will migrate Portal Content, Partial/Manual promotion won’t. about 22 hours ago from web

Partial/Manual promotion won’t migrate users Data explorations about 22 hours ago from web

Users folders move to new My Folder about 22 hours ago from web

BIP Tree structure in 9.2 is the same as 9.1.3 about 22 hours ago from web

Export cubes via OLAP Cube Studio (SP4) export function and import into 9.2 about 23 hours ago from web

M2 should look for STP .sas files outside config path and migrate them. about 23 hours ago from web

Macro libraries outside config path need to be manually migrated. about 23 hours ago from web

SASContent server defaults to web app server (i.e 7001) so publish to webdav code needs to be chnaged from 8300 about 23 hours ago from web

Collection Portlet links may need to be updated, new tool in M2 to automate this. about 23 hours ago from web

Upgrade LSF and apply SMC hotfix before migration. about 23 hours ago from web

DI jobs need to be manually redployed about 23 hours ago from web

Issue with AD load, fixed in M3. http://support.sas.com/kb/37/099.html 3:50 PM Nov 30th from web

AD syncronisation scripts will need to be changed 3:49 PM Nov 30th from web

OMAbackup has been changed 3:49 PM Nov 30th from web

Security migration auditing and validation http://tinyurl.com/ylo6hnw 3:42 PM Nov 30th from web

9.1.3 to 9.2 migration guide http://tinyurl.com/dypcjo 3:30 PM Nov 30th from web

Port remap utility is part of M2 3:28 PM Nov 30th from web

All other hotfix levels (windows) are in \windows\vpd.properties 2:52 PM Nov 30th from web

Check hotfix level (windows), \Program Files\SAS\SAS 9.1\core\sasinst\hotfix 2:47 PM Nov 30th from web

To check Service Pack level for foundation invoke base SAS on the server 2:45 PM Nov 30th from web

Must add -davtier when running SMU on web tier 2:31 PM Nov 30th from web

Always run SMU on metadata tier first 2:31 PM Nov 30th from web

SMU doesnt doesnt bring across settings in the WRS LocalProperties file 1:49 PM Nov 30th from web

Rename the “SAS Administrators” group before running the Automatic Migration 1:36 PM Nov 30th from web

When migrating from 32 bit windows to 64 bit windows, you should run Proc Migrate on the datasets to upgrade them to 64 bit format 1:12 PM Nov 30th from web

SAS Deployment Wizard (SDW) has a capture/replay capability to record the install and automate it. 7:17 PM Nov 29th from web

Browser based SMC http://server:port/SASAdmin 6:23 PM Nov 29th from web

SAS 9.2 you can turn object spawner logging on and off in SMC without having to restart the object server 6:09 PM Nov 29th from web

9.2 supports 2 external Token Authentications, WebSeal and Siteminder 6:04 PM Nov 29th from web

Internal Accounts allow access to metadata realm, SAS Token Authentication allows access to SAS Compute Server realm 6:02 PM Nov 29th from web

You need to use Kerberos in 9.2 to utilise Integrated Windows Authentication (IWA), which is windows based SSO as you need more than one hop 5:58 PM Nov 29th from web

By default Workspace Server doesn’t use Token Authentication, the other servers (i.e OLAP, STP, Table, Content, Pooled Workspace) do. 5:46 PM Nov 29th from web

SAS Token Authentication doesn’t work for outbound authentication (i.e Oracle) 5:43 PM Nov 29th from web

After default install change Policy “Allow user login from web logoff page” in config mgr, SAS Application Infrastructure – right click 5:33 PM Nov 29th from web

9.1.3 Inhertitance toolpool plugin for SMC is now std in 9.2 SMC 5:29 PM Nov 29th from web

New metadata permission “WriteMemberMetadata” allows you to create tables in a library, but not change permissions on library. 5:27 PM Nov 29th from web

Access unregistered plugins grants access to non-standard jars/plugins in SMC 5:26 PM Nov 29th from web

Public is automatically added to all roles in the default install. You then need to start removing them to lock things down. 5:17 PM Nov 29th from web

User and/or group can be assigned to roles. Roles are additive, you have to be assigned a role with the capability to use the function. 5:16 PM Nov 29th from web

New metadata security type = roles (think groups). Roles maps to capabilities (think applications/menus/functions). 5:14 PM Nov 29th from web

SAS 9.2 Deployment Manager Tool allows you to change a SAS system account password in all places at once. 5:10 PM Nov 29th from web

sassrv must stay as a externally authenticated account as it it needs to authenticated externally to run STP, Workspace servers etc 5:05 PM Nov 29th from web

SAS Metadata now does authentication (for/titled internal accounts), must user username@saspw construct. 4:52 PM Nov 29th from web

SAS have a script to backup Content Server, part of SAS Consulting install, not base install 3:37 PM Nov 29th from web

There is a new Web Administraton Console, cut down version of SMC 3:30 PM Nov 29th from web

SAS Logon Manager (part of Web Infrastructure Platform – WIP, used to be WIK) now handles login for all mid-tier applications 3:30 PM Nov 29th from web

SAS has paid for JBoss support subscription. So tech support can leverage this for patches where required (so be nice to tech support 3:25 PM Nov 29th from web

Still cant promote Pages & Portlets in 9.2 2:56 PM Nov 29th from web

You can promote OLAP Schema’s/Cubes 2:55 PM Nov 29th from web

You can promote EG projects (if they are stored in Metadata) 2:55 PM Nov 29th from web

SAS 9.2 has batch promotion functionality, yeeha! 2:54 PM Nov 29th from web

BI Manager disappears, Import/Export now part of folder options. 2:53 PM Nov 29th from web

SAS 9.2 Metadata repair/validation tool based on Proc Metacleanse 2:50 PM Nov 29th from web

Metadata Server is now in UTF-8 compressed format, should reduce disk space (quite a bit-ish!) 2:47 PM Nov 29th from web

SAS Table Server is multi-user read/write based on firebird. 2:41 PM Nov 29th from web

SAS Table Server provides a mapping to SAS Datasets, removes the ability for users to see where the SAS Datasets are stored. 2:39 PM Nov 29th from web

SAS 9.1.3 Web Report Viewer disappears in 9.2 and is now part of Web Report Studio. 2:36 PM Nov 29th from web

SAS 9.2 Web/Java apps moved from .WAR to .EAR 2:36 PM Nov 29th from web

SAS 9.2 Content Server replaces WebDav (Xythos/Apache) 2:32 PM Nov 29th from web

SAS Foundation Services (9.1.3) allowed Java apps to talk to the metadata server, effectively an interface/translator for Java 2:28 PM Nov 29th from web

SAS 9.2 Mid Tier now uses UDP as well as TCP so firewall must be open to allow this. 2:20 PM Nov 29th from web

New server – Pooled Workspace Server, used by WRS for server side pooling (diff to std workspace server that is spooled) 2:04 PM Nov 29th from web

Stored Process Servers now only uses one port – no longer multiple load balanced ports 1:58 PM Nov 29th from web

9.2 OLAP server drill through now uses OLAP server rather than a workspace server session means double the number of OLAP Server connections

SAS 9.2 External Identities

Shane Gibson — Tue, 01 Dec 2009 22:20:03 +0000

SAS 9.2 now has the concept of External Identities against a user or group.

The following is an extract of the online help:

About External Identities

What is an External Identity?

While logins and internal accounts are involved in the log on process, external identities are not. An external identity is an optional synchronization key for a user, group, or role. If you use batch processes to coordinate SAS identity information with your primary user registry, you need external identities (such as employee IDs) to facilitate matching. This list explains the circumstances in which a user, group, or role needs an external identity:

For a user, group, or role that you maintain interactively in SAS Management Console, no external identity is needed.
For a user, group, or role that you maintain using batch processes, one external identity is needed.

Where do External Identities Come From?

External identities can be added in these ways:

For a user, group, or role that is created by an import process, an external identity is added as part of that process.
For any user, group, or role, you can interactively add an external identity on the General tab of their definition.