eg Sexton came up and
> snatched his report off of the printer.
>
> Robert Crawford
> Abstract Evolutions LLC
> (210) 913-3822
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of Paul Gilmartin
> Sent: Thursday, July 13, 2023 4:53 PM
53 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXT] Re: Userid schemes
On Thu, 13 Jul 2023 17:22:12 -0400, Phil Smith III wrote:
>I've seen various schemes used for creating up-to-eight-character userids, all
>truncated as needed, of course. These are IDs I've had, won't tel
While I might agree to that somewhat, it fails when you also use the
userid for other things, such as email, where the userid is 'public'.
But, uses of alias for public view can resolve that issue.
For instance, my email userid at 'vse2pdf.com' is not 'tony', it's
something else. t...@vse2pdf.
A good userid scheme should not identify who the userid belongs to or the
job function of the person. Several places I have worked had this
philosophy. All userids that belonged to a human began with the letter U
followed by 3 to 6 random characters and numbers.
On Thu, Jul 13, 2023 at 4:22 PM P
s
Parwez Hamid
From: IBM Mainframe Discussion List on behalf of
David Spiegel <0468385049d1-dmarc-requ...@listserv.ua.edu>
Sent: 14 July 2023 14:58
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Userid schemes
Hi Paul,
You said: "...Just rema
Nah, that's an old myth that (I think) sprang up only in my
lifetime. "Man" has always applied, in English, to humans and also to adult
males, depending on context. I'm still unembarrassed to use the term
"man-hours".
At about the same time sprang up the myth that "my" indicates ownership, a
A.EDU
Subject: Re: Userid schemes
I fully agree with the general principle that one ID must have no more than one
owner. (I'll admit to exceptional cases, but I'll argue about them first.)
I've never understood the reverse principle that every user must have only one
ID. I think
For testing authorized code, it helps to have a userid with minimal privileges.
From: IBM Mainframe Discussion List on behalf of Tom
Brennan
Sent: Friday, July 14, 2023 10:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Userid schemes
I had 3 id'
.
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Friday, July 14, 2023 9:45 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Userid schemes
On Fri, 14 Jul 2023 06:43:49 -0400, David Spiegel wrote:
>
>EEOC is an Americ
I had 3 id's on each system, but all had the same sysprog capability.
Mainly it was to avoid the embarrassment of having to go to another
sysprog to fix my #1 id after I messed it up testing or changing
something. But they also came in handy for testing things like enqueues
and multiple tasks.
Being a RACF geek and a contractor for roughly half my career I've seen most of
the conventions people have shared here in this thread. The best laugh I get
talking with other mainframe geeks though was from a large bank where the
algorithm went:
First 5 letters of SURNAME + first initial of f
I can verify that CA would adjust the userid if the resulting userid was
'inappropriate'. One of my coworkers was such a case. Unfortunately, its
been too long ago and I can't remember the specifics. When CA bought our
company and told us the new rules, one guy just busted out laughing and
it t
Maybe it wasn't a "man number" as in "male human being", but rather a
"machine automation number number"? /s (but ya gotta admit, it DOES sound
like something IBM would have, complete with redundancy!)
On Fri, Jul 14, 2023 at 9:59 AM David Spiegel <
0468385049d1-dmarc-requ...@listserv.ua.edu>
Paul Gilmartin wrote, in part:
>IBM has over 300,000 employees.
While it's not relevant to the point you were making, I suspect that number is
much smaller these days. I'd heard that IBM was down to fewer than 25,000 U.S.
employees several years ago, before the Kyndryl spinoff and several more W
Hi Paul,
You said: "...Just remarking that "man number" is conspicuously
gender-specific. ..."
True, but, you have to remember the historical context for it.
You said: "...IBM has over 300,000 employees. Are the numbers required
to be unique? ..."
AFAIK, my number was unique in Canada.
My Re
On Fri, 14 Jul 2023 06:43:49 -0400, David Spiegel wrote:
>
>EEOC is an American thing. In Canada, we have an equivalent.
>
Just remarking that "man number" is conspicuously gender-specific.
>Please explain: "... Five digits isn't enough. ..." Enough for what?
>
IBM has over 300,000 employees. A
Radek, I can't read the mind of Canadian legislators, but I would guess it has
to do with fraud. I'm told that one can go through someone's trash, find old
bills (telephone, power etc) and use that information to convince someone at
the power company that I'm the householder because I have the
I fully agree with the general principle that one ID must have no more than one
owner. (I'll admit to exceptional cases, but I'll argue about them first.)
I've never understood the reverse principle that every user must have only one
ID. I think the folks who make a rule like that are simply
You could connect them all to a dummy group with no privileges.
From: IBM Mainframe Discussion List on behalf of Bob
Bridges
Sent: Friday, July 14, 2023 9:27 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Userid schemes
I like the part about service IDs
I hope that they're not, e.g., defense, financial, health.
From: IBM Mainframe Discussion List on behalf of
Matt Hogstrom
Sent: Friday, July 14, 2023 9:18 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Userid schemes
I think it’s not having multip
I like the part about service IDs. One of the challenges at most installations
I've worked at is being able to identify non-human IDs; they're easy enough to
spot by eye (because of the name attached to it), but I need some sort of
indicator when writing a program.
---
Bob Bridges, robhbrid...
ors don't like multiple user ids, but sysprogs are usually in multiple
>> roles, with different authority requirements.
>>
>>
>> From: IBM Mainframe Discussion List on behalf of
>> Colin Paice
>> Sent: Friday, Jul
ike multiple user ids, but sysprogs are usually in multiple
roles, with different authority requirements.
From: IBM Mainframe Discussion List on behalf of Colin
Paice
Sent: Friday, July 14, 2023 7:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Userid sch
A.EDU
Subject: Re: Userid schemes
Some of the UK banks use your D.O.B as an account number - such as
601225JC12 ! which exposes sensitive information.
At one point some of us had two userids. SYSPROG1 ... for sysprog stuff,
and a personal ID.
When anyone moved on they just reallocated SYSPROG1 to
IBM Mainframe Discussion List On Behalf Of
Matt Hogstrom
Sent: Thursday, July 13, 2023 7:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Userid schemes
A place I worked used initials followed by a 5 digit employee ID. xxn
Matt Hogstrom
“It may be cognitive, but, it ain’t intui
Some of the UK banks use your D.O.B as an account number - such as
601225JC12 ! which exposes sensitive information.
At one point some of us had two userids. SYSPROG1 ... for sysprog stuff,
and a personal ID.
When anyone moved on they just reallocated SYSPROG1 to a new user, and all
the accesses
Hi Paul,
EEOC is an American thing. In Canada, we have an equivalent.
Please explain: "... Five digits isn't enough. ..." Enough for what?
(I think you're confusing employee number with SIN (equivalent to
American SSN).
Regards,
David
On 2023-07-13 22:53, Paul Gilmartin wrote:
On Thu, 13 Jul
W dniu 14.07.2023 o 02:32, Paul Gilmartin pisze:
On Thu, 13 Jul 2023 20:17:38 -0400, Matt Hogstrom wrote:
A place I worked used initials followed by a 5 digit employee ID. xxn
Many years ago someone reported here that in Canada it was illegal to
use an employee# as a UID because it's con
My favourite (admittedly on a sandbox) was an IMS guy with the right
initials who snagged DL1.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-
First position for the company first letter and six digits with the
employee number. For external people, "EX" and five digits for a sequence
number. "Y" for service userids with up to seven letters taken from the
product name (as these do not logon to TSO, eight positions could be used)
Regards
Ja
When I worked at IBM it was first letter of surname plus personnel number
(5 numerics).
Another site used a role based ID such as SNRDBA for Senior DBA.
On Fri, Jul 14, 2023 at 10:31 AM Bob Bridges wrote:
> One place I worked used the employee number as proof of identify when the
> help desk pr
On Thu, 13 Jul 2023 21:56:55 -0400, David Spiegel wrote:
>
>When I worked at IBM Canada full time (1994-2002), our TSO Userids were
>XXn, where n was a person's "man number" (aka employee number).
>
No EEOC.
Five digits isn't enough.
--
gil
--
Hi Gil,
When I worked at IBM Canada full time (1994-2002), our TSO Userids were
XXn, where n was a person's "man number" (aka employee number).
Regards,
David
On 2023-07-13 20:32, Paul Gilmartin wrote:
On Thu, 13 Jul 2023 20:17:38 -0400, Matt Hogstrom wrote:
A place I worked used in
On Thu, 13 Jul 2023 20:30:41 -0400, Bob Bridges wrote:
> Since Anna knows me (or knows my voice over the phone), no issue.
>
Consider recent reports of deep fakes.
--
gil
--
For IBM-MAIN subscribe / signoff / archive
On Thu, 13 Jul 2023 20:17:38 -0400, Matt Hogstrom wrote:
>A place I worked used initials followed by a 5 digit employee ID. xxn
>
Many years ago someone reported here that in Canada it was illegal to
use an employee# as a UID because it's considered privileged HR information.
I'd guess the sa
One place I worked used the employee number as proof of identify when the help
desk proposed to help him with his password. The employee ID was printed on
the photo ID we carried around. As a security jock I never thought much of
that scheme; no better than SSN, in my opinion.
(The best schem
In my customer's company, we had such a scheme for decades:
first letter X for external, S or L for division
next letter S or M or K ... for city (where the department is located)
then two digits department number (38, 91, 95, ...)
then three chars from the name (OPP in my case)
that made XS95OP
A place I worked used initials followed by a 5 digit employee ID. xxn
Matt Hogstrom
“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
> On Jul 13, 2023, at 8:09 PM, David Spiegel
> <0468385049d1-dmarc-requ...@listserv.ua.edu> wrote:
>
>> "N" was for Number and "xxx" wa
Hi Richard,
I worked at a place where the SysProg-in-chief was an arrogant guy from
the Former Soviet Union.
His Userid was "A".
Regards,
David
On 2023-07-13 19:49, rpinion865 wrote:
I worked at a place where the VP didn't like using anything related to names,
due to name changes and the suc
I worked at a place where the VP didn't like using anything related to names,
due to name changes and the such. Rather he used Nxxx, where
"N" was for Number and "xxx" was a numeric value starting with 1 and being
incremented for the next userid. Since he was first in the shop, and he k
On of my current clients uses your scheme #1, with the variation that
contractors and other off-site personnel start with a 'V' for "vendor". So
"VPSMIT2" instead of "PSMITH2".
For a good many years a manufacturer I worked for used, let's see ... my ID
was TTGGRHB. RHB are my initials, and I thi
On my systems my ID is IMAHOG. Although, it’s really pronounced like
Hōkstrum. Never have trouble in Sweden with people mispronouncing my name :)
Matt Hogstrom
“It may be cognitive, but, it ain’t intuitive."
— Hogstrom
> On Jul 13, 2023, at 6:41 PM, David Spiegel
> <0468385049d1-dmarc
Hi Phil,
I worked at a multi--national food company in the early '90s. Their
Userid scheme was first 5 letters of surname, first letter of first
name. One guy, Mr. M. Pinchbeck became irate when people kept referring
to him (PINCHBM) as "Pinch Bum".
I didn't get excited about mine (SPIEGED). On
I generally dislike those schemes that make use of departments or projects,
as this means a new id must be assigned when the employee moves department.
However, some may argue this has its own benefit, as it prevents inheritance
of authorities in those situations.
Lennie
Lennie Dymoke-Bradshaw
ht
So many.
YaaaRR1 (aaa was 3 alpha office/project)
XXnnnRR (XX for office, no idea why 3 digits)
RUPREY01
DEVRR01
Roops
On Thu, 13 Jul 2023, 22:22 Phil Smith III, wrote:
> I've seen various schemes used for creating up-to-eight-character userids,
> all truncated as needed, of course. These are
: Thursday, July 13, 2023 6:06 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Userid schemes
On Thu, 13 Jul 2023 17:37:16 -0400, Phil Smith III wrote:
>
>So I'd be SMTHPH? Ick. I know, I'd get used to it, but.
>
I had a manager who told a tale of having been one of four Thomas J.
Murray
On Thu, 13 Jul 2023 17:37:16 -0400, Phil Smith III wrote:
>
>So I'd be SMTHPH? Ick. I know, I'd get used to it, but.
>
I had a manager who told a tale of having been one of four Thomas J.
Murrays employed at Kodak. They learned to adapt by forwarding
each others' emails by topic relevance.
Remem
On Thu, 13 Jul 2023 17:22:12 -0400, Phil Smith III wrote:
>I've seen various schemes used for creating up-to-eight-character userids, all
>truncated as needed, of course.
...
>Anyone got any other variations? This is purely a curiosity item, no agenda.
Standard at IBM Poughkeepsie when I started
On Thu, 13 Jul 2023 17:22:12 -0400, Phil Smith III wrote:
>I've seen various schemes used for creating up-to-eight-character userids, all
>truncated as needed, of course. These are IDs I've had, won't tell ya where
>each was (and omitting just firstname, just lastname, or intials):
>
It was egre
Jay Maynard wrote:
>The one I use was formed by taking the first four non-vowels of the last
>name and then the first and second initials.
So I'd be SMTHPH? Ick. I know, I'd get used to it, but.
That SMIPH03 really was my ID at CA after Sterling bought them. I didn't mind,
the 03 was perfect!
The one I use was formed by taking the first four non-vowels of the last
name and then the first and second initials.
And, of course, the usual collection of department code plus sequential
number (T40TS01), or installation code plus sequential number (YHX0382), or
group code plus initials (S0JM).
51 matches
Mail list logo
