[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

1474.0. "INSTANCE parameter for the MCC_AES_GET call?" by SWORD1::ES (Eugene Shvartsman) Mon Sep 09 1991 21:56

How should I set up the 'instance' parameter on the call to the MCC_AES_GET,
i.e which fields of the MCC_T_Descriptor should I fill up?

Which fields of this descriptor will be set on the return from the call?
What should I expect in the buffer pointed by the mcc_a_pointer field?

Thank you
Gene
T.RTitleUserPersonal
Name
DateLines
1474.1aes_get instance descriptorTOOK::CALLANDERJill Callander DTN 226-5316Fri Sep 20 1991 11:5410
null the a_link.

define the a_pointer, and maxstrlen

set the curlen to 0

As long as those are defined I have found no problems in calling the
get.  Remember if you don't want a particular piece of information
(say the class) then simply pass in a null pointer for the argument.
1474.2TOOK::SWISTJim Swist LKG2-2/T2 DTN 226-7102Fri Sep 20 1991 11:5913
    Not quite right.
    
    If using a static descriptor (DSC_K_CLASS_S), set the class, pointer,
    and maxstrlen.   MCC will set the idcode, datatype, and current length.
    
    If using a dynamic descriptor (DSC_K_CLASS_D), set the class and zero
    the pointer and maxstrlen.  The buffer will get allocated for you and
    both curlen and maxstrlen will be set to its size.
    
    (You can make subsequent calls using the dynamic class without touching
    anything - the buffer size will be adjusted in each case (if necessary)
    to accomodate the length of the instance value).
    
1474.3dynamics in v1.2TOOK::CALLANDERMCC = My Constant CompanionWed Sep 25 1991 18:387
V11 does not fully support dynamic descritpors. 

If you are coding to V1.1 you want to allow for
dynamic descriptors, but not all routines will automatically
allocate the additional space. You will have to check for
insufbuf and allocate the additional memory yourself. In
v1.2 this is changing.
1474.4TOOK::SWISTJim Swist LKG2-2/T2 DTN 226-7102Wed Sep 25 1991 19:523
    I was only refering to the operation of mcc_aes_get, and not to
    descriptors in general.