@telligent wrote: I made an SGPLot image and it went there, but I have no idea how to find it.  NOTE: Listing image output written to /sastmp/saswork/SAS_workXXXXXXXXXXXXXXXXXXXXXXXXXXXXX Thanks. This is likely the path to your compute server Work directory. You can verify using code. data _null_; put "Work loc: %sysfunc(pathname(work))"; run;   Often your Explorer Home doesn't start at root.  In my environment Home is /create-export/create/homes/<&sysuserid> and I can only drill into subfolders but not traverse to other locations.   You can via SAS code copy objects from the path under WORK to a location under Home or you can also directly direct the output to there or you can just download the Report in SAS Studio to your local environment.    Below some sample code for SAS Studio for writing the output directly to Home /* Sample data */ data sample_data; input X Y; datalines; 1 2 2 3 3 5 4 7 5 11 ; run; /* Specify the output path */ ods html file="&_USERHOME/scatter_plot.html"; /* Create a scatter plot */ proc sgplot data=sample_data; scatter x=X y=Y; title "Scatter Plot of Sample Data"; xaxis label="X Axis"; yaxis label="Y Axis"; run; ods html close;   ... View more

@Ronein wrote: I found the problem but i cannot explain it. When I changed the location of the CSV file (moved it to another folder) then import worked 100% How can you explain it? Is the import wizard effected by folder name (IF it is in hebrew or other language)? OR maybe in the folder there was anyting that caused the error? I have no explanation for what you describe. I assume something else changed as well - like being connected to a different SAS Server. ... View more

Just to add what already has been said. data demo; a=10/3; b=10/3; c=10/3; total=sum(a,b,c); run; proc print data=demo; format _numeric_ f16.1; run;   ... View more

Using the SAS EG import wizard to generate data step code appears to work. Below the generated code with some manual changes applied (like longer character variables so they hopefully are also sufficiently long for all your data and not only the sample). DATA WORK.test_Eems; LENGTH Datum 8 Url $ 500 Sentiment $ 8 Type $ 7 Discussie_lengte 8 Views 8 Auteur $ 250 Volgers 8 Bron $ 9 Titel $ 250 Bericht $ 1500 Labels $ 10 ; LABEL Discussie_lengte = "Discussie lengte" ; FORMAT Datum date9. Url $500. Sentiment $8. Type $7. Discussie_lengte best32. Views best32. Auteur $250. Volgers best32. Bron $9. Titel $250. Bericht $1500. Labels $10. ; INFORMAT Datum ddmmyy20. Url $500. Sentiment $8. Type $7. Discussie_lengte best32. Views best32. Auteur $250. Volgers best32. Bron $9. Titel $250. Bericht $1500. Labels $10. ; INFILE 'C:\temp\test_Eems.csv' LRECL=30000 ENCODING="UTF-8" TERMSTR=CRLF DLM=';' truncover DSD ; INPUT Datum Url Sentiment Type Discussie_lengte Views Auteur Volgers Bron Titel Bericht Labels ; RUN; ... View more

Below two coding options for replacing any non alphanumeric character (or underscore) with a blank. If below sample code doesn't work for your real data then please be very specific what's not working and ideally provide amended sample data that demonstrates where the current result doesn't meet your desired result. data _null_; input have :$40.; /* create target variables with same type and length than source variable */ if 0 then do; want1=have; want2=have; end; /* option for single byte characters only */ want1=prxchange('s/\W/ /',-1,strip(have)); /* option that also allows for multi byte characters */ want2=ktranslate(strip(have), ' ', kstrip(kcompress(have, ,'n'))); /* print want variables */ file print; put 'have: ' @10 have / 'want1: ' @10 want1 / 'want2: ' @10 want2 / '-------------------------' ; datalines4; YT;-/*ADD^M Y9;-/*A;;D@D^M ;;;; run;   ... View more

Assuming you're talking about SAS9.4 metadata: If the tables on the new server are identical (name and structure) then I believe the only thing you would need to do is amend the metadata library definition and point it to the new server. As long as you don't create new metadata objects (like a new metadata library definition) then everything else should just continue to work. If the metadata library is not pre-assigned and you've got DIS jobs then you would also need to re-deploy these jobs so the amended libname syntax gets generated in the .sas file. If the metadata library is pre-assigned then the DIS generated code only contains the libref which doesn't change and though you also don't need to re-deploy the jobs. ... View more

"But why we can run in locally using non-admin account, that weild issue should be expained by SAS. " Can you run any VB Script via SSH on the remote machine with a non-admin account? I assume what you observe is due to security policies and not related to SAS. ... View more

@sassy_seb wrote: It's a mix of datasets from Access, Excel, and stuff they had already saved in SAS, as well as from REDCap. I was thinking of just separating based on being bigger than a certain number and applying the changes there. Under the assumption that the source dates converted into the correct SAS date and datetime values and you don't have actual source datetimes close to 01Jan1960 this should work. However as others already stated if your current SAS date/datetime values aren't correct then you would need further logic to amend them based on the source system (Excel, Access, ....).   Below sample code with two options how to display/print the values without changing the internally stored value and the 3rd case how to amend the values.  I don't recommend the first two options because any sorting will use the internally stored values and you also can't use functions like intck() and intnx() with a mix of date and datetime values. proc format; value dt_dttm_A '01Jan1900'd - '01Jan2500'd = [date9.] other = [datetime20.] ; value dt_dttm_B '01Jan1900'd - '01Jan2500'd = [date9.] other = [dtdate9.] ; run; data demo; input src_date_vals_raw; date_vals_A=src_date_vals_raw; format date_vals_A dt_dttm_A.; date_vals_B=src_date_vals_raw; format date_vals_B dt_dttm_B.; if '01Jan1900'd <= src_date_vals_raw >='01Jan2500'd then amended_date_vals=datepart(src_date_vals_raw); else amended_date_vals=src_date_vals_raw; format amended_date_vals date9.; datalines; 23601 23607 23601 23614 1991520000 1806883200 1804982400 1806364800 1807488000 1808092800 1808956800 1810166400 ; run; proc print data=demo; run;     ... View more

For debugging purposes: 1: Run your program with code as simple as possible using your clear text password. Once that works: 2: Only replace the clear text password with the encoded version (not passed via a macro variable) and run again. Does this work or already fail? ... View more

The error message indicates that your source file uses U_UTF8_CE which is a multibyte encoding and that it contains multibyte characters that can't get mapped into single byte characters under U_HEBREW_CE (which is a single byte encoding).  You need for SAS EG to connect to a SAS session that's also multibyte encoded (talk to your administrator if that exists at your site).  ... View more

I've never done it myself but... I guess it's a two step process. First figure out the name of the lock file, then delete the lock file.   The link you've shared indicates that the lock file itself is likely under some /temp directory or wherever the SPDELOCKPATH environment variable points to.  To delete the file here the docu link:  https://go.documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/proc/n0sksf47t7lheen11ay3w7490o5x.htm#n0nj9w2t8wjxcwn19fp75ec5c3km  I found above docu entry very quickly because I first asked Copilot: Proc hadoop delete file And got the answer: To delete a file in Hadoop using the PROC HADOOP procedure in SAS, you can use the HDFS statement with the DELETE option. Here’s an example of how you can do this: proc hadoop; hdfs delete="/path/to/your/file"; run; Replace "/path/to/your/file" with the actual path of the file you want to delete on the Hadoop Distributed File System (HDFS) 1 .         ... View more

If you want to install R in a cloud environment then you also need to first understand what a cloud environment is. Are you trying to install SAS Viya locally on a PC? ... View more

If this is just about display/print then a format could do the job. data a; a='A'; b='B'; w=.; x=1; y=1; v=.; run; data b; a='A'; c='C'; d=' '; x=2; z=2; v=.; run; proc format; value numMiss . = .A ; value $charMiss ' ' = '/' ; run; data all; set a b; format _character_ $charMiss. _numeric_ numMiss.; run; proc print data=all; run; I've added a variable V to your sample data to demonstrate that a missing doesn't tell you if a source variable existed in both source tables or not. It can just be missing in both source tables. ... View more