The decoding is not to complex, split the string into 4 parts (3 for the WMI, 5 for the VDS, an extra checkdigit, and the last 8 for the VIS) Now each of those parts need to point to several tables with countries, manufacturers and types for the WMI. The same must be done for the VDS and the VIS.
So it's more a matter of creating tables.
Frank
prod: WF 7.6.10 platform Windows, databases: msSQL2000, msSQL2005, RMS, Oracle, Sybase,IE7 test: WF 7.6.10 on the same platform and databases,IE7
October 09, 2008, 05:15 PM
Tony A
Use Google search on "VIN CALCULATION" to find some good sources such as the "How Things Work" site.
T
In FOCUS since 1986
WebFOCUS Server 8.2.01M, thru 8.2.07 on Windows Svr 2008 R2
WebFOCUS App Studio 8.2.06 standalone on Windows 10
October 13, 2008, 08:08 AM
Bruce C. Litzkow
I already have the specifications for how to calculate the VIN# check digit. I'm merely looking for ready to use code that will run on mainframe FOCUS, ZOS, FOCUS Rel 7.0.9. All I need the code to do is validate the check digit. As it turns out, after I made the original post I wrote a set of code in a series of DEFINEs in about an hour. Now I'm mostly curious about how best to package the code to maximize flexibility of use. Thanks all for your input.
October 13, 2008, 09:20 AM
nubi
if its for data validation we tend to set ours up as a caster job-
i guess its a case of how you want it to work-
because our main ERP has no validation we check the data each night and email users who have made a mistake automatically
depends how your system work- if all the submitted VIN numbers are on their way to a database this may be a good way of catching them before they go in...
Developer Studio 7.64 Win XP Output: mostly HTML, also Excel and PDF
"Never attribute to malice that which can be adequately explained by stupidity." - Heinlein's Razor