Explore using the SAS function INTNX for this type of date calculation, such as: ( INTNX('QTR',TODAY(),-1) LE your_date_var LE INTNX('QTR',TODAY(),-1,'E') ) Scott Barry SBBWorks, Inc. ... View more

The DATA step, in general, is the source, even if there is no SET statement. Suggest you set the FILEMSGS option for more complete diagnostics. Also, you should consider sharing SASLOG output (and local/foreign FTP environments, SAS version info) for more accurate assistance/guidance from forum members -- your first DATA step should have worked fine, presuming you are able to FTP to that machine outside of SAS, with native FTP client on your OS platform. Recommend that you first confirm you are able to use FTP (native), and then with FILEMSGS set, test FTP under SAS. Scott Barry SBBWorks, Inc. ... View more

Oooo - kewl! Never used SYMPUTX. Thanks much for the tip! ... View more

It's only that using MACRO language increased the PITA effect for debugging, because....let's see, where should I start...NO LINE NUMBERS REVEALED!! Sorry, increased cuban coffee consumption this Friday. Understandably, some have an aversion to embracing the SAS macro language unless absolutely required. Scott Barry SBBWorks, Inc. ... View more

Depending on your OS, review the SAS functions such as FILEEXIST (as well as other like-purpose functions) and you can use %SYSFUNC with one of these functions in a macro. If you want to maintain your DATA step outside the macro, set a %GLOBAL statement at the start of your macro and test the "&MYGLOBAL" in a DATA step IF, placed "BEFORE" the SET statement, and issue a STOP when you have detected that the path does not exist. Also, consider that the entire DATA step could be executed within your macro, using SAS macro language SAS data member read functions, FOPEN, FREAD, FCLOSE. Suggest you scan the SAS.COM support site for examples and SUGI/SGF papers on these topic-areas; also there is a related link pasted below. Scott Barry SBBWorks, Inc. http://support.sas.com/documentation/cdl/en/lrdict/59540/HTML/default/a000210912.htm ... View more

This item may or may not be applicable to your situation. SN-009465 ***Alert Note*** Nested logit parameters estimates equal to zero with zero degrees of freedom Product: SAS/ETS Component: MDC procedure Priority: ALERT http://ftp.sas.com/service/techsup/tsnews-l/0366.html http://support.sas.com/rnd/app/papers/mdc.pdf ... View more

After reading and sorting your input, use a DATA step to input your sorted data, and assign your GROUP (based on using RETAIN statement variable), as your have explained. And if you know all possible COMMENT values, consider using a PROC FORMAT to read-up your input data, which would minimize your need for IF/THEN logic to assign GROUP. Remember that PROC FORMAT can handle character-data range, such as your "starts with", but the VALUE statement or CNTLIN= coding is a bit tricky. If you do not have a large-volume of unique COMMENT strings, maybe the DATA step IF/THEN approach is sufficient, rather than the time required to setup a PROC FORMAT approach. Scott Barry SBBWorks, Inc. ... View more

Please read my most recent reply - the function INDEXC was suggested where it should be a different function to determine the number of variables. Scott Barry SBBWorks, Inc. ... View more

You may want to explore the SAS DATA STEP functions INTCK and also INTNX; the latter function can be helpful with generating DATE and DATETIME variable values, based on other variables. For example, you can use a DATA STEP DO/END loop to generate (OUTPUT) SAS observations for each date value in a date-range, say for the past 12 months or 26 weeks. Scott Barry SBBWorks, Inc. ... View more

A Google.com search against the SUBJECT words revealed the PROC REG DOC link below. If you want to limit your search to the SAS.COM website as I like to do, you can add the "advanced search" option site:sas.com The SAS.COM support website hosts a complete set of all SAS software documentation, an incredible benefit for its user community. Bookmark it for frequent reference. Scott Barry SBBWorks, Inc. The REG Procedure - Model Fit and Diagnostic Statistics http://v8doc.sas.com/sashtml/stat/chap55/sect37.htm ... View more

Frankly, how do you expect to learn, otherwise. Attaining an reputation as "experienced SAS programmer extraordinaire" through a burn-in phase requires self-diagnostic iteration -- something more than just trolling the Internet forums, I'd suggest. It's your program, your input data, your information processing requirement, programming composition, etc., therefore I encourage you to gain from what you learn here and go-forward. Others may have their own opinions and are free to share. I tend to guide rather than push. To that end, I suggest you investigate each of your INFILE statement parameters, pare down your SAS code to the bare minimum, and run various GENKEY value scenarios, in order to learn from the SAS VSAM programming/processing behavior. Good luck. Scott Barry SBBWorks, Inc. ... View more

Presumption here without a date contribution is that the DHMS function will increment the "end" variable by 86400 seconds, assigning the DHMS argument1 to a value of 1, as in: if end lt start then end = DHMS(1,0,0,end); So, without a "date", the surgery duration must be within a presumed 24 hour period. Scott Barry SBBWorks, Inc. ... View more

Use PROC SQL to generate the macro variable, as demonstrated. Then code a DATA step with a RETAIN statement, specifying your desired SAS data variable name, and initialize the variable with the "generated" SAS macro variable, specified in double-quotes (not single-quotes -- otherwise the macro var is not going to be resolved). Scott Barry SBBWorks, Inc. ... View more

Regarding the first DATA step in the previous post, I believe you want to use the SAS function (new with v9) COUNTW instead of INDEXC, such as: data _null_; infile datalines dsd dlm='|'; input; call symput('ANTVAR',cat(countw(_infile_,'|'))); stop; datalines; 1|2|3|4|5 run; %put Survey Says? Input &antvar variables; Regards, Scott Barry SBBWorks, Inc. ... View more

Your end-of-file PUTLOG generated part of the diagnostic with the _INFILE_; Simplify your DATA step by removing the DO loop. If you need to test FDBK, conditionally output if FDBK=0, and then use END=EOF DO/THEN if you need to generate some SASLOG end-of-processing messages. Scott Barry SBBWorks, Inc. ... View more