> John Eells wrote: > > Originally, TSO/E user IDs were kept in the User Attribute Data Set > (UADS), a PDS. User IDs with few attributes fit in a single member. > User IDs with many attributes overflow into multiple members. The > member naming convention is USERIDn, where n is a digit from 0 (the > first member) to 9. You can control when IDs overflow by changing the > block size; smaller block sizes split sooner, and larger ones split > later. >
So UADS being a PDS restricted the name to 8 chars. However, because of the way ACCOUNT functioned in maintaining overflow information it reduced the name by 1. However, what in the PDS structure reduced the pds member name to a maximum of 8 chars to start with. Isn't that where the convention started and then permeated to the jobname, and so forth? So I must ask, was it the restriction in the BPAM process that forced the length to be 8 Chars or was there something else? Did this evolve from something more primitive in MVT, MFT or ??? It seemed to me that something in 24bit programming had to cause this design for BPAM to be born. Lizette ---------------------------------------------------------------------- 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
