>>#2 - Stop giving me 3K and 6K blocksizes, loadlibs should be blocked at 32760 >>and everything else should get 0 for SDB (unless you have a wacky format like >>CA-Viewpoint). >> >Does SDB make an adverse selection for loadlibs? Has a suggestion >been made to IBM to ameliorate this? How much worse, by what >metric, is SDB's default (half track?) than 32760? >
I understood the BINDER, aka linkage editor, knows how to utilize the space in a LOADLIB, so 32760 is the best number to use. Following the earlier suggestion to use 32760 on a loadlib and 0 everywhere means SDB is not choosing a blksize for loadlibs, and I agree that is fine. Before SDB can choose 32760 for every RECFM=U LRECL=0 dataset, the user community would have to swear this is never used for other than a loadlib. Until then, the two BLKSIZE values work for me. As for stupid PROCs versus DDDEFs - in my opinion, SMS means uniquely named datasets and they are are catalogued so a DDDEF only needs to have DSNAME and DISP. If a vendor has trouble doing this, they are stupid. UNIT=SYSALLDA during allocation makes perfect sense. My ACS routine will assign a volume. For those shops working in the 1980's (non-SMS), they can add parameters to make the install complete. Use today's technology. ---------------------------------------------------------------------- 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
