Hi David,
Doesn't look like it. If you need to write the xml, write it to a type 19 file
and use system(1017) to ensure the document doesn't get CRLFs converted to UV
system marks.
assign @true to system(1017)
write xml on type19file,id
assign @false to system(1017)
z =
Perfect, thanks!
From: dgo...@interlinebrands.com
To: u2-users@listserver.u2ug.org
Date: Thu, 17 Jun 2010 08:35:58 -0400
Subject: Re: [U2] RFS error question
Dan,
You may want to look here.
https://u2tcint.rocketsoftware.com/developerzone/techarticles/wterhune0512/
Below is
OKHow do I setup a
sh -c when what I want to pass has in it, single quotes, double quotes
and backslashes?
George Gallen
Senior Programmer/Analyst
Accounting/Data Division, EDI Administrator
ggal...@wyanokegroup.com
ph:856.848.9005 Ext 220
The Wyanoke Group
You can usually escape any given character passed to the shell by preceding
it with a backslash. In other words:
To pass a quote: \
To pass a backslash: \\
Etc.
Larry Hiscock
Western Computer Services
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
Write a shell script to your current directory and execute it and
delete it
George Gallen wrote:
OKHow do I setup a
sh -c when what I want to pass has in it, single quotes, double quotes
and backslashes?
George Gallen
Senior Programmer/Analyst
Accounting/Data Division, EDI
that doesn't help.
I'm passing is:
mysql --user username -e LOAD DATA infile '/mnt/mount/FILE.TXT' REPLACE INTO
TABLE database.updates FIELDS TERMINATED BY ',' LINES TERMINATED BY '\n'
(Emailaddress, Reference) SET UpdateType = 'D', DateAdded =
current_timestamp(); LOAD DATA infile
I wanted to avoid that route...but I don't think I can.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-
boun...@listserver.u2ug.org] On Behalf Of Jeff Schasny
Sent: Thursday, June 17, 2010 1:28 PM
To: U2 Users List
Subject: Re: [U2] I've run out of
Use the QUOTE() function, thusly:
sh -c mysql --user username -e :QUOTE(LOAD DATA infile
'/mnt/mount/FILE.TXT' REPLACE INTO TABLE database.updates FIELDS TERMINATED
BY ',' LINES TERMINATED BY '\n' (Emailaddress, Reference) SET UpdateType =
'D', DateAdded = current_timestamp(); LOAD DATA infile
Oops ... missed something at the end. Try this:
sh -c mysql --user username -e :QUOTE(LOAD DATA infile
'/mnt/mount/FILE.TXT' REPLACE INTO TABLE database.updates FIELDS TERMINATED
BY ',' LINES TERMINATED BY '\n' (Emailaddress, Reference) SET UpdateType =
'D', DateAdded = current_timestamp(); LOAD
We recently migrated from Unidata 7.1.8 on Solaris to Unidata 7.2.5 on
RedHat.
We make use of @LOGNAME quite a bit to determine a person's username.
Since our migration, however, we've documented some cases where @LOGNAME
is not returning the proper username - it returns someone else's.
When I've run into situations like this I just set up vars to hold the chars I
need
DQ = ''
SQ = ''
BS = '/'
ASTRING = BS:'HELLO MA BABY ':SQ:DQ:'GAL':DQ:SQ:BS
Larry Hiscock lar...@wcs-corp.com wrote:
=
Oops ... missed something at the end. Try this:
sh -c mysql --user
I have seen this in the past where the file wtmp usually found in /var/adm is
corrupt or too big ( over 2 meg ). To correct this just type at the unix
prompt
wtmp
And it will clear the file.I recommend doing this just before a reboot of
the system.
-Dan
-Original Message-
On 06/17/10 14:20, Dan Goble wrote:
I have seen this in the past where the file wtmp usually found in /var/adm is
corrupt or too big ( over 2 meg ). To correct this just type at the unix prompt
wtmp
And it will clear the file.I recommend doing this just before a reboot of
the
On 6/17/2010 2:23 PM, Jeffrey Butera wrote:
On 06/17/10 14:20, Dan Goble wrote:
I have seen this in the past where the file wtmp usually found in
/var/adm is corrupt or too big ( over 2 meg ). To correct this just
type at the unix prompt
wtmp
And it will clear the file.I recommend doing
As an aside, most people here know that I prefer to do things
outside of the DBMS, but driven by the DBMS. So I do what you're
talking about all the time with mySQL, cURL, and many other
command-line tools.
Combine the great advice you've received so far to create the
best solution:
- Use
On Universe you can use SYSTEM(19) instead of @LOGNAME. It might exist on
Unidata too.
I don't know if @LOGNAME gets it from the Unix environment LOGNAME variable.
If so, there may be a Unix script that is changing the environment variable.
You can try:
- Original Message
Hi Jeff,
While at Beloit I had a problem with @LOGNAME. It only showed up when a
Datatel program was calling another Datatel program (or something like that).
I know it had something to do with a problem with Uniobjects and PAM
authentication. The work-around was to add the DMI username and
We ran into a similar situation in the past with uv on hpux
Although @LOGNAME is documented as a readonly value, we found out that
it is possible to change it ( and other readonly system variables ) by
passing it as an argument to a subroutine - the subroutine can then
change the value. I guess
I looked into this and there appears to be 2 different type of system
variables in UniData. There are those like @AM which cannot be changed
and those like @LOGNAME which can be. It is not required to pass them to
a subroutine to change those that can be. A program will not compile if
you assign
That is different from universe where you get the error @Variable
(Read-only) unexpected when you try to directly assign to @LOGNAME
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Dan McGrath
Sent: June 17, 2010
Thanks, Stuart.
SYSTEM(1017) seems to have a different function in UV10.0 - 1017 Returns the
user's supplementary UNIX groups in a dynamic array.
Can't find any reference to xmapopen() - maybe new since 10.0 ?
Regards,
David Norman
Senior Software Engineer - SA Ambulance
David,
The assign n to system(1017) syntax is an undocumented feature which allows
you to do reads without system delimiter conversion. It is definitely available
on 10.0. You should be able to test it simply enough.
id = 'test'
rec = 'x':char(10):'y'
open 'type19file' to t19 then
crt
My experience is similar - I usually try to write out a shell script -
hopefully reusable.
...
Within basic code, I would preference equates over variables for quotes other
immutable delimiters. Not only more readable (like a variable) but also more
protection against fatfingeritus!
equ SQ to
On 6/17/2010 9:33 PM, Boydell, Stuart wrote:
My experience is similar - I usually try to write out a shell script -
hopefully reusable.
...
Within basic code, I would preference equates over variables for quotes other
immutable delimiters. Not only more readable (like a variable) but also
24 matches
Mail list logo
