Can we have use a parameter to define which column to be used in the VA report. ... View more

Tomorrow I will try to implement it on my case, let's see what happen! Thanks 🙂 ... View more

Hi:   TAGSETS.EXCELXP does have an Embed_Titles_Once suboption, but it did not work for me with your PROC REPORT. This Tech Support note explains that the option is problematic: https://support.sas.com/kb/46/620.html .     However, when I tried Embed_Titles_Once with ODS EXCEL, that suboption worked for me with a version of your code. I created a subset of the sorted data to make everything fit in one screen shot.     I wasn't sure what you wanted, but asking for the mean AGE for every name didn't make sense, unless you wanted to see the Overall Mean at the bottom of the list for each group.   Cynthia   ... View more

Hi:   With some fake data that represented an "even" matrix of 4 values for the rows and 4 values for the columns, I was able to use of PROC REPORT with a temporary variable to do the highlighting on the diagonal, as shown below:     Note that this method will only work with an "even" matrix. If Region_A had 4 values, but Region_B had 5 values, then the logic of the COMPUTE block would not work. But, then, there's no really a diagonal to highlight for the EEE value, so I would assume that's OK.   Cynthia ... View more

Hm, you might need to prepare the tables, add the attributes to each if them.. ... View more

ballardw  gave you right code. If you want PROC REPORT.   data have; input Group $ Class $ Subclass $ Value; datalines; G1 A A1 1 G1 A A2 2 G1 A A3 3 G1 B B1 4 G1 C C1 10 G1 C C2 20 G1 D D1 20 G1 E E1 30 ; proc report data=have nowd; columns Group Class,(Subclass,Value Value=v) Value=total; define group/group; define class/across ' ' nozero; define Subclass/across ' ' nozero; define value/analysis sum ' ' ; define v/analysis sum 'total'; define total/analysis sum 'grand total'; run; ... View more

Have you ever found a solution to this problem? 🙂 ... View more

Hello Luke, we are running also a Grid but with different version (SAS 9.4 M3 to M5) and LSF 9.1.3. 1. How Do you set the queue definition in the grid options set? I use here queue=”<target queue>” in the Grid options field. 2. It’s a question how you run the batch jobs. We are using the SASGSUB for batch jobs with the ability to control most of the options. Which scheduler will you use, Plattform Process Manager? 3. There is an option for making SAS Applications gridCapable if they are not by default, maybe this is an option? http://support.sas.com/documentation/cdl/en/gridref/67371/HTML/default/viewer.htm#n1inymfs0b7go2n147xdknz0ygpx.htm Also you could have a look to the ‘esub’ feature of LSF. It is described in ‘Administering Platform LSF’ under the topic ‘External Job Submission and Execution Controls’. It is an external script (bash) which can change a job’s Options. In your case you can switch the queues or something else based on the user or something else. We use it for the things not are possible under the standards (e.g. Connection Services, debug feature) for direct them to the grid. It is very handy option but could be a potential performance bottleneck if the script run’s long time. Best regards, Andreas ... View more

Hi, thanks for the sudgestion. I will try to apply this on my case. In regards to my table example, there are just 2 border thikness, that is what I want; I'm not interesting in having different border size, just one bolder and one smaller depending on if the border divide cells inside a group or outside it. IE on the picture, row A, thin border between 1 and 2 (both in GA group), bolder border between 2 and 3 (going from Ga to Gb group), and so on!   Luca ... View more

What code do you need? The steps are:   SIGNON to VA server from BI Server RSUBMIT load code to VA server ENDRSUBMIT to close load step SIGNOFF to close VA session ... View more

Hi LukeL,   You might want to open a track with Technical Support for that “insufficient memory” message. There may be some options or a different syntax that might work for this exercise.   Best, Anna     ... View more

Sorry for confusing you. I did not want to suggest to move to M4 for everything right away. Just get the depot while you're at it. You can update EG to 7.13 without touching the other clients or the server side; it will work happily with SAS versions prior to 9.4M4. You can decide later what to do with the rest of your deployment.   Regards, - Jan. ... View more

You could have an initial job which runs a System command to pick up the filenames and insert them into a sas array or sas variables. This would be essentially be polling any of the files. This job would then also generate the triggers required to run the specific flows.   Then dependant on the inputs, triggers for each of the flows are generated and using a system command it will output them into the required directory(s). And each flow could be triggered based on what's present in a folder at a given time.   That seems the most logical for what you require at the moment. ... View more

After some more search, I find out that when you go to import a dataset from report designer: 1. The interface that let you choose what dataset to import is made with the SASApp>Pooled workspace server 2. The interface that let you choose the dataset, and hence browse the file system, is made by the SASApp Logical worksapce server. Deny the access to this two server from the SASMC to the user importing data make impossible to proceed, with some error message displayed...   Putting the lockdown on that workspace server actually limit the ability to navigate the file system, but the problem now is how to tell VA to use the newly created WS server and not the standard one!!! 😞 ... View more

Thanks for the suggestion. I was hoping in something less tricky, but I see there are no other advice 🙂 We will try to find out if can do something like this in our case 🙂 ... View more