http://itknowledgeexchange.techtarget.com/itanswers/spooled-files-not-saved-after-printing-when-migrating-to-v5r4/ Sat, 25 May 2013 17:28:03 +0000 hourly 1 http://itknowledgeexchange.techtarget.com/itanswers/spooled-files-not-saved-after-printing-when-migrating-to-v5r4/#comment-68351 tomliotta Thu, 24 Sep 2009 20:44:01 +0000 #comment-68351 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.

]]> http://itknowledgeexchange.techtarget.com/itanswers/spooled-files-not-saved-after-printing-when-migrating-to-v5r4/#comment-68341 wlakesearcher Thu, 24 Sep 2009 18:43:18 +0000 #comment-68341 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.

]]>