Conference azur::mcc

5358.0. "Inconsistent use of quotes in MCC command line parsing." by FORTY2::MARSHALL () Tue Jul 20 1993 07:43

The use of quotes in MCC, in quoting certain values, seems to be inconsistent.

For example in our entity we have an attribute called Presentation Address which
is defined as a Latin1String. The syntax enforced by our entity is such that
values like '"DSA"/"DSA"/"DSA"/NS+11223344,CLNS' are required.

If this attribute is a characteristic attribute of the DSA then the following
command succeeds :-


DECmcc (V1.3.0)

MCC> set node DEC:.reo.nodename dsa pres addr '"DSA"/"DSA"/"DSA"/NS+88776655,CLNS'

Node DEC:.reo.nodename DSA
AT 20-JUL-1993 11:27:40 Characteristics

Modifications completed successfully


However we have several sub-entities which contain a constructed characterictic
attribute contained the identical field. The definition of this attribute is :-                                       

 TYPE
   AccessPoint = 12 
    RECORD
     AE Title  = 0 : DirectoryName;
     Presentation Address  = 1 : PresentationAddress;
    END RECORD;

 TYPE AccessPointSet = 13 SET OF AccessPoint;

Where DirectoryName and PresentationAddress are both Latin1Strings.

Now the following command fails :-

MCC> create node DEC:.reo.nodename dsa naming context "/l=test" consumer access poi
nt={[ae title="/l=1234", presentation address='"DSA"/"DSA"/"DSA"/NS+88776655,CLN
S']}
%MCC-I-NOPARCMD, {[ae title="/l=1234", presentation address='"DSA"/"DSA"/"DSA"/
                 ^
%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
%MCC-E-LATIN1STRING_ER, error in Latin1String value

It works if I specify it as :-

MCC> create node DEC:.reo.nodename dsa naming context "/l=test" consumer access poi
nt={[ae title="/l=1234", presentation address="""DSA""/""DSA""/""DSA""/NS+887766
55,CLNS"]}

Node DEC:.reo.nodename DSA Naming Context "/l=test"
AT 20-JUL-1993 11:32:17

This Naming Context entity already exists.

QUESTION :-
===========
1) Why is the use of quotes inconsistent between the two examples? Using the "" 
   and """ is not very user friendly.
2) NCL will allow both examples to work correctly so surely MCC should aswell?

3) Why does the shrinking of the field names (presentaion address) cause 
   the following parse problems?
   Surely 4 characters is sufficient? NCL allows this without any problems.

MCC> create node DEC:.reo.nodename dsa naming context "/l=test" consumer access poi
nt={[ae title="/l=1234", presentation add="""DSA""/""DSA""/""DSA""/NS+88"]}

Node DEC:.reo.nodename DSA Naming Context "/l=test"
AT 20-JUL-1993 11:37:15

This Naming Context entity already exists.
MCC> create node DEC:.reo.nodename dsa naming context "/l=test" consumer access poi
nt={[ae title="/l=1234", presentatio add="""DSA""/""DSA""/""DSA""/NS+88"]}
%MCC-I-NOPARCMD, {[ae title="/l=1234", presentatio add="""DSA""/""DSA""/""DSA""
                 ^
%MCC-I-SYNTAXERR, Syntax error -- unable to interpret remainder of line
%MCC-E-RECORD_FIELD_NA, no such Record field name

MCC>


	Thanks in advance for any help

			Adrian.