Monster Media 1993 #2/Image.iso/os2/wr07010.zip/WR07010.INF

OS/2 Help File | 1993-08-12 | 13KB | 292 lines

ΓòÉΓòÉΓòÉ 1. Installation ΓòÉΓòÉΓòÉ

Installation Prerequisites

 1. If you have DDCS/2 2.0 installed on your machine and you intend to install
    either the DB2/2 or DDCS/2 2.0 Select Pak then you must install both of
    them.  The DDCS/2 2.0 Select Pak has dependencies on the DB2/2 Select Pak
    and DDCS/2 2.0 will not operate correctly unless both Select Paks are
    installed.

 2. If you have just finished installing IBM DB2/2, IBM Lan Server/Requester or
    IBM CM/2, please shutdown and reboot your system before installing the
    DB2/2 Select Paks.  You will have to reboot twice, once after the
    installation of these products to process any locked files, and a second
    time before using the Select Pak(s) to process some remaining locked files.

 3. If you are planning to install IBM LAN Netview/2 or IBM CM/2 with DB2/2 on
    the same machine, you MUST install DB2/2 and the Select Paks before the
    other products.  Otherwise, DB2/2 may replace some common files that are
    shared among these products with an earlier version of the same files.
    This may cause undesirable results in the other products.

To install the Select Pak:

o Unzip the file WR07010.ZIP (use PKUNZIP2)
o Before starting the install you will need to know the drive that OS/2 is
  installed on and the drive where DB2/2 1.0 is currently installed
o Run WR07010.CMD in the directory where it was unzipped.

Note:  If you ran the install command file an OS/2 full screen, you will be
returned to the desktop upon exitting.  Be sure to return to the correct
session to proceed with the installation.

Installation Errors

If the Select Pak installation aborts with an error, then your DB2/2 system may
be left in an inconsistent state.  Possible causes for this are:

 1. Your OS/2 swapper file has become too big and there is no room for the
    temporary files that the install program needs to install.

 2. The file 'LSI.MSG' under x:\OS2\install (x is the boot drive) is locked and
    cannot be overwritten.  You need to reboot to unlock this file.

After you correct the cause of the problem, you must restart the Select Pak
installation and let it complete successfully in order to bring your DB2/2
system to a consistent state.

Re-installing DB2/2 Gold

If you ever re-install DB2/2 from the original installation disks, you should
first copy the following files from WR07010.PKZ to the DB2/2 1.0 installation
diskette 1:

o LSI.MSG
o IBMLANLK.SYS
o IBMLANLK.EXE

These changed files correct a problem in the original installation program
which causes the current date to be given to the files being installed instead
of leaving the date untouched.  This fix is required since the Select Pak
install program checks the existing file date before installing the Select Pak
files. If the date of the file already installed is later than the Select Pak
file date, then the install program will ask you whether this file should be
replaced or not. If you re-install from your original DB2/2 diskettes after the
date the Select Pak was finalized then you would be asked whether you want to
overwrite ALL of the Select Pak files (one at a time).  Changing the above
three files on your original DB2/2 diskettes will stop this from happening.


ΓòÉΓòÉΓòÉ 2. The DB2 Family Newsletter ΓòÉΓòÉΓòÉ

This is a bi-monthly newsletter that reports the latest news for the family of
DB2 products (DB2 and DDCS on all available platforms : OS2, AIX, MVS...)

If you are interested in receiving this newsletter, please mail or fax your
request to

 IBM Canada Ltd.
 Database Technology Planning
 31/110/895/TOR
 895 Don Mills Rd.
 North York, Ontario
 Canada, M3C 1W3

 Attn: L. G. Pedron
 Fax:  [phone]


ΓòÉΓòÉΓòÉ 3. Submitting Suggestions to IBM ΓòÉΓòÉΓòÉ

If you have any suggestions to enhance our products, there are two vehicles to
communicate your requirements to IBM.

o If your organization has an IBM Representative, discuss your requirements
  with your IBM Representative, and have them submit your requirements to the
  Database Technology Planning group at  TOROLAB2(DBMREQ).

o Or, send your detailed requirements to the following address:

  IBM Canada Ltd.
 Database Technology Planning
 31/110/895/TOR
 895 Don Mills Rd.
 North York, Ontario
 Canada, M3C 1W3

 Attn: L. G. Pedron
 Fax:  [phone]


ΓòÉΓòÉΓòÉ 4. What's Changed ΓòÉΓòÉΓòÉ

Return to the table of contents and choose one of the sub-branches of this
heading.


ΓòÉΓòÉΓòÉ 4.1. APARs ΓòÉΓòÉΓòÉ

The following changes have been made as a result of direct customer feedback.

Blocking Selects (APAR JR06827)

This fixes a problem that occurs when you initiate a blocking select against an
SQL/DS database using the command line proceesor, and then interrupt the select
and issue a second query.  The second query would then return rows continuing
from where the first query ended, rather than starting at the top of the table.

Running in a LAN security shell (APAR JR06867)

Previously, when running DB2/2 in a LAN security shell, the processes started
by database manager would take their authorizations from the shell rather than
the parent process.  As a result, the processes would not have privileged
status and would soon fail.  This has been changed so that the processes now
inherit the authorization of their parents.

This, however, creates a potential security risk.  If a remote user calls the
SQLEPROC, any dynamic link library files (.DLL) specified in the server library
path will be granted privileged authorization.  These files can then execute
any operations allowed with a privileged status.  Hence, you must be cautious
in choosing the dynamic link library files in your libpath.

Message Tokens  (APAR JR06918)

Message tokens are now being properly supplied for sqlcodes -1113, -1114, and
-1115.  Previously the tokens were missing from these messages.

Guest ID support not allowed  (APAR JR06975)

The LAN server product supports guest accounts. This means that a user can log
on to the server without having the USERID explicitly defined in UPM.  The user
is then given the same access as the guest userid.  The database manager,
however, does not support guest accounts.

If a workstation is configured as both a database manager server and a LAN
server, guest accounts will not be supported by the database manager.  If the
user attempts to log on to DB2/2 using the guest account, a message will be
displayed indicating that the logon failed.  The user will be prompted again
for another USERID and password.  If the user is already logged on (to the LAN)
as the guest USERID, the user will be prompted to logon using another USERID.

Backwards Table scan (APAR JR07102)

During a backwards table scan, it was possible that an incorrect number of rows
would be returned when there were gaps (deletions) among the slots of the
table.  The problem has been corrected.

Communication Performance (APAR JR07196)

Client/Server communications performance via NetBIOS is slower when receiving
data on clients or servers.

To improve the performance, the receive processing has been redesigned on both
the client and the server.

Thread Termination  (APAR JR07196)

When using NetBIOS, the DB2/2 cleanup thread can terminate prematurely. All
client/server operations continue to operate normally, however, and users will
not notice any symptoms.

The situation has been changed so that the thread will no longer terminate.

NetBIOS Communication Error (APAR JR07196/JR07197)

When connecting to a DB2/2 server, if the first data block arrives at a NetBIOS
client before the session is fully established, the client will receive a 30080
000a message, and the attempt to connect to the server fails.

The connection and first receive are now sequenced to ensure that the agent
cannot proceed with the first receive until the connection has been completely
established.

Note:  Application Programs will need to be rebound in order for these changes
to take effect.

Stopdbm Hang  (APAR JR07198)

"stop using database" followed by "stopdbm" causes a session hang when using
the Application Program Interface.

The code has been fixed to ensure that the processes involved in the "stop
using database" and the "stopdbm" will not compete for the same resources to
cause the deadlock.

FFST Trap (APAR JR07300)

When DB2/2 encounters an error, it calls FFST to log the error.  FFST requires
a lot of stack which in turn traps the application.

To fix this problem, DB2/2 now provides a larger stack for the application to
use while inside the engine.

MAXLOCKS  (APAR JR07310)

If MAXAPPLS is set to greater than 100, then MAXLOCKS is always set to one.
This has been changed so that the user can alter the maxlocks value.

However, in order to avoid excessive numbers of deadlocks, as you increase
MAXAPPLS, you should decrease MAXLOCKS.

Invalid Records (APAR JR07324)

Formerly, when a record was fetched that was not a user type, it was assumed to
be a control record.

Now, the record type is checked to ensure it is valid.  If it is not, a -902
"25" error message will be returned.


ΓòÉΓòÉΓòÉ 4.2. Other Changes ΓòÉΓòÉΓòÉ

DOS\WINDOWS applications using Japanese Code pages

It is now possible to have DOS and DOS Windows client applications runnning on
Japanese code page 932 connect to DB2/2 server databases created with the
Japanese code page 942.


ΓòÉΓòÉΓòÉ 5. Questions and Answers ΓòÉΓòÉΓòÉ

Q: I'm migrating from ES 1.0 to DB2/2 and received message "SQL5122N: Access to
the database was invalid because of a machine dependent check".  What is the
cause?

A: The database and database configuration file cannot be accessed because of
copy protection.  To correct this error, return to the original database and
modify the database configuration to turn the copy protection off, then create
a new backup which may be used to restore the database.

Q: What do I look for if my application ABENDED while connected to a database?

A: Look for a .TRP file in the x:\SQLLIB directory, where x is the installation
drive for DB2/2.  This file is created when DB2/2 ABENDs. The file contains the
user's stack and current register information.  Using this information you
should be able to find the problem If you are unable to resolve the condition
phone IBM support.

Q: What are the recommended trace settings for DB2/2?

A:

>sqltrc on -l 1000000 -e 10
>sqltrc dump trace.dmp
>sqltrc fmt trace.dmp trace.fmt

This procedure will create a 1 MB trace file which is used by IBM support to
help resolve any DB2/2 problems.  The TRACE.FMT file will be an ASCII file with
DB2/2 activity recorded during the problem recreation.

Q: I have printing problems after installing DB2/2 on OS/2 2.1.  I lose the
ability to print any file to a printer.  The file goes to the PM print spooler.
What is wrong?

A: As documented in the OS/2 2.1 README file, you must REMark the
RUN=C:\OS2\EPW.EXE and DETACH C:\OS2\EPWROUT.EXE 1 statements out of the
config.sys files and the DETACH C:\OS2\EPW.EXE and DETACH C:\OS2\EPWROUT.EXE -1
statements out of the startup.cmd file.  DB2/2 will install the FFST/2 code
(EPW) and update your config.sys file.

Q: When using DB2/2 with the Lotus Datalens product, I receive the following
message when attempting to connect to a DB2/2 database:
 Error Code sql0804N and you are unable to connect.
What is wrong?

A: Lotus 1-2-3 for OS/2 has a driver called DATALENS that allows you to bring
data from a database into your spreadsheet.

 This is a known problem with the Lotus Datalens product.  The fix should be
available from your local Lotus Technical Support centre in a SLIPSTREAM driver
package by the end of August 1993.