Kbase 16865: AS/400 case sensitivity using ALTSEQ with Progress/400
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
17/03/2005 |
|
Status: Verified
GOAL:
How to oversome the AS/400 v Progress case sensitivity issue using ALTSEC.
FACT(s) (Environment):
AS/400
Progress/400
FIX:
DB2/400 is, by default, case sensitive. PROGRESS is, by default, case insensitive. This case sensitivity issue can be controlled from the Server Schema by specifying an Alternate Collating Sequence table at time that the DUPPRODB utility is executed. This will cause any physical files/tables or logical files/indexes that are created or modified using the Progress/400 Data Dictionary tool to use the ALTSEQ table specified for this Server Schema. The default value for the ALTSEQ parameter in the DUPPRODB utility is *NONE. This will cause the
utility to use the value supplied when the Progress/400 product was installed. The ALTSEQ table will be inserted into the Data Description Specicification (DDS) and compiled into the resulting DB2/400 object when the transaction is committed. **NOTE: The ALTSEQ value for a Server Schema cannot be changed.
There may be instances when the removal or changing of an ALTSEQ table for a specific object is needed. This must be done via AS/400 tools. The DDS source can be edited using SEU and the source recompiled to produce a new DB2/400 object that reflects this change. The change must be updated to both the Server Schema and the Client Schema holder
***MAKE SURE TO HAVE CURRENT BACK_UPS PRIOR TO MAKING ANY DATABASE CHANGES!!***