|
In response to various emails: I need to be able to take the object(LIBRARY/DBF) and derive who created the file in order for the application to properly handle the data file. Currently, I know that the file arrive in a library, I know the job(iSeries server job) that created the file. How do I connect this object information to the user exit log, what is the hook. What I have heard so far: Exit Log: Job Name, Number, User, Library , File, Original User, Transferred to User QAUDJRN Job Name, Number, User, Library , File This key structure seems to lacking "something". Michael -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of JMichael Smith Sent: Friday, January 05, 2007 8:22 AM To: midrange-l@xxxxxxxxxxxx Subject: FTP question As a baseline, my knowledge of FTP and how it works is limited. My question is based on the following scenario: 1> User1/Password1 initals an FTP request to the iSeries 2> Exit program on the iSeries recognizes User1/Password1 and changes it to a "common" FTP "user profile" that has proper authority to put a file 3> FTP request to put a file to the iSeries is completed and the user log's off At a later date, how can I determine who User1/Password1 was... inorder to properly process the data in the file. TIA Michael -------------------------------------------------------------------------- ---- This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail postmaster@xxxxxxxxxxxx ========================================================================== ==== -- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. -------------------------------------------------------------------------- ---- This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail postmaster@xxxxxxxxxxxx ========================================================================== ==== ------------------------------------------------------------------------------ This message contains information from Certegy, Inc which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e:mail postmaster@xxxxxxxxxxxx ==============================================================================
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.