[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

1024.0. "Is text substitutions for enumeration datatype supported?" by PHONE::ALLAIN () Thu May 16 1991 15:58

Hi,

I've read the note 513 and replies .6, .7. I'd like to know if text substitions 
for enumeration datatype is supported now?

I'd like to use it for an event report as argument of an event.

Francois
T.RTitleUserPersonal
Name		DateLines
1024.1one down another to goTOOK::CALLANDERThu May 16 1991 16:2913
    
    Isn't it always true, you fix one thing and someone wants another....
    
    The enumeration problems from not 513.6 and 7 have been corrected,
    but...the V1.1 kit does not handle event report arguments from the
    notification services (when requested using the NOTIFY command), though
    you shouldn't have a problem with the GETEVENT command. The NOTIFY
    command problem (we simply didn't write the code to accept arguments)
    has now been corrected and should be available in the next major
    baselevel.
    
    jill
1024.2Sorry for the troubles...PHONE::ALLAINThu May 16 1991 17:0889
1024.3ilv encoding of the event reportTOOK::CALLANDERThu May 16 1991 18:2536
ILV dump of OUT_P:

[  1 ] (
    [  1 ] (
        [  69 ] (
            [  0 ]             09
            )
        )
   

        EVENT PARTITION FRANCOIS EVENTS = 15 :
                SYMBOL = PRT_FRANCOIS_EVENTS,
                EVENT Bip = 69 :
                        DISPLAY = TRUE,
                        SYMBOL = CMEAGT_BIP,
                        TEXT = " BIP Event Argument:  !<Trigger Param>. ",
                        ARGUMENT Trigger Param = 01 : totrigEnum
                                DISPLAY = TRUE,
                                SYMBOL = BIP_EVENT_ARG
                        END ARGUMENT Trigger Param;
                END EVENT Bip; 


You will notice in the ilv encoding that [0] is supplied for the argument
to the event report (code 69), and that "Trigger Param" is defined as
code 1. My guess at looking at this is that that is what is causing your
problem.

The only other question I have is why did you make the event report an FAO type 
argument on the getevent response? Chapter 15 (SRM pg 884) gives the architected
(generic) way in which the common directives should be modeled. The SRM shows
the response as having no reply text, with a single argument of datatype
event_report.

jill
1024.4It's me again...PHONE::ALLAINThu May 16 1991 18:5339
1024.5event report as FAO argTOOK::CALLANDERThu May 16 1991 21:4215
It looks like (you are now getting a data type error) that the error is due 
to the fact that you have the event report as an `fao' argument to the
reply text. Try removing that and see what happens.

$MANAGE/TOOL/DICT
DAP> use class code 1001 subclass code 1017 directive getevent exception code 1
DAP> set definition code 19 TYPE T COUNT 1 LENGTH 19 -
_DAP>  VALUE "Getevent Successful"
DAP> exit

^^^^ I know this is quick and dirty but it will simply remove the argument
substitution. You DON"T need to rebuild the parse tables or anything else
to test this change.

jill
1024.6event report as FAO argPHONE::ALLAINFri May 17 1991 12:125
You're right, it's ok now.

I've removed the Fao argument and it works fine. Thanks a lot for your help.

Francois.