Scan Function for data input

[jacksonan123]

The code works well. I had one additional question. In my data output I
would like to capture the string MINIMIZATION SUCCESSFUL or in some other
cased MINIMIZATION TERMINATED as part of my output?



( K13 K23 CL V3 D1 TLAG2 LOGITT MINIMIZATION SUCCESSFUL) or ( k13 k23
..MINIMIZATION TERMINATED)

[ballardw]

---

@jacksonan123 wrote:

 When I run the code I get no output but an error 49 which states " The meaning of an identifier after a quoted string might change in a future SAS release. Inserting white space between a quoted string and the succeeding identifier is recommended."  I really habe no idea what this means.  Can anyone tell me what is the problem and how I can solve it?  The data sets test1 and test 2 are the same.

---

If you read carefully that is a WARNING. There aer several code structures, date, datetime, time and name literals that use a quoted value followed immediately by a special character to indicate the quoted value is to be used in a specific way.

x = '01JAN2017'd; for example says that the variable x is assigned a date value (the trailing d). So if you use code with any quoted string such as:  'some string followed by'anything the 'a triggers the generic warning because the character was not one of the currently used d,dt, t, n (and I think there's another couple I don't remember of the top of my head).

Note that if you had used one of the data indicators you may have generated an error instead:

446  data _null_;
447     x='23Fre2017'd;
          ------------
          77
ERROR: Invalid date/time/datetime constant '23Fre2017'd.
ERROR 77-185: Invalid number conversion on '23Fre2017'd.

448  run;

because the value in the quotes does not match the type indicated by the trailing character.

[ccaulkins9]

I know this is old and resolved but just wanted to chip in a bit of "clarity" as to the error @jacksonan123? is seeing: if you were to provide the part of the error log where the message is printed there's a good chance theres' some coordinates to point out where those unbalanced quotes maybe are lurking - anybody give this a shot?

[ccaulkins9]

in fact, this error actually isn't barely related to SAS Studio, but more like Base SAS related