Spooled files not saved after printing when migrating to V5R4

100 pts.
Tags:
Spool files
V5R4
We migrated from V5R3 to V5R4.  A user tells us that spooled files that used to change to SAV after printing are 'disappearing'.  What could have changed?

Answer Wiki

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

When youy installed the new released “System objects” get replaced.
If you had modified them, you lose those changes.
My guess is you had done a CHGPRTF QSYSPRT SAVE(*YES) or (some other printer file) when you were running V5R3.
You need to run that command again.
**
Most shops will create a CL program that contains these types of changes so they can just run it when a release update is done. This would include and CHGMDDDFT you may have done.
This also serves as a form of documentation.

Discuss This Question: 2  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
  • Wlakesearcher
    Thank you Charlie Brown. One of the places where we noticed this problem was when printing a JDE World Writer. I ran it and looked at the attributes of the spooled file - it said Save(*no). I changed qsysprt, reran the worldwriter and checked the attributes of the spooled file - it said Save(*yes). I am thinking that this change to Qsysprt will also correct the reports that are produced using JDE Electronic Burst and Bind (EBB). Although I can't find reference to it anywhere, JDE must get its defaults from QSYSPRT for reports.
    100 pointsBadges:
    report
  • TomLiotta
    If JDE is using your QSYSPRT for its defaults, maybe you should complain to JDE. JDE should supply its own printer file for its own use. Relying on an IBM-supplied, generic, system-wide printer file is simply asking for trouble. IMO, vendor programs shouldn't even need QSYSPRT to exist on the system except when calling a system function that uses it.
    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