×
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.
Rob,
I tried using your suggested SQL statement, but SQL didn't like
something. It positioned the cursor on the "J" in JOB_TYPE and said...
"Token JOB_TYPE was not valid. Valid tokens: ) FETCH ORDER UNION EXCEPT"
I tried repositioning parentheses (even though your statement looks fine
to me) but with no success. I even stripped out the 't1' logic and
tried running the select by itself. No soap. I tried this on two
systems (both 7.2), one slightly more up-to-date than the other.
I finally gave up and did it the other way.
Thanks for trying.
~TA~
On 3/18/2019 10:28 AM, Rob Berendt wrote:
As to your
<>'Q'
QSYS showed up because that is the user for the SBS job type. Doing it your way is effective but limiting it to job_type='INT' would have also worked.
Somehow I missed AUTHORIZATION_NAME this morning which made me do all the string manipulation.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
