Referential constraints within V4R5 QUSRSYS has QAYIVSYS as the parent file when restoring/upgrading to V5R1M0. The constraints sit check pending and subsequently the upgrade fails disastrously with QUSRSYS showing up in error and the system needs to be reloaded. Do you have any idea why this is happening?
Check the Database Relations for the file in QUSRSYS. I would assume that someone has built a logical or permanent SQL index over that file. Once removed, you should be able to upgrade without any further problems. This usually happens when someone builds a logical for a utility over a file in a "Q" library. As a general rule, building logicals or constraints in permanent SQL indexes (which creates a logical data path), is not a good idea.
MORE INFORMATION ON THIS TOPIC
The Best Web Links: tips, tutorials and more.
Ask your OS/400 questions--or help out your peers by answering them--in our live OS/400 discussion forums.
OS/400 Discussion Forum: Post your questions, and get answers from other iSeries users as well as search400 experts.
Search400.com's targeted search engine: Get relevant information on V5R1.
Ask the Experts yourself: Our OS/400 gurus are waiting to answer your questions.
Dig Deeper on Past Releases
Related Q&A from John Brandt
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.