Re: Password Security

I am I the only one who thinks these sound like homework questions for an
operations class?




From:
John Mathew <johnmathew400@xxxxxxxxx>
To:
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date:
07/24/2012 11:39 AM
Subject:
Re: Password Security
Sent by:
midrange-l-bounces@xxxxxxxxxxxx




Really thats true defently the programmers productivity will go down...
dont know exactly why they need this...and the advantage of this.

I will give try not suggesting this...

John




________________________________
From: "Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx"
<Tommy.Holden@xxxxxxxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, 24 July 2012 9:54 PM
Subject: Re: Password Security

The programmers, etc can have the value for limiting sessions set on their

individual profiles to allow more sessions as desired.


Thanks,
Tommy Holden



From: "sjl" <sjl_abc@xxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 07/24/2012 11:21 AM
Subject: Re: Password Security
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Your business analysts, and programmers [if you have any] are going to be
very upset with this requirement, since it significantly affects their
productivity.

- sjl

John wrote:

regarding option4

Sorry i was miscommunicated actually it should be prevent system and
user profiles from logging onto multiple workstations at same time.

I should not allow logging more than one session/workstation.... .....

QLMTDEVSSN (how many session we can limit with this)

Regards,
John






________________________________
From: "rob@xxxxxxxxx" <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, 24 July 2012 9:34 PM
Subject: Re: Password Security

Option 3. See QPWDVLDPGM. Search for that in the Infocenter. You can
customize that to your hearts content.

Option 4. So, you're willing to allow them to use multiple sessions of
5250 at once? Good for you! Now, you just want to stop them from running
multiple Queries at the same time interactively. Let's try a different
tack. Instead of that, how's about throttling their performance?
One way is to change the command RUNQRY to not allow it to run
interactively outside of a program at all. When you do a WRKQRY and use
any option to run it uses RUNQRY under the covers. See CHGCMD RUNQRY
<F4>. You can drop *INTERACT.
Another way to throttle them is lower the QRYTIMLMT by using the CHGQRYA
command.
You may also want to check the options available in the query options
file, otherwise known as QAQQINI. Search the infocenter on that.

Option 5 is the easiest. See WRKSYSVAL QPWDEXPITV



Rob Berendt