On 10 July 2014 21:38, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
on 07/09/2014 at 03:27 AM, Barry Merrill ba...@mxg.com said:
While I clearly didn't recollect the correct command names, I do
remember specifically that when one of the commands that used TPUT
was encountered in
The result when running TSO TEST in batch under an 8 char userid is shown below.
//BATCH EXEC PGM=IKJEFT01
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
TEST *(IEBGENER)
L 10.%%+4%+b4%+108% x L(17)
END
The first 7 bytes will be PSCBUSER.
All bytes are blank (x'40') and the length value at the
In
0f990dc213e6fe4c9539d02818273f8c7b1bb...@mcexchmbx01.mclane.mclaneco.com,
on 07/09/2014
at 08:52 PM, Sam Bass sam.b...@mclaneco.com said:
There are at least two TSO control blocks that have a 7 char
userid followed by a 1 byte length. I remember someone back in the
MVT days that someone
In 045501cf9b4f$9f5df3d0$de19db70$@mxg.com, on 07/09/2014
at 03:27 AM, Barry Merrill ba...@mxg.com said:
While I clearly didn't recollect the correct command names, I do
remember specifically that when one of the commands that used TPUT
was encountered in the list of commands in my benchmark
char technical userid to use TSO CONSOLE command
In 045501cf9b4f$9f5df3d0$de19db70$@mxg.com, on 07/09/2014
at 03:27 AM, Barry Merrill ba...@mxg.com said:
While I clearly didn't recollect the correct command names, I do
remember specifically that when one of the commands that used TPUT
Let me try to conclude this thread as it has drifted apart from the original
question to the question whether an 8 char (MVS) userid can become valid TSO
user (which it *cannot*).
My interest was to find out why some TSO commands can be used in a *batch* job
while others (which?) cannot when
On Thu, 10 Jul 2014 21:16:14 +0200, Peter Hunkeler wrote:
Let me try to conclude this thread as it has drifted apart from the original
question to the question whether an 8 char (MVS) userid can become valid TSO
user (which it *cannot*).
My interest was to find out why some TSO commands can be
Could you run it and share the results?
Will do.
--
Peter
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
: Re: Authorizing 8 char technical userid to use TSO CONSOLE command
In 02fa01cf9aaf$b9ddd130$2d997390$@mxg.com, on 07/08/2014
at 08:22 AM, Barry Merrill ba...@mxg.com said:
Not sure if this applies to this issue, but I recall that TSO commands
that issue TPUT will simply stop the rest
There are at least two TSO control blocks that have a 7 char userid followed by
a 1 byte length.
I remember someone back in the MVT days that someone implemented a 8 char TSO
userid. Might have been Stanford or SLAC?
UPTPREFX DSCL7 DSNAME PREFIX
UPTPREFL DSBL1 LENGTH OF
Initially posted on RACF-L (more by mistake tang by intention). Reposting here
with emphasis on the TSO mechanisms I'd like to get some deeper insight.
We're in the process of cleaning up our technical userids. There is a job
running a REXX under IKJEFT01 that is issuing MVS commands via TSO
IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED
IKJ55353I THE CONSPROF COMMAND HAS TERMINATED.+
From what I have read in the FM and in the archives of this forum, I tend to
conclude that there is no way to authorize an 8 character userid to use the
TSO CONSOLE command, is
No, I don't think there is a way to define a valid 8 character TSO userid. ...
Yep, understand that. But that wasn't the question. The question is why some
(most?) TSO commands are working fine under an 8 char userid, whereas some like
CONSOLE obviously don't.
It's mostly my own curiosity
technical userid to use TSO CONSOLE command
Initially posted on RACF-L (more by mistake tang by intention). Reposting
here with
emphasis on the TSO mechanisms I'd like to get some deeper insight.
We're in the process of cleaning up our technical userids. There is a job
running a
REXX under IKJEFT01
Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Peter Hunkeler
Sent: Tuesday, July 08, 2014 8:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Aw: Re: Authorizing 8 char technical userid to use TSO CONSOLE command
Before any TSO commands may be entered, the LOGON command must be used
than what it could in the past.
Thanks
Lizette
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Peter Hunkeler
Sent: Tuesday, July 08, 2014 6:16 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Aw: Re: Authorizing 8 char technical userid
What do you consider an 8 character TSO ID?
I never talked about an 8 character TSO ID, did I? I always wrote (or meant
to write) 8 character userid. And by userid I mean a userid as understood
by MVS, and this has always been allowed to be 8 characters in length. (I'm
sure someone will
The max length of a UID in UADS is 7 characters.
Ed
On Jul 8, 2014, at 2:24 AM, nitz-ibm wrote:
IKJ56644I NO VALID TSO USERID, DEFAULT USER ATTRIBUTES USED
IKJ55353I THE CONSPROF COMMAND HAS TERMINATED.+
From what I have read in the FM and in the archives of this forum,
I tend to
TSO/E does not support user IDs with more than 7 characters. The reason
for this is a historical one. TSO/E user ID information was originally
stored in the user attributes data set, UADS. A PDS, UADS has an
8-character limit on member name length. To save space (remember that
2314s and
On Tue, 8 Jul 2014 13:24:33 -0400, John Eells wrote:
TSO/E does not support user IDs with more than 7 characters. The reason
for this is a historical one. TSO/E user ID information was originally
stored in the user attributes data set, UADS. A PDS, UADS has an
8-character limit on member name
W dniu 2014-07-08 16:04, Lizette Koehler pisze:
What do you consider an 8 character TSO ID?
Please explain your statement. My understanding is TSO IDs are maximum of 7
Chars. A batch job can be the 7Chars + 1. So what may look like an 8 Char
TSOID may just be a batch 8 character name.
I
Paul Gilmartin wrote:
snip
Why only 10? Up to 36 should have been practical.
Your guess is as good as mine, Paul. Since the original TSO (no /E)
product was available in 1971 what is now TSO/E is at *least* 43 years
old. As UADS was a pretty basic part of the overall implementation the
In 02fa01cf9aaf$b9ddd130$2d997390$@mxg.com, on 07/08/2014
at 08:22 AM, Barry Merrill ba...@mxg.com said:
Not sure if this applies to this issue, but I recall that TSO
commands that issue TPUT will simply stop the rest of the
commands in a Batch TSO job,
They don't stop anything, but the TPUT
In 008c01cf9aa4$70193d10$504bb730$@mindspring.com, on 07/08/2014
at 05:02 AM, Lizette Koehler stars...@mindspring.com said:
Over time, there was never an 8 Char TSO ID. Instead several
alterations were made that allowed the TSO ID to look like 8
chars. In the past when you submitted a job in
24 matches
Mail list logo
