If that is a non-sms volume, check SYS1.PARMLIB(VATLSTxx). If that is a sms volume, check you ACS routines.
On Tue, May 10, 2011 at 3:07 PM, Thomas David Rivers <riv...@dignus.com> wrote: > Just to follow up... > > As every good programmer knows; when the user asserts > that nothing has changed - it's clear something *has* changed. > > In fact, the SBSYS1 volume was full of junk; and I suppose IEBCOPY > couldn't mount whatever-was-next and so reported it was unable > to mount (instead of telling me which volume was full.) > > I discovered which volume IEBCOPY was using by doing a TRANSMIT > of a pretty-empty PDS (which succeeded). From the "success" messages > I gleaned which volume IEBCOPY was using and I was hot-on-the-trail > after that.... > > Thanks for the pointers! > > - Dave Rivers - > > > -- > riv...@dignus.com Work: (919) 676-0847 > Get your mainframe programming tools at http://www.dignus.com > > ---------------------------------------------------------------------- > 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 > -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- 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
