Good point. However, update-in-place really only *need* be done during the user's session to record profile changes, etc.
Extending the member should only be necessary when the ACCOUNT command is adding segments, in which case it shoul be opened for output and recreate the entire member. > Date: Sat, 6 Nov 2010 10:45:08 -0500 > From: [email protected] > Subject: Re: Why are TSO IDs limited to 7 characters > To: [email protected] > > On Sat, 6 Nov 2010 11:06:09 -0400, J R wrote: > > >I'm not sure I buy this highly speculative explanation. > > > >There's a big difference between not allowing multiple blocks per member and > >not considering second blocks to be necessary. Furthermore, to "solve" the > >problem by introducing multiple members per userid, rather than multiple > >blocks per member, defies credibility. > > > I'm highly speculating about the possibility of update-in-place. If > UADS management employs update-in-place, the only way to extend a > member is to introduce an overflow member. > > -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
