Alejandro olivan Alvarez wrote:
I attach the configuration file I use, and the hercules log
(which is very long!)
[...]
I noticed two messages appearing just before the I/O error:
I find relevant that, just before the I/O Error, two lines
show up that look very suspicious:
11:15:00 HHC00204E 0:0281 Tape file tape/power-deblock.aws,
type aws: error in function readhdr_awstape(), offset
0x0000000000000D20: end of file (uninitialized tape)
and:
11:15:00 HHC00204E 0:0280 Tape file tape/ibm.360d052006.dos.
power.II.with.rje.opt2.v4m1.aws, type aws: error in function
readhdr_awstape(), offset 0x0000000000000D0A: end of file
(uninitialized tape)
Strangely but, before these errors show up, there was a lot of
activity both on the log regarding devices 280 and 281, and on
the tape files themselves, as I see on the filesystem that their
sizes changed, so it looks like hercules was initially happy
handling the tapes but at some point the thing went wrong.
Yep. I'm seeing the same thing.
But before we get to that, PLEASE REMOVE YOUR:
LOG herclog.log
STATEMENT FROM YOUR CONFIGURATION FILE, and specify a *proper* log file via the '-o' or '--output' or '--logfile' command line option instead!
*
What you sent me was NOT the full/complete Hercules logfile! It is only a partial logfile. It is missing perhaps the most important part of a Hercules logfile: THE VERY BEGINNING, that contains all of Hercules's startup initialization messages!
I would recommend NEVER using the 'log' statement or command EVER! Never ever! Using it make it virtually impossible to provide proper support for a person when they're having problems, since we cannot see what version of Hercules they are using and other important things that get logged during Hercules startup and initialization.
Thanks.
Now... About your problem...
Looking at your log file, it is painfully obvious to me there is an extremely high likelihood that DOS/360's "TPTP" program (or DOS/360 itself) is buggy.
The problem does NOT appear to me to be with Hercules. The problem is instead, with an extremely high degree of likelihood, with TPTP and/or DOS/360.
Tape 280 is the INPUT tape, yes?
And 281 is the OUTPUT tape, yes?
"TPTP" is a simple(?) program that is supposed to READ the specified input tape, deblock each physical block of data that it reads from that input tape, and then write the individual unblocked records from that block to the output tape. Yes? Pretty simple.
Well, for some very strange unknown reason, TPTP (or DOS/360) --in the middle of its processing! -- is deciding to suddenly and unexpectedly switch from *reading* its input tape, to, oddly enough, start *WRITING* to it instead! (WTF?!)
Yes, you read that sentence correctly: It is deciding for reasons unknown to start *WRITING* to its *INPUT* tape! (WTF?!)
AND... it decides at the same time, to also suddenly and unexpectedly switch from writing to its output tape to READING from it instead! (WTF?!)
Yep! It decides for some unknown reason (likely due to the same bug I'm guessing) to start *READING* from its *OUTPUT* tape! (WTF?!)
DUE TO THIS APPARENT BUG, I would *strongly* recommend that you re-download your "ibm.360d052006.dos.power.II.with.rje.opt2.v4m1.aws" input tape file, and *immediately* set it to read-only, to ensure that it cannot be damaged due to this bug.
Where did you download it from anyway? I'd like to take a look at it myself with my AWSBrowse program to see what it looks like. Thanks.
Finally, for the record, since you failed to provide a COMPLETE Hercules log, what version of Hercules are you using, and on which type of host are you running it on? Windows? Linux? Which Windows? Which Linux?
Thanks.
I hope that helps!
--
"Fish" (David B. Trout)
Software Development Laboratories
mail: fish@...
