For a firewall, a rejected connection is something it does because it was instructed to do so, it is not an error. I would first investigate possible connection limits in your network infrastructure connecting to the outside world. Firewalls, VPN nodes, whatever. ... View more

WORK is specifically designed to be non-persistent. The directory is created when the SAS session starts, and removed as soon as it terminates. You do not have to copy datasets to WORK to use them, you can use them right where they are stored. If you want to make your code more flexible, you can use macro variables: %let worklib=work; proc whatever data=&worklib..dataset .... By changing WORKLIB to another library name, you can redirect the dataset access. ... View more

Make it a habit to have %LOCAL as the first statement in every macro you write, and then include any variable you use that is not a macro parameter or explicitly coming from a global or higher level context. This will prevent unwanted side effects like the one you accidentally created here.   ... View more

Absolutely no need for transposing, which in fact makes your task unnecessarily hard. data calc (rename=(visit_date=last_visit)); set pt_visits; by patient; if last.patient; days_since_last_visit = today() - visit_date; run; Maxim 19: Long Beats Wide.   Posted from my tablet, therefore the code is not tested. ... View more

The first question that arises: why do you need to do this? This dataset looks very much like one of the dreaded "wide" datasets which always cause trouble and are much harder to handle than "long" datasets. This also smells like data hidden in structure. The only fully automated way to handle this which comes to my mind is a double TRANSPOSE with a modification of the long dataset: data _temp_; input x1 x2 x3 x4; n = _N_; datalines; 1 2 3 4 ; proc transpose data=_temp_ out=long ; by n; var x:; run; data long2; set long; substr(_name_,1,1) = "y"; run; proc transpose data=long2 out=want (drop=_name_) ; by n; var col1; id _name_; run; Note that, for the second TRANSPOSE to work correctly, you need a variable (or variables) to identify the original observation and used in the BY.   Let us know how you arrive in this situation in the first place. ... View more

For working, you always use internal disks connected to the main bus via SATA. The external USB connections are good for backup and similar, but not for real heavy load working. ... View more

Either you have a completely inadequate disk (read: from the 90's), or you have other processes congesting your computer. Process monitor from Microsoft Sysinternals can be handy. ... View more

Ask your government. But don't tell them you use a foreign VPN to circumvent their "security measures". ... View more

TBH, a large part of my accepted solutions have been rehashes of other solutions/posts, and "translation" of SAS documentation for the novice user. In short, I was a better search engine. With the advent of AI-supported searches in Google and others, these have taken over that particular role, and so the people coming here for help find answers much easier before they post a new thread asking the same old, same old. And they will be pointed towards relevant documentation also, including examples. Knowing where (and how) to look for relevant documentation has always been a daunting task, given the sheer size of SAS doc. ... View more

Can there be groups with more than 5 observations? ... View more

What do you intend to do with this data? Keep in mind that, for most purposes, the original long layout is better than wide. ... View more

Run it, then look at the log. This will tell you all you need. Also see Maxims 4 and 2. ... View more

This filename out zip 'Batchfile 7.6.zip'; is your problem. You did not use a fully qualified path name, so SAS tries to write to its current working directory, which is usually the place where the script file WorkspaceServer.sh is located, and where you do not have write permission. Use a file name that includes the complete path starting at root (like you did for indir) and pointing to your home directory. You can also use the tilde shortcut for this: filename out zip '~/Batchfile 7.6.zip'; ... View more

Something unbalanced (unbalanced quotes, macro definition without a valid %MEND, ...) has caused your SAS session to become unstable. Start a new session and rerun your code, paying attention to the above. ... View more