changing qpquprfil in query

5 pts.
Tags:
AS/400 Query
QPQUPRFIL
how do i change the qpquprfil in as/400 query. i have doone it before and i know it is doabe but ican't rember how. i mean thesystem one not the one at the user level??

Answer Wiki

Thanks. We'll let you know when a new response is added.

If you mean, how do you change the system-supplied qpquprfil file so that it uses different outq/forms/other attributes, you would simple use the prompted CHGPRTF command and change whatever printer file parameters you wanted. You would have to repeat this change process every time you put up a new release of OS/Query.

If you wanted to change it for just a single run instance, you would override it with a OVRPRTF command, again specifying the parameters of interest.

Carter

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Gilly400
    Hi, Best to use the OVRPRTF option for this. It's never a good idea to change the system-supplied objects. If you do, then every time you upgrade the OS, you'll need to go through and change them all again. Then you wonder which ones you changed, how many of them you changed, not to mention exactly which parameters you changed. If you can keep to using overrides, then you won't need to do this. Martin Gilbert.
    23,730 pointsBadges:
    report
  • VBOTone
    Actually, it is easy to keep track of changed objects with a little organization. We have placed an IBM_CHANGE library high in the system library list to avoid redundant programming efforts.
    55 pointsBadges:
    report
  • Gilly400
    Hi, The idea of an IBM_CHANGE library is ok for most things, but you can still get problems with this when you get OS upgrades. For example you want to change the standard attributes of one of the system supplied print files, so you take a copy to your IBM_CHANGE library and change the attributes of your copied print file. Along comes a new OS upgrade, with a new version of the print file - any programs that use this print file will find your *old* version of the print file instead of the new one. The OS programs that use this print file may crash or dump, until you remove your copied print file or replace it with a copy of the one from the new OS (with your attribute changes re-aplied). Personally I think it's best to avoid changing system objects as far as possible. Cheers, Martin Gilbert.
    23,730 pointsBadges:
    report
  • TomLiotta
    I agree with the principle of avoiding changes to IBM-supplied objects. If it needs to be done, it's best to do it to a duplicate and use the library list to access the necessary version. Create the duplicate and apply the change together in a CL program. Add statements to that same program for each changed object. When upgrading the OS, run that program after the upgrade completes in order to capture new versions from the upgrade and to apply your changes to those new duplicates. This keeps track of changes and helps recover them later. Tom
    125,585 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following