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 |
My customer is beginning to write a new specific AM, and he's starting the design of the entity model. He asked me how he could chose entity codes in his MSL, that will not conflict with codes used by existing AMs. Can someone tell me the procedure to follow ? Thanks. Michel.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3962.1 | The DECmcc registry: | TEMTY::L_GROSSMAN | Mon Oct 26 1992 12:50 | 7 | |
To register MSLs or if you have any questions please send mail to DSSR::MCC. You will need to send mail to find out how customers should do this, and please create a reply. | |||||
3962.2 | documentation pointers | TOOK::KOHLS | Ruth Kohls | Tue Oct 27 1992 11:05 | 18 |
The customer can Start from the v1.2 SRM, section 7.4, and the v1.2 version of "Management Module Programming", section 2.9. Right now in the Entity Space, only Global Entity Codes are required to be unique, and they MUST be obtained from the registry, and as early in the development process as possible. A Global Entity Code conflict leaking out can cause considerable work, as we discovered with the first field test versions of the Data Collector. In the Verb space, the customer must use the same Verb words and verb codes as everyone else to take advantage of DECmcc integration. The Registry will assign new verb codes to new verbs, and resolve conflicts with existing verbs and codes. Chapter 15 of the SRM has standard verb definitions. Additional verbs and their specifications are in the various Module Reference Manuals (MRMs). Ruth K. |