David,
There is a known problem with NetView 6.x with Framework 3.7.1. I have
attached the workaround.
Cheers,
Jane
--
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2002 Jane Curry <jane.curry AT skills-1st.co DOT uk>. All rights
reserved.
There is apparantly an error in Framework 3.7.1. This error corrupts an
environment variable sent to the scripts that do installation work. The
environment variable's value ends up with an extra space character
appended to it, rendering it corrupt.
I was able to circumvent the problem, and install the 6.0 product, then
repeat the process and install the 6.0.2 patch.
Here's how:
Copy the cdrom to disk using the Framework's wcpcdrom command:
wcpcdrom -c <cdrom directory> <disk directory>
You'll need enough disk space to hold the entire cdrom contents... about
700Mb. You can usually define a logical volume (aix) to work with
temporarily, and delete it when you are finished with it.
After you have the cdrom on disk, edit the .IND file that corresponds
to what you are installing-- for example, if you are installing the
NetView for UNIX Server, edit file NVSERV50.IND.
-
The environment variable NetView installation is receiving corrupt is
"ThisFpk". If it is the *LAST* environment variable on the lines in the
.
.IND file before the ":" (colon), it will be corrupted unless you edit
the line in the .IND file. Edit it by adding an additional environment
variable and value after it. For example, if you see:
...;ThisFpk=xxxxx;:...
change it to:
...;ThisFpk=xxxxx;Place=holder;:
-
Be careful editing the IND file not to add spaces or control characters
or break lines.
-
There are occasions of Framework environment variables at the ends of
lists that don't seem to cause problems like ThisFpk does for NetView.
-
Remember you only have to add a variable=value if you find "ThisFpk" at
the end of a list.
-
You have to make the change in one place in the IND file for the 6.0.2
server patch, and several places on the 6.0 server base IND file.
-
The 6.0.2 server patch IND file is named NVS50001.IND
-
After you successfully install the server, you can remove the cdrom
files from disk, then copy the patch cdrom to disk to edit it, then
install the patch.
-
Be sure to point the Framework product/patch install to the files on
disk, rather than the cdrom. Double check it!!
-
Hope this works for you and is not too confusing... Please let me know
your success or questions!!
Regards,
Geo.
PRE-SCREEN NO.= RSCP= RS371
ERROR DESCRIPTION:
The NetView product
cdrom IND files contain specifications
of environment variables to be passed
to the cdrom-based unix scripts that
perform installation duties. The unix
scripts are failing during
installation because they are getting
one of the environment variables
corrupted. This is true for both the
base product and patch cdroms. The
list of environment variables in the
IND files are passed to the scripts
intact except for the last variable in
the list. It's value has a space
character added to the coded value,
rendering the value corrupt. This
does not occur with Framework releases
prior to 3.7.1.
LOCAL FIX:
Copy CDROM to disk using wcpcdrom command. Edit NV*.IND file
to add additional environment variable=value pair to lines that
contain ';ThisFpk=XXXX;:'
example, ....;ThisFpk=XXXX;FOOBAR=foo;:
This is only a Framework 3.7.1 problem. This is also Framework APAR
IY18735.
.
The critical symptom is the following two error messages found in the
"last few messages of the error log" in the tivoli.cinstall of the
failed NetView installation:
.
ERROR in FilePack.
Bad value $ThisFpk = base
.
The cause is basically this:
.
The NetView product cdrom IND files contain specifications of
environment variables to be passed to the cdrom-based unix scripts that
perform installation duties. The unix scripts are failing during
installation because they are getting one of the environment variables
corrupted. This is true for both the base product and patch cdroms.
The list of environment variables in the IND files are passed to the
scripts intact except for the last variable in the list. It's value has
a space character added to the coded value, rendering the value corrupt.
This does not occur with Framework releases prior to 3.7.1.
.
To circumvent this problem, the basic steps are:
.
1. copy or link cdrom to disk
2. edit *.IND file on disk for component being installed
3. install component from disk
.
The details:
.
1. copy or link cdrom to disk.
.
The copy can be done using Framework's wcpcdrom command line utility.
.
wcpcdrom -c <cdrom dir> <disk dir>
.
Be sure you have enough disk space. Have at least 700Mb available.
.
An alternative is to build symbolic links on disk to every file and
directory on the cdrom and then copy the *.IND file to be edited to
disk. This takes up very little disk space.
.
The following commands will set up links to all cdrom files, remove the
one link to the *.IND file to be edited, copy the *.IND file to disk,
and start vi for editing.
.
The current directory (PWD) is assumed to be . (dot). The links go
here.
.
The cdrom is assumed to be mounted on /usr/<cdrom>. "<cdrom>" in the
commands below should be replaced with whatever name you are using for
your cdrom!
.
Again, this is symbolized by the "<cdrom>" below.
.
Again, the symbolic links will go into the current directory (PWD), or .
(dot).
.
Note the example below shows NVSERV50.IND which is the NetView Server
6.0 base product fresh installation *.IND file. All other *.IND file
names are described below.
|
