The other question was asked in the context of a scheduled batch run. So the
following suggestion may not be practical for that. For your question you
can use the DBPROMPT option on the libname:
libname clfy oracle dbprompt=yes path='oracleserver';
That option is valid in proc sql passthru code too:
connect to oracle (dbprompt=yes) ;
From: Larry Kaskey [mailto:LKaskey@TRACFONE.COM]
Sent: Tuesday, February 03, 2004 5:14 PM
Subject: connecting to oracle
I am creating a library like this...
libname clfy oracle user=xxxxxx password=xxxxxxx
I have two questions....
1. Is there a way to avoid the hard coding of my username and
password...perhaps have sas prompt me for those. I believe someone asked a
similar question today
2. When I create the library, I can access the data tables, but when I
drill down in the folder to see the names of the tables, the folder appears
blank. Why would that be?
I am using EG 2.0 for this.
Thanks for any and all help!!
Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately.