All board posts in SAS Support Communities

Re: How to use VS Code with SAS OnDemand for Academics

lhartjordan — Tue, 30 Apr 2024 13:36:08 GMT

You will need to save your SPSS table as a CSV and then you can follow these instructions: https://support.sas.com/ondemand/manuals/UploadingDataUsers.pdf

Re: How to use VS Code with SAS OnDemand for Academics

FSU_TOM — Tue, 30 Apr 2024 13:33:10 GMT

Check out this post:

https://communities.sas.com/t5/SAS-Software-for-Learning/How-to-import-excel-files-in-SAS-On-Demand-for-Academics/m-p/280052#M50

Re: Format proc report to output dates in excel using ods excel

PaigeMiller — Tue, 30 Apr 2024 13:24:37 GMT

When I use format=date9. in a DEFINE statement, the variable is recognized as a valid date in Excel.

If it is not recognized as a valid date for you, please show us actual code where the DEFINE statement includes format=DATE9. and also a screen capture of Excel where we can see clearly that this is a character variable.

Please use the "insert photos" icon to include your screen capture in your reply. Do NOT attach files.

Re: Format proc report to output dates in excel using ods excel

Kia_B — Tue, 30 Apr 2024 12:54:14 GMT

My code outputs multiple sheets to an excel workbook. The first code is where the issue is. The second code is just an example showing that sheet is exporting correctly with the correct date format. Since the second code is working correctly, I was wondering if the issue was in my define statement in the first code. There is no define statement in the second code. The format=date9.; output the variable as a character variable in excel.

Re: Severe penalty for using MFILE?

Quentin — Tue, 30 Apr 2024 12:53:27 GMT

@peterprec wrote:

Great post, @Patrick ! It completely confirms my observations. It aligns poorly with cause being the MFILE target written to a slow location, but supports that something in the MFILE implementations does not work as intended. Completely guessing here, it almost feels like MFILE writes one resolved programming statement/token at a time to disk (i.e., no buffering at all) while the rest of the execution sits and waits for the MFILE I/O to finish.

I think that's a good guess. There are system options to control the amount of log buffering, but they probably don't apply to MFILE. Could definitely be that adding MFILE just changes the process from "send a token to the word scanner (or compiler or whatever is asking for tokens)" to "send a token to a file, then send the token to the word scanner".

You have to assume a LOT of work was put into general speed of writing to the log over many many years, since every time code is submitted it writes to the log, and log files get big. My guess is not much work was put into developing logging for MFILE, because it's just one part of macro language, is less-used, etc. And since the macro language has been 'functionally stable' for a while, I wouldn't think the chances are high they a developer will dive in to improve it.

Re: Using SAS PROC S3 to access a bucket using CEPH

alisio_meneses — Tue, 30 Apr 2024 12:44:35 GMT

I managed to resolve the issue by incorporating a custom region using a different approach. Since there was no response, I'll share my solution for anyone who might benefit from it.

Here's what I did to make it work:

Set a unique name for the custom region. Previously, I had assigned a custom region name identical to an existing AWS region, so I opted for a distinct name instead.
Utilized PROC S3 to introduce the custom region instead of relying on environment variables.

/*Add custom region*/

proc s3;
REGION ADD HOST="storage.middle.earth" NAME="shire";
run;
/* Listing all regions (including the custom region) */
proc s3;
region list;
run;

This resulted in the following log output (note the added custom region):

1 %studio_hide_wrapper;
83 proc s3;
84 REGION ADD HOST="storage.middle.earth" NAME="shire";
85 run;
NOTE: PROCEDURE S3 used (Total process time):
real time 0.01 seconds
cpu time 0.00 seconds

86
87 proc s3;
88 region list;
89 run;
Amazon Regions
us-east-1 s3.amazonaws.com Default 0
us-east-2 s3-us-east-2.amazonaws.com Default 0
us-west-2 s3-us-west-2.amazonaws.com Default 0
us-west-1 s3-us-west-1.amazonaws.com Default 0
eu-west-1 s3-eu-west-1.amazonaws.com Default 0
eu-central-1 s3-eu-central-1.amazonaws.com Default 0
ap-southeast-1 s3-ap-southeast-1.amazonaws.com Default 0
ap-southeast-2 s3-ap-southeast-2.amazonaws.com Default 0
ap-northeast-1 s3-ap-northeast-1.amazonaws.com Default 0
sa-east-1 s3-sa-east-1.amazonaws.com Default 0
us-gov-west-1 s3-us-gov-west-1.amazonaws.com Default 0
us-gov-west-1 s3-fips-us-gov-west-1.amazonaws.com Default 0
ca-central-1 s3-ca-central-1.amazonaws.com Default 0
ap-south-1 s3-ap-south-1.amazonaws.com Default 0
ap-northeast-2 s3-ap-northeast-2.amazonaws.com Default 0
cn-north-1 s3-cn-north-1.amazonaws.com Default 0
cn-northwest-1 s3-cn-northwest-1.amazonaws.com Default 0
eu-west-2 s3-eu-west-2.amazonaws.com Default 0
eu-west-3 s3-eu-west-3.amazonaws.com Default 0
ap-east-1 s3.ap-east-1.amazonaws.com Default 0
eu-south-1 s3.eu-south-1.amazonaws.com Default 0
eu-north-1 s3.eu-north-1.amazonaws.com Default 0
me-south-1 s3.me-south-1.amazonaws.com Default 0
af-south-1 s3.af-south-1.amazonaws.com Default 0
ap-northeast-3 s3.ap-northeast-3.amazonaws.com Default 0
Custom Regions
shire storage.middle.earth Default 0
NOTE: PROCEDURE S3 used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds

90
91 %studio_hide_wrapper;
102
103

Now, with the appropriate credentials, it's possible to test bi listing a bucket content:

proc s3 KEYID="isItSecret" SECRET="isItSafe" region="shire";
list "/bucket" ;
run;

That's it.

See ya!

Re: concatenate two macro variables with "/" between them

PaigeMiller — Tue, 30 Apr 2024 13:26:04 GMT

No quotes used inside %SYSFUNC

%let customer_branch=%sysfunc(cat(&customer_ID.,/,&branch_Id.));

But really @Astounding has the better advice.

Is it mandatory to use a slash here (which sometimes will be interpreted as division)? Couldn't some other character, which isn't also a mathematical operator, such as underscore, work here? Do you even need a character like slash or underscore, could you just append customer_id and branch_id without any character between the two? All of this would make your programming simpler.

Re: Error Occured on SAS Data Studio - Prepare Data

cludena — Tue, 30 Apr 2024 12:30:34 GMT

Hi. Could you solve this issue? We seem to be facing the same problem with a SAS viya 3.5 production deployment. We can't get any previous functional job to work . The error message we get is exactly the same

Re: Calculating Cohen's d from multiply imputed data

SAS_Rob — Tue, 30 Apr 2024 12:20:07 GMT

My suggestion would be to calculate Cohen's D and its standard error for each imputed data set and then use Proc MIANALYZE to get the combined estimate.

You can find several variations of the standard error calculation here:

effect size - What is the formula for the standard error of Cohen's d - Cross Validated (stackexchange.com)

This would be a simpler approach than what you are taking I believe. Plus, I think the last MIANALYZE step is wrong since the standard error you are supplying is not for the standard deviation which is the statistic you are combining.

proc mianalyze data=subset;
by class;
modeleffects stddev;
stderr stderr;*this is not the standard error for the standard deviation;
run;

Re: Severe penalty for using MFILE?

peterprec — Tue, 30 Apr 2024 12:11:36 GMT

Great post, @Patrick ! It completely confirms my observations. It aligns poorly with cause being the MFILE target written to a slow location, but supports that something in the MFILE implementations does not work as intended. Completely guessing here, it almost feels like MFILE writes one resolved programming statement/token at a time to disk (i.e., no buffering at all) while the rest of the execution sits and waits for the MFILE I/O to finish.

Re: concatenate two macro variables with "/" between them

Astounding — Tue, 30 Apr 2024 12:04:21 GMT

You are overcomplicating things. This would be the usual way to concatenate strings in macro language:

%let customer_branch=&customer_ID./&branch_Id.;

Simple. Macro language does not perform math in a %let statement However, if you use the variable later, macro language may try to perform math. For example, this statement would have the potential to cause trouble:

%if 9872622/987 = &customer_branch %then %do;

%IF/%THEN statements do try to perform math. While there are a few ways to suppress this, an easy way would be to add double quotes:

%if "9872622/987" = "&customer_branch" %then %do;

The quotes become part of the comparison.

concatenate two macro variables with "/" between them

Ronein — Tue, 30 Apr 2024 11:23:25 GMT

Hello

I want to concatenate two macro variables with "/" between them.

I get error 49


%let customer_ID=9872622;
%let branch_Id=987;
%let customer_branch=%sysfunc(cat(&customer_ID.,"/",&branch_Id.));/***9872622/987*****/
%put &customer_branch;

Re: Format proc report to output dates in excel using ods excel

PaigeMiller — Tue, 30 Apr 2024 11:20:50 GMT

It's hard for me to understand the two blocks of code you show. There is no variable named STATUS_DATE in the first block of code. However, in the first block of code, for example, you include the format in the DEFINE statement, like this:

define FINAL_Code_Date/'Final Code Date'  style={background=lightyellow color=black} format=date9.;

Re: HPE Greenlake to host SAS Viya?

AnshulNagori — Tue, 30 Apr 2024 11:08:24 GMT

Yes, HPE GreenLake now supports SAS Viya on-premises. HPE, SAS ad Red Hat have created a joint solution for SAS Viya. The technical paper is available at: https://www.hpe.com/psnow/doc/a00138240enw

This paper describes the solution for virtualized SAS Viya using Red Hat OpenShift using hostel control plane. HPE ahs also tested VMware based Viya deployments: https://www.youtube.com/watch?v=x2XJ9a7QxOI

Format proc report to output dates in excel using ods excel

Kia_B — Tue, 30 Apr 2024 12:56:04 GMT

I am attempting to output an excel (xlsx) file using ods excel from a proc output. My variables are in date9. format in the SAS data set, but when they output to excel they are in a text format.

This is my code:

ods excel file="\\xxxmyfilelocation\Events_%sysfunc(date(),yymmddd10.).xlsx" style=forNESUG options (FLOW='Tables');

ods excel options (zoom='80' sheet_name='Tracker');

proc report data=tracker nowd split= "_" style(column)=[JUST=LEFT VJUST=TOP FONT=(Calibri, 11pt, NORMAL) BORDERSTYLE=SOLID BORDERCOLOR=black]

style(header)=[BACKGROUNDCOLOR=light grey FONT=(Calibri, 11pt, BOLD) JUST=CENTER VJUST=TOP BORDERSTYLE=SOLID BORDERCOLOR=black];

column Initial_Code_Date Initial_Attribution_Date Initial_SO_Coverage Date_of_AE_status_Evaluated Initial_Rep_event_became_SAE Type_of_SAE Final_attribution Study_RX_held Treatment_rechallenged Treatment_Permanently_Discontinu Status_AE SO_FU_Log_Comments AF_summary_comments Final_MedDRA_code Final_MedDRA_LLT FINAL_Code_Date Final_Attribution_Date FU_SO_Coverage Initial_site_email_archived_ Final_site_email_archived_ Completed_pharma_reporting_ Closed SO_closed_AE Close_Date Teaching_example Tracker_run_date;

define Initial_Code_Date/'Initial Code Date' style={background=lightyellow color=black};

define Initial_Attribution_Date/'Initial Attribution Date' style={background=lightyellow color=black};

define FINAL_Code_Date/'Final Code Date' style={background=lightyellow color=black};

define Final_Attribution_Date/'Final Attribution Date' style={background=lightyellow color=black};

define SO_Log_Comments/'SO Log Comments' style(column) = [just=left cellwidth=3in background=lightyellow color=black] style(header)=Header{background=lightyellow color=black};

define SO_FU_Log_Comments/'SO FU Log Comments' style(column) = [just=left cellwidth=3in background=lightyellow color=black] style(header)=Header{background=lightyellow color=black};

define Reas_NonReportable_AE/'Reas NonReportable AE' style(column) = [just=left cellwidth=0.5in background=lightyellow color=black] style(header)=Header{background=lightyellow color=black};

define Teaching_example/'Teaching example' style={background=lightyellow color=black};

define Closed/'Closed' style={background=lightyellow color=black};

define SO_closed_AE/'SO closed AE' style={background=lightyellow color=black};

define Close_Date/style={background=lightyellow color=black};

options missing=" ";

format Initial_Code_Date date11. Initial_Attribution_Date date11. Final_Code_Date date11. Final_Attribution_Date date11. Close_Date date11.;

run;

I think the issue is my define statement, because the last block of code which exports to a different sheet in the excel workbook exports the date correctly and there is no define statement.

proc report data=sites nowd split= "_" style(column)=[BACKGROUNDCOLOR=white JUST=LEFT VJUST=TOP FONT=(Calibri, 11pt, NORMAL) BORDERSTYLE=SOLID BORDERCOLOR=black]
style(header)=[BACKGROUNDCOLOR=light grey FONT=(Calibri, 11pt, BOLD) JUST=CENTER VJUST=TOP BORDERSTYLE=SOLID BORDERCOLOR=black];
column SiteNo Name Status Country Status_Date Note;
format Status_Date date11.;
run;

Any suggestions?

Can we prevent publishing intelligent decision with the same name if publishers are different users?

Mayt — Tue, 30 Apr 2024 10:57:15 GMT

Hi guys!

I use SAS viya and my environment has many users. I want to publish a decision, and want it to be replaced if the published name is the same as my old published decision. I know we can press "Replace item with the same name"

But can we prevent publishing if another user want to publish it with the same name like mine?

Thank you in advance!

How to import SPSS file with SAS OnDemand for Academics

ElsayedamrBasma — Tue, 30 Apr 2024 13:36:22 GMT

I am new to SAS OnDemand
please can anyone help me to know how to import SPSS file from my hard-disk to SAS library to work on it.

Re: If first with multiple BY variables and counts/calculations

PaigeMiller — Tue, 30 Apr 2024 09:55:09 GMT

Industry Specialization = Sum of square root of total assets of auditor clients (by gvkey) in a particular industry (sic code )divided by the sum of the square root of total assets of all clients of the auditor.

Compute the square roots of the variables on each row in a DATA step. Compute the sum of the square roots by gvkey and sic code by using PROC MEANS or PROC SUMMARY. (Do not try to compute sums by gvkey/sic code by yourself, SAS has already done this for you). Then, once done, do the division in another data step.

Working with sum of square roots seems somewhat strange way to calculate something. Are you sure this is written correctly? Should it should say "sum of squares"?

Re: proc ttest pvalue

Ksharp — Tue, 30 Apr 2024 09:34:07 GMT

Yes. That is correct. Alternative way is using PROC UNIVARIATE.

proc univariate data=base_post ;
by trt01pn; 
var cat3;
run;

Editing slice labels in a donut chart so that they don't overlap

ElGent99 — Tue, 30 Apr 2024 09:23:09 GMT

Hi everyone,

I need to visualise some survey data using a donut chart in PROC GCHART. Because some adjacent pie slices are very small, their percentages and labels overlap. See below (chart generated using sample data):

Is there a way to display the slice percentage on the same line as the slice label instead of after a line break? If yes, can someone provide me with a snippet of code that achieves this? I don't think it's possible within PROC GCHART, but I've heard PROC TEMPLATE or the graphics editor might help (I'm a novice so I can't figure out either). I'm using SAS 8.3.

Alternative solutions I've considered and discarded:

Reordering slices so that small segments are not together: can't do that because of the nature of the data (Likert scale).
Experimenting with ARROW/INSIDE/NONE/OUTSIDE and ANGLE: already done, labels still overlap in the original data.
Using PROC SGPIE instead: not available in the version of SAS that my organisation uses.

Here's the sample data I used to generate the chart:

data survey;
input name $ q1 & $100.;
datalines;
John Very positive
Cathy Very positive
Phil Very positive
Jason Very positive
Darryl Very positive
Gary Very positive
Courtney Very positive
Andrea Very positive
Dave Very positive
Andy Very positive
Will Very positive
Zach Very positive
Isla Very positive
Florence Very positive
Henry Very positive
Mo Very positive
Evie Very Positive
Nigel Positive
Linda Positive
Anna Positive
Luke Positive
Arlo Positive
Archie Positive
Wendy Positive
Meghan Positive
Jack Positive
Lucy Positive
Theo Positive
Dylan Positive
Grace Positive
Stella Positive
Eva Positive
Nora Positive
Camilla Positive
Violet Positive
Jude Positive
Harry Positive
Louis Neither positive nor negative
Joe Neither positive nor negative
Leo Neither positive nor negative
Janet Neither positive nor negative
Debbie Neither positive nor negative
Alex Neither positive nor negative
Daniel Neither positive nor negative
Nina Neither positive nor negative
Gabe Neither positive nor negative
Oliver Neither positive nor negative
Anthony Neither positive nor negative
Chris Neither positive nor negative
Evan Neither positive nor negative
Adam Neither positive nor negative
Max Neither positive nor negative
Sophia Negative
Mia Negative
Abigail Negative
Caroline Negative
Shane Negative
Chloe Negative
Clint Negative
Lizzie Negative
Sarah Negative
Nick Negative
Amelia Negative
Ava Negative
Hazel Negative
Ivy Negative
Olive Negative
Rose Negative
George Negative
Arthur Negative
Ben Negative
Finn Negative
Elliot Negative
Sam Negative
Josh Negative
Kai Negative
Jacob Negative
Hugo Negative
Mason Negative
Mike Negative
Liam Negative
Vanessa Very negative
Fred Prefer not to say
;