From:	SMTP%"gavron@ACES.COM" 31-AUG-1993 12:24:30.28
To:	EVERHART
CC:	
Subj:	Re: How does SORT parse many /KEY qualifiers?

X-Newsgroups: comp.os.vms
Subject: Re: How does SORT parse many /KEY qualifiers?
Message-ID: <30AUG199320015857@spades.aces.com>
From: gavron@spades.aces.com (Ehud Gavron)
Date: 30 Aug 1993 20:01 MST
Reply-To: gavron@ACES.COM
Distribution: world
Organization: ACES Research Inc.
NNTP-Posting-Host: alpha.sunquest.com
News-Software: VAX/VMS VNEWS 1.41    
Lines: 39
To: Info-VAX@KL.SRI.COM
X-Gateway-Source-Info: USENET

In article <1993Aug31.105630.45@iwsd01.itwol.bhp.com.au>, webosk@itwol.bhp.com.au (Ken Bosward) writes...
#How is it possible to parse multiple occurrences of the same qualifier
#on the command line? For example, the SORT utility allows more than one
#/KEY qualifier. But when I call CLI$GET_VALUE, I can only ever get the
#rightmost occurrence of a qualifier. I used VERB on the SORT command and
#got the following:
# 
#   define verb SORT
#      [...]
#      qualifier KEY
#         value (required,list,type=SORT_KEY)
#      [...]
#   define type SORT_KEY
#      keyword POSITION
#         value (required,type=$number)
#      keyword SIZE
#         value (required,type=$number)
#      keyword NUMBER
#         value (required,type=$number)
#      [...]
# 
#There isn't anything special about this definition, so what sort of
#fiddle does SORT do to get more than one /KEY qualifier?

	Use CLI$NEXT_QUAL and move through the entire line.
	Use CLI$GET_VALUE for every entity_desc returned.
	Utility manual, CLI-9, 10, and CLI$NEXT_QUAL is not
	documented :)

#-- 
#Ken Bosward, BHP Information Technology, Wollongong. Australia.
#E-mail: webosk@itwol.bhp.com.au

Ehud

--
Ehud Gavron        (EG76)     
gavron@aces.com
Yow!  Is my fallout shelter termite proof?