We've encountered the same issue after upgrading our test environment from 1.6 to 1.8. While we were on z/OS 1.3, we made the ACS coding change to assign PDS/PDSEs to a dataclas that does not allow multi-volume capability. Unfortunately, the use of LIKE has allowed the proliferation of inappropriately assigned dataclasses to go unchecked. Most folks aren't fully aware of the limitations associated with the LIKE parameter.
In a PMR, we've asked IBM to remove the restriction even though were are well aware that end-of-volume extent processing may fail for PDS/PDSEs. That risk has been around for sometime. We know it is in out best interest to get all PDS/PDSEs assigned to the proper dataclass a.s.a.p. Currently, there is no ALTER support for dataclass. One of our sysprogs opened an enhancement request to IBM back in 2005 to be able to alter the dataclass. The request is MR0117055621. The only way to change the dataclas for a dataset is to delete and redefine the dataset. Since we don't know how extensive the use of LIKE is in our shop, we are unwilling to rollout z/OS 1.8 into our production environments. We have searched extensively for any announcement of this new PDS/PDSE dataclass restriction and found none. It is our hope that there is a significant number of IBM customers out there who have the same issue and are willing to apply due pressure on IBM to lift the restriction or provide alter support for dataclas. Terry Traylor charlesSCHWAB TIS Mainframe Storage Management Remedy Queue: tis-hs-mstg (602) 977-5154 WARNING: All email sent to or from this address will be received by the Charles Schwab corporate e-mail system and is subject to archival and review by someone other than the recipient. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Hall Sent: Thursday, May 24, 2007 10:39 PM To: [email protected] Subject: Re: z/OS 1.8 upgrade ________________________________________________________________________ _______________ Note: This e-mail is subject to the disclaimer contained at the bottom of this message. ________________________________________________________________________ _______________ <snip> Can you share your experiences with us? We are just starting a z/OS 1.6 -> 1.8 migration ourselves. </snip) So far we have only upgraded 2 Sysprog LPARS so far (one RACF, one ACF2). Our only problem so far is with SMS & the LIKE parameter for PO or POE datasets (both within JCL & TSO). With z/OS 1.6 these files can be created with our DEFAULT Dataclas that has Dynamic Volume Count set to 2. If we try the same allocation using z/OS 1.8 we receive the following error message; IGD17295I DATA SET dataset.name HAS PARTITIONED ORGANIZATION AND CANNOT HAVE A DATA CLASS WITH A DYNAMIC VOLUME COUNT GREATER THAN ONE, ALLOCATION FAILED We have now coded SMS on all our systems to prevent PO/POE files from receiving the DEFAULT dataclass but there is one exception that cannot be controlled by SMS, and that is when using the LIKE parameter. SMS does not recognise the DSORG passed from the model dataset when using LIKE to allocate datasets in JCL or REXX/CLISTS. PO/POE datasets allocated using LIKE will fail with the message mentioned above. To prevent this the DSORG parm needs to be coded in any exec of JCL. Regards, Stephen Hall Technology Services Insurance Australia Group (IAG) Melbourne VIC . ________________________________________________________________________ _______________ The information transmitted in this message and its attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information, by persons or entities other than the intended recipient is prohibited. If you have received this in error, please contact the sender and delete this e-mail and associated material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files, with the permission of the sender. This message has been scanned for viruses with Symantec Scan Engine and cleared by MailMarshal. ________________________________________________________________________ _______________ ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
