RPG compilation errors QRG4033 and QRG7030 due to model-database mismatch in CA 2E

Products

• CA 2E

Issue/Introduction

RPG program generation and compilation fails with the following errors:

• QRG4033 Severity: 30 - External name specified for Rename option is not valid. Option ignored.
• QRG7030 Severity: 30 - The Field or indicator is not defined.

These errors occur when the generated RPG source references fields or record formats that do not exist in the physical file structure used during compilation.

Environment

• CA 2E (All Versions)
• IBM i

Cause

The CA 2E model and the physical database files are out of sync. This typically happens when:

1. Fields are removed or renamed in the model but the changes are not promoted to the target environment.
2. A development model is modified without re-compiling the associated physical and logical files.
3. The library list for the compilation job points to an outdated version of the physical file.

Resolution

Follow these steps to synchronize the model and database:

1. Identify missing fields by running the command DSPFFD on the physical file in the development, QA, and production environments. Compare the results to identify discrepancies in field names or missing fields (e.g., ####, ####).
2. Verify the file definition in the CA 2E model. Ensure all fields referenced in the program logic are present in the file's field list.
3. If discrepancies exist, update the model and re-compile the physical and logical files in the affected environment.
4. Perform a Forced Generation** of the file and the failing program to rebuild internal cross-references.
5. Verify the library list of the generation/compilation job to ensure it references the correct physical file library.

Additional Information

**The most common way to force generation is by manually setting the Required Action indicator to GEN.

• Location: Access the Work with Model Objects (YWRKMDLOBJ) or Work with Objects by List (YWRKOBJLST) panels.
• Procedure: Locate the object (e.g., an access path or external function) and manually type GEN in the Required action column.
• Result: When you next run the generation process (e.g., using YSBMMDLCRT), CA 2E will include this object in the job list regardless of whether it was previously marked as changed. CA 2E automatically resets this indicator to blank once the object is successfully regenerated.

See also:

Problems compiling both RPG and CBL source in same model