Service Group Definition and Customization Guide

10.5 HotFix 1
- 10.5 HotFix 3
- 10.5 HotFix 2
- 10.5
- 10.2 HotFix 1
- 10.2
- 10.1 HotFix 1
- 10.1
- 10.0 HotFix 1
- 10.0

Back Next

Example 11

An example on usage of

CCVALIDATE

keyword.

Nameset Definitions and output:


FORMATTING-OPTIONS-24=3
NAME-FORMAT=RIGHT
*CODEKEYS,CODEPREFIX=91,TRANSPOSEKEYS,CCVALIDATE,MINCODELEN=10,MAXCODELEN=16,NOSTAB,NM3KEYSIZE=

Input 1:
4417 1234 5678 9111083

Output:
KEYS:
 1 210C3D27E8B7204000000000 NC
 2 2D4F29992B47200000000000 NC
 3 210C3D27E8B720C000000000 NC
 4 2D4F29992B44B00000000000 NC

Input 2:
4417 1234 5678 9113

Output:
KEYS:
 1 210C3D27E8B720C000000000 NC
 2 2D4F29992B44B00000000000 NC

The extra 3 digits in the end are not generally exposed and it is very unlikely to be found in any credit card numbers. But in case if it is available one can use the

FORMATTING-OPTIONS #24

to remove the trailing numbers. This information is provided as an example usage of

FORMATTING-OPTIONS #24

The difference in Input 1 and Input 2. The Input 1 credit card number is invalid and it will fail Luhn validation. The valid one is Input 2. The keys of 3 and 4 of Input 1 is same as 1 and 2 of Input 2. So if and only if the credit card number check digit calculation fails, the extra keys will be generated for the valid credit card number if the

CCVALIDATE

keyword is specified.

This keyword can be used for exhaustive key generation.

For information on

CCVALIDATE

keyword, refer table

NAMESET Code Key Building Keywords

given above.

NAMESET

function parameter which contains only the characters

uses the following default values:

*FINE,CASCADE*