If not interested in using MACRO language, consider using CALL EXECUTE to assign a SAS variable that contains each of your well-defined PROC steps. No array needed - just generate the SAS code and the steps will be executed serially after your main DATA step completes. Scott Barry SBBWorks, Inc. ... View more

From the SAS support website and its incredible resource of code snippets and examples -- which I found using a GOOGLE.COM advanced search with site:sas.com to limit the search: Sample 25976: Create a macro variable that contains a quoted list http://support.sas.com/kb/25/976.html Scott Barry SBBWorks, Inc. ... View more

Curious if you want to treat the problem or symptom here? Do you consider the messages generated to be a normal condition or maybe you could share some of the SASLOG output for forum feedback? If necessary though, one option is using PROC PRINTTO to re-direct your SASLOG to a permanent file on your local system. Scott Barry SBBWorks, Inc. ... View more

If your time-range crosses midnight, you will then need to introduce the DHMS function as well. Scott Barry SBBWorks, Inc. ... View more

One technique of several - use a DATA step and code an INPUT; statement (no variables listed). Then use the _INFILE_ variable within a DO/END loop to parse your individual fields with the SCAN function. Scott Barry SBBWorks, Inc. ... View more

Share your SAS code and ideally some SAS-generated HTML code, if at all possible. Scott Barry SBBWorks, Inc. ... View more

Use a SAS DATA step, and code a DO I=0 TO 23; and use the HOUR function to test your start and end variable range, marking your HR00 through HR23 variable with a 1 or 0, if the a test matches within the start and end time ranges. Scott Barry SBBWorks, Inc. ... View more

If you expect to get an accurate response, it's most important to share your SAS code up-front. And without that, it's conjecture at best, frankly. Scott Barry SBBWorks, Inc. ... View more

Have a look at this SUGI/SGF technical paper. http://www2.sas.com/proceedings/forum2008/180-2008.pdf Scott Barry SBBWorks, Inc. ... View more

Ran your code. Did you notice the message below in your SASLOG? NOTE: DATA STEP stopped due to looping. Scott Barry SBBWorks, Inc. ... View more

For example, not having seen your code, if you are using a PUT statement in a DATA step, you must also code +(-1) to suppress the implicit blank (equivalent of back-up one space) between variables unless you have an explicit format length in the PUT statement for the SAS variable display. Scott Barry SBBWorks, Inc. ... View more

Best option is to share what code you have tried for a most meaningful and accurate response. Scott Barry SBBWorks, Inc. ... View more

No problem here (ThinkPad T61, Windows XP Pro SP3 with 4GB RAM) with merging 10,000 one-variable files and no BY statement. Your error message is a bit odd sounding, as you showed in your post. Start with a small subset of files, get that working, and then work your way up to a larger set of files for your merge, to confirm your process works. Scott Barry SBBWorks, Inc. ... View more

Though I have no experience, the SUGI/SGF paper below mentions a two-level drill-down generated by HTMSQL in a single HTML document with multiple queries, although the HTML tags are suppressed. The SAS Support team know their stuff, so like Cynthia mentioned, your quickest route to success would likely be to open a track with your question and provide any / all details about requirements you have collected. Scott Barry SBBWorks, Inc. Experience Learned in Deploying htmSQLâ Based Application http://www.dc-sug.org/htmsql.pdf ... View more