|
if your transaction is a financial tran, especially credit cards & banking, the check digit is standard. Just be aware some routines are "home grown", others are more standard. If it's credit card "lrc" let me know, I have the rpg code (which came from this list several years ago). Watch out for things like a valid "blank" in the last character of the string. Don't cat the check digit to the last non blank character. Took 2 months of live operation before that happened and tran rejected. jim franz ----- Original Message ----- From: "DeLong, Eric" <EDeLong@Sallybeauty.com> To: <rpg400-l@midrange.com> Sent: Tuesday, January 29, 2002 5:28 PM Subject: Sockets client in RPGIV > Group, > > I got a q+d project this morning to write a socket client app. The > programmer at the other end wants to include a check digit to validate the > record before processing. I always thought TCP handled all data validation, > eliminating the need to add this layer of validation. He claims that bad > data and/or garbled records will still sometimes be returned to the > application, making this additional testing and process control necessary. > I have doubts. Can anyone confirm that this is necessary, or even useful? > TIA. > > Eric DeLong > Sally Beauty Company > MIS-Sr. Programmer/Analyst > 940-898-7863 or ext. 1863 > > > > _______________________________________________ > This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list > To post a message email: RPG400-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l > or email: RPG400-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. >
As an Amazon Associate we earn from qualifying purchases.
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.