RE: [U2] UV/NET questions/confirmation

2008-08-20 Thread Carl Dula
UV/NET only needs to reside on the system that you want to remotely read/write
data from. For example, if you have system A and B with uv installed, and you
want to read/write uv files on A from B, then UV/NET is installed on A only. If
you need to do both read and write on A from B and on B from A, then you need
UV/NET on both systems. UV/NET is used simply by changing the file pointer to
point to the file on the remote system, then UV/NET takes care of the rest.

UV/NET is a purchased product, and therefore needs to be licensed on the system
which it is installed. The licensing procedure is similar to that for uv itself.

--
Carl Dula   Voice: 973-227-8440 X111
Pulsar Systems, Inc.Fax: 973-227-8440
271 Route 46 West, Suite H209   email:[EMAIL PROTECTED]
Fairfield, NJ 07004-2474http://www.pulsarsystems.com
Authorized IBM U2 Distributor
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/


RE: [U2] UV/NET questions/confirmation

2008-08-20 Thread Rick Nuckolls
Curt,

Only the file server (remote) needs to be licensed for UV/NET. The
client just needs uv.  If you have two machines that want to access each
other, then both need UN/NET licenses.

If your local box is accessing a remote UV box via UV/NET, you need
enough UV/NET licenses to support the number of users on the local
machine who might be logged in and accessing the remote box.  Only one
connection will be made for each user.  I am not sure how IBM is
licensing this now; they may just give you unlimited remote connections
when you buy UVNET for a machine.  They do that for the Enterprise
licenses.

If a local user opens a connection to a remote machine, he will hold
that connection open for a configurable amount of time (1 hr of idle
time), or until he logs out.  If your applications open files to common,
you may need to reconfigure the timeout to a large number to avoid users
attempting to access a file that has been closed with the connection.

UVNET has been a very reliable product for us; but we also use it over
some very fast wire.  If you intend to run over a slow network, you
should consider what the transmission time will do to your processes.
For instance, if an application were to open 25 remote files, you will
have injected considerable delay into it if it is accessing a those
files over a slow UVNET link.  All of the operations using UVNET are
essentially blocking, so an application is going to pause momentarily
between remote reads and writes.  This is only an issue if you have a
slow connection.

-Rick Nuckolls
Lynden Inc.

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Curt Stewart
Sent: Wednesday, August 20, 2008 8:30 AM
To: [EMAIL PROTECTED]
Subject: [U2] UV/NET questions/confirmation

First off let me apologize for my last post. I realized it was unsigned
the moment I released the button after clicking on Send.

I've just reviewed the Uv/Net documentation and would just like to get
confirmation on my understanding of what I read.

For UV/NET to work, both systems need to be running Universe and UV/NET.
Do both have to have the same user licenses? What is the minimum license
count needed for the remote server, given the local server is licensed
for 34 users?

The documentation states that the Unix version must be installed and
authorized, but the Windows version is installed and licensed. Does this
mean that the Windows version does not need to be authorized and can be
used right out of the box?

Thanks for all the help and insight.
Curt Stewart
Tri-sys Consulting
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/