RE: Replacing packed fields in record

[<Rick.Chevalier@xxxxxxxxxxxxxxx>]

I did try that yesterday but I couldn't get it to produce a satisfactory
file.  I don't use the command much so it probably has something to do
with my lack of knowledge about how it works.

I think Chuck has hit on the most pressing issue, the records that don't
fit the pattern.  I'm leaning heavily towards a SQL solution but I will
need to resolve the non-conforming record issue first.

The packed fields don't have to be replaced with blanks, just handled in
a way that the UNIX system can handle them.  The values aren't required
by the data warehouse group so preserving the data isn't a concern.  At
least not yet.

Rick 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Tuesday, March 04, 2008 3:35 PM
To: Midrange Systems Technical Discussion
Subject: Re: Replacing packed fields in record

Why not just use CPYTOIMPF?

I mean, that won't replace the packed data with blanks -- but it WILL
replace the packed data with character data that will be readable by the
Unix box. (That's assuming that the file is externally defined...)

Another way to omit the packed fields is to run a simple SQL statement
or create a logical file that only contains the fields you need.  Again,
that wouldn't insert blanks, it'd just omit the ones you don't need...

I wonder why you'd want to replace it with blanks?

Privileged and Confidential.  This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information.  If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail.  You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.