Interesting.  So if you run multiple parallel batch jobs, they fail with an error about the macro catalog being locked/inaccessible? I suppose it's possible that macro catalogs are locked by a single session.  If you did store the macro code, I wouldn't think that would be locked.   Troy Hughes has a book and a bunch of papers about this sort of automated parallel processing, so I wouldn't give up too soon.  e.g.: http://support.sas.com/resources/papers/proceedings17/0870-2017.pdf   In theory you wouldn't need to save code permanently on the server, so you could avoid maintaining code in two places.  When your parent program starts, it could copy the .sas source code for the shared macros to a temporary shared location on the server, then spawn child sessions which can read the macro definitions from the shared location, then at the end the parent program could delete all the files from the shared location.  You might even be able to use the WORK library of the parent session as the location for storing shared code.  The parent would just need to tell the child sessions the path to look in.   Those are just ideas.  I haven't played with this sort of roll-your-own parallelism myself. ... View more

As a general note you might want to consider using numeric values of 1 and 0 instead of character 'Y' and 'N'. If 1 is the value for 'Y' or 'Yes' or however you think then:   If varname then <other code> ; treats a value for the variable varname as true. You can a have a number of different formats to assign a display value of 'Y', 'Yes' ,'True', 'In Compliance' or what have you. For summary tables such as in proc report or proc tabulate then the N statistics gives how many results are assigned either value, Sum shows number of 'Y' values and mean is percentage of 'Y' values. If you have multiple variables code this way then Sum of the variables gives a count of how many variables have 'Y' values. And other coding behaviors are possible that get more cumbersome for character values. ... View more

Hello,   Here is a solution that avoids using a list of names in a macrovariable   data persons; input name $ male; cards; John 1 Mary 0 Peter 1 Robert 1 Jane 0 Lucy 0 William 1 Richard 1 Anna 0 ; run; data results; input John Mary Michael Peter Sylvia Robert Jane Lucy William Charlotte Richard Annna; cards; 3 4 2 3 5 4 2 5 3 4 1 4 ; run; proc sql noprint; SELECT count(*) INTO :nmales FROM persons WHERE male=1; quit; data want; set results; array a_names(&nmales.) $ _TEMPORARY_; if _N_=1 then do i=1 by 1 until (eof); set persons (where=(male=1)) end=eof; a_names(i)=name; end; do i=1 to dim(a_names); total+vvaluex(a_names(i)); end; drop i name male; run; ... View more

I like it, this line does what I want;;   with a set statement; rc = dosubl(cats('SYSECHO "OBS N=',_n_,'";'));   in a loop; rc = dosubl(cats('SYSECHO "OBS N=',i,'";')); ... View more

Thanks, I thought as much, I just wanted to check to see if there was anything obscure I didn't know about. ... View more

Awesome, nice thinking.  ... View more