Re: SDB (was: I have an Idea for ISPF...)
On Fri, 15 Sep 2023 23:52:23 +, Sri h Kolusu wrote: >>> What's the default DSORG? Does SDB not respect that? I've long trusted >>> SDB. > >SDB is supported foD DSORGs of PS and PO for DASD and tape datasets. > Also for UNIX and JES. I know because at the advent of SDB REXX removed its OPEN exit to allow SDB to operate. That broke my ALLOC SYSPRINT PATH(...) LRECL(137) because SDB defaulted to BLKSIZE(80) for unknown devtype. Fixed promptly by an available PTF. Tier 1 advised me, "*Always* specify BLKSIZE," which I regarded as an ironic consequence of SDB; I ignored it. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: SDB (was: I have an Idea for ISPF...)
>> What's the default DSORG? Does SDB not respect that? I've long trusted SDB. Gil, SDB is supported for DSORGs of PS and PO for DASD and tape datasets. Thanks, Kolusu -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
SDB (was: I have an Idea for ISPF...)
On Fri, 15 Sep 2023 23:25:02 +, Sri h Kolusu wrote: >>> Is there reason not to use BLKSIZE=0, which has been preferred for over a >>> decade (but may not work with COBOL.) > >You can use BLKSIZE=0, but also code DSORG=PS , so that SMS calculates the >Optimum Blksize based on the LRECL > What's the default DSORG? Does SDB not respect that? I've long trusted SDB. I assume SDB operates *after* the DCB OPEN exit, for compatibility with ancient code. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
