Thank You Matthew, the absence of an exclusion in the Storclas routine apparently was at the root of the problem, along with having Sys%r% enclosed in apostrophes.
The allocations are now working as desired. I'm still at a loss to explain the inconsistency but it now works so time to move on. Regards, Dave O'Brien NIH Contractor ________________________________________ From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of Matthew Stitt [mathwst...@bellsouth.net] Sent: Thursday, February 12, 2009 3:23 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Dataset allocation is SMS managed on 1 LPAR and not another?? All right, let's quit fumbling around. It is the assignment of a valid storage class which determines the dataset is going to SMS managed volumes. Data class and Management class have no bearing on this problem. I would examine the STORCLAS routine on the aberrant system to figure out why the dataset got assigned a valid storage class. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
