Unfortunately, no luck for me here. The sysget)USER). When ran in batch, it still outputs 'edwardrichards' without the metaserver suffix. I think I will have to park this one and find another solution for parallel processing. (Here's hoping we get SAS/CONNECT). ... View more

Thanks Kurt, outputs: in SAS: edwardrichards@tu.local in batch PuTTy: edwardrichards I have also foundthat the options: METAPROFILE, METASERVER & METAAUTORESOURCES all have different values set. I will try to add these and let you know the outcome. thanks again. ... View more

I have compared both proc options outputs in Word - nothing about user is different 😕 ... View more

I should have been more spefici here - I actually don't know. I was hoping to find a USER option where I could specify, but I don't think there is one? With "-compress yes" added to the PuTTy code, I still have the same error 😞 ... View more

I think it's worth mentioning at this point, the file being sorted is only 192 KB. I'm going to try and find a way to run the batch server using my user ID, and also with compress option. The code runs fine in SAS EG again. ... View more

ChrisNZ - Hi, thanks for the suggestion - unfortunately, this can't be the problem as the program is creating datasets in the STG directory. ... View more

I understand it does look like that. If I delete the files and re-run in SAS, runs fine. If I delete the files and re-run in PuTTY, I/O error. Thanks very much for your help so far Kurt - really appreciate it. The proc options results are slightly different. As you predicted, compress = NO in Batch. There are a couple of other different ones: NOXCMD TERMINAL SYNTAXCHECK DEVICE NOOBJECTSERVER and some others... The 2 I am unsure about are TERMINAL & NOOBJECTSERVER. ... View more

I see, thank you. The entire log is quite lengthy, as I am creating some formats... What would be most helpful in this case? Here is the log output from the 'opt/..../BatchServer' run from PuTTY: 853 proc contents data=stg.policy out=stg.policy_names(keep=name varnum where=(substr(name,1,5)='Risk_')); run; NOTE: The data set STG.POLICY_NAMES has 10 observations and 2 variables. ERROR: An I/O error has occurred on file STG.POLICY_NAMES.DATA. NOTE: PROCEDURE CONTENTS used (Total process time): real time 0.25 seconds cpu time 0.01 seconds NOTE: The PROCEDURE CONTENTS printed pages 26-27. 854 proc sort data=stg.policy_names; by varnum; run; ERROR: A lock is not available for STG.POLICY_NAMES.DATA. NOTE: The SAS System stopped processing this step because of errors. NOTE: SAS set option OBS=0 and will continue to check statements. This might cause NOTE: No observations in data set. NOTE: PROCEDURE SORT used (Total process time): real time 0.01 seconds cpu time 0.00 seconds I am now receiving I/O errors on the POLICY_NAMES file, regardless of being ran via PuTTY or SAS EG. The day gets better.. ... View more

Hi,   Thanks for that. I've been comparing the proc options output.   I have compared the SAS EG output with PuTTY output and PuTTY Batch output. There are some differences, however BATCH is not working as expected either.   I think I need to be using: /opt/sas/config/Lev1/SASApp/WorkspaceServer/WorkspaceServer.sh ...but, when running this in PuTTY, I am not receiving a log output to compare! Do you have any ideas as to why the log wouldn't be output?   ... View more

When ran in SAS, the output is: path=/SASWORK/SAS_work3A1900004CAC_ploffice01.tu.local/SAS_work7FD900004CAC_ploffice01.tu.local When run in batch: path=/SASWORK/SAS_work1D5F0000538C_ploffice01.tu.local ... View more

Hi Kurt, Thank you for taking the time to help me with this (and the quick response). I'm not 100% sure I am following. Could you confirm for me: Instead of using: /opt/sas/sashome/SASFoundation/9.4/sas *PROGRAM* I could try: /opt/sas/config/Lev1/SASApp/BatchServer/sasbatch.sh *PROGRAM* Kurt, if you had a moment - I have a few questions around this issue that I would love to be answered! ... View more