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

What happens if you subset your source table to a 1000 rows and load these? Does this work? For the Proc Append: I can’t see the Force option specified but it’s mentioned in the Log. Is this really the log from the Proc Append statement you shared? Did you try bulk load? Do you really want to commit after every 32K rows? Or could you eventually use dbcommit=0? Is the target table empty? Are there a lot of indexes and constraints on the table (eventually disable them prior to the load and then re-enable them once loaded)? ... View more

Not sure if it will work but worth trying: %let path=/dwh_actuariat/sasdata/Data_Retention/sas2002/be; filename oscmd pipe "uncompress -c &path./bel.prod0110.se8030ac.m525.dat.Z"; I believe if you direct standard out to a new file then you would need another filename statement for this new file from which you then read via a data step. I you omit this redirection then I believe your infile/input statement will directly read from stdout. Also not sure but I believe 2>&1 would also redirect error messages to stdout and though become part of the data you're reading - which is likely not what you want.   ... View more

Here the SAS code portion that returns an indicator macro variable if the condition is met or not. %macro check_mod_date(file_name); data info; length infoname infoval $60; rc=filename('ext_file', "&file_name"); fid=fopen('ext_file'); infonum=foptnum(fid); do i=1 to infonum; infoname=foptname(fid, i); if find(infoname,'Last Modified','it') then do; infoval=finfo(fid, infoname); last_modified_dttm=input(infoval,datetime18.); if datetime()-last_modified_dttm<86400 then condition_met_flg=1; else condition_met_flg=0; leave; end; end; call symputx('condition_met_flg',condition_met_flg,'g'); close=fclose(fid); rc=filename('ext_file'); run; %mend; %check_mod_date(C:\temp\create_data.sas); %put &=condition_met_flg; 54 %put &=condition_met_flg; CONDITION_MET_FLG=1 ... View more

If you've got an LSF license that also allows to schedule non-SAS jobs then below should work.  If you can only schedule SAS jobs then as long as you can issue OS commands out of SAS jobs (XCMD) then all that would be required is to formulate part of below logic in SAS syntax (which of course is less efficient because for each call SAS needs to be invoked).   Questions: 1. Is below logic what you're trying to achieve? 2. Do you need this in SAS syntax or can you also schedule bash scripts?   Using Copilot with below prompts: "using lsf rerun job in regular intervals until condition is met condition is file modified date less 24 hours in past compared to current time"   I've got as reply: Got it! To rerun an LSF job at regular intervals until a file’s modified date is within the last 24 hours, you can modify the previous script to include this specific condition check. Here’s how you can do it: Job Script: This is the script that performs your task. Wrapper Script: This script submits the job and checks the file’s modified date. Here’s an example of the wrapper script: #!/bin/bash # Define the condition check function check_condition() { # Replace /path/to/your/file with the actual file path file="/path/to/your/file" # Get the current time and the file's modified time current_time=$(date +%s) file_mod_time=$(stat -c %Y "$file") # Calculate the time difference in seconds time_diff=$((current_time - file_mod_time)) # Check if the file was modified within the last 24 hours (86400 seconds) if [ $time_diff -le 86400 ]; then return 0 # Condition met else return 1 # Condition not met fi } # Submit the job to LSF bsub < your_job_script.sh # Loop until the condition is met while ! check_condition; do # Wait for a specified interval before rerunning the job sleep 600 # Wait for 10 minutes (600 seconds) # Resubmit the job bsub < your_job_script.sh done In this script: The check_condition function checks if the file’s modified time is within the last 24 hours. The stat -c %Y "$file" command retrieves the file’s last modified time in seconds since the epoch. The time_diff variable calculates the difference between the current time and the file’s modified time. The script resubmits the job every 10 minutes until the condition is met. You can adjust the file path, sleep interval, and other parameters as needed for your specific use case. Does this look like what you need?       ... View more