[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

4500.0. "mcc_desframe.a has changed in T1.3.1 ?" by TAEC::WEBER () Thu Feb 04 1993 09:02

       Hello,
    
    When verifying the mcc_desframe.a of Toolkit T1.3.1,
    we identified differences with the one of V1.2.3.
    Are these changes documented somewhere ?
    This is important to customers who use the design framework.

    Thanks to answer
    Florence

T.RTitleUserPersonal
Name
DateLines
4500.1Changes were made, but they are backward compatibleMOLAR::ROBERTSKeith Roberts - Network Management ApplicationsFri Feb 05 1993 08:0938
RE: .0

>    When verifying the mcc_desframe.a of Toolkit T1.3.1,
>    we identified differences with the one of V1.2.3.
>    Are these changes documented somewhere ?
>    This is important to customers who use the design framework.

  Florence,

  There were a number of internal changes made to the Toolkit Design 
  Framework library - however these changes are backward compatible
  with earlier versions of the library and should present no problems
  for existing Management Modules ... Please let us know if this is
  not the case.

  The primary change was to provide a c++ like interface to hide
  the DECmcc Call Protocol stuff; Init-handle-first, etc... routines have
  been hidden.  The Design Framework required a lot of extra baggage to
  be included in each Management Module directive - using the new routine
  interface the YOURMM module has been reduced size by 60%.

  Also - the User-friendly MIR interface routines presented in the Example
  FM code were incorporated into the Design Framework - with a few bug
  fixes and enhancements.

     Q: Why are you asking in the Notes file and not
        reading the Documentation ?

     A: Because it isn't documented 8(

  These changes were left over from v1.2 development and were added to the
  v1.3 release as they are backward compatible.  There was (vitually) no
  funding for the V1.3 Toolkit so the Documentation phase was not done.

  It may be possible to provide you with examples of using the new interface
  routines as the Script AM is based on the new code.

  /keith
4500.2TAEC::WEBERMon Feb 08 1993 11:3979
    

    Well, I'am glad to see that eng=hancements are there.
    However, it might be compatible but it is not automatic.
    If I list the two libraries they are ovbiously different.
    Should the current code be modified? and modified to what ?
    To avoid problems, what happend is the we renamed the V1.3.1 library
    in order to re-use the V1.2.3 one.

    Any guidelines welcome
    Thanks in davance from TeMIP customers.
    Florence
    

nm mcc_desframe.a V1.2.3

00000020 N exc_e_SIGEMT
00000020 N exc_e_SIGIOT
00000020 N exc_e_SIGTRAP
00000070 T mcc_desframe_alloc
00000860 T mcc_desframe_append_error
00000214 T mcc_desframe_create_descriptor
0000018c T mcc_desframe_free_alloc_list
00000000 T mcc_desframe_init_alloc_list
00002adc T mcc_desframe_package_call_args
000004d8 T mcc_desframe_set_cvr_and_reply
000009f0 T mcc_desframe_validate_callargs
000013f8 T validate_time_now

nm mcc_desframe.a V1.3.1

00000020 N exc_e_SIGEMT
00000020 N exc_e_SIGIOT
00000020 N exc_e_SIGTRAP
00000070 T mccdfw_alloc
0000087c T mccdfw_append_error
00002b64 T mccdfw_call_begin
00002f8c T mccdfw_call_done
00000214 T mccdfw_create_descriptor
0000018c T mccdfw_free_alloc_list
00004d8c T mccdfw_ilv_begin_attr_list_read
00004f74 T mccdfw_ilv_copy_attribute_list
00004e00 T mccdfw_ilv_merge_buffers
00000000 T mccdfw_init_alloc_list
00005240 T mccdfw_itt_add_thread
00005554 T mccdfw_itt_binreltim_to_ticks
000050c8 T mccdfw_itt_free
00005030 T mccdfw_itt_initialize
000053b4 T mccdfw_itt_remove_thread
0000517c T mccdfw_itt_shutdown
00005110 T mccdfw_itt_startup
000054dc T mccdfw_itt_thread_alerted
000046cc T mccdfw_mir_cancel
00004630 T mccdfw_mir_close
00004998 T mccdfw_mir_commit
00004158 T mccdfw_mir_create_attributes
0000355c T mccdfw_mir_create_instance
00003774 T mccdfw_mir_delete_instance
00003ee0 T mccdfw_mir_get_all_attributes
00003cc0 T mccdfw_mir_get_attribute
00004b84 T mccdfw_mir_get_time_stamp
00004ba8 T mccdfw_mir_next_instance
00004b98 T mccdfw_mir_next_time
0000325c T mccdfw_mir_open
00003ba0 T mccdfw_mir_put_attribute
0000391c T mccdfw_mir_select_instance
00004344 T mccdfw_mir_set_attributes
00004b68 T mccdfw_mir_set_time_range
00004b54 T mccdfw_mir_set_time_stamp
00002af8 T mccdfw_package_call_args
000057b4 T mccdfw_queue_initialize
000057c8 T mccdfw_queue_insert
00005818 T mccdfw_queue_remove
000058a4 T mccdfw_queue_walk
000004d8 T mccdfw_set_cvr_and_reply
0000563c T mccdfw_thread_terminator
00000a0c T mccdfw_validate_callargs
00001414 T validate_time_now

4500.3Ah - routine names have changed ... but ... macros should take care of itMOLAR::ROBERTSKeith Roberts - Network Management ApplicationsMon Feb 08 1993 13:4851
RE: .2

  These are the v1.2 --> v1.3 Design Framework routine name changes

> mcc_desframe.a V1.2.3
> 
> 00000070 T mcc_desframe_alloc
> 00000860 T mcc_desframe_append_error
> 00000214 T mcc_desframe_create_descriptor
> 0000018c T mcc_desframe_free_alloc_list
> 00000000 T mcc_desframe_init_alloc_list
> 00002adc T mcc_desframe_package_call_args
> 000004d8 T mcc_desframe_set_cvr_and_reply
> 000009f0 T mcc_desframe_validate_callargs
>
> mcc_desframe.a V1.3.1
>
> 00000070 T mccdfw_alloc
> 0000087c T mccdfw_append_error
> 00000214 T mccdfw_create_descriptor
> 0000018c T mccdfw_free_alloc_list
> 00000000 T mccdfw_init_alloc_list
> 00002af8 T mccdfw_package_call_args
> 000004d8 T mccdfw_set_cvr_and_reply
> 00000a0c T mccdfw_validate_callargs

  In the v1.3 'mcc_desframe.h' file, there are macros which convert the
  v1.2 naming to the v1.3 format.  Recompiling should take care of the
  naming changes.  Ofcourse, you can edit your source code to use the
  new names, but because we were unable to document the changes, the
  macros will take care of it automatically.

  Were there problems compiling the code ?

  /keith

/************************************************************************
 *                                                                      *
 *  Macro:  Backward compatibility macros for DECmcc Design Framework   *
 *          module naming conventions                                   *
 *                                                                      *
 ************************************************************************/

#define  mcc_desframe_init_alloc_list    mccdfw_init_alloc_list
#define  mcc_desframe_alloc              mccdfw_alloc
#define  mcc_desframe_free_alloc_list    mccdfw_free_alloc_list
#define  mcc_desframe_create_descriptor  mccdfw_create_descriptor
#define  mcc_desframe_set_cvr_and_reply  mccdfw_set_cvr_and_reply
#define  mcc_desframe_append_error       mccdfw_append_error
#define  mcc_desframe_validate_callargs  mccdfw_validate_callargs
#define  mcc_desframe_package_call_args  mccdfw_package_call_args