| 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 |
I'm getting the following DAP error message. Can someone please explain? It would seem to be pretty intuitive, but I've searched the MSL and can't find any multiply defined directives with different request arguments. Am I looking for the right thing? Where would this message be documented? Thanks. -------------------------------------------------------------------------------- DAP> LOAD FROM SRC$:MLM_BLS.COM Percent of file processed = 35% Percent of file processed = 75% p Percent of file processed = 100% Now writing processed records to dictionary file... (Control C and Y will be disabled while records are being written) Using parse table log file: wrk$root:[com]mcc_fdictionary.log;2 Reading parse table file: wrk$root:[com]mcc_fdictionary.bpt;3 Please wait while parse tables are updated Processing entity 1 65 Processing entity 1 65 22 %MCCPTB-W-DIFFREQARG, Same verb string defined with different request argument. %MCCPTB-W-DIFFREQARG, Same verb string defined with different request argument. Processing entity 1 65 23 %MCCPTB-W-DIFFREQARG, Same verb string defined with different request argument. %MCCPTB-W-DIFFREQARG, Same verb string defined with different request argument. Processing entity 1 65 59 %MCCPTB-W-DIFFREQARG, Same verb string defined with different request argument. %MCCPTB-W-DIFFREQARG, Same verb string defined with different request argument. %MCCPTB-I-NOENTRY, No dictionary entries found. No attributes defined for entity class. Writing parse table file. Please wait... Created parse table file: wrk$root:[com]mcc_fdictionary.bpt;4
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3800.1 | check SRM CH 15 for common directives | KAJUN::NELSON | Fri Sep 25 1992 09:56 | 36 | |
Hmmmm, All of the verbs (directives) within the DECmcc system are registered. Each verb has a unique code. SHOW = 1, SET = 2, TEST = 3, ... The dictionary (parse table) processing will catch any non-matching codes for the same verb string. The parse table builder that runs on DAP exit expects directives to be defined in a similar fashion. This goes for new directives that you are adding, as well as the already registered ones. BTW - if you are adding directives - get them registered. In addition, each of the verbs defined to be "common directives" have a minimum set of requests, responses, and exceptions already defined and registered. This helps the generic management modules make sense of replies. The dictionary will also catch non-standard request and reply codes. You can add additional requests, replies, and reply arguments. The rule for common directives is as follows: You don't have to implement the directive. However, if you do implement the directive, you must implement at least the minimum subset specified by the SRM. Check in Chapter 15 of the SRM to see the definitions for the common directives. Each one has the the proper constants for the verb, request, reply, and any reply arguments specified. Each of these constants should be defined in . on VMS - SYS$LIBRARY:mcc_vea_def.h or SYS$LIBRARY:mcc_interface_def.h . on ULTRIX - /usr/include/mcc_vea_def.h or /usr/include/mcc_interface_def.h If you are not lucky today, and the constant you need doesn't happen to be in the include files, check the Sample AM, Example FM, or YOURMM MS files. They all are using the proper, registered codes for everything, I hope. ...kjn | |||||