× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: RE: Copying AFP Spooled Files to a PF
  • From: "Alex Moore" <alexm@xxxxxxxxxxxxxxxx>
  • Date: Thu, 29 Jun 2000 11:23:59 -0400
  • Importance: Normal

Title: Copying AFP Spooled Files to a PF
We set up a user profile at the remote site using the name of the outq we want the spool file to go to - like "PRT04".  The user profile has PRT04 as it's default outq.  Net result is when you send a spoolfile to user PRT04 it ends up in the proper outq on the remote system.
-----Original Message-----
From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Brad McDaniel
Sent: Thursday, June 29, 2000 8:56 AM
To: 'midrange-l@midrange.com'
Subject: Copying AFP Spooled Files to a PF

Does anyone know how to copy a SPLF type *AFPDS to a physical file without losing any of the AFP attributes?  I've seen many questions about this in the archives, but can't seem to find an answer (an answer I like, anyway :))

I have been using SNDTCPSPLF, but we are having problems at the remote site directing where each SPLF should go.  My thought was to copy the splf's to a PF, and then FTP the file.  That way we can put it wherever we like.  (i.e. /user/spool/annuity/etc...).  This works with regular splf's, but not AFP splf's.

Any suggestions?!?!  I'm stuck.

Brad McDaniel
Information Services
Annuity Board, SBC
(214) 720-6546


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.