On Wed, Aug 10, 2011 at 6:50 PM, Scott Ford <scott_j_f...@yahoo.com> wrote: <deleted> > 19.25.29 JOB00166 IGD17040I ERROR IN DADSM PROCESSING FOR DATA SET 570 > 570 SFORD.TEST1 > 570 HISTORIC RETURN CODE IS 4 DIAGNOSTIC INFORMATION IS > 04280039 > 19.25.29 JOB00166 IGD306I UNEXPECTED ERROR DURING IGGDAS02 PROCESSING 571 > 571 RETURN CODE 4 REASON CODE 57 > 571 THE MODULE THAT DETECTED THE ERROR IS IGDVTSDA > 571 SMS MODULE TRACE BACK - VTSDA VTSDL SSIRT > 571 SYMPTOM RECORD CREATED, PROBLEM ID IS IGD00008 > 19.25.29 JOB00166 IEA995I SYMPTOM DUMP OUTPUT 572 > 572 SYSTEM COMPLETION CODE=0C1 REASON CODE=00000001 > 572 TIME=19.25.29 SEQ=00090 CPU=0000 ASID=001A > 572 PSW AT TIME OF ERROR 078D2000 00000052 ILC 2 INTC 01 > 572 NO ACTIVE MODULE FOUND > 572 NAME=UNKNOWN > 572 DATA AT PSW 0000004C - 00FE14B8 00000000 00000000 > 572 GR 0: 00007CA0 1: 00007C40 > 572 2: 00000040 3: 008D79D4 > 572 4: 00000000 5: 00000000 > 572 6: 008C6FE0 7: FD000000 > 572 8: 008D0F88 9: 008CFCC8 > 572 A: 00007B48 B: 008FF350 > 572 C: 00007920 D: 00007B48 > 572 E: 60007AB2 F: 00000050 > 572 END OF SYMPTOM DUMP <deleted>
I was using TSO ISPF 3.4 to try to delete datasets and got similar messages. This was a spare volume I was putting junk datasets on, then trying to delete them. I solved the delete by running and ICKDSK Convert NONSMS on the volume. The VTOC was inited to Storage Group, but no storage group contained the volser. Not sure if this is the case in your situation. -- 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
