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 Definitions Not Requiring an Algorithm

Service Definitions Not Requiring an Algorithm

An example is as provided below.
* SERVICE-DEFINITION NAME=MATCH TYPE=MATCH ALGORITHM= * SERVICE-DEFINITION NAME=DEBUG TYPE=DEBUG ALGORITHM= * SERVICE-DEFINITION NAME=BROWSE TYPE=BROWSE ALGORITHM= * SERVICE-DEFINITION NAME=INFO TYPE=INFO ALGORITHM= *
The Service Definition has the following format:
SERVICE-DEFINITION NAME=Service Name TYPE=Service Type ALGORITHM= SERVICE-DEFINITION
A Service definition starts with this identifying line,
NAME=Service Name
Specifies a user-definable name of the service. As there is only one definition required for each of these Services, it is recommended that a Service’s type also be used as its Name. The name may also be user-defined and if so, can consist of any valid characters so long as it is no longer than eight characters or delimited with asterisks, in which case 32 characters are allowed. This Service name is passed as a parameter by an application in a Call to the Service Group, e.g.:
CALL ’N3SGPR’ USING ’MATCH ’ ... NAME=Service Type
The valid types for Services not requiring an Algorithm are:
MATCH
,
BROWSE
,
INFO
and
DEBUG
.
Even though these Services do not require an Algorithm, the
Algorithm Name
parameter is still required, left blank.

0 COMMENTS

We’d like to hear from you!