About ChrisNZ

ChrisNZ · ‎10-24-2024

> I cannot access the logs produced by that job until it is complete What message do you get? Please describe what happens. You should be able to see the log.

ChrisNZ · ‎10-24-2024

There are various menu entries iirc. Have you tried them? I don't remember the exact phrase, but something like Sent to or Open with or View with.

ChrisNZ · ‎10-21-2024

If you want to transfer the files, you can compare the data inside using proc compare. If you want to compare before transferring, or if you want to just use the OS on exactly identical files, you can compare the files' checksum (the SHA-256 hash values).

ChrisNZ · ‎10-17-2024

@Kurt SPDE is also great to speed up IO thanks to its much better compression algorithms and better indexing, even if just one directory is used.

ChrisNZ · ‎10-17-2024

Have you tried using a prompt?

ChrisNZ · ‎10-17-2024

Probably you also want %LET DTMVTFIM = %sysfunc(INTNX(MONTH1, %sysfunc(DATE()), &DT_INI., E));

ChrisNZ · ‎10-17-2024

If all files are in the same directory, list all the files in that directory (see the pinned topic https://communities.sas.com/t5/SAS-Programming/How-to-List-all-the-files-in-a-folder/m-p/674065#M202918) and get the size of all component files. Don't forget index files if applicable. Note that you can use the PARTSIZE option of LIBNAME SPDE to avoid splitting the data into multiple files.

ChrisNZ · ‎10-14-2024

Please select a reply as the answer if you answered your question.

ChrisNZ · ‎10-14-2024

Please select a reply as an answer if you answered your question.

ChrisNZ · ‎10-07-2024

@stataq wrote: dose that mean "&colvar.=A1" and "&colvar. in (1,2)" are correct way to refer a macro variable name and value, but they should not be used in the same step using and to connect the conditions? "&colvar.=A1" and "&colvar. in (1,2)" are obviously 2 different ways to test since you're testing against different values (A1 and 1,2) The first test would typically be macro language test (where I used %if ) to know the value given to the macro variable, while the second test tests a data set variable whose name is &colvar, i.e A1 for example (and if is used) to know the value of the data set variable.

ChrisNZ · ‎10-07-2024

@stataq wrote: Hello, How can I refer a macro variable and its value in a data step? for example, if I have a dataset that have 3 variables A1 B2 and C3. If I set marco variable "%letr colvar=A1"., how can I utilized &colvar. to get a filter that macro variable colvar was setup as 'A1" and its value is within (1,2)?: if &colvar.=A1 and &colvar. in (1,2) then do;... how to refer a macro variable name, and how to refer a value that belong to a variable? If I understand your question correctly, you simply code: if symget('colvar'='A1') then if &colvar. in (1,2) then do;... Note that all values of &colvar must exist as variables in the data set since there's code to test them, or SAS wil complain. Otherwise a better method would be %if &colvar.=A1 %then %do; if &colvar. in (1,2) then do;...end; %end; Here, only the appropriate test is inserted in the data step.

ChrisNZ · ‎10-07-2024

Are you using ODBC? I'd expect a dsn option in the libname statement if you are. That ODBC manager's DSN entry would contain the ODBC connection parameters. I'd just create a test table on the new server and check that I can see it.

ChrisNZ · ‎10-07-2024

Have you seen this? https://communities.sas.com/t5/Administration-and-Deployment/Error-in-SASPy-using-Python-Linux-to-a-remote-SAS-9-server/td-p/865565 If so please give more details.

ChrisNZ · ‎10-06-2024

@Kurt_Bremser I've seen the construct &&&var&i used on regularly. I'm surprised you haven't.

ChrisNZ · ‎10-05-2024

You can also execute commands such as: execute by COBSPROD (drop table test_table1) ;

Online Status	Offline
Date Last Visited	‎08-06-2025 07:02 AM