Move File with Sas pgm
in [SAS]
|
Prev: Variable reduction method
Next: SUBSTR Madness
From: Paige Miller on 1 Oct 2009 14:36 On Oct 1, 3:39 am, ash007 <ramsamyash...(a)gmail.com> wrote: > Hello Arthur, > > Yes I have started with the question on Ascii Files but now I need to > know for the binary file.because I have a 10 Giga dataset and with > "proc copy" it lasts 2 hours.... and with "copy&past" it lasts only 5 > minutes. This doesn't explain your reluctance to use X commands. Without knowing your reasons, I would say that you should be able to use whatever tool/method works best, including X commands which appear to be faster in this case. -- Paige Miller paige\dot\miller \at\ kodak\dot\com
From: Savian on 3 Oct 2009 03:49 On Oct 1, 12:36 pm, Paige Miller <paige.mil...(a)kodak.com> wrote: > On Oct 1, 3:39 am, ash007 <ramsamyash...(a)gmail.com> wrote: > > > Hello Arthur, > > > Yes I have started with the question on Ascii Files but now I need to > > know for the binary file.because I have a 10 Giga dataset and with > > "proc copy" it lasts 2 hours.... and with "copy&past" it lasts only 5 > > minutes. > > This doesn't explain your reluctance to use X commands. Without > knowing your reasons, I would say that you should be able to use > whatever tool/method works best, including X commands which appear to > be faster in this case. > > -- > Paige Miller > paige\dot\miller \at\ kodak\dot\com X commands are turned off in a lot of sites. Alan http://www.savian.net
From: ash007 on 5 Oct 2009 10:39 Hello Sas-Users, How can the pgm SAS wait for the end of the copy of the datasets before execution of the next data step? option noxwait noxsync; data _null_; x copy /*move*/ "c:\users\ash_rmy\documents\ __________________\02_gfm \performancecopie\garantie_tr_ventile.sas7bdat" "c:\users\ash_rmy\documents\ __________________\02_gfm \performancecopie\source"; run; Thanks. ash007.
From: "Data _null_;" on 5 Oct 2009 11:29 I would execute these commands with SYSTASK. It has specific options for waiting and you easily capture return codes. On 10/5/09, ash007 <ramsamyashley(a)gmail.com> wrote: > Hello Sas-Users, > > How can the pgm SAS wait for the end of the copy of the datasets > before execution of the next data step? > > option noxwait noxsync; > > data _null_; > x copy /*move*/ > "c:\users\ash_rmy\documents\ __________________\02_gfm > \performancecopie\garantie_tr_ventile.sas7bdat" > "c:\users\ash_rmy\documents\ __________________\02_gfm > \performancecopie\source"; > run; > > Thanks. > ash007. >
From: Michael Raithel on 5 Oct 2009 12:16
Dear SAS-L-ers, Ash007 posted the following: > Hello Sas-Users, > > How can the pgm SAS wait for the end of the copy of the datasets > before execution of the next data step? > > option noxwait noxsync; > > data _null_; > x copy /*move*/ > "c:\users\ash_rmy\documents\ __________________\02_gfm > \performancecopie\garantie_tr_ventile.sas7bdat" > "c:\users\ash_rmy\documents\ __________________\02_gfm > \performancecopie\source"; > run; > Ash, I think that the answer to this problem is as plain as the nose on your face:-) That is; the BIG clue is hidden in your posting! If you are going to use X statements (or X commands, or CALL SYSTEM) to run your OS commands, and want SAS to wait for them to complete, simply specify "XSYNC" instead of "NOXSYNC". That directs SAS to "suspend" your SAS program, execute the operating system command, and then return control to your SAS program once the operating system command has completed. The good news is that XSYNC is the default, so you should only need to excise it from that pesky OPTIONS statement of yours. Ash, best of luck in all of your SAS endeavors! I hope that this suggestion proves helpful now, and in the future! Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk. +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Michael A. Raithel "The man who wrote the book on performance" E-mail: MichaelRaithel(a)westat.com Author: Tuning SAS Applications in the MVS Environment Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172 Author: The Complete Guide to SAS Indexes http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The cure for anything is salt water--sweat, tears, or the sea. - Isak Dinesen +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |