× 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.



Jim,

I've noticed that on some systems I need to use the exclamation mark ! 
instead of the pipe character |

HTH,

Peter Colpaert
Application Developer
Massive - Kontich, Belgium
-----
Yoda of Borg are we.  Futile is resistance, assimilated will you be.
-----




"Jim Franz" <franz400@xxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
02/03/2005 13:53
Please respond to Midrange Systems Technical Discussion

 
        To:     <MIDRANGE-L@xxxxxxxxxxxx>
        cc: 
        Subject:        sql concat symbol


Currently working on a partitioned v5r2 system. On one partition,
we have embedded sql which includes the concat symbol || (example:
digits(u.pscc)||digits(u.psyy)||digits(u.psmm)
In one partition this runs, the other we get an 
invalid token error. Same error if we key into
strsql, or into a qsqlsrc member & use runsqlstm.
Sent same code to another system at v5r1 and had 
same problem. We have verified language, country,
ccsid, default ccsid all the same (ENU,US,65535,37)
Not authorized to verify ptfs.
Any known fixes or reasons?
tia
jim franz
-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.