Vince Rosso@TRANSALTA
15/07/99 03:21 PM
Jason ... checked as you suggested but the files
$IMDIR/BUNDLE/DIR021/FNM04X.HLD do not exist on our media.
Vince (working with Harry)
(Embedded
image moved Jason Kravitz <Jason_Kravitz@TIVOLI.COM>
to file: 07/15/99 02:52 PM
pic05286.pcx)
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: Vince Rosso)
Subject: Re: Netview Migration to 5.1.1 and Frameworks
Harry/Vince - when I look at my WPREINST.SH script, I see the following
ln -s $IMDIR/BUNDLE/DIR021/FNM043.HLD $CLONEDIR/./bin/osf-axp/sapack
ln -s $IMDIR/BUNDLE/DIR021/FNM044.HLD $CLONEDIR/./bin/osf-axp/wserver_cli
ln -s $IMDIR/BUNDLE/DIR021/FNM045.HLD $CLONEDIR/./bin/osf-axp/wserver_gui
you don't see this in your WPREINST.SH? Perhaps you could try creating
these
links from the command line and then try the install again. I am not sure
why
your script would not have this. I am looking at an image server and not
the GA
CD so there might be some discrepancy but I don't think they would have
changed
this script for the CD image...
Jason
Vince Rosso <Vince_Rosso@TRANSALTA.COM> on 07/15/99 04:35:21 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Jason Kravitz/Tivoli Systems)
Subject: Re: Netview Migration to 5.1.1 and Frameworks
Vince Rosso@TRANSALTA
15/07/99 02:35 PM
Jason,
We have done essentially the same thing, the directory name we used are the
ones suggested in the installation manuals.
We get an error when we run the ./wserver -c /cdrom command because it is
unable to find the wserver_gui file. When I review the WPREINST.SH script,
the script we have does not create a soft link for this file. It does so
for HPUX. Solaris etc.. but does not seem to do so for the "tier 2"
vendors.
Thanks
Harry
(Who is working with Vince)
(Embedded
image moved Jason Kravitz <Jason_Kravitz@TIVOLI.COM>
to file: 07/15/99 02:03 PM
pic30372.pcx)
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: Vince Rosso)
Subject: Re: Netview Migration to 5.1.1 and Frameworks
Vince - where are you running the wpreinst.sh script from? Here is the
steps I
would take on my own DEC server... (assume Tivoli code is in a mounted
directory /cdrom)
mkdir /tmp/tivinst
cd /tmp/tivinst
/cdrom/WPREINST.SH
this comes back with the following message:
"to install, type ./wserver -c /cdrom"
so I type this: ./wserver -c /cdrom
and a setup GUI pops up...
are you getting this far?
Jason
Vince Rosso <Vince_Rosso@TRANSALTA.COM> on 07/15/99 02:33:41 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Jason Kravitz/Tivoli Systems)
Subject: Re: Netview Migration to 5.1.1 and Frameworks
Vince Rosso@TRANSALTA
15/07/99 12:33 PM
Jason ... we are performing our install on Digital UNIX v4.0d and in
English. Following the suggested install sequence we first run
wpinstall.sh. The second step is to run wserver, but it returns the error
message: "wserver. /usr/local.Tivoli/install_dir/bin/osf-axp/wserver_gui:
not found" It appears that when we run the wpinstall.sh that it is not
creating the softlink required to osf wserver.gui or the libraries. Hope
I've explained this so it makes sense.
(Embedded
image moved Jason Kravitz <Jason_Kravitz@TIVOLI.COM>
to file: 07/15/99 11:45 AM
pic11480.pcx)
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: Vince Rosso)
Subject: Re: Netview Migration to 5.1.1 and Frameworks
Let's back up a bit then... where is the 3.6 installation failing? You
mention
the scripts not being complete? Give us some more information about this -
what
level of DEC are you using? Are you running in English or another locale
(I am
assuming English since you are going to install NetView)
Jason
Vince Rosso <Vince_Rosso@TRANSALTA.COM> on 07/15/99 01:21:51 PM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Jason Kravitz/Tivoli Systems)
Subject: Re: Netview Migration to 5.1.1 and Frameworks
Vince Rosso@TRANSALTA
15/07/99 11:21 AM
The software was ordered specifically for the Digital UNIX install so I'm
assuming they shipped the proper software. Is there some way to confirm
what you mention? Another user has replied that our version 3.1.3 is not
Y2K compliant, this being the case will have to try and resolve the v3.6
install problems. Thanks!
(Embedded
image moved Jason Kravitz <Jason_Kravitz@TIVOLI.COM>
to file: 07/15/99 09:53 AM
pic15491.pcx)
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.ucsb.edu>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: Vince Rosso)
Subject: Re: Netview Migration to 5.1.1 and Frameworks
Vince - keep in mind Digital UNIX is a Tivoli Tier2 platform - therefore
you
must use a different Framework install image (than you would use for AIX or
Solaris) make sure you are installing from the Tivoli Tier2 framework CD's
Jason
Vince Rosso <Vince_Rosso@TRANSALTA.COM> on 07/15/99 10:50:53 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Jason Kravitz/Tivoli Systems)
Subject: Netview Migration to 5.1.1 and Frameworks
Vince Rosso@TRANSALTA
15/07/99 08:50 AM
We are currently installing Netview on a Digital (Compaq) UNIX box
upgrading from v4.1. We are unable to install Frameworks 3.6 as the
scripts do not appear complete the Digital UNIX install. We worked around
this by installing Frameworks 3.1.3. Does anyone know if there are
problems running with this version of Frameworks? Are there problems or
Y2K compliancy issues with this version? Our primary reason for doing
the 4.1 to 5.1.1 upgrade is for Y2K compliancy reasons and our customer
requires the reassurance that any new software installed is Y2K compliant.
Thanks!
pic15491.pcx
Description: Binary data
pic11480.pcx
Description: Binary data
pic30372.pcx
Description: Binary data
pic05286.pcx
Description: Binary data
|