On Fri, 16 Sep 2016 13:13:25 +0800, Timothy Sipples wrote:
>Tom Marchant wrote:
>>Yes, AFAIK TSO is still an acronym for Time Sharing Option. Big deal.
>>TSO was an option for OS/MVT. It never was an option for MVS.
>
>Of course TSO is optional in the plain meaning of the word...
Oh, sure, you co
On Thu, 15 Sep 2016 16:36:06 -0500, Paul Gilmartin wrote:
>On Thu, 15 Sep 2016 07:01:42 -0400, John Eells wrote:
>>
>>...
>>
>>The 7-character length restriction comes from the same source. Users in
>>UADS have one or more members in that data set, depending on its block
>>size and the number of
Tom Marchant wrote:
>Yes, AFAIK TSO is still an acronym for Time Sharing Option. Big deal.
>TSO was an option for OS/MVT. It never was an option for MVS.
Of course TSO is optional in the plain meaning of the word, beyond de
minimis use at least. That should have been clear from my Cognos example.
riginal Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Paul Gilmartin
Sent: Thursday, September 15, 2016 2:36 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: TSO User ID Rules (Was: z/OS and code pages)
On Thu, 15 Sep 2016 07:01:42 -0400, J
On Thu, 15 Sep 2016 07:01:42 -0400, John Eells wrote:
>
>The MVS restriction stems from the need to name PDS members starting
>with an alphabetic or national character, as all users were originally
>
That "need" is largely a superstition. Consider the following from an
ISPF member list, retouched
ID Rules (Was: z/OS and code pages)
Or was it because the default jobname was tso userid plus 1 character and a
jobname could only be 8 characters?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
(Was: z/OS and code pages)
Did the reason for the 7 char TSO HLQ come from the UADS process needing the
last char in the member name to chain the information for a given TSO ID in
SYS1.UADS (think ACCOUNT Function)?
--
For IBM
st enough.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Thursday, September 15, 2016 10:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: TSO User ID Rules (Was: z/OS and code pages)
Did the reason for the 7 char TSO
iscussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Mike Schwab
> Sent: Thursday, September 15, 2016 10:19 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: TSO User ID Rules (Was: z/OS and code pages)
>
> The TSO ID is used as a HLQ for data set names. Therefore it must
M-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Mike Schwab
> Sent: Thursday, September 15, 2016 10:19 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: TSO User ID Rules (Was: z/OS and code pages)
>
> The TSO ID is used as a HLQ for data set names. Therefore it must meet the
> rules for MVS Dataset
The TSO ID is used as a HLQ for data set names. Therefore it must
meet the rules for MVS Dataset names: first character A-Z@#$, second
to seventh character A-Z@#$0-9, max 7 due to PDS member needing 8th
character. Minimum length determined by site.
On Thu, Sep 15, 2016 at 11:19 AM, Tony Harminc
On Thu, 15 Sep 2016 14:41:20 +0800, Timothy Sipples wrote:
>The O in TSO is "Option," after all.
Yes, AFAIK TSO is still an acronym for Time Sharing Option. Big deal.
TSO was an option for OS/MVT. It never was an option for MVS.
--
Tom Marchant
-
On 15 September 2016 at 02:41, Timothy Sipples wrote:
> Tony Harminc wrote:
>>What, in this context, is an MVS subsystem? ...And where is this
>>text from -- evidently not the RACF Security Administrator's Guide?
>
> You are allowed to take a look at the Administrator's Guide. :)
I already had, a
LISTSERV.UA.EDU
Subject: Re: TSO User ID Rules (Was: z/OS and code pages)
Timothy Sipples wrote:
> "TSO and MVS also require that the first character of user IDs be
> uppercase A - Z, # (X'7B'), $ (X'5B'), or @ (X'7C')."
>
> So what does "M
Timothy Sipples wrote:
"TSO and MVS also require that the first character of user IDs be uppercase
A - Z, # (X'7B'), $ (X'5B'), or @ (X'7C')."
So what does "MVS" mean in this context? The Administrator's Guide doesn't
say. "Not z/OS UNIX System Services" is a reasonable answer, but it might
be
Paul Gilmartin wrote:
>The antiquated TSO restriction is armament for managers
>who oppose moving applications to z/OS.
Microsoft Windows supports only 26 drive letters, an "antiquated
restriction" lifted from CP/M. CP/M might have inherited drive letters from
CP/CMS (minidisks). CP/M debuted 43 y
On 14 September 2016 at 02:05, Timothy Sipples wrote:
> (a) If you want your RACF ID to be usable within MVS subsystems, the first
> character cannot be a numeric digit (0 through 9).
What, in this context, is an MVS subsystem? And what does "to be
usable within MVS subsystems" mean? And where i
On Wed, 14 Sep 2016 14:05:44 +0800, Timothy Sipples wrote:
>zMan wrote:
>>If my name were "*�tienne*", would I be able to have that as a TSO userid?
>>Or would I have to suffer through just "*Etienne*", sans accent aigu?
>
>a RACF user ID is 1 to 8 characters in length ...
>
Usage has evolved. P
Timothy Sipples wrote:
I'm afraid not; I concur with the other posters. According to "User naming
conventions" on page 62 of the "z/OS Security Server RACF Security
Administrator's Guide," IBM Publication No. SA23-2289-02 ...
Or maybe an quicker check would be:
READY
adduser Étienne
IKJ5670
zMan wrote:
>If my name were "*Étienne*", would I be able to have that as a TSO userid?
>Or would I have to suffer through just "*Etienne*", sans accent aigu?
I'm afraid not; I concur with the other posters. According to "User naming
conventions" on page 62 of the "z/OS Security Server RACF Securi
20 matches
Mail list logo
