About Doc_Duke

Doc_Duke · ‎04-09-2013

check out this SUGI proceeding http://support.sas.com/resources/papers/proceedings11/091-2011.pdf Doc Muhlbaier Duke

Doc_Duke · ‎04-08-2013

Ram, I think that this is just a definition problem. All character variables in SAS are fixed length. The LENGTH function measures the number of characters, from the left, to the last non-blank character on the right. Therefore, your x_var and x_new_var would both show as having the same LENGTH when you use that function. Doc Muhlbaier Duke

Doc_Duke · ‎04-05-2013

This may be key: "data was added in them incrementally with increasing values of indexes," In a number of database systems, when data are appended, the index just does a linear search (e.g. does not really use the index) for observations after the first appended one. If SAS works that way, then dropping the index and rebuilding it will cure the problem. If you try it, let the list know what you find out. Doc Muhlbaier Duke

Doc_Duke · ‎04-04-2013

M.A.C., Seeing your other post, you have a huge incoming dataset. Judicious use of the KEEP statement or option will significantly reduce work data set size; EGuide does that as well as using VIEWs when you are using the task interface. In a shared server environment, putting the WORK space on a separate spindle can do marvels. It can also be treated as a separate drive and not backed up. Also in a shared server environment, the problem may be someone else's and you may be "collateral damage". The network admin can tell you if others are using all the space. As Astounding said, the server environment can make a big difference; maybe you could tell us more about your work setup. Doc Muhlbaier Duke

Doc_Duke · ‎04-02-2013

There are lots of ways for the e-mail interface to fail. A couple of things to check: your system options (e-mail ones start with EMAIL). the type of e-mail service (MAPI or SMTP) do you have access to SMTP? Your network admins can block that. Doc Muhlbaier Duke

Doc_Duke · ‎04-01-2013

Try using the EXCEL engine; XLS only supports through Excel 2003. See the documentation for SAS/Access for PC FIle Formats.

Doc_Duke · ‎03-26-2013

see previous discussions

Doc_Duke · ‎03-20-2013

Nicnad, Have you read the documentation? That is not what the LEFT and RIGHT functions do. They are character string functions that just align the non-space part to the left or right in the string. If the date filed is a text string, then you can get the first 4 characters as 2007 by left(TXNS.DateOperation,4) =: "2007" (not the "=:" operator). If it is a SAS Date variable, then it would be year(TXNS.DateOperation) = 2007 It looks like MontantOperation is numeric, in which case you need to either convert it to a string and pick off the last two characters (check RIGHT, LENGTH, and SUBSTR documentation for syntax; there are other ways possible (like reversing the string)). Or by using some mathematical identities. If montantoperation is an integer, this should work floor(montantoperation/100) = montantoperation to pick off numbers that are multiples of 100. Doc Muhlbaier Duke

Doc_Duke · ‎03-18-2013

HI, I haven't used MIXED in quite a while, so I can't help you on the specifics. If you post the section of your log with the error message, maybe someone else can help. Doc Muhlbaier Duke

Doc_Duke · ‎03-07-2013

from the reference manual "Interaction:If length is zero, a negative value, or larger than the length of the expression that remains in string after position, SAS extracts the remainder of the expression. SAS also sets _ERROR_ to 1 and prints a note to the log indicating that the length argument is invalid."

Doc_Duke · ‎03-07-2013

RTFM. Your code should read sch=substr(cdcode,8,7);

Doc_Duke · ‎03-07-2013

Tom, It ran fine in batch for me (Win 7 Pro x64, SAS 9.3 TS1M1 32bit); I got the same thing you did for interactive SAS. Rather than running that long script, try running it by right-clicking on the program icon and then submitting in batch. That will tell you whether the problem is in your SAS install or something that you need to tweak in the script. Also check the top of the batch log for warnings about missing configurations or something similar. Doc Muhlbaier Duke

Doc_Duke · ‎03-06-2013

For the first, see 1528 - ERROR: The character variable XXX has too long a value for the SASV5XPTengine. For the second, 14181 - XPORT engine does not support SORTEDBY operations. SORTEDBY informationcannot be copied Just search support.sas.com with part of the error message to find the answer to this sort of question.

Doc_Duke · ‎03-04-2013

I would be hesitant to delete individual files without knowing what they are. Here are a couple of ideas clean up your disk drive: 1) SAS may have left some temporary files around from previous runs that crashed. You can clear those out by exiting all parts of SAS and then going to the work area and deleting all the temp stuff that is left. 2) it may not be SAS that has gobbled up the space. Use a utility like cleandisk to clear out all of Microsoft's temporary files. 3) when you start an EGuide project, SAS makes a copy. You might save some space by cleaning up the project and using EGuide's Save As to get a clean and compacted copy. 4) By default, EGuide creates views, so it's temporary files are small. Check your save options to make sure it is using views on WORK. Doc Muhlbaier Duke

Doc_Duke · ‎02-28-2013

This is a common problem in epidemiology for case-control matching. A typical problem there might be matching by nearest age within 5 years. It is also called proximity matching. A generalization to multiple variables is often done by propensity score matching. If you search for those terms on sas.com, you will find a number of examples to choose from. Doc Muhlbaier Duke

Online Status	Offline
Date Last Visited	‎05-03-2025 03:08 PM

Re: Chi-Square WARNING

Re: Exposure-adjusted event rate

Re: Time to event analysis- ADTTE

Re: How can I Find Code that opens a given dataset?

Re: How to extract date from start date (description part) and create ...

Re: ERROR: No valid observations are found.

Re: setting VALIDVARNAME as the default for the duration of the sessio...

Re: SAS Enterprise Guide Project Size Increasing with no changes

Re: How to calculate confidence interval for crude rate by using age g...

Re: Why will my proc lifetest code not work?

Re: Invalid third argument to function SUBSTR

Re: Cleanwork command for /saswork and /sasutil cleanup

Re: Why this message “Data set Limit Reached” appear in “Project Tree...

Re: Chi-Square WARNING

Re: Power calculation for proportions

Maxims of Maximally Efficient SAS Programmers

Re: Global English Guidelines for Community Members

Re: Sequence Number

Re: padding blanks on variable values

Re: Ineffective index

Re: Error Disk full or maybe damaged

Re: How to send sas output to email

Re: Proc export problem?

Re: Learning sas programming - Advice needed

Re: SQL procedure in SAS - Left function in where statement

Re: PROC MIXED, PROC CALIS...

Re: Invalid third argument to function SUBSTR

Re: Invalid third argument to function SUBSTR

Re: Problem with variable names when batching SAS

Re: Issue in creating xpt files

Re: SAS EG - Releasing Temporary memory

Re: Finding like records in a table