SNDNETSPLF with overlaysPublished by: renojim on 11 Jun 2013 view comments(3)
I know this issue has been here on the forum before, but I can't find it. When sending a spool file from one machine to another, or one partition to another, what's required besides changing Data Format to *ALLDATA?
If you're configured for HPRIP (or AnyNet, or actual, honest to goodness SNA), SNDNETSPLF still works.
For SNDNETSPLF, DTAFMT(*ALLDATA) should be all you need. This tells the system to send all of the spooled file attributes, not just the content. But keep in mind that overlays and other resources must be available on the remote system. Hardcoded library names are easier, in this case, so that the remote printer writer doesn't need to be able to find the overlay in its library list. [There is an exception. For *AFPDS, the AFP printer writers know about the QFNTxx libraries automaticaly.]
SNDTCPSPLF behaves like DTAFMT(*RCDDTA). It doesn't send spooled file attributes, because the LPR protocol assumes the remote system is going to handle the spooling. I've not tried this, but DESTTYP(*AS400) and TRANSFORM(*NO) might work; feels like an IBM extension to get around the LPR limitations. Even if this works, though, you're back in the same boat with the remote printer writer needing to be able to find the overlay and other resources.
The overlay would be a stand-alone file that is associated with the SPOOL attributes. So if the copy command (SNDxxxSPLF) was smart enough, it could replicate the attributes, including the overlay, but not necessarily the overlay itself. If you store the overlay on the remote system (assuming its an IBM i system) then you could get away with it, in theory.