RE: QLMTDEVSSN like for iseries access

No good way that I can think of.

You could configure client access to use the computer name as the device name, 
then check the device names.

But, there'd be nothing to stop somebody from having the same device name 
configured on multiple PCs.



Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx
> [mailto:midrange-l-bounces+cwilt=meaa.mea.com@xxxxxxxxxxxx]On 
> Behalf Of
> Emilio Padilla - Sistemática Intl.
> Sent: Monday, January 10, 2005 1:28 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: QLMTDEVSSN like for iseries access
> 
> 
> What a bout people that is coming in behind nat? How do I 
> know tht does are
> different pcs? 
> 
> 
> EAPT
> Informática corporativa
> 
> 
> -----Original Message-----
> From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx] 
> Sent: Monday, January 10, 2005 12:23 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: QLMTDEVSSN like for iseries access
> 
> Why the data area and not a call to an api to find out what 
> other jobs the
> user has access to and find the IP Address of those jobs?  No 
> worry about
> restart procedures, like if the user signed off of all 
> sessions, moved to
> another PC and then found out that the data area still existed.
> 
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> PO Box 2000
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
> 
> 
> 
> 
> 
> Jonathan Mason <masonjo1@xxxxxxxxxxxxxxxx> 
> Sent by: midrange-l-bounces@xxxxxxxxxxxx
> 01/10/2005 12:54 PM
> Please respond to
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> 
> 
> To
> Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> cc
> 
> Subject
> Re: QLMTDEVSSN like for iseries access
> 
> 
> 
> 
> 
> 
> I used to do a similar thing, limitting users to 4 sessions 
> unless they 
> had a user class other than *USER in which case they were allowed 
> unlimmited sessions across multiple workstations.
> 
> The way I did it was to use the users Initial Program to 
> check on how many 
> sessions were active and respond accordingly.  To allow 
> multiple sessions 
> on the one PC I would do something like the following in the 
> users initial 
> program:
> 
> a) Retrieve the IP address for the current jobs joblog.  
> Peter Colpaert 
> has posted a utility that should help with this on Leif 
> Guldbrand's site 
> at www.think400.dk/downloads.htm.
> 
> b) Attempt to retrieve the contents of a data area with the 
> same name as 
> the user ID into a 25 character field.  The data are should 
> hold a date in 
> the first 10 chars and an IP address in the last 15.
> 
> c) If the data area doesn't exist then create it (Size: 25 
> chars), setting 
> chars 1-10 to the current date and chars 11-25 to the IP 
> address retrieved 
> in step a) above
> 
> d) If the IP address is different and the date is the same 
> and this is not 
> the only interactive session for the user then display a 
> message and sign 
> him/her off.
> 
> e) Update the data area with the current date and IP address.
> 
> f) Continue with the rest of the initial program
> 
> All the best
> 
> Jonathan
> www.astradyne-uk.com
> 
> 
> -----Original message-----
> From: Emilio Padilla - Sistemática Intl. EPADILLA@xxxxxxxxxxxxxxxxxx
> Date: Mon, 10 Jan 2005 17:30:02 +0000
> To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx
> Subject: QLMTDEVSSN like for iseries access
> 
> > Hi everybody, I need some help, I've been ask to create a 
> function that
> > works like the QLMTDEVSSN system value on 3476 terminal but 
> in PC's with
> > iseries access.  Let me explain a little better: 
> > 
> > The user must have the ability to open any number of 
> session on 1 pc 
> but, he
> > shouldn't been able to open 2 sessions on 2 differents pc.  I was 
> thinking
> > in something like a combination between a telnet exit 
> program and an 
> initial
> > program on the user profile.  Any suggestion will be appreciated.
> > 
> > EMILIO PADILLA T
> > E-mail: epadilla@xxxxxxxxxxxxxxxxxx
> > 
> > 
> > -- 
> > 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.
> > 
> 
> 
> Jonathan Mason
> www.astradyne-uk.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.
> 
> -- 
> 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.
> 
>