Community
Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Read only

ECC

Former Member

‎2007 Dec 07 7:48 AM

0 Likes
394

Hi ALL

This was works fine in 4.6c

TRANSLATE gwa_empty1-resource TO UPPER CASE.

TRANSLATE gwa_empty1-phase TO UPPER CASE.

What is alternate statement in ECC6.0 for TRANSLATE

Thanks & Regads

SEK

2 REPLIES 2
Read only

amit_khare
Active Contributor

‎2007 Dec 07 7:51 AM

0 Likes
372

No alternate is available. Just neglect the SLIN warning for obsolete statement and use the same.

Read only

matt
Active Contributor
In response to amit_khare

‎2007 Dec 07 8:17 AM

0 Likes
372

TRANSLATE is NOT and obsolete statement. Only the following forms are obsolete.

<b>1. TRANSLATE dobj [FROM CODE PAGE cp1] [TO CODE PAGE cp2].

2. TRANSLATE dobj [FROM NUMBER FORMAT nf1] [TO NUMBER FORMAT nf2].</b>

TRANSLATE blah TO UPPER CASE is fine, but it generates a SLIN warning of "Dangerous use of TRANSLATE in a multilingual system". You'll need to use the suppression comment "#EC TRANSLANG or "#EC SYNTCHAR.

I do wonder when companies are going to get away from the notion that you have to have clean SLIN, without using suppression comments? It forces programmers to implement convuluted code to get round the restrictions, which makes the programs more difficult to maintain, and therefore MORE EXPENSIVE!!!!!

matt