About DBailey

DBailey · ‎05-23-2017

Any ideas on why (or how to turn off) I'm getting a warning message that says a SQL Server job that was submitted started successfully? WARNING: During execute: [SAS/ACCESS][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Job 'A2A25B47-24FC-498B-B738-E89C3AD1AAB7' started successfully. I'm guessing that the warning doesn't mean much...but it is confusing to see it.

DBailey · ‎01-06-2016

I think they are going to look at setting $BATCH_LOGPATH different for the different users.

DBailey · ‎01-06-2016

Thanks...I'll forward this to the admins for evaluation.

DBailey · ‎01-06-2016

We have what I would consider to be a fairly large (300+ users) grid environment across 10 or so different departments. Many of the users automate their processes by creating Flows in Management Console schedule manager. When trying to troubleshoot, it is sometimes difficult to find the right log file when all of the logs get put in the same location ($BATCH_LOGPATH). The path can be changed manually (a minor pain in itself) when adding a job to a flow, but an accidental click resets the location to $BATCH_LOGPATH. I'm looking for how to set the $BATCH_LOGPATH variable by user so that the logs can be segregated by department.

DBailey · ‎01-05-2016

I'm looking for some information on how we might customize the batch log location by user. We have a fairly large installation and scheduled work flows use the default $BATCh_LOGPATH unless each job is customized at time of scheduling. That works....but it is a bit of a pain and is subject to being reset by accidental clicks.

DBailey · ‎09-11-2015

You might end up with different export statements for each area/chart field option. In the current version of SAS, you can send data to the same file but different sheets by using the "sheet=" option. something like proc export data=srcdata (where=(area='Area1' and chart_field_1='c1')) file=a1 dbms=xlsx replace; sheet='c1'; proc export data=srcdata (where=(area='Area1' and chart_field_1='c2')) file=a1 dbms=xlsx replace; sheet='c2'; proc export data=srcdata (where=(area='Area2' and chart_field_1='c1')) file=a2 dbms=xlsx replace; sheet='c1'; proc export data=srcdata (where=(area='Area2' and chart_field_1='c2')) file=a2 dbms=xlsx replace; sheet='c2';

DBailey · ‎09-10-2015

Have you tried: connect using WWtest as cWWTest;

DBailey · ‎08-27-2015

try this: %let Cur_month='30Apr2013'd; %let sqlval = %sysfunc(putn(&Cur_month,yymmddd10.)); %put sqlval=&sqlval; and I believe the syntax for the date math would be: dateadd(dd,-180,%str(%')&sqlval%str(%')) sorry..had to fix the sql syntax

DBailey · ‎08-13-2015

looks like autocomplete was the culprit. Still sometimes slow, but it doesn't hang like it was.

DBailey · ‎08-12-2015

7.1

DBailey · ‎08-12-2015

I have a fairly large sas program (1500 lines or so) linked in EG. Whenever I'm editing the program near the end, EG freezes for 4-5 seconds after every character edit. Just typing in the program is almost impossible. Any suggestions on what may be causing this?

DBailey · ‎06-30-2015

proc sql; create table table_C as select g1.*,g2.* from Table_A g1 left join TABLE_B g2 ON g1.ALPHA eq g2.ALPHA and g1.BETA eq g2.BETA where g2.beta is null; quit;

DBailey · ‎05-18-2015

I've seen two methods: 1) create a separate table to house the new records and then append proc sql; create table work.recs_to_add as select distinct 'C1' as site, 123 as value from test t1 where not exists (select * from work.test where site='C1'); insert into test(site,value) select site,value from work.recs_to_add; quit; or 2) create a temp variable as part of a data step: data test; set test end=eof; retain tmpSite; format tmpsite $1.; if _N_=1 then tmpSite='N'; if site='C2' then tmpsite='Y'; output; if eof and tmpsite='N' then do; site='C1'; value=123; output; end; run;

DBailey · ‎04-16-2015

true...but that's what I'm trying to do. It looks like SAS is sending invalid syntax to oracle for the name change as you can't include the schema as part of the "to" name.

DBailey · ‎04-16-2015

Using Proc datasets against oracle: proc datasets lib=ldbmr memtype=data nolist nowarn; delete tmpzippsycle:; delete psycle_zip4_xref; change stage_psycle_zip4_xref=psycle_zip4_xref; run; produces an error: ERROR: ORACLE execute error: ORA-01765: specifying owner's name of the table is not allowed. any ideas? dat log below 23 proc datasets lib=ldbmr memtype=data nolist nowarn; 24 delete tmpzippsycle:; 25 delete psycle_zip4_xref; 26 change stage_psycle_zip4_xref=psycle_zip4_xref; 27 run; NOTE: Deleting LDBMR.TMPZIPPSYCLE (memtype=DATA). ORACLE_7: Prepared: on connection 4 SELECT * FROM DBMR.TMPZIPPSYCLE ORACLE_8: Executed: on connection 4 DROP TABLE DBMR.TMPZIPPSYCLE NOTE: Deleting LDBMR.TMPZIPPSYCLE_2 (memtype=DATA). ORACLE_9: Prepared: on connection 4 SELECT * FROM DBMR.TMPZIPPSYCLE_2 ORACLE_10: Executed: on connection 4 DROP TABLE DBMR.TMPZIPPSYCLE_2 NOTE: Changing the name LDBMR.STAGE_PSYCLE_ZIP4_XREF to LDBMR.PSYCLE_ZIP4_XREF (memtype=DATA). ORACLE_11: Prepared: on connection 4 SELECT * FROM DBMR.PSYCLE_ZIP4_XREF ORACLE_12: Prepared: on connection 4 SELECT * FROM DBMR.STAGE_PSYCLE_ZIP4_XREF ORACLE_13: Executed: on connection 4 RENAME DBMR.STAGE_PSYCLE_ZIP4_XREF TO DBMR.PSYCLE_ZIP4_XREF ERROR: ORACLE execute error: ORA-01765: specifying owner's name of the table is not allowed.

Online Status	Offline
Date Last Visited	‎08-17-2026 03:59 PM

Re: Create snowflake table as select from sql

Re: Create snowflake table as select from sql

Re: Create snowflake table as select from sql

Re: Create snowflake table as select from sql

Create snowflake table as select from sql

Re: SAS Logs from LSF Scheduled jobs

Re: SAS Logs from LSF Scheduled jobs

Re: SAS Logs from LSF Scheduled jobs

Re: SAS Logs from LSF Scheduled jobs

SAS Logs from LSF Scheduled jobs

Add ability for PROC JSON to parse and read in JSON-formatted data

Re: proc sql and connect using

Re: proc sql and connect using

Re: Why this warning in numeric to charactoer conversion?

Re: Lag equivalent in PROC SQL

Enterprise Guide 8.2 Pane options

SAS/Access connection to sql server

Re: $BATCH_LOGPATH

Re: $BATCH_LOGPATH

Re: $BATCH_LOGPATH

$BATCH_LOGPATH

Re: how to split excel export into separate sheets

Re: How to derive my proc sql connection string from libname connectio...

Re: SAS date parameter in pass through SQL statement

Re: Problem with large linked program nodes

Re: Problem with large linked program nodes

Problem with large linked program nodes

Re: PROC SQL-Combining data from multiple tables

Re: How to check if an value existing in a column? and if not then add...

Re: Proc Datasets Error

Proc Datasets Error

SAS Global Forum 2019

SAS Global Forum 2020