Earlier the datasets I did the COMPRESS tests on had a high level of compression but I ran COMPRESS on a dataset with a lot of binary data and the output COMPRESSed dataset became 90G instead of 72G and it took quite a while longer to output it than the uncompressed dataset.    I had seen earlier in a paper that SAS would not compress a dataset that would be bigger than the uncompressed but when I went back and looked at the paper, it was quite old (SAS 8).    I'm using SAS 9.4 M3. ... View more

Thanks for mentioning that but yes the CLEANWORK utility runs hourly on each server via crontab.    Also on a daily basis will kill any SAS bjobs that are older than 5 days which has helped a lot. ... View more

Hi Juan   Regarding the question about getting users to add the OPTIONS COMPRESS=YES, what I mean is that I can send out an email to all users but only a portion of them will take action which is why I was interested in making the compress=yes a default.   I was wondering why the SASWork and Utilloc usage would go up?    I was hoping that the COMPRESS option might free up room there too by compressing WORK datasets as well.   Our WORK volume gets heavily used for large amounts of data since WORK is a 10TB flash drive and much faster than DASD and has more free space available most of the time than some teams have on their DASD volumes.   Several times a week there are multiple users using terabytes of WORK storage and I have to kill the jobs of the largest consumer to avoid being 100%.  ... View more

I think this is great news for me as an admin because our security team is going to start blocking SSH port 22 that is used for SFTP.   I'm assuming the copy task uses a SAS port and if SAS/Secure is enabled, that the transmission is encrypted.   Do you know if this is the case? ... View more

I realize that there will be other ways for content to be downloaded off of the server (copy/paste, email, etc) but I've started on this journey to write the tools to know what's occurring on the system and I'll capture these other items as they get identified. I used the logconfig.trace.xml on WS and I didn't see the IOM::FileService events but I did see evidence of the file transfer in these messages: 2016-12-01T15:22:23,078 TRACE [00002894] 2:sas - Bridge PE [7fad0c395fd0] 7fad000a3aa0: 00 00 00 00 2f 68 6f 6d 65 2f 73 61 73 00 01 00 |..../home/sas...| 2016-12-01T15:22:23,078 TRACE [00002894] 2:sas - Bridge PE [7fad0c395fd0] 7fad000a3ab0: 0d 00 00 00 73 61 73 63 68 65 63 6b 2e 6c 6f 67 |....sascheck.log| Do you have any examples of capturing the IOM:FileServices? BTW, I recently changed WS logconfig.xml to record errors and wrote a Perl script that reformats the log data into a CSV file and emails it to me so that I now have visibility to users having database connection errors instead of waiting for a SAS user to report the issue and guess how many others are having the issue. ... View more

I found that the EG logging on the PC does capture the copying but I need to track it on the server and haven't found where that would be logged or what service on the server is providing the transfer.  Thanks for the feedback. 2016-11-30 10:55:18,614 [17] INFO  SAS.Tasks.CopyFiles.SasFileTransferTask [(null)] - Running Copy Files task: Copy Files ,,, 2016-11-30 10:57:21,448 [17] INFO  SAS.Tasks.CopyFiles.SasFileTransferTask [(null)] - Checking for existence of target folder: C:/users/kcd01/Downloads 2016-11-30 10:57:21,448 [17] INFO  SAS.Tasks.CopyFiles.SasFileTransferTask [(null)] - DOWNLOADING files... ... View more

We are using SAS 9.4 M2 Grid on RHEL 6.8. So far I have just enabled WS logging on QA but I want to do so for production so that we can detect SAS/ACCESS errors. I feel like I can manage the logs (scan them for errors and remove them) but I don't want to have any unnecessary performance hits. I configured the logging with ImmediateFlush false. So far using threshold INFO but assuming that the ERROR threshold would be enough to detect the ACCESS issues I'm looking for. Regarding the EG file copy, this will be a really good feature, assuming it's encrypted, since Security wants the ssh sftp shutdown, but they would also want some way to review what files are uploaded/downloaded from the servers. ... View more

Hi Kurt, last May I converted a SAS 9.4m2 Redhat Grid over to authenticating with Active Directory using sssd/pam services. Along with that I had to change ownership and groups for 700,000+ files. It's much better for us now that we don't have users maintaining local accounts on multiple Linux servers. I can share some of the details with you next week if you think it would be useful for you. ... View more

Another topic for me would be along the lines of Site Reliability Engineering, what tasks should an admin automate to maintain, update and check on health of their systems.     Currently we are on 9.4 M2 but we are looking to 9.4 M3 to have the new version of Environment Manager to better manage SAS. ... View more

I'm interested in hearing about successes/failures of implementing SAS in the cloud (preferably Google Cloud) and how to decide which approach to take (containers, SAS 9.4 on VMs, or Viya). ... View more

Thanks for the insight.   I should have mentioned that the server is a RHEL 6.x 2 node grid.   It's a pretty big effort to update our servers (with 250+ SAS users) from 9.4 M2 to M3 but the client PCs will be upgraded from Win 7 to 10 this summer.    It's nice that we can take the EGuide from M3 and push that out.   I'm now trying to determine what needs to be done for EMiner (only 5 users) since we aren't planning to upgrade the servers until Q4.   ... View more