About ChrisBrooks

ChrisBrooks · ‎02-14-2018

In my opinion you should ALWAYS set an explicit length for your character variables. If you don't you could end up with the same variable on different files having different lengths which could lead to problems if you try to to append or merge them.

ChrisBrooks · ‎02-09-2018

It sounds like some sort of memory leak or disk space issue although 1.8M obs isn't that huge. Try increasing the amount of available memory with the Memsize option http://support.sas.com/documentation/cdl/en/hostwin/69955/HTML/default/viewer.htm#n0srij4mcdpzv2n1vtphltb00xjw.htm although note that this has to be done at invocation of the session or in the config file.

ChrisBrooks · ‎02-06-2018

I'm not sure that you can do this either unless @ChrisHemedinger or @OliviaWright know a way. However you can do this already with the supplied Query Utility so you may not need a Custom task after all...

ChrisBrooks · ‎02-06-2018

I'm not entirely sure why you're code isn't trapping those errors but I would strongly recommend fixing the SAS code outside of an IOM call anyway. When calling SAS from another language I always use a test harness which attempts to emulate the call from within SAS as it's much easier to resolve issues. In your case I think the "Format Couldn't be Loaded" error is caused by a missing FMTSEARCH option telling SAS where to look for the stored custom format and if you add that to your SAS program you should resolve that issue. The "Open Code Statement Recursion" error is impossible to give advice on without seeing the SAS code as it could be caused by a multiplicity of issues.

ChrisBrooks · ‎02-02-2018

This isn't really my field but it seems Proc Freq might be able to give you what you want - documentation here -> http://support.sas.com/documentation/cdl/en/procstat/67528/HTML/default/viewer.htm#procstat_freq_details63.htm and here -> http://support.sas.com/documentation/cdl/en/procstat/66703/HTML/default/viewer.htm#procstat_freq_details80.htm

ChrisBrooks · ‎02-02-2018

This question was asked before - you'll find the solution here https://communities.sas.com/t5/SAS-Analytics-U/Virtual-Box-error-kernel-requires-an-x86-64-CPU/td-p/317016

ChrisBrooks · ‎02-02-2018

Your data files should be fine as long as you make the same shared folders as you had before the reinstall. If you're happy with the fix could you mark the solution as accepted please? It helps others who might have the same problem and also saves people reading through a problem which is resolved when they were looking to help

ChrisBrooks · ‎02-01-2018

As the other contributors have said a merge may be your best bet - alternatively an SQL join might also be able to do what you what which you may find easier if you come from an SQL background.

ChrisBrooks · ‎02-01-2018

There's a post on another forum https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225288 which suggests the error is caused by updating VirtualBox while a VM was paused/suspended. There's no suggested fix so you might either try reverting to the previous version of VirtualBox or deleting and reinstalling University Edition after a fresh download of the OVA file. I know there was a recent update to VirtualBox so I'm guessing that's what happened.

ChrisBrooks · ‎02-01-2018

SAS Enterprise Guide includes SAS base (which is the foundation for all SAS environments) but if you want to retain the classic SAS Display Manager you could look at running SAS in Client/Server mode using SAS Connect. You'll find the documentation here -> http://documentation.sas.com/?cdcId=pgmsascdc&cdcVersion=9.4_3.3&docsetId=connref&docsetTarget=p12j8b6w2nuxpon15xu0fqsisfkk.htm&locale=en

ChrisBrooks · ‎01-25-2018

The problem isn't with app_sys_no - it's because obligor is, presumably, character and 0 is of course numeric. If you change your case statements to read as follows you should be OK count(distinct (case when app_sys_no = '337' then obligor_no else "" end)) as Cnt337, count(distinct (case when app_sys_no = '339' then obligor_no else "" end)) as Cnt339, count(distinct (case when app_sys_no = '342' then obligor_no else "" end)) as Cnt342, count(distinct (case when app_sys_no = '362' then obligor_no else "" end)) as Cnt362

ChrisBrooks · ‎01-23-2018

To be honest 1,500 lines of code isn't really the problem (I've seen much bigger programs) it's the quantity of data and how it's being processed which is causing the long run time. You could set the errorcheck option to STRICT as documented here -> http://documentation.sas.com/?docsetId=lesysoptsref&docsetTarget=n074sx2hkq8dzpn1ptoydcmzfspt.htm&docsetVersion=9.4&locale=en or use the errorabend option but that will terminate the whole session leaving you no wiser as to what went wrong....

ChrisBrooks · ‎01-23-2018

That seems odd - I think your best bet would be to raise a track with SAS Support

ChrisBrooks · ‎01-22-2018

You shouldn't need a Federation Server licence for this - I suspect there may be something wrong with your ODBC connection. Are you able to successfully connect and run some "old school" SAS i.e. not DS2 code against the data source using the same connection string?

ChrisBrooks · ‎01-21-2018

The update often fails - your best bet is to download the VM again from scratch - delete the existing VM from inside VirtualBox and install the new VM - you won't lose any work.

Online Status	Offline
Date Last Visited	‎10-08-2024 11:59 PM