We're making some real strides here in product development and
connectivity and I'd like to share this with people in the U2
community. If that's an ad, so be it, but I want people to be
aware of the many things that are possible with the MV DBMS that
faces daily threats from those who call it a
FYI, I've done autodial from MV (as well as outbound calling for
collections with voice/DTMF response). With a character
interface or thick/thin GUI, the MV system sends a message to
Skype running on the user's local PC. The call is made and
statistics logged back to the app.
Doing it yourself
To consolidate your ideas then, you don't want to write a shell, you don't
want to change the voc, and you do want it to change?
Ha ha
Easiest is to write a shell, but along the lines of the spell checker :
- use soundex to look for similarities,
- file: key= soundex'd names.
- file: line 1:
Well - thanks, I guess.
Regarding the internal workings, yes - it would need to work along those
lines, especially the 'learning logic' part.
As for not wanting to write a shell, not wanting to change the voc -
you're right - my original question (perhaps poorly phrased) was an
enquiry as to
I am curious about this also. GSEMNUM is 97 here also with a 117 UV
user license on Redhat Linux UV 10.1.12.
-Original Message-
From: IT-Laure Hansen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 01, 2008 5:43 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] locking question
Is
I'd say that if you don't have locking problems, and as there is not a
great difference from 97 to 110, that would mean that your applications
are not requiring more locks.
The recommendation is to make sure that all users will have sufficient
room for locking, and will not get an error like :
Hi Brenda,
Is the rule of thumb about the value of GSEMNUM valid for
other systems?
In my personal opinion (which may be wrong!), the rule of thumb is not
right.
UV locking is a very complex topic. It is another good reason to recommend
the UniVerse Internals course.
To explain the
we have a 473 user license of universe and GSEMNUM was 87 so I think
we are woefully undersized as far as that parameter goes.
Hopefully this will fix our issue and I'll owe you guys (and gals) a
HUGE thank you!
one question though what exactly is this parameter used for? I am
trying to
Thanks
Patricia M. Wilson
M.I.S
813.810.0210
Ext: 3095
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Herve
Balestrieri
Sent: Wednesday, July 02, 2008 9:23 AM
To: u2-users@listserver.u2ug.org
Subject: Fw: [U2] locking question
I'd
Like the original poster we don't have any locking issues and since it
has been 2-3 years since I took the UV Internals course and about 2
years since the last time I had to change UV settings, I just didn't
remember the GSEMNUM setting default and recommendation.
Our license count was originally
From the Administering UniVerse 10.2 Guide section is UniVerse Configurable
Parameters Chapter 4-4 has the following information Managing Locks is
Chapter 9. Link to all 10.2 documentation
http://www-306.ibm.com/software/data/u2/pubs/library/102univ/
FLTABSZ Sets the number of file lock entries
Hi Nancy,
I would add a dictionary item NAME giving it the next available attribute
number and it would be multivalued and associated to the phrase PARAMS.
I would make the dictionary item PARM multivalued and associated to the
phrase PARAMS
I would replace your line : ColumnMap Node=PARAMS
I need to check the write status of an item in a type 19 file. Normally,
it will bomb out on write while trying to update a read-only item. (on
error and else clauses don't seem to do much for this in a write
statement).
I have a 'before update' trigger checks if an item in a type 19 file is
13 matches
Mail list logo
