Conference azur::mcc

    Chris,
    
    What has been qared in 41 (maybe you reference the wrong one) is a
    bridge problem. What you have here is what looks to be a trm, ptb or
    dictionary problem. What I need to know from you, before it can be
    qared, is where does it fail. You state that placing an underscore
    between the multikeyword record elements fixes your problem, but where
    did the problem occur. 
    
    Were you able to get MSL and DAP to accept the names with the spaces,
    but the TRM failed when trying to set the elements? 
    
    One more thing that would be helpful is to know what version of the MCC
    software you are using. My guess is that this restriction still
    exists in the EFT kit; I checked the current MS files in use and
    none of them use multikeyword tags inside a record definition.
    
    jill
     
    
    

Jill,

    Apologies for not being more precise.   The problem is with the MSL 
translator.  The following log of a session demonstrates the problem, and gives
the version number you require.

    Cheers,

Chris
--
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: TYPE  was not parsed by the MSL Translator.

 Text: MessageIdentifier = 11 RECORD  was not parsed by the MSL Translator.

 Text: Country = 1 : Latin1String  was not parsed by the MSL Translator.

 Text: Admininstration Domain = 2 : Latin1String  was not parsed by the MSL Tran
slator.

 Text: Private Domain = 3 : Latin1String  was not parsed by the MSL Translator.

 Text: Local Identifier = 4 : Latin1String  was not parsed by the MSL Translator
.

 Text: END RECORD  was not parsed by the MSL Translator.

mrtie:3� ty t.err
  Errors in MS file(s):
Line #: Text
-----------------------------------------
4: TYPE
5: MessageIdentifier = 11 RECORD
6: Country = 1 : Latin1String
7: Admininstration Domain = 2 : Latin1String
8: Private Domain = 3 : Latin1String
9: Local Identifier = 4 : Latin1String
10: END RECORD
mrtie:3� ty t.ms
MANAGEMENT SPECIFICATION NCL$MTA;
   VERSION = X1.0.0;
   SYMBOL-PREFIX = NCL_;
   (* Description: This is the Management Specification of the Message
                   Transfer Agent, a module of the NODE global entity. *)

   TYPE
      MessageIdentifier = 11 RECORD
          Country = 1 : Latin1String;
          Admininstration Domain = 2 : Latin1String;
          Private Domain = 3 : Latin1String;
          Local Identifier = 4 : Latin1String;
      END RECORD;

END SPECIFICATION NCL$MTA;
mrtie:3� ddel t.ms;
%DELETE-I-FILDEL, USER1:[MELLING.MTA]T.MS;3 deleted (3 blocks)
mrtie:3� ty t.ms
MANAGEMENT SPECIFICATION NCL$MTA;
   VERSION = X1.0.0;
   SYMBOL-PREFIX = NCL_;
   (* Description: This is the Management Specification of the Message
                   Transfer Agent, a module of the NODE global entity. *)

   TYPE
      MessageIdentifier = 11 RECORD
          Country = 1 : Latin1String;
          Admininstration_Domain = 2 : Latin1String;
          Private_Domain = 3 : Latin1String;
          Local_Identifier = 4 : Latin1String;
      END RECORD;

END SPECIFICATION NCL$MTA;
mrtie:3� mccmsl
MCC Management Specification Language Translation Tool
               Version T1.1.0

MSL File: t
Languages:cc
Scan of MS file has completed successfully.
mrtie:3�

    
    Thanks for the additional information Chris. I have passed this
    along to the developer and we should have an answer soon as to if
    and/or when this will be corrected. For now I would suggest using
    and underscore between the mulitple keywords.
    
    Sorry for any inconvenience this caused in finding it.
    
    jill