× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Rick,

I'd create a PF with the correct format, packed fields and all. Then an LF with all the packed fields
unpacked.

You'd receive the file into the PF and the DW system would read the LF.

Thus, you have a solution that can provide the values from the packed data if it's ever needed.

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Rick.Chevalier@xxxxxxxxxxxxxxx
Sent: Tuesday, March 04, 2008 2:15 PM
To: midrange-l@xxxxxxxxxxxx
Subject: 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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.