T.R | Title | User | Personal Name | Date | Lines |
---|
2642.1 | No bugs in Vid's code - ALLIN1/NOCUSTOM? | AIMTEC::WICKS_A | on the Streets of San Francisco | Fri Apr 30 1993 00:34 | 9 |
| Ann,
On my system (v3.0-1) the file VTX.COM has not been changed since the
legendary Mexican himself created it in October 1986 amd so I don't see
who MJG is - is this is a customisation?
Regards,
Andrew.D.Wicks
|
2642.2 | VTX owned by our DPC | AIMTEC::WICKS_A | on the Streets of San Francisco | Fri Apr 30 1993 00:39 | 12 |
| Ah now STARS will talk to me I see that ALL-IN-1 does not like VTX V5.*
unless you apply the recommendations of our Dead Products Consultant
see the STARS article entitled...
Cannot Access VTX From ALL-IN-1 After VTX Upgraded to Version 5
Sorry I forgot that VTX came under the realm of 'dead products' and
didn't have that database open!
regards,
Andrew.D.Wicks
|
2642.3 | I just wrote this artcle the other day | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Fri Apr 30 1993 14:25 | 97 |
| TO: _PAND::EXPRESS
SUBJ: {**} ..OA_VTX 204951 tech-rev_badge CR
Making unsupported VTX versions work with ALL-IN-1 version 3.0
ALL-IN-1 IOS Server for VMS versions 3.0, 3.0-1
OpenVMS version 5.4-3
ALL-IN-1 IOS version 3.0 and 3.0-1 are not compatible with version
5.x of VAX VTX.
The following files, contained within the VAX VTX installation kit,
are provided to bridge the compatibility gap:
VTX$LIBRARY:VTXALLIN1.INI
VTX$LIBRARY:VTX.COM
VTX$LIBRARY:VTX.SCP
VTX$LIBRARY:OA$APPL_INTMENU.SCP
Per the VAX VTX installation guide, copy VTXALLIN1.INI to
SYS$COMMON:[VTX$LIBRARY]VTX.INI.
The other 3 files can be placed in the correct locations, by
performing the following ALL-IN-1 operations, from within the
MANAGER (or any other appropriately privileged) user account in
ALL-IN-1 IOS.
Through ALL-IN-1 IOS customization managament, the elements must be
modified, by using the following steps:
CM{CR} go to the Customization Management
ABE{CR} use the Access Base Elements option
SEL{CR} use the SELect option
VTX{TAB} the name of the element
COM{CR} the type of element
1{CR} choose the first one in the list
CO{CR} use the COpy to developement option
Need to modify for VTX version 5.x{CR}
provide a reason for copying the element
{KEY 0} go back to Customization Management
E{CR} use the Edit option to modify the file
(delete the complete file, include the new VTX.COM then file it)
MLA{CR} use the Move to Live Area option
It's ready for use{CR} provide a reason for moving the element
(repeat for the next element)
ABE{CR}
SEL{CR}
VTX{TAB}
DO{CR}
1{CR}
CO{CR}
Need to modify for VTX version 5.x{CR}
{KEY 0}
E{CR}
(delete the complete file, include the new VTX.SCP then file it)
MLA{CR}
It's ready for use{CR}
(repeat for the next element)
ABE{CR}
SEL{CR}
OA$APPL_INTMENU{TAB}
DO{CR}
CO{CR}
Need to modify for VTX version 5.x{CR}
{KEY 0}
E{CR}
(delete the complete file, include the new OA$APPL_INTMENU.SCP
then file it)
MLA{CR}
It's ready for use{CR}
Through ALL-IN-1 IOS customization managament, the elements must be
processed, by using the following steps:
AM{CR} use the Application Maintainer option
PME{CR} use the Process marked elements option
{CR} produce an index of all marked elements
ALL{CR} to select all the marked elements
XPR{CR} to process all the marked elements
{KEY 0} to escape from the marked element index
{CR} tread informational and warning messages
Through ALL-IN-1 IOS customization managament, the elements must be
compiled into the customized TXL, by using the following steps:
SM{CR} go to the system management subsystem
CSZ{CR} use the System customization management option
CCM{CR} use the compile and install site library option
Y{CR} to compile the CDS TXL
Now any users starting a new ALL-IN-1 IOS session, will be able to
use the IM VTX option to enter VTX.
//VTX
|
2642.4 | VTX is NOT dead and IS supported! | RDGENG::POVEY | Tom, REO-D3/3G, DTN: 830-4263 | Fri Apr 30 1993 15:20 | 26 |
| I'm working on improving the usefullness of VTX in the UK. I've just
started working on some improvements for using VTX from ALL-IN-1.
I'd just like to correct some comments in these replies:
o VTX is not a "dead product" -- it is very much alive and well but
development have been relocated which has slowed down the upcoming release
which is VTX V5.2 or VTX/TR 1.1.
o VTX is NOT unsupported. Support is, electronically, via the VTX_technical
notes conference which has moved to VIA:: The engineers have responded to
a number of ALL-IN-1 related questions there and have recently added a new
feature to VTX V5.2 to help ALL-IN-1 users.
However, there has been a lack of coordination between VTX and ALL-IN-1
engineering groups which we are now working on fixing.
I am also looking at some short-term, quick improvements to the use of
VTX from ALL-IN-1 such as direct printing of VTX pages to ALL-IN-1 queues
and saving to the file cabinet.
Please check out the vtx_technical notes conference for further information
on VTX and ALL-IN-1
Tom
|
2642.5 | noted | AIMTEC::ZANIEWSKI_D | Why would CSC specialists need training? | Fri Apr 30 1993 19:44 | 10 |
| Hi Tom,
I see room for improvement in the draft copy of my article. I
meant to communicate, not that some versions of VTX are
unsupported, but that some ALL-IN-1/VTX combinations are not
documented as supported, per the SPD/SSA.
Thanks for the comment. Clarity is most important.
Dave Zaniewski
|
2642.6 | thos protections will get you every time! | ANGLIN::HARRISA | user vicious | Mon May 03 1993 23:08 | 11 |
| well...after a much deserved rest on friday, i'm back.
i looked at the STARS atricle in .1 and the line that it says to change
doesn't exist in the VTX.COM for VTX 5.1. VTX.COM has changed
dramtically since the mexican wrote it (he wouldn't recognize!)
so, i followed the DPC's article in .3. worked fine, but I needed to
change the protections. after i remembered to set the protection ton
the VTX$LIBRARY.DIR things worked okey-dokey.
ann
|