Why not just catalog the dataset or use a temp DSN? Is there a real need for an uncataloged dataset?
The messages begin with IGD, so you are working with SMS datasets. While you can allocate / use non-cataloged datasets, I thought they would not be permanently retained. I thought part of the concept was to eliminate uncataloged datasets. If not, then look at your SMS related products. I suspect some allow conversion to delete for uncataloged datasets. I vaguely remember a product that allowed you to write scripts to change dataset disposition based on the criteria you set (20 years ago, I think it was called SAMS). Alternatively, you could try putting the dataset to non-SMS volume. Jon Perryman > On Friday, May 23, 2014 12:31 PM, "Grinsell, Don" <[email protected]> wrote: > > Step 2 indicates that the dataset was deleted: > IGD105I F00.DUMMY DELETED, DDNAME= > > Step 3 is a little more descriptive: > IGD103I SMS ALLOCATED TO DDNAME DD1 > IEF142I xxxxxxF STEP3 - STEP WAS EXECUTED - COND CODE 0000 > IGD17054I DATA SET NOT FOUND FOR DELETE/RENAME ON VOLUME TS741D > DATA SET IS F00.DUMMY > > But then I get this after the step termination blocks for STEP3: > IEF379I xxxxxxF STEP3 - JOB ENDED BECAUSE OF CATALOG ERROR > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
