It would be best to share exact SAS code being executed, but do so as part of a COPY/PASTE reply to your post with the SAS-generated log, not just your code piece. Suggest you incorporate some SAS diagnostic command logic, like below, at various points in your DATA step logic flow to display data values -- also considering how you are coding any SAS DATE constants (with or without the year/century), as was mentioned previously: PUTLOG _ALL_; Most important, you need to share your SAS-generated log output with all code revealed to get further guidance, other than someone's guess. Scott Barry SBBWorks, Inc. ... View more

Suggest some SAS support website technical references and also SAS-hosted documentation, also available on the SAS support site at http://support.sas.com/ on this topic / post. Typically a FUNCTION provides a defined purpose/use to perform some type of task, calculation, data-manipulation, or otherwise utility execution in the SAS environment. And the MACRO FACILITY is a language used within the SAS environment, where SAS programmers can exploit coding techniques to perform executed-once or executed-repetitively task processes to address a particular programming activity or to generate some result with SAS. Scott Barry SBBWorks, Inc. Suggested Google advanced search arguments, this topic / post: function introduction site:sas.com macro introduction site:sas.com ... View more

The technical method / process will depend on your SAS OS environment. So, for Windows, consider using PROC DATASETS with KILL to clear the SAS library of all members followed by using the FDELETE function (either in a DATA step or with SYSFUNC using SAS macro language) to remove/delete an empty directory (or external file reference). Scott Barry SBBWorks, Inc. ... View more

Why would the OP want to manipulate a "date" string in character format, simply by dividing it, without any validation along the way? The power of SAS provides the data-accuracy and data-quality validation, which can be achieved using the INPUT function and the appropriate SAS INFORMAT. And, so, an invalid date will not be allowed to pass into the system. Then, also, additional SAS functions YEAR, INTNX, etc. can be exploited to derive additional useful data-variables, which can help the user improve their data analysis processing, as has been explained in this post-thread. Scott Barry SBBWorks, Inc. ... View more

Look at using the CALL SYSTEM function from a DATA step -- you generate your OS command syntax. Recommend reviewing the particulars in the OS-specific SAS "companion" guide available on the SAS support http://support.sas.com/ website, where you will find SAS-hosted DOC but also supplemental technical and conference reference material, available using the website SEARCH or an Internet search engine. Scott Barry SBBWorks, Inc. Suggested Google advanced search arguments, this topic / post: call system site:sas.com execute os commands site:sas.com ... View more

A straightforward SAS support SEARCH request (or Google advanced) reveals several relevant references. Scott Barry SBBWorks, Inc. Google advanced search argument, this topic / post: delete sas library site:sas.com ... View more

Use INTNX function to derive a period-start date from which you can then count each period and roll-up observations to another new variable that has YEAR (using YEARPART or YEAR function). Of course, it's unclear if you are working with SAS numeric DATE type variables or numeric/character data in format "yyyymmdd". If not SAS DATE variables, I would encourage you to get those data-values converted to SAS DATE type variables, so you can manipulate/reference then to get month-start and year-start derivations. Scott Barry SBBWorks, Inc. ... View more

Look at the TRANSLATE function to manipulate your MAIN variable, I suppose. Honestly, you're spoon-feeding information making it difficult to assist you --- paste the SASLOG intact with your code as well as SAS diagnostics revealed (COPY and PASTE). Scott Barry SBBWorks, Inc. ... View more

You have not shared info about the SAS variable MAIN and its content. Also, it is unclear exactly what SAS variables contain in your DATA step. Suggest you consider re-posting another REPLY and add this SAS code to your DATA step (using COPY/PASTE to share your exact SAS log, not just partial code info): PUTLOG _ALL_; STOP; Also, consider (from SAS Language DOC) that CATX function can have multiple parameters -- it may be suitable to add L1_0 as then third positional parameter argument to the function call. Scott Barry SBBWorks, Inc. ... View more

"Faster"? Look at SAS DICTIONARY TABLES for this type of information -- suggest searching the SAS support website. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: dictionary tables site:sas.com ... View more

From what you have explained, it appears as though you do not actually have a common SAS variable to use with the MERGE/BY processing. You need to investigate your input data files for differences for your MERGE/BY variable(s). And, you can add this SAS statement to help diagnose the IN= variable when doing the MERGE -- though, again, it will not solve any problem. PUTLOG _ALL_; Possibly using PROC FREQ may help analyze your input file(s), as well. Scott Barry SBBWorks, Inc. ... View more

Suggest you create a suitable "sample data" file for testing purposes, review the various ODS PDF parameter options for controlling output quality, and test various approaches with your sample data and OS / SAS environment. Or, as an alternative, consider whether a DATA step approach may be more efficient while suitable for your information output requirements. Scott Barry SBBWorks, Inc. Suggested Google advanced search arguments, this topic / post: ods pdf options site:sas.com ods pdf slow performance site:sas.com ... View more

It is possible to add conditional SAS macro logic that tests expected conditions and only execute a particular code-piece when the condition is / is not met. With this instance you can wrap code around the first DATA step to only execute it if the file being output does not already exist. You would use the EXIST(...) function as shown below: %IF %SYSFUNC(EXIST( ))=0 %THEN %DO; * do your DATA step code here. ; %END; There are other techniques that can be exploited, such as using "gate" macro variable flags (or alternatively a temporary "gate" SAS file, instead), to set a value/condition as a SAS global MACRO variable, as your program progresses, and test for the file/variable existence and perform or skip SAS code pieces as needed. Scott Barry SBBWorks, Inc. Suggested Google search argument, this topic / post: conditional code execution site:sas.com ... View more

The SAS variable LAST is incremented until it reaches the NOBS= value (based on WORK.PRODS). Then, unless you were to reset the value to LAST=0; outside your DO /END loop, the "expression" condition will never be met again. For self-diagnosis, suggest you add the following statement at various points in your SAS program to display all SAS variable values: PUTLOG '>DIAG>' / _ALL_; Scott Barry SBBWorks, Inc. ... View more

Recommend searching the SAS support website for your topic / post. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: +sas +cics site:sas.com ... View more