To run the CCSID conversion tool

1. Backup the libraries before you execute the CCSID Conversion tool.

2. Take Option 1 from the G96CCSID menu.

   This option will produce a report of tables in the library that have CCSID 65535 columns. For the report, you can elect to print errors only (E) or *ALL (A). It is suggested that you print errors only.

   These statuses might appear on the report:

   • “80"

     Indicates the table has CCSID 65535 columns.

   • “70"

     Indicates the table has CCSID 65535 columns, but the tool will not fix the columns (This could be because the table is an AS/400 source file or the table was created through SQL. This process only works for tables created through DDS.)

     Note:

     If there is going to be a delay in the JD Edwards EnterpriseOne 9.2 migration, you should run this report shortly before the migration to ensure there have been no unexpected changes, such as a restore of the library.

3. Take Option 3 from the G96CCSID menu – Alter tables in library.

   The Target CCISD is the CCSID you are converting to. For Western European languages this is normally 37. If you are not sure of the Target CCSID, look at the Client Access data source jobs (QZDASOINT in subsystem QSERVER) and see what CCSID you are using. The job takes approximately ¾ - 1-¾ hours to run depending on the speed of the AS/400 and size of the data library.

   The Alter tables program will add an entry to the System Reply List:

   943 CPA32B2 C

   Carefully examine the report. The tables that failed are at the top of the report and have a status code of 50. The tables that completed with warnings have a status code of 40.

   Failures and warnings refer you to the joblog. Open the joblog and search for the table name that failed.

   In the joblog for status 50, a typical error might be “Alter table may cause a loss of data in column <xxx>." For status 40, a typical error might be “CHGPF MAXMBRS(1) cannot complete because there is more than one member in the file." The CCSID tool does not convert more than the first member of a multi-member file. If you look at the tables that failed (status 50), you will see the usual cause is that the file is a “World only" file, meaning that it doesn't exist in JD Edwards EnterpriseOne and therefore its format is not compatible with SQL. If the format of the table is JD Edwards World (“I" as opposed to “F"), and the file does not exist in the JD Edwards EnterpriseOne 9.2 environment, ignore the error.

   If the table is JD Edwards EnterpriseOne format you might need to use the Copy Table method to convert the CCSID values.

   Repeat the above steps for every library that needs to be converted.

4. Return to the initial Direct Migration Special Jobs menu.

   Note:

   If any files ended in error because of maxmember, and the files should be converted, then manually change maxmembers to 1, place the files in a separate library, and then run the CCSID conversion again.