[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

2221.0. "Going back to V1.1" by USWRSL::GIBEAU_LE (Les Gibeau, Network Consultant - DTN 521-3294) Wed Jan 29 1992 22:47

    I have installed DECmcc T1.2.4 and now want to go back to V1.1.  Has
    anyone had the opportunity to do this yet and was it a success?  Does
    anyone know of anything I should look out for or any reason why it
    shouldn't work.
    
    Thanks,
    Les
T.RTitleUserPersonal
Name
DateLines
2221.1It worked for me.ECRU::TAMERThu Jan 30 1992 01:427
Les,

I ported the AM that i am developing to T1.2.4 and then was able to run it
on V1.1.  This was done just in case we went to field test before V1.2 ships.
Note that the AM doesn't use threads or shared memory.

Phil  
2221.2Hope you're not using MCC_MUTEXCHRISB::BRIENENDECmcc Bridge|Station|SNMP Management.Thu Jan 30 1992 12:2210
RE. 2221.1

>I ported the AM that i am developing to T1.2.4 and then was able to run it
> on V1.1.

  That's great.

  If you're using the mcc_mutex routines, make sure they're ifdef'd
 for the datatype change that occurred between V1.1 and T1.2 (or
 you'll be clobbering memory)...
2221.3TOOK::MINTZErik Mintz, DECmcc DevelopmentThu Jan 30 1992 13:3110
My impression is that .0 wants to know if it is possible to 
install V1.1 on top of T1.2.4, to roll the whole platform back
to V1.1.  I do not know of any reason that would not work,
but also don't know of anyone who has done it yet.

Be sure ALL T1.2.4 processes are stopped (including batch jobs),
or event pool version mismatches will cause a problem.

-- Erik

2221.4Thanks but I don't use mcc_mutexECRU::TAMERSat Feb 01 1992 00:5121
 <<< Note 2221.2 by CHRISB::BRIENEN "DECmcc Bridge|Station|SNMP Management." >>>
                      -< Hope you're not using MCC_MUTEX >-

RE. 2221.1

>I ported the AM that i am developing to T1.2.4 and then was able to run it
> on V1.1.

>>  That's great.

>>  If you're using the mcc_mutex routines, make sure they're ifdef'd
>> for the datatype change that occurred between V1.1 and T1.2 (or
>> you'll be clobbering memory)...


	Thanks for the info Chris.

	I don't use mcc_mutex.  If I do, I will use your suggestion.


	Phil
2221.5Clean out T1.2.4 firstTOOK::R_SPENCENets don't fail me now...Mon Feb 03 1992 21:0110
    Ah well, I don't think it will work unless you clean up all the T1.2
    dictionary files (and for sure yuo can't use the local MIR).
    
    I don't know if there are any changes in the Alarms MIR files.
    
    I suggest you extract all your alarms (see the V1.1 release notes),
    and then delete the content of MCC_SYSTEM: and all the MCC_* files
    in SYS$LIBRARY and SYS$SYSTEM before you reinstall V1.1
    
    s/rob
2221.6RE-install OKUSWRSL::GIBEAU_LELes Gibeau, Network Consultant - DTN 521-3294Mon Feb 10 1992 15:589
    Sorry it took so long to tell you all how it worked but I just got back
    from Net. U.
    
    It turns out that re-installing V1.1 work OK, I just had to re-install
    all the extra access modules (SNMP, VITALINK).  The alarms still worked
    and maps came up fine.
    
    Thanks for all your input,
    Les