Conference iosg::all-in-1_v30

15.0. "Upgrading a system with Lotus 1-2-3 for ALL-IN-1" by SIOG::T_REDMOND (Thoughts of an Idle Mind) Fri Feb 14 1992 15:25

================================================================================
Note 309.0       Upgrading a system with 1-2-3 already installed      21 replies
SIOG::T_REDMOND "Thoughts of an Idle Mind"          132 lines  19-JAN-1992 20:59
--------------------------------------------------------------------------------
                                        Date:     19-Jan-1992 08:06pm GMT
                                        From:     Tony Redmond
                                                  REDMOND.TONY
                                        Dept:     European B/OIS Engineering
                                        Tel No:   DTN 827 2264

Subject: I: Upgrading Lotus 1-2-3/ALL-IN-1 systems to DIAMOND
    
    The CM+ team had an opportunity to review the requirements of the 
    Customization Management subsystem in ALL-IN-1 V3.0 with some technical 
    representatives from Lotus Development at the European CSO Forum in 
    Paris last week. You'll recall that we have been looking for such a 
    meeting for quite some time.
    
    During our review, which I believe was mutually benefical, we 
    established that:
    
    o	 Lotus and Soma (subcontractors to Lotus) are working hard to ready 
         a new release of 1-2-3 for ALL-IN-1 V3.0. They hope to go into 
         beta test in May with an aim to ship in the U.S. and U.K markets 
         in July.
    
    o	 Some post-installation manual intervention is required if a 
         customer upgrades an ALL-IN-1 V2.3 or V2.4 system to V3.0 if Lotus 
         1-2-3 for ALL-IN-1 is present on the system. 
    
    This memo is to identify the post-installation problem to people within 
    Digital that may be involved with customer upgrades. Please pass it 
    onto anyone not already on the distribution list who should receive 
    this information. I'll like to stress that the information contained 
    here is preliminary. It needs to be checked out by upgrading ALL-IN-1 
    V2.3 and V2.4 systems to V3.0 and noting the steps required to get 
    1-2-3 working again. As the same situation may occur for Digital 
    products such as EARS and Mica, I have taken the liberty to include the 
    relevent development managers in the initial distribution.  I'll also 
    post it the DIAMONDFT conference.
    
    The first question to ask is why some manual intervention is necessary 
    after an upgrade operation is successful.  As we know, ALL-IN-1 
    upgrades are performed in a totally uncustomized state. Site specific 
    changes are therefore avoided and the installation can be carried out 
    in a known environment.  Customized code, ranging from simple script or 
    form changes up to and including site code level additions are normally 
    reintroduced after the installation completes.
    
    ALL-IN-1 V2.3 or V2.4 did not offer the facility to isolate the code 
    for layered applications. Separate applications are fully supported in 
    ALL-IN-1 V3.0. In the interim, Lotus 1-2-3 and some other applications 
    such as Mica and EARS, extended ALL-IN-1 by defining separate 
    application areas through Customization Management, providing separate 
    startup procedures, and, in some cases, including their own source code 
    areas into TXL compilation routines.  Records written into the 
    CM$LANGUAGES data set, such as L123_SHARE and L123_ENGLISH, are the 
    most obvious sign that such an extension had been made.
    
    We attempt to recognize these applications during an upgrade procedure. 
    A scan is made of CM$LANGUAGES and any non-standard entries are 
    identified and prototype records written into the CM$APP, CM$MAF, and 
    CM$AUTH$USERS data sets.  These serve to identify the application 
    (L123), application areas (L123_SHARE and L123_ENGLISH), and authorized 
    programmers for Customization Management. The CM$APP, CM$MAF, and 
    CM$AUTH$USERS data sets do not exist under ALL-IN-1 V2.3 or V2.4.
    
    Prototype records identify that applications exist. But they do not 
    contain the information that we require to start up the application 
    properly, nor to define logical names or place application code within 
    a TXL.  These steps must be carried out after an upgrade occurs and if 
    they are ignored, then Lotus 1-2-3 will not be available until they 
    are.  The most serious consequence is that all of the 1-2-3 scripts 
    which are currently compiled into CMTXL.TXL will not be available 
    after an upgrade. Thus, 1-2-3 will not work.
    
    After the discussion with Lotus last Friday it became evident that we 
    cannot detail exactly what steps need to be executed and in what order 
    without exposure to systems running 1-2-3.  Interaction with the 
    development team is also necessary to ensure that the updated version 
    of 1-2-3 for ALL-IN-1 V3.0 correctly identifies itself to Customization 
    Management.  
    
    Clearly some customers in this situation will want to upgrade to 
    ALL-IN-1 V3.0 soon after they receive their update kit. A customer 
    satisfaction issue is likely to arise if we have to tell customers that 
    they must wait until the upgraded 1-2-3 kit becomes available. A note 
    has been included in the ALL-IN-1 V3.0 release notes advising customers 
    to contact the appropriate vendor to seek advice regarding upgrades for 
    layered applications.
    
    Also, both our CSCs and the Lotus support channels must be made aware 
    that the problem exists and be able to help customers perform the 
    manual steps for an upgrade, if that is what the customer wishes. I 
    believe that it would be in all our interests to create a script/DCL 
    command procedure which would populate the data sets correctly after an 
    upgrade had been completed. Lotus are in the best position to write 
    such a procedure, as they will have to do something similar for their 
    own upgrade procedure.  
    
    Anyway, I have advised Lotus that the problem exists and I know that 
    Mark Benzies has already been in contact with Cambridge to advise them 
    of same. As Lotus have had baselevels of DIAMOND for some months now I 
    am sure that they already have been through some upgrades and are 
    likely to have noticed that some adjustments are necessary. If they 
    haven't, then they know now.
    
    Let me know how you want us to proceed with this. I think that we need 
    to get together with Lotus development staff, but I'll leave the final 
    call to the people that manage our relationship with Lotus and ALL-IN-1 
    product management.
    
    Best Regards, Tony 
    
================================================================================
Note 309.1       Upgrading a system with 1-2-3 already installed         1 of 21
SIOG::T_REDMOND "Thoughts of an Idle Mind"            5 lines  19-JAN-1992 21:02
                                 -< Comments? >-
--------------------------------------------------------------------------------
    Your comments on .0 are invited. I believe that there are a couple of
    hundred 1-2-3 sites in the U.S., which is where I believe we will get
    the most grief...
    
    Tony
================================================================================
Note 309.2       Upgrading a system with 1-2-3 already installed         2 of 21
AIMTEC::WICKS_A "Oh no he's back in Atlanta!!"       35 lines  19-JAN-1992 21:22
                 -< Yes we're expecting lots of calls on this >-
--------------------------------------------------------------------------------
    Tony,
    
    [Well it had to be me didn't it who else is there?]
    
    This is just the kind of information we in the CSC have been waiting
    for. Lotus 1-2-3 is kind of strange beast in that SOMA who actually
    write the code are in Canada and so we hadn't heard much from them. 
    
    I guess there are two things we need to do at this point.
    
    1) ensure that there is adequate documentation to warn customers
       of the danger of upgrading to v3.0 when they have any third party
       asset or other DIGITAL SSB product on their system.
       [so far IOSG have strongly declined to provide this]
    
    2) develop a process, STARS article, tool etc... that helps a customer
       get themseleves out of the mess they've got themselves into. I'll
       talk to our L123 people tomorrow and show them your note. I also
       promise to read it in more detail - at 2400 baud and without a printer
       i've only got my recollections of what i've just read to go on.
    
    Coincidently on Friday night Angela and I were dialed into the
    Microsystems (MASS-11) machine and they don't look close to being
    ready for DIAMOND. It would appear (and i hope you're sitting down
    here) that they are writing thing directly into CM datasets without
    quite knowing what - i'll leave the rest of the gory detail to another
    note.
    
    ... and as for Wordperfect ....
    
    Regards,
    
    Andrew.D.Wicks
    P.S I guess after the comments during the World Cup about Western Samoa
        you'd expect me to mention the rugby wouldn't you?
================================================================================
Note 309.3       Upgrading a system with 1-2-3 already installed         3 of 21
SIOG::T_REDMOND "Thoughts of an Idle Mind"           12 lines  20-JAN-1992 09:17
                     -< A warning is in the release notes >-
--------------------------------------------------------------------------------
    Because we knew that some work is necessary to upgrade kits for V3.0,
    we stuck the entry into the release notes advising people to contact
    their vendor for product-specific information before attempting to
    upgrade. Clearly we cannot try and cover the bases for everyone in this
    world who layers on top of ALL-IN-1. I think it's going to be a process
    of learning (for us, as we tackle the first product and find out all
    the issues), followed by education (as we spread the information to
    others).
    
    Of well, back to looking for a 1-2-3 system...
    
    Tony
================================================================================
Note 309.18      Upgrading a system with 1-2-3 already installed        18 of 21
SIOG::T_REDMOND "Thoughts of an Idle Mind"           71 lines  28-JAN-1992 09:16
                  -< Getting 1-2-3 to work on ALL-IN-1 V3.0 >-
--------------------------------------------------------------------------------
    1-2-3 now works (nearly) on DIPROD. I have managed to munge everything
    together so that all the initialization etc. is done correctly. 
    However, I cannot edit a worksheet as no licence is installed!  
    
    Lots of things have to be changed to get 1-2-3 running. Here is a brief
    list:
    
    1. CM$APP and CM$MAF records for L123, L123_SHARE, and L123_ENGLISH
       deleted and recreated by hand.  This makes sure that the areas are
       correctly initialized and history files are provided.  Note. Do not
       accept the option that creates default authorized locations!
    
    2. Authorized locations created for the locations that 1-2-3 uses.
      
       - FRM
       - SCP
       - DO
       - BLP
    
       Some of these locations have to be marked to be included in the
       TXL.
       
       Lotus (under V2.3/V2.4) doesn't use an area called OA$L123_A1_SCP_ENGLISH
       However, the TXL compilation code complains about the instructions 
       in L123_A1_CMU_ERROR.SCP (.PROCESS executed in wrong mode), so I
       set up two new directories for SCP elements and defined logicals to
       point to them (OA$L123_A1_SCP_ENGLISH and OA$SITE_L123_A1_SCP_ENGLISH).
       The authorized locations records were then created to point at these 
       directories.
    
    3. Note that 1-2-3 doesn't know about OA$CUSTOM, and will not open
       customized form libraries. I set the libraries up anyway...
       (SITEL123_A1.FLB and SITEL123_A1_MANAGER.FLB). I didn't bother
       amending code to use OA$CUSTOM, but this could easily be done in
       the standard 1-2-3 initialization script (L123_INIT.SCP).
    
    4. The 1-2-3 startup procedure (SYS$STARTUP:L123_A1$STARTUP.COM) was
       then amended so that the 1-2-3 logicals were not appended to the
       standard ALL-IN-1 logicals used for OA$DO and OA$BLP. This doesn't
       have to happen in V3.0 as CM takes care of bringing the 1-2-3
       directories into the TXL compilation. 1-2-3 also adds definitions to
       OA$LIB and OA$DATA - I left these alone as they do little harm!
    
       The 1-2-3 procedure mentions OA$SITE_DEV, which is not used in V3.0.
       I left this alone (commented it out...) pending further investigation!
    
    5. After starting up 1-2-3 and making sure that all the logicals were
       correctly defined, I compiled the ALL-IN-1 TXL. Sure enough, all the
       Lotus directories (SCP, BLP, and DO) were included in the A1TXL.
    
    6. 1-2-3 amends the MAIN, DEFAULT, SM, SM_DEFAULT, SA, and SA_DEFAULT 
       forms. After an upgrade these forms will be registered in CM.
       However, as many changes have been made to forms like DEFAULT in 
       ALL-IN-1 V3.0, I deleted the elements and recustomized the base 
       V3.0 versions to add the 1-2-3 code. This is much easier than
       attempting to reconcile the V3.0 changes with a customized version
       of a V2.4 form. Use the "Print Differences" option to locate the
       changes that must be made.
    
    7. The forms were moved into their live locations.
    
    8. I restarted ALL-IN-1 (pick up new TXL etc.) and was able to get into
       the 1-2-3 main menu and create a worksheet. Unhappily before any 
       edits could be performed 1-2-3 said "that's quite enough" and exited
       saying that I didn't have a licence.
    
    Lots of fun...
    
    Tony
    
    
================================================================================
Note 309.19      Upgrading a system with 1-2-3 already installed        19 of 21
SIOG::T_REDMOND "Thoughts of an Idle Mind"            6 lines  28-JAN-1992 13:58
                            -< Slight afterthought >-
--------------------------------------------------------------------------------
    One point I forgot is that the standard 1-2-3 startup file used under
    V2.3 and V2.4 needs to be changed for V3.0. A lot of the work they do
    in the startup is obsolete now - for example, they don't need to define
    logical names for authorized locations as CM will do this for them...
    
    Tony
================================================================================
Note 309.21      Upgrading a system with 1-2-3 already installed        21 of 21
SIOG::T_REDMOND "Thoughts of an Idle Mind"           28 lines  30-JAN-1992 20:18
                     -< Lotus 1-2-3 and customized forms >-
--------------------------------------------------------------------------------
    Final, final, note.
    
    Lotus 1-2-3 updates (with safe CM techniques) some standard forms under
    V2.3 or V2.4. These are also updated by ALL-IN-1 in V3.0. CART will
    detect (thanks to safe CM) the changes and flag the forms as having
    been updated by Digital.
    
    The forms are:
    
    DEFAULT	Mandatory change. Lots of new code for UDPs, GPC 
    	 	initialization, captive accounts, keyboard locking etc.
    SM		Advisory change. New SM options, new SM message symbols.
    SM_DEFAULT	ditto.
    SA		Advisory change. New SA options, new SA message symbols.
    SA_DEFAULT	ditto.
    MAIN	Advisory change. Not much happened here.
    
    I think that's the lot, but every little bit of information counts.
    
    Just upgrading 1-2-3 following the steps reported here (perhaps this
    note had better be extracted and posted in the main ALL-IN-1
    conference?) will result in a working 1-2-3 system. But the long term
    effect of not recustomizing the forms mentioned above cannot be
    determined due to the different circumstances on each system. 
    
    Just to bear in mind...
    
    Tony

    Quick update. It looks like Lotus have been convinced that they need to
    produce a patch that can be run after an ALL-IN-1 V3.0 system that had
    already installed 1-2-3 for ALL-IN-1 (under V2.3 or V2.4) has been
    upgraded. The patch might even be available at the start of April.
    
    FWIW, Tony

    
    
    Re .1 that is good news!  So, what would you like for the customers
    to be told up front (before upgrading ALL-IN-1 to V3.0)? Is it
    limited to the warning given in the read-me-first etc. Which is 
    basically they should first check with the vendor?  If so, do you
    know how Lotus will respond until they get this patch available?
    If they respond, they do not recommend upgrading ALL-IN-1, is that
    okay with us? That would be the easiest thing for them to say. 
    
    If the only option would be to de-integrate Lotus, do we have the steps
    to do that, or is that Lotus' responsibility too?
    
    If there is any additional information and/or warnings that should be
    available to the customer, let me know and I can at least load them
    into STARS.
    
    Trying to get a jump on things,
    Faith
    

    We have worked out how we (Digital) can help Lotus to create a kit that
    fully supports ALL-IN-1 V3.0. A discussion is currently raging as to
    whether effort should be put into building a patch that would help
    sites that upgrade to V3.0 run 1-2-3 afterwards, or whether we should
    just put the effort into an upgraded kit.
    
    With the slip in ALL-IN-1 V3.0 FCS, the end April date for a Lotus
    patch is, I suspect, a moot point.
    
    Tony

We have just installed ALL-IN-1 v3.0 on a new system, and then went to 
try and get Lotus 1-2-3 for ALL-IN-1 installed afterwards.  This has 
built in checks about the version of ALL-IN-1, and wont let me get to 
the satge of trying some of the manual changes detailed in earlier 
notes and replies.

Is there any sign of an updated kit as we are just about to enter April.

John

    No, there is no updated kit available yet. The earliest date I have
    heard is that a beta version of Lotus 1-2-3 for ALL-IN-1 V3.0 should
    be around in June. Lotus decided not to try and produce a patch since
    ALL-IN-1 V3.0 slipped its FCS date from February into April.
    
    Don't try and install the current Lotus kit onto V3.0. It won't work,
    even if you try to work around the check in KITINSTAL.COM.  At least,
    it won't work initially, but may do if you do a lot of changing in
    KITINSTAL.COM.
    
    Tony

    Any news yet on what customers should do if they want to 
    upgrade to v.3.0 and they have Lotus for ALL-IN-1 installed?
    
    Its the middle of May now - is there a patch available yet?
    
    Thanks
    Julia CSC

    I spoke with the Lotus development manager yesterday. As expected,
    Lotus are finding out that there's a bit more to upgrading an
    application to V3.0 than meets the eye. So it's taking them a little
    longer than they imagined. The good news is that code is starting to
    come out and they are making progress, hopefully towards a beta kit in
    June.
    
    As you are located in Europe, you should contact Luis Lassala @ILO
    (European Marketing) to get a customer on the list of beta sites, if
    they want to upgrade early.  
    
    The alternative is to use the procedure documented in this topic to
    perform a manual upgrade.
    
    Tony

    Julia,
    
    Have you seen the article entitled 
    Third Party Integration (Lotus 1-2-3) and Upgrade To ALL-IN-1 V3.0            
    it's in the OA1 database here in the U.S. It's got a lot of 'CSC eyes
    only' stuff in it so I won't post it here as I assume you can access
    our database?
    
    What it does say in unhidden text is:
    
     Lotus 1-2-3 for ALL-IN-1 Customers                                        
                                                                                  
    Customers who are currently using Lotus 1-2-3 for ALL-IN-1 under ALL-IN-1     
    V2.3 or V2.4 should be aware that 1-2-3 for ALL-IN-1 will not function        
    properly if ALL-IN-1 is upgraded to V3.0.  Lotus Development Corporation is   
    currently developing a new release that will support ALL-IN-1 V3.0 and many   
    of the new V3.0 features.  This release is expected to be available in the    
    summer timeframe.  No patch or workaround will be available in the interim.   
        
    The information in the article came from both ALL-IN-1 and Lotus
    Product Management.
                                                            
    Regards,
    
    Andrew.D.Wicks

    I just spoke with the people doing the work. They think that they can
    get a beta kit out on May 30...
    
    Tony

    Tony,
    
    Do you know what the process is, or who to contact, to be a beta test
    site for the Lotus 1-2-3 integration kit?  I'm not sure we'd be
    interested in doing it, but we might be.
    
    -Linda

    Linda,
                  
    In the U.S at least you can contact either your friendly CSC a few
    exits down I-85 or you can contact the Product Manager Joe Tomas.
    
    But of course i'm sure Tony has another route.
    
    Regards,
    
    Andrew.D.Wicks

    The best way is to contact Joe Tomas @TTB, the Lotus relationship
    manager. Joe is a sensible sort of fellow and I'm sure he will be
    interested in a few beta sites.
    
    Tony

Hi,

Did I miss something or is the LOTUS 1-2-3 kit for V3.0 of ALL-IN-1 available
yet?  The last reply to this note is 2 months ago...

I hope a kit is ready now,

any help is always appreciated,

-jackie brown

    Jackie,
    
    No - the kit is still some way away.
    
    Regards,
    
    Andrew.D.Wicks

    While we are talking about LOTUS does anyone have a pointer to an
    integration kit for ALL-IN-1 BRITISH V2.4?
    
    Ta,
    Kevin

    Who knows.... but there is something in:
     	SAC::DISK$USER22:[OPAC_ROOT.PUBLIC.A1LOTUS]
    
    Whether it is V2.3 or V2.4, I don't know.... maybe Bob Scarr or Zoe
    Pickup (DEC Park) can help?
    
    Cheers, Chris

I sent mail to Joe Tomas to find an approximate timeframe for the Lotus product
for ALL-IN-1 V3.0.  He indicated a September (!) timeframe.  Also, the new
product manager is Laurie Studivan @OGO.

-jackie

    Jackie,
    
    I would still consider the ship date to be optimistic, so I wouldn't
    set the customers expectations quite yet.
    
    I'd certainly hope that the month it ships in ends with the letters BER
    though (:==:)
    
    Regards,
    
    Andrew.D.Wicks

The beta releases that Lotus have sent out look good.  They want to get some 
minor problems sorted out, especially those that occur in the I18N area where 
1-2-3 is installed on multilingual systems, or 1-2-3/English needs to be 
installed on top of ALL-IN-1/German (etc., etc.)

Before anyone comes up with the bright idea that all would be well if Lotus 
released an English compliant version now, this is not the case.  They are 
changing things all the time in the installation and other procedures. 
Upgrades are already a pain (to take account of all possible upgrade paths), 
so they want to get it right before they release anything. I think this 
approach is good.

We should all note the amount of time taken for a vendor to upgrade their 
application to comply fully with ALL-IN-1 V3.0.  Upgrading is not a quick 
overnight job, at least, not if you want it done properly.

Tony

    How about now? Is the integration kit ready now? Huh?
    
    Bruce

    Bruce,
    
    The Lotus notesfile is at MRKTNG::LOTUS and the Product Manager
    is Laurie Hunter-Studivan @OGO, DTN: 276-9691
    
    Regards,
    
    Andrew.D.Wicks

    Chris,
    
    Lotus have shipped their version since we have it installed. The
    DIGITAL counterpart put a note in the Lotus conference saying it 
    was shipping on Sept 23rd and we haven't been able to contact her
    by phone/mail to confirm this.
    
    Regards,
    
    Andrew.D.Wicks

    If it SHIPPED on 23rd September... how can the following be true??:
    (as obtained from ESSB from VTX):
    
                             
    P L A N N E D    R E L E A S E S
    
               LOTUS 1-2-3 ALL-IN-1 V1.5       (  Submission Number WMOI272 )
                                                       Updated on 03-Oct-92
                     
                      Orig/Plan  Curr/Plan   Actual    Slips  Slip Reason    
    
     Submission      31-Aug-92  17-Sep-92  17-Sep-92  0005                  
     U.S. release    15-Sep-92  02-Oct-92  02-Oct-92  0003   CORSPOND SUBM  
     Europe release  02-Oct-92  16-Oct-92             0004                  
    
    
    Is the kit available on the network anywhere??

    A rather large UK customer ran into a problem installing Lotus 1-2-3
    for ALL-IN-1 on a BRITISH English system.  I have done some digging
    around on behalf of our product marketing people and have discovered
    where the problem lies -- incorrect updating of the CM$SDC records. 
    This note is posted to enable people to address the issue if it happens
    on your site while Digital and Lotus sort out whether a new kit is
    required.
    
    Tony
    
The first problem isn't really an issue. The installation procedure offers the
first language found on the kit, in this case ENGLISH.  That's the reason why
the customer had to enter BRITISH. 

The real problem is that the Lotus 1-2-3 installation adds the correct records
to the base elements file (CM$SDC) but writes an incorrect value into the
DISK_LOCATION field.  Instead of writing pointers to BRITISH language logical
names it writes ENGLISH language values.  The same problem will occur on any
installation that attempts to install the ENGLISH kit onto any other ALL-IN-1
language, so clearly this is rather a large problem!   

xxxx will be taking to Lotus about whether they need to re-release the kit. I
think they should as otherwise we'll get into the "paper patch" fiasco that we
had for ALL-IN-1 V2.4.  I suggest that someone makes this point to Lotus

There are two workarounds that I can think of.  The customer might like to take
either:

a) Create a set of system logical names that, for example, point
OA$L123_A1_LIB_ENGLISH to OA$L123_A1_LIB_BRITISH.

b) Write an ALL-IN-1 script that loops down through the CM$SDC data set and
fixes up the records.

Option b) is the better option.  
    
    Let me know what you want me to do.
    
    Tony

Tony,

Has the 'rather large UK customer' been given both workarounds ?

I think they happen to be my customer.

Pam

    I don't know.  I gave the answer to the Lotus 1-2-3/ALL-IN-1 marketing
    manager (Luis Lassala @ILO) and left it to him...
    
    Tony

    Now I'm confused.
    Is the new LOTUS 123 kit available yet ? What version is it ?
    
    The reason I asked is, I told my customer that the version they've been
    running with for the last year or so under 	ALL-IN-1 V2.4 won't work
    with V3.0.  So she rang LOTUS and the chap there said the version she's
    got WILL work OK, now having read all the previous replies this can't
    be true can it ??
    
    Steve Rice - SPS, North West UK.
    
    

    Hello Steve,

 >   Is the new LOTUS 123 kit available yet ? What version is it ?

    The sticker on the box says: Version 1.5 ! NEW.....

    Regards,

    Jan

    
    Steve,
    
    Lotus 1-2-3 V1.5 is specifically written for ALL-IN-1 V3.0, but also
    runs under ALL-IN-1 V2.4. So, if that's the case at your customer site
    then the answer of the Lotus chap is correct.
    
    Ciao,
    
    	Simon

>>    The reason I asked is, I told my customer that the version they've been
>>    running with for the last year or so under ALL-IN-1 V2.4
                           ^^^^^^^^^^^^^^^
    
    In view of the above, I doubt they've got V1.5 - however the customer
    will let me know on Monday.
    
    Thanks,
    	Stevie.

    Steve,
                  
    Simple...
    
    If they have previous version of Lotus it runs under v2.3 and v2.4
    If they have version 1.5 it runs on v2.4 and v3.0
    
    Regards,
    
    Andrew.D.Wicks
    

	LOTUS 1-2-3 for ALL-IN-1 V1.5 is on hold in the UK.

	I believe Luis Lassala is dealing with this issue. I will chase
	this up when I can get to talk to Luis next week

	Cheers

	Jill

    I have a question about Lotus 1.02 under ALL-IN-1 V3.0. I have been
    able to make this Lotus version working on a french ALL-IN-1 language
    and have now to do the same on a german system.
    
    It seems that the type DOCUMENT is doing problem (german is DOKUMENT,
    french is same as english). There is a symbol called cli$fcab_fd_stype
    pointing to DOCUMENT and the cabinet scan function find DOKUMENT as
    type. I didn't found were this symbol is defined?
    
    Any sugestions?
    
    Felix

    I have now been able to read a worksheet by doing the following change
    on the script l123a1_fcab_find_doc.scp:
    
.label start
get cli$fcab_fd_rfolder = cli$fcab_fd_rtitle = cli$fcab_fd_rnumber = -
      cli$fcab_fd_rtype = #fcab_fd_scan_doc = #fcab_fd_scan_doc2 = ""
.if cli$fcab_fd_anchored_folder eqs "TRUE" then -
				get #fcab_folder_condition = "==" else -
				get #fcab_folder_condition = "="
.if cli$fcab_fd_anchored_title eqs "TRUE" then -
				get #fcab_title_condition = "==" else -
				get #fcab_title_condition = "="
!--------------------------------------------------------
.if cli$fcab_fd_title eqs "TEMPORARY READ FILE" then -
get cli$fcab_fd_stype = "DOKUMENT"
!--------------------------------------------------------
    .....
    
    I know this is not very nice, but I don't see were to put some ":U". Is
    there some better sugestions around?
    
    Felix

    I were able to answer myself to me question today. This is may of
    interest for those who are using Lotus on other languages than
    english. As you may know Lotus is only available on english under
    ALL-IN-1 V3.0. I were now able to install Lotus 1.02 on a geman brand
    new system. This may be even easier than using vmsinstal. I just did
    the following:
    
    - backup from an running Lotus system the following files:
      [allin1.l123_a1...]*.*,[allin1.site.l123_a1],
      sys$library:l123*.*,sys$message:l123*.*,
      sys$startup:l123_a1$startup.com
    
    - restore on the same directories on the target system
    
    - add a format record on the target system
    
    - perform the points described by Tony in this topic
    
    - and finaly search in all scripts and boilerplates of the Lotus
    elements for the occurance of ".type" and replace by "type:u". My problem
    was due to the fact that I forget to perform this last point on the
    boilerplates elements.
    
    Felix

Re: .34

>	LOTUS 1-2-3 for ALL-IN-1 V1.5 is on hold in the UK.
>
>	I believe Luis Lassala is dealing with this issue. I will chase
>	this up when I can get to talk to Luis next week
>
>	Cheers
>
>	Jill

Jill,

any more news on Lotus running under ALL-IN-1 IOS v3.0. We have a customer
who says there are still problems and it doesn't work properly!

Cheers,

mb

	This is now available and can be ordered from ESSB.

	Cheers

	Jill

Have the previous reported language problems between English & British etc.
now been resolved please ?

Pam

Pam

Yes the problems have now been resolved and the kit is available from ESSB.

Cheers

Jill