So maybe something in your ACS routines is causing your trouble? Yes, I did the allocation with 0 specified in the BLKSIZE and BLANK. Worked fine..
Lizette > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Lizette Koehler > Sent: Wednesday, January 11, 2017 6:25 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: SDB and Program Object Library > > I just used Option 3.2 and allocated a PDSE with LRECL 80 and Blksize 0 with > Version 2 (z/OS V2.1) > > No issues - it took it fine and the Blksize is 32760. > > Lizette > > > > -----Original Message----- > > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > > On Behalf Of Paul Gilmartin > > Sent: Wednesday, January 11, 2017 5:12 PM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: SDB and Program Object Library > > > > In order to copy a load module library to a progam object library I > > used ISPF Data Set Utility to allocate the new library with > > DSNTYPE=LIBRARY. Believing that "SDB knows best," I left BLKSIZE > > blank. ISPF warned me. I told it, "Trust me." I went to Move/Copy > > Utility and tried the copy. It failed: can't deal with BLKSIZE=0. > > Curious, I deleted and re-created with BLKSIZE=1(!?) and retried the copy. > > Succeeded, and as a side effect set BLKSIZE to 4096. > > > > Is there any rationale to this logic, that BLKSIZE=0, which is > > supposed to defer the choice to SDB, fails, while the absurd BLKSIZE=1 > > succeeds and SDB operates? > > > > -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
