We use Netbase shadowing to simultaneously create the spoolfiles on both our development machine and the production machine, with the backup machine having a suitably high outfence so that the spooler never tried to print these spoofiles.  It was very easy - you just needed to have the same printer defined (by class) on both machines and then setup a printer file equate in the netbase directory program. This technique used to be used for all of our printers, but with the introduction of network printing, it is now only used for the main system printer (LP). 

>>> Bob Comeau <[log in to unmask]> 11/08/99 >>>
We just updated to express 7 and I was under the impression that FTP would
now handle non-standard MPE files more elegantly, including spoolfiles.

KSAM files now transfer nicely but I see little change in the handling of
spoolfiles, not that my testing was exhaustive and perhaps my expectations
were a little high.

I would like to be able to PUT Oxxx.OUT.HPSPOOL and have it appear on the
other side in the spooler as Oyyy.OUT.HPSPOOL owned by whoever I logged on
as
or maybe 'Oxxx.OUT.HPSPOOL with similar ownership.  The put command appears
to execute and transfers nnn bytes without any error.  Problem is the file
is nowhere to be found at the other end.  I suspect it is being created as
temporary file Oxxx.OUT.HPSPOOL under the programmatic session, and cannot
be
closed as a permanent file with that name since the session is not in that
account.  Explains the disappearance, but not the lack of an error message.

We have a been using a workaround involving copying the spoolfile,
transferring
the copy, manually logging on the other system, prefixing the received copy
with
spacing control, and then send that to the spooler on the receiving system.
This is done via a couple UDC's but still seems like a lot more work than it
should be.

We don't have a real printer on the source system, and no network printers,
hence the song and dance.

Any suggestions for a smoother transfer of spoolfiles?

Bob