Conference iosg::all-in-1_v30

2906.0. "ALL-IN-1 and VTX integration" by RDGENG::POVEY (Tom, REO-D3/3G, DTN: 830-4263) Wed Jun 23 1993 15:45

VTX T5.2-5 is now available from VIA::$PROJ4:[VTXT52_KITS]. This is also
known as VTX/TR T1.1-5.

This contains the first stage of improved integration with ALL-IN-1.

Please report any problems to: VIA::VTX_X50_QAR -- the EFT notes conference
For technical discussions: VIA::VTX_TECHNICAL -- the main VTX notes conference


The following extract from the release notes describes what is contained
in FT-5 for ALL-IN-1:


        3.8.1 ALL-IN-1 Integration

        3.8.1.1 Integrating VTX with ALL-IN-1

              After installing VTX, the ALL-IN-1 system manager should
              perform the following steps:

              1. copy VTX.SCP, and OA$APPL_INTMENU.SCP to the site TXL
                 area and re-compile the TXL.

              2. copy VTX.COM to OA$LIB. This will ensure that all
                 ALL-IN-1 users will have the ALL-IN-1 key bindings when
                 they run VTX from within ALL-IN-1.

        3.8.1.2 VTXALLIN1.INI file

              Following discussions with the ALL-IN-1 engineering group,
              the VTXALLIN1.INI file has been revised. The changes ensure
              that those functions that VTX supports which are familiar
              to the ALL-IN-1 user, are initiated by the key or keys that
              the ALL-IN-1 user would expect to use. The ALL-IN-1-style
              key is now placed first in the list of key bindings in
              the .ini file so that it will be displayed by the VTX help
              mechanisms. The keys involved are:

              o  The Exit-Screen function is the keypad0 key and the F14
                 key.

              o  The Exit function is F10.

              o  The Main function is F9.

              o  The Next-Choice and Previous-Choice functions are PF1
                 Next and PF1 Prev respectively

              o  The Find function is the Find key.


              The special VTX functions for ALL-IN-1 are:

              o  Call the interrupt menu: PF1-i

              o  Call the scratchpad menu: PF1-*

              o  Write the current screen to the scratchpad: PF1-p

              Also, the prompt is now: A1VTX Command> so that the user
              has confirmation that they are using the ALL-IN-1 key
              definitions.

        3.8.1.3 Writing to the ALL-IN-1 scratchpad

              ALL-IN-1 SCRATCHPAD-COPY now appends to the SCRATCHPAD file
              rather than starting a new (PASTE.TMP). If the customer
              site would like it to always create anew, this can be done
              by deleting PASTE.TMP in the command script serving the
              call (VTX.com)

              VTX now writes a "NEW PAGE" marker (form-feed character)
              before it appends to the scratchpad. Any non-printable
              characters are converted to printable characters. A
              problem has been identified with the way VTX writes to the
              scratchpad. This problem only shows up if the scratchpad
              is created by ALL-IN-1 (or an ALL-IN-1 application). The
              workaround in ths field test is to have VTX.COM perform
              a CONVERT/FDL step on any existing scratchpad before
              calling VTX. ALL-IN-1 system managers should be aware
              of this so that if other applications have problems with
              the scratchpad, then they can investigate VTX.COM. A more
              complete fix is expected later.

        3.8.1.4 Using the interrupt and scratchpad menus

              There was a problem in that VTX called the appropriate
              scripts using a hard-coded OA$DO: prefix. This has now been
              removed.

        3.8.1.5 The VTX Welcome Screen

              By default, the VTX client will display a "welcome" screen
              to the user while it is attempting to connect to the home
              server. If your system has a local server, this can confuse
              users because the welcome screen appears only briefly and
              is then replaced by the main menu before the users have a
              chance to read it.

              To remove this "welcome" screen, rename the vtx_welc.txt
              from the language specific directory. For example for
              english language users:

              $RENAME/LOG VTX$LIBRARY_EN_US:VTX_WELC.TXT VTX$LIBRARY_EN_
              US:VTX_WELC.UNUSED

              The logical names for other languages are :

              o  Italian : VTX$LIBRARY_IT_IT
              o  Spanish : VTX$LIBRARY_ES_SP
              o  French : VTX$LIBRARY_FR_FR
              o  German : VTX$LIBRARY_DE_DE
              o  Dutch : VTX$LIBRARY_NL_NL
              o  Swedish : VTX$LIBRARY_SV_SE

    Tom,
    
    I'm pleased to se this closer integration between ALL-IN-1 and VTX
    restored, but if you have any input to the release notes, please get
    them fixed:
    
    <<<< 1. copy VTX.SCP, and OA$APPL_INTMENU.SCP to the site TXL
    <<<<    area and re-compile the TXL.
    
    <<<< 2. copy VTX.COM to OA$LIB. This will ensure that all
    <<<<    ALL-IN-1 users will have the ALL-IN-1 key bindings when
    <<<<    they run VTX from within ALL-IN-1.
    
    Please tell the customer to use Customisation Management (and explain
    exactly how!) to add/update these files. I don't think it's enough to
    say the "site TXL area" for example. Also, they only need to compile
    the CM TXL.
    
    Or should I report this to them directly?
    
    Graham

    Tom,
    
    Also isn't it possible that a customer may have customised
    OA$APPL_INTMENU.SCP or it may have been in an  ALL-IN-1 patch 
    just placing a copy over the top of there's isn't a very nice thing to
    do to a customer is it?
    
    Regards,
    
    Andrew.D.Wicks

        As the DPC in the US CSC that gets all the calls about the errors
        in this part of the VTX documentation, I couldn't agree more.  If
        the VTX group needs help in learning how to do it right things with
        ALL-IN-1, there are plenty of capable people available.
        
        Dave Zaniewski

re: .1, .2, .3 -- Thanks!

If someone would care to write down exactly what we should say, then send
it to me and I will get it into the next set of release notes and,
eventually, the documentation.

Tom

VTX famously doesnt come with Customisation Management history and elements. 
Is it known when that aspect of integration with ALL-IN-1 will get fixed?

tta rv  Tuesday 29-JUN-1993 17:48 

re: .-1

I need an ALL-IN-1 person to explain what VTX should do/say regarding CM.

Tom

    tom,
    
    should be lots of them in DEC PARK II
                  
    regards,
    
    Andrew.D.Wicks

re: .6

>>>I need an ALL-IN-1 person to explain what VTX should do/say regarding CM.

Tom,
We have loads of code to do just this in the patcher. Call me...
tta rv  Thursday 8-JUL-1993 17:39 

    Just installed VTX V6.0 and I didn't see any CM instructions.
    Have I missed something ?

        Probably not.  I'd suggest raising a SPR against VTX.  The version
        5.* SPR's I've raised, have migrated to the bottom of the "fix"
        list by now.
        
        Dave Zaniewski

    I believe that the VTX engineer mentioned in .6 is now no longer with
    the company so I've no idea who owns the interface anymore.
    
    All questions on VTX should probably start with the ALL-IN-1 Product
    Manager Dave Holt @REO.
    
    regards,
    
    Andrew.D.wicks

    
    Is VTX V6.0 supported with IOS V3.0A ???
    
    If not, what are the problems/restrictions etc.
    
    Thanks,
    
    Andy
    CSC Sydney