Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!mordor!sri-spam!nike!ucbcad!ucbvax!UW-JUNE.ARPA!js
From: js@UW-JUNE.ARPA (A. K. Ulgai)
Newsgroups: mod.computers.vax
Subject: CLD question answered. undocumented CLI$NEXT_QUAL
Message-ID: <8608282308.AA23388@uw-june.arpa>
Date: Thu, 28-Aug-86 19:08:25 EDT
Article-I.D.: uw-june.8608282308.AA23388
Posted: Thu Aug 28 19:08:25 1986
Date-Received: Fri, 29-Aug-86 05:40:54 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 29
Approved: info-vax@sri-kl.arpa


	Sorry, I don't know how to retract an article, so, since I answered
my own question I thought I'd post the answer and see if anybody has a better
idea. As a reminder, I wanted to parse a command such as -
	SORT/KEY=(POS:10,SIZ:20)/KEY=(POS:1,SIZ:9)

	It turns out I need to do the following:
	(pretend theres error checking)

	status=cli$present('KEY')
	status=cli$next_qual('KEY')	! undocumented routine
loop:	! this loop pulls apart each /KEY qualifier
	! i.e. for above example, it returns POS:10 and SIZ:20 the first
	! two times through
	status=cli$get_value('KEY',qualval)
	if status then goto loop

	! this moves it to the next /KEY qualifier or returns an error
	status=cli$next_qual('KEY')
	if status then goto loop


	Of course, I hate using undocumented routines, esp. when I just wildly
	guess at how to use it until I get a configuration that works, so
	if anyone from DEC cares to enlighten me as to its status I'll be
	happy to heed their advice..

	Thanks and cheers,
	Joe Meadows Jr.		js@uw-june.arpa