Conference azur::mcc

21.0. "PROBLEM - Request ID not found in a IN_P argument." by KETJE::PACCO () Fri Oct 13 1989 16:57

First a case study of a correct ILV.
SHOW TIMER xxx all CHAR	...	gives SECONDS back in OUT_P argument
The dump is the following.
[   0 ] (
     )
[   105 ] (
     [   104 ] (
          [   2 ] (
               [   1 ]		26  --  &
               [   2 ]		00
               [   3 ]		00
               )
          )
     )
Everything seems O.K.
[ 105 ] = SERV_SHOW_SUCCESS	return code
[ 104 ] = SERV_SHOW_RESP 	attribute list argument
[ 2 ] = SECONDS			attribute

Now the problem case.
When I execute from the TRM presentation module the command :
	SET TIMER xxx SECONDS 100
In the TIMER access module the following ILV structure is found
for the IN_P argument:
[   0 ] (
     [   1 ] (
          [   2 ] (
               [   1 ]		26  --  &
               [   2 ]		64  --  d
               [   3 ]		00
               )
          )
     )


Question.
I wonder why the ILV Id's are [ 0 ] and [ 1 ].
I had expected [ 0 ] and [ 100 ]
	[ 0 ] beeing a non defined variable.
	[ 100 ] beeing SERV_SET_REQ

What is wrong, my mind or the data ?

I add here also an extract from the MSL.

Regards,
Dominique.

GLOBAL ENTITY Timer = 107 :
...
  CHARACTERISTIC ATTRIBUTES
    ATTRIBUTE Seconds = 2 : Counter32
      ACCESS = SETABLE,
      DISPLAY = TRUE,
      UNITS = Seconds,
      CATEGORIES = (CONFIGURATION),
      SYMBOL = TIMER_SECONDS
      END ATTRIBUTE Seconds ;

    DIRECTIVE Show = 1 :
      DIRECTIVE-TYPE = EXAMINE,
      CATEGORIES = (CONFIGURATION),
      REQUEST
      ARGUMENT Show Req Attributes = 103 : Attrib_List
        ECHO = TRUE,
        DISPLAY = TRUE,
        DEFAULT = "All Identifiers",
        SYMBOL = SERV_SHOW_REQ
        END ARGUMENT Show Req Attributes;
      END REQUEST ;
    RESPONSE Success =  105 :
      SYMBOL = SERV_SHOW_SUCCESS,
      TEXT = "Timer AM SHOW Success Response ",
      ARGUMENT Show Resp Attributes = 104 : Attrib_List
        SYMBOL = SERV_SHOW_RESP
        END ARGUMENT Show Resp Attributes;
      END RESPONSE Success;
    END DIRECTIVE Show;

    DIRECTIVE Set = 2 :
      DIRECTIVE-TYPE = MODIFY,
      CATEGORIES = (CONFIGURATION),
      REQUEST
         ARGUMENT Set Req Attributes = 100 : Attrib_List
          ECHO = TRUE,
          DISPLAY = TRUE,
          SYMBOL = SERV_SET_REQ
          END ARGUMENT Set Req Attributes;
        END REQUEST ;
      RESPONSE Success =  102 :
        SYMBOL = SERV_SET_SUCCESS,
        TEXT = "Timer AM Success Response ",
        ARGUMENT Set Resp Attributes = 101 : Attrib_List
          SYMBOL = SERV_SET_RESP
          END ARGUMENT Set Resp Attributes;
        END RESPONSE Success;
      END DIRECTIVE Set;

    END ENTITY Timer ;
  END SPECIFICATION;

    Yes, you're correct.  The code is supposed to be 100.  At the time
    of changeover to attribute lists, this must have slipped past us.
    We are currently always encoding the value of "1" for a SET argument, 
    since there is only 1 request argument allowed for SETs.
    
    The proper SET request argument code will be used in a future
    baselevel.
    
    Christine

    
    This will be entered in the QAR system, and listed as a known bug
    in the release notes until corrected.