Conference iosg::all-in-1_v30

Hi,

>> the system says that you
>> need at least VAXNOTES version 2.1 installed, and the customer has 
>> install the VAXNOTES v2.3

>> Is that right that VAXNOTES v2.3 is not supported by ALL-IN-1 3.0?

This seems like a leap of logic to me... just because the system says you need
at least Notes V2.1 doesn't mean that V2.3 isn't supported; in fact, the use
of "at least" V2.1 means that V2.3 should work.

So what makes you think it doesn't work?  Did the installation fail?  Did the
installation work, but ALL-IN-1 refuse to start?  Did ALL-IN-1 start, but GPC
not work?

The only thing that might stop Notes V2.3 working with ALL-IN-1 is if it isn't
fully backwards compatible (slapped wrists to the notes developers if so :-).
I don't know enough about Notes V2.3 to comment on that.

Scott

    Notes V2.2 will only work on workstations if Motif is installed.
    Although the character cell interface will still work OK, this may
    cause some sites (including the one hosting this conference :-) ) to
    stay on Notes V2.1 because they don't have Motif compliant versions of
    all their other layered products. I suppose you could describe this as
    not being backwards compatible...
    
    V2.3 is *very* similar to V2.2, it was just reissued with "no new
    user-visible functionality" but supporting new licence types, and hence
    my use of V2.2 in the first paragraph.
    
    As far as ALL-IN-1 is concerned there should be no problems, *UNLESS*
    our galactically powerful Notes license doesn't work with V2.3....
    
    Graham

In fact what happens when you install ALL-IN-1 3.0 with notes 2.3 already on 
your system is as follows :

The installation procedure tells you that you need at least version 2.1
of notes and asks you if you want to continue without group conferencing.
If you say yes, notes 2.3 doesnt get linked to ALL-IN-1 and if you say no,
the installation stops.

I have a suspicion that this is merely a small bug in the installation 
procedure but have not yet gone that far in my investigation.

Regards,
  Richard

    We've looked at the code (KICHECKS.COM), and can't obviously see where
    it is failing.
    
    As we don't have VAXNotes V2.3 installed here, can you look and see
    what's going wrong, or post the first record from the shareable image 
    SYSLIBRARY:NOTES$SHARE.EXE using this sort of code from KICHECKS:
    
    $ open/read/share/error=CHECK_VERSION_ERROR idf SYSLIBRARY:NOTES$SHARE.EXE
    $ read idf hdr
    $ close idf
    $ sho sym hdr
    
    Thanks
    
    Graham and Chris (the installation team!)

Graham,

That directory spec should have been SYS$LIBRARY: or SYS$SHARE:, not SYSLIBRARY:.

This is what I got on my system in case it helps:

$ SHOW SYMBOL HDR
  HDR = "�.0.D.X.....0205................*............X.........................
.0................NOTES$SHARE.............................NOTES023........ z���.
..05-05............�...............-.�.......�.....................)............
.....,.............�.....!............LIBRTL_001................................
................................................................................
................................................................................
...............................
Preceding symbol value has been truncated

/Marty

The "NOTES023" ident is a different format to previous versions. It used to be
"NOTES V2.1".  It looks like this format is not handled by the check_version
routine in KICHECKS.COM.  Is the routine making a wild assumptions, or is the 
ident format of the Notes V2.3 image wrong according to standards?

Cheers,
	Chris.

    The way I read the SQM VMS Technical Requirements manual, says that
    this (NOTES023) is an invalid format...
    
    Anyone know whether it has shipped yet?
    
    Graham

I have been in contact with VAX Notes eng and they are about to send
me a patch to fix the image ID of NOTES$SHARE.EXE.  We will also discuss
the possibility of re-mastering the VAX Notes kit, but that will take
time and $$$ so we're not sure that will happen yet.

If you like getting your hands dirty, here's this morning's work on
getting around the problem (before I knew the image id patch was coming):

DISCLAIMER - I have not tested this completely so I cannot say if this
will actually fix the problem or not, but it appears it will

In VAX Notes V2.3, the Image ID for SYS$LIBRARY:NOTES$SHARE.EXE has been 
changed to "NOTES023" instead of "NOTES V2.3".  The ALL-IN-1 V3.0 Install and
re-link procedures check this image id to verify the correct version of
VAX Notes is on the system.

If you have VAX Notes V2.3 on the system and try to install ALL-IN-1 V3.0
with GPC, the install will fail claiming you do not have the correct version
of VAX Notes.

One way around this is to create a dummy NOTES$SHARE.EXE image with the
proper image id:

Step 1:
Create a file named FOOBAR.MAR with the following 4 lines in it

.title notes
.library "sys$library:lib"
.entry notes,^m<>
.end notes

Step 2:
Create a file named FOOBAR.OPT with these two lines in it

foobar.obj
identification="NOTES V2.3"

Step 3:
Issue these commands to create FOOBAR.EXE

$ macro foobar.mar
$ link foobar /options

Step 4:
Verify the image id of FOOBAR.EXE

$ anal/image/header foobar.exe

Step 5:
Issue these command to swap the files

$ rename sys$library:notes$share.exe notes$library:swapped_out_n$s.exe
$ rename foobar.exe sys$library:notes$share.exe

Step 6:
Install ALL-IN-1 V3.0, but do not choose to run the IVP at this time

Step 7:
Issue this command to swap the files back

$ rename notes$library:swapped_out_n$s.exe sys$library:notes$share.exe 


Re-linking ALL-IN-1 V3.0

The A1LNKASK.COM file also checks the image id of NOTES$SHARE.EXE so we need
to fix that as well.

Edit OA$BUILD:A1LNKASK.COM and find the label "CHECK_NOTES_VERSION".  Directly
beneath the label add the following line:

$ exit

(this will bypass the checking routine completely)

ALL-IN-1 V3.0 install fails at GPC link with VAX Notes V2.3

If you try to install ALL-IN-1 V3.0 and want to incorporate GPC, if you have
VAX Notes V2.3, it will fail, claiming you do not have at least V2.1 of Notes.

If you try to relink ALL-IN-1 V3.0 and you have VAX Notes V2.3, it will fail
to link in the Notes image because it claims you do not have the proper version
of Notes installed.

These errors are caused because ALL-IN-1 V3.0 looks to the Image Ident of
the SYS$SHARE:NOTES$SHARE.EXE file for the version number.  It is looking
for the Image Ident in the form of 'NOTES V2.x', but in VAX Notes V2.3 this
Image Ident was changed to 'NOTES023'.  This causes ALL-IN-1 V3.0 to think
you do not have the proper version of VAX Notes installed and it will not
link with the image.

*NOTE*
  VAX Notes V2.3 is not officially supported by ALL-IN-1 V3.0 because VAX Notes
  V2.3 was released after ALL-IN-1 V3.0 was and it has not been certified by
  ALL-IN-1 engineering.

The following patch file will change the Image Ident of the 
SYS$SHARE:NOTES$SHARE.EXE file to 'NOTES V2.3' so the ALL-IN-1 V3.0 install
and relink procedures will function properly.

-------------------

NOTES$SHARE.EXE
!  This patch will change the ident field of NOTES$SHARE.EXE Version 2.3 
!  from "NOTES023" to "NOTES V2.3".  This will fix the install and relink
!  problem in ALL-IN-1 V3.0.
!  PAF
!  To apply this patch: $ copy <this file> sys$update:notes023_version.com
!                       $ copy sys$share:notes$share sys$update
!                       $ set def sys$update
!                       $ anal/image notes$share.exe !ident is NOTES023	
!                       $ patch/absolute @notes023_version.com 
!                       $ anal/image notes$share.exe !ident is now NOTES V2.3
!                       $ copy notes$share.exe sys$share:
REPLACE/BYTE
^X00000080  ! change length from 8 to 10
^X00000008
EXIT
^X0000000A
EXI
REPLACE/BYTE
^X00000086  ! change "023.." to " V2.3" (five character change)
^X00000030
EXIT
^X00000020
EXI
REPLACE/BYTE
^X00000087
^X00000032
EXIT
^X00000056
EXI
REPLACE/BYTE
^X00000088
^X00000033
EXIT
^X00000032
EXI
REPLACE/BYTE
^X00000089
^X00000000
EXIT
^X0000002E
EXI
REPLACE/BYTE
^X0000008A
^X00000000
EXIT
^X00000033
EXI
UPDATE
EXI

-------------------

Here is an alternative method for those customers receiving this patch by means
other than electronically and who do not feel comfortable typing in the 
commands:

- Install ALL-IN-1 V3.0 and choose not to incorporate GPC at that time.

- Once ALL-IN-1 has been installed, go into ALL-IN-1 and do the following:
  CM
  ABE
  SEL
  NAME = A1LNKASK {find key}
  {cr}
  CO
  {fill in reason - To skip the VAX Notes V2.3 version check}
  {cr}
  {keypad 0}
  E
  ** insert a '$ exit' directly beneath the CHECK_NOTES_VERSION: label.  This 
     will cause the relink procedure to skip the section on checking the VAX 
     Notes version, link with Notes and then continue.
  MLA (and enter reason again)
  {the ALL-IN-1 manager or administrator has to actually move it to the 
   live area}
  Exit ALL-IN-1

- Relink ALL-IN-1 and choose to incorporate GPC at this point.

I just had a customer report (through a DEC internal) that ALL-IN-1 V2.4
complained about VAX Notes V2.3 in the same way ALL-IN-1 V3.0 does.  I sent
him the patch anyway.

Dave

    
    
    Hello and greetings,
    
    Re 1172:10
    Does the patch mentioned work satisfactorily?
    
    We've had a recent customer inquiry about ALL-IN-1 V2.4 with NOTES 2.3
    
    Regards,
    
    Chele (in disguise)

    We have had no complaints!
    
    regards,
    
    Andrew.D.Wicks (not Dave or Terry)

    since no one has answered here in a while, i was just wondering...
    
    has this been fixed at all or should i still do what is in .10?
    
    will be upgrading from ALL-IN-1 2.4 to 3.0 on a site that has NOTES
    V2.0 in a couple of weeks.
    
    	ann

    Ann,
                  
    rtfm? (IG p 4-1) notes must be at least v2.1 to work with ALL-IN-1 v3.0
    
    v2.1, v2.2, and v2.4 install and link fine against v3.0
    v2.3 still needs the creative patch discussed in this note
    
    Regards,
    
    Andrew.D.Wicks

    ok, i guess i didn't word my question right...
    
    i'm upgrading from ALL-IN-1 2.4 to 3.0 next weekend. the system
    currently has NOTES 2.0. i realize i have to upgrade to NOTES 2.3.
    
    is NOTES 2.3 sanctioned for ALL-IN-1 3.0 yet?
     has anything changed in NOTE023 in that i could NOT do the fix
    mentioned in .9?
    
    	ann
    

    Ann,
    
    It's sanctioned by me providing you do the patch thing. An official
    certifed list of supported products from Engineering hasn't been
    issued since Oct-1992! sorry.
    
    regards,
    
    Andrew.D.Wicks

    <<<< An official certifed list of supported products from Engineering
    <<<< hasn't been issued since Oct-1992!
    
    That's because the only thing we've certified since then is about two
    hundred field test kits of VMS V6.0
    
    Graham

    thanks andrew, i'll certainlydo the patch thing.
    
    there is a DSN article that the customer MIGHT see that mentions that
    NOTES023 is nor certified yet by ALL-IN-1 engineering. the article was
    last updated in Feb 93, that's why i was asking.
    
    thanks again 	ann

    GAP,
    
    I think you might have been missing the point I was trying to make
    about NOTES v2.4, Datatrieve v6.0/v6.1 etc... Like everyone I look
    forward to an updated product compatibility matrix that includes v6.0
    in note 6.*
    
    Regards,
    
    Andrew.D.Wicks

    No, I'm not missing the point at all. The only certifications we are
    currently doing is of VMS versions. When Open VMS for VAX V6.0 (or
    whatever it's called) is released, we'll update the matrix.
    
    Graham

    Thanks Ron - the mail I got said OpenVMS v6.0 shipped on June 26th
    with all update contracts being fulfilled on or before July 10th
    (these may of course be just U.S dates)
    
    regards,
    
    Andrew.D.Wicks