Conference azur::mcc

    Chris, I will check this out for you. But, the following information
    would make my checking a bit easier.
    
    product release you are running:
    
    		release printed by MSL:
    		release printed by DAP:
    		release printed by PTB:
    		release printed by TRM:
    
    Also the segment from the .MS input file that is causing the problem.
    
    thanks
    jill
    

OK .. here you go ...

mrtie:3� mccmsl
MCC Management Specification Language Translation Tool
               Version T1.1.0

MSL File:

mrtie:3� dap

        DECmcc Dictionary Administrator Program   Version T1.1.0

DAP>

mrtie:3� mcc/mod=mcc$ptb
Using default file names: MCC$PTB_COMMAND.LOG
                          MCC$SYSTEM:MCC$PTB_PARSER.DAT
MCC Parse Table Builder
Component Version: T1.1.0

And here's a cut down MSL file which demonstrates the problem:

MANAGEMENT SPECIFICATION NCL$MTA;
   VERSION = X1.0.0;
   SYMBOL-PREFIX = NCL_;


   TYPE
      DSIEF = 4 (
	  Message Originator = 0,
	  Message DL Expansion History = 1, 
	  Message Recipient Information = 2, 
	  Message Recipient Redirection History = 3, 
	  Message Flags = 4, 
	  Message External Trace Information = 5, 
	  Message Internal Trace Information = 6, 
	  Message Priority = 7, 
	  Message Content Type = 8, 
	  Message EITs = 9, 
	  Message Size = 10, 
	  Report Subject Identifier = 11, 
	  Reported Originator and DL Expansion History = 12, 
	  Report Destination Name = 13, 
	  Reported Actual and Intended Recipient = 14, 
	  Report External Trace Information = 15, 
	  Report Internal Trace Information = 16, 
	  Report Size = 17, 
	  Agent = 18 ); 

   TYPE
      DeliverySubmissionImportExportFilter = 5 SET OF DSIEF;

SUBORDINATE ENTITY MTA = 50 :
   SUPERIOR = ( NODE ),
   IDENTIFIER = ( ),
   DYNAMIC = TRUE,
   SYMBOL = CLASS_MTA,

   CHARACTERISTIC ATTRIBUTES

         ATTRIBUTE Accounting Delivery Filter = 25 : DeliverySubmissionImportExportFilter
	 (* This is the filter which determines what accounting data gets logged
	    at delivery time. *)
	    ACCESS = SETTABLE,
	    DISPLAY = TRUE,
	    DEFAULT = "( Message Originator,
			Message Recipient Information,
			Message Priority,
		        Message Size,
			Reported Originator and DL Expansion History,
			Report Destination Name,
			Reported Actual and Intended Recipient,
			Report Size,
			Agent )",
	    SYMBOL = MTA_ACC_DELIVERY_FILTER,
	    CATEGORIES = ( CONFIGURATION, ACCOUNTING )
	 END ATTRIBUTE Accounting Delivery Filter;

   END ATTRIBUTES; (* CHARACTERISTIC *)

END ENTITY MTA;

END SPECIFICATION NCL$MTA;

If you comment out the DEFAULT statement then the above compiles successfully.
As it is, is doesn't:

mrtie:3� mccmsl
MCC Management Specification Language Translation Tool
               Version T1.1.0

MSL File: t
Languages:cc
Scan of MS file has completed with errors, check error file.
 Text: ATTRIBUTE Accounting Delivery Filter = 25 : DeliverySubmissionImportExpor
tFilter  was not parsed by the MSL Translator.

 Text: ACCESS = SETTABLE ,  was not parsed by the MSL Translator.

 Text: DISPLAY = TRUE ,  was not parsed by the MSL Translator.

 Text: DEFAULT = " ( Message Originator ,  was not parsed by the MSL Translator.

 Text: Message Recipient Information ,  was not parsed by the MSL Translator.

 Text: Message Priority ,  was not parsed by the MSL Translator.

 Text: Message Size ,  was not parsed by the MSL Translator.

 Text: Reported Originator and DL Expansion History ,  was not parsed by the MSL
 Translator.

 Text: Report Destination Name ,  was not parsed by the MSL Translator.

 Text: Reported Actual and Intended Recipient ,  was not parsed by the MSL Trans
lator.

 Text: Report Size ,  was not parsed by the MSL Translator.

 Text: Agent ) " ,  was not parsed by the MSL Translator.

 Text: SYMBOL = MTA_ACC_DELIVERY_FILTER ,  was not parsed by the MSL Translator.

 Text: CATEGORIES = ( CONFIGURATION , ACCOUNTING )  was not parsed by the MSL Tr
anslator.

 Text: END ATTRIBUTE Accounting Delivery Filter  was not parsed by the MSL Trans
lator.

mrtie:3� ty t.err
  Errors in MS file(s):
Line #: Text
-----------------------------------------
13: ATTRIBUTE Accounting Delivery Filter = 25 : DeliverySubmissionImportExportFi
lter
15: ACCESS = SETTABLE ,
16: DISPLAY = TRUE ,
17: DEFAULT = " ( Message Originator ,
18: Message Recipient Information ,
19: Message Priority ,
20: Message Size ,
21: Reported Originator and DL Expansion History ,
22: Report Destination Name ,
23: Reported Actual and Intended Recipient ,
24: Report Size ,
25: Agent ) " ,
26: SYMBOL = MTA_ACC_DELIVERY_FILTER ,
27: CATEGORIES = ( CONFIGURATION , ACCOUNTING )
28: END ATTRIBUTE Accounting Delivery Filter
mrtie:3�

Hope this helps find the problem,

Chris

             
    Sorry for the delay, the DEFAULT clause in MSL presently does not
    allow the '(', ')' and ',' characters. This will be fixed! for EFT
    update.

Thanks.

Chris

    Chris,
    
    Also note that you are running the October 1989 release of the toolkit.
    Since then there has been a new release of the end user kit, which
    includes updates of all the tools. You might want to consider doing
    an upgrade to take advantage of a number of improvements. One of
    them being a drastic speed up in both PTB and the base system.
    
    Another thing I want you to note is that you are running the toolkit
    T1.1.0, there will also be an end user kit T1.1.0 coming out in
    the not to distant future. Just wanted you to be aware of the fact
    that both kits  use the same numbering scheme.
    
    jill
    

Thanks for the information.  I was/am confused by the numbering and naming 
scheme.  I had assumed that the developers kit numbered T1.1.0 which I had
was more up to date (and different) to the user kit T1.0.0.  Clearly I was 
wrong.

It seems that now you've only got one kit in the kit area now anyway (which is
the T1.0.0 user kit.

Maybe you could outline the kit naming and numbering scheme for the future? 
Will there continue to be only one kit, or two, and how are they different?

Thanks,

Confused of Reading.

    I will get the official write up, there is one floating around some
    where. The end user kit includes both the tools (as you knew them
    from the earlier toolkit releases) and the end user modules.
    
    Since the tools are needed as part of the enrollment/installation
    of new modules they are always part of the kit. As you  noted since
    one is a subset of the other, there is currently only one kit
    available, and this is the end users T1.0.0 kit. Everyone should
    be upgraded to this kit for both end users and developers.
    
    jill