Kbase P100683: How to verify if the DB2/400 cross-reference files are corrupted on the AS/400 system
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/1/2005 |
|
Status: Unverified
GOAL:
How to verify if the DB2/400 cross-reference files are corrupted on the AS/400 system
GOAL:
What is a possible problem when loading df file with a word index
FACT(s) (Environment):
IBM AS/400 (RISC)
FIX:
Progress implements word index support based on physical file triggers. The DataServer adds 6 triggers (ADDPFTRG) on the file you have a word index defined and manages them via a special program (PROWISTRG). The corruption of the cross-reference files makes it impossible to add triggers to physical files on the AS/400. ADDPFTRG command will fail with the error message CPD32E7 in the joblog and the reason code 6: "Cross reference failed with returned code <xN> and diagnostic code <N>"
Here are the exact steps how to check the cross reference files for possible corruption:
1. Type GO LICPGM at the command line and press Enter. The Work with Licensed Programs menu appears.
2. Type 5 (Prepare for Install) and press Enter. The Prepare for Install display appears.
3. Select the option to verify system objects and press Enter. The system verifies the system directory entries and adds the QSECOFR and QLPINSTALL user profiles if necessary. Database cross-reference files are checked for errors.
4. If the database cross-reference files are in error, you will see message CPI3DA3. Follow the instructions of this message to resolve the errors before you continue.
5. If the database cross-reference files are not in error, you will see a completion message at the bottom of the display. Press F3 (Exit) to return to the Work with Licensed Programs menu.