This works! And it's so simple. Thank you.  ... View more

Try adding this line of code immediately before the step where you get the misbehaving format usage: Proc options option=fmtsearch;run; That will write the actual in effect search path to the log.     Also you may want to run this code: title "In FMTS.FORMATS1"; proc format library=FMTS.FORMATS1 fmtlib; ; run;TITLE; title "In FMTS.FORMATS2"; proc format library=FMTS.FORMATS2 fmtlib; ; run;TITLE; to get human readable text of the contents to verify which catalog has which catalog has which formats and the assignments. Perhaps the issue is more subtle than the search order but that the format does not exist or is the wrong type in the Formats2 catalog.   ... View more

A couple of general comments/questions on that macro.   First you have S as a parameter but then force an assignment to S in a do loop. So why is S a parameter? Understanding that this is a development in progress but using macro variables inside a macro not explicitly passed into the macro has many potential for bad behaviors. Since you are setting a single variable FLAG to 1 then testing multiple variables will likely lead to hard to tell which variable met the condition.   And probably most critical: use of <= (or >= or just > and < with strings is seldom appropriate please see: data _null_; diag1 = 'T4 '; if ("T36" <=substr(diag1,1,3)<="T50") then flag=1; put diag1= flag=; run; Obviously we do not have every possible value of your diagxx variables but consideration for string values with likely numeric comparison needed is always problematic.     Example input and desired output is often helpful. And sometimes how that result is to be further used.   You could probably describe the needed behavior with only 4 or 5 DIAG variables. The question about "leave" would require information about do you want to stop for the first match (flag)? Or do you need to know for each DIAG variable? (Not leave but ARRAY processing). ... View more

It might help to let us know what type of catalog is involved. For instance if the catalogs are Format catalogs then perhaps someone was kind enough to generate CNTLOUT data sets when the formats were created and then you could use those to recreate the formats. ... View more

Thank you so much to all of you! A combination of all of your responses got me what I needed. it is so crazy that this is such a problem. smh ... View more

For SASBASE 9.4 in Windows this is how it will work:   <SASBASE instaled path>\sas.exe -CONFIG <SASBASE instaled path>\nls\en\sasv9.CFG -sysin <prgram with path name> -autoexec <if any with path name> -log <log path with log name>   the last tag will print the logs where you want it to print. And it will print the batch log. Not Applog.   Hope this helps. ... View more

Here's an example that uses SQL   data have; input type $ cost flag; cards; a 20 1 a 30 0 a 40 0 b 10 1 b 15 1 b 70 0 ; run; proc sql; create table want as select type, sum(cost*flag) as numerator, sum(cost) as denominator, CALCULATED NUMERATOR/ CALCULATED DENOMINATOR AS FRAC FORMAT=FRACT., CATX("/", put(calculated numerator, 8.), put(calculated denominator, 8.)) as frac_text from have group by type; quit; ... View more

Perhaps starting more from scratch. Consider what this result looks like:   proc tabulate data=dsn; class gender ethnicity; table gender ethnicity, n colpctn ; format gender gender. ethnicity ethnicity.; run; ... View more