Re: Exit point QIBM_QTMF_SVR_LOGON vs QIBM_QTMF_SERVER_REQ

[rob@xxxxxxxxx]

Interesting idea Vern.  Does anyone know if it is a guarantee that the 
logon and the requests are processed by the same QTFTP* job?  And that not 
more than one FTP session is active at a time per QTFTP* job?

Boss came up with suggestion to create a iSeries user on the fly and store 
that in the custom user file.  Then, with an index on this user profile I 
can tie it back.

Cleanup would involve blasting any user profile with this prefix that is 
not locked by a current job.  And purging them out of the custom user file 
field.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/14/2003 04:56 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Exit point QIBM_QTMF_SVR_LOGON vs 
QIBM_QTMF_SERVER_REQ


Rob, I believe the SERVER_REQ will be handled by the same job? If so, what 

about storing the name in a data area? or data queue, keyed on job name 
and 
original login id? or a small keyed file?

HTH

Vern

At 03:03 PM 3/14/2003 -0500, you wrote:
>If we change user profiles in exit point QIBM_QTMF_SVR_LOGON, any chance
>to tie that back in to the original user in exit point
>QIBM_QTMF_SERVER_REQ?
>
>For example, if we have numerous users from company XYZ ftping us
>information.  User's like:  RALPH, JONI, etc.  These users don't really
>have iSeries user id's.  Then what I do is use exit point
>QIBM_QTMF_SVR_LOGON to switch them to an iseries user id, let's say
>FTPTEST.  Then when exit point QIBM_QTMF_SERVER_REQ kicks in it only 
knows
>them as FTPTEST, but I want to keep RALPH from doing some of the stuff
>that I let JONI do.
>
>Rob Berendt
>--


_______________________________________________
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.