I would tryQuote:> When I run mksysb, it gives OK looking output then nothing
> happens for hours. If I hit return I see:
> a ./Assessor/support/detailed_coding.txt 5 blocks.
> a ./Assessor/support/coding.txt 4 blocks.
> a ./Assessor/support/tool_reuse.ezX 210 blocks.
> a ./audit
> a ./.kshini 1 blocks.
> 0512-005 mksysb: Problems in making the system backup.
> It sat for hours after the .kshini line.
> Is this just what it looks like?
> I used the following command:
> mksysb /dev/rmt0 ; mt -f /dev/rmt0 offline
> After I hit the return the tape ejected OK.
1. a new tape (I know, I know, too obvious)
2. check the errpt to see if the tape drive is logging any errors during
this procedure
3. run it (just for the heck of it) without multiple commands on the same
line.
4. use 'diag / service aids / backup + restore device check' to check the
drive
BTW: our mksysb (ver. 3.2.5) only takes 40 minutes to run - don't wait for
hours!
(I'm assuming you have 3.2.5 as 4.1.4 doesn't display the file names as it
puts them to tape)