[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

830.0. "Port efforts..." by SUOSW4::HARDT (Daniel Hardt,EIS/Germany,765-5286) Fri Mar 22 1991 14:35

    Is it possible now (a few months before DECmcc Ultrix is launching) to
    qualify the effort for porting a customer/partner written AM from
    DECmcc VMS V1.1 to DECmcc Ultrix V1.2. Not in terms of how long (man
    days) that takes, but in terms of "what has to be changed ?"
    
    This is really important for us, because we are dealing with "unix
    shops" who have to start today with their AM development work.
    
    Tks & Rgds.
T.RTitleUserPersonal
Name
DateLines
830.1not as bad as it soundsTOOK::CALLANDERSat Mar 23 1991 16:4022
    I am not an Ultirx wizard so I hope Jim S will chime in here, but I can
    tell you this.
    
    The length of time will be directlry proportional to the following
    items:
    	- coding conventions (good style)
    	- use of VMS services
    	- size of AM
    
    The hardest to port was the VMs specific services, like the use of SMG
    in the FCL PM forms mode (which we still don'ty have working). As to
    the majority of the rest of it an awful lot of it was simply getting to
    the code to compile on ultrix (VMS compile standard=portable will
    give you an idea as to where you stand right now).
    
    Overall the modules porting now that more of the base system functions
    are working are finding the task a lot easier. If you are in-house and
    doing the port you might want to talk to Jim Swist for his helpful
    programming hints (a number of memos he has writen on the subject).
    
    jill
    
830.2good news ?SUOSW4::HARDTDaniel Hardt,EIS/Germany,765-5286Mon Mar 25 1991 08:278
    If i understand Jill correctly then portability can be guaranteed by
    
    - good coding behaviour (ANSI C ?)
    - eliminating VMS specifics as far as possible (?)
    
    Regarding the 2nd i have the impression that everything (also qio's)
    is captured by MCC$call routines and the Ultrix toolkit might offer the
    same layer, so it would not be necessary to use VMS vehicles ??!