ulimit is a limit on system resources that can be set on a per user base. This
command is on all versions of *nix that I know of. Depending on the operating
system the values under the ulimit may differ.
Dan Goble
Sr. Programmer Analyst
-Original Message-
From:
What user was assigned to udt when it was installed? Check that user's
ulimit.
We run UV, and some commands (create-file, SH -c, etc.) run as the user
assigned to UV during the install, not as the user that is actually logged
in. Shelling out with sh gives you your own environment variables,
In your diff comparison below, it appears that the first shell is /bin/bash and
the second shell (started as a subshell of Universe) is /bin/sh. Wondering if
that's where your problem is.
You could try changing the UV Verb SH from /bin/sh to /bin/bash and see if that
helps.
Thanks for the
Hello,
I am trying the following command:
/u1/uv/bin/fixtool -file /resize/FOOBAR -logging -logpath /resize/loggin
The directory: /resize/FOOBAR
contains:
-rwxrwxrwx 1 root sys 1256974336 Jul 3 07:33 DATA.30
-rwxrwxrwx 1 root sys 7190597632 Jul 3 07:33 OVER.30
Hi, On most linux systems /bin/sh is a sym link to /bin/bash
It just turns out that ulimit is inherited from the shell above and 32 bit
udt does change it, hence why i get my issue.
So i can work round that now by resetting ulimit. Thanks for everyones
insight.
-Original Message-
The csv 'standard' for fields containing a quote is double quote
So for the data
Col1 = col1data
Col2 = col 2 is here !, and it is good
Col3 = end
You have a csv of
col1,col 2 is here !, and it is good,end
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
Our primary application hasn't needed the performance gains offered by
indexing, but our database has grown large and complex enough that we're
looking at it seriously. Having only dabbled with indexing in test
environments, I've got a few general and best practice questions. I've
seen some
The csv 'standard' for fields containing a quote is double quote
So for the data
Col1 = col1data
Col2 = col 2 is here !, and it is good
Col3 = end
You have a csv of
col1,col 2 is here !, and it is good,end
Does the ! in front of the comma in Col2 make it escape the comma. In
other
There is a standard RFC4180 with iana. The standard is to have any commas
enclosed within the double quotes. Only the Double quotes are escaped with
double quotes.
hth
Colin Alfke
Calgary, Canada
From: Charles_Shaffer
The csv 'standard' for fields containing a quote is double
It is not the case, I used the uv user which has root permissions and my
directories have 777 permissions.
From: IT-Laure Hansen lhan...@redwoodcity.org
To: Jacques G. jacque...@yahoo.com
Sent: Tuesday, July 7, 2009 2:23:54 PM
Subject: RE: [U2] [UV] Using the
There is a standard RFC4180 with iana. The standard is to have any
commas enclosed within the double quotes. Only the Double quotes are
escaped with double quotes.
Got it. Thanks everyone. I didn't know that. I still think I'll stick
with tab delimiters though.
Charles Shaffer
Senior
Hello all,
I'm hoping this is a good place to find the error of my ways. I thought it
was possible to do tabulations on multivalued fields within a dictionary
item. I've included the dictionary, a sample of the output and a sample of
the item.
We've already resolved it another way, but thought
charles_shaf...@ntn-bower.com wrote:
Got it. Thanks everyone. I didn't know that. I still think I'll stick
with tab delimiters though.
lol, standards are made to be broken :)
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
Is it because of the IF statement? @record3-...@record2 tabulates correctly
for each value position.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ross Morrissey
Sent: Tuesday, July 07, 2009 3:40 PM
To: U2 Users
Got it. Thanks everyone. I didn't know that. I still think I'll
stick
with tab delimiters though.
lol, standards are made to be broken :)
We used to joke about the RS-232 'standard.' It was such a great standard
because there were so many different ways to implement it.
Charles
Using LTS gets you to compare each element of an array to each of another.
Reuse will repeat the last element if you have an unequal number of elements in
each array.
It could also be a problem that this dictionary has an MTS conversion. It is
probably comparing a time to zero. By the
As already stated, IFS, LTS, REUSE, and a bunch more are MultiValue
Handling Functions documented in Universe Basic manual. Don't know
where UD documents them.
They can be called from I-descriptors.
Unidata is similar, but I think you might need to call them from
I-descriptors via SUBR().
Thanks for the input all.
Using those functions is the path one of our other developers took.
TST
0001 I
0002 LTS(@RECORD3,@RECORD2); MULS( @1, REUSE(86400)) ; ADDS(@RECORD3,
@2) ; SUBS(@, @RECORD2)
0003 MTS
0004
0005 10R
0006 M
-Original Message-
From:
Let's not forget what the RS stands for.
In addition, there were many applications that went far beyond anything
contemplated by it, kind of like off-label uses for prescription drugs. Your
mileage will vary.
Best regards,
Henry
Henry P. Unger
Hitech Systems, Inc.
http://www.hitech.com
The semi-colon way of writing is more readable, but UV does not let you
reference such an I-descriptor (as reusable code) from some future one.
For example, next year you want to know how fast/slow certain programs
run during certain times of the day. You'll want to use the RUN_TIME
result
20 matches
Mail list logo
