When I was a Storage Admin I fixed or changed the Management Class for datasets that had this problem. If the batch window is blowing out because of this problem then there is something wrong with the SMS policies. IEFBR14 and DFSMShsm are just innocent bystanders.
> > I fear we're losing the forest for the trees. Here's the problem. > > Say I'm in a large production shop. We have production JCL that runs to > hundreds of thousands or perhaps millions of lines spread across myriad > batch jobs. Jobs often stall due to recalls before data sets are > deleted; once in a while I blow a batch window because of this. I know > how to change the jobs to eliminate the problem, and I do it when I > must. But every change to every production job is moderately > labor-intensive: > ---------------------------------------------------------------------- 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
