Progress/400
Product Guide


Setting Up Collation for Progress/400 Databases

After you determine which code pages and ALTSEQ tables you need for your Progress/400 database, you can set up your database files. This section describes how to do this in the following circumstances:

Working with Existing Database Files

Read this section if your implementation includes existing physical and logical files that were created using AS/400 tools such as DDS and STRSQL.

Progress/400 requires that all files in a database use the same code page and ALTSEQ tables. If the existing files were defined using an ALTSEQ table, you must specify this table as the value of the ALTSEQ parameter in the DUPPRODB utility. However, if they were defined without an ALTSEQ table specification, you can use any ALTSEQ table in DUPPRODB.

It is possible to convert existing files from one ALTSEQ table to another.

NOTE: You should convert existing files only if doing so will not interfere with existing non-Progress applications (for example, RPG or COBOL applications) on the AS/400.

Follow these steps to perform the conversion:

  1. Create a new file using the same record format and the desired ALTSEQ table.
  2. Use the CPYF command to copy the records from the old file to the new file. The command handles the collation conversion. For details on the CPYF command, see your IBM documentation.
  3. Delete the old file.
  4. Rename the new file with the name of the old file.

Note that if you cannot convert all of the physical files, you can convert just the logical files. This avoids the need to copy all of the records, but it leaves the physical files with the original definition relative to the ALTSEQ table. To resolve this problem, simply use the CHGPRODCT utility to notify Progress/400 about the logical files.

Follow these steps to convert a logical file:

  1. Delete the logical file.
  2. Re-create the logical file, changing the definition to the appropriate ALTSEQ table.
Creating a New Progress/400 Database (DUPPRODB)

Read this section if you are creating new database files. It describes how to specify ALTSEQ tables when using the DUPPRODB utility to create a new Progress/400 database.

The example in Figure 8–2 illustrates using the DUPPRODB utility on an AS/400 machine whose system code page is IBM037.

Figure 8–2: DUPPRODB Prompts and Responses

Note that in the example in Figure 8–2, the DataServer Database Code Page parameter is *SYSVAL, which specifies the AS/400 operating system code page. Specifying the AS/400 code page typically provides the best results. You will need a different code page only in very rare circumstances.

Once you have determined the code page to use and you know the default code page on your AS/400, you must choose the corresponding ALTSEQ table from the tables that IBM provides for the AS/400.

Table 8–3 provides a list of commonly used code pages that correspond to IBM ALTSEQ tables.

Table 8–3: Code Pages and Corresponding ALTSEQ Tables

Code Page
Country or Alphabet
Case-sensitive ALTSEQ Table
Case-insensitive ALTSEQ Table
Uppercase ALTSEQ Table
037
USA
QLA10025U
QLA10025S
Q037
037
Canada
QLA10025U
QLA10025S
Q037
256
The Netherlands
QLA10100U
QLA10100S
Q256
273
Germany
QLA10111U
QLA10111S
Q273
273
Austria
QLA10111U
QLA10111S
Q273
277
Norway
QNOR0115U
QNOR0115S
Q277
277
Denmark
QDANR0115U
QDAN0115S
Q277
278
Sweden
QSNF0016U
QSNF0016S
Q278
278
Finland
QSNF0016U
QSNF0016S
Q278
280
Italy
QLA10118U
QLA10118S
Q280
284
Spain
QLA1011CU
QLA1011CS
Q284
285
United Kingdom
QLA1011DU
QLA1011DS
Q285
297
France
QLA10129U
QLA10129S
Q297
420
Arabia
QARA01A4U
QARA01A4S
Q420
870
Latin 2
QLA20366U
QLA20366S
Q870
1026
Turkey
QTRK0389U
QTRK0389S
QA3S
500
Denmark
QDAN01F4U
QDAN01F4S
Q500
500
Latin 1
QLA1014FU
QLA1014FS
Q500
500
Norway
QNOR01F4U
QNOR01F4S
Q500
500
Spain
QESP01F4U
QESP01F4S
Q500
500
Sweden
QSNF01F4U
QSNF01F4S
Q500
500
Finland
QSNF01F4U
QSNF01F4S
Q500

Note that Table 8–3 does not include a list of lowercase tables. IBM does not provide lowercase tables, so you must build them yourself. You use lowercase tables only when the DataServer must evaluate the Progress 4GL function LC within a query. For information on building these tables, see the “Creating the Tables” section.

For more information about collation on the AS/400, or for a complete list of IBM ALTSEQ tables, see the IBM AS/400 National Language Support Planning Guide .


Copyright © 2004 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095