Table of Contents

Search

  1. Preface
  2. Introduction
  3. Definition File Overview
  4. Customization Steps
  5. Service Group Definition
  6. Algorithm Definition
  7. Edit-list Definition
  8. Matching Scheme Definition

Service Group Definition and Customization Guide

Service Group Definition and Customization Guide

Service Function Definition Structure and Format

Service Function Definition Structure and Format

Functions defined at the Service Group level must be added immediately after the
SCHEME-DEFINITIONS=
option, or
PASSING-WORKAREA-SIZE
option if that is being used, for example,
... SCHEME-DEFINITIONS=N3MAUS PASSING-WORKAREA-SIZE * FUNCTION-DEFINITIONS ...
The format of the Service Function Definitions is as follows (note the alternate spelling for this directive):
FUNCTION-DEFINITIONS FUNCTIONS-DEFINITION [name]:[keyword],...[keyword] [name]:[keyword],...[keyword]
where,
[name]
is the function name, any combination of up to 32 valid characters and
[keyword],...
is any number of comma-separated keywords, as defined in the next chapter, up to a total of 1022 characters. As many functions as required can be defined in the one
FUNCTIONS-DEFINITION
block. For example:
FUNCTIONS-DEFINITION CUST_LOOKUP:NWORD,SECONDARY,COARSE,STOP=WI CUST_INSERT:NEG,START=WW CUST_FRAUD:NEG,START=WI,PROBESWORD SCORE:SCORE-ONLY
A function definition can also span several lines. This allows long descriptions to be defined without exceeding the 80 or 72 character limit common on many systems. The above definition for
CUST_LOOKUP
could be written as follows:
CUST_LOOKUP:NWORD, SECONDARY, COARSE, TOP=WI
The commas that usually separate options must remain at the end of each continuing line, the first line without this comma at the end will terminate the definition.

Keyword Types

There are two types of Function definition keywords:
Keywords
Description
FLAG
These are used to select an option, for example,
NEG
enables the NAMESET code that allows full word ranges. A flag can also be used to turn off an option,
-NEG
will disable the option.
The following keywords cannot be turned off in this manner:
FINE, WORDS, COARSE, PROTECTED, FILESIZE=, BASE=, START=, STOP=
FINE
,
WORDS
and
COARSE
override each other, and therefore one can be used to turn off the other.
VALUE
Some options are not simple on/off switches, they require a value. Value keywords perform this function, the syntax is as follows:
[keyword]=[value]
for example,
START=WW
specifies that a NAMESET Search-table should start at the two-word level.

Keyword Precedence Issues

Keywords are processed in order of appearance (left to right) in the function, this means that an option can be overridden by another further to the right. For example a description similar to the following,
.....NOSTAB,......-NOSTAB
will have no net result. This is not a problem in a simple description but can become one when the
BASE=
keyword is used, for example:
BASE=AFUNC,NOSTAB
is a valid construct that reads the description for
AFUNC
then applies the
NOSTAB
option to stop the generation of a Search-table. However, the description,
NOSTAB,BASE=AFUNC
may or may not have the desired affect depending on the options specified in the description for
AFUNC
. If, for example,
AFUNC
was defined as,
NEG,START=WI,-NOSTAB
the
-NOSTAB
option would overwrite the previous
NOSTAB
and there would be no obvious reason for the resultant "invalid" behavior of the Service.

0 COMMENTS

We’d like to hear from you!