RE: QLMTDEVSSN like for iseries access -- MIDRANGE-L

Rob:

I think you need two data stores here. One is from QUSLJOB, and one is
user-defined, which contains permanent and temporary blocking criteria, such
as QSECOFR from remote terminals (permanent) or user PHIL from all sessions
not coming from 10.21.72.12 (temporary).

--phil 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, January 10, 2005 1:59 PM
To: Midrange Systems Technical Discussion
Subject: RE: QLMTDEVSSN like for iseries access

How does one get QUSLJOB to populate an index or a database versus a user
space?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Phil Ashe <Phil.Ashe@xxxxxxxxx> 
Sent by: midrange-l-bounces+rob=dekko.com@xxxxxxxxxxxx
01/10/2005 02:37 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






Others have said this, there are lots of ways to get a 5250 terminal
session, including STRPASTHR, if you have multiple servers. If you want to
control this traffic along with Telnet, etc., you probably want to use an
initial program on the user profile. This will give you a single place to
check and debug problems regardless of how the 5250 session started on the
system. 

Also, if you want to roll this out to a subset of users, it's easier to 
deal
with this at the user profile level instead of the exit program. All 
Telnet
jobs will invoke any exit program installed. 

If you haven't dealt with exit programs, the Telnet exit point is a poor
choice to learn on. You need to cycle the Telnet server to replace the
program, and cycling the Telnet server knocks off users. 

Based on previous suggestions, I highly recommend you use a database file 
or
user index to store the active jobs, rather than data areas because of 
speed
of completing the test. This is an area where "response time" is highly
visible. 

Until you get this "perfect" (whatever your standard of perfection is), a
database file is easier to deal with. You can query the records and clear
the file as needed. When it's perfect, you can convert to user indexes 
(and
test all over again).

Phil Ashe
NetIQ Corporation
Houston, Texas
713-418-5279


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, January 10, 2005 1:02 PM
To: Midrange Systems Technical Discussion
Subject: RE: QLMTDEVSSN like for iseries access

Yes.  However a user can also manually name the sessions.  There's nothing
stopping me from naming a session on the PC name ROB to GDSPC40S3.  Our
users, who span multiple systems often do something like ROBHQS1, ROBHQS2,
ROBSYSS1, ROBSYSS2 for the i5 GDIHQ and the i5 GDISYS.  So figuring out 
the
naming would be no great shakes for some of them.

I do appreciate the original posters attempt to work with this scenario
instead of adopting the standard IS audit mantra that you should just turn
on limit device sessions and go from there.  I typically ignore that
suggestion.  I understand what problem they are trying to solve, but
disagree with their method.

Anyone figure out a good solution, let me know.  We do currently have a
problem with users sharing user id's.  Normally it's discovered when 
someone
goes on vacation and you get a request to reset their password.

Granted all of our solutions will only thwart 5250, and not C/S 
applications
and that genre.

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Wilt, Charles" <CWilt@xxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
01/10/2005 01:50 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






Should have been more specific...

You can't have the exact same device names on the iSeries.  But you can 
have the same device name configured in multiple CA sessions with the 
"avoid duplicate names with other workstations"/ checked; which will add a 

unique suffix to the base device name.

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

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Wilt, Charles
> Sent: Monday, January 10, 2005 1:40 PM
> To: Midrange Systems Technical Discussion
> Subject: 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
> 
> 

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


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