home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
vi112sv.doc
< prev
next >
Wrap
Text File
|
1996-05-21
|
10KB
|
243 lines
VisualInfo 1.1.2 Fix Package -- 15 May 1996
This fix package contains of all the APAR fixes for the VisualInfo version 1.1.2
of Library Server, Object Server, and Library services. The fix package consists
of one file(VI112SV.ZIP). Please execute the file in a directory of your choice
on your code server to extract the files.
For example:
Go to a drive D: where D: is a drive on the Code Server
Make directory VIFIXPK
Change directory to VIFIXPK
Copy VI112SV.ZIP file to this directory
Type PKUNZIP2 -d -o VI112SV.ZIP to extract the fix files.
The following files are in this package broken down by components.
Files for Lan Based Object Server
---------------------------------
Length Date Time Name
------ ---- ---- -----
87130 5-15-96 12:00 frnolbmn.exe
2620 5-15-96 12:00 frnolbdb.cmd
2899 5-15-96 12:00 frnolbv2.cmd
54362 5-15-96 12:00 DLL\frnolbcm.dll
32346 5-15-96 12:00 DLL\frnopddm.dll
82767 5-15-96 12:00 frnoliis.exe
25933 5-15-96 12:00 DLL\frnoliia.dll
3183 5-15-96 12:00 DLL\frnoliic.dll
To install the fix for the Object Server, perform the following steps:
1) Shutdown the VisualInfo Object Server.
2) If you would like, backup the files listed above,
except the "frnollbv2.cmd", since this file is only for
migrate object server to DB2/2 Version 2.1.1 to use.
To do this, you can rename the files in their subdirectories
or make backup versions of the directories and copy all the
files to these new directories.
3) Type "SET FRNROOT" to determine your FRNROOT directory and make it
your current directory.
4) Copy the DLL files to the FRNROOT\DLL and the two command files and the
EXE files to FRNROOT directory from the corresponding Code Server
directories where the files for the fixpack reside.
Apar fixes for the Object Server:
=================================
IR28802: Destager/Migrator now do write verification for all file copies
Also fixed Overflow volume processing to correct cases where only
one object was stored on each overflow volume.
IR30772: Fixed problem with FRN9821 TIMEOUT messages due to erroneous processing
in 3995 Device Manager during platter queries. The support fixed the
Virtual Device Option toleration for 3995 jukeboxes.
IR31371: Fixed Database BIND bug that caused subsequent migration problems due
to wrong date/timestamps. The solution involved adding /ISO to
database BIND command.
IR31565: Corrected case where Oject Server Migration hangs library server if
the number of requests reaches 65K and the Library
Server never got completely full during this cycle.
Info For DB/2 2.1 Migration for LBOS:
-------------------------------------
Before installing VisualInfo, you must apply DB2/2 CSD number
8090, after installing DB2/2 2.1.1. Then you need apply the fix
for APAR JR09065. You can get CSD 8090 and the APAR fix in the
subdirectories of "ftp.software.ibm.com/ps/products/db2/fixes".
Fix includes a command file to update the APPLHEAPSZ for the
Object Server Database on DB2 V2. This corrects the problem where
the Object Server fails to initialize under DB2 V2.
Info For Upgrading to VisualInfo V2.1
=====================================
After installing the VisualInfo V1.1.2 Fix Package, users who
want to upgrade to VisualInfo V2.1 may do so by following the
migration procedures provided with this new version.
For users who have also upgraded to DB2/2 V2.1.1, the only
modification to those procedures is in the Database migration
procedure. As described in the OS/2 README on the V2.1 product
CD ROM, two database configuration file parameters need to be
altered prior to migrating a large Object Server Database.
The procedure in the README is oriented to the DB2/2 V1
Configuration Tool. Users with DB2/2 V2.11 will need to use
the Database directory tool to modify the parameters.
After running the Object Server migration utility, restore the
database configuration file parameters for the object server
to their original values.
Files for Lan Based Library Server
---------------------------------
Length Date Time Name
------ ---- ---- -----
370298 5-15-96 12:00 DLL\frnollls.dll
129658 5-15-96 12:00 DLL\frnollio.dll
144417 5-15-96 12:00 BIND\frnpllio.bnd
61120 5-15-96 12:00 BIND\frnpllqx.bnd
82767 5-15-96 12:00 frnoliis.exe
25933 5-15-96 12:00 DLL\frnoliia.dll
3183 5-15-96 12:00 DLL\frnoliic.dll
To install the fix for the Library Server, perform the following steps:
1) Shutdown the VisualInfo Library Server.
2) If you would like, backup the files listed above.
To do this, you can rename the files in their subdirectories
or make backup versions of the directories and copy all the
files to these new directories.
3) Type "SET FRNROOT" to determine your FRNROOT directory and make it
your current directory.
4) Copy the two DLL files to the FRNROOT\DLL and the two bind files to
FRNROOT\BIND directories from the corresponding Code Server directories
where the files for fixpack reside.
5) Bind the Library Server Database using the Library server bind utilitiy
in the VisualInfo utilities folder.
Apar fixes for the Library Server:
==================================
IR30898 - SYS3175 in FRNOCLLCH.EXE during LS init when 33 or more attributes
are defined to an index class. The Limit now is 50 due to client
restriction.
IR31922 - MSGFRN6056 - LS function 7156-SQLCODE501. Fixed the Cursor problem
with LLSEXECUTESTATICQUERY().
Files for Library Services
--------------------------
Length Date Time Name
------ ---- ---- ----
51519 5-15-96 12:00 DLL\frnolcli.dll
22998 5-15-96 12:00 DLL\frnolmlc.dll
72822 5-15-96 12:00 frnolmld.exe
55926 5-15-96 12:00 frnolmlk.exe
82767 5-15-96 12:00 frnoliis.exe
25933 5-15-96 12:00 DLL\frnoliia.dll
3183 5-15-96 12:00 DLL\frnoliic.dll
To install the fix for the Library Services, perform the following steps:
1) Shutdown the VisualInfo of your computer.
2) If you would like, backup the files list above.
To do this, you can rename the files in their subdirectories
or make backup versions of the directories and copy all the
files to these new directories.
3) Type "SET FRNROOT" to determine your FRNROOT directory and make it
your current directory.
4) Copy the DLL files to the FRNROOT\DLL and the EXE files to FRNROOT
directory from the corresponding Code Server directories where the
files for the fixpack reside.
5) Make sure you need to copy the isolator files(frnoliia.dll, frnoliic.dll
and frnoliis.exe) on both Library Server, Object Server and Client machines.
APAR fixes for the Library Services:
===================================
IR29975 - MSGFRN6728A on the CLIENT during Logon when the CONFIG.SYS
setting FRNDISP=NO. Now if you have FRNDISP=NO in CONFIG.SYS
it will works ok.
IR31170 - Timestamps in expired utilities always 5 + GMT. It is now set by
adding the value determined by the TZ Variable set in the
CONFIG.SYS file to GMT.
IR31087 - MSGFRN9093A sometimes followed by MSGFRN9006A, not limited to
one server and sometimes causes server hang.
IR30634 - When using the VI V1.12 CLIENT with VI/MVS, keyfields created as
decimal are not translated correctly to the Library Server.
Now pass server Floating Point representation back in the init
client reply message so that daemon can preperly know how to
convert.
IR32143 - FRN6728 or FRN8500 when isolator starts, sockets are loaded
even if the network is APPN.
Apar fixes via Documentation
=============================
IR28798 - You cannot delete Database Index Class index even if the Index Class
Table has Data. This was stated wrongly in the System Adminstration
and Operation Guide. You can delete the index.
IR31425 - Password Change made via system Adminstration is not successful if
User is logged on. The change password request is ignored if the
User is already logged on.
IR30458 - The max duriation for password is stated 32767 in System Admin and
and Operation guide. The correct value is 10,000.
IR30423 - When defining new nodes, APPC is not an option. This has fixed in
VisualInfo Version 2.1.
IR30636 - System defined attribute using SimLibSerach API on the VI
Application Programming Reference is not clear. Document
has changed to state clearly for all the system-defined
attributes.
IR31485 - What to do when you replace or repartition the hardrive that contains
LBOSDATA.
To have the Object Server recognize the new or changed
volume:
a. Using DB2. Query Manager or some other method, change
the following columns in the BASE_VOLUMES table to
zero (0):
VOL_SERIAL = 0
VOL_SIZE = 0
VOL_FREESPACE = 0
Changing those columns to zero forces the Object
Server to pull the information from the new drive or
partition and place the new values in the
BASE_VOLUMES table.
b. Start the Object Server.
The first time the Object Server tries to write or
delete an object, it will pull the information from
the new drive or partition and place the values in
the BASE_VOLUMES table.