|
No, the Connect has always been QTCP (this is the connection when getting the login screen... there is no userid at that point). All other commands are different userids after that, but the initial connect has always been QTCP. Brad On Fri, 21 Jul 2006 11:28:28 -0400 rob@xxxxxxxxx wrote:
That's always been different than QTCP. I've written my own exit programs. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Brad Stone" <brad@xxxxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 07/21/2006 11:53 AM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: FTP, Connections and QTCP User ID It's actually the userid passed in by the FTP exit program. Brad On Fri, 21 Jul 2006 11:21:33 -0400 "Jim Franz" <franz400@xxxxxxxxxxxx> wrote:If they are seeing this from within applications, the program status data structure has both id's. QTCP is in @UID, the log on user is@CUSERD* PROGRAM STATUS DATA STRUCTURE * D SDS D @PNAME 1 10 D @JOB 244 253 D @UID 254 263 D @CUSER 358 367 jim franz ----- Original Message ----- From: "Brad Stone" <brad@xxxxxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Friday, July 21, 2006 11:39 AM Subject: FTP, Connections and QTCP User IDI am working with a client who is seeing connectionstotheir FTP server with a "real" User ID and not QTCP. I've always seen that when you initially connect totheFTPserver it uses user ID QTCP. But in this case it's connecting with their own user id. They are on V5R3, so I am not sure if something has changed, or if there is a way to configure an FTPclient toconnect with a different user id. There is just one UserID that is doing this. Allothersinitially connect with QTCP. Thanks for any info. Brad www.bvstools.com -- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit:http://lists.midrange.com/mailman/listinfo/midrange-lor email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review thearchivesat http://archive.midrange.com/midrange-l.-- 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.Bradley V. Stone BVS.Tools www.bvstools.com -- 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 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.
Bradley V. Stone BVS.Tools www.bvstools.com
As an Amazon Associate we earn from qualifying purchases.
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.