RE: User profile limit to 10 characters. We need more...

I'll second the use of accounting code for identifying people. I used to
use that for division and empid to check for terminations so we could
disable the profile and audit reports for SOX.

The systems I inherited used to use a generic ID like Rob's example.
Problem was... Who is FIUSCC01 or RMBY15 when you're looking at jobs,
spool files, etc.? I switched to first initial, last name and it made life
a lot easier. Of course, then we found the programs that had hard-coded
profile names to compare against for some things - jeesh - what were they
thinking?



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, May 11, 2012 4:27 AM
To: Midrange Systems Technical Discussion
Subject: Re: User profile limit to 10 characters. We need more...

A few comments...

One, by significance it was asked if you are doing something like the
following. Rob Berendt works in the US for department 1600. So his user
profile is US1600RB01. If so, see about changing your ways. Use other
fields to contain this information. No law about perhaps putting this info
in part of the text description field. The job accounting code is where we
stick department hyphen employee number. We sync this up with Lotus Notes
and it works well for us.

Two, syncing passwords. We use a product called IBM Tivoli Identity Manager
to sync passwords across Lotus Notes, the i, Active Directory and more.
Works well for us. You can even roll out the ability for users to reset
their own passwords. Just like banks and other high security operations
allow. With that I change my password in Windows and it's immediately
propagated to all 10 of my lpars. I haven't enhanced it yet to CHGSVRAUTE
or my sst password. Hate to throw that in the mix for the few concerned
with that.

We were using EIM for awhile but that one sort of fell by the wayside. Not
sure how well that's supported by NetServer.


Rob Berendt