[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

2144.0. "Q/A: "PM-like" applications on Ultrix?" by MCDOUG::MCPHERSON (Scientific progress goes 'Boink!') Mon Jan 20 1992 15:06

================================================================================
Note 99.0              Q: "PM-like" application on Ultrix?               1 reply
TOOK::MCPHERSON "Scientific progress goes 'Boink!'"  11 lines  20-JAN-1992 09:21
--------------------------------------------------------------------------------
    On *ULTRIX*, what specifically must an application developer do to be
    able to use mcc_call_function() and mcc_call_access() from a program
    _external_ to DECmcc (i.e. not an enrolled module.) ?

    I understand what is required on VMS, but I don't know about ULTRIX
    because of the different execution model...
    
    /doug



================================================================================
Note 99.1              Q: "PM-like" application on Ultrix?                1 of 1
TOOK::SWIST "Jim Swist LKG2-2/T2 DTN 226-7102"       23 lines  20-JAN-1992 14:55
--------------------------------------------------------------------------------
    You only need to do a couple of things:
    
    1)  Put "mcc_fw_init();"  (mcc kernel init) *IMMEDIATELY* after your
    main() entry point (Don't even try a printf before doing this).
    
    2) Define a dummy routine mcc_xmm_log() {return;}  (It will never
    get called but will link undefined if you don't put it in).
    
    3) Follow the linking instructions that come with the toolkit, except
    instead of using mcc_mmshell_unix.o (Which is the "main" for a regular
    management module), use your own main routine.   You will need all
    those libraries (cma, dtss, etc).
    
    4) You may bump into CMA if you do your own signal handling - in
    particular sigvtalrm.  
    
    5) You must include mcc_interface_def.h in all of your (non-MCC)
    modules.  This will make sure that all non-reentrant C library routines
    are appropriately mutex-jacketed.
    
    6) Your process will be killed if someone issues an mcc_kill command
    running under your UID.  Let me know offline if this is a problem
    and I'll find a workaround.
T.RTitleUserPersonal
Name
DateLines
2144.1Already documentedDFLAT::PLOUFFEJerryTue Jan 21 1992 09:146
Doug:

  This information is documented in MM Programming p. 4-14 (section 4.9) 
  "Using a Callable DECmcc".

                                                                  - Jerry