[Info-vax] SET SHADOW SYNTAX

[VAXman- at SendSpamHere.ORG]

In article <j7n2bh$2qb$1 at usenet01.boi.hp.com>, "Robert A. Brooks" <rab at aitchpee.com> writes:
>On 10/18/2011 4:35 PM, Phillip Helbig---undress to reply wrote:
>> Normally, single parameters after "=" are OK, but more than one give
>>
>>     %DCL-W-PARMDEL, invalid parameter delimiter - check use of special characters
>>
>> with the complaint about the first character after "=" being an invalid
>> delimiter.  The solution is to enclose the list in parentheses.
>> However, as long as there is only one parameter per "=", everything is
>> OK, e.g. $ DIR/SEL=SIZ=MIN=1000.  SET SHADOW seems to obey these rules,
>> but $ SET SHADOW/POLICY=HBMM=MASTER_LIST=* doesn't; one has to specify
>> $ SET SHADOW/POLICY=HBMM=(MASTER_LIST=*).  Why is this?
>
>I don't know; I didn't work on the command parsing.  It's troublesome to 
>me that this requirement is not explicitly called out in the help,
>and the examples listed are somewhat misleading if that is a requirement.
>
>It may be a weird artifact of using LIB$TABLE_PARSE, but that is just a 
>hand-waving guess.

Better than a hand-waving guess, I took a look at the Bliss STATE and TRAN
definitions in SETSHOSHADOW.REQ.  I'd have to conclude that it isn't due to
the finite state parsing syntax enforced in this code.

!
! TPARSE tables to parse the 'xyz' in /POLICY=HBMM=xyz
!
$INIT_STATE(HBMM_STB, HBMM_KTB);
:
:
!**************************************************************
! MASTER_LIST=name
! MASTER_LIST=*
! MASTER_LIST=(*)
! MASTER_LIST=(name)
! MASTER_LIST=(name,name,...)    i.e. comma separated list of names


But, instead, from this:

SET.CLD:

define type shadow_policy
        keyword hbmm            value(type=$PARENTHESIZED_VALUE)

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.