Re: Limiting FTP sessions

["Carel Teijgeler" <coteijgeler@xxxxxxxxx>]

Rob,

not much help from here, but ...

You can change the number of FTP sessions simultanuously active on the AS/400: 
CHGPTFA. I do not think this is the most likely solution.

It is is strange, though that one FTP call from MSIE will generate multiple 
sign ons. Perhaps a setting in the browser is at fault here.



*********** REPLY SEPARATOR  ***********

On 31-3-03 at 10:18 rob@xxxxxxxxx wrote:

>Well, I suppose that, if the user profile is locked then I could issue an 
>immediate endjob for that other user.
>
>But, then I could also look at it this way, how often would multiple ftp 
>sessions be caught at the same time?  It's not like 5250 in >which you leave a 
>session running for any great length of time.  Thus if they are sharing 
>profiles, then they'd really have to be >cranking out the sessions to get two 
>going at the same time.  With the checks on:
>limiting what ftp operations are allowed,
>limiting which directories they can upload to and which they can download from,
>limiting how much space may be used by their user profile,
>Should I really spend anymore development dollars, or blood pressure on this 
>issue?
>
> AND
>
>This is what I figured out what was happening.  Lovely (dripping with sarcasm) 
>MSIE would:
>I)  Request exit point is called under QTCP with a request code of 0 for log 
>on.  I allow that.  Job=043731/QTCP/QTFTP02845.
>II)  Login exit point is called under ANONYMOUS which I forbid. 
>Job=043731/QTCP/QTFTP02845. 
>III)  Request exit point is again called under QTCP with a request code of 0 
>for log on.  I allow that.  >Job=043732/QTCP/QTFTP00078.
>IV)  Login exit point is again called under ANONYMOUS which I again forbid.  
>Job=043732/QTCP/QTFTP00078. 
>IV-A)  Browser user is prompted for User id and password 
>V)  Request exit point is again called under QTCP with a request code of 0 for 
>log on.  I allow that.  >Job=043733/QTCP/QTFTP00081.
>VI)  Login exit point is called with 'dummy' user id.  I allow that by giving 
>it a return code of 3 which allows logon but overrides user 
>profile.  Rest of it looks fine.    Job=043733/QTCP/QTFTP00081.
>VII)  Requst exit point is (strangely) called again under QTCP with a request 
>code of 0 for log on.  I allow that.  >Job=043734/QTCP/QTFTP00079.
>VIII)  Login exit point is called with 'dummy' user id.  However, I stop it 
>because the user profile I've overridden to is assigned to >another ftp job 
>(043733/QTCP/QFTTP00081).
>VIII-A)  Browser user is again prompted for their user id.
>
>The MSIE browser does the double whammy with steps V/VI & VII/VIII.  I 
>modified my program to stop checking for locks on the >user profile in order 
>to pay homage to the MSIE gods.  However now the problem becomes is there 
>anyway to stop a browser user >from having more than one session?  I believe 
>the answer is no.  What do you think?