As a Colorado native, here are some of my suggestions for things to do in Denver...   1. Wynkoop Brewery - one of the original brew pubs in Denver and started by Gov. Hick, good beer, food and pool tables 2. The "Cruise Room" at the Oxford Hotel...not your typical hotel bar! 3. Denver Beer Co. - some of the funkiest beers you will find 4. The "LoDo" (lower downtown) area - next to Coors baseball stadium, lots of restaurants, brew pubs, etc.  5. For music fans, a couple of great CD & vinyl stores - "Twist & Shout" and "Wax Trax" 6. For great and authentic British style Fish & Chips, go to "GB Fish & Chips" on Broadway 7. If you have a car, Boulder, CO is only 30-40 minutes drive - main campus for the Univ. of Colorado and Pearl Street Mall 8. Longmont (Left Hand Brewery) and Fort Collins (New Belgium Brewery & CSU) are worth the visit, but longer drive - 1+ hour 9. There are a number of smaller music venues in and around downtown Denver as well. 10. Pick up a copy of the free Westword newspaper for all the latest happenings, best restaurants, concerts, etc.  Here's the link to the digital version:  http://www.westword.com/about/flipbooks ... View more

To all who are following this thread and or might read it: In my case, what triggered this error was the volume of data I was trying to process in the Proc Report set and output in PDF format. Initially, I didn't think of this because this Proc Report routine was / is a clone of another routine that runs successfully. The difference between the two are their data sources, which have the same structure, but differ significantly in their size (i.e # of OBS). Once this occurred to me, I performed a simple test on the routine that was failing by limiting the size of the input dataset and it worked properly. This issue appears to be primarily associated with the ODS PDF functionality because I was able to successfuly run the full dataset through the Proc Report routine, but to and ODS Excel output. I'm assuming it would work OK with the ODS HTML as well. As such, it does appear there is a memory limitation of some type with the ODS PDF functionality that doesn't exist in some of the other ODS formats. I was able to overcome this problem by basically separating my data and creating two separate reports (e.g. Group A Data Report and Group B Data Report). ... View more

Cynthia, Thank you for the input on this, these articles are helpful and do seem to support what SAS Tech Support believes might be occurring...that this is some type of internal Proc Report or ODS problem. The errors mentioned in these articles are very similar to the error I'm seeing...the "class method OM_NEW(3)" matches exactly. The errors in these articles are all related to using / running Java directly from a SAS session, which I'm not doing (at least directly). My assumption is that Proc Report is probably not using any Java sub-routines natively "under the covers", but the ODS functionality I'm guessing is another matter... The ODS style attribute I'm using is "Printer", so my next question(s) is / are: "what is the 'TCELL' in the ODS Printer style and what about the 'TCELL' would cause a memory error?" ... View more

Understood and have already opened a Tech Support case with SAS on this error. However, they don't have solution for this error at the moment. I did find a reference to this type of error on SAS-L from a couple of years ago, but no resolution. Just checking with the SAS Community...assumption being some one else might have encounter this or similar problem. ... View more

See the SAS 9.1 Companion for UNIX Environment, pg 13 "Executing Operating System Commands from your SAS Session". This explains it fairly well. You can use an "X" statement or "call system" statement from within a SAS session to jump out to the OS and run a command. ... View more