@Rabelais wrote: Many thanks for the detailed analysis! So basically are you saying that these lines of code %do i=1 %to 1000000; b = a; %end; are turned into 1000000 lines of text where each line is equal to "b = a;" ?   The SAS option MPRINT, assuming no syntax problems will show the generated code in the LOG. Example: %macro loop; %do i=1 %to 25; %put Loop is &i. ; %end; %mend; options mprint; %loop The log will show the result of each %put statement, only 25 in this case. I used that for an example to avoid the errors that would occur with assignments when no data step is present.   Turn off the option with : options nomprint;  after the code.   The options SYMBOLGEN will show the results of creating and combining macro variable values, MLOGIC will show the result of macro logic comparisons such as %if statements.  ... View more

How about some example data in the form of a working data set then demonstrates the issue, which I think means the example needs to have a couple different Pageno values as well as the definition code for the three custom formats.   May need to go into some detail on the nature of the "dummy" variables as well. If multiple values get mapped to the same value then all the values only get one bar in the graph.   Since you mention "outside of a macro" then if your variable names, such as Paramn, or formats actually differ inside the macro then perhaps you need to supply the macro code as well as some working data.    It would also likely help if you could show an example of what your graph(s) are supposed to resemble. Sometimes the data needs to be rearranged for some types of plots. ... View more

I think the issue may be the name of the state variable in the look up data Look at the help for the LOOKUPSTATEVAR. The default if the option is not set is to use a STATECODE variable. It looks like variable in the USM data set is MapIDNameAbrv.  So try adding  to the options in the Geocode syntax:   Lookupstatevar = Mapidnameabrv So you may be getting results for similar City and Address values in different states.   The Geocode procedure defaults to a lot of variable names so it is worth checking if anything goes wrong. I never had actual street lookup needs so I'm not sure how the procedure might complain if expected variable names aren't met. Did the LOG show anything that might be interpreted as expected  variable not present? ... View more

This type of recoding: if RIGHT_HOURS = .M or RIGHT_HOURS = ' ' then New_Time = 'Missing'; if '0.0000'<=RIGHT_HOURS <'2.0000' then New_Time = 'LT2' ; if '2.0000'<=RIGHT_HOURS then New_Time = '> 2+'; IF right_hours is numeric (the .M as a special missing makes be believe that it is) often is not needed. When you want to process groups of values of a variable then a custom format is often preferable as it doesn't need to modify any data set, which may take time, and can be quite flexible by having multiple formats or modifying the format definition.   An example you might be able to run: proc format; value right_hours 0 -< 2 = 'LT2' 2 - high = '>2+' .,.M = 'Missing' ; run; proc freq data=name2; table right_hours /missing; format right_hours right_hours. ; run; If your name2 data set has trillions of records then the data storage space and time to run to create the data set name3 could be prohibitive. Custom formats like this will be honored by analysis and reporting procedures for just about any grouping purpose and usually for graphing as well with some caveats.   Advantages to formats include:    typically easier coding than multiple If/then/else statements    easier to understand once familiar    ease of modification    with numeric values the formatted values will appear in value order    reduces the number of needed variables when one is based solely on another single variable    one format can be applied to multiple variables that need the same rules    lists of specific values may be much easier to code   and for advanced purposes a lookup data set may be used to create the formats        Consider a data set with person ages. I used to have to report on 5-year based age groups, 10-year based age groups, ages like 18 to 25, 26 to 40, 41 to 65 and 65+ (and a few other groups based on specific projects). I did not need a specific variable for each but had separate formats used with which ever age variable was appropriate for the data set such as age at marriage, treatment, enrollment or departure from program.   ... View more

Can you post the output of Proc Contents on the street lookup data set used and the Proc Geocode syntax you used?   If you used a SAS Map data set of some flavor it may be that the X and Y coordinates returned are Map coordinates and not latitude and longitude OR you are getting Lat and Long coordinates that are treated as X, Y map display pairs which would tend to display on a map incorrectly. ... View more

What is the actual text of theerror reported? ... View more

As @WarrenKuhfeld says, details are needed.   Likely the best start of sharing the needed details is the LOG. Copy the text from the log of the model code with all the notes through whatever report code was used if any. On the forum open a text box by clicking on the </> icon above the message box and pasting the text.   The log will have information about many possible issues that could do such. If you have closed down your session or cleared the log then you would want to rerun the code enough to generate the output again so you have a fresh log to work with. ... View more

There a several places that decimal conversions can act oddly. If you see one then it may be that you should round to a desired decimal level before applying an inconsistent format. ... View more

You might also explain where the data set J actually comes from.    There are hints that this involves Excel as a possible data source. Which may mean that manipulation of the data set in Excel prior to reading into a SAS data set might be a better solution such as setting a single date format in the Excel column. Or save to a CSV text file and use a data step to read the data. ... View more

<Pedantic mode:on> Sun in your subject line and Count in your question are quite different mathematical concepts. <Pedantice mode:off>   It is a good idea to describe, better provide some example, the starting data and the desired result from the given data. You should also include the LOG when you get errors such as you code will throw. Copy from the log, open a text box using the </> icon that appears above the main message window and paste the copied text. Example: 24 proc sql nosqlremerge; ------------ 1 WARNING 1-322: Assuming the symbol NOREMERGE was misspelled as nosqlremerge. 25 create table junk as 26 select *, 27 sum(age) as agesum 28 from sashelp.class 29 group by sex 30 ; ERROR: The query requires remerging summary statistics back with the original data. This is disallowed due to the NOREMERGE proc option or NOSQLREMERGE system option. 31 quit; NOTE: The SAS System stopped processing this step because of errors. NOTE: PROCEDURE SQL used (Total process time): real time 0.00 seconds cpu time 0.00 seconds My version of SAS also doesn't like the option you specified as NOSQLREMERGE but does use the NOREMERGE option and attempts the code with that option and then errors because of the required remerege. Removing the noremerge to run the code: 48 proc sql ; 49 create table junk as 50 select *, 51 sum(age) as agesum 52 from sashelp.class 53 group by sex 54 ; NOTE: The query requires remerging summary statistics back with the original data. NOTE: Table WORK.JUNK created, with 19 rows and 6 columns. 55 quit; You can copy the code from the above and run it on your system as you should have the SASHELP.CLASS data set available.       Does your desired output data want to have the same "sum" value repeated for each value of the groupid variable? If you look at the above created data set JUNK you will see 9 values of 119 for the Agesum variable and 10 of 134 .     ... View more

If you want to display a dash in the date look at the YYMMDDXw format. The X position lets you use a list of characters in that position, B C D N P and S which will then use a Blank, Colon, Hyphen (dash), nothing, Period or Slash as the separator between the elements.   Note that custom rolled date, time and datetime formats created with Proc Format are also not going to display properly in graph axis.   ... View more

@adalisaw wrote: I am sure you are wrong. I have been using SAS for at least 8 years. I can use SAS to do what R, Python, SQL, and etc allow me to do. And I love it. BTW, you have not given us your reason (s) why you seem to not like SAS.  I think you replied to the wrong thread @adalisaw . If this comment relates to the original post by @ShaneClark you should have initiated the reply by clicking the REPLY button at the base of his post. This is also a fairly old thread to respond to in general.   I, ballardw, whose post you replied to, have a very positive history with using SAS staring in 1986. ... View more

Some minor things that when dealing with conversion from Excel to SAS sometimes aren't minor. 4.when i exported to sas it shows as mm/dd/yy format as numeric 8. EXCEL and SAS both use numeric values for date, time or datetime values. The way tell that such values are intended to be used as such is shown by applying a date, time or datetime format. The underlying numeric values do not change  but the format may. Depending on the particular method used to convert data between Excel and SAS, SAS may attempt to duplicate the display appearance of the dates. If you right click on a cell populated with one of these date values in EXCEL you should see a cell format box pop up that will indicate what role the cell plays such as General, Number, Currancy, Date and a few others. If the cell is a date then that role will be selected and another part of the window should show the current display format in effect though Excel will provide an example appearance (generally) to select. SAS format descriptions use letters such as DD to indicate the day of month position, MM the month position and YY the year position in a date. Some of the behavior of the order of those fields can depend on your national language so it is not impossible to see a value in Excel appear differently in SAS because the numeric value in Excel could be displayed in day moth year order and get transposed to a month day year order if that is the national preference set in SAS (or vice versa).   On not uncommon behavior is for an Excel sheet to have columns that mix numeric values with date display formats and character values of similar appearance if people are entering or modifying data manually. At which point you have have missing values or character date values, again depending on how you convert the data.   Using SAS you do want to get some terminology a bit clearer when using the word "format" as that is a very specific meaning. A variable with have a format and the name is important and would be reported by clicking on displayed tabled headings or running Proc Contents on a data set or even using one of the information functions. Your SAS data set displays a value like  mm/dd/yy but that is not a format as the format name is not allowed to have special characters. The FORMAT might be MMDDYY10. to show 10 characters, default using a / between the elements which would be displayed with 2 digits for month and day and 4 digits for the year. It is a good idea to specify the exact format SAS uses for a variable as some "problems" may well be addressed by changing formats such as displaying more or fewer characters, different or no delimiter between date or time elements and even which elements to display. SAS supplies over 50 date related formats and you can create custom appearances for dates using Proc Format if one of the existing formats doesn't fit your need.   ... View more

Will you provide the reason that you want these variable names in single quotes?   I can see lots of potential problems with a long string and many single quotes for some types of use and perhaps it would be easier to approach the how this is to be used in the long run.   As an aside to basic SAS coding, when you have variables with common names that only vary by a sequence of digits such as your  balance_MESHU_LLL_PIG_MTI_1_AMT balance_MESHU_LLL_PIG_MTI_6_AMT you are often much better off providing the sequence number at the end of the variable as then you can use lists such as Common_part_:  to get all variables that start with a common name portion or Common_part_2 - Common_part_6 to process just the 2 through 6 named variables. Note that the : list builder immediately follows the common part of the name.   These lists can be used in keep/drop statements, array definitions using existing variables and many function calls that accept multiple variables using OF <list descriptor> such as Max(of Common_part_: ... View more

@Ronein wrote:   The issue is that I wrote code that other people should run. It might happend that in the source data set some of fields will not exist and then I want that the code still run (no error). If you are writing the code for other people to run the I would say that it is also your job to verify if the variables exist in the data sets used and to modify the code so that there are no such  issues.   Easy enough to check existence of variables for SAS data sets, I suspect there are at least 20 or 30 threads just on this forum related to such. If your data is external then that may be a bit more complicated.   Modifying the code to use a verified list of variables may be much more complicated depending on how you are using the variables. There are many places that missing variables are critical failures and just turning off warnings will not allow the code to run at all much less "with no error". You may have to provide some examples of other examples of where these possibly missing variables may occur if other than in a Keep option or statement.  ... View more