KB Article 9546

Contact Tech Support

 Email Tech Support
 (250) 655-1766
 [7:30 - 5:00 PST]
Your Meeting ID will be Provided by a Rep.
Tech Support
Tech Support Home
Software Updates
Knowledge Base Search
Recent KB Articles
Product FAQs
Code Samples
Tech Blog
System Requirements
Installation Instructions
Support Testimonials
Contact us to...
Create a Ticket
Request a Free Demo
Suggest a New Feature
Submit Feedback
Upload a Large File
Other Services
Software Training
Professional Services

Various issues related to links between files where either within the definition, or in the generated code, it seems like there are bogus (duplicate, orphan, etc.) records in the underlying files. This task explains some variations and solutions.

Product: ProGen Plus Type: Frequently Asked Question

There are a few variations on this issue.
In one of them, when you go into your definition it opens at the Work with Files screen, reporting that links are incomplete. When reviewed, the link appears fine, and on typing over any of the characters in the linking field name, is accepted as correct and saved.
In some cases, the program may not compile with an extra key field generated in the link on generation. In other similar situations you may be able to get into the definition, but it doesn't compile because there are extra, blank key fields in the link. This would be manifested with RNG5030 errors in your key field definitions (@DL01, etc.).
Another scenario is that you add new keys to an auxiliary file, and when you check the link from the Work with Files screen you see the right number of new keys, but one of the previous ones is repeated, rather than the new key being inserted into the correct location.
Explanation & Solution:
All these problems tend to be related to extra, duplicate or orphaned records in the internal file GN#FKRF.
In most situations you can resolve the problem by following these steps:
  • Go into the definition to note which field(s) were required in the link.
  • Run the command ZWRKPDFINT. Press Enter past the nefarious warning.
  • At the menu presented, select option 1 to Work with Definitions.
  • Find your definition and select option 9 to Work with Files.
  • Select option 3 to work with GN#FKRF.
  • In the list of links to the file in question, look for extra, duplicate or orphaned records. Delete these.
If you delete any extras, you can correct these when you go back into your definition; deleting records here is easily resolvable through the definition by just adding the keys back in. What the definition can't handle is presenting bogus records from this file (hence the need to come in the back door...).
Go back into your definition and save, generate and compile. The error should be resolved.
Tech Note: An item similar to this  (most recently encountered in ProGen 9) had come up before and is described in internal task 1801. It was reported as fixed in an update to ProGen 5.

Rate This Article

Did this example help you to achieve your goal?
 Yes  No  Don't Know

Enter additional comments below.   If you want to hear back from us, include your contact information.

Email Address:
Please enable JavaScript in order to rate this page.