This works at least back to V5R1

select cnmacc from arstageeo/arcnm where translate(cnmacc, '0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ ',
'~') <> '~~~~~~~~~~~~~~~~~~')
to the length of cnmacc.

This is case-sensitive - and your test includes blanks - so you need to find a character that will never be found - you could do a like test against '%~%', e.g.

-------------- Original message --------------
From: "Francis Lapeyre" <flapeyre@xxxxxxxxx>


I'm scratching my head here. I'm trying to find all intances where a
particular field does not have a space, a number, or an uppercase letter in

Using STRSQL, this does not work:

SELECT cnmacc FROM arstageeo/arcnm WHERE cnmacc not like('%

Niether does this:

SELECT cnmacc FROM arstageeo/arcnm WHERE trim(cnmacc) not in('%1%') and
trim(cnmacc) not in('%2%') and trim(cnmacc) not in('%3%') and trim(cnmacc)
not in('%4%') and trim(cnmacc) not in('%5%') and trim(cnmacc) not in('%6%')
and trim(cnmacc) not in('%7%') and trim(cnmacc) not in('%8%') and
trim(cnmacc) not in('%9%') and trim(cnmacc) not in('%0%') and trim(cnmacc)
not in('%A%') and trim(cnmacc) not in('%B%') and trim(cnmacc) not in('%C%')

(continuing the alpahbet) ...

trim(cnmacc) not in('%Z%')

This is a one-shot deal. We want to identify accounts in CNMACC (a 10-byte
fixed-length character field) which were entered with "funny" characters.

What am I doing wrong?

Thanks in advance.

Francis Lapeyre

Da mihi sis crustum Etruscum cum omnibus in eo.
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].