Bill,
Ah, yes, big fish are always eating the littler fish and now Fidelity is
swallowing Metavante another big fish...
Between my first email and this one, I was notified of a new vendor who
is getting ready to come online with us (IS/IT always the last to know)
and they have a "scubbed" FRB compatible test deck they'll be sending me
as an X9.37 file. When I get it and verify it really is scrubbed perhaps
I can pass it on to you. I haven't talked to their CIO yet so it may be
a week or two out, but it that fits your timeframe, let me know.
Coy Krill
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Blalock, Bill
Sent: Wednesday, 27 May, 2009 1:27 PM
To: Java Programming on and around the iSeries / AS400
Subject: RE: Experience working with Check 21 file format X9.37
Hi Coy!
I'd venture to guess your internal imaging folks (by your email
address,
I can only assume you work for Fidelity) already have some good X9.37
test files that you could borrow since they can be a pain to create.
You would think! But you know that old saying about left and right
hands! Actually I work for a company that was bought by a company that
was bought by a company that was bought by Fidelity.
X9.37 is a standard with many implementation specific nuances.
Yes, the revisions are scary. I wrote to X9 and this is part of the
reply I received..
" The "Draft Standard for Trial Use" or DSTU never became an industry
standard and was withdrawn, although the "historical document is
available my understanding is that the industry does not want to see any
future development with the withdrawn standard. Anyone requesting it
should do it only for reference purposes and new development should be
according to ANS X9.100-187 and appropriate industry application aids
for guidance on implementation(i.e., Universal Companion Document). "
Maybe this will come back to visit you someday.
Bill Blalock
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Coy Krill
Sent: Wednesday, May 27, 2009 2:40 PM
To: Java Programming on and around the iSeries / AS400
Subject: RE: Experience working with Check 21 file format X9.37
Bill,
I'd venture to guess your internal imaging folks (by your email address,
I can only assume you work for Fidelity) already have some good X9.37
test files that you could borrow since they can be a pain to create. Our
original test files with the Fed and bogus data passed fine, but once we
sent tests with live data, those had to be tuned in. I don't remember
all the issues as that was 2005, but I do know we have to have separate
import/export parameters for both the Fed files and the RDC files we
receive from ProfitStars. X9.37 is a standard with many implementation
specific nuances.
And for the record, we don't process them on our AS/400, it's handled by
Metavante ImageVision which I believe is what your outsourced item
processing people are also using.
Coy Krill
Whidbey Island Bank
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Blalock, Bill
Sent: Tuesday, 26 May, 2009 12:04 PM
To: Java Programming on and around the iSeries / AS400
Subject: Experience working with Check 21 file format X9.37
Hi all:
My manager asked me to look into importing check data and images, for
Check 21, from files in the X9.37-2003 format.
I've have some PDFs which explain the file format layout but I haven't
found any example or test files that I can compare the documentation to.
Any suggestions where I can find sample or test files? Would you happen
to have one you could share (has to be a safe, clean file - no
confidential information)?
My boss is hard core RPG'r and wants this done in RPG. Personally I
think it is more suitable for Java (or C shudders). Does anyone have
any experience either way?
Thanks
Bill Blalock
_____________
The information contained in this message is proprietary and/or
confidential. If you are not the
intended recipient, please: (i) delete the message and all copies; (ii)
do not disclose,
distribute or use the message in any manner; and (iii) notify the sender
immediately. In addition,
please be aware that any message addressed to our domain is subject to
archiving and review by
persons other than the intended recipient. Thank you.
_____________
midrange.com
