DISCLAIMER:
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please delete it and notify
the sender immediately. Please note that there is no guarantee
The daemon that UVODBC on AIX uses is the uvrpcd and this is defined in
the /etc/services file.
The daemon should automatically start following a boot / reboot of the
server.
The UVODBC group needs to be included as part of the UniVerse
installation process.
It is also worth doing a netstat -a
DISCLAIMER:
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please delete it and notify
the sender immediately. Please note that there is no guarantee
Have a look at the UniObjects docs on your client cd. There are
examples in vb and java. I've done links with vb6, c# and java. It's
all good.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Hi David,
Well basically all that we require is the ability to interrogate a SQL
Server and download any data that is applicable for updating on our UV
database, and then reverse the process going from UV to SQL server.
Thanks
Sunny.
-Original Message-
From: [EMAIL PROTECTED]
Does anyone out there still do this (if you ever have)?
Take a backup of the file systems (in our case, AIX UNIX), format the disks
clean, then restore the data back down to lay it back contiguous.
Are there any (noticeable) I/O advantages to doing this for a UniVerse
database on today's
We're using Universe 10.0.10.0 on Win 2000 Server.
I need to determine when a Basic WRITE Statement of a record to a Type 1 file
has completed so I can execute a subsequent action on the record written, but
not before all the data in the record has been written.
These can be large records
Dave,
It can take 'numbers of seconds' to write? Phew, they must be b--i--g
records!
Could you consider changing from WRITE to WRITESEQF?
And maybe from Type 1 to Type 19?
If the 'subsequent action' is inside the UniVerse environment, I would
expect that the program would access the copy
Do you have something external waiting on this record to appear? If
so, you might consider writing out the record out under a temporary
name and then renaming it to a name that your watcher is looking for.
We do this all the time with drop file interfaces; write the record
with a .tmp extension
If you are using AIX you can gain pretty much the same defragmentation
advantage, however slight it might be, by using the built in filesystem
defragment on AX 4.x and above:
smit:
System Storage Management (Physical Logical Storage)
File Systems
Add / Change / Show / Delete File
Write a tag record and watch for the tag instead of the actual data
record. When the tag appears, you're sure the related data record is
there.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Taylor
Sent: Monday, October 31, 2005 11:53 AM
To:
11 matches
Mail list logo