Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: parsing issue with edi file
Top Forums Shell Programming and Scripting parsing issue with edi file Post 302383384 by fwellers on Tuesday 29th of December 2009 12:28:54 PM
Old 12-29-2009
parsing issue with edi file
Hello,
We have edi files we need to do some extra parsing on.

There is a line that shows up that looks like this:
GE|8,845|000000000

We need to parse the file, find the line ( that begins with GE "^GE" ), and remove the comma(s).

What is the easiest way to do that ? I know I can grab the line individually, fix it and then remake the file again, inserting the line in the proper place.
But I think there should be a proper awk or sed combo that will easily do it for me.

Any help is appreciated.

Thanks,
Floyd
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

parsing logfiles (performance issue)

-------------------------------------------------------------------------------- Hi All, I am reading some logfiles and parsing data and printing to some textfile. Here is my code OLDIFS=$IFS IFS=' ' # just a newline, in single quotes while read data do if then #Parsing the... (4 Replies)
Discussion started by: subin_bala
4 Replies

2. Shell Programming and Scripting

How to Strip lines off Streamed EDI Output

Attached is a streamed EDI ANSI X12 output where the segment terminator/delimiter is a tilde ~ character. Is it possible to do the following pseudo-code in a unix script (using either sed, awk and/or grep)? Open file StreamedOutput.txt Search for ISA and delete the data up to the tilde ~ char... (7 Replies)
Discussion started by: sapedi
7 Replies

3. Shell Programming and Scripting

Parsing of file for Report Generation (String parsing and splitting)

Hey guys, I have this file generated by me... i want to create some HTML output from it. The problem is that i am really confused about how do I go about reading the file. The file is in the following format: TID1 Name1 ATime=xx AResult=yyy AExpected=yyy BTime=xx BResult=yyy... (8 Replies)
Discussion started by: umar.shaikh
8 Replies

4. Shell Programming and Scripting

Compare EDI files by skipping selected Segments

Hi, I wanted to compare EDI files present in Two different Directories which can be related by the file names. While comparing the EDI files i have to skip selected segments such as "ISA" "IEA" and "GS" "GE" since this may have datetime stamp and different "Sender" "Receiver" Qual. and... (3 Replies)
Discussion started by: Sivas
3 Replies

5. UNIX for Dummies Questions & Answers

Issue with parsing config variables

I am using MKS tool kit on windows server. One config variable is defined in windows environment and I am trying to use that variable. # Below RootDir is defined in windows RootDir="\\f01\var" # in unix script details="$RootDir/src|$RootDir/tgt" src=`echo $details|awk -F '|' '{print... (1 Reply)
Discussion started by: madhukalyan
1 Replies

6. Shell Programming and Scripting

Parsing issue

Scripting geeks please advice how this script should parse the input parameter to File Name convention to search the strings. Enclosed is the basic view of the search architecture. ##******************************************************************************************************* ## ... (2 Replies)
Discussion started by: raghunsi
2 Replies

7. Shell Programming and Scripting

Issue with awk script parsing log file

Hello All, I am trying to parse a log file and i got this code from one of the good forum colleagues, However i realised later there is a problem with this awk script, being naive to awk world wanted to see if you guys can help me out. AWK script: awk '$1 ~ "^WRITER_" {p=1;next}... (18 Replies)
Discussion started by: Ariean
18 Replies

8. Shell Programming and Scripting

EDI File Parser

I've one EDI file which is to be parsed into 7 different file. I managed to extract required segments for a file(HEADER) to a separate file(sample3.dat) and is given below. $ cat sample3.dat REF*EI*273543997~ REF*2U*HELLO~ REF*G2*77685|132~ CLM*1000*0.00***12>B>1*N*A*Y*I~ CN1*05~... (5 Replies)
Discussion started by: ashokv3
5 Replies

9. Shell Programming and Scripting

Issue in awk parsing under while loop

Hi I am trying to parse a grep output using awk. It works fine individually and not working under the loop with variable name assigned. cat > file.txt dict=/dictr/abcd/d1/wq:/dictr/abcd/d2/wq:/dictr/abcd/d3/wq: sample tried code Nos=`grep -w "dict" file.txt | awk -F"=" '{print... (10 Replies)
Discussion started by: ananan
10 Replies

10. Shell Programming and Scripting

Parsing via sed issue

sorry I messed up the last post with too many mistakes and corrections so I closed it and opening a new one which should be clear to everyone .my apologies to the admins. I am using sun solaris and Linux , what I want is SED to print any string (or output it to a file preferably) that does... (2 Replies)
Discussion started by: boncuk
2 Replies

LEARN ABOUT MOJAVE

cr

cr(1)                                                         General Commands Manual                                                        cr(1)

NAME

       cr - converts text files between nix EOL and dos EOL

SYNOPSIS

       cr  - | +  <input file> <output file>

DESCRIPTION

       Text  files,  such  as tle files, that come from a dos source usualy have the ^M symbol at the end of every line. Cr converts files between
       the dos newline format and the normal *nix newline format by stripping the ^M to convert dos to *nix, using the '-' option, or adding ^M to
       a *nix file to create the proper dos file when the '+' option is used.

       Although this extra character is not often a problem, programs like seesat5, which are data driven will encounter parsing problems when the
       extra character is present. It is these problems that cr is intended to repair.

   Options
       - | +  One or the other of these options is required. The '-' option is used to remove ^M from all newlines found in the dos file. The  '+'
              option is used to add ^M to every newline found in a *nix file.

       input file
              Fully delineated path to the input file. As this program is used in the dos environment as well, standard input is not used.

       output file
              Fully delineated path to the output file. As this program is used in the dos environment as well, standart output is not used.

SEE ALSO

       seesat5(1), seesat5(7), SEESAT5.INI(5), tle(5)

BUGS

       Cr  is  not an inteligent program. It methodicaly replaces/removes the offending character when it finds it in the correct context. Newline
       sequences found in contexts other than 'newline' will be replaced/removed just like those found in the proper  context.  Passing  a  binary
       file through cr is not advised, for this reason. Send all inqueries to Dale Scheetz <dwarf@polaris.net>.

Debian Linux                                                        2 April 96                                                               cr(1)
All times are GMT -4. The time now is 06:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy