Alan Altmark <[EMAIL PROTECTED]> wrote: >dasdfmt should work reliably without any dependence on prior format. I >notice in the dasdfmt code commentary (on Developerworks) that it doesn't >format track 0. Maybe that's ok, maybe not.
>Or maybe it's the dasd device driver causing the problem. On at least some kernel levels, with at least some DASD device drivers, never-formatted DASD won't come ACTIVE -- it stays READY forever (yes, those states seem backwards: ACTIVE is "better" than READY). Hence, I suspect, the original admonition. ...phsiii
