> The problem that I'll be facing stems from the fact that our
> users come
> from a variety of organizations (each organization could have
> originated
> from a different company that was acquired by Raytheon), and,
> unfortunately, there may be payroll number duplication (While
> a new unique
> payroll number is available, due to historical reasons and
> field size, most
> of our user ids are based on the 'legacy' numbers).
>
> The problem can be avoided if a further check of the employe's name
is
> performed.  However there is no guarantee that the spelling
> of the name
> will be consistent, in the input file and our security database
(Users
> could have been added by different application managers).

Any reason you can't ask the users themselves? You don't mention the
environment, but a logon-time command, batch file, UDC
(or--preferably--command file called from an OPTION LOGON UDC) or
equivalent can see if the user's information is up to date; if not,
collect the appropriate info (names, ID numbers, payroll center,
whatever) and stuff it into a database. When your HR updates come in,
run them against the database. No guessing required. You can also use
the results, in combination with the HR info, to identify "problem"
user IDs and correct, or at least cross-reference, them in advance.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *