×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Scott, you are the man!
Jeff Carey, MSIT, MBA
Senior Technical Support Specialist
Jeffrey.Carey@xxxxxxx
COMMON members - Board elections end 5/3/11
http://www.common.org/elections
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, April 28, 2011 06:15 PM
To: Midrange Systems Technical Discussion
Subject: Re: Disabled User Profiles
The db2 command handles $ characters just fine -- it's QShell that
causes interference. In a Unix shell, $ has a special meaning (it means
"insert variable value here"). If you can get the $ past QShell and
into the db2 command, it'll be handled just fine.
FWIW, I have written an "improved" version of the db2 command. My
command allows both SQL and SYS syntax, as well as better error
handling, and extra options for formatting the output. If you're
interested, you'll find it here:
http://systeminetwork.com/article/improved-db2-command-qshell
On 4/28/2011 6:01 PM, Jeffrey Carey wrote:
You can also invoke QShell in a CL to run a SQL statement. Note you
need to use SQL style syntax (e.g. library.file not library/file) and
it
has some issues (such as handling $ characters well I hear):
QSH CMD(DB2 "sql statement") and those are double quotes ( shift + ' )
not single quotes.
midrange.com
