From: jaheuk on 4 Feb 2010 02:55 dear all, to use in SAS SQL an update/insert you have to specify UNDO_POLICY=OPTIONAL But because of this i get a WARNING in the log and on mainframe this gives a RETURN CODE 4! HoW can i push this RC to 0 (zero) ?? Regards, Herman
From: Sigurd Hermansen on 4 Feb 2010 17:21 Herman: Open http://support.sas.com/documentation/cdl/en/sqlproc/62086/HTML/default/a001360983.htm and search for UNDO_POLICY. Setting UNDO_POLICY=none may give you RC=0, but will make it impossible to roll back an INSERT. S -----Original Message----- From: SAS(r) Discussion [mailto:SAS-L(a)LISTSERV.UGA.EDU] On Behalf Of jaheuk Sent: Thursday, February 04, 2010 2:56 AM To: SAS-L(a)LISTSERV.UGA.EDU Subject: SQL update/insert dear all, to use in SAS SQL an update/insert you have to specify UNDO_POLICY=OPTIONAL But because of this i get a WARNING in the log and on mainframe this gives a RETURN CODE 4! HoW can i push this RC to 0 (zero) ?? Regards, Herman
From: montura on 5 Feb 2010 09:01 With SAS dataset constraints, you can use undo_policy=none and data will roll back when errors are detected. for example, rollback when any row has a missing value in a specified column... proc sql; create table temp ( anyColumnName num, constraint anyColumnName check(anycolumnName is not null) ); quit;
From: Charles Harbour on 5 Feb 2010 11:01 Why are you setting this option? If you're looking to increase performance while doing a large insert/update, you may see better performance by separating your inserts from your updates and using bulkload (or libname, proc append) to perform your inserts. I also counsel _not_ using sysrc to run your insert/update logic--it' my opinion that that methodology does not work well with sas. HTH, CH On Wed, 3 Feb 2010 23:55:37 -0800, jaheuk <hejacobs(a)GMAIL.COM> wrote: >dear all, >to use in SAS SQL an update/insert you have to specify >UNDO_POLICY=OPTIONAL >But because of this i get a WARNING in the log and on mainframe this >gives a RETURN CODE 4! >HoW can i push this RC to 0 (zero) ?? > >Regards, >Herman
|
Pages: 1 Prev: Are these SAS date functions Next: Assigning value to a variable in proc sql |