Re: SQL Acting Strangely -- MIDRANGE-L

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

Presumably that the DECPNT() specified on STRSQL was being ignored has since been confirmed to have been the correct behavior, due to a SQL6335 having been logged into an existing STRSQL session versus the request having created a new session, as described in the post:
http://archive.midrange.com/midrange-l/201002/msg00703.html

Posting this reply was more about summarizing this sub-thread more succinctly in the archives, than about getting an actual reply.

kwds: substr substring comma -104 sql0104 syntax error token ,#

Regards, Chuck

Jonathan Mason wrote:

Thanks for that. The parameter for STRSQL was set to *JOB which should have picked up the *BLANK that the job was changed to.
When I explicitly set the parameter to *PERIOD it still kicks out
the error. The QDECFMT system value is set to "3" which gives a
comma and suppresses zero - although there's no reason why it
should be set this way (being in the UK and all that).

McGovern, Sean wrote:

If you try it in STRSQL, prompt STRSQL and change the DECPNT parameter also.

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.