The true problem is that the LIKE= parameter does not send the dataset organization across.
I've known about this for years. At one time in the early 1990's I opened a PMR about it. This was an attempt to create a VSAM KSDS wanting to use the LIKE= parameter much the same way as the IDCAMS MODEL paramter. It would have saved an IDCAMS step, allowing even an IEFBR14 to be used. Instead the job kept getting sequential files created with incorrect space allocations also. This would have made file reorg jobs much simpler. I basically got a deaf ear back then. On Fri, 15 Feb 2008 16:09:10 -0600, Mark Zelden <[EMAIL PROTECTED]> wrote: >Interesting. I had an extended off-list thread with someone about this problem >last May after this subject came up. There was really nothing that could be >done because they used the LIKE parameter. > >It appears that IBM has "given in" and is backing out the change made >in z/OS 1.8. > > >APAR OA22738 > >IGD17295I RECEIVED AFTER Z/OS 1.8 HDZ1180 FOR PDS PDSE DATA SETS USING >DYNAMIC VOLUME COUNT DVC II14304 > > > APAR Identifier ...... OA22738 Last Changed ........ 08/02/14 > IGD17295I RECEIVED AFTER Z/OS 1.8 HDZ1180 FOR PDS PDSE DATA SETS > USING DYNAMIC VOLUME COUNT DVC II14304 > > Symptom ...... MS IGD17295I Status ........... CLOSED PER > Severity ................... 3 Date Closed ......... 08/02/14 > Component .......... 5695DF101 Duplicate of ........ > Reported Release ......... 180 Fixed Release ............ 999 > Component Name STORAGE MGMT SU Special Notice ATTENTION > Current Target Date ..08/04/04 Flags > SCP ................... > Platform ............ PERVASIVE > > > Status Detail: TESTPACKAGING - Packaged solution is being tested. > > PE PTF List: > > PTF List: > Release 180 : PTF not available yet > Release 190 : PTF not available yet > > > Parent APAR: > Child APAR list: > > > ERROR DESCRIPTION: > Partitioned data sets are not eligible to be multi-volume data > sets and are normally failed, if they have a volume count > greater than one, with message: > > IGD17293I DATA SET XYZ HAS > PARTITIONED ORGANIZATION AND IS NOT ELIGIBLE > TO BE A MULTI-VOLUME DATA SET, ALLOCATION FAILED > > Because of APAR OA13500, a new message was created: > > IGD17295I dsname HAS PARTITIONED ORGANIZATION AND CANNOT HAVE A > DATA CLASS WITH A DYNAMIC VOLUME COUNT GREATER THAN ONE, > ALLOCATION FAILED > > This change was implemented at base release z/OS 1.8 and will > stop partitioned data sets from receiving a dynamic volume > count greater then one. The change was not documented in the > z/OS 1.8 Migration Guide so info apar II14304 was created to > inform customers to change their ACS routines to prevent > partitioned data sets from getting assigned a Data Class with a > dynamic volume count greater then one. > > New data sets created using the LIKE keyword where the LIKE > data set is a PDS/PDSE will be identified as a physical > sequential data set during ACS processing. This > situation creates a new problem for customers because they are > not able to prevent the IGD17295I via ACS routines. Because of > this new problem this APAR will reverse the changes made in > component 5695DF101. > > Additional Keywords: > msgIGD17295I DVC DATACLAS > > > LOCAL FIX: > Usermod is currently available per customer request to remove > the message. > > > PROBLEM SUMMARY: > **************************************************************** > * USERS AFFECTED: All users of DFSMS V1R8 and higher. * > **************************************************************** > * PROBLEM DESCRIPTION: If a SMS data set with partitioned * > * organization is being created with a * > * DATA CLASS that has a DYNAMIC VOLUME * > * COUNT > 1, this creation will be failed * > * with the IGD17295I message. * > **************************************************************** > * RECOMMENDATION: * > **************************************************************** > This causes problems for customers, particularly those customers > that use the LIKE= JCL keyword on the DD card. The ACS routines > cannot determine if the new data set being created is PO and are > unable to direct these data sets to a DATA CLASS that has a > DYNAMIC VOLUME COUNT of 0 or 1. > > > PROBLEM CONCLUSION: > The DYNAMIC VOLUME COUNT check for PO data sets will be removed. > Consequently the IGD17295I message will be eliminated. > > > > >-- >Mark Zelden ---------------------------------------------------------------------- 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
