RE: Replacing packed fields in record

Chuck,

You are correct that the iSeries is an intermediary. As I understand
it, there are big $ involved in having the data sent to us in the format
we need. The packed data is not needed. It is a flat file that
originates in EBCDIC from the vendor and our data warehouse system is
ASCII (Unix) and can't do the translation (or so I'm told). We have a
utility called Informatica that they use to pull files from the iSeries
but it apparently doesn't handle packed fields either, at least not the
release we have.

I'm about to use an SQL update statement on it. The problem with that
is every few records there is one that doesn't fit the pattern. No one
can tell me why or what the data is supposed to be. Doing a blanket
update will certainly trash those records but leaving them alone will
allow packed fields in the transfer which brings me full circle.

HTH,

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Tuesday, March 04, 2008 10:45 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Replacing packed fields in record

To give a good answer, requires knowing more about the file [a
database file?] and its packed data, how the file and that data needs to
be used [as a database file with the packed data column?], how the data
gets into the DW, and where the DW resides [presumably on an ASCII
system?].

If the file is only getting to the i5/OS system as an intermediary,
such that the data is unused except to transform for a push to the DW,
then the best option is to have the data properly exported from the
vendor and eliminate the intermediate step. If the file needs to be
used for its packed data when it arrives from the vendor, then changing
the data in the file would not be best. Copying of data is not ideal,
for its CPU & storage requirements, and thus possibly just a logical
view of the existing data is best. But each /if/ is an unknown for the
scenario, requiring more details.

Regards, Chuck
--
All comments provided "as is" with no warranties of any kind
whatsoever and may not represent positions, strategies, nor views of my
employer

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.