LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (January 2010, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 19 Jan 2010 13:59:07 -0500
Reply-To:     Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Gerhard Hellriegel <gerhard.hellriegel@T-ONLINE.DE>
Subject:      Re: Error or Abort on invalid data

I don't know how to add that option to the standard file-reader. However I don't find file-reader and file-writer very useful. What I'd do is not to use user-written code, but to create 2 user-transformations. One for input with that special behaviour to set a returncode or abort, one for output with the usage of proc export which let you have variable names as column headers in CSV files for example. You can also add some options to trigger special behaviours. Gerhard

On Tue, 19 Jan 2010 08:02:32 -0800, Frank Poppe <Frank.Poppe@PWCONSULTING.NL> wrote:

>Hi, > >I have a job in DI Studio that reads data from an external (CSV) >file. >This process is scheduled together with some other jobs. > >Occasionally (or even more often) there is invalid data in one of the >fields. This causes NOTE's in the LOG, but the process continues. >I would like to have an error condition set, so that the process >aborts, or at least so that the scheduler will not start subsequent >processes. > >I know that the _ERROR_ flag is set within the data step so that code >could be added there to abort. But there is no way that I know of to >accomplish that from within DI Studio, without changing to 'user >written code'. And that makes the code difficult to maintain in the >future. > >Any ideas to force an abort, or at least a return code for the job >that prevents the scheduler from continuing? > >Thanks > >Frank Poppe >PW Consulting >the Netherlands


Back to: Top of message | Previous page | Main SAS-L page