Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!UKANVAX.BITNET!SLOANE
From: SLOANE@UKANVAX.BITNET (BOB)
Newsgroups: comp.os.vms
Subject: Re: Contemplations on CDU
Message-ID: <8706060828.AA10670@ucbvax.Berkeley.EDU>
Date: Thu, 4-Jun-87 17:40:00 EDT
Article-I.D.: ucbvax.8706060828.AA10670
Posted: Thu Jun  4 17:40:00 1987
Date-Received: Wed, 10-Jun-87 02:45:54 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 29

Erland Sommarskog, ENEA Data, Stockholm gives the following CLD example:

   Define type DESCRIPTION_WORDS
       Keyword HEADER  default, nonnegatable, value(default=0)
       Keyword FOOT    default, nonnegatable, value(default=0)
       Keyword PAGE    default, nonnegatable, value(default=0)
   ...
   Qualifier DESCRIPTION
             Default,
             Nonnegatable,
             Value(Required, List, Type = DESCRIPTION_WORDS)

and comments that CLI$GET_VALUE returns a null string for FOOT when
/DESC=HEAD:5 is entered.

It seems to me that HEADER, FOOT and PAGE are VALUES that the /DESC
qualifier can have.  As such, I doubt that the DESC qualifier should
take on more than one value by default.  What you really have is 3
different qualifiers here, not just one qualifier that can take different
values.  Users not only have to remember the FOOT, HEADER, and PAGE values
but also the /DESC Qualifier.  If I were using a program with this syntax
I would rather just remember 3 things, not 4. It seems to me that the DESC
qualifier is redundant and could be eliminated.

                      Bob Sloane
                      University of Kansas
                      Computer Center
                      (913) 864-4291
                      SLOANE@UKANVAX on BITNET