Re: sql concat symbol

[Alexei Pytel <pytel@xxxxxxxxxx>]

I suggest you look at the actual hex code entered in a source file and 
what does it mean in a CCSID of a source file (on a system where it 
fails).
Most probably this is related to how the symbol was entered.
There is a long way from keyboard key being pressed to actual hex code 
being written to a source file and then to what compiler actually sees. 

    Alexei Pytel
always speaking for myself




"Jim Franz" <franz400@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/02/2005 06:53 AM
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.