Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / May 2007

Tip: Looking for answers? Try searching our database.

ALTSEQ in logical files

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
jacquestardif@gmail.com - 09 May 2007 21:04 GMT
Hi,

I have to use the QLA10025S translation table (SRTSEQ FOR LATIN 1
SHARED CCSID 00037) in order to equally process lower/upper cases and
accentuated characters.

I did add the ALTSEQ(QSYS/QLA10025S) keyword in my logical file.

With a RPG ILE program compiled with no special options, the alternate
collating sequence just works fine.

The exactly same code in RPG III does not behave the same way. I had
to do some changes:

1) I added a "D" at position 26 of the H-spec
2) I compiled the RPG III pgm with the SRTSEQ(QSYS/QLA10025S)
parameter.

The compilation listing gave the following:

DONNEES TABLE DE SEQUENCE DE TRI DE LANGUE
NATIONALE
                                        Valeur en cours    Valeur en
entrée
         Séquence de tri. . . . . . :   QLA10025S
QLA10025S
           Bibliothèque . . . . . . :     QSYS
QSYS
         Identificateur de langue . :   FRC
FRC
          CCSID de la table de séquence de tri :
37.
         Nombre de caractères avec modification de séquence :
190.
              0_ 1_ 2_ 3_ 4_ 5_ 6_ 7_ 8_ 9_ A_ B_ C_ D_ E_
F_
          _0  .  .  .  .  .  6B 44 93 93 78 79 50 5D 5E 6A 7B
_0
          _1  .  .  .  .  7A 89 4C 89 85 8E 52 67 85 8E 70 7C
_1
          _2  .  .  .  .  85 89 85 89 86 8F 97 68 86 8F 97 7D
_2
          _3  .  .  .  .  85 89 85 89 87 90 98 53 87 90 98 7E
_3
          _4  .  .  .  .  85 89 85 89 88 91 99 61 88 91 99 7F
_4
          _5  .  .  .  .  85 8D 85 8D 89 92 9A 5F 89 92 9A 80
_5
          _6  .  .  .  .  85 8D 85 8D 8A 93 9B 60 8A 93 9B 81
_6
          _7  .  .  .  .  85 8D 85 8D 8B 94 9C 7B 8B 94 9C 82
_7
          _8  .  .  .  .  87 8D 87 8D 8C 95 9D 7B 8C 95 9D 83
_8
          _9  .  .  .  .  92 97 92 4F 8D 96 9E 7B 8D 96 9E 84
_9
          _A  .  .  .  .  65 48 77 47 57 85 49 5B 43 7C 7D 7E  _A
          _B  .  .  .  .  4D 66 45 6C 58 93 4B 5C 93 99 93 99  _B
          _C  .  .  .  .  72 69 6D 63 88 85 88 42 93 99 93 99  _C
          _D  .  .  .  .  59 5A 41 55 9D 54 9D 51 93 99 93 99  _D
          _E  .  .  .  .  6E 46 74 73 98 85 98 4E 93 99 93 99  _E
          _F  .  .  .  .  76 75 4A 56 6F 64 62 71 93 9D 93 .   _F
              0_ 1_ 2_ 3_ 4_ 5_ 6_ 7_ 8_ 9_ A_ B_ C_ D_ E_ F_

Seeing this stuff in my compilation listing looks like a good thing to
me.

The problem is, if I run the RPG ILE program, I do get all the
expected results. Doing the same with the slightly changed RPG III
version does not return the expected results; like the translation
table did not work properly.

Is there anything I should define for the RPG III programs? Note:
Convert and compile the RPG III program to ILE is NOT an option...
don't ask me why, it still gets me mad!!! =)
Karl Hanson - 10 May 2007 14:40 GMT
> Hi,
>
[quoted text clipped - 71 lines]
> Convert and compile the RPG III program to ILE is NOT an option...
> don't ask me why, it still gets me mad!!! =)

You might try posting the question in newsgroup comp.sys.ibm.as400.misc,
as some RPG experts contribute there.

--
Karl Hanson
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.