[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

951.0. "How to add a reference attribute to a class" by STRASB::EBLE () Wed Apr 24 1991 13:31

	Hi,

	I try to augment the global entity class node4 to add a reference 
attribute. So I write a MSL procedure with the new attribute "Numero de 
serie". Then I create the DAP command file doing MANAGE/TOOL/SPECIF/AUGMENT
/TRANSLATE. Then under DAP I do AUGMENT CLASS NODE4 FROM file. 
Then I rebuild the parse table. It works. After this I try to use enter a 
Numero de serie for an existing node4 entity( SET NODE4 CHNA01 NUMERO DE SERIE
XX ). I have the following error message :
	 MCC_W_ATTRUNKNOWN, unknown attribute NUMERO

Then I try to do that from the ICONIC MAP and it works !!! The result of a show
is :

Node4 chna01 
AT 24-APR-1991 17:16:10 References

Examination of Attributes shows:
                    Implementation Desc = ""
                               Location = ""
                           MAIL Account = ""
                        Numero de serie = "XX-ZZ"
                           Phone Number = ""
                                Remarks = ""
                     Responsible Person = "M Jean-Marc Moser"
                              Text File = ""

So the main question is : how could I get the right reference attribute name 
to enter a Show or a set under the FCL interface ??? Another question is where 
could I find a "cookbook" of how to augment the the references attributes ?

Francois EBLE
EIS Strasbourg

Ps : I have just put after a copy of the MSL file.    

(*
  ENVIRONMENT:
    VAX/VMS
    Management Specification Language (MSL) Translator
 
  AUTHOR:
	EBLE
 *)

MANAGEMENT SPECIFICATION AUGMENT_NODE4;
    VERSION = V1.1.0;
    SYMBOL-PREFIX = MCC_;


     (* Begin Global Entity NODE4 definition *)
     
GLOBAL ENTITY Node4 = 12 :

	REFERENCE ATTRIBUTES		

	(* Entity's physical location. *)
		
	ATTRIBUTE Location = 300 : Latin1String
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = REPTR_LOCATION
	END ATTRIBUTE Location;

	(* product/version ID information not in characteristics *)
	
	ATTRIBUTE Implementation Desc = 301 : Latin1String
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = REPTR_IMPLEMENTATION
	END ATTRIBUTE Implementation Desc;
	

	(* who ya gonna call? *)

	ATTRIBUTE Responsible Person = 302 : Latin1String
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = REPTR_PERSON
	END ATTRIBUTE Responsible Person;
	

	(* Responsible person phone number *)
		
	ATTRIBUTE Phone Number = 303 : Latin1String
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = REPTR_PHONE
	END ATTRIBUTE Phone Number;
	

	(* Computer Mail address *)
		
	ATTRIBUTE MAIL Account = 304 : Latin1String
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = REPTR_MAIL_ACCT	   
	END ATTRIBUTE MAIL Account;
	

	(* Remarks *)
		
	ATTRIBUTE Remarks = 305 : Latin1String
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = REPTR_REMARKS	   
	END ATTRIBUTE Remarks;
	
	(* Num�ro de s�rie. *)
		
	ATTRIBUTE Numero de serie = 10000 : Latin1String
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = SERIAL_NUMBER
	END ATTRIBUTE Numero de serie;

	(* Pointer to text file. *)
		
	ATTRIBUTE Text File = 306 : FileSpec
	   ACCESS = SETTABLE,
	   DISPLAY = TRUE,
	   CATEGORIES = (CONFIGURATION),
	   SYMBOL = REPTR_TEXT	   
	END ATTRIBUTE Text File;

	END ATTRIBUTES; (* REFERENCE *)



END ENTITY Node4;

END SPECIFICATION; (* AUGMENT_NODE4 *)

T.R	Title	User	Personal Name	Date	Lines
951.1	put the new parse tables in mcc_system	TOOK::CALLANDER		`Wed Apr 24 1991 14:45`	6
	The difference between the PMs is that the iconic map goes in this instance to the dictionary, where the FCL uses the parse tables. My guess is you rebuilt the tables but didn't copy them to the mcc_system directory. Please remember also that mcc_system is a search list and will be searched according to the ordering listed, frist found is the one used.
951.2	Another idea please ...	STRASB::MOSER	Jean-Marc MOSER -- Strasbourg @ZTO	`Thu Apr 25 1991 10:06`	10
	Hello, We copy the MCC_PTB_PARSER.DAt from SYS$LOGIN directory to the MCC_SYSTEM directory who is the same as MCC_COMMON. The sympton explained in the first note remains...... Another idea ??? Regards
951.3	Wrong file	TOOK::GUERTIN	I do this for a living -- really	`Thu Apr 25 1991 10:39`	4
	The file is supposed to be MCC_PTB_PARSER.BPT not .DAT ! ^^^ -Matt.
951.4	It works but ...	STRASB::EBLE		`Fri Apr 26 1991 05:26`	9
	Thanks for your answer it was really this MCC_PTB_PARSER.BPT that was not copied in the MCC_SYSTEM directory. Now all is working. But I have still a question about that. Is there a way to add a reference attribute to an existing global entity without having to redefine in the MSL file all the already existing reference attributes ? Is there a full documentation about MSL ? Regards.
951.5	SRM contains MSL documentation	TOOK::CALLANDER		`Thu May 02 1991 12:05`	4
	Without modifying the dictionary and parse tables to know about the new attributes you will not be able to use them. MSL it self is documented in the system reference manual, with additional information in the toolkit documentation, toolkit reference manual.
951.6	Where are the MSL sources	STRASB::EBLE		`Tue May 14 1991 04:55`	10
	Thanks, but where is it possible to find this SRM manual ? Our customer asked us to modify all the references attributes of the access modules. For the NODE4, NODE5, Ethernet and Bridge access module I could not find the MSL source files. They are not in the BMS kit. Is it possible to get them mainly to be sure that for each symbol we use we define the right code number and not an already existing one. For the TCPIP access module the MSL sources are provided. We need a very quick answer.
951.7		BSYBEE::EGOLF	John C. Egolf LKG2-2/T02 x226-7874	`Tue May 14 1991 08:25`	11
	RE .0 >>> Thanks, but where is it possible to find this SRM manual ? Our See note 5.26 for the bookreader version. Order number AA-PD5LA-TE Vol 1 AA-PE55A-TE VOL 2 JCE
951.8	how to do it wothout msl source	TOOK::CALLANDER		`Wed May 15 1991 15:12`	16
	I hope you got the mail I sent you off line for updating the node4 info you sent me. If not please contact me and I will send it again In general you don't need the source to create the procedures you are looking for. The reference attributes for ALL classes are supposed to be the same, if not the registration process should be kicking them out. To find out what they are you can use dap and do a show command. This will list you all of information for a specific entity class. Next to each attribute you will find the associated code. You now need to delete the existing attributes, and then write a small msl file to "AUGMENT CLASS xxx", to get your new stuff in there. You should be able to write one msl that you can use to augment each class you want updated, and reissue the augment command for each of the classes to be modified. If you need more assistance please call.
951.9	re:.8	BARREL::LEMMON		`Tue May 21 1991 18:08`	12
	>> The reference attributes for ALL classes are supposed to >> be the same, if not the registration process should be kicking them out. Jill, I don't think the above is true. Last I heard the Registration FM only requires the datatype of reference attributes to be latin1string. It doesn't do any validation. At one time it was discussed that the reference attributes would be architected, but this never happened. It appears this way because we all used the same .MS include file to save time. /Jim
951.10	paper process...I will check	TOOK::CALLANDER		`Tue May 21 1991 18:51`	7
	Jim, I didn't mean the registration FM, as you stated it doesn't care at all. But, I was under the impression that (and I will check with Steve when he gets back) that the registration process (the paper one) would be checking for consistency; maybe I was just confused with the partition codes and names having to be consistent only.