View previous topic :: View next topic
|
Author |
Message |
arunkumarvks
New User
Joined: 16 Jun 2008 Posts: 30 Location: Chennai
|
|
|
|
Hi All,
Is it possible to extend the maximum length of TSO userid from Seven to Eight.? |
|
Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007 Posts: 8797 Location: Welsh Wales
|
|
|
|
Why on earth would you want to do that ? |
|
Back to top |
|
|
PeD
Active User
Joined: 26 Nov 2005 Posts: 459 Location: Belgium
|
|
|
|
No
max 7 characters ( USERID) + 1 character = job name |
|
Back to top |
|
|
arunkumarvks
New User
Joined: 16 Jun 2008 Posts: 30 Location: Chennai
|
|
|
|
Yes, this is one of our requirement to use eight character TSO id. As of now i extended the IKJLPENU from seven to eight.But the exit IKJPARS not allowing the eight characters.
we have the source code for IKJPARS and modified it. but its shows the following error when compiling,
** ASMA068S Length error - CBLTPDE
** ASMA044E Undefined symbol - TEMPPDE
do you have any idea to overcome this issue? |
|
Back to top |
|
|
PeD
Active User
Joined: 26 Nov 2005 Posts: 459 Location: Belgium
|
|
|
|
I repeat : I don't think you will be able to extend to 8 characters.
The design is not prepared to accept that. I suspect you will have a lot of problems .... and never succeed.
Pierre
Now the reason already asked by Expat : why do you want to do that? |
|
Back to top |
|
|
arunkumarvks
New User
Joined: 16 Jun 2008 Posts: 30 Location: Chennai
|
|
|
|
thanks PeD... just i am trying only... |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
From the TSO/E Administration manual:
Quote: |
2.1.2 Selecting a User ID
TSO/E and the z/OS operating system require that each user be assigned a unique user ID. This ID must be unique to the system's node, but can be a duplicate of another ID used by another node. The ID can either be chosen by the user or the system administrator depending on your installation's administrative guidelines. However, a number of operating system restrictions apply to the ID naming convention; your administrative policy may have defined others.
A user ID is often the user's name, initials, or department number, or any combination of valid characters you and the user choose with the following restrictions:
* Length - no longer than seven characters |
so you cannot define the TSO user id as 8 characters, period. |
|
Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007 Posts: 1512 Location: Virginia, USA
|
|
|
|
Well other that rewriting TSO/E, ZOS and any subsystem or applications that reference the USERID I don't see where it would be a problem. And don't forget all the documentation and future updates. |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Now that would take a bit of time! |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
As of now i extended the IKJLPENU from seven to eight |
Suggest you very quickly change it back. . . |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2546 Location: Silicon Valley
|
|
|
|
fyi. RACF ids can be 8 characters. They can be used by started tasks (no TSO access).
You might even be able to use 8 character ids on batch jobs (I am not sure). But you cannot logon to TSO with them. |
|
Back to top |
|
|
arunkumarvks
New User
Joined: 16 Jun 2008 Posts: 30 Location: Chennai
|
|
|
|
Thanks to All,
Any reason behind to restrict the length of TSO user id..? |
|
Back to top |
|
|
Robert Sample
Global Moderator
Joined: 06 Jun 2008 Posts: 8696 Location: Dubuque, Iowa, USA
|
|
|
|
Jobs submitted via TSO can use the user id plus a single character suffixed to make up the 8-character job name. This is probably why the 7 character limitation to TSO user ids. |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2546 Location: Silicon Valley
|
|
|
|
Our site allows arbitrary job names, so I do not think that is the limiting factor.
I think system control blocks only have room for 7 characters. And you cannot expand them. There are many customer and vendor products that would have to be changed, so IBM will not change it. |
|
Back to top |
|
|
PeD
Active User
Joined: 26 Nov 2005 Posts: 459 Location: Belgium
|
|
|
|
Quote: |
Our site allows arbitrary job names, so I do not think that is the limiting factor.
|
As I said before, I think it is the real limiting factor.
Just my opinion but I can dig |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2546 Location: Silicon Valley
|
|
|
|
Repeat: "Our site allows arbitrary job names"
So if jobname was the principle reason that prevents 8 character TSO userids, then there is a way around it. But it is -not- the main reason. |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
I believe the limiting factor is based on length of member name in a PDS
TSO used to store (and still can) Userid information in a member in the UADS dataset. The format of the member name is USERID plus one char |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10872 Location: italy
|
|
|
|
the main reason for userids being 7 chars is that
a PDS member name can be 8 chars,
mvs stored tso user info in a PDS ( SYS1.UADS)
with a member name composed of the userid plus a zero
if I can find it I will try to post the reason why the appended 0 |
|
Back to top |
|
|
PeD
Active User
Joined: 26 Nov 2005 Posts: 459 Location: Belgium
|
|
|
|
At one time, I think the extra byte was to retain the length of the UserId.
Still in use? |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Quote: |
if I can find it I will try to post the reason why the appended 0 |
Might it have been an Oh rather than a zer0?
Once upon a time many things were maintained with a 7-max member name length so a backup (old) copy of same could be saved as memnameO. . . |
|
Back to top |
|
|
nevilh
Active User
Joined: 01 Sep 2006 Posts: 262
|
|
|
|
Each user can have multiple entries in the Uads dataset depending on number of logon procs they have access to etc and the blksize of the Uads dataset. First entry will be suffixed with 0 subsequent entries with 1,2,3 etc |
|
Back to top |
|
|
arunkumarvks
New User
Joined: 16 Jun 2008 Posts: 30 Location: Chennai
|
|
|
|
Hi All,
Thanks for your valuable information to know about TSO user id information. |
|
Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006 Posts: 6250 Location: Mumbai, India
|
|
|
|
Pedro wrote: |
"Our site allows arbitrary job names" |
Are you allowed to use 9 charactes for JOB name ? |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2546 Location: Silicon Valley
|
|
|
|
No, the job names are still eight characters. While my userid is PEDRO, I can submit a job called COMPILE or any arbitrary name. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Quote: |
Are you allowed to use 9 charactes for JOB name |
The system will not allow 9-position job names. . .
Many different organizations have many different rules as to what constitutes a valid job name. . . |
|
Back to top |
|
|
|