× 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: Logging file transfer user access -Reply
  • From: John Cirocco <JCirocco@xxxxxxxxxx>
  • Date: Sun, 24 Aug 1997 20:45:48 -0400

Ralph,

>>You can use the PCSACC exit for this as long as everyone is using
>>the IBM supplied file transfer user interface for all versions of PCS and
>>CA/400. For the "optimized clients", OS/2 and Win '95/NT, if someone
>>has written their own program and uses the PC file transfer API's you
>>will also need to use the exit point for the database server.  See the
>>manual "Server Concepts and Administration" for more information on
>>the exit points and example code.  You may find it convenient to set
>>PCSACC to *REGFAC and register a file transfer exit with the
>>registration facility (WRKREGINF).  This allows you to manage all exit
>>points except DDM in the registration facility.

I have never used Exit Points before.  I will check out the manual above
along with the examples others have offered.  Is this as confusing as I
think it is?

John
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.