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?
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.
Last Wiki Answer Submitted: September 24, 2009 6:26 pm by CharlieBrowne33,730 pts.
All Answer Wiki Contributors: CharlieBrowne33,730 pts.
If you live outside the United States, by submitting your email address you consent to having your personal data transferred to and processed in the United States.
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.
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.
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.
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.