aruku
asked on
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
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
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.
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 &
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 &
ASKER
@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.
@lowaloysius - we are running the job in the back ground.
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.
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.
ASKER
ok. Is this facility like we have in our settings or we need to install this utility separately.
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.