SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-Programming Mailing List Archives

Return to [ 21 | September | 1998 ]

<< Previous Message << >> Next Message >>


Date: Mon, 21 Sep 1998 10:11:17 PDT
From: MDINET!ELMONTE!TomE@mdipo.attmail.com (Emerson, Tom # GPS-MDI)
Reply-To: scoug-programming@scoug.com
To: scoug-programming@scoug.com (internet!scoug.com!scoug-programming)
Subject: SCOUG-Programming: Need help selec

Content Type: text/plain

On Sunday, September 20, 1998 8:09 AM, Peter Skye
[SMTP:attmail!internet!peterskye.com!pskye] wrote:
> I've finally found a DB2 description page at
> http://www.software.ibm.com/data/db2/udb/about.html (it's linked off
the
> main page with a small "About" button).
>
> The DB2 "Personal" edition isn't network-aware and the "Enterprise"
> editions are far more than I need (they're cross-platform).

What do they mean by "not network aware"? Nowadays, I would think that
would translate to "not multi-process aware" since you should be able to
"export" the directory containing the database for access by other
workstations, the program running on the other workstation should "think"
that the data base is on a local drive. From the point of view of the
workstation containing the database, someone accessing the data "from the
network" should appear as simply another process reading a (shared) file.
Someone accessing a file on your system while you are accessing it
locally should look no different (to your system) than two processes on
your own system running concurrently.

Or, to attack this more directly, the database "files" themselves have no
inate intelligence -- they're just bits on a magnetic platter. In order
to access the data, you need the data access program. In this case, the
data access program is DB2. DB2 simply reads bits off of magnetic
platters and presents them to the user in a humanly-understandable way.
But DB2 doesn't go down to the hardware level -- it asks the operating
system to read the bits off of the platters and THEN it translates this
to something the human-at-the-keyboard will understand. So in reality,
DB2 shouldn't NEED to be "network aware".

However, DB2, "network aware" or not, should honor file locks since it is
feasible that two or more instances of DB2 may be accessing the same
file. [Note that when I refer to an "instance of DB2", I also include a
user-written program making use of library procedures to read the data
file(s) as "an instance".] Again, file locking is the responsibility of
the OS, not the application (but it is the app's responsiblity to CALL
the lock procedure at appropriate times).

When you export/publish/share (or whatever term you want to use) a drive,
you're basically telling the network that your computer has files
available for access. When you use an exported/published/shared drive,
you're telling your local machine to treat that data as if it were on a
local drive. It is possible, through system calls and what not, to
determine if the file(s) you are accessing reside on truly local drives
or on drives that are on "the network". Applications rarely need to know
this much information about the file(s) it is using -- apps generally
need to open, read, write/update, and close files (and occaisionally
detect EOF :) )

So, the question then becomes is "did IBM ADD code to explicitly check to
see if the file(s) being accessed reside on a truly "local" drive?"
(and, obviously, refuse to work if they aren't)

>
> That leaves:
> $999 DB2 UDB Workgroup Edition V5
> 999 DB2 Universal Developer's Edition V5
>
> The descriptions on the IBM site are:
> - DB2 Universal Database Workgroup Edition--a multi-user
> DB2 database for applications and data shared in a
> workgroup or department setting on PC-based LANs.

This one sounds like it knows about AND honors file locking -- implying
the "personal" edition might not!

> - DB2 Universal Developer's Edition--provides all the
> tools required for one software developer to develop
> client/server applications to run on DB2 Universal
> Database and business tools and applications for a
> company's business on any supported platform.

But this version sounds like it has more "tools" for development.

> If I buy these two packages, do I get the functionality that I want?
> - a database, like dBase or dbExpert.
> - works both standalone or on a network.
> - I can write programs for it in both C++ and Java.
> - I'll be "really cool".
>

I think others have answered this last set of questions... :)

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-programming".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message << >> Next Message >>

Return to [ 21 | September | 1998 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.