You can almost consistently reproduce this error with a batch job that
executes commands in the Posix shell, especially if the Posix command
or its output is very long. If you abort such a job you get this error.
I think it has to do with the fact that the individual input/output lines
from
Posix commands (Bytestream format) are sometimes not correctly
mapped to records in the spoolfile (variable record size format) because
they are longer than the maximum size of a spoolfile record.

Johan

----- Original Message -----
From: "Paul H Christidis" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, 27 November, 2000 20:43
Subject: [HP3000-L] BAD VARIABLE BLOCK STRUCTURE (FSERR 105)


> Fellow listers,
>
> Twice, since we upgraded from 5.5 pp7 to 6.0 pp2 on 11/19, my backup job
> aborted (just as it was ready to bring the system into operational state)
> with the following error:
>
> 596 <rr>exit
> 597
> 598 END OF PROGRAM
> 599 BAD VARIABLE BLOCK STRUCTURE  (FSERR 105)
> 600 I/O error on input. (CIERR 901)
> 601 REMAINDER OF JOB FLUSHED.
> 602 CPU sec. = 7567.  elapsed min. = 134.  THU, NOV 23, 2000,  3:19 AM.
>
> I'm waiting for the vendor to call me back, and the RC suggests to use
> FSCHECK and look for disc corruption (something that cannot be done until
> tonight) I thought I'd ask if anyone has seen this in their system.
>
> Regards
> Paul Christidis