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



On 11/8/2013 3:17 PM, rob@xxxxxxxxx wrote:
I use this:
CHGVAR VAR(&APOS) VALUE(X'7D')

Of course, this upsets the chest thumpers who say that if you can't figure
out the quotes you've no place programming.

I haven't much of a chest to thump, but thankfully, counting to 2 is not
beyond my very limited capabilities. 'Escaping' delimiters is one of
the earliest things to trip up a programmer. I distinctly recall the
System/3 RPG II manual's example of how to specify a literal like
O'CLOCK, and it looked like this 'O''CLOCK'.

The first delimiter indicates 'here comes a literal'.
The next delimiter is escaped - there are two of them - so this
indicates 'here is an apostrophe'.
The next delimiter indicates 'here ends a literal'.

I'm a simpleton, and so I rely on simplistic things like counting on my
fingers - it's true. In OPs original battle then, I would say something
like this:

CHGVAR VAR(&DEVICE) VALUE('/QSYS.LIB/' +
*TCAT +
&LIBNAME *TCAT '.LIB/' *TCAT &SAVEFILE +
*TCAT '.FILE' || ''')' )

begin literal /qsys.lib end literal
append libname
append begin literal .lib end literal
append savefile
append begin literal .file end literal
append begin literal ') end literal

The final literal is apostrophe, close paren because the quote is
escaped: doubled up, resulting in a single apostrophe.


With respect to the hex value, this may not work in Unicode encoded XML.
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.