IBM® DB2® Content Manager OnDemand for OS/390™ Version 2 Release 1 and Item Access Facility Version 1 Release 3 customers that are migrating their metadata to DB2 Content Manager OnDemand for z/OS™ and OS/390 Version 7 Release 1 might experience incorrect data being put into the V7.1 ARSAPP table due to incorrect code points being used. This could result in failures at load time due to the posting date mask being ignored, or problems at view time with data being incorrectly formatted.
The DB2 Content Manager OnDemand for z/OS and OS/390 Version 7.1 application definitions include two columns which contain unformatted text. This text consists of section headers which contain three characters whose code points are dependent on the code page of the DB2 database.
The characters are:
- Left Square Bracket -- [
- Right Square Bracket -- ]
- Commercial At -- @
The metadata migration program, ARSZFLDG, was written to always use code points from code page 1047 for these characters. If your DB2 database is in a code page which uses different code points for these characters, the data in the PREPROCESSOR and FIXED_VIEW columns of the ARSAPP table will be ignored by the report capture process and by the view processes.
To identify if your OnDemand V7.1 installation contains incorrect data, follow these steps:
1. Identify the code page of your DB2 database
2. Identify the code points for these three characters used by your code page
3. If the following code points are different for your code page, then the problem may exist:
x’AD’ for left square bracket
x’BD’ for right square bracket
x’7C’ for commercial at
4. If your code points for these characters match the above, you do not have this problem. If your code points are different for any of these characters, then further analysis is needed.
A scan of the Application Table for the PREPROCESSOR and FIXED_VIEW columns can identify definitions which have incorrect code point values.
SUBSTR(FIXED_VIEW, 1, 500) AS FIXED_VIEW,
SUBSTR(PREPROCESSOR, 1, 500) AS PREPROCESSOR
WHERE SUBSTR(FIXED_VIEW, 1, 1) = X'AD'
OR SUBSTR(FIXED_VIEW, 2, 1) = X'7C'
OR SUBSTR(PREPROCESSOR, 1, 1) = X'AD'
If any rows are returned for the above query, and your DB2 database uses a code page whose code points for a left square bracket is not x’AD’ and commercial at is not x’7C’, then your ARSAPP contains rows with data that will be ignored by OnDemand V7.1.
Install APAR PK12574 to correct the problem for future metadata migrations. This APAR supports a new, optional, input parameter to allow you to specify the locale of your DB2 database. Refer to the APAR’s ARSODPUB member of the SARSINST library for a description of how to specify this new parameter.
OnDemand V8.4 includes support for the optional LOCALE parameter, which is described in the V8.4 Migration Guide, SC19-1216.
The following describes some alternatives for correcting existing data in your ARSAPP table. Each customer will need to determine which is appropriate for their circumstances.
A. Delete the Application Group and Folder definitions from your V7.1 tables and re-migrate the metadata.
B. Use the V7.1 Administration Client to manually correct the missing data. This will include data on the Load Information tab and the View Information tab. Note that the old, incorrect data will still reside in the PREPROCESSOR and FIXED_VIEW columns of the ARSAPP table, but the new, correct data will have been appended onto the end of these columns. The bad data is ignored and the new data is used by OnDemand.
C. Unload the ARSAPP table. Use an editor to change the code points for the left square bracket, right square bracket and commercial at from the incorrect values to the correct ones for your database. Reload your ARSAPP table from this corrected data.