These fix levels can only be applied to IDS 1.0.2 servers. They
CANNOT be applied to IDS 1.0.0 or 1.0.1 servers.
You must apply all fixes from an OS/2 workstation while IDS is
running. All IDS Services and Workstations must be reset for the
fixes to take affect.
Also, ensure all temporary fixes have been removed, this pertains
to any DLLS that were added to the 'nodeovly' directory or using
the /s parameter. Please contact the Technical Support Engineer
that supplied the temporary fix to verify that this needs to be
done.
Should you have any problems applying a fix level, please contact
Technical Support, 1-800-237-5511.
Download the desired ZIP files. Each one should be downloaded
into a separate directory.
Extract the files in the ZIP file by typing its filename. For
example, type "jo7b6fix". A new directory named "fix" is
created in your current directory.
Read the UPGRADE.TXT file that is located in the new directory.
This file contains additional instructions you might need to follow
before you begin the upgrade, depending on whether or not you have
changed the desktop system defaults or any conversion tables.
This will ensure your changes are not lost.
If IDS services are not already running, click on the IDS icon
on the OS/2 desktop. Wait for the services to start completely.
Type "cd fix" to change to the fix directory.
In the OS/2 window, type "upgrade". You might be prompted for
the directory where the IDS software is installed on your
workstation. The fix application compares the timestamps of all
files within its domain with files present on the Primary File
Server. Messages are displayed for each file, stating that your
version is either newer, older, or matches, the upgrade file.
These messages are also saved in a log file in the directory
where the IDS software is installed and is called IDSFIX.LOG
(for a fix level) or IDSUNDO.LOG (for an undo level).
Type the system password when you are prompted to do so.
Messages are displayed informing you that the files are being
replaced.
NOTE: If you enter the wrong password, you will be given another
chance to enter the correct password. If you again enter the
wrong password, the upgrade will not occur and you will need to
restart to the previous step, type "upgrade".
Apply any additional fixpacks using the same procedure.
Messages added to the log file will be appended to the end of
the existing log file.
After all fixpacks are applied, you must reset all workstations
and services for the updates to take affect. To do this:
Log on to the IDS Desktop.
Open the SA Tool.
In the SA Tool, select "Network Command" from the "Service Type"
menu.
Click on the "Connect to Service" button.
Type your password when prompted. You are now in the "Network
Commands" menu.
Click on the "Reset All Workstations and Services" button. The
workstation you are using will reset and all services will
recycle. Monitor all network services to ensure that they
reset.
IDS is now upgraded to the new fix level.
1.) DB2 DISBIND
For some fix levels, a DB2 bind may be required. Check the details
under "Available Fix Levels" below. If a bind is required, follow
these steps on your OS/2 database gateway:
a. Ensure that the OS/2 database gateway has been
restarted
after the fixpack was applied.
b. Connect to the target database you are using.
Ex1. db2 connect to TARGETDB
Ex2. db2 connect to TARGETDB
user USERID using PASSWORD
c. Do the DB2 BIND. There are some syntax differences
for DB2
on different platforms.
Please reference the DB2 manuals.
i) Example for DB2/MVS or
DB2/400:
db2 bind c:\$IDS_HOME\exe\m4esd.bnd
action replace blocking
all collection USERID grant
public isolation NC
Note: Use "add" instead
of "replace" when doing the BIND
for the first time.
ii) Example for DB2/2 or
DB2/UNIX:
db2 bind c:\$IDS_HOME\exe\m4esd.bnd
blocking all grant
public isolation
d. Do DISBIND on the local database.
Change directory to \$IDS_HOME\exe
then do the DISBIND.
Ex. disbind sample cs
Note: The sample is the
local database name.
2.) Windows NT/95 Console Window enhancement in fixpack jw95f.
A change has been made in the starting of IDS and how the console window
will now be displayed. The change is by default all console windows
on
Windows NT/95 machines will now come up minimized. If you would like
to
have the console window display, you will need to add the following
line
to the idsdsk.bat file on the machine. Enter SET MET_CONSOLE_MAXIMIZED=YES.
3.) Enhancement to the PC Application tool to support $$$ token for
RDS products XLaunch
and Send Message.
4.) When using the PC Directory tool, a user must specify a NAME.EXT
as the destination
region name on the arrow in a Capsule tool. The extension must
match the conversion type
in the PC Directory tool. If no name is provided, the Capsule
will stop running and an
error message will be posted.
5.) The PC Directory tool cannot be copied directly to a placeholder
in a Capsule. The
work around is to copy the PC Directory first to the desktop or inside
the Capsule area,
then copy it to the placeholder.
For each fix level, there is a corresponding undo level available
in a self-extracting ZIP file. For example, the undo level for
jo7b6fix.exe is jo7b6und.exe. When you apply a fix level undo,
your system will return to the IDS 1.0.2 base level. You can then
apply any of the other available cumulative fix levels to move your
system to the desired level.
The steps for applying a level undo are the same as the steps for
applying a fix level. You will need 30 megabytes of free hard disk
space to download and extract the undo file.
Available fix levels for IDS 1.0.2
Each fix level and corresponding undo is located in a directory
with the same name as the fix level. Within each directory, the
FIXES.TXT file lists the problems that are fixed in that level.
The following fix levels should be installed together:
joI01 for IDS 1.0.2 OS/2 Servers and Workstations
jwI01 for IDS Windows Workstations
jgI01 for IDS Messages
NOTE: If you have IDS 1.0.0 Unix database gateways, you must also
install "gd786" from the ...\v101\dbgw directory.
For IDS 1.0.2 OS/2 Servers and Workstations:
For IDS 1.0.2 Windows Workstation:
For IDS 1.0.2 Messages:
For IDS 1.0.2 ODAS SA Console: