Hello Patrick, yes, it's on SAS Metadata 9.4. I tried to repoint last night but it says the table doesn't exist even the table is there. I think need to update the metadata. ... View more

We were able to resolve now this issue. The reason behind the below error message is that /bin/su has only Read permission.. Whereas compared to our working environment, there is an read,write, permission. After update the permission we can successfully schedule the job smoothly. Unable to get JS_SU_COMMAND JFJobExecutionAgent::_executeCommand: su command to execute </bin/su sasdemo -c /sas/scheduler/pm/work/tmp/JS_HjFO64 ... View more

"The components at work here are SAS Management Console, Process Manager (jfd) and LSF. SMC is a Process Manager client, telling Process Manager to run the flow. Process Manager does this by submitting the job(s) in the flow to LSF." -- yes this one is correct.   "When you say you can schedule on LSF in Linux, are you saying it works when running SMC from the Linux host, or when instructing the flow to run in Flow Manager, or are you submitting the same bsub command to LSF from the command line?" -- when submitting the flow on SMC it says successful but when we're seeing it on flow manager it says its exited. The one I can schedule is bsub from the command line itself. I have raise this to Technical Support, they enable debug and got this JFJobExecutionAgent::_executeCommand: Unable to get JS_SU_COMMAND JFJobExecutionAgent::_executeCommand: su command to execute </bin/su sasdemo -c /sas/scheduler/pm/work/tmp/JS_HjFO64   As per the IBM ticket, https://www.ibm.com/support/pages/job-submission-failed-different-error-codes. It says its because of the directory not having the executable permission but the noexec is not visible on the mount point of this directory and we tried to change also to another but same result.. We are still investigating on this      ... View more

Hi greg, Its consistent. Suddenly users cannot schedule, even new flows cannot schedule. It seems the connection from SMC to LSF is the issue but couldnt trace where. I can run the same jobs on SAS even on linux command line, I can schedule also on LSF in linux also. I raised to SAS TS also and they still checking ... View more

Hi RobH, Thanks for the quick response. For the prerequisites, I'm okay with this. I'm just using one machine. The thing im trying to do now is like the Method A. The first step in the method A is it referring the contents of the backup from old server which is named as a backup ID? Step 1 on Method A "copy the content of the source shared vault to the alternate shared vault." Once i copied it, i dont see it on the backup list for the command sas-admin backup list ... View more

Hi Greg, Thank you for replying. I tried that also bsub sleep 20 and then i run bjobs -l and i can see the sleep job also. ... View more

I figured this one out eventually. The certificate must have the FQDN. Need to re-apply the certificate and run the distribute certificate using the ansible-playbook. Once done, check the localhost.crt and it should have the FQDN. ... View more