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:
- Create a new file using the same record format and the desired ALTSEQ table.
- 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.
- Delete the old file.
- 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:
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.
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 |