Re: IBM response on my CPYFRMIMPF request

Your search/replace is including the quotes.  The / is the delimiter between 
parms.  Google sed for details.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787  F: +1-312-601-1782
Sent from my Treo SmartPhone

--- Original Message ---
From: "Steve Landess" <sjl_abc@xxxxxxxxxxx>
Sent: Thu 10/7/2004 8:28
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Cc: "John.Jones@xxxxxxxxxx" <John.Jones@xxxxxxxxxx>
Subject: Re: IBM response on my CPYFRMIMPF request

> John Jones wrote:
> Subject: RE: IBM response on my CPYFRMIMPF request
> Before you CPYFRMIMPF, could you QSH CMD('sed s/","/~,~/g
> <srcpath/srcfile >targetpath/targetfile') to replace the "," with ~,~
> (note: syntax not checked but should be pretty close)?  Maybe a Unix
> guru can chime in here but that should use the Stream EDitor to
> Substitute the / delimited "," with the / delimited ~/~ Globally (all
> occurrences on each line).

John -

What if you have a comma embedded within the field data?  This is one of the
major reasons for using a delimiter on alphanumeric fields, since otherwise
the comma would be seen as the start of a new field.

Example:
"Billy Bob", "123 Main Street","Austin, Texas"

BTW, I haven't yet found a way when exporting data from Excel to create a
CSV with " as the delimiter to protect against this situation.

Steve Landess
Austin, Texas
(512) 423-0935







This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.