If it's broken, AWSBrowse will report it (and then ignore the garbage and only show you the valid data).
AWSBrowse does not report anything, so I'm assuming the tape is okay. I applied AWSFixTape anyway just in case.
Yet an error still occurs while trying to load a file. I am using the module petape from the tape, since neither the CMS command tape nor vmfplc2 work on that tape (WATERLOO2.aws):
Ready; T=0.01/0.01 23:45:44
petape rew
Ready; T=0.01/0.01 23:47:37
petape fsf 3
Ready; T=0.01/0.01 23:47:41
petape load
LOADING.....
M0003V00 MEMO
M0003V00 DOCUMENT
DMSTPE110S ERROR READING 'TAP1(181)'.
Ready(00100); T=0.01/0.01 23:47:45
According to AWSBrowse, the file has 24 blocks. I can clearly see the memo, the document, and the assembler code in some of the blocks with AWSBrowse.?And just to make it more fun, sometimes petape works fine:
Ready; T=0.01/0.01 00:09:32
petape rew
Ready; T=0.01/0.01 00:09:40
petape fsf 2
Ready; T=0.01/0.01 00:09:44
petape load
LOADING.....
M0002V00 MEMO
M0002V00 DOCUMENT
DEFINE? ?ASSEMBLE
DEFTBLV? ASSEMBLE
END-OF-FILE OR END-OF-TAPE
Ready; T=0.01/0.01 00:09:47
Could it be that the problem is not the tape, but the petape module instead?