Gerhard Postpischil wrote: >>This could be done except for TSO, due to unfortunate dependences on both the >>high and low portion of the data set name. The designers, in their infinite >>wisdom, chose to define the PSCB to contain a 7-byte user id (or user >>specified prefix), followed by a one byte length.
Indeed. I have a re-look at my ISPF Exit 16, and found that if you change any limits on HLQ (and others too) that exit (and others which allocate datasets) will not work. It is about [somewhat clumsy] usage of PREFIX. Paul Gilmartin wrote: >Under TSO, I was able to allocate a data set with both HLQ and LLQ of 8 >characters; edit it (with ISPF) and browse it. I couldn't catalog it because >I don't know of an 8-character HLQ to which I have access, but I believe >that's an administrative limitation, not anything imposed by the OS. This is >a good example of not letting the limitations of one component (TSO) impose a >restriction on many others. I believe you can do that with 8 char HLQ, but I need to test it too. About raising length limits of HLQ, you will have to redesign RACF, JES2 and modules used to allocate temp dsn. >I'm eagerly waiting for the support to grow. Me too. :-) Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
