|
James, As Nathan pointed out, there is more than one way to convert the case of a string. One way is to use XLATE. I got away with that for years. On more recent releases, you might look at QlgConvertCase. That API supports a CCSID parameter so you can convert ASCII, Cyrillic, or even EBCDIC. If you are interested in an example, the iSeries-tookit (www.iseries-toolkit.org) has an example that is part of the TXTTKT module. You can check it out at: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/iseries-toolkit/CVSROOT/src/qrpglesrc/txttkt.irp?rev=HEAD&content-type=text/vnd.viewcvs-markup Depending on the range of values you plan on supporting, you should be able to use a 1-byte binary field. David Morris >>> nandelin@relational-data.com 04/01/02 17:34 PM >>> > > D dsCvt DS > > D dsCvtChar 1A > > D dsCvtInt 3U 0 overlay(dsCvtChar:1) > > V4R1 tells me that > > The length of an integer or unsigned field is not valid. My understanding is that integers can be defined with the following lengths: 5 = short = 2 bytes 10 = int = 4 bytes 20 = long = 8 bytes Over the past couple years, there have been some good discussions about uppercase functions at: http://www.iseriesnetwork.com/Forums/main.cfm?CFApp=54 Nathan M. Andelin www.relational-data.com
As an Amazon Associate we earn from qualifying purchases.
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.