[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

1620.0. "GETEVENT response event_report argument ID ?" by KETJE::PACCO (To manage you have to be a (manag..) skilled person!) Tue Oct 08 1991 18:13

    As from several sources, it seems that the argument ID of the
    event_report in the response to a GETEVENT directive MUST BE 1
    in order for the call to succeed.
    
    Is this a temorary restriction ?  The SRM does not enforce this.
    
    Dominique.

T.R Title User Personal
Name Date Lines

1620.1 *NOT* temporary -- getevent; chapter 15 TOOK::CALLANDER MCC = My Constant Companion Wed Oct 23 1991 19:56 10

T.R	Title	User	Personal Name	Date	Lines
1620.1	NOT temporary -- getevent; chapter 15	TOOK::CALLANDER	MCC = My Constant Companion	`Wed Oct 23 1991 19:56`	10
	The new registry procedures will now REQUIRE adherence to the chapter 15 definitions of common directives, of which getevent is one. Also the mcc_interface_def files will now include all of the codes for the responses/exceptions/args... of the common directives. These must be the same everywhere if the generic FM modules are to be able to work. If you have questions on this please post them and I will explain what I can. jill

The new registry procedures will now REQUIRE adherence to the chapter
15 definitions of common directives, of which getevent is one. Also the
mcc_interface_def files will now include all of the codes for the
responses/exceptions/args... of the common directives. These must be
the same everywhere if the generic FM modules are to be able to work.

If you have questions on this please post them and I will explain what I 
can.

jill