On Sat, 11 Nov 2017 13:35:36 -0600, John McKown wrote: >I am looking at the source code to TSSO 4.3. In particular in program >TSSOINI2. This program does a TSO ALLOCATE of 'SYS1.PARMLIB' (hard coded) >and reads the configuration member, which defaults to TSSOPARM. One thing >that I do _NOT_ see is a EODAD address to process "end of file". It appears >that the TSSOPARM had better have an "END" statement as the last control >card. If not, it appears to me that you'd get an I/O error (read past end >of file). > Does it use BSAM/BPAM on a presumed single-block member, or QSAM?
>Why am I looking? In order to remove the TSO ALLOCAT & FREE of >DSN=SYS1.PARMLIB with an IEFPRMLB REQUEST=ALLOCATE and REQUEST=FREE >respectively. I may also consider removing the BPAM I/O with a >REQUEST=READMEMBER. This will use the standard system PARMLIB concatenation >for the TSSOPARM initialization statements, so that there will be fewer WTF >moments for new users. > A noble quest. That should even be RFE material. If TSO weren't (sort of) functionally stabilized. But is there any component that presumes that TSSOPARM, like UADS, can be updated in place? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
