In order for a new allocation to be SMS managed and go to a managed pack, it must be assigned a storage class. This can be done in JCL but most use the ACS routines. So the question becomes why isn't your ACS routine assigning a storage class. Once you invoke ISMF in administrator mode, you can display the names of the ACS routines. If you can't find the problem by analysis, you can add debugging WRITE statements at key decision points.
Mark Steely <[EMAIL PROTECTED]> wrote: I have implemented SMS for our production files. Everything appears to be working correctly except this one file. It is a IEFBR14 and it is allocating the dataset as non-SMS, but every test I do using the same JCL works correctly. All the other files with this hi-level qualifier are working. What can I do to help track this allocation. I have looked at the SMS routines and can't figure out why it is not being SMS managed. Like I said all my test work correctly and even the test under ISMF work correctly. Any ideas would be greatly appreciated. We are z/OS v1r4. Thanks ---------------------------------------------------------------------- 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 __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ---------------------------------------------------------------------- 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
