Conference iosg::all-in-1_v30

    
    	Because the ALL-IN-1 image has installed privs, you need to install
    	everything it links against with /PROTECT.
    
    	The FileCab server stuff links against DNS in case you want to use
    	DNS naming for your partitions, but most people don't, so it
    	doesn't usually get used.
    
    Regards,
    Paul

    Sean,
    
    the need for the /PROT on DNS$SHARE is of course on page 1-2 of the
    release notes - you did read them didn't you? (:==:)
    
    Regards,
    
    Andrew.D.Wicks

		As a matter of interest we did read the release note(notice the
	use of the singular here) that was moved into SYS$HELP as we started 
	the installation...and very helpful it was too, so much so that I've
	even included it below for your dissertation. So we look for the various
	A1CUS/LUS/LDE etc release notes in SYS$HELP....NFF. We checked on 
	SYS$HELP on another node where we did a recent successful ALL-IN-1 V3.0
	installation...guess what....NFF. It worked over there so we make what
	seems like a reasonable decision to go ahead....well you know the rest,
	grabbed by the proverbial DNS$SHARE's. 

		So here's a couple of thoughts for sharing....

	Seeing as we're discussing manuals, could we get the name of images
	correct in them..the installation guide (mine at least) talks about
	DNS$SHR...a mute point you might think but try telling that to the 1st
	customer who blasts his office system having done it by the book!

	Lets have ALL the appropriate release notes moved to SYS$HELP, its a 
	bit late after the event extracting them with VMS Backup.

	And finally, surely it would be a very good idea for the installation/
	upgrade to check for the protection levels on this image at the outset
	rather than at a stage where its likely to blow away n hours work.

	Sorry not to be able to respond until now, Birmingham has been off the
	network most of the day. Paul,thanks for your helpful comments. Andrew,
	what does that D stand for! :-)....

	Thoughtfully yours,
	
		Se�n
	
$ty a1030.release_notes
                          
        The on-line release notes for ALL-IN-1 V3.0 are split by
        component and installed from separate media (See the
        installation documentation for more information). Once
        installed they can be obtained by printing the following
        files.

        SYS$HELP:A1Cxx030.RELEASE_NOTES - Market component related.
        SYS$HELP:A1Lyy030.RELEASE_NOTES  - Language component related.

        Where xx = Market id and yy Language id.

        Eg.

   SYS$HELP:A1CUS030.RELEASE_NOTES      - US Market component notes.
   SYS$HELP:A1LUS030.RELEASE_NOTES      - AMERICAN Language component notes.
   SYS$HELP:A1LDE030.RELEASE_NOTES      - GERMAN Language component notes.
   SYS$HELP:A1LFR030.RELEASE_NOTES      - FRENCH Language component notes.

    Hi Se�n, you're not the only one to get confused about the release
    notes for ALL-IN-1.
    
    The release notes for the base and for each language you want comes on
    a separate tape, and needs to be installed separately using VMSINSTAL.
    If you never did that, you'll only find the A1030.RELEASE_NOTES.
    
    If you're going to submit an SPR, maybe you could suggest that
    something like the following might be added to the A1030.r...: 
    
    ++ Note:  If you can't find any A1Cxx030.RELEASE_NOTES or
    ++        A1Lyy030.RELEASE_NOTES in SYS$HELP ask your system
    ++        manager to install them from their separate media.
         
   Best regards,
   Allan
   

    
    	Details on how to obtain the release notes are described in the
    Installation guide.
    
    	The release notes are on the Language/Market component tape.  To
    obtain them mount this tape and enter :
    
    	$ @SYS$UPDATE:VMSINSTAL A1L<lang>030 <tape> OPTIONS N
    	$ @SYS$UPDATE:VMSINSTAL A1C<mkt>030 <tape> OPTIONS N
    
    Where :
    	<lang> is the name of the language component (e.g. US)
    	<mkt>  is the name of the market component (e.g. GB)
    	<tape> is the name of the tape drive (e.g. MUA0)
    
    Martin.

    Backing up Martin's .-1
    
    We've done the release notes separate from the base tape since V2.3.
    It's hardly our fault if VMSINSTAL hasn't been upgraded to support the
    ABC packaging model that we have been spearheading and following for
    some years now.
    
    In V3.0 we made it easier to find the release notes by putting them
    back on the language tape instead of on a separate tape as they were in
    V2.3 and V2.4.
    
    I don't see how we can put language specific release notes anywhere
    other than on the language tape.
    
    I don't see how we can describe the copying of the release notes any
    more specifically than the way it is in the Installation Guide. If you
    don't read the IG, then I don't see how we can describe it any better
    than by putting the explanation we do in the dummy base release notes.
    
    FLAME ON
    
    Notes written in the tone of .3 do not encourage me to look favourably
    on addressing this so called problem, produced by not bothering to read
    the documentation properly.
    
    FLAME OFF
    
    I look forward to receiving a copy of your SPR against VMSINSTAL's
    non-support of the ABC packaging model.
    
    Graham

	Heh, this has generated a bit of action hasn't it. Andy D, thanks for
your suggestions, I'll do just that. Graham, is that a job offer I see there?

	Right Graham, yes we admit not reading the Dialect release notes,
otherwise we wouldn't have been caught out...in our defence, we had time 
constraints after having problems with the CART and Licensing, see some previous 
notes. Again, we checked out SYS$HELP on another system where we had completed
a recent installation and as this installation worked, no problems, assumed
(wrongly..our fault) that it should be ok to proceed.

	I guess this could be reviewed in several ways. Package all the release
notes (Base,Dialect & Market) on 1 save_set and based on the responses to the
installation questions, move the appropriate ones to SYS$HELP. Or have all (I
guess this would be asking a lot) the release notes in one file, with chapters
for Base,Lang and Mkdt...again it would be better if based on responses to the
installation questions. With most layered product installations, the release
notes tend to get read after they've been moved into SYS$HELP..i.e. thats 
normally in my experience a break off time in the installation....and if all's
ok, proceed onwards. When we didn't find the Dialect and Market notes on either
our system or on the other where things went ok, we decieed to go ahead. Mea
culpa! BTW, should all the various notes have got moved to SYS$HELP, 'cos they
definitely aint there on our "good" one.

	Graham, I can assure you that no supercillious "tone" was implied		 
in my response...there were mitigating circumstances and I was hoping to bring
a few things to your and other peoples attention. If someone else profits from
our experience...GREAT...this note will have been worthwhile. As VMSINSTAL is
the only tool that Im aware of to install/upgrade ALL-IN-1 with, the issue if
you regard it as such, needs to be addressed...obviously at least one other 
person in Digital perceives this to be the case. Thanks to all who have made 
contributions to this note, sorry anyone has been upset.

	Regards,
		Se�n

    Se�n,
    
    Unfortunately your suggestions of putting all the various versions of
    the release notes on one piece of media won't work, for the same reason
    that we package the code like that in the first place i.e. they aren't
    all available at the same time.
    
    We have the US and GB notes now, but the other languages aren't
    available for a bit (Moderator ambiguity!) whilst some of the other
    languages aren't available for a bit longer after that. Hence the only
    way we could put them all in one place would be if we reissued the "one
    place" every time another language became available. Since the SSB
    charge us loads of dosh to resubmit things, apart from the logistics
    involved, we don't do it like that...
    
    The problem is that when you do @VMSINSTAL OPTIONS N to get the dummy
    release notes (of course you don't realise they're the dummy ones at
    that stage!) off the base tape, none of our code gets executed, so I
    can't fix it. That's why I said it was a VMSINSTAL problem.
    
    I was thinking that perhaps we could provide the language release notes
    to SYS$HELP during a full installation, once we knew what language you
    wanted, and had the tape loaded. There are two problems with this, one
    from your point of view, it's too late, since you *should* have already
    read the Release Notes before getting that far, but secondly, we don't
    normally read saveset .A off the language tape, and in fact it would
    cause errors if we did, since it would have duplicate file names in it,
    which breaks VMSINSTAL. So we'd have to move the release notes into
    anotehr saveset, which would mean that if you *did* read the IG and
    knew that you had to load the language tape and do an OPTIONS N to get
    the Release Notes, we'd need to put them in two places! Perhaps we could
    provide another option like the licence load option that would go off
    and get all the release notes. Any better ideas????
    
    I hope the preceding complex explanation goes some way towards
    explaining why we haven't solved this problem before!
    
    Graham