Re: RUNSQL and apostrophe problem

[Justin Dearing <zippy1981@xxxxxxxxx>]

Just use 4 apostrophes since your inside double apostrophes.

RUNSQL SQL('update qclsrc set srcdta = ''PUT ''''long file name 2016-02-03
11.40.02.csv'''' ''
            where upper(left(srcdta,3)) = ''PUT''')

On Wed, Feb 3, 2016 at 11:54 AM Glenn Gundermann <glenn.gundermann@xxxxxxxxx>
wrote:

> Hi all,
>
> I'm having a problem with RUNSQL along with apostrophes in my CL program.
>
> I have a CL source member with one record containing PUT.  I want to
> replace it with PUT followed by the file name surrounded by appostrophes.
>
> OVRDBF FILE(QCLSRC) TOFILE(GLENNLIB/QCLSRC) MBR(FTPSRCMBR) OVRSCOPE(*JOB)
>
> The following will work in a STRSQL session:
>
> update qclsrc
> set srcdta = 'PUT ''long file name 2016-02-03 11.40.02.csv'''
> where upper(left(srcdta,3)) = 'PUT'
>
> In the CL program, I can get it to work with quotes.  It's hard to see but
> I have a quote " before long and after csv.  All others are apostrophes '.
>
> RUNSQL SQL('update qclsrc set srcdta = ''PUT "long file name 2016-02-03
> 11.40.02.csv"''
>             where upper(left(srcdta,3)) = ''PUT''')
>        COMMIT(*NC)
>        NAMING(*SYS)
>
> I can't get it to work in a CL program replacing the quotes with
> apostrophes.
>
> Yours truly,
>
> Glenn Gundermann
> Email: glenn.gundermann@xxxxxxxxx
> Work: (416) 675-9200 ext. 89224
> Cell: (416) 317-3144
> --
> 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.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.