Yes, delete the QUSRSYS version. Replicate QSYS into QUSRSYS and change QUSRSYS. No need to change QSYS. This is the shipped version. You can also create duplicates into other libraries or schemas to create unique environments or testing.

One last thing, the QAQQINI file is read immediately before each and every SQL statement. So, you can alter values on the fly, thus fine-tuning individual statements prior to their execution.


Jerry Adams wrote:
I installed the latest V5R4 Cume yesterday, and one of the special instruction cover letters noted that to take advantage of the PTF it would be a good idea to update the Parallel_Degree parameter. All fine and good, but I noticed that there are two [2] QAQQINI files on our System i5.

So I went to the Midrange archives for help and solace. So I found that there usually are two versions of the table; one in QSYS and the "real" one in QUSRSYS. I gathered that the one in QUSRSYS is the one used by most (all?) system functions. But I noticed that the one in QSYS had more parameters defined (30) than the one in QUSRSYS (23). I suspect that the reason for the difference is the V5R3 -to- V5R4 upgrade we did last year. But the new version (QSYS), I'm surmising, didn't get replicated to QUSRSYS.

OK so far. My question is: Can I simply delete the version in QUSRSYS and replicate (using CRTDUPOBJ) the one in QSYS to QUSRSYS? In practice it probably doesn't matter since all of the parameters in both versions have a value of *Default, but I'm a neat freak (don't look at my desk, though).

Also, does it even matter if the parameter values are ever updated in QSYS? Or do I need to update both versions whenever I change a parameter's value?

Thanks.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.