Paul Gilmartin wrote: >How do VBS data sets get "broken"?
From my sour experiences on this planet I will try to explain. In my SMF jobs, years ago, I get nasty 613 abends due to channel error (example message from my documentation) IEC147I 613-1C,IFG0194K,SMFDMP,TAPE,SYSUT2,0C30,... IEE763I NAME= IFG0194K CODE= 6131C IEC147I LOGREC ID = IEE763I NAME= CBRLLACS CODE= 140366 Now, if it does go undetected and you MOD (next day) after that tape (RC=00), all those MODding are just a waste of time and resources, since you can only read your SMF data up to the point on the tape where that abend took place. So your SMF tape layout is something like this: <volser label> <file label> <rec 1> ..... <last full intact rec n> <half written record - point of 613 abend> <--- unreadable by IFASMFDP <MODded rec 1> <--- Can that program mentioned by Barry Merrill read it? ... <MODded rec last> <EOF + EOV> To recover, I read all SMF data of that tape immediately up to the very last readable record to ANOTHER tape. Then I MOD the rest of my SMF data still waiting to be written to that new tape. When RC=00, I copy everything back to the broken SMF data on my tape to reuse it and make it ready for next day SMF job. And make a new backup of course. I got absolutel weary and p*ssed off about those channel errors. Hope this explain those 'broken' VBS datasets on tape. I'm not sure how to explain such broken datasets on DASD. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
