Two things, Skip...
First, your assumption is quite understandable.
As a severely CDO programmer, I have always been
deeply offended by IBM's placement of the
username length field in the PSCB and UPT.
Second, I think the most likely way IBM will deal
with this is to do what it has done in the past...
1) Create new fields to hold the longer names and their lengths.
2) Create a flag to indicate that the new fields exist.
3) For names that will fit, put that name into both fields.
4) For names that won't fit, put it only in the new field,
and set the old field to some indicative keyword such as
" INVALD", "!WRONG", "*NOTHIS" or some such.
At 2/6/2017 04:57 PM, Jesse 1 Robinson wrote:
I stand edified. Had not seen the inverse, which
I feel is kind of unusual. In general, when a
field is governed by a length indicator, it
seems that most often the length comes first. In
this case, since the overall field itself is
fixed, it doesn't much matter where you put the
length. Maybe an EXecute MVC or CLC is a tad
simpler if the thing being handled comes first.
In any case, finding room for an 8th meaningful
character is going to be a massive undertaking.
Besides OA51203 (which looks like Omegamon),
there are going to be a ton of supporting APARs.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office â=== NEW
[email protected]
-----Original Message-----
From: IBM Mainframe Discussion List
[mailto:[email protected]] On Behalf Of David Cole
Sent: Monday, February 06, 2017 12:22 PM
To: [email protected]
Subject: (External):Re: Eight-character TSO Userid Support
At 2/6/2017 02:51 PM, Jesse 1 Robinson wrote:
"In one sense, TSO userids have always 'tied
up' 8 bytes, but the first byte by convention
has always been the length of the actual
userid in the next 7 characters. This
structure is utterly pervasive throughout
TSO(/E). Not just IBM processes but countless
RYO and third party processes as well. Even
the structure of UADS for a user is set of
multiple members named as userid+digit, which
requires an id of 7 characters or less."
Uh no. In a couple of major TSO cblocks, it's a
7 character field FOLLOWED by the length field...
Examples:
PSCBUSER DS CL7 USERID PADDED RIGHT WITH
BLANKS 03-IKJPSCB
PSCBUSRL DS CL1 LENGTH OF
USERID 03-IKJPSCB
and
UPTPREFX DS CL7 DSNAME
PREFIX Y02669 03-IKJUPT
UPTPREFL DS BL1 LENGTH OF DSNAME
PREFIX Y02669 03-IKJUPT
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: [email protected]
Home page: www.colesoft.com
LinkedIn: www.xdc.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
Dave Cole
ColeSoft Marketing
414 Third Street, NE
Charlottesville, VA 22902
EADDRESS: <mailto:[email protected]>[email protected]
Home page: www.colesoft.com
LinkedIn: www.xdc.com
Facebook: www.facebook.com/colesoftware
YouTube: www.youtube.com/user/colesoftware
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
