About ArtC

ArtC · ‎11-01-2012

The period or dot used with a format name is a parsing character. It is needed so that the parser can detect a difference between a format name and a variable name. In the macro language this is not necessary as there are no data set variables, only macro language elements (that start with a macro language trigger - & and %), and non macro language elements, which don't start with a trigger. functions such as the INPUT function know that the second argument is a format, so in the macro language the period is not necessary. I suspect that we should be grateful that the periods don't cause problems.

ArtC · ‎11-01-2012

You are very close. The macro reference is indeed broken into parts - left to right. Non macro elements are passed along for each pass. for this example say that &m2 contains the text: Fred &&m1&m2 && m1 &m2 & m1 Fred &m1Fred A good way to learn how more complex macro variables are resolved is to use symbolgen. something like. options symbolgen; %put &&m1&m2;

ArtC · ‎11-01-2012

You might also consider building a picture format. For a datetime value you could use something like the following: proc format; picture dbdate other = '%Y-%0m-%0d:%0H:%0M:%0S' (datatype=datetime); run; The %Y, %m, etc. are directives that can be used with picture formats. There are over a dozen of them and they can be very helpful when working with date, time, and datetime values.

ArtC · ‎10-31-2012

Art T is correct. Because macro language elements are executed before the Program Data Vector, PDV, has been established, macro functions cannot work with values on the PDV (data step variable values, and such). The macro language primarily works with text, it is afterall a code generation language. You can think of text as being keystrokes that may eventually become a part of your program.

ArtC · ‎10-31-2012

Your compute block was not included in your post so we cannot actually see the code. My initial guess is that there is a logic issue with the assignment of the path information (URL). More information can be found here: http://www.wuss.org/proceedings09/09WUSSProceedings/papers/how/HOW-Carpenter.pdf

ArtC · ‎10-31-2012

The OF operator can also be used to eliminate the need for the commas. total=sum(of f2000-f2011);

ArtC · ‎10-30-2012

@RichardinOz I like the use of the SUM function over my statement. Much cleaner code.

ArtC · ‎10-30-2012

The variable NUM in the following step will contain the number of variables with a value of 0. data want; input A B C D; num = 1*(a=0) +1*(b=0) +1*(c=0) +1*(d=0); put num=; datalines; 1 0 0 2 3 1 2 0 4 2 8 4 0 6 1 9 run;

ArtC · ‎10-30-2012

Are you more concerned about preserving the attributes of GL? If so specifying the ATTRIB after the SET will not change the length but could change the label. Are you instead trying not to overwrite the value of GL if it already exists on the incoming data set?

ArtC · ‎10-30-2012

The X or SYSTASK statements should do the trick (as Doc@Duke suggests), however if you need more control to select certain types of files, try the FDELETE function. This function will delete any type of file, and since you are in the DATA step, this gives you a great deal of flexibility. For windows: filename list pipe 'dir "c:\temp\sasdat" /b/o'; data _null_; length fname $40; infile list truncover; input fname $; rc=filename('abc',catt("c:\temp\sasdat\",fname)); if rc = 0 and fexist('abc') then rc=fdelete('abc'); rc=filename('abc'); run;

ArtC · ‎10-30-2012

When reading delimeted files, PROC IMPORT writes a DATA step, though somewhat less sophisticated than the one written by DATA _NULL_ below. If you are running IMPORT from the Display Manager you can recover this program without copying from the LOG by using the RECALL command (under RUN) after executing the IMPORT . This can save a bit of editing of extraneous characters that will be a part of the LOG.

ArtC · ‎10-23-2012

@Jonam, Although I have not had it fail, I just recently learned that the SASZIPAM fileref engine is not recommended for use by SAS. http://support.sas.com/kb/31/244.html

ArtC · ‎10-19-2012

If your 'data files' are SAS data sets, there are a series of data set options that can be used to provide various levels of password and/or encryption. http://support.sas.com/documentation/cdl/en/ledsoptsref/63326/HTML/default/viewer.htm#n03k13diwk36x1n1az3mpixdfbfp.htm

ArtC · ‎10-19-2012

An earlier thread on memory usage and matricies can be found at: https://communities.sas.com/message/140513#140513 The system option for memory allocation is MEMSIZE. You may also get more detailed responses in the SAS/IML forum, which specializes in issues with matrix manipulation.

ArtC · ‎10-19-2012

The matrix being inverted seems a bit large, and memory may indeed be an issue. Have you tried increasing the memory buffers? Although it won't help with the memory, we can speed up the processing a bit by replacing your A[I,J] IF-THEN/ELSE assignment statements. r=ranuni(12345); a[i,j] = 0*(r<=.4)+.5*(r>.4);

Online Status	Offline
Date Last Visited	‎06-20-2021 07:11 PM