SSH Settings - SAS Job getting killed


I am running a huge job which runs for about 3 days and because of some issues it is getting killed. I have approached the admin and the answer was to work with SSH settings.

My environment is unix.

Can any one help me on this.

Thanks in advance
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Matt VCommented:
Are you running the job remotely on the SSH server?  If so, find out if the screen utility is installed, this gives you the option to reconnect to a disconnected "scren" session that continues to run.
Aloysius LowCommented:
how are you triggering the sas code?

have you tried sending the job process to run in the background by adding an '&' behind the command? e.g. /app/sas &
arukuAuthor Commented:
@matt -   Yes matt we are running the code background but are there no settings where I can avoid the killing of the job insted of the killed job running again.

@lowaloysius - we are running the job in the back ground.
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

Matt VCommented:
Screen will allow you to background your session, and it will stay running until you reconnect to it.  Whatever was running on the screen when you left will be running while you are gone and when you get back.

I believe CTRL-A then D disconnects the session (send it to the background) and when you ssh back in you can run screen -r and it will re-attach to the foreground.

Also useful if the connection fails, you can ssh back in and execute screen -r.
arukuAuthor Commented:
ok. Is this facility like we have in our settings or we need to install this utility separately.
Aloysius LowCommented:
i'm just wondering - is there a batch job that has been scheduled say every night to do housekeeping and backup for example.

does the job always fail at the same time for example? anything common between the job failures?

i'm just thinking if a batch job has been schedule at a certain time of the day to kill off runaway processes before starting any batch runs or take backup of the server or some other housekeeping activities.
What OS is you remote server running?

If it's Unix / Linux based you could just "nohup" the job, see:

Else schedule the job via "at" or "cron", see: 


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.