On 4/6/2016 3:41 PM, Darryl Freinkel wrote:
I use RDi (8.03) and have found the following problems that are show
stoppers. Getting a newer release is not possible now and we are on V5R4 at
this site.
-snip-
3. I have a program that compiles normally on our development LPAR but
fails to compile with SQL invalid characters when I compile it on the
production LPAR.

That sounds like a precompiler issue but you aren't going to get that
fixed on 5.4 :-(

4. I am unable to use scan and replace in RDi as it does not know I
want to do a hex search. Is there a way to do this?

You can find these using regular expression search. The thing that may
throw you is that the text is ASCII, not EBCDIC. So you need to search
for x'80' on up.

Ctrl-F to bring up the search dialogue
Check the 'Regular Expression box
In the Find box, type \x80
Click Next to find the first occurrence

Alternately, you can search for many of them in one go if you use a
slightly more complex regex:

[\x80-\xff]

I am a keyboarder, so I like to find and replace them in one shot.
Press Escape to go to the command line and type:

findText all regularExpression replaceWith " " [\x80-\xff|\x15-\x16]

Pressing Enter will find all the embedded oddities (in code I deal with)
and replace them with blanks. The regex can be understood this way:

find all of the characters which are in the group of
x'80' through x'ff'
or, are in the group of
x'15' through x'16'

Replace each one found with a blank.
Process all instances of them.

If the code you deal with has more characters than that, either expand
the groups (ie \x10-\x1f) or add more individuals with more 'or'
conditions (ie \x15-\x16|\x99|\x03]


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.