In a fixed length structure, the number of digits in the field of a
person’s card must match the number of digits in each field of the
structure you define. For example, if your facility’s code (site code)
is 75 (encoded on the second and third digits on your card) and your
cards use up to 4 digits for the card number (encoded on the fourth
through seventh digits) you would configure the
CustomABAFormat string as follows:
T112222...
When the cards are encoded, any card with a number less than 4
digits must be padded to 4 digits. For example, a card with card
number 12 must be encoded with 0012 in the card number field.
z
In a fixed-length structure, you must use a field separator (S) to
correspond with every place it appears in the person’s card. For
example, if the card contains four field separators, your structure
must have four separators that must appear in the same location
specified by the CustomABAFormat string. If the card has no
separators, your structure should have no separators.’
z
A variable-length structure can accommodate cards containing
fields whose digits vary in length. If the number of digits in a field
on a person’s card is less than the number of corresponding digits in
your structure, then CyberStation pads that number with zeros.
For example, if a person’s site code is 75, the card number is 1234,
and your structure is V11111S222222, then these numbers become:
00075
001234
In a variable-length structure, you must use a field separator (S) to
separate the fields. The card must be encoded with a field separator
to indicate to CyberStation where each field ends, as follows:
SS74FS1234FS.....ESLRC
(For the purpose of this illustration, SS is the start sentinel, FS is
the field separator, and ES is the end sentinel.)
z
In any structure, the not-used character (X) should correspond with
digits that are not used on the card (see example on the previous
page).
z
Any ASCII character, other than A, B, C, D, E, F, L, R, S, T, V, X,
and Z, is invalid.
