To add my two cents - turn off the log. It's useless here. Also turn off the auditing. If you fail on the data read, send the data via a run map as a text blob to a 2nd map with auditing and/or logging on.
All of this involves graduate-level Mercator mapping - run maps, auditing, multiple output cards. If you don't have a good handle on the tool (which you don't), get help. You'll embarrass yourself and do nothing but chew hours trying to solve this. And it sounds like you're re-architecting as well. Michael Mattias/LS wrote: >> We are using WTX 8.1 software for EDI translator. I have to do >> validation at the ST level before converting that message into custom >> specific file. I can turn on log file and send information of >> validation error, but it is affecting performance. Is their anyother >> way? Please help me. >> > > "Affecting performance" is a tad vague, isn't it? Causes the software to > fail? Results in incorrect data? Slows it down? Changes the user interface > behavior? Audit/trace files too big to be useful? > > That said, I have worked with Mercator/DataStage 1,2,5,6,7 but not 8 (now > called WTX); there is a 'REJECT' function in all versions at least up to 7 > so let's assume this function was retained in WTX 8x. > > Run your input file thru a map, REJECTing invalid transaction sets; do this > without logging, auditing or tracing. Pass any good output to your actual > application destination. > > Now run the REJECTS ONLY thru another map, this time WITH detailed auditing > and/or logging and/or tracing. > > This gets your 'good' input processed without any baggage, and provides you > with detailed debug information for anything which fails..debug info > unencumbered by details of non-failing input. > > No muss, no fuss, no bother. > > (Plus, just as a matter of style: I like exception-based processing. No > sense holding up the "good" input which may be 95% of the total all because > of one dinky little transaction set is invalid, is there?) > > BTW, you can't use the standard ANSI X12 detail type trees for this, since > the presence of an invalid transaction set affects the control totals in the > GE and IEA segments and one bad transaction set will generate a cascading > failure all the way up to the interchange level. (Which might be what you > want anyway?) But you surely can gin up a tree to deal with this. > > > Michael C. Mattias > Tal Systems Inc. > Racine WI > [email protected] > http://www.talsystems.com > > > > > > > > > ------------------------------------ > > ... > Please use the following Message Identifiers as your subject prefix: <SALES>, > <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> > > Job postings are welcome, but for job postings or requests for work: <JOBS> > IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links > > > > > -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Brian Lehrhoff, EA ([email protected]) Messaging Consultant 201-913-4506 Upgrade your Quickbooks for 20% off at http://ea.brianlehrhoff.com Circular 230 Notice is located at http://ea.brianlehrhoff.com/230notice.html %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ------------------------------------ ... Please use the following Message Identifiers as your subject prefix: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Job postings are welcome, but for job postings or requests for work: <JOBS> IS REQUIRED in the subject line as a prefix.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/EDI-L/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/EDI-L/join (Yahoo! ID required) <*> To change settings via email: mailto:[email protected] mailto:[email protected] <*> To unsubscribe from this group, send an email to: [email protected] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
