--- snip -- Bruce, This conflicts with BLKSIZE=0 being used for SDB. SDB does not work unless DSORG can be established. BLKSIZE=0 is a null - SDB requires DSORG and no BLKSIZE. Additional DCB depends on the DSORG.
Most sites have a default DATACLAS that will allocate with DSORG=PS if nothing else can be determined. This allows SDB to work, and also ensures SMS datasets have an EOF at allocation. Ron > (the DSORG is not > determined until the dataset is opened for output -- snip -- We've just noticed (z/OS 1.8) that a problem was fixed with DSORG=PO data sets and dynamic multivolume. Our ACS routines (as probably other sites also do) check for DSORG. A DATACLAS with dynamic multivolume capability is assigned to most data sets, unless they don't support mulitvolume (DSORG=PO). This had worked well in the past. Data sets that have an unknown DSORG also had a DATACLAS assigned to them (with DYNVOL) specified. Unfortunately, some of the unknown DSORG data sets happened to be PDS data sets that were allocated with the LIKE parameter (DSORG is NOT passed to the ACS routine when LIKE is used). This now results in an allocation error. Be careful with assigning a DATACLAS to an unknown DSORG allocation in SMS. John PS. Good to hear that you're still around Ron. ---------------------------------------------------------------------- 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
