[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 44.370::system_management

Title:system management communications forum
Moderator:CHEST::THOMPSON
Created:Fri Mar 21 1986
Last Modified:Thu Jul 08 1993
Last Successful Update:Fri Jun 06 1997
Number of topics:490
Total number of notes:2018

18.0. "Problems due to software upgrades" by RDGE28::HAYES (Ian Hayes, ext. 4992) Mon Aug 04 1986 11:33

	This message is intended to help developers and supporters anticipate
        the impact on their applications caused by the listed upgades to
        the various systems software.
        
        This message is *not* a substitute for appropriate testing, rather
        it will help to resolve any problems caused by the upgrades.

        The information presented here was gained from the Release Notes
        documents relevant to the products and versions being considered.
        The Release Notes for the relevant product should *always* be consulted
        whenever a version changes, not only to gain knowledge of potential
        problems, but also to be made aware of any new features of the product.
        
        The information is presented here in a table. The FROM version number
        is taken from the currently implemented version on RDGE28. The TO
        version number is taken from the recent (11-Jul-1986) message from
        Pierre Roblin - Release Management.
        
        Product ! FROM ! TO  !Likely concerns
        --------+------+-----+----------------------------------------------
        VMS     ! 4.2  ! 4.3 ! NONE       
        --------+------+-----+----------------------------------------------
        CDD     ! 3.1  ! 3.2 ! NONE        
        --------+------+-----+----------------------------------------------
        DBMS    ! 2.2  ! 3.0 ! Root files need converting - use DBO/CONVERT.
                !      !     ! AIJ files are *not* compatible - roll forward
                !      !     ! all journals before converting.
        --------+------+-----+----------------------------------------------
        Rdb     ! 1.1  ! 2.0 ! Databases need converting - use RDO BACKUP
                !      !     ! before upgrading, then use RDO RESTORE after.
                !      !     ! See page 1-2 of Rdb V2.0 Release Notes.
        --------+------+-----+----------------------------------------------
        DTR     ! 3.2  ! 3.3 ! Minor changes to the way that DTR translates
                !      !     ! logicals - page 1-2 of DTR V3.3 Release Notes.
                !      !     ! Various bugs fixed which may effect RSEs,
                !      !     ! RUNNING TOTAL and others. See page 2-1 of
                !      !     ! Release Notes if you have problems.
        --------+------+-----+----------------------------------------------
        TDMS    ! 1.4  ! 1.5 ! NONE
        --------+------+-----+----------------------------------------------
        PASCAL  ! 3.1  ! 3.2 ! 3.2 environment files are *not* downward
                !      !     ! compatible with 3.1 PASCAL.
                !      !     ! 3.1 environment files are OK on 3.2 but
                !      !     ! recompiling is recommended anyway.
        --------+------+-----+----------------------------------------------

        Following is the complete list of new versions suggested by Pierre.
        I have not covered all of these in the above table because
        a) We are already using the required version
        b) We don't use that particular product.
              
	VMS 4.3
		
	ACMS 2.0	CDD 3.2		DBMS 3.0	DTR 3.3
	FMS 2.2		INDENT 2.1	RDB 2.0		TDMS 1.5

	ADA 1.2		APL 2.0		BASIC 2.4	BLISS 4.2
	C 2.1		COBOL 3.2	FORTRAN 4.4	PASCAL 3.2
	PL1 2.4		RPG 2.0

	DECMAIL 2.2	NMAIL 8.1	VTX 2.1		FTSV 2.0

        Finally, if there is any doubt - check the Release Notes!

	Ian.
    
T.RTitleUserPersonal
Name
DateLines
18.1Notes upgradeRDGE28::KEWJerry Kew dtn 830-4373Thu Aug 21 1986 11:244
When are we planning to upgrade to notes v1.1??

Jerry    

18.2Cluster Time...RDGE28::DRAPERSteve DraperThu Aug 21 1986 13:588
    In principle, I would have thought that it would be during/after
    the cluster upgrade work (just like nmail).
    
    In practice, I don't think it can be any earlier than that as, as
    far as I know, we don't have our IDS Notes V1.1 kit yet.
    
    steve
    
18.3Is it not in VMS?RDGE28::HAYESIan Hayes, ext. 4992Fri Aug 22 1986 09:203
    I thought VAXnotes was bundled in with VMS. Is it actually a seaprate
    installation then?
    
18.4No - it's not in VMSRDGE28::DRAPERSteve DraperFri Aug 22 1986 09:369
    1.	As far as I know, it's a layered product. 
    
    2.	It may well be bundled into VMS at some date in the future,
    	but I have no information regarding this.
    
    3.	A clue to point (1) is that you will not find a manual for VAXnotes
    	in the VMS documentation set.
    
    steve
18.5notes & dbmsRDGE28::KEWJerry Kew dtn 830-4373Tue Aug 26 1986 11:2911
2 points,

1st, it appears that we are not even on v1.0 notes yet, which is already 
giving us problems with the new tool ENOTES, the fast o'night batch 
extractor, as extractions of unseens extracts the whole conference in the 
case of notefiles on our own machine. I believe we are running T00.01.

2nd, it appears that DBMS v3.0 has bugs cleared in 3.1, so we would like to 
go straight to 3.1 if possible.

Jerry
18.6VMS 4.4??RDGE28::KEWJerry Kew dtn 830-4373Tue Aug 26 1986 14:337
More on the previous point, re: DBMS v3.1,

There are bugs in 3.0, which are cleared in 3.1 so obviously we would like 
to go to 3.1 asap, *but*, DBMS V3.1 requires VMS 4.4 as a minimum, thus, 
the obvious question, when are we moving on to VMS 4.4???

Jerry
18.7Aghhhhhhhhh..........Dont !RDGE21::MORRISTue Aug 26 1986 14:546
    Dont go to 4.4 its got more bugs than a dog and if you also have
    All-in-1 on the system it simply dont work no more.
    
    4.5 is SDC available October , net kits available now.
    
    Chris...
18.8Arrrrrrrrrrgh - when?RDGE28::KEWJerry Kew dtn 830-4373Tue Aug 26 1986 15:2011
>                        -< Aghhhhhhhhh..........Dont ! >-

>    Dont go to 4.4 its got more bugs than a dog and if you also have
>    All-in-1 on the system it simply dont work no more.


Thanks Chris, Ok, the question still stands,  when do we go to V4.5?

The DBMS version 3.0 bugs may well affect us.

Jerry
18.9Hang-on, we can't delay forever!!!RDGE28::HAYESIan Hayes, ext. 4992Thu Aug 28 1986 10:0722
    There is an never ending argument related to this issue. One can
    always say "...but the next version will cure xyz bug" because every
    release has bugs!
    
    To make things worse, there seems to be ever more dependancies on
    specific versions of other related system software so we are even
    more in danger of never upgrading to anything. Follow this scenario:
    
    DBMS V3.0 has a bug so wait till V3.1
    DBMS V3.1 requires VMS V4.4 so wait till VMS V4.4
    VMS 4.4 has a bug so wait till V4.5
    DBMS V3.1 doesn't work correctly with VMS V4.5 so wait till DBMS V3.2
    etc etc...
    
    I hasten to add that only the first three of the above are true
    but you see the sort of circles we can get into - and that's only
    considering two products! We have around twenty (I guess) on RDGE28!!
    
    I am not suggesting we migrate and be damned - that would be foolish
    but we *have* to put a stake in the ground somewhere and suffer
    some of the less painfull aggravations purely for the sake of getting
    somehwere!!    
18.10ADGV02::KERRELLDo not disturbThu Aug 28 1986 10:2220
>                    -< Hang-on, we can't delay forever!!! >-

I agree with you Ian, perhaps we need a slighly more 'formal' approach;

1.	The designer will describe the ideal world to system management.

2.	System Management will check against the needs of the whole (ADG+EIS+
	End User) and inform the designer how much of the ideal world is
	available now and when/if the rest will be available.

3.	The designer modifys the ideal world and the project plan to fit
	in and therefore becomes part of the whole.

4.	The whole world is published for the benefit of designers, supporters
	and system management.

Meanwhile this is a good forum for expressing concerns about future
product releases.

Dave.
18.11Compromise, compromiseRDGE00::DSMITHWed Sep 10 1986 15:2016
    That all sounds very nice but what about that little person we all
    seem to forget called the user, what he wants, and what his machine
    availability/requirements is. You could end up with one hell of
    a compromise that way.
    Personally I think the ADG machines should be kept as up to date
    on software and hardware as possible. After all, we're supposed
    to be setting the way for the future not getting embroiled in the
    past! Okay you have to support existing applications, but that's
    what a/several support machines are for - which consequently don't
    necessarily lend themselves to be in the same cluster as development.
    Somehow we seem to be tying our hands to conform all the time, instead
    of taking the lead.
    
    Just a few twitterings to keep the fire fed!
    
    Debbie (the heretic?!)