| Date: | Wed, 7 Feb 2001 16:05:17 -0500 |
| Reply-To: | rpresley <rpresley@GMCF.ORG> |
| Sender: | "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU> |
| From: | rpresley <rpresley@GMCF.ORG> |
| Subject: | Abnormal termination of remote SAS |
| Content-Type: | text/plain; charset="iso-8859-1" |
|---|
SAS-L,
When a program has been remotely submitted to our Unix box from the PC/NT
and it seems to be stalled we click on the "Break" button. We then select
"TCP/send receive break" from the pop up menu. This terminates our
connection with the remote server. It appears that this results in an
abnormal shut down of SAS on the remote (Unix) server. Work libraries may
not be deleted. More importantly it appears that Oracle processes that were
running in conjunction with the SAS job do not terminate properly.
What is the best way to terminate a remote SAS job? How can we terminate
the processing of code on the remote server without losing our connection to
the remote server? How can we terminate remote processing and be assured
that any processes on Oracle associated with the SAS job will terminate
properly also?
Thanks for your help.
Rodney J. Presley, PhD
Georgia Medical Care Foundation
57 Executive Park South, NE
suite 200
Atlanta, GA 30329-2224
404-982-0411 ext. 7574
404-982-7592 fax
rpresley@gmcf.org
------------------------
CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files
or previous e-mail messages attached to it may contain proprietary,
privileged or confidential information. If you are not an intended
recipient, or a person responsible for delivering it to the intended
recipient, you are hereby notified that any disclosure, copying,
distribution or use of any of the information contained in or
attached to this transmission is STRICTLY PROHIBITED. If you have
received this transmission in error, please immediately notify me by
reply e-mail and destroy the original transmission and its
attachments without saving them in any manner.
-----------------------
|