We use a product call NBSPOOL from Quest Software. We use it to transfer
spoolfiles from one machine to another where it is loaded into VISTA, a
report viewing tool.

> -----Original Message-----
> From: Bob Comeau [SMTP:[log in to unmask]]
> Sent: Wednesday, August 11, 1999 12:24 PM
> To:   [log in to unmask]
> Subject:      FTP and spoolfiles
>
> 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