• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 584
  • Last Modified:

SSH Settings - SAS Job getting killed

Hi,

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
0
aruku
Asked:
aruku
  • 2
  • 2
  • 2
  • +1
1 Solution
 
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.
0
 
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 sysin=code.sas &
0
 
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.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
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.
0
 
arukuAuthor Commented:
ok. Is this facility like we have in our settings or we need to install this utility separately.
0
 
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.
0
 
arober11Commented:
What OS is you remote server running?

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

http://athens.src.uchicago.edu/econlab/background.shtml
http://en.wikipedia.org/wiki/Nohup

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

http://en.wikipedia.org/wiki/At_%28Unix%29 

or:  

http://en.wikipedia.org/wiki/Crontab
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now