This concept is not all that different than what some crafty Oracle and
Sybase(ptooey) DBA's have attempted to do in the past(Prior to Oracle
gateways). Early versions of some gateways on the AS400 worked this way
as well. With regards to speed and flexibility when you look at the
"cost" of storage and integration there are some real savings, IF the
database procedures are written properly. However, there are even
better cost savings when the task of migrating large amounts of data
from a "staging" environment to an application. The greatest draw back
of this approach is when there are lots of little files and the I/O
gets crunched. So having a concept of number of records and a whole
transaction is key in developing this type of solution. The other thing
that is key is having the logs report in a format that makes a 997
feasible and reportable.

I have set up a similar system Each "map" if you will was a call to a business 
rule table placing a field mapped to another field there by forcing all the 
logic to be carried out by a stored procedure on the database. Which is 
normally a whole lot larger machine than a desktop trying to parse data. 

Before embarking on this endeavor I would carefully examine how much data you 
are going to want to throw at your application per cycle.

John

----- Original Message ----
From: John Kaess <[EMAIL PROTECTED]>
To: Ozzie Laakso <[EMAIL PROTECTED]>; [email protected]; "Becker, Adam" 
<[EMAIL PROTECTED]>
Sent: Tuesday, December 5, 2006 6:24:02 PM
Subject: Re: [EDI-L] Application File Formats

Have you ever thought about storing the date in EDI standards format since
we are discussing EDI on this list?  I am including an individual on this
reply that did this on a main frame back in the early 1980's.  It one get
program and one put program in CICS and another pair of get and put programs
for batch.  The entire concept is the same as using the EDI standards.  The
get programs put the data into the format the application programs were
looking for based on whatever version was on the file.  The put program
after using or modifying the data put it away using the most current
version.  This had cost saving benefits including space saving (smaller
files), being upgraded to most current standards version when being accessed
and only requiring a few programs to be modified when standards
modifications are made.

        John D. Kaess

P.S.  Ozzie: I hope you did not mind my letting others know of your
accomplishments.



...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links










 
____________________________________________________________________________________
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail beta.
http://new.mail.yahoo.com

[Non-text portions of this message have been removed]



...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix. 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 

Reply via email to