Spooled files not saved after printing when migrating to V5R4
25 pts.
0
Q:
Spooled files not saved after printing when migrating to 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?
ASKED: Sep 24 2009  5:34 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
0
6540 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
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 Answered: Sep 24 2009  6:26 PM GMT by CharlieBrowne   6540 pts.
0
0
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Wlakesearcher   25 pts.  |   Sep 24 2009  6:43PM GMT

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.

 

TomLiotta   8000 pts.  |   Sep 24 2009  8:44PM GMT

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.

 
0