Re: Model numbers that can/cannot have LPAR 0

["Mark S. Waterbury" <mark.s.waterbury@xxxxxxx>]

James:

In my opinion, this problem is intractable -- as long as you rely on 
manually entered data, and verify it only on your machine, there is 
really no way that you can ever be 100% sure of the results, because if 
someone (on their end or yours) makes any mistakes, these errors may 
well come up with a combination (of feature code and model, etc.) that 
IS valid ... :-o

SUGGESTION: supply a small simple-to-use "free" program your prospects 
can download from your company web-site, that gathers the information 
you need (model, feature code, processor group, etc.) and puts this into 
some kind of a "coded number" (with check-digits or check-sums) so that 
if they read it to you over the phone, and digits are dropped or 
misstated or transposed, etc., your check-digits or check-sums can 
detect this when you try to key in this "magic number" on your end, to 
generate license codes.

Mark S. Waterbury

> James Lampert wrote:
> rob@xxxxxxxxx wrote:
>   
> > You really need to look at the 
> > detail provided by the other poster that uses the APIs.
> >     
>
> HOW MANY TIMES DO I HAVE TO EXPLAIN THAT THIS IS TO VALIDATE 
> MANUALLY-ENTERED DATA? THE AUTHORIZATION CODE GENERATOR RUNS ON OUR BOX, 
> AND DOES NOT HAVE ANY WAY TO ACCESS THE CUSTOMER'S BOX!
>
>