Functions and CALL Routines |
Requirement: | If specified, the locale must be loaded into memory as part of the locale list. |
Valid in: | DATA step, PROC SQL, and SCL |
Syntax | |
Arguments | |
Example | |
See Also |
Syntax |
DQMATCHPARSED (parsed-char, 'match-definition' <,sensitivity> <,'locale'>) |
specifies the name of the match definition. The definition must exist in the locale that is used.
specifies a character constant, variable, or expression that contains the value that is the name of the parsed-definition that is associated with the match definition.
To determine the name of the associated parse definition, use the DQMATCHINFOGET function. To determine the tokens that are enabled by that parse definition, use the DQPARSEINFOGET function.
specifies an integer value that determines the amount of information in the returned match code. Valid values range from 50 to 95. The default value is 85. A higher sensitivity value inserts more information in the match code. In general, higher sensitivity values result in a greater number of clusters, with fewer members per cluster; input values must be more similar to receive the same match codes.
specifies a character constant, variable, or expression that contains the locale name.
Default: | The default locale is the first locale in the locale list. If no value is specified, the default locale is used. |
Example |
The following example returns a match code for the parsed name of an individual. The amount of information in the match code is high.
data _null_; length nameIndividual matchCode $ 20 parsedName $ 200; nameIndividual='Susan B. Anthony'; parsedName=dqParse(nameIndividual, 'name', 'enusa'); matchCode=dqMatchParsed(parsedName, 'name', 90, 'enusa'); run;
See Also |
Functions: |
Copyright © 2010 by SAS Institute Inc., Cary, NC, USA. All rights reserved.